Assistant
We strongly recommend to readRules section "Android - firmware"
New threads need to be created only inroot partition! In the future, they will be processed by moderators.
REPLY |
Cube U55GT Talk 79 - Official firmware (OS 4.2) |
Message#42 25.02.14, 10:35 | |
Visitor [offline] Group: Users Messages 12 Check in: 11.06.13 Jiayu G2 Dual Core Reputation: 0 | [email protected], 03:30 For information: I tried to compile TWRP 2.5.0.0 for our device today and it doesn’t start, the port did mini7_TWRP_recovery, I also tried TWRP + Recovery_THL_W7s also, it’s stuck on the splash screen and that's it, tomorrow I’ll try to compile from the sources but something It does not tell me, maybe the resources for resolution 1024x768 did not fit? if someone tried to collect, with a positive result, share your thoughts ... Smoking forum stumbled upon info that for TWRP in our device you need to change the size of the file system partitions, otherwise nothing ... |
Message#43 25.02.14, 13:33 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | kau4uk Smoking forum stumbled upon info that for TWRP in our device you need to change the size of the file system partitions, otherwise nothing ... You are absolutely right; I increased the recovery size to 10Mb. |
Message#44 25.02.14, 17:16 | |
Help [offline] Topics Curator Group: Curators Messages 3276 Check in: 30.09.08 Blackview BV6000 Reputation: 597 | Attention !!! after firmwarepatched bootandTWRP recoverythrough wonderful softwareMtkDroidTools got a dead touchscreen similar problems no "dancing with a tambourine" question is not decided (I used the mouse) tablet returned under warranty so I already haveThree trues Post has been editedDigins - 26.02.14, 04:30 -------------------- |
Message#45 25.02.14, 18:50 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 271 Check in: 24.11.12 Oneplus X E1003 Reputation: 14 | [email protected], 18:16 got a dead touchscreen ImaSoft don't take chances! We still need you ;-) -------------------- |
Message#46 25.02.14, 21:19 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | [email protected], 16:16 Attention !!! after flashing the patched boot and TWRP recovery through the wonderful MtkDroidTools software, it received a dead touch-screening "dancing with a tambourine" did not solve the question (used the mouse), the tablet returned under warranty I had THREE TROUBLES And in more detail please? Posted 02/25/2014 21:18: [email protected], 16:16 after flashing the patched boot What patched boot? Where does he give a look at him? Posted 02/25/2014, 21:19: [email protected], 16:16 so I have already three trupe Cool!!! |
Message#47 26.02.14, 16:59 | |
Veteran [offline] Group: Friendssavagemessiahzine.com Messages 1737 Check in: 14.09.13 Xiaomi Mi 4c Standart Reputation: 320 | [email protected], 18:16 after flashing the patched boot and TWRP recovery through the wonderful MtkDroidTools software boot and MtkDroidTools have nothing to do with it. The wrong TWRP recovery is guilty, the method of its installation is not important. -------------------- Xiaomi Mi4c (Resurrection Remix N) |
Message#48 26.02.14, 17:58 | |
Help [offline] Topics Curator Group: Curators Messages 3276 Check in: 30.09.08 Blackview BV6000 Reputation: 597 | gray.cat, In the heat of fever, I forgot to remember "gray"as one of the victims. MDTI do not scold at all, I am stating a fact. A similar method of preparation and successful installation of TWRP, tested on several MTK 6589-8389 devices with different screen resolutions. OnZTE One S, after that I received a "bootlup" and a few hours of "dancing with a tambourine" to restore the device !!! -------------------- |
Message#49 26.02.14, 18:12 | |
Veteran [offline] Group: Friendssavagemessiahzine.com Messages 1737 Check in: 14.09.13 Xiaomi Mi 4c Standart Reputation: 320 | |
Message#50 26.02.14, 18:44 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | gray.cat, In the heat of a fever, I forgot to remember "gray.cote" as one of the victims. MDT, I do not in any way abuse, I state a fact. A similar method of preparation and successful installation of TWRP, tested on several devices MTK 6589-8389 with a different screen resolution. People, I feel somehow deprived, give the links to read where you experimented, where they discussed what method, and here boot, I don’t understand anything !!! p.c. I CWM reworked everything in manual as TWRP did in general, according to the classical scheme. Post has been editedImaSoft - 26.02.14, 18:48 |
Message#51 26.02.14, 20:32 | |
Veteran [offline] Group: Friendssavagemessiahzine.com Messages 1737 Check in: 14.09.13 Xiaomi Mi 4c Standart Reputation: 320 | |
Message#52 26.02.14, 22:43 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | gray.cat, can break the touchscreen controller firmware, which is treated only by replacing the latter. I googled the topic of discussion, in the end I did not find anything about this, I can assume that this is not the TWRP (recovery) binary itself, but most likely in the kernel that is not from our device, which is sewn up in the recovery.img itself, the binary itself can hardly Something to spoil in the device itself, I understand that they sewed TWRP (recovery.img) from another device! Post has been editedImaSoft - 26.02.14, 22:46 |
Message#53 27.02.14, 04:34 | |
Help [offline] Topics Curator Group: Curators Messages 3276 Check in: 30.09.08 Blackview BV6000 Reputation: 597 | I can assume that the matter is not in the TWRP (recovery) binary itself, but most likely in the kernel that is not from our device, which is wired in the recovery.img itself I will certainly ask a questionrua1, but it seems that by choosing "boot from the body, and recovery from the analog", the kernel is taken native (from boot.img), and ramdisk from the analog. and of course Inotsew left preloader -------------------- |
Message#54 27.02.14, 08:07 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | Nothing like this is taken from recovery.img, boot.img can be completely broken, so it happens after the redistribution of partitions, I don’t even upload it back, it will only be installed with the firmware, but I can assume that if there is no kernel in recovery.img Maybe it can be taken from boot.img but this should be checked. Still, how did you sew TWRP without expanding the recovery section? |
Message#55 01.03.14, 00:01 | |
Veteran [offline] Group: Friendssavagemessiahzine.com Messages 1415 Check in: 31.12.11 Oneplus one Reputation: 16 | I use framaroot, and never had any problems. After the first attempt to get the root, the program closes. Therefore, run it again, choose supersu and presses on boromir or another "uncle" and everything should work out. I did likewise, downloaded fromsavagemessiahzine.cominstalled. I started the program, chose SuperSu and Boromir, the tablet blinked and threw it on the desktop, I launch the second time I put SuperSu and tried different options, but it all comes down to this ... Already delivered and reset to factory settings, I launch framaroot and nothing happens until you select an exploit. And then the bother described above Post has been editedAlexeyHunter - 01.03.14, 00:18 -------------------- Home bodies: Ainoi Fire (sold out) / FreeLander PD20 Great Vision (given to father) / Hyundai A7HD (given to mother) / Hyundai T7S / HTC Incredible S / Huawei U9508 (given to father) / Lenovo A789 (working) / Lenovo A660 (given to mother ) / Xiaomi MI 2S (?) |
Message#56 02.03.14, 09:43 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | For information: In the continuation of thisfasting, I picked yesterday again with TWRP and came to the depressing conclusions !!! I found the reason for not collecting the collected TWRP by me and as the reason it turned out that: as I wrote the recovery section earlier, I increased it from 6144kB to 10000kB but !!! That's not all, experimenting yesterday, I was surprised that if I added any 800Kb file to my ramdisk working CWM, then it becomes not working, I was shocked as I already checked it and that way, as a result, at least the size and partition output Increasing to 10MB then this will not give anything, as soon as the final recovery.img image passes for 6144kB then it all becomes not working, the output is such that the bootloader in uboot, stupidly when loading the recovery partition into memory, does not check the size of the partition itself, but loads its with a clear length of 6144kb in memory and if our size is larger than the size of 6144kb it just becoming not working, googling a bit I found the answers to my questions here>>here<<, the output should be like a patch uboot, so the idea with TWRP is still postponed! Post has been editedImaSoft - 02.03.14, 14:01 |
Message#57 06.03.14, 02:20 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | For information: I turned to the room, asking for help to flash the tablet.grafich_29my firmware, the request was that it does not mount disks in CWM, using USB_Storage protocol on the BB, as a result of the analysis it turned out that under CWM the microSD card doesn’t see the microSD card and, accordingly, there is no mmcblk1p1 block, in general the solution was found In the manual mode, the internal memory is formatted, the disk is mounted and the firmware was copied to the internal memory with which it was installed, this is not an isolated case.Daniles, but it does not have a microSD card slot, the solution to this problem has not yet been found. I think that the culprit for the whole kernel (kernel), needs to be changed and checked how these comrades will work CWM with other cores ... Post has been editedImaSoft - 06.03.14, 08:28 |
Message#58 06.03.14, 10:40 | |
Help [offline] Topics Curator Group: Curators Messages 3276 Check in: 30.09.08 Blackview BV6000 Reputation: 597 | H. forum users, already several times there was a problem "I can not installMaud. firmware from ImaSoft " Pay attention to the item, "installing firmware ", i.e. MANDATORY resizing of memory partitions. For your own development, I recommend reading,Memory layout for mobile devices. Theory and practice -------------------- |
Message#59 06.03.14, 13:41 | |
Help [offline] Topics Curator Group: Curators Messages 3276 Check in: 30.09.08 Blackview BV6000 Reputation: 597 | |
Message#60 06.03.14, 23:11 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | People need your help !!! And especially those who installed my firmware mods and are now sitting on them,Daniles; grafich_29; bujhm7 It is necessary to test two variants of Recovery CWM6032 with different cores, this is an attempt to solve the problem of not mounting disks on the BB, in CWM The first version with the core: Kernel_v3.4.5_ (liujihui @ wangzijian-desktop) _ (gcc_version_4.6.x-google_ (GCC) _) ___ # 1_SMP_Thu_Dec12_CST_2013 ...................... 01_BASE_JB422_0502HP18_v1.06_20131212 Keener K-8S The result is mine: I see_ob_disc U55GT_CWM_V6.0.3.2_recovery_MTwinTools_060314 (1) .rar(18.18 MB) The second option with the core: Kernel_v3.4.5_ (ser3 @ ser3System-Product-Name) _ (gcc_version_4.6.x-google_ (GCC) _) __ # 1_SMP_Thu_Aug08_CST 2013 ................... ... Found in U55GT_touch_recovery (Chinese) Result at me: Vidytsya_tolko_microSD_kart U55GT_CWM_V6.0.3.2_recovery_MTwinTools_060314 (2) .rar(18.17 MB) >>Video_example_proshivki<< I ask you to test and unsubscribe, sew as a shining Recovery, that is, unpack the archive, start Flash_tool.exe from the archive, in the opened program, select Scatter-loading, select from the ROM folders, file MT6589_Android_scatter_emmc.txt, then tick the checkbox of DA DL ALL With Check Sum, then Download, agree with the warning and flashing the device! Also, who has the stock firmware and he once installed CWM and he had problems mounting disks on the BB and would like to check how the disks on the BB are mounted on him, I upload the stock file for recovery firmware MT6589_Android_scatter_emmc.txt(523 bytes) For the firmware, we change the MT6589_Android_scatter_emmc.txt ROM file in the daddy to the one that I posted above! Post has been editedImaSoft - 07.03.14, 09:07 |
Message#61 07.03.14, 11:46 | |
Frequenter [offline] Group: Friendssavagemessiahzine.com Messages 4835 Check in: 01.05.07 Samsung Galaxy A7 (2018) SM-A750FZ Reputation: 1056 | For information: I was taking about half an hour now, I couldn’t start my GSM card, I don’t plow it, I’ve already done something and pulled out a card and rubbed it with alcohol, and restored IMEI, reset it to factory settings (made Format / Data) I don’t plow and everything, I’ve cut down the pichal, I think what the hell is, went to lie down, then I remember, the recovery section increased and increased, and what’s behind it is secro.img and when I returned the sizes of the recovery unit back secro.img I restored NO, I’m running to I restore the computer and voila everything worked right away, but lost 1.5 hours, Is that the first time a sim card touch and messed up firmware (but not the trouble restore), here's the story, so that when saving data to NVRAM yet, just in case, save secro.img little. Post has been editedImaSoft - 07.03.14, 11:50 |
mobile version | Now: 05/19/19, 17:55 |