Related
I was on official stock ICS i took complete backup of my Stock rom and flushed ICSupercharged one, It was working fine on it, than i flushed MIUI ROM using "Boot Menu Manager" than i tried to flush restore my stock rom, for that i formated data,system etc and tried to restore Stock rom it failed due by error, checksum mismatch. Now my mobile is in Soft Brick condition, i followed this post too Soft Brick using RSD Lite 6.0 , Soft Boot with "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip" Rom but did't work for me it gives error while flushing
First of all that is flashing a ROM. Not flush.
Did you flash the right fxz via RSD Lite?
Re
Lifehacker7 said:
First of all that is flashing a ROM. Not flush.
Did you flash the right fxz via RSD Lite?
Click to expand...
Click to collapse
I downloaded InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip rom from http://sbf.droid-developers.org/edison/list.php which was recommended in http://forum.xda-developers.com/showthread.php?p=34613531
cheeta123 said:
I downloaded InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip rom from http://sbf.droid-developers.org/edison/list.php which was recommended in http://forum.xda-developers.com/showthread.php?p=34613531
Click to expand...
Click to collapse
What is the error? You're putting phone in fastboot and flashing via RSD right?
And is your phone ATT?
Try http://forum.xda-developers.com/showthread.php?t=1961310
If not ATT then that's not the one you flash. Look here - http://forum.xda-developers.com/showthread.php?t=1934874
Error i have
Lifehacker7 said:
What is the error? You're putting phone in fastboot and flashing via RSD right?
And is your phone ATT?
Try http://forum.xda-developers.com/showthread.php?t=1961310
If not ATT then that's not the one you flash. Look here - http://forum.xda-developers.com/showthread.php?t=1934874
Click to expand...
Click to collapse
Yes my mobile is ATT i was downloaded rom from your given link i tried Fastboot with RSD light and i get "allow-mbmloader-flashing-mbm.bin phone returned failed" error, and if i flush MIUI rom or any other which i was flushed before and was working fine .
I changed my pc now it flush but keep progressing
i was using it on 32 bit machine when i tried to flush it on 64 bit machine, it gives keep progressing at "2/19 reboot-bootloader" and dont progress
I had a similar problem using RSD. (see my original thread)
Try using a script as detailed in this thread
So i have a Droid Razr Maxx HD xt926
it is on the latest 4.2.1 ota
It was starting to run slow, so i figured it was time to root and get a custom rom. but what i didn't realize is you cant unlock boot-loader.
So i rooted the phone, no issues. i tried to flash TWRP and CWM and both failed.
So when i go to recovery all i get is a black screen with white writiing that says
AP Fastboot Flash Mode (s)
10.9B(#) (sha-1e9f, 2013-05-25 01:04:26)
eMMC info: Size 32GB
Divice is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
I can exit out and get back to android.
Since i can get the bootloader unlocked (at least i dont think there is a way) i want to flash everything back to factory, it can be unrooted as well. just want a clean start on it.
any help would be great thanks.
Can't flash twrp or cm on locked bootloader.
Sent from my DROID RAZR HD using xda app-developers app
xlow78 said:
Can't flash twrp or cm on locked bootloader.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Yea i figured that out, so i was triing to get it back to stock.
Figured too late though .
Did you try rsd lite?
Sent from my DROID RAZR HD using xda app-developers app
soloblazer said:
So i have a Droid Razr Maxx HD xt926
it is on the latest 4.2.1 ota
It was starting to run slow, so i figured it was time to root and get a custom rom. but what i didn't realize is you cant unlock boot-loader.
So i rooted the phone, no issues. i tried to flash TWRP and CWM and both failed.
.............
any help would be great thanks.
Click to expand...
Click to collapse
sounds like you jacked stock recovery. if it will boot up, try using this http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar to put the stock recovery back on. i cant say for sure it will work but i think it will.
bweN diorD said:
sounds like you jacked stock recovery. if it will boot up, try using this http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar to put the stock recovery back on. i cant say for sure it will work but i think it will.
Click to expand...
Click to collapse
If the bootloader is locked, it's highly unlikely that attempting to flash a recovery would've touched the stock recovery. With that being said, you can use one of the utilities to flash back to completely stock or use RSD and flash the most up-to-date XML from here:
http://sbf.droid-developers.org/vanquish/list.php
RikRong said:
If the bootloader is locked, it's highly unlikely that attempting to flash a recovery would've touched the stock recovery. With that being said, you can use one of the utilities to flash back to completely stock or use RSD and flash the most up-to-date XML from here:
http://sbf.droid-developers.org/vanquish/list.php
Click to expand...
Click to collapse
true but you have to modify files before rsd will work, and the utilities say dont use on the latest update (locked) unless there is one i haven't seen, correct?
bweN diorD said:
true but you have to modify files before rsd will work, and the utilities say dont use on the latest update (locked) unless there is one i haven't seen, correct?
Click to expand...
Click to collapse
I've never had to modify the XMLs to work in RSD, but you might have to for some of them. You can swap files in the utilities and put the newest update in there. Also, flashing your zip or any other zip should clear the flash fail.
RikRong said:
I've never had to modify the XMLs to work in RSD, but you might have to for some of them. You can swap files in the utilities and put the newest update in there. Also, flashing your zip or any other zip should clear the flash fail.
Click to expand...
Click to collapse
Hey guys thanks for all the answers, i will try this monday, sorry for late reply, had some things come up this weekend, so wont have time to work on it. I just want to get it back to completely stock since i cant unlock the bootloader and isntall custom rom.
soloblazer said:
Hey guys thanks for all the answers, i will try this monday, sorry for late reply, had some things come up this weekend, so wont have time to work on it. I just want to get it back to completely stock since i cant unlock the bootloader and isntall custom rom.
Click to expand...
Click to collapse
Ok guys i am ready to try. How do i flash a zip file if i cant get into recovery?
What should i try first?
soloblazer said:
Ok guys i am ready to try. How do i flash a zip file if i cant get into recovery?
What should i try first?
Click to expand...
Click to collapse
boot the phone up (just power on), after on plug it into your pc, use the tool i posted in #5 (just going off what RikRong said, any successful flash should clear the failure) flash "stock recovery", let it reboot and see if its fixed.
if its not fixed, im still under the impression you will have to do one of 2 things to fix it from what i read others post previously,
-replace the files in matts utility with the latest ones from the stock files, or
-modify the xml file in the latest sbf to get rsd to work without failing
bweN diorD said:
boot the phone up (just power on), after on plug it into your pc, use the tool i posted in #5 (just going off what RikRong said, any successful flash should clear the failure) flash "stock recovery", let it reboot and see if its fixed.
if its not fixed, im still under the impression you will have to do one of 2 things to fix it from what i read others post previously,
-replace the files in matts utility with the latest ones from the stock files, or
-modify the xml file in the latest sbf to get rsd to work without failing
Click to expand...
Click to collapse
First one worked, thanks guys, phone is good to go. Does anyone know if there will ever be a unlocker for the bootloader?
soloblazer said:
First one worked, thanks guys, phone is good to go. Does anyone know if there will ever be a unlocker for the bootloader?
Click to expand...
Click to collapse
unlikely
btw, i swapped the files in Matts utility for the latest update if you want it. im working on switching out the root method in it too to the new one.
its posted in the dev forum
CM10.1 Android 4.2.2 Razr HD XT925
Already installed various recoveries only my device so enter the stock recovery, bootloader unlocked with this, I want to install cm10.1.3 4.2.2 and I can not, can someone help me?
My Droid Razr HD is doing the same thing
My screen says all of that also.
its says its locked and the battery is ok and all of that
I was trying to root my phone which was unsuccessful.
Now I cannot start and run my phone properly.
when it comes on it has me choose a language and press start and then acts like its loading and says it may take a few minutes. It will do that for hours and never move on to the next step.
How did you fix yours and recover it?
None of the other options on the reboot screen work...
I had tried:
normal start up
AP fast Boot
Recovery
BP Tools
They all lead to the same thing with the language selection and so on.
What can I do?
McmanisCody said:
My screen says all of that also.
its says its locked and the battery is ok and all of that
I was trying to root my phone which was unsuccessful.
Now I cannot start and run my phone properly.
when it comes on it has me choose a language and press start and then acts like its loading and says it may take a few minutes. It will do that for hours and never move on to the next step.
How did you fix yours and recover it?
None of the other options on the reboot screen work...
I had tried:
normal start up
AP fast Boot
Recovery
BP Tools
They all lead to the same thing with the language selection and so on.
What can I do?
Click to expand...
Click to collapse
assuming you have a 926, re-flash it with this.
if you have a 925 do NOT use ^^ that. you will have to use rsd instead.
I am having a similar issue but my bootloader is unlocked and no matter what I flash to recovery recovery won't work anymore whether it being a factory reset or trying to just plain boot in to it.
CONC3PT said:
I am having a similar issue but my bootloader is unlocked and no matter what I flash to recovery recovery won't work anymore whether it being a factory reset or trying to just plain boot in to it.
Click to expand...
Click to collapse
on the bootloader screen it says "status code 3" correct?
you cant flash cwm or twrp with fastboot?
what exactly is it doing or not doing and does the flash dialog indicate it flashing ok?
you imply, you cant boot into recovery, then say a factory reset wont work. what happens exactly in either of those attempts?
after you flash a custom recovery, you have to power off the phone and boot right into it and flash the su zip (do not boot the system in between), you know that correct?
any other info you can provide that i may have left out could be helpfull in getting this working for you.
Hello everyone,
I know this tread is old but, I have a problem and I hope someone here can help me. I have a mot razr 926 with these specs:
android version 4.1.2;
System version 9.30.1.XT926.Verizon
Kernel 3.0.31 ( I believe is stock)
Build number 9.8.1Q-94-1
My phone was rooted before with stock rom; I had to do a factory reset; so I reset, rooted again and my mistake it was trying to unlock the bootloader ( I know, I know, it's 9.30....)
Now my problem is that I don't have "recovery" or I don't have access to it. Things that I have tried:
Moto utility 1.34
Moto utility 1.3 gpt fix
Razr HD Recovery flasher V7 (tried to install cwm and stock)
I'm just trying to get any recovery working.... any help would be appreciated
Thanks
kpitao said:
Hello everyone,
I know this tread is old but, I have a problem and I hope someone here can help me. I have a mot razr 926 with these specs:
android version 4.1.2;
System version 9.30.1.XT926.Verizon
Kernel 3.0.31 ( I believe is stock)
Build number 9.8.1Q-94-1
My phone was rooted before with stock rom; I had to do a factory reset; so I reset, rooted again and my mistake it was trying to unlock the bootloader ( I know, I know, it's 9.30....)
Now my problem is that I don't have "recovery" or I don't have access to it. Things that I have tried:
Moto utility 1.34
Moto utility 1.3 gpt fix
Razr HD Recovery flasher V7 (tried to install cwm and stock)
I'm just trying to get any recovery working.... any help would be appreciated
Thanks
Click to expand...
Click to collapse
Have you tried the stock recovery??, it can be tricky to get into stock recovery by pressing the correct combination of buttons
EDIT: You can use RSD Lite to update your phone to 182.46.10 and use Towelroot to re-root the phone. Once rooted, you can use Motoapocalypse to unlock bootloader.
EDIT 2: Read this thread: http://forum.xda-developers.com/droid-razr-hd/general/index-motorola-droid-razr-hd-2015-t3167557
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
After trying to update to 4.4 via the posted .zip my phone is now unable to get passed the bootloader, with the resulting error "Partition (boot) Security Version Downgraded Boot up Failed"
I have tried restoring factory via RSD Lite, House of Moto, fastboot, and through the device itself, all to no avail. Please help - I have never had a device end up this far gone and am in no desire of having an expensive paperweight.
This is a Non-Developer Edition Droid MAXX
Yachter99 said:
After trying to update to 4.4 via the posted .zip my phone is now unable to get passed the bootloader, with the resulting error "Partition (boot) Security Version Downgraded Boot up Failed"
I have tried restoring factory via RSD Lite, House of Moto, and through the device itself, all to no avail. Please help - I have never had a device end up this far gone and am in no desire of having an expensive paperweight.
Click to expand...
Click to collapse
Check this out.
http://forum.xda-developers.com/showthread.php?p=48742551
Sent From My KitKat Ultra
Caseyk621 said:
Check this out.
http://forum.xda-developers.com/showthread.php?p=48742551
Sent From My KitKat Ultra
Click to expand...
Click to collapse
No luck with this flashing the recovery fails, the update.zip was wiped from phone and adb is unable to recognize device to push file over
i have the same problem
you must wait until FXZ 4.4. KitKat Firmware will be released.
then flash it by fastboot
sp47 said:
i have the same problem
you must wait until FXZ 4.4. KitKat Firmware will be released.
then flash it by fastboot
Click to expand...
Click to collapse
I suspected that'd be my only option... Any knowledge on how soon it will be released? is there a normal length of time that it usually takes?
Yes you are right. It's not only yours option. Everybody of us with the same problem you have an opportunity to solve this waiting for SBF 4.4.
I think it will be in one or two weeks.
Don't panic your phone as mine is not hard bricked, it's only soft bricked. It's bootlocked - the main reason we cannot to downgrade to existing 4.2.2
Stay tuned.
Yachter99 said:
After trying to update to 4.4 via the posted .zip my phone is now unable to get passed the bootloader, with the resulting error "Partition (boot) Security Version Downgraded Boot up Failed"
I have tried restoring factory via RSD Lite, House of Moto, fastboot, and through the device itself, all to no avail. Please help - I have never had a device end up this far gone and am in no desire of having an expensive paperweight.
This is a Non-Developer Edition Droid MAXX
Click to expand...
Click to collapse
You are running into a similar problem that others (including myself) have, where the 4.4 update partially installed. If you try to SBF (using RSD Lite, HouseOfMoto, fastboot, or otherwise), It will not succeed because the bootloader doesn't like the fact that you wen't backwards to an older boot.img. Currently, we don't have a new boot.img from the KitKat update because that file is not contained anywhere in the update.zip (it only has a boot.img.p patch, rather than a whole new img file), and we don't have the SBF yet. Once the SBF comes out, this should fix the problem for you entirely as it will replace your boot.img, your recovery, and system partition regardless of their current contents.
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.
BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet
BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.