Database Info

[Q] ;Help please. Can't get my Touch Pro's boot to start

Hello
I've flashed my Touch Pro several times in the past 2 years and everything went always OK. The last time I've flashed with TAELROM_v5.23138_17SEP2010
Everything went OK for several days, until yesterday:
1. battery drained very quick after full charge (6 hours);
2. Can't put it to charge again;
3. Can't wake it up, even with other battery fully charged;
4. No boot menu;
5. With just access to bootloader mode
Some info:
Is the device HardSPL'ed
Yes: SPL-1.90.Olinex
Is the device unlocked
Yes
Access to bootloader mode (tricolour screen)
Yes (won't start the phone even if I try to soft reset in bootloader mode)
How can I revive?
Thanks in advance

If you can get into the bootloader just plug it into your usb port and flash a new ROM.

I've done it already, and the problem stays the same... Although the installation runs normally, after reinstall the phone doesn't restarts unless in bootloader mode!
Could it be a hardware problem?

Try pulling the sd card (and maybe the SIM card) and resetting. A corrupted sd card could jack up the device.

Farmer Ted said:
Try pulling the sd card (and maybe the SIM card) and resetting. A corrupted sd card could jack up the device.
Click to expand...
Click to collapse
if that does not help then is something wrong with hardware probably.
I always pull out sd card and sim before flashing with new rom just to avoid that kind of problems.

expert.. help me please..
i also have same problem as u'r.. the device stuck in 3 color bootloader, i already flash it with original factory rom, but nothin' change.. try using axe box to create goldcard, but the problem still not solve. can somebody help me pls...
1. when updating with factory rom (RUU_Raphael_hTC_Asia_5.07.707.2_signed_Raphael_52.58.35.30_1.11.25.01ship) it stuck at 25%
-message: error(226): flash write -iu634
2. when updating via sd card the message that appear is -updating failed, wrong OS..
what should i do next to survive my lovely phone?

My advice in this case is: try task29 before flashing your rom (without sd- and simcard in TP)

so, what i should do now my friends?

borisku said:
My advice in this case is: try task29 before flashing your rom (without sd- and simcard in TP)[already doing task29, but nothin' happen.. pls help me if u hv another solution.. ]
Click to expand...
Click to collapse

what would i do?: I would flash bootscreen via task29, then (different?) radio, then a different (stock?) rom. If that doesnt help, i dont know more, sorry... good luck
btw ehhhm: Your phone is a gsm, isnt it?

rumpang said:
i also have same problem as u'r.. the device stuck in 3 color bootloader, i already flash it with original factory rom, but nothin' change.. try using axe box to create goldcard, but the problem still not solve. can somebody help me pls...
1. when updating with factory rom (RUU_Raphael_hTC_Asia_5.07.707.2_signed_Raphael_52.58.35.30_1.11.25.01ship) it stuck at 25%
-message: error(226): flash write -iu634
2. when updating via sd card the message that appear is -updating failed, wrong OS..
what should i do next to survive my lovely phone?
Click to expand...
Click to collapse
Do you have hard spl? Or were you flashing a stock rom with a gold card? I would try flashing the stock rom for your device/carrier. You may be screwed, if you don't have hard spl.

In my case, the problem was hardware: charging malfunction.
Thanks to all of you who helped me

Farmer Ted said:
Do you have hard spl? Or were you flashing a stock rom with a gold card? I would try flashing the stock rom for your device/carrier. You may be screwed, if you don't have hard spl.[yes, i already flashing stock rom with gold card, but before the problem, i install the rom without hspl, that is my fault! anyway, do you have solution for this? ]
Click to expand...
Click to collapse

yes, my phone is gsm..

If you can get into bootloader, then try flashing hard spl. Then flash whatever you want.

i can get into bootloader mode, but d device can't flash with hspl (RaphaelHardSPL-Unsigned_190_1_3), it only stuck at 0%. try flashing hspl with sd card with no success. any other way to flash d hspl? do i need to flashing with the factory rom that has 1.9xxx spl? My SPL is 5.07.0000.. I need ur ADVICE Sir.. TQ..

[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

Help installing GB rom. May be bricked.

I'm a noob and I wiped my phone before trying recovery! DERP. Not sure what to do next.
So... I need a little help. I've been looking around and havent been able to find a situation like mine. I've got a completely wiped/factory reset HTC Inspire 4g. SD card is good and reformatted to fat32. Heres the basics. When I press the power button I get 3 vibrate and orange light, when I press volume down and power I get 5 vibrates and green light. When I plug phone in with usb (to computer or charger) I get clockworkmod recovery v5.0.2.7. I am able to toggle through options, all works fine.
This is where I need help and I get easily confused. What do I do to get this phone back to stock settings? I've tried putting the stock pd98img.zip file onto the sd card, then installing via clockwork recovery. When I do this, I get failed installation EVERY time. I've also tried connecting through ace hack kit on my lap top and running the stock settings flash. Whenever it resets the phone it does the 3 vibrates/orange light and stops.
I would really appreciate someone with a little more experience to walk me through what I need to do to recover.
Update: When I try to download the zip from the sd card via clockworkmod I get the error E:Signature Verification Failed. I'm not sure what this means.
If someone can solve my problem I'll buy them lunch or coffee! Some kind of gift card to your favorite place? I'd really like my android back!

Drdandy said:
I'm a noob and I wiped my phone before trying recovery! DERP. Not sure what to do next.
So... I need a little help. I've been looking around and havent been able to find a situation like mine. I've got a completely wiped/factory reset HTC Inspire 4g. SD card is good and reformatted to fat32. Heres the basics. When I press the power button I get 3 vibrate and orange light, when I press volume down and power I get 5 vibrates and green light. When I plug phone in with usb (to computer or charger) I get clockworkmod recovery v5.0.2.7. I am able to toggle through options, all works fine.
This is where I need help and I get easily confused. What do I do to get this phone back to stock settings? I've tried putting the stock pd98img.zip file onto the sd card, then installing via clockwork recovery. When I do this, I get failed installation EVERY time. I've also tried connecting through ace hack kit on my lap top and running the stock settings flash. Whenever it resets the phone it does the 3 vibrates/orange light and stops.
I would really appreciate someone with a little more experience to walk me through what I need to do to recover.
Update: When I try to download the zip from the sd card via clockworkmod I get the error E:Signature Verification Failed. I'm not sure what this means.
If someone can solve my problem I'll buy them lunch or coffee! Some kind of gift card to your favorite place? I'd really like my android back!
Click to expand...
Click to collapse
You only flash pd98 files from fast boot not from CWM recovery. Boot in bootloader and it will find it

I am going to come off as the biggest noob here, but its got to be done. How do you boot in bootloader?
EDIT: Alright. So Bootloader is Volume down and power. My phone won't boot into bootloader. Phone vibrate 5 times and green led comes on. Screen stays black the whole time.

Drdandy said:
I am going to come off as the biggest noob here, but its got to be done. How do you boot in bootloader?
EDIT: Alright. So Bootloader is Volume down and power. My phone won't boot into bootloader. Phone vibrate 5 times and green led comes on. Screen stays black the whole time.
Click to expand...
Click to collapse
Ok i dont use CWM but there maybe an option in there to reboot into bootloader. Try holding volume up and power. Could be confusing devices on that though

zelendel said:
Ok i dont use CWM but there maybe an option in there to reboot into bootloader. Try holding volume up and power. Could be confusing devices on that though
Click to expand...
Click to collapse
Nah, no other combo's work for getting into bootloader or rebooting it. From what I've read on other forums, if I can't get into bootloader, I'm bricked. Do you think since the phone is wiped back to factory settings that HTC would replace it under the warranty?

Since you can boot into recovery, adb should still work. Enter recovery then plug in your phone to PC and run adb reboot bootloader
Have you tried reflashing a rom in recovery aswell?

Drdandy said:
Nah, no other combo's work for getting into bootloader or rebooting it. From what I've read on other forums, if I can't get into bootloader, I'm bricked. Do you think since the phone is wiped back to factory settings that HTC would replace it under the warranty?
Click to expand...
Click to collapse
If you are booting into CWM your not back to factory. As stated above you can use adb to boot into bootloader

Just making sure I'm doing this right as its the first time I've ever use adb commands to me phone. Do I need to downloand Android SDK to write commands to the phone?

Okay. I've learned how to use the adb commands. That was cool. haha. So I popped the battery out, then back in to get to CWM. With phone connected to computer I tried adb reboot bootloader. My phone rebooted itself, but it did the 3 vibrates with a flashing orange LED. Adb reboot recovery does the same thing.
For being in recovery. Are you guys talking about the volume down power combination, when I do this and connect the phone to the pc, the pc doesn't detect the phone. So there is no abd commands/flashing roms to it in recovery.

Drdandy said:
Okay. I've learned how to use the adb commands. That was cool. haha. So I popped the battery out, then back in to get to CWM. With phone connected to computer I tried adb reboot bootloader. My phone rebooted itself, but it did the 3 vibrates with a flashing orange LED. Adb reboot recovery does the same thing.
For being in recovery. Are you guys talking about the volume down power combination, when I do this and connect the phone to the pc, the pc doesn't detect the phone. So there is no abd commands/flashing roms to it in recovery.
Click to expand...
Click to collapse
OK looks like your bootloader is messed up. Go to the ace hack kit thread. There you will find a link foe the IRC chat room. Go there and tell them what you did. They maybe able to help you.

Oneplus One Freezing On Startup

He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,

Zastarx said:
He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,
Click to expand...
Click to collapse
Your persist partition might be corrupt. Grab this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then do this with fastboot:
Code:
fastboot erase persist
fastboot flash persist persist.img

Didn't work sadly. Maybe I should just flash everything?

Zastarx said:
Didn't work sadly. Maybe I should just flash everything?
Click to expand...
Click to collapse
Yeah, it's worth a shot. You can find full instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471

Yay!
It worked, thanks a lot!

Nexus 5 bootloop, stuck in Rom intro - Don't know how to connect it to my pc

First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:

Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw

Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird

It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.

No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!

audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad

ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.

audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked

ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.

audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great

It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.

hmm not a bad idea at all. Thank you!