Database Info

miui and CM7 keeps cycling the inital loading

hi all,
Ok, I'm new to this stuff.
1. used the simple root and it worked great.
2. I then flashed CM7 and it worked great except market was not on it.
3. I downloaded and flashed gapps-hdpi-20101114-signed.zip by mistake, not realizing I had to use another gapps.
4. After I flashed it, the cm7 and android setup screens kept cycling between each other.
5. I restored to clockworkmod (sp) and then deleted the gapps and tried to then flash cm7. It didn't cycle between cm7 and android setup, but the cm7 screens kept cycling and never got past that.
6. I thought perhaps it was just cm7 now, so I tried miui and it's doing the same thing. It's cycling between the gingerbread man and MIUI with the status bar and won't do anything else.
Very frustrated. what have I done and how do I fix it?
Thanks folks,
Brett

I believe that those ROMs both require ENG S-OFF. Open simple root on your computer, click Fixes, then apply the fix there. Also, did you make sure you cleared your Dalvik cache before flashing? Always do a factory reset AND clear dalvik cache when changing ROMs.

make sure you have wifi off in your first boot

ardynine said:
make sure you have wifi off in your first boot
Click to expand...
Click to collapse
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards

EtherealRemnant said:
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
Click to expand...
Click to collapse
Thanks ER. I'll try your method this evening.
I'll report back.
thanks!
brett

EtherealRemnant said:
I believe that those ROMs both require ENG S-OFF.
Click to expand...
Click to collapse
I can say with no doubt whatsoever, no.

id10terrordfw said:
I can say with no doubt whatsoever, no.
Click to expand...
Click to collapse
any suggestions then???????

I tried doing the ENG-off and still the same hang up on the front screen.
Any help please?
thanks,
brett

what method do you use to flash cm7? what exactly do you do.
to clarify what is your exact process for flashing the rom?

mudknot2005 said:
what method do you use to flash cm7? what exactly do you do.
Click to expand...
Click to collapse
Hi. Thanks.
I use rom manager to boot to recovery. Then I install zip from sd card. I go through the process until it says reboot. It's when I reboot that I get stuck in the bootloop. It just cycles from the CM7 circular arrow to blank and then to the arrow thing again. MIUI does the same between the gingerbread guy and the status bar and back.
I then take the battery out, take out the sdcard, down volume & power, reinsert sdcard and do a restore so I can use my phone again in clockworkmod 3.0.0.6.
thanks,
brett

sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..

mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett

bdws1975 said:
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
Click to expand...
Click to collapse
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.

EtherealRemnant said:
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
Click to expand...
Click to collapse
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett

mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.

bdws1975 said:
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
Click to expand...
Click to collapse
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.

EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
I'll give it a shot and then get back to you.
I do believe, however, that the restore I'm doing is the backup I did right before I did the original cm7 flash. I'll try.
thanks!

If you toggle wifi on after the first boot it goes into a bootloop. This is a know bug not a hunch.

EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
DUDE!!!! You freaking rock. I got it!
I installed MIUI and it's amazing. Thank you very much.
Brett

Mustang302LX said:
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
Click to expand...
Click to collapse
thank you!!!!! I really appreciate your help!

Transformer stuck in constant boot loop

I'm not sure what happened to my tablet. I really can't seem to figure it out. I was using it last night before I went to sleep, and I just closed it away (I have the keyboard dock), and packed it in the case this morning for work. When I took it out to use it at work it had already been stuck in a boot loop. I have wiped, and reinstalled 3 different roms on it since. It's still doing the same thing. Is there anything else I can do? What could have caused this?

I know that you've tried to flash several ROMs, but please check if you've done all the steps described below:
Copy ROM to /sdcard
Reboot in recovery
Wipe /system, /cache and dalvik-cache
Install ROM
Reboot and see if it works
If not, you might also want to delete /data, but make sure you backup it first (you can do that with a nandroid) and use /external_sd to store the ROM (just in case).

You can also try restoring your nandroid backup.

VibrantWind said:
You can also try restoring your nandroid backup.
Click to expand...
Click to collapse
I have tried both. When I flashed the original backup back onto the tablet I got the same result. I have completely wiped all data as far as I know. I even went a step further and formatted my sd card to ensure none of the ROM files were corrupt, then placed them back on the card. Is there even more data I can delete other than the system wipe/cache/dalvic cache?

wipe staging
wipe battery stats
ummmmm yeah those are the only 2 not listed and are not all that usefull to you
Do you have nvflash ? If so i would do a complete wipe ie format everything even recovery etc then flash a nvflash rom then restore my nandroid if i knew the integrity of it was good
Sent from my Transformer TF101 using xda premium

theres a Super wipe I use in mikes Android Revolution HD thread..
I have used this before to fix a few problems I was having..
Check "how to flash" section for it
http://forum.xda-developers.com/showthread.php?t=1245892

I had the same thing happen to me. Just boot loop out of the blue. It was sitting at home charging, came home to it boot looping.
I tried re-flashing the rom I was on (prime) and flashing other roms and nothing worked.
I had to use the super-wipe script to get it working.

fone_fanatic said:
I had the same thing happen to me. Just boot loop out of the blue. It was sitting at home charging, came home to it boot looping.
I tried re-flashing the rom I was on (prime) and flashing other roms and nothing worked.
I had to use the super-wipe script to get it working.
Click to expand...
Click to collapse
I have tried the Revolutionary Rom, and after it wipes and installs, and reboots it just says at the Asus eEE screen. What on earth could I have possibly done? Is the super wipe something that can be manually done, or does this only occur while installing the rom?

Holy Canoli, I think I may have forgot one step.....one second..."tinkering"...
Edit: update, I'm not going to tell anyone what I forgot to do after the super wipe (which is a godsend), but alas, my Transformer is functional again. Thanks guys!

MrAutomatic said:
Holy Canoli, I think I may have forgot one step.....one second..."tinkering"...
Edit: update, I'm not going to tell anyone what I forgot to do after the super wipe (which is a godsend), but alas, my Transformer is functional again. Thanks guys!
Click to expand...
Click to collapse
Let me guess... You flashed super-wipe, but didn't install any ROM after...

Don't worry, we're here to help, not judge!
AzureusPT said:
Let me guess... You flashed super-wipe, but didn't install any ROM after...
Click to expand...
Click to collapse
My bet is on that as well! haha
Not going to lie.. I've done that before.

[Q] CM9 Install

So Ive been using EOS for a while, but was ready to hop onto the CM9 train as it was looking stable enough from what I had been reading.....
So I boot into recovery, wipe date, cache, and dalvik, and proceed to flash the latest CM9 cm-9-20120521-NIGHTLY-stingray (ive tried 3 different builds) ....
Everything goes fine. Flash Gapss and reboot. All good. Let it sit for 10 minutes, then connect to wifi and set up my google account. As soon as thats done I reboot.....and thats the end of it. It will boot loop every time. But ONLY on second boot. Ive tried changing recoveries...same result..... GO back, flash latest EOS, and everything is working fine...
Am I missing something because this is driving me crazy??
Thanks.

try this - after clearing caches and wiping data - install cm9 as normal - once this is done run the fix permissions option inside cwm and reboot
let us know if this worked - good luck

daley stephenson said:
try this - after clearing caches and wiping data - install cm9 as normal - once this is done run the fix permissions option inside cwm and reboot
let us know if this worked - good luck
Click to expand...
Click to collapse
OK im gonna try this. Thanks
Ive used rogue and EOX rcovery and same result, should I try CWM or does it matter?

sactownsav said:
OK im gonna try this. Thanks
Ive used rogue and EOX rcovery and same result, should I try CWM or does it matter?
Click to expand...
Click to collapse
i recommend using the latest rogue recovery found here http://goo.gl/OW1k4 - good luck

CM10 Alpha 3 Problem?

Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!

Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
Click to expand...
Click to collapse
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.

Phizban said:
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Click to expand...
Click to collapse
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.

Droid111 said:
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Click to expand...
Click to collapse
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.

mjwhirly said:
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
Click to expand...
Click to collapse
Thanks for the help. I'm going to try it within the next few days. Right now I have SKY-ICS going fine but I'll definitely try that.
What do the different kernels do?

Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Click to expand...
Click to collapse
I used TWRP and flashed over CM9 with no problems. Did it as an upgrade. Wipe system> install CM10> install gapps> Wipe cache
Several people have reported that TWRP worked for them.

[Q] ViperOneS 2.2.0 OTA

Hey guys, since my post count is too low to post my problems with this OTA update in the development section of this rom, ill do it here. Sorry for that.
I think im having no problems with flashing the 2.1. ROM yet but i have my concerns if i did that right.
First problem with flashing it, is the question if im having a custom kernel. I flashed ViperOneS a several times but made a fullwipe before.
So am i having a custom kernel or not?
Next issue is that im only able to flash this ROM with CWM. TWRP 2.5 doesnt work and even 2.3.3.0, which should work, but does not for me...
Well with CWM i ll do it that way:
1. Doing Fullwipe in CWM (Factory reset, Wipe Cache, Wipe Dalvik and System).
2. Flashing the ROM and choosing HTC Theme > Custom Kernel? > not sure sometimes "yes" sometimes "no".
3. Flash finished? > asks me if i want to reboot (into system) or save the logs. Since the instruction tells me to flash the boot.img first before rebooting...
4. ... im going into bootloader via adb which works
5. flash the boot.img
6. fastboot erase cache
7. reboot system
8. before doing the first setup i go into recovery and wipe cache.
I think 2.1 works but i want to be sure if i did everything right, especially with the custom kernel question and that i reboot into bootloader right after aroma says that the flash is finished.
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
The problem is that they dont keep their instructions up-to-date (+ how to flash the OTA... right)
It looks to my like there are 100 different ways to flash 2.1.0 and 2.2.0 and only 1 is the right way which lets the ROM being amazing...
Hope you can help me. Thanks in advance!

turnschuh said:
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
Click to expand...
Click to collapse
All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
What EXACTLY doesn't work with TWRP 2.3.3.0?

All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
Click to expand...
Click to collapse
yea i did it like that. i just flashed it in the recovery, but im not sure if i have to wipe caches after or before doing that.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
Click to expand...
Click to collapse
about finding such "tricks": the problem is that those ROM release threads have tons of post (500+ sites of them) and it seems like 90% are from people who didnt even flash the ROM... i think you ll excuse me if i say i got tired of searching for my problems there^^
well can u tell me which skin i have to change? on venom tweaks or the htc skin on personalization? and app settings > venom tweaks > wipe cache and data right?
What EXACTLY doesn't work with TWRP 2.3.3.0?
Click to expand...
Click to collapse
when i flash it with 2.3.3.0 (or 2.5... its the same), the flash process doesnt even take up to 2 seconds and it says its finished and that causes a bootloop but doesnt make me wonder.
dont you have problems with TWRP flashing sense roms either?
ah and another one: did i flash the version 2.1 right and what about the custom kernel question?
well thanks for ur time.
edit: well this time flashing with twrp 2.3.3.0 worked somehow, but i choosed flashing without wipe (made it in recovery) and not to delete apps with aroma installer (which i did before)... just strange.

new problem. dont know whats wrong with my phone but:
wanted to make a backup of my ViperOneS 2.1 with TWRP 2.3.3.0 after lets say 70% of progress it starts turning off my phone and restarts into system. i flashed 2.5.0.0 but its the same issue (edit#1: with CWM too...). strange is that TWRP turned out my phone before when i wiped something there.
i think somethings really messed up atm...
edit#2: had to run a ruu over the system again, flashed twrp and backups seem work again..strange ****