Related
My wireless tether app for root users wasn't working (kept force closing) so I decided to just reflash the ROM I was then using (RegawMod). So, I downloaded it from xda, put it on my SD, flashed it, and everything was going well. I booted the phone up for the first time after I flashed it and I wouldn't boot, only cycle through the boot screen (the boot screen would appear, stay for a good ten minutes, then go black, and the boot screen would appear again..). So, I nandroided back to my stock 1.5, and that booted up just fine. I decided to try another ROM (DamageControl). I downloaded it, put it on my SD, flashed it, and again everything went well, but same problem, it will not get past the boot screen, just keeps cycling the boot screen over and over again..
So..what's wrong here? Can anyone help?
In the recovery go into wipe and click on every option in that menu.
Re: So I Think I Have A Problem...
did you wipe SD ext.
centran said:
In the recovery go into wipe and click on every option in that menu.
Click to expand...
Click to collapse
Did it. Lets see what happens..
EDIT: Good work, it booted up now!! Thanks guys, gotta love these forums!
Guys please I know this is the wrong forum but no one is answering help. At all. Alright, I went to flash the ICS Sense alpha, and needed to restore a backup. I went into hboot, and restored the PD98IMG.zip. Afterwards it said "Press power to reboot" so i did. The phone turned off, and now nothing. After a LONG time the phone turned on to the White HTC Splash and vibrated CONSTANTLY, until the battery was pulled. I tried volume down + power but nothing. Except for the occasional white screen, nothing. Please, anyone/.
You're bricked
Sent from my Desire HD using telepathy...
I think your phone had a bootloop. Did you already installed custom recovery? Can you enter it through fastboot menu (vol down + power)?
I doubt he's bricked,why are you restoring that zip? You restore your back up....from clockwork?
Sent from my Desire HD using XDA Premium App
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
HTC_Phone said:
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
Click to expand...
Click to collapse
I am confused. So what exactly happens when doing this:
remove or rename the PD98IMG on the sd card
pull the battery from the DHD
re-enter it and hold volume down and power until the hboot starts
navigate by volume down/up to Recovery and press POWER
If you had to restore back to factory, why bother flashing ICS?
You should get away by installing one of the RUU using PC. here is a guide on how to install RUU and you'll have to search this section to find a RUU or google it.
Though firstly i would ask you if you can go into the recovery mode anyhow since you're saying that your phone can get the HTC logo. For that, hold down POWER + volume DOWN key to get you into hboot (IF YOU CAN) and choose recovery from there, once in recovery, go to option where you wipe your data + cache, wipe both of em and try restarting again...If you can't even get into recovery then do the RUU way of getting the rom working.
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Lol least its on
Sent from my Desire HD using XDA Premium App
HTC_Phone said:
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Click to expand...
Click to collapse
Gratz, suppose this thread's unnecessary now?
Anyway take care of what you do: always do a nandroid backup prior to flashing everything. Better spend 5min for backup than 5 days without a phone.
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Also spamming the threads is a pretty good way of getting banned. Maybe zel or Andy will be nice about it
marsdta said:
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Click to expand...
Click to collapse
That sounds somewhat correct. I DID get it replaced, but had a GB PD98 on the SD card. Anyway, it vibrated for quite some time, and eventually the vibration stopped. So I let the phone sit as I figured out some way to salvage the phone. And the the next HTC splash booted, and the phone proceeded into the stock ROM. Idk what happened, but I'm not complaining.
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
HTC_Phone said:
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
Click to expand...
Click to collapse
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
motherninja said:
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
Click to expand...
Click to collapse
The phone itself is already rooted, but I tried booting into CWM, and it did the same thing as it did before. So I have to run the RUU, and then S on the phone, and run the hack kit again. I already ran the RUU once, and nothing.
Probably best just to start over and do everything again,even if you've already done it,maybe the root didnt work?
Your phones a nightmare mate
Sent from my Desire HD using XDA Premium App
So you intentionally created a thread in the wrong section?
I guess the rules don't apply to you then.
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Ok, I just started experiencing an issue. I suddenly can't get into recovery. Here is a little back history. My N7 was running CNA 3.6.6 (I know, but...), and I was bored so I decided to try ParanoidAndroid. Well, I have that gotta try something else feeling again, and when I try to get into recovery, it will go to the google screen, then go black for about 10 seconds, then go back to the Google screen and boot up. This happens if I reboot to recovery through the power menu, or getting into recovery from the bootloader. I even tried Quick Boot, in hopes it had some magic I didn't. No luck. The same crap. I even switched from TWRP to clockwork recoveries, and the same crap happens (I tried the same things I did originally).
Also tried through other apps too, like Rom Manager, Rom Toolbox, and TiBu. Everything works, but I am bored with this rom... I have tried turning it off, plugging the N7 into a PC and trying to get into recovery. Again, I can get into the bootloader, but as soon as I select recovery, it goes black, then fully reboots...
Anyone have any ideas? Any help would be greatly appreciated.
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
BillGoss said:
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
MetalWych said:
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
Click to expand...
Click to collapse
Scheiße, I reflashed TWRP in fastboot, and I am getting the same result. I think my N7 forgot it has a recovery!? I will try flashing clockwork through fastboot and see if this works. Thanks for your help...
Edit: Clockwork does not help. There is no recovery for me. I am now at a loss. Hopefully someone will have some suggestions...
Finally got my recovery back...damn latest bootloader!
Yeah, this has sucked. I have spent several hours figuring out what the hell went wrong. It turns out its the latest bootloader. Others are having this issue. So, I had to go back to stock (which will erase EVERYTHING) and then had to re-root. Now that my bootloader is back to JRO03D, I am back up and running.
So, the first time I did this route, I decided to take the update and re-root my N7, and ran into the same issue. I could not get into recovery. So, I had to do it all over, this time not taking the update and not updating the bootloaders, and I am now back and already have a ROM running and everything installed.
If you want to go this route, here are a couple of links that will help...
http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764328 and go to the Back To Stock section. The next part is for rooting (if you wish to do this yourself)...
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
I will post this in case anyone has a need for this info...
Unable to get into Recovery after 4.1.2 upgrade... - xda-developers
Any help?
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
scythefwd said:
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
Click to expand...
Click to collapse
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
lj50036 said:
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
Click to expand...
Click to collapse
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
scythefwd said:
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
Click to expand...
Click to collapse
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
charesa39 said:
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
Click to expand...
Click to collapse
Like hit them and let go, or till it reboots again?
scythefwd said:
Like hit them and let go, or till it reboots again?
Click to expand...
Click to collapse
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
charesa39 said:
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
Click to expand...
Click to collapse
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
scythefwd said:
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
Click to expand...
Click to collapse
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
charesa39 said:
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
Click to expand...
Click to collapse
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
scythefwd said:
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
Click to expand...
Click to collapse
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
charesa39 said:
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
scythefwd said:
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
Click to expand...
Click to collapse
Thx for taking the time to learn mate, Let us know when you get it back
Thx Josh