Hi, this watch (a1619s) is driving me crazy. I unlocked the bootloader and flashed stratOS v2, After that the watch just after optimization was restarting all the time.My mistake i went to force erase.
I flashed with cloner stock us/international 2.3.8.0 but touch was working and SN was missing.I rooted it and flash misc.img with the correct infos.Infos was ok except touch. I wiped it in fastboot mode still the same. I flashed Everest 2.0.63.1 ROM v2.0.1 Installer still the same.After flash custom rom sn is missing again and watch keeps restarting after optimization. When I tried to flash again the misc file on custom rom it was saying that there is not space to write the misc file from SD card (internal space) to the system folder. Help please...!
Related
Hi,
After flash, my htc 516 Dual sim is dead.
I have prober to flash system.img found on net *some rusian site), than it starts BUT Touch screen didnt work.
I also prober recovery - the same problem.
What i did?
First flasz boot.img by adb command.
Than recovery CWM
Super su.
THAN works perfect...
I did NOT make myselef backup.
I decided to probe kitkat so in fastboot i took ERASE Data, system etc.
Kiktat sucks. Now i have "empty" Htc.
Everything what i could found n internet also sucks... Even if phone starts i dont have touch screen.
Probe to flashing another files by comand adb flash tp c:/tp.img , radio, ts, aboot etc. Every kind of boot.img. system.img, System.tar.gz(from backups another users),
Everything by CWM (backup and restore) , Install from zip- but there is alltime error 0 or 7 .
Try to download the system files (all the rar parts) from here: https://yadi.sk/d/CON0Zh_DbfB56 export the file and update it via cwm.That might work!!
Hi guys, i got my H9 yesterday and because i thought i read enough on this forums i wanted to unlock it then install TWRP and install superSU to gain root access and stick with the stock firmware.
Unlocking went perfectly fine,phone booted to OS, than i flashed twrp 3.1.1-1 as advertised here and made a factory reset. Phone was stuck in bootloop for unknown reason.
I made several wipes and somehow managed to check all boxes in the wipe menu which erased the whole OS.
Now i read here that others have the "no OS" problem too but because i still have all unlocked fastboot and twrp i wanted to ask which method is best to flash back the original FW.
Which stock ROM is safe to install? i have european H9 is STF-L09C432B170 the right one for me?
Which method is the best to install it? Copy the 3 zips to internal stoagre via OTG device and install it out of twrp? I read that there is also a force method where users can push vol up, vol down and power simultaneously and enter the huawei install force mode.
I am quite sad that the phone was stuck in bootloop after twrp install and still dont know what caused it. When i install it from twrp there are 3 zips: update, data full public , hw eu. In which order do they have to e installed and is one of them overwriting the TWRP recovery?
Please give me a short hint/procedure, im quite afraid that i cant get my phone back to work and it is brand new. I dont know what caused the unsolvable bootloop.
Best regards and many thanks
Hi.
Check this:
https://forum.xda-developers.com/showpost.php?p=73334439&postcount=1
This help you.
Regards
thanks for the hint but i cant find a solution for me there.
ut this
i copied the 3 .zip files to internal today but TWRP doenst allow me to write them it fails with "write err errno 9"
then i tried to copy the update.pp in DLOAD folder on micro sd but this is not possible because filesize is over 2gb. i tried to format micro sd with twrp to exfat but it till doesnt work. please give me a little hint what to do im completely desperate about the situation.
Today i installed Huawei Multitool and extracted the .img file out of the update.app files, i was able to flash all 4, system, boot, recovery and cust.
Now the rec. menu is back to stock and everything got installed but the phone still isnt booting. i think it is because i missed the userdata.img which i cant find anywhere.
Other users here have the same problem. Is there a firmware package which includes all 5 .img data?
Best regards
i found the official huawei service full repair firmware with all necessary files for unbrick (system, cust, recovery, userdata, boot) flashed them via fastboot but stil device is "hanging" after the warning message that its unlocked. i think it is because i wiped vendor data in twrp but i cant flash vendor.img in fastboot. it is included in the fw package but cant be transfered to phone via fastboot. it stops at part 1/2 because the filesize allowd is around 470mb max but the extracted file has a size of 670. anyone know what to do?
Best regards
You need to go via the Rebrand way with no rebrand. I had the same problem and was trying to use the multitool without success. The oeminfo can be flashed alternatively if it fails during the HWOTA process.
https://forum.xda-developers.com/honor-9/help/how-flash-oeminfo-t3657499
ok i download all the folders with the .bat file. Then i download C432B150 from the czech site and add it to the update folder. Than i rename the 3 files accoding to the manual and run the .bat file but without rebranding right?
Des this tool any different than the HuaweiMultiTool or fastboot with flash command?
Best regards
I treid out HWOTA, the first step installing twrp is successful than i disattach usb cable as described and enter twrp. Then it says in twrp i have to connect again and press enter but then the bat file stops and doenst go on. i dont come to the point where i can choose rebrand or flash firmware.
Whats wrong here?
edit: i saw in the .sh file that the script executes wait_adb but my phone is not entering adb mode as it seems when in main screen of twrp. is this normal or do i have to set it manually in twrp
best regards
I was able to install the B130 now via 3 button recovery. Now im on B130 but cant update elsewhere. Also the 2 capacitive buttons are not working. Bootloader is locked again. Everything is stock and the phone runs great. When i update with the 3 buton method from external sd, which firmware should i use? i tried B150 full OTA but it aborts after 5% with an error. Do i only need to get a small OTA package now?
How can i put my cap. buttons back to work? Too bad only the 3 button method worked to recover the phone.
Best regards and many thanks.
I did the HWOTA with b120 firmware and then used firmware finder to update to b150.
The bug with capacitive buttons is present till Oreo. I use the home button gestures anyways.
Hope it helps.
ok, thats bad but they worked with the initial revision of b130 and b150 when i downloaded it OTA. Is this something like a fuse like.knox at samsung which happens at custom flashing?
Sent from my GT-I9300 using Tapatalk
the HWOTA method doesnt work, the batch file gets stuck after connecting the phone in twrp back to computer. in script it says wait_adb but it is not recognized somehow.
do u know a solution? anotherone here got that problem too.
im very afraid of that, i read here that everything related to twrp 3.1.1-0 and 3.1.1-1 is problematic a lot of people cant boot after installing twrp and can wipe whtever they want the phone never boots fully
whats the difference in the B130/B120 the phone came from huawei and the version flashed via tools? when i got it everything worked
i have this version.
ok so install twrp have frq and bootloader unlocked and then do backup out of recovery? with your file? can you provide download link? is this then a zip file?
I want to solve the thread and how i solved problem.
The B130 service firmware by huawei could be installed via 3 button method, than i was able to go up to the newest B180 via firmwarefinder and DNS method but with not working cap. buttons and flash etc.
Yesterday i installed TWRP 3.1.1-1(temporary) via HWOTA.zip method (ireplaced the older twrp in recovery folder) and successfully installed B120 and got the buttons etc working again. Then installed root and now system works fine and is rooted. My mistake was to install twrp over B130 or B150 which i downloaded OTA at the first day i got the phone. I tested this yesterday to install TWRP along with B150 and unlocked bootloader, infinite bootloop again. With B120 the TWRP 3.1.1-1 works out of the box without any loops.
The 2 trouble solvers where B130 service firmware and HWOTA with B120.
The external SD had to be inserted in card reader on PC because of the large filesize of the B130.
I would recommend to everyone before starting to play with the H9 to move the B130 folders to phone while it is still accessible. When everything bricks like in my case and u still have twrp than you can go to twrp main screen and connect phone to computer to rename the folder with B130 to "dload" and arrange update.app accordingly on PC or in TWRP file manager.
Can i set this topic to [SOLVED] myself?
Best regards
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
this works flawlessly with 3 button method
Hi everyone,
I ran out of ideas with my problem, and could really use some help / advice with this.
Trying to updgrade my STF-L09C432 from B368 to B385 using HuRu updater, something went wrong and now it bootloops after the blue Honor logo.
Fastboot, Huawei eRecovery and TWRP are still working and accessible, my device is bootloader unlocked and says FPR unlock in fastboot mode.
So here's the detailed steps and procedure which I followed:
0) TWRP Backup of System + Data
1) Load three update files (FullOTA) via FF: update.zip (update.zip), update_data_full_public.zip (update_data_full_public.zip), update_full_STF-L09_hw_eu.zip (STF-L09_hw_eu/update_full_STF-L09_hw_eu.zip)
2) Create folder on SD-card with above files and TWRP v0.3 as recovery.img and the HuRu 0.4 zip file. Additionally I've left the HuRu 0.3 in the same folder renamed as HuRUpdater_0.3_old.zip
3) Installed the HuRu 0.4 from TWRP with zip verification disabled (tried before with enabled, but it failed -> call me stupid but I've double checked the checksum with a new download, so I took the risk).
4) the installation log showed warnings about some missing .zip files, but I ignored those as well, as I've never heard of them and didn't have them from FF.
5) rebooted the system and caught the first bootloop
Now I tried myself to fix it the following way, but unsuccessful until now:
1) Flashed TWRP into recovery_ramdisk because I didn't know the right procedure to boot into it
2) Flashed the new B385 versions of KERNEL.img, RAMDISK.img and RECOVERY_RAMDIS.img which I extracted from the UPDATE.APP -> still bootloop
3) Flashed TWRP into recovery_ramdisk again because I still didn't know the right procedure to boot into it
4) Flashed the old B368 versions of KERNEL.img, RAMDISK.img which I extracted from the UPDATE.APP, but not the RECOVERY_RAMDIS.img this time -> still bootloop
5) Then I've managed to boot into TWRP finally, and tried to restore my previous backup as a last resort, but that still didn't resolve my bootloop
Anybody has any idea what I could still try? Maybe I'm missing something obvious, or I'm still to new to this to see what is wrong.
If possible I'd like to keep my data intact, but I could probably extract most of it out of the backup, if nothing else helps.
Thank you very much!
Best regards,
Chris
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Schrubbi said:
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Click to expand...
Click to collapse
well, aslong as its still unlocked (frp & bl) i'm able to help.
Do you have telegram? if so, send me your username through pm.
Regards
I managed to get into TWRP again when I've installed the latest kernel and recovery images. After that I've realized that I still had Magisk installed and Active.
Uninstalling that solved my bootloop for now.
Unfortunately my backup restore just returned me to the previous version B368 which I already had installed... so lets see what happens if I apply the update again
---------------------
Edit:
Update applied, without magisk installed, still bootloop... At least the way back was quicker this time
Any hints what's going wrong are appreciated!
As curtana has dynamic partition, we can't flash any zips to modify partitions. That's why we can't change/edit fstab to make data encryptable. But i found out, that, the partitions' content can be edited right after flashing any rom. They become RO only after first boot.
Instructions:
1. Download any Eu rom for you variant
2. Download decrypt zip from here
3. Flash Eu and flash en_de-crypt_v2.zip right after that without reboot
4. Unmount vendor partition
5. Format data and reboot.
Thanks. I'm going to try this later.
So after that you can edit root files? cuz i want to edit mixer_paths.xml because of the very low sound
After this , phone always reboot in fastboot , xiaomi eu 11.0.9.0 ! who can i fix this now?
Anasbel said:
After this , phone always reboot in fastboot , xiaomi eu 11.0.9.0 ! who can i fix this now?
Click to expand...
Click to collapse
I got the same issue and the only one thing I can fix it was to reinstall ROM or flash stock ROM via MiFlash.
I think rebooting in fastboot shows that the ROM on your device is broken.
For example when I'd tried to install Xiaomi.eu after installing LineageOS (ofc did full_wipe), I got the rebooting issue. But flashing Stock ROM before installing that ROM, It went well.
It sometimes depends on the installed ROM or other zips which you install it with
For me it worked also with Global 11.01, but not by the first Try and I could not see it in Miui, but after flashing a Custom Rom (Havoc) over it, the Device was decrypted.
Can't flash it with Joyeuse.
Can someone please port it?
Thanks!
this method does not work, writes rw, but when you delete the system application after restarting, you get bootlop.
I can't believe he provided a boot-loop tutorial
will it work for poco m2 pro (GRAM)?
@Sudeep Duhoon Bro can you help this thread out plz?
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
There is a newer Version v3 of the decryption Zip. Could you please update the Link?
If I am not mistaken, the zip is designed to encrypt, it will not work to decrypt.
Via recovery:
- If the file exists: -
/vendor/etc/fstab.qcom.bak
1 - Go to the file:
/vendor/etc/fstab.qcom
2 - With a text editor change in fstab.qcom:
"encryptable = ice" to "fileencryption = ice"
- If the file does not exist: -
/vendor/etc/fstab.qcom.bak
1 - Go to the file:
/vendor/etc/fstab.qcom
2 - We copy it in the form:
/vendor/etc/fstab.qcom.bak
3 - With a text editor change in fstab.qcom:
"encryptable = ice" to "fileencryption = ice"
The error is displayed in the selected line of the encryption.sh file, the command has the strings reversed.
Changing that line in the file should work the .zip
Hello everybody!
Unfortunately my cell phone has a softbrick and I don't know how to fix it.
Starting position (unlocked bootloader):
I was on 10.0.7 Xiaomi.eu ROM (worked very well) and installed LuckyPatcher. After patching a file in LuckyPatcher, a reboot came and it took a long time, after the reboot, both SIM cards no longer worked and no WLAN.
Then I installed the Xiaomi.eu ROM with TWRP again - same error, then the original FastbootROM - same error.
I entered + # 06 # in the phone app and lo and behold, the phone no longer has an IMEI.
I hope someone can help me.
I have a TWRP backup, I restored the EFS but nothing changed. HOW can I extract modemst1.bin and modemst2.bin from efs1.emmc.win and efs1.emmc.win.sha2?
Regards Mirakulixs
1. try flashing original boot image without magisk (idk... worth a try, that's what I do when I boot loop because of some crap I installed, though I didn't check if I somehow lost my IMEI)
2. try flashing stock rom using miflash
Hey (same error is no IMEI´s and no Mac-Adress and Baseband is unknown)
to point 1 - same error
to point 2 - same error
try to flash zip with twrp.. - same error
with mi flash fastbook rom - same error