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.
Related
T329w is customized version Of Desire X (t329e) which have to SIM card
The rom for Desire X running Perfect on my T329w except there is no Signal...
I think flash back the T329w's stock Kernal and Radio can fix it?
Has anyone can Help me?
Thanks a Lot !
link of Rom for T329w
Version 1
http://pan.baidu.com/s/122oNL
Version 2
http://pan.baidu.com/s/1oVdzO
Hi
You can downlod from here:https://hotfile.com/dl/249367403/0b72cc6/T329W.rar.html
This is decrypt stock rom for T329w without "System.img"
I can't install this,
more details: http://forum.xda-developers.com/showthread.php?t=2483223
BABAK236 said:
Hi
You can downlod from here:https://hotfile.com/dl/249367403/0b72cc6/T329W.rar.html
This is decrypt stock rom for T329w without "System.img"
Click to expand...
Click to collapse
I need the Stock Recovery for T329w as by mistake flashed Single sim recovery. I am from India and using Stock ROM with JB (version 4.1.1).
Flashing the "recovery_signed.img" inside the folder of this Download would be helpful?
Please reply.
Thanks.
arindam4u said:
I need the Stock Recovery for T329w as by mistake flashed Single sim recovery. I am from India and using Stock ROM with JB (version 4.1.1).
Flashing the "recovery_signed.img" inside the folder of this Download would be helpful?
Please reply.
Thanks.
Click to expand...
Click to collapse
I think it will
Did the same mistake..
Any help on this front will be useful
yashvchauhan said:
Did the same mistake..
Any help on this front will be useful
Click to expand...
Click to collapse
There is a dual sim rom in one of these threads, flash that and after that flash the correct stock recovery.
And next time read carefully because this forum is not for the the Desire X dual sim
GtrCraft said:
There is a dual sim rom in one of these threads, flash that and after that flash the correct stock recovery.
And next time read carefully because this forum is not for the the Desire X dual sim
Click to expand...
Click to collapse
Searched, couldn't find any dual sim roms apart from the one in this thread
EDIT - or maybe it's this one? it's compatible with dual sim http://forum.xda-developers.com/showpost.php?p=46730392&postcount=30
thanks for your help though..
This is what i plan to do :
Download and flash TWRP for t329w
Transfer http://pan.baidu.com/s/122oNL (version 1) to SD Card and the recovery_signed.img and boot_signed.img to SC Card
Reboot phone to recovery
Choose Wipe then Swipe to Factory Reset
or the best is Select Advance Wipe, tick all except sdcard then swipe to wipe
Select Install and select the version1 rom.zip then swipe to confirm flash
Wait until the installation is finished
Reboot phone to fastboot and connect it to your PC
Open command prompt, lead it to folder where you installed adb and fastboot and issue commands:
fastboot flash recovery C:\recovery_signed.img
fastboot erase cache
fastboot reboot
fastboot flash boot c:\boot_signed.img
fastboot erase cache
fastboot reboot
yashvchauhan said:
Searched, couldn't find any dual sim roms apart from the one in this thread
EDIT - or maybe it's this one? it's compatible with dual sim http://forum.xda-developers.com/showpost.php?p=46730392&postcount=30
thanks for your help though..
This is what i plan to do :
Download and flash TWRP for t329w
Transfer http://pan.baidu.com/s/122oNL (version 1) to SD Card and the recovery_signed.img and boot_signed.img to SC Card
Reboot phone to recovery
Choose Wipe then Swipe to Factory Reset
or the best is Select Advance Wipe, tick all except sdcard then swipe to wipe
Select Install and select the version1 rom.zip then swipe to confirm flash
Wait until the installation is finished
Reboot phone to fastboot and connect it to your PC
Open command prompt, lead it to folder where you installed adb and fastboot and issue commands:
fastboot flash recovery C:\recovery_signed.img
fastboot erase cache
fastboot reboot
fastboot flash boot c:\boot_signed.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Perfect steps, if those two roms don't work then try this: http://sourceforge.net/projects/others/files/DX/Dual SIM/T329w_2.12.1402.1.zip/download
(That was the one I meant)
GtrCraft said:
Perfect steps, if those two roms don't work then try this: http://sourceforge.net/projects/others/files/DX/Dual SIM/T329w_2.12.1402.1.zip/download
(That was the one I meant)
Click to expand...
Click to collapse
One last thing, I forgot to mention I had taken a NAndroid backup before installing the ROM. I restored it and did a full wipe/factory reset, but I think the kernel is the problem (it shows the kernel used by the single sim ROM)
So as of now, I'm just going to flash the boot and recovery, coz boot_signed should change the kernel.
Also, this folder contains other images such as radio, hboot, dzdata etc. what are these for and would they help?
Thanks a lot for your help!!
---------- Post added at 06:57 AM ---------- Previous post was at 06:21 AM ----------
There's a guy on FB who had a similar problem. He said he flashed a "brushed" ROM from a chinese forum (i got the links), well if you translate it means a modified ROM for the dual sim, right? He also said he was missing the RUU. Any help here would be appreciated.. Thanks a lot!
Heres what he said
"i used a brushed rom and installed through twrp recovery bro . check the link i sent u can translate it and find everything . i couldnt find ruu file"
yashvchauhan said:
One last thing, I forgot to mention I had taken a NAndroid backup before installing the ROM. I restored it and did a full wipe/factory reset, but I think the kernel is the problem (it shows the kernel used by the single sim ROM)
So as of now, I'm just going to flash the boot and recovery, coz boot_signed should change the kernel.
Also, this folder contains other images such as radio, hboot, dzdata etc. what are these for and would they help?
Thanks a lot for your help!!
Click to expand...
Click to collapse
After restoring Nandroid, just fastboot flash the boot_signed.img and reboot and see whether it boot. It should work if the custom recovery is working well for your device. No need to fastboot flash recovery_signed.img first. Just boot and see whether it works. If it works then only you fastboot flash the recovery_signed.img if you want to.
Don't worry about other images as you can't flash those on a S-On device.
ckpv5 said:
After restoring Nandroid, just fastboot flash the boot_signed.img and reboot and see whether it boot. It should work if the custom recovery is working well for your device. No need to fastboot flash recovery_signed.img first. Just boot and see whether it works. If it works then only you fastboot flash the recovery_signed.img if you want to.
Don't worry about other images as you can't flash those on a S-On device.
Click to expand...
Click to collapse
HELP!! I flashed the boot.img and now the phone doesn't boot. Shows white screen then blackout.
adb doesn't detect it
help!!
yashvchauhan said:
HELP!! I flashed the boot.img and now the phone doesn't boot. Shows white screen then blackout.
adb doesn't detect it
help!!
Click to expand...
Click to collapse
Inside your nandroid backup there is a file boot.emmc.win, this is your stock boot.img
So fastboot flash this one with command
fastboot flash boot boot.emmc.win
ckpv5 said:
Inside your nandroid backup there is a file boot.emmc.win, this is your stock boot.img
So fastboot flash this one with command
fastboot flash boot boot.emmc.win
Click to expand...
Click to collapse
shows Error : Cannot open boot.emmc.win
Is it because my nandroid is on external sd? I'm using nexus prime as the recovery
yashvchauhan said:
shows Error : Cannot open boot.emmc.win
Is it because my nandroid is on external sd? I'm using nexus prime as the recovery
Click to expand...
Click to collapse
What do you mean shows Error : Cannot open boot.emmc.win ? boot.emmc.win is created by a TWRP recovery only. If there is one you don't have to "open" it, just copy it to your fastboot folder
Now you mentioned you use nexus prime as the recovery do you mean you use NexusRecovery ? Can you list here the file names inside the nandroid backup ? I don't think you have boot.emmc.win in NexusRecovery
ckpv5 said:
What do you mean shows Error : Cannot open boot.emmc.win ? boot.emmc.win is created by a TWRP recovery only. If there is one you don't have to "open" it, just copy it to your fastboot folder
Now you mentioned you use nexus prime as the recovery do you mean you use NexusRecovery ? Can you list here the file names inside the nandroid backup ? I don't think you have boot.emmc.win in NexusRecovery
Click to expand...
Click to collapse
Hmm, i went to Nandroid restore > Advanced restore > Restore boot
doesn't boot.
tried restoring the whole backup, doesn't boot.
even a wipe data/factory reset doesn't make it boot!
Will taking it to an HTC centre help? (I'm ready to pay some amt of money.)
Oh no... you don't know what fastboot flash means ? It is not using the recovery to restore boot. You need to copy the boot.img to your PC where you have all your fastboot files in a folder.
Try again this way as I don't have my PC with me. Replying to you with someone else PC.
In my ROM threads, you will see Boot.img_Installer_RCx.x.zip in post #1. Download any of them then do the following
1. Download theBoot.img_Installer_RCx.x.zip and extract it on your PC desktop
2. Reboot your DX to bootloader and connect to your PC (you should see the word "fastboot usb" in red color on the bootloader)
3. Open the Boot.img_Installer_RCx.x folder that you extracted, you should see a batch file Install Boot.img.bat there
4. Replace the boot.img with your boot.img (don't use the one that already in the folder). Try the boot_signed.img that you have, rename it to boot.img
5. Run that Install Boot.img.bat and when it stop just press any key to exit
6. Reboot
And yes, taking it to HTC centre will help but of course you need to pay them
ckpv5 said:
Oh no... you don't know what fastboot flash means ? It is not using the recovery to restore boot. You need to copy the boot.img to your PC where you have all your fastboot files in a folder.
Try again this way as I don't have my PC with me. Replying to you with someone else PC.
In my ROM threads, you will see Boot.img_Installer_RCx.x.zip in post #1. Download any of them then do the following
1. Download theBoot.img_Installer_RCx.x.zip and extract it on your PC desktop
2. Reboot your DX to bootloader and connect to your PC (you should see the word "fastboot usb" in red color on the bootloader)
3. Open the Boot.img_Installer_RCx.x folder that you extracted, you should see a batch file Install Boot.img.bat there
4. Replace the boot.img with your boot.img (don't use the one that already in the folder). Try the boot_signed.img that you have, rename it to boot.img
5. Run that Install Boot.img.bat and when it stop just press any key to exit
6. Reboot
And yes, taking it to HTC centre will help but of course you need to pay them
Click to expand...
Click to collapse
Hmm, I will try that. Guess I will have to take it anyway coz of the SIM card issue.
Thanks a lot man. You've been a great help. Appreciate every bit of it.
yashvchauhan said:
One last thing, I forgot to mention I had taken a NAndroid backup before installing the ROM. I restored it and did a full wipe/factory reset, but I think the kernel is the problem (it shows the kernel used by the single sim ROM)
So as of now, I'm just going to flash the boot and recovery, coz boot_signed should change the kernel.
Also, this folder contains other images such as radio, hboot, dzdata etc. what are these for and would they help?
Thanks a lot for your help!!
---------- Post added at 06:57 AM ---------- Previous post was at 06:21 AM ----------
There's a guy on FB who had a similar problem. He said he flashed a "brushed" ROM from a chinese forum (i got the links), well if you translate it means a modified ROM for the dual sim, right? He also said he was missing the RUU. Any help here would be appreciated.. Thanks a lot!
Heres what he said
"i used a brushed rom and installed through twrp recovery bro . check the link i sent u can translate it and find everything . i couldnt find ruu file"
Click to expand...
Click to collapse
don't flash the radio hboot and other files than boot and recovery
[
yashvchauhan said:
Hmm, I will try that. Guess I will have to take it anyway coz of the SIM card issue.
Thanks a lot man. You've been a great help. Appreciate every bit of it.
Click to expand...
Click to collapse
Ohh, I just read it properly. I know what fastboot flash means. Using Android SDK > Platform tools > Shift+rightclick > open as command prompt > fastboot flash boot boot_signed.img
I've already done it. This boot_signed.img in this thread seems weird.
After installing the custom ROM, restoring my nandroid backup, my phone was booting, but without the sim being recognized.
So I fastboot flashed the above (second post of this thread) boot_signed.img from c:\
But THAT boot_signed.img led to my phone being stuck in a bootloop > white start screen > turns black > try switching it on again > same thing
Hoped I could restore the nandroid boot using recovery advanced restore, but didn't work.
Will try fastboot flashing the MIUI boot.img (coz that's what was working initially, though without a sim, and the one in this thread's second post doesn't have a source), atleast that should get my phone booting. And will try searching for the boot of my nexus recovery backup, coz that will be the stock boot.img.
My last thing before I go to HTC .
---------- Post added at 03:08 PM ---------- Previous post was at 03:06 PM ----------
GtrCraft said:
don't flash the radio hboot and other files than boot and recovery
Click to expand...
Click to collapse
I only flashed boot and recovery, not the others
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
Hello People !!!
Want to return your OP2 to 100% Stock Factory Image or have you soft bricked OP2 and nothing except fastboot works or you need OxygenOS fastboot images ? This is the thread for you !!
Download Fastboot Image from here :- https://mega.nz/#!itR00ZaI!gJ6T0jgqfZaIF9NLlCzWj4LIGMMhCw8m8owFdeB_2B4
Extract the Zip in a folder .
Boot the phone into fastboot.
Run the batch file.
Done.
This method WILL NOT WIPE DATA
If you want to wipe data to,flash userdata.img from here :- https://www.androidfilehost.com/?fid=24052804347833307
Use command
fastboot flash userdata userdata_64.img
Click to expand...
Click to collapse
You need the latest adb/fastboot package to be successful.For that,do this :-
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only)
Extract the zip and place the android-sdk-windows folder on your desktop.
Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):-
Tools > Android SDK Tools, Android SDK Platform-tools- Extras > Android Support Library, Google USB Driver
Click to expand...
Click to collapse
Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
Thanks for reading ...
Credits :- @jcespi2005 For making the fastboot zip ... @Naman Bhalla for making the thread and partitions images thread.
Done to @jcespi2005 here :- http://forum.xda-developers.com/donatetome.php?u=281521
Donate to me here :- http://www.amazon.in/gp/registry/wishlist/1X55WMSVTW3KW/
Thanks again. !!
This method has been tested successfully by atleast 2 people ,including me
This img is oxygen os 2.1.1?
Sent from my Nexus 5 using XDA Free mobile app
matitorres07 said:
This img is oxygen os 2.1.1?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Correct
DEAD
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
S0ad113 said:
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
Click to expand...
Click to collapse
i've got the exact same problem. Let me guess: your bootloader is locked?
anyways, try this: press POWER + VOLUME UP until you're in fastboot mode. connect the OP2 to your PC and execute the command 'fastboot continue' in a cmd window. if not, repeat until it works. your phone should boot like normal, you can't restart or shutdown though, since you'll be stuck in the same loop again.
at least that's my problem. can't flash anything since bootloader is locked, ADB does work fine though, as long as the phone is running.
really sucks to need a PC everytime you want to power on your phone.. if anyone can help, i'd gladly appreciate it
S0ad113 said:
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
Click to expand...
Click to collapse
I TRY TO USE TOOLBOX and try to flash..some via CMD But give me error writing "recover" ...Failed Remote: device is Locked. Cannot Flash images)
Helppppppp me
---------- Post added at 11:13 PM ---------- Previous post was at 11:08 PM ----------
rattig said:
i've got the exact same problem. Let me guess: Your bootloader is locked?
Anyways, try this: Press power + volume up until you're in fastboot mode. Connect the op2 to your pc and execute the command 'fastboot continue' in a cmd window. If not, repeat until it works. Your phone should boot like normal, you can't restart or shutdown though, since you'll be stuck in the same loop again.
At least that's my problem. Can't flash anything since bootloader is locked, adb does work fine though, as long as the phone is running.
Really sucks to need a pc everytime you want to power on your phone.. if anyone can help, i'd gladly appreciate it
Click to expand...
Click to collapse
i try all always locked always loop omg
---------- Post added at 11:38 PM ---------- Previous post was at 11:13 PM ----------
Helpppppppppppppppppppppppppppppppppppppppppppppppppppppppp
Please note that on the fastboot userdata command you are missing a letter. You have "fastboot flash userdata userdata_64.img" and it should be fastboot flash userdata userdata_64G.img. Great job by the way, used it to reset the OP2 and works great.
ukcain said:
Please note that on the fastboot userdata command you are missing a letter. You have "fastboot flash userdata userdata_64.img" and it should be fastboot flash userdata userdata_64G.img. Great job by the way, used it to reset the OP2 and works great.
Click to expand...
Click to collapse
I did it..but is not that the problem....the problem is..when i try to flash some...fail always. give the error : device is Locked. Cannot Flash images
REBORN
Solved ty allll
How on earth did you manage to get a fastboot image for the OP2?
Thanks by the way
Stevles said:
How on earth did you manage to get a fastboot image for the OP2?
Thanks by the way
Click to expand...
Click to collapse
Converting the .DAT inside the official recovery ZIP to .IMG format
The rest of partitions are on the fastboot format, so only system and cache needs conversion, and userdata comes from hydrogenOS fastboot package...
jcespi2005 said:
Converting the .DAT inside the official recovery ZIP to .IMG format
The rest of partitions are on the fastboot format, so only system and cache needs conversion, and userdata comes from hydrogenOS fastboot package...
Click to expand...
Click to collapse
Nice
is not flash me the file system.img
i get error message "the app crash" from windows
pls help
Zahi122 said:
is not flash me the file system.img
i get error message "the app crash" from windows
pls help
Click to expand...
Click to collapse
I'm having the same issue
I'll try to do it through TWRP and see if that works for me
Naman Bhalla said:
Hello People !!!
Want to return your OP2 to 100% Stock Factory Image or have you soft bricked OP2 and nothing except fastboot works or you need OxygenOS fastboot images ? This is the thread for you !!
Download Fastboot Image from here :- https://mega.nz/#!itR00ZaI!gJ6T0jgqfZaIF9NLlCzWj4LIGMMhCw8m8owFdeB_2B4
Click to expand...
Click to collapse
Hi,
Are these images from a Chinese, EU or US version of the device?
thanks
Hello all,
is there a new img.image?
I have great problems and need a super clean install included wipe data!!
Thanxx for helping
S5 & One + Boeffla Inside
S0ad113 said:
Solved ty allll
Click to expand...
Click to collapse
How? What did you do different? For me, the fastboot.exe stops working at the below step.
..\fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
avi0889 said:
How? What did you do different? For me, the fastboot.exe stops working at the below step.
..\fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
I got the same error at first then I copied all the files into my platform-tools dir that has ADB & fastboot then run it.
Try this tool. It works good for me. But the windows driver for OP2 and the Qualcomm Diagnostic 9006 Driver must be installed.
Sry, can`t post the link. please PN.
Worked great, but it switched my wifi off. Even if I turn it on manually it doesn't show any active networks. I have rebooted several times. Any workaround?
NEW VERSION AVAILABLE!
https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3601596
----------
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:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Download ALL-IN-ONE zip (system.img, boot.img, recovery.img): Dropbox (262MB) - OneDrive Backup
Download recovery.img: Dropbox (16 384KB) - OneDrive Backup
Download boot.img: Dropbox (16 384KB) - OneDrive Backup
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
Please check your file, system.img have problem
leap_ahead said:
Please check your file, system.img have problem
Click to expand...
Click to collapse
What problem you mean? While flashing?
EpicLPer said:
What problem you mean? While flashing?
Click to expand...
Click to collapse
Invalid system parse
leap_ahead said:
Invalid system parse
Click to expand...
Click to collapse
Just to make sure, you do have unpacked the ZIP and flashed the system.img via fastboot, right? Not that you renamed the ZIP to IMG lol
EDIT: Okay, tried it myself and I'm getting the same error... Weird...
EpicLPer said:
Just to make sure, you do have unpacked the ZIP and flashed the system.img via fastboot, right? Not that you renamed the ZIP to IMG lol
EDIT: Okay, tried it myself and I'm getting the same error... Weird...
Click to expand...
Click to collapse
I know my friend! I use the other and is ok
leap_ahead said:
I know my friend! I use the other and is ok
Click to expand...
Click to collapse
Okay, I have no idea how to make a fastboot flashable image out of the dd system.img I made... Sorry
Flashing ok
I flashed this via fastboot without probs. system.img has been flashed splitted into some chunks.
Device booted ok. All fine.
t.daun said:
I flashed this via fastboot without probs. system.img has been flashed splitted into some chunks.
Device booted ok. All fine.
Click to expand...
Click to collapse
Hm, maybe there are some old fastboot versions around that don't know how to handle a "new system image"? Weird...
t.daun said:
I flashed this via fastboot without probs. system.img has been flashed splitted into some chunks.
Device booted ok. All fine.
Click to expand...
Click to collapse
Invalid,!!
EpicLPer said:
Okay, I have no idea how to make a fastboot flashable image out of the dd system.img I made... Sorry
Click to expand...
Click to collapse
I'm using "ext2simg".
I used to use "img2simg" but it caused trouble.
In Ubuntu it's easy peasy going (Win? try Ubuntu on Linux on Windows. Win 10 only)
Code:
sudo apt install android-tools-*
ext2simg <inputfile> <outputfile>
BTW: .simg is something I invented myself.
ranf said:
I'm using "ext2simg".
I used to use "img2simg" but it caused trouble.
In Ubuntu it's easy peasy going (Win? try Ubuntu on Linux on Windows. Win 10 only)
Code:
sudo apt install android-tools-*
ext2simg <inputfile> <outputfile>
BTW: .simg is something I invented myself.
Click to expand...
Click to collapse
Awesome! Thanks a ton man! Did that now and it worked flawlessly
@EpicLPer https://forum.xda-developers.com/zenwatch-2/general/ota-url-sparrow-build-m6e70c-t3601468 u got this ota alrdy? i cant update like always. fastboot flashable imgs would be highly appreciated ^^
can it be the root installed through live booted twrp or the now unlocked bl that prevents normal updates for me? i never did a single ota on any of my phones always custom rom so idk much about ota's.
Sent from my Nexus 6P using XDA Labs
NEW VERSION AVAILABLE!
https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3601596
leap_ahead said:
Invalid,!!
Click to expand...
Click to collapse
Hello, do you have a Chinese version of the brush bag?
Stock kernels with the "forceencrypt" flag changed to "encryptable".
These are "IMG" files that need to be flashed with fastboot.
(Oct) N6F27M-noencrypt-boot.img - https://mega.nz/#!e4AmQJTa!-b9VEDCUHMa2YedScgHpSpStmKfhVWQMFWQf93L0OCU
(Oct) NGI77B-noencrypt-boot.img - https://mega.nz/#!XsBR0QBb!nkNQibCAT-IMpGH3pPVKLmHsGzE90JQfBcDzkWWwHEM
(Sept) NGI55D-noencrypt-boot.img - https://mega.nz/#!6sYSUbTb!dT-pBFhY4iJuHcqGWnRZiFvnUHLxVlNxrDDfgl0L_9w
(Aug) N6F27I-noencrypt-boot.img - https://mega.nz/#!atxQSZYK!y4H4uFt8pNW0szhUyWrp_QinytKIE3WhszAQMNJ4rO0
(Aug) N8I11B-noencrypt-boot.img - https://mega.nz/#!voxiWQqY!DtV5VWhRRLH3cvpxL37QJDFGMUjZU9uubBP8NuADG0k
Hi, and which one is to use? Are these carrier specific versions?
day242 said:
Hi, and which one is to use? Are these carrier specific versions?
Click to expand...
Click to collapse
Sounds like the N8I11B build has some Verizon specific code. After reviewing, it appears they devs used the same kernel in both builds, so it should not matter which is flashed.
Lose data?
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
TheTomahawk said:
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
Click to expand...
Click to collapse
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release and maintain the exisiting data)
Re: lose data
jbaumert said:
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release any maintain the exisiting data)
Click to expand...
Click to collapse
Cool. Em, could you provide instructions, please?
Tnx
TheTomahawk said:
Cool. Em, could you provide instructions, please?
Tnx
Click to expand...
Click to collapse
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Much obliged.
im assuming one of these brings back ota? probably N6F27I
guessing one is official ota from 7.0 to 7.1.1
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
dudikaz said:
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
Click to expand...
Click to collapse
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
jbaumert said:
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
Click to expand...
Click to collapse
if i flash it after los it gets stuck on google logo and doesn't boot at all :/
---------- Post added at 01:08 AM ---------- Previous post was at 12:36 AM ----------
ok so now i've went back to stock N8I11B which is force encrypted. could you tell me exactly what steps should i take to make it not encrypted please? also what about the franco kernel does it get rid of encryption as well maybe?
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
jbaumert said:
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
Click to expand...
Click to collapse
it's really confusing as this is what it says in the official los thread here on xda - "Current lineage 14.1 shamu nightlies are based on the N8I11B August 2017 update from google. So you should be using the radio and bootloader img from that update. " also how do i erase this userdata properly? "fastboot format userdata"? i think last time i did it my device didn't boot at all afterwards. going to try it again now.
Added September 2017 "no encrypt" boot.img to OP
Added October 2017 "no encrypt" boot.img to OP
thumbs up !!!
i was looking all over for the latest img. really grateful for your work. thanks a lot
Thank you very much
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Jeffro64 said:
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also, can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Click to expand...
Click to collapse
You can leave the name of the file (unless you just want to type in a short command with fastboot). As for the backup of "userdata", if you are updating the phone from one stock version to another and following the instructions you quoted, there is no need to backup. Coming from another ROM you would want to wipe and then yes, a backup is a good idea (needed).