So I have a nandroid backup i made of my stock install just before going to cm9. Due to the impending time limit of .03 I wanted to get back to stock so I could follow the same instructions to install .04. However, I'm not sure where I can put my nandroid backup that CWM will be able to see it. I dont think CWM can restore from internal memory, so i was thinking hot-swapping another SD with the backup on it, but I wanna make sure thats safe before I do it. Thanks in advance.
1. You don't need to return to stock to flash a new rom. You can just flash right on top of whatever you have installed new (presumably cm9 .03 based on what you've said).
2. Nandroid backups are stored at /mnt/sdcard/clockworkmod/backup/[folderwithbackupinit]
3. Clockworkmod can restore from internal. I suggest flashing clockworkmod to internal if you haven't already. You can use indirect's latest app for this. Again, you can use the same path nomenclature for the backup. Except for internal it will be at /mnt/emmc/clockworkmod/backup.
4. My personal suggestion (and what I am doing this very instant) is download the new version of cm9, make a nandroid backup of your current cm9 setup and then flash the new version. There is no need to do a data wipe as it is simply an update to the same rom. If/when they add the 3.0 kernel to it (or make any other "major" changes) however, it will probably be a good idea to do a data wipe.
Thanks a ton, I was under the impressions that flashing CWM to internal was a no no ATM on the 8gb NT. I have another question, often times when I burn the recovery image to my sdcard and go to boot from it, I get an error to like "Unable to boot-bad boot magic" or something, any clue as to the issue with that? Regardless youre post was a ton of help.
I'm guessing you installed CM9 via the version of cwm from sdcard? If you want to go internal, you can use indirect's new app to flash now, it works with both 8GB and 16GB.
I don't know about that error but it sounds like the image is just bad. I'd suggest reimaging the card. Though, once you have cwm recovery running internal, it will be rather irrelevant.
---------- Post added at 12:24 AM ---------- Previous post was at 12:17 AM ----------
Don't forget to reinstall gapps as well, if you are using them, as they will be gone after flashing the update.
Awesome, internal cwm will take a lot of the hassle out of all this. This is just an app I can run from CM9 right? Or are there some other instructions im missing?
Download the app, check the md5 hash (there are apps on the play store you can get to do this), install the app if the md5 is good, run the app, select flash cwm (probably have to give superuser access) and then you should be able to boot into recovery.
I don't recommend booting to recovery from the app though. I would manually power off, power back on, hold n to get to the menu in cyanoboot then go down to boot recovery in the menu.
Gah, got excited a bit too quick. Got the recovery to flash, appeared fine, when I try to make a nandroid backup CWM tells me it can mount backup path. Didnt get any errors or anything while flashing the recovery, boots into the CWM fine, just can seem to mount the SDCard.
Did you try powering off and accessing recovery manually via cyanoboot?
Actually I'm not on CM9 anymore, tried using the CWM Sdcard to install .04 got stuck in a boot loop so it factory resetted. Rooted using wertz 8gb/16gb card and loaded the flasher apk. Tried accesing CWM by holding Power+N but it doesnt seem to want to boot into CWM. Atleast not without using the flasher app to reboot. Oop, just had to take the SD out and reinsert, herp derp.
So you got into cwm internal then with sd mounted?
Yes CWM appears to be working fine, I just cant seem to access it without using the flasher app to boot to it. Kinda paranoid about trying to install CM9 and being locked out of CWM without using the SDcard and (I guess) starting over. I'm just supposed to hold Power+N from off, then let go of power once the black screen pops up right?
Power off. Power on, hold N when you get to black screen (something like that anyway, I haven't done it like that in a long time though, as I am on cm9).
You should not worry though for cm9. With cm9 comes cyanoboot. When you boot up you will be presented with the option to "hold n for menu." Doing so will bring you to a menu where you can select to boot into "emmc recovery," i.e. the internal recovery.
With that said, as a fail safe, I do personally keep a 2gb micro sdcard with cwm flashed to it ready to use and restore a backup, should I need it.
I tried installing CM9 .04 before using a CWM SDcard and it started bootlooping(though it still gave me access to cyanoboot), thus me being back at stock at all. Even if the install borks again and I get a loop I should still have access to Cyanoboot?
I'm not sure, but I don't believe so.
I would try to reflash and make sure to wipe data/cache.
Tried going back to stock recovery, rebooting, reinstalling CWM, still cant seem to boot into it from power off. If i go into CWM and reset then quickly press power and N then let go of power, it reboots into CWM again. Think I may just try and reinstall CM9.
Yeah it can definitely be a bit finicky. If you were running cm9 as your daily though, I would do as you said and continue to push forward with that. Once you have it working, you won't have to worry about the magic button combo.
I got CM9 .03 installed and working just fine, tested booting into CWM with cyanoboot just to be sure, went perfect. Decided to install .04, and I get bootloops, thinking something that was changed with .04 isnt working atm with the 8gb NT.
Well you'll need .04 as .03 will expire. Have you tried wiping data?
My process was install .03 wipe data/factory reset, checked it worked fine, tried .04 wiped data/factory reset boot loop. Just tried it again without installing gapps just in case and still get resets after the cyanoboot screen. I restored and am back on rooted stock atm.
You should really make a backup of cm9 .03 so you don't have to keep restoring to stock
On that note, I'm not sure. I would follow up in the thread for that rom and see what others with the 8gb say.
You might consider redownloading the new version as you could just have a bad download.
Related
Guys,
We all know you have to pay to play.....
Used rom manager to restore my 2.1 backup I made before I flashed to bionix 1.3.1.
Just wanted to learn how to do the restore should I run into issues.
Everything went fine, I say it copying the files, etc etc. Didn't see any errors, phone rebooted on it's on but never came on fully.
Phone has been stuck on "VIBRANT" logo on the screen for quite a while.
What's the steps to get my phone working again?
I hope it's not a big UGH.
EDIT: I just restarted phone and with the two volume buttons depressed and after vibrant flash I hit the home button and somehow got into clockwork recovery mode. trying to restore the bionix 1.3.1, will report back shortly
EDIT: restore worked with bionix and is back up and running.
Why did the bionix restore work but not my back up for 2.1????? Is this because the original restore was performed from rom manager and second restore was performed from clockwork recovery mode?????
Did I luckily avoid a brick situation?
Doesn't back up your kernel. So you restored a 2.1 rom running a 2.2 kernel =bootloop
Sent from my SGH-T959 using XDA App
odin or reflash bionix if its still on your sd card then put a 2.1 kernel on then flash that then restore ??
So as per my OP I restored bionix and all worked fine.
What was the point of backup up my 2.1 version if I can't restore back to it since the kernels are different???
If I want to restore my 2.1 version, via clockwork recovery, what's the process. Is there a way to delete the kernel or wipe it first if I need to go back to 2.1?
I know the odin way, but the clockwork recovery console is so easy and convenient?
download any 2.1 kernel and put it on your internal sd . After you have your kernel just restore your nandroid and before rebooting flash the 2.1 kernel .
I'm new to the whole kernel thing to be honest. By putting it on the internal SD card, what does that accomplish, I'm sure it has to get installed somehow, no?
Another quick question, why do some roms require to clear davlik and cache and some don't?
Is it something that can be done regardless if a rom directions say to do it?
Just getting more noob stuff out of the way.
sometimes they include that in the rom so u dont have to but as a rule always wipe dalvik and cache and data.
Excellent, thank you
kero4 said:
I'm new to the whole kernel thing to be honest. By putting it on the internal SD card, what does that accomplish, I'm sure it has to get installed somehow, no?
Another quick question, why do some roms require to clear davlik and cache and some don't?
Is it something that can be done regardless if a rom directions say to do it?
Just getting more noob stuff out of the way.
Click to expand...
Click to collapse
Like I said flash the 2.1 kernel. You could download a flashable zip. Place it on your sd then after restoring your nandroid backup flash the kernel by selecting "install zip from sd" in recovery.
Sent from my SGH-T959 using XDA App
Ok so im realtively new to working on android phones, just got an atrix, rooted fine, superuser and all bootloader unlocked and stuff, booted into clockwork mod for the first time.
When i did this i clicked on "install update from SD card", chose Greyblur as a test rom cause i seen it on the guide to flash roms, so i followed what they did exacly, when i installed it, i went straight to the "reboot" button, clicked reboot and when it did it wont go past the Dual Core Technology screen, please help me android atrix veterans! i dont have insurance and ive been searching for about a week now, im really scared that im royally screwed, i bought accessories for the phone and want to use them on a non-soft bricked phone!
Please and thanks!
1. Install Romracer's cwm
2. Greyblur is a pseudo-rom, try any rom at the top in the development forum instead. I'm using Nottach's Dark Side right now, it's crazy fast and is very stable.
i have cwm, the problem is i just cant get booted into it without getting on my phone, and launching it via an app i have, is there a way to get on the CWM recovery without an app? cause when i click android recovery it takes me to the stock recovery
Ok, sounds like you installed Tenfar's OLD clockwork recovery, which was only a 'bootstrap' recovery.
What you need to do is, try getting into recovery by doing this:
power off.
press and hold power and vol down buttons until you see 'fastboot' appear on screen. press vol down 7 times until you see 'android recovery' and press vol up key.
This may or may NOT work since you installed the boostrap recovery from Tenfar.
If it DOES work. Do a factory reset. and reboot. See if its fixed.
If not do this:
Download RomRacers Recovery and flash via Fastboot
then do the same button commands to get into Recovery and try to factory reset again.
If none of that works, PM me with your information, such as Android version (froyo, gingerbread, etc etc) and I'll get you sorted.
how do i use fastboot? do i need a program or something on my computer? never touched fastboot before i dont think
Hey i have a similar problem my phone was rooted and an unlocked bootloader using the automatic unlocker and i went to install a rom i believe it was called unofficial aroma rom by th3 bill i went to install it from tenfars cwm and i wiped every thing first and when i went to install the rom it finished in like 5 seconds i pretty new to all this but i thought something was up when it rebooted it wont go past the dual core screen so i went and looked around and found that it could be a kernel issue or a recovery be outdated issue since when i tried to restore my back up on tenfars it still wouldn't go past the dual core screen i then put olmypus cwm on it to see if that wont fix it but i guess that made it worse cus now when i went to go restore I it says error mismatch mdsum so yeah i looked around and read that i can return to stock by flashing a fruitcake but before i did that i thought i should make sure first.hope you guys can help
daftvirus7749 said:
Ok so im realtively new to working on android phones, just got an atrix, rooted fine, superuser and all bootloader unlocked and stuff, booted into clockwork mod for the first time.
When i did this i clicked on "install update from SD card", chose Greyblur as a test rom cause i seen it on the guide to flash roms, so i followed what they did exacly, when i installed it, i went straight to the "reboot" button, clicked reboot and when it did it wont go past the Dual Core Technology screen, please help me android atrix veterans! i dont have insurance and ive been searching for about a week now, im really scared that im royally screwed, i bought accessories for the phone and want to use them on a non-soft bricked phone!
Please and thanks!
Click to expand...
Click to collapse
did you reaaly install it? i mean you should instead select install zip from sd card (not install update).....and do a wipe to factory it helps.....
hope it helps
htchd2fix said:
did you reaaly install it? i mean you should instead select install zip from sd card (not install update).....and do a wipe to factory it helps.....
hope it helps
Click to expand...
Click to collapse
i mean i dont know since it was my first rom but it took like 5 secs and. Did choose install from sd card and i wiped delvik cache,and data.
no install take 5secs. download again your rom in pc
go in recovery
wipe factry reset
go in mount
mount usb
transfer your rom torugh usb into phone sd card ext
when done unmount
go back to install zip from sd card
select your rom
when done reboot
htchd2fix said:
no install take 5secs. download again your rom in pc
go in recovery
wipe factry reset
go in mount
mount usb
transfer your rom torugh usb into phone sd card ext
when done unmount
go back to install zip from sd card
select your rom
when done reboot
Click to expand...
Click to collapse
alright so i did what you said and I'm just guessing the rom just doesnt work for my phone cuz it installed in 5 secs again and i installed a previous version of the rom and it didn't work as well it took me to a rom setup screen like asking me what i want to wipe and what memory to use and then installed pretty quick as well and it didn't boot past the dual core i then whent ahead and flashed the fruit cake rom which is pure stock 1.4.1 and now my phone works...i now have a couple questions do you think it would be smart to back up this rom and keep it as my back up even though its not my real original stock rom? my original one doesn't work it gets a md5 mismatch error or something and doesn't restore.i read some where that tenfars recovery doesnt back u roms properly and that might me why because that what i backed up on should i install rom racer recovery i read that that one is specifically for the atrix if should can you explain how to do that?lastly i stil want to put a custom rom on my phone because the whole reason i did this was because i found out i wasn't getting ics but
each of the two roms i installed never booted up and the only one that worked was the fruit cake do you know a good stable rom to use preferably ics or jellybean?i was also looking into the neutrino v2.9 rom but the linked is down and you need rom racer to install if you cant answer anything i asked please do thanks so far though
daftvirus7749 said:
Ok so im realtively new to working on android phones, just got an atrix, rooted fine, superuser and all bootloader unlocked and stuff, booted into clockwork mod for the first time.
When i did this i clicked on "install update from SD card", chose Greyblur as a test rom cause i seen it on the guide to flash roms, so i followed what they did exacly, when i installed it, i went straight to the "reboot" button, clicked reboot and when it did it wont go past the Dual Core Technology screen, please help me android atrix veterans! i dont have insurance and ive been searching for about a week now, im really scared that im royally screwed, i bought accessories for the phone and want to use them on a non-soft bricked phone!
Please and thanks!
Click to expand...
Click to collapse
go back into recovery by pressing volume down while it's turning on. Then mount sd storage (from recovery) and past into your sdcard an other better rom).Unmount when transfer is complete. WIPE ALL: factory reset, cache and dalvik cache. Install the zip from sdcard. Enjoy
Try formatting data and cache. Format options should be under advanced - mount menu. After formatting your data and cache go to install zip from sdcard and install the new rom. Do wipe data, cache and dalvik cache.
Sent from my Atrix using xda-developers app
This happened to me too, I flashed an up to date cwm and flashed the JB ROM again and that solved my issue, its a strange one!
Sent from my MB860 using xda app-developers app
Been there done that
Been there done that. I was stuck at the M logo for days about a week ago. Couldn't figure it out. Check out my thread here http://forum.xda-developers.com/showthread.php?t=1936337 for how I solved it with help from this forum.
Good luck, I am on epinters latest and greatest CM10 now and it is grand!
So my Evo LTE is running 2.13.651.1, and is on what I understand to be the newest HBOOT (1.19). Naturally, I have S-ON as a result. This is my first Android device, and I've had it about a week since switching from an iOS device. I have root and the Teamwin recovery, which I used to backup the phone. I understand this is called a nandroid backup?
I plan to flash Cyanogenmod 10, in fact I already tried once. It resulted in a bootloop, and I restored from the nandroid backup. I have since learned I need to flash the boot.img from CM10 using fastboot, Flash Image GUI, or any other alternative. Once I do this, if I want to go back to Sense 4.1 like I have currently, how would I do so? Once I flash the boot.img from CM10, I won't simply be able to restore to my nandroid from teamwin, will I? I assume that if I tried to restore from the nandroid, due to S-ON I would be unable to write to the boot partition from a recovery utility and I would be left in another bootloop. How can I get a boot.img corresponding to my stock Sense 4.1 rom in the event that I want to revert to stock?
In the folder containing my nandroid backup, I see a file called boot.emmc.win and a boot.emmc.win.md5. I understand what the MD5 is for, but is the boot.emmc.win what I will need to undo the effect of flashing CM10's boot.img? If so, how would I use it (I do not recognize that file extension, and Flash Image GUI does not seem to like it either)? If not, where would I get something that will work?
I've done several searches here and on other forums, but I can't seem to find what I need. If someone has already answered this question, could you simply point me in the direction of that thread?
Thanks in advance,
Kristoffer
I have yet to restore a back up but to avoid any issues I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
When you reboot, do not boot to recovery, the boot partition has been replaced with a temporary twrp and all you need to do is reboot normally
om4 said:
I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
Click to expand...
Click to collapse
Once I flash CM and its boot, the boot for my Sense 4.1 will have been overwritten, no? I opened Dumlock in my Sense rom (as I have not yet flashed CM successfully), and it gives me a warning to make a backup of boot PRIOR to using the app, then just under that says the app will make a backup of the boot. If I go ahead and run Dumlock, I'm not entirely sure what is going to happen. It seems that it will move my recovery (TeamWin at the moment) onto the boot partition? If this is the case, why is this something that needs to be done? Does moving the recovery onto the boot partition allow the recovery to write to the boot without S-OFF, thereby allowing a simple restore of the nandroid to replace my rom AND boot at the same time, as if I were restoring with S-OFF? Sorry if I'm not making sense, but I don't really know what I'm talking about here, and thats the only thing that makes sense to me.
I see a button in Dumlock that says "restore original boot." If I install CM and the CM boot, will pushing this "restore original boot" button give me back the boot setup for the stock Sense rom? If it does, then I could just push that button, let it do its thing, and then restore my Sense nandroid with my recovery, right?
Thanks for your help, and quick response.
Install HTC dumlock
Open the app and back up boot
Once back up is successful, press execute
Once the phone restarts it will only boot to twrp, you then go to dumlock menu again and restore boot
Now flash a Rom or restore back up and reboot
Sorry to sound ignorant, but will this method will restore the stock boot regardless of what rom/boot combination I'm currently running? Or is this creating a backup of the currently installed boot, and saving it somewhere for future use? Specifically, do I want to follow this procedure before I upgrade to CM so I have a backup of the current boot, or is this something I want to do if/when I want to go back from CM to Sense that will magically put the boot back how it was from the factory?
Yes, its a workaround that gives access to boot partition and will let you flash normally, I would only use it for stuff like nandroids rather normally flashing because it writes to boot 3 times. It's a lot of unnecessary wear and tear
Awesome, thanks alot for your help. I'm excited to go and try my CM10 rom, now I know how to get back to stock if I don't like it.
Thanks again,
Kristoffer
Hmm. Now I don't know what I've screwed up. I flashed the boot.img from the CM10 zip using Flash Image GUI, then rebooted to recovery and wiped the System partition and cleared dalvik/cache. Then I flashed the CM10 zip using twrp, cleared dalvik/cache, and rebooted. Now, I'm stuck at the CM boot animation again, just like last time. This does not seem terribly complicated, and I don't know what I've done wrong.
I understand twrp cannot flash the boot due to S-ON, but I thought flashing the boot from inside my Sense rom using Flash Image GUI would fix the problem. I restored the Sense nandroid like before, rebooted, and then I got the Recovery boot logo (htc logo, with red text underneath). After maybe a minute, that went away, and I got a Sprint logo and then the normal boot screen with only an HTC logo. The phone then restarted, and this process repeated several times. So, apparently whatever I did to the boot sector with Flash Image GUI wreaked whatever was there before, and failed to replace it with something that would play nice with CM.
A factory reset won't fix the boot, will it? All it will do is overwrite my system partition and internal sd with the default files, and I still won't be able to boot. Any idea what I've screwed up, and how I can fix it?
EDIT:
I reflashed the CM10 zip, and it still gets stuck at the CM boot logo (spinning blue thing). What are the chances my CM10 download is corrupt? Is it worth trying to redownload it, reflash boot with fastboot, then move the new zip to the phone and flash that?
What version of twrp are you using, some people have had issues with the older 2.1.8
Ok, progress. I'm on twrp 2.2.1. I wiped everything again (wiped cache and dalvik, Factory Reset, and then wiped System) and reflashed CM10. It booted this time, so I assume the boot partition is fine. Apparently I'm the retard that can't understand a point-and-click system and follow simple directions
Once it boots, however, I instantly see an error "Unfortunately, the process com.android.phone has stopped." Once I click Ok, the error will either pop back up immediately, or wait for an indefinite period and them come back. Possibly this is the result of the CM10 release not being entirely stable as of yet, I don't know.
But thanks again, your help and your fantastic Don't Panic post together fixed the problem. I think I can figure out what is going on with this error popup and fix it. So long as I have voice service in the interim, which I do, all is well in the world.
It's normal, it pops up when you lose signal, its a bug but its technically a feature. If the phone loses signal, normally android is supposed to prompt you so you are aware. I think its for debugging purposes, normally this is disabled. Not sure if its really a bug in cm or they just haven't gotten around to disabling it, but its normal. It's not a real priority either since it doesn't adversly affect the phone
Hmm. This just gets better and better. So CM10 ran nicely for awhile, then last night I rebooted the phone and the internal SD card failed to mount. Both twrp and the actual OS cannot get it to mount properly. Is this something I broke, or does it sometimes occur at random? I read the following, but I don't quite know where to go with it.
om4 said:
You're card is beyond a simple reformat, the physical address linking the card and or entire card is corrupt. Don't panic, you have to start clean. Back up the info on you external or remove it, make sure you have a ROM available on your PC. Go into recovery and repartition your phone, this will wipe all memory. You then load up a working ROM (a bad back up may be responsible or just reintroduce the problem), after you have flashed the ROM (HBOOT 1.15+ must fastboot kernel, unless S-OFF) go ahead and boot into android and restore your apps.
Click to expand...
Click to collapse
Repartitioning seems simple enough; twrp> advanced >partition SD card>swipe (leaving all settings default).
After that, I can flash the new rom and boot using fastboot from my PC, right? I'm confident that my nandroid of the stock rom is clean, because I didn't develop this problem until after I had been using CM10 for awhile. Could I use fastboot to flash the boot, data, and system from the nandroid, and be good to go? If not, is the most current file avalible to download at http://stockroms.net/file/HTCEvo4GLTE/RUU? the appropriate file I would need to restore the phone to its stock unrooted state.?
Also, none of my nandroid files have a .img file extension. Is this normal? It has the normal .md5 files, but everything else has a .win extention. I've never heard of this one. My boot, for example, seems to be backed up as boot.emmc.win, with a boot.emmc.win.md5 corresponding to it. Cache, data, and system backups are named <option>.ext4.win. Does ext4 has something to do with the filesystem of the backed up partition? If this is the case, what is a .emmc? Can I flash these files with their strange (to me, at least) extensions using fastboot as if they were all .img files?
I can't imagine any of this is really as complicated as it seems. I've used a PC and a jailbroken iDevice extensively, and never managed to break something I couldn't fix. I guess Android just doesn't like me, or something.
Thanks again for all your help.
EDIT:
Apparently physically removing the external SD from the phone allowed me to mount the internal SD as a USB device. The phone still refused to allow me to read/write data to the memory, but somehow managed to allow my PC to see it. I formatted the internal SD to fat32 (one of the limited options) using Windows, and rebooted the phone to recovery. Now, it suddenly can detect its internal SD. I was able to wipe everything, and restore my Cyanogen backup and the SD card now works again. Weird...
Since I didn't have to repartition anything, was the "physical address linking the card and or entire card" corrupt, or did I have some other issue? Also, I'm still curious about my above question pertaining to file extensions and restoring a nandroid via fastboot.
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.
Hi everyone, I have a problem with my phone.
It is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as what the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go", expecting that it would work. It said "Rebooting..." and booted to recovery mode, so I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. And, this is where I discovered that CWM has a rainbow color mode. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted to Recovery Mode.
I tried . . .
Odin, but since it boots only to recovery, Odin isn't detecting it.
Wiped the data, cache partition, and Dalvik cache. Then restore.
Can this be fixed? I badly need help.
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Any inputs will be very much appreciated. Thanks.
No intention of giving the "Rashr" app a bad name. I just didn't know how to use it.
Endroyed said:
My device is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and I got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go" with expecting that it would work. It said "Rebooting..." and it booted to recovery mode. And I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted into Recovery Mode. Can this be fixed?
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Click to expand...
Click to collapse
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Cheers!
manojkumar8552 said:
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Click to expand...
Click to collapse
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Finally fixed it!
What I did:
1) Flashed the stock Recovery. I was surprised it was able to boot to Android cause I was thinking that the zip is only the stock recovery. It had errors though. Home Screen won't appear or load.
2) When rebooted, it got stuck in SAMSUNG boot animation, but it was all good cause Odin was still able to detect it which means it can still be rooted. So . . .
3) Flashed CWM Recovery v6.0.3.6
3) Wiped data, cache partition, and Dalvik cache.
4) Restored the backup.
Endroyed said:
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Click to expand...
Click to collapse
No Problems Buddy !!!
Step by step getting all f,,,, Fundas of Android soon