Related
Okay so I have noticed that there are still some people out there having issues with either going back from Update .901 or have dropped into a (Boot Failure) mode and cannot find a solution. I have decided to post up what works for me. Mind you I have personally and purposely bricked my Bionic multiple times to ensure that this works. However:
I am in no way responsible for any permanent damage you do to your phone. If you have an issue I will do the best I can to assist as I’m sure the rest of the members will. But you take full responsibility for anything you decide to attempt.
While some of you have been able to use the one click method provided by , some of you can’t follow through with the fix due to the (Boot Failure) or (CDT Failure). I have changed some of the files in the One Click method provided by. These files worked for me multiple times but I cannot gauruntee they will do the same for you. But if you are brave enough giver er hell.
Step One: Download these files. You will need all three if you want to go through to .901. Each update is labeled as such to limit the confusion. Once downloaded move all folders to your desktop and unzip the CDT file ONLY!!!
http://www.megaupload.com/?d=GZ4AC6ML
http://www.megaupload.com/?d=3XE1OFOM
http://www.megaupload.com/?d=TSYCAFP4
Step Two: Plug your Bionic in via USB. Once plugged in you can either boot into Fastboot mode by holding the POWER + VOLUME DOWN. If you are in (CDT Failure) you won’t be able to reach fast boot but that’s okay. In fact “Fastboot” mode isn’t necessary as long as you are in one of these error screens.
Step Three: Open the folder labeled “CDT_BOOT_FIX” and double click “EVERYTHING”. The system will begin running the install of the files contained. ALL FILES SHOULD SUCCEED. Not one of these files should fail and in the event one does please post so we may figure it out together.
Edit: You will need to also download this and place it into the unzipped CDT folder:
Sorry I must have forgotten to add it originally when composing the file.
Step Four: Once the files have finished running, reboot your Bionic. You should now have a running system. YOU ARE NOT FINISHED YET, so please pay attention. Failure to do so will only cause you to go through this again.
Step Five: Move the Update files (893 if you only want to go that far or 893 and 901 to go all the way) to your SD card. Make sure both files are on the root of the SD card. Now shut down your phone.
Step Five: Boot into recovery and choose “Update Zip on SD Card”. Choose the 893 file and click okay. Your phone will now install the 893 update. Reboot. STILL NOT DONE. As noted below if you plan to go to the .901 update then you can skip step six and just flash both the 893 and 901 one right after the other. If only going to 893 then proceed to step six.
Step Six: Your phone will now boot into “CDT Failure”. Make sure your Bionic is plugged into the USB port. Hover your mouse over the “CDT_BOOT_FIX” folder, hold SHIFT and RIGHT CLICK your mouse. A pop-up box comes up. Click “Open Command Prompt Here”. Once the Command Prompt comes up type:
moto-fastboot flash cdt.bin cdt.bin
/\ You can copy and paste this if you would like.
Your phone will now flash the CDT file. It should succeed. Once this is complete you are full OTA 893. You now have the choice of booting into recovery and loading the 901 file should you choose to do so.
That should be it. Thank you to all who have contributed. The scripting for the Everything command came from P3DROID. If you object to me using it please let me know. I appreciate it but the files can be run manually so no biggy. Thanks
If you have any problems feel free to ask
If you are still having problems I will do my best to assist. If it comes down to it download Team Viewer (www.teamviewer.com) and all files posted here. I will then run the repair process for you. Just for some peace of mind Team Viewer is a remote PC control program. It generates a password each time it is opened so it can never be replicated unless you choose to set a password. If at anytime you feel uncomfortable with what's going on you can immediately close Team Viewer and break the connection. If you need help this badly send me a PM and we will set up a time. As it stands now I am on duty from 6 P.M. to 6 A.M. And yes if it helps you any I am a Police Officer in the State of Ohio.
i just unpacked the 901 update and flashed the cdt file from it to get by this problem. took me a few different cdt files to get it right though.
Glad you found a solution. Some people just can't seem to get through this issue. Doing this process will put you back on 893 updatable.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk
I'm having an issue now it wont let me use your recovery img and I have to use one from 893 FXZ rather then yours. but then once I get to recovery it wont let me update to 893 (I guess it thinks I'm already there?) so I'm not sure what to do atm.
I also noticed on your batch file you put "moto-fastboot boot boot.img" it should be "moto-fastboot flash boot boot.img"
Eluvatar said:
I'm having an issue now it wont let me use your recovery img and I have to use one from 893 FXZ rather then yours. but then once I get to recovery it wont let me update to 893 (I guess it thinks I'm already there?) so I'm not sure what to do atm.
I also noticed on your batch file you put "moto-fastboot boot boot.img" it should be "moto-fastboot flash boot boot.img"
Click to expand...
Click to collapse
I apologize and will fix this. Thank you for pointing it out. I also posted a reply to your thread on Rootzwiki.
Hello, first off, I will like to thank for all the help!
Ever since I tried upgrading to 901, I been having a brick for 2 days now.
I read through your post a few times and I am using your method to fix the problem.
You specifically stated, everything should be OKAY. But in my case,
boot.img and recovery both failed.
Any help will be greatly appreciated!
Thank you again for all the help and support!
Gil
Here is a copy of my output:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.008s]
writing 'cdt.bin'... OKAY [ 0.864s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.000s]
Press any key to continue . . .
erasing 'cache'... OKAY [ 0.013s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.008s]
writing 'lbl'... OKAY [ 0.466s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.062s]
writing 'logo.bin'... OKAY [ 0.379s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.008s]
writing 'ebr'... OKAY [ 0.466s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.002s]
writing 'mbr'... OKAY [ 0.404s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.044s]
writing 'devtree'... OKAY [ 0.511s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 17.225s]
writing 'system'... OKAY [ 24.643s]
sending 'system' (229120 KB)... OKAY [ 15.139s]
writing 'system'... OKAY [ 22.028s]
Press any key to continue . . .
downloading 'boot.img'... OKAY [ 0.553s]
booting... FAILED (remote: unsupported command)
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 0.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 0.908s]
writing 'cdrom'... OKAY [ 2.269s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 16.790s]
writing 'preinstall'... OKAY [ 23.150s]
sending 'preinstall' (49152 KB)... OKAY [ 3.175s]
writing 'preinstall'... OKAY [ 4.221s]
Press any key to continue . . .
sending 'webtop' (262144 KB)... OKAY [ 17.211s]
writing 'webtop'......
Can you try manually pushing the boot and recovery images. Some users have reported that the one click want able to do this. Let me know what happens.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk
There is a missing command in the batch file I have.
This below should do what you need it to do, I still have the recovery flashing error though.
ERROR
sending 'recovery' (9216 KB)... OKAY [ 0.663s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Which actually doesn't matter once you can get into a working system.
Contents of the corrected batch file
@echo off
pause
moto-fastboot flash cdt.bin cdt.bin
pause
moto-fastboot reboot-bootloader
pause
moto-fastboot erase cache
pause
moto-fastboot flash lbl lbl
pause
moto-fastboot flash logo.bin logo.bin
pause
moto-fastboot flash ebr ebr
pause
moto-fastboot flash mbr mbr
pause
moto-fastboot flash devtree device_tree.bin
pause
moto-fastboot flash system system.img
pause
moto-fastboot flash boot boot.img
pause
moto-fastboot flash recovery recovery.img
pause
moto-fastboot flash cdrom cdrom
pause
moto-fastboot flash preinstall preinstall.img
pause
moto-fastboot flash webtop grfs.img
pause
moto-fastboot flash radio radio.img
pause
moto-fastboot -w
pause
The fixed batch file can be downloaded [HERE]
Terror_1 said:
There is a missing command in the batch file I have.
This below should do what you need it to do, I still have the recovery flashing error though.
ERROR
sending 'recovery' (9216 KB)... OKAY [ 0.663s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Contents of the corrected batch file
@echo off
pause
moto-fastboot flash cdt.bin cdt.bin
pause
moto-fastboot reboot-bootloader
pause
moto-fastboot erase cache
pause
moto-fastboot flash lbl lbl
pause
moto-fastboot flash logo.bin logo.bin
pause
moto-fastboot flash ebr ebr
pause
moto-fastboot flash mbr mbr
pause
moto-fastboot flash devtree device_tree.bin
pause
moto-fastboot flash system system.img
pause
moto-fastboot flash boot boot.img
pause
moto-fastboot flash recovery recovery.img
pause
moto-fastboot flash cdrom cdrom
pause
moto-fastboot flash preinstall preinstall.img
pause
moto-fastboot flash webtop grfs.img
pause
moto-fastboot flash radio radio.img
pause
moto-fastboot -w
pause
Click to expand...
Click to collapse
That is awesome and thank you. As for the Recovery what is your current system info?
darkstarsinner said:
That is awesome and thank you. As for the Recovery what is your current system info?
Click to expand...
Click to collapse
Doesn't matter, once the phone gets to a point where it will boot you can use the 1 click path saver to get things back up and running.
Good deal. Hopefully that will work for everybody. There are so many different errors out there we should compile a list of fixes into one thread to make it a little easier for everyone to find.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk
Hi everybody,
A buddy of mine bricked his bionic by attempting the 901 update with root so I attempted this fix since it was stuck in boot failure. The phone will now boot up but doesn't pull in any service. Am able to connect it to wi-fi, but once you hit the droid to run thru set up, it sits there thinking, telling me, "please wait, this may take a few moments." I attempted going back into recovery and installing the 893 zip and 901 zip and both fail. I've also attempted using rsd lite with the 893 fxz but no dice. Here's what I'm looking at when running the script:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.011s]
writing 'cdt.bin'... OKAY [ 0.564s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.008s]
Press any key to continue . . .
< waiting for device >
erasing 'cache'... OKAY [ 0.039s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.016s]
writing 'lbl'... OKAY [ 0.486s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.162s]
writing 'logo.bin'... OKAY [ 0.309s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.013s]
writing 'ebr'... OKAY [ 0.468s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.398s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.094s]
writing 'devtree'... OKAY [ 0.518s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 81.860s]
writing 'system'... OKAY [ 22.592s]
sending 'system' (229120 KB)... OKAY [ 45.569s]
writing 'system'... OKAY [ 20.132s]
Press any key to continue . . .
sending 'boot' (8192 KB)... OKAY [ 1.674s]
writing 'boot'... OKAY [ 1.139s]
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 1.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 2.443s]
writing 'cdrom'... OKAY [ 2.109s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 46.399s]
writing 'preinstall'... OKAY [ 22.774s]
sending 'preinstall' (49152 KB)... OKAY [ 8.490s]
writing 'preinstall'... OKAY [ 4.404s]
Press any key to continue . . .
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Press any key to continue . . .
sending 'radio' (21768 KB)... OKAY [ 3.661s]
writing 'radio'... OKAY [ 2.052s]
Press any key to continue . . .
Any help would be greatly appreciated! Thanks again for all the hard work that goes into this!
s.dubs317 said:
Hi everybody,
A buddy of mine bricked his bionic by attempting the 901 update with root so I attempted this fix since it was stuck in boot failure. The phone will now boot up but doesn't pull in any service. Am able to connect it to wi-fi, but once you hit the droid to run thru set up, it sits there thinking, telling me, "please wait, this may take a few moments." I attempted going back into recovery and installing the 893 zip and 901 zip and both fail. I've also attempted using rsd lite with the 893 fxz but no dice. Here's what I'm looking at when running the script:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.011s]
writing 'cdt.bin'... OKAY [ 0.564s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.008s]
Press any key to continue . . .
< waiting for device >
erasing 'cache'... OKAY [ 0.039s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.016s]
writing 'lbl'... OKAY [ 0.486s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.162s]
writing 'logo.bin'... OKAY [ 0.309s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.013s]
writing 'ebr'... OKAY [ 0.468s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.398s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.094s]
writing 'devtree'... OKAY [ 0.518s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 81.860s]
writing 'system'... OKAY [ 22.592s]
sending 'system' (229120 KB)... OKAY [ 45.569s]
writing 'system'... OKAY [ 20.132s]
Press any key to continue . . .
sending 'boot' (8192 KB)... OKAY [ 1.674s]
writing 'boot'... OKAY [ 1.139s]
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 1.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 2.443s]
writing 'cdrom'... OKAY [ 2.109s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 46.399s]
writing 'preinstall'... OKAY [ 22.774s]
sending 'preinstall' (49152 KB)... OKAY [ 8.490s]
writing 'preinstall'... OKAY [ 4.404s]
Press any key to continue . . .
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Press any key to continue . . .
sending 'radio' (21768 KB)... OKAY [ 3.661s]
writing 'radio'... OKAY [ 2.052s]
Press any key to continue . . .
Any help would be greatly appreciated! Thanks again for all the hard work that goes into this!
Click to expand...
Click to collapse
I am getting the exact same issue. I am getting errors in the recovery and cant get to the point where i can turn usb debugging on for 1 click path to work. any ideaS?
To those getting stuck at the "push the android" screen and have the recovery error,
you can touch the four corners of the LCD starting from top left and moving clockwise to each corner. This will bypass the android guy and send you to the home screen allowing you to put your device in usb debug mode and push the files through path saver.
MarcMaiden said:
To those getting stuck at the "push the android" screen and have the recovery error,
you can touch the four corners of the LCD starting from top left and moving clockwise to each corner. This will bypass the android guy and send you to the home screen allowing you to put your device in usb debug mode and push the files through path saver.
Click to expand...
Click to collapse
I wish it was that easy but it will not allow me to bypass the android guy. Usually i can click him and skip thru setup then go into settings but when clicking the android guy it just sits there thinking saying please wait, this may take a few minutes, but never gets past that point. Any other ideas?
Sent from my DROID BIONIC using xda premium
I believe my problem stems from flashing webtop grfs.img. Fails out any time i try and says:
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Please help! I would hate to see this phone a paper weight!
Sent from my DROID BIONIC using xda premium
Ok so i ended up flashing the radio.zip from the guide, how to receive otas again if you are on a leak, and was able to boot up afterwards, skip the setup and am about to run the pathsaver. Will let you know how i make out...
Sent from my DROID BIONIC using xda premium
Edit- looks like youre on your way
i attempted this method and it did this:
sending 'recovery' (9216 KB)... OKAY [ 1.594s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: >
Press any key to continue . . .
==============
EDIT: everything else was sent to the phone ok, so once done i powered it down/up, then rather then booting up normally, it automatically went into the stock recovery, so i pressed the VOL UP+DOWN to proceed and it then showed this:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/caller
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
==============
EDIT 2: I ignored the above, rebooted & chose to boot normally. Upon doing so, it loads up and gets to the "Welcome to DROID BIONIC" screen. When i tap on the android figure to begin, it just stays at "Please wait, this may take a few minutes." but never changes. Does not proceed any further.
I'm moving this from another forum, to post in the correct place.
From Me
Hello all, I really appreciate all the work that Samurai HL has put into HoB/HoM. I used it in the past, and still I'm very grateful.
I have installed SafeStrap 3.5 on my Bionic, and I've successfully installed CM10 on the Slot 1. However, what I seem to have done is also installed CM10 in the Factory slot. When I boot using that slot, it just sits there and does not do anything. I've tried several times to install the stock roms, but all I get are Error Flashing Zip messages.
My question is about whether HoM will solve my problem or not. Am I able to flash the stock slot with HoM or do I remove SS and try flashing the slot another way? I've searched and searched, but I haven't seen an issue quite like this.
Thanks for all your help.
From SamuriHL
Yes, you can use the House of Moto with the xt875 support file and the latest FXZ to restore stock. Use the KEEP DATA option. You will have to reinstall root and SS recovery once that's done. (No need to uninstall SS).
Click to expand...
Click to collapse
SamuriHL, I did exactly what you said, but now SS doesn't come up and the phone still sits after the M logo goes away.
Then you've managed to corrupt the data partition. That sucks. The only fix is to FDR.
SamuriHL said:
Then you've managed to corrupt the data partition. That sucks. The only fix is to FDR.
Click to expand...
Click to collapse
Is that the full option?
Sure you can do it that way. Or you can boot into recovery and do it from there. Just understand what it means....your phone will be reset completely and you'll have to reinstall everything.
SamuriHL said:
Sure you can do it that way. Or you can boot into recovery and do it from there. Just understand what it means....your phone will be reset completely and you'll have to reinstall everything.
Click to expand...
Click to collapse
I did both methods, and same issue. Do I need to try another FXZ version? I have all 4 from the sbf site.
Um, it can't be "same issue" if it flashed properly and you did in fact do an FDR. That's not possible. So I'm guessing your flash didn't work. And no, you can't just pick a different FXZ. The phone is security locked and you'll brick it trying to downgrade it. How did you flash the FXZ? fastboot or rsd? I need to see the log of the flash.
SamuriHL said:
Um, it can't be "same issue" if it flashed properly and you did in fact do an FDR. That's not possible. So I'm guessing your flash didn't work. And no, you can't just pick a different FXZ. The phone is security locked and you'll brick it trying to downgrade it. How did you flash the FXZ? fastboot or rsd? I need to see the log of the flash.
Click to expand...
Click to collapse
Fastboot, and here's the log.
Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
Ready to flash...
Press any key to continue . . .
Flashing: FULL_xt875.bat
rebooting into bootloader... OKAY [ 0.006s]
sending 'mbm' (256 KB)... OKAY [ 0.029s]
writing 'mbm'... OKAY [ 0.480s]
rebooting into bootloader... OKAY [ 0.293s]
sending 'mbmloader' (41 KB)... OKAY [ 0.011s]
writing 'mbmloader'... OKAY [ 0.288s]
sending 'mbm' (256 KB)... OKAY [ 0.314s]
writing 'mbm'... OKAY [ 0.477s]
rebooting into bootloader... OKAY [ 0.293s]
sending 'cdt.bin' (16 KB)... OKAY [ 0.008s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
rebooting into bootloader... OKAY [ 0.293s]
erasing 'cache'... OKAY [ 0.012s]
erasing 'userdata'... OKAY [ 0.012s]
error: cannot load 'lbl'
sending 'logo.bin' (854 KB)... OKAY [ 0.065s]
writing 'logo.bin'... OKAY [ 0.281s]
sending 'ebr' (16 KB)... OKAY [ 0.294s]
writing 'ebr'... OKAY [ 0.444s]
sending 'mbr' (16 KB)... OKAY [ 0.294s]
writing 'mbr'... OKAY [ 0.401s]
sending 'devtree' (512 KB)... OKAY [ 0.336s]
writing 'devtree'... OKAY [ 0.447s]
sending 'system' (262144 KB)... OKAY [ 18.319s]
writing 'system'... OKAY [ 21.761s]
sending 'system' (229120 KB)... OKAY [ 16.152s]
writing 'system'... OKAY [ 19.797s]
sending 'boot' (8192 KB)... OKAY [ 0.625s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
sending 'recovery' (9216 KB)... OKAY [ 0.949s]
writing 'recovery'... OKAY [ 1.524s]
sending 'cdrom' (12032 KB)... OKAY [ 1.167s]
writing 'cdrom'... OKAY [ 2.052s]
sending 'preinstall' (262144 KB)... OKAY [ 18.260s]
writing 'preinstall'... OKAY [ 22.709s]
sending 'preinstall' (49152 KB)... OKAY [ 3.410s]
writing 'preinstall'... OKAY [ 4.335s]
sending 'webtop' (262144 KB)... OKAY [ 18.449s]
writing 'webtop'... OKAY [ 22.590s]
sending 'webtop' (262144 KB)... OKAY [ 18.218s]
writing 'webtop'... OKAY [ 22.377s]
sending 'webtop' (262144 KB)... OKAY [ 18.481s]
writing 'webtop'... OKAY [ 21.559s]
sending 'webtop' (262144 KB)... OKAY [ 18.192s]
writing 'webtop'... OKAY [ 22.479s]
sending 'webtop' (262144 KB)... OKAY [ 18.124s]
writing 'webtop'... OKAY [ 21.669s]
sending 'webtop' (54016 KB)... OKAY [ 3.768s]
writing 'webtop'... OKAY [ 4.137s]
sending 'radio' (21896 KB)... OKAY [ 1.445s]
writing 'radio'... OKAY [ 2.697s]
rebooting...
Press any key to continue . . .
UMMMMM, you didn't notice the flash failures in there? Yea, that's bad. What is the filename of the FXZ you're flashing? Cause this isn't a good thing. When I said flashing the wrong FXZ can brick the phone I wasn't speaking hypothetically.
SamuriHL said:
UMMMMM, you didn't notice the flash failures in there? Yea, that's bad. What is the filename of the FXZ you're flashing? Cause this isn't a good thing. When I said flashing the wrong FXZ can brick the phone I wasn't speaking hypothetically.
Click to expand...
Click to collapse
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip is what I used. I see the flash failures, but have no idea what that means or why they show up. I did a few searches and didn't find anything specific.
Akivaran said:
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip is what I used. I see the flash failures, but have no idea what that means or why they show up. I did a few searches and didn't find anything specific.
Click to expand...
Click to collapse
Oh man. It means you flashed the WRONG file. And have now bricked the thing which is why it won't boot.
cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
That is what you need to flash with. Show me the log when flashing this.
SamuriHL said:
Oh man. It means you flashed the WRONG file. And have now bricked the thing which is why it won't boot.
cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
That is what you need to flash with. Show me the log when flashing this.
Click to expand...
Click to collapse
Will do.
OMG IT BOOTED. I about lost my crap when I heard the noise. Thank you so much for being patient with me.
What I don't understand is why I was pointed to the other files. What are those for?
They're old versions which can't be used anymore. Delete the old FXZ's so you don't run into this problem again. The sucky part is that it bricked because of the wrong FXZ so had you used the proper one in the beginning, you wouldn't have lost the data partition. Ah well.
Hey guys, it seems I screwed up royally this time :crying:
What preceded:
I got off SafeStrap and installed BMM to use [Patch] Patch to change Boot Manager Menu partitions layout for System_2. I wanted to have a nice and clean system layout, hate SafeStrap's keeping of the system images in /sdcard/.
I flashed the patch, but there were some problems, I don't remember what kind of problems though... I suspect it somehow messed up with partitioning, but I don't know much about Linux or Android partitions, Windows user here.
Then I removed BMM, because I decided I liked SafeStrap more, and put SS back in. Installed cm-11-20140926-NIGHTLY-maserati.zip into non-safe system not to have system in /sdcard/. It worked, but Google Play was acting up - probably due to problems while applying GApps. After some more stuff I don't exactly recall, I ended up with boot hung at CM boot animation with rotating arrow.
I backed the system up to maybe return to it later - I thought it might be caused by formatting the Internal Storage (/sdcard/) by the computer in TWRP's USB Mass Storage connection.
Here's the backup log (902 KB) - shortened version (204 KB). I think mounting has been problematic even in the GApps installation before, maybe that was the original culprit?
The output is data.ext3.win and system.ext3.win, plus md5s and recovery.log. Is there a way to extract logcat from the backup to see why it got stuck?
I decided to do a complete wipe. I completely wiped everything I could in SafeStrap's TWRP menu, including /system/, while working on non-safe sytem. Then switched phone off to continue work when I have some more free time.
Shortly: I completely wiped everything I could in SafeStrap's TWRP menu, including /system/, and powered the device off.
After I switched it back on, it wouldn't boot even into SS (surprise surprise), hung at the red Motorola's M logo. I was like whatever, let's sfb and start clean.
Now the main problem: sbf won't flash, it gets stuck flashing system.img.
RDS Lite (both 5.7 and 6.1.4) says Failed flashing process. 20/25 flash system "system.img" -> USB error occured while reading/writing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried both 182 (that was there already) and 188 sbfs.
When using a bit changed script from D4 Utility:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
c:\stock\stock_jb_182\cdma_maserati_9.8.2O-72_VZW-18-2_1ff.x
ml>flash.bat
...>moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (512 KB)... OKAY [ 0.055s]
writing 'mbm'... OKAY [ 0.470s]
...>moto-fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.245s]
...>ping 1.1.1.1 -n 1 -w 1000 1>nul
...>moto-fastboot flash mbmloader mbmloader.bin
< waiting for device >
sending 'mbmloader' (42 KB)... OKAY [ 0.015s]
writing 'mbmloader'... OKAY [ 0.301s]
...>moto-fastboot flash mbm mbm.bin
sending 'mbm' (512 KB)... OKAY [ 0.306s]
writing 'mbm'... OKAY [ 0.460s]
...>moto-fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.235s]
...>ping 1.1.1.1 -n 1 -w 1000 1>nul
...>moto-fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 0.030s]
...>moto-fastboot flash logo.bin logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.101s]
writing 'logo.bin'... OKAY [ 0.265s]
...>moto-fastboot flash devtree device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.305s]
writing 'devtree'... OKAY [ 0.495s]
...>moto-fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.230s]
...>ping 1.1.1.1 -n 1 -w 1000 1>nul
...>moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 32.841s]
writing 'system'... OKAY [ 22.772s]
sending 'system' (262144 KB)... OKAY [ 28.117s]
writing 'system'... OKAY [ 22.493s]
sending 'system' (130816 KB)... FAILED (data transfer failure (Too many links)
)
...>moto-fastboot flash boot boot.img
sending 'boot' (8192 KB)... FAILED (command write failed (Unknown error))
...>moto-fastboot flash recovery recovery.img
sending 'recovery' (9216 KB)... FAILED (command write failed (Unknown error))
...>moto-fastboot flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... FAILED (command write failed (Unknown error)
)
...>moto-fastboot -w
erasing 'userdata'... FAILED (command write failed (Unknown error))
...>REM moto-fastboot flash radio radio.img
...>moto-fastboot reboot
rebooting...
...>
When I don't flash system nor radio, everything works fine:
Code:
jc:\stock\stock_jb_182\cdma_maserati_9.8.2O-72_VZW-18-2_1ff.x
ml>moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (512 KB)... OKAY [ 0.060s]
writing 'mbm'... OKAY [ 0.468s]
c:\...>moto-fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.225s]
c:\...>ping 1.1.1.1 -n 1 -w 1000 1>nul
c:\...>moto-fastboot flash mbmloader mbmloader.bin
< waiting for device >
sending 'mbmloader' (42 KB)... OKAY [ 0.010s]
writing 'mbmloader'... OKAY [ 0.296s]
c:\...>moto-fastboot flash mbm mbm.bin
sending 'mbm' (512 KB)... OKAY [ 0.321s]
writing 'mbm'... OKAY [ 0.475s]
c:\...>moto-fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.005s]
c:\...>ping 1.1.1.1 -n 1 -w 1000 1>nul
c:\...>moto-fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 0.035s]
c:\...>moto-fastboot flash logo.bin logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.100s]
writing 'logo.bin'... OKAY [ 0.260s]
c:\...>moto-fastboot flash devtree device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.321s]
writing 'devtree'... OKAY [ 0.490s]
c:\...>REM moto-fastboot flash system system.img
c:\...>moto-fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 1.281s]
writing 'boot'... OKAY [ 1.039s]
c:\...>moto-fastboot flash recovery recovery.img
sending 'recovery' (9216 KB)... OKAY [ 1.396s]
writing 'recovery'... OKAY [ 1.430s]
c:\...>moto-fastboot flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... OKAY [ 33.922s]
writing 'preinstall'... OKAY [ 22.595s]
sending 'preinstall' (262144 KB)... OKAY [ 34.226s]
writing 'preinstall'... OKAY [ 22.355s]
sending 'preinstall' (98304 KB)... OKAY [ 12.221s]
writing 'preinstall'... OKAY [ 8.340s]
c:\...>moto-fastboot -w
erasing 'userdata'... OKAY [ 0.695s]
erasing 'cache'... OKAY [ 0.291s]
c:\...>REM moto-fastboot flash radio radio.img
c:\...>moto-fastboot reboot
rebooting...
I even soldered a factory cable, but the power's probably not an issue, and now I have it hard-wired from USB charger to the battery contacts holding T5 screws I depleted the battery though (down to 2,6 V), it's been two days without charge now, with many attempts to flash. The battery wouldn't charge this way (usb power on battery wires) btw, it worked on all my previous phones
I'm working on a Windows 8.1 64 bit machine, running RSD Lite & all the scripts as Administrator and flashing from a SSD drive.
Any sugestions on how to unbrick? My last hope is that the power actually was the issue and the factory cable was faulty - gonna solder another one now.
I'd love to recover the phone as I refuse to lose HW keyboard and don't want to be without phone for month or so until a replacement eBay D4 gets shipped from the USA
Plus when I try to go to BP Tools (turn on with Vol Down + Vol Up pressed), it gets to this screen:
Code:
Invalid Flash Mode (S) (Boot Failure)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery Low
Cannot Program
Connect USB
Data Cable
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG Version (CG: system)
Invalid CG OTV (CG: system)
Normal power up:
Code:
AP Fastboot Flash Mode (S) (Boot Failure)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery Low
Cannot Program
Connect USB
Data Cable
The only Boot Mode Selection Menu option that has different output from the two is BP Only - it keeps the red "M" logo. It doesn't charge anyways though, if I'm not mistaken...
LuH said:
Plus when I try to go to BP Tools (turn on with Vol Down + Vol Up pressed), it gets to this screen:
Code:
Invalid Flash Mode (S) (Boot Failure)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery Low
Cannot Program
Connect USB
Data Cable
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG Version (CG: system)
Invalid CG OTV (CG: system)
Normal power up:
Code:
AP Fastboot Flash Mode (S) (Boot Failure)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery Low
Cannot Program
Connect USB
Data Cable
The only Boot Mode Selection Menu option that has different output from the two is BP Only - it keeps the red "M" logo. It doesn't charge anyways though, if I'm not mistaken...
Click to expand...
Click to collapse
if it says low battery it will not flash
if it says low battery your factory/fastboot cable is not correct
suggest buying a TBH Factory cable adapter
sd_shadow said:
if it says low battery it will not flash
if it says low battery your factory/fastboot cable is not correct
suggest buying a TBH Factory cable adapter
Click to expand...
Click to collapse
I like the adapter a lot Helped to a factory cable myself already though even with my buttery hands - it took three cables to do it correctly. But I only have a truly terrible soldering gun I inherited from my father, which has totally burnt insides (I wonder how it still didn't kill me ) so the soldering part rattles in the transformer and sometimes I need to wiggle it a bit to make the light work...
Anyways, after making myself a working factory cable, I have a working Droid back, woohoo!!! It was the power problem after all, even though I thought I got to bypass it...
Also charging the battery directly by connecting stripped USB cable to the battery screws actually works fine, i just used a dead cable. For anyone needing an alternative method when factory cable is not available, just cut any USB cable, strip red and black wires from inside and connect red wire to the right screw and black wire to the left screw. DON'T leave it connected for too long (1 hour should be enough, 3 hours may be too much) - this might bypass the protection circuitry and make your battery explode when overcharged for too long.
LuH said:
I like the adapter a lot Helped to a factory cable myself already though even with my buttery hands - it took three cables to do it correctly. But I only have a truly terrible soldering gun I inherited from my father, which has totally burnt insides (I wonder how it still didn't kill me ) so the soldering part rattles in the transformer and sometimes I need to wiggle it a bit to make the light work...
Anyways, after making myself a working factory cable, I have a working Droid back, woohoo!!! It was the power problem after all, even though I thought I got to bypass it...
Also charging the battery directly by connecting stripped USB cable to the battery screws actually works fine, i just used a dead cable. For anyone needing an alternative method when factory cable is not available, just cut any USB cable, strip red and black wires from inside and connect red wire to the right screw and black wire to the left screw. DON'T leave it connected for too long (1 hour should be enough, 3 hours may be too much) - this might bypass the protection circuitry and make your battery explode when overcharged for too long.
Click to expand...
Click to collapse
Connecting the usb wires directly to the battery terminals, while connected to the phone is very risky, many people have ruined their phones internal battery charger doing that. Posts all over the net about that...
sd_shadow said:
Connecting the usb wires directly to the battery terminals, while connected to the phone is very risky, many people have ruined their phones internal battery charger doing that. Posts all over the net about that...
Click to expand...
Click to collapse
Well, considering waiting a month for a factory cable or battery replacement (I'm from Europe), I decided to take my chances I do agree it's extremely risky and should be done with caution as a last resort.
Hello.
I am hoping some kind soul out there could help me solve my boot looping issue. I have been following the instructions from the mega-thread and have successfully managed to unlock the boot loader. However I also managed to get stuck in a boot loop. As such I have been reading up on Chapter 4 of the mega-thread but I have been unable to fix it.
Phone info:
Code:
Dual sim
Model number
- ALE-L21
Build Number
- ALE-L21C432B200
Android version
- 5.0.1
Android Security Patch Level
- 1 March 2016
Baseband Version
- 22.126.21.00.00
- 22.126.21.00.00
Kernel Version
- 3.10.61-gcd3fde7-dirty
- [email protected] #2
- Wed May 18 22:24:39 CST 2016
EMUI Version
- EMUI3.1
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.622s]
finished. total time: 1.178s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.545s]
finished. total time: 9.077s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.853s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.767s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.957s]
writing 'system'...
OKAY [ 7.476s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.980s]
writing 'system'...
OKAY [ 7.473s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.907s]
writing 'system'...
OKAY [ 7.423s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.394s]
writing 'system'...
OKAY [ 7.186s]
finished. total time: 100.983s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
I have flashed with both the dual and single sim files provided in the mega-thread. Neither solves my boot loop problem. How do I proceed from here?
Thank you.
try with C432B170 file... that may help
amageek said:
try with C432B170 file... that may help
Click to expand...
Click to collapse
Thank you for your suggestion. I grabbed the update.app file for HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU and extracted the BOOT.img, CUST.img, RECOVERY.img and SYSTEM.img with the HuaweiUpdateExtractor. After which I flashed my device again, console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.582s]
writing 'boot'...
OKAY [ 0.650s]
finished. total time: 1.234s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 6.196s]
writing 'cust'...
OKAY [ 3.977s]
finished. total time: 10.175s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.807s]
writing 'recovery'...
OKAY [ 0.903s]
finished. total time: 1.712s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.539s]
writing 'system'...
OKAY [ 7.464s]
sending sparse 'system' (459817 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.425s]
sending sparse 'system' (455915 KB)...
OKAY [ 12.435s]
writing 'system'...
OKAY [ 7.380s]
sending sparse 'system' (444418 KB)...
OKAY [ 12.311s]
writing 'system'...
OKAY [ 7.180s]
sending sparse 'system' (460198 KB)...
OKAY [ 12.624s]
writing 'system'...
OKAY [ 7.391s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.378s]
writing 'system'...
OKAY [ 0.809s]
finished. total time: 101.698s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
C:\adb>
However it did not end the boot loop sequence. I am presented with the logo then straight into a black screen. After 2 or 3 minutes the device reboots.
Did I do it incorrectly?
may be you didn't flashed in correct order??
try once this sequence:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
amageek said:
may be you didn't flashed in correct order??
try once this sequence:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Click to expand...
Click to collapse
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.583s]
writing 'boot'...
OKAY [ 0.645s]
finished. total time: 1.231s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.805s]
writing 'recovery'...
OKAY [ 0.896s]
finished. total time: 1.704s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 6.192s]
writing 'cust'...
OKAY [ 3.968s]
finished. total time: 10.162s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.667s]
writing 'system'...
OKAY [ 7.465s]
sending sparse 'system' (459817 KB)...
OKAY [ 12.933s]
writing 'system'...
OKAY [ 7.410s]
sending sparse 'system' (455915 KB)...
OKAY [ 12.644s]
writing 'system'...
OKAY [ 7.389s]
sending sparse 'system' (444418 KB)...
OKAY [ 12.462s]
writing 'system'...
OKAY [ 7.152s]
sending sparse 'system' (460198 KB)...
OKAY [ 12.775s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.403s]
writing 'system'...
OKAY [ 0.805s]
finished. total time: 102.527s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
Still no luck through, however the reboot cycle is much faster if that means anything.
I transferred the dload folder onto a SD card in order to restore. Holding down the volume up and down buttons along with power for 12 seconds. While the device does vibrate as if command was accepted it never shows anything beyond the logo.
Do you have any further advice or an idea as to what is my device's problem?
can you go to recovery? if yes, then you can wipe everything again and see if that helps..
3 key methods that try to install with stock recovery. Update.app file copy to dload folder.
Marcolomboss
amageek said:
can you go to recovery? if yes, then you can wipe everything again and see if that helps..
Click to expand...
Click to collapse
I have attempted this however nothing shows when holding down both volume and power buttons. The phone does vibrate as if the phone accepted the recovery mode command yet the screen stays black.
marcolomboss said:
3 key methods that try to install with stock recovery. Update.app file copy to dload folder.
Marcolomboss
Click to expand...
Click to collapse
I have also attempted this. I loaded my 32gb SD card with "HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU" update.app file. As previously stated trying to enter recovery mode however is not successful despite the phone vibrates as if it was.
Please advise. Thank you.
YetAnotherP8Owner said:
I have attempted this however nothing shows when holding down both volume and power buttons. The phone does vibrate as if the phone accepted the recovery mode command yet the screen stays black.
I have also attempted this. I loaded my 32gb SD card with "HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU" update.app file. As previously stated trying to enter recovery mode however is not successful despite the phone vibrates as if it was.
Please advise. Thank you.
Click to expand...
Click to collapse
any update.app file "Huawei Update Extractor" Open the program. After flashed in the recovery.img file. Sorry for bad english
Marcolomboss
YetAnotherP8Owner said:
Hello.
I am hoping some kind soul out there could help me solve my boot looping issue. I have been following the instructions from the mega-thread and have successfully managed to unlock the boot loader. However I also managed to get stuck in a boot loop. As such I have been reading up on Chapter 4 of the mega-thread but I have been unable to fix it.
Phone info:
Code:
Dual sim
Model number
- ALE-L21
Build Number
- ALE-L21C432B200
Android version
- 5.0.1
Android Security Patch Level
- 1 March 2016
Baseband Version
- 22.126.21.00.00
- 22.126.21.00.00
Kernel Version
- 3.10.61-gcd3fde7-dirty
- [email protected] #2
- Wed May 18 22:24:39 CST 2016
EMUI Version
- EMUI3.1
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.622s]
finished. total time: 1.178s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.545s]
finished. total time: 9.077s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.853s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.767s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.957s]
writing 'system'...
OKAY [ 7.476s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.980s]
writing 'system'...
OKAY [ 7.473s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.907s]
writing 'system'...
OKAY [ 7.423s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.394s]
writing 'system'...
OKAY [ 7.186s]
finished. total time: 100.983s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
I have flashed with both the dual and single sim files provided in the mega-thread. Neither solves my boot loop problem. How do I proceed from here?
Thank you.
Click to expand...
Click to collapse
try with vers.c432b132,flash in this order:
boot
recovery
cust
system
if is work,your imei will be null,in that case just update to a higher version(ex.c432b170)
marcolomboss said:
any update.app file "Huawei Update Extractor" Open the program. After flashed in the recovery.img file. Sorry for bad english
Marcolomboss
Click to expand...
Click to collapse
I am not sure I'm following what you are trying to convey. I have already flashed the recovery.img file with various firmware versions with no luck. Do you have a specific firmware version in mind?
cristi.blidariu said:
try with vers.c432b132,flash in this order:
boot
recovery
cust
system
if is work,your imei will be null,in that case just update to a higher version(ex.c432b170)
Click to expand...
Click to collapse
Fetched 'ALE-L21 C432B132 Europe channel Dual' and flashed as ordered. Black screen still occur. Recovery mode is still not responding.
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.553s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.174s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.873s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.844s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.520s]
writing 'cust'...
OKAY [ 4.174s]
finished. total time: 10.697s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.720s]
writing 'system'...
OKAY [ 7.479s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.505s]
writing 'system'...
OKAY [ 7.221s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.890s]
writing 'system'...
OKAY [ 7.427s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.818s]
writing 'system'...
OKAY [ 7.433s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.027s]
finished. total time: 100.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
Is there a reason why I can not enter recovery mode? What causes this issue that is preventing me from doing a recovery?
Thank you for your answers so far.
very interesting. You're in the wrong place, but where
Marcolomboss
YetAnotherP8Owner said:
I am not sure I'm following what you are trying to convey. I have already flashed the recovery.img file with various firmware versions with no luck. Do you have a specific firmware version in mind?
Fetched 'ALE-L21 C432B132 Europe channel Dual' and flashed as ordered. Black screen still occur. Recovery mode is still not responding.
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.553s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.174s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.873s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.844s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.520s]
writing 'cust'...
OKAY [ 4.174s]
finished. total time: 10.697s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.720s]
writing 'system'...
OKAY [ 7.479s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.505s]
writing 'system'...
OKAY [ 7.221s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.890s]
writing 'system'...
OKAY [ 7.427s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.818s]
writing 'system'...
OKAY [ 7.433s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.027s]
finished. total time: 100.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
Is there a reason why I can not enter recovery mode? What causes this issue that is preventing me from doing a recovery?
Thank you for your answers so far.
Click to expand...
Click to collapse
i have upload boot.img from aosap and twrp recovery here
https://mega.nz/#!3U1WwKRA!N2rNjghUugSSHtKDnbAzP1Xy4OlkI9CtyXz0jDxRBog
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
cristi.blidariu said:
i have upload boot.img from aosap and twrp recovery here
https://mega.nz/#!3U1WwKRA!N2rNjghUugSSHtKDnbAzP1Xy4OlkI9CtyXz0jDxRBog
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
Click to expand...
Click to collapse
Flashed with the provided images; console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (24064 KB)...
OKAY [ 0.613s]
writing 'boot'...
OKAY [ 0.381s]
finished. total time: 0.996s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.131s
C:\adb>
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
YetAnotherP8Owner said:
Flashed with the provided images; console results:
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
Click to expand...
Click to collapse
To enter the recovery mode you need to press and hold volume up and power buttons only
YetAnotherP8Owner said:
Flashed with the provided images; console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (24064 KB)...
OKAY [ 0.613s]
writing 'boot'...
OKAY [ 0.381s]
finished. total time: 0.996s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.131s
C:\adb>
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
Click to expand...
Click to collapse
read all my friend and do as i say:
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
cristi.blidariu said:
read all my friend and do as i say:
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
Click to expand...
Click to collapse
I apologize, I misread the instructions.
After the complete shutdown, I held down volume up and power button. Upon seeing the Huawei logo, I let go of the power button. After a few seconds, the screen goes blank, then booted into 'Huawei eRecovery' mode and presented with the same options as before. "Reboot", "Download new version and recovery" and "Shutdown".
Am I to choose "Download new version and recovery" option from this screen?
YetAnotherP8Owner said:
I apologize, I misread the instructions.
After the complete shutdown, I held down volume up and power button. Upon seeing the Huawei logo, I let go of the power button. After a few seconds, the screen goes blank, then booted into 'Huawei eRecovery' mode and presented with the same options as before. "Reboot", "Download new version and recovery" and "Shutdown".
Am I to choose "Download new version and recovery" option from this screen?
Click to expand...
Click to collapse
No,that not gone help at all,please try again to shutdown your phone and do the same think with volume up and power key,if is not gone boot in to recovery try again to flash but this time flash stock recovery
Sent from my ALE-L21 using XDA-Developers mobile app
cristi.blidariu said:
No,that not gone help at all,please try again to shutdown your phone and do the same think with volume up and power key,if is not gone boot in to recovery try again to flash but this time flash stock recovery
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
I attempted flashing with the provided files again, boot then recovery. I did not use 'fastboot reboot' command but instead held in the volume up button for 10 seconds until 'Huawei eRecovery' mode appeared. I chose shutdown, waited for the phone to completely shut off upon which I then held in volume up and power buttons. Soon as the Huawei logo appears, I let go of the power button and continued to hold in volume up. Once more I was presented with 'Huawei eRecovery' and three options of "Reboot", "Download new version and recovery" and shutdown.
I did notice if I disconnect the phone before attempting to enter recovery mode by holding in volume up and power buttons, instead of shown 'Huawei eRecovery' the screen stays blank as recovery mode is still not responding.
What is the command to flash the stock recovery image? 'fastboot flash stockrecovery'? And with what image should I flash it with?
YetAnotherP8Owner said:
I attempted flashing with the provided files again, boot then recovery. I did not use 'fastboot reboot' command but instead held in the volume up button for 10 seconds until 'Huawei eRecovery' mode appeared. I chose shutdown, waited for the phone to completely shut off upon which I then held in volume up and power buttons. Soon as the Huawei logo appears, I let go of the power button and continued to hold in volume up. Once more I was presented with 'Huawei eRecovery' and three options of "Reboot", "Download new version and recovery" and shutdown.
I did notice if I disconnect the phone before attempting to enter recovery mode by holding in volume up and power buttons, instead of shown 'Huawei eRecovery' the screen stays blank as recovery mode is still not responding.
What is the command to flash the stock recovery image? 'fastboot flash stockrecovery'? And with what image should I flash it with?
Click to expand...
Click to collapse
You can extract from any firmware stock recovery using huawei update extractor,what i gave you is a custom recovery,the command is fastboot flash recovery recovery.img
Sent from my ALE-L21 using XDA-Developers mobile app
Hey All,
I am attempting to install the n6f26u update to resolve the speakerphone issue, but my phone has already received a more recent (Oct 5, 2017) update from OTA. When I follow the instructions here
https://developers.google.com/android/images#instructions
the flash-all.bat sees that the bootloader is newer and stops, giving me an error.
I have looked all over this site and google, but do not see how to get around this. I do not know know if I am searching for the wrong thing or what, but any info on this would be great. I really need to go back to the previous version. I would love to be able to use this phone again.
bwquestion said:
Hey All,
I am attempting to install the n6f26u update to resolve the speakerphone issue, but my phone has already received a more recent (Oct 5, 2017) update from OTA. When I follow the instructions here
https://developers.google.com/android/images#instructions
the flash-all.bat sees that the bootloader is newer and stops, giving me an error.
I have looked all over this site and google, but do not see how to get around this. I do not know know if I am searching for the wrong thing or what, but any info on this would be great. I really need to go back to the previous version. I would love to be able to use this phone again.
Click to expand...
Click to collapse
Did you unlock the bootloader?
sd_shadow said:
Did you unlock the bootloader?
Click to expand...
Click to collapse
I ran the command
fastboot flashing unlock
The result showed OK [0.000s]
The phone screen shows
Device is UNLOCKED. Status Code: 3
I jut ran it again, this time it made it further, but still stopped. Here is the last part. If the rest is needed let me know.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot' (8491 KB) OKAY [ 0.281s]
Writing 'boot' OKAY [ 0.262s]
Sending 'recovery' (13881 KB) OKAY [ 0.469s]
Writing 'recovery' OKAY [ 0.181s]
Sending sparse 'system' 1/4 (520563 KB) OKAY [ 17.749s]
Writing sparse 'system' 1/4 OKAY [ 7.980s]
Sending sparse 'system' 2/4 (523233 KB) OKAY [ 17.504s]
Writing sparse 'system' 2/4 OKAY [ 6.711s]
Sending sparse 'system' 3/4 (498449 KB) OKAY [ 16.863s]
Writing sparse 'system' 3/4 OKAY [ 10.087s]
Sending sparse 'system' 4/4 (32756 KB) OKAY [ 1.106s]
Writing sparse 'system' 4/4 OKAY [ 0.429s]
Erasing 'userdata' OKAY [ 11.269s]
Sending 'userdata' (4501 KB) OKAY [ 0.166s]
Writing 'userdata' OKAY [ 0.292s]
Erasing 'cache' OKAY [ 0.047s]
Sending 'cache' (120 KB) OKAY [ 0.022s]
Writing 'cache' OKAY [ 0.031s]
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 103.359s
Press any key to exit...
bwquestion said:
I jut ran it again, this time it made it further, but still stopped. Here is the last part. If the rest is needed let me know.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot' (8491 KB) OKAY [ 0.281s]
Writing 'boot' OKAY [ 0.262s]
Sending 'recovery' (13881 KB) OKAY [ 0.469s]
Writing 'recovery' OKAY [ 0.181s]
Sending sparse 'system' 1/4 (520563 KB) OKAY [ 17.749s]
Writing sparse 'system' 1/4 OKAY [ 7.980s]
Sending sparse 'system' 2/4 (523233 KB) OKAY [ 17.504s]
Writing sparse 'system' 2/4 OKAY [ 6.711s]
Sending sparse 'system' 3/4 (498449 KB) OKAY [ 16.863s]
Writing sparse 'system' 3/4 OKAY [ 10.087s]
Sending sparse 'system' 4/4 (32756 KB) OKAY [ 1.106s]
Writing sparse 'system' 4/4 OKAY [ 0.429s]
Erasing 'userdata' OKAY [ 11.269s]
Sending 'userdata' (4501 KB) OKAY [ 0.166s]
Writing 'userdata' OKAY [ 0.292s]
Erasing 'cache' OKAY [ 0.047s]
Sending 'cache' (120 KB) OKAY [ 0.022s]
Writing 'cache' OKAY [ 0.031s]
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 103.359s
Press any key to exit...
Click to expand...
Click to collapse
Did it boot up?
Sent from my PH-1 using Tapatalk
sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
The phone was still showing the same screen. I did not want to mess anything up. When I read your reply I pressed the button on the right to "START".
The circle patterns are doing someting now. I will let you know when it is complete.
sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
The phone did boot. The set up ran and the settings show March 5 2017.
Thanks for you time.
sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
After a reboot of the phone, it only shows the word Google in while letters with an unlocked padlock on the screen. I can get to the original screen with the android and the status. Reloaded again, It boots up the first time, then reboot goes back to just Google with the unlocked padlock.
bwquestion said:
After a reboot of the phone, it only shows the word Google in while letters with an unlocked padlock on the screen. I can get to the original screen with the android and the status. Reloaded again, It boots up the first time, then reboot goes back to just Google with the unlocked padlock.
Click to expand...
Click to collapse
try a factory reset in recovery
As a general cautionary statement, when on a newer release and trying to go to an older release, don't use the flashall method. Fastboot flash system, boot and data separately. You don't want to run a chance that the bootloader downgrades. That might be one of the few ways to brick an N6.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
sd_shadow said:
try a factory reset in recovery
Click to expand...
Click to collapse
Thanks, It is working now. Unfortunately it did not fix the speakerphone issue. I am now installing the February release and will sideload the OTA for n6f26u and see if it makes a difference.
bwquestion said:
Thanks, It is working now. Unfortunately it did not fix the speakerphone issue. I am now installing the February release and will sideload the OTA for n6f26u and see if it makes a difference.
Click to expand...
Click to collapse
If you are referring to the storage phone echo bug that occurred with the February 2017 OTA, Google addressed that in the March 2017 security patches.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
If you are referring to the storage phone echo bug that occurred with the February 2017 OTA, Google addressed that in the March 2017 security patches
Click to expand...
Click to collapse
N6F26U is showing to be that release. I have loaded the factory image for March 2017, and also the factory image from February 2017 then side loaded the OTA for March 2017. Users still tell me there is an echo on the speakerphone when they talk to me. I can't figure out if I am doing something wrong or if it is just not working.