Database Develop

LG540 - Fastboot - no way to get back to original state

I think it is time to say truth. LG540 cannot be recovered in original state, or at least bootloader. The first time you use fastboot, bootloader is changed and there is no way to back it to original state. For that reason you cannot flash LG540 with original KDZ from LG.
And that is fact that no one wont tell to you. All says that you got recovery mode, fastboot mode, but dont tell you that phone cannot be back to original state.
Now I know that, and it is to late for me.
Yes , you can changed roms via recovery menu, and that is ok, but all that roms are modded.
so be beware...
happy flashing

Hmm.. i can flash my first non-modded baltic rom (v20b_00.kdz) with my kdz updater.. in curiosity, i try the fastboot (camera+power) and recovery button but nothing happen.
So i guess it back to normal
Sent from my GT540 using Tapatalk

@Pepi74 Pretty sure you're wrong there, Bud.
When I first tried to put clockwork on my 2.1, I flashed a CIS 2.1 ROM that had fastboot, then I flashed clockwork from fastboot and that went great.
Then I decided to flash a stock Carphone Warehouse 2.1 ROM thinking I'd still have clockwork and fastboot - I DID NOT, THEY WERE BOTH ERASED BY THE NEW STOCK ROM
If you want to go back to stock then grab a stock ROM, put your phone into DOWNLOAD MODE and flash it with KDZ_UPDATER (if you had 2.2.1 on then wipe all data/chache from clockwork first) otherwise do a factory reset after you flash.
Try to make sure you know what you're talking about BEFORE you post.

I try that 10 times, and always have same result: after blue animation, LG stuck.
As I say, I can flash with fastboot modded ROM via KDZ, but cannot use original KDZ and flash it.
So I try many times before made this post to public

What application are you using to flash? There's no blue animation on the app you should be using.
Have another go with this app http://www.mediafire.com/?rj8dlhhp9ihm7ro
Put your phone in Download Mode (no battery, sd or sim - then hold vol - and plug in to PC). You see "Download Mode" on phone screen. Set app up as in picture and choose kdz file then Launch Software Update. Have a cup of tea. Profit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I use KDZ updater just like you.
Blue animation is animation that show when android boot up: and after that comes white LG logo, and phone stuck.
All of tutorial I use says that KDZ updater must be set as
TYPE 3GQCT
on your picture is
TYPE CDMA
(so I need that you verify this settings)
Also phone mode is recommended as DIAG, and you set up CS_EMERGENCY
( so verify again that your setting is right)
On mediafire file you send me two files
boot.img and update zip.
How to flash this? ( via AMON RA) ?
Waiting for your answer , thanks for info!
P.S From where you get this settings? -links?

Sorry, I posted the wrong link - it's just to the KDZ_Updater but you have it already:
http://www.mediafire.com/?3hd4ao113lx8gq4
The phone should flash using this method even if you bricked it. I don't have the source of this method (maybe somewhere in the FAQ @modaco) but it saved my ass a few times and now it's the ONLY method I'll use to flash anything other than 2.2.1
You can either try it or not - I won't take offence

Open KDZ_FW_UPD as administrator by choosing "Run as administrator" in the right-click menu. Once it's open, set the type to "CDMA" and the mode to "DIAG". The people over at ******** will often tell you to set it to "3gqct" and "EMERGENCY MODE", ignore this as it will not work properly.
They say this way, so I will try it in CDMA mode
Try and retry
Yes, first time I pass this procedure got grey ANDROID logo, I think: that is that. But LG 540 stuck on that animation
So I give up.
Thanks one more time for you time.

pepi74 said:
Open KDZ_FW_UPD as administrator by choosing "Run as administrator" in the right-click menu. Once it's open, set the type to "CDMA" and the mode to "DIAG". The people over at ******** will often tell you to set it to "3gqct" and "EMERGENCY MODE", ignore this as it will not work properly.
They say this way, so I will try it in CDMA mode
Try and retry
Yes, first time I pass this procedure got grey ANDROID logo, I think: that is that. But LG 540 stuck on that animation
So I give up.
Thanks one more time for you time.
Click to expand...
Click to collapse
Hi Pepi,
your stock ROM got stuck because of the leftover userdata and/or cache from the "fastboot" ROM.
Before you flash the stock ROM via KDZ, you should erase userdata and cache (fastboot -w or wipe data/factory reset and wipe cache partition from recovery), go STRAIGT to download mode thereafter (must NOT boot into android) and then flash non-fastboot, stock ROM!
There is a whole tutorial on Modaco or here on XDA, but the above info should be enough to get you past the LG logo or Android animation...
Hope it helps...!

robber_t said:
Hi Pepi,
your stock ROM got stuck because of the leftover userdata and/or cache from the "fastboot" ROM.
Before you flash the stock ROM via KDZ, you should erase userdata and cache (fastboot -w or wipe data/factory reset and wipe cache partition from recovery), go STRAIGT to download mode thereafter (must NOT boot into android) and then flash non-fastboot, stock ROM!
There is a whole tutorial on Modaco or here on XDA, but the above info should be enough to get you past the LG logo or Android animation...
Hope it helps...!
Click to expand...
Click to collapse
What you explain I made minimum ten times without success.
I go to fastboot mode
fastboot - w
fastboot erase system
fastboot erase boot ( so I erase all I can erase as user)
Then reboot phone , go directly to download mode and flash with KDZ file. But no success
Flash is ok, but when finished, and rebooted stuck with first LG logo animation before grey ANDROID animation. I will be very happy when your process give me solution for my problem, but it is not
Opposite ( as I say before) when I flash with fastboot rom, every rom work without any problems.

pepi74 said:
fastboot erase boot
Click to expand...
Click to collapse
Never done that
All I've had to do is put the phone into download mode and flash with the latest stock rom in 3gqct & diag. Once it wouldn't boot up, so I flashed a V20B with fastboot, did the usual 'fastboot.exe -w' & 'fastboot.exe erase system', then flashed the latest Australian V20C rom, did a Factory data reset and was all good again.
If you can get a fastboot rom to work then do a factory reset from Settings > Privacy > Factory data reset. This wipes more than the fastboot method for whatever reason. After doing the fastboot wipe the phone always has the date and time correct where as the Factory data reset is reset to default values.
Anyway, what stock rom are you trying to flash?

Destroyer-XDA said:
Never done that
All I've had to do is put the phone into download mode and flash with the latest stock rom in 3gqct & diag. Once it wouldn't boot up, so I flashed a V20B with fastboot, did the usual 'fastboot.exe -w' & 'fastboot.exe erase system', then flashed the latest Australian V20C rom, did a Factory data reset and was all good again.
If you can get a fastboot rom to work then do a factory reset from Settings > Privacy > Factory data reset. This wipes more than the fastboot method for whatever reason. After doing the fastboot wipe the phone always has the date and time correct where as the Factory data reset is reset to default values.
Anyway, what stock rom are you trying to flash?
Click to expand...
Click to collapse
Any stock rom is ok, since I use english language. ( try 20B 20C Baltic 20D) - downloaded from LG web page.
And if you use fastboot -w and fastboot erase system, phone also reset to factory state ( language and date and time is erased)
So you suggest that I flash with fastboot ROM, then wipe data from factory data reset and then try to flash with stock ROM from download mode?
P.S Why not to fastboot erase boot?
every clockwork recovery has boot.img, so even erased I can bring boot back

pepi74 said:
So you suggest that I flash with fastboot ROM, then wipe data from factory data reset and then
Click to expand...
Click to collapse
And then flash a kdz version V20C or D with kdz_update in 3gqct & diag. Fingers crossed it works!
pepi74 said:
P.S Why not to fastboot erase boot?
Click to expand...
Click to collapse
Never had to do it, no problem with it if it doesn't do any harm.

Destroyer-XDA said:
And then flash a kdz version V20C or D with kdz_update in 3gqct & diag. Fingers crossed it works!
Never had to do it, no problem with it if it doesn't do any harm.
Click to expand...
Click to collapse
Try as you say, but result was same: stuck

I am the exact same as you mate. I also have tried numerous times to get back to a stock ROM and found it stuck on the second LG screen before the android logo. I have done ALL the steps, erased everything, tried everything. It's a bit of a bummer these stock ROMs.

pepi74 said:
Try as you say, but result was same: stuck
Click to expand...
Click to collapse
Crap!!
So the factory data reset worked, and the kdz flash worked but still stuck in the loop?
Sounds like wiping the phone doesn't wipe everything OR that a kdz_update crash does some damage some how. Never had a crash (touch wood) in kdz_update so maybe thats why I can go back to the LG stock AUS V20C rom.
I wonder if you guy's have a bad sector that the stock rom writes to. If this is true, I'm not sure how we can fix it.
keewanchoapsss said:
I am the exact same as you mate. I also have tried numerous times to get back to a stock ROM and found it stuck on the second LG screen before the android logo.
Click to expand...
Click to collapse
A kdz_update crash too?

Destroyer-XDA said:
I wonder if you guy's have a bad sector that the stock rom writes to. If this is true, I'm not sure how we can fix it.
Click to expand...
Click to collapse
I assume that many LG540 has "bad sector" in memory blocks ( I have two), but also found that programs are clever enough to NOT WRITE to those sectors, they are marked as bad ,and skipped when writes ROM. So I am sure 99.99% that bad sectors in memory are not related with function of stock ROM. Fastboot rom works ok, so if bad sectors are problem, I assume that fastboot sectors also have problems.
I know that phone must have part of memory that cannot be erased, and maybe fastboot rom writes something to that part.
Also mystery is also: why some users can flash stock rom without any problem, and many other cannot.

Destroyer-XDA said:
A kdz_update crash too?
Click to expand...
Click to collapse
Nope, didn't crash. It done the whole flash at the end it stated finished and then when my phone went to reboot it got stuck on LG loading screen. Although flashing the Clockwork 2.5.0.6 stock 2.1 rom works, but clockwork doesn't get installed. It's really strange.

pepi74 said:
I assume that many LG540 has "bad sector" in memory blocks ( I have two), but also found that programs are clever enough to NOT WRITE to those sectors, they are marked as bad ,and skipped when writes ROM.
Click to expand...
Click to collapse
Bad sectors aren't marked on Windows unless you do a long format (or search for them), it finds them and marks them. If you wipe the partitions the info has gone and if remake the partitions, windows will write to them unless you scan for them again and then you have trouble. Linux is the same, it doesn't scan for bad sectors by default when formatting so it will write to the bad sectors too, afaik.
Now kdz_update doesn't scan for bad sectors so it writes the whole image to to the drive so its possible that it is writing to a bad sector and that's why you have trouble. Possibly
pepi74 said:
I know that phone must have part of memory that cannot be erased, and maybe fastboot rom writes something to that part.
Also mystery is also: why some users can flash stock rom without any problem, and many other cannot.
Click to expand...
Click to collapse
Could be right about the memory, even with a kdz flash you still have some of your previous setup, that's why we have to factory data reset, so it doesn't wipe everything. If I was the foil head type, I might be thinking..........
Do the fastboot roms only write data to the already made partitions? Does kdz? I know kdz changes my button assignments if I flash a V20C > 20A.
keewanchoapsss said:
Nope, didn't crash. It done the whole flash at the end it stated finished and then when my phone went to reboot it got stuck on LG loading screen.
Click to expand...
Click to collapse
Not a crash but still with kdz rom. Hmmm.....
keewanchoapsss said:
Although flashing the Clockwork 2.5.0.6 stock 2.1 rom works, but clockwork doesn't get installed. It's really strange.
Click to expand...
Click to collapse
I didn't have recovery with the stock clockwork rom either, had to install it manually.

Destroyer-XDA said:
Bad sectors aren't marked on Windows unless you do a long format (or search for them), it finds them and marks them. If you wipe the partitions the info has gone and if remake the partitions, windows will write to them unless you scan for them again and then you have trouble. Linux is the same, it doesn't scan for bad sectors by default when formatting so it will write to the bad sectors too, afaik.
Click to expand...
Click to collapse
In that case mystery is much bigger. Fastboot ROM works without problem. So if you theory is true it looks like that fastboot ROMs are less sensible to memory errors ( bad block) then stock ROM, and that thing to me looks nearly impossible.
So answer must be in something that is not erased, and not in ROM and bad sectors.
Also even you erase all data from phone there is always left part it cannot be erased, so it is possible that information of bad sectors are stored in that place.

Device is corrupt and can't be trusted?

So I flashed a factory image on my Nexus, and when it boots it tells me this, it should be unrooted and un tampered in every way because of the restore! But my device tells me this on boot? Why is that and how do I fix this? Thanks! Please help! Here's my flash process.
fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash radio
fastboot reboot-bootloader
fastboot flash system
fastboot flash recovery
fastboot format userdata
fastboot erase cache
fastboot flash boot
fastboot reboot
I should also add that I had multirom installed previously, if this changes anything.

fastboot flash boot boot.img, fastboot flash system systen.img, etc... Your commands are wrong
Sent from my Nexus 6 using Tapatalk

blueyes said:
fastboot flash boot boot.img, fastboot flash system systen.img, etc... Your commands are wrong
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My syntax was right, I did it that way I just didn't add the file names in my original post, sorry about that haha I did fastboot flash system system.img and so forth.

And you don't use erase, use format.. Really no need to erase/format if your flashing an image
Sent from my Nexus 6 using Tapatalk

blueyes said:
And you don't use erase, use format.. Really no need to erase/format if your flashing an image
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
erasing or formatting the cache partition isn't needed?

Don't need to format cache if your flashing cache.img. Going to be wiped with new img
Sent from my Nexus 6 using Tapatalk

blueyes said:
Don't need to format cache if your flashing cache.img. Going to be wiped with new img
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tend to just wipe it and not flash the img. I never flash the cache img, is this most likely the error?

I just flashed elementalx kernel and a supersu zip to remove the corruption message, the device is fine now, but I'm wondering why it said corrupt in the first place.

Common with stock kernel and root
Sent from my Nexus 6 using Tapatalk

blueyes said:
Common with stock kernel and root
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It gave me this error message before the device was rooted though, the device was clean at that point. I rooted after seeing that message. I installed elementalx kernel to get rid of the message and THEN rooted it.

H4X0R46 said:
It gave me this error message before the device was rooted though, the device was clean at that point. I rooted after seeing that message. I installed elementalx kernel to get rid of the message and THEN rooted it.
Click to expand...
Click to collapse
you dont read around xda or do any reseach, do you? lol! its because its been asked in many threads that have been started in this section. its something new that google has added to matshmallow. itll appear if your bootloader is unlocked, if you are using the stock kernel.

simms22 said:
you dont read around xda or do any reseach, do you? lol! its because its been asked in many threads that have been started in this section. its something new that google has added to matshmallow. itll appear if your bootloader is unlocked, if you are using the stock kernel.
Click to expand...
Click to collapse
I usually do but to be honest, I just kinda flipped and posted this in a hurry haha sorry man xD I'll read around next time! Thanks for saving my @$$ anyway lol so it's just the bootloader that triggers that? I knew marshmallow added those messages to it's kernel, I knew about that, had no clue that the open bootloader triggers it! Thanks!

simms22 said:
you dont read around xda or do any reseach, do you? lol! its because its been asked in many threads that have been started in this section. its something new that google has added to matshmallow. itll appear if your bootloader is unlocked, if you are using the stock kernel.
Click to expand...
Click to collapse
Also, I got the red error, did some reading and I should have gotten the orange one shouldn't I?

H4X0R46 said:
Also, I got the red error, did some reading and I should have gotten the orange one shouldn't I?
Click to expand...
Click to collapse
orange/red? maybe youre red is someone elses orange? honestly, ive no idea, as ive never gotten it. but.. i did find the image in the system partition. did it look like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

simms22 said:
orange/red? maybe youre red is someone elses orange? honestly, ive no idea, as ive never gotten it. but.. i did find the image in the system partition. did it look like this?
Click to expand...
Click to collapse
It was that exact screen yes! I wonder why I got that one because this was after a fresh stock rom flash! Everything stock, although, I did just use fastboot format userdata and fastboot erase cache instead of flashing the cache.img and userdata.img. could this matter?
Sent from my Nexus 6 using XDA Free mobile app

(Ignore this)

H4X0R46 said:
It was that exact screen yes! I wonder why I got that one because this was after a fresh stock rom flash! Everything stock, although, I did just use fastboot format userdata and fastboot erase cache instead of flashing the cache.img and userdata.img. could this matter?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
na, that wouldnt matter. i didnt see it because i flashed a custom kernel the first flash(i think).

simms22 said:
na, that wouldnt matter. i didnt see it because i flashed a custom kernel the first flash(i think).
Click to expand...
Click to collapse
I'm just worried that it is a corrupted part of my phone, I'm hoping it's just a false thing though. The phone boots and everything works fine, just wanting to be sure haha
Sent from my Nexus 6

H4X0R46 said:
I'm just worried that it is a corrupted part of my phone, I'm hoping it's just a false thing though. The phone boots and everything works fine, just wanting to be sure haha
Sent from my Nexus 6
Click to expand...
Click to collapse
it is a false thing

[ROM] Oxygen OS 3.2.5 untouched system.img + boot.img (twrp + fastboot)

If someone wants to make mirrors or a flashable zip, feel free to contact me and I will update thread
I've got my new OP3 today and what I've noticed that it runs with Oxygen OS 3.2.5. So I have looked around and saw that nobody backed up their 3.2.5 und uploaded it so I decided to do it.
Here is the download link: https://mega.nz/#!PJhzRDyL!wX12zmq9ptiu8gNbtfQfypB2Q6wGdu3IfNFFwi9acQk
The only requirement is an unlocked bootloader as fastboot doesn't allow to flash on locked devices
How to install:
via twrp:
- boot into twrp recovery
- press "install"
- press "install image" on the bottom right
- select the image and confirm on which partition it should flash
(not recommended) via fastboot:
- boot into fastboot
- use these commands to flash it:
ignore the little warning message and pe patient because it can take a while till you get a response from cmd because fastboot splits the image into 6 parts
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Note: if your phone isn't booting, flash supersu and it should boot.
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Fastboot flashing is not working.

Can you comment on the LTE reception and performance? It was the only issue i had with 3.2.4

Anyone tried looks tempting
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

TWRP is working, fastboot not.
Im on 3.2.5 now so yes its working, but only with TWRP

*Extracted fine with newest winrar*
Error on my end, sorry, thank you!

Chronzy said:
@hellcat50 zip is corrupt, "unexpected end of archive" when I tried to extract the img's. Downloaded it twice. Don't recommend wiping and trying to install at this time.
Would love to have this though, would you mind repacking?
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
you were able to extract the imgs? I downloaded it twice and got corrupt zip both times.
Click to expand...
Click to collapse
It did extract without any issues on my end.
I downloaded and extracted the file on my PC with the latest winrar.
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!

So, I will not lose my data, right?

No, but you should still do a backup in TWRP.

AcmE85 said:
No, but you should still do a backup in TWRP.
Click to expand...
Click to collapse
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)

Andrea224 said:
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Click to expand...
Click to collapse
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.

AcmE85 said:
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
Click to expand...
Click to collapse
Mmh...ok, thanks anyway.

So basically you should have unlocked bootloader, supersued, and TWRP'ed

Reconfigured said:
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Click to expand...
Click to collapse
SuperSU is not needed, why should it be? With this you overwrite the whole System partition, thus removing all mods including SuperSU and Xposed.

waiting for someone to confirm the LTE issue resolution.. if it's resolved, I'll flash this ASAP..

AcmE85 said:
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
Click to expand...
Click to collapse
Pick your brain for a moment if you don't mind...
Still having issues with both methods... in TWRP, at the install image screen i'm only getting boot and recovery partition options, supposed to have system too right?
Fastboot it hangs for a moment at an error of something about invalid sparsing but continues to flash, apparently successfully, but when i reboot system it just boots back to recovery.

Chronzy said:
Pick your brain for a moment if you don't mind...
Click to expand...
Click to collapse
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...

AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
Can we directly flash it over 3.2.4 in twrp ?

Any differences with the previous version guys?3.2.4....Tnx!!

AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
I was on an older recovery, should have known... that did it, Thanks! :good:

[RECOVERY][swift] Unofficial TWRP 3.1.1-0 touch recovery [2017-10-24]

DEPRECATED because I don't have the watch anymore. Might still work, might also not. Feel free to just try and iterate on my work.
TWRP touch recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is TWRP touch recovery for the Asus Zenwatch 3.
Usual disclaimer:
Code:
[I] I take no responsibility for any issues to your watch, your house, your job, your kitten, blah blah.[/I]
DON'T ALLOW TWRP TO MODIFY /SYSTEM IF YOU DIDN'T DISABLE DM-CRYPT! Recovery will then get overwritten on every boot though.
INSTRUCTIONS
It's recommended to boot it via "fastboot boot twrp_swift_*.img".
To flash, use the default "fastboot flash recovery twrp_swift_*.img". To boot into recovery, use adb or hold center and bottom button when off. Everything is tested to work fine.
If you want to return to stock recovery, flash recovery image from here.[/SIZE]
DOWNLOAD
3.1.1-0: View attachment twrp_swift_3.1.1-0.img
3.1.0-0: View attachment recovery_swift-3.1.0-0.img
3.0.2-0: View attachment recovery.img
SOURCES
Device/board config
Recommended platform manifest
Thanks a lot to @joeykrim and @T10NAZ, I used their Zenwatch 2 thread as a guide to compile the kernel and recovery.

This is interesting to see, I don't own a ZenWatch 3, but I'm curious how this would work. Would it be possible to flash custom ROMs on a watch? Maybe even port over Android 2.0 for the ZenWatch 3? Just curious how this would work on a watch.

To see something like this on a watch I must say you guys and everyone involved are truly awesome

Thank you!
I flashed a SuperSU zip file and the flash process worked well. Still root is not working because the SuperSU app crashes everytime something needs root rights...

g4rb4g3 said:
Thank you!
I flashed a SuperSU zip file and the flash process worked well. Still root is not working because the SuperSU app crashes everytime something needs root rights...
Click to expand...
Click to collapse
Which SuperSU.zip did you flash? Remember not every SuperSU.zip are compatible with Android wear. I am a bit out of time ..will try to play with root in my kernel.

janjan said:
Which SuperSU.zip did you flash? Remember not every SuperSU.zip are compatible with Android wear. I am a bit out of time ..will try to play with root in my kernel.
Click to expand...
Click to collapse
Nevermind, I got it working now using this tutorial: https://forum.xda-developers.com/ap...t-squashfs-t3319097/post65428079#post65428079

g4rb4g3 said:
Nevermind, I got it working now using this tutorial: https://forum.xda-developers.com/ap...t-squashfs-t3319097/post65428079#post65428079
Click to expand...
Click to collapse
Did you flash the recovery or also only boot it?

Maxr1998 said:
Did you flash the recovery or also only boot it?
Click to expand...
Click to collapse
Sorry for the late response, I didn`t flash it I just booted it. But I`ve sent the watch back and got a Gear S3 instead now.

g4rb4g3 said:
Sorry for the late response, I didn`t flash it I just booted it. But I`ve sent the watch back and got a Gear S3 instead now.
Click to expand...
Click to collapse
No prob, I already tested myself and flashing worked fine.

Thanks, can't wait to see other development stuff to follow too. Anybody tried to root through the recovery ?

I just updated the recovery to TWRP 3.1.0, grab the image from OP.

Latest TWRP installed and working fine. Thank you!

wokrs well!
Thank you
Now running :
https://forum.xda-developers.com/zenwatch-3/development/rom-asus-zenwatch-3-swift-t3537340

I added TWRP 3.1.1-0 to the OP, built on latest Nougat kernel from git and with latest TWRP sources in 7.1 tree. Enjoy!

is there an repair option for the partitions like there is in a stock TWRP? I do not see it. I am having some issues with my watch, one of which is that I am unable to mount /data, which is normally fixed with the repair option under the advanced wipe menu, but I do not see that option here. Please help.
Here is a link to the full issues I am experiencing.
https://www.reddit.com/r/zenwatch/comments/7de8ax/help_unbricking_zenwatch_3/

re: flashing roms in twrp
Coltonbyu said:
is there an repair option for the partitions like there is in a stock TWRP? I do not see it. I am having some issues with my watch, one of which is that I am unable to mount /data, which is normally fixed with the repair option under the advanced wipe menu, but I do not see that option here. Please help.
Here is a link to the full issues I am experiencing.
https://www.reddit.com/r/zenwatch/comments/7de8ax/help_unbricking_zenwatch_3/
Click to expand...
Click to collapse
Have you tried to "FORMAT DATA" in TWRP?
If not then go to the WIPE option in twrp and
select "format data" then you will be ready
to flash a zip file rom or IMG files.
Most likely your DATA partition is "encrypted"
which means the watch cannot successfully
complete a rom installation because it cannot
write to the data partition.
Wiping DATA is fine if your DATA partition is
not encrypted.
Good luck, have a great day!

Misterjunky said:
Have you tried to "FORMAT DATA" in TWRP?
If not then go to the WIPE option in twrp and
select "format data" then you will be ready
to flash a zip file rom or IMG files.
Most likely your DATA partition is "encrypted"
which means the watch cannot successfully
complete a rom installation because it cannot
write to the data partition.
Wiping DATA is fine if your DATA partition is
not encrypted.
Good luck, have a great day!
Click to expand...
Click to collapse
I do not see a "format data" option under wipe in TWRP on my zenwatch when i go to wipe i have either factory reset, or advanced wipe.
If i go to advanced wipe, and then select data, and slide to wipe, it says "unable to mount storage " "updating partition details..." "Failed to mount '/data' (invalid argument)" "...done" "unable to mount storage"

I have a problem with my ZW3: I unlockt the bootloader and booted into TWRP 3.1.1.0 (via fastboot, did not install it).
I wanted to transfer a ROM on my watch, but did not find a way to do it. So I rebooted the system.
But now everytime I want to boot into (stock) recovery (on the watch) I get the android droid with a exclamation mark. Is there a recovery image I can flash to solve this?
How do I transfer files on my watch? I don't see the device on my pc in the list (adb and fastboot work fine).
EDIT: Found a file here: https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
Do I have to flash all three files (system, boot and recovery) in order to get recovery back?
EDIT 2: When I boot the recovery from the file above via fastboot I also get the droid with the exclamation mark.

re: stock firmware
Der-Knuffi said:
I have a problem with my ZW3: I unlockt the bootloader and booted into TWRP 3.1.1.0 (via fastboot, did not install it).
I wanted to transfer a ROM on my watch, but did not find a way to do it. So I rebooted the system.
But now everytime I want to boot into (stock) recovery (on the watch) I get the android droid with a exclamation mark. Is there a recovery image I can flash to solve this?
How do I transfer files on my watch? I don't see the device on my pc in the list (adb and fastboot work fine).
EDIT: Found a file here: https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
Do I have to flash all three files (system, boot and recovery) in order to get recovery back?
EDIT 2: When I boot the recovery from the file above via fastboot I also get the droid with the exclamation mark.
Click to expand...
Click to collapse
@Der-Knuffi
Go into fastboot and flash all 3 of the image files (recovery.img, boot.img and system.img)
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot oem lock
When your done flashing reboot the watch.
The watch will boot into official stock Android Wear 1.5, have patience it takes a long time to boot.
Good luck, have a great day!

Misterjunky said:
@Der-Knuffi
Go into fastboot and flash all 3 of the image files (recovery.img, boot.img and system.img)
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot oem lock
When your done flashing reboot the watch.
The watch will boot into official stock Android Wear 1.5, have patience it takes a long time to boot.
Good luck, have a great day!
Click to expand...
Click to collapse
Thanks, I will try it. Isn't there a dump from AW2.0?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

[RESOLVED] Bricked after flashing firmware for Pie, stuck in md5 checksum bootloop

Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.

bump pls
even bad news is appreciated

Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?

Javellinh said:
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Click to expand...
Click to collapse
Thank you for answering.
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.

Hmm.. does phone in TWRP works like USB storage?

Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

swumo said:
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
Click to expand...
Click to collapse
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok

swumo said:
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
Click to expand...
Click to collapse
you can boot to stock recovery?

vinoxflame said:
you can boot to stock recovery?
Click to expand...
Click to collapse
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.

swumo said:
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
Click to expand...
Click to collapse
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

vinoxflame said:
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'm using a OP3T.
The link you provided points to a similar guide to the one I used. https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-tool-3t-unbrick-data-babloo-t3737791
I've already performed these steps, and the md5 problem happened after the process mentioned was completed.

swumo said:
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Click to expand...
Click to collapse
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.

redpoint73 said:
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
Click to expand...
Click to collapse
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Are there steps in fastboot that I can take to fix this phone?

swumo said:
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Click to expand...
Click to collapse
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
swumo said:
Are there steps in fastboot that I can take to fix this phone?
Click to expand...
Click to collapse
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).

swumo said:
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
Click to expand...
Click to collapse
I forgot a detail in the middle of the story.
Right after I flashed the pie firmware, it restarted and I was given a prompt that said something along the lines of "Flash successful and everything, but decryption failed. You will lose all data if you boot, are you sure?"
I turned off the phone, from there it bricked with a blank screen. It was then that I got the unbrick tool and went through the rest of the earlier story.

redpoint73 said:
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
Click to expand...
Click to collapse
I appreciate you reaching out and offering closure. It seems this phone is fried.
Thank you.

I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?

swumo said:
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
Click to expand...
Click to collapse
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you for dropping by.
Regarding the couple of errors in the MD5 checksum, "modem" and "dsp", the problem lied in that I didn't know which files I'm supposed to flash using fastboot to fill their spots.
By referring to the forum post of the firmware here, I found one workaround was to "consult META-INF/com/google/android/updater-script in the flashable zip of the firmware ... to check which file from the firmware-update directory goes to which partition."
From there, I inferred that "modem" takes the file named NON-HLOS.bin, and that "dsp" takes adspso.bin
Flashed them via fastboot, and I was greeted by a successful boot to stock OOS 3.1.2, the version provided by the unbrick tool I used.
However, it seems that the damage done to the phone (either by the failed firmware flash or the unbrick tool) has led to the internal storage being corrupted, or perhaps the damage was done to how the system decrypts internal storage. I am a medical student, so most of these intricacies are way out of my league.
I was hoping to recover the internal storage, but would gladly part with the data if it means I can use the phone again. There was nothing particularly important on the phone that the TWRP backup didn't have.

Pardon me, but which file system would be most suitable for each partition?
The Wipe>Advanced Wipe menu offers several file systems for several partitions. I'm inclined to leave everything as it is, but should I perhaps format the /system partition as f2fs for instance?