Situation:
yota3 in bootloop caused by fastboot command "fastboot flashing lock" with installed TWRP recovery and rooted. (don't ask me why)
Now i have only access to fastboot.
No recovery access
Bootloader locked
I tried flashing stock recovery (+ttp://www.mediafire.com/file/6hvldb...806223.7z/file) with MIFLASH, QFIL and TOOL STUDIO in EDL mode 9008 (fastbood oem edl) but without success.
Qualcomm com 9008 drivers ok
Have you any other idea?
Thank you.:good:
(SOLVED)
Re-flash following exactly the instructions.
Pay attention that during the first flash you have to select the 2 xml files and the second
time flash only one xml indicated.
https://forum.xda-developers.com/yot...-news-t3862999
Does anyone have a different recovery rom to try?
You have tried to unlock another time?
fastboot flashing unlock ?
skirep said:
You have tried to unlock another time?
fastboot flashing unlock ?
Click to expand...
Click to collapse
Thanks for the reply. I was starting to feel lonely and lost.:laugh:
Yes, I think I tried every fastboot command but no boot, no erase, no flash .. is allowed.
QFIL errors logs
Programmer Path:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\prog_emmc_firehose_8953_ddr.mbn
Image Search Path: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images
PATCH file path ignored: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch0.xml
PATCH file path:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch0.xml
Image Search Path: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images
Invalid RAWPROGRAM file path ignored: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\rawprogram_unsparse_without_QCN.xml Ignored
Invalid RAWPROGRAM file path ignored: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\rawprogram2.xml Ignored
Invalid PATCH file path ignored:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch2.xml
PATCH file path ignored: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch0.xml
PATCH file path:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch0.xml
Start Download
Program Path:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\prog_emmc_firehose_8953_ddr.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\QSaharaServer.exe -p \\.\COM10 -s 13:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\prog_emmc_firehose_8953_ddr.mbn 'Current working dir: C:\Users\paolo\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\prog_emmc_firehose_8953_ddr.mbn
18:30:22: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
18:30:22: ERROR: function: sahara_main:854 Sahara protocol error
18:30:22: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
This is the FILES LIST of the "RECOVERY ROM" i have.
adspso.bin
boot.img
cdt.img
cmnlib.bin
cmnlib64.mbn
custom.img
ddr.img
devcfg.mbn
dummy.img
emmc_appsboot.mbn
filelist.txt
gpt_backup0.bin
gpt_both0.bin
gpt_main0.bin
junklog.img
keymaster.mbn
letvconfig.img
lksecapp.img
lksecappbak.img
logdump.img
mcfg.img
mota.img
NON-HLOS.bin
oem.img
params.img
partition.xml
patch0.xml
persist.img
prog_emmc_firehose_8953_ddr.mbn
rawprogram0.xml
rawprogram0_BLANK.xml
recovery.img
recoverybp.img
rpm.mbn
sbl1.mbn
splash.img
syscfg.img
system.img
tz.mbn
wipe_rawprogram_PHY0.xml
wipe_rawprogram_PHY1.xml
wipe_rawprogram_PHY2.xml
wipe_rawprogram_PHY4.xml
wipe_rawprogram_PHY5.xml
wipe_rawprogram_PHY6.xml
wipe_rawprogram_PHY7.xml
Click to expand...
Click to collapse
jelixsu
Today, 02:59 AM |#78
Junior Member24 posts Thanks: 2
first write firmware, this step can save your phone in most brick situation.
*ttp://download1518.mediafire.com/rvo7la5b5ohg/6hvldbq5lojxlgn/yota3_images_Y3XSCN06A1000MPX1806223.7z
then extricating the file
fastboot
*ttps://forum.xda-developers.com/attachment.php?attachmentid=4651886
driver Qualcomm_USB_Driver_V1.0.zip
*ttps://forum.xda-developers.com/attachment.php?attachmentid=4651890&d=1543200054
twrp rec.img
*ttps://drive.google.com/drive/folders/14MO7_WUwOkVl94apC29YMzbuWKePjjTV
fastboot flashing unlock
fastboot flash recovery RECOVERY.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flashing lock
-------------------------------------------
into original recovery
press up+POWER then start ,still press up
double clean the date and devil-cache
-------------------------------------------
<only want root>will get twrp and magisk
fastboot flashing unlock
fastboot flash recovery rec.img
fastboot flash recoverybp rec.img
-------------------------------------------
flash new rom(R05 link)
*ttps://1drv.ms/u/s!Ak8Mx9Xz2kf8b0M0UXQ6zMkLPSU
press up+POWER into twrp
then triple clean
install R05
-------------------------------------------
in the middle of time
PIN LOCK,I have the same problem, try many way the solve it but.........
after unlock even brick the cell phone
follow those step by step can save brick phone again!!
Click to expand...
Click to collapse
If this replay in one other tread is for me i tell you that i cannot "fastboot flash, unlock, boot... anything" because i have bootloader locked.
Anybody has the original -prog_emmc_firehose_8953_ddr.mbn- for our YOTA3 ?
Thanks
paolinger said:
If this replay in one other tread is for me i tell you that i cannot "fastboot flash, unlock, boot... anything" because i have bootloader locked.
Click to expand...
Click to collapse
i have the same question with you.
yesterday i try to restore system, but forget press 7 times develop option then open oem unlock.
last time i remember after reset don`t open oem unlock .........it's ok. this time brick......
https://item.taobao.com/item.htm?id=562597407389
i will try to connecet the seller to solve the problem. have any news will tell you
jelixsu said:
i will try to connect the seller to solve the problem. have any news will tell you
Click to expand...
Click to collapse
I am not so experienced but i think we need the ORIGINAL STOCK ROM with SIGNED PROGRAMMER to flash with QFIL.
paolinger said:
I am not so experienced but i think we need the ORIGINAL STOCK ROM with SIGNED PROGRAMMER to flash with QFIL.
Click to expand...
Click to collapse
the seller try one day fail....he say need takethe emmc chip away then direct write something.
---------- Post added at 11:04 AM ---------- Previous post was at 11:04 AM ----------
paolinger said:
I am not so experienced but i think we need the ORIGINAL STOCK ROM with SIGNED PROGRAMMER to flash with QFIL.
Click to expand...
Click to collapse
the seller try one day fail....he say need take the emmc chip away then direct write something.
jelixsu said:
the seller try one day fail....he say need takethe emmc chip away then direct write something.
---------- Post added at 11:04 AM ---------- Previous post was at 11:04 AM ----------
the seller try one day fail....he say need take the emmc chip away then direct write something.
Click to expand...
Click to collapse
Wow! A radical intervention!?
Do you think that exists a FACTORY CODE to unlock the bootloader of our yota3? Like "FASTBOOT OEM UNLOCK 123456ABCD"?
jelixsu said:
the seller try one day fail....he say need takethe emmc chip away then direct write something.
---------- Post added at 11:04 AM ---------- Previous post was at 11:04 AM ----------
the seller try one day fail....he say need take the emmc chip away then direct write something.
Click to expand...
Click to collapse
Did the seller solved your problem?
Finally recovered the device and succesfully ugraded to yota 3+
Great work of China team
paolinger said:
Finally recovered the device and succesfully ugraded to yota 3+
Great work of China team
Click to expand...
Click to collapse
Could you please provide instructions how to achieve this? HexaDog deleted his post, regarding the upgrade of the y3 to y3+...
leser12 said:
Could you please provide instructions how to achieve this? HexaDog deleted his post, regarding the upgrade of the y3 to y3+...
Click to expand...
Click to collapse
Yes i will upload the files at:
https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
For the moment you can read the tutorial by Yunyao shopkeeper
and team.
paolinger said:
Finally recovered the device and succesfully ugraded to yota 3+
Great work of China team
Click to expand...
Click to collapse
How did you manage to unbrick your phone? I can only boot in qfil and don't know if bootloader is unlocked things got messy during the upgrade.
Woud be great if ou could help or at least tell what you did.
killsers said:
How did you manage to unbrick your phone? I can only boot in qfil and don't know if bootloader is unlocked things got messy during the upgrade.
Woud be great if ou could help or at least tell what you did.
Click to expand...
Click to collapse
Re-flash following exactly the instructions.
Pay attention that during the first flash you have to select the 2 xml files and the second
time flash only one xml indicated.
https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
paolinger said:
Re-flash following exactly the instructions.
Pay attention that during the first flash you have to select the 2 xml files and the second
time flash only one xml indicated.
https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
Click to expand...
Click to collapse
Thanks for the reply. I did that i forgot to check reset after download in the first time and the installation failed. now i get the following error message every time.
Edit: HvMES from the other thread had the solution just try it if you are stuck like me. Love you all guys really great community!
Related
I experience the same symptoms as this thread, but the proposed solution does not work for me. (the sd_update.log says
Failure: OSBL°æ±¾Æ¥Åäʧ°Ü.
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
Click to expand...
Click to collapse
I rooted the phone, and misread the instructions for altering the recovery.img, which is what caused the problem in the fist place.
I have tried flashing with B925, B927 without luck.
I have also tried to use sudo fastboot boot recovery.img with a local recovery.img, and tried flashing fastboot flash recovery recovery.img - but it says
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
which i presume is because the bootloader is not unlocked.
I also tried fastboot getvar all - but that came out empty.
I also tried http://androidforums.com/huawei-ideos-x5-u8800/593253-unlock-bootloader-huawei-supply-code.html but the model is not listed...
I have an idea that essentially i just have to get in and delete recovery.img and rename recovery.backup.img to recovery.img - but i haven't got a clue about how to do it.
Phone responds to fastboot commands.
I look forward to your input.
Jonas
[SOLVED] patch to enable B919 was the missing link
Solved: www .shadowandy .net/2013/01/huawei-honor-u8860-shendu-rom-flashing-guide.htm the first link (dload_B929rus.rar (MD5 = 7264f7ad3bd7eebd298a8be978823734)) solved the problems, i am now on a B919 chinese rom.
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?
Hi !
I desesperatly seeking a root process for the Archos Diamond 2 Plus.
I can not find it by google.
As it looks like the P9000 of Elephone, I wondered if it was possible to use its recovery.img and supersu 1 and 2.
An idea ? A link for tutorial or for the stock rom (If root process failed) ?
Please ?
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
fanfan7110 said:
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
Click to expand...
Click to collapse
What android version?
android 6.0 marshmallow
fanfan7110 said:
android 6.0 marshmallow
Click to expand...
Click to collapse
You can boot into fastboot, which is good, in fastboot, type fastboot oem startftm. It will give you an error in the command line but what this allows you to do, is push files into partitions that are mounted R/W, that is of course, if this actually works for your device since every device is different.
Report results!
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Please please please make a whole IMG backup since what we'll do might brick your device. I can't help you till Thursday, hit me up on Thursday with a reply on this thread.
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Also, it is supposed to say failed when you start it.
hummm i can't take a backup of boot.img, because SU is not installed..
fanfan7110 said:
hummm i can't take a backup of boot.img, because SU is not installed..
Click to expand...
Click to collapse
Well, since the device is running mtk, try this. Flash the superuser binary and report, also, I am NOT responsible for anything, YOU are making these changes.
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
fanfan7110 said:
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
Click to expand...
Click to collapse
Well, now you have a mission to somehow port a working recovery to your phone.
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.
Hello, I have bricked my phone when I was trying to go back to stock firmware from RR.
TWRP does not work for me, internal storage can not be read (even though I've tried all images I've found for this phone..) so I had to do it through fastboot and hwota.
Somehow it bricked the phone and I get
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 7 (teeos image)
Error NO: 1 (security verify failed!)
If I extract TEEOS.img from UPDATE.app (8.0.0.145(C432)) and try
fastboot flash teeos TEEOS.img
I get
FAILED (remote: command not allowed)
I've tried to flash
SYSTEM.img
RECOVERY_RAMDIS.img
RAMDISK.img
If anyone know what I can do to fix this please enlighten me..
monsterkaka said:
Hello, I have bricked my phone when I was trying to go back to stock firmware from RR.
TWRP does not work for me, internal storage can not be read (even though I've tried all images I've found for this phone..) so I had to do it through fastboot and hwota.
Somehow it bricked the phone and I get
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 7 (teeos image)
Error NO: 1 (security verify failed!)
If I extract TEEOS.img from UPDATE.app (8.0.0.145(C432)) and try
fastboot flash teeos TEEOS.img
I get
FAILED (remote: command not allowed)
I've tried to flash
SYSTEM.img
RECOVERY_RAMDIS.img
RAMDISK.img
If anyone know what I can do to fix this please enlighten me..
Click to expand...
Click to collapse
Can you still get a bootloader mode?
If you still get bootloader enough to fix it.
This job must be solved on DC Phoenix Only
I'm sucess with this link
https://www.******.com/recover-huawei-bricked-devices-dc-phoenix/
I accomplished these images. ..good luck..
My device : huawei nova 2i [RNE-L22]
You can try this:
https://forum.xda-developers.com/showpost.php?p=74853704&postcount=91
Im not sure why is was removed from first post...?
taddzio said:
You can try this:
https://forum.xda-developers.com/showpost.php?p=74853704&postcount=91
Im not sure why is was removed from first post...?
Click to expand...
Click to collapse
I payed for funkyhuawei... it fixed the recovery. I now have a working eRecovery and recovery but failed to download OS. I will try hwota method. Does it work with 8.0.0.145(c432)??
Just download the official files and run?
The download link seem to be removed
monsterkaka said:
I payed for funkyhuawei... it fixed the recovery. I now have a working eRecovery and recovery but failed to download OS. I will try hwota method. Does it work with 8.0.0.145(c432)??
Just download the official files and run?
Click to expand...
Click to collapse
Can you fix it?? Please let me know how you do it?? I´m in the same situation
ï have the same problem please add me on discord if you can help i will reward you Moose#9703