Okay, this is my story about my baby.
BEFORE UNLOCKING MY BOOTLOADER:
1) I had 4.4.2, then got the OTA to 4.4.4
2) Then got Invitation to Soak Test.... Got 5.0.2 and received two versions (forgot the versions)
3) Got kicked out of MFN for sharing info
4) Till received the 3rd and final 5.0.2 OTA (22.27.1 maybe)
Got tired with waiting with a buggy 5.0.2
One fine day, unlocked my bootloader.... the fun started
AFTER UNLOCKING MY BOOTLOADER:
1) Installed TWRP 2.8.6 and safely backed up my Stock ROM
2) Installed Custom ROMS one after another (CM12.1, PA, AOSP)
3) Used PA for a long time as it had really very less bugs
4) Stumbled upon Euphoria OS
5) Now Euphoria is my current OS
Okay, enough stories.....
My Question is.... How to revert to 4.4.4 in the safest way possible....?
I don't want to brick it.....
Seen many posts here in XDA but all are confusing.... having mixed user reviews.... Most hard bricked.... Others Happy
So, please help me.
http://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
follow this guide !
ChaTy said:
http://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
follow this guide !
Click to expand...
Click to collapse
I remember very well something mentioned about flashing gpt.bin, boot.img and something else.
I've read somewhere in this forum, that without flashing these, we can have our phone up and running KitKat 4.4.4.\
Also these files are responsible for the bricking process.... Can you please confirm?
Just don't flash gpt.bin and motoboot.bin, or you cuold just flash any KitKat ROM
emilio1625 said:
Just don't flash gpt.bin and motoboot.bin, or you cuold just flash any KitKat ROM
Click to expand...
Click to collapse
Didn't get you... What do you mean by flashing any KitKat ROM?
Download Full 4.4 xml Formatted ROM from filefactory and flash files one by one without gpt,bin and motoboot.bin
Adarsh1998 said:
Download Full 4.4 xml Formatted ROM from filefactory and flash files one by one without gpt,bin and motoboot.bin
Click to expand...
Click to collapse
Okay let me get this straight....
1) GPT is the partition info right? So flashing it will brick? Will it get flashed?
Or, will it show an error?
2) What about motoboot? What is that file? I know that boot.img is the kernel.
What has motoboot got to do with bricking?
Just being curious... please don't mind
You cannot skip any commands while downgrading from 5.0.2 to 4.4.4..if you do it correctly just as mentioned,then you will have kitkat running as before..
And btw you mentioned that most guys on xda here hardbricked while flashing kk image,which is false..most guys succeed and the ones who brick their phone post about it on xda so it looks like almost everyone is hardbricking their phone...
and just make sure that you are flashing 4.4.4 and not 4.4.2 image,ota'ing to .4 from .2 messes up the gpt/bootloader which leads to hardbrick
Sent from my condor using Tapatalk
Faiz Syed said:
You cannot skip any commands while downgrading from 5.0.2 to 4.4.4..if you do it correctly just as mentioned,then you will have kitkat running as before..
And btw you mentioned that most guys on xda here hardbricked while flashing kk image,which is false..most guys succeed and the ones who brick their phone post about it on xda so it looks like almost everyone is hardbricking their phone...
and just make sure that you are flashing 4.4.4 and not 4.4.2 image,ota'ing to .4 from .2 messes up the gpt/bootloader which leads to hardbrick
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I get you.... And now I am back to 4.4.4 with a huge problem
My boot loader is unlocked!!!
I try to enter the command fastboot oem lock begin
It says something like "(bootloader) ready to flash signed images"
I tried first only fastboot oem lock..... It said something like failed to verify system image signature!
So decided, to first type in
fastboot oem lock begin
fastboot flash gpt gpt.bin
fastboot flash motoboot motoboot.img
At this point both failed to flash just like before..... So I went to
fastboot flash logo logo.bin (Success)
Now when I type
fastboot flash system system.img_sparsechunk.0
It says, signature validation failed.
So what to do? How to relock my phone? Or id doesn't need relocking.
Just suggest me a way to remove that "Boot Loader Unlocked warning"
Rohitagni said:
I get you.... And now I am back to 4.4.4 with a huge problem
My boot loader is unlocked!!!
I try to enter the command fastboot oem lock begin
It says something like "(bootloader) ready to flash signed images"
I tried first only fastboot oem lock..... It said something like failed to verify system image signature!
So decided, to first type in
fastboot oem lock begin
fastboot flash gpt gpt.bin
fastboot flash motoboot motoboot.img
At this point both failed to flash just like before..... So I went to
fastboot flash logo logo.bin (Success)
Now when I type
fastboot flash system system.img_sparsechunk.0
It says, signature validation failed.
So what to do? How to relock my phone? Or id doesn't need relocking.
Just suggest me a way to remove that "Boot Loader Unlocked warning"
Click to expand...
Click to collapse
You can only relock bootloader after flashing the entire stock rom including the gpt ,bootloader and all..if you want to remove the bootloader unlock warning just follow this link,download one of the bootlogos you like and flash it in twrp.
http://forum.xda-developers.com/moto-e/themes-apps/boot-logo-t2836629
Sent from my condor using Tapatalk
Faiz Syed said:
You can only relock bootloader after flashing the entire stock rom including the gpt ,bootloader and all..if you want to remove the bootloader unlock warning just follow this link,download one of the bootlogos you like and flash it in twrp.
http://forum.xda-developers.com/moto-e/themes-apps/boot-logo-t2836629
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Can't I fully flash the ROM?
I mean.... There has to be a way.....
And also, I have to tell you I won't flash twrp right now.
UPDATE: I managed to flash a custom logo via fastboot..... Can't I flash the original one?
You should wiping the cache from fastboot and doing it again
Sent from my condor using Tapatalk
Faiz Syed said:
You should wiping the cache from fastboot and doing it again
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I figured it out bro...
U can't relock on .XML signed zip factory images.... Also, the logo.bin in the zips are absolutely stock, not modified to replace the warning boot loader unlocked message.
Hence, it was showing...
But I might as well stay unrooted.
Rohitagni said:
I figured it out bro...
U can't relock on .XML signed zip factory images.... Also, the logo.bin in the zips are absolutely stock, not modified to replace the warning boot loader unlocked message.
Hence, it was showing...
But I might as well stay unrooted.
Click to expand...
Click to collapse
Great then,as you were planning to lock i thought you were selling your phone thats why you wanted an oem lock......just flash another bootlogo and nobody will be able know unless they get into the bootloader[emoji6]
Sent from my condor using Tapatalk
Related
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
GaryWS said:
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
Click to expand...
Click to collapse
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
pruano said:
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
Click to expand...
Click to collapse
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
GaryWS said:
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
Click to expand...
Click to collapse
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
pruano said:
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
Click to expand...
Click to collapse
Pruano, using fastboot, the erase command seems to work but format does not. Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
and just for interest i had to use: "fastboot flash modem modem.img"
GaryWS said:
Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit:and just for interest i had to use: "fastboot flash modem modem.img"
Click to expand...
Click to collapse
Did not know fastboot would recognize that partition, not on the docs.
Always learning.
GaryWS said:
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
Click to expand...
Click to collapse
Yes, unlocked bootloaders do not interfere with OTAs
Regarding the modem, in truth it was a long shot, just a step to restore to pristine state.
The knowledge that the P7500 modem works best with custom ROMs and flashing it as a common procedure is relatively new, no wonder one had to guess that it would interfere with OTAs (as its not obvious, probably the OTA install does some kind of background safety check using the modem firmware as base); good to know for the future.
I tried to flash a downgrade image to my moto e 2nd gen. Now Im stuck in bootloader and a warning message for unlocked bootloder. Ive tried to flash logo.bin, and other images aswell with no luck. It keeps asking me to install a valid signed images, I don't know where to find these images. Please help!
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
pemhak said:
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
Click to expand...
Click to collapse
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder: https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
I got my device back!! I did succeed to flash it with this rom "surnia_stock_5.0.2.zip" with TWRP. I did not have the patience to wait at the Motorola logo when booting, I have to wait 2-3 min and 2-3 min for services to start. for the device to boot. But now it doesn't register any sim card when at desktop?!?
squid2 said:
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder:
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
Click to expand...
Click to collapse
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
pemhak said:
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
Click to expand...
Click to collapse
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
squid2 said:
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
Click to expand...
Click to collapse
Ok, thanks. I will wait for download to complete and flash that image.
pemhak said:
Ok, thanks. I will wait for download to complete and flash that image.
Click to expand...
Click to collapse
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Noeljunior said:
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Click to expand...
Click to collapse
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
pemhak said:
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
Click to expand...
Click to collapse
And I'm back with my Moto E! Thank you! I wasn't doing some of those commands and with all those commands it works! Thank you!
Hi, I used fastboot to boot TWRP without flashing it (using fastboot boot twrp.img). Foolishly of me when exit TWRP I was asked to disabled Stock Recovery wich I swiped yes. Now my stock recovery is gone. How do I enable it via TWRP again without having to flash it? or what are my options? phone functionlity was not afected, just the stock recovery.
thanks.
imho you either use twrp OR stock recovery. so in my opinion youve done all right.
Download fastboot image.. extract boot.img from it. Boot in TWRP using fastboot .. then install->install image->boot.img(file you extracted)->flash->choose recovery, not boot when where to flash->done.
If it doesn't work then flash the whole fastboot image with mitool.
h0LLe said:
imho you either use twrp OR stock recovery. so in my opinion youve done all right.
Click to expand...
Click to collapse
dragneelfps said:
Download fastboot image.. extract boot.img from it. Boot in TWRP using fastboot .. then install->install image->boot.img(file you extracted)->flash->choose recovery, not boot when where to flash->done.
If it doesn't work then flash the whole fastboot image with mitool.
Click to expand...
Click to collapse
I ended up flashing the whole image beacuse it bricked when using the command "fastboot oem lock".
any idea why it bricked? i did flash a stock recovery before in order to lock it again.
After rooting it im interested in locking the bootloader again. Maybe I skipped a procedure in order to lock the bootloader again??
Right now im rooted, phone working, stock recovery (since I flashed a fastboot image with SP tools) and unlocked bootloader but I want to lock it without bricking it again.
thanks.
pach33 said:
I ended up flashing the whole image beacuse it bricked when using the command "fastboot oem lock".
any idea why it bricked? i did flash a stock recovery before in order to lock it again.
After rooting it im interested in locking the bootloader again. Maybe I skipped a procedure in order to lock the bootloader again??
Right now im rooted, phone working, stock recovery (since I flashed a fastboot image with SP tools) and unlocked bootloader but I want to lock it without bricking it again. (i lock bootloader for my friend which has redmi 3s)
thanks.
Click to expand...
Click to collapse
To lock bootloader again you must flash stock image via fastboot with "lock bootloader" bat file (it is in stock image flashtool zip). But why U need to lock bootloader? i dont see sense to do it.
dromaczek said:
To lock bootloader again you must flash stock image via fastboot with "lock bootloader" bat file (it is in stock image flashtool zip). But why U need to lock bootloader? i dont see sense to do it.
Click to expand...
Click to collapse
Hi, thanks for the answer, I want to lock it because some features got disabled when unlocking the bootloader, like xiaomis "Find mi Device". I also read that having the bootloader unlocked may compromise your data security.
pach33 said:
Hi, thanks for the answer, I want to lock it because some features got disabled when unlocking the bootloader, like xiaomis "Find mi Device". I also read that having the bootloader unlocked may compromise your data security.
Click to expand...
Click to collapse
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
chandradeepdey01 said:
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
Click to expand...
Click to collapse
He write only true! He could "read that having the bootloader unlocked may compromise your data security" :laugh::laugh::laugh::laugh::laugh:
chandradeepdey01 said:
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
Click to expand...
Click to collapse
dromaczek said:
He write only true! He could "read that having the bootloader unlocked may compromise your data security" :laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Glad I made you guys laugh. :good: Next time I will better use the noob friendly Q&A.
pach33 said:
Glad I made you guys laugh. :good: Next time I will better use the noob friendly Q&A.
Click to expand...
Click to collapse
Woah, didn't mean to offend you bro. It was sarcasm.
It is replaced not disabled...
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.
Download the stock ROM HERE
and unzip it along with the abd fastboot archives (inside it's folder)
put your phone on fastboot mode: volume down + power
open abd + fastboot HERE (shift + right mouse button - open command window)
it will open a command window
write: fastboot devices and hit enter - make sure it shows numbers like serial numbers
past this comand:
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
hit enter and wait, you are done!
PS:
1. doing this fixed "Your device has failed verification and may not work properly" showing on my brand new phone
2. it is just flashing stock room it is not rooting or unlocking boothloder so it will not make you lose your warranty
3. as for me (I'm from brazil) its working perfectly
CREDITS FOR THE ROOM: stockrom.net
Force close
I'm facing force closes from apps like file manager Moto apps and more. Did you face these?
Are you sure this is the stock rom for the XT1710-07? The stock rom you posted is exactly the same as
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
But good to know that it worked for you. Who knows, maybe now there is only one RETAIL stock rom which works for all variants (except VZW and CN)?
@lexie90
1- Room = quarto, sala. The correct name is "ROM"
2- Original credits to ROM is for Adriana Pignata (Google+) and mirrors.lollinet.
This site stckrom.net simply copying.
Since the origin of this code is unknown and the OP is not a developer, members are advised to exercise due caution - in other words, you take the risk entirely.
I credited the site I got It from, How could I know where they got It from?
Junior Passos said:
@lexie90
1- Room = quarto, sala. The correct name is "ROM"
2- Original credits to ROM is for Adriana Pignata (Google+) and mirrors.lollinet.
This site stckrom.net simply copying.
Click to expand...
Click to collapse
Thanks for the Very important correction
LenAsh said:
Since the origin of this code is unknown and the OP is not a developer, members are advised to exercise due caution - in other words, you take the risk entirely.
Click to expand...
Click to collapse
Yep this note was in the post until the ADM edited and apparently took It off
If my Moto don't have unlock bootloader, I can flash it?
lexie90 said:
I credited the site I got It from, How could I know where they got It from?
Click to expand...
Click to collapse
That's exactly the point I made. Other members NEED to understand the risks this brings.
LenAsh said:
That's exactly the point I made. Other members NEED to understand the risks this brings.
Click to expand...
Click to collapse
Yep I agree! I dont understand why the ADM took the advertising out
this rom stock work with other variants of XT1710, in Mexico we have XT 1710-06, please you can tell me?
XT1710-06 Variant
Does anyone has the XT1710-06 variant? it's the Latin American Retail version.
I'm still on APRIL 1st Security Patch, and I'm really starting to wonder if this version is ever going to upgrade to 8.0 or whatever.
Is there a way to go back to full stock rom in case I mess up in the process of installing a different official rom?
Thanks!
Not exactly the best at all with phone development, and this may be the dumbest question ever, but can I flash this onto a Samsung phone somehow? I am just wondering. Like I said, sorry if it is a dumb question I am not good at all with phone stuff haha
@Junior Passos Were you able to install OTAs after installing this stock retail rom?
gngshpor said:
Not exactly the best at all with phone development, and this may be the dumbest question ever, but can I flash this onto a Samsung phone somehow? I am just wondering. Like I said, sorry if it is a dumb question I am not good at all with phone stuff haha
Click to expand...
Click to collapse
You can't put it on a samsung. You needa put that Samsung's roms on that samsung.
Hi to all. Have a question. I bought Moto z2 play xt 1710-11 with ZUI!!! where can I get working global stock rom?
Yevgeniy1985 said:
Hi to all. Have a question. I bought Moto z2 play xt 1710-11 with ZUI!!! where can I get working global stock rom?
Click to expand...
Click to collapse
Hi, nowhere.
I used 2 stock ROMs to get a clean Nougat with working modems.
KirMit said:
Hi, nowhere.
I used 2 stock ROMs to get a clean Nougat with working modems.
Click to expand...
Click to collapse
Maybe custom? Something with working gapps and Moto mods
Yevgeniy1985 said:
Maybe custom? Something with working gapps and Moto mods
Click to expand...
Click to collapse
Year, just replace with correct modem images.
KirMit said:
Year, just replace with correct modem images.
Click to expand...
Click to collapse
If it possible, could you give me a link to read materials how to do that?