Is it possible to gain root (on an unlocked + S-OFF device), without flashing a custom recovery?
I've been searching for a couple of hours, but couldn't find a working solution.
The superboot method doesn't seem to be working, something to do with not being able to boot into an image from fastboot anymore (I'm on the latest firmware/hboot).
Any other methods available?
Thanks in advance.
totoguy said:
Is it possible to gain root (on an unlocked + S-OFF device), without flashing a custom recovery?
I've been searching for a couple of hours, but couldn't find a working solution.
The superboot method doesn't seem to be working, something to do with not being able to boot into an image from fastboot anymore (I'm on the latest firmware/hboot).
Any other methods available?
Thanks in advance.
Click to expand...
Click to collapse
If you want to use superboot then use an hBoot of 1.44. other then that you have to flash a custom recovery
These directions are based on Win7 pc...Assuming you have ADB, drivers and fastboot on your machine:
You need a recovery to use temporarily. Download (to your computer) the one you like and proceed:
Reboot phone to bootloader, enter fastboot
The next step temporarily boots your phone to a recovery. On a command prompt, CD to the directory where you downloaded the recovery image, then enter this:
fastboot boot "recovery.img"
You need to replace "recovery.img" with the file name of your choice that you downloaded: CWM or TWRP...also, do not use "quotes"
You should be in CWM or TWRP now.
Backup your phone with the recovery's nandroid...DO IT.
All you need to do is select the option to reboot. When you do, the recovery will ask you if you want to install root. Select "Yes" and you're basically done.
When you phone reboots, it will maintain the stock recovery and you'll have su in system/bin as well as the superuser apk in system/app. Now install busybox from the play store.
oophlamer said:
fastboot boot "recovery.img"
Click to expand...
Click to collapse
I've tried that with the superboot method, and it looks like it's not working anymore with the latest stock rom (or might be a 4.3 change). It just hangs and the phone freezes, until I hard reset with the power button.
I did another search now and it seems that the command might have been replaced with "fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img", at least on the Nexus 4.
I'll look into it when I get back home.
totoguy said:
I've tried that with the superboot method, and it looks like it's not working anymore with the latest stock rom (or might be a 4.3 change). It just hangs and the phone freezes, until I hard reset with the power button.
I did another search now and it seems that the command might have been replaced with "fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img", at least on the Nexus 4.
I'll look into it when I get back home.
Click to expand...
Click to collapse
"fastboot boot ..." no longer works as of hboot 1.54+, it used to work on hboot 1.44.
nkk71 said:
"fastboot boot ..." no longer works as of hboot 1.54+, it used to work on hboot 1.44.
Click to expand...
Click to collapse
Exactly what i was going to reply. I had tested this on my stock Hboot 1.54 to keep a 1:1 backup but failed miserably.
I have the same problem...
Any solution?
Related
I'm having a problem rooting my Nexus One (I have also read the newbie FAQ and searched the forum to no avail) - I have followed the instructions listed on the androidandme site.
When I try to unlock using fastboot I get this returned:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFOErasing userdata...
FAILED (status read failed (Too many links))
When I start the phone in fastboot mode it now says *** UNLOCKED *** at the top of the screen. I then flashed Amon-Ra's recovery image, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-
RA-nexus-v1.6.2.img
sending 'recovery' (3954 KB)... OKAY
writing 'recovery'... OKAY
I assumed everything was going to be fine despite the issues unlocking. On trying to boot into recovery mode all I get is a screen with an exclamation mark and the android robot.
On turning the phone on as usual it seems that I can not run "Root required" apps such as the N1 torch.
I have tried running the OEM unlock command again but it seems to think that it has worked, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFODevice was already unlocked!
OKAY
It would seem from the newbie guide that I still need to flash the recovery image but that seems to be going fine. I can't see that I've messed up so far so is there some way to "unroot" my phone or go through the OEM unlock process again?
Thanks.
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
I tried this, but still don't have root permissions - any thoughts?
I have read and searched and read some more and searched some more, and now just need some help...
Thanks in advance.
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
jongie123 said:
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
Click to expand...
Click to collapse
I suggest One thing. Pay 15.47 american Usd, at Online Kitchen for Modaco, Viola, Your done, always rooted.. Always Su'd up..
The Bootloader is simple on a windows machine, and so is root.. On Modaco's site there is a whole tutorial on this.. Plus search the threads, a whole ish load too..
i"d pay the 15.47.. Just Nike it, Just do it.. It's so much easier.. Just click-click, bake, download, flash, done..
Go..Go..!
jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
If you just need root, get 'superboot'. It needs to be flashed to the "boot" partition (after unlocking the bootloader).
What it does is copy the root files to the data ROM and sets up permissions the first time the phone is booted (runs some sort of script I guess).
Link to superboot (free), make sure you get the right version:
http://android.modaco.com/content/g...erd79-epe54b-superboot-rooting-the-nexus-one/
look up "get root back".... Try these commands via ADB:
adb remount
adb shell chmod 6755 /system/xbin/su
....This should "fix_permision" and get you root back, IF you ever had it....
papermonk said:
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
Click to expand...
Click to collapse
Using adb you can issue "adb reboot recovery" and wind up in recovery mode. You can also hold down the power button and trackball (connected or disconnected from the computer) and enter fastboot. From there, select bootloader and then recovery.
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
sadhuKashmir said:
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
Click to expand...
Click to collapse
If you are rooting a G1, correct me if I am wrong, but couldn't you just use one of the one click root methods?
I thought all of the patches denying one click root were contained in official FW's of GB and the G1 did not get it.
Hi everybody, I unlocked a N1 using fastboot and clockwork recovery. At the time to install the CM6 I encountered and error related to the version of de HBOOT.
I found a guide by Amritttt for reverting HBOOT to 0.33.0012, when I flashed PASSIMG following reboot the screen has become dead.
I tried to re-flash the phone with Amon_Ra recovery (1.8.1 and 2.0) but I can't enter in any mode. The only way I found is entering in the Bootloader and pushing files using fastboot... so I tried to restore the original system using the following:
PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed
Passion-VF-FRF91
with this method: uncompress, flash userdata, system and recovery.
But it did't work, in the last flash the phone hasn't the SIM inside and I realized that the trackball blincked in red two or three minutes after rebooting. So I am wondering if I have a SLCD N1 what can I do to solve this disaster??
thanks!
Look at my signature, go there, see "Unroot/restore your Nexus", reflash EVERYTHING - either with fastboot (and you need to reflash HBOOT too), or do the PASSIMG method - with FRG33, and then upgrade to FRG83.
actually ignore me, that wont work for s-on, yeah, u gunna have to go through the pass-img method, completely reverting back to stock and start from scratch
Thanks, I'll try. I can't use PASSIMG method because my screen ism't working, or there's other way to do?
When you say all, you refer to use "fastboot flash all FRG33" Doing that I reflash alse the HBOOT or I need to do something more?
Thanks
ptrigomou said:
Thanks, I'll try. I can't use PASSIMG method because my screen ism't working, or there's other way to do?
When you say all, you refer to use "fastboot flash all FRG33" Doing that I reflash alse the HBOOT or I need to do something more?
Thanks
Click to expand...
Click to collapse
Can you not get your working hboot.img
boot to fastboot by Powering off
Power on by holding power & Trackball (will take you directly to fastboot)
then do "fastboot flash hboot hboot.img"
bagofcrap24 said:
Can you not get your working hboot.img
boot to fastboot by Powering off
Power on by holding power & Trackball (will take you directly to fastboot)
then do "fastboot flash hboot hboot.img"
Click to expand...
Click to collapse
The hboot files i have are hbootxxxxxxxxx.nb0, it's ok?
bagofcrap24 said:
actually ignore me, that wont work for s-on, yeah, u gunna have to go through the pass-img method, completely reverting back to stock and start from scratch
Click to expand...
Click to collapse
Yeah, but my screen is not working, and ADB is not reconizing the phone. I only can send files using fastboot and the screen is not working
There is a method for doing the pass-img method using fastboot?
or maybe the only problem is the HBOOT?
OK, here we go
Download Latest Amon-Ra
http://forum.xda-developers.com/showthread.php?t=611829
copy it to your android-sdk/tools/ folder and rename recovery.img
boot to fastboot, (Power & Trackball)
open up a shell (cmd prompt) and
cd (path to sdk/tools)
fastboot devices (make sure your device is there)
fastboot boot recovery.img
your phone should boot into recovery image
use your method for flashing through adb now if you can
if you can't then try flashing the korean wwe update
hit enable usb-ms
download this, its a korean FRF91 build. it is known to have the updated 0.35.0017 Hoot in it which i believe has support for slcd displays, http://forum.xda-developers.com/showthread.php?t=722281
copy to your SD
hit trackball to disable usb-ms, go to wipe, wipe all data
then goto flash image from zip,
choose the korean frf91 that you just downloaded hopefully when you reboot you will have updated your hboot again
i tried the baove method but i cannot get the recovery .......i have the same problem my display is dead !! i have gone into recovery but i cant see it and hence cant do a wipe and flash the zip can nyone please help me!!!!
Jack gave you the response you need.
Follow the unroot/restore guide from the wiki, using the PASSIMG method:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
The long to the files is on the word "here" on step 2. Use FRG33.
This is done from the bootloader - you don't need to use recovery...
Sent from my Nexus One using XDA App
actualy i cant see anything cant see fastboot menu nor the bootloader! so i will not be able to do from step 2...please can nyone tell me wad to do?? is my fone bricked?? do i have to giv it to htc??
Its HBOOT, not recovery.
Rusty! said:
Its HBOOT, not recovery.
Click to expand...
Click to collapse
What's HBOOT, not recovery?
Sent from my Nexus One using XDA App
I want to return to stock Ive messed a few things up. Is there a RUU for 1.31?
?
Yeah, I second that request...
Reading through the forums, there isn't one released yet.
tbrad413 said:
I want to return to stock Ive messed a few things up. Is there a RUU for 1.31?
Click to expand...
Click to collapse
I realize this post is hard to follow and all over the place, but I'm tired.
Without a RUU:
Have ADB drivers ready to go if you don't already.
First be sure the bootloader is unlocked via HTCDev.
Next, get a copy of both TWRP and CWM recoveries, you can read why both at the end of the post.
Download the stock rom/stock rooted rom from the thread in development.
Plug the phone into USB and copy the rom onto the phone. Will most likely need to be in a folder called "0" in the root folder.
Open a shell and navigate to your copies of fastboot and adb from the HTCDev unlock.
"adb reboot-bootloader" "fastboot flash recovery TWRP.img"
This will flash TWRP, make sure that you change TWRP.img to the actual file name.
If TWRP doesn't work (like mine didn't), no big deal. Issue the following commands:
"adb reboot-bootloader" "fastboot flash recovery CWM.img"
This will flash clockwork mod recovery, which worked better for me than TWRP.
After you figure out which recovery you want, wipe data/factory reset.
Navigate to 0 and select the stock rom that you downloaded.
One of the recoveries will only see the "0" folder, it's a bug. I believe if you're on TWRP, you can only access 0 which is why you need to put the rom there. Clockworkmod should be able to see anything, but if I remember correctly immediately reboots with the latest firmware.
Flash the room and reboot.
That's how you can go back to stock without a RUU. All of this is from memory but it's accurate. The other option would be to S-OFF via revone and downgrade afterwards. You CAN use revone on the newest firmware - I did it earlier.
Good luck and all that jazz.
Why both recoveries:
TWRP ****ed up really hard on 1.29.x for me and failed to flash or see any files. CWM worked for me on 1.29.x but instantly reboots on 1.31.x. TWRP works for me on 1.31.x but can only see within /sdcard/0/, meaning nothing outside that 0 folder is flashable.
Other notes:
There's also some **** about USB-OTG but I didn't mess around with that. I've been working with multiple Ones over the passed few days and the steps above worked for me. I realize this post is hard to follow and all over the place, but this is all I've been doing this past week and I've got a lot of info on it.
Another note:
If you don't have a working install on the phone to boot into, you can do what I did and boot into the bootloader and use
adb push file.zip /sdcard/0/
Then boot into the recovery and it should be installable.
Hi guys. I recently flashed a boot image via the Flashify app, which had worked in the past. After it flashed, I chose to reboot. Now my phone boots to the bootloader. I can't get fastboot to recognize my device on any PC (which is why I was trying another hboot). I can boot into recovery (cwm touch for now) but restoring roms etc. fails due to "no files found". ADB detects the phone in recovery. Can I repair my phone via adb without fastboot? I had a recent cwm and titanium backup on my sd card.
xpurtwitness said:
Hi guys. I recently flashed a boot image via the Flashify app, which had worked in the past. After it flashed, I chose to reboot. Now my phone boots to the bootloader. I can't get fastboot to recognize my device on any PC (which is why I was trying another hboot). I can boot into recovery (cwm touch for now) but restoring roms etc. fails due to "no files found". ADB detects the phone in recovery. Can I repair my phone via adb without fastboot? I had a recent cwm and titanium backup on my sd card.
Click to expand...
Click to collapse
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.
alray said:
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.
Click to expand...
Click to collapse
I am stuck in the same boat - I can't use fastboot., but I need it to flash a new recovery before updating to cm11. I don't have access to any Win7 computers to use, only have Win8.1. Are there updated drivers for the HTC One yet? Or any way to get fastboot working properly on Win8.1?
Artemicion said:
I am stuck in the same boat - I can't use fastboot., but I need it to flash a new recovery before updating to cm11. I don't have access to any Win7 computers to use, only have Win8.1. Are there updated drivers for the HTC One yet? Or any way to get fastboot working properly on Win8.1?
Click to expand...
Click to collapse
windows 8.1 doesnt work with early hboot version like 1.44 and if irc 1.54.
if you can't access another computer, use a live cd of ubuntu 12.04 32bit (no installation required, only boot from the disc or from a bootalb usb drive) and use fastboot from there.
alray said:
windows 8.1 doesnt work with early hboot version like 1.44 and if irc 1.54.
if you can't access another computer, use a live cd of ubuntu 12.04 32bit (no installation required, only boot from the disc or from a bootalb usb drive) and use fastboot from there.
Click to expand...
Click to collapse
So is it possible to upgrade my hboot to 1.55 (currently 1.54)?
EDIT: Ok, actually, examining things, it looks like this should work:
a) Go to Ubuntu for fastboot, flash new recovery
b) Back to windows, into recovery, wipe everything, push ROM over using adb, clean install of cm11
c) new cm ROM will include updated hboot so fastboot will now work in Win8.1
....that seem logical/like it should work to you? Thanks
Artemicion said:
So is it possible to upgrade my hboot to 1.55 (currently 1.54)?
Click to expand...
Click to collapse
yes, via fastboot :laugh:
EDIT: Ok, actually, examining things, it looks like this should work:
a) Go to Ubuntu for fastboot, flash new recovery
b) Back to windows, into recovery, wipe everything, push ROM over using adb, clean install of cm11
c) new cm ROM will include updated hboot so fastboot will now work in Win8.1
....that seem logical/like it should work to you? Thank
Click to expand...
Click to collapse
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)
alray said:
yes, via fastboot :laugh:
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)
Click to expand...
Click to collapse
Wow, ok, I think that sounds like far too much effort to just update my phone. Guess I'll use the ubuntu fastboot trick once, then just hope I never need to flash anything from fastboot again on this phone. Why is it always such an effort with these damn things? Thanks for the help, won't have a chance to try this for a couple of days but doubtless I'll be back with some other failed horror scenario then.
alray said:
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.
Click to expand...
Click to collapse
Yeah, that's pretty much the extent of what I knew, but I really appreciate your response. I did manage to get my old Win7 laptop running and with some effort got all the drivers working. I used htc1guru reset, but sadly I did lose the entire contents of my SD, despite its message that nothing would be touched. :-/ Luckily, most photos were auto-backed up by G+ and it's just a few settings and such that I can't get back or figure out. Least of my concerns after having a functional phone!
alray said:
yes, via fastboot :laugh:
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)
Click to expand...
Click to collapse
Hey, so I'm trying to do this, have got linux up and running and fastboot recognizes the phone, but I couldn't flash the recovery image as the terminal couldn't see it. What location does it need to be in within linux? I put it on the root of the usb drive and it wouldn't work from there...
Artemicion said:
Hey, so I'm trying to do this, have got linux up and running and fastboot recognizes the phone, but I couldn't flash the recovery image as the terminal couldn't see it. What location does it need to be in within linux? I put it on the root of the usb drive and it wouldn't work from there...
Click to expand...
Click to collapse
the answer is always the same, in the same folder you have adb in.
so in ubuntu it should be androidsdk/platform-tools/
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!
nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?
fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem
rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?
rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.