Hi All
Now a proud owner of HTC One mini (uk) but am having issues trying to unlock bootloader, root and install custom rom.
for some reason my PC will not recognize my mini in fastboot mode . i have re installed the usb drivers and even tried to connect my wifes HTC one which i have previously rooted ...but it will not connect to either of the two.
I would be grateful if the community could offer a solution or advice, Thanks
oh forgot to say pc running windows 8.1
Edit: I found this http://forum.xda-developers.com/showthread.php?t=2588979 on the portal. it has ADB,FASTBOOT and DRIVERS needed . Not tried it myself as reverted to windows 7 however, many users confirming that it works on win 8 & 8.1.
I hope this helps, any thanks is given to the developer "Snoop05" as i am just posting the link.
cheers
Braddison said:
Hi All
Now a proud owner of HTC One mini (uk) but am having issues trying to unlock bootloader, root and install custom rom.
for some reason my PC will not recognize my mini in fastboot mode . i have re installed the usb drivers and even tried to connect my wifes HTC one which i have previously rooted ...but it will not connect to either of the two.
I would be grateful if the community could offer a solution or advice, Thanks
oh forgot to say pc running windows 8.1
Click to expand...
Click to collapse
same problem,change system to windows 7
thinkinbunny said:
same problem,change system to windows 7
Click to expand...
Click to collapse
Hi and thanks for the reply.
yeah ive had to used an old laptop running windows 7 and eventually unlocked bootloader. Now have an issue that adb is out of date! so still unable to root and install magioRom R3 :crying:
Braddison said:
Hi and thanks for the reply.
yeah ive had to used an old laptop running windows 7 and eventually unlocked bootloader. Now have an issue that adb is out of date! so still unable to root and install magioRom R3 :crying:
Click to expand...
Click to collapse
Search around to see if you can find a updated version? Let me explain to you how I did it. First, I unlocked my bootloader. Second, I downloaded the twrp and magiorom r3. Third hold shift and right click on the flashboot folder that you downloaded from htcdev and click on the open command window here. Rename you twrp to recovery. If your twrp file says img on it then try recovery.img, if not then type recovery. And on the cmd type flashboot flash recovery.img. Then you go back to bootloader and go to recovery and follow all the steps on the magiorom link. Don't forget to thank me. And btw, I didn't have to download any of those adb files. You root your phone when you have twrp. It'll ask you if you want to root. Say yes!!!!
abzboi said:
Search around to see if you can find a updated version? Let me explain to you how I did it. First, I unlocked my bootloader. Second, I downloaded the twrp and magiorom r3. Third hold shift and right click on the flashboot folder that you downloaded from htcdev and click on the open command window here. Rename you twrp to recovery. If your twrp file says img on it then try recovery.img, if not then type recovery. And on the cmd type flashboot flash recovery.img. Then you go back to bootloader and go to recovery and follow all the steps on the magiorom link. Don't forget to thank me. And btw, I didn't have to download any of those adb files. You root your phone when you have twrp. It'll ask you if you want to root. Say yes!!!!
Click to expand...
Click to collapse
should be:
fastboot flash recovery recovery.img
theodorius123 said:
should be:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks for that. I forgot about that. And I hope that it'll work for him.
abzboi said:
Search around to see if you can find a updated version? Let me explain to you how I did it. First, I unlocked my bootloader. Second, I downloaded the twrp and magiorom r3. Third hold shift and right click on the flashboot folder that you downloaded from htcdev and click on the open command window here. Rename you twrp to recovery. If your twrp file says img on it then try recovery.img, if not then type recovery. And on the cmd type flashboot flash recovery.img. Then you go back to bootloader and go to recovery and follow all the steps on the magiorom link. Don't forget to thank me. And btw, I didn't have to download any of those adb files. You root your phone when you have twrp. It'll ask you if you want to root. Say yes!!!!
Click to expand...
Click to collapse
Many thanks for your advice. I will try this later on.
btw the adb file is in the flashboot file downloaded from htcdec but have found a workaround that i will try
Braddison said:
Many thanks for your advice. I will try this later on.
btw the adb file is in the flashboot file downloaded from htcdec but have found a workaround that i will try
Click to expand...
Click to collapse
cool
Related
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
Hey guys i have a problem with the bootloader of my chacha. I just bought this phone because my legendary hd2 broke. I've tried serveral times to unlock my bootloader of my chacha via the htcdev method but without any luck. Everytime I try the ruu it gives me the 170 error code which indicated my phone isn't connected to my computer.
I tried changing usb ports without luck and installing htc sync, but the device doesn't get recognized by eather the ruu or htc sync. So does anybody know a solution so I can root my phone?
BUMPY
Bump!
Try skipping RUU Update step, maybe you don't need a hboot update. It worked for me and others as well.
didije said:
Try skipping RUU Update step, maybe you don't need a hboot update. It worked for me and others as well.
Click to expand...
Click to collapse
Thanks for the reply! Are you sure if I skip the bootloader unlock and try to root and install cwm it wont brick my phone?
iliendo said:
Thanks for the reply! Are you sure if I skip the bootloader unlock and try to root and install cwm it wont brick my phone?
Click to expand...
Click to collapse
I am not saying to skip unlocking process, just the step about RUU Update and then continue unlocking.
Just hit 'proceed to step 1' and folow instructions.
Flash custom rom
Sent from my GT-S5300
didije said:
Try skipping RUU Update step, maybe you don't need a hboot update. It worked for me and others as well.
Click to expand...
Click to collapse
Okay thanks, I will try it in about an hour and report back!
ultimat3m3 said:
Flash custom rom
Sent from my GT-S5300
Click to expand...
Click to collapse
how can i flash a rom if I havent installed cwm installed
You cannot do anything until you unlock the bootloader or s-off your device.
Apparently the problem is within HTC USB drivers.
If you have successfully installed HTC Sync and/or HTC USB drivers on your workstation, then enable USB debugging option on your phone and try to connect the USB cable to USB ports on your motherboard (at the back of computer case).
If this is not working, then probably the best option is to use somebody's else computer with Windows XP 32bit to unlock your device.
Or try a hardware reset on your PC. This will let your PC recognize the phone as a new device. Or try to fix drivers when you plug it in. This can be done from the config screen (Not sure what's the official name for in english windows... Only worked with dutch versions...
Bunnybugs_007 said:
Or try a hardware reset on your PC. This will let your PC recognize the phone as a new device. Or try to fix drivers when you plug it in. This can be done from the config screen (Not sure what's the official name for in english windows... Only worked with dutch versions...
Click to expand...
Click to collapse
peleeks said:
Apparently the problem is within HTC USB drivers.
If you have successfully installed HTC Sync and/or HTC USB drivers on your workstation, then enable USB debugging option on your phone and try to connect the USB cable to USB ports on your motherboard (at the back of computer case).
If this is not working, then probably the best option is to use somebody's else computer with Windows XP 32bit to unlock your device.
Click to expand...
Click to collapse
didije said:
I am not saying to skip unlocking process, just the step about RUU Update and then continue unlocking.
Just hit 'proceed to step 1' and folow instructions.
Click to expand...
Click to collapse
Thanks for all the help guys, just used my hackintosh to unlock the phone and it worked! The only problem now is when I try to root my device with easy rooting toolkit it gives me alot of errors regarding adb, maybe you guys know some solution for this?
Try flashing the superuser.zip method... worked for me...
Sent from my HTC ChaCha with CM9 using XDA app.
Bunnybugs_007 said:
Try flashing the superuser.zip method... worked for me...
Sent from my HTC ChaCha with CM9 using XDA app.
Click to expand...
Click to collapse
Could you link me to a tutorial or thread?
iliendo said:
Could you link me to a tutorial or thread?
Click to expand...
Click to collapse
This is a brief tut on windows:
Download adlx' small fastboot tools: link
Download adlx' recovery (best one is 5.0.2.8) - couldn't find link, search it in a development section.
Download superuser zip: link - it is in the attachments - su-2.3.6.1-ef-signed.zip.
Extract fastboot and recovery. Put recovery.img in the folder where your fastboot tools are. Navigate the command prompt to the fastboot folder. Connect your phone in fastboot mode and type this command:
fastboot flash recovery recovery.img
This will install recovery.
Copy su zip on your sd card.
Then just flash superuser zip through recovery and you will have a rooted phone.
I rooted my ChaCha
Hi Guys
I rooted my ChaCha by using unlock from HTC and installing CWM and superuser. I installed Link2SD too. What I assume now it is giving me a all the space I have on sd card for installing the apps???
Nope... if you search the forum, there are plenty of guides that explain how to set up link2sd
Sent from my HTC ChaCha with CM9 using XDA app.
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.
Hey guys just got my nexus yesterday and rooted today...my issue/question is after I flashed the lastest build I seem to be stuck in an endless bootloop I really need my phone so any help would be awesome. I've tried mounting the usb via CWM but that seems to not work at all. Does anyone else know a way I could get my phone to load or push a different file to flash? I'll probablly post this in Q&A or General as well but I thought I'd give it a shot here first!
Thanks in advance.:good:
copy and pasted from original post but I'm running the newest build of the unofficaial/official Cyanogenmod!
farmerwill said:
Hey guys just got my nexus yesterday and rooted today...my issue/question is after I flashed the lastest build I seem to be stuck in an endless bootloop I really need my phone so any help would be awesome. I've tried mounting the usb via CWM but that seems to not work at all. Does anyone else know a way I could get my phone to load or push a different file to flash? I'll probablly post this in Q&A or General as well but I thought I'd give it a shot here first!
Thanks in advance.:good:
copy and pasted from original post but I'm running the newest build of the unofficaial/official Cyanogenmod!
Click to expand...
Click to collapse
Flash TWRP. Wipe EVERYTHING you can inside of TWRP.
Lol
Sent from my Nexus 5 using xda app-developers app
Thanks!
Kwongger said:
Flash TWRP. Wipe EVERYTHING you can inside of TWRP.
Click to expand...
Click to collapse
How does one go about flashing TWRP though? I can't get my phone to mount USB storage in CWM nor can I get it boot to just download or transfer TWRP to it? Thanks for the quick reply btw
Copy file into the folder where you have fastboot.exe
Run cmd. Cd to that folder
Put phone in fastboot and connect to PC
"fastboot flash recovery (whatever the name of the recovery is).img" enter this in cmd.
Magic
Sent from my Nexus 5 using Tapatalk
farmerwill said:
How does one go about flashing TWRP though? I can't get my phone to mount USB storage in CWM nor can I get it boot to just download or transfer TWRP to it? Thanks for the quick reply btw
Click to expand...
Click to collapse
Ummm... TWRP is a custom recovery LIKE CWM. Install it via Fastboot .
1. Boot into Bootloader
2. fastboot flash recovery namehere.img (in cmd)
3. Boot Into recovery
THEN follow the above instructions.
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...