Alright, i honestly have done at least 6 or 8 hours of research and trying different things to fix this problem. (specifically, my phone is a verizon xv6900)...
after flashing the NFSFAN rom, everything seemed to be fine, but i discovered once i unplug the phone from the usb cord, it waits about 20 seconds and reboots itself. it'll boot all the way back up to the today screen then itll wait another 20 seconds and reboot, looping over and over untill i plug it back into the computer.
the battery is fine, ive tried a backup battery just in case that was the issue. i've reflashed the rom twice, and tried several others also.
any ideas?
p.s. i searched the forum here for about an hour for this specific problem before i posted, so sorry if its already been posted/answered. let me know if i need to provide more information.
[mutex] said:
Alright, i honestly have done at least 6 or 8 hours of research and trying different things to fix this problem. (specifically, my phone is a verizon xv6900)...
after flashing the NFSFAN rom, everything seemed to be fine, but i discovered once i unplug the phone from the usb cord, it waits about 20 seconds and reboots itself. it'll boot all the way back up to the today screen then itll wait another 20 seconds and reboot, looping over and over untill i plug it back into the computer.
the battery is fine, ive tried a backup battery just in case that was the issue. i've reflashed the rom twice, and tried several others also.
any ideas?
p.s. i searched the forum here for about an hour for this specific problem before i posted, so sorry if its already been posted/answered. let me know if i need to provide more information.
Click to expand...
Click to collapse
If you have an Sd card in the device, take it out and see what happens.
i have tried that with all the roms i flashed. no luck.
[mutex] said:
i have tried that with all the roms i flashed. no luck.
Click to expand...
Click to collapse
Have you tried to flash back to stock?
yeah i have. the loader gets stuck at 44% every time. even with the loader from the disk.
[mutex] said:
yeah i have. the loader gets stuck at 44% every time. even with the loader from the disk.
Click to expand...
Click to collapse
Computer that you are using? (OS, architecture)
Also, one thing that could help would be to change ports. Honestly, whenever the flash stops half way as it does with you, it normally points to battery. Does it stop at 44% on any flash or only the stock?
ive only flashed with windows xp x86, but the phone will stay on on any platform/os, i.e. works on both xp, fedora, and freebsd. it'll reboot when its just plugged into the normal wall charger though.
also, it only gets stuck at%44 when flashing the stock rom. im not even sure i have the right one, i found the whole .nbp and RUU **** confusing so who knows, i mihgt not even have it right.
I believe the problem is that you unlocked with cokeman 0.41 instead of 2.31 which will make the phone reboot after it sleeps.
youre right. i re-unlocked with 2.31 and it works fine now. i guess i didnt read the directions as closely as i thought (all though i read them about 10 times ;p) thanks for your help guys.
So here's the problem, I wanted to flash the cyanogenmod rom to my wildfire, which was running the sunaabh rom. Nothing wrong with it though, just wanted to try something new. So I made a nandroid backup. All's well and I wiped clear and proceed with the flashing. After a while the installation seemed to stopped at a point, I thought it was just installing so I left it there. After a whole hour it was still stuck. So I did the stupid thing a pulled the battery out. Now when I boot the screen is black but the vibrate noise of the startup is still there (silent boot) and the buttons light up, which I'm thinking it boots up fine. The problem is that the screen is blank even when I go to the HBOOT menu. Tried flashing a RUU but the program couldn't recognise the phone. I'm stumped now.
So what should I do?
nachos011 said:
So here's the problem, I wanted to flash the cyanogenmod rom to my wildfire, which was running the sunaabh rom. Nothing wrong with it though, just wanted to try something new. So I made a nandroid backup. All's well and I wiped clear and proceed with the flashing. After a while the installation seemed to stopped at a point, I thought it was just installing so I left it there. After a whole hour it was still stuck. So I did the stupid thing a pulled the battery out. Now when I boot the screen is black but the vibrate noise of the startup is still there (silent boot) and the buttons light up, which I'm thinking it boots up fine. The problem is that the screen is blank even when I go to the HBOOT menu. Tried flashing a RUU but the program couldn't recognise the phone. I'm stumped now.
So what should I do?
Click to expand...
Click to collapse
try taking sd card out and boot into hboot
May be restoring the nandroid could help. I am not sure, but you can try.
Sent from my HTC Wildfire using Tapatalk
he can't get to the nandroid though if he can't get into recovery,
have you had any luck nachos?
Well, it seems that the screen is the problem. It took a lot of reboot and pulling battery's but finally the screen was fine. Cyanogenmod seems to run fine too. But the screen would respond really slowly when I wake it and when I power it off, I'll have to be lucky again to get the screen running again. I did the smart thing and flashed a RUU (it can detect the phone now) and sent it to the shop to get it repaired. Oh well, thanks for your help! I really appreciate it
Quite strange...I had similar issue when I first flashed my HTC Desire where the screen was just blank, but it was at the time when the Desire moved from AMOLED to SLCD and some of the flashing caused it not to work...I thought I also bricked my phone but then flashed again then worked. Created a GoldCard just in case...good luck and just be aware that some phones may require a GoldCard to flash properly.
nachos011 said:
Well, it seems that the screen is the problem. It took a lot of reboot and pulling battery's but finally the screen was fine. Cyanogenmod seems to run fine too. But the screen would respond really slowly when I wake it and when I power it off, I'll have to be lucky again to get the screen running again. I did the smart thing and flashed a RUU (it can detect the phone now) and sent it to the shop to get it repaired. Oh well, thanks for your help! I really appreciate it
Click to expand...
Click to collapse
So what you were facing was the black screen and everytime you put the battery back in and hit power it would vibrate 3 times? I am having the same problem. I was actually flashing it with this and it shut down and now I can't get it back on. But you say that after pulling the battery and replacing it numerous times it came back on?
okay i almost just bricked my hero i was playing around with different prl/radio combos again and when i flashed the 2.2.27 radio using cm witch i do all the time. first it updated the radio image succes reboot now and i did. then it went to the usual black screen with the android guy but it turned of and didnt reboot so i turned it back on and got to the splash screen then it immediately powered of again. so i tried to reboot to recovery and same thing. then i went to hboot and pressed home to get to recovery. so at this point im starting to panic a little because wouldnt have internet access on my computer without my phone,but i remembered i still had the 2.2.27 ruu on my computer and i went to fast boot usb but nothing poped up on my computer i heard the notification noise though so i tried the ruu anyway and luckily it worked! so from there my phone was able to restart normally after the ruu finished and i was able to z4 it and use rom manager to install recovery. so all is well now im just wondering if this has happened to anyone else doing a normal radio update because nothing like this has ever happened to me before and im definitely going to be more careful for now on lol.
dude you crack me up.. at least you have a computer to do all of this stuff at.. thats why i dont flash radios, i do most of what i do on phone, so near bricks put me without a phone for a while.. and i cant have that.. thankfully i havent near bricked my phone in like 6 months (knock on wood)..
yea that was a close call for sure lol.
I unsuccessfully tried to fix my friends moto Droid x after he ran out of battery while flashing a rom. What a retard.
Sent from my HERO200 using XDA App
All this just to get a better signal lmao wow real close call
®patience is a virtue©
Hi!
It's been a while when I flashed my Blade with Swedish Spring and now when I'm trying update to Elite S2, the Clockwork seems to freeze with everything I'm trying to do with it.
First I tried with the old one I had already installed -> Factory reset, nothing happens, only the orange arrow with hat pops on to the screen and about half hour later it was still the same.
Same thing happens when I'm trying to go and select zip, only the arrow comes to screen, nothing happens after that.
And even when I'm trying to reboot or turn my phone off, the arrow shows up but nothing happens. Removing the battery and turning my device on again and my old rom (SS) works like it should and every app are still on their places.
Same thing happens with the newest Clockwork which I updated today, only the color of the clockwork-menu changed from orange to blue, but not the color of the arrow.
I'm not sure should I try straight flash the new rom with Rom Manager? I'm scared that it might brick my device becouse isn't Rom Manager based on Clockwork, so if the old fashioned-way doesn't work, the Rom Manager won't either?
If you got any ideas, please share them. I'm eager to try Android 2.3
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.