Hello everyone,
so I have been playing around with my HTC U11. I unlocked the bootloader and installed the newst TWRP version. Then I flashed it to Lineage 16. However I could not install the HTC Edge Sense App and since I couldnt find any answers to that problem decided to flash back to stock rom and then update to Android 9.0 and get my Edge Sense back.
So I checked for my device CID which is HTC_034 and downloaded myself the stock rom from the getdroidtips stock firmware collection (cant post link because I am new)
I did the MD5 Checksum and everything was fine. However when I try to sideload it via adb i get a zip file corrupt error and TWRP stops it. Then I tried pushing it and installing it through the install function of TWRP. I can push it onto the device but when I want to install it I get the same error again. Things I tried so far:
1. used an older version of TWRP
2. all the 4 stockroms available for the HTC_034 on said link
3. load the .zip onto an sd card, enter it and tell TWRP to install from there - didnt work either.
4. rename the .zip to package.zip (read it somewhere)
Everytime I get the Error that the .zip is corrupt. Checksums of all the files are ok...
Has anyone an idea what else I can do? I would actually be fine with lineage 16 if I could just get my HTC Edge Sense back (
Thanks in advance for your help
Headcannon: what if the problem ia for some reason the twrp? Could i somehow flash the stock rom without going through the TWRP?
I am not talking about removing it. I am talking about somehow flashing without using it. Maybe via adb or odin?
Then the stockrom should be able to install. If something goes wrong I can still boot into recovery and use TWRP to get LOS16 back.
Ok so since I read somewhere that on the pixels root access was necessary to get HTC Edge Sense running I installed Lineage 16, added GAPPS and then used Magisk to get root access.
I still can't install HTC Edge Sense. I even downloaded the apk and pushed it onto the phone but the install always stops and tells me it can't finish
So for now I can neither have stock rom nor Edge Sense - any suggestions because I am slowly running out of ideas
Related
I got my DNA back in December, unlocked with S-ON, rooted, and flashed a lightly modified stock ROM. It's been super stable, so I figured I wouldn't mess with it, and I've been running it since.
Yesterday, I was trying to free up some space on my device by integrating updates of system apps through Titanium Backup, and it jacked stuff up pretty royally. I figured, this is a great chance to install a new Sense 5 ROM.
I went through TWRP, installed the new ROM, cleared data, and when it restarted, it hung at the white HTC screen. Undeterred, I tried again through recovery. Then through sideloading a different ROM. Then by restoring a backup, downloading a new ROM and trying through recovery. Then installing CWM instead of TWRP and trying that way. Then by sideloading through CWM.
Every single method by which I've tried to install a new ROM has resulted in the phone hanging indefinitely at the white HTC screen.
I have obviously searched repeatedly for a fix for the white screen issue, and while I can restore an old backup and get the phone running, I can't seem to find a solution that gets me up and running on a new ROM. I'd hate to go through all the work (my phone's been unusable since around 8 PM last night) and not come out of it with a new ROM.
Am I missing something? Maybe I should be installing a new kernel before installing the ROM?
you are s-on you must flash the kernel boot.img via fastboot then flash kernel modules via recovery
copy boot.img from rom.zip
in command prompt goto folder with boot.img and enter
fastboot flash boot boot.img
then create a flashable module.zip and flash via recovery or adb eacxh module into system folder or just s-off your device and re flash rom.zip
The best way to fix ur phone now is to go through RUU, first relock the bootloader through fastboot, then enter RUU again through fastboot nd run the RUU from ur pc, ur good to go.
The reason it's getting stuck thr is becoz the system partition isn't getting mounted
As soon as I typed "S-On" in that original post, I started getting suspicious that might be the problem, but none of the ROMs I was trying specifically mentioned the need to be S-Off. But that does make sense.
So I spent the afternoon getting it S-Off, which was a bit of a hassle, and now in about three minutes, I see if I can indeed flash a ROM. I feel pretty optimistic, though.
Update: Success. I am now a very happy person.
congrats hope you enjoy
now no need for anything special to flash roms or kernels.
Okay so when I went to Italy (maybe not the problem) my phone turned on registered and now is stuck in a boot loop. I have followed the directions to hardware button into TWRP 3.0 so I can install a ROM or backup. I can get the screen for TWRP and unfortunately as soon as I try "Install" or "Restore" it freezes either trying to install a ROM or backup after I select the file; the progress bar at the bottom stops then it kicks me back into the bootloop issue. The ROM I had was stock.img that I rooted (when we first could) and I froze all the spyware (carrier IQ and tmo apps) my only guess is either that the Italian tower figured my phone was rooted and did something or my TWRP is bad. Problem is I can't get into something to either install an older TWRP (or try 3.0 again) and just install a ROM again. So any suggestions on how I can either install TWRP again is appreciated. :crying:
Oh if anyone has an answer on whether traveling to another country and registering on the network (I'm pretty sure that's not what created this odd behavior but who knows) could have done that I would appreciate it too.
Thanks
Okay for some reason (and I don't even want to turn off might end up with an LG ghost on my screen) I got into download mode. Anyone remember the Fastboot command to flash the stock IMG file (yeah got it from @TheJesus post) I extracted the 4gig file but don't remember (still jet lagged) the fastboot command so I can get restore default.
I believe the image file is too big to flash thru fastboot, so what we do is use the TWRP flashable file from the other thread there. And I'm not positive if TWRP 3.0 is buggy, but I see people having problems.
Sent from my LG-H901 using XDA-Developers mobile app
Buggy
YrrchSebor said:
I believe the image file is too big to flash thru fastboot, so what we do is use the TWRP flashable file from the other thread there. And I'm not positive if TWRP 3.0 is buggy, but I see people having problems.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
So I flashed the older TWRP recovery instead but still not working. Also TWRP is also now not loading each time I do the hardware (power and volume) recovery option. I think I'll just need to go into download mode since I can't get ADB to work either (if I still can) send the default recovery from @TheJesus files of the .img and then hope I can re-lock the bootloader (get rid of that message at boot) and see what happens at the store.
Very disappointed.
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
Hello,
first of all i want to mention that i have a special skill when it comes to choosing smartphones to buy. I like em small and cheap so i always had trouble installing custom roms when buying new phones. Just like this time, when i decidied that replacing my Galaxy S5 Mini screen for the fourth time is just not worth it anymore. I ran to the next store, checked the offers, found the Galaxy A20e, did a quick google "A20e lineage" saw there were a few install threads and decided to buy the phone.
That was on Thursday i have since then continuously tried to either root the stock firmware or flash TWRP to install Lineage GSI.
Whatever i try, when rooting with Magisk and afterwards booting the rooted OS using the recovery key combo, the touchscreen won´t work.
I can boot to the unrooted OS and use the touchscreen.
When installing TWRP using XDADEV guide, i can boot to TWRP right after install, wipe and flash required zip file but after the next reboot i can only boot into stock recovery.
Here´s what i did so far:
Software Used:
- Odin 3.14
- Magisk Manager App 7.5.1
- SamFirm 0.3.6
- downloaded the newest Stock firmware "A202FXXU3BTD1"
- unlocked bootloader / SamsungVault
- Flashed newest Firmware "A202FXXU3BTD1" using Odin.
- Installed Magisk Manager
- Patched extracted file "AP_A202....tar" from "A202FXXU3BTD1"
- Moved the patched AP file back to computer
- Flashed modified AP + stock BL, CP and Home_CSC again
- Wipe/Factory reset
- Start Phone with Power+Volume Up until Logo flashes, then release for rooted OS
- Touchscreen not working
- Boot Phone without root (just press Power Button)
- Touchscreen works fine
II then repeated the complete procedure with an Andoid 9 based FW "A202FXXU3ASL4" which ended with the same result.
Then i wanted to move on, since i always thought that Installing TWRP normally does not require root permissions.
I found several guides, some required root, some not. So i decided to try that. I Found two different testing versions, one from xda and flashed them regarding to the HowTo.
With the Android 10 stock firmware, odin was not able to install them at all.
The Android 9 Stock firmware was able to install TWRP and i was able to wipe and flash additional required zip file but after the next boot, i was only able to boot to stock recovery.
I will continue trying different Firmware versions, for now i want to go back to the newest stock FW since i have tried this one in the beginning of my research, maybe now, 15 hours of work later, i will manage to get it running =D
I am willing to provide further details, just let me know. Hope someone has an idea.
best regards,
Hannes
correcting
after frther testing, there is no way to boot into unrooted OS with working touch once magisk patched firmware is installed
GG
looks like reading and testing for 2 days built the right knowledge so after flashing the most recent firmware and only flashing the modified boot.img again (this was one of my first steps ever) this time it seemed to work.
Magisk is officially installed and the system is rooted. on to the next step, i´ll keep reporting.
on to the next one
I was finally able to get TWRP running after flashing Pie based Stock FW.
Now i am stuck installing Q based GSI, they just wont boot.
Pie based GSI work fine, is flashing Q based Stock FW required to install Q based GSI using TWRP?
SOLVED
hannes22 said:
looks like reading and testing for 2 days built the right knowledge so after flashing the most recent firmware and only flashing the modified boot.img again (this was one of my first steps ever) this time it seemed to work.
Magisk is officially installed and the system is rooted. on to the next step, i´ll keep reporting.
Click to expand...
Click to collapse
Could you be more specific on how you managed to root your A20e SM-202F? I've got the exact same issue with an unresponsive touch screen. My bootloader is unlocked, no problem there. I've tried three different firmwares (one of them being the exact same as stock, and the others are newer versions), and several different (but similar) methods. I've tried patching the firmware with both latest Magisk Manager and the canary version. I use latest Odin. I've also tried to patch both the full AP-file and the only the boot.img (boot.tar). But every time that I reboot into android after I've done the rooting I get a touch screen that's not working. I just can't get past that point...
The phone I'm trying to root has Android 10 and U3 bootloader, NEE version.
EDIT - The solution was to first download and flash the newest firmware _without_ using a patched Boot.img or AP.tar-file. I.e, patching the same firmware the phone had out of the box did NOT work. After the firmware update I could successfully flash the patched Boot.img file and root the phone.
bottom line is what is the easiest way to roll back to stock firmware and get ota becuase i tried some guides and failed?
in detail: i installed twrp and flashed lineage os 8 but it somehow dont work proberly and cant detect the sims and keep crashing so i want to rollback to stock rom i downloaded the firmware but it was .ozip extention and flashed stock recovery but when i go to select the file from internal storage it reads folders in random letters like "ydc45shabshdbha" and i cant find the ozip file so im stuck now can any one help me
You could flash the ota with twrp .. and you can rename your file. If you need any help about it ..you can knock me on telegram