Database Develop

[Q] Problems with OTA Upgrade

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?

[SOLVED] SuperSU and Re-root on 4.4.2

Hey everyone
I've recently solved my OTA problem (seen here) but I soon discovered yet another problem.
When I tried to enter SuperSU, I received the following error shown below.
As mentioned before, I'm on 4.4.2 and I have NO desire whatsoever to unlock my bootloader all over again. Is there anyway to re-root my phone without unlocking my bootloader or will I need to do just that in order to re-root?
Thanks in advance

Anyone?

Please help :crying:

ArmyMan007 said:
Please help :crying:
Click to expand...
Click to collapse
From what I know, and by the error displayed on the attached screenshot, you need to do the whole rutine all over again. I am pretty sure rooting can not be done if bootloader is locked, which might mean you have a stock recovery image as well - and since that is not keen to be rooted (as far as I know) you need to flash a custom recovery like twrp. I might be wrong in all this, I'm newish to all this.

ArmyMan007 said:
Hey everyone
I've recently solved my OTA problem (seen here) but I soon discovered yet another problem.
When I tried to enter SuperSU, I received the following error shown below.
As mentioned before, I'm on 4.4.2 and I have NO desire whatsoever to unlock my bootloader all over again. Is there anyway to re-root my phone without unlocking my bootloader or will I need to do just that in order to re-root?
Thanks in advance
Click to expand...
Click to collapse
Since you are S-ON you can not flash a custom recovery or root without unlocking your bootloader.

Frogger209 said:
From what I know, and by the error displayed on the attached screenshot, you need to do the whole rutine all over again. I am pretty sure rooting can not be done if bootloader is locked, which might mean you have a stock recovery image as well - and since that is not keen to be rooted (as far as I know) you need to flash a custom recovery like twrp. I might be wrong in all this, I'm newish to all this.
Click to expand...
Click to collapse
Well, for starters, my bootloader is unlocked (as mentioned before), thus we eliminate the bootloader unlocking dilemma. But it still doesn't tell me how can I re-root my device: you want to tell me that I have to do is to flash a custom recovery and install SuperSU again, and my phone will be rooted again?

majmoz said:
Since you are S-ON you can not flash a custom recovery or root without unlocking your bootloader.
Click to expand...
Click to collapse
Like I wrote before: I DO have an unlocked bootloader

ArmyMan007 said:
Well, for starters, my bootloader is unlocked (as mentioned before), thus we eliminate the bootloader unlocking dilemma. But it still doesn't tell me how can I re-root my device: you want to tell me that I have to do is to flash a custom recovery and install SuperSU again, and my phone will be rooted again?
Click to expand...
Click to collapse
flash twrp 2.6.3.3. boot in recovery then exit, twrp will prompt you to root the phone. Then yo ucan flash back the stock recovery for future ota updates.

alray said:
flash twrp 2.6.3.3. boot in recovery then exit, twrp will prompt you to root the phone. Then yo ucan flash back the stock recovery for future ota updates.
Click to expand...
Click to collapse
Why can't I flash twrp 2.7.1.0? and don't I need to install SuperSU via twrp? and what do you mean that twrp will promote me to root the phone? it never did that before..

ArmyMan007 said:
Why can't I flash twrp 2.7.1.0?
Click to expand...
Click to collapse
latest known bug free version of twrp is 2.6.3.3/.4 thats why we always recommend using this version.
and don't I need to install SuperSU via twrp? and what do you mean that twrp will promote me to root the phone? it never did that before..
Click to expand...
Click to collapse
that is for the M8 but same thing apply for the M7:
http://www.youtube.com/watch?v=bKGKlkJRroQ#t=122
or flash the latest su binary from twrp

alray said:
latest known bug free version of twrp is 2.6.3.3/.4 thats why we always recommend using this version.
that is for the M8 but same thing apply for the M7:
http://www.youtube.com/watch?v=bKGKlkJRroQ#t=122
or flash the latest su binary from twrp
Click to expand...
Click to collapse
I used to install the latest binary within twrp and it never asked me to do so. Now I got root access again Can I flash my stock recovery again?

ArmyMan007 said:
I used to install the latest binary within twrp and it never asked me to do so. Now I got root access again Can I flash my stock recovery again?
Click to expand...
Click to collapse
yes you can flash your stock recovery again, might be a good idea to do a nandroid backup of your current config before flashing back the stock recovery.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot

alray said:
yes you can flash your stock recovery again, might be a good idea to do a nandroid backup of your current config before flashing back the stock recovery.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Will do! Thanks a bunch!!!

Issue rooting with unified rooting tool

Having an issue with the unified rooting tool (http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053). Paid for the pro version because i enjoy supporting quality work.
Went to do the all-in-one unlock/recovery/root, however it's not rooting for me. The final step of rooting gets stuck in TWRP and nothing happens. The program says 'Recovery mode not detected' and just hangs asking me to try again, ask for help, or abort.
I have ADB and everything on and working as unified can connect to my phone, just can't get root going.
The phone is now unlocked with TWRP, but I can't achieve root. I flashed 5.0.1 via the app. Anyone have any clues?
edit: did it manually (before reading simms22's post). was hoping for lazy-automated as i paid money for the app and all.

If you have twrp installed just flash SuperSU. The newest version of SuperSU (2.37 or something I think) can be flashed like old days.

lol, learn to root a nexus the right way. its easier than using a toolkit..
1. fastboot oem unlock
2. fastboot flash yourself a recovery
3. flash the latest supersu with that new recovery
4. reboot and profit
root

Looking to Root - running marshmellow stock

Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.

ccf60 said:
Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.
Click to expand...
Click to collapse
rooting marshmallow..
1. unlock the bootloader(yours is there already)
2. fastboot flash twrp recovery.
3. flash the latest supersu in twrp recovery
4. flash a custom marshmallow kernel, any. this ones new for marshmallow, and is needed.
5. boot up.

simms22 said:
rooting marshmallow..
1. unlock the bootloader(yours is there already)
2. fastboot flash twrp recovery.
3. flash the latest supersu in twrp recovery
4. flash a custom marshmallow kernel, any. this ones new for marshmallow, and is needed.
5. boot up.
Click to expand...
Click to collapse
Thank you.

ccf60 said:
Just had a problem after using root toolkit to attempt root on nexus 6 with marshmellow. (6.0 ), build MRA58R. After this attempt, got the message that" device is corrupted" and would not boot into system. Luckily bootloader was still unlocked and was able to flash stock image. Phone boots fine now with Boatloader unlcocked, and TWRP is gone, with no root. How do I root from here and install TWRP again without going through what happened before.
In the beginners guide to root, Chanifire's link hasn't been working and I want to be sure I do this right to avoid what happened with the toolkit. Also, my phone is setup with apps and data, and I dont't want to loose my setup.
Thanks for your help.
Click to expand...
Click to collapse
how did you manage to flash stock again after corrupt. mine wont recognize adb while corrupt. please give step by step
nvm. i got it finally

You don't flash with adb, but with fastboot.
The steps are:
1. Turn on phone with pressing vol down and power.
Sent from my Nexus 6 running cyosp using Tapatalk

No boot after flashing supersu. Attempting stock rooted.

So I followed a guide off of YouTube on how to root this phone. The steps were simply put use fastboot to enable oem unlocking. Use adb to push twrp. Use twrp to flash supersu walla you have rooted stock rom. I attempted this and got stuck after flashing supersu. The rom would not boot. I let it sit for 15 mins. Held the power button let it try again. Again it didn't boot. So I fiddled with it trying to figure out how to get stock rooted and wasnt able to. I could flash a stock image in twrp and it would boot. But as soon as I flashed supersu it would no longer boot. I read somewhere I needed a different supersu so I tried that one. Just asking simply how can I achieve stocked rooted. I also don't understand the encryption thing this phone has. Apparently you have to delete a partition to get rid of it but at boot it will just encrypt again. Any information on that would be greatly appreciated. Sorry for any spelling or grammar mistakes. Writing this out over my lunch break.

jakeneal22 said:
So I followed a guide off of YouTube on how to root this phone. The steps were simply put use fastboot to enable oem unlocking. Use adb to push twrp. Use twrp to flash supersu walla you have rooted stock rom. I attempted this and got stuck after flashing supersu. The rom would not boot. I let it sit for 15 mins. Held the power button let it try again. Again it didn't boot. So I fiddled with it trying to figure out how to get stock rooted and wasnt able to. I could flash a stock image in twrp and it would boot. But as soon as I flashed supersu it would no longer boot. I read somewhere I needed a different supersu so I tried that one. Just asking simply how can I achieve stocked rooted. I also don't understand the encryption thing this phone has. Apparently you have to delete a partition to get rid of it but at boot it will just encrypt again. Any information on that would be greatly appreciated. Sorry for any spelling or grammar mistakes. Writing this out over my lunch break.
Click to expand...
Click to collapse
I always use this toolkit: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
So far it worked flawlesly and saved me trouble.

jakeneal22 said:
So I followed a guide off of YouTube on how to root this phone. The steps were simply put use fastboot to enable oem unlocking. Use adb to push twrp. Use twrp to flash supersu walla you have rooted stock rom. I attempted this and got stuck after flashing supersu. The rom would not boot. I let it sit for 15 mins. Held the power button let it try again. Again it didn't boot. So I fiddled with it trying to figure out how to get stock rooted and wasnt able to. I could flash a stock image in twrp and it would boot. But as soon as I flashed supersu it would no longer boot. I read somewhere I needed a different supersu so I tried that one. Just asking simply how can I achieve stocked rooted. I also don't understand the encryption thing this phone has. Apparently you have to delete a partition to get rid of it but at boot it will just encrypt again. Any information on that would be greatly appreciated. Sorry for any spelling or grammar mistakes. Writing this out over my lunch break.
Click to expand...
Click to collapse
What version of supersu you installed, and on what version of system you were ?

I was on the latest official version of both as of yesterday. I will try the toolkit when I get home. With this toolkit are you able to root the new 7.1? I tried that out and liked it when attempting to get back to stock. Ultimately the goal is the newest software one plus has to offer with root, snapchat working, and a custom kernel set for better battery life.

You probably flashed an older version of SuperSU, which will cause endless boot animation. The SuperSU included in the toolkit should be the latest stable version. Alternatively, you could root with Magisk, which I have personally found to be easier to install (not as many branched versions) and use. Magisk is not the same as SuperSU, but they both result in the same outcome - systemless root. It's also easier to hide root from other apps (such as Snapchat) using Magisk through the Magisk Manager app. You can find out more about it here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Toolkit worked perfectly for me. I flashed the latest beta directly from one plus and installed snapchat and logged in. Used the toolkit to root and install franco kernel. Moderator please close this thread.

Are there any issues using adb backup to babkup all apps and restore after unlocking the bootloader? Or is there any better way to backup apps?