Soft Bricked Huawei Watch - Huawei Watch

Hi everyone
Saw some threads related to Huawei watches getting bricked. But mine is kinda ok. Here is my case:
My Huawei watch was running Android 2.0
I wanted to try out the Negalite Rom. I have some experience in flashing android phones so I went ahead and did as follows:
Booted into fastboot (using adb)
Unlocked oem
Flashed boot image
Flashed twrp
Then flashed system image
I rebooted to system but it took me back to twrp
I tried sideloading adb in twrp and flash the Negalite rom but it gives me the Error 7
Any hope left for me :crying:

Related

Help Un-Rooting Bell Canada HTC One M9

I have an HTC One M9 that's rooted with the CM 13 based on 6.0.1, and I have TWRP Recovery installed. I wanted to unroot my phone and install the stock ROM to my phone because I have some physical problems with the phone and some software problems that aren't related to the root or CM 13. I followed a guide that said to get ADB and Fastboot on my computer so I did that (AT this point I had already gone to TWRP and wiped the device including the OS) and then it said to get the stock ROM. I tried to look for the stock ROM and I found a few so I tried one. It said to flash it by using commands on ADB to flash it. I did all of the commands it asked and when it came to typing "fastboot flash recovery (file name here)" it said waiting for device and didn't ever change. I tried putting the zip file onto my device and then lashing it using install on TWRP and it failed then automatically restarted the phone with no OS so it was bricked. I waited for the battery to die and then booted the phone into recovery mode. This is currently where I'm at. I live in Canada and use Bell so I can't find the stock ROM on the Official HTC website, or anywhere else for that matter. I would like to use my phone so any help would be appreciated. Thanks!

Bootloader unlock bootloop on 2.0

Hey guys,
So I was able to return my HW to a normal state on AW 2.0. It turns out as soon as I unlock the bootloader, it goes into a bootanimation bootloop (a few times, it displayed an error then finally booted AW). And I can't get into the stock recovery. It seems like this one is screwed up somehow. Flashing TWRP works though.
I really don't understand this. I thought this was supposed to be like a Nexus/Pixel device. Has anyone else experienced this behavior? I would really like to unlock it and flash Negalite ROM.
Thanks!
Edit: OK so the watch only works if I flash the custom ROM from AW 1.5 using TWRP. It goes all the way and doesn't bootloop. SO WEIRD.
---------------
Original post:
Hi everyone,
I got my HW today and it's already messed up! I've been flashing ROMs and such for a long time now but I'm stomped. Initially, I wanted to install Negalite ROM.
Here's what happened:
- I used my watch for a bit on 1.5, connected it to my phone, did the initial setup and OTA updated to 2.0.
- I decided to unlock the bootloader. Worked but watch got stuck on a recovery bootloop (with the open bugdroid). Managed to get rid of it by factory resetting through TWRP (which I fastbooted).
- Watch was restarting (on 2.0) but got stuck on another bootloop (on Nougat bootanimation). Sat there for about 20 min.
- I decided to downgrade to 1.5. Used fastboot to flash boot.img, recovery.img and system.img. The system.img gave me an error at first while flashing but proceeded all the way (9 steps out of 9) with success (?)
- Now the watch is still stuck on bootanimation (I think it's the MM one, with the flying around dots) and won't go any farther.
Note: I can get into fastboot and TWRP 3.0.3 is installed. But multiple factory resets from TWRP don't change anything. I can't adb push anything to the watch from TWRP either (I tried the ADB sideload option). ADB drivers should be OK on my Windows 7 x64 machine (I used Google drivers from the SDK).
Any HELP please? I really don't know what to do now since I can't push any file to the watch... and I've read many threads on here to no avail.
Thanks in advance.
edit: IT BOOTED! I used a different system.img (the one from sturgeon-m6e69f-factory-e659286a.tgz) and flashed it with fastboot and IT WORKED! Thanks to whoever posted this version! Now I will try again to install Negalite.

LG G4 H815 No TWRP Access

Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error
Code:
FAILED (remote: unkown command)
since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Bennou said:
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Click to expand...
Click to collapse
It's clearly written on the official website and in the official TWRP support thread for the g4 what you have to do when on Nougat bootloader and want to flash TWRP... and keeping it.
Sent from my LG-H815 using XDA Labs
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Bennou said:
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Click to expand...
Click to collapse
Okay if it doesn't work for you you must do something wrong. It works 100%. If you really want help you should explain in detail exactly which steps you took as otherwise it's all just guessing what you're doing.
Sent from my LG-H815 using XDA Labs
Indeed, I didn't followed the procedure exactly, didn't do the step after flashing TWRP (removing battery and boot manually to recovery). Well thank you, was my bad on that.
Should I do a clean new install of cypheros or should I keep it like that, what would be your advice ? Knowing that at the moment CypherOS works like a charm. I also plan to install Magisk on it to root it.
To help others newbie like me, solution can be found here : https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424

bricked my phone with locked bootloader, sideload successful but bootloop persist

Dear all,
I bricked my phone when i upgrade my pixel 2 xl to android 10 while never enabling the allow oem unlock form the developer mode.
I notice many similar thread but my case is a bit different since i can still acceaa fastboot and recovery, i tried to sideload the recovery ota as per official guide in google website, the process indicate that sideload is successful but my phone still stuck in bootloop.
Since i live in Indonesia, there is no available rma for me. Please help me, is anyone have any idea how to fix this, i've tried almost every tool i find in this forum such deuce script, all in one tool, etc. But still getting bootloop.
I'd like to get something straight...
When you upgraded to 10, did you do it through the stock Android System Updater or did you download an OTA/Full Factory image and flashed it yourself?
Also, you can boot to a twrp recovery and flash as I posted here in this topic. simplepinoi177 responded there also
Hi, i upgrade trough the ota (system updater), and i can not flash twrp as the bootloader is locked. I can not boot any img.
Have you tried factory reset in recovery?
Edmontonchef said:
Have you tried factory reset in recovery?
Click to expand...
Click to collapse
Yes I did, several times but still stuck in bootloop.

Bootloop issues

Hello folks !
So I just got my hands on a Redmi Note Pro 8:
Model - M1906G7G
MIUI Version - Global 12.0.5 Stable (QGGMIMX)
Android Version - 10 QP1A.190711.020
Kernel Version - 4.14.141-G78546ce
Click to expand...
Click to collapse
Since I'm a longtime custom ROM user on my previous Android devices, I wanted to go for it and install [ROM][CFW][10][begonia] Pixel Experience [OFFICIAL][AOSP] but I ended up being stuck in a bootloop.
The bootloader unlock went fine, but I couldn't find a functioning TWRP recovery that doesn't end up with an infinite bootloop.
Then I stumbled upon a LRTeam recovery and things went fine from there. I was able to access the custom recovery menu.
I taped on the "Install root" feature after that but when rebooting, the phone went bootlooping on that Redmi logo.
Even after pushing recovery and try and install Magisk over zip install, the same thing occurs, eternal bootloop.
Since fastboot was always accessible, I managed to successfully flash the device back to stock with XiamiToolsV2 and even when trying the process again, I couldn't manage to go further in the install.
What seems to be the problem? Am I missing something?
Thanks a lot lads !
Downgrade to android 9 and read the megathread

Categories

Resources