Q&A for RUU M8_VZW files (s-off only)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for RUU M8_VZW files (s-off only). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
SuperSU issue
When I try to run SuperSU it shows up with this message "There is no SU binary installed, and SuperSU cannot install it. This is a problem! I was wondering if there is anyway I can get a modified version of the ROM without root so I can full root it on my own. Thanks.
Superboyman said:
When I try to run SuperSU it shows up with this message "There is no SU binary installed, and SuperSU cannot install it. This is a problem! I was wondering if there is anyway I can get a modified version of the ROM without root so I can full root it on my own. Thanks.
Click to expand...
Click to collapse
If you ran this properly it would be fully rooted no need to flash binaries or root. How are you flashing the ruu?
Response
dottat said:
If you ran this properly it would be fully rooted no need to flash binaries or root. How are you flashing the ruu?
Click to expand...
Click to collapse
fastboot with ADB.
Superboyman said:
fastboot with ADB.
Click to expand...
Click to collapse
Fastboot only. No adb involved. Did you this once or twice? Via fastboot you often have to run twice as it does not hit all the partitions in one shot.
2nd Response
dottat said:
If you ran this properly it would be fully rooted no need to flash binaries or root. How are you flashing the ruu?
Click to expand...
Click to collapse
All I need this ROM to do is get me back to full stock without Root so I can get back to where I was earlier before I screwed all of this up.
Superboyman said:
All I need this ROM to do is get me back to full stock without Root so I can get back to where I was earlier before I screwed all of this up.
Click to expand...
Click to collapse
Sending you a pm. Need more info on this one...
---------- Post added at 10:32 PM ---------- Previous post was at 10:20 PM ----------
Superboyman said:
All I need this ROM to do is get me back to full stock without Root so I can get back to where I was earlier before I screwed all of this up.
Click to expand...
Click to collapse
Sent you a pm with my hangouts address. In the meantime you should be using this one.
http://forum.xda-developers.com/showthread.php?t=2873144
RUU M8_VZW 4.4.3 (s-off only)(newest)
Response
If I can get this RUU without SuperSU that would fix all my problems, I need it without SuperSU so I can gain temp root on my phone to use firewater to gain s-off (I know that it isn't suppose to work but it does because I can do everything fine except SuperSU) and then I can install TWRP and install a permanent root. Can you give me a guide on how to remove SuperSU from the ROM's zip?
If I wanted to return my phone back to stock as possible would I flash this, then uninstall superuser then do the writesecure command to relock boot loader?
jsminnis said:
If I wanted to return my phone back to stock as possible would I flash this, then uninstall superuser then do the writesecure command to relock boot loader?
Click to expand...
Click to collapse
I answered this over in the main thread.
dottat said:
I answered this over in the main thread.
Click to expand...
Click to collapse
Lol, just realized you changed my quoted text. Thanks.
I've gotten to the last part where you flash the RUU file, but for some reason I'm still getting this error: cannot load 'RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip'
I'm using a Mac and have made sure everything is correct up until this point, i've tried re-naming the file, making sure that it wasn't a double extension etc.. and it still doesn't seem to recognise it. Plus i'm certain that Terminal is pointing to where the file is placed (in platform-tools)
Any help greatly appreciated
Edit: solved. I had to include the entire location link for the ruu file (Users/ etc..) etc even though Terminal was already looking in platform-tools.
Your RUU rocks!
Thank you so much. Your RUU rocks!
My phone was messed up because I used the stupid LTE On/Off tool to switch between networks. It completely messed up my radio. I did not have signal anymore. I flashed other ROMs but the issue was not resolved. In trouble shooting section @digitalhigh said the some radio problems on HTC are caused by a corrupted NV partition. I followed his instruction to go back to the my base stock ROM and your RUU was a miracle. I used method 2. It worked like a charm. I then I used stock recovery to do a data/factory reset. It restored the NV partition. Now, my phone works again!
Thank you for the great job!
Can someone post the model id and cid on a stock Verizon HTC M8 32GB? Thank you.
BlackKnight23 said:
Can someone post the model id and cid on a stock Verizon HTC M8 32GB? Thank you.
Click to expand...
Click to collapse
VZW__001
0P6B20000
Let me know if you have any issues.
What firmware do we need for Viper Lolipop on vzw?
dottat said:
VZW__001
0P6B20000
Let me know if you have any issues.
Click to expand...
Click to collapse
Thats what I was looking for, thank you! I am having issues but not due to you. I changed my mid and cid trying everything to convert to GPE without success so I had to modify the android-text file to have my model but still didnt seem to want to work. I just found the rom I wanted to try and used TWRP to flash to it. I got it to work.
BlackKnight23 said:
Thats what I was looking for, thank you! I am having issues but not due to you. I changed my mid and cid trying everything to convert to GPE without success so I had to modify the android-text file to have my model but still didnt seem to want to work. I just found the rom I wanted to try and used TWRP to flash to it. I got it to work.
Click to expand...
Click to collapse
I have a tool that we can change them straight back to those if you want. No DD/ADB commands.
dottat said:
I have a tool that we can change them straight back to those if you want. No DD/ADB commands.
Click to expand...
Click to collapse
That would be awesome. I'll PM you my email. Thank you!
Everything flashed OK. Phones fine except for BT cutting off every now and then. Was curious if anyone one knows why my firmware version is in red parenthesis ?
It reads:
3.28.605. (4.17.605.5)
and it's in red not green
Had a few errors while flashing. Too
Sent from my One M8 using Tapatalk
Related
For Dev's reference
stock recovery here
Onepagebook said:
For Dev's reference
stock recovery here
Click to expand...
Click to collapse
Version: 0.89.997.1 CL144629 test-keys
ro.build.date=六 12月 29 01:11:35 CST 2012
ClockworkMod Recovery! Well whenever the phone gets released. I attempted to build a test version of CWM at http://forum.xda-developers.com/showthread.php?t=2173863
Fingers crossed that it works.
But I will probably need someone to give me these two items once they get a phone to correct the configs.
Post the file /proc/partitions
Post the file /proc/mounts
For the adb commands. "adb shell" then "cat /proc/partitions" and "cat /proc/mounts" Should work.
EDIT: Thank you to he_stheone64 for giving me what I need above. Now I can make a fully working recovery.
To get back on topic, here's the fstab extracted from the recovery
http://pastebin.com/tBzTE4GA
Hey guys.
Nice to see all of you to be getting the HTC One
But lets not turn this to a conversation thread please.
Thread cleaned.
Cheers
Pardon me, but is this the same stock recovery as the AT&T version?
robstunner said:
Pardon me, but is this the same stock recovery as the AT&T version?
Click to expand...
Click to collapse
I'm sure it's not.
mike1986. said:
I'm sure it's not.
Click to expand...
Click to collapse
Darn, accidentally flashed CWM Touch when I was just looking to unlock and root. Oh well, no biggie. Thanks for the quick reply!
mike1986. said:
I'm sure it's not.
Click to expand...
Click to collapse
Looking at this string, my guess it's stock recovery for the M7_U: ro.build.date=六 12月 29 01:11:35 CST 2012
can i use it to flash my htc one dev edition?? im on 1.29.1540.3
so?????????
eltoffer said:
can i use it to flash my htc one dev edition?? im on 1.29.1540.3
Click to expand...
Click to collapse
Why would you use this? Go read some guides and then flash either twrp or cwm.
Sent from my HTC One
ECEXCURSION said:
Why would you use this? Go read some guides and then flash either twrp or cwm.
Sent from my HTC One
Click to expand...
Click to collapse
just curious, to get updates
My device has T-Mobile UK firmware (1.28.61.7) and I will be looking to go back to stock soon to hopefully receive official 1.29 firmware update.
I need the appropriate recovery for my device but am not quite sure what that is. I have a nandroid but this was done in CWM after rooting.
Is the recovery of 1.29 different to 1.28 and do I need a T-Mobile specific recovery or is the generic recovery just the same?
If somebody could point me in the direction of the recovery I require it would be much appreciated.
Onepagebook said:
For Dev's reference
stock recovery here
Click to expand...
Click to collapse
Hi Bro, Do you have STOCK Recovery for ONE Developer Edition ??
Regards,
hi there,
is the recovery can be installed for HTC ONE M7 802W?
mahesh_9j said:
Hi Bro, Do you have STOCK Recovery for ONE Developer Edition ??
Regards,
Click to expand...
Click to collapse
recovery files are all the same
Onepagebook said:
recovery files are all the same
Click to expand...
Click to collapse
Are you 100% sure??
I am trying to return my 1.28.61.7 device to stock using a rooted nandroid which I made without any other modifications. After many trials and tribulations, I managed to unroot by removing SuperSU and binaries but, after installing 'stock' recovery my device still says relocked and tampered and will not boot into recovery.
I am, however, able to perform a full wipe from within android though.
I would really like complete clarity on this if anyone can help me as I need to get back to stock to get an official update when it appears as there are no stock nandroids available or any RUU's for my device.
bobsie41 said:
Are you 100% sure??
I am trying to return my 1.28.61.7 device to stock using a rooted nandroid which I made without any other modifications. After many trials and tribulations, I managed to unroot by removing SuperSU and binaries but, after installing 'stock' recovery my device still says relocked and tampered and will not boot into recovery.
I am, however, able to perform a full wipe from within android though.
I would really like complete clarity on this if anyone can help me as I need to get back to stock to get an official update when it appears as there are no stock nandroids available or any RUU's for my device.
Click to expand...
Click to collapse
no problem, here is the US dev edition stock recovery-signed
http://d-h.st/b5g
Tampered showed @ hboot is because you have "unlocked" before
So If I have clockwork mod touch recovery installed and I want to go back to stock recovery without loosing my app and data I can just flash this in cwm?
Sent from my HTC One using xda app-developers app
nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
I am unlocked and rooted but the download from verizon automatically started. It did nothing after it was done downloading. I dont know what to expect of this?? I am on viper rom 2.5.
Here's the link folks
https://www.androidfilehost.com/?fid=95747613655049317
Only for stock recovery and untouched system users
dottat said:
Here's the link folks
https://www.androidfilehost.com/?fid=95747613655049317
Only for stock recovery and untouched system users
Click to expand...
Click to collapse
Hey dottat what is the correct directory that the file gets saved to on the phone?
lucky_strike33 said:
I am unlocked and rooted but the download from verizon automatically started. It did nothing after it was done downloading. I dont know what to expect of this?? I am on viper rom 2.5.
Click to expand...
Click to collapse
Won't flash if you have custom recovery or modified system.
krazie1 said:
Hey dottat what is the correct directory that the file gets saved to on the phone?
Click to expand...
Click to collapse
/cache/fumo
dottat said:
Won't flash if you have custom recovery or modified system.
Click to expand...
Click to collapse
Thank you!
Sent from my HTC6525LVW using XDA Premium HD app
Is there a full change log somewhere?
all good here, just reflashed @dottats RUU and updated the organic way. SOFF is good, it even says official in the software status in HBOOT
hboot- 3.19.0.0000
radio- 1.09.20.0926
dsp - v46.2.2-00564-m8974_F0.0811
os- 3.28.605.4
dottat said:
nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
Click to expand...
Click to collapse
Ready for that RUU.... It saved me 1,000 million times...
JB_Da_Greatest said:
Ready for that RUU.... It saved me 1,000 million times...
Click to expand...
Click to collapse
You can just use the 4.4.3 ruu and do the OTA, then your firmware is done all in 1 shot
can someone upload a 4.4.4 system dump? or point me to one if someone has already? thanks!
I have looked around and found all kinds of different answers so can someone here help me out a bit?
I got the phone when it first came out, have S-OFF, root, TWRP custom recovery but have version 4.4.2 still installed with everything being left pretty much stock. I would prefer to keep things pretty much stock so what would I need to do to update to 4.4.4? Do I need to get 4.4.3 first? Do I need to flash stock recovery first before doing anything? Anything with firmware or radios?
Resputan said:
I have looked around and found all kinds of different answers so can someone here help me out a bit?
I got the phone when it first came out, have S-OFF, root, TWRP custom recovery but have version 4.4.2 still installed with everything being left pretty much stock. I would prefer to keep things pretty much stock so what would I need to do to update to 4.4.4? Do I need to get 4.4.3 first? Do I need to flash stock recovery first before doing anything? Anything with firmware or radios?
Click to expand...
Click to collapse
well, this is my idea for you
1. Flash the stock 4.4.2 recovery over the TWRP, then just do the OTA's
aer0zer0 said:
well, this is my idea for you
1. Flash the stock 4.4.2 recovery over the TWRP, then just do the OTA's
Click to expand...
Click to collapse
Reasonable enough, sorry if this is another dumb question but I havent been paying much attention to these boards since I rooted, I see that recent phones require Sunshine to root, is that because of the firewater method being patched via a software update (4.4.3?) or some other manufacturer change that I shouldnt be concerned with if the old root method already works for me?
aer0zer0 said:
You can just use the 4.4.3 ruu and do the OTA, then your firmware is done all in 1 shot
Click to expand...
Click to collapse
I already updated... I was just saying for safe keeping just in case I get in some unforseen trouble.
Go here http://forum.xda-developers.com/showthread.php?t=2723159 and just flash the 4.4.3 with not boot img. YOu dont need to flash the recovery to accept ota's. YOu can just flash this and you will get the updated radios and h boot.http://forum.xda-developers.com/showthread.php?t=2723159
Downloaded OTA and updated, they added file manager and flashlight back ~!
JB_Da_Greatest said:
I already updated... I was just saying for safe keeping just in case I get in some unforseen trouble.
Click to expand...
Click to collapse
yup, its saved a billion times too
---------- Post added at 02:17 PM ---------- Previous post was at 02:16 PM ----------
lchupacabras said:
Downloaded OTA and updated, they added file manager and flashlight back ~!
Click to expand...
Click to collapse
i know, right that was such an awesome surprise
---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------
Resputan said:
Reasonable enough, sorry if this is another dumb question but I havent been paying much attention to these boards since I rooted, I see that recent phones require Sunshine to root, is that because of the firewater method being patched via a software update (4.4.3?) or some other manufacturer change that I shouldnt be concerned with if the old root method already works for me?
Click to expand...
Click to collapse
nope, if your already SOFF, you will stay SOFF. might break your root, but all you need to do is reinstall supersu when you put twrp back on
dottat said:
nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
Click to expand...
Click to collapse
Hi dootat, Hope you remember me. You help me restore my mobile Via team viewer. Thanks for the RUU i am trying to flash but nothing going. Copy zip to SD card rename to 0p6bimg.zip and hit Hboot. i can see it installing and then ask for reboot but when check in mobile still 4.4.3. Any help?
thanks
Best regards
I've rooted my phone and having TWRP Recovery but due to S-On i'm unable to make any changes on my root folders. I've tried many times with firewater and rumrunner but both are unable to S-Off my phone.. i've attached the image of message showing while doing with firewater. Error exist at last step. Due to S-On unable to fix the SD card permission, unable to Update SU Binary, Unable to change bootanimation, unable to Download Busybox, Unable to install Xposed Framework, unable to use adaway and many more thing (Only flashing works). :crying::crying::crying: I'll very thankful to you if you please help me.
Thanking YOU
cjmaaz said:
I've rooted my phone and having TWRP Recovery but due to S-On i'm unable to make any changes on my root folders. I've tried many times with firewater and rumrunner but both are unable to S-Off my phone.. i've attached the image of message showing while doing with firewater. Error exist at last step. Due to S-On unable to fix the SD card permission, unable to Update SU Binary, Unable to change bootanimation, unable to Download Busybox, Unable to install Xposed Framework, unable to use adaway and many more thing (Only flashing works). :crying::crying::crying: I'll very thankful to you if you please help me.
Thanking YOU
Click to expand...
Click to collapse
I can't get you s-off but I can help you with root issues.
Do a twrp backup first especially the kernel.
Now flash my boot.img . The system write protection is off in this boot.img so root will work perfectly.
But still firewater does not work on my boot.img so no s-off.
iamsuperuser said:
I can't get you s-off but I can help you with root issues.
Do a twrp backup first especially the kernel.
Now flash my boot.img . The system write protection is off in this boot.img so root will work perfectly.
But still firewater does not work on my boot.img so no s-off.
Click to expand...
Click to collapse
Thanks, Now I need to do S-Off, will it (firewater etc) work if I flash any other kernel?
What do you need S-Off for? After installing the kernel you can write to /system.
crystal_ball said:
What do you need S-Off for? After installing the kernel you can write to /system.
Click to expand...
Click to collapse
Seen in list of requirement in one Chinese ROM
iamsuperuser said:
I can't get you s-off but I can help you with root issues.
Do a twrp backup first especially the kernel.
Now flash my boot.img . The system write protection is off in this boot.img so root will work perfectly.
But still firewater does not work on my boot.img so no s-off.
Click to expand...
Click to collapse
I'm looking to get write protection off so this looks perfect for me! Is it limited to a specific variant of E8 though? I've got a China Unicom HTC One E8 dual sim (M8sw). You reckon the kernel will work with mine?
mongastein said:
I'm looking to get write protection off so this looks perfect for me! Is it limited to a specific variant of E8 though? I've got a China Unicom HTC One E8 dual sim (M8sw). You reckon the kernel will work with mine?
Click to expand...
Click to collapse
I'm not sure just try it but please make a backup first.
cjmaaz said:
I've rooted my phone and having TWRP Recovery but due to S-On i'm unable to make any changes on my root folders. I've tried many times with firewater and rumrunner but both are unable to S-Off my phone.. i've attached the image of message showing while doing with firewater. Error exist at last step. Due to S-On unable to fix the SD card permission, unable to Update SU Binary, Unable to change bootanimation, unable to Download Busybox, Unable to install Xposed Framework, unable to use adaway and many more thing (Only flashing works). :crying::crying::crying: I'll very thankful to you if you please help me.
Thanking YOU
Click to expand...
Click to collapse
it seems S-off is achievable with the use of sunshine only. I did it on my M8sw to go from Chinese to Indian rom.
Sunshine costs 25US$. And license is only for one device to toggle s-off and s-on.
there is no other way to the best of my knowledge as HTC patched against firewater.
iamsuperuser said:
I'm not sure just try it but please make a backup first.
Click to expand...
Click to collapse
I've got TWRP and made a nandroid backup, so I should be able to get back even if I flash a incompatible boot.img right? Apologies for my paranoia. Right, going to give it a go tonight. Thanks for the file!
mongastein said:
I've got TWRP and made a nandroid backup, so I should be able to get back even if I flash a incompatible boot.img right? Apologies for my paranoia. Right, going to give it a go tonight. Thanks for the file!
Click to expand...
Click to collapse
The kernel is compatible with mec_dwgl variant of E8.
U can check it in the fastboot mode where it shows s-off or s-on
I think China Unicom M8Sw devices are mec_dugl so may not work.
Try the ones at the end if THIS post
cjmaaz said:
I've rooted my phone and having TWRP Recovery but due to S-On i'm unable to make any changes on my root folders. I've tried many times with firewater and rumrunner but both are unable to S-Off my phone.. i've attached the image of message showing while doing with firewater. Error exist at last step. Due to S-On unable to fix the SD card permission, unable to Update SU Binary, Unable to change bootanimation, unable to Download Busybox, Unable to install Xposed Framework, unable to use adaway and many more thing (Only flashing works). :crying::crying::crying: I'll very thankful to you if you please help me.
Thanking YOU
Click to expand...
Click to collapse
Did you end up getting your phone get sorted out? I had to flash busybox instead of using one of those installer apps (although Busybox on Rails was useful for checking if I had flashed an appropriate one). Only the first one here http://forum.xda-developers.com/showthread.php?t=1929852 worked for me though.
---------- Post added at 12:29 AM ---------- Previous post was at 12:23 AM ----------
iamsuperuser said:
The kernel is compatible with mec_dwgl variant of E8.
U can check it in the fastboot mode where it shows s-off or s-on
I think China Unicom M8Sw devices are mec_dugl so may not work.
Try the ones at the end if THIS post
Click to expand...
Click to collapse
Thanks mate, you saved me a lot of grief from installing an incompatible one! I must be doing something wrong on my end though since flashing the boot.img from that other thread still didn't remove the write protection, but at least it did no harm at all since it was compatible as you rightly pointed out. Will keep looking.
mongastein said:
Thanks mate, you saved me a lot of grief from installing an incompatible one! I must be doing something wrong on my end though since flashing the boot.img from that other thread still didn't remove the write protection, but at least it did no harm at all since it was compatible as you rightly pointed out. Will keep looking.
Click to expand...
Click to collapse
Clearly we did not look HERE
The link in the above post is dead but it says it is for china unicom and sys is r/w. :good:
HERE is the new link. :good:
mongastein said:
I've got TWRP and made a nandroid backup, so I should be able to get back even if I flash a incompatible boot.img right? Apologies for my paranoia. Right, going to give it a go tonight. Thanks for the file!
Click to expand...
Click to collapse
And also working good on my m8sd.
iamsuperuser said:
Clearly we did not look HERE
The link in the above post is dead but it says it is for china unicom and sys is r/w. :good:
HERE is the new link. :good:
Click to expand...
Click to collapse
So, after I flashed this kernel, can I change my firmware?
presario3839 said:
So, after I flashed this kernel, can I change my firmware?
Click to expand...
Click to collapse
No, you can't. It only remove system protection. Only signed firmware can flashed with S-On. Sunshine can s-off your device. But it costs 25$ or wait for signed RUU to roll out of lollipop, if you want to use Bindroided Lollipop with sense 7 Rom. If you want to use sunshine, flash the stock downgraded Rom. Sunshine can't work with custom kernel. and If you want to change directly through root explorer, I don't know what will happen. Edit it through ES File explorer mounting RW but I can't guarantee that it will work or not brick your device.
My opinion: Go through Sunshine. It will lighten your path.
Q&A for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
billblack said:
Long time lurker. I read and can use Google . Regardless, it failed and scared the crap out of me as it wouldn't boot. Got back into boot loader, fired up EXE again and it seems to have finished the 2nd time. A few more grey hairs, but all is good my friend. Thanks.
Click to expand...
Click to collapse
Same thing happened to me! Failed the first time around, worked the second. Booting now and it appears to be working (Android is upgrading...)
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
EXE/ZIP RUU M8_VZW 5.0.1 Help
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
mbarcus said:
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
Click to expand...
Click to collapse
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
dottat said:
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
Click to expand...
Click to collapse
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
mbarcus said:
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
Click to expand...
Click to collapse
recovery doesnt' weigh in here. You can install it from bootloader using the SD card method.
How do I flash L Hboot? with twrp? do I have to flash it or can I just use the ruu to get to the new 5.0.1 firmware? thanks
So you asked to report our experience ...
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
A_Levis said:
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
Click to expand...
Click to collapse
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
..
dottat said:
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
Click to expand...
Click to collapse
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
A_Levis said:
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
Click to expand...
Click to collapse
Most recoveries will offer to flash su on an unrooted rom. You can either do that or manually flash the newest supersu.zip After you boot up you can install busybox from an app like this... https://play.google.com/store/apps/details?id=stericson.busybox
So what rom/firmware are you currently on?
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
Nickchapstick said:
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
Click to expand...
Click to collapse
After looking for a little bit, it appears I'm having a similar issue.
klw7890 said:
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
After looking for a little bit, it appears I'm having a similar issue.
Click to expand...
Click to collapse
You were able to boot up the OS successfully the first time right?
dottat said:
You were able to boot up the OS successfully the first time right?
Click to expand...
Click to collapse
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
klw7890 said:
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
Click to expand...
Click to collapse
Stock recovery?
dottat said:
Stock recovery?
Click to expand...
Click to collapse
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
klw7890 said:
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
Click to expand...
Click to collapse
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
dottat said:
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
Click to expand...
Click to collapse
"That app" being TWRP Manager?
Trying to keep this short but i seem to have messed up. I was trying to get back to stock with this phone so i've been trying to use the RUU to flash back to stock. I keep getting the 22 RU_HEADER_ERROR when i try the RUU sd card method but i read on here that you may need S off to make it work. I was in the process of flashing a custom rom (Bad Boyz rom) just so i can be rooted so that sunshine would work but system won't mount. Looking for options before i mess more stuff up
DarkmanXTC said:
Trying to keep this short but i seem to have messed up. I was trying to get back to stock with this phone so i've been trying to use the RUU to flash back to stock. I keep getting the 22 RU_HEADER_ERROR when i try the RUU sd card method but i read on here that you may need S off to make it work. I was in the process of flashing a custom rom (Bad Boyz rom) just so i can be rooted so that sunshine would work but system won't mount. Looking for options before i mess more stuff up
Click to expand...
Click to collapse
If you flash a RUU that matches your cid/mid you don't need s-off. At least when you upgrade your OS Version and not downgrade.
A "fastboot getvar all" will help us to provide you a correct RUU version, if there is one.
About the system not mouning:
you most likely checked in twrp to mount system as readonly.
TWRP-MOUNT: Uncheck "Mount system read only"
I have the correct version but i keep getting the above error.
Also i did uncheck read only for mount system. I think i may have messed up something when i relocked the bootloader with custom rom and recovery then unlocked it again. I must have messed up something then. The ruu seems the only option. I'm trying to flash the same one i have installed which is the 1.28.617.6 on the spread sheet for the us phone but keep getting the error. You said i need s off to downgrade but not to upgrade. So do i have to wait for newer software?
Seems more like it you have a bad download. Did you check the md5 of your download?
Yep, bad download.
Also, why do people re-lock the bootloader? I don't see any gain from doing this.
Sent from my HTC U11 using Tapatalk
aliveanddead86 said:
Yep, bad download.
Also, why do people re-lock the bootloader? I don't see any gain from doing this.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
agree, unlocked bootloader breaks safety net. So if you decide to return back to stock/non rooted you would need to relock to be able to pass Safety Net again.
That would be the only reason for me.
j to the 4n said:
Seems more like it you have a bad download. Did you check the md5 of your download?
Click to expand...
Click to collapse
Sorry been away. Yes i checked it, downloaded it more than once to be sure and checked it in cmd. Now to be sure on the HTC U11 google doc spreedsheet, the RUU (https://docs.google.com/spreadsheet...EYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=2137120377) is the recovery option at the bottom right? Thats what i been downloading, at this point i could be messing something up
DarkmanXTC said:
Sorry been away. Yes i checked it, downloaded it more than once to be sure and checked it in cmd. Now to be sure on the HTC U11 google doc spreedsheet, the RUU (https://docs.google.com/spreadsheet...EYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=2137120377) is the recovery option at the bottom right? Thats what i been downloading, at this point i could be messing something up
Click to expand...
Click to collapse
No, it is on the first tab what you need.
j to the 4n said:
No, it is on the first tab what you need.
Click to expand...
Click to collapse
Thanks i just got it. It took me awhile to notice that recovery its talking about the stock recovery not the RUU. i just flashed it. Thanks for the help
DarkmanXTC said:
Thanks i just got it. It took me awhile to notice that recovery its talking about the stock recovery not the RUU. i just flashed it. Thanks for the help
Click to expand...
Click to collapse
you are welcome.