Related
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Quicka said:
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Click to expand...
Click to collapse
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Jan Philipp said:
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Click to expand...
Click to collapse
i have done it... but after i wiped data,... etc. flashed lineage os and gapps and reboot system, phone screen gets black... and i can only go to download mode to flash again stock rom ive tried it about 5 times
Problem fixed
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Quicka said:
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Click to expand...
Click to collapse
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
djsasha78 said:
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
Click to expand...
Click to collapse
just held the volume up button and then connected with pc. then using lg flash tool to flash lollipop stock rom
1. Root + TWRP : https://www.dropbox.com/s/2shvozzbu29xjfu/LGG2-D802-OneClickRootRecoveryV1.1.zip?dl=0
2. Update TWRP to 3.1 by flashing zip file and then rebooting recovery: http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.1.0-1
3. LineageOS by flashing rom zip file and gapps: https://download.lineageos.org/d802 + http://opengapps.org/ (ARM + Android 7.1)
easiest method to flash lineageOS on LG G2 https://www.youtube.com/watch?v=BoPjGM0nrak (Video tutorial)
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
JackSparreau said:
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
Click to expand...
Click to collapse
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
cropsroth said:
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
Click to expand...
Click to collapse
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
JackSparreau said:
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
Click to expand...
Click to collapse
Yes, you don't wipe after flash, but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. Check MD5 of the all files you downloaded with original MD5 to confirm the file didn't get corrupt.
Boot stack flash not needed. Please read the first post thoroughly in lineage thread
"""
Requirements:
Custom recovery (TWRP or any other)
KitKat (KK) bootloader (included in the lg-devs LP bootstack)
KitKat (KK) bootstack minimum; Please read the entire FAQ for important bootstack information. Installation of bootstacks is NOT recommended.
Clean flash if coming from another ROM or CM 13 (no dirty flash, wipe system too check you bootstack(needen bump support)
"""
crophs said:
... but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. ...
Click to expand...
Click to collapse
Hi,
what do you mean by "you swipe the factory reset", I'm not sure what it is, either "give it a clean shot again".
Sorry I'm not very aware of all those processes ^_^, and I'm french so not very aware of some vocabulary words
Thank you
Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state
I have a systemless-rooted SM950FD model with AQDG firmware/baseband, with TWRP.
Before anything took place I backed up with TWRP 3.1.0 the essentials: boot, recovery, system, data, baseband & efs.
Wanting to update to the latest AQH3 firmware without losing any data, I used the 'TWRP-flashable' firmware provided by Renovate here http://www.renovate-themes.de/firmware.html
This zip claims to update bootloader, modem and TWRP.
The update seemed to go well, but when I rebooted I the phone was stuck on Galaxy S8 logo. TWRP disappeared, as did any other recovery, so I had to flash TWRP from ODIN (at which point I updated to latest TWRP version, 3.1.1-2)
Now back on TWRP, I am trying to restore a bootable system from my backup, but no combination has worked for me so far. I always do a quasi-full wipe (system, caches, data) and restore boot/system/data/baseband/efs (with minor variations between the 5). So far nothing has succeeded in booting the phone, it always gets stuck at the Galaxy S8 screen.
At this point I could totally install a stock-like rom which will fast-forward me to the latest version, but since my goal was to keep my original stock rom without losing sms/apps, I would at least need to boot up once in my original backed up state.
Any ideas?
Thank you very much,
Batman Rom Is very close to stock.
I would say flash that one. In fact it's better than stock.
Sent from my SM-G950F using Tapatalk
SM-G950F FLASHED WITH TWRP WITHOUT OEM UNLOCK
Hi guys I need your professional opinion the stupidity I done. I Flashed cf-auto root and without to enable OEM unlock i Flashed TWRP. After reboot the phone stuck on the Samsung logo.
Is the phone dead? Any chance to recover ?
Thanks for ur time
erclalle said:
I have a systemless-rooted SM950FD model with AQDG firmware/baseband, with TWRP.
Before anything took place I backed up with TWRP 3.1.0 the essentials: boot, recovery, system, data, baseband & efs.
Wanting to update to the latest AQH3 firmware without losing any data, I used the 'TWRP-flashable' firmware provided by Renovate here http://www.renovate-themes.de/firmware.html
This zip claims to update bootloader, modem and TWRP.
The update seemed to go well, but when I rebooted I the phone was stuck on Galaxy S8 logo. TWRP disappeared, as did any other recovery, so I had to flash TWRP from ODIN (at which point I updated to latest TWRP version, 3.1.1-2)
Now back on TWRP, I am trying to restore a bootable system from my backup, but no combination has worked for me so far. I always do a quasi-full wipe (system, caches, data) and restore boot/system/data/baseband/efs (with minor variations between the 5). So far nothing has succeeded in booting the phone, it always gets stuck at the Galaxy S8 screen.
At this point I could totally install a stock-like rom which will fast-forward me to the latest version, but since my goal was to keep my original stock rom without losing sms/apps, I would at least need to boot up once in my original backed up state.
Any ideas?
Thank you very much,
Click to expand...
Click to collapse
try flashing stock AQH3 then booting then flashing TWRP again.
mweinbach said:
try flashing stock AQH3 then booting then flashing TWRP again.
Click to expand...
Click to collapse
Thank you, I ended up flashing a custom ROM, unfortunately I did not have time to do this intermediary step, but thank you!
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.
Hello everyone, I'm trying to flash Havoc os 3.0 alongside with BitGaps, but it always ends up in a bootloop (I always wait one hour in the "android" boot screen). My device is the A205G with Android 10. I successfully flashed TWRP using the guide posted here in xda (also flashed magisk), then I flashed Havoc and BitGaps (wiping dalvik, cache, data and system first and then doing a factory reset), but ended up in a bootloop after rebooting to system. In a second try after reinstalling Android 10 stock rom I followed the steps shown in a youtube video (can't post link since I'm a new user) with no luck (still getting a bootloop). In a third try I just flashed the stock rom, then flashed twrp with odin and tried to flash Havoc without flashing Magisk at any moment, still bootloop. Any ideas or suggestions on what could be wrong? I've only flashed one device before with a custom rom so I'm not an expert in this area, any help will be appreciated.
Downgrade phone to Android 9, later flash twrp, then install system and Gapps.
GamingMichu said:
Downgrade phone to Android 9, later flash twrp, then install system and Gapps.
Click to expand...
Click to collapse
Thank you so much! Worked perfectly.
No problem bro. If you have problems, write to me, I will try to help.