I am still not able to install latest lineage without bootloop see here:
see older xda thread
so this weekend I thought well give it a last try before selling my unlocked H850 on ebay. I want to flash it back on stock rom and do the whole process again - maybe flashing this time a different custom rom(15.1 unofficial).
The problem is it seems stock rom is no longer available.
See here
LG-H85010E-Flashable.COMPLETE.zip -> download speed is very slow and I wasn't able to finish download successfully (always connection errors )
H85010e_00_OPEN_EU_OP_0817.kdz -> get no access to this file (has LG stopped service?)
can be closed solution was first flashing Android 8 stock rom with uppercut (H85030f_00_OPEN_EU_OP_1122.kdz) than flashing custom rom based on Android 9 (lineage-16.0-20200811-X86CPU-h850 - thank you to the author) and than I was able to flash official lineage 17.1 than bootloop was suddenly fixed. Each time after flashing I just did normal wipe (confirming with yes).
official tutorial completly sucks:
https://wiki.lineageos.org/devices/h850/install
-> sideload is not necessary and when you come from older Android Version you have to flash Lineage 16 before (no evidence and no image in download section).
Related
Here is the Solution watch this video
https://www.youtube.com/watch?v=kTdKmceC5xU
am not able to update twrp
twrp-3.1.0-0-onyx.img
twrp-3.0.3-0-onyx.img
twrp-3.0.2-1-onyx.img
when i flashed these files using twrp and rebooted my device i was stuck in one plus logo.
Even i cant flash any of above 3 twrp files using fastboot adb method i am getting an error "remote dtb not found" pls check screenshot
then i reinstalled twrp-3.0.2-0-onyx.img using adb fastboot method , but i cant not install or update version above 3.0.2.0 plz help
Hi guys if anyone facing same problem Read this
PROBLEM
1)Error Code 7 while flashing new ROM (like Nogut ROMS ).
2)Remote dtb not found while updating old twrp to new (eg. twrp 2.8 to twrp 3.1.0.0)
Cause of problem
Users who have already flashed and rooted their phone and using custom ROMs like CM12 CM 13 or any other from past year will likely to face this problem
while updating twrp recovery or while updating to new custom ROM Nogut cm14 .
Because new custom ROMs have bootloader in diffrent partition (something like this) so you wont be able to flash your phone with new ROMs i.e cm14 or nogut or you wont be able to flash new twrp recovery which is 3.1.0.0
Please keep in mind if you are using following twrp version then you should flash your phone with old twrp 2.8.7.0
twrp-3.0.2-0-onyx.img 14.4M 2016-04-04 23:04:23 EDT
twrp-3.0.1-0-onyx.img 14.5M 2016-04-01 04:24:54 EDT
twrp-3.0.0-1-onyx.img 14.5M 2016-02-15 23:17:25 EST
twrp-3.0.0-0-onyx.img 14.4M 2016-02-06 09:18:41 EST
above point is important look at the solution now
Solution
Step
1)flash your phone with old twrp version TWRP 2.8.7.0 using fastboot method(because we are going to install stock recovery in my case stock recovery of oneplus X lollipop version)
2)after installing stock recovery install 2.14 ver of stock ROM of oneplus X (for oneplus x devices) (for other brands eg samsung look for ur old stock recov and ROM)
3)install old Stock ROM in ur device
4)now again boot into stock recovery and install latest stock ROM (for oneplus X i installed latest oneplus X oxygen OS 3.1.4).
5)after doing above step you can install latest twrp-3.1.0-0-onyx.img without any "remote dte not found error" using fastboot.
6)once you flash twrp-3.1.0-0-onyx.img flash your phone with latest CM14 or any latest android N or nogut ROM without any problem
Note : For error code 7 some people suggested to edit udatescrip file which is not good solution and it is temporary and it wont work for all so do it as i suggested
Comman ERRORS :
1) if you are on twrp 3.x.x.x you will face Remote dte not found while booting your phone in stock recovery using fastboot
so first of all flash your phone with old twrp 2.8.7.0.
2)Do not wipe your internal storage in frustration it will create more problems because you wont be able to transfer files into your phone to flash it (Use OTG cable or SD card if u did it already).P.S you can do it afterwards
Do i need to install stock recovery of stock ROM ? some help would really be appreciated
i can install all twrp upto "twrp3020 " version
but if i try to flash greater version like twrp3021 or twrp3100 m getting same error
i need new twrp because i am not able to flash Android N custome roms i am getting an error code 7 when i am installing ROM
Follow the mega unbrick guide, then update your bootloader then flash latest twrp.
@Joshwin Aranha
CheckYourScreen said:
Follow the mega unbrick guide, then update your bootloader then flash latest twrp.
@Joshwin Aranha
Click to expand...
Click to collapse
thanx for replay but i found solution
Hi guys if anyone facing same problem Read this
PROBLEM
1)Error Code 7 while flashing new ROM (like Nogut ROMS ).
2)Remote dtb not found while updating old twrp to new (eg. twrp 2.8 to twrp 3.1.0.0)
Cause of problem
Users who have already flashed and rooted their phone and using custom ROMs like CM12 CM 13 or any other from past year will likely to face this problem
while updating twrp recovery or while updating to new custom ROM Nogut cm14 .
Because new custom ROMs have bootloader is diffrent partition (something like this) so you wont be able to flash your phone with new ROMs i.e cm14 or nogut or you wont be able to flash new twrp recovery which is 3.1.0.0
Please keep in mind if you are using following twrp version then you should flash your phone with old twrp 2.8.7.0
twrp-3.0.2-0-onyx.img 14.4M 2016-04-04 23:04:23 EDT
twrp-3.0.1-0-onyx.img 14.5M 2016-04-01 04:24:54 EDT
twrp-3.0.0-1-onyx.img 14.5M 2016-02-15 23:17:25 EST
twrp-3.0.0-0-onyx.img 14.4M 2016-02-06 09:18:41 EST
above point is important look at the solution now
Solution
Step
1)flash your phone with old twrp version TWRP 2.8.7.0 using fastboot method(because we aree going to install stock recovery in my case stock recovery of oneplus X lollipop version)
2)after installing stock recovery install 2.14 ver of stock ROM of oneplus X (for oneplus x devices) (for other brands eg samsung look for ur old stock recov and ROM)
3)install old Stock ROM in ur device
4)now again boot into stock recovery and install latest stock ROM (for oneplus X i installed latest oneplus X oxygen OS 3.1.4).
5)after doing above step you can install latest twrp-3.1.0-0-onyx.img without any "remote dte not found error" using fastboot.
6)once you flash twrp-3.1.0-0-onyx.img flash your phone with latest CM14 or any latest android N or nogut ROM without any problem
Note : For error code 7 some people suggested to edit udatescrip file which is not good solution and it is temporary and it wont work for all so do it as i suggested
Comman ERRORS :
1) if you are on twrp 3.x.x.x you will face Remote dte not found while booting your phone in stock recovery using flashboot
so first of all flash your phone with old twrp 2.8.7.0.
2)Do not wipe your internal storage in frustration it will create more problems because you wont be able to transfer files into your phone to flash it (Use OTG cable or SD card if u did it already).P.S you can do it afterwards
mhmm.. the unbrick guid dosnt help.. followd the guidé - now my bootloader is locked and stuck locked so no 2.8.7.0 flashing.. Ideas? i`m working now 24h this issue..
Wagner.B said:
mhmm.. the unbrick guid dosnt help.. followd the guidé - now my bootloader is locked and stuck locked so no 2.8.7.0 flashing.. Ideas? i`m working now 24h this issue..
Click to expand...
Click to collapse
are you on stock recovery right now ?
Finaly the Lv.2 support got it back working via "our" msm unbrick tool (Still got it on my drive =D)
but learned nothing - trying to get lineageOS again.
The recovery is now TWRP v3.1.0-0 for E1003_15_161107 (it works for now on a backup..)
But... i must say - I'm very worried that i cant flash lineage again..
I dont know what the trick is...
Here is the Solution watch this video
https://www.youtube.com/watch?v=kTdKmceC5xU
Yes!!
I ve been looking for a solution the past days since i got stuck in older twrp versions and could only upgrade to android 6.
Thanks man!! You rock!!
I had downloaded latest version of lineage OS from official website and I tried to flash on my REDMI Note 3 Kenzo but I can't here is the screenshot attached of remark.
Pls help
I was just about to post about this. I have the same issue, a work around I found was described in this video: https://www.youtube.com/watch?v=bGVOR0kugZw
However, now that I have it installed, and try to OTA update, I get the same, I have to repeat the steps in the video every time I update, kinda frustrating and unnecessary imho. I had the latest MIUI updated and unlocked with the miui unlocker before the wiping and installing. All I have found its related to the bootloader not supporting android N.
Look at the error and you will see the issue.
Your firmware is too old.
Download one from Lineage thread and flash that before Lineage
update, I installed the firmware from this thread: https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
now update goes thru like its supposed to
every recovery i flash gives me ERROR 7 :/
i have a 'kate' and befor i used to flash roms without issue. kenzo roms and flash kate modem done.
but phone crashed some months ago so i changed but now i want it again. and now im back on did a edl flash miui beta unlocked bootloader flashed twrp (all the twrp possible btw i tried all i could find) they all dont want to flash a custom rom i tried 7 different ZIP of custom roms... i tried to flash 4 diffeeent versions of RR 5.7.4 and 1 RR 5.8.4 all give error 7. flash kate modem. still error, then flashed modem with emmc thing patched nope still wont flash any custom rom
does anybody know how to fix this
You have to erase dalvik cache and DATA it will bring you new setup but still your device would be updated....
A month ago I tried installing Android 9.0 ROM and i got reboot loop after I did the phone setup. I tried different ROMs and everything had the same problem. Even twrp will also stop showing any files in the device and I need to change the file system and revert it back again then mount my phone to desktop and transfer the ROM. I was told that it was because of me not installing MIUI 10 before trying it. So today I installed MIUI 10 and tried installing lineage 16.0 and got the same problem. Phone starts going into reboot And recovery does not show any files!
Please help me from this hell! I'm hating this MIUI.
mynameisvineeth said:
A month ago I tried installing Android 9.0 ROM and i got reboot loop after I did the phone setup. I tried different ROMs and everything had the same problem. Even twrp will also stop showing any files in the device and I need to change the file system and revert it back again then mount my phone to desktop and transfer the ROM. I was told that it was because of me not installing MIUI 10 before trying it. So today I installed MIUI 10 and tried installing lineage 16.0 and got the same problem. Phone starts going into reboot And recovery does not show any files!
Please help me from this hell! I'm hating this MIUI.
Click to expand...
Click to collapse
First of all I have to assume that you are sure that you have Redmi 5 plus (Vince) and not Redmi Note 5 Pro (Whyred), if this is the case let´s go to the next.
Any Miui rom encrypts data by default at least from oreo so no way to avoid this, if you flash a Miui rom then your data wont´be accesible and the next rom to be flashed you have to sideload it via adb (there are other ways).
I think you missed something here, if you flash a mui rom and over it a pie rom then there´s no way that your device reboots to system. You only have to flash firmware 8.1 from miui not the whole rom.
Start this from the scratch; I recommend OrangeFox recovery instead of TWRP so it has more features https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479
- Before to flash nothing In orangeFox recovery enable the options DM-verity and disable force encryption, you will find too options to keep OTA and others, check which you want.
- Flash the firmware miui 8.1 https://androidfilehost.com/?fid=11410963190603850663
- Flash the pie rom for vince (may not apply for a GSI pie)
- Flash the Gapps (if needed)
it´s all.
Just a tip; be careful with changing system of files at any time so if the process is cutted/interrupted for some reason your device could be seriously damaged.
it does. you just need to flash firmware file first.
ABOUT VERSIONS OF kvt:
2.x is if you're coming from stock Oreo or Pie
3.x seems to be only for stock Pie (otherwise networks don't work) - Oreo modem still has to be flashed though
There is a guide for GSI, but it is outdated, no longer maintained and all links are dead. That's why I'm creating this up to date guide.
If you do not know, what is Project Treble and GSIs, google it first. Proceed only if you know what are you doing. This guide is only for those, who know what is bootloader, fastboot, recovery and TWRP. If you don't, learn that first. There are many guides (for example guides for rooting and Magisk) UNLOCKED BOTLOADER REQUIRED
Guide
1) Download needed files:
- treble recovery: https://mega.nz/#F!b8RgGQCa!48TRsDcJFpaAGNOcc9Fb-A?GxR2TCAA
(this is my mirror, as original links are dead, don't know who is the original developer)
- kvt (find lastest version here) https://androidfilehost.com/?w=files&flid=303096&sort_by=date&sort_dir=DESC (developer deivesj)
(this allows GSI to work on Moto Z2 Play with some of it's stock features like fingerprint gestures, device gestures, pass safety-net and more)
- if you want to use Android 9.0 Pie based ROMs and older, you might want to use V7 kvt instead:
https://mega.nz/#!7w5V1KpQ!uoCMqynn5D83trvZ6uXY30S8b9rLiBlXf1JTeMYQ0rc
- if you are coming from stock Android 9.0 Pie ROM, you will need modem from Android 8.0 Oreo
https://mega.nz/file/mxhxXCaI#nJpdQ3nPnc6urkYP8vLrVb_vc_7EsnXK7MXw3U1xohw
- you may need stock recovery https://mega.nz/#!XphFEIxK!yNdHJSakfO90K1ua92SODoqd85nvwRi7h65EA8RkOuI
-GSI of your choice (links below)
transfer kvt to your phone to external microSD, keep the rest in your PC
1) go to fastboot mode (power+volume up simulaneously)
2) flash treble recovery (using fastboot command: fastboot flash recovery 'filename.img')
3) boot to recovery and wipe system, data, cache
Note: after boot to recovery, touchscreen doesn't work. Turn screen off and on to make it work!
4) in recovery, flash kvt zip. It will guide you through
5) reboot back to bootloader
6) flash chosen GSI as system image (fastboot flash system 'filename.img')
7) if you are coming from stock Pie, flash Oreo modem (fastboot flash modem NON-HLOS.bin)
reboot
Note: If you are coming from stock ROM, decryption may fail. The easiest way is to temporarily flash stock recovery. After decryption fails, it will prompt you to reboot and format data. TWRP can't do it, but stock recovery can. After you are booted, you can flash TWRP again.
Where to get GSIs:
the biggest list is here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
For Z2 Play, always download arm64 version and Aonly
There is a folder with ported stock ROMS (MIUI, Samsung, Moto...) on mirrors.lollinet but they do not work on Z2 Play. I also tried various stock ROM ports from other sources and they did not work. Custom ROMs fork fine.
Magisk:
Standard Magisk versions may not work. If you get bootloop, after installing Magisk, flash uninstaller. Then you can try phusson's version:
leodexe said:
Updates:
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
Click to expand...
Click to collapse
Ask if something isn't clear.
updated treble
Updates:
KVT 2.6: https://androidfilehost.com/?fid=8889791610682867863
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
I am currently using Pixel Experience Plus (Android 10) GSI, I installed it with latest KVT 2.6 and most stuff works out of the box. If you come from Stock Pie you need to flash the modem file from Stock Oreo to get proper audio during calls, as the modem from Android 9 gets bugged on Custom ROMs breaking the audio during calls. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file
Confirmation
Mate can u confirm whether this kvt fix the screen flickering issue when there are more than 3 notifications in the status bar and does it have fingerprint gestures enabled???
lordfinix said:
Mate can u confirm whether this kvt fix the screen flickering issue when there are more than 3 notifications in the status bar and does it have fingerprint gestures enabled???
Click to expand...
Click to collapse
I don't use fingerprint gestures so I can't tell you about that. Also I had experiencing some crashes and reboots with this GSI lately, so I will try with another one once I can access internet to download anothet GSI.
CONFIRMED
i confirm it by flashing the flickering issue is gone and the gestures works as well this is by far the most stable KVT released kudos to developers
There are new versions of kvt available. Check the updated first post for link to deivesj's last files.
I did not experience any flickering or other graphical glitches with the new (2.X) versions of kvt (unlike the old v8 one).
Fingerprint gestures work, but not in all gsis
leodexe said:
Updates:
KVT 2.6: https://androidfilehost.com/?fid=8889791610682867863
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
I am currently using Pixel Experience Plus (Android 10) GSI, I installed it with latest KVT 2.6 and most stuff works out of the box. If you come from Stock Pie you need to flash the modem file from Stock Oreo to get proper audio during calls, as the modem from Android 9 gets bugged on Custom ROMs breaking the audio during calls. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file
Click to expand...
Click to collapse
Thanks, I will update the guide
Could someone please give me a mirror of kvt v2.6? androidfilehost is terribly slow...
Hello,
Seem to have lost my network after flashing the pixel experience gsi from stock. imei missing as well. Any help?
It may be problem with modem.
What was your stock ROM? 8.0 or 9.0?
What version of kvt did you use? 2.x or 3.x?
How install?
how is the modem installed?
It's explained in the guide, step 7.
Wrongly flashed modem may cause WiFi, Bluetooth and SIM not to work
Kvt link is down. But you can use LineageOS with treble support now
It's not the first time I'm dealing with custom roms but this H850 project causes me headaches but finally I found somebody with the same problem I have: Video of H850 shutdown problem
I am now back on stock rom (Android 6) so how to upgrade to 17.1 without bootloop?
can be closed solution was first flashing Android 8 stock rom with uppercut (H85030f_00_OPEN_EU_OP_1122.kdz) than flashing custom rom based on Android 9 (lineage-16.0-20200811-X86CPU-h850 - thank you to the author) and than I was able to flash official lineage 17.1 than bootloop was suddenly fixed. Each time after flashing I just did normal wipe (confirming with yes).
official tutorial completly sucks:
https://wiki.lineageos.org/devices/h850/install
-> sideload is not necessary and when you come from older Android Version you have to flash Lineage 16 before (no evidence and no image in download section).