I am really happy with Carbon 5.1, but thought Oreo might have achieved similar stability
Problem is that after flashing .570 and .291 there is a bootloop into recovery when attempting to flash any Oreo boot.img
The crazy part - the device was bought used with D6502 in the settings, and after flashing .291 using flashtool? Baseband patch fixed connectivity issues - Then I pull out the MicroSD strip and lo and behold its actually D6503. Then any RR/Carbon/lineage Oreo boot.img throws the recovery into a bootloop
Immediately flash the 5.1 Carbon boot.img and things return to normal. A bit confusing here.
Apologize if this is dumb - but can I just install Oreo ROMs without the initial boot.img flash, or even on top of one extracted from Andro/Advanced Kernel?
Okay just pushed through it
I didn't flash the RR boot.img coming from carbon 5.1 N. Just RR 6.0 or 8.1 with gapps regular style and not a single hiccup. I forgot to download magisk and came back and the Recovery loop began
I decided well WTF let's try to flash magisk in between loops it does modify the boot.img. The loop stopped and I took my time flashing xposed 8.1 and the baseband patch.
RR 8.1 or 6.0 works beautifully without a hitch but entering recovery begins the loop. I am going to try flashing older TWRP versions or the modded 3.1.1 by the generous developer
Problem solved - Just installed TWRP recovery 3.1.1, many thanks to aboodyaiman - https://forum.xda-developers.com/xperia-z2/development/recovery-twrp-3-1-1-0-touch-recovery-t3640856. And as I suspected it was a boot.img / recovery issue. Now running on my desk for 30 minutes without a hitch in recovery and no problems with LOS / RR Oreo
Great work everyone ITT, congratulations all round
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!!
Hello everybody, i'm new in this forum! I'm really disappointed because i can't root my tablet after many procedures, downgrades, updates, flashing!
Actually, there isn't a kernel and a recovery for the latest nougat version, and with the latest twrp the touch doesn't work. Even if i have unlocked bootloader i can't do nothing... I really appreciate if everyone has a solution for this!
I've tried root kernel but with the latest kernel the os doesn't boot, it stops with the boot animation.
I've tried downgrading with lollipop and marshmallow too, installed respectively twrp 2.8.0 and twrp 3.0 and then flashed a prerooted nougat zip created with prf creator, but after flashing it stucks with sony logo.
Can't help with TWRP but you can patch up boot.img of newest kernel (32.4.A.1.54, right ?) https://forum.xda-developers.com/xp...ot-automatic-repack-stock-kernel-dm-t3301605
zacharias.maladroit said:
Can't help with TWRP but you can patch up boot.img of newest kernel (32.4.A.1.54, right ?) https://forum.xda-developers.com/xp...ot-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
Yes, i've tried this method. I can patch the boot.img of the newest kernel, but when i flash it to the tablet and then i boot in android, the touch doesn't work. it boots up, but i can't go over the lockscreen cause of the touch issue.
Anyone have any solution for the flash to work with magisk?
If i uninstall and install SU my flash will work?
Replace the kernel with the MK2000, flashing it with TWRP after Magisk, and the flash will be back.
tremalnaik said:
Replace the kernel with the MK2000, flashing it with TWRP after Magisk, and the flash will be back.
Click to expand...
Click to collapse
There is an Oreo mk2000 kernel? I used it for nougat, I'll give it a look.
thunderc8 said:
There is an Oreo mk2000 kernel? I used it for nougat, I'll give it a look.
Click to expand...
Click to collapse
It's still a beta version, but on my phone is working perfectly.
You can find it here, in the same thread of the Nougat version: h850 mk2000 kernel
I installed the kernel and after magisk again but the flash light is not working again.
I get the same error.
I have to wipe everything again?
Never mind i just flashed mk again without flashing magisk again and its working.
thunderc8 said:
I installed the kernel and after magisk again but the flash light is not working again.
Click to expand...
Click to collapse
I get the same problem.
After flashing TWRP I do this:
don't wipe Data, but "format" data (you have to type "yes" to delete encryption)
intall Magisk-v17.1.zip
install xposed-v90-sdk26-arm64-beta3 (optional)
install driver Adreno 530 rev21 non treble (optional)
install as last zip: KERNEL MK2000 v1.0 Beta5 (for OREO)
reboot system
now flashlight works fine.
So installing "no-verity-opt-encrypt" (DM-verify) is not necessary.
P.S.
I was on Fulmics 5.5 (stock 7.x) with unlocked bootloader, the correct twrp flashing for me was this:
with LGUP
flash kdz android 7.x (flag on refurbish) (I tried upgrading directly to 8.x, but the G5 was gone in bootloop)
flash kdz android 8.x (flag on upgrade)
(the bootloader still remain unlocked, so you have not flash unlock partition with unlock.bin file)
Phase 2
Boot, skip all settings, Enable Developer, enable Debug USB and accept request permissions etc...
open ADB and type
reboot bootloader
fastboot flash recovery twrp.img
don't reboot!
remove cable, remove battery, reinsert battery
power on in recovery mode (correctly, or you have to return at Phase 2)
double yes for reset factory (to enter in recovery)
you should enter in TWRP recovery
Is there any way to fix the "flashlight" bug with the stock kernel, still with the stock recovery
and rooting with Magisk by patching the boot image beforehand and flashing it in fastboot ?
I tried using the mk2000 kernel, but no img image is provided for this, only a zip,
but I don't want to root by using TWRP and flashing zips.
Why, I want systemless root, in case OTA updates will appear.
Thank you.
Even though I'd really suggest you to install TWRP permanently (if you accidentally enter in the stock recovery, the whole internal memory gets erased permanently), you may try to install Magisk from TWRP and then flash again the stock recovery.img using fastboot.
By the way, the Magisk zip is systemless: it doesn't flash executables on the system partition; it's just packed as a zip file for convenience to be easily read by TWRP.
On the other hand, if you want both original kernel and Magisk with a working flashlight, you can't. Flashlight with Magisk only works with MK2000 kernel at the moment.
It's new version mk2000 kernel v2.0 stable version from 04 January 2019, for Oreo try it. I want to unlock BL and make root, pls tell us it is flash work ? Sorry for my English.
Wysłane z mojego LG-H850 przy użyciu Tapatalka
I din't try the latest version, but I'm currently using mk2000 with unlocked bootloader and Magisk, and everything (both root and flash) is ok.
Edit: I now have the latest version of mk2000, and I can confirm everything is ok.
My flashlight and camera flashlight are not working too. I have to back read just in case I am not the only one with the same problem. I see there is a lo of suggestion and I tried it and it worked like a charm. I used H850_v1.0-mk2000 to make it work.
BBCAtomic said:
My flashlight and camera flashlight are not working too. I have to back read just in case I am not the only one with the same problem. I see there is a lo of suggestion and I tried it and it worked like a charm. I used H850_v1.0-mk2000 to make it work.
Click to expand...
Click to collapse
read previous massages
https://forum.xda-developers.com/showpost.php?p=77832747&postcount=6
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
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).