Related
My sceen wont come back to life whenver it goes into standby. The phone is still one however. This started happening after the upate to version 2.3.6. I would like to try 2.3.5 again however my phone also wont go into fastboot mode " Vol up/down and power same time".
Whats wrong with my phone?
My A2 is sleeping/waking up easily on 2.3.6. Are you sure that you're holding the power button long enough to wake it up?
It's odd that your phone isn't booting into fastboot...
-First make sure you're completely powered down. First "shut down" then pull the battery.
-Hold the volume up+down buttons while reinserting the battery, then release them
-Hold the volume down buton, then hold the power button. Wait about 5 seconds then release both buttons.
-This should make you boot directly into fastboot.
My phone is acting up. I definitely can't get into fastboot mode. I tired the SuperCharged V5 rom and the same screen issue was present. I really wish I could get into fastboot so I could flash back to stock in hopes in hopes it fixes my issue.
Your intrustions are confusing. Most insturctions i read say hit volup and voldow along with power at the same time. This just boots the phone normally, im not sure exactly what your steps below are indicating...
Here is what I did.
1. Removed Battery for 10 seconds
2. While holding volup and voldown down, I inserted the battery and immediatley let go, proceeded by voldown and power. (Nothing happens at all)
I'm a n00b and dont know if this will help.
I had almost the same problem after updating to 2.3.6 with the first two Atrix 2. I was told by AT&T that the OS was corrupted during update. This was prior to me rooting phone.
I started having problems again when I went to Supercharge V5. What I had to do to get to fastboot was pull out the battery, reinsert battery and then hold down power button and up/down volumn at the same time for about 5 seconds.
This took me several trys before I could get fast boot.
I plugged phone to USB on computer and reinstalled 2.3.5 using RSDLite 5.6 and InLineFlash.
Again n00b and steps may not be exact but best I can recall. Good Luck.
No dice. What a shame!!! I just paid $300 for this phone off contract. I dont have the receipt as i bought it on Criagslist, however it was brand new "sealed box" and phone.
What a joke, I can't even boot into fastboot!!! Never ran into any issues like this before where I can't even try to reinstall fresh factory os.
Anyone else have any ideas? Please please help me!
Additional Details...
When i do the reccomended steps it basically sits at a dark black screen, then eventually like 10 seconds later you can see the baclight kick in (black screen turns lights grey, it sits there for about 8 secons then boots into the Supercharged V5 splash screen. Issue is, superCharged wont actually boot, just does boot loop, and I can't get into Fastboot.
Is there any other option for me or Im I out $300?
Thanks in advance.
Thats exactly what mine was doing with Supercharged V5 it stuck in that loop when I unpluged it form charger.
It took me over 5 attempts of pulling out the battery reinserting it and holding down power button and up/down volumn.
I also had RSDLite open and INLineFlash place in the File Box ready to go.
I was about to give up and get ready to buy another Atrix 2 when I was able to get fast boot.
It did take me almost half a day to get it running. I do think however that their maybe some files missing because it doesnt run to the level it did before Supercharged V 5 was installed.
Not that their is anything wrong with V5, but being new at all this I more than likely messed something up.
I hear what your saying I would hate to have to buy another phone. Good Luck.
Thanks for trying to help but I think Im SOL. I have tried this process like 100 times and still can't get into fastboot. Im so upset right now, this was just after my Xperia Arc was stolen, then i have to buy this $300 phone and 1 day later its bricked.... ugh.... FML!
ej_424 said:
When i do the reccomended steps it basically sits at a dark black screen, then eventually like 10 seconds later you can see the baclight kick in (black screen turns lights grey, it sits there for about 8 secons then boots into the Supercharged V5 splash screen. Issue is, superCharged wont actually boot, just does boot loop, and I can't get into Fastboot.
Click to expand...
Click to collapse
It sounds like it's probably not activating the screen at the boot menu... but the boot menu might be coming up and timing out to a normal bootup like usual.
You might be able to still get to fastboot.
Basically boot up into the "dark black screen" before the 10 second timeout...
Then press VolumeDown twice, and VolumeUp once to hopefully select AP Fastboot from the invisible menu.
You seem to be somewhat right!!! I did this and a drive stareted to install when i plugged it onto my computer. However when i load up RSD lite, I see "fastboot EDISON s" under moble on far left, port type is listed as USB.
When I hit start after loading the xml file with teh "replace" zip overwriten the 2.3.6 files for a 2.3.5 restore i get "Failed flasing process. 1/18.
Any further ideas? Seems we are moving in the right direction!
Im definitely in fastboot, just can't flash back to stock as I get an error. Any thoughts? I was running stock 2.3.6 rooted, then went to Supercharged V5 Update 2 but never booted succesfully. Now Im in fastboot but can't flash back to factory.
I apprecaite all the help and I feel we are getting closer.
You might go through the manual moto-fastboot method of flashing... this seems like a good start.
RSD lite is typically doing the flashing steps through fastboot in the background for you. You might be able to get a better idea of what the error is if you use moto-fastboot.
Gotta get some sleep, good luck
Im desperately looking for some help. The method posted above seems to be the same using RSD lite. As soon as i try to flash it fails, I dont even get to step 1. Is there logging that RDS does to help me out.
Since I can get into fastboot and RDS lite detects it, do you think its possible to recover my phone?
RSD Lite Log Messages
I was able to find the logs messages within RSD Lite:
Here is what I see (Fails right away)
02/22/12 10:39:52 New Log Started For Software Download.
02/22/12 10:40:04 The FlashLog key is turned off.
02/22/12 10:40:06 Multi upgrade started for 1 phones
02/22/12 10:40:06 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin"
02/22/12 10:40:06 ERROR: 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin" -> Phone returned FAIL. - on device ID 0.
02/22/12 10:40:06 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin" -> Phone returned FAIL.
02/22/12 10:40:06 ERROR: Failed flashing process. - on device ID 0.
02/22/12 10:40:06 Multi upgrade finished.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
02/22/12 10:43:15 --------------------------------------------------------
Any ideas?
ej_424 said:
Any ideas?
Click to expand...
Click to collapse
Hmm no idea... Are you using windows 7? There have been reports of problems with people using vista...
I would still try going through the steps in moto-fastboot. If you look at the InlineFlashing .xml document, you can see the steps in order.
To replicate rsdlite, you'd just copy moto-fastboot into the same directory, then run these from a command line there...
moto-fastboot <operation> <partition> <filename>
ie: from the beginning of the steps...
moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
moto-fastboot reboot-bootloader
moto-fastboot flash mbmloader mbmloader.bin
moto-fastboot flash mbm mbm.bin
moto-fastboot reboot-bootloader
Click to expand...
Click to collapse
etc...
Hi,
I'm not allowed to reply on "Development" thread, so I open this new one.
But really this should be a reply on qtotter thread:
http://forum.xda-developers.com/showthread.php?t=1568787
I don't want to make it pm as well because this may be of interest to others like me that try and unfortunately get no result at this...
So here is what I got try at qtotter procedure and advices.
My ChaCha original memory mapping is:
Code:
# df /system
df /system
/system: 266240K total, 266116K used, 124K available (block size 4096)
# df /cache
df /cache
/cache: 35840K total, 2324K used, 33516K available (block size 4096)
# df /data
df /data
/data: 153600K total, 131484K used, 22116K available (block size 4096)
original mapping is:
--> 260 / 35 / 150
My custom recovery is CWM v4.0.1.0 (original PH06img.zip thread)
I take an empty SD Card and partition it (CWM recovery) into: "sd-ext = 512, swap = 0, rest of it is fat32"
I copy on it (fat32 part):
FR-Custom-MTD-v1.5.6-boot.zip
FR-Custom-MTD-v1.5.6-recovery.zip
mtdpartmap.txt
mtdpartmap.txt is (UNIX EOL):
Code:
mtd 265 10
I reboot to recovery.
mounts and storage > format /cache
mounts and storage > format /data
mounts and storage > format /system
install zip from sdcard > FR-Custom-MTD-v1.5.6-recovery.zip
Here is what I get in the '/tmp/recovery.log' file:
Code:
-- Installing: /sdcard/FR-Custom-MTD-v1.5.6-recovery.zip
mtd: successfully wrote block at c3a6c00000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/FR-Custom-MTD-v1.5.6-recovery.zip
Opening update package...
Installing update...
CustomMTD Patcher v1.5.6about to run program [/tmp/patchbootimg.sh] with 2 args
Recovery Mode
Extracting Patch Tools...
BOARD_KERNEL_CMDLINE no_console_suspend=1 console=null
BOARD_KERNEL_BASE 12c00000
mtd: erase failure at 0x00000000
mtd: erase failure at 0x00040000
mtd: erase failure at 0x00080000
mtd: erase failure at 0x000c0000
mtd: erase failure at 0x00100000
mtd: erase failure at 0x00140000
mtd: erase failure at 0x00180000
mtd: erase failure at 0x001c0000
mtd: erase failure at 0x00200000
mtd: erase failure at 0x00240000
mtd: erase failure at 0x00280000
mtd: erase failure at 0x002c0000
mtd: erase failure at 0x00300000
mtd: erase failure at 0x00340000
mtd: erase failure at 0x00380000
mtd: erase failure at 0x003c0000
mtd: erase failure at 0x00400000
mtd: erase failure at 0x00440000
mtd: erase failure at 0x00480000
mtd: erase failure at 0x004c0000
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00280000 (I/O error)
mtd: erase failure at 0x00280000 (I/O error)
mtd: skipping write block at 0x00280000
mtd: erase failure at 0x002c0000 (I/O error)
mtd: erase failure at 0x002c0000 (I/O error)
mtd: skipping write block at 0x002c0000
mtd: erase failure at 0x00300000 (I/O error)
mtd: erase failure at 0x00300000 (I/O error)
mtd: skipping write block at 0x00300000
mtd: erase failure at 0x00340000 (I/O error)
mtd: erase failure at 0x00340000 (I/O error)
mtd: skipping write block at 0x00340000
mtd: erase failure at 0x00380000 (I/O error)
mtd: erase failure at 0x00380000 (I/O error)
mtd: skipping write block at 0x00380000
mtd: erase failure at 0x003c0000 (I/O error)
mtd: erase failure at 0x003c0000 (I/O error)
mtd: skipping write block at 0x003c0000
mtd: erase failure at 0x00400000 (I/O error)
mtd: erase failure at 0x00400000 (I/O error)
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00480000 (I/O error)
mtd: erase failure at 0x00480000 (I/O error)
mtd: skipping write block at 0x00480000
mtd: erase failure at 0x004c0000 (I/O error)
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
failed with error: -1
flashing recovery from /tmp/recovery.img
error writing recoveryrun_program: child exited with status 255
script result was [to take effect]
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/patchbootimg.sh"
minzip: Extracted file "/tmp/unpackbootimg"
Custom MTD written
Please wipe system,cache & data
& reboot to recovery for changes
to take effect
Install from sdcard complete.
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
Then I format again /cache /data /system partition
and I reboot again to recovery
and there the 'df' commands give me:
Code:
~ # df /system
df /system
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 266240 2820 263420 1% /system
~ # df /cache
df /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock4 35840 2328 33512 6% /cache
~ # df /data
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
df: /data: can't find mount point
so this means that the '/system' and '/cache' partitions have not been resized and I still have the same 260 / 35 / 150 mapping...
I tried as well with a newer version of the CustomMTD tools (AutoPatch-v1.5.9-Beta2-CustomMTD_S.zip).
But this time the patch tool gives a more explicit error:
Code:
-- Installing: /sdcard/AutoPatch-v1.5.9-Beta2-CustomMTD_S.zip
mtd: successfully wrote block at c3a6c00000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/AutoPatch-v1.5.9-Beta2-CustomMTD_S.zip
Opening update package...
Installing update...
CustomMTD Patcher v1.5.9-Beta2about to run program [/tmp/patchbootimg.sh] with 2 args
Mode AutoPatch
Extracting Patch Tools...
about to run program [busybox test -f /sdcard/mtdpartmap.txt] with 1 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
script result was []
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/patchbootimg.sh"
minzip: Extracted file "/tmp/unpackbootimg"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
############ ERROR #############
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
none consecutive partitions
detected, can not proceed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Install from sdcard complete.
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
I'm therefore a bit lost here.
How did you succeed in resizing?
Could you please detail step by step what you did because I followed quite carefully your instructions and HTC Desire steps, but this doesn't work...
Thanks in advance.
spoutnik
Hi,
No answer yet on this subject...
So I investigated a bit more and here are the steps and results.
(I can tell you already that I did not succeed yet, but I'm sure I'm not far)
*** Which CustomMTD tools version I used ***
As seen in my previous post, with CustomMTD tools v1.5.9 (AutoPatch-v1.5.9-Beta2-CustomMTD_S.zip), the 'patchbootimg.sh' does some smart checking on system / cache / data being concecutive, which is not the case on ChaCha (I'll explain later).
For this reason, I reverted to CustomMTD tools v1.5.8 (recovery-v1.5.8-Beta-CustomMTD_S.zip).
This version improves the 'patchbootimg.sh' code over the 1.5.6, but remains more easily customizable.
*** Which re-partitionning is easier / better for ChaCha ***
The original partition table on ChaCha (official ChaCha_HTC_Europe_1.54.xxx ROM) is:
Code:
0x000002FC0000-0x0000034C0000 : "recovery" --> size = 0x500000 = 5242880 Bytes = 5120 KB = 5 MB
0x0000034C0000-0x000003800000 : "boot" --> size = 0x340000 = 3407872 Bytes = 3328 KB = 3,25 MB
0x000003800000-0x000013C00000 : "system" --> size = 0x10400000= 272629760 Bytes = 266240 KB = 260 MB
0x000013C00000-0x000015F00000 : "cache" --> size = 0x2300000 = 36700160 Bytes = 35840 KB = 35 MB
0x000015F00000-0x000016900000 : "devlog" --> size = 0xA00000 = 10485760 Bytes = 10240 KB = 10 MB
0x000016900000-0x00001FF00000 : "userdata" --> size = 0x9600000 = 157286400 Bytes = 153600 KB = 150 MB
0x00001FF00000-0x000020000000 : "misc" --> size = 0x100000 = 1048576 Bytes = 1024 KB = 1 MB
As you can see, we have "system" / "cache" / "userdata" = 260 / 35 / 150
But they are not consecutive since the "devlog" partition is inbetween.
This means that it is not possible to repartition in a classic way the "system""cache""userdata" block (... I don't see how the original v1.5.6 and v1.5.8 'patchbootimg.sh' code could work for qtotter in this case ...).
It is as well difficult to switch a partition ("userdata" for instance) to put it "system" instead because 150 MB is too small (the official ROM system takes around 240 MB !!)
After searching, I've seen that firerat has helped on a similar case (LG Optimus S) where the partition table is not consecutive as well. see code modif here: Firerat / CustomMTD / quickly added support for LG Optimus S ( thunderc ) (h_t_t_p_s://github.com/Firerat/CustomMTD/commit/f3ec0fdcd6823e674cd3bc81267db6a482eaa39a)
So my idea about this was to modify the v1.5.8 'patchbootimg.sh' code in a similar way in order to obtain the following partition table:
- keep the "userdata" partition intact
- repartition the "system""cache" block to give more space to the "system" partition
- the 'mtdpartmap.txt' file allowing to specify the "system" partition size
The modified partition table would then be:
Code:
0x000002FC0000-0x0000034C0000 : "recovery" --> size = 0x500000 = 5242880 Bytes = 5120 KB = 5 MB
0x0000034C0000-0x000003800000 : "boot" --> size = 0x340000 = 3407872 Bytes = 3328 KB = 3,25 MB
0x000003800000-0x0000[B]XXX[/B]00000 : "system" --> size = 295 MB - [I]<cache partition size>[/I] MB
0x0000[B]XXX[/B]00000-0x000015F00000 : "cache" --> size = [I]<cache partition size>[/I] MB
0x000015F00000-0x000016900000 : "devlog" --> size = 0xA00000 = 10485760 Bytes = 10240 KB = 10 MB
0x000016900000-0x00001FF00000 : "userdata" --> size = 0x9600000 = 157286400 Bytes = 153600 KB = 150 MB
0x00001FF00000-0x000020000000 : "misc" --> size = 0x100000 = 1048576 Bytes = 1024 KB = 1 MB
*** Modified 'patchbootimg.sh' code and resulting KCMDline ***
I modified then the 'patchbootimg.sh' source code to customize it specifically to the ChaCha and to the modified partition table to get (as explained before).
And I tested this new code on my ChaCha with the 'test-v1.5.8-Beta-CustomMTD_S.chacha.zip' package, built with my modified 'patchbootimg.chacha.sh'.
With 'mtdpartmap.txt' = mtd 290 5
(the 2nd parameter is not used anyway)
I should get:
Code:
[idem] 0x000002FC0000-0x0000034C0000 : "recovery" --> size = 0x500000 = 5242880 Bytes = 5120 KB = 5 MB
[idem] 0x0000034C0000-0x000003800000 : "boot" --> size = 0x340000 = 3407872 Bytes = 3328 KB = 3,25 MB
[changed] 0x000003800000-0x000015A00000 : "system" --> size = 0x12200000= 304087040 Bytes = 296960 KB = 290 MB
[changed] 0x000015A00000-0x000015F00000 : "cache" --> size = 0x500000 = 5242880 Bytes = 5120 KB = 5 MB
[idem] 0x000015F00000-0x000016900000 : "devlog" --> size = 0xA00000 = 10485760 Bytes = 10240 KB = 10 MB
[idem] 0x000016900000-0x00001FF00000 : "userdata" --> size = 0x9600000 = 157286400 Bytes = 153600 KB = 150 MB
[idem] 0x00001FF00000-0x000020000000 : "misc" --> size = 0x100000 = 1048576 Bytes = 1024 KB = 1 MB
The test run returns the following command line:
Code:
+ KCMDline=mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](userdata),[email protected](devlog),[email protected](system),[email protected](cache)
This is GOOD
So now I can test the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package to see if my partition table gets properly modified.
At this point, I do think that my specific 'recovery-v1.5.8-Beta-CustomMTD_S.chacha' package is good to be run on the ChaCha.
So let's re-try.
*** Impossible to flash the "recovery" partition while in recovery mode?? ***
In my first post, I was getting lots of errors when updating my ChaCha in recovery mode with the "recovery-..." package:
Code:
[...]
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
failed with error: -1
flashing recovery from /tmp/recovery.img
error writing recovery
In fact I did some tests, and it looks like it is not possible to do such recovery flashing operations while in recovery mode.
These operations must be done in fastboot mode.
So what I'll do is:
- reboot in recovery mode and install the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package
--> this will fail in the end, but it will extract all the necessary files to do things by hand
- reboot in fastboot mode and do operations by hand
Check the next post for this part.
spoutnik
[Q] custom mtd on chacha [please a dev (firerat) look at this]
Hi,
So I built a ChaCha specific 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package and now I'll run it for real.
As I said, what I'll do is:
- reboot in recovery mode and install the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package
--> this will fail in the end, but it will extract all the necessary files to do things by hand
- reboot in fastboot mode and do operations by hand
*** [recovery mode] Installing the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package ***
The recovery I use is CWM v4.0.1.0 (original PH06img.zip thread).
install zip from sdcard > 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip'
I get errors, as expected.
Then I reboot to fastboot mode.
*** [fastboot mode] Manual installation of 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package ***
First, here is the content of the '/tmp/recovery.log' file that shows the expected errors (the same than in my first post):
Code:
~ # cd /tmp
cd /tmp
/tmp # ls
ls
recovery.log
/tmp # cat recovery.log
cat recovery.log
Starting recovery on Tue Jul 3 12:02:44 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 320)
ClockworkMod Recovery v4.0.1.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
I:Completed outputting fstab.
I:Processing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at c3a6c00000000
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_chacha-eng 2.3.4 GINGERBREAD eng.mike.20110714.204851 test-keys
ro.build.version.incremental=eng.mike.20110714.204851
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Thu Jul 14 20:49:56 CEST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=mike
ro.build.host=AndroidCompiler
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_chacha
ro.product.device=chacha
ro.product.board=chacha
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=chacha
ro.build.description=full_chacha-eng 2.3.4 GINGERBREAD eng.mike.20110714.204851 test-keys
ro.build.fingerprint=Android/full_chacha/chacha:2.3.4/GINGERBREAD/eng.mike.20110714.204851:eng/test-
keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT15XV403307
ro.bootmode=recovery
ro.baseband=7.51.35.19
ro.carrier=HTC-FRA
ro.bootloader=1.10.0000
ro.hardware=chacha
ro.revision=128
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
-- Installing: /sdcard/recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip
mtd: successfully wrote block at c3a6c00000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip
Opening update package...
Installing update...
CustomMTD Patcher v1.5.8-Betaabout to run program [/tmp/patchbootimg.sh] with 2 args
2344
16
Recovery Mode
Extracting Patch Tools...
BOARD_KERNEL_CMDLINE no_console_suspend=1 console=null
BOARD_KERNEL_BASE 12c00000
mtd: erase failure at 0x00000000
mtd: erase failure at 0x00040000
mtd: erase failure at 0x00080000
mtd: erase failure at 0x000c0000
mtd: erase failure at 0x00100000
mtd: erase failure at 0x00140000
mtd: erase failure at 0x00180000
mtd: erase failure at 0x001c0000
mtd: erase failure at 0x00200000
mtd: erase failure at 0x00240000
mtd: erase failure at 0x00280000
mtd: erase failure at 0x002c0000
mtd: erase failure at 0x00300000
mtd: erase failure at 0x00340000
mtd: erase failure at 0x00380000
mtd: erase failure at 0x003c0000
mtd: erase failure at 0x00400000
mtd: erase failure at 0x00440000
mtd: erase failure at 0x00480000
mtd: erase failure at 0x004c0000
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00280000 (I/O error)
mtd: erase failure at 0x00280000 (I/O error)
mtd: skipping write block at 0x00280000
mtd: erase failure at 0x002c0000 (I/O error)
mtd: erase failure at 0x002c0000 (I/O error)
mtd: skipping write block at 0x002c0000
mtd: erase failure at 0x00300000 (I/O error)
mtd: erase failure at 0x00300000 (I/O error)
mtd: skipping write block at 0x00300000
mtd: erase failure at 0x00340000 (I/O error)
mtd: erase failure at 0x00340000 (I/O error)
mtd: skipping write block at 0x00340000
mtd: erase failure at 0x00380000 (I/O error)
mtd: erase failure at 0x00380000 (I/O error)
mtd: skipping write block at 0x00380000
mtd: erase failure at 0x003c0000 (I/O error)
mtd: erase failure at 0x003c0000 (I/O error)
mtd: skipping write block at 0x003c0000
mtd: erase failure at 0x00400000 (I/O error)
mtd: erase failure at 0x00400000 (I/O error)
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00480000 (I/O error)
mtd: erase failure at 0x00480000 (I/O error)
mtd: skipping write block at 0x00480000
mtd: erase failure at 0x004c0000 (I/O error)
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
failed with error: -1
flashing recovery from /tmp/recovery.img
error writing recoveryrun_program: child exited with status 255
script result was [to take effect]
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/patchbootimg.sh"
minzip: Extracted file "/tmp/unpackbootimg"
Custom MTD written
Please wipe system,cache & data
& reboot to recovery for changes
to take effect
Install from sdcard complete.
And now, here are the manual steps to install by hand the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package:
Here is the content of the '/tmp' folder:
Code:
/tmp # ls
ls
mkbootimg recovery.img-cmdline unpackbootimg
patchbootimg.sh recovery.img-ramdisk.gz update_binary
recovery.img recovery.img-zImage
recovery.img-base recovery.log
Let's clean-up the formerly generated 'recovery.img' file:
Code:
/tmp # rm recovery.img
rm recovery.img
Now let's dump the recovery again and name it 'recovery_original.img' (and backup it to sdcard):
Code:
/tmp # dump_image recovery /tmp/recovery.img
dump_image recovery /tmp/recovery.img
/tmp # cp recovery.img recovery_original.img
cp recovery.img recovery_original.img
/tmp # cp recovery_original.img /sdcard/recovery_original.img
cp recovery_original.img /sdcard/recovery_original.img
/tmp # rm recovery.img
rm recovery.img
Now let's unpack the 'recovery_original.img' in order to repack it with modified command line afterwards:
Code:
/tmp # /tmp/unpackbootimg /tmp/recovery_original.img /tmp/
/tmp/unpackbootimg /tmp/recovery_original.img /tmp/
BOARD_KERNEL_CMDLINE no_console_suspend=1 console=null
BOARD_KERNEL_BASE 12c00000
Now is the IMPORTANT part, which is repacking with the correct kernel command line.
In our case, the kernel command line we want (as explained in my previous post) is the same as the original one + the new 'mtdparts' addition:
Code:
msm_nand:102
[email protected](misc),[email protected](recovery),[email protected](boot),[email protected]
0000(userdata),[email protected](devlog),[email protected](system),[email protected](c
ache)
Here is the command:
Code:
/tmp # /tmp/mkbootimg --kernel /tmp/recovery_original.img-zImage --ramdisk /tmp/recovery_original.im
g-ramdisk.gz -o /tmp/recovery.img --cmdline "no_console_suspend=1 console=null mtdparts=msm_nand:102
[email protected](misc),[email protected](recovery),[email protected](boot),[email protected]
0000(userdata),[email protected](devlog),[email protected](system),[email protected](c
ache)" --base 12c00000
/tmp/mkbootimg --kernel /tmp/recovery_original.img-zImage --ramdisk /tmp/
recovery_original.img-ramdisk.gz -o /tmp/recovery.img --cmdline "no_console_susp
end=1 console=null mtdparts=msm_nand:[email protected](misc),[email protected]
0000(recovery),[email protected](boot),15[email protected](userdata),10240
[email protected](devlog),[email protected](system),[email protected](c
ache)" --base 12c00000
This has repacked a 'recovery.img' file.
Let's name it 'recovery_modified.img' and copy it as well to sdcard:
Code:
/tmp # cp recovery.img recovery_modified.img
cp recovery.img recovery_modified.img
/tmp # cp recovery_modified.img /sdcard/recovery_modified.img
cp recovery_modified.img /sdcard/recovery_modified.img
Now let's unpack the 'recovery_modified.img' in order to check the BOARD_KERNEL_CMDLINE part:
Code:
/tmp/unpackbootimg /tmp/recovery_modified.img /tmp/
BOARD_KERNEL_CMDLINE no_console_suspend=1 console=null mtdparts=msm_nand:[email protected](misc),
[email protected](recovery),[email protected](boot),[email protected](userdata),[email protected]
000015F00000(devlog),[email protected](system),[email protected](cache)
BOARD_KERNEL_BASE 12c00000
This looks coherent with what I want to do.
Now I mount USB to copy the 'recovery_modified.img' in my android sdk tools folder ('D:\android-sdk-windows\tools\recovery_cMTD.img').
Then I'll flash this modified recovery with a "fastboot flash" command.
Code:
D:\android-sdk-windows\tools>adb reboot bootloader
D:\android-sdk-windows\tools>fastboot flash recovery recovery_cMTD.img
sending 'recovery' (3664 KB)...
OKAY [ 2.797s]
writing 'recovery'...
OKAY [ 3.266s]
finished. total time: 6.063s
The flashing process was a success, which is good.
Then I'll boot to recovery to see if this works.
In bootloader mode, I choose RECOVERY
--> THE RECOVERY DOES NOT BOOT !!!!! (stays frozen on green HTC banner...)
Argh........ the recovery does not boot...
And fortunately, when I reflash the original (CWM) recovery, I can boot to recovery.
So my question now is:
Why does the modified recovery does not boot??????
I compared (hexadecimal compare) the 'recovery_original.img' and the 'recovery_modified.img' files, and really the only difference in it is the command line part.
The file are exactly the same byte size.
And they are identical, except at offset 0x61 where:
the 'recovery_modified.img' file contains the following bytes:
[hexa]
Code:
206D746470617274733D6D736D5F6E616E643A313032344B403078303030303146463030303030286D697363292C353132304B403078303030303032464330303030287265636F76657279292C333332384B40307830303030303334433030303028626F6F74292C31303234304B403078303030303135463030303030286465766C6F67292C3239363936306B4030783030303030333830303030302873797374656D292C353132306B4030783135413030303030286361636865292C3136333834306B403078313546303030303028757365726461746129
[ascii]
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](devlog),[email protected](system),[email protected](cache),[email protected](userdata)
whereas the the 'recovery_original.img' file contains 0x00 bytes (same number)...
So my question really is:
Why does the modified recovery does not boot??????
spoutnik
I'm wondering what might happen if you use a more up to date CWM.
I did build this copy of CWM 6.0.1.5 a month or two ago. MOST functionality works. It has some issues with backings and restoring. but otherwise I didn't notice anything else.
Perhaps it will be helpful, and might work with the patching?
Hello. I've read this thread, and wondered (sorry if this is a silly idea) if the partition scheme cannot be altered because of the phone being S-ON.
If I've understood the flash memory when you boot your Chacha is some kind of plain: just a large set of bits one after the other.
And someone do the job of organizing those bits in partitions that once that are setup, can be used to load Android.
Is my idea right?
If it is, then that someone could be the bootloader, and there is where the changes/hacks should be made.
I'm on my phone only, using Tapatalk, could you paste here, or link me to the content of the patchbootimg.sh file? I'm curious about what it does.
Sent from my Galaxy Nexus
Spoutnik, regarding your intent, just by reading the cmdline it seems you messed the partition order. Also it seems to me that your devlog and user data partitions would start at the same offset.
I've been working to do it manually and it works. I have a 312MB /system as seen from the recovery at least.
I'm 99% sure that s-on/s-off isn't the issue but your command line is.
Wondering what would be a good partitioning?
I was thinking giving more to system, and not that much to userdata as the latter can be replaced with app2sd...
I can't say much more right now, I'm from my phone, Internet line at home is dead tonight :-\
Sent from my Galaxy Nexus
Is there any update of this issue?
I am a fresh hand in this field. I think it is much better to keep /data as large as possible because /system size will not increase after new software installation (if my understanding is correct).
BTW, any books recommended for android?
kronflux said:
I'm wondering what might happen if you use a more up to date CWM.
I did build this copy of CWM 6.0.1.5 a month or two ago. MOST functionality works. It has some issues with backings and restoring. but otherwise I didn't notice anything else.
Perhaps it will be helpful, and might work with the patching?
Click to expand...
Click to collapse
watchthinker said:
Is there any update of this issue?
I am a fresh hand in this field. I think it is much better to keep /data as large as possible because /system size will not increase after new software installation (if my understanding is correct).
BTW, any books recommended for android?
Click to expand...
Click to collapse
I got it working, it's a bit tricky but feasible.
Actually with increasing versions of Android also increases the size of system. While on the other hand, if you use app2sd you don't need that much /data AFAIK.
That's why I would rather increase system over data.
Sent from my Galaxy Nexus, no Internet at home these days.
Yes, but I'd like to keep my /system as small as possible, only to keep the basic system (maybe the kernel?).
Chacha's battery is not durable and I'd like programs run from internal flash so I can save battery a little bit
adlx.xda said:
I got it working, it's a bit tricky but feasible.
Actually with increasing versions of Android also increases the size of system. While on the other hand, if you use app2sd you don't need that much /data AFAIK.
That's why I would rather increase system over data.
Sent from my Galaxy Nexus, no Internet at home these days.
Click to expand...
Click to collapse
watchthinker said:
Yes, but I'd like to keep my /system as small as possible, only to keep the basic system (maybe the kernel?).
Click to expand...
Click to collapse
Sorry, that doesn't make much sense...
Sent from my Galaxy Nexus
It is the pity that Chacha comes with a too small ROM for data.
I don't know why my internal flash size keep going down.
adlx.xda said:
Sorry, that doesn't make much sense...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ...
Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog
Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
LetMeKnow said:
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
Click to expand...
Click to collapse
Fixed let me know if you see anymore ..
Thx @LetMeKnow
LetMeKnow said:
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
Click to expand...
Click to collapse
I am going to get to this once you have fastboot back and you can boot with hardware buttons then its just like @Buster99's
guide but there is one very important command that he leaves out ..
I will post the rest of the guide after bit ...
Thx Josh
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx _that I did update the OP with the correct bootit.ko ...
lj50036 said:
Thx _that I did update the OP with the correct bootit.ko ...
Click to expand...
Click to collapse
Great stuff! Thanks for this thread Josh!
Now , if I understand this correctly, the insmod command injects a command into the kernel to boot straight to the bootloader before checking misc to break that 'forced reboot to recovery' cycle.
Kinda correct?
In another thread @_that stated once that
Code:
fastboot getvar all
does not return misc as a supported partiton and that
Code:
fastboot erase misc
only "theoretically" erases misc partition. Is that confirmed now?
You guys are great! So much fun to learn this...
I tried to follow this but i get this output:
After pushing bootit.ko to the root and insmod, the transformer reboots directly in the bootloader.
When try fastboot devices, nothing happens just the next line to fill in a command.
Also, when trying then to fastboot erase misc, it hangs with 'waiting for devices'..
lvrijn said:
I tried to follow this but i get this output:
After pushing bootit.ko to the root and insmod, the transformer reboots directly in the bootloader.
When try fastboot devices, nothing happens just the next line to fill in a command.
Also, when trying then to fastboot erase misc, it hangs with 'waiting for devices'..
Click to expand...
Click to collapse
Did you have a working fastboot driver on your PC before you got into this pickle?
Give us a detailed description on why you tried this procedure.
berndblb said:
Did you have a working fastboot driver on your PC before you got into this pickle?
Give us a detailed description on why you tried this procedure.
Click to expand...
Click to collapse
Thanks for the advice.
It was not the driver, if was my fastboot and adb .exe, i think an old version?
I now downloaded from here http://forum.xda-developers.com/showthread.php?t=2588979
And these are working!
So if someone ever have problems command doesn't recognize fastboot commands, its not always the driver! It can also be the fastboot.exe
This transformer is working again !
lvrijn said:
Thanks for the advice.
It was not the driver, if was my fastboot and adb .exe, i think an old version?
I now downloaded from here http://forum.xda-developers.com/showthread.php?t=2588979
And these are working!
So if someone ever have problems command doesn't recognize fastboot commands, its not always the driver! It can also be the fastboot.exe
This transformer is working again !
Click to expand...
Click to collapse
Great to see you up and running...:good:
I did add a Troubleshooting post number 3
The Josh
berndblb said:
Great stuff! Thanks for this thread Josh!
Now , if I understand this correctly, the insmod command injects a command into the kernel to boot straight to the bootloader before checking misc to break that 'forced reboot to recovery' cycle.
Kinda correct?
In another thread @_that stated once that
Code:
fastboot getvar all
does not return misc as a supported partiton and that
Code:
fastboot erase misc
only "theoretically" erases misc partition. Is that confirmed now?
You guys are great! So much fun to learn this...
Click to expand...
Click to collapse
No, I dont think it injects anything into the kernel as there may not even be one in the LNX partition ..
The bootit.ko module comes from the source of the kernel code..
Also the /misc partition is a full partition as shown here ..
Code:
mmcblk0p3
Offset: 1292369920 (0x4d080000)
Size: 2097152 (0x200000)
File system size: 512 * 4096 = 2097152 (fully occupies partition)
Linux rev 1.0 ext3 filesystem
Not mounted
Permissions: GID system can manipulate
Contains: Empty file system
Purpose: Recovery /misc
Referenced by: /system/lib/libandroid_runtime.so recovery ramdisk: /etc/recovery.fstab
Note: File system is referenced in recovery as emmc, not ext3!
Thx Josh
lj50036 said:
No, I dont think it injects anything into the kernel as there may not even be one in the LNX partition ..
Click to expand...
Click to collapse
I think berndblb meant that insmod injects something into the *currently running* kernel, which it does. It's used for loading additional kernel modules, usually drivers. When a module is loaded, its "init" function is called by the kernel so that it can hook its functionality into the proper kernel subsystems. My bootit.ko's init function simply reboots the tablet - without properly terminating processes, unmounting filesystems, etc. - so it should only be loaded when no partitions are mounted.
_that said:
I think berndblb meant that insmod injects something into the *currently running* kernel, which it does. It's used for loading additional kernel modules, usually drivers. When a module is loaded, its "init" function is called by the kernel so that it can hook its functionality into the proper kernel subsystems. My bootit.ko's init function simply reboots the tablet - without properly terminating processes, unmounting filesystems, etc. - so it should only be loaded when no partitions are mounted.
Click to expand...
Click to collapse
Nothing like _that to put you in your place....
lj50036 said:
Nothing like _that to put you in your place....
Click to expand...
Click to collapse
I'm trying to get back to a working recovery. Now I get a cycle of TWRP splash screens. This method looks promising because it appears to rebuild all of the partitions. I can use the Vol Down + Power keys to get to the bootloader (us_epad-10.6.1.14.10-20130801 A03. Can I skip to the fastboot steps? I had Crombi-kk running with rom2sd before I broke something trying to upgrade to zombie-x.
Thanks!
awilson77584 said:
I'm trying to get back to a working recovery. Now I get a cycle of TWRP splash screens. This method looks promising because it appears to rebuild all of the partitions. I can use the Vol Down + Power keys to get to the bootloader (us_epad-10.6.1.14.10-20130801 A03. Can I skip to the fastboot steps? I had Crombi-kk running with rom2sd before I broke something trying to upgrade to zombie-x.
Thanks!
Click to expand...
Click to collapse
You can skip all the way down to the command "fastboot erase misc". It should kick you out of twrp cycling...good luck..:fingers-crossed:
LetMeKnow said:
You can skip all the way down to the command "fastboot erase misc". It should kick you out of twrp cycling...good luck..:fingers-crossed:
Click to expand...
Click to collapse
Thx!
Back up and running! Thanks!!!
Hello,
My phone fell to the floor and since than can't boot.
I see the google logo and then it turning off.
I can't enter recovery mode.
I can enter bootloader mode, tried to re-flash the rom (factory) with -w (wipe) and still can't boot / enter recovery mode.
Any suggestions?
Thanks!
time for a new phone
If the screen is okay, get a nexus 5 with a busted screen and swap internal components.
I have the same problem, but allow me to add some more details:
When trying to go to recovery, i got a dead droid with a red sign on it. See my post on android enthusiasts: /questions/169999/stuck-in-bootloop-and-flash-recovery-doesnt-work-on-nexus-5/170395 (can't post url from my account)
From fast boot, I could flash a recovery (my fastboot is unlocked) but it gave no results: still had the dead droid (tried with twrp, cwm, and stock rom).
After that I gave up trying to get back my data and tried flashing the whole stock rom, but it when bad. Now when trying to flash anything I got errors:
Code:
$ sudo ./fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.630s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.936s
- or -
Code:
$ sudo ./fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.118s
The only good news is I realized I could boot to any arbitrary recovery without flashing it with:
Code:
$ sudo ./fastboot boot recovery.img.twrp
Most functions on recory wouldn't work (it says it can't mount most partitions), but from where I can get an
Code:
adb shell
. I tried various steps but without success so far:
Code:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/recovery
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/recovery
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Code:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/system
e2fsck 1.41.14 (22-Dec-2010)
system: clean, 1939/65536 files, 254904/262144 blocks
Code:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/msm_sdcc.1/by-name/cache: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name/cache
I think I managed to somehow mess up my partition system, and I don't know much how to recover it, anyone have clues or can suggest something ?
You may need to replace the power button on the motherboard. If the phone keeps booting and then restarting when the Google logo appears, the power button might be your culprit. It was for me, and after a trip to my local repair shop, it is as good as new.
Fvolfrine said:
You may need to replace the power button on the motherboard. If the phone keeps booting and then restarting when the Google logo appears, the power button might be your culprit. It was for me, and after a trip to my local repair shop, it is as good as new.
Click to expand...
Click to collapse
The power button works fine on my phone. It's isn't constantly rebooting, but it gets stuck at the booting animation. I can use the power normally in the bootloader and it behaves as expected.
biaib said:
The power button works fine on my phone. It's isn't constantly rebooting, but it gets stuck at the booting animation. I can use the power normally in the bootloader and it behaves as expected.
Click to expand...
Click to collapse
I have the same problem sir.
were you able to solve your issue?
If yes please explain how?
If the phone is stuck at the boot animation, try flashing the oldest Kit Kat ROM from the Google site: https://developers.google.com/android/images
ahiel2 said:
Hello,
My phone fell to the floor and since than can't boot.
I see the google logo and then it turning off.
I can't enter recovery mode.
I can enter bootloader mode, tried to re-flash the rom (factory) with -w (wipe) and still can't boot / enter recovery mode.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Well I Still am trying to fix that issue since almost 2 years now.....
My guesses are that eMMC is damaged when you thre your phone.
If you do find a solution please do let me know.
Thanks!
Help me out here.
Basically, my situation is like this:
Recovery: Doesn't work, when i boot to recovery an error message like this appeared:
ERROR MODE
Attention!
Please update system again
*green android guy*
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
Fastboot:
works, but flashing anything but openkirin's lineage os and the kernel results into this error:
FAILED (remote partition length get error)
Normal boot: goes to erecovery
i dont know what to do now, someone help me