VZW Kernel/Recovery/System/Flashable Radio - HTC One Max

For use on Verizon variant HTC ONE MAX only!!!
S-off users only!!!!
Software version 1.11.605.4
Stock Recovery-
http://www.androidfilehost.com/?fid=23252070760974293
flash via fastboot
fastboot flash recovery recovery.img
Stock Kernel (insecure)-
http://www.androidfilehost.com/?fid=23252070760974294
flash via fastboot
fastboot flash boot boot.img
System Image (must unrar first to get system.img)
http://www.androidfilehost.com/?fid=23252070760974295
flash via fastboot
fastboot flash system system.img
Flashable radio-
download this:
https://www.mediafire.com/?ucj15e2zavewnbq
vzw_max_radio.zip ba7f0302040731949a4db3cb0c9c4e98
double check the md5 matches above.
flash in ruu mode:
-phone in fastboot
-open cmd
-enter:
fastboot devices
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip vzw_max_radio.zip
fastboot reboot-bootloader
if you see a baseband in the bootloader screen now,thats a good sign
fastboot reboot
Credits- Scotty1223 for working his radio magic
Jiggity Janx - afh mirrors

Awesome sauce, thank you :good:

@dottat is it possible to write a script for those for the n00bs that may be the faint of heart type? Like a flash-all deal? I'm good with manually flashing them all individually but for those that aren't that would be dope.. Can you even do that with the .img's for HTC devices?

Murrda said:
@dottat is it possible to write a script for those for the n00bs that may be the faint of heart type? Like a flash-all deal? I'm good with manually flashing them all individually but for those that aren't that would be dope.. Can you even do that with the .img's for HTC devices?
Click to expand...
Click to collapse
dottat worked with the Flashify dev to get it working with the One Max. Recommend everyone use that.

HELP !!!
I tried flashing the system img, but keep on getting this error msg below. Can't do anything else but go into Custom Recovery.
error: cannot load 'system.img': Not enough space
---------- Post added at 09:27 PM ---------- Previous post was at 09:15 PM ----------
mustangmao said:
HELP !!!
I tried flashing the system img, but keep on getting this error msg below. Can't do anything else but go into Custom Recovery.
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
When sending boot image after i use fastboot erase boot commend, it just stuck on sending 'boot' <16384 kb> and nothing happens. Any help suggestion?

...Send boot.img when flashing boot. Send system when sending system. Can't flash system into boot partition
The boot partition is only 16 megs so if you try to flash a 2 gig file into it you'll prolly hang.
Flashing the 2gig system.img to the system partition properly will likely take some time. You have screenshots?
Sent from my HTC6600LVW using Tapatalk 4

That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
---------- Post added at 12:29 AM ---------- Previous post was at 12:08 AM ----------
mustangmao said:
That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
Click to expand...
Click to collapse
BTW: Reason I need to flash the Stock Rom is because my One Max has this weird charging problem, where once the phone is turned on, it only charges to 35-37% and it stops, however if I leave it powered off and charge, it charges to 100% all the way. It must be a software issue and since I am using it on AT&T, Verizon CS and retail store doesn't even want to offer at help. So, i am kinda stuck with fixing the issue myself.

mustangmao said:
That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
---------- Post added at 12:29 AM ---------- Previous post was at 12:08 AM ----------
BTW: Reason I need to flash the Stock Rom is because my One Max has this weird charging problem, where once the phone is turned on, it only charges to 35-37% and it stops, however if I leave it powered off and charge, it charges to 100% all the way. It must be a software issue and since I am using it on AT&T, Verizon CS and retail store doesn't even want to offer at help. So, i am kinda stuck with fixing the issue myself.
Click to expand...
Click to collapse
Are you unlocked? Because remote not allowed word indicates you are not. Can you confirm?
If your kernel is what got hosed you always flash my boot.IMG using the app flashify from the market from a booted rooted rom....assuming you are unlocked. Otherwise you will have create a flashable 0p3img.zip file and flash your kernels from hboot.
Sent from my HTC6600LVW using Tapatalk 4

dottat said:
Are you unlocked? Because remote not allowed word indicates you are not. Can you confirm?
If your kernel is what got hosed you always flash my boot.IMG using the app flashify from the market from a booted rooted rom....assuming you are unlocked. Otherwise you will have create a flashable 0p3img.zip file and flash your kernels from hboot.
Sent from my HTC6600LVW using Tapatalk 4
Click to expand...
Click to collapse
Yes, i am unlocked and S-OFF and rooted.
Tried another PC and using factory HTC cable, still the same error when flashing system.
Now, if the issue is with my OS, all i need to flash is just System.img and nothing else, right?

mustangmao said:
Yes, i am unlocked and S-OFF and rooted.
Tried another PC and using factory HTC cable, still the same error when flashing system.
Now, if the issue is with my OS, all i need to flash is just System.img and nothing else, right?
Click to expand...
Click to collapse
Load flashify (free) from the app store. Copy the boot.IMG to your SD card and flash boot from that app and report back.
Sent from my Nexus 7 using Tapatalk 4

dottat said:
Load flashify (free) from the app store. Copy the boot.IMG to your SD card and flash boot from that app and report back.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Flash boot.img from SDcard, everything went fine, just rebooted the phone, no issues. Now, how do i flash the System.IMG, which is the key to hopfully solve the battery charing issue? thanks

It should be via fastboot...but your fast boot install doesn't seem to like flashing anything to your phone. Do you have any other pcs you can try and can you see if your charging issue was fixed before proceeding ?
Sent from my Nexus 7 using Tapatalk 4

dottat said:
It should be via fastboot...but your fast boot install doesn't seem to like flashing anything to your phone. Do you have any other pcs you can try and can you see if your charging issue was fixed before proceeding ?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Wow, i am amazed, just flashing the boot.img and my phone starts chargin pass 37% now while the phone is powered on. Maybe i don't need to flash system.img after all. You rocks dude, thanks so much. Keep up the good work !!!

for what its worth,ive never been able to fastboot flash system system.img ive always gotten that space error.
ive just skimmed thru this,but the easiest way7 for you guys to flash this is to just open the radio zip and add the other images to it. then you can use those directions(oem rebootRUU,etc) and flash them all in one shot.
i could work with you guys to dump the relevant images that usually come in an ruu if you want to make up a full(unsigned) ruu.

I also had the charging issue.(wouldn't charge past 37%....Switched charger and the issue is no more.
sent from my humongous VZW HTC ONE MAX

mustangmao said:
Wow, i am amazed, just flashing the boot.img and my phone starts chargin pass 37% now while the phone is powered on. Maybe i don't need to flash system.img after all. You rocks dude, thanks so much. Keep up the good work !!!
Click to expand...
Click to collapse
Sorta figured that would happen...good deal.
Sent from my HTC6600LVW using Tapatalk 4

scotty1223 said:
for what its worth,ive never been able to fastboot flash system system.img ive always gotten that space error.
ive just skimmed thru this,but the easiest way7 for you guys to flash this is to just open the radio zip and add the other images to it. then you can use those directions(oem rebootRUU,etc) and flash them all in one shot.
i could work with you guys to dump the relevant images that usually come in an ruu if you want to make up a full(unsigned) ruu.
Click to expand...
Click to collapse
Lets make that
Sent from my HTC6600LVW using Tapatalk 4

I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.

Jiggity Janx said:
I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.
Click to expand...
Click to collapse
Good to know, thanks for the heads up.

Jiggity Janx said:
I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.
Click to expand...
Click to collapse
any idea where it is? I hadn't seen one but there's an app for decrypting

Related

[Q] EVO stuck in bootloop

Alright, so i have an EVO 4g lte and i attempted to root it today. It didnt turn out very well to say the least... I unlocked bootloader and flashed TWRP recovery.I then flashed superSU, and at the same time i flashed a custom rom and gapps zip. Then hit reboot. It has not booted up since.. It will just sit at the white HTC screen. i tried clearing cache and Dalvik cache, also did a factory reset. tried flashing cm10 rom onto the device as well as a rooted stock rom. nothing works! the farthest i have gotten was with the cm10 rom and it went to the cyanogenmod boot logo but was in bootloop still. I downloaded the ADT tool bundle but the phone wont show up on the device list. Can anyone help? im completely stumped.. Im fairly new to rooting and custom roms, but i have rooted multiple tablets and samsung galaxy phones and havent had any issues. this is my only phone also, i just gave my backup to my mother because her phone broke... please if anyone knows how to fix this let me know. when i boot into recovery mode it says Tampered and Unlocked at the top as well as S-On. I can also go into TWRP recovery with no problems. just cant use fastboot with my computer (windows 7 PC).
I am pretty sure i know what i did wrong, I flashed SuperSU to gain root at the same time i flashed the custom rom and gapps.. on all the other devices i would reboot after root and then flash the custom rom seperately.. but is there a way to correct my mistake?
Since you are s-on you have to fastboot flash the boot.img/kernel first and then flash CM and gapps
Any questions PM me
OK sorry to be a noob but how do I do that? I used cmd.exe while rooting but now it won't recognize my device. Much thanks for any help!!
Sent from my GT-P5110 using xda app
If in bootloader type fastboot devices
In recovery type adb devices
See if you get a reply
In fast boot USB menu on the phone, I typed fastboot devices on cmd and it came up blank.
Sent from my GT-P5110 using xda app
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
bigdaddy619 said:
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
Click to expand...
Click to collapse
ok ill uninstall all that and give it a try. is pm a better contact method for you?
AUSRA15 said:
ok ill uninstall all that and give it a try. is pm a better contact method for you?
Click to expand...
Click to collapse
Here is fine
bigdaddy619 said:
Here is fine
Click to expand...
Click to collapse
OK rebooting now I'll see if it uninstalled everything.
:fingerscrossed:
OK were connected now, now what? :good:
PC and phone are talking ?
fastboot devices
yes they are talking now. fastboot devices and my phone shows up.
i tried fastboot flash boot.img but it wont recognize the command, i placed the boot.img file into the platform-tools folder inside my C drive. what am i doing wrong? its late at night and im frustrated so i know im screwing something up...
ok good BTW which version of twrp are you using? Let me know before you continue.
pull the boot.img from the rom zip and copy it to the folder you opened your cmd window from
then type fastboot boot boot.img
once it says successful press the power button to return to HBOOT and use the vol keys to navigate to recovery
Once there choose wipe and wipe cache/dalvik cahce/system/data or factory reset depending which version of twrp you are using
then flash CM and gapps
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
AUSRA15 said:
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
Click to expand...
Click to collapse
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
bigdaddy619 said:
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
Click to expand...
Click to collapse
same thing, cannot load unknown error. also i am using twrp 2.6.0.0
Ok lets try something different at least it will get you up and running
Get twrp v2.4.1.0 from http://techerrata.com/browse/twrp2/jewel
put it in the same folder you are using and we will downgrade your twrp for now
copy and paste this in the cmd window
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
then fastboot erase cache
ok got the twrp done succesfully as well as the wipe cache. whats next? i think i figured out what i was doing wrong, i hadnt opened the file directory. cd downloads, cd android files, etc.
should i try going into recovery now on the phone and flash a rom, or should we stay on fastboot and push the boot.img?
Easiest way to open a cmd window is to press shift and right click inside the folder and choose open cdm window here
That way you know you are in the correct folder.
Yeah go ahead and try to flash the boot.img again

No signal, phone number, SIM problem? Number 000-000-0000

As I was using CM 4.4.2, everything was going fine, I had 3 bars of LTE, and then I tried to make a call and it said mobile networks not available, I checked my signal in the status bar and it still said LTE and data still worked fine. I went to my phone settings and checked it and it said my mobile network was unknown, and my phone number was 000-000-0000. I wiped, and flashed CM10.2(4.3) and it did the exact same thing, only this time it said my phone number, but still, I couldn't make any calls or text, I've tried flashing two sense 5 roms and none of them display my phone number or let me call or text, but upon changing the subscription type from global to LTE/CDMA, it gives me LTE data, but that's it...Can anyone please help me?
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
rejectedjs said:
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
santod040 said:
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
rejectedjs said:
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
Click to expand...
Click to collapse
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
rejectedjs said:
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
Click to expand...
Click to collapse
No problem bud.
Glad that worked out for you.
Same process always fixes 3g/4g issues after flashing many roms for me, on all of my devices.
:good:
This exact thing happened to me a few weeks ago. Busted my ass trying to fix it, after a few days of no service i finally got it.
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
The way you fixed it seems a lot easier than what I did. I returned to s-on, 1.15 hboot and the oldest firmware. Now my phone's bootloader will always say tampered too, since i had to HTC dev unlock it to get root.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
:good: Can't thank you enough.
I have a second DNA that I have not been able to use.
Since Moonshine S-off I have not had any data connection. It has been very frustrating.
Followed your steps and now it's back up and running.
Awesome my friend, just awesome. Thank you.
quick question
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
LuckyPuppy said:
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
Click to expand...
Click to collapse
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
how to
sdamark said:
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
Click to expand...
Click to collapse
Awesome! Thank you so much!
Where is there a stock rom
thayl0 said:
Where is there a stock rom
Click to expand...
Click to collapse
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
sdamark said:
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
Click to expand...
Click to collapse
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
thayl0 said:
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
Click to expand...
Click to collapse
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
sdamark said:
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
Click to expand...
Click to collapse
why would i do a dirty install?
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
uNdea said:
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
Click to expand...
Click to collapse
You do know flashing 3.06 ruu makes it stock recovery. Not sure of you flashed a Rom or a ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app

[Q] HELP can not install TWRP through Fastboot! What am I doing wrong?

OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.

Bricked Nexus 9

Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
nexus 9
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
MoooN said:
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
Click to expand...
Click to collapse
I don't have a Linux system and looking through thread seems too advance for me. I can't relate it to the N9. However, there seems to be something wrong partition, because I can't mount storage.
matt4787 said:
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
Click to expand...
Click to collapse
I can flash custom recovery, but I can't push files or adb sideload, therefore I can't do anything in recovery anyway.
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Does the Google Logo flash for a second or so before it goes to bootloader?
nexus 9
Try to get into bootloader by holding power and volume down.
MoooN said:
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
Click to expand...
Click to collapse
I will look in to it, thank you.
jd1639 said:
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already tried one version of the image, which didn't work, will try to flash the others.
scrosler said:
Does the Google Logo flash for a second or so before it goes to bootloader?
Click to expand...
Click to collapse
restart - sometimes yes and sometimes no, if plug into computer - no, if not plugged - yes,
matt4787 said:
Try to get into bootloader by holding power and volume down.
Click to expand...
Click to collapse
you mean power + volume up, but yes, no problem getting there, also adb is working
thanks for all your help, I will try different factory image and flashing from OTG
The problem is your kernel is not loading or mismatched to the operating system. I have experienced this a lot on HTC devices when I screw something up... I mean "experiment"
You need to flash the boot system and vendor image from the latest factory ROM.
You need to do it manually...
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot to recovery and wipe data. Not factory rest but actually wipe all of /data partition.
That should get you back. If not post back results.
If you are not familiar with fastboot then state so and I will help you.
Yes! I got it booting again, thank you everyone for helping. Apparently, the problem was, I think, wiping manually, that is, system, cache, recovery, boot, user data, and vendor didn't erase everything. What did the trick was [fastboot -w], I did this instead of erasing one by one. Thank you so much guys!
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
bynarie said:
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
Click to expand...
Click to collapse
Um, he's got it fixed.
Sent from my Nexus 5 using XDA Free mobile app
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Thanks for paying it forward.
I have a similar problem my nexus 9 wont turn on and would freeze in the optimizing apps screen after going past the nexus logo but i can get to the fastboot and recovery. But i cannot flash the factory image because my bootloader is locked and i didn't enable developer options prior to the problem. I'm thinking about sideloading the latest ota would that help me ? And is there anyway to unlock bootloader if i can't boot the device?
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Can you please explain to me what fastboot w- command means ?
It erases userdata and cache. Often needed if you run into bootloops. But it does wipe your data so backup off your device first.
Bricked N9
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
emi.guego said:
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
Click to expand...
Click to collapse
I had the same problem... I had to manually flash each image through fastboot starting with the recovery img
Sent from my HTC One M9 using XDA Free mobile app
But how can I do it if I can't enable USB debugging?
Enviado desde mi Moto MAXX mediante Tapatalk

[DUMP] ZenWatch 2 (sparrow, WI501Q) Build M6E70C

Inspired by this thread!
Dumped via non-flashed (only live booted) TWRP so I can dump the original recovery too.
Can be flashed in fastboot mode!
To flash these images reboot your watch, swipe from the top left to the bottom right corner when you see the ASUS logo and connect it to your PC.
Then in a command line enter:
Optional (wipes the device): fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Neat All-In-One Backup Document: DropBox Paper
Downloads:
ALL-IN-ONE zip (system.img, boot.img, recovery.img): Dropbox (269MB) - OneDrive Backup
recovery.img: Dropbox (16 384KB) - OneDrive Backup
boot.img: Dropbox (16 384KB) - OneDrive Backup
MD5 Hashes:
sparrow_601_M6E70C_170505.zip: 34745B23F9ED2FD5DCBB6189EA7011A9
recovery.img: 7B33DE51549919AB5DA700B425978BB4
boot.img: 051FF5BAA13B3EB34B0E5DD818ACC167
If you need more partitions tell me below, I've only included these ones so far because I know they won't contain any personal or device specific information and should be flashable on other devices too. However I've dumped every single one existing on the ZW2
ok i ve flashed every single file and also did a wipe before, now i get stuck in the boot screen, before it i was on the 7.x rom from this forum. do u have any idea how to solve this problem? i got the WI501Q
Lecani said:
ok i ve flashed every single file and also did a wipe before, now i get stuck in the boot screen, before it i was on the 7.x rom from this forum. do u have any idea how to solve this problem? i got the WI501Q
Click to expand...
Click to collapse
Seas!
Did you do "fastboot -w"? That'll wipe all userdata. Then flash the images.
EpicLPer said:
Seas!
Did you do "fastboot -w"? That'll wipe all userdata. Then flash the images.
Click to expand...
Click to collapse
Seas
Yes, I did. but now I'm stuck in the bootscreen. :/
Lecani said:
Seas
Yes, I did. but now I'm stuck in the bootscreen. :/
Click to expand...
Click to collapse
Did you get any error message while flashing? And is your bootloader unlocked?
EpicLPer said:
Did you get any error message while flashing? And is your bootloader unlocked?
Click to expand...
Click to collapse
No I didn't get a single one, and yes it is. :/
Guess if I could install the TWRP and flash this on the watch, would this be possible?
Lecani said:
No I didn't get a single one, and yes it is. :/
Click to expand...
Click to collapse
You have to unlock your bootloader first.
EpicLPer said:
You have to unlock your bootloader first.
Click to expand...
Click to collapse
Yea, the bootloader was every single time i tried to install this one unlocked, before flashing, after wiping.. again and again.. always stuck on bootscreen. The only thing i can see is the ASUS logo with some other things, but no boot.
Lecani said:
Yea, the bootloader was every single time i tried to install this one unlocked, before flashing, after wiping.. again and again.. always stuck on bootscreen. The only thing i can see is the ASUS logo with some other things, but no boot.
Click to expand...
Click to collapse
Why would you want to relock your bootloader anyways?
Unlock it now, format via -w, flash boot, recovery and system and then try to boot the watch.
EpicLPer said:
Why would you want to relock your bootloader anyways?
Unlock it now, format via -w, flash boot, recovery and system and then try to boot the watch.
Click to expand...
Click to collapse
Exactly that is what i ve done several times right now.. without any succsess.. I ve never relocked the bootloader. I ll send you what i ve done per PM.
EpicLPer said:
Inspired by this thread!
Dumped via non-flashed (only live booted) TWRP so I can dump the original recovery too.
Can be flashed in fastboot mode!
To flash these images reboot your watch, swipe from the top left to the bottom right corner when you see the ASUS logo and connect it to your PC.
Then in a command line enter:
Optional (wipes the device): fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Neat All-In-One Backup Document: DropBox Paper
Downloads:
ALL-IN-ONE zip (system.img, boot.img, recovery.img): Dropbox (269MB)
recovery.img: Dropbox (16 384KB)
boot.img: Dropbox (16 384KB)
MD5 Hashes:
sparrow_601_M6E70C_170505.zip: 34745B23F9ED2FD5DCBB6189EA7011A9
recovery.img: 7B33DE51549919AB5DA700B425978BB4
boot.img: 051FF5BAA13B3EB34B0E5DD818ACC167
If you need more partitions tell me below, I've only included these ones so far because I know they won't contain any personal or device specific information and should be flashable on other devices too. However I've dumped every single one existing on the ZW2
Click to expand...
Click to collapse
THANKS!! worked PERFECTLY!!
relock bootloader
EpicLPer said:
Why would you want to relock your bootloader anyways?
Unlock it now, format via -w, flash boot, recovery and system and then try to boot the watch.
Click to expand...
Click to collapse
i relocked my bootloader because i taught that is the problem why my update everytime fails but i think i have the wrong recovery why it wont update
---------- Post added at 05:58 AM ---------- Previous post was at 05:44 AM ----------
keep it up!
What must be noted if one of WebWear 2.0 again on stock if the AW 2.0 update comes? Bootloader is Open ?
SirusX said:
What must be noted if one of WebWear 2.0 again on stock if the AW 2.0 update comes? Bootloader is Open ?
Click to expand...
Click to collapse
Just flash the in post 1 mentioned images and wait, you don't have to close the bootloader.
The ZenWatch is the first watch that I flash, I keep stock in the Fastboot mode!, How do I solve this
Property of WebWear 2.0 according to your instructions flasht and now stands the Stock Asus Screen
Your command fastboot flash system system.img is wrong it must be fastboot flash system.simg
Since I still had an old WebWear 2.0 system.img in the folder it came to the Bootscreen Stock
SirusX said:
Property of WebWear 2.0 according to your instructions flasht and now stands the Stock Asus Screen
Since I still had an old WebWear 2.0 system.img in the folder it came to the Bootscreen Stock
Click to expand...
Click to collapse
I found out there is are two type's of ZenWatch2 I have the wren version
Is it for the Big Version of Zenwatch 2
Gesendet von iPhone mit Tapatalk Pro
SirusX said:
Is it for the Big Version of Zenwatch 2
Click to expand...
Click to collapse
Yes is for the big version (Sparrow)
---------- Post added at 03:22 PM ---------- Previous post was at 03:17 PM ----------
I did the process of flashing the images given in the OP and all worked fine . Just to add , I did fastboot oem unlock first, then fastboot -w, and then followed the instructions given in the OP.
All worked just fine and I'm back to AW 1 .5.
Cheers.
Cannot Load "system.img" Error
Can someone please help me downgrade back to 1.5? I'm seriously so mad that I'm about to throw my Zenwatch 2 in the garbage. Two days of trying to do this and nothing. I'm good until I get to the "fastboot flash system system.img" command line. I'm keep getting an error saying cannot load "system.img". I'm so angry I can barely see straight. Can someone please offer some guidance?
Update: I found the problem. I was so mad that I realized that I just kept entering "fastboot flash system system.img" instead of "fastboot flash system system.simg". All good now thankfully.

Categories

Resources