Anyone having issues with reboot loop (I think) at "ANDROID" screen for the GingerSense ReMix and Uber GingerSense RCMIX ?
I think I have AMOLED DInc.
I am running .92 hboot and 3.08 recovery.
reboot loop
Just for more info, I wiped, via rom manager as well as in recovery before and after installs. It just keep flashing at "ANDROID" screen.
xktk929x said:
Just for more info, I wiped, via rom manager as well as in recovery before and after installs. It just keep flashing at "ANDROID" screen.
Click to expand...
Click to collapse
hboot .92? cwm3? flash manually through recovery?
Yup. hboot .92. CWM 3.0.8 and manual wipe and install through recovery. I had the same issue with your Uber Gingersense and Gingersense Remix.
You don't wipe after install, you're getting rid of what you just flashed. Wipe before only.
Sent from my ADR6300 using XDA App
I wiped the data, and cache. It does not wipe the OS. Not sure what you meant by it will wipe what I installed.
I'm saying if you wipe data after install that's most likely why it wont boot.
Sent from my ADR6300 using XDA App
Interesting. I tried this time without wiping data and it actually booted.
It used to be pick your poison between "HTC Incredible" screen and "ANDROID" screen. If I don't wipe after install, it gets stuck at "HTC" screen.
Thanks though. It finally booted. Let's see how it goes.
Just for future reference. If you would like to further verify what display you have, look at your hardware specs.
Menu>Settings>About Phone>Hardware Information.
Amoled= Hardware Version 0002
SLCD= Hardware Version 0003
This could be a useful headache saving piece of info for later.
Also sorry for posting this randomly but while reading your question I caught where you mentioned you thought you had Amoled.
If it happens again, try wiping again and reflashing.
Thanks all for the info. I realized wiping afterward was killing the ROMs. I thought they were like the built in OS where it's ok to wipe all the data and factory reset.
Thanks Wildstang83 for the screen info. I guess I have a slcd contrary to what I thought.
Related
My evo has gone insane. Since a few days ago it was randomly reboot fairly often. Now as of a couple hours ago it pretty much reboots as soon as it boots up.
I have re wiped everything and reflash rom (was using fresh), then i wiped and tried damage control, then i wiped and nandroided back to before problems started (from ava's 2.2 rom leak)
all 3 result in reboots galore.
Any ideas at all? should i considering a stock 2.2 rom to break root and return to sprint?
My buddy had this issue and it ended up being his GPS that was making the phone reboot overtime the phone tried to use a location service. Could be anything but a call to Sprint and he was given his MSL and walked through how to reset everything and it works like a charm now.
Sent from my EVO using XDA App
Are you overclocking at all? If you are, scale that back some.
clamknuckle said:
Are you overclocking at all? If you are, scale that back some.
Click to expand...
Click to collapse
nope. im not doing anything. it wont even run a fresh stock 2.2 rooted rom without rebooting even after full wipe/reflash
What recovery are you using, and how are you doing the wipes?
If you are using clockwork, here's what I always do when flashing a rom that requires a wipe.
I wipe from the first menu, where it says clear storage.
Then I reboot and go into recovery, wipe data from there. Then I wipe cache. Then I go into advanced and wipe dalvik cache. I've never had an issue like yours since doing that.
Maybe try that?
clamknuckle said:
What recovery are you using, and how are you doing the wipes?
If you are using clockwork, here's what I always do when flashing a rom that requires a wipe.
I wipe from the first menu, where it says clear storage.
Then I reboot and go into recovery, wipe data from there. Then I wipe cache. Then I go into advanced and wipe dalvik cache. I've never had an issue like yours since doing that.
Maybe try that?
Click to expand...
Click to collapse
Ive used both clockwork and RA in about every combination possible through every wipe method I have ever read about. Its driving me nuts nothing is working i cant even get it to boot up now before it reboots
That sounds like faulty hardware at this point.
im trying to unroot and cant even seem to get that to work. I am on hboot 79 for some reason, trying to downgrade to 76 but cant connect with abd via recovery. you normally are able to, right? I cant boot the rom to turn on debugging and abd that way..
ok, using an official RUU i get an
"error [140]: bootloader version error"
for some reason my hboot is 0.79 not 0.76
trying to flash the pre-leaked "official" 2.2 rom i get error saying no signature
trying to do step 2 of toast root over again (to get 0.76 hboot back) also is not working. I am getting "older version" error on the pc36img part
Okay, so I rooted an Incredible successfully for a friend with Unrevoked 3. Everything was going well until I tried to flash cyanogenmod. I'm getting stuck in boot on cyanogen and anything i try to do in clockwork just gives me the the rom manager logo(Orange circular arrow wearing hat) and nothing else. It will immediately return to clockwork if I push power but that's it. I've tried restoring, rebooting, flashing new Rom, etc but it just sticks at the Rom Manager logo. Any help is greatly appreciated.
Sounds like updated recovery is needed. Assumed factory reset and full wipes complete before flash?
Which versions of CM & CWM?
Sent from my ADR6300 using XDA Premium App
I wiped data, cache, dalvik and battery stats in Recovery before flashing Cyanogen. It has the latest version of Clockwork.
Edit: I just tried to factory reset from Hboot, but it gets into Clockwork and says "E: Invalid command argument"
Some of the newest CW have a wipe bug. Try updating to the newest one or a version 2.x.x.
Sent from my Incredible using Tapatalk
linuxmotion said:
Some of the newest CW have a wipe bug. Try updating to the newest one or a version 2.x.x.
Sent from my Incredible using Tapatalk
Click to expand...
Click to collapse
Edit: Crisis averted. Turns out I'm ****ing stupid. The power button on this phone doesn't select **** in Clockwork like my phone. Reflashed and it booted up. Feel free to point and laugh; I deserve it.
I just flashed a fresh cm7 rc4, along with gapps, and zendroid kernel (avs i think i'm not sure which one).
Things were working great. I was using the phone, had just installed widget locker, and then tried to plug my phone into the computer.
Thats when the trouble started. For some reason, usb debugging worked, even the wireless tether worked, but I could not get the sd card to be on the computer, the option just never came up.
To fix the problem, I tried resetting the phone, but when I did so the phone became stufk on the cm7 boot animation for a few hours. What do I do?
I would just do a fresh install, but this is actually the third time that I have gotten stuck on the bootloading screen with cm7, so I just need to find a solution. Please help.
-AJ
Really need some help with this, guys...need my phone back
You're not alone. I installed GApps along with CM7. Stuck in Boot animation. My wife is pissed.
You posted in the wrong section. I will transfer this over to the EVO Q&A area.
I am assuming that you have your EVO rooted. If you are stuck in a bootloop, simply pull your battery, put it back in and press the power button while holding Vol Down. This will make you go into bootloader. From there, simply go into recovery, wipe everything, and reflash the rom. I have done CM7 and gapps and have no issue.
egzthunder1 said:
You posted in the wrong section. I will transfer this over to the EVO Q&A area.
I am assuming that you have your EVO rooted. If you are stuck in a bootloop, simply pull your battery, put it back in and press the power button while holding Vol Down. This will make you go into bootloader. From there, simply go into recovery, wipe everything, and reflash the rom. I have done CM7 and gapps and have no issue.
Click to expand...
Click to collapse
I did that, many times. One time, it just worked. Didn't do anything different as far as I know, but kind of makes me unsure about future flashes etc.
Pull your battery out, wipe data, cache, and dalvik cache in recovery. Flash ONLY CM7 and the google apps. I think the kernel might be the problem for the bootloop.
harryprk2x said:
Pull your battery out, wipe data, cache, and dalvik cache in recovery. Flash ONLY CM7 and the google apps. I think the kernel might be the problem for the bootloop.
Click to expand...
Click to collapse
I never wipe any of those things seperately, I just use calkulin's format all. That couldn't be the source of any problems right?? I mean, I always believed that that was the best way.
Thanks. I ended up doing that. All is better now.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
My problem was installing both at the same time.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
thenimboo said:
I never wipe any of those things seperately, I just use calkulin's format all. That couldn't be the source of any problems right?? I mean, I always believed that that was the best way.
Click to expand...
Click to collapse
I've used Caulkin's format all twice, and both times, I got stuck in the white screen boot loop and had to reflash Amon Ra, just to get back to recovery and flash one of my nandroids.
Wiping everything in recovery works perfectly fine for me.
I use Calk's format all at least a few times a week, sometimes a couple times a day. Always works fine.
Did you wipe?
Did you wipe the data/cache from the handset? if not do so through clockwork
I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?
it is salvage mod 1.2.1.
JerenOtt said:
I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?
Click to expand...
Click to collapse
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.
I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?
JerenOtt said:
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.
Click to expand...
Click to collapse
No problem man. It will boot up after a doing a full wipe, most likely.
JerenOtt said:
I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?
Click to expand...
Click to collapse
Can you boot into the bootloader? Power off your device. Simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text should scroll across the screen and then you will see a few options. One of the options will be recovery. Anyway, at the top of the screen, you should see either S-ON or S-OFF. Hopefully, it displays S-OFF. Anyway, select recovery from the set of options and then, as k2buckley has instructed, go to the wipe menu and wipe EVERYTHING except the SD card itself. When you're done, do not reboot. Go to the flash menu and flash the rom you want to flash. Do not flash the gapps zip yet. Reboot after flashing the rom. I want to make sure you're able to boot into the homescreen. If you're successful, reboot into recovery, wipe cache & dalvik and then flash the gapps.zip. afterwards, reboot. When you're all setup, go back I to recovery and make a nandroid backup.
posting & replying via the XDA Premium app.
also, make sure you got the full ROM, not just the patch for going from 1.2 to 1.2.1. I did that
I was having similar issues, mine went into a boot loop about twice before getting hung up at the initial setup with FCs. I was coming from CM7 Nightly 41 that was acting weird with FC's, I always double wipe cache/dalvik/factory reset. I thought that I might have had a bad download so I re-downloaded, wiped and flashed. I couldn't get past the initial setup so I went back to Ultimate Droid and have been running that for the last 4 days or so with out any major problems except for the Facebook update dicking things up and one random reboot that I had today... I really want to give Salvagemod a shot though since it's Evo-centric.
still not working for me
hey guys... i been trying to boot into salvage mod for the past 2 days... i get it to install just fine i do get the salvage screen up too...
then when the rom is supposed to be loaded up i get the Android dude with emergency call and a crash u keep pressing ok then it goes away and comes back right away... i just wiped everything again and reflashed it and now i am stuck with salvage screen re looping..
any help would be appreciated
thanks
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3? (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Glad you got him going Doug. I had asked him to use RA in a PM, and he responded that he liked clockwork and rom manager better, and wouldn't use RA, lol. I'm glad you convinced him otherwise.
Sent from my PC36100 using XDA App
lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.
dougjamal said:
lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Thank you Doug, happy Easter to you as well.
Sent from my PC36100 using XDA App
dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks
Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App
k2buckley said:
Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yup did everything... weird but i got it working now..did everything the same way as b4...its really sweet.. and really fast... thanks a bunch for the help
nxtstep said:
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks
Click to expand...
Click to collapse
You're very welcome, my friend. I'm glad I was able to help. Take care and have a great day....
posting & replying via the XDA Premium app.
k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
You're a genius. I was doing a data/factory reset, cache, and dalvik, but not boot and system. When i did those, it worked. Thanks!
everytime i try to boot any of the gingersense roms it freezes at the htc start up screen i do a battery pull and it does the same thing. Ive wiped evrything and it still occurs.
Same here. I think it is tied to the CWM & HBOOT versions on the device. Believe those require at least the 3.x CWM, idk for certain about the HBOOT. Mine aren't the latest, and those Roms don't boot for me either.
Sent from my ADR6300 using XDA Premium App
Pretty sure your hboot needs to be the latest (.92). Easy to update in bootloader.
Sent from my ADR6300 using XDA App
gingersense remix b4 did hang at the white htc screen for a long time when i installed it tonight i eventually got it to go past that point by re wiping everything and re installing the rom in cwm
how do you update the bootloader?
Go to www.dougpiston.com for the files, just download the zip, put it on your SD, and flash in bootloader (reboot holding power and volume down).
Sent from my ADR6300 using XDA App
I have hboot .92 along with the latest radio and CWM 3.0.0.7 as suggested for AMOLED screen and my phone still hangs at the white screen. Any ideas?
AJGO23 said:
I have hboot .92 along with the latest radio and CWM 3.0.0.7 as suggested for AMOLED screen and my phone still hangs at the white screen. Any ideas?
Click to expand...
Click to collapse
Cwm 2.5.1.2 works flawlessly for me.
WWW.dougpiston.com for that version.
AJGO23 said:
I have hboot .92 along with the latest radio and CWM 3.0.0.7 as suggested for AMOLED screen and my phone still hangs at the white screen. Any ideas?
Click to expand...
Click to collapse
Are you doing a full wipe before installing the rom? I'd recommend going into recovery and doing wipe data/factory reset, wipe cache, wipe dalvik cache, (mounts and storage) format system, format boot, format data, format cache. Then install zip from SD.
Sent from my ADR6300 using XDA App