I downloaded the 3/29/15 nightly build, copied it to my SD card and booted into recovery. Flashed, wiped data/factory reset and then boot to all sorts of errors from the Google apps. I can't use the tablet at all.
I've tried reflashing and wiping to no avail. I'm flashing in CWM 6.0.2.8 and there's no build newer than 3/29.
Should I just go back to 10.1.3?
For the record, I didn't think gapps was included with the ROM, but apparently it was.
General_Mayhem said:
I downloaded the 3/29/15 nightly build, copied it to my SD card and booted into recovery. Flashed, wiped data/factory reset and then boot to all sorts of errors from the Google apps. I can't use the tablet at all.
I've tried reflashing and wiping to no avail. I'm flashing in CWM 6.0.2.8 and there's no build newer than 3/29.
Should I just go back to 10.1.3?
For the record, I didn't think gapps was included with the ROM, but apparently it was.
Click to expand...
Click to collapse
I fixed it.
I reflashed CM10.1.3, downloaded CWM 6.0.4.6, upgraded CWM using Rashr, and reflashed CM12.
Related
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
geon106 said:
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
Click to expand...
Click to collapse
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
McJesus15 said:
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
Click to expand...
Click to collapse
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
geon106 said:
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
Click to expand...
Click to collapse
IT LIVES!!!
Don't know how I did it, but I managed to get TWRP installed on it. Using Fastboot somehow or ADB. It booted into TWRP and mounted external SD card, then flashed an official JB ROM(the Prime was on ICS before) and it has now booted up fine
I will now try and re-flash a custom ROM again(a different one) using TWRP but it is all looking superb
I was worried i'd have to claim on the extended insurance I took out with the retailer
So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Try this
SarahAnne said:
So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
Click to expand...
Click to collapse
Try this : http://www.mediafire.com/?4s77jvehqvsuruu
1)Download it
2)put the files ( flashing.boot Mlo etc...) on your sdcard,
3)completely turn off your nook ,
4)put your sd card on nook and turn it on.
5) press the ''N'' button when you see ''cyaogenboot'' (it also saids press ''n'' button for BOOT MENU)
6) in Boot Menu just choose option #1 (Internal Boot) it should boot into cm10
I had the same issue, but after a time (after making some supid things) i bricked my tablet, I figured this out with some help, It worked for me so it should work for you too.
So I was able to randomly boot into the bootloader and boot into CM but now it keeps rebooting into clockwork.
I have also attempted installing CM10 using the following link including using the flashable_fix_bootloop.zip that I cannot sadly can't link to due to being a new user
and the only difference is that now CWM went from blue accents to orange.
The function of flashable_fix_bootloop.zip is to reset BootCnt counter and BCB flag (see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1) in the event they do not get reset properly in some installation/recovery process. It seems that your "recovery boot-loop problem" might have a different underlying root-cause, hence re-setting these counter+flag by itself will not cure the problem.
Which particular build version of CM10 and AOKP ROM did you try?
Also, did you do "wipe data & factory reset" & "wipe cache" as part of the ROM installation?
Have you tried reflashing the ROM once you're in CWM? (As I underestand you may have, but just making sure!)
Maybe download it again (or try another one) and the flash it again (after the usual wipes) with your new recovery.
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
SarahAnne said:
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
Click to expand...
Click to collapse
When you boot from the SD card have you tried holding down 'n' to get to the menu then selecting SDC boot? It should boot cm10.1. Try selecting SDC recovery also and see what it does. You might be doing something wrong during the process.
You can also try renaming your boot file for cm10.1 to altboot. Then try it.
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
SarahAnne said:
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
Click to expand...
Click to collapse
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
DavDoc said:
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
Click to expand...
Click to collapse
6.0.3.1
SarahAnne said:
6.0.3.1
Click to expand...
Click to collapse
Still may be a shot in the dark, but try downgrading CWM to an earlier version, but not so early as to be unable to flash CM10. Maybe 6.0.2.5 to 6.0.2.9
Not ensuring this will work but it may be worth a shot. At least it won't put you in any worse condition than what you are in now.
Good Luck
Another thought, did you make a backup of your last ROM before flashing CM10? If you did I would assume you tried flashing your backup already, but have to ask.
It looks like you may have used two different builds of CWM based on one of your earlier posts - change of font color.
You also try the repart image if you don't have a stock backup. Find it on raywaldo site. It will re write your internal storage with stock ROM. Then flash cm afterward.
Woot I got the factory rom reinstalled, time to install cynogenmod again
I had the same problem
This worked:
digixmax said:
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Click to expand...
Click to collapse
However I was still unable to install any 4.2.2 ROMs + gapps.
I was on cwm 6.0.2.8 (or whatever the exact numbers are)
updated to cwm 6.0.3.7
wipe data
install rom
install gapps
wipe cache
wipe dalvik
everything works now.
I just loaded CM10 SDC on my tablet because CM10.1 started to get really buggy and crashed a lot. Normal procedure wipe data,wipe cache, wipe dalvik cache.
I replaced the recovery.img which was 5.x.x.x with the newest version (6.0.2.9). Installed zips and when I booted it didn't find WiFi. Went into settings and WiFi wont turn on.
Trying to figure out what's wrong. I didn't delete and ROM partitions or anything. Only thing I can think is by installing the zip with the newest recovery didnt fully install the ROM. Any suggestions what to do?
datallboy said:
I just loaded CM10 SDC on my tablet because CM10.1 started to get really buggy and crashed a lot. Normal procedure wipe data,wipe cache, wipe dalvik cache.
I replaced the recovery.img which was 5.x.x.x with the newest version (6.0.2.9). Installed zips and when I booted it didn't find WiFi. Went into settings and WiFi wont turn on.
Trying to figure out what's wrong. I didn't delete and ROM partitions or anything. Only thing I can think is by installing the zip with the newest recovery didnt fully install the ROM. Any suggestions what to do?
Click to expand...
Click to collapse
Also (in case somehow a partition was erased) I have all my Serial Number, Mac Address etc etc on backup. But I am assuming it's not a problem because I didn't write over the p5 partition.
I solved the problem by using the SDC img and writing that to my SD card. WiFi works now. If anyone else has similar problems DO NOT upgrade your recovery.img before flashing. It will most likely not flash correctly.
So I'm tying to help my best friend flash CM11 on his e970, it's rooted and had TWRP 2.7.0.1 installed. I did a full backup and attempted to wipe data, system, cache, and dalvik. It would start then flash off and then back to TWRP again. Doing this one at a time showed that the error happened when attempting to wipe data. I tried the latest Phil's CWM and backed up wiped fine but when I attempted to install CM11 either M6 or the 052114 Nightly it gives a status 7 error. So I tried it with the latest CWM touch recovery and the same thing. Backups restore each time. I then attempted to flash Mokee thinking it must be an.issue with the downloads, and still status 7. Any ideas? Thanks, every time I google the error I read it's a recovery issue, now I'm not too sure it is in this case. 3 different recoveries and 3 different ROMs. I did keep the phone on ice to keep it cool when it was getting hit to be safe.
Thanks
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
tshuford said:
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
Click to expand...
Click to collapse
I've had some issues before regarding actions within the CWM on my d2vzw. I got rid of CWM and installed TWRP 3.0.2-0. I was then able to do much more.
I had also read somewhere that CWM is an abandoned project and TWRP is kept current and is also recommended by Cyanogenmod for all their ROM's and other flashable files.
The link for the d2vzw TWRP is https://dl.twrp.me/d2vzw/
Good luck!