My Touchpad gets stuck with the CM Logo. How can I reinstall everything?
what exactly did you do? power + home button should hard reset your device. provided you placed the moboot.zip file in the folder you should be able to boot in to webos and redo your acmeinstaller, or doctor your tablet.
did you follow the steps for using acmeinstaller? were you trying to use clockwork mod to flash an update? how long was it on the loading screen before you declared it looped?
mister timely said:
what exactly did you do? power + home button should hard reset your device. provided you placed the moboot.zip file in the folder you should be able to boot in to webos and redo your acmeinstaller, or doctor your tablet.
did you follow the steps for using acmeinstaller? were you trying to use clockwork mod to flash an update? how long was it on the loading screen before you declared it looped?
Click to expand...
Click to collapse
After about 5mins on the CM logo screen on 5 occasions I declared it looped.
I used Acmeinstaller to install the original alpha, then I used CWM to install the alpha2.1.
I think it went into the loop after upgradeing to 2.1 then booting into webos once.
When I go into CWM I cant access the .zip files in the cwrecovery folder
If you can get back in to recovery, reflash, and still have the issue then I would boot in to webos recovery and, using acmeuninstaller, remove cyanogenmod.
From there doctor your touchpad using the webos version of your choice. (newest is 3.0.4)
Re-enable developer mode on webos and set up to install alpha 2 using acmeinstaller.
Webos recovery mode again, then acmeinstall that bad boy. (along with gapps, cwm, and moboot).
I have installed on a handful of devices with no glitch. I didnt use CWM to install two point one, I just did the same procedure with acmeinstaller with the updated version.
This happened to my mom's tp and my own. I read somewhere that powering off would fix it and it worked for both touchpads
Sent from my HTC Eva 4G using Tapatalk
mister timely said:
If you can get back in to recovery, reflash, and still have the issue then I would boot in to webos recovery and, using acmeuninstaller, remove cyanogenmod.
From there doctor your touchpad using the webos version of your choice. (newest is 3.0.4)
Re-enable developer mode on webos and set up to install alpha 2 using acmeinstaller.
Webos recovery mode again, then acmeinstall that bad boy. (along with gapps, cwm, and moboot).
Click to expand...
Click to collapse
Did this and it worked like a charm. Thanks
Related
Hi, I just brought my G Tablet and I have downloaded "ClockworkMod_Gtab_v08.zip" and copy the "update.zip and "recovery" into my internal SD Root dir.
I boot into recovery mood and ClockworkMod install but after reboot into recovery mood again, the screen freeze in "Booting recovery kernel image" and don't go into ClockworkMod screen (for more then 10 mins and have try rebooting it a few times).
The G Tab can still boot up normally in to TapnTap, everything seem working find and I can connect to my computer using USB cable. But just can't boot into recovery.
I wanted to install new rom, how do I make boot into ClockworkMod screen (recovery)?
Any help is welcome.
Thanks
Take a look at the recovery script and make sure it says sdcard vs sdcard- ext that's the only thing i can think of right now that May do that.
Sent from my MB860 using XDA App
This is the symptom of installing the wrong cwm. You're on the 1.2 branch but you put the cwm for the 1.1 branch. You hosed your recovery. Go to my website and use code red in the "start here" page to recover.
Same thing I happened to me. I bought mine off Woot a few days back and it came with 1.2 bootloader (4349). No matter how many times I tried, I could never get back into recovery. Here are the steps I did to fix that:
1. You need to do nvflash to recover your stock recovery (http://forum.xda-developers.com/showthread.php?t=861950) - I followed all steps in the "Installation" section.
2. After this, you should now have your stock recovery back. You're going to need to downgrade manually to 3588 - Just follow the "POST NVFlash" section on that same page.
3. Once you're done downgrading, should be able to install CWM without issue.
Problem solved!
Thanks goodintentions you save my G Tab, it works!
And now it can boot back into ClockworkMod recovery mode.
Your website is very good and informative. Good job.
Thanks again.
Thanks "goodintentions", You saved me as well
Followed your post and it worked.
Good information...thanks for the help!
bvd
nvflash for dummies not working
Bro I connected my gtab to my computer in apx mode and my computer couldn't see it. Went to device manager and apx device was absent. Needless to say connecting my gtab to the computer was as far as I could get. If it helps any, I'm currently running bottle of smoke. Where I screwed my tab up is when I opened up time manager and it had an ota update for the recovery I was using.... Shoulda known better than to select advent vega for the device when it was running on the 1.2 branch recovery. Any tips? I wanna change my time but I need my recovery up n running.
goodintentions said:
This is the symptom of installing the wrong cwm. You're on the 1.2 branch but you put the cwm for the 1.1 branch. You hosed your recovery. Go to my website and use code red in the "start here" page to recover.
Click to expand...
Click to collapse
I am currently trying to flash my vibrant back to stock 2.2. My latest attempt was done using the AIO tools. Every method I have tried has lead to the Vibrant boot screen appearing for a few seconds, and then rebooting. Any suggestions?
Have you tried Odin?
Sent from my SGH-T959 using XDA
whatever5 said:
Have you tried Odin?
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Yes, I have tried Odin with and without AIO tools. In all of the threads I have looked at, the answer seems to be flash back to 2.2 stock, but that is what I am trying to do. Thanks.
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Woodrube said:
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Click to expand...
Click to collapse
I currently can not get into recovery mode. I am holding the power, vol+, and vol- buttons, inserting the battery and then releasing them when the vibrant screen appears. But it just continues to boot cycle.
I flashed the pit and tar that came with AIO tools. No go. Still just boot cycles. Sorry for being a pain.
I do have a backup, but I am not sure what I can do with right now.
Try turning the phone off, plug in USB hold just volume up and power on the phone..... that should put it into download where you can run Odin and flash back to stock
Sent from my touchpad using XDA
related problem (sort of)
Solved: problem solved. I reflashed CM7 over the bootlooping mess, and it took. Then I was unable to get AIO Vibrant Toolbox to recognize that debugging mode was on, even though it was. So I just copied the files over and went through a massive round of forcing the zip files on again and again. I now have Slim 3.5 on my phone, so I can start playing with it.
*****************************************
I'm an extreme noobie, trying to upgrade my T959 to ICS. I've picked Slim 3.5 (latest release version as of this week) as my first attempt (but really any simple but well-functioning ROM will do for me).
I've rolled back to Eclair (from the official Tmo Froyo upgrade way back when), rooted, and numerous times followed various directions to install the zip for Slim -- sometimes trying CM7 as an intermediate step. The CM7 install failed in the same way as the ICS, as described below.
I've done it with and without AIO Vibrant Toolbox. I've used ClockworkMod Recovery 2.5.1.2 to wipe the data, clear both cache partition and Dalvik cache, and format system. I've popped the zip file in various folders and at toplevel, both external and internal SD.
In all cases, it gets off to a good start, and then I'm left with endless bootlooping: Vibrant logo, Mod logo, a textblock of about 15 lines, repeat. I've always been successful after that in using Odin3 v1.81 to get back to Eclair.
I got sucked into a tech vortex until 4:30 am last night trying again and again, and I'm way way too old for that!
Any thoughts?
It doesn't seem real common, but I seem to have permabricked my nook. I can't connect to it via adb, can't boot to recovery from sd or the emmc, and can't seem to get it to recover via sdcard. I've tried Adam's Unbuntu Unbrick, copying the recovery to the sdcard, and trying to recover to 1.4.2 via the sdcard.
How I broke it:
I installed Goomanager and installed TWRP, and then flashed to CM9 with the 3.0 kernel. The recovery and CM9 were working as well as could be expected, but CM9 had too many Sleep of Death issues so I decided I wanted to roll back to a nandroid backup of CM7. TWRP couldn't see my backups, so I decided I'd flash the recovery back to CWM via indirect's nookrecoveryflasher.apk. This was the end.
The symptoms:
I rebooted after using the nookrecoveryflasher flashing back to CWM, and now it just displays the n with the copyright info. It then flashes white briefly, then a slightly bigger n is displayed, it gets brighter, then dimmer, then a black screen (still backlit). The charger goes from red-orange to green after the screen goes black, and charging appears to be halted. If I hold down the power button for 8 secs, the backlight goes off and the charger light turns back to red-orange and it seems to charge. ADB lists no devices.
Are there any suggestions for things I should try that I haven't already? I thought this was pretty much unbrickable but something went really badly, and this should have been a relatively "safe" operation.
Update:
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
Did you try removing and inserting the sdcard back in while in twrp?
I stayed with cwm and I was able to flash both kernel versions of cm9 just fine. Since u already tried the 1.4.2 revert to stock, your situation seems quite troublesome indeed
Sent from my Nook Tablet using xda premium
I can't get into either TWRP or CWM now.
Hm sounds like your recovery is screwed up...
Sent from my Nook Tablet using xda premium
Do you know what kind of bootloader you are using? Is it cyanoboot?
Sent from my Nook Tablet using xda premium
Cyanoboot was installed when I installed CM9, but after trying to flash back to TWRP, it doesn't seem to be coming up any more.
Wow that's unfortunate. I was thinking if u were using cyanoboot you would be able to hold the n button to choose where to boot from...
Sent from my Nook Tablet using xda premium
Have you tried burning a clockworkmod recovery image to an sdcard and booting into cwm via said sdcard? If you can get this to work, you can flash the internal cwm recovery zip to overwrite the internal recovery partition.
Also try the 8 failed boots method. Each time you see the gray n logo dissapear when powering on, pressand hold both the n button and the power button until your nook tablet shuts off. Repeat this 8 times and your tablet should be forced to boot into recovery mode. Good luck!
Sent from my Nook Tablet using xda premium
I don't think that will work, as it sounds as though the recovery partition was broken with indirect's app (it happens and I think there is a thread he made with 1 method of fixing broken partitions but it requires you to have drivers set up properly for it).
I had this same thing happen to me when indirect pushed his new app that supports the 8GB and 16gb models out. I got the big N and I ended up flashing cwm via sdcard cwm and then flashing cm9 again via the newly flashed internal cwm.
Yes I've tried putting CWM on the sdcard but the same thing happens. I've also tried 3 different sdcards 2,8,16Gb. I've tried meghd00t's repart.img and it all behaves the same. It's as if the code that gets called to read the sdcard is broken now.
It sounds like after that white flash is when CMW should load but instead I get a bit bigger n, and then it goes black.
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
comat0se said:
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
Click to expand...
Click to collapse
try locating the stock 1.4.2 rom in the development section and flash that. see if it works.
In general if you are in CWM you have adb access at that time. The world is at your wish when adb works. Push stock recovery, etc., etc. Instead of trying to flash (which continues to fail) use adb to recover by of the many methods available. I would begin with pushing stock recovery and boot recovery (by command or power + N).
Good Luck.
Lars for tobdaryl
Did you flash TWRP using the .zip from the 1st-2nd page? That TWRP .zip is bugged so as not to recognize an external sd. I had a problem like this until I used a recovery sd (ill put a link in here in a sec)
I had a terrible 13 hour run of trying to fix it before I finally got it to boot, then I opened up my gmail inbox and found out that I had won a Transformer Pad 300 from Phandroid.com, needless to say after 13 hours I was nearly hysteric when I found this out, hope your issue gets resolved.
I also couldnt mount sd, couldnt adb, couldnt fastboot, couldnt get sd to show up in TWRP so maybe this method will work:
http://forum.xda-developers.com/showthread.php?t=1640958
Sent from my Transformer Prime TF300T using XDA Premium HD app
Heres what I did:
The other day I updated to TWRP 2.3.0.0. That seemed to work fine, but it may be part of the cause here. So that's my recovery.
Today I:
Downloaded latest CM9 nightly
Opened Goo Manager
Told it to flash that Nightly+4/29 gapps and do dalvik/cache wipes.
And hit Install.
I left the room for a while, and when I came back, I noticed it was boot looping after the CM logo(never makes it to the animation). So I booted into webOS, redownloaded the nightly from my PC, and moved in onto the TP from there. Then I tried to boot into TWRP to flash it, and it gets as far as the Team Win logo then it resets and goes back into moboot.
So, I safely boot into webOS, but neither CM or TWRP will load up. What can I do to get android back up and running w/o losing my data?
If not possible, how do I get android up and running at all?
I had been on the nightly before this one so it was running fine before.
Should I try to use Acmeinstall2 to reinstall an earlier version of TWRP?
Posted by Mr. Z's Galaxy S3
I would use ACMEUninstaller then in webos from preware run Android uninstall as it clears out the boot folder .
After that yes do a normal installation using ACMEInstaller 2 or 3 , if using 3 gapps also needs to be renamed so that it begins update- .
Below is a link for TWRP 2.2 .
https://www.box.com/shared/dvtih92a2zwebe550mnj .
Which you can install after you're up and running safety with with the normal clockwork recovery.
PS someone else on this forum had the same problem.
Good luck .
sstar said:
I would use ACMEUninstaller then in webos from preware run Android uninstall as it clears out the boot folder .
After that yes do a normal installation using ACMEInstaller 2 or 3 , if using 3 gapps also needs to be renamed so that it begins update- .
Below is a link for TWRP 2.2 .
https://www.box.com/shared/dvtih92a2zwebe550mnj .
Which you can install after you're up and running safety with with the normal clockwork recovery.
PS someone else on this forum had the same problem.
Good luck .
Click to expand...
Click to collapse
Does this allow me to retain the data on CM or will it delete it? I don't guess it matters really, I just would like to know before trying.
Also, I went ahead and tried using ACMEInstaller2 to install TWRP and the latest nightly, and it makes the TP go into the linux command line install screen its supposed to go to, but it does it really fast. Not sure if its installing or not.
Posted by Mr. Z's Galaxy S3.
zanderman112 said:
Does this allow me to retain the data on CM or will it delete it? I don't guess it matters really, I just would like to know before trying.
Also, I went ahead and tried using ACMEInstaller2 to install TWRP and the latest nightly, and it makes the TP go into the linux command line install screen its supposed to go to, but it does it really fast. Not sure if its installing or not.
Posted by Mr. Z's Galaxy S3.
Click to expand...
Click to collapse
Normally I just put the latest nightly renamed to begin update- , moboot, gapps 04/29 and cmw https://www.box.com/shared/0dc8571f09a8f285df59 into the cminstall folder then run ACMEInstaller2
After that you can use cmw to install the TWRP zip or unzip and copy the TWRP ulimgage to your boot folder with the free version of Rom
Toolbox pro then deleting the cmw ulmage .
Well, I'm trying to get ACMEInstaller2 to work, but its not flashing *anything.* Not CM, not gapps, not CWM.
Its what I used to flash CM9 initially, so I know it works. And I put all of the zips in the cminstall folder, but after I type in the
novacom boot mem:// < ACMEInstaller2
It goes to the Linux screen, and scrolls through about 10 seconds worth of text, then reboots. And of course I have no moboot.
Anything else I can try? As it stands, I have no moboot.
Posted by Mr. Z's Galaxy S3.
It sounds like your boot partition is full. It is located at /boot. You need to get some spare kernels off there. Adb can clear it out. Classic Nerds have a utility to clear out extra kernels. I'm sure there are other techniques. there is probably something at preware to do it. The boot partition isn't big. With webos, cwm, twrp, teamwin, cm etc. it is full. It doesn't give any good error messages either. It just tries to boot a half image and loops.
I am thinking that your boot folder has to much crap in it . Did you you run the Android uninstaller from preware as I suggested after using ACMEUninstaller?
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Use this thread to install CWM, I'm not a fan of TWRP. http://forum.xda-developers.com/showthread.php?p=25786947 I used this and had no problems updating
Sent from my NOOK Tablet running CM10
deltantor said:
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Click to expand...
Click to collapse
This has been happening to me occasionally. I have found that when I get the black screen, pressing the Power button launches Recovery (CWM in my case). See if that works for you.
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
To the rescue
Ok, I have posted this on a different day. Try this with a blank sd card. Look at the bottom post called "Here is a video"
It a external boot cwm v.5 but you can copy this into your sd then flash and you have cwm v6.0.1.5 internal. Either way you have two ways to do recovery (external and internal):victory:
djd338 said:
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
Click to expand...
Click to collapse
Thanks very much for the reply & link!
I'll do this ASAP when I get back home & report. Thx again!
Sent from my Nexus 7 using Tapatalk 2
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Look pass the fear and go one step at a time, before you know it, your there.
It looks like you have already resolved this from this thread.
Ok, basically I'll go step by step.
1. Download ubuntu iso from ubuntu website (you can donate or put 0$ then download iso) and burn it to cd. 5 minutes
2. Stick the cd into a system that you don't plan to look at the video that is showing you the process and boot it up from a reboot and not from within windows. Select the left square which basically load the ubunbu from cd but does not install anything to your hard drive.3 minutes
3. You can view the whole video but I would skip to the section in video (3:28 watch to 4:43, 6:56 watch to 8:06 ) where I mentioned the setting the two flags in your sd after quick format fat32 and extracting the four files into your sd within ms windows platform from the post . I did this with a normal mini sd card adapter and not the usb stick adapter he used in the video. Since you are doing this to a blank mini sd then there really nothing to worry about since it is blank in the first place. 2 minute
4. If you had your apps backup with titanium backup then it still will be on the main mini sd and not the one that working with for this recovery.
5. I notice you did not mention wipe dalvik cache from your post. You should always wipe dalvik then wipe factory then do a single flash to test boot up.. You can flash gapps after a successful boot up into jellybean. (here's a video showing that I'm using external cwm v.5 even though its recommended to use v.6 .) You can always use cwm v.6 on your next cm10 test rom or use cwm v.6 to reflash to same rom once a successful boot up have been obtained with external cwm v.5. This purpose is to get it running on your nt.
6. Be patient for the first boot. Should not be more than 5 minutes max. It will look black then load. If it boot loops then wipe dalvik then wipe factory and do a single flash to test boot up again.
This will at least get cm 10 flavored rom on to your nt.
djd338 said:
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Click to expand...
Click to collapse
Got it back! Thank you for your help & patience. Also for the timely responses. I now have a bootable "recovery sd card" for curing these type problems. I've labeled it & filed away for any future borks of this kind! And I have cm10 up & running stable.
Thank you!
Sent from my Nexus 7 using Tapatalk 2