I know there a few tutorials already on here, however it seems quite a lot of people are eitiher asking questions about the ADB method, or cannot understand other methods. So i'll try and put it all in one easy to follow tutorial. This is for the latest version on Android 4.0.x.
For this method we are going to use Paul O'Briens Superboot.
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Click to expand...
Click to collapse
APPLY THIS AT YOUR OWN RISK!
Download the latest version of Superboot: DOWNLOAD
You might need the drivers, however its worth getting them anyway as you'll probably need them in the future: DOWNLOAD DRIVERS
If you get you might need the USB drivers: DOWNLOAD
Windows
1) Extract the contents of the above file into C:\root
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up cmd and navigate to by typing to following (Hit enter after each line):
cd C:/
cd root
6) Unlock your bootloader by typing - this will wipe your device!:
fastboot-windows oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, double click:
install-superboot-windows.bat
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
Linux
1) Extract the contents of the above file into a folder
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up terminal and navigate to the folder used in step 1
6) Unlock your bootloader by typing - this will wipe your device!:
./fastboot-linux oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, type the following (Hit enter after each line):
chmod +x install-superboot-linux.sh
./install-superboot-linux.sh
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
OS X
1) Extract the contents of the above file into a folder
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up terminal and navigate to the folder used in step 1
6) Unlock your bootloader by typing - this will wipe your device!:
./fastboot-mac oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, type the following (Hit enter after each line):
chmod +x install-superboot-mac.sh
./install-superboot-mac.sh
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
If i've missed any steps out such as downloading drivers etc, let me know what to add in etc. I did mine on OS X and it didn't require me to install anything extra
Update: it would appear some people are having issues with 4.1 rooting. I'll see what I can find an then update it. For the time being, just reflash the vanilla install and you should be fine. I'd imagine there's an incompatibility between this root and 4.1
Very nice indeed, might be worth doing a tutorial on how to return to stock if there isn't already one out there somewhere. Not many people know that it's possible to Fastboot OEM lock, I've tried it
Yeah I'm going to wait until there's a proper system.img about.
I got mine back to stock, however it was a complete bodge and highly advised against.
Locking the boot loader is the easy bit. It's going back to the default rom
Sent from my iPad 2 using Tapatalk
...but this should be moved to general i think. This subforum will br crowded next months.
sent from a kanged gt-i9000 using Tapatalk
It's based on development so I don't see why. General is anything to do with the phone. Unlocking and rooting is the first step of development
Sent from my iPad 2 using Tapatalk
Thank you for your work.
Just a small correction for your original post.
Instead of
fastboot-windows oem unlock
it's actually:
.\fastboot-windows oem unlock
Cheers. I'll edit that. Didn't work for me like that when I did it on a windows PC, however I'll add it in
Sent from my iPad 2 using Tapatalk
Maybe it worth to mention in the first post that many ppl (including me) had issues with this process, because we had no proper drivers installed first, and for that the solution was installing the newest PDAnet software. After that everything went pretty well.
Aylarth said:
Maybe it worth to mention in the first post that many ppl (including me) had issues with this process, because we had no proper drivers installed first, and for that the solution was installing the newest PDAnet software. After that everything went pretty well.
Click to expand...
Click to collapse
Ah yes. Added
Sent from my Galaxy Nexus using Tapatalk
I'm very new to this so prepare for a stupid question!
I'm trying to run this on a Mac, and when I'm trying to run fastboot oem unlock I get the following:
/Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac: No such file or directory
What could cause this?
helen_xxxx said:
I'm very new to this so prepare for a stupid question!
I'm trying to run this on a Mac, and when I'm trying to run fastboot oem unlock I get the following:
/Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac: No such file or directory
What could cause this?
Click to expand...
Click to collapse
Have you navigated to the folder where the files are located? Stupid question but not sure what you've done
Sent from my Galaxy Nexus using Tapatalk
Evostance said:
Yeah I'm going to wait until there's a proper system.img about.
Click to expand...
Click to collapse
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Evostance said:
Have you navigated to the folder where the files are located? Stupid question but not sure what you've done
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Oppressa said:
Thank you for your work.
Just a small correction for your original post.
Instead of
fastboot-windows oem unlock
it's actually:
.\fastboot-windows oem unlock
Click to expand...
Click to collapse
I am pretty sure you don't need the .\ on Windows? Only Mac & Linux.
StuMcBill said:
I am pretty sure you don't need the .\ on Windows? Only Mac & Linux.
Click to expand...
Click to collapse
Thats what I thought. Worked without the .\ for me at work as its just an exe
helen_xxxx said:
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Click to expand...
Click to collapse
OK, If you files are in the folder r2-galaxynexus-superboot, open terminal and just type (after each line hit enter):
cd /Users/
cd extra_ham/
cd r2-galaxynexus-superboot
./fastboot-mac oem unlock
chandlerweb said:
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Click to expand...
Click to collapse
I tried that system.img and it bricked my phone. Couldn't get it to launch, it just hung on the animation. I did a boot to CWM, messed with some stuff and then the phone randomly launched. Its not a stock image, missing all the Google apps etc and the Gallery doesn't work. I think for now though, its the closest thing to a stock image we have
Brilliant thank you, will give it a try.
Think I need to tune up on Unix....
helen_xxxx said:
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Click to expand...
Click to collapse
On OSX you can just drag the fastboot-mac file from finder into the terminal window and it will automatically fill in the path for you, then type the rest of the unlock command and hit enter
chandlerweb said:
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Click to expand...
Click to collapse
The Droid with triangle actually is stock recovery. When you see it just press power + volume down.
Sent from my Galaxy Nexus using XDA App
I hope the LTE version is as easy to root/unlock as this.
Knowing Verizon though...probably not.
Related
DISCLAIMER
Thank you to all the DEV'S who have made this possible BIG UPS TO YOU
This worked for me, and in theory if my instructions are followed carefully it will work for you.
However if your results are not the same I am in no way responsible for any dammage done to your tablet!
THE GOOD STUFF
This was tested on Acer A100 on the latest ICS LEAK found here http://forum.xda-developers.com/showthread.php?t=1510706
Also my PC is running windows 7 x64
(Follow install instructions carefully)
First install the latest ICS leak http://vache-android.com/v1/index.ph...files&file=148
Once complete do a factory data reset on your device from the settings/backup and restore menu on the tablet
When that is complete, Root your Device using the method found here http://forum.xda-developers.com/showthread.php?t=1531646
( again Follow instructions Carefully )
BE ABSOLUTELY SURE YOUR DEVICE IS ROOTED BEFORE YOU GO ANY FURTHER!!
Unlock your BOOTLOADER using the method here http://forum.xda-developers.com/showthread.php?t=1557445
(Really be careful here!)
This is where it gets tricky download http://forum.tegraowners.com/viewtopic.php?f=7&t=369 for your OS and extract recovery_thor17_403.img to the root of your platform-tools folder for instance mine is C:\android-sdk\platform-tools
Once completed on your PC open a command prompt as an administrator and navigate to your platform-tools folder from cmd prompt e.g. cd c:\android-sdk\platform-tools and hit enter
next type the following commands:
adb reboot bootloader
once in bootloader mode type:
fastboot flash recovery recovery_thor17_403.img
and hit enter you will see it flash to your device within a couple of seconds.
once complete with the tablet in upright landscape mode ( home button on the right hand side ) power the device down and power it back on while holding the leftmost volume button firmly when it vibrates you may release the power button.
continue to hold the volume button until you see Booting recovery kernel image on the screen.
if all went well you now have cwm on your device
now for rom manager!
boot back into android OS and navigate to the google market, search for rom manager in the upper search pane.
download the app and install
open the app and press ok
next press flask clockworkmod recovery
next confirm your phone model
a popup will say your device is not officially supported press yes
next confirm version 3.x+
and you should be good to go
Sent from my A100 using xda premium
masterpker2 said:
First check out this post http://www.acertabletforum.com/foru...rkmod-recovery-your-acer-iconia-tab-a200.html
Download the updated file from the above website, extract it to your desktop, and run acera200simpletool.bat and follow the onscreen instructions.
Once complete download the rom manager app from the market and install it.
Once installed open from manager and choose flash clockwork mod recovery from the top of the list, then confirm your device is Acer a100. It will say there is currently no recovery for your device and ask if you installed a custom one, choose yes and select the second option it should say 3.x.x or something to that effect. Again confirm your selection and tada you now have cwm and a working from manager. I have tested this and made a complete backup already. Cheers
Sent from my A100 using xda premium
Click to expand...
Click to collapse
hello masterpcker...Did you install anything else first? Were you just using the standard a100 root? Also, did you unlock your bootloader beforehand? thanks so much friend
Yes I unlocked my boot loader first, and my device was rooted so all I did was run the .bat file from the above website and choose option 3 install recovery only. I am about to try a modded a500 from and see what it does.
Sent from my A100 using xda premium
masterpker2 said:
Yes I unlocked my boot loader first, and my device was rooted so all I did was run the .bat file from the above website and choose option 3 install recovery only. I am about to try a modded a500 from and see what it does.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
I will be eager to hear how that comes out! I wish you the best of luck, but I'm not real confident. let us know the outcome if you don't mind....good luck!
For some reason I followed the directions to install CWM and it doesn't work.
When I try to boot to recovery all I see is the android mascot on it's back with a warning sign. If I press the home button it brings up the Android System Recovery, which I believe is the stock recovery. I'm not even sure how to select the items. I can only highlight the menu items using the volume keys.
It doesn't look like the cwm that I have flashed on my atrix.
Any ideas?
Edit...
Btw, I did unlock my bootloader
Well the a500 modded rom was a bust, it just booted to a really colorful screen lol. But my Android backup worked great for reinstall
Sent from my A100 using xda premium
Myster1ous what os are you running and what method for root did you use?
Sent from my A100 using xda premium
masterpker2 said:
Myster1ous what os are you running and what method for root did you use?
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Running Windows 7, I did the root method from here
http://forum.xda-developers.com/showthread.php?t=1531646
Did you try running the script as administrator?
Sent from my A100 using xda premium
masterpker2 said:
Did you try running the script as administrator?
Sent from my A100 using xda premium
Click to expand...
Click to collapse
I did, nothing still. I'm going to have to look at the batch file and manually input in the commands. Maybe that will do a difference
myster1ous said:
I did, nothing still. I'm going to have to look at the batch file and manually input in the commands. Maybe that will do a difference
Click to expand...
Click to collapse
Did you ever get it to work properly? I am having the same problem now.
@masterpker2...are you running linux? i am running windows 7 here and i am getting a [cant install recovery.img] from the a200 batch.....did you have any problems with this to begin with? thanks
I had to dd it to the correct partition and then I was able to get in, but I don't recommend doing it that way!
shadowofzeus said:
I had to dd it to the correct partition and then I was able to get in, but I don't recommend doing it that way!
Click to expand...
Click to collapse
did you have the same problem as we are having? is everything working correctly with you now? thanks
Followed instructions... works perfectly on Win 7 x64... thanks man!! Nandroid in Progress ...
A101
And for the A101, this method will not work?
oneovakindoldys2 said:
Did you ever get it to work properly? I am having the same problem now.
@masterpker2...are you running linux? i am running windows 7 here and i am getting a [cant install recovery.img] from the a200 batch.....did you have any problems with this to begin with? thanks
Click to expand...
Click to collapse
Nope, never got it working.
shadowofzeus said:
I had to dd it to the correct partition and then I was able to get in, but I don't recommend doing it that way!
Click to expand...
Click to collapse
What's the syntax did you use to dd to the device?
I found this dd syntax in the other thread. That the same one you used?
Code:
su
dd if=/mnt/external_sd/recovery.img of=/dev/block/mmcblk0p1
-Extract the zip folder "recoverycwma100" ( It's a recovery into Acer a200 simple tool )
-Copy ''recovery.img'' into your external sd card
-open a terminal emulator to your A100 ( root acces !!! )
- Write the following commands :
su
dd if = / mnt / external_sd / recovery.img of = / dev/block/mmcblk0p1
-wait a message '' xxxx bytes transferred in... ''
-exit terminal
-open root explorer with a mount system
-rename the file '' install-recovery.sh'' into /etc/ it '' install-recovery.bak''
Reboot into recovery with volum down + power , and Enjoy
leclasheur22 said:
-Extract the zip folder "recoverycwma100" ( It's a recovery into Acer a200 simple tool )
-Copy ''recovery.img'' into your external sd card
-open a terminal emulator to your A100 ( root acces !!! )
- Write the following commands :
su
dd if = / mnt / external_sd / recovery.img of = / dev/block/mmcblk0p1
-wait a message '' xxxx bytes transferred in... ''
-exit
Reboot into recovery with volum down + power , and Enjoy
Click to expand...
Click to collapse
Can't we just go into fastboot and use fastboot flash recovery recovery.img?
If you're running linux or just want to use adb it's way more simple than it looks.
Code:
Adb reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot
And if you brick your device by accidently installing the wrong boot.img
find your respected rom .zip file that you are currently using and use this.
Code:
Adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
blmvxer said:
If you're running linux or just want to use adb it's way more simple than it looks.
Code:
Adb reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot
And if you brick your device by accidently installing the wrong boot.img
find your respected rom .zip file that you are currently using and use this.
Code:
Adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I can confirm that I have already flashed the recovery.img via fastboot, however cwm still fails on my particular tab. I did a full factory reset and flashed the entire new ics through recovery with the exact same results. I will be investigating the cause of some tabs doing this later tonight when I get home from work. If someone figures this out please post. I have gotten the recovery.img to flash via the a200cwm, however android exclamation upon recovery attempt. i have tried all three paths with no success. I am almost certain that it is a problem with the rooting method, but i won't have time to have a look until tonight. thanks and goodluck! I think the problem could be because of installing different rooting methods in the past, however I have yet to find a way to solve it.
There seems to be a lot of confusion in the air around either how to unlock your bootloader or how to install a new recovery.
I am writing this as a very easy step by step guide to do all the things necessary to get your new HTC One X ready to accept some custom fun so here goes nothing
Unlocking Your Bootloader
Words of warning - unlocking your boot loader will wipe your data partition
Things you have put on your internal memory will be fine but all of your apps etc will be gone.
Before we can even think about doing anything the first port of call is unlocking your bootloader.
As of the time of writing this there is currently no S-OFF method available so this is the only method of flashing a new recovery or boot image.
I'm going to keep this as simple as possible
1. Go Here "http://www.htcdev.com/" and create yourself an account on HTCDEV.
2. Download These Fastboot Files
3. Make a new folder on your C: drive called fastboot.
4. Extract The Zip downloaded in step 2 to the new folder
5. Go Here http://www.htcdev.com/bootloader/ and select "All Other Supported Models" and "then begin unlock bootloader"
6. Yes, Tick both Boxes, Proceed
7. Skip up to step 8 as we have all we need for the first 7 steps
8. Power off your phone by holding the power button down for 10 seconds
9. Power your phone on by holding power and volume down
8. Highlight Fastboot With Volume+or- then press Power
9. plug your phone into your PC and open a Command Prompt.
(windows XP - Click Start > Run > type CMD in box then press OK
(Windows 7 - Click Start > type CMD in search box then press Enter)
10. cd to your folder where we put fastboot files cd c:\fastboot
11. type this into your command prompt window fastboot oem get_identifier_token
12. select & copy the text as per step 9 on the HTCDev website
13. paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
14. download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files to in step 2
15. type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
16. The Display Will change on your phone, press Vol + to accept and power to confirm.
Note you may get an error on screen or on your cmd window (cant remember which now) that says something about too many links. It is nothing to worry about and your bootloader will still unlock
Congratulations You Have Successfully Unlocked Your Bootloader
Now to the good stuff
Installing A Recovery
This one is very simple to do once you have your bootloader unlocked.
A thing to note; at present there is no USB-Mass Storage in recovery so if you are planning to install a custom rom i would get it put on the internal memory of your phone now rather than messing things up later and been unable to install it
(if you have follwed my unlocking guide skip to step 4)
1. Download These Fastboot Files
2. Make a new folder on your C: drive called fastboot.
3. Extract The Zip downloaded in step 1 to the new folder
4. The Official Version of CWM has been released and is now capable of flashing all roms, you can grab it HERE
5. download the custom recovery and save it in the same folder as you did the fastboot files
6. Power Phone Off by Holding power button for 10 secs
7. select Fastboot with volume + or - then press power
8. plug your phone into your PC and open a Command Prompt.
(windows XP - Click Start > Run > type CMD in box then press OK
(Windows 7 - Click Start > type CMD in search box then press Enter)
9. cd to your fastboot files folder cd c:\fastboot
10. type in your command prompt fastboot flash recovery name_of_recovery_image.img
in my case it was fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img
Congratulations you now have a custom recovery
power off the phone by holding power for 10 seconds
power on the phone holding power+volumer down
choose recovery with volume +/- then power to select
You are now on your custom recovery
First Thing - Do A Nandroid Backup Of Your Current Rom In Case anything bad happens
Make sure you already have your new rom on your internal memory as you cannot enable mass storage in the current recovery builds.
Wipe then Flash your new Custom Rom
Or you can download the latest SuperSU binaries from HERE and install them Via Recovery to just root the stock rom
Hope this helps some of you
Thx !
Wasted a lot of time yesterday downloading entire Java, SDK, for a 2 minutes job...
Your package seems great !
fabulous guide buddy
thanks a million
Good idea such guide!
Sent from Samsung Galaxy Nexus
so freakin useful !
luminouche said:
Thx !
Wasted a lot of time yesterday downloading entire Java, SDK, for a 2 minutes job...
Your package seems great !
Click to expand...
Click to collapse
to be fair i dont even think we need the 2 adb files in the package i uploaded as we are only using fastboot however the htcdev website said to have them so may aswell include it, only a small download
thank you
It was exactly what I was searching for... Thanks a lot
Nice tut
Wasted a lot of time yesterday downloading entire Java, SDK, for a 2 minutes job...
Click to expand...
Click to collapse
No waste at all.....Watch u`ll need it one day
"adb reboot recovery" for start
Thank you you helped me a lot with such
A geest device:thumbup::thumbup:
Sent from my HTC One X using xda premium
nimoi62 said:
It was exactly what I was searching for... Thanks a lot
Click to expand...
Click to collapse
+1!! It's easy once someone spells it out, lol.
Question (and I know it's probably been discussed elsewhere, but clearly I've only just noticed it), with this issue with not being able to enable mass storage...does this mean that once I've chosen a particular ROM, placed it onto SD and unlocked/flashed recovery, I won't be able to flash another different ROM? Can I not just flash through fastboot??
Is it worth collating the oem get_identifier_token calls and responses? As there may be an obvious correlation whereby HTVDev can be bypassed or the process simplified.
777ace said:
+1!! It's easy once someone spells it out, lol.
Question (and I know it's probably been discussed elsewhere, but clearly I've only just noticed it), with this issue with not being able to enable mass storage...does this mean that once I've chosen a particular ROM, placed it onto SD and unlocked/flashed recovery, I won't be able to flash another different ROM? Can I not just flash through fastboot??
Click to expand...
Click to collapse
If the dev has released a set of fastboot images then you can install them through fastboot.
You can change roms as you still have USB mode in the custom Rom you have, the only real problem comes if you format your system partition and then realise you don't have a Rom to install on the sdcard, at this point you can't get to a position where you can put a new zip on so you would have to do the ruu and start from scratch
It's only when in the recovery that USB doesn't work, as soon as you flash your new Rom and boot it you can use USB as normal
Sent from my HTC One X using XDA
Excellent
Hi
Thank you for taking the time to put this together.
I think your tutorial will save many people much sweat!!
Plus it will help reduce the "I've bricked my phone" threads also!!
Cheers
Aussie
f4flake said:
Is it worth collating the oem get_identifier_token calls and responses? As there may be an obvious correlation whereby HTVDev can be bypassed or the process simplified.
Click to expand...
Click to collapse
It's highly unlikely that we will be able to learn anything by the identifier tokens, if anything is to be learned it would be finding what link your own identifier token has to the unlock_code.bin that they send you in the email, but we will probably never know
Sent from my HTC One X using XDA
Great set of instructions.
Really looking forward to getting new HOX now ;-)
Sent from my A500 using XDA Premium HD app
I cant download the boot file as modacos website catchpa image isnt working for me... any help here?
aussie1234 said:
Plus it will help reduce the "I've bricked my phone" threads also!!
Click to expand...
Click to collapse
Hahahahahahahahaha....nice one!
Wait...you were kidding, yeah??
When I do the process of unlock from htcdev, I got this error:
Error Code: 122.
Error Reason: Email cannot be sent.
Anyone can help?
Same error Message for me, but it seems to be an error by HTCdevs Email sending like you see, i done same with my Sensation XL before 2 months and it works. Surely HTCdevs have any issues by sending mails from their system! Hope thats not generally when ONE X has Software: 1.26.401.2
But cool TUT! I`m impressed!
I have 1.26.707.4 getting the same 122 error interspersed with site unavailable. I think something is wrong on htcdev at the moment
Help! My Galaxy Nexus sudden going through BootLoop (Google logo kept coming back).
I have new born baby photos and video that I need to pull them out to my PC.
SO I read Mike 's Toolkit 7.8 and trying it.
I do not know what extract model and built is my phone. This is original phone so I bootloader is still LOCKED.
With Mike toolkit I followed up his Toolkit instuction #14.
Here is what I done.
1) In GNex TOOLKIT V7.8. I choose from 4.0.1 to 4.0.4 android build and model version (Yakju-Maguro since I am in Canada using Rogers/Fido as Carrier). Then I chose option#1 to install Nexus Window 7 drivers. This didn't work. My Window 7 did'nt regconize it.
2) During the installation of PDaNet. I hold Power On Buttom + Up Bottom (I think) Fastboot mode. I am able to get a page that shows me my "bootloader version", "Baseband version" etc...Only then PDaNet then installed Android driver successfully to my WIndow 7 Device Manager.
3) Go back to Toolkit V7.8 menu. Choose all 4.0.1 to 4.0.4 android build and model version.
I can now see my Serial Number on then top left side onw.
4) Then I chose #14 pull data from my phone.
It said the Device not found/regconized. Choose 4.0.1 to 4.0.4 android build and model
So I don't what I did wrong..
Please help..me..
I can only access to fastboot mode? Can I still files/photos pull?
Help me
Thank you very much! Your help is greatly appreciated!
step 1) stop using a toolkit
step 2) http://forum.xda-developers.com/showpost.php?p=30772799&postcount=9
Zepius said:
step 1) stop using a toolkit
step 2) http://forum.xda-developers.com/showpost.php?p=30772799&postcount=9
Click to expand...
Click to collapse
Thank you Zepius! Got few question..
My phone is in bootloop .so I can't go to android market and install Android SDK. I can't turn debugger mode on..
"assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager."
Installation of Android SDK to my window 7 pc?
Please tell me what I need to do. Much appreciated!
First install 1wayjonny's drivers on your PC so it can communicate with your phone. See his thread in the dev section.
Then get adb (and fastboot) and unzip them somewhere on your PC. There's a link to a zip file containing those two commandline programs in one of efrant's threads. You don't need to install the whole SDK, just adb.
Then boot into recovery mode, since android mode bootloops.
Then follow the instructions in the link Zepius provided to use adb commands to pull your data from your phone to your PC.
Since you can get into fastboot, I would :
- download a flashable custom recovery image such as clockworkmod
- boot into bootloader (fastboot)
- type: fastboot boot recovery nameofimage.img
- start adb
- type: adb pull /sdcard c:\somepathhere
This will not flash the custom recovery but it will boot it once. The adb command will copy your entire sdcard contents.
Sent from my Galaxy Nexus using Tapatalk 2
strumcat said:
First install 1wayjonny's drivers on your PC so it can communicate with your phone. See his thread in the dev section.
Then get adb (and fastboot) and unzip them somewhere on your PC. There's a link to a zip file containing those two commandline programs in one of efrant's threads. You don't need to install the whole SDK, just adb.
Then boot into recovery mode, since android mode bootloops.
Then follow the instructions in the link Zepius provided to use adb commands to pull your data from your phone to your PC.
Click to expand...
Click to collapse
Thank you for your help!
1wayjonny's driver is called "Universal Naked Driver 0.7"?
http://forum.xda-developers.com/showthread.php?t=1161769
Where can I find efrant's threads about adb + fastboot zip file(s)?
Sorry to keep bothering you.
Thank you!!
Petrovski80 said:
Since you can get into fastboot, I would :
- download a flashable custom recovery image such as clockworkmod
- boot into bootloader (fastboot)
- type: fastboot boot recovery nameofimage.img
- start adb
- type: adb pull /sdcard c:\somepathhere
Click to expand...
Click to collapse
Thank you!
My first and most priority is not to fix my bootloop issue but I need to get my phone photos+video backup.
So can I just make sure I get adb (Android SDK development and tools install) and adb my device?
then adb pull /sdcard c:\somepaththere?
I just want backup it first .. before I fix my phone or fastboot boot recovery nameofimage.img.
Thank you again.. I already lose some nights of sleeps because when I thought of photos that I took with my baby.
Gosh.. what a nightmare!
May I suggest to install either dropbox, box, Google drive and have it sync all your media, so if you ever have this happen again or worse the pics will be safe. Just saying..
Sent from my Galaxy Nexus using Tapatalk 2
Duce HD2 said:
May I suggest to install either dropbox, box, Google drive and have it sync all your media, so if you ever have this happen again or worse the pics will be safe. Just saying..
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes. Once I get my photos and phone fix. I will.
Actually my coworker just said the same thing to me.
He has Samsung Nexus phone as well.
Thank you.
Someone please confirm me.
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
2) Install Android SDK with adb and fastboot commandline to my PC?
3) Boot my Nexus to bootloops (power buttom+volume)
4) Then connect my phone with USB and connect to my PC
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?
jurassic98 said:
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
2) Install Android SDK with adb and fastboot commandline to my PC?
3) Boot my Nexus to bootloops (power buttom+volume)
4) Then connect my phone with USB and connect to my PC
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?
Click to expand...
Click to collapse
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879
jurassic98 said:
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
Click to expand...
Click to collapse
Yep.
2) Install Android SDK with adb and fastboot commandline to my PC?
Click to expand...
Click to collapse
You don't need the entire SDK. You can if you want to, but unless you're planning on developing apps on Android, the SDK is overkill for just fastboot and adb. I suggest using the package efrant links to in his 101 & FAQ: http://forum.xda-developers.com/showthread.php?t=1812959
3) Boot my Nexus to bootloops (power buttom+volume)
Click to expand...
Click to collapse
Into bootloader: volume up+down+power.
4) Then connect my phone with USB and connect to my PC
Click to expand...
Click to collapse
Yes.
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?
Click to expand...
Click to collapse
Almost. Adb won't work in when booted into bootloader. When you are in the bootloader, use the steps I mentioned earlier. In custom recovery, you do have the adb interface.
efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
Thank you efrant! I have been reading your article and Galaxy Nexus 101&FAQ.
My quick question is will step #6 fastboot boot recovery.img wipe all my photos/video/user data? Or this is like linux rescue disk? where you boot into a rescue environment?
Thank you again!
jurassic98 said:
Thank you efrant! I have been reading your article and Galaxy Nexus 101&FAQ.
My quick question is will step #6 fastboot boot recovery.img wipe all my photos/video/user data?
Click to expand...
Click to collapse
No, it won't wipe anything.
jurassic98 said:
Or this is like linux rescue disk? where you boot into a rescue environment?
Thank you again!
Click to expand...
Click to collapse
Yes, that's exactly like what it is.
efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
From my understanding you can't pass adb commands in fastboot. However if you're able to boot into recovery mode, you'll be good
henno87 said:
From my understanding you can pass adb commands in fastboot. However if you're able to boot into recovery mode, you'll be good
Click to expand...
Click to collapse
Nope, you cannot. fastboot = fastboot, adb = adb. Different interfaces.
Try it.
efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
Whew! efrant to the rescue. I really didn't want to look up a bunch of links.
I was just thinking that your instructions are so concise and organized that they're almost like a scripting language for "human virtual machines" that interface with Android.
strumcat said:
Whew! efrant to the rescue. I really didn't want to look up a bunch of links.
I was just thinking that your instructions are so concise and organized that they're almost like a scripting language for "human virtual machines" that interface with Android.
Click to expand...
Click to collapse
LOL, thanks! (Sorry, you are limited to 8 thanks per day)
The thing is, all of those links are in the 101 thread.
efrant said:
LOL, thanks! (Sorry, you are limited to 8 thanks per day)
The thing is, all of those links are in the 101 thread.
Click to expand...
Click to collapse
Help! me..
I run "fastboot boot recovery.img"
it says
c:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.680s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.690s
c:\Android>
In the bootloader , Lock state = Locked.
What do I do now? I need my photos and video.
Help me!
jurassic98 said:
Help! me..
I run "fastboot boot recovery.img"
it says
c:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.680s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.690s
c:\Android>
In the bootloader , Lock state = Locked.
What do I do now? I need my photos and video.
Help me!
Click to expand...
Click to collapse
You said your bootloader was unlocked in the first post, no???
jurassic98 said:
[snip]
I do not know what extract model and built is my phone. This is original phone so I bootloader is still unlocked.
Click to expand...
Click to collapse
If your bootloader is locked, which it obviously is, you canNOT use what I had suggested. You need to try using ADB backup (use copkay's guide). However, as I mentioned before, given that you have a bootloop, it may not work...
This is a prefect example of why you should leave your bootloader unlocked -- if it was, you'd easily be able to recovery your data.
Introducing.... Superboot!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
APPLY THIS AT YOUR OWN RISK!
Superboot r1 - DOWNLOAD - MD5: f53825a2df09277f899b6738b3a059d5
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by './superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by './superboot-linux.sh'
Note: If you are using a retail device, you may need to unlock the bootloader first, using './fastboot-windows oem unlock' (or the appropriate version for your machine, included in this zip). Note that the OEM unlock sequence wipes your device, so consider doing an 'adb backup' beforehand if required!
Enjoy!
P
paulobrien said:
Introducing.... Superboot!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
APPLY THIS AT YOUR OWN RISK!
Superboot r1 - DOWNLOAD - MD5: f53825a2df09277f899b6738b3a059d5
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by './superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by './superboot-linux.sh'
Note: If you are using a retail device, you may need to unlock the bootloader first, using './fastboot-windows oem unlock' (or the appropriate version for your machine, included in this zip). Note that the OEM unlock sequence wipes your device, so consider doing an 'adb backup' beforehand if required!
Enjoy!
P
Click to expand...
Click to collapse
I almost asked if anyone could confirm that this works... then I saw that it was written by Paul O'Brien himself.
Awesome!
So this won't wipe anything at all, right?
the superuser not. But u have to unlock it before and that wipe your device
treyy said:
the superuser not. But u have to unlock it before and that wipe your device
Click to expand...
Click to collapse
How can i save all program, data, internal storage, aplications, etc, before unlock bootloader?
comand "adb backup" save all this? and then, how restore the backup¿?
This method of root changus the stock recovery? Or only installs ths superuser whitout changes on any stock system?
For OTA updates, i need to relock recovery or not?
Thank you
noodlesfordaddy said:
I almost asked if anyone could confirm that this works... then I saw that it was written by Paul O'Brien himself.
Awesome!
So this won't wipe anything at all, right?
Click to expand...
Click to collapse
Correct, unlocking does though.
rufus- said:
How can i save all program, data, internal storage, aplications, etc, before unlock bootloader?
comand "adb backup" save all this? and then, how restore the backup¿?
This method of root changus the stock recovery? Or only installs ths superuser whitout changes on any stock system?
For OTA updates, i need to relock recovery or not?
Thank you
Click to expand...
Click to collapse
No recovery change, just Superuser, no need to relock for OTA.
P
Sent from my Nexus 7 using Tapatalk 2
Just rooted. Thanks!
paulobrien said:
Correct, unlocking does though.
No recovery change, just Superuser, no need to relock for OTA.
P
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thank you, but unlock bootloader wipe all..
For backup, only with command "adb backup" works fine?
Yes, the oem unlock wipes, use adb backup.
P
So I've had my Nexus 10 a few days and unlocked only. Can I use this as is or do I need to wipe my device first? Noob here and have been hearing horror stories of boot loops etc with the other methods so this appeals to me....won't lose any of my data or app installs because it's already unlocked right?
AjSvb said:
So I've had my Nexus 10 a few days and unlocked only. Can I use this as is or do I need to wipe my device first? Noob here and have been hearing horror stories of boot loops etc with the other methods so this appeals to me....won't lose any of my data or app installs because it's already unlocked right?
Click to expand...
Click to collapse
This does not wipe your device. Unlocking it does. If you have already unlocked, this will not erase anything. Just an easy way to get root.
Thanks worked great for me, was already unlocked but now rooted too
Thank you. I rooted tablet easy.
This method not change stock recovery. Then...
With bootloader unlocked can i update by ota? Keep root updating by ota?
OTA should work fine and likely stay rooted too.
P
Sent from my PadFone 2 using Tapatalk 2
Rooted without unlocking on mine just fine.
Croak said:
Rooted without unlocking on mine just fine.
Click to expand...
Click to collapse
Your tab was shipped with an unlocked bootloader?
Alleycat68 said:
Your tab was shipped with an unlocked bootloader?
Click to expand...
Click to collapse
Bootloader is still locked, just extracted the archive Paul provided, put it in fastboot mode, ran the batch file, and I was rooted.
Worked as well for me while locked.
+1 confirmed rooted while on locked bootloader, made esp easy with "naked drivers" package.
wow, if i konw this, i dont unlock my bootloader Now I have unlocked boot.... I wait dont have any problems with ota updates!
Is there anything special or additional that needs to be done in order to root without unlocking? In other words, can I just follow the op steps as if I have unlocked the boot loader?
Hello everyone,
I bought an used HTC One M8 and I realized it is rooted and with a TWRP recovery.
Recently I've been waiting for the auto update for Android 4.4.3 and I believe I haven't received it because of the issue I referred earlier.
Is there anyway to receive OTA's now? Since I don't value root that much I'm considering every options.
By the way, it's the international unlocked version of the device.
Thanks for the support.
Nun0fskY_ said:
Hello everyone,
I bought an used HTC One M8 and I realized it is rooted and with a TWRP recovery.
Recently I've been waiting for the auto update for Android 4.4.3 and I believe I haven't received it because of the issue I referred earlier.
Is there anyway to receive OTA's now? Since I don't value root that much I'm considering every options.
By the way, it's the international unlocked version of the device.
Thanks for the support.
Click to expand...
Click to collapse
flash philz recovery (search for it and flash it in fastboot)
get ur cid use this command in fastboot
fastboot getvar version-main
fastboot oem readcid
then download ur recover (philz one)http://forum.xda-developers.com/showthread.php?t=2701376
open zip file and copy recovery.img file to platform tools (if u dont know whats platform tools is do a decade search how to set up android sdk )
put recovery file in folder in ur phone named clockworkmod >backup>XXXXXXXXXXX
get ur phone into recovery mode then select restore from back up or some thing like that in recovery
it will detect ur file right away if u put it there and start doing its stuff
after that ur not done yet
get in to fastboot
then type in comnd promp
(right click in platform tools folder open comand promt window here) then type
fastboot flash recovery recovery.img
last thing is this command
fastboot oem lock
and do a factore re set ur good to get ota s now lol omg
This is my first non Samsung smartphone so it will take me some time to understand how to do all of that.
I'll read it again and again, do some searching and I'll get back with the results of my journey.
Lol thanks
Btw do you happen to know any tutorial or video tutorial on this subject in order to make it possible for me to succeed? Lol
Nun0fskY_ said:
I bought an used HTC One M8 and I realized it is rooted and with a TWRP recovery.
Recently I've been waiting for the auto update for Android 4.4.3 and I believe I haven't received it because of the issue I referred earlier.
Click to expand...
Click to collapse
Root will not prevent notification and download of the OTA, only its installation. But if a custom ROM is installed, that may prevent you from getting the notification.
If you don't want to mess with this stuff, I'd complain to the seller and ask for refund/exchange if they sold it to you without telling you it was modded. Unless you got a really good deal, or something.
It was actually a good deal.
If it prevents me from installing the OTA it's still bad.
Being the unlocked international version shouldn't I have the 4.4.3 KK available by now?
Nun0fskY_ said:
Being the unlocked international version shouldn't I have the 4.4.3 KK available by now?
Click to expand...
Click to collapse
Not sure (not my version) but as that version has been deployed to a good number of countries/regions, it might take some time to roll out to all users.
redpoint73 said:
Not sure (not my version) but as that version has been deployed to a good number of countries/regions, it might take some time to roll out to all users.
Click to expand...
Click to collapse
Hmm ok..
With the device conditioned as I mentioned is there anyway at to update when it's available or the only way to do it is with the procedure zhiarw described?
Nun0fskY_ said:
Hmm ok..
With the device conditioned as I mentioned is there anyway at to update when it's available or the only way to do it is with the procedure zhiarw described?
Click to expand...
Click to collapse
The described process is the best way to get to stock ROM and recovery, and therefore receive OTAs.
I couldn't understand the process completely.
Is this what i'm supposed to do?
https://www.youtube.com/watch?v=8HhOAdBOaYE
Nun0fskY_ said:
I couldn't understand the process completely.
Is this what i'm supposed to do?
https://www.youtube.com/watch?v=8HhOAdBOaYE
Click to expand...
Click to collapse
idk i never use tool kit but if this is ur first htc phone then CMD or Terminal will be ur new best friend
ill go with u step by step
do u have adb ? and fastboot service if yes
we will start with philz recovery
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8/
any of them will work
I don't have adb.
Nun0fskY_ said:
I don't have adb.
Click to expand...
Click to collapse
install htc drivers from htc transfer tool
then download this and extract it in a folder
http://downloadandroidrom.com/file/tools/fastboot.zip
inable adb from developer option in ur phone
open the file u made for fastboot files
press and hold shift and right click
open command prompt here
look at ur phone unlock it
then type
adb devices
ri8 after that
press agree on ur phone and tip it as trusty pc
then this command
adb reboot bootloader
on ur phone press power button to chose fast boot
then put philz recovery in the folder that adb and fastboot files are in
use this comand
fastboot flash recovery philz_touch_6.25.5-m8.img
and enter
ur good to go now download philz recovey file that fits with ur CID
there is CID checker in play store or use the command that i told u before
turn ur phone
find clockwork mode folder
open it
if there is backup folder good if not make one name it backup
the recovery u downloaded contain file named
recovery.img
copy and paste in fastboot/adb folder
put the philz recovery in clockworkmod>backup>2014-07-22.01.52.47_KOT4xxx_release-keys(the recovery file have name like this)in ur phone
then turn the phone off the hold volume down and power (this will get u in bootloader )chose recovery
it will lead u in philz recovery and restore it will show the file name then yes
reboot now
then put phone in to fastboot type in the command prompt
fastboot flash recovery recovery.img
it will have to be successful then
fastboot oem lock
and do factory reset ur good now bro i cant clearfiy more just ask if u have problem
I tried to translate it to my main language and I believe it is this (sorry for being so insisting, it's just that i bricked one samsung once and i can't risk anything on this one lol)
1. Install drivers HTC from htc transfer tool (can't figure out how, should i install sync is that it?)
2. Download and extract "fastboot.zip"
3. Enable USB debugging on the phone
4. Open the file i extracted from "fastboot.zip"
5. Press+Hold Shift e Right Click (should do this on the file i opened right?)
6. Open command prompt here
7. Unlock the phone
8. Type: "adb devices" (on the exe in the PC?)
9. Press Agree on the phone and "trust" the PC
10. Command: "adb reboot bootloader" (again, this is on the .exe in the PC right?)
11. On the phone press "Power" to choose fast boot
12. Put recovery philz on the folder where are the adb/fastboot files
13. Use command: "fastboot flash recovery philz_touch_6.25.5-m8.img"
14. Download the recovery that matches my CID
15. Turn on the phone
16. Search for the clockwork folder
17. If it has a "backup" folder good, if not, create a folder named "backup"
18. Copy "recovery.img" i just downloaded to the "fastboot/adb files" folder
19. Put philz recovery in "clockworkmod>backup>2014-07-22.01.52.47_KOT4xxx_release-keys" (something like that) on the phone
20. Turn off phone and go into bootloade (power+vol. down) -> go to recovery
21. (In philz recovery) do "restore" and choose the file i placed in the phone
22. Put the phone in fastboot
23. Type command: "fastboot flash recovery recovery.img"
24. Type command (on fastboot): "oem lock"
25. Do a factory reset.
Mostly the driver part is messing me up, if i could make sure how to install the right drivers i could explore through the following steps.
Nun0fskY_ said:
I tried to translate it to my main language and I believe it is this (sorry for being so insisting, it's just that i bricked one samsung once and i can't risk anything on this one lol)
1. Install drivers HTC from htc transfer tool (can't figure out how, should i install sync is that it?)
2. Download and extract "fastboot.zip"
3. Enable USB debugging on the phone
4. Open the file i extracted from "fastboot.zip"
5. Press+Hold Shift e Right Click (should do this on the file i opened right?)
6. Open command prompt here
7. Unlock the phone
8. Type: "adb devices" (on the exe in the PC?)
9. Press Agree on the phone and "trust" the PC
10. Command: "adb reboot bootloader" (again, this is on the .exe in the PC right?)
11. On the phone press "Power" to choose fast boot
12. Put recovery philz on the folder where are the adb/fastboot files
13. Use command: "fastboot flash recovery philz_touch_6.25.5-m8.img"
14. Download the recovery that matches my CID
15. Turn on the phone
16. Search for the clockwork folder
17. If it has a "backup" folder good, if not, create a folder named "backup"
18. Copy "recovery.img" i just downloaded to the "fastboot/adb files" folder
19. Put philz recovery in "clockworkmod>backup>2014-07-22.01.52.47_KOT4xxx_release-keys" (something like that) on the phone
20. Turn off phone and go into bootloade (power+vol. down) -> go to recovery
21. (In philz recovery) do "restore" and choose the file i placed in the phone
22. Put the phone in fastboot
23. Type command: "fastboot flash recovery recovery.img"
24. Type command (on fastboot): "oem lock"
25. Do a factory reset.
Mostly the driver part is messing me up, if i could make sure how to install the right drivers i could explore through the following steps.
Click to expand...
Click to collapse
9-look at the attachment
18-recovery.img in recovery folder u just copy it and put it in extracted adb/fastboot folder
19-if u mean the recovery (restore) files yes, in (backup)folder on ur phone
20-just get ur self into bootloader and use volume to navigate the menu - (recovery) then press power
26--------------if u get any error from the command prompt u wont succeed
27------UR PHONE IS S-OFF MEANS SECURITY ON BRICKING PHONE THIS WAY IS HARDER THAN U THINK .
Ok now! I believe I've made some progress! Or maybe I didn't... Do you happen to have a direct link for the drivers? I believe that is the problem for the commands not working properly.. even though I have installed HTC sync...
Jesus what a mess lol
Nun0fskY_ said:
Ok now! I believe I've made some progress! Or maybe I didn't... Do you happen to have a direct link for the drivers? I believe that is the problem for the commands not working properly.. even though I have installed HTC sync...
Jesus what a mess lol
Click to expand...
Click to collapse
There are a couple guides if you use the XDA "Search" function called "adb minimal drivers" "5 minute adb install" etc. that I've seen other folks recommend. Probably your best bet, although I personally can't recommend any particular thread, as I did it the hard way (Android SDK)!
HTC Sync can cause more issues than it solves, so I would try minimal drivers over HTC official ones. Or even uninstall drivers and let Windows find generic drivers for the device.
Yes, this is a lot of rather esoteric phone modding stuff (for someone that has never tried this type of thing before) to get your phone back to "stock". But if you case, possibly worth it for a "free" device upgrade. You're going to end up learning a lot more about Android than you ever wanted to know!
zhiarw said:
9-look at the attachment
18-recovery.img in recovery folder u just copy it and put it in extracted adb/fastboot folder
19-if u mean the recovery (restore) files yes, in (backup)folder on ur phone
20-just get ur self into bootloader and use volume to navigate the menu - (recovery) then press power
26--------------if u get any error from the command prompt u wont succeed
27------UR PHONE IS S-OFF MEANS SECURITY ON BRICKING PHONE THIS WAY IS HARDER THAN U THINK .
Click to expand...
Click to collapse
Ok now.
I've flashed the philz recovery and i did everything until the moment you tell me to create the folder insider the "clockworkmod" folder in the phone and named it "backup".
Next step is a bit confusing for me :S
Nun0fskY_ said:
Ok now.
I've flashed the philz recovery and i did everything until the moment you tell me to create the folder insider the "clockworkmod" folder in the phone and named it "backup".
Next step is a bit confusing for me :S
Click to expand...
Click to collapse
yes whats ur CID ? let me give u a nandroid back up if u dont know search play for cid getter
zhiarw said:
yes whats ur CID ? let me give u a nandroid back up if u dont know search play for cid getter
Click to expand...
Click to collapse
It's HTC__203
The ".zip" i downloaded has no file named "recovery.img" inside :S