Sorry to post this in the main section. A mod can delete it if necessary. I just hoped I could get some help from an expert right away. I'm quite experienced with this process on my Sensation and never had any trouble. Bought a One S today and...
Using the All in One Tool I flashed the latest recovery, and now it appears to be soft-bricked. I can't figure out how to get into recovery or the bootloader. It just brings up the HTC screen with the red text. Help?
Edit: hold tight... bootloader spontaniously started working again. I may survive.
If your device is off just hold down volume down, press and hold the power button for a little bit before you let it go. Keep pressing the volume down button until your in the bootloader
If it's on (or booting ) just press and hold power and volume down, when it has shut down let power button go but keep pressing volume till it has booted
Sent from my HTC One S using xda app-developers app
Habarug said:
If your device is off just hold down volume down, press and hold the power button for a little bit before you let it go. Keep pressing the volume down button until your in the bootloader
If it's on (or booting ) just press and hold power and volume down, when it has shut down let power button go but keep pressing volume till it has booted
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Now holding the bottom rocker is bringing up Recovery, which is unable to mount storage. I'm trying to get into Bootloader now and try to reflash another recovery. Is the TWRP one any good? I've never used it. CWM is giving me no end of grief on this phone.
Update: Installed TWRP. It's working, but it cannot mount USB either, so I have no idea how to install a ROM on the phone.
There is a guide here about how to adb push a rom to your phone, try that
Sent from my HTC One S using xda app-developers app
Habarug said:
There is a guide here about how to adb push a rom to your phone, try that
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
when I do the adb push command it just says "device not found." When I do the "fastboot devices" it appears to show the device.
HRMMMM.....
ADB requires the phone to be running and have USB debugging activated, while fastboot requires it to be in bootloader. Also try to get this thread out of dev section.
frdd said:
ADB requires the phone to be running and have USB debugging activated, while fastboot requires it to be in bootloader. Also try to get this thread out of dev section.
Click to expand...
Click to collapse
I don't have the ability to move the thread myself and I apologize for the intrusion, but I am pretty desperate to get this sucker running and this is really the only active forum at this hour.
So how do you get something on an internal only SD card when the Recovery can't mount the card? And why can't the recovery mount the card? It's bizarre.
Stay in recovery while doing the adb commands
Habarug said:
Stay in recovery while doing the adb commands
Click to expand...
Click to collapse
abd push rom.zip \sdcard
appeared to work. But it didn't appear on my card. Or at least recovery can't read it.
This is nuts. Suddenly I appreciate my trusty sensation.
UPDATE:
Reinstalled CWM 5.8.3.1 off of the clockworkmod website. Same issue.
Mounting USB storage never worked for me with CWM, but I have no problems at all with TWRP... You have the right drivers installed right? You were able to mount when it was on your stock rom?
Habarug said:
Mounting USB storage never worked for me with CWM, but I have no problems at all with TWRP... You have the right drivers installed right? You were able to mount when it was on your stock rom?
Click to expand...
Click to collapse
I did everything through the AIO Kit. Yes it worked with stock, and if I remember right it worked once with CWM then I tried to install MIUI. It crashed on boot, and from then on neither CWM or TWRP has been able to mount the storage. Just trick relocking and unlocking the bootloader. No dice.
This thread:
http://forum.xda-developers.com/showthread.php?t=1630459
Post 8 has instructions. The only one I don't understand is the first one. What does he mean when he says "flash your recovery back to stock." Relock the bootloader, or is there a stock recovery file I need to put in the recovery folder?
In that kit there is a list with the recoveries to the right, isn't stock there?
Habarug said:
In that kit there is a list with the recoveries to the right, isn't stock there?
Click to expand...
Click to collapse
Nope. Just says CWM, then TRW, then "your own recovery."
HOWEVER, I found what should be a stock recovery, and tried that with the bootloader locked. No luck. Trying it with the bootloader unlocked now.
Update:
The TWR recovery seems to be behaving slightly differently, but it still won't mount. I'll try the entire process again with CWM now.
PS. This 2 minute posting rule for editing posts is super obnoxious and counter productive.
Update 2:
No luck. CWM says the same thing:
E: Unable to open ums lunfile (No such file or directory)
Sorry, then I have no idea :/ I don't think I've seen any others having problems with TWRP not mounting properly
Habarug said:
Sorry, then I have no idea :/ I don't think I've seen any others having problems with TWRP not mounting properly
Click to expand...
Click to collapse
I got it. Apparently the version of TWR or whatever it's called wasn't current. I fount a 2.1.8 instead of 2.1.7 and that worked.
Thanks a TON for the help though. REALLY appreciate it so much. 5 hours on this thing and I finally have a working phone again. =)
Related
I was using this guide http://forum.xda-developers.com/showthread.php?t=1078019 to unlock, install CWM, and then root. Unlocking was fine, installing that version of CWM seemed okay, but when I enter command "fastboot reboot", then hold down the volume - button after 3 seconds of the Moto logo showing, then pressing the volume + key, I get only 1 option....-->Android Recovery. I press the Volume + key, get "Entering Android Recovery Mode", and below that "Reading ODM Fuse 1", then the screen switches to an android with a yellow hazard sign in his tummy.
From that screen, if I press Volume + and power, I see:
Android system recovery <3e>
Use volume keys to highlight; power button to select.
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
I don't get a choice to apply something from the microSD card I have installed with the WiFi_RootTool_3.1.zip I put on the card.
Has anyone had this happen? I can't ask in the development forum. I also just got the Xoom back from a repair, and it was wiped to stock, then I did the 3.1 update when I got it back this morning. Is the fuse thing something they may have done to block rooting?
Have you tried reformat your sd card?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I'll try that. But would that stop it from going into recovery?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I reformatted my sd card, but I still can't get CWM to work and boot into recovery. Same message-
-->Android Recovery
Entering Android Recovery Mode
Reading ODM fuse: 1
And that's it....no options to load the root zip from an SD card or anything. Is there a way to push root without using the SD card? Or is that ODM fuse thing making it impossible?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
siscim23 said:
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
Click to expand...
Click to collapse
I have to root first? I'm not sure how to do it....can't find any other methods of rooting 3.1....everything on Google just points me to the same method, using the SD card that won't work cuz I can't boot into recovery. Ugh.
Hey jump hour PM me.
Hey guys,
I called JumpHour and we tried to troubleshoot this over the phone. We aren't able to get into the recovery because of error "reading odm fuse: 1". The OP is using Windows 7 64 BIT and has the SDK installed properly. He updated the sources and installed them so those are up to date. We also verified that USB debugging was enabled and that the correct files were in the tools section in the SDK folder.
We ran the commands:
adb reboot bootloader
fastboot-recovery ........ (we typed it in correctly accoriding the thread)
fastboot reboot
and we get that error message.
This was all initiated while the Xoom was powered on. JumpHour stated that he had to send his Xoom back to Moto because his Xoom got messed up during the re-locking process when he unrooted a one click root and re-locked.
We then went ahead and downloaded the recovery image again and replace the one in the tools folder. We ran the commands again and we were getting the same error.
Does anyone have any idea what is going on with this process? Are we missing something? Is something broken?
Get the official images. I am assuming you have a USA 3g or wifi model.
Follow the steps to return the device to stock. But do not issue the reclock bootloader command. There is no need to relock.
From there power up the device and turn on USB debugging.
Then adb reboot into recovery. That should bring you to the stock recovery.
If all goes well from here just do what ever else you where intending to do in the first place.
You most likely can just flash the stock recovery but I would just do a full flash back to official images minus relocking bootloader.
Sent from my Xoom using Tapatalk
Then let the ota update it to 3.1 and so on.
Sent from my Xoom using Tapatalk
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
gqstatus0685 said:
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
Click to expand...
Click to collapse
Hi, thanks for the response. I'm gonna try it now. I was up REALLY late last night, and just got up a little while ago. I'll definately respond after I try it out.
Finally, I did it!
Okay, I fixed it finally. Reloaded the stock images, and it's now rooted with SD support. Yay! Only took 2 days!
Thanks for all your help guys.
Can reflashing with original images fix recovery mode mount problem?
Does any window is flashing to the original images can restore access to the sdcard IF the recovery mode in the official recovery mode (not CWM) says that you cannot mount the sdcard?
I've looked through the searches but I couldnt really find the answer.
I've rooted and unlocked my HOX but I can't boot into bootloader through volume donw + power.
I have CleanROM 4.0 flashed and the 4.1 version just came out. It says to use TWRP so I will.
How do I go about removing CWM that I installed through the one-click tutorial?
I want to put TWRP after that.
Thanks a lot XDA.
RYEGRAIN said:
I've looked through the searches but I couldnt really find the answer.
I've rooted and unlocked my HOX but I can't boot into bootloader through volume donw + power.
I have CleanROM 4.0 flashed and the 4.1 version just came out. It says to use TWRP so I will.
How do I go about removing CWM that I installed through the one-click tutorial?
I want to put TWRP after that.
Thanks a lot XDA.
Click to expand...
Click to collapse
Make sure fastboot I the power settings is u checked then you can boot into bootloader with the button combo. And the easiest way to install twrp would be to use Goo Manager from the market, it will install it for you.
Sent from my HTC One X using xda premium
kleeman7 said:
Make sure fastboot I the power settings is u checked then you can boot into bootloader with the button combo. And the easiest way to install twrp would be to use Goo Manager from the market, it will install it for you.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks for the response, I appreciate it.
I still can't boot into bootloader with both fastboot checked and unchecked. However I did install TWRP through Goomanager. By doing that does it mean CWM is gone?
It freaks my out that I can't use my H-boot. :crying:
RYEGRAIN said:
Thanks for the response, I appreciate it.
I still can't boot into bootloader with both fastboot checked and unchecked. However I did install TWRP through Goomanager. By doing that does it mean CWM is gone?
It freaks my out that I can't use my H-boot. :crying:
Click to expand...
Click to collapse
You can use your bootloader, you need to make sure fastboot is unchecked, and when you hold power + vol down make sure you let go of power and keep vol down til in bootloader, and yes cwn is gone you can only have one recovery.
Just keep trying you will get it.
Sent from my HTC One X using xda premium
RYEGRAIN said:
I still can't boot into bootloader with both fastboot checked and unchecked.
Click to expand...
Click to collapse
Assuming you still have CleanROM installed... try this:
1. Boot into the Android OS as usual
2. Press and hold the power key; this will bring up the "Phone Options" dialog
3. Select "Restart"; this will bring up a second "Phone Options" dialog
4. Choose "Recovery"
The phone will reboot into recovery. No need to press and hold volume down or anything like that. See attached screenshots.
denversc said:
Assuming you still have CleanROM installed... try this:
1. Boot into the Android OS as usual
2. Press and hold the power key; this will bring up the "Phone Options" dialog
3. Select "Restart"; this will bring up a second "Phone Options" dialog
4. Choose "Recovery"
The phone will reboot into recovery. No need to press and hold volume down or anything like that. See attached screenshots.
Click to expand...
Click to collapse
I was just going to say, use the Advanced Power Menu way, which is what I do almost every time to get into Recovery.
If you do the power+vol down way, make sure the phone is fully powered off (with fast boot unchecked in power settings). Hold down vol down, then depress the power button for a few seconds, release power, but keep holding vol down until you get into Hboot.
Might just be (hopefully) pilot error. If neither method works, you have some other issue.
Ok so I think I may have accidentally deleted something I wasn't supposed to on the TWRP recovery and when I tried to reboot the phone (the system) it gave me a prompt saying "No OS Installed" or something like that. I ignored it and continued anyway. So basically the phone rebooted but it got stuck/froze on boot (where it says HTC blah blah). It's not really a boot loop where it keeps restarting it's just there froze. Now I now you have to hold the power button for 10 seconds or so but the phone just won't reboot or power down/turn off. I also tried holding down the volume down + power and it doesn't restart to recovery either. It's just there frozen. I'm trying to get to the bootloader or recovery so I can fix this issue but I can't even power down the phone! And this phone doesn't have a removable battery so that's out of the question. What can I do other than waiting for the phone's battery to die out?
Can you hold down the power button until the keys start flashing? It should boot if you press until the lights go out.
Can you reach it from adb or fastboot?
leit4444 said:
Can you hold down the power button until the keys start flashing? It should boot if you press until the lights go out.
Can you reach it from adb or fastboot?
Click to expand...
Click to collapse
No. Like I said I already tried holding down the power button for several seconds up to a minutes multiple times. The keys don't flash at all. It doesn't reboot or turn off. It's just stuck there. I tried holding down the volume and power button as well. Nothing. It's just stuck there on that boot screen (HTC quietly brilliant). I can't reach the device on abd (it says offline) and I can't reach it on fastboot either
Hm. What exactly did you delete?
You could try to leave it on until battery low. Then charge, power on into bootloader.
leit4444 said:
Hm. What exactly did you delete?
You could try to leave it on until battery low. Then charge, power on into bootloader.
Click to expand...
Click to collapse
I basically wiped the entire internal sd card. I also wiped the System.
Ok so now the phone is dead but I can't seem to boot into bootloader/recovery. I keep pressing volume down + power multiple times but it just doesn't work. And if I do turn it on normally it'll go back to the boot screen and stay frozen until the battery dies.
Ok so I managed to "/adb reboot-bootloader" from my computer. I noticed that there's no recovery option on the bootloader anymore. What the hell? Did I delete the recovery by mistake? How can I flash the recovery again?
Strange... Get a recovery and
fastboot flash recovery FILENAME
Good luck!
leit4444 said:
Strange... Get a recovery and
fastboot flash recovery FILENAME
Good luck!
Click to expand...
Click to collapse
Ok so I actually did manage to get into TWRP Recovery (v2.3.3.0). But it says "No OS Installed" what does it mean by that? How can I fix it?
Actually when I try to do anything like wipe something or ADB Sideload i keep getting these errors:
E: Unable to mount '/sdcard'
E: Unable to mount storage.
It seems that it can't locate my sd card. Although when I press mount I can see all the files on my computer but I can't see it on the TWRP's File Manager or when I try to install a .zip
Try latest twrp and see if it lets you wipe the sdcard.
Sent from my One S using Tapatalk 4
El_Svanto said:
Try latest twrp and see if it lets you wipe the sdcard.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
I flashed the latest verison of TWRP and it's still doing the same thing. Same errors
Fixed
Mods you can close this thread. I found out what the problem was. It was the way the SD Card was formatted. I have a MacBook so I guess when I was formatting the SD Card on my Mac it wouldn't format it right or to a way recognizable to TWRP
The solution? I just wiped the internal SD Card on TWRP Recovery instead. That fix all the "E: Unable to mount '/sdcard'" issue.
As I told you
Skickat från min HTC One S med Tapatalk 4
El_Svanto said:
As I told you
Skickat från min HTC One S med Tapatalk 4
Click to expand...
Click to collapse
Yeah I didn't know what you meant exactly. I thought you meant to wipe the sd card any way like through the computer (since my Mac read the sd card, oddly). But I guess you meant to do it inside of TRWP. Thanks
I rebooted my OnePlus One yesterday and found myself in a weird situation. The phone would go to the initial OnePlus logo then after, a smal android logo with a red warning sign appears for a split second, and I boot into the CM stock recovery. I can't turn it on or enter fastboot, nor can I turn on ADB Debugging on my phone and would really appreciate help as I do not want this phone to be gone. Pretty scared guys, help would be much appreciated!
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
badjoras said:
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
Click to expand...
Click to collapse
Thanks for the prompt response. I think you should also know that I attempted to put a custom recovery on my OPO, but after saying that it worked, I only loaded into the CM Stock Recovery. I do not, have my phone with me at the moment as I did not think it would be necessary to bring to school with me, but I will attempt everything you have said. Thanks for the help so far!
badjoras said:
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
Click to expand...
Click to collapse
I attempted both ways but nothing happens as I press the buttons. It will only boot in the CM Simple Recovery.
NizzleFish98 said:
I attempted both ways but nothing happens as I press the buttons. It will only boot in the CM Simple Recovery.
Click to expand...
Click to collapse
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
badjoras said:
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
Click to expand...
Click to collapse
Yes. It does.
Download the stock image. I'm sure it will be there somewhere in the forums.
Then go to recovery and do the following:
Select 'apply update'. Then you either have the option to apply update from Internal Storage or from adb.
Select adb and enter: adb sideload update_filename.zip
badjoras said:
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
Click to expand...
Click to collapse
assuming it's the stock android recovery, i'm pretty sure it allows for sideloading.
Def sounds like something got flashed to the wrong parition though
Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help
Fireflynj said:
Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help
Click to expand...
Click to collapse
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372
andybones said:
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372
Click to expand...
Click to collapse
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
Download the .exe and click open. Follow directions on the screen. It doesn't get easier, trust me you'll be fine. Wouldn't steer you wrong.
Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk
dottat said:
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:
Fireflynj said:
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:
Click to expand...
Click to collapse
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.
dottat said:
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.
Click to expand...
Click to collapse
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.
Fireflynj said:
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.
Click to expand...
Click to collapse
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yup , that was it, the older one worked.
So dumped the idea of getting KitKat back and I flashed the Marshmallow custom s-off RUU with TWRP that you provided. so far good now I just need to re-root it.
Thank you