Develop Bugs

Is it bricked? UnSolved AGAIN!

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?

samsung galaxy nexus wont unlock

Hi I have this problem my samsung galaxy nexus wont unlock. The phone worked fine 10 minuts ago then clicked the power bottom to unlock but it just stays black screen
and i have to pull out the battery and turn it on aging and there is 75% battery left so that's not the problem

after a hard reboot with pulling out the battery, you still can't unlock your phone?

fine
after a battery pullout i will unlock fine but it's just thet some times theres is no response when i click the power bottum to get to the unlock screen and the only option is to pull out the battery

is your phone rooted? if so, go to cwm, backup, and flash a clean rom. Then if it works, try restoring from ur backup

Not rooted
The phone is not rooted and totaly like origina. I tried to root the phone but it dient worked beacuse the fastboot driver wuldent install so no change at the phone it think but culd it be that, that is causing the problem

same here
I had the same problem once three weeks ago. The Gal N would just not respond to the power button. I had to pull the battery AND the SIM card. It has never happened again since then.
All stock phone, no root, no unlocked bootloader

Sounds like 'sleep of death', there's a thread on it - eta here:
http://forum.xda-developers.com/showthread.php?t=1360880
It seemed to be some app stopping the phone waking up, for some ? lightflow, others ? juice defender. I stopped following the thread so I don't know if a definitive fix was found.
You could try a factory reset and see if that fixes it...

[Q] rebooting to home screen then turning off

After rooting my htc one X and flashing the Viper X rom in it, i had some problems rebooting my phone when the battery is lower than 20%.
I restored my official rom back Android 4.1.1 sense version 4+ (that i have recovered from CWM) but i'm still facing the same issue after my battery drops down to 20% sometimes the phone turns off by itself or if im playing a game and some other times if I reboot it (when the battery is below 20%) it starts to the home screen when it say preparing SIM card it turns off. I removed the SIM card and turned it on it started to the home screen and everything went ok but after installing the SIM card it shuts down immediately!
Is there anyways to fix this problem?
Is it a software or a hardware malfunction ?

alaa_kibbi said:
After rooting my htc one X and flashing the Viper X rom in it, i had some problems rebooting my phone when the battery is lower than 20%.
I restored my official rom back Android 4.1.1 sense version 4+ (that i have recovered from CWM) but i'm still facing the same issue after my battery drops down to 20% sometimes the phone turns off by itself or if im playing a game and some other times if I reboot it (when the battery is below 20%) it starts to the home screen when it say preparing SIM card it turns off. I removed the SIM card and turned it on it started to the home screen and everything went ok but after installing the SIM card it shuts down immediately!
Is there anyways to fix this problem?
Is it a software or a hardware malfunction ?
Click to expand...
Click to collapse
i think u should flash correct boot.img.

pa4mpp said:
i think u should flash correct boot.img.
Click to expand...
Click to collapse
I did Flash the original endeavoru Boot.img this only happens sometimes not always but when it does it does not boot properly until i recharge it for 4-5 mins then everything goes normal.

Hi, how did you solve the problem??? I have same problem

Boot Problem
Did you solve this problem? How? I have the same issue..

Same issue
Did you solve it?? If yes please tell how?

D855 not working

Hey,
my phone is not turning on,not entering recovery mode, not entering download mode, not entering the hard reset mode, not recognised by the PC and not charging.
2 months ago i reached my phone and he had "black screen". took the battery out,turned the device on and he got black screen again. took the battery out again but it back in and turned on the device again, entered the menu and it got stuck. took the battery out and in,turned the device on and it happened again.
I wanted to reach the settings menu to restore the phone but couldnt get to it because the phone froze. so i decided to perform a hard reset.
I did this, the screen was black for 10 minutes (could see it is turned on), the the android logo was on the screen with a loading bar,and then the screen went off. waited another 15 minutes and tried to turn it on,and it did not respond.
what can i do to make it work?

Did you make any software modifications to it prior to the problem occuring

itsbighead said:
Did you make any software modifications to it prior to the problem occuring
Click to expand...
Click to collapse
did nothing.
I tried to update to 5.0 but with not success (pc suite and from the phone updater)
forgot to mention, i took it to a lab and they told me its a flash component

anyone?

AirM said:
anyone?
Click to expand...
Click to collapse
I had the same problem, with black screen, but mine showed LG logo bootloop, tried everything, without success, I send it to a service, waited almost two months, they said dead mmc and replaced motherboard under warranty. Hope you will resolve this...

Need Help Bootloop on LG G7

Hello, I have the LG G7 thinq. The Device is on Bootloop but I don’t know why!! It starts again and again. It comes to the Red LG Logo and than It boots again. Please Help

zzman31 said:
Hello, I have the LG G7 thinq. The Device is on Bootloop but I don’t know why!! It starts again and again. It comes to the Red LG Logo and than It boots again. Please Help
Click to expand...
Click to collapse
Please describe what happened prior to this before you start a whole big riot again.

Hello, I have this problem well. It started 8 hours ago. I was using it normally, no root or anything. And suddenly when I take it out of the pocket, it just keeps restarting.
I'd like to recover all my data before hard reset. Any help please?
Couldn't even turn it off, I had to wait until battery died.

Hello, same problem here. 2 hours ago I received a WhatsApp message and suddenly it restarts again and again.

Me too! But after two factory restarts I found the problem I guess.
For me, it occured twice when I started Airplane mode and after that everything went to...
Now I am affraid to start airplane mode again
What ROM and version are you guys??
V10f-EUR-XX

My version is V10k-EUR-XX.
After 2 factory resets it looks like my SIM card is the problem.
Without card the phone starts... But in my old LG G6 the SIM card works well.

I tried it with and without SIM as well, but it behaved the same. Sometimes I got into the system, but it just got stuck right away and bootlooped again.
But weird, because for me its airplane mode, which disables/enables celular, so SIM again.
I got T-Mobile, you?

I got t-mobile, too.

So lets wait for stormeye25, I wonder if he also has t-mob

Airplane mode is working well. Without a SIM ...

I am working with SIM. Only when I switch airplane on it stucks again. First time it was me turning airplane off, second time turning it on. Always with SIM and working celular

I tried without sim. Same problem. Also sometimes it boots up, but freezes after 2 seconds. I have the Europe version

I have same problem and i dont know what to do. Problem start about 5 hours ago (what i know last working time was 2:00AM CET). Itself reboot in boot screen or immediately on screen lock after start. I did factory reset, it work for few minutes and again. Version G710EM DEC (germany open market) last FW

It's something from lg ?
Update gone wrong maybe

Exact same problem on my G7 Thinq. Started about 8 hours ago. Boot loop, managed to get it in factory reset mode. Did nothing. Managed to reset it again (without the SIM in) then it booted. After reset it does not recognize (any) SIM. Called Tmobile to ask some questions about repair-process, they told me I was the 3th today with this problem. At this point I wish I wrote down my Google's 2FA recover keys :'). Can't access anything at the moment.

Same bootloop here, g7 thinq bought in Hungary Unlocked, but it downloaded the local t-mobile branding.
It was untouched on charger. When I wanted to pick it up it was already bootlooping and hot.
Put it into freezer, it booted, wallpaper lockscreen arrived, but nothing more.. it was stuck and started bootlooping again after like 30 secs.
Any info / resolution you have?

Okay so it happened again for me with not changing airplane mode or anything. Now I will try without SIM card. I will try to get into touch with our corporate t-mobile associate... Can we pinpoint if its t-mob (SIM) or something to do with LG?

Same here, G7 bought through TMobile Netherlands. I had turned it on airplane mode before going to bed, and when I tried to put airplane mode off it got stuck.
I'm waiting for the battery to die so I can try to wipe the cache...

Flash back to V10F did not help. More accurately until I insert sim (T-mobile) it looks like it works, after inserting sim freezes and resumes bootloop

Okay, out of the blue when in my pocket I noticed my phone was very hot and appeared, also without warning, stuck in a boot loop. Also on T-mobile...I had no problems before.
***Edit*** For the record I run a stock phone/firmware that I have never tempered with...