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.
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.
As the title says the stock slot was wiped on this Bionic. I have tried using BionicRestorer to fxz to 5.5.893 and 5.9.901 and it encountered a couple of errors. I'm not sure exactly what the mean though. The phone boots to the Moto logo, then the screen goes blank and the soft keys stay lit. Nothing else happens and I have to pull the battery. I tried booting into recovery mode but after selecting recovery I get the android laying on his back with a triangle/exclamation point above him.
I'm not sure what else I can do with this and would greatly appreciate some help. I do have a charger so I'm not worried about the battery getting low. I'm using Linux but do have access to Windows as well.
Here is the command line output from the BionicRestorer script:
Code:
Here we go, I don't stop on errors, once it starts there is no stopping
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.023s]
writing 'mbm'... OKAY [ 0.453s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbmloader mbmloader.bin
sending 'mbmloader' (40 KB)... OKAY [ 0.009s]
writing 'mbmloader'... OKAY [ 0.289s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.451s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdt.bin cdt.bin
sending 'cdt.bin' (16 KB)... OKAY [ 0.007s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase cache
erasing 'cache'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase userdata
erasing 'userdata'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash lbl lbl
sending 'lbl' (16 KB)... OKAY [ 0.007s]
writing 'lbl'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash logo.bin logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.061s]
writing 'logo.bin'... OKAY [ 0.267s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash ebr ebr
sending 'ebr' (16 KB)... OKAY [ 0.008s]
writing 'ebr'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbr mbr
sending 'mbr' (16 KB)... OKAY [ 0.007s]
writing 'mbr'... OKAY [ 0.397s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash devtree device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.041s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.514s]
writing 'system'... OKAY [ 21.258s]
sending 'system' (229120 KB)... OKAY [ 14.442s]
writing 'system'... OKAY [ 18.771s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.533s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash recovery recovery.img
sending 'recovery' (9216 KB)... OKAY [ 0.600s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdrom cdrom
sending 'cdrom' (12032 KB)... OKAY [ 0.771s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... OKAY [ 16.499s]
writing 'preinstall'... OKAY [ 22.208s]
sending 'preinstall' (49152 KB)... OKAY [ 3.106s]
writing 'preinstall'... OKAY [ 3.931s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash webtop grfs.img
sending 'webtop' (262144 KB)... OKAY [ 16.516s]
writing 'webtop'... OKAY [ 23.794s]
sending 'webtop' (262144 KB)... OKAY [ 16.515s]
writing 'webtop'... OKAY [ 23.305s]
sending 'webtop' (262144 KB)... OKAY [ 16.507s]
writing 'webtop'... OKAY [ 21.253s]
sending 'webtop' (262144 KB)... OKAY [ 16.521s]
writing 'webtop'... OKAY [ 22.130s]
sending 'webtop' (262144 KB)... OKAY [ 16.514s]
writing 'webtop'... OKAY [ 22.110s]
sending 'webtop' (54016 KB)... OKAY [ 3.408s]
writing 'webtop'... OKAY [ 5.240s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash radio radio.img
sending 'radio' (21768 KB)... OKAY [ 1.377s]
writing 'radio'... OKAY [ 3.805s]
I think I've tried flashing the wrong file in a mad case of Idon'tknowwhati'mdoingsoIshouldhaveleftittheheckalone. So I'm going to try flashing http://sbf.droid-developers.org/download.php?device=12&file=162 with RSD Lite as suggested in some other posts I've read today.
Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd
Ryan11271 said:
Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd
Click to expand...
Click to collapse
That's what I plan on doing. I can still get to recovery and ap fastboot mode. I'm going to d/l rsd now.
The biggest thing is that you cannot flash back to an earlier version than what had been installed. You can only flash the same version or newer.
How about this, I ordered a droid bionic, I'll root and put on safestrap, Once I do all that good stuff I'll make you a stock rom backup and send you the zip. I'll pm you when I get it
Probably doesn't have safestrap installed anymore, so a backup from safestrap wouldn't help.
Ohhh, I didn't think of that XD
Yeah I borked safestrap too but thanks for the offer though. I'm about to reboot into windows and try to rsd what I believe to be the correct version.
I get my pixel 4 xl oem unlocked(auto reset after the unlock) and try to flash Android 12 beta image of below link
https://dl.google.com/developers/android/sc/images/factory/coral-spp1.210122.022-factory-0b84a8a1.zip
but durning run flash-all.sh, it failed in writing system, any idea how to deal with this?
checking product...
OKAY [ 0.070s]
checking version-bootloader...
OKAY [ 0.070s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot_b' (65536 KB)...
OKAY [ 2.810s]
writing 'boot_b'...
OKAY [ 0.221s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.459s]
writing 'dtbo_b'...
OKAY [ 0.093s]
sending sparse 'system' 1/4 (262140 KB)...
OKAY [ 10.958s]
writing 'system' 1/4...
FAILED (remote: Partition system not found)
finished. total time: 15.109s
finnally I find the issue:
the fastboot on my test machine(ubuntu20.04) need sudo fastboot to run ,and with sudo , it uses the android studio old fastboot bin. after force replace the fastboot bin to newest , the flash is good
but any idea the fastboot flash need a sudo?
We will flash the ubuntu touch boot image which is required temporarily. And the currently latest sfos build for the QX1050.
1. Download ubuntu touch build from here and extract the boot.img
Ubuntu for Pro¹ X build job 2830649718 artifact.zip
2. Download SailfishOS 4.4.0.64 build from here and extract the userdata.simg
SailfishOS for Pro¹ X job 2807435728 artifact.zip
3. Flash using fastboot
Code:
fastboot flash boot_a boot.img
fastboot flash userdata userdata.simg
4. Reboot using fastboot reboot or fastboot continue
Thanks for moving mods! Did not realize its more appropriate here in the guides section than in the development section.
fastboot flash userdata userdata.img
fastboot flash userdata userdata.simg Typo
Nope, the sailfish userdata is in sparse format. So its .simg correctly.
Thats why you will not have the infamous "Invalid sparse file format at header magic" message from fastboot when flashing that .simg. Since fastboot expects sparse images, but *****es about raw images like the ubuntu boot.img above.
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
bobnot said:
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
Click to expand...
Click to collapse
what version of the android platform tools are you using? I'm on r33.0.2 and "fastboot flash userdata userdata.simg" works just fine for me
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
eltmosen said:
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
Click to expand...
Click to collapse
Neither SFOS or UT will boot
I also updated to latest fastboot from googles source. Still same issue as previously stated.