Related
Bootloader version I9020xxka3
Baseband version I9020xxkd1
Lock State - Unlocked
I followed the steps given on XDA forum to root my phone I was able to unlock the boot loader. But that's it. It doesn't go beyond it.
After selecting recovery, it did reboot but got the google screen with unlock icon.
Then splashed a installer screen, as if phone wants to install something and couldn't find it. Screen splashes an Exclamatory mark with in a triangle.
Now when I boot my phone it doesnot go beyond the google screen.
We all know, a lot of people have been facing this issue but how do we resolve it?
Is my phone useless or is there a way out? If we have genius devs who can rewrite the android platform I'm sure some dev can find a fix to this also.
I couldn't find a solution anywhere. But I brought my phone back to life.
Before you think of a root or ROM mod make a Nandroid back up.
SO here's the deal.
Why would it not work for me or you when root works for entire world?
It's sweet and simple, files we used were corrupted or USB drivers we are using, just don't fit.
So I looked around for best version of files we need like recovery.img or boot.img and repeated the process. If files are in good shape, it will work second time.
It's important you use same USD drivers which you used to find your way to get bricked else you'll keep getting "<Waiting for device>"
If nothing works (which I doubt) adb programming can push back the soul into the phone.
Heck, it ain't I-Phone ---- It's Opensource. Android doesn't die.
Hope it makes sense to a lot of people who be in a similar situation.
So, this is what has happened so far:
I googled for a small and easy to follow guide to unlock my phone so that I can later on install a custom rom. I followed the steps provided here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
What I didn't notice on the first place was the "UPDATE: DO NOT FOLLOW THIS GUIDE INSTEAD Please see new root method which works on all Nexus S and Nexus S 4G!" link. Don't ask why - really don't know.
The result was having my Nexus S stuck on a screen that shows Google logo on the middle and an unlocked padlock on the bottom.
It seemed, or to be exact, I figured out that, the problem was the .img file mentioned on some point in the middle of this.. tutorial.
So, I decided to follow the newer guide that can be found here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Although all went well (didn't have to go all over the same processes up to the .img installatin point), I ended up with the same screen that shows Google logo on the middle and an unlocked padlock on the bottom.
I figured out that I could just install a rom at this point, and decided that I should go back to stock. So, I followed this guide here:
http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
But, when I choose to install the .zip file, I get this error:
assert failed: "getprop ("ro.product.device") == "crespo" || "getprop ("ro.product.device") == "crespo"
E: Error in /sdcard/i9020t_i9023.zip
(status 7)
Installation aborded
..let me add to this point that I have bought my Nexus S from EU, it is an i9023. Let me also add that all I wanted is to flash an ICS rom and I think I have ended with a f****d device I don't know what to do with!
Any help, really, would be so much appreciated since I need to use this phone. I have a backup for calls etc but I need some smartphone features!
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
nickmv said:
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
Click to expand...
Click to collapse
Yes, I can enter this menu - there already. My model is an i9023GSM.
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
nickmv said:
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
Click to expand...
Click to collapse
You gave me the good news so, thank you for that. Now, I should follow this guide and come back in case I have a problem.
As far as the rom, I wanted to flash an ICS since I cannot wait any longer for Google to release the official update. But right now, anything that can get my device up and running would be really good!
Edit: nvm. >_<
kijp15 said:
Why don't you just use shabby's one click root. Simple & much easier. Saves all sorts of troubles.
Click to expand...
Click to collapse
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
nickmv said:
but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
Click to expand...
Click to collapse
OK, stuck already. On Part 2 what I understand is that I have to open the CMD and copy-paste the path to the "tools" folder? Because this is what I do, and after - since this is what I have understand - I type "fastboot oem unlock" and I get "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
What do I do wrong?
EDIT:
Tottaly stuck on Part 2. It seems that there is no fastboot.exe file inside "tools" folder. I don't think the problem is something else - I'm sure I give the right commands since I tryied for fun another folder I have with fastboot.exe inside and it worked - to be exact it just gave me a FAILED messsage since device is already unlocked. Plus, regarding Part 3, Step 1, the first file for download is missing so I used the second link and downloaded 5023-cyan file. Hope this was a right move to do.
EDIT 2:
Ok, here is the story so far: I followed the guide given step by step. The USB drivers has been installed correctly so the device can be connected to the PC.
In the "tools" folder there was no such fastboot.exe file so I manually added one that I've found on the newer guide given on the 1st post. The unlocking process is failing because the device is already unlocked.
I did manage to install after this, the 5023-cyan.img file since this is the only link working from Part 3, Step 1. This gone well too!
Now, I couldn't go on with Part 4, I mean, I could not install the .zip file as it describes so through recovery mode I installed the .zip file succesfully (confirmation message to Nexus S screen).
I reboot and still get the same Google logo on the middle and an unlocked padlock on the bottom.
I cannot understand what I do so wrong? Oh, I'm so disappointed..
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
http://forum.xda-developers.com/showthread.php?t=1063664 or use ROM manager and select Stock ROM (you should then receive OTA upgrades to 2.3.6).
On the latter: You colud just back up different ROMs and switch between them using CW.
skatastamoutrasas said:
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
Click to expand...
Click to collapse
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
mixtapes08 said:
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
Click to expand...
Click to collapse
Can you give me a CM9 kangs link since as new here, I'm kinda lost?
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
skatastamoutrasas said:
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
Click to expand...
Click to collapse
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
kijp15 said:
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
Click to expand...
Click to collapse
Worked just fine! Thank you!
skatastamoutrasas said:
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
Click to expand...
Click to collapse
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
nickmv said:
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
Click to expand...
Click to collapse
It did worth the hassle, that's for sure. Now I think it's so easy to unlock a Nexus plus I now have a little more knowledge regarding Android .
I will stick with CM 2.3.7 as it looks just fine. I don't care about warranty, I don't think I will ever need the official service for a software issue. Now I have to re-install my apps, re-sync my accounts and setup the phone the way I want it. It will take a little more time.
But I'm glad that I pulled this through - with your help of course! Guys, you rock!
I wish that I'll be as helpful as you at the near future.
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
MAKE SURE THAT YOU HAVE CLOCKWORKMOD PERMANENTLY INSTALLED BEFORE DOING THIS. It saves time if you mess up. Also, make sure you get the latest gapps HERE
Instructions:
1. Go to clockwork recovery
2. Select data/factory reset/wipe
3. Select clear cache as well
4. Adv Mounts and Storage > wipe /system (note, this wipes android off the phone. It's a good idea since youre going from ver 2.x to 4.x)
5. Choose "flash from zip" (or whatever it's called.....NOT flash from update.zip)
6. Flash the cm9 update file first, then flash the kernel of your choice, then flash the gapps file.
7. Back out of the menu and select reboot.
Take note though, that the new ICS OS has incompatibilities with certain apps while GPU rendering is turned on, etc. It'll prob reboot on you sometimes, etc. For the most part it's stable, but that's completely subjective.
If you do run ICS, make sure you turn on GPU rendering in Dev Options. It takes full advantage of the GPU for UI animations, etc. Sometimes there's a stray app here and there that doesnt play nice, and you'll notice if the window looks really tiny or funny. Turning it off will fix the problem.
nickmv said:
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
Click to expand...
Click to collapse
Two questions:
The link you give me to download the ICS rom keeps loading for ever. So, I choosed this one instead:
http://forum.xda-developers.com/showthread.php?t=1356228
Right or wrong thing to do?
It it essential to install a custom kernel? I ask because I forgot to copy/paste the .zip file and due to lack of time, I procceded without it, installing the ROM and G-APPS.
Sent my phone to Square Trade before I got the 4.0.4 update (was previously on 4.0.2 with T-Mobile). They put a new "main circuit board" in my phone (sent it in for power button inop).
Well when I got my phone back the first thing I noticed was an "unlocked lock" symbol during boot up. Then I found that that it was updated to 4.0.4 and in my app drawer the Superuser app (which I updated to v3.0.7 (41)) is present.....
Here is the specs under the "about phone" section in Settings:
Build number: IMM76D
Baseband version: I9020XXKI1
Kernel version:
3.0.8-g6656123
[email protected] #1
Thu Feb 2 16:56:02 PST 2012
I've never rooted before -so I don't know how to confirm that I am. However I noticed that in the Superuser app, when I go to check for updates it says that my installed version is LEGACY -and it says a new version of SU BINARY was found. When I tap on "update" it says: CHECKING FOR BUSY BOX... NOT FOUND, and then GAINING ROOT ACCES... FAIL!
Also when attempting to try out Droid Wall and Adblock they both say that I am not rooted.
Does this mean that I am not rooted?? -even though that "unlocked lock" symbol is present at start up??
If they rooted my phone wrong, what can I do to root it correctly??
-and-
How to I return to stock un-rooted 4.0.4 if I ever need to??
Any help would be GREATLY appreciated.
The unlocked symbol when you start up your phone (under the Google logo, right?) just means your bootloader is unlocked, which is the first step in actually rooting the phone.
As for Superuser, even non-rooted phones can install it from the Market/Play Store (like you have), doesn't necessarily mean you're rooted.
Did you install Superuser or did they put it on the phone?
They put it on my phone. I just updated it from the Play Store when I was putting all my apps back on my phone.
Sent from my Nexus S using XDA
Maybe they just wanted to see whether or not you were rooted?
So I can go ahead and follow the "how to root i9020T" guide under the stickied General section of this Nexus S forum? ....and I should be ok?
I figure that if my bootloader is already unlocked I might as well go all the way and finally root this phone, right? That or lock it up again.
My main concern is since I didn't know where they left of, I wasn't sure where to begin/pick back up in finishing the root process.
If I follow the guide from the top I should be safe though, right?
Sent from my Nexus S using XDA
MotorcycleKopp said:
So I can go ahead and follow the "how to root i9020T" guide under the stickied General section of this Nexus S forum? ....and I should be ok?
I figure that if my bootloader is already unlocked I might as well go all the way and finally root this phone, right? That or lock it up again.
My main concern is since I didn't know where they left of, I wasn't sure where to begin/pick back up in finishing the root process.
If I follow the guide from the top I should be safe though, right?
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
if you already have a custom recovery, just flash any of the custom roms(or kernels) and youll have root. if not, flash a custom recovery then a custom rom(or kernel). all the custom roms come with su binaries. yea, its that easy.
So I'm not sure if they put custom recovery on my phone.... how can I tell??
MotorcycleKopp said:
So I'm not sure if they put custom recovery on my phone.... how can I tell??
Click to expand...
Click to collapse
power off>hold volume up+power>volume rocker to select recovery>power to select
OK, when I do that process I got what looked like a dead Android??
MotorcycleKopp said:
OK, when I do that process I got what looked like a dead Android??
Click to expand...
Click to collapse
ha! dead android, lol.
youll need to flash a recovery via fastboot(probably clockworkmod recovery).
Ok.... flashing recovery is ALWAYS where I get lost when I read up on rooting.
Could you/someone point me in the right direction please?? (via instructions or a link to some GOOD & CURRENT instructions and files).
Can I just follow instructions from http://forum.xda-developers.com/showthread.php?t=895545 and start from the top -so that I get a feel of how to do this from the beginning????
-and if I follow the instructions from this post, will I still be running 4.0.4??
This dead android really concerns me a bit!!
That guide is perfect. If you use, it will install a custom recovery on your phone, which can then be USED to install 4.0.4 on your phone again. If you don't really want root access, I'd stay where you are right now.
Anyhow, if you DO decide to follow the guide, you can skip the part where it says to type "fastboot oem unlock" (beginning of part 2) because that command unlocks the bootloader, and your phone already has an unlocked bootloader (shown bythe unlocked lock you see when you turn your phone on).
OK.... so I'm following the guide, BUT when I go to "update driver software" I point it to where I downloaded the "android-sdk_r13-windows.zip" file, but it won't let me select it. I also tried extracting the file directly onto my C:\ drive, but it won't let me select it there either.
What am I missing here??
(running Windows XP 32 bit, by the way)
Do you have either WinZip, Winrar, or 7-zip installed on your computer? You need them to extract the file, which will give you a folder. Point the driver installer to that folder after you've extracted it
Well I got the file extracted just fine. Problem is that when it won't let me select ANYTHING when I try to update the driver (the "OK" is dulled out when I point it to where I extracted the file to).
BTW, at the current state, next to "Android 1.0" in my Device Manager it shows a yellow "question mark & exclamation mark", and it is a sub of "other devices" (with a yellow "question mark" next to that as well).
Did I miss a step????
Try picking just the folder where the extracted folder is, that might work. As for the yellow exclamation mark, it's normal. That's what the drivers you install are going to fix
Still won't let me chose anything.....
One thing I noticed is that in the instructions it says to point it to "(..\android-sdk-windows\google-usb_driver)" .....but I don't have anything that says "\google-usb_driver" at the end of the file name. I only have "android-sdk-windows" -even after I extracted the file.
All I have inside the "android-sdk-windows" folder are: add-ons, platforms, tools, SDK Manager, and SDK Readme. None of them have anything that say "google-usb_driver" in them.
Where do I find this "google-usb_driver"??
Scroll down on this page
http://developer.android.com/sdk/win-usb.html
Actually, it might be easier to try this out
http://forum.xda-developers.com/showthread.php?t=1589251
Hmmm... that one-click root method looks awesome, but since it was only uploaded yesterday I'm a little bit weary of it.
I tried to get that google-usb_driver, but with the sdk r13 it won't let me unless I update to r17. I'm thinking of just going to http://developer.android.com/sdk/index.html and getting the latest sdk r17 exe file & trying to go from there. Only concern is that on the guide here on xda it says "from sdk r14 forward Google removed the fastboot command so I'd have to make the fastboot command myself" -will this be an issue or is that easily done??
(I seriously can't believe I'm running into wall after wall with this.
I REALLY appreciate all the help thus far, by the way)
See the first link from my last post for a driver
Sent from my Nexus S 4G
The darn thing just started nagging me with an update notice that comes back every ten minutes. I read somewhere that updating is going to stop me from doing certain advanced things, so I finally got the last push to go for either CM10 or CleanRom, depending on which one gives me the most advanced and pleasant experience.
But before doing so, it's recommended to get some kind of flash info file or something from it that doesn't come out when upgraded to the latest firmware but does on the old 4.0.3. What would be the best way to go from now on?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Found something myself, thank me very much!
http://androidroot.mobi/t3_nvflash/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
do yourself a favor if you gonna go with a custom rom, Energy rom and TWRP recovery!
What are their advantages when compared to CM10 or Clean?
Sent from my Galaxy Nexus using xda app-developers app
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Lex_Michdeandroid said:
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Click to expand...
Click to collapse
Your tablet will say it is unlocked in the upper left part of the screen when The Asus logo appears at boot.
Sent from my Transformer Pad TF300T using Tapatalk HD
Hi, if your tablet is still on stock 4.0.3 (ICS bootloader), I recommend doing NVflash first
http://forum.xda-developers.com/showthread.php?t=1894867
If you have already updated to JB bootloader it won't work.
It doesn't say Unlocked, so I guess that's why I don't see the USB option when I try to get into Fastboot?
I'm also not able to get ADB commands recognized on my win7x64... Am I doing it wrong? What's the proper method/order of events here? Isn't there a really n00b-proof version of a guide here, or is it something I should write as soon as I get out of this mess and get it working?
Sent from my Galaxy Nexus using xda app-developers app
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
pjc21 said:
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
Click to expand...
Click to collapse
Perhaps I'm not really looking in the right location, but the Asus website says I need to choose an operating system and gives me no option to choose. This way I'm not able to download the apk...
Edit:
Tried clicking the links with the tab and it started the download... Device now has an unlocked bootloader. On to the next one...
Edit2:
Ah, now I get it. Pay attention to where that Android SDK stuff is being installed. Mine got installed in the folder I unpacked the installation files! So somewhere 256 folders deep on the Desktop was the right 'adb.exe' file. Make sure the tf300_nvflashpack files are in the same directory and open the command prompt there. After that I got back to the http://androidroot.mobi/t3_nvflash/ website and entered the commands. One moment please, back in a flash!
Edit3:
Now I have 5 files in /mnt/sdcard/AndroidRoot and I uploaded them to my Dropbox. I'm guessing they are the right files...
blob.bin
blob.log
bootloader.ebt
create.bct
recovery.bct
To be sure I uploaded them all.
Copied these files into the SDK folder, along with the other zipped files for nvflash so the nvflash command works to get the other three backup files.
Edit4:
Went on following the guide and checked the video to see if I was really going the right way. Finally I have all files backed up. Goddamn what a journey, but it makes you grow a pair of balls. Now on to the next hurdle, getting a proper ROM, because stock is really getting on my nerves.
So CleanRom, CM10 or Energy ROM? Should I first upgrade to JB? Without or with the popup I'm constantly getting?
Lex,
You have alot of the same questions I do/did, and I have your original post open in another window to respond to all your questions. I'm working on writing a guide for all this stuff so this is rather helpful. If I respond to a question twice, please forgive me as I'm literally just going down the list and answering em as I read em.
In your first post, the file you're referring to is gathered via NVFlash. I haven't used NVFlash yet, but what I understand is that if you use this tool it basically backs up your ICS (4.0.3) bootloader information. The newest firmware change is to Android Jelly Bean (4.1.1) and that re-locks your bootloader. Once you go to JB, you cannot go back. So this servers as a backup (again, this is just how I interpret the information from their website. I don't know how correct my interpretations are, and have actually opened a thread to ask for clarification about this program).
For the drivers, all I did was download the android SDK and install the 'android tools' and "extra - google drivers' from the list. My laptop was just recently wiped-out so I have no prior drivers installed, nor have I connected my tablet to my computer yet (just got a replacement tablet last weekend). I didn't use the universal driver or any other add-ons. Just use the SDK, it will install drivers, and then it will detect your device. I verified this by typing "adb devices" in command prompt and it detected the serial # of my device.
Within that same post, you had some confusion about ADB. It's just an executable, and you have to use the command prompt window from whichever directory it is installed to. So once you unzip the Android SDK or wherever you installed ADB to, use the command line commands "cd directory/where/adb/is/installed" to navigate to it, or use shift + right click within that folder and it will have an option to "open command prompt here" with admin privileges. That makes life a bit easier. Other people also install their SDK to C:\android\SDK or something similar, so it's less to type.
In order to determine if your bootloader is unlocked, look at your tablet in the top left hand corner when it boots up. It will say "Device is unlocked" and list a bunch of numbers (which if I remember correctly would just be the firmware information). Your device will not be unlocked until you actually download the unlock tool from asus' website and push the file via adb to your tablet and install it. That is, you have to take a very specific, very advanced overt action to unlock it. Nothing else and no one else can do it for you nor can it be done accidentally.
Next post (#8 in the thread): You are correct that fastboot will not show unless you are unlocked. I just verified this on my not-unlocked, not-rooted new tablet, and cannot enter fastboot mode. Your ADB commands wont work if your drivers are not correctly installed.
Post #10: You have to select "Android" under the OS drop-down box to find the unlocker app. As for the location of the ADB.exe, mine was found in this subfolder within the android SDK: <whereveryouunzippedit>\Android SDK x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
That folder contained the correct (and I think only) adb.exe I needed.
For your last part, I think you should try out a number of ROM's to see which you like best. I've tried all the major ones (CM9, CM10, CleanRom, Hydro, Blackbean, and some of the stock rooted/de-odexed) ROMs and used Blackbean for the longest time because of how slick it looks (all black) and how easy it is on my eyes.
Make sure you document the steps you took so you can remember them in the future. I'm working on writing a guide right now and documenting my steps to go from a stock, locked, and not-rooted tablet to a rooted unlocked and custom flash tablet.
I really hope I was able to clarify some things. I am by NO MEANS an expert but I've spent many hours experimenting and think that I wish I had someone to answer my questions when I was first learning, rather than learning by mistake.
Hopefully this helps,
Opethfan89
Hi, I use Energy rom which I find pretty good, you will need to update to JB first as Energy, CM10 & Clean rom are all JB bootloader compliant. My tab came with JB pre installed so not sure what the best way to update is but would assume since you still have stock recovery would be with OTA update (popup notice). Here is a guide to update to JB but I think this is if you have already installed a custom recovery as it looks like you flash back to stock recovery first, thats why I think if your getting update notice and still have stock recovery, go with that.
http://forum.xda-developers.com/showthread.php?t=1845377
Once you have updated to JB stock here is a guide to install custom recovery (CWM or TWRP), root & install custom roms.
http://forum.xda-developers.com/showthread.php?t=2041627
Here is link to TWRP recovery (I had issues with CWM).
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps.
opethfan89 said:
Lex,
You have alot of the same questions I do/did,
[..]
Hopefully this helps,
Opethfan89
Click to expand...
Click to collapse
I can only click the thanks button once, but I clicked the f- out of it that one time. Although I already got to the point where my stuff is backed up, it is really good for my/our fellow adventure-seekers to have an answer to these FAQuestions. It's awesome you took the time and effort to type that much words to help out someone you don't even know. Thanks again!
pjc21 said:
Hi, I use Energy rom which I find pretty good,
[..]
Hope this helps.
Click to expand...
Click to collapse
Same goes for you! Tomorrow I will be trying as much ROMS as I can to see which one suits me best. Also repeating this process is the best way to learn something and since I'm unbrickable, I am going to flash the hell out of it for a few days. I'll try to post my steps and findings here so I (and perhaps others with the same trouble) can benefit from it in the future.
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
pjc21 said:
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
Click to expand...
Click to collapse
It's upgrading now. Of course I forgot I lost root with the last OTA update and I forgot to make sure I rooted the thing so it was able to use the rootkeeper after upgrading to JB. I hope there is some documentation on rooting JB, because at the time this all happened root was not possible yet. It's past 1 AM over here, so I guess it's best to save this quest for later when I had some sleep.
Edit:
Just for kicks I tried 'Root Checker' and it said 'no root'. Then I saw 'Rootkeeper' was installed. Opened it up, tapped the restore button... Device rooted! Guess my memory is really failing big time... One down, # to go.
Edit2:
Installed TWRP:
Just downloaded the .blob from their website and
put it in the platform-tools folder.
Then renamed it to TWRP.blob.
Turned off tablet,
plugged in USB cable in the tablet ONLY,
hold volumeDown button,
plug into laptop holding button,
waiting...
choose USB logo,
open cmd-line in the platform-tools folder,
run command: "fastboot -i 0x0B05 flash recovery twrp.blob"
waiting...
Done. Let's see if it works...
Edit3:
At first I didn't understand how to get into TWRP (DOH!),
Hold volDown, power on, choose RCK.
Edit4:
Been having a fight with TWRP when I try to install CM10.1 (latest nightly: 20130121). Gives me an error status 7 or something...
Code:
Verifying update package...
assert failed: getprop("ro.product.device") == "tf300t" ||
getprop("ro.build.product") == "tf300t"
E:Error in /external_sdcard/CROMS/****.zip
(Status 7)
Error flashing zip ' /external_sdcard/CROMS/****.zip'
Of course, ****.zip is a long filename I didn't want to type completely here.
Will try to figure out whats wrong later today, first I'm going to try restoring the backup I made earlier, just to see how a complete backup works when the tablet is wiped back to factory settings.
Edit5:
The backup stuff is really cool! My tablet is back the way it was even though I wiped it completely!
Back to the ROM rumble... baked_tf300t_blackbean-6_jb-bl_b6.zip gives me the same error. Starting to get annoyed again... Let's try something different, CleanROM. Download is taking ages... I'm restoring again, so I can use the tablet for the rest of the day. As soon as I feel like it I will try again, for now I'm giving it 'the finger'.
Edit6:
Cleanrom is installing now. I guess CM (baked is CM based right?) was causing some trouble...
Done installing...
Wipe Cache/Dalvik...
Reboot...
Android is upgrading...
Might need to choose the small font, my screen is really clogged up with stuff. Didn't expect to keep my settings etc., thought it would be completely wiped. I'm going to restore and then reinstall with the highest DPI setting first, then I'll wander around the rom to check if I like it.
Edit7:
I think I'll stick with this one for a few days, runs fine if you ask me, maybe take the time to finally update my Galaxy Nexus to CM...
Whats up guys? First I just wanna say hi I am a new member and looks like you guys have a great little community here and I'm glad to be a part of it. I hope someone can help me out. Also, I did watch that noob video, I loved it. Before posting this I have searched found some similar but according to that video service provider matters. I guess no one uses virgin mobile..
Alright, so I have an HTC one S that I have had for almost a year now, bought it brand new through virgin mobile. I used for a while and liked the phone but my buddy at work had a galaxy phone and could do so much cool stuff with his that I wanted to do the same. So one day at work he came to this site and "Rooted" my phone. He was suppose to put a different operating system on it too but never did get around to it (he quit before he could). I didn't know him outside of work so I was stuck with just the root which is cool and all but now jellybean has just come out for my phone about 2 weeks ago. But here's where the problem lies, I go to update my phone and the download and install looks like it goes fine, the phone is plugged in while i update, When the phone restarts after the install, the update is not on it and my phone asks me again to update. I've tried this dozens of times with the same result. I have reformatted my phone in the settings and I lost everything I had on it, but that's no big deal. What I ultimately want is for this update to go through. My question: Is there any thing I can do so that it finally updates to jellybean and this damn notification goes away? Sorry if this is a noob question but I'm really stuck and don't have a lot of techie friends that can help me out.
Thanks in advance
Age
I think your problem is that you're not on the stock recovery. Official updates require stock recovery to be properly installed.
To fix this, first download this http://d-h.st/rZW . It's the stock recovery image. Next you'll need fastboot executable on your computer. This comes with android sdk (google it) but i believe can also be found separately. Then you flash the stock recovery on your phone by first booting your phone into bootloader (by pressing volume down and power button when device is shut down) and then entering fastboot mode by selecting it in the bootloader and finally running a command: fastboot flash recovery ville_recovery_signed.img. Now your phone should be able to install the update.
Option two: as your phone is rooted, you could probably also use an app called flash image gui. It's available in the themes and apps subforum. With it you just first download the file from http://d-h.st/rZW on your phone, then open the flash image gui, browse the downloaded img and flash. After a reboot the update should install.
Please note that I quickly googled for recovery image and even though its named like the correct recovery img I'm not 100% sure its legit. Here in he forums are links to the correct stock recovery if you look around a bit.
Hope this helps!
Sent from my One S. Please hit thanks if I helped.
stonedage said:
Whats up guys? First I just wanna say hi I am a new member and looks like you guys have a great little community here and I'm glad to be a part of it. I hope someone can help me out. Also, I did watch that noob video, I loved it. Before posting this I have searched found some similar but according to that video service provider matters. I guess no one uses virgin mobile..
Alright, so I have an HTC one S that I have had for almost a year now, bought it brand new through virgin mobile. I used for a while and liked the phone but my buddy at work had a galaxy phone and could do so much cool stuff with his that I wanted to do the same. So one day at work he came to this site and "Rooted" my phone. He was suppose to put a different operating system on it too but never did get around to it (he quit before he could). I didn't know him outside of work so I was stuck with just the root which is cool and all but now jellybean has just come out for my phone about 2 weeks ago. But here's where the problem lies, I go to update my phone and the download and install looks like it goes fine, the phone is plugged in while i update, When the phone restarts after the install, the update is not on it and my phone asks me again to update. I've tried this dozens of times with the same result. I have reformatted my phone in the settings and I lost everything I had on it, but that's no big deal. What I ultimately want is for this update to go through. My question: Is there any thing I can do so that it finally updates to jellybean and this damn notification goes away? Sorry if this is a noob question but I'm really stuck and don't have a lot of techie friends that can help me out.
Thanks in advance
Age
Click to expand...
Click to collapse
You can not because your recovery isn't stock so you have to download ruu or ota and flash it vie cmd
Thanks alot guys for the quick reply im going to try this out now. may take me awhile as it looks like i have alot to learn to do this by myself but im sure ill figure it out. and i hit both your little thanks button
All right so after trying both of those out I am still stumped. When I try my first option that adb sdk program package and tried to use the fastboot program on it I get an error. Now I typed this error into your forums and searched around and found some hope but once tried it still didn't work. It's an .".dll" file is missing when I get home to a computer I'll post a link for it. I do understand the steps just this fastboot program won't load.
Now option 2 is what really messes me up because I swear my phone was rooted but I'm scared from trying to factory reset this phone so may ways I may have it only half rooted if that's what its called. Because after I bought this IMG flash program downloaded the image to my phone the program says that there no root so I downloaded and payed for another of this dudes apps that tells me if my phone is rooted and it says sorry has no root access. But if my phone has no root access then why would it boot into that teamwin screen...
I even took a 3rd option and clicked the phone image button on the teamwin start screen. After that flashes I get another error saying that it didn't work so my question now. Is my phone even rooted? And have I ruined anything so far like could I send it in for warranty or is it considers tamperd.
I have tried to explain this the best I can apologize for spelling mistakes. But any help or suggestions would be greatly appreciated.again thanks in advance.
Sent from my HTC One S using xda app-developers app
Install htc sync on your pc to get the drivers. Then download viper ROM along with its boot.img flash script. Flash viper through that "team win thing" (lol
Then put your phone into bootloader, then fastboot USB connected to pc and run the boot.img flash script.
That would be about the easiest way to get jellybean on your phone.
Pm me if you need more help our can't find links.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
So last night I emailed the creator of the app I used to check my root and here is the msg I got back. Today is a day off and I'm just spending the day browsing the forums and looking for the right tools to fix it. if you get this in mean time can you maybe help to point me in the right way. I really don't want to bug you guys on this forum I know how you hate people like me but I live in a small town and am really relaying on this forum to completely teach me everything from scratch. hopefully without bricking my device that's sounds horrible. Here's my email I got back.
Hi,
The Root Checker Pro results show the device does not have root access setup and unless you've erased and re-installed Android, the device appears to have never had proper root access. I would suggest relying on the same forum to locate the latest and most accurate directions on unlocking the internal memory write protection and then gaining proper root access.
Flash Image GUI will loading custom kernels and assist with loading custom ROMs on devices that have internal memory write protection, such as your HTC One S.
Thanks for the support!
Joey
Sent from my HTC One S using xda app-developers app
Sent from my HTC One S using xda app-developers app
oh and here is the results from my root test.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your HTC One S device by Root Checker Pro version 1..3.1 from joeykrim in the Android Market -
Is your bootloader unlocked? You can check by (with your phone on) hold "volume down" and "power" until button lights at bottom start blinking and the screen turns off... At that point let go of the power button but keep holding the volume down button And eventually you will see the boot loader screen. At the top of the screen it will either say locked or unlocked. Check and report back.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
Ya its unlocked but now thats the only screen i can get to i tried to flash that stock image and when i did my phone went into some scfeen that showed a phone and some triangle with an explanation mark. my phone either boots up now to a htc quietly brilliant screen or if i hold the volume down button when its off it goes to that boot-loader screen that shows unlocked and tamperd at the top this is all i really know. Guys im sorry im trying to act like i know what im talking about but in all honesty i really have no idea. im really just pissed now that i even touched it cause it was working fine before besides the wifi constantly shutting down and bugging me to update to jelly bean. I honestly really shoudnt be here i just really wanted my phone fixed and i cant find anyone to pay localy to do it for me so thought i would try to do it with google but now im here. please just tell me if this phone has just become an expensive coaster AKA garbage thanks again for all the help.
stonedage said:
Ya its unlocked but now thats the only screen i can get to i tried to flash that stock image and when i did my phone went into some scfeen that showed a phone and some triangle with an explanation mark. my phone either boots up now to a htc quietly brilliant screen or if i hold the volume down button when its off it goes to that boot-loader screen that shows unlocked and tamperd at the top this is all i really know. Guys im sorry im trying to act like i know what im talking about but in all honesty i really have no idea. im really just pissed now that i even touched it cause it was working fine before besides the wifi constantly shutting down and bugging me to update to jelly bean. I honestly really shoudnt be here i just really wanted my phone fixed and i cant find anyone to pay localy to do it for me so thought i would try to do it with google but now im here. please just tell me if this phone has just become an expensive coaster AKA garbage thanks again for all the help.
Click to expand...
Click to collapse
I think what you should do is:
- find ruu matching to your carrier and download it
- relock the bootloader
- flash stock recovery
- boot into bootloader and go to fastboot mode
- connect use cable and wait till phone screen shows fastboot usb
- run the downloaded ruu.exe on pc and wait for it to complete
- on successful completion your phone will be same as you got from a store
Just note that flashing ruu will cause hboot upgrade as well.
If my post helps, remember to use the thanks button.
Sent from my HTC One S using xda app-developers app
wouldnt that "ruu" be what the gentleman in the very first reply in option 1 gave me? i have the file and tried flashing with the one button root tool kit by hasoon2000 i clicked on flash recoveroy then chose the file ville_recovery_signed.img. and let the black screen (beleive its called cmd) do its thing but really it looks like its doing nothing and my phone wont boot up the main screen where i can receive texts or make calls. thanks
Ok so i found a friend that understands the way you guys have explained this. Now the unfortunate part is that the virgin mobile (canada) RUU file is extreamly difficult to find. So my question now is do you know where i can find this file i have searched the forums and google but with no luck. im sure once we find this file my phone will be fixed then im not touching it AGAIN! cant explain how much i appreciate all your guys help and patience with me.
Thanks again
Adrian
Help!!!
I am having the same issue as described only I relocked my my phone.
***TAMPERED***
***RELOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.17.31501S.10_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 20 2012,151418
I try to fastboot flash recovery or even the boot image and I get
(bootloader) signature checking...
FAILED (remote: signature verify fail)
I cannot seem to find an ruu for my phone from telus and trying to flash the recovery will not work. Any help would be greatly appreciated.
I emailed HTC and asked for it. if i get it i will send it your way.
Heres my email back does this mean that my phone is broken and garbage now or could i flash it with rogers/telus/bell and then sell it to someone on that service provider or even switch mine???
Dear Adrian Berdux,
Thank you for reaching the HTC Tech Support Team with your inquiry, I’m here to make sure all your questions and doubts are cleared.
In regards of your request, the Jelly Bean RUU for the Virgin Mobile HTC One S is not yet available, nevertheless on the following link, you will be able to find all the Jelly Bean RUU's available for your device:
http://www.htcdev.com/devcenter/downloads/P10
Adrian, if you need further assistance, please do not hesitate to contact us, I’m here to make sure all your questions are addressed in the most efficient way.
Thank you for choosing HTC.
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Ash
HTC
Done
Finally got it, reunlocked my phone, pushed out a stock recovery image using the One S all in one tool and was able to download and install the update.
really and you where in the same position as me but on telus right? My phone is still broken but is it good hands at the moment so hope its fixed soon really starting to miss having it.
Mine is the S3 model and its not rooted but the bootloader says it RELOCKED. So I get the notification yesterday and whenever I try to update it keeps rebooting back to the bootloader. Any solution?