i installed cm7 on my touchpad last week and everything went fine. so i tried to install it on my friends 32 gb touchpad and i get stuck in a bootloop. moboot seemed to install fine becuase i have the boot menu working, cwm works, but when i try to load cm7 i get the green pic that says cyanogenmod loading but after that it goes back to the hp logo and starts over. i can boot into webos just fine but cm7 gives me the run around. ive tried doing a factory reset, wiping the cache and dalvik cache from cwm but nothing. i even tried making a nandroid backup from my 32 gb touchpad and tried to copy that to my friends touchpad but i got an error in the restoring process. ive also tried reinstalling the zip through cwm and through the acmeinstaller. do i have to doctor it and try again? has anyone run into this problem?
the noan said:
i installed cm7 on my touchpad last week and everything went fine. so i tried to install it on my friends 32 gb touchpad and i get stuck in a bootloop. moboot seemed to install fine becuase i have the boot menu working, cwm works, but when i try to load cm7 i get the green pic that says cyanogenmod loading but after that it goes back to the hp logo and starts over. i can boot into webos just fine but cm7 gives me the run around. ive tried doing a factory reset, wiping the cache and dalvik cache from cwm but nothing. i even tried making a nandroid backup from my 32 gb touchpad and tried to copy that to my friends touchpad but i got an error in the restoring process. ive also tried reinstalling the zip through cwm and through the acmeinstaller. do i have to doctor it and try again? has anyone run into this problem?
Click to expand...
Click to collapse
have you tried reflashing cm7.1 from cwm recovery? i am not sure the cminstall folder is accessible from cwm recovery, if not, try mounting usb storage in cwm recoevery, copy the fulofbugs.zip cm file and reflash. if this doesn't work, try reflashing using acme installer again.
krarvind said:
have you tried reflashing cm7.1 from cwm recovery? i am not sure the cminstall folder is accessible from cwm recovery, if not, try mounting usb storage in cwm recoevery, copy the fulofbugs.zip cm file and reflash. if this doesn't work, try reflashing using acme installer again.
Click to expand...
Click to collapse
Yes I have tried reflashing with cwm but I got the same loop. I have tried the acme installer a.couple times now but I get the same outcome
Sent from my PC36100 using xda premium
Use HP doctor and start from scratch, this happened to me and got it to work after, make sure u have good clean copies of the zip.
sent from 3d greatness......
Sad days..
I have a similar issue, but now more troubling. I had CM7 working for a little while, but I booted yesterday and got the boot loop as well (32GB touchpad). I couldn't get it out of the boot loop, so I let it run until the battery died. I charged it all day today, but now I'm trying to boot it, and I'm just getting the charging screen (it shows in red, and isn't letting me boot anything). Anybody else see any issues like this? I'm afraid I might have killed it
Also, if I should be posting somewhere else, please let me know. This seemed to be the most applicable topic currently. Thanks in advance.
Edit: Posted here, too:
http://forum.xda-developers.com/showthread.php?p=18515235#post18515235
I'm going to leave this here as well, though, because it pertains to the boot loop. If anyone has seen this, or has ideas, please let me know. Thanks again.
Edit 2: I think maybe this had to do with my charger or something (switched chargers when I got home, so maybe the other one wasn't working completely - I have 2 touchpads, though, they're both the same charger). I held home + power for about 60 seconds, touchpad didn't seem to do anything at all, then it booted into Android. Restarted into WebOS and I'll try charging completely.
vasmi said:
Use HP doctor and start from scratch, this happened to me and got it to work after, make sure u have good clean copies of the zip.
sent from 3d greatness......
Click to expand...
Click to collapse
I had to hard reset it because it was stuck in the loop, hold the power and home button for a long time like at least 30 seconds, and that got me back to moboot. I was trying to avoid the doctor because my buddy put alot of media on his tp already. When I do it should I open up the terminal and delete the cm7 partition and then do the doctor or will the doctor alone just work
Sent from my PC36100 using xda premium
alright i just ran the doctor and it did not get rid of the bootloop, im thinking that i have to erase the cm7 partition like i read about. damn
so i deleted the cm7 parts from the touchpad, ran the doctor again, and reinstalled. acme didnt install cm7 but moboot and cwm were installed. so i tried to install cm7 from cwm and it gave me a couple of errors, after clearing cache and dalvik cwm finally let me install. now instead of the bootloop im just stuck at the green cyanogenmod loading pic. so now im gonna try uninstalling everything from my comp then trying again.
i gave up after spending the entire day today trying to fix this. i tried everything and nothing will break this touchpad. my touchpad took about 30 minutes to install everything including reading about how to install cm7 and everything went fine on the first try, but my friends touchpad keeps getting the bootloop. i dont know what else to try any ideas anyone? i have tried removing the cm7 partitions made and doctoring, installing from another computer, installing from cwm after the bootloop, ive tried roms from 3 different links...nothing works. can somebody send me a copy of the rom they used to install because i "cut" mine as opposed to "copying" it to my touchpad. did anybody get out of this hole? thanks
I also got stuck in random boot loop after just rebooting into Android one time. I wiped both caches, fixed permissions, and then installed the CM7 zip file through recovery, then fixed permissions again and it's fine now.
There's also a new Alpha out, maybe try that.
durps said:
I also got stuck in random boot loop after just rebooting into Android one time. I wiped both caches, fixed permissions, and then installed the CM7 zip file through recovery, then fixed permissions again and it's fine now.
There's also a new Alpha out, maybe try that.
Click to expand...
Click to collapse
Damn wish I would've read this before I went to work, thanks for the input.
Sent from my PC36100 using xda premium
Youre welcome, report back and let us know if everything worked out.
Sent from my HTC Sensation 4G using XDA App
i downloaded the new alpha and went into cwm to try and install. i tried wiping both caches, fixing permissions then installing alpha 2.1, and fixing permissions again after that im out of the loop but now im stuck at the cyanogenmod loading screen
Related
Hey guys. I've been an Android & XDA user for a while now, so this question shouldn't be about a nooby-sitiuation.
My friend bought an AT&T Samsung Galaxy SII (SGH-i777) this week. I've been trying to flash CM7 ever since. I got the rooting done, the properly recovery (with no signature / "abort" problems)
The rom seems to keep bricking the phone. Its simply unflashable. I seen tons of people on XDA who got it to work, with barely any serious problems. I troubleshooted the problem myself, and its simply just the CM7 roms. I would do a full wipe, and then install the rom like I would on my other Android phones, and the installation is successful. When it boots, it gets stuck on the Galaxy SII boot screen (not the splash/boot animation screen) and it would stay on it with a yellow warning triangle on the bottom.
I tried flashing other roms, like Cognition X2, and they worked. Its just CM7 on this phone... which is odd because CM7 is usually stable (nightlies aside.) Especially since the 7.1 stable version was recently released. Anyone can help me get the rom up and going? Would be highly appreciated.
did you try to wipe dalvick cashe as well when you wiped data?
I just flashed it tonight myself and all I did was reboot into CWM and did a Wipe data/factory reset and then Wipe cache partition. After doing that, I simply flashed the cm7 zip file that was loaded on my internal sd. Rebooted and no problems.
I didn't have ANH ISSUES installing it but I know I read that some.people bad to flash it twice initially. So flash it, then when it goes back to the recovery screen flash it a second time. I also remember users on the international SGS2 bad to do the same thing. Most have no issues but I think they found that it depends on what you used to root your phone (on the SGS2 internationals) and I THINK some had to do the same here. Try it and if it works just hit the thanks button.
Sent from My KickAss CM7 Galaxy S2
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
How do you boot into recovery? I know On the SGH-i777 you have to hold the Vol down+back+power to get to the Download mode, but I tried everything to get to the recovery itself.
Boobie Watcher said:
did you try to wipe dalvick cashe as well when you wiped data?
Click to expand...
Click to collapse
Yes. I've flashed many roms before, this seems to be the only one I had ever seen a problem with.
mfpearson said:
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
Click to expand...
Click to collapse
Word.
Edit: To boot into recovery vol up+vol down+power
Had the same problem. Read somewhere to install the ROM twice in a row in CWM without rebooting inbetween. Worked like a charm.
Thanks for the feedback guys. I'll try this in the morning once I get my hands on the phone again.
Saw this type of behaviour on occasion with cm7 on my aria. Sometimes caused by a bad download of the rom. Did you verify md5s ?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Don't forget to do a master data clear /reset before trying to boot the new CM7 rom for the first time - clear out the old stuff. Works perfectly here.
Sent from my SGH-I777 using xda premium
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
squigge said:
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
Click to expand...
Click to collapse
That's the way I did it. Put the update in the same folder on the internal SD card. I can't even access my external SD card from CWM.
Sent from my SGH-I777 using xda premium
Hmm, I'm not sure what I'm doing wrong then. I did a factory reset, and wiped the cache and get the same thing. I know it wiped because now I have nothing setup on the phone when I boot normally. Suggestions?
Quit downloading the CM7 builds for the International Galaxy S II. They will NOT work. That is why it fails. Look for the Galaxys2ATT build.
Sent from my SGH-I777 using xda premium
I got the build by going to the cm7 website, looking by device, finding the galaxy s 2 and grabbing the stable one. So perhaps that is the incorrect one and I'll look closer for one that has att in it, whenever the site isn't going up and down. They seem to be having issues today.
Make sure you're installing the version located in this thread...
http://forum.xda-developers.com/showthread.php?t=1297568
Specifically this link
Double flash made it work. Thanks guys. + thanks for telling me how to boot into recovery lol. Great rom.
Sorry for the newb issues, it was the wrong version. I got the att version from the thread previously mentioned and that worked perfectly. Thanks!
i tried installing CM7 alpha 3.5. first install went okay fully. went to reboot and boot up and after i clkick cyanogenmod in the dual boot loader, it will display cyanogen icon and load for about 8 - 10 seconds then restart. keeps going in that order. tried erase/wipe all, dalvik, cache, etc... i am not sure what hapopened. does anyone have any ideas for me?
thanks in advance!
Bad zip?
Are you coming from a earlier version of cm7?
Or is it a first time flash for the touchpad?
Bear gri11z said:
Bad zip?
Are you coming from a earlier version of cm7?
Or is it a first time flash for the touchpad?
Click to expand...
Click to collapse
coming from alpha 3. not first time flashing. havent had problems before. tried redownloading the zip 2x
i had the same issue with miui. took me a day to figure it out, as there are few posts on this. you must "wipe sd" in cm recovery before installing the rom. do a backup first. it doesnt touch the webos area.
-ben
bensdeals said:
i had the same issue with miui. took me a day to figure it out, as there are few posts on this. you must "wipe sd" in cm recovery before installing the rom. do a backup first. it doesnt touch the webos area.
-ben
Click to expand...
Click to collapse
tried to do clockwork recovery. finished backing up boot, then went to back up system and restarted.
how do you wipe sd? do you mean partition it?
A sort of solution
I upgraded from 3 to 3.5 as well and I got in to a bootloop as well do I downgrade then re-upgrade or what, any help would be great.
EDIT: After posting this I reinstalled 3.5 and it's working but i'm never going to turn off android again at least until ICS
KJSOARES2 said:
I upgraded from 3 to 3.5 as well and I got in to a bootloop as well do I downgrade then re-upgrade or what, any help would be great.
EDIT: After posting this I reinstalled 3.5 and it's working but i'm never going to turn off android again at least until ICS
Click to expand...
Click to collapse
did you perform any other steps? you just installed 3.5? nothing special?
edit: i tried reinstalling 3.5. i tried redownloading it ot make sure it wasnt corrupt. nothing happened. it reboots during the installing system partition.
I wiped the cache and dalvik other than that I did nothing special, then I just re-installed it and it's working so far.
My tab is rooted, I have cwm 4.0.0.4 on the tab. I have been happily using TASK650 10 ROM. Today when I turned it on I had a garbled screen. Tried rebooting, get the same thing.
I rebooted into recovery and attempted to restore my latest nandroid back up. I got an error say the there was en error restoring \data.
I tried a couple other backups still had and got the same result. I now get no further then the boot animation. I was going to try factory reset/wipe etc and reinstall the ROM. After doing this realized I had deleted the zip.
So now I can't get my TAB to boot past the boot animation.
I have tried searching for a solution but I haven't had a lot of luck. If you can help or point me to a link or something, I will greatly appreciate it.
thanks
did you try wiping everything before restoring nand?
rlowens44 said:
My tab is rooted, I have cwm 4.0.0.4 on the tab. I have been happily using TASK650 10 ROM. Today when I turned it on I had a garbled screen. Tried rebooting, get the same thing.
I rebooted into recovery and attempted to restore my latest nandroid back up. I got an error say the there was en error restoring \data.
I tried a couple other backups still had and got the same result. I now get no further then the boot animation. I was going to try factory reset/wipe etc and reinstall the ROM. After doing this realized I had deleted the zip.
So now I can't get my TAB to boot past the boot animation.
I have tried searching for a solution but I haven't had a lot of luck. If you can help or point me to a link or something, I will greatly appreciate it.
thanks
Click to expand...
Click to collapse
animatechnica said:
did you try wiping everything before restoring nand?
Click to expand...
Click to collapse
Yes, I tried that.
why can't you factory reset? Should boot fine to task10. Worst case, start over using odin.
Out of curiosity... Do u have a different version of CWM than the one u made the back up with? This happened to me last week. I had a different CWM version than when i made the back up so i got error when tryin to restore. I had to use odin
Sent from my SGH-T989 using XDA App
Hi got a galaxy tab 10.1 ive got the Kang CM9 ICS rom on it, worked fine for about a month then suddenly just started crashing
did a hard reset device powers on charges starts to load boot image then freezes and crashes.
im able to launch recovery mode, tried doing factory reset and it wouldnt go through.
tried cache whipe was able to complete and the boot logo lasted longer then froze and crashed again.
not sure what happened and im thinking the only thing left to try is a full reflash
has anyone else experianced this?
thanks in advance
alstylez said:
Hi got a galaxy tab 10.1 ive got the Kang CM9 ICS rom on it, worked fine for about a month then suddenly just started crashing
did a hard reset device powers on charges starts to load boot image then freezes and crashes.
im able to launch recovery mode, tried doing factory reset and it wouldnt go through.
tried cache whipe was able to complete and the boot logo lasted longer then froze and crashed again.
not sure what happened and im thinking the only thing left to try is a full reflash
has anyone else experianced this?
thanks in advance
Click to expand...
Click to collapse
I've not experienced this because I haven't messed much with Kang CM9 ICS, but my first suggestion would to be restore from nandroid backup. If you're like me, in the past, you didn't do one or can't access it. So a full reflash or possibly going back to stock and then a reflash would be my suggestion.
If you decide to go back to stock first, or still need to after a reflash, the overcome ROM thread is a good place to lead you to 7500 & 7510 stock ROMs. You'll find a link to a guide outside xda there where towards the bottom part of the guide it says Restocking yer system.
Sent from my GT-P7510 using XDA Premium HD app
thanks Benzoman was able to reflash the stock rom from rogers using ODIN after which it got stuck in a bootloop. then tried data wipe in recovery mode and it booted up like normal.
any idea what could have caused it?
Depends if you had HC 3.1 as a base firmware, more likely to crash, then another would be what version of ICS you used, because the kang is at milestone 4, the current stable march edition.
Well let me explain my predicament. The other day I flash somex's something explosive rom after a wipe of the everything I need to wipe ( Data,Cache,Davlik) When it was finished flashing I got to rebooting. I ended up with a blank, yet illuminated screen ( if that makes sense) I waited about 20 minutes. After coming to the conclusion that the ROM doesn't work I did another wupe of everything needed. Then i flashed JoseGalre's ROM since it has aroma it told me that it had an error and coundln't finsih the instalation. I wiped again and reflashed, same error. I wanted to see what would happen if it let it boot up w/o recovery and it ended up in a boot loop. I tried to go back to 4ext and it seemed to load up just fine but half way through the startup it ends up back in the bootloop. I ran Hasoon's all in one kit and flashed TWRP and it worked just fine until I flash a rom. It seemed to be working just fine then it suddenly crashes and we're back in the loop. I've been trying to fix for the last few days but to no avail. I marked the title as urgent because my parents are going out of town for the weekend and I really need a phone. They havn't a clue that it doesn't work becausse they get home before me. Any help would be appreciated a great deal.
I've had something similar happen and freaked out my phone was down for half a day.
Try booting into the boot loader by holding vol down and power boot into recovery, wipe everything then format everything except SD card and try restoring a backup. Hopefully you made one or two in the past.
Sent from my HTC Amaze 4G running Evervolv jellybean 4.3
Illstatic said:
Well let me explain my predicament. The other day I flash somex's something explosive rom after a wipe of the everything I need to wipe ( Data,Cache,Davlik) When it was finished flashing I got to rebooting. I ended up with a blank, yet illuminated screen ( if that makes sense) I waited about 20 minutes. After coming to the conclusion that the ROM doesn't work I did another wupe of everything needed. Then i flashed JoseGalre's ROM since it has aroma it told me that it had an error and coundln't finsih the instalation. I wiped again and reflashed, same error. I wanted to see what would happen if it let it boot up w/o recovery and it ended up in a boot loop. I tried to go back to 4ext and it seemed to load up just fine but half way through the startup it ends up back in the bootloop. I ran Hasoon's all in one kit and flashed TWRP and it worked just fine until I flash a rom. It seemed to be working just fine then it suddenly crashes and we're back in the loop. I've been trying to fix for the last few days but to no avail. I marked the title as urgent because my parents are going out of town for the weekend and I really need a phone. They havn't a clue that it doesn't work becausse they get home before me. Any help would be appreciated a great deal.
Click to expand...
Click to collapse
I don't think you wiped properly. You needed to format ALL PARTITIONS. I can't stress that enough lol.
Edit: Go into bootloader first. Hold volume down then hold power as well. Choose recovery and format all partitions. If that works you're good! :thumbup:
Use the toolkit and flash 4ext. And make sure whenever you flash Roms that you format all partitions.
If that doesn't work you need to flash a RUU, get it back to stock, it will still retain S OF. Then flash 4ext again. Your problems should be fixed for sure if my first method doesn't work.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey guys it completly out of the question to format my internal storage so keep that in mind
GB or IC RUU and which one?
You don't have to format internal storage just data, cache, system, and boot
Sent from my HTC Amaze 4G running CyanogenMod 10.1
Illstatic said:
Hey guys it completly out of the question to format my internal storage so keep that in mind
GB or IC RUU and which one?
Click to expand...
Click to collapse
Just choose format all partitions.
If you want to use a ruu use the T-Mobile ICS RUU.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So i changed the name of the RUU i download to PH85img.zip and use the all in one tool kit to flash it. The black htc loading screen came up. I waited until it finished and then the bootloader came up with a list of things it head to unzip and then load. After all of that was finished it gave me an error. After reading a message that you should get an error ( i now realize this was at another stage) so i though nothing of it and rebooted. A black screen with 4 warning triangles came up. I let it load all day and when i got home i plugged it back in and I noticed it looked like it was unplugging after securing the charger in I came the conclusion that it wasn't holding a charge and dying on the battery. Normally I would leave it alone but when you plug in the charger it turns itself on. I've began living with the fact that my phone is bricked. But any help would be appreciated.
BTW is there a way to get data (music pictures contacts) that were saved on the internal storage?
Probably should have gone with full caps on the PH85IMG.zip
It's easier just to put the zip on your external sdcard and gone in to bootloader.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
Probably should have gone with full caps on the PH85IMG.zip
It's easier just to put the zip on your external sdcard and gone in to bootloader.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
So is there anything that I can do when I plug it in it wont boot or charge at all so am i truly bricked or is there still hope
Illstatic said:
So is there anything that I can do when I plug it in it wont boot or charge at all so am i truly bricked or is there still hope
Click to expand...
Click to collapse
Should be hope, check out the unbricking project...
http://forum.xda-developers.com/showthread.php?t=1627882:cowboy: