Related
Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???
Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.
matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!
Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App
I just recently rooted my HTC One X and and now attempting to unlock the bootloader using HTC Dev. I've gotten my folder set up with all of the correct files (ADB and such) as well as gotten Android SDK installed. So far I've gotten into my command prompt and navigated to my file called "fastboot" that contains all of my adb files. I'm stuck at the fastboot unlock token stage. Whenever I enter that I get this error-
C:\fastboot>fastboot oem get_identifier_token
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
I've played around with it and tried different things, but still get this error. I am in bootloader/fastboot mode so that isn't the problem.
One thing I find interesting is that if I do "adb devices" I get
C:\fastboot>adb devices
List of devices attached
Click to expand...
Click to collapse
So as you can see, it doesn't say there are any devices connected. Is this normal?
Please, if you see what I'm doing wrong it'd be great if you could help me out!
tanner4137 said:
I just recently rooted my HTC One X and and now attempting to unlock the bootloader using HTC Dev. I've gotten my folder set up with all of the correct files (ADB and such) as well as gotten Android SDK installed. So far I've gotten into my command prompt and navigated to my file called "fastboot" that contains all of my adb files. I'm stuck at the fastboot unlock token stage. Whenever I enter that I get this error-
I've played around with it and tried different things, but still get this error. I am in bootloader/fastboot mode so that isn't the problem.
One thing I find interesting is that if I do "adb devices" I get
So as you can see, it doesn't say there are any devices connected. Is this normal?
Please, if you see what I'm doing wrong it'd be great if you could help me out!
Click to expand...
Click to collapse
If I'm not mistaken you need to super Cid before doing that I'd suggest just using and following this thread http://forum.xda-developers.com/showthread.php?t=1672284
Thank you so much! I got that done, unlocked the bootloader, and installed TWRP recovery. Now before I install CleanROM do I have to flash the boot.img using "fastboot flash boot boot.img" or am I good to just flash the whole .zip file through recovery?
tanner4137 said:
Thank you so much! I got that done, unlocked the bootloader, and installed TWRP recovery. Now before I install CleanROM do I have to flash the boot.img using "fastboot flash boot boot.img" or am I good to just flash the whole .zip file through recovery?
Click to expand...
Click to collapse
Depends ...what firmware r u on 1.73 or 1.85
---------- Post added at 02:18 AM ---------- Previous post was at 02:17 AM ----------
If you're on 1.73 you don't have to do anything but on not sure about 1.85 ill get back to you :angel:
1.85
tanner4137 said:
1.85
Click to expand...
Click to collapse
Unless you took the 2.20 update you dodon't have to do that so go ahead and flash clean rom and enjoy 99.7% ssure
Could I see where you found this?
tanner4137 said:
Could I see where you found this?
Click to expand...
Click to collapse
A couple different threads now I'm 99.9 percent sure you isn't have to flash the boot img. U can post in the q and a section if you really must you'll get a straight answer there
First you do have adb files installed? If you do make sure you install the drivers. Just install HTC Sync and make sure that it's not running in the task bar. Then try again. I'm almost sure that the drivers are missing in this case.
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
First you do have adb files installed? If you do make sure you install the drivers. Just install HTC Sync and make sure that it's not running in the task bar. Then try again. I'm almost sure that the drivers are missing in this case.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Lol, thanks. If you read above you can see that I solved that. What I'm needing to know now is if I have to flash a boot.img before I flash a ROM, or if I can just download the .zip and flash it from recovery.
tanner4137 said:
Lol, thanks. If you read above you can see that I solved that. What I'm needing to know now is if I have to flash a boot.img before I flash a ROM, or if I can just download the .zip and flash it from recovery.
Click to expand...
Click to collapse
Sorry I'm just incredibly lazy and forget to read sometimes , well since you never took the 2.20 RUU/OTA you just have to run the zip unless the instructions for the rom specificly says to flash the boot.img.
Sent from my HTC One XL using xda premium
Okay, so I decided to do something stupid and forget to backup my HTC One S while rooting. I installed CM10, and it got stuck in a bootloop, so stupid me decided to also do a factory reset and basically delete everything I needed to get out of it. I've tried numerous things, including ADB sideloading a ROM, but whenever I do that, it also gets stuck in a boot loop. I have no idea how to use RUU's, and if anybody could help me to fix my phone, that'd be really really helpful. I'm also kindof a n00b towards this stuff, so step-by-step instructions would be much appriciated Thanks.
~MuZiiX
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
CuzCrostyPwns said:
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
Click to expand...
Click to collapse
I think my device is s-off...i used the HTC One S all in one toolkit, and I have no idea what supercid is :s I've tried a couple RUU's before (don't know if i used them correctly, but i did relock the bootloader when i did it) but none of them helped. It just stayed at a black screen with "htc" in the middle. No error triangles or anything.
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
CuzCrostyPwns said:
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
Click to expand...
Click to collapse
Yeah, the RUU's were .exe's with my phone connected through USB. I can get into recovery, I have CWM installed.
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
CuzCrostyPwns said:
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
Click to expand...
Click to collapse
Well thats what I've been trying to do with the ADB sideloading, because it wont let me mount my sd card. It just says 'ERROR MOUNTING SD CARD" and when I've tryed flashing a new ROM from ADB sideloading, it just gets stuck in a bootloop again.
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
CuzCrostyPwns said:
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
Click to expand...
Click to collapse
I've tried running multiple RUU files, and I have no idea what one to use. The phone when I got it was unlocked, and the android version was ICS I'm pretty sure.
I dunno how to find my stock settings because I cant get past the loading screen.
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
did you flash boot.img? most of roms will bootloop without it
Roundtableprez said:
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
the boot.img is located in the zip you downloaded from get.cm
NQNH said:
the boot.img is located in the zip you downloaded from get.cm
Click to expand...
Click to collapse
So what command would I use while flashing the boot.IMG file? (again sorry for not getting this, I just wanna get my phone working again)
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Download or build from source
Download gapps
wipe unless you're upgrading from an earlier CM10 ROM
flash rom in recovery
flash gapps in recovery
unless you have s-off fastboot flash boot boot.img
Click to expand...
Click to collapse
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
dc211 said:
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
Click to expand...
Click to collapse
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
MuZiiX said:
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
Click to expand...
Click to collapse
It not really a big deal. Your problem is the most common one we see in Q&A. Also, once you finish flashing the boot.img keep in mind that CM10 can take a few minutes to boot the first time.
Also, just a heads up while the toolkits are helpful learning the command yourself actually lets do you a lot more things a lot faster.
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
CuzCrostyPwns said:
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
MuZiiX said:
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
Click to expand...
Click to collapse
Nope, just gotta do it one of the three ways mentioned. If debugging isn't enabled use option 1.
This can either be done via
1 powering off and keeping volume up & the power-button pressed
2 the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
3 via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Click to expand...
Click to collapse
Hi All,
Of course the first thing I did after getting my new HTC One SV is root it and install LBE privacy protection to stop data leakage. However recently ive been getting a notification of an update to jelly bean through my phone provider (Vodafone Australia). However this will not install due to custom recovery image so the pre-install check fails. I cannot find stock recovery images anywhere and even if I did, due to presence of clockwork mod cant push images via Android SDK (skips straight past hboot to clockworkmod so isn't detected as an available device).
Can anyone help me get my phone back in a state where I can install the new update and the re-root?
Am not 100% noob, am familiar with custom roms and basics required to root and use SDK, this is my 3rd android device ive played with so hopefully this question is not tooooo SIGH.
Seems like HTC one SV is too new to have its on page in XDA support?
Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV
Not helpful
marceli-szpak said:
Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Hi there,
Unfortunately I don't have permission to post messages in that thread, nor does it seem the appropriate place to ask my question as it is an area for resources not help.
You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV
RE HTC One SV Revert to Stock Help (for update)
marceli-szpak said:
You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000
snorglamp said:
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000
Click to expand...
Click to collapse
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.
old.splatterhand said:
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.
Click to expand...
Click to collapse
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.
snorglamp said:
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.
Click to expand...
Click to collapse
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.
?????????????*
ismailnayir said:
?????????????*
Click to expand...
Click to collapse
If's there anything you don't understand, ASK!
So nobody knows, what you want, sorry.
old.splatterhand said:
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.
Click to expand...
Click to collapse
Yes I thought that might be the case but was not having any luck with search results to find out what to do. Thank the internet gods for you! Going to your thread now XD!
I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!
madpausa said:
I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!
Click to expand...
Click to collapse
DUDE! THATS TOTALLY WHAT I WANNA HEAR, however, ive been having enormous trouble getting fastbood/ADB to recognise the phone is attached, I have tried the universal clockwork mod ADB driver which didnt work, and I havent had any luck folloing the instructions on Splatterhand's other threads in getting it recognised. The command fastboot devices just leaves a flashing cursor FOREVER! Other commands leave the message "waiting for device". According to splatterhand ADB/Fastboot wont recognise the phone as attached because of clockworkmod and therefore I cant push any commands or files...how did you solve this?
OMG
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhead for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help
madpausa said:
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help
Click to expand...
Click to collapse
So I took your advice and pulled a recovery image from the ICS Cricket (using the link in splatterhand's thread to stock resources) image. Downloaded the OTA and went to apply it, got past boot/recovery screen checks and all was looking good until i got to a screen with what looked to be an SD card icon and a loading bar under a larger phone icon with a green recycle type circle over it. That loading bar stopped about half way with a red triangle and exclamation mark (i.e. during the update process). Fortunately not bricked. It may be that I need the original Vodafone AU recovery image, or that there was something about the ICS OTA image that I used that made it fail. Not sure. Will try to find another stock recovery image.
Applied recovery from EU RUU stock and while that went fine and can boot into htboot no problem, when applying the OTA update it skips the fastboot and gets stuck on HTC One screen like normal loading except stuck.
I think I will try old.splatterhand's recommendation now that I am able to push things to the phone through adb/fastboot, so thanks for your commandline tip but now I must try flashing the JB recovery etc as outlined in his post.
The problem may be that the OTA is expecting a vodafone australia stock recovery as i seem to be getting different outcomes depending on which stock recovery image I apply...
I have sent Old.Splatterhand the Vodafone Australia JB OTA file for the main thread collection in case anyone wants it or the images therein, but at the moment it is of little use to me hehe.
SUCCESS! How to update to Jelly Bean from modded/rooted HTC One SV ICS
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!
Good to see you got your problem sorted out!:highfive:
And the download of OTA was succesful, thanks!:good:
snorglamp said:
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!
Click to expand...
Click to collapse
This is the exact problem I had. I started trying to root my HTC One SV (Boost Mobile) a couple of months ago. I got past the HTC unlock bootloader, but I got confused by the rest of the rooting guide, so eventually I gave up on finishing the rooting process. Ever since then, it has said ***TAMPERED*** in hboot when I go in there. Well, just like you, I started getting the JB update notification in the OTA. I tried to install it like 15 times, but it always just rebooted into the existing image I had, which was the stock image.
So today I decided to try and finish the root and then find a JB ROM to install. old.splatterhand helped me out with getting it rooted, and it was a success. But when I asked him about JB ROMs, he said I had to have S-off. When we spoke a little more about it, he pointed me here, telling me that he helped you get the root back after you got through the OTA update.
So now, I guess I need to try and follow your instructions on getting the OTA update, and then go back to the thread where he helped you get the root back.
I'm a complete n00b to rooting android devices, but I'm pretty confident that I can do this with the proper guidance. I have rooted 2 Samsung SCH-i500s and today I finally got this HTC One SV rooted. I'm starting to see how it all works.
If you don't mind, let me know of any details of issues you faced that may not be in the guides you followed. That would be a great help.
Congrats on getting yours all done.
Thanks.
---------- Post added at 07:32 PM ---------- Previous post was at 07:15 PM ----------
snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Do you type "adb reboot bootloader" in the command line? I wanna be clear on this before I make any moves.
Brand new user here! So much info on this site; truly amazing
I have read so much, but still can't seem to figure out the best, error free method to root the TF700.
- New tablet that I bought 5 days ago.
I understand how to unlock as that's simple.
I understand I need to install TWRP.
After reading a website on androidcentral, I got the impression I need to start the Fastboot tool in Windows, and boot tablet into Fastboot mode, connect to PC...ect.
XDA forums suggests downgrading the firmware and using MOTOCHOPPER
Also, someone said to just install Scott's recovery install tool and rooting will be an option.
Any help would be great as I don't want to mess up my new toy!!!!!
Bryan480 said:
Any help would be great as I don't want to mess up my new toy!!!!!
Click to expand...
Click to collapse
Very understandable!
Downgrading to .8 and using Motochopper is useless by now. That was the easiest method to get TWRP on your tab. You would root and use GooManager to install TWRP. But Goo doesn't support flashing recoveries anymore - so root doesn't get you any closer to getting a custom recovery and a custom rom.
You have to use the fastboot method now (and need to be unlocked for that).
If you are new to this, you may want to read this:
http://forum.xda-developers.com/showthread.php?t=2277112
Scott's tool is a possibility but hasn't been updated or supported in quite a while. I would recommend the Minimal ADB Fastboot Tool:
http://forum.xda-developers.com/showthread.php?t=2317790
Or you go for the whole enchilada and install the SDK Developer tool on your PC.
http://developer.android.com/sdk/installing/index.html
Which is kinda overkill if you don't want to develop stuff for Android. What you really need out of that package is the Platform Tools.
Either way - get the correct drivers installed on your PC and fastboot TWRP 2.6.1 or 2.6.3.1 (I prefer the earlier version) onto your tab.
Then flash away :cyclops:
berndblb said:
Downgrading to .8 and using Motochopper is useless by now. That was the easiest method to get TWRP on your tab. You would root and use GooManager to install TWRP. But Goo doesn't support flashing recoveries anymore - so root doesn't get you any closer to getting a custom recovery and a custom rom.
Click to expand...
Click to collapse
While it is true that GooManager downloads no longer work, it is still possible to install a recovery from a rooted Android using dd to mmcblk0p4. But it is a good idea to do it via fastboot, just to learn how that works in case one really needs it.
Hello
Thank you so much for the reply!!
So I basically need to install the ADB fastbood on my PC and connect my TF700 to my PC via USB?
Do I need to install it on my TF700 also?
Bryan480 said:
Hello
Thank you so much for the reply!!
So I basically need to install the ADB fastbood on my PC and connect my TF700 to my PC via USB?
Do I need to install it on my TF700 also?
Click to expand...
Click to collapse
No you put your TF700 into fast boot mode by booting into the bootloader by holding down power and Volume Down when powering on.
First make sure you have downloaded the correct TWRP recovery blob file for your device from the TeamWin webpage. Use their search to find and choose the blob image for JB4.2 for the TF700T.
Rename it to twrp.blob and put it into the same folder as the fast boot.exe file
Then with it connected to your PC via USB, open a command window in the fastboot.exe folder (shift, right click, open command window here) and type or paste the following one line at a time. Wait for each line to finish:
Code:
TWRP:
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot bootloader
When it reboots back into the bootloader pressing the volume down on ECK will now load TWRP
Hello
Think I understand most of this...
Do I need to do anything with USB debug?
When I open command window, due I include TWRP: in each line, or is that not needed?
And what is volume down on ECK?
Sorry If I sound like an idiot; this is all new to me.
Thank you so much!
Bryan480 said:
Hello
Think I understand most of this...
Do I need to do anything with USB debug?
When I open command window, due I include TWRP: in each line, or is that not needed?
And what is volume down on ECK?
Sorry If I sound like an idiot; this is all new to me.
Thank you so much!
Click to expand...
Click to collapse
Omit the TWRP ahead of the fastboot command. I think sbdags meant to write that outside of the code marks.
He's a busy man....
ECK is a typo. Supposed to be RCK, the icon for your recovery in the bootloader menu. And you have to push Volume UP on the flashing icon to enter it. Volume Down let's you cycle through the icons.
He's a busy man
Sent from my DROID4 using Tapatalk
berndblb said:
Omit the TWRP ahead of the fastboot command. I think sbdags meant to write that outside of the code marks.
He's a busy man....
ECK is a typo. Supposed to be RCK, the icon for your recovery in the bootloader menu. And you have to push Volume UP on the flashing icon to enter it. Volume Down let's you cycle through the icons.
He's a busy man
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Oops yep ignore the TWRP: bit and also ECK should be RCK
Ok great
I'm going to try this and will report back!
Thanks again
Hello,
I just want to make sure I have the correct bootloader before I do this, as I don't want to break my new toy!!
My tablet is new...just bought about a week ago.
Thank you so much!!
You guys are great!
Well, if you have a 10.6.1.14.x bootloader, you're good to go.
Sent from my DROID4 using Tapatalk
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Bryan480 said:
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Click to expand...
Click to collapse
What happens when you try to unlock? Need more info.
Bryan480 said:
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Click to expand...
Click to collapse
My recent experience with unlocking:
http://www.transformerforums.com/fo...ent/40226-my-recent-unlocking-experience.html
Dave
ok I finally got it to work after at least 15 attempts. Maybe because I bought on ebay?
Flash time.
I flashed TWRP
I put the reboot code...how long does it take?
Bryan480 said:
I flashed TWRP
I put the reboot code...how long does it take?
Click to expand...
Click to collapse
Less than a minute - are you unlocked now?
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Bryan480 said:
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Click to expand...
Click to collapse
Well done and welcome aboard. If you want to change the launcher settings you should flash Apex or Nova launcher from the installer and then you can mess with all sorts of things The stock launcher can't be changed.
Bryan480 said:
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Click to expand...
Click to collapse
When you have your system up and running the way you want, go back to your TWRP and do a nandroid backup. After the backup, you can disable your Fsync. The worse case is to restore your back or reinstall your rom but you will enjoy your tablet more with Fsync off...