Related
Hellloo xda...is there anyone who can gimme a proper step to step guide for unrooting my htc one v.
1. Download the HTC Asia India RUU from Football's collection in the development section
2. While that's downloading, relock your bootloader using the command
Code:
fastboot oem lock
3. Open the RUU. Find the temp folder it created and open ROM.zip from inside it with 7Zip. Extract the recover.img and flash it
Code:
fasboot flash recovery recovery.img
4. Run the RUU and your phone's status will be *** RELOCKED *** and unrooted.
So why do you want to unroot?
Whenever I install custom Rom my sd card and WiFi doesn't work...soo I installed custom Rom without having a nandroid.backup.that's y I was asking.neways thanks a lot for replying.this. is my second one v(replacement)
sent from my sexoo one v
My build number is1.56.720.2 and the ruu is 1.58.707.3.what should i do now??
how do i find the temp folder??..
What is the use of other images???in rom folder..does this stock ruu flashing fixes error?
So what exactly are you trying to do now? Before you said unroot the phone, then you said install custom ROM in a later post.
could you also please find a way to help me? my htc one v freeze forever after i turn it on, please help me
Assuming you're on stock rom, have you try factory reset in bootloader ?
Do you know your software version or cid no. ?
He sent a pm telling me that his phone is rooted and he flashed a zip file that supposedly increases the SD card speed, and apparently causes soft bricks too
I think the only thing to do is re-flash the RUU because I don't think he did a backup in CWM Recovery.
Roxas84, please confirm.
I see.. if he can send the file, sometimes do a revert.zip will help. The easiest is reflash the same rom.zip with wipe cache & system. It should correct the error.
Hey dudes,
I was going to start the same thread but since this is open I want to ask you one question:
If I root the phone, flash cwm, and then I want to return to stock (for warranty purposes) how can I 'uninstall' cwm? Because for unroot I know how to do it, but uninstall custom recovery I never done that even on my older phone - Htc hero.
I'm not new to recoveries, custom roms, flashing and all this kind of stuff, but this is a problem that I don't know how to handle it since I didn't needed to uninstall the custom recovery in the past.
TIA!
L.E: To Answer my own question:
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
Thanks @ckpv5 for these awesome guides
I just summarized this thread in the following tut but with much more detail:
[TUT] Re-flash stock ROM (RUU) after bricking a rooted device (for noobs)
Roxas84, follow this tut if ckpv5's suggestion above doesn't work.
1ceb0x, it will also show how to revert to stock recovery.
1ceb0x said:
Hey dudes,
I was going to start the same thread but since this is open I want to ask you one question:
If I root the phone, flash cwm, and then I want to return to stock (for warranty purposes) how can I 'uninstall' cwm? Because for unroot I know how to do it, but uninstall custom recovery I never done that even on my older phone - Htc hero.
I'm not new to recoveries, custom roms, flashing and all this kind of stuff, but this is a problem that I don't know how to handle it since I didn't needed to uninstall the custom recovery in the past.
TIA!
Click to expand...
Click to collapse
relock bootloader flash stock ruu
bt i dnt think ul get ur warranty back as. the bootloader will not show locked
it will show relock
i dnt think there is any way to get factory bootloader lock
dont just say thanks hit thanks if i helped
sent from my awesome HTC One V using xda premium
i need help cause mine is a koodo one can sombody link me to a thread to unroot the htc one v
Just restore the nandroid backup you made before rooting your phone.
Hello guys, I want to unroot my One V but I have a problem. I don't find my RUU. HBOOT says:
*** UNLOCKED ***
PRIMOU PVT SHIP S-ON RL
HBOOT-1.18.0000
Radio-3831.18.00.282
eMMc-boot
Which ruu should I use?
Thx!
Dude you don't look here you look at your software number in settings
Oh! My device says 2.19.666.3 and again, there's not RUU with this mention...
Does anyone have ROM version 1.56.1402 of HTC Desire V T328w China Unicom, please share. I have this version install on my device (HBOOT already updated to 1.14.0002).
My current rom is error by missing notification bar when I try to instaff gapps_201204xx to the rom, and bacause I failed to make backup before flash, now I want to revet it back to original rom.
I have try to flash the previous leaks rom 1.35.xxxx, but have no luck by both using RUU or PL111IMG.zip. (even I have done reverted recovery back to stock and relock).
Please kindly help me.
why don't you try to use the taiwan ROM, it comes with gapps
bigjimmy546 said:
why don't you try to use the taiwan ROM, it comes with gapps
Click to expand...
Click to collapse
it doesnt look like the taiwan ROM is flashable on mainland chinese version of t328w because of CID difference.
That's exactly the point!
I am trying to flash a Taiwan version of the ROM. But becouse of this SID difference, I'm unable to do it.
Any good soul knows how to do it? Bypass, change or fix this SID difference issue?
Best regards,
you need to flash a china version, then replace the rom and boot file with the taiwan rom
SokRatha said:
Does anyone have ROM version 1.56.1402 of HTC Desire V T328w China Unicom, please share. I have this version install on my device (HBOOT already updated to 1.14.0002).
My current rom is error by missing notification bar when I try to instaff gapps_201204xx to the rom, and bacause I failed to make backup before flash, now I want to revet it back to original rom.
I have try to flash the previous leaks rom 1.35.xxxx, but have no luck by both using RUU or PL111IMG.zip. (even I have done reverted recovery back to stock and relock).
Please kindly help me.
Click to expand...
Click to collapse
what u need to do is the following:
1) *skip this step if your phone is still locked* if you have unlock your bootloader, you need to relock it using the same tool that unlocked the bootloader
2) download the RUU version of the original ROM. RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.35.1402.1_Radio_1.04.34D.11_20.11.30.11U_release_256137_signed.exe
address is here:
http://dl.dbank.com/c0ys4u58d7#
3) go into fastboot mode, and execute the RUU file.
4) follow the steps and your phone should be back to original factory states.
the thing to make sure: your bootloader needs to be locked to flash RUU.
cezent said:
what u need to do is the following:
1) *skip this step if your phone is still locked* if you have unlock your bootloader, you need to relock it using the same tool that unlocked the bootloader
2) download the RUU version of the original ROM. RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.35.1402.1_Radio_1.04.34D.11_20.11.30.11U_release_256137_signed.exe
address is here:
http://dl.dbank.com/c0ys4u58d7#
3) go into fastboot mode, and execute the RUU file.
4) follow the steps and your phone should be back to original factory states.
the thing to make sure: your bootloader needs to be locked to flash RUU.
Click to expand...
Click to collapse
This instruction I have follow many time already, but no luck.
I guest this only work when our device not yet receive 1.56.xxx OTA update. When we receive such this OTA update, our bootloader has been updated to 1.14.0002 which is newer then the 1 in the ROM you suggested to me. Finally, the update is failed with a report "HBOOT is older, update failed".
Anyway, really thanks for your great time for suggesting. And till now I have found solution on this issue, is that you could use the, what they called mini-RUU of China ROM (it's also same version suggested above, without HBOOT, and some other part of image file). Using flash zip file method in recovery mode, it work and you need to update software after complete flashing.
bigjimmy546 said:
you need to flash a china version, then replace the rom and boot file with the taiwan rom
Click to expand...
Click to collapse
Could you clearly explain what to do?
SokRatha said:
My current rom is error by missing notification bar
Click to expand...
Click to collapse
this is because old Kernel is used. I've got the same problem when played with roms on my device.
Try to unpack boot_signed.img from rom.zip of original RUU and flash it via fastboot
fastboot flash boot boot_signed.img
This should help.
hey i tried to insatl the new maximus rom 4.1 ia have the right cid so i get into fastboot locked my device when i was still at viper x rom and now i can't do anything with my device it won't reboot and tells me that my device is for develepment pruposes only and it wil get back to fastboot please help i tried to get this command fastboot flash unlocktoken unlock_code.bin but it says failed so i tried adb reboot oem-78 and but it tells me the is no devices attached then i removed the phone and the pluged it back but it is still the same please helpp what to doo i am still on the old hboot so i could get back to viper x.. ps is because i forgot to hit usb debuging before starting? please help asap
this should cover it:
http://forum.xda-developers.com/wiki/HTC_One_X#Disaster_Recovery_-_what_to_do_in_the_event_of_a_bad_flash
please use better english next time. in your entire text, there are only two points and one question mark...
DON'T PANIC YOUR NOT BRICKED
Best thing to do would be to unlock your bootloader again at HTC dev .com.
Once unlocked flash custom recovery again and restore from a previous back up to yet the phone working.
This can all be done while you are in the bootloader screen. I had the same problem, and got mine sorted
I think the issue was that you didn't flash the boot.img of the new Rom before you locked the bootloader. Hence leaving you stuck and not booting.
Other than that best thing could be to download the correct .ruu version for your phone and install that from your computer and restore it to origial Rom and bootloader, the you have the option to update the hboot so that you can flash jellybean roms.
1. Either down load correct ruu and run.
To restore phone.
Or
1. Unlock your bootloader (HTC dev.com)
2. Install custom recovery
3. Restore from back up (if you made one) and of course flashing correct boot.omg of that back up Rom.
4. Flash new custom Rom with correct boot omg
At least your phone will be working.
Check the forum there are threads that detail several methods on how to update hboot to install jellybean.
But first get the phone to a working state.
Goodluck.
Sent from my HTC One X using xda premium
Hi
hope any can help with the issue i am facing, simply i deleted my os & the back up file while trying to flash a rom
all i can access now is twrp recovery screen, i tried flashing a couple of custom rom with no luck
my device is HTC one M8, it was rooted but i don't think it is anymore since it says that i don't have su installed
excuse my lack of android knowledge, as i am new to this whole thing
thanks for reading and any help is appreciated
I never fail to be frustrated at the nearly countless reports here of "I deleted everything on my phone and now its stuck".
If you lack knowledge of Androids mods, the proper way to proceed is to familiarize yourself and understand what you are doing before doing it. The absolute wrong thing to do, is to delete things without knowing what the result will be, and not knowing how to revert from that condition. Plus, the default wipe (user data, cache and Dalvik) on TWRP clearly states that "most of the time, this is the only wipe you need". It says this for good reason, and the additional wipe options are labelled "Advanced" also for good reason. So there were a couple warning signs against doing what you did, that you chose to ignore.
You didn't specify what ROMs you tried (makes it hard to help) and whether you put those on the phone before you wiped the OS; or if you know how to put ROMs on the phone in the current condition (using adb push, or removable SD).
Also, missing some key info:
1) hboot number
2) OS number on hboot screen (or main version as determined by adb getvar all)
3) CID (carrier version) of your phone
4) S-on or s-off
5) What version TWRP
while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.
ashypanda said:
while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.
Click to expand...
Click to collapse
While your advice is generally true, the specific ROM (or TWRP version) may part of the issue. OP will need to be careful to flash a ROM that supports his current firmware (hboot, radio, etc.) otherwise he may have some serious problems.
The fact that he said he tried a few ROMs that didn't work, leads me to believe he either has old firmware, or old TWRP.
OP should provide the info I requested in my last post, so we can more specifically help.
thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance
ahmed.abdelradi said:
thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance
Click to expand...
Click to collapse
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.
redpoint73 said:
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.
Click to expand...
Click to collapse
Personally, I would rather go with a "combined" firmware, such as the ones provided here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Mike's firmwares are incremental afaik (pulled from the OTAs), so jumping from from a 1.xx firmware all the way to an [incremental] 4.16 version, is going to cause problems.
i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...
srijan0008 said:
i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...
Click to expand...
Click to collapse
Dude, your firmware is super old and you won't be able to run the latest ViperROM with it.
Be aware what I'm telling you to do will wipe your phone, (you'll need to do a full wipe to flash the ViperROM anyway)
Go here to download the official RUU from HTC's US website
Scroll down to the "Manual System Update Instructions" and read them. The RUU download is at the end of the instructions
After the RUU has run, reflash TWRP, then flash the ROM
srijan0008 said:
i did the same..
Click to expand...
Click to collapse
A word of advice, I know you are new here, but posting "I did the same" or similar ("same problem" etc.) is never true. Especially since you are responding to a thread from 2 years ago, different M8 versions, different ROM, different TWRP version.
There are simply far too many differences to say you "did the same" and that statement is therefore meaningless. Better to just describe the exact issue (which you did) and not bother with such vague statements.
srijan0008 said:
os-1.54.651.8
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom
Click to expand...
Click to collapse
As xunholyx explained you need to update the firmware, not just the ROM. Firmware includes a whole bunch of other partitions (hboot, radio, WiFi, and more) that ROM doesn't touch. Old firmware (your is very old) is not compatible with a more recent version ROM.
Old firmware is also not compatible with the current TWRP 3.1.1-0, so the ROM won't flash properly, either.
So as already suggested, flash RUU to update all the firmware. Then flash TWRP 3.1.1-0 back to the phone, and flash Viper.
srijan0008 said:
i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
Click to expand...
Click to collapse
Another good rule of thumb, do NOT wipe things in TWRP "Advanced" wipe options, unless you know exactly what it is, and what the result will be. Wiping internal storage and/or SD will in most cases not help matter, but just make them worse (wipe backups, ROM zips, etc.).
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.