Related
When I tried the new OTA with a new Incredible I got off of eBay (not rooted or tampered with) it kept messing up half way through and causing my phone to constantly reboot. I restored my phone but when I leave it plugged in with 3G on the OTA messes up my phone again.
I don't have root access so ES Explorer can't delete the .zip in the security folder to stop the OTA.
I've been trying to downgrade the HBOOT and get it to 2.3.3 but it won't work.
I either want it to be full stock or gain S-OFF so I can put CM9 on there. I have HBOOT .98 and can't get it to downgrade.
So, I tried following the following:
http://forum.xda-developers.com/showthread.php?t=1298990
Everything worked fine up until near the end. It says "remote: 99 unknown fail". (SEE 1ST IMAGE)
*NOTE, ERASING CACHE WILL WORK. JUST DIDN'T THIS TIME. I'VE TRIED THIS SUCCESSFULLY UP UNTIL THE REMOTE 99 FAIL*
http://www.youtube.com/watch?featur...v=CgIYFGcVimU&annotation_id=annotation_395071
It's still 2.3.4, Sense 2.1.
My phone is Unlocked but still S-ON. I can't get rid of S-ON no matter what I try and do.
See 2nd image for what my HBOOT looks like.
Can anyone tell me what I'm doing wrong and what steps I need to follow at this point?
Also, can I flash CM9 and delete bloatware even with S-ON?
Thanks!
Someone correct me if I'm wrong, but it seems like the phone was unlocked through the HTC Dev Unlock tool. Have you tried relocking using that?
Sent from my Incredible 2 using xda app-developers app
To my knowledge I didn't use that. Just what is listed on these links.
Where can iI find this program and try to relock?
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
I cant boot back into the phone.
---------- Post added at 03:10 AM ---------- Previous post was at 02:43 AM ----------
I locked the bootloader and now it just will not boot into the phone. I tried to go into recovery but it just reboots.
Did I just mess up my phone?
sjpritch25 said:
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
Click to expand...
Click to collapse
Thank you! I actually decided to stick with stock. The new OTA actually worked this time around so I have no issues. IF ICS ends up never coming out, I'll eventually root. I really enjoy Cyanogenmod but for now stock feels safe for me.
You have no idea how much I truly appreciate this. I've been frustrated for a week. Searching all over the internet and doing everything in my power to fix it. All it took.. was that! THANK YOU!
Your welcome...
Now I have no stock recovery. It's a phone image and a red exclamation point. It then boots e3 and says something like "E: can't open cache/recovery/command"
How can I regain stock recovery?
Sent from my ADR6350 using xda app-developers app
Download the gingerbread RUU located http://minus.com/mvivow#1
I recommend renaming before downloading it.
rename it PG32IMG
Be careful with windows because it might rename it as PG32IMG.zip.zip. It won't work.
Move it to the sdcard
reboot into bootloader and allow the update. Its a signed RUU, so it should work.
It says "Main Version is older! Update fail"
Is there a RUU yet for the latest 6.xxxx OTA version?
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked again and could use recovery, which is what I'm doing right now.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
It would be less confusing if you used the same user name on all the forums you post on.
undergone said:
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked the phone again and can now use Recovery. I will stay like this I suppose.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
Click to expand...
Click to collapse
Sorry dude.
Here's what is happening now... let me re-clarify.
So I had several issues caused by the latest INC 2 OTA. After the OTA messed up my phone I followed several threads online to downgrade to 2.3.3. After I did this, I updated back to 2.3.4 and then did the new OTA. It worked.
When I did this, "recovery" disappeared in the bootloader.
I eventually unlocked my phone again and was able to flash a custom recovery.img to get clockwork mod recovery back on. Everything was going smoothly!
I then entered recovery and accidentally restored a previous backup (version 5.xxxxx which would power off due to the OTA messing it up). So I immediately did a factory reset.
After this, the Radio is 1.09.01.0312. Every time I boot up it gets stuck on the white HTC screen. I've tried clearing cache, formatting system and then doing a factory reset. It still is the same.
To my knowledge this current radio is the radio for the new OTA (6.xxxxxx). My phone thinks it's software is still 5.xxxxxx due to the accidental restore.
I guess the radio I need ends in .1111. Would not having this radio cause this issue? I downloaded the radio but it says I have to be S-OFF to install it.
I am currently unlocked and S-ON.
Am I screwed or is there anything I can do to fix this?
I can only Fastboot and use CMD prompts. I don't even care if it's a custom rom at this point. Anything I can do to restore the phone.
Please and thank you.
EDIT: Also, PG32IMG files will not work. If I go to manually install it says E: Can't open sdcard/PG32IMG.zip (BAD)
Nor will it go through when I boot it up in the bootloader. I tried this for the version 5.xxxxxx. Do I need to wait for a 6.xxxxxx officiall RUU PG32IMG to come out? I haven't seen one yet.
when you see the red exclamation point press power button and volume up at same time, will put you in stock recovery
Is there ANYONE that can possibly help be fix my phone? I'm still stuck in the white HTC boot screen.
I can only load up in the bootloader.
***UNLOCKED***
VIVO_W XB SHIP S-ON RL
RADIO-01.09.01.0312
eMMC-boot
I need to install the latest software. Is there a RUU yet for the latest 6.xxxx software yet as a PG32IMG?
Any steps to successfully do this would be appreciated.
Could someone with the stock software do a backup, zip the file and send it to me? that way I could put it in the sd/clockworkrecovery/backup and try to make it work.
Thank you.
EDIT: ***HERE IS THE FIX THAT WORKED FOR ME***
Here is how I fixed it: I suggest all others with my issue try this...
Flash the boot.img from this rom: http://forum.xda-developers.com/showthread.php?t=1737494
THEN went into recovery > factory reset > clear cache > wipe dalvik > install zip from SD > install
If you need addition details, how to flash, etc. they can be found here (http://forum.xda-developers.com/showthread.php?p=28262673#post28262673) where I was also given help.
I'm user "telecastertunes" on there.
Good luck!
Hi,
I have rooted my phone ,s-off etc, and I have TWRP.
I am unable to install the update, phone goes to recovery, stops there.
Is there anyway I can download the update and flash it manually , or do i have to go back to stock recovery?
thanks
leonzon said:
Hi,
I have rooted my phone ,s-off etc, and I have TWRP.
I am unable to install the update, phone goes to recovery, stops there.
Is there anyway I can download the update and flash it manually , or do i have to go back to stock recovery?
thanks
Click to expand...
Click to collapse
I'm not an expert . But I think you can't flash stock Rom from custom recovery. You must do it with Adb commands or what they like to call flash in fastboot mode. And for getting official firmware updates from HTC you need to setup stock recovery. I dunno but you may have to lock boot loader and S-ON too. But not sure. As I said, I'm not an expert
leonzon said:
Hi,
I have rooted my phone ,s-off etc, and I have TWRP.
I am unable to install the update, phone goes to recovery, stops there.
Is there anyway I can download the update and flash it manually , or do i have to go back to stock recovery?
thanks
Click to expand...
Click to collapse
You need a stock recovery to do OTA updates, won't work with custom recovery.
COLLECTION of Stock Backups See if you can find your stock recovery in that thread. Flash it and then you should be good to go.
---------- Post added at 06:57 PM ---------- Previous post was at 06:46 PM ----------
Saikat.mondol1 said:
I'm not an expert . But I think you can't flash stock Rom from custom recovery. You must do it with Adb commands or what they like to call flash in fastboot mode. And for getting official firmware updates from HTC you need to setup stock recovery. I dunno but you may have to lock boot loader and S-ON too. But not sure. As I said, I'm not an expert
Click to expand...
Click to collapse
No, if he's S-OFF there is no need to lock bootloader or to go S-ON.
He can just download the recovery stock .img file and flash it through command prompt. When he's done and the phone restarted he should get the OTA update.
Only issue he might run into, if he's rooted he'll lose root access and will have to reroot, it happened to me, but it's not a major issue though.
BerndM14 said:
You need a stock recovery to do OTA updates, won't work with custom recovery.
COLLECTION of Stock Backups See if you can find your stock recovery in that thread. Flash it and then you should be good to go.
---------- Post added at 06:57 PM ---------- Previous post was at 06:46 PM ----------
No, if he's S-OFF there is no need to lock bootloader or to go S-ON.
He can just download the recovery stock .img file and flash it through command prompt. When he's done and the phone restarted he should get the OTA update.
Only issue he might run into, if he's rooted he'll lose root access and will have to reroot, it happened to me, but it's not a major issue though.
Click to expand...
Click to collapse
Thanks for the basic outline. Would you be willing to give step by step instructions? I always get nervous when I have to do multiple flashing, rerooting, etc. . .
Michael833 said:
Thanks for the basic outline. Would you be willing to give step by step instructions? I always get nervous when I have to do multiple flashing, rerooting, etc. . .
Click to expand...
Click to collapse
Instructions for? To flash back stock recovery?
1. Download the recovery from the link provided (Make sure it's the correct recovery, correct base number etc)
2. Place the downloaded recovery .img file in the adb folder where fastboot.exe is (by default it'll be in the platform-tools folder) - Though if you did a custom recovery you're probably already familiar with this.
3. Hold shift and right click anywhere in the white area of the folder > go to "open command prompt/window here"
4. Plug usb cable into device and connect up to computer (All familiar surely if you did custom recovery)
5. Commands:
a) adb devices ... to check if device is connected, should see serial number of device.
b) adb reboot bootloader
c) fastboot flash recovery name_of_recovery.img
d) fastboot reboot
Done.
Once the device restarted you should get the prompt for the OTA update(Depending on settings of course), you can then do OTA update.
To get mainversion number for the recovery you need. Just go to software information(in settings menu > about > software information) and check for OS version number or connect device to computer, reboot into bootloader adb reboot bootloader then type fastboot getvar version-main to see main version for device.
BerndM14 said:
No, if he's S-OFF there is no need to lock bootloader or to go S-ON.
He can just download the recovery stock .img file and flash it through command prompt. When he's done and the phone restarted he should get the OTA update.
Only issue he might run into, if he's rooted he'll lose root access and will have to reroot, it happened to me, but it's not a major issue though.
Click to expand...
Click to collapse
Actually, I forgot that. I need to lock boot loader if I'm S-ON but don't need if S-Off
I have a Htc One M8 ; s-off, hboot 3.16, running 4.4.2. CID is Roger001, unlocked boot
Problem I have is I'm trying to restore the phone to stock because I want to do OTA updates. I followed the guide to return Canadian HTC1m8 to stock - downloaded the nandroid backup, restored it, flashed a stock image through fastboot;
However, now if I try a OTA it just reboots my phone and normally stalls out on the HTC screen. Nothing gets updated . If i try a factory reset, same thing, and it won't boot into bootloader until I wait a while then restart it. My data won't work anymore and TWRP recovery has disappeared. I think my issue is i flashed the wrong recovery .img, I'm a fairly noob. Checked all the related links and can't figure it out.
Any help would be amazing.
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
htcspark said:
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
Click to expand...
Click to collapse
I would but
I can't find an ruu that would work, there doesn't seem to be one for rogers...I dunno if any US carriers would work?
htcspark said:
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
Click to expand...
Click to collapse
I got an update to work, I think I had the wrong stock installed so it wouldn't work properly. Only thing now is my data isn't working, any assistance with that that could be??
Instead of trouble shooting, I would just flash this TWRP backup tested to work on Rogers M8:
http://forum.xda-developers.com/showthread.php?p=58611288
See end of 1st post in above link.
It is already in lollipop. No OTA update needed.
Use latest TWRP recovery, see 2nd post in above link.
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.
Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.
RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456
Hi all, I am playing around with an HTC m8 to decide if I should use it as replacement of my Nexus 4 (so far, too big and heavy ).
But well, I unlocked the phone and installed TWRP. All worked fine, but then I flashed supersu and I'm stucked in a boot loop. I am reading a lot of things but I am unsure about what to do now and how to actually root the phone and start installing a different ROM as I don't know what´s the phone model. It says M8_UL in fastboot...
I´m looking at this but not sure if this phone is gpe.
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Any ideas?
Thanks!
1. flash TWRP 3.0.20
2. boot TWRP
3. copy SuperSU v.[2].56 zip to SD card of device in TWRP if on Marshmallow.
4. Flash SuperSu v.[2].56 zip
5. You should boot if you were booting before flashing TWRP.
EDIT: corrected SuperSU version.
spideyngo said:
1. flash TWRP 3.0.20
2. boot TWRP
3. copy SuperSU v.1.56 zip to SD card of device in TWRP if on Marshmallow.
4. Flash SuperSu v.1.56 zip
5. You should boot if you were booting before flashing TWRP.
Click to expand...
Click to collapse
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Thanks,
frozst said:
I am reading a lot of things but I am unsure about what to do now and how to actually root the phone and start installing a different ROM
Click to expand...
Click to collapse
You don't need to root in order to install a custom ROM. Once you have TWRP installed, just put a ROM on the phone (download ROM direct to phone, copy to SD card, adb push, etc.), boot into TWRP, and install the ROM (also recommended to backup the stock ROM before flashing a custom ROM, and also do default wipe in TWRP before ROM flash - data, cache and Dalvik).
All custom ROMs are pre-rooted, so you don't need to root separately after flashing a ROM, either. Although, some AOSP based ROMs need root enabled in phone Settings>Developer's Options.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
frozst said:
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Click to expand...
Click to collapse
S-on is fine. I don't know why the previous user stated SuperSU 1.56. That build is ancient, and will definitely not work on Marshmallow. Might be a typo, or they were just thinking of the wrong number (maybe 2.56).
Latest stable version SuperSU 2.76 is recommended for rooting Marshmallow: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
But as already mentioned, you don't need root to flash custom ROMs.
frozst said:
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Thanks,
Click to expand...
Click to collapse
EDIT: SuperSU version 2.56. Sorry about that.
I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop. You may need to flash a rooted stock ROM to repair booting. S-off not needed, but makes your life easier.
Thanks! the problem was the old SU version, solved now and testing different ROMs. Any recomendations?
spideyngo said:
I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop.
Click to expand...
Click to collapse
Hadn't heard that. I wonder if its a known issue experienced by others? If so, I'll fall back to my previous recommendation to use 2.65, which was the former "latest" STABLE version; and no complaints that I am aware of.
Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?
kbytes said:
Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?
Click to expand...
Click to collapse
This forum is for the M8, any advice you get may not be correct. Post in the M9 forum.
But what I can say, is if you say "several version" SuperSU is not specific enough (when you post to the correct device forum). Be specific as to what version numbers you tried. Nobody can help, if you don't give the proper info to see what you did wrong. In particular, you need to provide info on what Android version your phone is currently on, what TWRP version, what SuperSU version(s) you tried.
But again, post to the M9 forum, not here.
Stuck on HTC Screen.
I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?
weismanak said:
I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?
Click to expand...
Click to collapse
You probably used an old version TWRP and/or old version SuperSU.
TWRP 3.0.2 and SuperSU 2.76 is recommended.
Hold power+vol up for a minute or so, to force a reboot. Once the screen goes dark to reboot, let go of the buttons, and only hold vol down. Don't let go of vol down, until you are in bootloader. If the phone just gets stuck on the logo screen again, you just got the timing wrong; either didn't start pressing vol down soon enough, or let go too early. Just repeat the process, until you get to bootloader.
From there, restore TWRP backup (which you should always make before attempting to root) and try again, with the proper versions TWRP and SuperSU.
If no TWRP backup, flash proper version TWRP in fastboot, then get proper version SuperSU to the phone (adb push, or put the file on SD card).
Still stuck in boot loop... but different place.
Whew!! OK, so I got past that hurdle (Thank you so much). I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. The phone is now stuck at the bootloader. If I select "Recovery" it simply comes back to the "Fastboot-usb". I've attached a screen shot (maybe) to demonstrate what I'm seeing on the phone.
*** Software status: Modified ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
Open DSP-v56.2.2-00593-M8974_FO.0126
OS-6.20.502.5
eMMC-boot 2048MB
Apr 14 2016,19:39:46.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Click to expand...
Click to collapse
Thanks for all your help, I'm a noOb to this process. Recent convert from iOS.
weismanak said:
I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. .
Click to expand...
Click to collapse
Meaning you used the TWRP version and SuperSU version included with the toolkit? If so, that toolkit hasn't been updated in a long time, and likely is not using the versions TWRP and SuperSU that I specified previously.
Additionally, I don't personally recommend using such toolkits. Doing so robs you of a valuable learning experience, and therefore guarantees that you stay a n00b. Also, the toolkits constitute an additional point of failure (even when they are updated) that is not necessary. I've often seen processes fail using the toolkits, when the exact same steps complete just fine if done "manually".
Since it appears you've successfully unlocked the bootloader (can be verified if it says UNLOCKED near the top of the bootloader screen), than I would advise:
1) Manually flash TWRP 3.0.2 with fastboot using the instructions here: https://twrp.me/devices/htconem8gsm.html
2) Download SuperSU 2.76 from here, and put it on SD card (alternately, adb push to phone - but that may be a bit complicated for you).
3) Boot into TWRP, under Install, navigate to the SuperSU 2.76 zip, and flash it.
redpoint73 said:
You don't need to root in order to install a custom ROM. Once you have TWRP installed, just put a ROM on the phone (download ROM direct to phone, copy to SD card, adb push, etc.), boot into TWRP, and install the ROM (also recommended to backup the stock ROM before flashing a custom ROM, and also do default wipe in TWRP before ROM flash - data, cache and Dalvik).
All custom ROMs are pre-rooted, so you don't need to root separately after flashing a ROM, either. Although, some AOSP based ROMs need root enabled in phone Settings>Developer's Options.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
S-on is fine. I don't know why the previous user stated SuperSU 1.56. That build is ancient, and will definitely not work on Marshmallow. Might be a typo, or they were just thinking of the wrong number (maybe 2.56).
Latest stable version SuperSU 2.76 is recommended for rooting Marshmallow: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
But as already mentioned, you don't need root to flash custom ROMs.
Click to expand...
Click to collapse
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2
ajay vadaparthi said:
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2
Click to expand...
Click to collapse
have you flashed the latest supersu.zip ?
does the flashing process ended with success ?
you may try to enable root in developer options and see
also you are in the wrong forum
Sent from my HTC M8 using XDA Labs
Can I re-flash SuperSU over an existing one?
Hi - Long time listener, first time caller!
So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.
I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.
However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.
I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.
I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.
I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.
From the bootloader menu these are the details I have:
HTC_HIMA UHL PVT S-ON
LK - 1.0.0.0000
Radio - 01.01_U11440792_96.00.51201G_F
OpenDSP - 15.6.1.0052.8994_1026
OS - 3.35.161.12
Dec 17 2015, 00:40:10 (671447)
MRA58K_Release-Keys
This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.
As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?
Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?
As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.
Thanks in advance.
tigarstyle said:
Hi - Long time listener, first time caller!
So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.
I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.
However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.
I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.
I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.
I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.
From the bootloader menu these are the details I have:
HTC_HIMA UHL PVT S-ON
LK - 1.0.0.0000
Radio - 01.01_U11440792_96.00.51201G_F
OpenDSP - 15.6.1.0052.8994_1026
OS - 3.35.161.12
Dec 17 2015, 00:40:10 (671447)
MRA58K_Release-Keys
This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.
As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?
Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?
As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.
Thanks in advance.
Click to expand...
Click to collapse
your first post in the wrong forum this forum for m8 )
if you can flash a rom then flash it,will save the hassle of flashing RUU
and you used an outdated version of supersu ( i don't know if this will fix it but try to flash the latest version on top the older )
you can rename the RUU to 0PJAIMG.zip and put it in the sd card root ( formatted as fat32 or exfat , 3.xx can flash RUU from exfat cards ) then reboot to download mode and follow the instruction
if you have any question ask in the m9 forum as you may get a wrong answer here :silly:
Thanks a lot. I didn't realise this forum was for M8 only, my mistake. I've now posted in the correct forum.
I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked. I guess I'm lucky that I have a connection with the PC as I can see the internal storage of my device still and I still have access to TWRP.
One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program? Just thought it might be worth sharing for anyone who is on M8 and stuck on the HTC One splashscreen like I am.
tigarstyle said:
I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked.
Click to expand...
Click to collapse
If the phone was hard bricked, you wouldn't be able to flash anything. The screen wouldn't come on at all. A hard brick means you need to open the phone to repair it (new motherboard or JTAG, at a minimum). You don't have a hard brick.
Do you mean to ask if flashing the proper SuperSU would brick the phone (if its safe to flash)? If that is the question, you best direct it to folks knowledgeable to the M9. On the M8, its fine to flash the newer SuperSU (and the proper fix after flashing obsolete SuperSU). But that doesn't meant the M9 is the same. And following advice meant for another device can possibly damage the device.
tigarstyle said:
One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program?
Click to expand...
Click to collapse
Nowhere in any instructions for flashing RUU.zip will you see anything about extracting files from the RUU.zip.
Therefore, don't do it.
The file is encrypted and signed. Even if you were able to extract anything, you wouldn't be able to flash it with s-on (s-on can't flash unsigned RUU zips).
Excellent, thank you. I was wondering why the zip file wouldn't extract on the PC. I saw videos explaining that in other to get to Stock ROM, you'd do it via the RUU.zip. So when I downloaded the RUU.zip Stock ROM file, I thought I had to extract the zip in order to get to the application, then flash the device.
Thanks for taking the time out to explain in detail...much appreciated.