so i have had a 16 hp touchpad for a while i had cm7 and now i have cm9 0.5 and never had a problem flashing them
but i just got hold of a 32gb hp tp did everything the sam but i am now stuck on a loop in double penguin mode see atached pics i factory restet the touchpad it was running web os 3.0.5 any ideas how to fix this
thanks
Did the touchpad even make it through the android installation? Or did this happen during the initial install? And is WebOS still bootable, or is the linux screen the only thing happening?
Yes it boot's to web os if I hard reset and everything works fine it's when I flash cm9 then it gets half way and starts to loop the Same things over and over that are in the pic I left it for 25 min with no luck I tryed cm9 0.5 and 0.6 with all the latest files and ACMEInstaller 2 I have do a full erase of web os with both 2 time but no luck there so I switched too the 16gb hp and did a total wipe and re flash with the same file and it installed so I am at a total loss lol
try and use WebOS Doctor and do a complete restore of your touchpad then try again
Airlesscorpse said:
Yes it boot's to web os if I hard reset and everything works fine it's when I flash cm9 then it gets half way and starts to loop the Same things over and over that are in the pic I left it for 25 min with no luck I tryed cm9 0.5 and 0.6 with all the latest files and ACMEInstaller 2 I have do a full erase of web os with both 2 time but no luck there so I switched too the 16gb hp and did a total wipe and re flash with the same file and it installed so I am at a total loss lol
Click to expand...
Click to collapse
Stupid questions have to be asked: Folder named cminstall with required zips?
Sent from my Galaxy Nexus using Tapatalk
The fact that your making it that far makes me think you have got the steps right. Sounds like a bad acmeinstaller2 or a bad cm9 zip. Download acmeuninstaller and run that to bring your TP back to stock. Then re-download acmeinstaller2 and the cm9 zip. Make sure you check your MD5 hash. Let us know!
Sent from my cm_tenderloin using Tapatalk
That happened to me once on a friends touchpad, it would get stuck at the installer. If it keeps doing that, try unplugging the USB cable from the HPTP once the scripts start to show up and see if it finishes.
Ok I think first I will try re down loading all files and yes the folder is cminstall lol it was the first thing I checked then I will run doctor and try the cable trick I will let you guys know how it goes thanks to you all for the hints !
so in the end i had to do a full recvery using web os doctor but good news it flash the first time i did try new cable and redownloading the files but that did not work but thanks for everyones help
Airlesscorpse said:
so i have had a 16 hp touchpad for a while i had cm7 and now i have cm9 0.5 and never had a problem flashing them
but i just got hold of a 32gb hp tp did everything the sam but i am now stuck on a loop in double penguin mode see atached pics i factory restet the touchpad it was running web os 3.0.5 any ideas how to fix this
thanks
Click to expand...
Click to collapse
I'll just put this out in the open, because nobody else has. Since you say you had a Touchpad with CM7 for a while and are doing the exact same procedure to flash CM9... Are you using the original ACMEInstaller or ACMEInstaller2 (The one that came out with the original CM9 A0)?
Related
okay, so i tried to install CM7 test build 8 onto my phone. the install got up till checking BML/MTD and then failed. i was already on test build 7.
anyhows, clockwork said the rom failed to install and then rebooted. now the phone is stuck in a loop of booting into clockwork and then aborting an install.
i would normally have just started up ODIN and flashed down to stock DJ05 or EB01 and then do the lovely root process; but alas i sent my PC into HP today for repair and stuck using a Macbook for a week or two. (no one else in my family uses PC anymore; iPad and Mac family now...sigh)
does anyone know of a way to fix this? i'd like to avoid going back to my old droid 1 (so laggy).
Dude.. this goes in either the thread for that rom or the Q&A section. You might get quicker responses when posting correctly.
Good luck.
Sry, thanks for the help though
reloaded89 said:
okay, so i tried to install CM7 test build 8 onto my phone. the install got up till checking BML/MTD and then failed. i was already on test build 7.
anyhows, clockwork said the rom failed to install and then rebooted. now the phone is stuck in a loop of booting into clockwork and then aborting an install.
i would normally have just started up ODIN and flashed down to stock DJ05 or EB01 and then do the lovely root process; but alas i sent my PC into HP today for repair and stuck using a Macbook for a week or two. (no one else in my family uses PC anymore; iPad and Mac family now...sigh)
does anyone know of a way to fix this? i'd like to avoid going back to my old droid 1 (so laggy).
Click to expand...
Click to collapse
i had a bootloop too with cm7 yesterday. Don't quote me on this but i think heimdall works on a mac, just like odin. here is a link that might help with heimdall
http://forum.xda-developers.com/showthread.php?t=957981
And yes wrong section to post, good luck
Im having the problem when I try to install it
Sent from my SCH-I500 using XDA App
I know it sounds odd but pull the battery and then do the three finger salute. I know we aren't supposed to but trying to wipe through there and then install has helped a couple of us with this problem on miui. I did it and when it finally installed right I rebooted into recovery the proper way and wiped. Worked like a charm.
Hope this helps, brother.
[Neuman]
SCH-I500 - EC09 Radio/MIUI FascinateMTD/OTB @1.2ghz -100mv/NeonGT & Infinite Themes
I Agree with Tim. Three finger method and reflash CM7 Build number 7 (after wiping of course) Then try build 8 again. You will lose settings and data. Hopefully you backed up beforehand but if you're stuck in a bootloop it's a moot point. Hope this helps.
Sent from my SCH-I500 using XDA Premium App
thedoman said:
I Agree with Tim. Three finger method and reflash CM7 Build number 7 (after wiping of course) Then try build 8 again. You will lose settings and data. Hopefully you backed up beforehand but if you're stuck in a bootloop it's a moot point. Hope this helps.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
have done this twice. after install number 7 restart and reboot recovery and you will see your back to the orange cwm and good to go with number 8 install. wipe delvik
Quickest way back is to use the EB01 install package that is linked in the stickied thread about returning to to a TW ROM after running. Apparently the two ROMs Linked (Eclair and Froyo) have the right bootloader to work with the PIT file. Anyway that's what it says in the thread.
Flash EB01 (with atlas PIT). Flash a 3.x CWM and then try the CM7 procedure. No need for OTA updates or voodoo and/or lag fix, root, etc. Just plain ol stock EB01. This worked for me last night. I have not used the phone a lot since then but so far its been working OK.
He can't do that without odin brother..
[Neuman]
SCH-I500 - EC09 Radio/MIUI FascinateMTD/OTB @1.2ghz -100mv/NeonGT & Infinite Themes
yeah...odin is out of the question for (hopefully) another two weeks. and i can't get heindall to work on my mac; keeps telling me that it isn't compatible with my laptop. *%&$ing MAC! STEVE JOBS, GO SUCK ON A BIG ONE
Lol tell us how you really feel.
Any friends that use pc? Work computer? Give what I suggested earlier a shot and let us know. If all goes well you could be fine in about 8 minutes lol
[Neuman]
SCH-I500 - EC09 Radio/MIUI FascinateMTD/OTB @1.2ghz -100mv/NeonGT & Infinite Themes
try using virtualbox and install xp. it'd be your best bet. not sure if you'll run into driver issues, should work fine. if you need an XP install let me know, i have an iso on my server that needs 0 activation and should get you by.
you can try a linux live cd and then heimdall
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
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.
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.
Installed CWM, didn't backup anything...being used to my inspire 4g i automatically went down to wipe data/factory reset. I flashed the base rom .7 and am getting a black screen on boot. Realised I wasn't supposed to wipe it and started download the lgnpst, and the recovery image but the only link I can find is codefi.re and its going insanely slow. Can I either be told I didn't mess up and just missed a step, or be given a new download link? Right now it looks like I get to wait 7 hours..
Go to http://webchat.freenode.net/?channels=lg-optimus-g and enter "!info lgnpst" if you're still having problems with booting or not able to boot.
There's a handful of people in there with successful experiences with it and they should be able to guide you through if you're having trouble.
Thanks, the codefi.re link for the files to restore the phone was just taking way too long. I was getting about 25 KB/s. But I finally got it working again
Sent from my LG-E970 using Tapatalk 2