Here is an easy way to achieve S-off and root without the need to go through the HTCDev unlock procedure and flashing custom recoveries:
1. Make a backup of all your data, just in case... (E.g. with Helium, which is free and works without root)
2. Make sure that
HTC drivers installed and working (You can download them here: http://forum.xda-developers.com/showthread.php?t=2217396)
HTC sync is removed (not closed – REMOVED)
All other phone software are removed or disabled (Samsung Kies, PDANet, etc.)
There is a working internet connection ON YOUR DEVICE - wifi, 3g, 4g, etc. are all supported.
USB debugging is enabled on your device
Ensure that lock screen security is disabled on your device: no passcode lock, no pattern lock, no face lock
3. Install ADB on your PC (e.g. download and extract fastboot_adb.zip to c:\ADB)
4. Download firewater
5. Download temproot
6. Download su binary for SuperSu (e.g. the one in su.zip, or extract it from the SuperSu zip installer)
7. Place firewater and temproot in the ADB folder (e.g. c:\ADB)
8. Copy the SU binary to the root of your memory card and install the card in your device
9. Connect your device directly to an USB 2.0 port on your PC
10. Open a command prompt, and navigate to your ADB folder (e.g c:\ADB)
11. Important: Reboot your device:
Code:
adb reboot
12. When the device rebooted, issue the following commands:
Code:
adb wait-for-device push firewater /data/local/tmp
adb push temproot /data/local/tmp
adb shell
chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/firewater
At this point, you have the temproot and firewater binaries on your device with execute permissions
13. Now start temproot to gain temporary root access via the shell:
Code:
/data/local/tmp/temproot
This will take long (5-10min) -> go and grab a coffee
14. Once root access is achieved (temproot will inform you about this, and you will see '#' at the end of the prompt instead of '$') you can start firewater:
Code:
/data/local/tmp/firewater
For my device, this step took about 2 minutes.
Now you have S-OFF and an unlocked bootloader. Yay!
15. Remount the /system partition in order to be able to write it:
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p38 /system
16. Copy su to the /system partition and set its permissions
Code:
cat /storage/ext_sd/su > /system/xbin/su
chmod 04755 /system/xbin/su
17. Grab your device, enter the Play Store and install SuperSu. At this point you are fully rooted.
18. If SuperSu requests to update the su binary, let it (choose the normal approach, NOT the TWRP/CWM method).
19. Shut down your device, then turn it on in bootloader mode by pressing and holding "power" and "volume down" buttons simultaneously
You should see (the UNLOCKED, TAMPERED, and Ship S-OFF texts)
20. To exit bootloader mode, select the "Fastboot" menu item with the vol up/dn buttons, then enter using the power button. Then choose the "Reboot" menu item the same way.
[OPTIONAL] Locking bootloader and clearing "tampered" flag
21. Start command prompt on your PC. Enter your ADB folder. And issue the following commands:
Code:
adb devices
adb shell
su
(I would very strongly recomend you copy/paste the following line)
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
Code:
exit
exit
adb reboot bootloader
22. Verify you are now locked. Then select Fastboot -> Reboot
23. Issue the following commands:
Code:
adb devices
adb shell
su
(I would very strongly recomend you copy/paste the following line)
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
Code:
exit
exit
adb reboot bootloader
24. Verify that the tampered flag is cleared
25. That's it. Reboot your device and have fun
FAQ:
Q: I have been waiting for ages to gain temporary root but nothing is happening!! What should I do?
A: Please be patient. It is a long process (usually 5-10 min)
Q: If I S-OFF/unlock/root my phone using this method, what happens to my apps in /data/preload? Will they get wiped?
A: No, they won't. They will be untouched.
Q: Why are you using that long and complicated command for remounting /system? Wouldn't it be easier to just issue "adb remount"?
A: Sure it would, but unfortunately it would not work, since our stock ROMs use secure ADB and this particular command is only available if the ADB daemon on your device is run in "insecure" mode. More information about the technical background here and here.
Q: Why are you suggesting we use SuperSu as a root management app? What's wrong with Superuser / XXX / YYY ?
A: I have no preference whatsoever. It is only an example. Feel free to use other apps (with corresponding su binary), if you so desire.
Q: Is the su binary inside su.zip safe? Where is it from?
A: Yes, it is safe. It was extracted from the zip installer package of SuperSu v1.93 and was not altered in any way.
Q: My phone rebooted itself when I issued the mount command. What now?
A: Run temproot again, then continue the process starting with reissuing the mount command.
Q: Don't you think XYZ is wrong / missing in your guide?
A: Please reply to the thread or drop me a PM and I will correct it ASAP.
Fine print
I created this guide with the best of intentions, to help people like me, who are more or less new to android but are willing to learn and want to make the most of their devices. I tested the whole procedure on my own Butterfly S 901s 1.23.708.3 without any issues.
However you must keep in mind that during this process you will be modifying vital parts of the system, and doing so always entails some risk. Therefore I cannot and will not take any responsibility if you accidentally brick your device attempting the above procedure.
The tools and most methods used throughout this guide are not my creations. I simply collected and organized information already available but scattered across several topics.
Kudos
to beaups and fuses for bringing us firewater,
to hikezoe and fi01, whose work the temproot is based on,
to daorderdillon for figuring out the way to lock the bootloader and clear tampered flag on an S-OFFed Butterfly S.
to ebautista, who was the first to confirm that firewater does indeed work with the Butterfly S
and of course to koniiiik who encouraged me to start experimenting with the /system remounting
edorner said:
Here is an easy way to achieve S-off and root without the need to go through the HTCDev unlock procedure and flashing custom recoveries:
13. Now start temproot to gain temporary root access via the shell:
Code:
/data/local/tmp/temproot
This will take long (5-10min) -> go and grab a coffee
14. Once root access is achieved (temproot will inform you about this, and you will see '#' at the end of the prompt instead of '$') you can start firewater:
Code:
/data/local/tmp/firewater
For my device, this step took about 2 minutes.
Now you have S-OFF and an unlocked bootloader. Yay!
15. Remount the /system partition in order to be able to write it:
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p38 /system
16. Copy su to the /system partition and set its permissions
Code:
cat /storage/ext_sd/su > /system/xbin/su
chmod 04755 /system/xbin/su
17. Grab your device, enter the Play Store and install SuperSu. At this point you are fully rooted.
18. If SuperSu requests to update the su binary, let it (choose the normal approach, NOT the TWRP/CWM method).
19. Shut down your device, then turn it on in bootloader mode by pressing and holding "power" and "volume down" buttons simultaneously
You should see (the UNLOCKED, TAMPERED, and Ship S-OFF texts)
20. To exit bootloader mode, select the "Fastboot" menu item with the vol up/dn buttons, then enter using the power button. Then choose the "Reboot" menu item the same way.
[/LIST]
Click to expand...
Click to collapse
i have one question and one comment:
1. if i was root and only did firewater, do i need to do since number 15?
2. i did this with my usb 3.0, i know is not recommended, but the device was not recognized in adb. and other thing: be really aware of the screen, if it shuts down the commands will not be working.
cheers
kemoli said:
i have one question and one comment:
1. if i was root and only did firewater, do i need to do since number 15?
2. i did this with my usb 3.0, i know is not recommended, but the device was not recognized in adb. and other thing: be really aware of the screen, if it shuts down the commands will not be working.
cheers
Click to expand...
Click to collapse
If you are already rooted, then steps 13 and 15-18 are unnecessary.
Thank you for the info about the screen, I haven't noticed that before.
As for the connection issue: Well, it may be caused by a lot of things... You could try using an usb 2.0 connection instead, or reinstalling the HTC drivers. And make sure USB debugging is turned on in the developer options.
usb 3.0
edorner said:
If you are already rooted, then steps 13 and 15-18 are unnecessary.
Thank you for the info about the screen, I haven't noticed that before.
As for the connection issue: Well, it may be caused by a lot of things... You could try using an usb 2.0 connection instead, or reinstalling the HTC drivers. And make sure USB debugging is turned on in the developer options.
Click to expand...
Click to collapse
sorry but my explanation was not clear, i can do this only with usb 3.0, with 2.0 my device is not recognized as mtp connection or adb at all even if i have usb debugging turned on... i don´t know exactly why, but it happens after i did a restore because when i did the root with wp_mod my device turns out crazy with superuser, so i root with supersu and after that did this s-off with firewater and works like a charm. I don´t know why but with every product of clockworkmod i have problems...with one old phone that i had, an atrix, my nandroid backup didn´t work and cannot be restored, twrp is the best for me since.
thank you for you response :fingers-crossed:
Ah, I see! I did misunderstand you before. I am glad the s-off method worked for you eventually
Hi edorner,
i have 2 questions need your help.
1. is it need backup everything including "DATA" before unlock bootloader via firewater? (all data will be wiped after unlocked bootloder via htcdev)
2. is it possible to unlock bootloader & root without S-OFF? because i searched several threads but didn't found any threads for "how to S-ON from S-OFF".
thx for your kindness helps n reply. sorry for my bad english...
Hey shiropetto,
shiropetto said:
1. is it need backup everything including "DATA" before unlock bootloader via firewater? (all data will be wiped after unlocked bootloder via htcdev)
Click to expand...
Click to collapse
It is not necessary to backup your data. Nothing will get wiped, when you use this method. Your DATA partition will remain intact.
However I still recommend you to do some kind of backup before you begin. Just as a precaution...
shiropetto said:
2. is it possible to unlock bootloader & root without S-OFF?[/B].
Click to expand...
Click to collapse
TBH, I am not sure.
You could try following the procedure from step 1 to 18, without performing step 14. In theory, it should be safe to try.
That might give you root.
However my guess is that Step 15 will probably not work without S-off or unlocked bootloader.
shiropetto said:
i searched several threads but didn't found any threads for "how to S-ON from S-OFF".
Click to expand...
Click to collapse
S-ON is very easy So I honestly do not see any reason why you would not want to go S-OFF.
To revert to S-ON:
1) open a cmd window in your ADB directory. plug in phone ,usb debugging on
2) adb devices
3) adb reboot bootloader
4) fastboot devices
5) fastboot oem writesecureflag 3
6) fastboot reboot-bootloader
7) verify you are locked s-on
8) fastboot reboot
There are just two important things you must keep in mind:
1) When / if you decide to go back to 100% factory default state, S-ON should be the last step (after unroot, bootloader lock, cid restoring, etc.).
2) Before going back to S-ON, make sure you have a stock hboot. If you go S-ON while having a custom hboot, your device will be bricked.
Just one quick question is this also working for h1.55?
elf_made said:
Just one quick question is this also working for h1.55?
Click to expand...
Click to collapse
Yep.
edorner said:
Hey shiropetto,
It is not necessary to backup your data. Nothing will get wiped, when you use this method. Your DATA partition will remain intact.
However I still recommend you to do some kind of backup before you begin. Just as a precaution...
TBH, I am not sure.
You could try following the procedure from step 1 to 18, without performing step 14. In theory, it should be safe to try.
That might give you root.
However my guess is that Step 15 will probably not work without S-off or unlocked bootloader.
S-ON is very easy So I honestly do not see any reason why you would not want to go S-OFF.
To revert to S-ON:
1) open a cmd window in your ADB directory. plug in phone ,usb debugging on
2) adb devices
3) adb reboot bootloader
4) fastboot devices
5) fastboot oem writesecureflag 3
6) fastboot reboot-bootloader
7) verify you are locked s-on
8) fastboot reboot
There are just two important things you must keep in mind:
1) When / if you decide to go back to 100% factory default state, S-ON should be the last step (after unroot, bootloader lock, cid restoring, etc.).
2) Before going back to S-ON, make sure you have a stock hboot. If you go S-ON while having a custom hboot, your device will be bricked.
Click to expand...
Click to collapse
* thx for your suggestion!
*that mean step 14 including s-off & unlocking? is it will brick if skip step 14?
*thx for your kindness for revert from s-off to s-on!
*i do believing the hboot version still same as official hboot if i never flash other firmware version and device will stay in safe. pls correct me if this explanation was wrong.
shiropetto said:
*that mean step 14 including s-off & unlocking? is it will brick if skip step 14?
Click to expand...
Click to collapse
What I meant is:
If you want to root your phone without S-OFF, you need to perform steps 1-2-3-4-5-6-7-8-9-10-11-12-13-15-16-17-18 from my guide.
It will not brick your device, but there is a good chance it will not be successful either.
BTW, I just had another idea!
If you don't want S-OFF, just unlock & root, there is another method, which might be more suited to your needs:
LINK
Pls check it out. It basically goes like this: HTCdev unlock -> install custom recovery -> install su + superuser/supersu ffrom custom recovery -> done
shiropetto said:
*i do believing the hboot version still same as official hboot if i never flash other firmware version and device will stay in safe. pls correct me if this explanation was wrong.
Click to expand...
Click to collapse
Your explanation is correct. If you have not -intentionally- flashed a modified hboot image to your device, then you can be sure it contains an "original" hboot partition, signed by HTC. And anyway, it is only possible to flash a custom hboot is you are S-OFF. And since you obviously don't have S-OFF yet, it is impossible for you to have a custom/modified hboot
edorner said:
What I meant is:
If you want to root your phone without S-OFF, you need to perform steps 1-2-3-4-5-6-7-8-9-10-11-12-13-15-16-17-18 from my guide.
It will not brick your device, but there is a good chance it will not be successful either.
BTW, I just had another idea!
If you don't want S-OFF, just unlock & root, there is another method, which might be more suited to your needs:
LINK
Pls check it out. It basically goes like this: HTCdev unlock -> install custom recovery -> install su + superuser/supersu ffrom custom recovery -> done
Your explanation is correct. If you have not -intentionally- flashed a modified hboot image to your device, then you can be sure it contains an "original" hboot partition, signed by HTC. And anyway, it is only possible to flash a custom hboot is you are S-OFF. And since you obviously don't have S-OFF yet, it is impossible for you to have a custom/modified hboot
Click to expand...
Click to collapse
i have flashed everything, tamperred, s-off, unlocked, but no SU. what i need suppose to redo which steps? coz i was accidentally done the wrong typo during step 16, even i repeat from step 12 "adb shell", its still the same no root permission once i run the SuperSU. any SU could be flashable via recovery? perhaps the Root_wp_mod.zip will bring the bugs (reported by some users).
shiropetto said:
i have flashed everything, tamperred, s-off, unlocked, but no SU. what i need suppose to redo which steps? coz i was accidentally done the wrong typo during step 16, even i repeat from step 12 "adb shell", its still the same no root permission once i run the SuperSU. any SU could be flashable via recovery? perhaps the Root_wp_mod.zip will bring the bugs (reported by some users).
Click to expand...
Click to collapse
I see.
This should work:
Code:
/data/local/tmp/temproot
mount -o remount,rw -t ext4 /dev/block/mmcblk0p38 /system
cat /storage/ext_sd/su > /system/xbin/su
chmod 04755 /system/xbin/su
Then open the Play Store and install SuperSu
If this solution does not work, then just flash a custom recovery e.g. TWRP, and install SuperSU from there.
edorner said:
I see.
This should work:
Code:
/data/local/tmp/temproot
mount -o remount,rw -t ext4 /dev/block/mmcblk0p38 /system
cat /storage/ext_sd/su > /system/xbin/su
chmod 04755 /system/xbin/su
Then open the Play Store and install SuperSu
If this solution does not work, then just flash a custom recovery e.g. TWRP, and install SuperSU from there.
Click to expand...
Click to collapse
Could u provide or guide me which one suitable for flashing via recovery mode? I try with root_wp_mod but removed tweaks n replace the supersu n su from your given link. Its been there in menu but can't proceed the binary progress, maybe su not installed properly.
edit: I have rooted with the link given by u. Thx! Hurray! I'm enjoying my s-off butterfly S now!
Sent from my HTC Butterfly s using xda premium
shiropetto said:
Could u provide or guide me which one suitable for flashing via recovery mode?
Sent from my HTC Butterfly s using xda premium
Click to expand...
Click to collapse
Great! Congrats
edorner said:
Yep.
Click to expand...
Click to collapse
Well I tried all the steps but the damn phone is still S-ON.
Here is my configuration:
Rooted
Android version: 4.3
Htc sense: 5.5
Software number: 2.21.708.1
Htc sdk api level: 5.65
kernel version: 3.4.10-g158f9a4 [email protected]#1
Please find below my cmd window which just hanged out and a print screen of my bootloader... Hope this helps! Thanks a lot!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Am I the only one having the above issue/configuration for which the s-off could not be done? Thanks!
help
hello
I'm new to this phone and I would like to know that I can do if I already have the bootloader unlocked HTCDev, where do I start?
thanks greetings
GAVANA said:
hello
I'm new to this phone and I would like to know that I can do if I already have the bootloader unlocked HTCDev, where do I start?
thanks greetings
Click to expand...
Click to collapse
If u have taken the kit Kat update u will have to wait for new s off
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
ups!!!
daorderdillon said:
If u have taken the kit Kat update u will have to wait for new s off
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
Click to expand...
Click to collapse
lol, just when I read your message, my phone ends Upgrading to kit kat,
I'll have to wait then, but I can do root and install recovery?
Greetings buddy
Related
CAUTION!! By upgrading HBOOT to 1.00+ you loose the ability to S-OFF your Legend!!!
Preface
Because there are too many ppl without any knowledge spreading false findings and statements I decided to write this HOWTO.
Audience
This HOWTO is primarily ment for those who already have rooted Legends but they recently experienced problems flashing CM's or new Vodafone FroYo boot.img.
Background
HBOOT is like a BIOS in our PCs and to cut a long story short it also contains partition table for phone's internal storage. That means it has info on where exactly certain partition starts and how big it is.
At HTC they decided to partition Legend's internal storage this way:
misc 640 kB
recovery 4,375 MB
boot 2,5 MB
system 240 MB
cache 40 MB
data 185 MB
...but as we found out (first with CM nightly) boot partition was a little short for the boot.img to fit in if we had one or more bad cells (sectors) on it. Eventually we found out that quite some Legend's had bad cell on boot partition and those unfortunate souls that owned such phone were unable to upgrade to Vodafone FroYo rooted ROM too.
I think that HTC also recognized that Legend's boot partition was kinda small so they rearanged partition table in HBOOT 1.00 a bit making boot partition bigger (now it is 3 MB) by shrinking recovery partition a little.
So now we know that some of us actually need HBOOT 1.00 in order to flash FroYo's boot.img without a problem. But how do we keep root then?
Prerequirements
Android SDK (primarily adb)
working USB drivers (for adb to work)
goldcard (in case you are trying to flash ROMs with different CID than your phone has)
ClockWorkMod recovery (if your Legend is already rooted)
Rerequirements
Vodafone FroYo OTA update (actually just firmware.zip from OTA)
Legend rooting tools (just testimage.zip)
Hack 4 Legend v5(just misc1-2.img and flash_image)
VISIONary r13(r14 is out also but i haven't tested it yet)
Instructions
I will split instructions into two parts... for already rooted phones and phones that were already updated with Vodafone OTA thus they lost root.
Already OTA updated with HBOOT 1.00
That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Unzip r4-legend-root.zip and find testimage.zip in it. Put it on your phone's sdcard renaming it to LEGEIMG.zip. You can then reboot into bootloader issuing:
Code:
adb reboot bootloader
...from command prompt. Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard. Make your sdcard gold and try again. After successful flash and reboot you may remove LEGEIMG.zip from sdcard. Next step is upgrading of rooted FroYo ROM. Put FroYo update ROM zip to your sdcard and install it via ClockworkMod recovery. You may also flash backed up misc partition after that. Still in recovery mode and hooked with your PC switch to command prompt and restore it back:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.
Rooted Eclair Voda FroYo or CM with HBOOT 0.43
Since you have already rooted phone we can prepare everything before we start. Hook your phone to your PC. Put FroYo ROM update zip to phone's sdcard. Put also misc1-2.img and flash_image from hack4legend-v5.zip and testimage.zip from r4-legend-root there. Extract Vodafone FroYo OTA and put firmware.zip to your phone's sdcard renaming it to LEGEIMG.zip. Reboot into bootloader from command prompt:
Code:
adb reboot bootloader
...bootloader will find LEGEIMG.zip extract it into RAM and check its integrity. If you get CID error at this point you don't have gold card. Make your sdcard gold and retry the procedure.
After successfull flashing of LEGEIMG.zip (firmware.zip from FroYo OTA) you have HBOOT 1.00, new (unrooted) recovery, new (unrooted) boot but old and intact system with superuser.apk and su. Reboot. When system is available, tick "USB debugging" in Settings->Applications->Development. After that you will be able to adb shell into your phone. Fire up some command prompt and issue:
Code:
adb shell
su
...while phone screen is still on. Superuser will pop-up. Grant it. Now make a backup of misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
...now copy flash_image from sdcard to internal storage, change its permissions, and flash misc1-2.img:
Code:
cp /sdcard/flash_image /data/local/
chmod 755 /data/local/flash_image
/data/local/flash_image misc /sdcard/misc1-2.img
...rename LEGEIMG.zip to firmware.zip and testimage.zip to LEGEIMG.zip:
Code:
mv /sdcard/LEGEIMG.zip /sdcard/firmware.zip
mv /sdcard/testimage.zip /sdcard/LEGEIMG.zip
...exit from adb shell and reboot into bootloader:
Code:
exit
adb reboot bootloader
Phone will reboot, find LEGEIMG.zip and flash it over. You will end up with HBOOT 1.00 and downgraded and rooted recovery. Boot into ClockworkMod recovery and flash Voda FroYo custom update of your choice from your sdcard. You may also want to restore backed up misc partition after updating is done:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.
Goldcard (no remove, no format, no data loss)
Here are few easy steps on how to make Goldcard without taking it out of your phone but you have to be root (VISIONary temproot is fine).
You will be doing this from command prompt:
Code:
adb shell
su
First you need to find out sdcard's CID:
Code:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
...copy it into text box on http://hexrev.soaa.me/. Now go to http://psas.revskills.de/?q=goldcard and put in the reversed CID you have got on previous web page. Push goldcard.img to your phone via 2nd command prompt:
Code:
adb push goldcard.img /data/local/
...unmount sdcard via Settings, go back to 1st command prompt and make a backup then make goldcard:
Code:
dd if=/dev/block/mmcblk0 count=1 of=/data/local/sdcard_backup.img
cat /data/local/goldcard.img > /dev/block/mmcblk0
sync
exit
You may also pull that backup to your PC:
Code:
adb pull /data/local/sdcard_backup.img .
BlaY0 said:
Reserved...
Click to expand...
Click to collapse
awosome , I think you must have found some method to crack the SPL? just as desire do ?
waiting
There's actually no cracking of SPL involved...
Hi blay0,
I follow your link to vodafone ota update and appoint me to the website, where is the the link to download it?
Thanks.
Sent from my HTC Legend using Tapatalk
BesFen said:
Hi blay0,
EDITED: I got it, thanks
Click to expand...
Click to collapse
THX
@blay0:
thanks you are great developer.
so if you could temproot automated so you could build pc software to root legend with one click automatically like as wildfire desire ......
thx again
Hmm, I don't understand what are you trying to say???
Sent from my HTC Legend
BlaY0 said:
Hmm, I don't understand what are you trying to say???
Sent from my HTC Legend
Click to expand...
Click to collapse
in htc wildfire rooting process will do Unrevoked 3 for Wildfire
is it possible to automated above process?
VISIONary has an option to "temproot" on every boot.
But I don't see why you would do that if you can root the way I described.
Sent from my HTC Legend
Thanks Blayo ...
@ Blayo
I have some doubts regarding OTAs .. Please check your PM
The primary use of OTA here is just to extract firmware.zip flashing it to upgrade HBOOT. This is not HOWTO for updating the whole system via OTAs.
Sent from my HTC Legend
After flashing firmware.zip, the phone wont boot. Stuck at the HTC logo. What should I do?
Hey guys , im really troubled gettin permission denied on push.
any suggjestions? googled loads of it but nothing related to my issue
Edit: i got root tru visionary yes , it aply's well and su promts for permission so i guess i got root
so was wondering why i keep gettin permission denied on any command in adb
Second EDIT : Nevermind total noobness , forgot i cant push within adb shell.
Hats off to BlaY0 for another amazing work.
rajasyaitan said:
Hats off to BlaY0 for another amazing work.
Click to expand...
Click to collapse
Yes indeed m8 , thanks for your efforts!
Finaly unlocked the Hboot 1.00 running rooted ota froyo
/bow 2 BlaYo.
You're awesome.
Amazing, thanx a million!!
Keeps the Legend running smoothly with custom Froyo Modaco rom.................
I used this guide after my downgrade to Rom 1.31 with HBoot 1.00 and it worked like a charm ! Thank you !
wow You're awesome
If you upgraded your device with official RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed
and your at HBOOT 2.02.0002 with S-ON then dont worry.
Follow below steps and you are back to normal to BLACKROSE with your own choice of ROM.
First Remove all kind of HTC drivers/HTC SYNC software from your computer and install these drivers (click to download) HTCDriver3.0.0.007.exe
Download attached files and link provided in my post.
1. Get the UNLOCK.bin file by registering htcdev.com and ( I hope you know how to unlock through HTCDEV.com) (attached adb.rar contains adb.exe , fastboot.exe and misc_version file)
2. Now In the bootloader You will see ***UNLOCKED**** at this time flash the recovery ( i love 4xt) So i downloaded 4xt and use this command.
( you need to be in FASTBOOT-USB MODE)
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
(where recovery.img is could be any recovery either clockmod or 4xt)
3. Download the Superuser-3.1.3-arm-signed.zip put it on SDCARD
4. Boot in to recovery and install Superuser-3.1.3-arm-signed and reboot (here you got root access to the device)
5.Do a normal boot enable usb debug and connect to the computer .And in the command prompt run these commands to check you got root access or not
adb.exe shell
You get a prompt like this $ means you are connected to the device then type su and press enter if your prompt change to this # means you got root access and then exit
Click to expand...
Click to collapse
So until now we have root access to our offical RUU ICS ROM and Now we are going to downgrade it .
6.Now type these commands in the command prompt
adb push misc_version /data/local/tmp/ <---- copying our file to the device
adb shell <--- you will get $ prompt
su <------you will get root access
chmod 777 /data/local/tmp/misc_version <--changing permissions of the file to execute
/data/local/tmp/misc_version -s 1.00.000.0 <----- you are faking your device for the official RUU installer that it need upgrade to gingerbread
reboot bootloader <-- rebooting to bootloader
Click to expand...
Click to collapse
Now your device will reboot in fastboot-usb mode (as it should be remain attached with computer) .Do not worry as it will still show same HBOOT 2.02.0002
7. Now run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe
8.After complete installation you will have HBOOT 1.13
9. Now follow Section 2 of this thread http://forum.xda-developers.com/showthread.php?t=1705913
After getting S-OFF you can install BLACKROSE HBOOT 2.02.0002 OR any other HBOOT of your device and your choice of ROM.
Feel free to ask if you feel any problem I tried my best to explain it with my poor English
msarmad said:
Hi brothers,
Is there any downgrade or s-off for HTC HBOOT 2.02.002?
Its RUU ICS 3.5 .I upgraded from BLACKROSE and now want to downgrade or S-OFF.
P.S. Its unlocked and rooted .
Please HELP.
Click to expand...
Click to collapse
This is not a Development topic and should have been posted in the General Section.
You need to go to the General Section and check out the Downgrade Script sticky post. It may work with HBOOT 2.02.0002 if the tacoroot exploit still works.
http://forum.xda-developers.com/showthread.php?t=1373697
tpbklake said:
This is not a Development topic and should have been posted in the General Section.
You need to go to the General Section and check out the Downgrade Script sticky post. It may work with HBOOT 2.02.0002 if the tacoroot exploit still works.
http://forum.xda-developers.com/showthread.php?t=1373697
Click to expand...
Click to collapse
if you dont understand that fully use this guide
http://forum.xda-developers.com/showthread.php?t=1705913 and start from section 2
Thanks tpbklake and FallenSuisydal
I have tried revolutionary but it does not support (attached Screen)
Using the downgrade kit thing ,it gives error of not having permission to copy taco exploit.
You are getting this error because you need to start from section 1 of my thread, we also need the exact error of downgrade kit. So use my thread and start from the top
Sent from my Incredible S using xda premium
I am copying the out put
C:\Downloads\d\IncS_MVDTKv3.2\IncS_MVDTKv3.2>runme.cmd
Incredible S Main version downgrade toolkit v3.2
This script will:
------------------------------------------------------------------
(1) Apply a temp root using the tacoroot exploit
(2) Downgrade your phones version-main using misc_version
(3) Turn your phones SDcard into a Goldcard
------------------------------------------------------------------
Before u begin:
------------------------------------------------------------------
(1) backup everything you don't want to lose
(phone storage and SDcard)
(2) make sure u have installed adb drivers for ur device
(3) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(4) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(5) connect USB cable to PHONE and then connect to PC
------------------------------------------------------------------
If script hangs on waiting for device, unplug usb and reconnect
Press any key to continue . . .
Waiting for device to connect
* daemon not running. starting it now *
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
Device found
Pushing tacoroot
failed to copy 'files\tacoroot.bin' to '/data/local//tacoroot.bin': Permission d
enied
Correcting permissions
Unable to chmod /data/local/tacoroot.bin: No such file or directory
tacoroot rebooting phone to recovery
/system/bin/sh: /data/local/tacoroot.bin: not found
Waiting for device to connect
Device found
tacoroot starting adbD as root
/system/bin/sh: /data/local/tacoroot.bin: not found
Waiting for device to connect
Device found
Pushing misc_version
2089 KB/s (367096 bytes in 0.171s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:y
Waiting for device to connect
Device found
Pushing goldcard binary
1565 KB/s (19240 bytes in 0.012s)
Changing permissions
Installing goldcard
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
http://www.eff.org/
or to B. Kerler:
http://psas.revskills.de/
/dev/block/mmcblk1: cannot open for write: Permission denied
Undoing tacoroot (if applied)
/system/bin/sh: /data/local/tacoroot.bin: not found
Waiting for device to connect
Device found
Cleaning temp files
Checking version-main
< waiting for device >
version-main: 4.10.405.1
finished. total time: 0.001s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:n
If all steps were completed without error,
you should be ready to run the RUU downgrade
Press any key to continue . . .
Click to expand...
Click to collapse
Even i tried this command after it reboot it to BOOT LOADER
C:\Downloads\d\IncS_MVDTKv3.2\IncS_MVDTKv3.2\files>fastboot getvar version-main
version-main: 4.10.405.1
finished. total time: -0.000s
Click to expand...
Click to collapse
Now after using this script when it reboot it to bootloader i have the same 2.02.0002
and tried to run RUU it get give the same error of CID
Have u installed correct drivers? Also try boot phone into fastboot and try
Sent from my Incredible S using xda premium
Yup i am using these drivers HTCDriver3.0.0.007.exe
When i try the same IncS_MVDTKv3.2 in FASTBOOT mode
then it keep waitting for device .
and nothing happens.
Just to let u know currently i have this boot loader
***unlocked***
VIVO PVT SHIP S-ON
HBOOT-2.02.0002
RADIO-3831.18.00.11_M
eMMC-boot
May 22 2012
Bro i have done it...
As i have already told you that I was on official RUU ICS Sense 3.5 with HBOOT 2.02.0002
Also i unlocked it through HTCDEV
and loaded 4xt Recovery as well.
Now Phone was loaded as normal i attached with computer in charging mode.
and use these code from the IncS_MVDTKv3.2
C:\Downloads\d\IncS_MVDTKv3.2\IncS_MVDTKv3.2\files>adb push misc_version /data/l
ocal/tmp/
* daemon not running. starting it now *
* daemon started successfully *
2553 KB/s (367096 bytes in 0.140s)
Click to expand...
Click to collapse
THEN
adb shell
su <------- (THE KEY POINT IN THE WHOLE SOLUTION )
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/misc_version -s 2.00.000.0
Click to expand...
Click to collapse
Then This is the output
/data/local/tmp/misc_version -s 2.00.000.0
--set_version set. VERSION will be changed to: 2.00.000.0
Click to expand...
Click to collapse
Then i reboot to bootloader
And RUN RUU_VIVO_SENSE30_S_HTC_WWE_3.11.405.2_Radio_20.4805.30.0822U_3822.01.08.14_M_release_252414_signed.exe
So currently i am on HBOOT 2.01.0001. I could downgrade more below it if set it to 1.00.000.0 in the misc_version.
NOw could you please send me the files to downgrade HBOOT 2.01.0001 so that i can install blackrose ,you mentioned them here http://forum.xda-developers.com/showthread.php?t=1373697&page=87
Thanks,
msarmad said:
Bro i have done it...
Then i reboot to bootloader
And RUN RUU_VIVO_SENSE30_S_HTC_WWE_3.11.405.2_Radio_20.4805.30.0822U_3822.01.08.14_M_release_252414_signed.exe
So currently i am on HBOOT 2.01.0001. I could downgrade more below it if set it to 1.00.000.0 in the misc_version.
NOw could you please send me the files to downgrade HBOOT 2.01.0001 so that i can install blackrose ,you mentioned them here http://forum.xda-developers.com/showthread.php?t=1373697&page=87
Thanks,
Click to expand...
Click to collapse
The RUU/ROM you are running is too new. You need to run a RUU/ROM that has HBOOT 1.13. That is the key to the downgrade!!!! Once you are on HBOOT 1.13, then you can run Revolutionary and get S-OFF.
BRo This rom is ok for HBOOT 1.13 ?
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe
Click to expand...
Click to collapse
Is there any way to downgrade HBOOT without 200+mb ruu rom ?
I have currently some downloading issues
msarmad said:
BRo This rom is ok for HBOOT 1.13 ?
Click to expand...
Click to collapse
msarmad said:
Is there any way to downgrade HBOOT without 200+mb ruu rom ?
I have currently some downloading issues
Click to expand...
Click to collapse
Yes that is a good one to use. No, you need to use an official RUU or PG32IMG.zip ROM that contains HBOOT 1.13
Thanks for your help bros.....
I got my black rose and s-off
What was happen that i update with
RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed
Click to expand...
Click to collapse
my machine.
Since then i was on HBOOT 2.02.0002 and S-ON
And i am back to normal with Official ICS 3.5 sense from here http://forum.xda-developers.com/showthread.php?t=1756500 which doesn't need S-ON
OK, so I did something not very wise...
I was S-OFF, on revolutionary HBoot, then installed Blackrose to try some ROM. It all went well until for whatever reason I don't know, I uninstalled Blackrose HBoot...
Then, my phone went back to HBoot 1.13 S-ON with a security warning on the top of Bootloader.
It was OK still, but, the breaking point was that I was in a hurry going home so installed: RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.3 0.0833U_3831.18.00.11_M_release_266013_signed, by mistake... should have used the Gingerbread RUU...
This one makes my phone completely stock, S-ON, Hboot 2.02.0002 with no root.
I tried to follow the S-OFF threads, using the IncS-MVDTKv3.2 method, but could not succeed (output the same as post #6). And since I do not have root so am not able to do:
--------------------------------
adb shell
su <------- (THE KEY POINT IN THE WHOLE SOLUTION )
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/misc_version -s 2.00.000.0
---------------------------------
as OP did in post #9.
When doing "/data/local/tmp/misc_version -s 2.00.000.0", I got error:
---------------------------------
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
---------------------------------
So is there anyway to do S-OFF in this case then?
Thanks!!
Bro exactly same thing happened with me and i stuck at the same spot where u r .But do not worry
Follow below steps and you are back to normal to BLACKROSE with your own choice of ROM.
First Remove all kind of HTC drivers/HTC SYNC software from your computer and install these drivers (click to download) HTCDriver3.0.0.007.exe
Download attached files and link provided in my post.
1. Get the UNLOCK.bin file by registering htcdev.com and ( I hope you know how to unlock through HTCDEV.com) (attached adb.rar contains adb.exe , fastboot.exe and misc_version file)
2. Now In the bootloader You will see ***UNLOCKED**** at this time flash the recovery ( i love 4xt) So i downloaded 4xt and use this command.
( you need to be in FASTBOOT-USB MODE)
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
(where recovery.img is could be any recovery either clockmod or 4xt)
3. Download the Superuser-3.1.3-arm-signed.zip put it on SDCARD
4. Boot in to recovery and install Superuser-3.1.3-arm-signed and reboot (here you got root access to the device)
5.Do a normal boot enable usb debug and connect to the computer .And in the command prompt run these commands to check you got root access or not
adb.exe shell
You get a prompt like this $ means you are connected to the device then type su and press enter if your prompt change to this # means you got root access and then exit
Click to expand...
Click to collapse
So until now we have root access to our offical RUU ICS ROM and Now we are going to downgrade it .
6.Now type these commands in the command prompt
adb push misc_version /data/local/tmp/ <---- copying our file to the device
adb shell <--- you will get $ prompt
su <------you will get root access
chmod 777 /data/local/tmp/misc_version <--changing permissions of the file to execute
/data/local/tmp/misc_version -s 1.00.000.0 <----- you are faking your device for the official RUU installer that it need upgrade to gingerbread
reboot bootloader <-- rebooting to bootloader
Click to expand...
Click to collapse
Now your device will reboot in fastboot-usb mode (as it should be remain attached with computer) .Do not worry as it will still show same HBOOT 2.02.0002
7. Now run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe
8.After complete installation you will have HBOOT 1.13
9. Now follow Section 2 of this thread http://forum.xda-developers.com/showthread.php?t=1705913
After getting S-OFF you can install BLACKROSE HBOOT 2.02.0002 and your choice of ROM.
Feel free to ask if you feel any problem I tried my best to explain it with my poor English
Thanks a lot for the guide, yes I unlocked the phone already, did not know at this stage you can already flash 4ext or cwm recovery... Always did that while I flashed revolutionary....
Will do this when I get home. Stuck in the rain now...
Sent from my HTC Incredible S using xda app-developers app
@msarmad, Thanks very much! I had some problem yesterday evening to downgrade the hboot, but this morning, at work everything worked perfectly!
Now back to revolutionary again with root.
Cheers!!!
u r welcome bro.....
Hi,
i get untill step 5.
when i type su i get nothing back.
I tryed su-3.0-efgh-signed and then i get : Permission denied.
my bootinfo:
***UNLOCKED***
VIVO PVT SHIP S-ON RL
HBOOT-2.02.002
Radio-3831.18.00.11_m
Any solution?
Update 1: Before following this guide, you should try using the tool from http://firewater-soff.com to obtain S-OFF. If it does not work then proceed with the following guide.
I do NOT take any credit for this guide.
You can thank BD619 for walking me through all this and the updated command, Indirect for the original commands, benny3 for his awesome ROM, O.M.J for his 3.04.651.2 RUU and for his 3.05.651.6 Firmware, and RumRunner for their awesome S-Off tool!
Also, if anything goes wrong I can try to help you, but the only person responsible is yourself for not following the guide 100%. I have done this all myself and it worked like a charm.
After 3.04.651.2, attempting to achieve S-Off with rumrunner will fail every time after the pouring 8 stage. This guide will show you how to change your version number in order to install an older RUU. After installing the older RUU, then you can proceed to unlock the bootloader, download benny3's Stock ROM (Link Below), flash it after a full wipe, and finally run rumrunner again with success. From there you can optionally update your firmware (Link Below) and flash a ROM of your choice. Once official kitkat is released this guide will not work because the hboot will be different than the one found in the RUU
Changing the Mainver
Before doing all of this, you should backup all your applications and other data with Titanium Backup which can be found in the Play Store. Once your backup is complete, you must copy the titanium backup folder found on your internal storage to your computer because the RUU will wipe the entire storage. Copy any other things you may need including Photos, Music, and Downloads to your computer so you can restore them later. Also, make sure you are on hboot 1.55. I have not tested this with any other hboot but it is confirmed working on hboot 1.55.
1. Make sure the ADB drivers are set up properly in recovery. I used TWRP but other recoveries should be fine.
2. Boot into recovery and connect the phone to the computer.
3. Open the command prompt, and type in adb devices A string of letters and numbers should pop up. This is only to test the ADB drivers and make sure they are working properly.
4. Now type adb shell and press enter.
5. Now type this exactly as it is here echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160 with the quotes around the version number. After entering the command, it will say failed in the window but just ingnore that.
^^^I recommend you copy and paste to avoid typos.
6. Now enter adb reboot bootloader into the prompt. Your phone will now reboot bootloader and you should see your version number changed to 3.04.651.2.
7. As most of you may know, in order to install a RUU you must relock the bootloader, so click on fastboot on the phone and make sure it says fastboot usb. From here type in fastboot oem lock. Now the bootloader is locked.
Essentially, all we did up to this point is change the version number in order to trick the RUU into installing, and lock the bootloader also for the RUU to work.
Installing the RUU
8. Now you have to download the 3.04.651.2 RUU from http://forum.xda-developers.com/showthread.php?t=2508907. The zip or exe is fine. Do not use the decrypted version.
9. Once downloaded, put the phone into fastboot usb mode, and run the exe. If you downloaded the zip, follow the instruction in the link above to install it.
Flashing the custom ROM
10. Once the RUU is complete you will have to download benny3's ROM from http://forum.xda-developers.com/showpost.php?p=47048176&postcount=2. Either odexed or deodexed is fine. I personally chose odexed but it does not matter. Once downloaded make sure the ROM is not corrupt by matching the MD5 codes, or simply opening the zip.
11. We cannot install yet however because the RUU restored the stock recovery and the bootloader is locked.
12. Unlock the bootloader by following the instructions at http://www.htcdev.com/bootloader
13. Once the bootloader is unlocked we can now flash a custom recovery. Download TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/m7wls Once it finished put phone into fastboot usb, copy the TWRP img you just downloaded into the fastboot command prompt folder, open fastboot command prompt, and type in fastboot flash recovery recovery.img Replace recovery.img in the command with the actual name of the file.
14. Once the custom recovery is installed boot into Android and copy the downloaded ROM into the internal storage, boot into recovery and do a full wipe (Dalvik Cache, Cache, Data, System). Do NOT wipe the internal storage!
15. Go back and tap install. Select the ROM you placed in the internal storage in step 11. Once it is flashed clear the dalvik cache and reboot the system.
Running RumRunner
16. Before you run RumRunner, confirm all drivers are working correctly by testing adb and fastboot commands in recovery, fastboot, and the OS. Enable USB Debugging in developer options. Set auto sleep to the maximum of ten minutes. Go to personalize, and choose the no lockscreen setting. Go to settings, power, and make sure fastboot is NOT checked. Disable firewall and anti virus programs on your computer. Run the SuperSu app and make sure all SU Binaries are updated.
17. Once you've done everything above, you can download RumRunner 0.5 from http://rumrunner.us/downloads-2/ Make sure phone is connected to PC in ADB mode, and run soju.exe as administrator. Follow the onscreen instructions.
18. Once RumRunner is complete your phone will reboot to bootloader and report S-Off.
Updating Firmware
19. Now that you are S-Off, we can move on and update the firmware. Download the Full unmodified Firmware (fastboot flashable) from http://forum.xda-developers.com/showthread.php?t=2576995 Follow the instructions in the link for a guide on how to flash the firmware.
20. Once your firmware is updated if you reboot into the OS, your touchscreen may not respond. Do not worry about that it will be fixed soon.
Flashing A Custom ROM
21. Find a ROM of your choice in the android development section or the android original development section. The ROM you choose MUST be a Sprint ROM.
22. Copy the ROM to your internal storage, reboot to recovery. and do a full wipe (Dalvik Cache, Cache, Data, System). Again, do NOT wipe the internal storage!
23. Once the wipe is complete, flash the ROM you chose and clear the dalvik cache. Reboot system and you should be good to go. Remember, the first boot takes a bit longer than usual. Give it a good ten minutes before getting worried.
24. At this point you could copy your titanium backup folder back into the internal storage. Install titanium backup from the Play Store, open it, go to menu>preferences, scroll down to backup folder location, tap it and find the backup folder you just copied to your storage. Now you can restore all the apps and data you backed up. Also, you can copy all the other things you backed up to the computer.
I know this is a long guide, but the process above works 100%, and I tried to include as many details as possible. If you have any suggestions, please let me know. Also, if anyone runs into any problems, post it in the comments and maybe someone can help you.
Nicely done
This is the command you should copy and paste into your cmd window for step 5
Code:
echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
As stated below please use at your own risk this is a VERY dangerous command if you don't know what you are doing!!!
Thanks!
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life
jluca98 said:
I do NOT take any credit for this guide.
You can thank BD619 for walking me through all this and the updated command, Indirect for the original commands, benny3 for his awesome ROM, O.M.J for his 3.04.651.2 RUU and for his 3.05.651.6 Firmware, and RumRunner for their awesome S-Off tool!
Also, if anything goes wrong I can try to help you, but the only person responsible is yourself for not following the guide 100%. I have done this all myself and it worked like a charm.
After 3.04.651.2, attempting to achieve S-Off with rumrunner will fail every time after the pouring 8 stage. This guide will show you how to change your version number in order to install an older RUU. After installing the older RUU, then you can proceed to unlock the bootloader, download benny3's Stock ROM (Link Below), flash it after a full wipe, and finally run rumrunner again with success. From there you can optionally update your firmware (Link Below) and flash a ROM of your choice. Once official kitkat is released this guide will not work because the hboot will be different than the one found in the RUU
Changing the Mainver
Before doing all of this, you should backup all your applications and other data with Titanium Backup which can be found in the Play Store. Once your backup is complete, you must copy the titanium backup folder found on your internal storage to your computer because the RUU will wipe the entire storage. Copy any other things you may need including Photos, Music, and Downloads to your computer so you can restore them later.
1. Make sure you are on hboot 1.55. I have not tested this with any other hboot but it is confirmed working on hboot 1.55.
2. Make sure the ADB drivers are set up properly in recovery. I used TWRP but other recoveries should be fine.
3. Boot into recovery and connect the phone to the computer.
3. Open the command prompt, and type in <code>adb devices</code> A string of letters and numbers should pop up. This is only to test the ADB drivers and make sure they are working properly.
4. Now type <code>adb shell</code> and press enter.
5. Now type this exactly as it is here echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160 with the quotes around the version number. After entering the command, it will say failed in the window but just ingnore that.
^^^I recommend you copy and paste to avoid typos.
6. Now enter adb reboot bootloader into the prompt. Your phone will now reboot bootloader and you should see your version number changed to 3.04.651.2.
7. As most of you may know, in order to install a RUU you must relock the bootloader, so click on fastboot on the phone and make sure it says fastboot usb. From here type in fastboot oem lock. Now the bootloader is locked.
Essentially, all we did up to this point is change the version number in order to trick the RUU into installing, and lock the bootloader also for the RUU to work.
Installing the RUU
8. Now you have to download the 3.04.651.2 RUU from http://forum.xda-developers.com/showthread.php?t=2508907. The zip or exe is fine. Do not use the decrypted version.
9. Once downloaded, put the phone into fastboot usb mode, and run the exe. If you downloaded the zip, follow the instruction in the link above to install it.
Flashing the custom ROM
10. Once the RUU is complete you will have to download benny3's ROM from http://forum.xda-developers.com/showpost.php?p=47048176&postcount=2. Either odexed or deodexed is fine. I personally chose odexed but it does not matter. Once downloaded make sure the ROM is not corrupt by matching the MD5 codes, or simply opening the zip.
11. Boot up current ROM and copy the downloaded ROM into the internal storage. We cannot install yet however because the RUU restored the stock recovery and the bootloader is locked.
12. Unlock the bootloader by following the instructions at http://www.htcdev.com/bootloader
13. Once the bootloader is unlocked we can now flash a custom recovery. Download TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/m7wls Once it finished put phone into fastboot usb, copy the TWRP img you just downloaded into the fastboot command prompt folder, open fastboot command prompt, and type in fastboot flash recovery recovery.img Replace recovery.img in the command with the actual name of the file.
14. Once the custom recovery is installed boot into recovery and do a full wipe (Dalvik Cache, Cache, Data, System). Do NOT wipe the internal storage!
15. Go back and tap install. Select the ROM you placed in the internal storage in step 11. Once it is flashed clear the dalvik cache and reboot the system.
Running RumRunner
16. Before you run RumRunner, confirm all drivers are working correctly by testing adb and fastboot commands in recovery, fastboot, and the OS. Enable USB Debugging in developer options. Set auto sleep to the maximum of ten minutes. Go to personalize, and choose the no lockscreen setting. Go to settings, power, and make sure fastboot is NOT checked. Disable firewall and anti virus programs on your computer. Run the SuperSu app and make sure all SU Binaries are updated.
17. Once you've done everything above, you can download RumRunner 0.5 from http://rumrunner.us/downloads-2/ Make sure phone is connected to PC in ADB mode, and run soju.exe as administrator. Follow the onscreen instructions.
18. Once RumRunner is complete your phone will reboot to bootloader and report S-Off.
Updating Firmware
19. Now that you are S-Off, we can move on and update the firmware. Download the Full unmodified Firmware (fastboot flashable) from http://forum.xda-developers.com/showthread.php?t=2576995 Follow the instructions in the link for a guide on how to flash the firmware.
20. Once your firmware is updated if you reboot into the OS, your touchscreen may not respond. Do not worry about that it will be fixed soon.
Flashing A Custom ROM
21. Find a ROM of your choice in the android development section or the android original development section. The ROM you choose MUST be a Sprint ROM.
22. Copy the ROM to your internal storage, reboot to recovery. and do a full wipe (Dalvik Cache, Cache, Data, System). Again, do NOT wipe the internal storage!
23. Once the wipe is complete, flash the ROM you chose and clear the dalvik cache. Reboot system and you should be good to go. Remember, the first boot takes a bit longer than usual. Give it a good ten minutes before getting worried.
24. At this point you could copy your titanium backup folder back into the internal storage. Install titanium backup from the Play Store, open it, go to menu>preferences, scroll down to backup folder location, tap it and find the backup folder you just copied to your storage. Now you can restore all the apps and data you backed up. Also, you can copy all the other things you backed up to the computer.
I know this is a long guide, but the process above works 100%, and I tried to include as many details as possible. If you have any suggestions, please let me know. Also, if anyone runs into any problems, post it in the comments and maybe someone can help you.
Click to expand...
Click to collapse
Thank you and Big Daddy! Only thing I noted in instructions mentioned to copy downloaded ROM to internal storage and then to unlock bootloader. However this will erase everything and therefore ROM needs to be copied after doing unlock and twrp flash after unlock. I sincerely thank you for helping me achieve S-Off.
Doc
SOLID.
Great guide you guys. Very concise and easy to understand steps. :good:
Anyone who does not have S-OFF yet I highly suggest getting it before KitKat drops...HTC has a habit of making things harder with every OTA. Rumrunner may not work afterwards.
Docarut said:
Thank you and Big Daddy! Only thing I noted in instructions mentioned to copy downloaded ROM to internal storage and then to unlock bootloader. However this will erase everything and therefore ROM needs to be copied after doing unlock and twrp flash after unlock. I sincerely thank you for helping me achieve S-Off.
Doc
Click to expand...
Click to collapse
Ok guide was updated with proper instructions. Thanks for letting me know. I'm glad the guide worked for you!
What am I doing wrong?
D:\Users\Android\HTC One\HTC Unlock>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
FA37SSxxxxxx recovery
D:\Users\Android\HTC One\HTC Unlock>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
[try again]
D:\Users\Android\HTC One\HTC Unlock>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Windows 8.1 / TWRP / unlocked / fastboot works fine / etc
echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
you need to bold "echo" it took me a bit to figure I needed to copy that part of the string
That command is very, very dangerous if you screw up even a little -- could easily brick a device. OP, the guide is really useful for folks, but please put all the parts folks need to copy in quote blocks.
Most of the readers don't even know what the dd command is because they don't use any Unix type OS (e.g., Linux) and they are using it with full root level access.
[Edit: adding a little explanation]:
The 'dd' command is a 'direct dump' and it takes whatever you tell it from the 'if' parameter (input file) or if no 'if' flag is provided, from the standard input. The 'echo' command puts whatever you specify to the standard output (a.k.a., stdout in unix/linux terms). The vertical bar is a 'pipe' specifier and pipes the stdout of the last command to the input of the next -- in this case the 'dd' command.
So how can this all to really, really badly? Imagine, just by happenstance, the recovery shell you use sends error output to stdout (by a mistaken bug, instead of stderr which is the norm). Whatever the shell would print as the error message is going to go to the dd command as stdin and it will write that to your device where you tell it. In short, brick city.
Just by luck, imho, the user above who failed to add the "echo" was using a recovery that (very luckily) sent nothing to stdout, so dd didn't have anything to write. I'm telling you, folks, @BD619 and I both have stated on multiple occasions the raw danger here.
Be careful and DO NOT RUSH INTO THESE THINGS -- IF YOU ARE NOT SURE, EVEN IF ONLY 0.000000001% UNSURE ASK! WE WILL GET YOU SET.
jluca98 said:
I do NOT take any credit for this guide.
You can thank BD619 for walking me through all this and the updated command, Indirect for the original commands, benny3 for his awesome ROM, O.M.J for his 3.04.651.2 RUU and for his 3.05.651.6 Firmware, and RumRunner for their awesome S-Off tool!
Also, if anything goes wrong I can try to help you, but the only person responsible is yourself for not following the guide 100%. I have done this all myself and it worked like a charm.
After 3.04.651.2, attempting to achieve S-Off with rumrunner will fail every time after the pouring 8 stage. This guide will show you how to change your version number in order to install an older RUU. After installing the older RUU, then you can proceed to unlock the bootloader, download benny3's Stock ROM (Link Below), flash it after a full wipe, and finally run rumrunner again with success. From there you can optionally update your firmware (Link Below) and flash a ROM of your choice. Once official kitkat is released this guide will not work because the hboot will be different than the one found in the RUU
Changing the Mainver
Before doing all of this, you should backup all your applications and other data with Titanium Backup which can be found in the Play Store. Once your backup is complete, you must copy the titanium backup folder found on your internal storage to your computer because the RUU will wipe the entire storage. Copy any other things you may need including Photos, Music, and Downloads to your computer so you can restore them later. Also, make sure you are on hboot 1.55. I have not tested this with any other hboot but it is confirmed working on hboot 1.55.
1. Make sure the ADB drivers are set up properly in recovery. I used TWRP but other recoveries should be fine.
2. Boot into recovery and connect the phone to the computer.
3. Open the command prompt, and type in <code>adb devices</code> A string of letters and numbers should pop up. This is only to test the ADB drivers and make sure they are working properly.
4. Now type <code>adb shell</code> and press enter.
5. Now type this exactly as it is here echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160 with the quotes around the version number. After entering the command, it will say failed in the window but just ingnore that.
^^^I recommend you copy and paste to avoid typos.
6. Now enter adb reboot bootloader into the prompt. Your phone will now reboot bootloader and you should see your version number changed to 3.04.651.2.
7. As most of you may know, in order to install a RUU you must relock the bootloader, so click on fastboot on the phone and make sure it says fastboot usb. From here type in fastboot oem lock. Now the bootloader is locked.
Essentially, all we did up to this point is change the version number in order to trick the RUU into installing, and lock the bootloader also for the RUU to work.
Installing the RUU
8. Now you have to download the 3.04.651.2 RUU from http://forum.xda-developers.com/showthread.php?t=2508907. The zip or exe is fine. Do not use the decrypted version.
9. Once downloaded, put the phone into fastboot usb mode, and run the exe. If you downloaded the zip, follow the instruction in the link above to install it.
Flashing the custom ROM
10. Once the RUU is complete you will have to download benny3's ROM from http://forum.xda-developers.com/showpost.php?p=47048176&postcount=2. Either odexed or deodexed is fine. I personally chose odexed but it does not matter. Once downloaded make sure the ROM is not corrupt by matching the MD5 codes, or simply opening the zip.
11. We cannot install yet however because the RUU restored the stock recovery and the bootloader is locked.
12. Unlock the bootloader by following the instructions at http://www.htcdev.com/bootloader
13. Once the bootloader is unlocked we can now flash a custom recovery. Download TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/m7wls Once it finished put phone into fastboot usb, copy the TWRP img you just downloaded into the fastboot command prompt folder, open fastboot command prompt, and type in fastboot flash recovery recovery.img Replace recovery.img in the command with the actual name of the file.
14. Once the custom recovery is installed boot into Android and copy the downloaded ROM into the internal storage, boot into recovery and do a full wipe (Dalvik Cache, Cache, Data, System). Do NOT wipe the internal storage!
15. Go back and tap install. Select the ROM you placed in the internal storage in step 11. Once it is flashed clear the dalvik cache and reboot the system.
Running RumRunner
16. Before you run RumRunner, confirm all drivers are working correctly by testing adb and fastboot commands in recovery, fastboot, and the OS. Enable USB Debugging in developer options. Set auto sleep to the maximum of ten minutes. Go to personalize, and choose the no lockscreen setting. Go to settings, power, and make sure fastboot is NOT checked. Disable firewall and anti virus programs on your computer. Run the SuperSu app and make sure all SU Binaries are updated.
17. Once you've done everything above, you can download RumRunner 0.5 from http://rumrunner.us/downloads-2/ Make sure phone is connected to PC in ADB mode, and run soju.exe as administrator. Follow the onscreen instructions.
18. Once RumRunner is complete your phone will reboot to bootloader and report S-Off.
Updating Firmware
19. Now that you are S-Off, we can move on and update the firmware. Download the Full unmodified Firmware (fastboot flashable) from http://forum.xda-developers.com/showthread.php?t=2576995 Follow the instructions in the link for a guide on how to flash the firmware.
20. Once your firmware is updated if you reboot into the OS, your touchscreen may not respond. Do not worry about that it will be fixed soon.
Flashing A Custom ROM
21. Find a ROM of your choice in the android development section or the android original development section. The ROM you choose MUST be a Sprint ROM.
22. Copy the ROM to your internal storage, reboot to recovery. and do a full wipe (Dalvik Cache, Cache, Data, System). Again, do NOT wipe the internal storage!
23. Once the wipe is complete, flash the ROM you chose and clear the dalvik cache. Reboot system and you should be good to go. Remember, the first boot takes a bit longer than usual. Give it a good ten minutes before getting worried.
24. At this point you could copy your titanium backup folder back into the internal storage. Install titanium backup from the Play Store, open it, go to menu>preferences, scroll down to backup folder location, tap it and find the backup folder you just copied to your storage. Now you can restore all the apps and data you backed up. Also, you can copy all the other things you backed up to the computer.
I know this is a long guide, but the process above works 100%, and I tried to include as many details as possible. If you have any suggestions, please let me know. Also, if anyone runs into any problems, post it in the comments and maybe someone can help you.
Click to expand...
Click to collapse
OK command fixed in step 5.
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life
pbassjunk said:
What am I doing wrong?
D:\Users\Android\HTC One\HTC Unlock>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
FA37SSxxxxxx recovery
D:\Users\Android\HTC One\HTC Unlock>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
[try again]
D:\Users\Android\HTC One\HTC Unlock>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Windows 8.1 / TWRP / unlocked / fastboot works fine / etc
Click to expand...
Click to collapse
I'm not sure, maybe try another PC with windows 7, USB 2.0, and drivers installed correctly.
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life
jluca98 said:
I'm not sure, maybe try another PC with windows 7, USB 2.0, and drivers installed correctly.
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life
Click to expand...
Click to collapse
After some more testing, this seems to be an 8.1 specific issue. Not sure if it's an HTC driver issue, an 8.1 USB 2/3 driver issue or something with ADB (up to date), but I tried it on an 8 laptop (USB 3 only) along with a 7 desktop (USB 2 only, older imac in bootcamp heh) and things worked as expected.
Not scientific but as close as I could get with the hardware I have. Pretty sure it's an 8.1 problem.
Looks a little complicated as much as I would love to go s-off not sure if could handle this
Sent from my HTCONE using xda app-developers app
androidforeve said:
Looks a little complicated as much as I would love to go s-off not sure if could handle this
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Its not really that hard. If you follow instructions properly and meet the prerequisites in the OP then you will be fine. I know of multiple people who followed this guide with no problems. Try it and if you run into any issues post a comment and we will try to help you.
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life
androidforeve said:
Looks a little complicated as much as I would love to go s-off not sure if could handle this
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Thanks for the input but do I really need to be s-off? So far I can flash everything fine with no problem of course I have not tried flashing firmware or radios because I have latest ones I'm assuming that's the problem I will have but I thought I read somewhere that you can still flash firmware and radios even with s-on but I could be wrong
Sent from my HTCONE using xda app-developers app
You can read this guide to understand more about s-off. http://android-revolution-hd.blogspot.com/2013/06/do-we-really-need-s-off.html?m=1
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life
androidforeve said:
Looks a little complicated as much as I would love to go s-off not sure if could handle this
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Do a backup in recovery
Copy your entire internal sd to pc
Follow instructions as above
After s-off root like you did before
Move internal back to device
Restore in recovery
Good 30 minutes
I sugest you download everything first, that way your device isnt down while you wait
I only have 1 very anoying issue. Was 3.05.651.5 complete stock with root and .6 update released. I did s-off, did ota, then rooted. I'm 3.05.651.6 s-off, rooted and i still got the ota notice to update to 3.05.651.6 and it wont go away.
Maybe this can help you. http://forum.xda-developers.com/showthread.php?t=1856632
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life
saaaaweet
FOR SPRINT M8 NON-H/K MODELS ONLY
Well everyone I'm here to bring you a little tool set i use to take official OTAs.I am not a dev nor do I take credit for the work. This is mainly just a collection of things I used to get OFFICIAL OTA updates. I've used this on 2 Sprint m8's with STOCK Hboots so I am sure this will work. Please feel free to share this with others JUST GIVE CREDIT WHERE IT IS DUE.
To start off there are some requirements...
S-OFF is needed
STOCK HBOOT
HTC One M8 (Sprint non-Harmon Kardon)
UNLOCKED Bootloader (If you are LOCKED and rooted PLEASE use UNLOCK Bootloader method included in zip. DO NOT use HTCDEV to unlock... Your internal storage will be wiped if you do. YOU HAVE BEEN WARNED
MAKE SURE TO UNLOCK BOOTLOADER before doing any of this (instructions are included in zip)
1. Copy the stock nand to backup folder in twrp
2. Make a backup of your setup
3. Restore the stock nand provided
4. Flash stock recovery provided
5. Boot up and do all otas up to latest
6. Flash custom recovery
7. Restore your backup
8. Flash modified firmware
9. Lock bootloader
10. Flash asdp for hk mod.zip in ruu mode (same as flashing FIRMWARE) if audio is not working in htc music
Locking-Unlocking & Remove Tampered flag
***NEED TO BE S-OFF!!***
TO LOCK BOOTLOADER
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should be ***LOCKED***
TO UNLOCK BOOTLOADER
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should be ***UNLOCKED***
TO REMOVE ***TAMPERED*** text
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should not see ***TAMPERED***
Flashing Firmware
IN HBOOT MODE
1. Label the file to exactly 0P6BIMG.zip
2. Put zip in root of external SD card
3. Boot into HBOOT to flash (bootloader should detect zip automatically and prompt you to flash)
IN FASTBOOT MODE
1. Boot device into FASTBOOT mode (device should show FASTBOOT USB)
2. Put the firmware file to be flashed in the folder with fastboot.
3. Open a command prompt from the folder where fastboot is located.
4. Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 0P6BIMG_M8WHL_x.xx.xxx.x_firmware.zip (the name of the zip should match the name of the file you're flashing)
5. Once complete, you can fastboot reboot or fastboot reboot-bootloader depending on what you want to do next. If you choose bootloader, you can confirm that your radio is now updated to the one from the file you flashed
Links needed ...
For Locking and Unlocking bootloader (ONLY WORKS WITH ROOTED ROM AND S-OFF!!)
For Removing Tampered Flag (ONLY WORKS WITH ROOTED ROM AND S-OFF!!)
For Modified Firmware
I'd like to give thanks to the people that have made this possible
if i forget someone I'm sorry send me a pm I'll add you to the list
Team420 for taking me in showing me the basics
BADSEED for allowing me to break so many test roms lol
BD619 for hooking me up with adb files
scotty1223 for making those awesome guides
Captain_Throwback for providing the collection of firmware ... Oh yeah and the TWRP recovery
TEAMWIN for making TWRP in the 1st place
HTC for making such an awesome phone
DISCLAIMER: I AM IN NO WAY HELD LIABLE FOR DAMAGES MADE TO YOUR PHONE OR IF YOUR DEVICE TRANSFORMS INTO A DECEPTICON CAUSING WORLD DESTRUCTION...YOU ARE FOLLOWING AND FLASHING THIS AT YOUR OWN RISK
DOWNLOADS
Main Link on Mega HERE
Mirror Link on AFH HERE
And this as well
Hi,
Added to FAQ Guide Q15
Nice work Miggs:thumbup:
Sent from my HTC M8
Great work Bro, very helpful. Thank you
Just one thought on your thread title. You might change it to "How to Return to Stock" since most of those steps aren't needed to take a OTA. Very useful for those who need to go back to a stock device though.
Sent from my HTC M8
Magnum_Enforcer said:
Just one thought on your thread title. You might change it to "How to Return to Stock" since most of those steps aren't needed to take a OTA. Very useful for those who need to go back to a stock device though.
Sent from my HTC M8
Click to expand...
Click to collapse
GOOD CATCH!! THANKS ... That was actually how this idea came about lol
Good work Miggsr!
Need stock apps to take OTA
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Piroman024 said:
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Click to expand...
Click to collapse
Why not just keep a backup of the latest stock rom on your sdcard?
BD619 said:
Why not just keep a backup of the latest stock rom on your sdcard?
Click to expand...
Click to collapse
Or look in the first post of this thread for stock backups:
http://forum.xda-developers.com/showthread.php?t=2736048
Sent from my HTC M8
Piroman024 said:
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Click to expand...
Click to collapse
in my zip i have included a STOCK backup made with TWRP that is also included in the zip it has ALL stock apps that you may be looking for to make things easier just copy that folder to your TWRP backup folder whether its on your internal sd or external sd restore that and boot up
Tring to upgrade "dirty"
I do keep a copy of the stock rom for when stuff hits the fan. I also have a backup i made before I went S-off. I deleted a few of the system apps that were bugging me before I learned that OTA also checks apps.
I'm trying to get the OTA without wiping my phone and all the setup time I have so far spent on it.
I just try to install the OTA again this time i checked the log. I get "/system/app/Plusone.apk" has unexpected contents. I guessing this is caused from my removing apps. I'm thinking i can use this to find what the installer thinks is missing.
My last question, is there a way to extract .apk and .odex files from the ruu?
Piroman024 said:
I do keep a copy of the stock rom for when stuff hits the fan. I also have a backup i made before I went S-off. I deleted a few of the system apps that were bugging me before I learned that OTA also checks apps.
I'm trying to get the OTA without wiping my phone and all the setup time I have so far spent on it.
I just try to install the OTA again this time i checked the log. I get "/system/app/Plusone.apk" has unexpected contents. I guessing this is caused from my removing apps. I'm thinking i can use this to find what the installer thinks is missing.
My last question, is there a way to extract .apk and .odex files from the ruu?
Click to expand...
Click to collapse
okay with the first half of what you said... i have not had an ota check for apps... when removing google plus you probably left a second apk that works with it hence your error message. if you are looking to be able to take an official ota you should NOT be rooted. honesty if you meet ALL REQUIREMENTS i listed then just follow the guide you should be fine. the backup i have there is based on initial rom that came with the device. so you will have to do 3 ota updates to be exact. i made it that way out of personal preference. now for the second half of your post ... as i mentioned i am not a dev unfortunately i can not answer that question for you... slightly above my pay grade. not to put you on the spot either i'd like to keep thread on topic in OP.
so Harmon Kardon edition can not be unroot?
hhhstonehhh said:
so Harmon Kardon edition can not be unroot?
Click to expand...
Click to collapse
Sure it can...same steps just use HK files
BD619 said:
Sure it can...same steps just use HK files
Click to expand...
Click to collapse
I could not have said it any better lol
Great Tut Miggs !!!
cbrown245 said:
Great Tut Miggs !!!
Click to expand...
Click to collapse
thanks CB i just making things easier for others
Hi, i want to install custom rom on my razr i xt890 but "your device is not qualify to boot loader unlock". Is there way to install custom rom or to unlock without unlock code. Thanks in advance.
kirovBG said:
Hi, i want to install custom rom on my razr i xt890 but "your device is not qualify to boot loader unlock". Is there way to install custom rom or to unlock without unlock code. Thanks in advance.
Click to expand...
Click to collapse
No.
is there a way with RDS lite to change the firmware or something
can i use this method to locked phone: http://forum.xda-developers.com/showthread.php?p=41479852
I don't know for sure, but since u have root it should be possible - pls somebody correct me if I'm wong with this.
Should work like this:
Code:
adb push xyzrecovery.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/xyzrecovery.img
dd if=/data/local/tmp/xyzrecovery.img of=/dev/block/mmcblk0p6
exit
exit
adb reboot
FourOne82 said:
I don't know for sure, but since u have root it should be possible - pls somebody correct me if I'm wong with this.
Should work like this:
Code:
adb push xyzrecovery.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/xyzrecovery.img
dd if=/data/local/tmp/xyzrecovery.img of=/dev/block/mmcblk0p6
exit
exit
adb reboot
Click to expand...
Click to collapse
Would be very cool and easy if that should work . But no. The bootloader lock prevents any writing to and from the recovery and boot. So it shouldn't work.
There's a possibility to change rom. Because u can have root access, u can write the system,data and cache partitions. In theory we can boot our own kernel after the boot kernel. Boot a custom recovery from sdcard, backup the system, data and cache partitions and write a new rom to it. As long as the boot.img supports the rom we will be fine. But because we can simply unlock the device, (most of the time) nobody (I think) will ever try to get this working.
Well i tried Why Motorola has to lock the bootloader in first place, Smartphones like Samsung S3 are unlocked so its much easier for customers to flash custom-roms etc.
what is this xyzrecovery.img ?!? i dont seve such file into the phone
When You paste code from command line (to unlock bootloader) delete 4 spaces. It should fix Your problem.