Hello
So I am a huge idiot noob and you are all going to hate me, but I've been frantically trying to get my Nexus S back into a usable state for over 6 hours and now it's 5 in the morning and really need to get some sleep..
So I tried rooting and trying out a rom for the first time on my Nexus today. I rooted and installed the rom and everything was fine but instantly realised I didn't backup the stock android that I started off with. So I tried downloading a stock version of Android and flashed that with CWM, I boot into it fine but only the 'menu' capacitive button lights up and non of the others do, anyway the capacitive buttons don't work at all so that makes navigating the system very hard. Also the calibration on the screen is now slightly warped, so I've always got to hit the screen below a button to hit that button. It's slightly weird but I think I've realised I've flashed a wrong version of stock android for my build of Nexus S.
During this time I followed a tutorial to unlock and unroot the phone as I thought everything was going to be fine. So now I have a crapped out stock android and I don't have CWM to flash anything else. I've tried flash boot and that is not working for the life of me, I can lock and unlock the bootloader but it says it 'cannot load' a recovery image for CWM when I try to install it that way, even when trying to put everything in the right folders.
Now I've got 3 different android sdk folders (as i've tried lots of tutorials and forum thread posts) in my C drive to try and get fast boot to work. Ive installed drivers for my phone but it shows up with nothing when I do adb drivers in the terminal.
I've gone and really messed up and I have a pretty much non-working phone and have no idea what to do now to get it up and running. If someone could please point me in the right direction that would be great because I'm getting so stressed over this and just wish I left everything alone.
Many thanks in advance,
Lee
I think the unroot option with a messed up system sure wasn't a good idea at all
Back on track, i'm not sure this will help you, but this is what i think you should do, and what i'd do on your situation... try following this tutorial:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
(for rooting it again)
After that and before rebooting, format the cache partition, the system, data and dalvik (in the "advanced" menu of the CWM).
Then, i'd flash a custom ROM (e.g. the MIUI -- http://miuiandroid.com/ ) and kernel (e.g. franco's kernel http://forum.xda-developers.com/showthread.php?t=1305360), just in case.
Reboot, and if that's working fine, download the Rom Manager and reboot to recovery (i have problems with getting to CWM recovery from cold boot, i think it's related to android >= 2.3.6, so i have to get there through that app...).
Do a nandroid backup there, and after that you can try messing it up again if you wish, but i think you'd be fine with that configuration, imo
Hope it helps, sorry if it doesn't
P.S.: don't give up, if you can turn on your phone and see something on the screen, it can be fixed
Thank you for your reply, I have now managed to get CWM on my phone now.
However, when I try to put Cyanogenmod or the ROM you suggested on my phone, it simply doesn't work and the install aborts, here is the error message I get..
installing update...
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") =="crespo" || getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-cm-7.1.0.1-NS-signed.zip
(status 7)
Installation aborted.
Note that in the bootloader it says my device is "herring" not "crespo". Also it is an I9023 not the I9000, not sure if this makes a difference at all. About the herring thing, I've searched up online and other people haven't had any problems installing roms on their Nexus S whether it is herring or crespo.
Many thanks in advance for any help you can give me,
Lee
Edit: I just had to update CWM! I now have Cyanogen working on my phone! This is very good, I have something working now!
I would however rather be on stock, but of course I didn't back it up. I was wondering how I would be able to do this, it seems rather complicated from looking online and wouldn't know where to begin or what files I would need for my specific phone. Any help for this would be much appreciated, thank you for pointing me in the right direction, you've helped me get my phone working now
To go back to stock, Just flash one of the roms in here in CWM, Flash your device specific ROM.
http://forum.xda-developers.com/showthread.php?t=1063664
Thank you so much, I am now back to stock the way I wanted. The reason why I got into this mess in the first place was because I wanted to try out the We Scream Ice Cream ROM, and it was too unstable for me but it was nice to see it running on the phone and then everything went wrong.
At least I have learnt my lesson not to touch this stuff again! Thanks a lot for the help guys
No problem, good to see that you managed to fix your phone!
Related
First.. I want to say hello and that i've been reading around these forums for quite a while since I got my Droid about a year ago. I haven't posted anything till now.. but that's only because everyone else usually get's the answers typed faster than me. lol
On to the problem... I think I screwed up. I JUST bought this thing today. I got a little too excited about getting this tablet rooted and might have jumped the gun a little. I used the apk that has been around to root. No problems there. I got ROM Manager loaded... and I ended up flashing the newest recovery from there before realizing that everyone else says to use something else.
So... at this point, i'm unable to reboot into recovery at all. It starts up, acts like it's about to, and then just reboots again into the OS instead. Is there a way to fix this and get it on the correct recovery image or have I totally screwed myself over? Maybe through ADB? I can only tolerate this horrid TnT OS for so long. Took me 20 minutes to get it to update without a FC... Browser, weather, calendar, and a bunch of other stuff FC on me when I tried starting.. Fortunately, those issues are less frequent with the update, but still not working keeping.
I need some "stock(CyanogenMod)" Froyo goodness.. lol I can't have my year and a half old phone outclass this tablet for too long. If anyone can offer any help on this, I would greatly appreciate it.
The good news is you are still booting into the OS, so I doubt you've screwed anything up too bad. Most likely Clockwork Mod just never flashed so you are still running with the gimpy stock recovery and it's puking on the update.zip file you have on your internal sd card for some reason.
First suggestion is get a copy of Clockwork Mod 0.8 and try installing it. The instructions here are geared toward installing from an external from an external MicroSD card: http://forum.xda-developers.com/showthread.php?t=865245 I am not certain why they say that's the only way to do it, since I never did it that way.
I just downloaded this: http://www.mediafire.com/?dvleg4oatkfxm7w and stuck the update.zip and recovery folder into my /sdcard directory, then turned my tablet off, then held down Vol+ and turned it back on. Clockwork Mod should install itself and boots into Clockwork Mod, and that was that.
I never used ROM Manager at all on my G Tablet, so I can't speak to doing anything that way, but I would stick with the tried and true methods at least until you have Clockwork Mod running.
If that fails and you really can't get any recovery working, maybe something did get botched and you might need to use nvflash to fix it, but I doubt it.
Once you get Clockwork Mod running properly, just copy over the update.zip for TNT Lite or Vegan ROM, flash, and wipe data, then you should be good to go.
Worked perfectly and entirely from the tablet! I installed CM6.1 and I'm a bit upset at the lack way it looks, but then, its packed for smaller screens, so I understand. Thank you for the quick reply. I'm off to try TnT Lite now.
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
I hope I am not wasting anyones time by posting something that may be and I hope is a simple fix, but I have a problem with my Verizon Xoom, a 602 (without the 4g upgrade- don't even have verizon service) that I can't figure out- and it's not for lack of searching. I have been rooting my devices and running custom Roms since my HTC Touch, (a big thank you to all of you here at xda for all the knowledge and instruction I have been able to leach) but I am very much still a noob with only the vaguest since of how Linux, android or the devices themselves actually work- and that is especially true of my xoom with all its post release changes in storage and whatnot since I bought mine, so please don't flame me to hard if this is just my ignorance- I promise you I'm not just being lazy, I just can't figure this one out. I have been running EOS for a while now without a hitch, and recently installed 150 when it became available. everything was fine until a couple of days ago when it started freezing on unlock which just took turning the screen off and back on to fix, but every app started crashing, some periodically and some such as android.process.acore, browser, and google play that won't open at all. I use Team Win's recovery and tried a wipe and reinstall, but same thing. When I try to fix permissions I get a failure with the message "E: Unable to chown '/data/app/com.google.android.youtube-2.apk' 1000 1000". Also when I try to wipe internal storage I noticed everything was still there even though my recovery was saying I had a successful wipe. I switched to clockworkmod recovery and tried to use eraseData file in the folder to wipe the old way but that didn't seem to work either (which I'm not even sure I did right but figured I better get some advice first anyway), and when I tried to flash EOS 3 stable it won't get past the EOS boot animation at all. If anybody out there knows whats up and has the time to point me in the right direction it would greatly appreciated... Thanks
Wowzers! When all else fails ... unroot / re-root. That will wipe everything.
okay, where to start.
I've a Nexus 7, and im running P.A 2.54, with twrp.
i got an article from one of my news apps about getting better volume for my nex 7 BeatsLouder, followed the link and downloaded, didn't do any information gathering and consequently i believe i've flashed the beatslouder for android 4.2 it was BeatsLouder v3b8 i believe.
Either way now, my tablet just hangs at the P.A splash screen/boot logo.
needless to say, with my lack of forward planning into researching what i was flashing i didnt make a back up either..
Are there any solutions that don't even a fresh wipe?
edit: so i had a back up in twrp, when i had the forethought to do a backup prior to installing something unknown, however i'm not certain if the back up is of data or system files or both, anyway to find out? the restoring of the back up seemed to happen almost instantaneously, making me think it didnt work?
oh, also i made a backup of everything (in its current broken state) in the hopes i might be able to recover my data?
would love some responses, anything to get the ball rolling
Try dirty flash your ROM then gapps in recovery again. No wipe needed.
For the last year or so, I was using this rom, and I loved it, but I was curious to try the new KitKat version so I tried updating, and kept getting getting a recursive error when trying to flash the d2lte(supposedly all the S3 roms are unified now?) KitKat version. So after doing this, after /system was cleared, but I couldn't flash back to the backup I had made before hand because I was getting an md5 mismatch.
In response, I used Odin to flash Root66. Phone works, but its seriously lacking in terms of bells and whistles of a custom ROM. It says its rooted, but a lot of root apps would fail the permission test. No prompt was given. I used towelroot and started getting root access, but I still can't update CWM or Superuser binaries. Trying to flash any other ROM leads me to an infinite boot screen, forcing me to flash Root66 again.
I tried this as well, but it seemed to yield the same results.
So, I really would like get off Root66, but I'm at a loss as to how. Anyone have any ideas? I'm sure the answer is staring me in the face in one of those threads I linked, but I'd really appreciate it if someone could (at least try to) point me in the right direction. Apologizing in advance if this question has been asked before.
Thanks.