Related
A strange thing happened and now I can't escape the bootloader screen. I lost my phone for a two days and when I found it it wouldn't come on. I connected it to a power cable and it immediately brought up the bootloader. The charge light won't come on but now the phone will power on without the power cable. Problem is it just brings up the bottloader and tries to install the rom image on the sd card. I put a new image on the card reinserted it and then allowed it to reflash. But it still just brings up the bootloader. Any advice?
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.
Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.
orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Lennyz1988 said:
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.
Click to expand...
Click to collapse
Reflashed from PC, reboot to bootloader behavior does not change.
ultramag69 said:
Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.
Click to expand...
Click to collapse
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?
cyberscribe said:
Reflashed from PC, reboot to bootloader behavior does not change.
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?
Click to expand...
Click to collapse
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1
this is certainly strange, could it be something with the SPL, i would look into that next if this doesnt help
cyberscribe said:
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1
Click to expand...
Click to collapse
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.
stevedebi said:
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.
Click to expand...
Click to collapse
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.
cyberscribe said:
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.
Click to expand...
Click to collapse
Fixed! Stable as a rock
cyberscribe said:
Fixed! Stable as a rock
Click to expand...
Click to collapse
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!
cyberscribe said:
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!
Click to expand...
Click to collapse
task 29 got me to the rom splash screen
cyberscribe said:
task 29 got me to the rom splash screen
Click to expand...
Click to collapse
reflash ROM from PC not SD. Reflashing after that from SD works. Hope I don't have to do this every time I change a battery!
I think I may be having the same or a similar issue as you cyberscribe. All of a sudden, I am getting restarted into the bootloader too.
I was using an older NRG 2.1 ROM (April-ish) and had to pull the battery after it froze up. Nothing new, it happens. The new part is that it would only restart into the bootloader screen. I thought it might be the older ROM, so I Task 29'ed and flashed NRG's newest 2.1 June 2nd ROM.
Successful boot and ROM setup while connected to USB. Unplugged USB, restarted phone, BOOTLOADER.
Plugged in USB, successful boot.
Unplugged USB, BOOTLOADER.
Plugged in wall outlet, successful boot.
Unplugged wall outlet, BOOTLOADER.
Obviously, I can conclude that there is an issue with trying to boot on battery power, or at least while not connected to a power source.
Anyone ever have this happen? Or have any ideas why this would be happening? I really don't want to have to find a power source every time I need to restart my phone, haha. I am still trying to troubleshoot further and will update if I find anything else worthwhile.
Also last night I tried restarting while plugged into car adapter, which as expected booted fine every time.
However, this morning I just restarted on battery power and it booted fine also. Nothing changed from last night to this posting. Honestly, I am completely at a loss as to why I am getting restarted into the boot loader seemingly at random. I thought I had it nailed down with the power source, but now that apparently is not the issue.
cyberscribe, are you still having issues? Anyone else ever have this problem? Any thoughts on a cause or solution? Or anything to help troubleshoot?
After the bootloader first pops up, there is a very quick screen that flashes, "Loading.... No image file", then goes back to the bootloader screen.
I have to discount my earlier theory that it will always boot when connected to any power source. Now it will only boot when connected via USB to the PC.
Looks like I am going to have to re-flash the stock ROM and then stock SPL and see if this solves the issue. Then, if not, I guess a warranty claim is in my near future.
I really wish we could have gotten some replies from smarter people than myself in this thread. haha
Finally flashed back everything to stock (SPL, radio, ROM) and still having the bootloader issue, looks like it is going to be a warranty claim after all.
Sounds more like a memory issue if it can't find the image file. If you both got your Rhodiums from the same carrier it could be a bad batch of phones...
Same issue on my tilt 2 just cropped up today. If I am reading the above correctly it sounds like 2 tilts and a t-mob rhodium having the issue, so different carriers. =/
Soft reset the handset and set it down, picked it back up and it was in bootloader. All attempts to get it out of bootloader (reflashing from sd, pc etc.) seem to complete just fine, but upon reboot dump into bootloader. May be a different problem than OP as I havent had any success in getting a boot after reflash.
Not sure if I am having the same problem, when I try to turn on it just comes up with the Touch pro 2 screen with the red text in the bottom left hand corner, I am using an energy Rom again from about April, I have tried re flashing but pc wont recognise/find phone, Wha acn be done?
This is a list of events that I have gone through today. I received a new charger because the old one I had became defective & was charging my phone up & then it would go back down to 0% & then shut off & it would end up in a problem where the phone would not turn on unless I pulled out the battery while the AC was in & then it was able to charge but still it would turn on, on its own to drain the battery when off & this was very frustrating. The charger I have now works but the device acts strange over the last few months doing a task29 & flashing the first ROM after would make that ROM not work & then I had to flash a totally different ROM to make it work. I was using Android & it had died a few times & also I experienced the same thing I did when it would charge up & go back down to 0%. please read below:
I got my new charger today & at 62% of charge I decided to flash to a custom ROM via mem card again well the ROM was a success but when pulling battery out to restart it didnt want to work. So I went to flash again in bootloader by memory card it shut off on me in the middle & restarted into bootloader again & shut off again right away. I did a task29 it worked got it out of bootloader & now the orange led flashes off & on when its off & now ive gotten that to stop. What exactly is wrong with this device?
it was @ 73% and finally setup a ROM NRGY however it ended up shutting off on its self & going into a power boot loop constantly restarting until that ROM can no longer start & now its stuck on the boot screen w/ its info.
I flashed the stock SPL on USB now im going to try to flash the carriers ROM back.
Stock SPL = Successful!
2nd Touch Pro 2 ROM Version Flash = Successful!
Its working for now. Battery is @ 80%
AHH! After charging to 100% idk what it did but when I went into the other room to check out its all possessed.
I have a black screen w/ white text that says:
The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source.
Press Volume Up to reset your device or press any other button to cancel.
This operation will delete all your personal data and restore the device to its factory default settings.
IDK how this happened.
When I hit any key it didnt do anything it was stuck until I did a battery pull. Then I restarted the device it was stuck at the boot screen w/ its red info. It erased the entire ROM. Then I tried to do recover mode & it did nothing. I tried to flash the stock ROM again & no results & then again & still no results. I think its now not accepting the ROM at all since from: in the ROM update utility is blank.
Now it decides to get past the boot screen but then it malfunctions again & restarts itself & it tries to setup a 2nd time then after it does & its on sense home for a couple of mins it reboots twice & now its stuck on the boot screen again.
Things that I can think of.
- Isn't your batterie just broken? You will break your batteries when you deplete them completely. Maybe try a new batterie, because you said that you let it die for a few times. It could be that this is causing your problems.
- Did you flash true usb when you were in the bootloader? Give that a try, because I believe that the customruu performs some sort of checks. Maybe this is nonsens, but you can try it.
The battery was fully charged & it was working better than before.
I reflashed the Stock SPL to flash the carriers ROM back & that worked but at anytime it just rebooted for whatever reason to make it so the ROM was unusable at any time I would reboot it would decide to actually go past it seldom. I experienced that at one point oddly it went into setup n it did it again after a while its just acting strange.
If you're back to stock SPL and stock ROM, can't you just send it back for a warranty replacement ?
IDK how old it is. I bought it brand new from ebay.
Viper Matrix Wireless said:
IDK how old it is. I bought it brand new from ebay.
Click to expand...
Click to collapse
No warranty bro...
You can try but no warranty 9/10 times.
What ROM are you using? I used to have that issue with my betas.
It wld destroy itself after softreset and I would have to reflash.
Try to flash, turn off right after it boots, turn on and see how that works for ya.
Rep had told me I could get it replaced & they know I bought from ebay. But I havent called them on this yet.
It doesnt work. It usually doesnt go past the boot screen. Flashing does nothing to help it. Whenever it feels like it it may have to stay on for a few mins to go into setup but most of the time it will stay there & reboot, reboot, reboot, reboot each time its a different # of times & it will reset itself at anytime. Ive even had bootloader shut off on me & restart itself during flashing its a pain. I had another issue I didnt mention my device on any custom ROM when I had 0.85 olinex SPL the device would just freeze & not respond every time. Now this is a different situation. I am back of SPL 0.87 which is the default. I flashed the entire carrier ROM which 0.79 was rewritten w/ 0.87 & that was successful but its still rebooting & causing fatal problems including the black screen w/ white text.
UPDATE: I just walked into the kitchen. Somehow the device turned on by itself & now its sitting on the sense home screen. I know its not fixed but idk why it would turn itself on.
Moved as not ROM Development.
Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....
I got so frustrated I just got done calling T-Mobile Tech Support & they are going to ship me a replacement.
ultramag69 said:
Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....
Click to expand...
Click to collapse
I thought I would reply to you.
This is what started my problems is when I did a task 29 my device was acting funny afterwards. I did it again about a month later cuz I flashed way too much & it kept getting worse. But Task29 didnt help this time its what caused me to have to flash 2 different ROMs cuz the first one I flash after doesnt work.
I received the battery & it didnt do anything.
I'm still waiting on the replacement to come.
My desire keeps on rebooting when trying to turn it on, going to recovery mode, or when im updating a lot of applications on the phone.
there are times that i can enter recovery, but it is very seldom that i can enter it.
im using amonra, when i was able to enter the recovery i tried to wipe everything. but the files are still there even if i wipe them. so i tried flashing a new rom to fish the problem. after flashing the new rom successfully it goes to the lock screen and then restarts again..
the problem started after flashing my rom to leedroid which was a month ago.
what can i do?..
hope my phone isnt bricked
Try this:
Do the "CLEAR STORAGE" option in the HBOOT menu.
Enter recovery
Wipe ALL userdata
Wipe dalvik-cache
Reflash LeeDrOid ROM
That is what I did when the same thing happened to me when I flashed my first ROM (which happens to be LeeDrOid lol).
Also, try following up with this thread.
this isn't my first time flashing.
i already tried doing clear storage and problem still exists.. keeps on rebooting and can't enter recovery.
did wipe all already.. still having same problem
just finished reformatting my sd card and reflashing a new rom.. still having same problem..
senkai16 said:
this isn't my first time flashing.
i already tried doing clear storage and problem still exists.. keeps on rebooting and can't enter recovery.
did wipe all already.. still having same problem
just finished reformatting my sd card and reflashing a new rom.. still having same problem..
Click to expand...
Click to collapse
I didn't mean to offend you, I just listed the steps I took when it happened to me a while back, hoping that it would work with you.
You can un-root the device and return it to factory condition by using the official RUU, then start all over =/.
wasn't offended
yah, right now im downloading the RUU and trying to unroot.. hope it works *crosses fingers*
thanks for the help though.
No problem =).
cant run the original RUU. because i can't even go to the original screen. kept getting error saying check the cable etc..
is there any other way?.
update:
now i can't even go to recovery manager again..
tried to clear everything.. still same problem.. any ideas on how to fix this?..
any help would be very much appreciated..
thanks..
update again:
now my phone is going till the lock screen and then restarts...
update on what i am doing.
i letted my desire rest for a couple of minutes and then tried opening it again. i was able to go to the lock screen w/o restarting. but sometimes it still does
When i was able to go past the lock screen i runned the asia RUU to unroot my phone but i got an error at the end of the process. now what i do have is an HTC logo in the middle of the screen and four exclamation point inside a triangle on the corners.
any help guys?..
Hi Folks,
I was setting up my "old", rooted and S-Off Incredible for our son to play games when travelling, etc. - it's no longer registered on Verizon's network, but is fine for wireless and downloaded apps.
After charging the battery and installing about 47 app updates today (i.e., it hasn't been booted in awhile), I was tinkering around with adding some apps from Play and it suddenly rebooted. Then, it kept booting at the white HTC logo screen.
So, I pulled the battery and decided to go back to Verizon stock, using the image from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
Essentially, I booted into HBOOT, went into CWM Recovery, wiped appropriate storage, then rebooted back into HBOOT after putting the above image onto the root of my SD card. Maybe I don't need to wipe storage for a RUU, but it's habit by now.
HBOOT installed the RUU image after it prompted for a Yes/No and the Incredible booted with that old, "DROID!!" startup (gosh, didn't miss that) and showed the initial lock screen.
I pulled down the lock and started only a few seconds into phone initialization when it rebooted.
Now, it reboots as early as the HTC logo screen or gets to the lockscreen and reboots on its own after a second or two.
Seems like a boot loop, but I just installed a new RUU - so . . . I'm wondering if this is a deeper issue.
Ideas on how to go about fixing this rebooting problem are welcome, please. Is it possible that my half-completed Play install - i.e., just before it began this symptom - crunched a file system that needs to be fixed up?
Thanks,
- ooofest
Do you get any kind of errors wiping data or cache from recovery? The play install wouldn't have botched up the filesystem but the reboot could have led to corruption in /data. The cause of reboot I wouldn't know without logs. Try pulling the logcat during the boot loop which may or may not work on stock. I seem to doubt it as stock doesn't have USB debugging on by default.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Do you get any kind of errors wiping data or cache from recovery? The play install wouldn't have botched up the filesystem but the reboot could have led to corruption in /data. The cause of reboot I wouldn't know without logs. Try pulling the logcat during the boot loop which may or may not work on stock. I seem to doubt it as stock doesn't have USB debugging on by default.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi tiny4579, I had no errors wiping data or cache within CWM that were visible to me. I agree that USB debugging is not likely enabled by default.
If we assume there's a /data corruption as one angle to go with, should I try wiping and reinstalling the RUU again? I could attempt to put on a custom ROM instead, particularly one with USB debugging enabled (if that exists). HBOOT currently shows Locked and S-Off.
Thanks,
- ooofest
ooofest said:
Hi tiny4579, I had no errors wiping data or cache within CWM that were visible to me. I agree that USB debugging is not likely enabled by default.
If we assume there's a /data corruption as one angle to go with, should I try wiping and reinstalling the RUU again? I could attempt to put on a custom ROM instead, particularly one with USB debugging enabled (if that exists). HBOOT currently shows Locked and S-Off.
Thanks,
- ooofest
Click to expand...
Click to collapse
If data wipe was fine I'm not sure. To test USB debugging flash something like cm7. I think it uses an insecure boot.img meaning USB debugging aka adb should be on by default.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
If data wipe was fine I'm not sure. To test USB debugging flash something like cm7. I think it uses an insecure boot.img meaning USB debugging aka adb should be on by default.
Click to expand...
Click to collapse
Using HBOOT 0.92
Installed CWM 5.0.2 via PB31IMG.zip route
Wiped all available storage areas/paths - no errors shown
Installed cyanogenmod 7.2 from the SD card
On bootup, I saw the CM 7.2 boot screen (i.e., a circling arrow) for about one minute, then it rebooted. And rebooted. And rebooted. So, I'm back to rebooting at the HTC logo screen.
Consider me baffled - this phone was working great yesterday until after updating 47 apps (got a "low space" message at one point, started deleting apps while others were still installing) trying to install another app from Play store. Ideas, perhaps?
- ooofest
ooofest said:
Using HBOOT 0.92
Installed CWM 5.0.2 via PB31IMG.zip route
Wiped all available storage areas/paths - no errors shown
Installed cyanogenmod 7.2 from the SD card
On bootup, I saw the CM 7.2 boot screen (i.e., a circling arrow) for about one minute, then it rebooted. And rebooted. And rebooted. So, I'm back to rebooting at the HTC logo screen.
Consider me baffled - this phone was working great yesterday until after updating 47 apps (got a "low space" message at one point, started deleting apps while others were still installing) trying to install another app from Play store. Ideas, perhaps?
- ooofest
Click to expand...
Click to collapse
Phone might be dying. Does it even get past the HTC screen?
Try reinstalling the ROM.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Phone might be dying. Does it even get past the HTC screen?
Try reinstalling the ROM.
Click to expand...
Click to collapse
Yeah, it tends to get beyond the HTC logo screen after a new ROM install, but usually reboots as soon as I see the notification for "preparing internal storage".
Afterwards, it tends to reboot at varying times - sometimes at the HTC logo, other times it gets past OS startup and reboots after a few seconds.
. . .
EDIT: I just rebooted and . . . now it suddenly booted into CM and is working normally. What the heck?!
I'm not a CM person and would like to install another ROM to see what happens after that - do you think the phone EMMC is starting to go, perhaps?
- ooofest
You might want to format the internal emmc and sdcard as the reboots could be related to filesystem. Grab /proc/last_kmsg if you want me to check.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
You might want to format the internal emmc and sdcard as the reboots could be related to filesystem. Grab /proc/last_kmsg if you want me to check.
Click to expand...
Click to collapse
Thanks, I couldn't find a last_kmsg to pull, but I wiped all storage available (including emmc and sdcard), then reinstalled the latest RUU for a test.
Bootup went OK until it rebooted again soon after getting to the Gingerbread lockscreen. Oh well.
I decided to try going back to CM7 since it actually booted after a time, so reapplied CWM 5.0.2 and then started to format storage again. When trying to format /system I got a 5 vibrate error.
I've gone through various combinations of reapplying the RUU, adding CWM, trying to wipe storage, etc. and I keep hitting the 5 vibrate shutdown at various points. I couldn't wipe /system without getting the 5 vibrate issue twice, then it worked the third time, etc.
Just now, I was in CWM and merely navigating the menu to go into "mounts . . ." and it 5 vibrated again. Ow.
My suspicion above keeps coming back to me: is my hardware potentially going?
- ooofest
ooofest said:
Thanks, I couldn't find a last_kmsg to pull, but I wiped all storage available (including emmc and sdcard), then reinstalled the latest RUU for a test.
Bootup went OK until it rebooted again soon after getting to the Gingerbread lockscreen. Oh well.
I decided to try going back to CM7 since it actually booted after a time, so reapplied CWM 5.0.2 and then started to format storage again. When trying to format /system I got a 5 vibrate error.
I've gone through various combinations of reapplying the RUU, adding CWM, trying to wipe storage, etc. and I keep hitting the 5 vibrate shutdown at various points. I couldn't wipe /system without getting the 5 vibrate issue twice, then it worked the third time, etc.
Just now, I was in CWM and merely navigating the menu to go into "mounts . . ." and it 5 vibrated again. Ow.
My suspicion above keeps coming back to me: is my hardware potentially going?
- ooofest
Click to expand...
Click to collapse
Could be the battery going bad. Do you have another battery you could try? Mabey once things start loading it pulls to much power and reboots.
cmlusco said:
Could be the battery going bad. Do you have another battery you could try? Mabey once things start loading it pulls to much power and reboots.
Click to expand...
Click to collapse
Yeah, I started charging again to see if that might help, and I've been booting up with it plugged in, too.
Could a battery still be the problem, even plugged in? That is, would a short of some kind be limiting how much could be drawn from the plug?
Wish I did, but don't have another battery on hand.
- ooofest
ooofest said:
Yeah, I started charging again to see if that might help, and I've been booting up with it plugged in, too.
Could a battery still be the problem, even plugged in? That is, would a short of some kind be limiting how much could be drawn from the plug?
Wish I did, but don't have another battery on hand.
- ooofest
Click to expand...
Click to collapse
Even when plugged in the power is going thru the battery, so it could still be the problem. Just a sugestion, may have nothing to do with it at all.
cmlusco said:
Even when plugged in the power is going thru the battery, so it could still be the problem. Just a sugestion, may have nothing to do with it at all.
Click to expand...
Click to collapse
Interestingly, I let it "cool down" for a bit and charge from the wall instead of USB, then was able to wipe all storage, install CM7 and it booted up fine.
So, I let it sit for a bit longer, wiped again and installed the latest stock RUU. This time, it took longer to boot and came up fine - I now have a relatively stock (except for S-Off) Incredible, again.
From your suggestion, I'll shop for another battery and see if a new one helps to keep the sudden reboots at bay.
Thanks.
- ooofest
Hi Folks,
After working this for some days, my Droid Incredible with AMOLED display still gets into a reboot or boot-loop condition after a random amount of time of continuous use. Almost as if it heats up or something in its memory mgmt is flaky.
It can take new ROMs, recoveries, HBOOTs, radios, etc. - but, regular use just brings up the boot condition too easily, so I can't give it to my kid as a simple gaming device. I tried a new battery in case that might be the issue, but the condition still persists. Pulling the battery and waiting 10+ minutes usually allows it to work again, until the next reboot cycle starts up.
This phone is running the latest RUU and is also S-Off.
So, I'd like to give it away to the first person who requests it.
I'm not offering a trade or purchase, but if someone wants this phone to use/test/etc. with, just PM me and we can plan on a quick dropoff in NY/NJ/CT area or I'll send it to your continental USA address with both batteries and no explicit or implied warranties, guaranties, liabilities or claims of operating performance, etc.
- ooofest
Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem