Database Info

[Q] Help needed, bootloader error frequently

Hi everyone, i am using milestone A853 model, i follow exactly the guide to root the phone and everything goes perfect, i can boot up and use all the custom rom as usual. BUT the problem now i having is, it happened randomly sometimes i reboot my phone it just got into this bootloader err 1A,23,35,23,00 and i have to flash the GOT 2.2.1.sbf again and do a nandroid restore, i have to flash my phone around 4 times a week.
FYI, i tried the 3 button combination to get into open recovery but still it leads me to the bootloader err page.. is there anyway i can get rid of this?? i need to constantly be with a pc to get my phone working

[d]amour said:
Hi everyone, i am using milestone A853 model, i follow exactly the guide to root the phone and everything goes perfect, i can boot up and use all the custom rom as usual. BUT the problem now i having is, it happened randomly sometimes i reboot my phone it just got into this bootloader err 1A,23,35,23,00 and i have to flash the GOT 2.2.1.sbf again and do a nandroid backup, i have to flash my phone around 4 times a week.
FYI, i tried the 3 button combination to get into open recovery but still it leads me to the bootloader err page.. is there anyway i can get rid of this?? i need to constantly be with a pc to get my phone working
Click to expand...
Click to collapse
According to this thread, it might be an issue with a bad SD card.
http://www.android-hilfe.de/motorola-milestone/12635-milestone-startet-nicht-mehr.html
Can you try with another SD card?
Is it possibly that you have the older version of the Milestone bootloader? (90.73), you can try to flash the VR from kabaldan's website( http://android.doshaska.net/rootable) instead of G.O.T., you just need to put OR on your SD card yourself.

i am using the bootloader 90.78 and androidiani 3.3 open recovery...i try to format my sd card first see if it helps....i flashed my phone yesterday and using a fresh new iceandfire rom 3.0, i tried a couple of times rebooting and turn off my phone and it just boot up without any problem, however this morning i tried to reboot once more and i got this bootloader error again...frustrating =/

[d]amour said:
i am using the bootloader 90.78 and androidiani 3.3 open recovery...i try to format my sd card first see if it helps....i flashed my phone yesterday and using a fresh new iceandfire rom 3.0, i tried a couple of times rebooting and turn off my phone and it just boot up without any problem, however this morning i tried to reboot once more and i got this bootloader error again...frustrating =/
Click to expand...
Click to collapse
AOR dont updated recently, try FuFu openrecovery. it is based on AOR but have many new features and fix, like mmc fix, ext4 module, etc...
if your problem is beacuse the sdcard then you have the mmc error, what is fixed be kabaldan, and he provided a module for the fix, or you have a broken sdcard.

Changing the a different OR will help? i already apply the dsifix.ko 2.6 by kabaldan in my /system/lib/modules directory, just only did a nandroid restore to my phone now, will monitor how long it will last till the next bootloader err...sigh, btw is it ok if i keep trying to reboot like 5 times in an hour time?

[d]amour said:
Changing the a different OR will help? i already apply the dsifix.ko 2.6 by kabaldan in my /system/lib/modules directory, just only did a nandroid restore to my phone now, will monitor how long it will last till the next bootloader err...sigh, btw is it ok if i keep trying to reboot like 5 times in an hour time?
Click to expand...
Click to collapse
5 times seems a bit excessive to me. If all you are trying to do is see if you will boot into the bootloader when you really wanted the recovery, 2 times every hour or so should suffice.

wait a sec, you can enter the recovery console? try to not use the autoboot to or script. if the phone booted to the bootloader mode you can see a triangle, then push the camera and the volume up button to entering the basic recovery mode.
at this point the sdcard not used. then you can try to the update menu, now the phone trying to load the OR update.zip from the sdcard. if you have problem only with the last step, then your sdcard maybe broken, if you have the error at the first step, it is possible that your phone nand memory is failing. in that case you need to call the motorola customer service for the repair.

vadonka said:
wait a sec, you can enter the recovery console? try to not use the autoboot to or script. if the phone booted to the bootloader mode you can see a triangle, then push the camera and the volume up button to entering the basic recovery mode.
at this point the sdcard not used. then you can try to the update menu, now the phone trying to load the OR update.zip from the sdcard. if you have problem only with the last step, then your sdcard maybe broken, if you have the error at the first step, it is possible that your phone nand memory is failing. in that case you need to call the motorola customer service for the repair.
Click to expand...
Click to collapse
Recovery console? you mean the console mode after enter the androidiani menu?i can go straight into AOR with the camera + power button after turning it off.
whenever i got the bootloader error, i cant do anything though, the camera button with volume up is not working.All i can do is flash the .sbf file again.
But for now my phone is still working since the last nandroid restore i did this morning, reboot a few times normally and also reboot to recovery both are working as usual.

[d]amour said:
Recovery console? you mean the console mode after enter the androidiani menu?i can go straight into AOR with the camera + power button after turning it off.
whenever i got the bootloader error, i cant do anything though, the camera button with volume up is not working.All i can do is flash the .sbf file again.
But for now my phone is still working since the last nandroid restore i did this morning, reboot a few times normally and also reboot to recovery both are working as usual.
Click to expand...
Click to collapse
it is sadly, but it is possible that your phone nand memory unstable or have some crc error. do you often reflash before?

vadonka said:
it is sadly, but it is possible that your phone nand memory unstable or have some crc error. do you often reflash before?
Click to expand...
Click to collapse
i only started flashing few weeks ago but the bootloader error occur too frequently that i have to flash at least once every 2 days...for now i see that it lasted longer than usual,if it is really nand memory unstable means that there is nothing i can do to fix it?

[d]amour said:
i only started flashing few weeks ago but the bootloader error occur too frequently that i have to flash at least once every 2 days...for now i see that it lasted longer than usual,if it is really nand memory unstable means that there is nothing i can do to fix it?
Click to expand...
Click to collapse
you cant fix that, only the motorola service, but i suggest to try it some benchmark software like antutu benchmark. with that you can test the memory and see what happened.

well i guess the only solution will be not turning off my phone/reboot for as long as i could, don't wan to take risk later it gets into bootloader error again

My phone always stuck at bootloader when it's hot while booting up.
Wait few minutes or use a fan to cool it down will solve it.
When this happen, recovery mode won't start
and flashing new ROM won't help or even make problem worse because of extra heat produced.
Avoid rebooting after gaming/heavy use is my workaround.

imTigger said:
My phone always stuck at bootloader when it's hot while booting up.
Wait few minutes or use a fan to cool it down will solve it.
When this happen, recovery mode won't start
and flashing new ROM won't help or even make problem worse because of extra heat produced.
Avoid rebooting after gaming/heavy use is my workaround.
Click to expand...
Click to collapse
when u stuck in the bootloader it shows the error code like mine? or just the usual bootloader screen? i tried leaving the phone for few hours without doing anything but it still stuck at the bootloader screen with error code =/

I doubt this will help, but can you try flashing an official 2.2 sbf and try it for a few days? or maybe get an official 2.2 sbf, then root it, then install a rom.

hey there just to informed you guys here that my phone currently had no bootloader error so far for a week, i am using Froyo Mod 2.9.3 and everything just work well. Wonder what happen actually to my phone previously when i flash other rom.
Just wanna ask will the following step i did causes a bootloader error?
-Flash 2.2.1 got sbf files.
-Reboot to recovery (using the latest minimod), Click on root phone (i not sure will this cause the problem as this is suppose to be for stock rom?? plz correct me if am wrong)
-Wipe Dalvik,cache and data
-Apply update of custom rom and gapps.
-Reboot

Failed to validate system image & stuck in fastboot

Hello, back in december I was trying to load up an app on my phone but in a video the guy said to download chainfire so I did and installed the driver and my phone got stuck in the warning unlocked bootloader screen and I really can't remember what I did but I did something with downloading the system restore image but it wouldn't work so I changed up the files and now my phone is stuck in fastboot and no longer is usable so I just threw it in my drawer and never used it again up until now here I am asking for help on how to resolve this issue. I'm no android techie so I really don't know much about anything other than rooting phones. My phone is a Moto G XT1031. Also I can't charge my phone because when I leave it, the phone just keeps rebooting and it really doesn't charge much.
UPDATE:
I managed to unlock the bootloader but now when I power it up, the device is stuck on the motorola screen.

If you can get into fastboot mode, try flashing a stock ROM for your phone.

audit13 said:
If you can get into fastboot mode, try flashing a stock ROM for your phone.
Click to expand...
Click to collapse
Thank bro it worked for me thanks a lot

Nexus 5 stuck on boot, help please!!!

Hello to you all, I am new to XDA and it is because of this problem I am having.
The other day, my N5 shut down unexpectedly and kept that virtual power button pressed (I've seen this happen to a lot of people). The next day, it stopped doing that, but the next big issue started: The phone was stuck on boot animation. Since then, I am not able to boot the phone, so I entered the bootloader (which is still functional) and tried to unlock the bootloader (I blame myself for not doing this since the beginning) from my PC but every time it reboots the phone to keep the changes, the bootloader locks itself again, preventing me to fastboot an image to my device
This is the main issue here, I can't start up my phone, the bootloader won't unlock and somehow, I can't ADB because my PC won't recognize the device. In other words, it seems my Nexus is bricked (may be the first Nexus in the history to be bricked).
I believe there must be a solution for this problem, can anyone help me please!?!?!
Thank you all!

this is how I fix mine.
Can you boot into recovery?

hongkongking said:
this is how I fix mine.
Can you boot into recovery?
Click to expand...
Click to collapse
Hey, thanks for this help, I'll let you know how that goes. And yes, I can boot into recovery.

My device isnt recognized on ADB, and everytime I try to unlock the bootloader, when the device restarts, immeditaly locks the bootloader again.

did u factory reset and wipe dalvik / cache? did u install a correct PC driver? did you ever using adb to connect to your phone?
I remember someone said sometimes you need to unlock the bootloader several times to get it unlocked.
from this and this, your nand flash seems has problem.
Try using LG Flash Tool to flash facory image, it doesn't need to unlock bootloader, but i think it's better not to write anything to nand flash as you don't know if it has problem or not, do so might make your phone completely bricked.

Please Help !. HTC One Mini stuck in BOOTLOADER Menu

My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP

Hi guys n gals
it appears ive inadvertantly deleted my rom i successfully unlocked bootloader installed recovery but over killed me wiping. Sso ive got an unlocked bootloader, have access to fasboot and recovery but fone is stuck at bootlader screen. How do I flash a rom now? as when hooked to a pc its no longer recognised. any help much appreciated!!!

moh19814 said:
My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP
Click to expand...
Click to collapse
I seem to be in the same situations... although I got to it in a different way. Where did you download the RUU from? is it version-main: 4.14.401.2 or higher?
Try: rootwiki dot net and search for htc one mini bootlocker unlock....this helped me to UNLOCK and put TWRP recovery on it... maybe it gets you a step closer.

Please help, soft bricked my [US] [Sprint] Samsung Galaxy S6 SM-G920P

After around 5-6 hours this morning/afternoon, I've officially given up on fixing this on my own, and I've all but accepted my device to be a $600 paperweight.
I decided to make one last attempt at saving it by posting for help.
Problem: My phone has a feature called "FRP" (Factory Restore Protection), which is tied to one's Google account. Basically, if you have a Google Account on the phone, it locks the phone to any custom binary/custom OS/whatever.
Once I realized this, in order to root my phone, I went in and removed my Google accounts. Sure enough, this disabled the FRP Lock, and I was able to root my device.
After rooting my device, I re-added my Google accounts and went about my business for the next couple of weeks or so.
Just this morning, my phone was having issues charging, so I decided it'd be a good idea to give my phone a reboot. Big problem. It turns out I simply haven't ever turned off my phone since I rooted it. On top of that, I didn't think the FRP Lock would apply to booting the phone, I thought it only affected flashing new firmware. I was wrong.
After my phone turned off, red text appears at the top of the screen: "Custom binary blocked by FRP Lock".
This is the problem. It simply cannot boot. Because it cannot boot, I cannot remove the Google accounts to disable the lock and resolve the problem. Because the lock can't be disabled, I can't flash the phone's original firmware, because FRP Lock will stop anything and everything I try to do.
---
Goodbye 1k+ photos on phone... And, well, goodbye *phone*.
Unless someone has any helpful thoughts! And that's why I'm here.
tl;dr: Soft bricked phone due to FRP Lock. Not able to restore original firmware, factory restore, or boot into phone's operating system.
Important: The phone turns on, and I have access to the recovery menu as well as "Download Mode"
---
What I have tried:
Factory restoring through the recovery menu, doesn't have any effect
Flashing stock firmware through Odin (Nand write failure)
Flashing a custom recovery environment (TWRP) through Odin (FRP Lock blocked this flash)
ADB and Fastboot cannot recognize the device
Tried to use Kies 3 and Smart Switch to "re-initialize" my OS or something. Both failed, saying that my phone wasn't compatible, and that my serial number was invalid (it was, in fact, correct)
---
And I probably did more things that I simply don't remember. The point here is that I've done everything, and literally everything has failed for one reason or another.
I feel like it is a possibility that if I attempted another stock ROM, then I might be able to avoid the Nand Write Failure. But again, I don't know, and I've almost accepted that I need to start looking for cheap alternative phones.
Thanks in advance, I really hope that this can be fixed one way or another. I'd be sad to see my photos disappear, but if it was the only way for my phone to work again, I could live with it.

have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.

Cosmic Blue said:
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Click to expand...
Click to collapse
I thought about doing that, but I have no way of wiping the phone. What do you suggest?

you can wipe the phone through recovery. it is under the advance section. you will need to delete each section manually.

1. Go to download mode
2.Untick auto reboot,
3.Flash twrp
4.do not reboot to system, reboot to recovery.
5. Install super su and reboot system
Done.

Cosmic Blue said:
you can wipe the phone through recovery. it is under the advance section. you will need to delete each section manually.
Click to expand...
Click to collapse
I am not running a custom recovery OS, there is no Advanced section. :s

Yarraque said:
1. Go to download mode
2.Untick auto reboot,
3.Flash twrp
4.do not reboot to system, reboot to recovery.
5. Install super su and reboot system
Done.
Click to expand...
Click to collapse
When I try to flash TWRP (or anything for that matter), FRP Lock blocks the flash.

Purlek said:
When I try to flash TWRP (or anything for that matter), FRP Lock blocks the flash.
Click to expand...
Click to collapse
Go to the developer settings and unlock "oem unlock" thing. Try again.

Yarraque said:
Go to the developer settings and unlock "oem unlock" thing. Try again.
Click to expand...
Click to collapse
I was unable to boot into the phone.
However, I've more or less resolved the issue.
The issue was that when I was first trying to flash stock firmware, I was using an old version. I've read since then that that doesn't work. So I spent 15 hours+ downloading the latest firmware of 6.0.1, and sure enough, it flashed successfully.

Purlek said:
I was unable to boot into the phone.
However, I've more or less resolved the issue.
The issue was that when I was first trying to flash stock firmware, I was using an old version. I've read since then that that doesn't work. So I spent 15 hours+ downloading the latest firmware of 6.0.1, and sure enough, it flashed successfully.
Click to expand...
Click to collapse
Oh nice to hear ^^

Samsung FRP
Cosmic Blue said:
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Click to expand...
Click to collapse
Would this work with the Samsung Account Factory Reset Protection?