Hi all,
Any help please? After nearly 2 years of having my HTC One M7 and not rooted a phone since either. Decided today would be the day and yep I cocked it up.
All was going well, unlocked bootloader, installed TWRP, installed SuperSu.
Rebooted then problems started, SU was not installed correctly, said binaries needed updating and would need to be done manually. Updated superuser with latest 2.46 update file through TWRP. Phone is now stuck on HTC One boot logo. I did a nand backup before SU update and that just boots back to TWRP.
Any help please?
Regards
fs1023
fs1023 said:
Hi all,
Any help please? After nearly 2 years of having my HTC One M7 and not rooted a phone since either. Decided today would be the day and yep I cocked it up.
All was going well, unlocked bootloader, installed TWRP, installed SuperSu.
Rebooted then problems started, SU was not installed correctly, said binaries needed updating and would need to be done manually. Updated superuser with latest 2.46 update file through TWRP. Phone is now stuck on HTC One boot logo. I did a nand backup before SU update and that just boots back to TWRP.
Any help please?
Regards
fs1023
Click to expand...
Click to collapse
which version of twrp do you have, binary update is often needed, nothing really wrong with that, while the bootloop could be due to a faulty version of twrp. if you have 2.8.6.0 you should look for 2.8.6.1 and chances are good that the problem is gone. of course i dunno what else could have gone wrong, just seeing that you freshly installed and that this could be the reason. hope it helps.
Related
Hello all!
This morning my phone decided to reboot over and over again. I got into twp and made a back up of my current ROM. After making the backups I tried to restart and twrp informed me my device was not rooted and asked if I wanted to install SU. I choose no, then rebooted. I tried to restore an older version of my rom twrp gave me a "failed" message. So I tried to reboot and again I got the message from twrp saying I was not reooted and ask to install SU.. so I did.
Since then I can not get back into twrp, I get the twrp splash screen and then the phone bootloops. I tried reflashing twrp 2.6.3.0, 2.6.1.0 and even 2.6.0.0 multiple times with all the same results of twrp splash screen, then phone reboots... Any ideas?
I'm s-off (VIA dirtyraccoon from about 16 months ago)
Hboot: 1.19.0000
EDIT: I used windroid HTC Evo LTE tool kit and s-off'd with faceplam... dunno why but it seems to have fixed it.
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
It was my first attempt to root.
I unlocked the bootloader from htcdev then used twrp
I downloaded supersu version 2.02 put in on my sd card and flashed it
I had supersu in my app drawer but it said SU binaries weren't installed and i had to reroot but i didn't have any problem with the functioning of my phone.
I downloaded the last version 2.46 from chainfire
I wipe cash and dalvik and then rebooted. My phone got stuck on the white screen with htc logo
I couldn't turn it off so i let the battery drain. Tried rebooting, same problem.
I would like to go back to stock.
Please help and I need step by step instructions if possible.
Thank you
Hey guys,
i tried to root my cellphone but since im not experienced with stuff like this i asked a friend of mine for help, but we kinda stuck so i need help. First i unlocked the bootloader then i flashed the 3.0.2.0 recovery and afterwards twrp didnt work out so i flashed an another version and then i made a backup. Then i swiped the factory reset & system, then i flashed the cyanogenmod 11 rom and google apps. And then i flashed the boot.img per fastboot and since then i can only enter the recovery but not the system nor i can fastboot. also i cant install a new rom. And once i missclicked on root tho the bootloader was rebooting. i would highly appreciate your help
I got out of the phone mod life about a year ago..
but one of my friends is going through some financial stress and needs a phone.. i had a Sprint M9 sitting here for about a year.. So i decided i'd try to unlock it so he could use it.
Needless to say i'm a little rusty and a lot of things have changed
I asked Stifilz to help with the unlock and he directed me to
http://forum.xda-developers.com/sprint-one-m9/general/nv-unlock-sim-t3314755
I needed to get the MSL, so I attempted the root following this guide
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Everything went smoothly with the instructions.. only problem is that I am now stuck in a bootloop of the HTC boot screen with the red writing.
Can anyone point me in the right direction?
firmware? boot.img? new rom?
Hi.. phone has been sitting down collecting dust since the last post.. a friend needs a phone so I'm trying to get it working to give it away.. anyone have any solutions for this?
I am willing to pay to get this resolved.
Hold power button and volume down button at the same time and boot to recovery. Can you get into twrp recovery?
{ParanoiA} said:
Hold power button and volume down button at the same time and boot to recovery. Can you get into twrp recovery?
Click to expand...
Click to collapse
Hi? I'm in same situation. From stock, I didn't follow any particular tutorial. I used my knowledge from HTC m8. I unlocked bootloader, flashed latest twrp for m9, flashed latest supersu zip. And that's it. Boot loop afterwards. I flashed supersu via OTG Drive. Could that be an issue? Phone is still S-ON
UPDATE: I some how wiped cache, dalvich, data and system partition in twrp now it says I have no OS installed. I think I wasn't supposed to wipe system partition? How to get back to phone plz? Could you Point me to a restore file or stock HTC file I can restore with adb or twrp? I didn't make a backup before I started the whole thing.
Grab stock rooted rom from development thread n flash that. Should be good after that
jazzdglass said:
Hi? I'm in same situation. From stock, I didn't follow any particular tutorial. I used my knowledge from HTC m8. I unlocked bootloader, flashed latest twrp for m9, flashed latest supersu zip. And that's it. Boot loop afterwards. I flashed supersu via OTG Drive. Could that be an issue? Phone is still S-ON
UPDATE: I some how wiped cache, dalvich, data and system partition in twrp now it says I have no OS installed. I think I wasn't supposed to wipe system partition? How to get back to phone plz? Could you Point me to a restore file or stock HTC file I can restore with adb or twrp? I didn't make a backup before I started the whole thing.
Click to expand...
Click to collapse
Did you get this fixed??? I'm kind of in the same situation!!!
elterru said:
Did you get this fixed??? I'm kind of in the same situation!!!
Click to expand...
Click to collapse
yes. i got it fixed. open the zip file of the ROM you were trying to flash, look for the boot.img file and flash it with adb. problem is with the boot image of stock rom. it somehow doesnt boot propely after root
jazzdglass said:
yes. i got it fixed. open the zip file of the ROM you were trying to flash, look for the boot.img file and flash it with adb. problem is with the boot image of stock rom. it somehow doesnt boot propely after root
Click to expand...
Click to collapse
Thank you!!!