Develop Bugs

[Q] need help rooting dinc2 please

so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[

simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder

In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.

im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes

Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk

nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally

drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.

how did you get it too work???

simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....

the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!

yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod

ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2

I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.

nothing is working out for me this is not fun

same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.

yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that

[Q] Looking for stock 4.0.2 nandroid

Does anyone have a nandroid for stock 4.0.2? I've searched the forums but have not come up with anything.
I know what you're thinking =). So before you say anything, no, sorry, due to technical issues the factory image fastboot is not working for me.

and why isn't factory image fastboot working for you?

From what I have read it is not good to restore someone else's nandroid, I imagine it could be even worse for the person providing it to you because it could possibly contain their personal information.

WiredPirate said:
From what I have read it is not good to restore someone else's nandroid, I imagine it could be even worse for the person providing it to you because it could possibly contain their personal information.
Click to expand...
Click to collapse
Some people actually do upload nandroid backups though.... they are purely stock without any information on them. It'd be silly if anyone uploaded their nandroid with all apps/data on it.

I'd say try the mobile odin route if fastboot isn't working

waylo said:
Does anyone have a nandroid for stock 4.0.2? I've searched the forums but have not come up with anything.
I know what you're thinking =). So before you say anything, no, sorry, due to technical issues the factory image fastboot is not working for me.
Click to expand...
Click to collapse
What are the "technical issues" that are affecting your ability to flash the stock 4.0.2 ROM?
And what build are you looking for? Yakju? Yakjuux?
Sent from my Galaxy Nexus using Tapatalk

Why can't you use fastboot? i'd say it's one of the safest ways to get back to 4.0.2.
just follow the guide from http://forum.xda-developers.com/showthread.php?t=1391881 but use an android 4.0.2 image http://code.google.com/android/nexus/images.html
you could try to use ODIN but I actually use Fastboot all the time on my GN.
my milestone has a custom recovery (comparable to ClockworkMOD) and I recently installed some ROMS on Galaxy S's and a Samsung Ace using CM. try to find an "update" to older stock version on that... but please do remember that MD5 codes will not work if you transport a Nandroid from one phone to the other and your'e phone will be screwed up since it's service numbers changes and becomes a duplicate of another registered phone on the network.

It looks like my mobo is dying/failing. Or internal memory. Regardless, something is very very amiss.
See:
http://forum.xda-developers.com/showthread.php?t=1589807
Given the horrendous symptoms the phone has just in recovery, it can't be a ROM issue.
I remember nandroid backups of pure stock with no personal info being more common for other phones, probably because the factory images were not available as they are for the Nexii.
With fastboot, the recovery can be written okay, but the actual ROM data errors out "too many links".
@efrant, either build would be fine. Mine originally came with the "non-google" build whichever that was, but I flashed it over quite quickly.
Of course, getting it onto the /sdcard is another issue. ADB isn't playing very nice either.

amonfog said:
Why can't you use fastboot? i'd say it's one of the safest ways to get back to 4.0.2.
just follow the guide from http://forum.xda-developers.com/showthread.php?t=1391881 but use an android 4.0.2 image http://code.google.com/android/nexus/images.html
you could try to use ODIN but I actually use Fastboot all the time on my GN.
my milestone has a custom recovery (comparable to ClockworkMOD) and I recently installed some ROMS on Galaxy S's and a Samsung Ace using CM. try to find an "update" to older stock version on that... but please do remember that MD5 codes will not work if you transport a Nandroid from one phone to the other and your'e phone will be screwed up since it's service numbers changes and becomes a duplicate of another registered phone on the network.
Click to expand...
Click to collapse
No, restoring someone else's nandroid will not make your phone a clone of the nandroid phone. /factory is not duplicated with nandroid.
The md5 is just of the tar files. With other recoveries (Amon-Ra's for instance) on other phones, there was a lot more altering needed, but it could be done.

waylo said:
It looks like my mobo is dying/failing. Or internal memory. Regardless, something is very very amiss.
See:
http://forum.xda-developers.com/showthread.php?t=1589807
Given the horrendous symptoms the phone has just in recovery, it can't be a ROM issue.
I remember nandroid backups of pure stock with no personal info being more common for other phones, probably because the factory images were not available as they are for the Nexii.
With fastboot, the recovery can be written okay, but the actual ROM data errors out "too many links".
@efrant, either build would be fine. Mine originally came with the "non-google" build whichever that was, but I flashed it over quite quickly.
Of course, getting it onto the /sdcard is another issue. ADB isn't playing very nice either.
Click to expand...
Click to collapse
I personally would try this first, and then do this.
Otherwise, here is your nandroid backup.

Just a question, what's the purpose of the 30 min wait after the final reboot, in the first posted instruction?

waylo said:
Just a question, what's the purpose of the 30 min wait after the final reboot, in the first post?
Click to expand...
Click to collapse
I exagerated a bit there. You shouldn't have to wait 30 mins. It should be more like 5-6 mins, but some people think that the device is not booting properly after waiting a few mins so they pull the battery, so I said wait 30 mins...
By the way, I re-read the first post, and the instructions include what I had linked to in the second link, so ignore that.

WOW
That's some research you did. My search around the internet came up with the same.
sorry guys for that post with clones... my misstake
to re-alocate your MD5 number you can use the following code from the terminal of your ClockworkMod (if you are using that)
Code:
cd /sdcard/clockworkmod/backup/"foldername"
rm nandroid.md5
md5sum *img > nandroid.md5
if you are able to connect to the device using adb use the following string in your command promt
Code:
adb shell
cd /sdcard/clockworkmod/backup/"foldername"
rm nandroid.md5
md5sum *img > nandroid.md5
If nothing works try using another os to get your phone running again. Linux and Mac OS X don't need drivers... so that would be knocking the possibility of driver problems on your computer or your phone.
if nothing works you could try uninstalling the drivers in windows (completely) and restarting your computer. an "android 1.0 device" should pop up in your device manager (after you rebooted your phone to fastboot). but that is a last hope

Thanks for the last ditch hope. I'm guessing there's no harm in trying all this again, it really can't be MORE broken.

amonfog said:
That's some research you did. My search around the internet came up with the same.
sorry guys for that post with clones... my misstake
to re-alocate your MD5 number you can use the following code from the terminal of your ClockworkMod (if you are using that)
Click to expand...
Click to collapse
I apologize if it seemed like I was not appreciating your help. Every thought is appreciated!
On a related note, on the Amon-ra series of recoveries, each backup was saved in a folder which was = the serial #. As I recall (it's been a while since I had my Nexus One) if the whole folder was copied over to another phone, it wouldn't work. The backup would have to be copied into that phone's serial # folder.

waylo said:
Thanks for the last ditch hope. I'm guessing there's no harm in trying all this again, it really can't be MORE broken.
Click to expand...
Click to collapse
Good luck, and let us know how it goes!

Yeah, so this isn't going to work:
F:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
F:\android-sdk\platform-tools>fastboot flash boot 402boot.img
sending 'boot' (4074 KB)...
OKAY [ 0.407s]
writing 'boot'...
OKAY [ 0.249s]
finished. total time: 0.656s
F:\android-sdk\platform-tools>fastboot flash system 402system.img
sending 'system' (317594 KB)...
OKAY [ 31.187s]
writing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 56.860s
Same error occurs with the attempt to flash userdata.img.
So I'm thinking for some reason it's unable to write either system or userdata info. Which supports my theory that the hardware is done broken.
Similarly, recovery is forced to reboot when it tries to restore large files and also when it tries to save a new nandroid.

waylo said:
Yeah, so this isn't going to work:
F:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
F:\android-sdk\platform-tools>fastboot flash boot 402boot.img
sending 'boot' (4074 KB)...
OKAY [ 0.407s]
writing 'boot'...
OKAY [ 0.249s]
finished. total time: 0.656s
F:\android-sdk\platform-tools>fastboot flash system 402system.img
sending 'system' (317594 KB)...
OKAY [ 31.187s]
writing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 56.860s
Same error occurs with the attempt to flash userdata.img.
So I'm thinking for some reason it's unable to write either system or userdata info. Which supports my theory that the hardware is done broken.
Similarly, recovery is forced to reboot when it tries to restore large files and also when it tries to save a new nandroid.
Click to expand...
Click to collapse
The only other suggestions I have for you are as follows:
1) Uninstall your current fastboot driver, and install this one.
2) Reboot your PC and your device.
3) Change USB cables. Use the one that came with the device, or one that came with a Blackberry, or another high-quality one.
4) Download the attachment and use the fastboot.exe file from that.
5) Try flashing the stock images again.
I believe that error has something to do with a connection problem -- either driver related, or cable related, or, in the worst case, hardware related.

Man, stop giving me hope! =)
It was all snuggled up in the original box, waiting for the RMA to come through.
Okay, one more night of fiddling. I'll install all the new drivers on my rarely used laptop and use the usb cable (same one that came with the phone) plugged directly in.

waylo said:
Man, stop giving me hope! =)
It was all snuggled up in the original box, waiting for the RMA to come through.
Okay, one more night of fiddling. I'll install all the new drivers on my rarely used laptop and use the usb cable (same one that came with the phone) plugged directly in.
Click to expand...
Click to collapse
P.S., the attachment in my last post probably won't download for you (it seems like XDA is having problems with attachments site-wide. Try and get a recent copy of fastboot.exe, just in case there are any incompatibilities with the older versions (I know there was a difference in the adb.exe files between newer and older revisions). If you can't find it anywhere (maybe look in the Toolkit thread), you can download it from the Android SDK, or pm me and I'll see if I can upload it somewhere else.

[Q] error: cannot load 'Unlock_code.bin'

Hello everyone, noob here and i ran into a problem. Trying to root my phone through the X_Factor exploit and I'm down to the step to load fastboot flash unlocktoken_code.bin but it keeps throwing the error: cannot load 'Unlock_code.bin' Please help, I also loaded the unlock file into the same file as the others as it stated, under my android file i made. Thanks

X_Factor exploit is for the AT&T One X, not the international One X, so you're either trying to use it on the wrong device or you're posting in the wrong forum.

martymarrr said:
Hello everyone, noob here and i ran into a problem. Trying to root my phone through the X_Factor exploit and I'm down to the step to load fastboot flash unlocktoken_code.bin but it keeps throwing the error: cannot load 'Unlock_code.bin' Please help, I also loaded the unlock file into the same file as the others as it stated, under my android file i made. Thanks
Click to expand...
Click to collapse
this isn't your forum, however you need to specify the unlocktoken_code.bin folder...type:
Code:
fastboot flash path/to/unlocktoken_code.bin

[Q] Unable to upgrade CyanogenMod on HTC One X

I have had installed and updated on a regular basis (Nightlies) CyanogenMod on my HTC One X (unlocked international version)
I have had no problem using the ROM Manager app. However, since February I have not been able to upgrade the ROM and I receive the same error message.
Current CyanogenMod version: 10-20130224-NIGHTLY-endeavoru
Attempting upgrade with file: cm-10.1.0-endeavoru.zip
This is the error message I am receiving:
Installing update…
Assert failed: getprop(“ro.bootloader”)== “1.28.0000” || getprop(“ro.bootloader”) == “1.31.0000” || getprop(“ro.bootloader”) == “1.33.0000” || getprop(“ro.bootloader”) == “1.36.0000” || getprop(“ro.bootloader”) == “1.39.0000”
E:Error in /sdcard/clockworkmod/download/get.cm/get/jenkins/32363/cm-10.1.0-endeavoru.zip
(Status 7)
Installation aborted.
Same message when trying to update with file cm-10.1.0-RC5- endeavoru.zip
E:Error in /sdcard/cmupdater/cm-10.1.0-RC5- endeavoru.zip
What is blocking me from updating?
Thanks

try to download it manually and flash it straight from recovery

I am guessing that your bootloader is to low !
Give the outcome of the following fastboot command
Fastboot getvar version-main

Mr Hofs said:
I am guessing that your bootloader is to low !
Give the outcome of the following fastboot command
Fastboot getvar version-main
Click to expand...
Click to collapse
Is there a solution for if this is the case? A very similar thing happened to my phone. I even deleted the asserts from the file so it didn't check for phone type or bootloader and it still wouldn't update, only now it isn't a status 7 error, it just says failed. So, is there anything that can be done, or am I just finished.

tendorphin said:
Is there a solution for if this is the case? A very similar thing happened to my phone. I even deleted the asserts from the file so it didn't check for phone type or bootloader and it still wouldn't update, only now it isn't a status 7 error, it just says failed. So, is there anything that can be done, or am I just finished.
Click to expand...
Click to collapse
Paste here the output of the following command
Code:
fastboot getvar all

matt95 said:
Paste here the output of the following command
Code:
fastboot getvar all
Click to expand...
Click to collapse
I tried, I can't get drivers to work...HTC One X on Windows 8 64 bit. I run it and it just says 'waiting for device.' Can you explain if there is a solution at all, and where I can find it without the information from running the fastboot getvar all?

tendorphin said:
I tried, I can't get drivers to work...HTC One X on Windows 8 64 bit. I run it and it just says 'waiting for device.' Can you explain if there is a solution at all, and where I can find it without the information from running the fastboot getvar all?
Click to expand...
Click to collapse
Well in fastboot modee it should be working good with the drivers too

tendorphin said:
I tried, I can't get drivers to work...HTC One X on Windows 8 64 bit. I run it and it just says 'waiting for device.' Can you explain if there is a solution at all, and where I can find it without the information from running the fastboot getvar all?
Click to expand...
Click to collapse
Open device manager while phone is in a fast boot, there will be one with a ! Right click and update (search online for updates)
My windows 8 installed drivers when I connected phone in fastboot by itself.
Sent from my HTC One X using xda app-developers app

treebill said:
Open device manager while phone is in a fast boot, there will be one with a ! Right click and update (search online for updates)
My windows 8 installed drivers when I connected phone in fastboot by itself.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I got excited because it took a little while to look, but it didn't find any drivers. I've downloaded htc sync manager, i've downloaded isolated drivers, nothing will work. I might have to just deal with it. However, I still haven't been told if there is any kind of solution for the main problem this thread is about. I'm not asking for exact steps on how to solve it (though that would be nice) I'm just asking if there is anything at all that can be done. I assume there is because people asked for more information about the problem, but nobody has said if there is a solution or what it might be. I work in IT so I understand that a solution cannot be provided without enough information, but I also know that guesses and estimates can be made as to what might be the root problem, or what a potential solution might be. I'm sorry if I seem unappreciative, I'm not, I appreciate all the help you're all trying to give, I'm just getting very frustrated that my question is essentially going unanswered.

tendorphin said:
I got excited because it took a little while to look, but it didn't find any drivers. I've downloaded htc sync manager, i've downloaded isolated drivers, nothing will work. I might have to just deal with it. However, I still haven't been told if there is any kind of solution for the main problem this thread is about. I'm not asking for exact steps on how to solve it (though that would be nice) I'm just asking if there is anything at all that can be done. I assume there is because people asked for more information about the problem, but nobody has said if there is a solution or what it might be. I work in IT so I understand that a solution cannot be provided without enough information, but I also know that guesses and estimates can be made as to what might be the root problem, or what a potential solution might be. I'm sorry if I seem unappreciative, I'm not, I appreciate all the help you're all trying to give, I'm just getting very frustrated that my question is essentially going unanswered.
Click to expand...
Click to collapse
The second post in this thread told you...manual install in recovery but you need fastboot to update hboot and flash boot.img.

Tigerlight said:
The second post in this thread told you...manual install in recovery but you need fastboot to update hboot and flash boot.img.
Click to expand...
Click to collapse
Ok, I'm sorry, I forgot that was listed there, but my problem goes a bit further. I didn't clarify it very well upon a second reading so I'm sorry for that frustration-driven outburst.
I have tried manually installing and I got the status 7 error. I went into the files and edited them to remove the asserts so it didn't check for phone type or bootloader so it should just install. However, now when I try to manually install I just get a message that says failed, but doesn't give a reason why. No status 7, no error code at all, nothing.
Once again, I'm sorry for snapping, I'm just getting so frustrated because, as far as I can see, this has no actual reason to not work.

tendorphin said:
Ok, I'm sorry, I forgot that was listed there, but my problem goes a bit further. I didn't clarify it very well upon a second reading so I'm sorry for that frustration-driven outburst.
I have tried manually installing and I got the status 7 error. I went into the files and edited them to remove the asserts so it didn't check for phone type or bootloader so it should just install. However, now when I try to manually install I just get a message that says failed, but doesn't give a reason why. No status 7, no error code at all, nothing.
Once again, I'm sorry for snapping, I'm just getting so frustrated because, as far as I can see, this has no actual reason to not work.
Click to expand...
Click to collapse
You cannot install without the asserts, period.
It MUST check hboot version which is what the "Assert failed: getprop(“ro.bootloader”)== “1.28.0000” || getprop(“ro.bootloader”) == “1.31.0000” || getprop(“ro.bootloader”) == “1.33.0000” || getprop(“ro.bootloader”) == “1.36.0000” || getprop(“ro.bootloader”) == “1.39.0000”
E:Error in /sdcard/clockworkmod/download/get.cm/get/jenkins/32363/cm-10.1.0-endeavoru.zip
(Status 7)" is doing.
Your hboot version obviously does not meet the minimum v1.28 required.
You MUST find a method of installing fastboot drivers before you can go ANY further in this process.
I am quite sure it has been solved somewhere. Google is your friend.

Mr Hofs said:
I am guessing that your bootloader is to low !
Give the outcome of the following fastboot command
Fastboot getvar version-main
Click to expand...
Click to collapse
Okay what number would mean that the bootloader is too low?
AND more importantly how do I correct/change that?
Thanks

[Q] File Size and ADB

I have unlocked, rooted with TWRP recovery and S-Off ATT&T HTC One M8 but when I tried to fastboot flash I got a message telling me: "target reported max download size of 1830711296 bytes
error: cannot load 'RUU-HTC_One_M8_GE-1.16.1700.16_rooted': No error
It does seem like a large file. I'm not sure if I did something wrong or not. Anyone have any advice?

DwadeCham said:
I have unlocked, rooted with TWRP recovery and S-Off ATT&T HTC One M8 but when I tried to fastboot flash I got a message telling me: "target reported max download size of 1830711296 bytes
error: cannot load 'RUU-HTC_One_M8_GE-1.16.1700.16_rooted': No error
It does seem like a large file. I'm not sure if I did something wrong or not. Anyone have any advice?
Click to expand...
Click to collapse
From the file name that appears to be an RUU. I believe they have to be run in Windows and the phone either booted to android or at the boatloader screen not flashed in Fastboot.
Sent from my HTC One_M8 using Tapatalk

lampel said:
From the file name that appears to be an RUU. I believe they have to be run in Windows and the phone either booted to android or at the boatloader screen not flashed in Fastboot.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. I thought I was following all the directions of the OP pretty closely. Don't know where to go now.

lampel said:
From the file name that appears to be an RUU. I believe they have to be run in Windows and the phone either booted to android or at the boatloader screen not flashed in Fastboot.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
These are the instructions in the op:
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
you will the following message:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
Code:
fastboot reboot

Why does your file have "_rooted" at the end while OP is normal ?!? Are you sure you are trying to load same file ?

v-b-n said:
Why does your file have "_rooted" at the end while OP is normal ?!? Are you sure you are trying to load same file ?
Click to expand...
Click to collapse
There are two files. One for a non rooted device and one that has already been rooted. I had already rooted.
Sent from my HTC One_M8 using XDA Free mobile app

v-b-n said:
Why does your file have "_rooted" at the end while OP is normal ?!? Are you sure you are trying to load same file ?
Click to expand...
Click to collapse
I am going to add the .zip extension and try again. Thanks for the help.
Sent from my HTC One_M8 using XDA Free mobile app

Thanks!
v-b-n said:
Why does your file have "_rooted" at the end while OP is normal ?!? Are you sure you are trying to load same file ?
Click to expand...
Click to collapse
Hey man! Thanks! I know that you asked a question but that steered me in the right direction. I added the .zip extension at the end of the filename in my command window and Bam! I never would have thought I had to add the file extension but that worked like a champ and I have converted my HTC One M8 to GPE. Feels like my old Gnex now except for the battery life and speed.
Thanks again!