I have an HTC One developer edition that I rooted with TWRP and then SuperSU. I left the stock ROM on as I only wanted the Xposed framework and MoDaCo toolkit installed. Now that the 4.3 update is out for the developer edition, how can I unroot the device to install it without completely flashing it? I've tried just flashing the stock recovery and the update wont install.
re-lock your bootloader again
"fastboot.exe oem lock"
double_ofour said:
re-lock your bootloader again
"fastboot.exe oem lock"
Click to expand...
Click to collapse
The update still fails after doing that.
You need to be 100% stock to flash it ideally, ie. stock ROM (no mods/changes), stock recovery, stock kernel
Related
Using the super tool, I managed to unlock bootloader, install superuser, and the modified cwm, but can't achieve Su permissions and can't flash Roms...
This is all after unbricking the device... Lol. I failed to properly install the android SDK tools, but proceeded to unlock bootloader, then flashed the holicakes kernel with the thought that it was a full Rom, lol... Needless to say, it was bricked... So I downloaded the HTC ics ruu and brought it back to stock. From there I re-unlocked the bootloader, flashed modified cwm, and installed superuser... Now what?
Installed su in recovery?
Sent from my HTC PH39100 using Tapatalk 2
Mr_Random said:
Using the super tool, I managed to unlock bootloader, install superuser, and the modified cwm, but can't achieve Su permissions and can't flash Roms...
This is all after unbricking the device... Lol. I failed to properly install the android SDK tools, but proceeded to unlock bootloader, then flashed the holicakes kernel with the thought that it was a full Rom, lol... Needless to say, it was bricked... So I downloaded the HTC ics ruu and brought it back to stock. From there I re-unlocked the bootloader, flashed modified cwm, and installed superuser... Now what?
Click to expand...
Click to collapse
If your goal is to flash a new modified rom then you can already proceed to do so with the unlocked bootloader and custom recovery. Your new modified ROM will have root access built in already. Just make sure when you flash a new ROM, you also flash the accompanying kernel (boot.img) as it is not flash automatically (unless you have already s-offed and the ROM chef has it written in his installation script) regardless it won't hurt to install the accompanying kernel just prior or after the ROM install.
Here is something important, if you are flashing ICS and you don't have the right bootloader, you have to get the new bootloader BEFORE flashing any ICS ROMs. You can do this by flashing the correct RUU with ICS (which requires you to relock and blah blah blah, but you already know this). Good luck with your flashing.
Thank you guys! I did install su from recovery, but I forgot that stock Roms still show as unrooted. I was hoping to just use flash image GUI to flash the kernel, boot into recovery, then Rom, but now I realize that without s-off/custom Rom, I need to use the supertool to flash the kernel.
However, supertool won't recognize the device when trying to push kernels... Should I check for and remove htc sync on the computer? Otherwise the right usb drivers and android SDK tools are present :-/
Also, when I go to flash the kernel for the Rom I choose, do I just unzip and pull the boot.img from within and replace the stock kernel in the supertool file? I've never successfully flashed an alternate kernel on to a device before, how do I know what is compatible?
If I ran the ruu, I should have the right bootloader, correct?
http://forum.xda-developers.com/showthread.php?t=1676787
How to ROOT Stock ICS
Root is working now, thanks! Now flash some custom rom's.
In the Xperia SP versions which don't allow bootloader unlocking (Bootloader unlock allowed: no) , does the phone not boot in fastboot mode? I can go to Flashtool mode but not to fastboot. Is this the reason why?
update:
I only got you question now.
It is true that fastboot doesn't work with locked bootloaders, and that Flashtool does work.
But that doesn't mean your custom rom or kernel you flash with flashboot will boot. It works for stock.
If you're at 4.1 there are ways to get root and CWM, I don't think there are easy ways to flashing custom rom or installing root or CWM from 4.3 unrooted without unblocking, getting back to 4.1 to get root on 4.3, or perfoming factory reset.
You may want this: http://forum.xda-developers.com/showthread.php?t=2649923
It's a very long way, but at least it works. You can get 4.3 rooted with recovery, but you must go back to 4.1.2 to run CWM once. That is for root; Recovery procedure includes factory resetting...
Hope you can get it working as you want... Locked bootloader really are nasty
Hi,
I've just done an OTA update to 6.09.401.5
My phone is 801n, S-OFF with locked bl. Hboot is 1.57.
After the OTA I had lost root, so I went on to recovery (stock) to sideload supersu.
Much to my surprise, I can't adb with the stock recovery.
Looking in device manager, it just shows up as mass storage device.
I've added the device ID to the google driver inf:
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
and forced the driver, which loaded fine. But adb devices still shows nothing.
Same thing when I force ADB Composite Device.
Also tried disabling and enabling USB debugging without any success.
Do you guys have a similar issue? Are your device ids the same as mine in recovery? ADB works?
Nemesis_00 said:
Hi,
I've just done an OTA update to 6.09.401.5
My phone is 801n, S-OFF with locked bl. Hboot is 1.57.
After the OTA I had lost root, so I went on to recovery (stock) to sideload supersu.
Much to my surprise, I can't adb with the stock recovery.
Looking in device manager, it just shows up as mass storage device.
I've added the device ID to the google driver inf:
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
and forced the driver, which loaded fine. But adb devices still shows nothing.
Same thing when I force ADB Composite Device.
Also tried disabling and enabling USB debugging without any success.
Do you guys have a similar issue? Are your device ids the same as mine in recovery? ADB works?
Click to expand...
Click to collapse
You can not sideload with stock recovery nor use adb commands. flash a custom recovery
alray said:
You can not sideload with stock recovery nor use adb commands. flash a custom recovery
Click to expand...
Click to collapse
That seems strange. It was a while ago, but i did root my 4.4.2 install somehow with the bootloader remaining locked (I didnt erase my phone), and keeping stock recovery. Since the BL is locked I probably didnt flash a custom recovery and then revert to stock.
I was pretty sure I just sideloaded it with stock recovery since my device is SOFF.
Are you certain it can't be done?
It's pretty stupid of me then, as I am not sure how I rooted it before then.
Nemesis_00 said:
That seems strange. It was a while ago, but i did root my 4.4.2 install somehow with the bootloader remaining locked (I didnt erase my phone), and keeping stock recovery. Since the BL is locked I probably didnt flash a custom recovery and then revert to stock.
I was pretty sure I just sideloaded it with stock recovery since my device is SOFF.
Are you certain it can't be done?
It's pretty stupid of me then, as I am not sure how I rooted it before then.
Click to expand...
Click to collapse
you can not use adb sideload with stock recovery.
if you don't want to wipe the phone by unlocking the bootloader using htcdev.com you can:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
do wait said above and then unlock bootloader from custom recovery using adb shell or guru bootloader reset tool.
alray said:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
unlock the bootloader with the s-off method and flash a custom recovery.
Click to expand...
Click to collapse
is masking firmware works ?
If this works then no one need htcdev I think it's not possible or can brick
For totally stock locked S On phone I take a same version firmware mix TWRP flashing you don't need htcdev or unlocked ?
How I can unlock with S Off & stock Recovery non root ?
yatindroid said:
is masking firmware works ?
Click to expand...
Click to collapse
with s-off you can flash a custom recovery with a locked bootloader, no risk. just pack the custom recovery image (renamed recovery.img) with an android-info.txt that match your phone info inside a firmware.zip file and flash it in ruu mode.
you can then use the guru bootloader reset tool to unlock your bootloader using the custom recovery or by using an adb shell from custom recovery
If this works then no one need htcdev I think it's not possible or can brick
Click to expand...
Click to collapse
This is not a magical way to unlock, you first need s-off. if the phone is s-on then htcdev is required.
For totally stock locked S On phone I take a same version firmware mix TWRP flashing you don't need htcdev or unlocked ?
Click to expand...
Click to collapse
will only work for s-off, you can not flash a firmware with twrp inside, you can only flash sigend firmware with s-on
How I can unlock with S Off & stock Recovery non root ?
Click to expand...
Click to collapse
you can't, you first need to flash custom recovery using a masked firmware.zip like said above or use htcdev. using the firmware method will not wipe the phone.
alray said:
you can not use adb sideload with stock recovery.
if you don't want to wipe the phone by unlocking the bootloader using htcdev.com you can:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
do wait said above and then unlock bootloader from custom recovery using adb shell or guru bootloader reset tool.
Click to expand...
Click to collapse
Well, im an idiot. That's probably what I did last time as well.
For some reason I remembered using sideload.
Flashed TWRP, installed SuperSU and back to stock recovery.
Thanks a bunch,
so say i upgrade my rooted htc one once the ota update becomes ready.. what happens? i dont want to end up with a bricked phone.. would it harm my phone in any way?
thaaaanxxx
monrokhoury said:
so say i upgrade my rooted htc one once the ota update becomes ready.. what happens? i dont want to end up with a bricked phone.. would it harm my phone in any way?
thaaaanxxx
Click to expand...
Click to collapse
An OTA update will not work on a rooted phone! For the OTA to work it needs stock recovery, stock rom and all of the files that it is attempting to update. If anything is missing then it will error out and return to your present setup.
and to complete what majmoz already said, if your rom is 100% stock, and you have flashed back your stock recovery, the phone will update fine but you will loose root. You'll need to flash a custom recovery after the OTA to re-root the rom.
Guys you're very helpful and i must thank you for that. i am on the official 4.4.3 rom so i just need to restore the stock recovery? how to do that? and will the current rooting method work on lollipop (and should i follow the same steps to install clockwork recovery)? Will the ota update relock the bootloader?
i'm sorry if i'm asking too many questions but i don't trust any other forum.
monrokhoury said:
Guys you're very helpful and i must thank you for that. i am on the official 4.4.3 rom so i just need to restore the stock recovery?
Click to expand...
Click to collapse
If you have not modified anything to your rom (Kernel is stock and always was, you have not deleted any /system files and you still have or restored all the content in /data/preload (wiped during bootloader unlock), so yes all you need to do is to flash back the stock recovery that match your version.
how to do that?
Click to expand...
Click to collapse
The same way you did to flash a custom recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
and will the current rooting method work on lollipop
Click to expand...
Click to collapse
Flash the latest supersu from a custom recovery. Version 2.37 and above should work on lollipop
and should i follow the same steps to install clockwork recovery
Click to expand...
Click to collapse
You always flash the recovery using the same commands, stock or custom, on all versions its always:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
Will the ota update relock the bootloader?
Click to expand...
Click to collapse
OTA updates will never affect the bootloader status (S-ON/S-OFF, LOCKED/UNLOCKED/RELOCKED)
If you have not modified anything to your rom (Kernel is stock and always was, you have not deleted any /system files and you still have or restored all the content in /data/preload (wiped during bootloader unlock), so yes all you need to do is to flash back the stock recovery that match your version.
Click to expand...
Click to collapse
So, if I did flash a custom kernel, and did uninstall system programs (but didn't flash a custom Rom), what are my options if I'd like to upgrade to lollipop?
Thanks!
Sent from my HTC One using XDA Free mobile app
I relocked my bootloader to update my firmware to 6.09.401.5 (S-ON) and everything worked smoothly. But now I can't unlock bootloader because seems like you are not supposed to relock it when you have TWRP installed. How can I fix this?
Nemesis Xanity said:
I relocked my bootloader to update my firmware to 6.09.401.5 (S-ON) and everything worked smoothly. But now I can't unlock bootloader because seems like you are not supposed to relock it when you have TWRP installed. How can I fix this?
Click to expand...
Click to collapse
only way is to flash the stock firmware to get stock recovery back on: https://www.androidfilehost.com/?fid=23622183712462447
never lock or re-lock with anything custom on the phone
Seanie280672 said:
only way is to flash the stock firmware to get stock recovery back on:
never lock or re-lock with anything custom on the phone
Click to expand...
Click to collapse
The firmware I flashed is the stock one.
I have ARHD installed if that helps.
Edit: I am an idiot, I just needed to unlock using htcdev. Everything solved now.
Nemesis Xanity said:
The firmware I flashed is the stock one.
I have ARHD installed if that helps.
Click to expand...
Click to collapse
you cant unlock the bootloader with TWRP installed, you have to have stock recovery to unlock using the unlock token you got from HTC Dev, you need to reflash stock firmware which will put stock recovery back on, dont do anything else after the flash until you've unlocked the bootloader, rom doesnt matter.