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.
Rooted my developer edition successfully. I just used Fastboot to install TWRP recovery, then I flashed superuser.zip.
I did make a backup.
Questions :
How easy is it to unrooted and flash stock recovery?
Do I just restore my backup and Fastboot stock recovery? Where can I find it?
I see HTC released the RUU files for the developer edition to completely restore the device to factory settings, where can I find it on the htc website?
I'm having a slight issue with superuser, it freezes a bit when asking for root permissions, perhaps I should have used SuperSu instead, anyone else having similar issues? For example, I can't use Adaway, when it reboots to apply Host file changes, it just disables itself again, but Superuser has given it permission.
Thanks,
Sent from my HTC One using Tapatalk 4 Beta
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Check PM
sgiitk said:
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Click to expand...
Click to collapse
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
BUT remember you cannot root again, as over i am facing problems,,,
check : http://forum.xda-developers.com/showthread.php?t=2494594
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
[email protected] said:
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
Click to expand...
Click to collapse
It is Sprint, and from Hetal. Unrooting and relocking can be a pain, reloading everything. However, for almost two years I did not do any work on the Android side, so have forgotten everything.
I do not mind a locked phone it I can get to 4.3
Can you please pm me with the unrooting, relocking and the 4.3! Root for 4.3 is inevitable - just a matter of time.
Following the GooManager route I managed to get TWRP 2.6.3.0 installed, except the phone did not reboot. I did check it is 2.6.3.0.
Now the problem of the OTA remains. Maybe I will be forced to follow pm.mohanani's route of relocking. I cannot understand if I relock the bootloader then is not the unrooting automatic!
Also, Mr Mohanani GooManager requires root, so do not bother.
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
sgiitk said:
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
Click to expand...
Click to collapse
There is no need to accept the OTA if you are s-off
bigdaddy619 said:
There is no need to accept the OTA if you are s-off
Click to expand...
Click to collapse
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
sgiitk said:
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
Click to expand...
Click to collapse
Install TWRP 2.6.3.0
Option 1 flash SuperSU or another superuser file and run stock rooted
Option 2 flash a custom rom
Still stuck. I downloaded GooManager, and it will go into download > nowstarting and hang forever. I was advised to go the adb fastboot way, i.e.
download latestTWRP image filethen
adb reboot bootloader
then when I get
ui fstboot
fastboot flash recovery <twrp-recovery-name.img>
and its done.
I downloaded the .img file. Put everything into c:\recovery. Moved there under the command prompt. Plugged the phone into the computer, got both the drives (htc sync manager, and HTCONE) . So the connection was kosher.
Then gave adb reboot bootloader
The adb daemon started, but it found no device.
Obviously I being a noob in this game was missing something.
Also, I hear that the ROMs are available which to not reformat the storage. Are these the Deodexed versions or something.
Also, once in ten calls or so the screen goes totally blank at the end and is pain to restart the phone.
Checked up with http://forum.xda-developers.com/showthread.php?t=2497712
Seems that I am S-off but no rooted! Now what??
After a day or so and some cool thought I think I may have the problem identified. It is likely to be the lack of a root. I tried the following and the responses there from:
adb reboot bootloader
rebooted into bootloader Showing relocked and S-off. No fastboot option in the lower menu!
Now:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
I get
sending recovery <8600kB>...
Okay [ 1.140s]
writing 'recovery'...
FAILED <remote not allowed>
finished. total time 1.170s
Any ideas, and when may I expect root for 4.3. At the moment the phone appears to be working file, but no recovery!! HELP!!
Do I need to unlock again despite S-off. Also, then what is the bitstream I send it from 4.3 - the same as the old one!!
Yes you need to unlock your bootloader again to be able to flash twrp
I did as per the htc route - Do the unlock, reinstalled the OS, download the bitstream, etc, and then the OS reloaded. Still Goomanager could not get TWRP 2.6.3.0 so used the fastboot route and succeeded in downloading it to the phone. Thanks for encouraging me and putting me on the right track.
Now ho to root. Then I may as well get Titanium up!
You can get SuperSU or Superuser from the playstore or install a custom rom.
A very interesting experience. I could not enter bootloader [Down-vol + power was just restarting the phone], even adb devices was drawing a blank. So I decided to do a factory reset from phone. Lo and behold it dropped me into the TWRP screen. I managed to root, restarted to the main Downloaded su checker which completed the root. Confirmed. Then downloaded Titanium with Pro license (I have it) and did a recovery. Also, TWRP Manager (downloaded) is working and I am able to start into bootloader, etc.
When I try and look for upgrades with TWRP installer it says none. I know 2.6.3.0 has been upgraded to 2.6.3.2 Let sleeping dogs lie.
Also, I have not checked with adb devices but I am sure that too will now work.
Thanks, but what is going on. Is it only God and maybe Google know what happened?
Thanks for helping, and keeping me going.
I had more or less decided to revert to 4.1 and do an S-on <fastboot oem writesecureflag 3> and bootloader lock and look for OTA!
Added on 25th November
adb still not recognising the beast. adb devices gets a blank list. Phone is available under Windows so drivers etc are Ok.
A noob question. I saw
Stock Rooted 3.04.651.2 Odex & De-Odexed
Insecure Boot img. init.d support, data/app support
Stock Rooted 3.04.651.2 Odex
Stock Rooted 3.04.651.2 De-Odexed
on the upgrade thread. Now what do the terms Rootedm Odex and De-Odexed mean to the average user. Stock means the basic htc ROM I presume.
Also, rooted means what stages are covered.
afaik to upgrade you lock the bootloader, do the upgrade, and then in normal situations again unlock the bootloader, root and install a custom recovery (TWRP does the rooting - hopefully).
Do these ROMs take care of some or more of these stages?
I am aware that I can't get the ota with a custom recovery. when lollipop gets released, how to I update my phone? I want to use stock so that I have active notifications and voice control.
You need to reflash the stock firmware.
Flash the entire stock rom? Or just recovery?
Recovery, revert any framework mods, reinstall any uninstalled system apps, and unfreeze any system apps.
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
Now, i have a Noob Question, but I always had Samsung devices, they have no bootloader like the moto or htc.
I unlocked the bootloader, is it safe to update via OTA ?
thx
TLH11 said:
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
Now, i have a Noob Question, but I always had Samsung devices, they have no bootloader like the moto or htc.
I unlocked the bootloader, is it safe to update via OTA ?
thx
Click to expand...
Click to collapse
Pretty sure all android devices have some sort of bootloader.
Anyway, since your bootloader is unlocked, you shouldn't have a problem rooting.
JJHunterx said:
Pretty sure all android devices have some sort of bootloader.
Anyway, since your bootloader is unlocked, you shouldn't have a problem rooting.
Click to expand...
Click to collapse
What about the OTA for future lollipop?
TLH11 said:
What about the OTA for future lollipop?
Click to expand...
Click to collapse
If you have a custom recovery you wont be able to OTA. That simple.
...or just wait for someone to cook up a custom Lolipop or stock rooted ROM flashable via custom recovery.
JJHunterx said:
If you have a custom recovery you wont be able to OTA. That simple.
Click to expand...
Click to collapse
It will certainly flash via custom recovery. You just can't do an automatic update with custom recovery, where the system reboots itself and tries to update. If you manually download an OTA zip and flash it manually in recovery, it will work as long as all the file checks pass as I've done this several times on different devices.
Sent from my Moto X
TLH11 said:
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
Now, i have a Noob Question, but I always had Samsung devices, they have no bootloader like the moto or htc.
I unlocked the bootloader, is it safe to update via OTA ?
thx
Click to expand...
Click to collapse
For #2 you do not need to UNROOT in most cases. Using the older methods for locked bootloaders like SlapMyMoto/RockMyMoto and the like it was suggested to flash back to stock because of potential changes those processes make that could cause the OTA update's pre-flash validation checks fail.
For #6 it depends on how they are "Frozen." Apps "frozen" or disabled the same way that going Settings -> Apps -> {select the app} -> tap DISABLE button (or uninstall updates, then disable) will be fine and will not impact the OTA.
In the past freezing apps via Titanium Backup did cause problems, so it was suggested to unfreeze. However, more recent updates (like 4.4.2 to 4.4.4) did not encounter that problems, and those who froze apps with Titanium Backup didn't need to unfreeze.
If you have an 3rd party recovery on the device, when it goes to reboot and install the update, it will fail, and get the phone stuck in a boot loop.
When I've tried manually installing an OTA.ZIP in TWRP, it has errored. The only way for me to install was via stock recovery. That being said, I didn't try CWM or Philz.
As for Lollipop, you will be able to install and then flash custom recovery. As for rooting, there are changes in Lollipop, and it wont be confirmed until Lollipop hits a 2013 X, but in theory, due to the latest updates from Chainfire to SuperSU, we may be able to just flash TWRP, and install SuperSU like we did with KitKat.
I'm trying to install an OTA update to get to the newest version of android for my (Rogers) ONE M7.
I had:
- Unlocked the bootloader
- Flashed a custom recovery
- Flashed a custom kernel
- Installed Supersu and rooted phone
- BUT KEPT STOCK ROM
Phone worked wonderfully with no problems but slowly became dated (4.4.2)
My phone still received OTA's, after ignoring them for a while I would like to move to the newest available (5.1) for all the upgrades like ART.
I then:
- Flashed stock recovery (successfully)
- Flashed stock kernel (successfully)
- Relocked bootloader (successfully)
- But this is where the weirdness starts. I can't unroot, and thus the OTA fails.
I have tried:
- Full unroot using supersu
- Disabling super user
- Uninstall Supersu
- Deleting all .su, su, supersu.apk, busybox (which I suppose supersu installed?) and all other associated files using file explorer.
- Using apps like Universal Unroot.
The best I can do is temporarily remove root by using supersu full unroot, BUT UPON RESTART THE PHONE REINSTALLS SUPERSU AND ROOTS ITSELF. This has me completely stumped.
I then tried installing a ruu to wipe the root off my phone but the ruu always crashes at 5%... with windows telling me "htc_fastboot.exe stopped working".
I tired extracting the ruu and flashing it using fastboot but in that case the cmd window fails with "invalid sparse file format at header magi"
And yes, the MID, CID and carrier match up exactly for my phone and the ruu.
The only option I have left is to redo everything so I can flash an (updated) custom rom on my phone. But I want to stay on stock rom so I don't lose all my files. Which I wouldn't with an OTA, or when using HTC's awesome backup feature (which I'll lose with a custom rom). (As well as holding its resale value!)
Thanks for reading, if anyone know's how to get around this seemingly impossible problem please let me know!!
123ethan said:
I'm trying to install an OTA update to get to the newest version of android for my (Rogers) ONE M7.
I had:
- Unlocked the bootloader
- Flashed a custom recovery
- Flashed a custom kernel
- Installed Supersu and rooted phone
- BUT KEPT STOCK ROM
Phone worked wonderfully with no problems but slowly became dated (4.4.2)
My phone still received OTA's, after ignoring them for a while I would like to move to the newest available (5.1) for all the upgrades like ART.
I then:
- Flashed stock recovery (successfully)
- Flashed stock kernel (successfully)
- Relocked bootloader (successfully)
- But this is where the weirdness starts. I can't unroot, and thus the OTA fails.
I have tried:
- Full unroot using supersu
- Disabling super user
- Uninstall Supersu
- Deleting all .su, su, supersu.apk, busybox (which I suppose supersu installed?) and all other associated files using file explorer.
- Using apps like Universal Unroot.
The best I can do is temporarily remove root by using supersu full unroot, BUT UPON RESTART THE PHONE REINSTALLS SUPERSU AND ROOTS ITSELF. This has me completely stumped.
I then tried installing a ruu to wipe the root off my phone but the ruu always crashes at 5%... with windows telling me "htc_fastboot.exe stopped working".
I tired extracting the ruu and flashing it using fastboot but in that case the cmd window fails with "invalid sparse file format at header magi"
And yes, the MID, CID and carrier match up exactly for my phone and the ruu.
The only option I have left is to redo everything so I can flash an (updated) custom rom on my phone. But I want to stay on stock rom so I don't lose all my files. Which I wouldn't with an OTA, or when using HTC's awesome backup feature (which I'll lose with a custom rom). (As well as holding its resale value!)
Thanks for reading, if anyone know's how to get around this seemingly impossible problem please let me know!!
Click to expand...
Click to collapse
When your have problems flashing a RUU, just flash the Same version Firmware first then the RUU
also your PC needs all the C++ installed (2005 - 2008 - 2010 both x64 and x32 bit versions)