Related
Hey so this issue is actually solved. If you want to see the process that I went through to get to the solution, please do! Its not that hard, I promise. Maybe a little stressful, but totally doable. Cheers!
----------------------------------------------------------------
I'm currently stumped on how to fix this issue that I'm currently having with my HTC Rezound at the moment. I did not buy this from any Verizon retailer, I bought it online in 2012. Anyway, the only issue that I've had the past few months is just that my battery kept dying super quickly and that my phone would randomly shut off after flashing Liquid Smooth ROM on my phone. I originally live in California but I moved to Spain, so any option of "take it to a retailer" or "take it to a cellphone repair shop" is not practical since NOBODY in Granada has ever heard of this phone.
The last time I had my phone operational was when I was using Mobile Data to chat with one of my friends on an app when it died, as usual. This time, I wasn't home to immediately plug it into the charger. One other thing I'd like to point out is that the number one reason why I think my battery kept dying so quickly is that while I was in Morocco, I was using an adapter to charge my phone. Maybe the difference in voltage fried my battery, not sure.
Anyway, I was out for at least 3-4 hours before I finally got home to put it on the charger. I plugged it in and went to bed without even looking at my phone. Woke up the next morning to power it up to find that not even the orange light is on (or green when fully charged). I unplug it, plug it back in and nothing happens. I take out my battery, keep it out for a couple hours and put it back in. I hold the Power button until the phone vibrates, screen turns on with the green HTC logo on a white screen, and then turns off. I take out the battery a couple more times and still same thing. I decide to leave the battery out for 2 hours and then put it back into the phone and directly to charge. The orange light turns on for about 3-5 seconds before turning off.
If I try to push the power button, nothing happens unless I take out the battery again. So I leave the battery to charge but then my phone started to get a little warm. Instead I just disconnect and leave the battery out of the phone for about 3 weeks until I had 2 spare new batteries shipped to me here in Spain. Once I got the batteries, I tried once again to get my phone working by replacing the batteries. Orange light comes on for 3-5 seconds before going out and its the same thing as before. I plug it into my laptop, use the CMD "adb devices" and I get nothing listed or "error: device not found". I can only boot into hboot by using Power + Down Volume and thats about it. By the way, its S-OFF and rooted with a custom ROM (Liquid Smooth) and the recovery should be Amon Ra.
If I get to fastboot/hboot and I select Factory Reset, Recovery, or Reboot, the screen dims, vibrates a bit and flashes the HTC logo on a white screen for 3 seconds before turning off. As of now, I can't connect to my phone through the PC as it doesn't even read via USB port, HTC Sync doesn't read, and I can't reach my phone through CMD prompt. Does anyone have any information on how I could fix this? And even though I have read most articles about the orange light thing and clockworks recovery, I'm still open to any/all solutions.
Update #1
Since I have not gotten any help from any community members or from other people, I decided to pursue this on my own to the best of my abilities. I decided to start looking up different articles with the same symptoms that I have and to see what the solutions were. Long story short, I combined a few solutions and one of the things some people did was just reinstall stock ROM altogether. For now, I am happy to say that I can access my phone via Command Prompt, but ONLY with "fastboot" commands. I came to this realization when I was looking up how to install stock ROM when one of the commands was to put "fastboot reboot-bootloader" and I happily had much success. Just make sure you're in FASTBOOT USB or else it won't work. I also ended up reinstalling all my HTC Drives and HTC Sync. At the moment, I cannot access internal memory via USB nor connect to HTC Sync. Also, to see what other commands that are available to your disposal, you can type "fastboot help".
Update #2
Since the last post, I've been looking around. Found out that the best solution would be to flash a stock RUU onto the phone. Requirements before flash would be to erase everything but the only command I can get to erase is with "fastboot earse cache" and thats about it. Everything else is unsuccessful. Anyway, instead of just going straight to downloading and flashing stock RUU, I accidentally decided to try following a procedure I read step by step by first locking bootloader with the command "fastboot oem lock" command and phone immediately shuts off. I try to power on again but just does same as before: boots to green HTC logo on white, stays on a for a few seconds, and turns off. This time, though, without the bootloader coming up. I believe I have bricked my phone.
Can you still get to Fastboot? If so, unlock again, and then download the latest TWRP recovery, and try:
fastboot boot recovery.img
replace recovery.img with the name of the recovery image file for TWRP.
Once that is done, look at your mounts and see if you can access any partitions.
Update #3
acejavelin said:
Can you still get to Fastboot? If so, unlock again, and then download the latest TWRP recovery, and try:
fastboot boot recovery.img
replace recovery.img with the name of the recovery image file for TWRP.
Once that is done, look at your mounts and see if you can access any partitions.
Click to expand...
Click to collapse
Alright so right now I am EXTREMELY happy!!! Thank you so much for the advice. My phone happened to not get into fastboot anymore for some reason after I thought I bricked it. The final attempt I made before going to bed that night was to put my Micro SD into my phone and attempt to get into fastboot one last time and by some miracle my phone decided to. This is the steps I took to get my phone back operational so please excuse the length. At the moment, its not completely solved until I get my phone 100% operational, but this is what I have so far. I listed a few notes before I started so here goes.
Update #3:
HTC Rezound 2014:
- S-OFF and rooted with Liquid Smooth ROM and Amon Ra recovery
- fastboot oem LOCKED (no bootloader access available)
- batteries all low powered, 1 fried (3 total)
- when plugged, charging light turns on for 3-5 seconds and turns off without charging battery or
allowing phone to power back on; requires battery pull to restart process
- Power + volume normally takes to bootloader; recovery, factory reset, and reboot option fail
- when attempting to boot, phone will vibrate, power on to green HTC logo on white screen and then
turns off to black
- any attempts to turn on phone result in said description and requires battery pull after each attempt
Current issues:
Batteries are not fully charged
Cannot access bootloader because of last command in console, "fastboot oem lock"
PC cannot read devices despite drivers installed and fully working USB cord
Possible causes:
- Extra batteries just aren't fully charged to allow phone to fully boot
- System files are corrupted; no recovery, no boot.img, no OS; nothing for the phone to read to start up
Attempt 1:
- Plug phone with battery inside and cover off
- Clear memory off SD card
- Remove battery and insert SD Card
- Note: Battery has little to no power
- Plug into USB cord connected to computer
- Before orange light comes on, hold down Power + Down Volume
- Failed; repeat (unplug from phone, battery pull and reinsert)
- Attempt to leave battery to charge for 8 minutes via USB
- Charge attempt failed; orange light turns on for 3 seconds before turning off
Attempt 2:
- Remove phone cover, take out battery and reinsert
- Hold Power + Down Volume and go into Fastboot USB
- If successful, plug into PC via USB cable
- Open console (Shift + Right Click in folder AndroidSDK\platform-tools)
- For list of fastboot commands, type in the console (which should read slike C:\AndroidSDK\platform-tools\) "fastboot help" without quotations
- To make sure you are connected, type the command "fastboot reboot-bootloader"
- If the phone reboots into FASTBOOT USB after the command, then you're good
- Type in the command "fastboot devices" to make sure your devices can be read by your computer (should show up like HT18BY892363 fastboot)
- Since the last thing I did on my phone was "fastboot oem lock", use the command "fastboot oem unlock" and hope for success
- Command prompt will read something like:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.014s ]
finished. total time: 0.017s
- Type into command "fastboot oem get_identifier_token"
- Submit Identifier Token to HTC Dev (need to create an account)
- Download file and save in platform-tools folder with the adb.exe and fastboot.exe files
- Type "fastboot flash unlocktoken Unlock_code.bin" into console
- Select "Yes" option and phone will reboot as follows: vibrates, shows HTC logo on white screen for 3 seconds and turns off
- Unplug phone from USB, take out battery and reinsert
- Hold Power + Down Volume and boot into FASTBOOT USB; should read "*** UNLOCKED ***" at top of screen
- Using TWRP 2.8.0.1F, extract "recovery.img" into "platform-tools" folder
- Type command "fastboot boot recovery.img" and profit!
Glad you got it working!
acejavelin said:
Glad you got it working!
Click to expand...
Click to collapse
I actually have another issue now. I have managed to install TWRP onto my phone but when I attempt to flash a RUU I downloaded, I get this error:
Installing '/external_sd/PH98IMG.zip' . . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/'external_sd/PH98IMG.zip'
Error flashing zip '/external_sd/PH98IMG.zip'
Updating partition details . . .
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/devlog
E: Unable to mount storage.
Your partition table is corrupted... Being S-Off you have an option, you need to run an EXE RUU, not flash a ph98img... I think the last one was 3.12.605.12 and you run it from a Windows PC with the phone in download mode... If that doesn't work only a JTAG programming can fix it, if it can be fixed. Once you get to this point that all partitions are not mountable, it is tough to recover, if it can be done at all. You have about a 50/50 chance at best.
acejavelin said:
Your partition table is corrupted... Being S-Off you have an option, you need to run an EXE RUU, not flash a ph98img... I think the last one was 3.12.605.12 and you run it from a Windows PC with the phone in download mode... If that doesn't work only a JTAG programming can fix it, if it can be fixed. Once you get to this point that all partitions are not mountable, it is tough to recover, if it can be done at all. You have about a 50/50 chance at best.
Click to expand...
Click to collapse
So how would I go about finding an EXE RUU? Do I just google "HTC Rezound 3.12.605.12 RUU exe"? And I apologize for the noobish questions, this is actually my first time getting this bad with my Rezound haha. I found this article (although it isn't associated with the phone) and was wondering if I should give it a try or not. http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
shock_and_awe said:
...
E: Unable to mount '/system' <<<<<< THIS is the real problem
E: Unable to mount '/devlog
Click to expand...
Click to collapse
Without /system being mountable, or even formatable, there isn't much you can do..
Since ALL partitions are unmountable it likely means the PIT (Partition Information Table) for the internal 16GB storage area is corrupted and it needs to be recreated.
This MAY be fixable manually if you have a Linux machine, and understand the partitioning of THIS device... The Linux part I have no issue with, but I no longer own the is device and do not have a copy of the partition table to help you repartition it.
Honestly, for all the work involved, why not just grab a cheap phone online and use it? I mean you can get a Galaxy Nexus, a replacement Rezound, or a handful of other LTE devices for under $100 on swappa.com
acejavelin said:
Without /system being mountable, or even formatable, there isn't much you can do..
Since ALL partitions are unmountable it likely means the PIT (Partition Information Table) for the internal 16GB storage area is corrupted and it needs to be recreated.
This MAY be fixable manually if you have a Linux machine, and understand the partitioning of THIS device... The Linux part I have no issue with, but I no longer own the is device and do not have a copy of the partition table to help you repartition it.
Honestly, for all the work involved, why not just grab a cheap phone online and use it? I mean you can get a Galaxy Nexus, a replacement Rezound, or a handful of other LTE devices for under $100 on swappa.com
Click to expand...
Click to collapse
I see what you mean. Honestly I would get another phone if I could but I'm no longer living in the States, I'm studying in Spain. Shipping is super expensive so I'll have to go local or figure something out. Its the only phone I have at the moment but I'll most likely just get another phone for cheap. I really appreciate the help and the advice though. If anything, this will be my "side project" to work on when I'm SUPER bored and fix it for sh**s and giggles.
shock_and_awe said:
I see what you mean. Honestly I would get another phone if I could but I'm no longer living in the States, I'm studying in Spain. Shipping is super expensive so I'll have to go local or figure something out. Its the only phone I have at the moment but I'll most likely just get another phone for cheap. I really appreciate the help and the advice though. If anything, this will be my "side project" to work on when I'm SUPER bored and fix it for sh**s and giggles.
Click to expand...
Click to collapse
Spain has mostly GSM service, correct? Why not look into cheap devices locally? Amazon.es has several devices under 200 euros, Moto G, Moto E (89 euro), LG G2 mini, Xiaomi Red Rice, BQ Aquaris E5, etc... Or local classifieds online.
Update #4
SOLVED!!!
The solution (as it appears to be on a few success stories) is to completely install an Official Stock RUU. You just have to be content with losing ALL your data (if there was anything to save in the first places). What I ended up doing was using a microSD adapter this whole time and I would not have been able to get my phone back without it. This is what I did (following the installation of TWRP Recovery):
Official Stock RUU:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Update #4 (Final):
For this process I used a microSD adapter, in which I plugged into my laptop and put the required files in there.
- Download file from Android Police and rename to "PH98IMG.zip"
- Using your storage device (whatever way you choose just do this) put the .zip file onto the SD card
- Place the SD card into your phone and boot into HBOOT using Power + Down Volume
- Wait a few minutes until the PH98IMG.zip is finished loading and press Volume Up for "Yes" when asked "Do you want to start update?"
- After about 10-15 minutes, the phone will ask you to reboot the system
- Profit!!!
- Don't forget to remove the PH98IMG.zip file from your SD card or else every time you boot into HBOOT, it will reload the file
acejavelin said:
Spain has mostly GSM service, correct? Why not look into cheap devices locally? Amazon.es has several devices under 200 euros, Moto G, Moto E (89 euro), LG G2 mini, Xiaomi Red Rice, BQ Aquaris E5, etc... Or local classifieds online.
Click to expand...
Click to collapse
I actually JUST fixed my phone haha but yeah there are a few local mobile phone stores here (like Phone House) where they sell discounted phones. I appreciate all the help and thank you so much for everything. Above all else, thank you for sticking through with this post
Glad its working!
Well, I was installing the M Preview when it froze and my Nexus 9 rebooted and had a screen saying the data was corrupted and I need to reset. I reset it but it never turned back on. I let it stay in the boot loop for about 15 minutes and nothing changed. loader the bootloader and now it says OS-n/a at the top. I cant connect via ADB anymore and cant flash the stock ROM. Google and HTC both said they cant help. I hope one of you can help me! ordo i just have a expensive paper weight now? (hope not!)
also, my bootloader is still unlocked but I just cant connect with ADB to flash the stock ROM.
How I solved this issue
ConceptCars_ said:
also, my bootloader is still unlocked but I just cant connect with ADB to flash the stock ROM.
Click to expand...
Click to collapse
Hi there,
I was running into the same issue today. I'm new to android so I thought I could just simply load the image-volantis-MPZ44Q.zip into a command prompt and that all would be well. Unfortunately, my N9 bricked and ended up in an endless reboot loop. I saw "google" then a few bouncing balls for a second or two and then the entire process would restart again. (note: I was trying to upgrade from 5.1.1 to M)
Here's how I fixed it
NOTE: I am typing this out from memory. Some steps may be missing. If so, I trust that the rest of the community who is more knowledgeable on this and other related topics will be able to assist.
After hours of research and numerous failed attempts, I was able to bring it back to 5.1.1 using the following method:
1. Google WUBFRESH Nexus Root Toolkit and download and Install it. (I can't post any links because I just signed up to post this message).
2. Choose your model type etc and the android build and hit apply. For me, I choose Nexus 9 (HTC Wi-Fi Tablet) and VOLANTIS-FLOUNDER: Android 5.1.1 - Build: LMY47X.
3. The toolkit should load up now. On the right side under Restore/Upgrade/Downgrade choose "soft-bricked/bootloop" and click "Flash Stock + Unroot". Note, you need to be unlocked for this step. I was already unlocked prior to my attempt at upgrading to M.
4. Plug in your N9 via USB to your computer. If it's still boot looping, wait until you see the google text, then hold the power button and the volume down button until you get either the HBOOT menu or you get an icon that shows the little android guy lying down with his door open (aka recovery mode). If you see a white screen with HBOOT, make sure at the top it says "UNLOCKED". If it says LOCKED, these steps may not work for you!
5. Use the volume buttons to select Fastboot and then press the power button to enter in it.
6. Back to your computer.
7. Press OK to get through all warning screen (read them first obviously).
8. The program will ask you for an image. At the top, choose VOLANTIS-FLOUNDER: Android 5.1.1 - Build: LMY47X from the drop down menu. Under Choice, choose Automatic download + extract. Under Settings, choose "Force Flash Mode". Press OK.
9. It will begin downloading the factory image from the google developer servers.
OPTIONAL:If the program isn't able to communicate with your device, it may be a driver issue. I used the instructions on the following site: (remove spaces when pasting into your webbrowser) theandroidsoul.com/ nexus-9-driver-adb-fastboot-mtp-installation-guide-68375/ . I had to supplement the instructions by first unplugging my device, then loading it into HBOOT, then choosing Recovery, then choosing apply update from ABD, then plugging in my device. The computer recognized it and it showed up in my device manager with a yellow exclamation mark. I right clicked, went to it's properties and then updated the driver. Then I choose Browse My Files, and choose "let me pick from a list", then I pressed have disk, navigated to where I had downloaded and extracted the usb drivers and selected android_winusb.inf. I selected the first one and continued through all the warnings by pressing next/ok. It was finally complete and the yellow exclamation mark was gone.
10. Once complete, the program may ask you again if you have backed up your files as this is a point of no return. Read the notice and press OK when you are ready to continue.
11. At this point, a command prompt will open up and it will transfer the 5.1.1 files. This took approximately 5 minutes on my end. At the end, there were some instructions that the N9 may be rebooting and that it would take 5-10 minutes. This never occurred for me. Instead, the device went back to the fastboot screen. I then selected REBOOT (the second option in yellow).
12. Finally! The device turned on. The colored balls were flying and after 5 minutes or so, the ANDROID logo came up and I was able to setup lollipop.
Hope this helps...
logikol said:
Hi there,
I was running into the same issue today. I'm new to android so I thought I could just simply load the image-volantis-MPZ44Q.zip into a command prompt and that all would be well. Unfortunately, my N9 bricked and ended up in an endless reboot loop. I saw "google" then a few bouncing balls for a second or two and then the entire process would restart again. (note: I was trying to upgrade from 5.1.1 to M)
Here's how I fixed it
NOTE: I am typing this out from memory. Some steps may be missing. If so, I trust that the rest of the community who is more knowledgeable on this and other related topics will be able to assist.
After hours of research and numerous failed attempts, I was able to bring it back to 5.1.1 using the following method:
1. Google WUBFRESH Nexus Root Toolkit and download and Install it. (I can't post any links because I just signed up to post this message).
2. Choose your model type etc and the android build and hit apply. For me, I choose Nexus 9 (HTC Wi-Fi Tablet) and VOLANTIS-FLOUNDER: Android 5.1.1 - Build: LMY47X.
3. The toolkit should load up now. On the right side under Restore/Upgrade/Downgrade choose "soft-bricked/bootloop" and click "Flash Stock + Unroot". Note, you need to be unlocked for this step. I was already unlocked prior to my attempt at upgrading to M.
4. Plug in your N9 via USB to your computer. If it's still boot looping, wait until you see the google text, then hold the power button and the volume down button until you get either the HBOOT menu or you get an icon that shows the little android guy lying down with his door open (aka recovery mode). If you see a white screen with HBOOT, make sure at the top it says "UNLOCKED". If it says LOCKED, these steps may not work for you!
5. Use the volume buttons to select Fastboot and then press the power button to enter in it.
6. Back to your computer.
7. Press OK to get through all warning screen (read them first obviously).
8. The program will ask you for an image. At the top, choose VOLANTIS-FLOUNDER: Android 5.1.1 - Build: LMY47X from the drop down menu. Under Choice, choose Automatic download + extract. Under Settings, choose "Force Flash Mode". Press OK.
9. It will begin downloading the factory image from the google developer servers.
OPTIONAL:If the program isn't able to communicate with your device, it may be a driver issue. I used the instructions on the following site: (remove spaces when pasting into your webbrowser) theandroidsoul.com/ nexus-9-driver-adb-fastboot-mtp-installation-guide-68375/ . I had to supplement the instructions by first unplugging my device, then loading it into HBOOT, then choosing Recovery, then choosing apply update from ABD, then plugging in my device. The computer recognized it and it showed up in my device manager with a yellow exclamation mark. I right clicked, went to it's properties and then updated the driver. Then I choose Browse My Files, and choose "let me pick from a list", then I pressed have disk, navigated to where I had downloaded and extracted the usb drivers and selected android_winusb.inf. I selected the first one and continued through all the warnings by pressing next/ok. It was finally complete and the yellow exclamation mark was gone.
10. Once complete, the program may ask you again if you have backed up your files as this is a point of no return. Read the notice and press OK when you are ready to continue.
11. At this point, a command prompt will open up and it will transfer the 5.1.1 files. This took approximately 5 minutes on my end. At the end, there were some instructions that the N9 may be rebooting and that it would take 5-10 minutes. This never occurred for me. Instead, the device went back to the fastboot screen. I then selected REBOOT (the second option in yellow).
12. Finally! The device turned on. The colored balls were flying and after 5 minutes or so, the ANDROID logo came up and I was able to setup lollipop.
Hope this helps...
Click to expand...
Click to collapse
Hi, ive tried this a few times now but it keeps saying:
sending 'cache' (6248 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
sending 'recovery' (8434 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.007s
sending 'vendor' (161111 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 5.451s
rebooting into bootloader...
OKAY [ 0.024s]
finished. total time: 0.025s
and then nothing happens. I really dont knot what to do now!
Ok so.... HOLY ****!
after trying about 25 times to do a factory reset, and it just going back into the bootloop. I tried again just after posting my last reply and it F***king worked! thanks for the help, hopefully other will find it useful!
Glad it worked out
Same Issue
so I'm running into the same issue and running the Root Toolkit. I've ran it about 6 times and I'm still hanging on Google. Did you continue running the same thing until it worked again randomly? Did you try change the Android version at any point from 5.1.1 to something earlier?
---------- Post added at 10:18 PM ---------- Previous post was at 09:26 PM ----------
Well scratch that, right after posting this, the next time it worked. Seems like the trick is to post here that it doesn't work and then it will work.
Lol
Sent from my HTC6500LVW using XDA Free mobile app
[email protected] said:
so I'm running into the same issue and running the Root Toolkit. I've ran it about 6 times and I'm still hanging on Google. Did you continue running the same thing until it worked again randomly? Did you try change the Android version at any point from 5.1.1 to something earlier?
---------- Post added at 10:18 PM ---------- Previous post was at 09:26 PM ----------
Well scratch that, right after posting this, the next time it worked. Seems like the trick is to post here that it doesn't work and then it will work.
Click to expand...
Click to collapse
Haha - glad it also worked for you.
Conceptcars, can you please rename the thread to "SOLVED" - might be easier to find for anyone else in the future who is also experiencing similar hangs
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.
In such cases, you cannot reach adb from the command line, so there seems to be no way to recover the watch. Fortunately, it has been discovered how fastboot can be entered without a running system.
2. Procedure
Step 1: Get into fastboot
This is the most difficult part. @kiralex1995 has developed a procedure that will lead reproducible to boot the watch into fastboot mode, but it may take many tries (one user reported that it took him 30 min of tries).
Follow this guide: https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
When you are in fastboot and see the fastboot logo, you have mastered the most difficult part.
Step 2: Choose a ROM to flash on the watch
There are currently three possible ROMs to choose from:
a.) The English AmazFit firmware 1.3.0n
Download the following file on your PC: https://mega.nz/#!xIkC1IQZ!bLLSN9BMvbp7zhZHg2oQq6p4ud-EFyUYkatCGKgHeS8
b) The Chinese AmazFit firmware 1.2.5a
Download the following file on your PC: https://mega.nz/#!tNdggR4b!VXmExGqdNixrj8pVLqTkAi_munmjF5RidRJP9L-LAXE
c) An old Chinese AmazFit firmware 0.9.50:
Download the following file on your PC: https://mega.nz/#!wY9mEQoI!0ARB0MaK0byjttgrPmJJQX4ZFdIXgHOUquxqFhghg7U
Step 3: Download flash script from xda
Download the attached flash script from this post to your PC.
Step 4: Unpack the archive on your PC
Depending on you PC choose the right method to extract the files in the ROM archive and the flash script.
Step 4: Boot the watch into special recovery
Check that your fastboot drivers see that watch (which should still show the fastboot logo):
'fastboot devices'
You should see your device listed. Otherwise check your fastboot driver installation on your PC. (Note: On Linux you sometimes need to use "sudo fastboot ...".)
Then boot the modded recovery that is included in the archive you unpacked in step 2.
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
Step 5: Transfer the ROM files and the flash script onto the watch
First check that you are now able to connect to your watch via adb:
'adb devices'
You should see your watch listed. Otherwise check you "adb driver" installation. For Windows take care that you use Khoushs universal adb drivers.
Then push the files to the watch:
'adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/'
Step 6: Enter the shell on the watch and check your files
After you have successfully transferred the files to the watch, you then enter the shell on the watch:
'adb shell'
You should see only a "#", meaning you have full root access.
Now switch drirectory to the sdcard
'cd /data/media/0/
ls'
You should see your files on the "sdcard", including the ones that were pushed before
7. Start flashing the files
Run the flash sccript with the following command on the watch:
'sh flash_rom.sh'
If everything worked correctly, you should see something like:
Code:
Validating images
boot.img.gz: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE! Press Enter to continue or CTRL-C to stop!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 2.075793 seconds, 4.3MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 107.981352 seconds, 7.6MB/s
Finished
If you see any error message during or after flashing, then DO NOT REBOOT the watch, but get some help or analyse yourself, what went wrong. You can still reflash.
8. OPTIONAL: Delete the dalvik-cache
You can erase the dalvik-cache on the watch with the following command:
'rm -rf /data/dalvik-cache'
This will make the system "re-optimize" all apps when it boots (successfully) the next time. This is optional, as you could always do that later again.
9. Reboot the watch
If everything is ok, then you can reboot the watch
'reboot'
Your watch should boot normally into the flashed system, you downloaded. CONGRATULATIONS, you unbricked your watch!
Thank you for this post.
Neuer_User said:
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.....[/B]
Click to expand...
Click to collapse
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
First watch has just successfully been unbricked (1immortals watch) [emoji106] [emoji2]
kiralex1995 said:
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
Click to expand...
Click to collapse
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Neuer_User said:
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
Click to expand...
Click to collapse
Well i guess constant WiFi would dramatically reduce the running time? On the other hand it might just be turned on for short periods, don't know how Google does that.
1immortal said:
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Click to expand...
Click to collapse
Congratulations and thanks to Neuer_User.
hi, after this step the watch reboot and restart the loop on logo. why?
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
edit: after more test, i'm not able to go to recovery mode. For an errore, when i try another time to go to Fastboot mode, i push 2 times the button and i ERASE ALL the watch, now i have a device called JZ4785 USB Boot Device.
There's some way to save this watch?
Thanks.
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
1immortal said:
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
Click to expand...
Click to collapse
This could indeed be the case. Noone of us ever entered that mode so far. It would be very good to understand, how you really got into that. It must have happened in the first step, where you were supposed to enter fastboot. Did you see the screen on the watch with the two options? There is a video in the link of @kiralex1995 post. Maybe you can comment, what exactly looked identical for you and where it exactly started to differ.
In case, you are really in that SOC flash mode, the Ingenic USBburner tool would indeed, probably, be the right tool to reflash the watch. As I mentioned, nobody here used that before. I have some experience with similar tools for the MTK platform. I believe that it should be possible to generate the necessary dump from a working watch, but this is all theory so far.
Where are you located?
well, nothing helped, there's no configs for the JZ4785, and there's no relevant information of partitions offset for flashing. we tried to flash both 1.2.5 and some generic ingenic image, with a lack of success as well
contacted ingenic for some clarification and some help, lets see where this lead to ...
Hello and thanks for tour support.
Also "launcher has stopped" i have to consider as a brick situation?
Palese led me know because i tried to update from chinese firmware but Now it doesn't work, i am able to start in fastboot mode
Thank you vero much fo and your advice
regarding the launcher errors, please try to unpair your watch and re-pair it again, it's a non-brick situation.
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
alon1211 said:
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
Click to expand...
Click to collapse
Try a different USB cable. Bad cables are known to produce that error.
This is pretty awesome! I used this to convert my Chinese Amazfit watch to English ROM, and it seems to work OK.
However, there's a piece missing from the bundle -- the recovery image. There's an OTA available, and I pulled the update.zip file using the Fastboot trick so the OS didn't load and delete it - then booted the "mod recovery". Here's that update.zip (to 1.3.2b): https://mega.nz/#!nIBDhLrR!7nQlWsn-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA
The OTA didn't succeed -- when it went to reboot to recovery and apply the update, it booted with Chinese text in recovery boot and failed with just one word - "Error". I'd imagine that's because recovery.img wasn't part of the bundle, so my watch still has the Chinese ROM recovery on it. Looking at the update.zip, it's fairly clear it's built in English - with English error messages in "updater-script".
I'm hunting around for the English ROM's recovery image, and will probably find it in the next few minutes, but figure I should mention this hole - and that this routine is also useful for converting to English. It'd been demonstrated before that you can run the English ROM just by flashing it (and boot.img), but no unified thread seems to exist for it yet (that I can find via Googling at least). :good:
edit: Literally 5 minutes later, bam. https://forum.xda-developers.com/showpost.php?p=71264431&postcount=599 - I downloaded that Fix_recovery bundle, pushed it to /data/media/0/ from the mod recovery, ran it, and it gave some errors but fell back to the "dd" method. So, all that's needed to get a complete English ROM flash is to add recovery.img and the line:
Code:
busybox dd if=recovery.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/recovery bs=4096
Hi All,
I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.
I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?
Thanks
Dimitar
dpenevdpenev said:
Hi All,
I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.
I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?
Thanks
Dimitar
Click to expand...
Click to collapse
You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
Neuer_User said:
You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
Click to expand...
Click to collapse
Thanks Neuer_User,
what I did:
1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above
Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"
This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.
Thank you once again.
dpenevdpenev said:
Thanks Neuer_User,
what I did:
1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above
Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"
This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.
Thank you once again.
Click to expand...
Click to collapse
Hmm, if that doesn't work, try "fastboot erase cache" and "fastboot erase data". That will really completely delete all user and cache data. The next restart should take a long time.
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
for g5 the command are these:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
Click to expand...
Click to collapse
I tried those, and that's how I got here.
Try reflashing twrp.img in fast boot (see Autoprime's AIO post for instructions) then try booting into twrp - then at least you can wipe and flash a new stock/custom rom!
Best of luck!
megatron_lives said:
Try reflashing twrp.img in fast boot (see Autoprime's AIO post for instructions) then try booting into twrp - then at least you can wipe and flash a new stock/custom rom!
Best of luck!
Click to expand...
Click to collapse
Thanks for the reply!
Reflashing TWRP doesn't work as the device is somehow locked again:
Code:
fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.471s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.490s
Unlocking fails as mentioned in my fist post.
did you try flashing stock kdz file with lgup? if it boots you can later try unlocking.
ozkaya said:
did you try flashing stock kdz file with lgup? if it boots you can later try unlocking.
Click to expand...
Click to collapse
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
gqo said:
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
Click to expand...
Click to collapse
good point. how about if you try fastboot flash recovery twrp.img or if it fails flash stockrecovery.img?
---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------
gqo said:
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
Click to expand...
Click to collapse
if flashing recoveries fail, try fastboot flash bootloader stockbootloader.img (you can find these images from stock zip format in the forum)
Thanks everyone for the help! Just to be thorough, I tried entering download mode for what felt like the 42nd time, and whaddaya know, it worked! So I'm currently in the process of returning to the point I was on before I tried that ill-fated update of LineageOS. Thanks again everyone!
gqo said:
Thanks everyone for the help! Just to be thorough, I tried entering download mode for what felt like the 42nd time, and whaddaya know, it worked! So I'm currently in the process of returning to the point I was on before I tried that ill-fated update of LineageOS. Thanks again everyone!
Click to expand...
Click to collapse
what exactly have you done? i have the same problem
trinity_user said:
what exactly have you done? i have the same problem
Click to expand...
Click to collapse
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
did u lost ur imei?
Zer0_rulz said:
did u lost ur imei?
Click to expand...
Click to collapse
Not sure what you mean. If you're wondering whether I lost that piece of information: no, it's printed on a sticker on the back of my phone. In general there's usually a sticker with your phone's IMEI somewhere on the packaging or, like in my case, on the device itself.
gqo said:
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
I tried those, and that's how I got here.
Click to expand...
Click to collapse
Wow... It's uncanny how close this is to the my own situation, except that in my case it's a G6 (US997).
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
Again I did the same, bar the tea, but unfortunately my tale does not end quite so happily... Not yet at least. I can "upgrade" with literally no problems using LGUP and one of the few G6 KDZs available, but when it's time reboot my phone always boots into the fastboot for bootloader unlock mode. I can use fastboot commands but my bootloader relocked at some point and I'm still not able to unlock it again. No matter what I do my phone always boots to fastboot... Except when I do the recovery key combination and press "Yes" twice, in this case there's a brief "erasing" animation and then I'm back to fastboot.
I realize I'm using a different device, but would anyone happen to have any thoughts on this? This is my first time using a non-Nexus LG and I must admit I'm struggling a bit to get out of this mess. The recovery and fastboot modes also look quite bare to me, but I might just be using the wrong.
Cheers!
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
Thank you for your detailed guide, but it didnt work for me yet. I tried maybe 100 times. Everytime the same Message "Your device is corrupted".
You are a life saver
Thank you for detailed tutorial.
My H850, which I managed to almost dead brick, like yours (of course from the same source - reddit ) after few minutes with uppercut + lgup ressurected with all the files and apps inside
So, after that I'm running through factory reset now and trying to unlock once again.
Thank you
Have the same problem but......
gqo said:
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
I tried those, and that's how I got here.
Click to expand...
Click to collapse
i have the same problem but i can still use the phone, how can i delete this error?
the boot loader it s not working.......PLEASE HEEEELP
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
I tried this, but my pc (and so LGUP) doesn't recognize my lg g5 (drivers are installed)... I don't know what to do.. please help me!!!
Use uppercut
Hello. I have the same problem. I was on LOS 15.1, then i deviced to go back on stock. I relocked the bootloader and i have this messege. When i go to download mode, lgup recognize the phone, but after 10 seconds the phone reboot and go to that screen again. Any suggestions?
volen said:
You are a life saver
Thank you for detailed tutorial.
My H850, which I managed to almost dead brick, like yours (of course from the same source - reddit ) after few minutes with uppercut + lgup ressurected with all the files and apps inside
So, after that I'm running through factory reset now and trying to unlock once again.
Thank you
Click to expand...
Click to collapse
I've got this problem also, thanks to those lines put into 'terminal'.
I can get into download mode easily, however by the time I then open Uppercut and try doing anything the phone reboots itself back into the 'corrupt' screen and keeps looping on that.
mgolder said:
I've got this problem also, thanks to those lines put into 'terminal'.
I can get into download mode easily, however by the time I then open Uppercut and try doing anything the phone reboots itself back into the 'corrupt' screen and keeps looping on that.
Click to expand...
Click to collapse
Maybe unlock.bin is corrupted, try ask LG to resend the file.
Hello guys,
I've recently got my hands on a not-working P20 Lite, which was stuck on boot with the well-known "your device has failed verification and may not work properly" error message. Since I got stuck on a HUAWEI logo when trying to enter the recovery, ended up in a bootloop trying to enter the download mode, the only way to get the phone working was fastboot. And since I am writing this post, yeah, y'all guessing correctly, it has not been successful. (Error message 'Command not allowed')
After giving up on it and leaving it stuck on the HUAWEI logo for a while, I have noticed that it has turned off. After turning on the device, it shows a green screen with 2, red and blue squares (see attached image), still not being able to boot in recovery mode, however fastboot still somehow manages to fire up.
Any suggestions? Is this phone dead (which I honestly believe), or is there something that would possibly be able to change its state?
Thanks!
EnterPaulini said:
your device has failed verification and may not work properly"
Click to expand...
Click to collapse
EnterPaulini said:
it shows a green screen with 2, red and blue squares
Click to expand...
Click to collapse
Wrong region (oeminfo).
EnterPaulini said:
Is this phone dead?
Click to expand...
Click to collapse
No, not dead yet
Need more information about your phone . Install on your PC "Minimal ADB and fastboot" tool .
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem battery_present_check
and post the results please.
(First try to charge the phone).
(bootloader) :ANE-LX1 9.1.0.372(C432E7R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
(bootloader) 3426mv
Thanks!
Okay, try this way out...
1. in fastboot mode run command
fastboot erase userdata
and try restart the device.
2. download and use a Service ROM
https://androidhost.ru/2AVi
with an sd/card or an USB-OTG flashdrive in dload mode. Unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .(Power+Vol.Up+VolDown).
-Alf- said:
Okay, try this way out...
Click to expand...
Click to collapse
Still hanging in there! Entering the dload mode does not work, I always land on the same green screen and it shuts down.
EDIT:
Back to the "Your device has failed verification and may not work properly" screen. It actually shows the HUAWEI logo again and shows that the device is charging, when turned off. Trying to enter the dload mode results in a bootloop.
EDIT2:
After few times of trying to enter the dload mode I am stuck with the green screen again. From what I have observed, the green screen does not come up when I am connected with the USB cable. When not, everything except fastboot leads to the green screen with a small LED diode blinking red (not so familiar with this phone, no idea what's this for, it's located on the notch). On the other hand, everything except fastboot with cable connected leads to a bootloop. But at least I can see the HUAWEI logo, eh?
Paid service
But if it's a hardware problem (e.g. dead memory), it won't help you.
-Alf- said:
Paid service
But if it's a hardware problem (e.g. dead memory), it won't help you.
Click to expand...
Click to collapse
And if I tried this solution @kikson112 suggested? Doing something with that test point, could this end up working?
I can't help you, that's Greek to me... I have never used this method, nor dc-phoenix (thank goodness).
This happened to my ANE-LX1 a while ago, bootloader never unlocked and device was fully stock...
Device was still under warranty and huawei repaired it for free
Probably a hardware issue
Hey! I have the same problem now. From todays morning it has been stuck on the loading Huawei logo. I haven't got any messages about that warning, you have got, but I have tried to enter the recovery mode and sometimes, it just flashes that green screen with the two squares. Now I think is without power. Have you somehow started the phone?
AmaliaRepova said:
Hey! I have the same problem now. From todays morning it has been stuck on the loading Huawei logo. I haven't got any messages about that warning, you have got, but I have tried to enter the recovery mode and sometimes, it just flashes that green screen with the two squares. Now I think is without power. Have you somehow started the phone?
Click to expand...
Click to collapse
Hello,
some related links:
https://forum.xda-developers.com/t/...-blue-red-flag-fastboot.4339931/post-85697163