Related
Hi there,
I am such an idiot, I deleted the framework-res.apk from /system/framework/ and rebooted. You all know what had to happen: the Nexus with FRF91 won't boot anymore.
So I am asking for help: Is there any way to restore (i.e. put a stock framework-res.apk) in that folder? I have ADB tools and stuff installed.
Or is there any way to access the sdcard without booting the system? I could put an update.zip there and apply it.
Of course, I'd rather not delete my apps and stuff but still better than a bricked phone.
Any help would be great. Thanks a lot.
try this:
1. put a copy of framework-res.apk in your sdk/tools folder (this can be taken from a copy of the rom that you have installed at the moment)
2. boot your phone like usual; when the bootscreen appears, enter this into a command window directed at your adb (SDK/tools is the tools folder in my adb):
Code:
cd/
cd SDK/tools
adb reboot recovery
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
this should put it into the correct folder and reboot the phone. give it a little time, whenever I flash a new FW-res it seems to take a little longer than when I have not to boot up. I have a desire, I am only presuming thats where it needs to go
Thank you very much for your answer.
Code:
adb reboot recovery
worked flawlessly when the boot animation was showing. Although it took quite a while until the device was recognized.
Now the Android dude with the exclamation mark is on the screen (recovery). Right now the device is not recognized. Therefore I cannot execute
Code:
adb remount
or any other adb commands.
This was one of my initial questions: how do I get to access the file-system from recovery?
Btw: is there any difference from manually (trackball + powerbutton) going to recovery to using adb?
Thanks
can you get into the green recovery screen by executing the .bat file after doing the reboot/recovery? I find sometimes it can take up to five tries to push the files correctly.
if you can do that, then you can execute the rest pretty easily.
you can even turn it into a 'mass storage device' to put an update.zip on the sdcard
edit: this one was the recovery I was meaning.
the other way to get into that is
Code:
How to boot in Recovery Mode
Boot the phone while holding down the VOLUMEDOWN-key.
Navigate to RECOVERY with the the VOLUMEDOWN-key.
Press the POWER-key to select.
anything other than the information above and I can't be much use, this is about as far as my adb and android knowledge extends sorry.
GL
yes, I do get the recovery screen but I cannot execute adb commands from there. Any hints?
Well, if you can't access terminal (console) from recovery, try fastboot, and reflash the whole firmware WITHOUT wiping. That should do the trick!
Ok, will try to do that. What I've done so far is copied update-nexusone-FRF91-stock-noradio-signed.zip to the sdcard's root, renamed it to update.zip and tried to install it via the stock bootloader (recovery with Volume UP + Powerbutton). This failed. Am I using a wrong Rom? Should I try to install this via fastboot?
wouldnt hurt. my next suggestion would then be an untouched rom (maybe 2.1 so you dont have a problem with the bootloader changing versions)
wouldn't fastboot allow me to copy the file to the system? I found this command for fastboot:
Code:
flash <partition> [ <filename> ] write a file to a flash partition
I think I will just have to flash the system-image:
Code:
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
Taken from http://forum.xda-developers.com/showthread.php?t=619153
Correct?
Then I need to find a system.img
Sorry for this double-post but I guess you guys don't come back, otherwise...
Can anyone provide a system.img for me? I've just tried the one from the stock PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip but received
Code:
sending 'system' (116663 KB)... OKAY
writing 'system'... INFOs
FAILED (remote: signature verify fail)
Edit: I have a LOCKED bootloader
can you either try using a stock rom rather than a cooked one, or try resigning the rom you are trying to flash?
Sent from my HTC Desire using XDA App
I have also accidentally deleted my framework-res.apk, and my X10 won't boot (duh). Now When I use the command "adb remount", I get the error message: "remount failed: Operation not permitted". How do I push framework-res.apk to my phone now?
I thought I was using a stock rom with
PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip
update-nexusone-FRF91-stock-noradio-signed.zip
How does resigning work? I guess there are tools for this. Never used a cooked rom so far.
signing roms: http://androidforums.com/developer-101/8665-how-signing-roms.html
try signing it again, then installing it.
the -signed extension to me sounds like someone dl'd the original, edited and resigned it (eg: to remove the radio). This edit may have been the reason why they are failing the verification. I dont know enough about the difference between fastboot and recovery to know any other reasons why it might fail in there.
this may be why it is not working in FASTBOOT
back to ADB, if you try it via that method and it fails, try killing the adb task in task manager, then try again. for me adb works after that more often than not.
nzdcoy said:
signing roms: http://androidforums.com/developer-101/8665-how-signing-roms.html
try signing it again, then installing it.
the -signed extension to me sounds like someone dl'd the original, edited and resigned it (eg: to remove the radio). This edit may have been the reason why they are failing the verification. I dont know enough about the difference between fastboot and recovery to know any other reasons why it might fail in there.
this may be why it is not working in FASTBOOT
back to ADB, if you try it via that method and it fails, try killing the adb task in task manager, then try again. for me adb works after that more often than not.
Click to expand...
Click to collapse
Okay, signing worked for the zip file. But the system.img is still not working.
What do you mean with adb? What should I do? I guess the problem is that the system is not fully booted and I don't get root at that stage.
which rom have you tried to flash in FASTBOOT? I would expect PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip to work since it is a stock rom, but the other one looks like it has been repackaged.
knox420 said:
Ok, will try to do that. What I've done so far is copied update-nexusone-FRF91-stock-noradio-signed.zip to the sdcard's root, renamed it to update.zip and tried to install it via the stock bootloader (recovery with Volume UP + Powerbutton). This failed. Am I using a wrong Rom? Should I try to install this via fastboot?
Click to expand...
Click to collapse
can you try doing this with the PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip one?
if possible try doing it without resigning the zip first.
Alright, none of this worked. I tried it all but in the end I had to realize I lack too much knowledge.
I wiped everything and reinstalled Cyanogen Mod 6 RC3. System's up and running.
Thanks for any help, though.
Or is there any way to access the sdcard without booting the system? I could put an update.zip there and apply it.
Click to expand...
Click to collapse
You mean get the card out of the phone and plug into a card reader?
cryshop said:
You mean get the card out of the phone and plug into a card reader?
Click to expand...
Click to collapse
What I meant -back in the days- was that I wanted to access the card while still in the phone. From the bootloader. Now this is possible with ClockworkMod or AmonRa Recovery.
Thanks anyway
I am sad to say the time has come to retire this post....Now before you get all panicky and ****, just sit your **** down, take your adderall and relax, damn antsy ass people. Anywho, with people our there like xHausx and others that have automated all of this there really isnt a need for me to keep this updated. I will keep the post here for archival purposes but, I will not be updating it, any further. I may pop into the thread here and there but probably not. I would like to thank all those that helped and supported me during this threads run. With out you we would still be stuck.
In the mean time if your looking to root your phone, check out xHausx's thread
here: http://forum.xda-developers.com/showthread.php?t=838448
And no I still dont recommend Clockwork or Unrevoked.
Till next time...Super Tramp - Goodbye Stranger
Archive of the guide as of 2/14/11
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
Presenting the ONE AND ONLY surefire root method that backs up your RSA KEYS prior to rooting !!!!
Also I am aware that unrevoked has out their new tool. However while I was sitting in IRC, I saw many that it wasnt working for. So Until there is a surefire, easy method, I will keep this thread updated.
Credit goes to:
amoamare (Initial method)
toast (fake recovery and script)
unrevoked (thanks for your app)
amon_ra (fixed custom recovery)
chris1683 (thanks for the rom) (sprintlovers)
ryanza (z4root)
illogos, epicroot, xHausx, TrevE, Chubbzlou (Testing)
BooDaddy (RSA Backup Info)
and who ever else I missed
Help me finance my Vette!
zikronix
Disclaimer and well a little fun:
This has been tested on many phones and it worked fine...but if it breaks your **** dont come cry to me about it...you knew the risks! No one here is responsible if you break, brick, set fire, punch, smash, stab, destroy, your self, computer or your phone. The only person responsible is you! Just because it worked for me and others does not mean it will for you. Anytime you flash something its a risk.
Ladies and gentlemen... I've traveled over half our forum to be here tonight. I couldn't get away sooner because I had a POST coming in and I had to see about it. That phone is now rooted at and running well. I have two others comming in and this method has rooted many on the board. So, ladies and gentlemen... if I say my guide works you will agree. You have a great chance here, but bear in mind, you can lose it all if you're not careful.
Out of all methods that beg for a chance to root your phone, maybe one in twenty will work; the rest will be trolls-that's posters trying to get between you and the guide-to get some of the root action that ought by rights come to you. Even if you find one that has a simpler guide, and means to root, he'll maybe know nothing about helping. This is... the way that this works. This method is reliable like no other in this field and that's because its been tested and tested time and time again. I assure you, whatever the others promise to do, when it comes to the showdown, they won't be there...
Downloads
================================================== ====
STOP HERE READ THIS
This Method soley uses Amon_RA Recoveries....Period. A poor soul that lost his RSA keys (broken 4g forever) by recent clock work shenanaigans here
VX - Updated Amon Ra Recovery. Download Here: hboot_2.xx_soff-VX.zip
MD5: 27eb4a36ba01078193975fc93723dd60 <---VERIFY YOUR MD5, IF ITS NOT THIS REDOWNLOAD
Lets Get Rooted!
======================================================
Prerequsites:
Extract only the main zip file to a folder of your choice. I recommend the root of C:\ into a folder of your choice or on the desktop. Make sure you have the drivers installed for your phone (recommended: SDK Drivers or unrevoked hboot drivers) and USB debugging is on. This was setup for people running windows, if you have access to it do it on a 32bit version. I can't stress this enough you must use the adb.exe included with the package This is command line based do NOT double click the exe. Assume nothing, and cut and paste or type the commands EXACTLY as listed, they are case sensitive and each line is a seperate command. Oh and Read the FAQ and Warnings for f-sakes
1) Connect your phone to the computer (Rear USB Port Perferred) make sure the computer detects the phone (DO NOT MOUNT USB) If it doesnt install the drivers. Now master Reset your Phone (Menu>settings>Sd & Phone Storage>Factory Data Reset). Your phone will reboot. While your phone is rebooting it ctrl+alt+delete on your computer and open up task manager and click the processes tab look for anything that says adb.exe click it and hit end process.
2) Your phone should be booted and in the rom. You can skip the setup. On your phone enable install applications from unknown sources.(menu>settings>applications>unknown sources) and turn on usb debugging.
3) Open a command prompt (do NOT click adb.exe) and change to where ever you extracted the files to.
4)Type the following (this must be excuted from the folder you extracted to)
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
Click to expand...
Click to collapse
5) Now were gonna install z4root. When its done look at your phone z4root should be running. Select temporary root... It will go thru the process will eventually come to a white screen *Wait* after a sec or so screen will come up saying temp root was a success. Ok so now type the following
adb -d install -r root/z4root.apk
adb shell am start -a android.intent.action.MAIN -n com.z4mod.z4root/com.z4mod.z4root.z4root
Click to expand...
Click to collapse
6) Your command should still be open and you should be in the directory where you extracted the files. Once you have typed "su" command below look at your phone and click allow for SuperUser...Ok so now type the following from the command prompt
adb shell
su
Click to expand...
Click to collapse
6A) REQUIRED RSA BACKUP This will back up your RSA keys just in case something goes wrong in that department. You should still be in your command window inside the shell with a #. (The following came from this thread)
mkdir -p /sdcard/nandroid/RSA-PR-BACKUP
cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
This saves it in a file that can actually be restored. This next step is another type of backup just for good measure
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
This will dump the RSA keys to a text file on your SD Card named rsa_OEM.key
Mine was about 4575 KB in size, but the size could vary. Go ahead and switch the phone's USB connection over to "Disk Drive" and then browse to your SD Card and verify that the file rsa_OEM.key is indeed on the card.
Proceed to Step 7
Click to expand...
Click to collapse
7) You Should still be at a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over...Otherwise
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
Click to expand...
Click to collapse
8) Now we are going to reboot your phone into the boot loader to flash the first PC36IMG.zip. You should still be in the shell So Type:
reboot bootloader
Click to expand...
Click to collapse
9) Once your phone is in the boot loader highlight bootloader, and press the power button. It will load the PC36IMG File...When it ask you to flash press VOL-UP. You will notice that it says bootloader bypassed and maybe some other errors. Dont worry this is normal. Once the flash of the file is done it will ask to reboot, Select NO by Pressing VOL-DOWN. Now some people have gotten some errors here and there during the flashing just continue as normal.
10) You should still be in the boot loader at this point. Scroll down to recovery and press the power button. It Should take you to a red triangle. If not and you get stuck at a white htc screen pull the battery and then repower the phone with power + vol down and select recovery. When you see the red triangle. Type the following (IF YOU GET STUCK HERE CHECK THE FAQ):
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
Click to expand...
Click to collapse
With any luck you should be at a recovery (green screen with text)
11) Select enable USB-MS. This will mount your sdcard. Look in the root of your sdcard and you should have two files. One named PC36IMG.zip and one named PC36IMG-MR.zip. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip when your done follow the instructions on your phone to disable usb (press power) then proceed to step 12
12) Now Select flash zip from the menu and choose unrevoked-forever.zip. Wait for it to complete. Select Reboot from the menu.
Now pay attention. It might kick you back into:
BOOT LOADER: See 12A
ROM: See 12B
WHITE HTC SCREEN: See 12C
12A) Ok so you got kicked to the boot loader. It should scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12B) Ok so the phone booted into a rom. Power the phone off. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is Sprint Lovers rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip
adb reboot recovery
Click to expand...
Click to collapse
14) You Should be in the recovery menu now (green text screen). Do a backup by navigating to backup/restore press power to select then do a Nand backup in the next menu. Once thats done, select return, then reboot or flash a rom of your choice. If you flashed a different custom rom than the one thats included in the package cool. If not no big deal eitherway. Do a PRL/Profile update while in the rom after the phone is done rebooting. Your Done.
15) Read the FAQ for questions
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to. It installs amon_ra 2.2.1
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
================================================
UNROOT GUIDE
NOTE: This will erase all data on the phone. (Will not erase data on the SDCard)
1) If your on Hboot 2.10 Download the PC36IMG.zip Here. If your on Hboot 2.02 Download the PC36IMG.zip here then Unrevoked s-on here rename the pc36img file to pc36img.zip copy that and the unrevoked s-on tool to the root of your sd
2) Power your off. Power the Phone back on into the boot loader by holding power and vol-down until your presented with a white screen.
3) It will scan for the pc36img.zip. Select no to flash. Select recovery from the menu. Once in recovery choose flash zip from the menu, and select unrevoked forever s-on.
4) When its done flashing select reboot from the menu.
5) From here either run the official ruu or boot back into the boot loader (see step 2). When it scans and ask you to flash the pc36img.zip select yes then yes to reboot.
Click to expand...
Click to collapse
FAQ
FAQ:
Your here cause something went wrong right? Ok thats fine. This list isnt extensive but its here to provide quick answers to some weird or common questions. New questions and problems are added to the bottom.
Q: Will this downgrade my hboot
A: No. I used to have an hboot downgrade but it was bricking peoples phones. However is you want to risk bricking your device, visit this thread here. I I advise against this. This bricked alot of phones which is why I pulled it.
Q: How do I install the Hboot Drivers
A: Check this here
Q: I get "error: more than one device and emulator"
A: kill the adb.exe tasks in task manager or reboot your computer
Q: Step #9 my phone does read the PC36IMg.zip
A: If you renamed the zip file make sure it doesn't say PC36IMG.zip in the name remember that xp and up on windows doesn't show the file ext by default so if you see PC36IMG.zip chances are its named PC36IMG.zip.zip
Q: Why cant I use Clockwork Recovery
A: At the moment its not coded for the new partitions. Just read the first few pages of this thread or check this here
Q: What Hardware does this work for
A: All currently known hardware 0001-0004
Q: What Hboot's does this work for
A: It was built for 2.02 and 2.10 however it will work for all version its just there are easier ways for those
Q: I think I messed up can I just start over.
A: Yes. Its recommended if you want to start over run the official ruu.
Q: This is very complicated
A: It is...thats why there is instructions
Q: Will this erase my data
A: Yes but not from the SDCARD
Q: Can I deleted the files off my SDCARD when done
A: Yes, except for RSA_OEM.KEY and WIMAX.IMG
Q: I get permission denied or device offline when trying to step 10
A: Check here or here or here this might work for you
Q: I used clockwork it seems to work fine.
A: It might but considering the partition information is not correct. You may have just over wrote your wimax keys and broke 4G. Have fun with that like this poor guy here
Q: This uses unrevoked in one of its steps? Explain?
A: There have been some concerns that this uses unrevoked-forever in one of its steps. As far as we know that Unrevoked 3 (not to be conufused with unrevoked-forever) is causing some radio issues with hardware in general and new hardware. Unrevoked-forever does not appear to bork the radio like unrevoked 3 does. This is apparent by the many success stories. However Unrevoked3 could very well possibly destroy your radio/wimax/brick if used.
Q: I get device not found
A: Install the drivers for your phone, (Unrevoked, ADB)
Q: Camera doesnt work after doing this
A: Flash a new rom thats current. Like SteelRom, Fresh, Stock Rooted. The issue here is the Hardware is different. NO CUSTOM KERNELS
A2: Reports say they changed the camera provider/hardware. And the drivers are different! Using a rom based off the latest release and kernel should fix it As Discussed here and here and here
Q: When I go to recovery. I get a red triangle.
A: See Step 10
Q: This doesnt work!
A: Yes it does if you follow the directions, Unless some other bull**** decided to popup!
Q: CM6.x doesnt work
A: See Question 7....Nothing I can do about that if the kernel doesnt support your camera/device.
Q: My phone boot loops now...You broke my ****!
A: I didnt break your ****. You broke your own ****! Its not broken so chill out (well it might be but probably not). What rom did you flash? Did you flash a custom kernel? Did your rom come with a custom kernel? I bet your using a custom kernel. Try a rom like Steel Rom, Sprint Lovers
Q: How do I back up my RSA Keys
A: Check here for the latest up to date information. Or run this command from the shell
cat /dev/mtd/mtd0 > /sdcard/wimax.img
Click to expand...
Click to collapse
Q: My 4g Doesnt work
A: Was it broken prior to the s-off, what steps did you take. Are you running AOSP ROM or Another kernel?, Did you try a different rom? What version is your phone? Do you have SwitchPro Widget installed? (uninstall it), Did you try to run unrevoked3 prior to this? After flashing the radios and stock kernel based rom did you do a data and prl update? Does the mac behind your battery match whats in about phone (4g has to be on to see mac) Also try the tree.xml fix posted
adb shell
ls /data/misc/wimax/
look for a file with your macaddress ending in .tree.xml. you want to move that to another location so it gets regenerated. (the following command basically renames it.)
mv /data/misc/wimax/(Your-mac-address).tree.xml /data/misc/wimax/(Your-mac-address).tree.xml.old
4. Start 4G may not connect
5. Do a prl/profile update
6. Power off the phone and power it back on. Try it
7. PRL/Profile. Try it
Click to expand...
Click to collapse
Q: 4G is still broke.
A: Check your RSA keys
adb shell
cat /dev/mtd/mtd0 | grep RSA
returned output show appear as this:
# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
#
It should look just like the above
the important lines are BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY.
If you have those two lines, your keys are still likely to be intact.
If those two lines are missing, your keys are likely missing.
/dev/mtd/mtd0 is where the wimax image is stored.
Click to expand...
Click to collapse
Q: OK I think My Keys are tossed. We made a backup right? So how do I restore it?
A: This post or post should do it for you
Q: My Phone says its not rooted.
A: If you have s-off your rooted. Simple as that. Try a different rom if you want. The second pc36img.zip file you flashed is Sprint Lovers and is a very nice rooted rom.
Q: When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
A: The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
Q: Can you tell me what this does?
A: Read the guide? Basically your downgrading the phone, so you can flash unrevoked because htc "comically fixed" the phone. Then your re upgrading the phone back to shipping radios, system, pri, nv, kernel...all the while with keeping s-off
Q: How did you get to be so cool
A: If you have it, you don’t need it. If you need it, you don’t have it. If you have it, you need more of it. If you have more of it, you don’t need less of it. You need it to get it. And you certainly need it to get more of it. But if you already don’t have any of it to begin with, you can’t get any of it to get started. Which means you really have no idea how to get it in the first place, do you? You can share it, sure. You can even stockpile it if you like. But you can’t fake it. Wanting it, needing it, wishing for it. The point is, if you’ve never had any of it, ever, people just seem to know.
Q: Do you really own a vette?
A: Yes, and a backpack with jets!
Q: Whats with you and the dots ...
A: ...
Q: Your Kind of an Cocky Asshole
A: Yea...I Get that. Oh well. I cant fix stupid or ignorant.
What is the point of getting the new HBoot?
sorry, wrong question
abiezer said:
What is the point of getting the new HBoot?
Click to expand...
Click to collapse
there is no point in getting a new hboot....this tool is for those that have phones with the new hboot....that unrevoked wont work on.
this is not the new hboot
Oh I see so this is basically for people who couldn't root to be able to root. Got it. Thanks.
Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?
shepkc said:
Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?
Click to expand...
Click to collapse
its included in the script it tells you how to do it.
update failed, said main version is older...
its working for some but not others...i dont know why the main version is older thing...
i think we have ironed out the mainversion deal...
looking into it now.
Should be fixed now...so try it I guess.
v2
Looks like your V2 is working, I didn't run into the main version failure. Flashing as I type, I hope slyder got this to work.
Confirmed, V2 works
alright brotha your v2 of the batch file works like a charm. S-OFF confirmed on HBOOT 2.02. Thanks to everyone involved in making this happen.
Outstanding
Sent from my PC36100 using XDA App
On a brand new fresh 2.2 out of the box running HBOOT 2.02 I got "Main version is older". Are there any prerequisites i have to run to get this to work? I just reinstalled 2.2 and ran the script and got main version is older.
did you download version 2
do you have gtalk
I did download v2, and I do have gtalk.
b0r0b said:
I did download v2, and I do have gtalk.
Click to expand...
Click to collapse
you got PM....i want to know exactly whats happening.
Main version is older
I have also tried with V2 and get the "Main version is older".
Baseband
2.15.00.09.01
Software
3.30.651.2
PRL
60671
Hello, all. First thread here on Xda, so I apologize if I missed something.
I own a myTouch 4g 2.3.4 and use an Ubuntu 11.04 desktop. I have the official SDK and ADB installed.
I'm looking to root my myTouch 4g and understand that as of now there is no method available for devices running 2.3.4... This means I need to downgrade in order to root... I've searched and searched and searched but am unable to find any guides on downgrading for those who use Linux.
wiki[dot]cyanogenmod[dot]com/wiki/HTC_Glacier:_Full_Update_Guide
I reviewed the above guide but was faced with quite a few programs in the rooting process that are available only for Windows.
Any help?
Looking to use Cyanogen as my rom, and therefore need to be running Android version 1.17.531.2
Okay, due to me being a noob I quickly discovered after more research that the platform is not a matter of concern when using the guide above.
HOWEVER...
I have a new problem...
Towards the bottom of the first section (this part
"Now that misc version has been downgraded, the HTC Glacier is ready to have the firmware downgraded. On the computer, open terminal and run the following commands:
adb push PD15IMG.zip /sdcard/PD15IMG.zip
adb shell md5sum /sdcard/PD15IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
adb reboot bootloader
Use Volume up/down keys on the HTC Glacier for navigation and Power key for confirmation. Select Fastboot to flash the 1.17.531.2 firmware.
Once finished you can can continue to the next section.
I get an error when performing the following command:
adb shell md5sum /sdcard/PD15IMG.zip
md5sum: not found
Any help?
How to Achieve Permanent Root and S-Off:
To get permanent root, you need to S-Off. So lets start with that first. This process will NOT wipe your device. It also works for OS X users. This guide will work on software version 1.55.605.2 (which as of 04/19/2014 is the latest OTA) and below.
--- S-OFF Instructions ---First, you'll need to download adb, enable its use and setup debugging.
adb is part of the android SDK. You can download it here (OS X users must scroll down and download the OS X version). It does not need to be installed, just unzip it into its own folder. You can also download a zip that contain only adb and fastboot.
once you have adb, you'll need to download the drive for your M8, which can be had from HTC's driver page:
http://www.htc.com/us/software/htc-sync-manager/.
Then install it. It will install the driver necessary for adb to work. After the installation is finished, uninstall HTC Sync immediately (do this regardless of whether or not you need it; you can reinstall it later if you still want it). This will leave the driver package installed, but remove HTC sync.
Now, back to the phone. Disable all security you have on, including PINs, Pattern Locks, passwords, etc. If you have an exchange forced security policy, you will need to disable the account. You can readd it later.
Enable access to developer options. Jump into the Settings. Then you’re going to scroll down to the bottom and tap on ‘About’, next tap on ‘Software Information’. Now you’ll need to tap on ‘More’, which will give you a new menu. Now just tap on the build number 9 times and you’ll enable Developer options.
Go into developer options menu and enable USB Debugging.
Next, go to Security page and enable "Unknown sources".
Now install weaksauce from here:
http://forum.xda-developers.com/showthread.php?t=2699089
If you followed the directions correctly, you should have SuperSU installed and root access. (You can use superuser as well).
Plug in your phone into your computer. Its best to use the factory cable provided with the phone. Use a USB 2.0 type port if possible (USB3.0 ports typically have a blue tab; I have personally used a USB 3.0 Device on Windows 8.1u to perform this without any problems, but your mileage may vary).
Your phone will ask if you if you trust your computer (RSA). Choose "Always Allow".
Ensure adb is working by opening a command prompt (terminal on OS X), navigate to the adt-bundle-[XXXXX]/sdk/platform-tools and typing "adb devices" without quotes. Your phone should show up. Ensure the working directory is the directory that adb is in. Otherwise, transferring firewater may fail. On Windows, you can shift-right-click inside the folder adb is in and click open command prompt to open a cmd in that directory.
Now go download firewater from here:
http://firewater-soff.com/instructions/ Make sure to use the weaksauce method (second method). Do NOT use the temproot method.
The firewater file should be called "firewater" without any quotes or extensions (like .bin). Ensure your browser did not partially download or corrupt it.** Make sure its in the same folder as adb. Then follow directions on the firewater site. Be aware the yes/no prompt is case sensitive, so make sure to answer it with an uppercase Y as in "Yes" not "yes". During the process, you will need to enable adb shell to get root. Make sure your phone screen is on so you can see the root request. Grant it and the S-Off process will continue. Otherwise, it will hang there and eventually time out. Sometimes, the process will fail and the phone will reboot. This is okay. Just restart the process. It can sometimes take multiple tries.
When completely successfully, you now have S-OFF. Your phone's bootloader is also unlocked in the process; you do NOT need to perform any additional steps to unlock the bootloader. However, you do not have permanent root. The root that weaksuace provides goes away on reboot and must be reapplied again on startup.
**The filesize seems to vary depending on what OS/browser is used to download it. It should be around 4,519,496 (on disk) in size. If you can't execute firewater, try redownloading it.
Getting permanent root:
-Flash a custom recovery and flash a zip with su.
-[Optional] Return to stock recovery This option is for people who don't want a custom recovery.
Be aware, once rooted and S-Off'ed, you do NOT need the kernel module that enables system write access*. All system changes will survive hard reboots (adb reboot).
-- Recovery Rooting: --
Move the supersu zip onto your internal sdcard. It can be downloaded here:
http://forum.xda-developers.com/showthread.php?t=1538053
You can use Superuser as well. Its your preference, but this guide uses SuperSU.
Uninstall weaksauce. It's no longer needed.
Uninstall SuperSU. It will be reinstalled when you flash the supersu zip. If you have SuperSU Pro installed, you can leave that in place, as that app only holds a key.
From adb, type:
adb reboot bootloader
Flash a custom recovery. CWM and TWRP are available. Use the fastboot method. Follow the directions here:
TWRP - http://teamw.in/project/twrp2/226
CWM - http://forum.xda-developers.com/showthread.php?t=2708520
Reboot into Recovery
Flash the supersu zip you downloaded.
Reboot and you're done. You have s-off and permanent root.
You can delete the downloaded supersu zip off your internal sdcard; its not longer needed.
-- Manual Root --Perform all steps noted in section "Recovery Rooting" above.
-Download the stock recovery:
http://forum.xda-developers.com/showthread.php?t=2723112
-Ensure the stock recovery img file is in the same folder as fastboot.
-Run the following command from command line: "fastboot flash recovery stockrecovery.img" without the quotes.
-Wait for the process to finish
-Reboot the phone. You now have the stock recovery along with root. With the stock recovery installed, you can now accept OTAs provided you haven't modified/deleted any stock system files. Any new OTAs you take will remove any files/folders you added to the system partition and will remove your root. However, with S-off, this can be undone. If you lost loot after taking an OTA, simply start from the beginning of the section "Recovery Rooting".
-- Common Tweaks --
All of these are optional and are NOT required. However, you may find some benefit to them.-- Wifi Tether Enabled --This is unnecessary if you are on a More Everything plan or are paying for hotspot/tethering. You can force enable the native tethering application:
http://forum.xda-developers.com/showthread.php?t=2708548
-- Device Wipe after ten attempts --I really dislike this "feature". Here is how to disable it. This works regardless if you enabled the security or its mandated by an exchange policy.
I use Root Explorer to make this change, but you can use any text editor. Make sure to mount system as R/W. Root explorer can do this from within the app.
Edit this file:
/system/customize/ACC/default.xml
change this:
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">10</item>
to this
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">0</item>
Reboot and its disabled.
-- Power Saver Mode --Enable "Power Saver" mode using these directions. It's disabled and hidden by default.
http://forum.xda-developers.com/showthread.php?t=2701909
-- *Unsecured Kernel --By default, the stock kernel prevents write access to /system. S-off and root should allow you to makes changes to system. However, some people have reported difficulties using ROM toolbox and other mods (like changing boot animations). In some cases, these issues can be resolved by flashing an insecure kernel:
http://forum.xda-developers.com/showthread.php?t=2708686
-- HTC Sense Broswer --The stock ROM now includes Chrome as the default browser and omits the Sense Browser. Users who prefer the Sense Browser can download it here:
http://forum.xda-developers.com/showthread.php?t=2708597
-- HTC Flashlight --The stock HTC flashlight app.
http://forum.xda-developers.com/showthread.php?t=2697025
-- Disable HTC Sync Virtual CDROM --This disables the virtual CD-ROM from mounting.
http://forum.xda-developers.com/showthread.php?t=2709386
-- Donations --Don't forget to donate to the developers involved in getting you here. Donations for firecracker go to [email protected] (paypal). Donations for weaksuace go to [email protected] (paypal). If I missed anyone, let me know.
FAQBeen getting some interesting PMs. Here is some of the popular questions.
Do I need a Java card for this?
No. You just need a PC/Mac, a USB 2.0 cable and the M8. Since a public S-off method is now available, that method is obsolete and its not recommended anymore.
Do I have to change or reset my CID?
No, that is only necessary for people who s-off'ed via a Javacard.
Do I need to do any of this if I S-off'ed via Javacard?
No, this method ends with the same result.
Can I reverse this and return to completely stock?
Yes, absolutely none of the stuff done here is permanent. You can unroot, relock the bootloader, and S-On as many times as you want. You can flash an HTC RUU to return to completely stock in one go. Note: Be careful with S-On'ing a device. If you S-On a device via a newer RUU and that RUU has no known exploits, you may not be able to S-Off again until an exploit is found.
Do I need to unlock my bootloader after this?
No, the firewater exploit will S-Off and unlock your bootloader.
Will this work on a Mac?
Yes, please read the directions more carefully.
Will this work on USB 3.0 ports as that is all I have?
Usually. On OS X, I've had success using a USB 3.0 port (since recent MBPs only include USB 3). On Windows, the answer seems to be maybe, depending on your OS. Your best bet would be to try on a Windows 8,8.1,8.1u1 machine as that OS includes native support for USB 3.0; that way you aren't relying on vendor specific driver support like on Win7 or below. I have personally done this exploit on USB3 on a Surface Pro.
Will this brick my phone?
There is always a chance, but I have honestly never heard of such a thing happening. Worst case is usually a full reset of the phone.
Will this wipe/format the external SDcard?
No.
How do I flash this via ODIN?
This has absolutely nothing to do with ODIN. That is for Samsung devices. You should not even have ODIN running when do any part of this guide.
How to I convert to a Google Play edition ROM?
Wait for a developer to make one. I will post a link here if/when that happens.
See here:
http://forum.xda-developers.com/showthread.php?t=2716306
Does this affect Google Wallet or ISIS?
Yes and no. Google wallet works just fine. ISIS will detect its rooted and refuse to work. You'll need to shield root from ISIS to use it. Directions on how to do that can be found via google.
Will this work on non-Verizon HTC M8's?
Yes, though you will need to use a different recovery.
Will this unlock my device for other carriers?
No....because your device is already unlocked in its stock form. AWS band rules force Verizon to keep all their LTE devices unlocked.
Will this jailbreak my device?
No. Wrong type of phone.
I can get red triangle exclamation mark with a black screen. How do I fix this?
You are in the stock recovery. Hold power and volume up and you will get a menu. You can choose reboot system now to get out of there.
appreciate the write up. ill check back here when i find a reason to unlock it
Has anyone done it yet? It's just sitting at "adb wait-for-device push firewater /data/local/tmp" for at least 5 minutes now.
sfreemanoh said:
Has anyone done it yet? It's just sitting at "adb wait-for-device push firewater /data/local/tmp" for at least 5 minutes now.
Click to expand...
Click to collapse
I have done everything mentioned in this guide. And it works just fine.
Make sure you are connected via USB2. Also make sure your phone is on and unlocked (as in, no security PIN, pattern, password etc.). Is USB debugging on?
When you type "adb devices" from command prompt, is your device listed?
Yeah, nvm, it's fine now. When I first connected it via debugging, I didn't hit the "Always allow" option on my phone, so after the adb reboot it wasn't allowed to reconnect. Just had to disable debugging and re-enable it, it's all set now.
sfreemanoh said:
Yeah, nvm, it's fine now. When I first connected it via debugging, I didn't hit the "Always allow" option on my phone, so after the adb reboot it wasn't allowed to reconnect. Just had to disable debugging and re-enable it, it's all set now.
Click to expand...
Click to collapse
Cool. I'll add that to the guide.
I have not had time to thank and will.
At work and going to hook it up when I get home this morning so I hope no one screws with you guys and gets it pulled.
Very much appreciate all the work they put into it.
Thank you very much for the dummy proof write up
These guys around here are getting to good.
Thank you thank you thank you.
Worked Perfect! Thank you guys!
thank you so much! now i can sleep at night knowing that verizon doesn't have control of my device anymore haha!!
Im happy to see that s-off was achieved and Im going to unlock my phone right now
but quick question, I'm new to this s-off stuff so I don't know how it works entirely.
But once we unlock the bootloader
is there any way to lock it again in case we need to send the phone to HTC?
sorry for the noob question but just a question that popped into mind.
So I don't quite understand. I am S-off with the Unofficial CMWR from InvisibleK and I flashed SuperSU zip v1.94. Do I need the system write access kernel module to write to system or no?
Great guide by the way. Thanks
I have been trying for the past hour, but I cannot get adb to connect. Am I missing a step?
I downloaded the htc synch, installed the drivers, uninstalled synch. I already had weaksauce root. I downloaded sdk, extracted the bundle. I downloaded firewater, moved it to the same folder with adb.
Everytime I try to run adb it just scrolls and then closes almost immediately. I thought it was my java at first. I updated that. The computer says I'm connected through HTC drivers. I'm debugged/unknown sources...
Running windows 8.1 64bit. I don't know what else to do at this point.
blacknet101 said:
Im happy to see that s-off was achieved and Im going to unlock my phone right now
but quick question, I'm new to this s-off stuff so I don't know how it works entirely.
But once we unlock the bootloader
is there any way to lock it again in case we need to send the phone to HTC?
sorry for the noob question but just a question that popped into mind.
Click to expand...
Click to collapse
Absolutely. Everything in this guide can be reversed. You can return everything back to stock via an RUU.
nicholi2789 said:
So I don't quite understand. I am S-off with the Unofficial CMWR from InvisibleK and I flashed SuperSU zip v1.94. Do I need the system write access kernel module to write to system or no?
Great guide by the way. Thanks
Click to expand...
Click to collapse
You do not. I have modified and added a few system files and they have persisted through several hard reboots.
MultiDev said:
Absolutely. Everything in this guide can be reversed. You can return everything back to stock via an RUU.
Click to expand...
Click to collapse
Hmmm! Thanks for the reply buddy! may i ask? Where can we find these RUU files? In case we need to go back to Stock?
JelloB said:
I have been trying for the past hour, but I cannot get adb to connect. Am I missing a step?
I downloaded the htc synch, installed the drivers, uninstalled synch. I already had weaksauce root. I downloaded sdk, extracted the bundle. I downloaded firewater, moved it to the same folder with adb.
Everytime I try to run adb it just scrolls and then closes almost immediately. I thought it was my java at first. I updated that. The computer says I'm connected through HTC drivers.
Running windows 8.1 64bit. I don't know what else to do at this point.
Click to expand...
Click to collapse
Java has nothing to do with adb. You don't need it installed to any of this guide.
You need to use adb from a shell. On, windows, you need to open a command prompt. Type "cmd" with the start screen open and hit enter. Then at the prompt, use the "cd" command to navigate to the correct directory where adb is located.
When i run the "adb wait-for-device push firewater /data/local/tmp" command it come back with "failed to copy 'firewater' to '\data\local\tmp': Read-only file system". I'm lost. I have root access and everything.
MultiDev said:
Java has nothing to do with adb. You don't need it installed to any of this guide.
You need to use adb from a shell. On, windows, you need to open a command prompt. Type "cmd" with the start screen open and hit enter. Then at the prompt, use the "cd" command to navigate to the correct directory where adb is located.
Click to expand...
Click to collapse
I knew I was missing something simple. It's been a while since I've used adb. Will try now...thanks.
trying to modify the default.xml to get rid of the 10 try's and wipe pattern lock and it doesn't appear I have access to read write from it still... trying with the ES note editor when going to the file with ES File Explorer. I've ran the wp_mod.ko as directed and I haven't rebooted.
I'm wondering if I'm missing something, or maybe there's a better way to do it via command line?
blacknet101 said:
Hmmm! Thanks for the reply buddy! may i ask? Where can we find these RUU files? In case we need to go back to Stock?
Click to expand...
Click to collapse
They are available from HTC. I'll have to find the exact links. Also, many android sites will host them too.
Slimfast35 said:
When i run the "adb wait-for-device push firewater /data/local/tmp" command it come back with "failed to copy 'firewater' to '\data\local\tmp': Read-only file system". I'm lost. I have root access and everything.
Click to expand...
Click to collapse
You need root access to write there, shell does not normally have access. Beaware that weaksauce takes a minute or two before after a restart before enabling root again. So wait till you have access again before trying it.
meest said:
trying to modify the default.xml to get rid of the 10 try's and wipe pattern lock and it doesn't appear I have access to read write from it still... trying with the ES note editor when going to the file with ES File Explorer. I've ran the wp_mod.ko as directed and I haven't rebooted.
I'm wondering if I'm missing something, or maybe there's a better way to do it via command line?
Click to expand...
Click to collapse
You do not need the kernal module actually; I have removed that from the guide. I haven't used ES Note before, but no matter what, you must mount system as R/W before you can change anything. Its by default R/O or Read Only. Root explorer has a button that auto mounts it and then you can make your edit.
Hi lovely people,
I'd like to install CM13 on my HTC Desire S S510e. I have found way too many different instructions on how to proceed and I was wondering if there's a simple, step-by-step (I really mean step-by-step) guide on how to do it. By now, as far as I understand I should:
1. S-OFF my phone (although I heard it's possible to install a custom rom even with S-ON?). I've read that you can do it using HTCDev or Alpharev. However the HTC Desire S doesn't appear on the list of supported devices in the first link. Which device should I select from the list? On the other hand, the Alpharev website says that Alpharev is deprecated and one should use Revolutionary but the Revolutionary website is empty. Finally a more general question: what's the benefit of using HTCDev or Alpharev?
2. Flash sagaopt TWRP 2.8.7.1. I use ArchLinux. In Linux I'd have to install android-tools to have adb and fastboot, then do "adb reboot bootloader" followed by "fastboot flash recovery TWRP-recovery-sagaopt-2.8.7.1.img"? Or do I have to first install an older version of TWRP to convert my sdcard to EXT4 to then install the sagaopt 2.8.7.1 version?
3. Use TWRP to convert my sdcard to EXT4.
4. Install cm-13.0-XXXXXXXX-UNOFFICIAL-sagaopt.zip and gapps by putting the files into the sdcard using adb (what's the command to do this?) and then flash the files using TWRP.
What steps am I missing? What are the perils? What should I be particularly careful with?
Please help me understand and condense the heaps of information found in this forum.
Thanks,
Ricardo
rikardo.h said:
Hi lovely people,
I'd like to install CM13 on my HTC Desire S S510e. I have found way too many different instructions on how to proceed and I was wondering if there's a simple, step-by-step (I really mean step-by-step) guide on how to do it. By now, as far as I understand I should:
1. S-OFF my phone (although I heard it's possible to install a custom rom even with S-ON?). I've read that you can do it using HTCDev or Alpharev. However the HTC Desire S doesn't appear on the list of supported devices in the first link. Which device should I select from the list? On the other hand, the Alpharev website says that Alpharev is deprecated and one should use Revolutionary but the Revolutionary website is empty. Finally a more general question: what's the benefit of using HTCDev or Alpharev?
2. Flash sagaopt TWRP 2.8.7.1. I use ArchLinux. In Linux I'd have to install android-tools to have adb and fastboot, then do "adb reboot bootloader" followed by "fastboot flash recovery TWRP-recovery-sagaopt-2.8.7.1.img"? Or do I have to first install an older version of TWRP to convert my sdcard to EXT4 to then install the sagaopt 2.8.7.1 version?
3. Use TWRP to convert my sdcard to EXT4.
4. Install cm-13.0-XXXXXXXX-UNOFFICIAL-sagaopt.zip and gapps by putting the files into the sdcard using adb (what's the command to do this?) and then flash the files using TWRP.
What steps am I missing? What are the perils? What should I be particularly careful with?
Please help me understand and condense the heaps of information found in this forum.
Thanks,
Ricardo
Click to expand...
Click to collapse
3.check android version in system settings if it is lower or lower2.3.X (if its not it could be ****ty) than check bootloader version
3.1 turn off fastboot in battery settings
3.2 power don phone
3.3 boot phone with vol down clicked and if its -REVOLUTIONARY- or if its 0.98.x s-off or 2.0X s-off go to 6
if its 0.98 s-on you go to 5
if its 2.02 ask anyone else on my desires with 2.02 s-off newer worked for me but you can try it (go to 4) or only unlock it
http://www.htcdev.com/bootloader select HTC Desire HD and dont upgrade anything (start at step 1 skip preparation) after that go to 8
if its 2.00 contine
4.download the oldest rom with you branding from http://androidruu.com/?developer=Saga
4.1 http://forum.xda-developers.com/showpost.php?p=18746686 downlad misc_version
4.2 http://forum.xda-developers.com/showthread.php?t=1312859 download DooMLoRD_v4_ROOT-zergRush-busybox-su.zip and extract zergRush
4.3 go to folder with misc_version and zergRush and open cmd there and type
adb push misc_version /data/local/tmp/
adb push zergRush /data/local/tmp/
adb shell
cd /data/local/tmp/
chmod 777 zergRush
chmod 777 misc_version
./zergRush
./misc_version -s 1.27.405.6
exit
exit
exit
4.4 execute the firmware form step 4
5 download and follow http://rev.alpharev.nl
6 follow http://forum.xda-developers.com/showthread.php?t=1679338 (optional)
7 follow B in http://forum.xda-developers.com/showthread.php?t=1858508 (optional)
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
for the complete tutorial look at http://forum.xda-developers.com/htc-desire-s/general/trying-to-install-cm13-htc-desire-s-t3414878 page 2 for the first one and page 1 for the second
---------- Post added at 09:36 PM ---------- Previous post was at 09:28 PM ----------
CM13 is to heavy for the phone CM12.1 is stable but slow (sometimes you miss a call because the mobile is too slow) CM11 is fast but old (i used CM12.1 now im using CM11 nightly but the gallery doesnt play videos i deleded it)
Thank you for reposting that guide and for suggesting CM11 instead of CM12.1 or CM13. In that guide it says that unlocking the 2.02 s-on using the htcdev tool doesn't work for him if I understand correctly. Also I went to the htcdev website and they say that the tool will remove all personal data including applications, text messages and personalized settings. However I wanted to install a recovery and make a backup of the phone as it is now and that wouldn't work if everything gets removed before installing the recovery. Is there a way to install a recovery without removing anything?
rikardo.h said:
Thank you for reposting that guide and for suggesting CM11 instead of CM12.1 or CM13. In that guide it says that unlocking the 2.02 s-on using the htcdev tool doesn't work for him if I understand correctly. Also I went to the htcdev website and they say that the tool will remove all personal data including applications, text messages and personalized settings. However I wanted to install a recovery and make a backup of the phone as it is now and that wouldn't work if everything gets removed before installing the recovery. Is there a way to install a recovery without removing anything?
Click to expand...
Click to collapse
I think you can try titanium backup with an oneclickroot (kingroot or framaroot) or unlock it with the risk of loosing data first backup contacts/sms and callhistoy with apps of the playstore and your sdcard isnt affected
Oh i could be that you need the win8+ fastboot fix for htcdev http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
and if it doesnt work use windows 7 (dont forget to install htc sync)
if its 2.00.0002/2.00.2000 you can s-off it if its 2.02.0002 its ****ty
I use linux. It's 2.00.0002 so I guess I should follow step 4, but step 4.4 asks me to execute a window's exe file which I can't execute. What should I do instead? Unlock it using htcdev as if it was 2.02 s-on or will that mess my phone up?
rikardo.h said:
I use linux. It's 2.00.0002 so I guess I should follow step 4, but step 4.4 asks me to execute a window's exe file which I can't execute. What should I do instead? Unlock it using htcdev as if it was 2.02 s-on or will that mess my phone up?
Click to expand...
Click to collapse
sorry for that step you need windows there is no other way
you can only unlock but the best way is to use a windows PC/Laptop of a dude or use a VM with windows 7 or XP with usb pass
google windows 7 iso and look for one you can use in vm
I found this https://code.google.com/archive/p/htc-flasher/wikis/HTCFlasher.wiki
Do you know if it would help?
you can try (you need your rom as NBH and the desire s (saga) isn't supported its risky) it but save is a Virtual Machine with windows and usb passthrough