Related
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
yvesg said:
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
Click to expand...
Click to collapse
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
yvesg said:
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Click to expand...
Click to collapse
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
lucky 69 said:
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
Click to expand...
Click to collapse
I ashamed, but I didn't do the backup :-( .....
yvesg said:
I ashamed, but I didn't do the backup :-( .....
Click to expand...
Click to collapse
Try what Harry wrote.
harry_m said:
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
Click to expand...
Click to collapse
Hi,
Thanks a lot.
I'm now able to get root access and I'm about to flash the G1.
I thaught I replaced the SPL, but I'm not sure .... I've tried so much things since I have this phone (since last sunday) .....
Again, thank you for your help.
Yves
ooops,
"Installation aborted", during the apply of update.zip.
Now the phone is bricked.
I'm going to format my sdcard and retry the flash ....
Same error :
(No such file or directory)
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
Installation aborted.
redownload the rom
Spon4ik said:
redownload the rom
Click to expand...
Click to collapse
Meanwhile, I try with another rom and it seems to work ....
Thanks again for your help.
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
If you ask me ... the above mentioned error
Code:
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
has nothing to do with a wrong-signed rom!
SPL
yvesg said:
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
Click to expand...
Click to collapse
would this have to do with the SPL? similar to not being able to flash a EUR ROM on a USA phone .. you have to flash the HardSPL etc in order to switch ROMs
Or you could just gain root access manually the way those of us who had RC30 did...
You are may be right about the HardSPL.
When I try to flash it, (with Camera + Power), I get "not allow".
Yes, I'm a noob
so I got my Moto XOOM and rooted it with adb and flashed a new kernel and installed ROM Manager and got a new recovery in it and all that and it was smooth as butter. I'm not a fan of ROMs but the kernel does make a huge difference already. Now, I did that as soon as I took the XOOM outta the box so I had no data to lose when rooting...
I've had my N1 for about a year now, been using 1-click root exploits because I didn't feel like starting over and losing all data even though I can have backups I know... but just putting the settings back, losing high scores in games, etc... is annoying enough.
But I'm starting to think now's the time.
So:
1) Best backup solution to not lose anything? My last titanium backup is from about two month ago when I lost root after the Gingerbread OTA
2) does it still stay rooted now with gingerbread? basically adb --> fastboot oem unlock and that's it?
3) I've read the wiki and it's great but not "omg I'm such a noob" proof... so the steps:
- I backup my stuff
- Reboot in recovery
- from my PC, run the command in adb --> fastboot oem unlock
- yes
- my nexus one is now unlocked, rooted but is back to factory...
after that, get the 2.3.3 update zip file from XDA and flash that. flash a new kernel via kernel manager (which one you guys recommend for speed and stability without all the fuss?)
that's it, finito?
thanks if you respond!
A - there are exploits available for Gingerbread, so you don't need to unlock the bootloader (though don't let that stop you)...
http://forum.xda-developers.com/showpost.php?p=13090966&postcount=67
B - unlocking the bootloader doesn't give you root. You also have to install a custom recovery and flash the su zip to gain root...
C - flashing an update zip will probably cause you to lose root (unless it's a pre-rooted zip, in which case you would need a custom recovery to flash it)...
hmm so I skipped a step, after unlocking bootloader I need to do what exactly? (commands/links if possible!)
it seemed simpler on the xoom.... unless it's the same thing?
adb reboot bootloader
fastboot oem unlock (wait for reboot)
adb reboot bootloader
fastboot flash boot rootboot.img
fastboot reboot (wait for reboot)
adb remount
adb shell push su /system/bin
adb shell ln –s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
that's it? are the Nexus files different? (got a link?)
as for Gingerbreak, I kinda got sick of always waiting a long time for 1-click roots after each update. I will try to get it working (so far no go, gonna stick a blank sd in my phone and try that) just so I can do a full Titanium backup and maybe a recovery if possible
Gingerbreak worked - stuck a blank micro-sd, rooted, put my 16gb micro-sd back in - all is well
running full Titanium now...
Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.
Edit: nvm
Here is the dump. Thanks for your work.
KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?
I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.
Glad I could help. Now folks have less things to worry about when they decide to root
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.
efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).
For science
KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.
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
Hi!
I haven't found aboot.zip for my device. LG D405 v20a. Help anyone? Rooted but need to unlock to install TWRP and custom ROM.
You must have full rooted device. Install terminal from play and open it.
Type: su
(grant superuser permission)
then type:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.bin
VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
Then download Flashify and install latest version of TWRP.
Note: You must save aboot.bin file in root of your external sd card before execute command.
View attachment D405_v20a_patched_aboot.zip
Vule991 said:
You must have full rooted device. Install terminal from play and open it.
Type: su
(grant superuser permission)
then type:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.bin
VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
Then download Flashify and install latest version of TWRP.
Note: You must save aboot.bin file in root of your external sd card before execute command.
View attachment 3598855
Click to expand...
Click to collapse
Did everything as you said. Took the twrp.img file from here: http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
After installed from flashify I go boot to recovery and then I get LG logo with white text Secure Booting Error! Cause: boot certification verify and black screen. Nothing happens then and I have to take my battery out and then put it in to reboot and it loads back to stock rom normally. What is wrong?
J3R3MiN said:
Did everything as you said. Took the twrp.img file from here: http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
After installed from flashify I go boot to recovery and then I get LG logo with white text Secure Booting Error! Cause: boot certification verify and black screen. Nothing happens then and I have to take my battery out and then put it in to reboot and it loads back to stock rom normally. What is wrong?
Click to expand...
Click to collapse
Hm if you work step by step it should be all right and that you can enter into recovery. Try again download aboot.bin and then do the same. Maybe the file is corrupted when you downloaded to disk.
Vule991 said:
Hm if you work step by step it should be all right and that you can enter into recovery. Try again download aboot.bin and then do the same. Maybe the file is corrupted when you downloaded to disk.
Click to expand...
Click to collapse
OK I'll try again but what about this command? Is it the same or is it wrong?
su
dd if=/storage/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
J3R3MiN said:
OK I'll try again but what about this command? Is it the same or is it wrong?
su
dd if=/storage/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
Same, download file again and repeat operation.
Vule991 said:
Same, download file again and repeat operation.
Click to expand...
Click to collapse
Repeated all the steps, nothing. Same error. My su + code didn't work (couldn't find sdcard file) so I used yours again. Flashed again twrp image and rebooted to recovery through Flashify.
J3R3MiN said:
Repeated all the steps, nothing. Same error. My su + code didn't work (couldn't find sdcard file) so I used yours again. Flashed again twrp image and rebooted to recovery through Flashify.
Click to expand...
Click to collapse
What about this code? With the use of Minimal ADB and fastboot
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
EDIT: I GOT IT WORKING WITH THIS CODE THROUGH ADB CMD ON MY LAPTOP. THANK YOU FOR THE ABOOT FILE :angel: :highfive:
EDIT2: Had rooted Lollipop LG L90 D405 v20a for this to work.
J3R3MiN said:
What about this code? With the use of Minimal ADB and fastboot
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
EDIT: I GOT IT WORKING WITH THIS CODE THROUGH ADB CMD ON MY LAPTOP. THANK YOU FOR THE ABOOT FILE :angel: :highfive:
Click to expand...
Click to collapse
I still have the error:crying::crying:
I use this patch but still unlocked bootloader
l90 d405 v20a
J3R3MiN said:
What about this code? With the use of Minimal ADB and fastboot
I GOT IT WORKING WITH THIS CODE THROUGH ADB CMD ON MY LAPTOP. THANK YOU FOR THE ABOOT FILE :angel: :highfive:
Click to expand...
Click to collapse
I have D405n V20a, how can I unlock bootloader?
Worked for me! Thanks for the modified aboot.bin. I took the command from this Thread, and the aboot.bin from this current Thread. I executed the command over ADB shell after copying the aboot.bin to the sdcard, worked without any problems!
rueolps said:
Worked for me! Thanks for the modified aboot.bin. I took the command from this Thread, and the aboot.bin from this current Thread. I executed the command over ADB shell after copying the aboot.bin to the sdcard, worked without any problems!
Click to expand...
Click to collapse
I have D410n v20a so what should i download?
Mammolos98 said:
I have D410n v20a so what should i download?
Click to expand...
Click to collapse
Not this one, I guess...
rueolps said:
Worked for me! Thanks for the modified aboot.bin. I took the command from this Thread, and the aboot.bin from this current Thread. I executed the command over ADB shell after copying the aboot.bin to the sdcard, worked without any problems!
Click to expand...
Click to collapse
I did the same but my bootloader is still locked
Because the adb commands were executed fine I thought it worked and I tried to flash TWRP. Probably flashing was okay but no I cannot boot into recovery. I get an android lying on his back with an exclamation mark. And fastboot getvar all tells me the bootloader is not unlocked.
What can I do to repair my recovery and unlock the bootloader (v20a)?
Try it again. Remember: Even if you execute it over adb shell, you need to type "su" first. Afterwards you need to allow the root access of adb shell on your phone (if you have never used it before). You should get the "#" on adb shell now. Only now you are able to execute the copy of the aboot.bin. If it executes fine you should see something like "1 file copied" if I remember correctly.