So I had just gotten my Nexus 10 yesterday. Downloaded the root toolkit to root, and eventually install CM10.1 for it. However, after installing CM10.1, i realized I can make do with stock, for my own reasons. And so late last night(late enough that I should have been playing around with clockwork recovery), I somehow ended pressing format /system, thinking it was mount, as I was just playing around. Yes, I clicked yes, I had no idea what was going on. I have a nexus s, so I'm used to the recovery by now. So now I'm stuck, without any way to flash a new rom. I made a backup of my stock rom, but now I don't know how to get it back from my computer! I have no way to boot into adb, or atleast I can't figure out how. Any help is greatly appreciated.
TL;DR No rom to boot, can't access SDcard from computer to cop another one over, or restore an older back up.
Nevermind, I managed to get sideload working through adb. I was finally able to flash CM10.1 again.
Here is an instructional video that every Android user must watch:
http://www.youtube.com/watch?hl=en&...ture=player_embedded&v=wwleOote5M0&nomobile=1
jk
Related
Ok so I've done a bit of searching and asking on androidforums but nobody can figure out my an answer to my problem. Alright, first off originally the phone had android 1.5 but when sprint released the 2.1 update I did it. From there, I used regaws tutorial on rooting the official 2.1 release which worked great. Basically I was on a mission at this point, a mission to try out all the 2.1 based custom rims. I had been using the rom manager app for its ability to wipe and flash new roms without even rebooting to recovery. As you are probably aware, to do anything with rom manager, you have to have their clockwork mod recovery flashed, which is simple to do with this app. So one day I wiped and flashed a new rom, aloysius I think, and after it was trying to boot the new rom it gave me some error message and the installation failed. I think at this point I tried to restore my nandroid, which also didn't work, I'm guessing that you have to be using the same recovery you were using when you created the nandroid? No matter what I did from recovery I could not restore my nandroid, as a last ditch effort I did a factory wipe and then rebooted. I didn't think it would reboot at all, honestly I was way scared and thought that I had bricked the phone but after about 5 minutes it finished booting up. Now I don't understand why or how, but when it came to it was quite obvious, I was back at stock 2.1. I immediately look in the app tray for the superuser app and obviously it isn't there, I've been dealing with the phone as is for about a month. A couple of weeks ago I decided to get back to work, sat down at the computer and tried to root it again using the same exact method. After like 5 attempts I get the same problem, I get to the step where command prompt spells out "UNREVOKED" really big but I notice that instead of having a "$" like it shows in the picture I have a "#". At this point the guide instructs you to open the Superuser app on the app tray on the phone, sure enough, I don't have one. I have tried this probably like 7 times all with the same result. I've even tried to install that .6 update to patch whatever remnant of root access I have and go from there as I'm sure the fact I was rooted once and lost it has something to do with my failure. I've tried running RUU's many times as well and always wind up getting an error 171 USB connection error. I havent heard of anyone else having an issue like this. I'm not sure whether I posted this thread in the right place to really get help either so if this needs to be moved to development or whatever don't hesitate. I'd really appreciate anyone trying to figure this out as I am tired of running the slow stock rom but have exhausted virtually every option that I am aware of, PLEASE HELP ME!
I know everyone is probably still reading that book I posted, but once you get to the end lol please gimme some advice, i've tried everything and don't wanna live with the phone as is for the next year....
It's a little hard to read your original post, but I'll do my best to help. From the sound of it you may still have root.
I haven't had to root on stock 2.1 install, so I'm not familiar with the new method. If you get to a bash shell or terminal prompt that is a '#' rather than a '$', you still have root.
You said that you did a factory wipe on the phone. Did you RUU or did you simply wipe through recovery? Are you still able to get to the clockwork recovery?
If you can get back to your modded recovery, you're golden. I would STRONGLY recommend you flash the newest Amon_RA. http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
If you can get that far, you should just be able to wipe and flash a new ROM.
have you tried to update your sync/drivers on your computer lately?
Sent from my Hero CDMA using XDA App
Oh well I finally got it all figured out, had to rum the ruu twice back to back whole the phone was still frozen at the bootloader. From there I finally was able to re root it.
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
I would recommend reading the Droid X wiki at the Cyanogenmod website. I had some of the same issues until I followed the downgrade + root method and then installed ROM Manager and CM7 manually through recovery. Good luck!
Sent from my DROIDX using XDA App
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Don't use ROM manager and don't use dxbootstrap (unless you have usb debugging unchecked). I use d2 bootstrap always. And you will have the occasion of it going in to cwm when you boot phone back up. I dealt with it for while. And cwm should be 2502 or something like that when you're just rooted 605. Did you make a nandroid of your rooted 605 before you tried to flash liberty
? Hopefully you did. Go back to that. Then use d2 bootstrap to get in to recovery, wipe data, cache and dalvik, then select install ip from sd card, then choose zip, then scroll via volume down to the liberty file, select that and flash.
I used directions posted over at Androidforums.com under the All Things Root forum for the Dx. I had a couple of hiccups, but it was user error. I now have Liberty 3 running smoothly on my Dx. Check it out, including the guide and ROM lists.
HTH
chaz_
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Just re-flash ur phone dude. do you know how to do that? It's a pain in the butt. but it is always failsafe.
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Hi guys. I seem to have outdone myself and am now stuck with a phone that plain refuses to boot any more. Let me give you some history so you get the full story.
Not long after I got my U8800 (18 months ago, 'ish) I decided to change my ROM to MIUI because I wanted to get rid of Froyo and Huawei were being incredibly slow to update officially. I did this with minimal troubles and ran it for a long time, updating etc. as needed to be done. Then along came ICS ports and I admit it, I had to fiddle once more...
I downloaded Aurora and read up in here on how to get it on my phone. It seemed before I did anything I needed to set my phone back to the defaults I had and this involved installing Froyo then the latest stock ROM for the U8800. I did all this without hassle and then tried to get the ICS on.
I don't know if it was me, bad reading, something built into the new stock ROM or what, but I could not get the ICS ROM on my phone no matter what I tried. It seemed to have issues deciding if it was rooted or not, it said it was but then failed to work when I needed it to, plus CWM Recovery completely failed to work for me and I just kept getting the stock recovery when trying to boot into it. ROM Manager was also being a pain and kept insisting my phone was a U8160 when previously it had worked as a U8800 (I may have flashed to the U8160 and having thought this I assumed this was my mistake).
I tried various methods of getting to my cust_ folders and manually changing the recovery.img but everything I tried ran into the same "is it or isn't it rooted" problem.
At this point I gave up and stayed with the official stock ROM from Huawei for a bit.
Two days ago I decided I couldn't hack the defaults any more, my phone was slower and I missed the MIUI way of doing things. I decided to have another go!
Ok, we are up to date, thanks for reading so far if you have.
I decided to try getting to the recovery.img again by doing the pink screen and connecting to my PC, problem was when I did this nothing ever showed on my PC, so I looked for other methods.
I uninstalled ROM Manager, because it still insisted I had the wrong phone and found the app, Root Explorer, it worked! Wish I'd have found it weeks ago. I instantly had access to the folders I needed and could mount them etc to overwrite/backup my recovery.img and as I was a little worried about the rooting thing again, despite Root Explorer working I though what harm can it do to overwrite the boot.img too. I did both by copying the originals to my SD Card and pasting the new ones that I had previously placed on my SD Card through the USB connection. I used the files recommended here: http://android.modaco.com/topic/340...-and-then-some-for-the-huawei-u8800-ideos-x5/ and here: http://forum.xda-developers.com/showthread.php?p=14870348
I rebooted the phone and again failed to get into CWM Recovery, just the default Android one.
I then hunted down another recovery and found this: http://www.androidxpert.com/2011/08...k-work-mod-recovery-on-huawei-u8800-ideos-x5/
It worked! I could finally get into CWM Recovery and figured I was home free.
Not so
I then downloaded the same stockwell MIUI I had used previously as I knew that worked, his latest stable version, and dropped the zip on my SD Card. Went to install it and found that CWM Recovery refused to mount my SD Card (16 gig sandisc). Tried a couple more times because I had issues with this card before and then the card ended up corrupted or something because it just refused to work now on anything I had. This was fairly major because I had backed up to this SD Card and forgot to take the backup off and into my PC for safer storage... I know... I do have the back up of recovery and boot.img though on my PC.
It was at this point I noticed I had a boot loop but could still get into CWM Recovery.
Not panicking too much, I tried my old 4gig SD Card, it mounted! I copied the MIUI Rom across to this card, booted into recovery and selected it. It stated it was installing etc but seemed to go pretty quickly. It said it was done so I rebooted as is the norm. Boot Loop. Damnit! Tried this a couple more times, made sure I once again wiped cache, dalvik etc, all of the things it states to do on the ultimate guides etc. Nothing.
Again, still not panicking I thought, fine, I will go back to stock rom. Downloaded the correct one, dropped dload into root, booted using vol + and - and up comes the unpacking screen. Trouble is it refuses to unpack. I quickly look on the net and find that some say if you take the battery out and connect just using the USB it will install it that way, maybe it does for them but it doesn't for me, it just boot loops again.
I am now at my wits end.
I have the feeling its something to do with my changing of the boot.img and I have the original should it be that but I cannot access the insides of my phone through Windows to change anything, plus of course I can't boot the phone due to the loop to change it back using Root Explorer (otherwise it would work anyway).
Is there anything you guys can help me with?
I can install Linux if needed, I read that it lets you view the phones file system better compared to Windows and with my slight knowledge of Linux Id quite expect this but even so, I am not sure what to do.
Any advice/solutions are extremely welcome.
Sorry for the long post, figured I should give as much info as possible.
So what was the latest Huawei official firmware you had on your phone?
What version of CWM are you trying to use?
What version of the huawei official rom did you have on the phone when you tried to install aurora?
What was the last huawei stock rom you tried to install?
Try and get a 2.2 froyo stock rom and flash it using the vol+and- method. This should hopefully get your pink screen back and access to recovery and boot.img. You can then use any recovery earlier then 5.0.2.6 and install stockwells miui.
It sounds like you have a Gingerbread based official rom flashed which you would have needed to flash aurora and are dropping bits into it like boot.img, roms and recoveries which are for froyo.
If this is the case and you can still get into recovery, I would try flash another rom like sbasils miui or wipe everything and format /system and then flash aurora again.
Ok, not sure what changed but, I figured whilst I wait for a reply I may as well keep playing and try to fix it myself still. So I stick my battery back in, was out all night, plug it in the USB as I wasn't sure what juice it had left and turn it on with vol + and - down for that one last try at the default install.
It starts unpacking!
I have no idea what changed, I did nothing different bar having left the battery out all night. Can it have had something in the residual memory?
Anyway, short version. Installed the default froyo, updated to the beta gingerbread (stock and latest).
Back up everything to internal storage this time, just incase and went to superclick to see if I could root it again, it did so. Used Root Explorer to copy CWM Recovery.img over, backed up it all again using CWM to internal, rebooted, worked.
At this point I got silly again and having it all backed up a few ways now decided to try Aurora again, 2.4 this time. It works.
Again, no idea what changed but its going again and after an initial mess with the SC Card again, that works too now.
Sorry to have wasted any ones time with this, though I still really appreciate the reply even if it seems to have fixed itself.
I just wish I was sure what fixed it so It could help others who have the same issue, unfortunately I don't
great stuff, seems upgrades are just a bit hit and miss on this phone. glad it all worked out.
Hey all! I've been lurking around XDA for years for various devices. I'm good with computers but newer to Android/Linux. And I don't have much of a programming background. I have done some installing of custom ROMS on a phone of mine and even dabbling in a kitchen some. So it's not totally foreign to me.
I've been reading about custom ROMS on and off for a few months thinking about installing a custom ROM. And then actually reading and researching it the last day or two. Since we're not going to get Jelly Bean I decided finally to update to a custom Jelly Bean ROM. I am finding all the information very unorganized and very spread out. And not very comprehensive. Which is making it hard to get a good grasp of everything. Things like what SKBs are and APX mode. And exactly what processes you need to take to install which ROMS. If you need to install a kernel or it does it automatically ect. Very confusing! I thought I had figured out enough to do it.
On my A500 I had the latest Acer ICS OTA update but rooted. I want to install the CM10 Jellytime ROM. I did a factory reset. Using AfterOTA v1.09 I installed first "Bootloader Ics v3.14.8+Thor v1.7.3". Then after that I changed to "Bootloader Ics v3.14.8+Recovery Twrp v2.1.3. It seemed to work fine. I got into the bootloader. I have the Jellytime ZIP file on my external SD card. The first time I think I just clicked install, picked the ZIP and did the swipe to install. Which brings me to my big question. What is it supposed to do after that? It just went back to the Recovery boot animation and back into the recovery without seemingly doing anything. If I rebooted holding the Vol-, it would just go into Recovery and not flash anything. If I just let it boot it would boot the factory ROM. The Thor recovery did something similar.
I then did the wiping/formatting of all of the cache, factory resets and system. And when I tried to install it again basically the same results. Except now it won't boot into the factory ROM since I wiped the system. Which will also not let it connect over USB and to the AfterOTA. If I turn it on holding the Vol+ and get the boot menu and pick the fastboot it tries to do the fastboot but just hangs on the Fastboot notification.
I've been searching and reading but can't figure out if I didn't do something I should have or missed a step. Any help would be appreciated.
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
briwayjones said:
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
Click to expand...
Click to collapse
great, thanks for posting your solution