OPO cannot recevive Lineage 13 install (err 7 with TWRP) - ONE Q&A, Help & Troubleshooting

Im currently upgrading my 4.4.4 to a 6.0, to be exact, I use the Kali Nethunter ROM, however I ran into trouble, since it requires a CM 13 as a template. The problem is the following : no matter how many times I've tried, the TWRP just don't want to install the only CM 13 image I could found (which is to be exact a Lineage 13 17-06-10 by kutep0v)
The TWRP-s I've used are ranging from 3.1.2.0 to the last tried and often mentioned 2.8.7.0
The exact model is a bacon with 64GB
And also I use the bacon root toolkit by wugfresh
The two possible cause of this was pointed out in certain other forums said that, there either is a compatibility error with the firmware (which currently displays : UNKNOW, and neither the wifi or sim card is working), or the twrp reads a compatibility error with the image (somehow doesn't gets that A0001 is the same as bacon) I downloaded (there were a forum post about a custom modified twrp, which fixes this error, but the link is broken, and the forum article has been closed in 2015)
Could someone link me the proper firmwares for the Lineage (or CM) 13, and the proper TWRP, which are validated to be working with together?
Or any other thoughts would be helpful

randoomkiller said:
Im currently upgrading my 4.4.4 to a 6.0, to be exact, I use the Kali Nethunter ROM, however I ran into trouble, since it requires a CM 13 as a template. The problem is the following : no matter how many times I've tried, the TWRP just don't want to install the only CM 13 image I could found (which is to be exact a Lineage 13 17-06-10 by kutep0v)
The TWRP-s I've used are ranging from 3.1.2.0 to the last tried and often mentioned 2.8.7.0
The exact model is a bacon with 64GB
And also I use the bacon root toolkit by wugfresh
The two possible cause of this was pointed out in certain other forums said that, there either is a compatibility error with the firmware (which currently displays : UNKNOW, and neither the wifi or sim card is working), or the twrp reads a compatibility error with the image (somehow doesn't gets that A0001 is the same as bacon) I downloaded (there were a forum post about a custom modified twrp, which fixes this error, but the link is broken, and the forum article has been closed in 2015)
Could someone link me the proper firmwares for the Lineage (or CM) 13, and the proper TWRP, which are validated to be working with together?
Or any other thoughts would be helpful
Click to expand...
Click to collapse
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
https://www.androidfilehost.com/?fid=24389512218018449
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
https://dl.twrp.me/bacon/
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.

Mr.Ak said:
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
link
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
link
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.
Click to expand...
Click to collapse
Update I : I just hard bricked it, so I have to rebuilt the whole from scratch (color os and stuff, probably the firmware is wrong too) I had 5.1, but the mobile network somehow didnt worked for me, and I wanted to downgrade to the previously used 4.4, unfortunately not from twrp but just simple flashing, and it somehow did not responded after a certain amount of time. (that won't be a problem)
BUT, I'm sorry to say that, but you are wrong
there are official builds for CM 13 / Marshmallow
they just don't update the main page
look at here : github slash offensive-security slash kali-nethunter slash wiki (sorry, newcomer and I cant post a proper link )in the builds you can find official and nightly packages for it (I can install the kernel, and when I want to install the whole package of marshmallow kali, it says, 'please install a regular Android system first')
that works far better than the Lineage or CM 13, and those are the problematic ones(with the firmware), not the Kali

randoomkiller said:
Update I : I just hard bricked it, so I have to rebuilt the whole from scratch (color os and stuff, probably the firmware is wrong too) I had 5.1, but the mobile network somehow didnt worked for me, and I wanted to downgrade to the previously used 4.4, unfortunately not from twrp but just simple flashing, and it somehow did not responded after a certain amount of time. (that won't be a problem)
BUT, I'm sorry to say that, but you are wrong
there are official builds for CM 13 / Marshmallow
they just don't update the main page
look at here : github slash offensive-security slash kali-nethunter slash wiki (sorry, newcomer and I cant post a proper link )in the builds you can find official and nightly packages for it (I can install the kernel, and when I want to install the whole package of marshmallow kali, it says, 'please install a regular Android system first')
that works far better than the Lineage or CM 13, and those are the problematic ones(with the firmware), not the Kali
Click to expand...
Click to collapse
Good...

Mr.Ak said:
Good...
Click to expand...
Click to collapse
Okay, so since (at least in my opinion) the bottleneck is the CM 13 / Lineage 13, do you have any experience with it?
could you give me a fine working firmware and ROM combo please?
I'll have no problem unbricking it, and after that I'll probably solve the kali installation (since its documented, and seems like working), but due broken links I can't really get the recommended ones at github

Mr.Ak said:
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
https://www.androidfilehost.com/?fid=24389512218018449
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
https://dl.twrp.me/bacon/
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.
Click to expand...
Click to collapse
randoomkiller said:
Okay, so since (at least in my opinion) the bottleneck is the CM 13 / Lineage 13, do you have any experience with it?
could you give me a fine working firmware and ROM combo please?
I'll have no problem unbricking it, and after that I'll probably solve the kali installation (since its documented, and seems like working), but due broken links I can't really get the recommended ones at github
Click to expand...
Click to collapse
This...

Oh, thank you.
I just didn't realised, sorry for that.
BTW do you have any idea why does my opo is undetectable for everything I've tried?
How I hard bricked was the following :
Bacon toolkit, Downgrading to Kitkat
the console was writing the stuff it flashed to the device, and suddenly stopped and said <waiting for device>
after that, nothing
I unplugged after 15 mins, and after that the only lifesign was that, it got how when I plugged it charging (not too hot, just the standard "oneplus one is charging" hot)
I have an xp machine with the proper drivers and the rescue toolkit, but it cannot detect, not even as an unrecognizable usb device which lacks driver
I think the bottleneck is the phone now, but I just don't know what should I do

randoomkiller said:
Oh, thank you.
I just didn't realised, sorry for that.
BTW do you have any idea why does my opo is undetectable for everything I've tried?
How I hard bricked was the following :
Bacon toolkit, Downgrading to Kitkat
the console was writing the stuff it flashed to the device, and suddenly stopped and said <waiting for device>
after that, nothing
I unplugged after 15 mins, and after that the only lifesign was that, it got how when I plugged it charging (not too hot, just the standard "oneplus one is charging" hot)
I have an xp machine with the proper drivers and the rescue toolkit, but it cannot detect, not even as an unrecognizable usb device which lacks driver
I think the bottleneck is the phone now, but I just don't know what should I do
Click to expand...
Click to collapse
Fastboot drivers are not installed correctly...try uninstalling and installing again.

Mr.Ak said:
Fastboot drivers are not installed correctly...try uninstalling and installing again.
Click to expand...
Click to collapse
That could be possible, however I've tried with at least 3 drivers on 2 laptops(Win10 and an old XP), and neither picked it up even as an unrecognisable device (So basically there is literally no difference wheter I plug in or not plug in, from the computers view, or at least I didn't find it at the device manager, neither was there an alert of a device not recognisable). The drivers were :
- QUD.WIN.1.1 10037.3 - Latest from androidbrick
- Driver from colorOS
- The one I've been using before bricking it (and I had no problem with it before)
I've been digging up threads, and the only one I could find so far, where the device wasnt recognised even as an unrecognisable device was due a discharged battery.

randoomkiller said:
That could be possible, however I've tried with at least 3 drivers on 2 laptops(Win10 and an old XP), and neither picked it up even as an unrecognisable device (So basically there is literally no difference wheter I plug in or not plug in, from the computers view, or at least I didn't find it at the device manager, neither was there an alert of a device not recognisable). The drivers were :
- QUD.WIN.1.1 10037.3 - Latest from androidbrick
- Driver from colorOS
- The one I've been using before bricking it (and I had no problem with it before)
I've been digging up threads, and the only one I could find so far, where the device wasnt recognised even as an unrecognisable device was due a discharged battery.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2588979
Try this.

Update :
a friend of mine had an OPO to sell for ~100 USD, so to have a working phone, I bought that
it had Lineage 14.1, with firmware 0241, and TWRP, BUT, when I've tried to install the lineage 13, it said the same error 7
I've updated its firmware to 0011, and same thing happened, error 7 when I've tried to install lineage 13
now its on a factory reset lineage 14.1
maybe my image is bad
any idea where could I find the CM 13 or lineage 13?
and also I've tried the old phone with the adb drivers you've suggested, but no update with that one

randoomkiller said:
Update :
a friend of mine had an OPO to sell for ~100 USD, so to have a working phone, I bought that
it had Lineage 14.1, with firmware 0241, and TWRP, BUT, when I've tried to install the lineage 13, it said the same error 7
I've updated its firmware to 0011, and same thing happened, error 7 when I've tried to install lineage 13
now its on a factory reset lineage 14.1
maybe my image is bad
any idea where could I find the CM 13 or lineage 13?
and also I've tried the old phone with the adb drivers you've suggested, but no update with that one
Click to expand...
Click to collapse
https://www.google.co.in/amp/s/foru.../rom-lineageos-13-0-oneplus-one-t3549203/amp/

Oh, then the problem is not with that
I've used the exact same
what do you thing, what would cause the error 7? how can I overcome with the problem, and finally install cm13? ( or at least some diagnostical features I should check to find the problem )
and do you have any idea what could I do with the bricked one?

randoomkiller said:
Oh, then the problem is not with that
I've used the exact same
what do you thing, what would cause the error 7? how can I overcome with the problem, and finally install cm13? ( or at least some diagnostical features I should check to find the problem )
and do you have any idea what could I do with the bricked one?
Click to expand...
Click to collapse
It's probably a bad download,redownload the zip.
About the bricked one,you have to figure out the fastboot drivers issue.

Related

[Completed] Samsung A3 (SM-A300FU) Cyanogenmod 13 not working but 12.1

I have been running Cryogenmod 12.1 for my Samsung SM-A300FU but its UNOFFICIAL and a preview the webpage i got it off says 'Wifi and Camera NOT WORKING'. I guess thats what i get for following my mates advice.
Because of this, i looked at CM13 (Android 6) which i got off the XDA site and i have made sure it is for my phone and model, the SM-A300FU. Of course, being my luck it didnt work. I get the error of 'Executing updater binary in zip' and i have wiped my phone then tried to install it and i have also tried to completly remove all OS and files then install it which apparently fixed it for people, but not me of course. In a desperate measure i even bluetoothed the ROM to another phone then back into my SM-A300FU to get it onto the internal storage but that obviously didnt change anything.
Finally, i gave up and tried to downgrade back to Android 5.0.2 although this isnt a CM zip. Once again, this ROM doesnt work. It just gives me an error saying it failed, no reason in particular.
I have a few issues for a whole range of files. Any help in fixing any or all of these would be much appreciated.
Links to the files I sites i downloaded the files from:
CM 12.1 UNOFFICIAL (Not meant to work fully) - https://forum.xda-developers.com/samsung-a-series/orig-development/rom-cyanogenmod-12-1-samsung-galaxy-a3-t3273323
CM 13 (Doesnt install) - https://forum.xda-developers.com/samsung-a-series/orig-development/rom-cyanogenmod-13-0-unofficial-samsung-t3326297
Android 5.0.2 ROM (Doesnt install) - http://www.youmobile.org/blogs/entry/-Firmware-Download-Samsung-Galaxy-A3-SM-A300FU-Official-Android-5-0-2-Lollipop-update-Rolling-out
So to reitterate: I installed the CM 12.1 ROM without issues but it turns out to be a mod that doesnt work fully meaning its unsuitable for me. I downloaded CM 13 but this gets an error. I downloaded a Android 5.0.2 ROM which has an error it doesnt even tell me about.
XDA Visitor said:
I have been running Cryogenmod 12.1 for my Samsung SM-A300FU but its UNOFFICIAL and a preview the webpage i got it off says 'Wifi and Camera NOT WORKING'. I guess thats what i get for following my mates advice.
Because of this, i looked at CM13 (Android 6) which i got off the XDA site and i have made sure it is for my phone and model, the SM-A300FU. Of course, being my luck it didnt work. I get the error of 'Executing updater binary in zip' and i have wiped my phone then tried to install it and i have also tried to completly remove all OS and files then install it which apparently fixed it for people, but not me of course. In a desperate measure i even bluetoothed the ROM to another phone then back into my SM-A300FU to get it onto the internal storage but that obviously didnt change anything.
Finally, i gave up and tried to downgrade back to Android 5.0.2 although this isnt a CM zip. Once again, this ROM doesnt work. It just gives me an error saying it failed, no reason in particular.
I have a few issues for a whole range of files. Any help in fixing any or all of these would be much appreciated.
Links to the files I sites i downloaded the files from:
CM 12.1 UNOFFICIAL (Not meant to work fully) - https://forum.xda-developers.com/sa...m-cyanogenmod-12-1-samsung-galaxy-a3-t3273323
CM 13 (Doesnt install) - https://forum.xda-developers.com/sa...-cyanogenmod-13-0-unofficial-samsung-t3326297
Android 5.0.2 ROM (Doesnt install) - http://www.youmobile.org/blogs/entr...ial-Android-5-0-2-Lollipop-update-Rolling-out
So to reitterate: I installed the CM 12.1 ROM without issues but it turns out to be a mod that doesnt work fully meaning its unsuitable for me. I downloaded CM 13 but this gets an error. I downloaded a Android 5.0.2 ROM which has an error it doesnt even tell me about.
Click to expand...
Click to collapse
Greetings and welcome to assist. Which recovery are you using ? Have you tried to update to the latest ? Also if that doesn't work try using odin to go back to latest stock then reflashing custom recovery
Why not make an account and let the experts here
https://forum.xda-developers.com/samsung-a-series
guide you
Good Luck
Sawdoctor

Lineage OS 14.1 Release 1 (uploaded January 17 1025pm eastern)

Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631
wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.
Awesome work! I've finally got me a full featured daily driver
I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...
After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.
Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk
I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..
This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.
I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.
Any update?
pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.
won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.
Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.

[Solved] WiFi not working after updating to LOS 18.1 and rooting it

Preamble / Rambling​Hello dear xda-community,
I am a little desperate right now. After hours of searching for solutions I am sadly out of luck and afraid I might destroy the system if I try to solve this issue any further by my own. :/
By no means I am an expert in flashing / rooting mobile devices, so please forgive me if I did something stupid.
But with that out of the way I hope you can help me. Thank you already for your efforts.
Have a great day,
TheAverageUser
The Problem​When trying to connect to a WiFi the connection disrupts and apparently the entire network management component (?) crashes and restarts.
I suspect it of crashing because the connection to the internet via my SIM card is disconnected as well for a short period of time after the WiFi tries to connect to a base station.
How I got here​
Upgraded from LOS 17.1 to 18.1 like so
Installed TWRP as described here
Installed Magisk as described in the "Custom Recovery" section of this guide
Additional Information​
After upgrading to LOS 18.1 I noticed that Magisk did not work anymore, so I tried to find a way to re-root my device.
A long search later I decided that I needed TWRP in order to root the device as many guides I found required this to be the case. Sadly I can't remember how I rooted the device the first time.
The mentioned method for installing Magisk seemed to be the only one working for me. (I did not find anything better.)
I would love to fix my current OS without having to start over, because setting it up again is very tedious.
Previous Setup (Before Upgrade)​
OnePlus 6 (obviously ^^)
Lineage OS 17.1
Magisk
Lineage Recovery
Updates:​
#1 Okay. Now I am even more confused. The phone just connected to my WiFi and it seems to work. I didn't do anything as of yet. I am going to investigate further to find out when exactly the connections fail. Honestly I don't like a 50:50 chance of it working ^^ (Just to be clear. My problem is not fixed as of yet.)
#2 For some reason the WiFi is now working. The only thing that I can think of which might have solve the issue is that I have uninstalled and reinstalled the "F-Droid Privilgeded Extension" for Magisk.
TheAverageUser said:
Preamble / Rambling​Hello dear xda-community,
I am a little desperate right now. After hours of searching for solutions I am sadly out of luck and afraid I might destroy the system if I try to solve this issue any further by my own. :/
By no means I am an expert in flashing / rooting mobile devices, so please forgive me if I did something stupid.
But with that out of the way I hope you can help me. Thank you already for your efforts.
Have a great day,
TheAverageUser
The Problem​When trying to connect to a WiFi the connection disrupts and apparently the entire network management component (?) crashes and restarts.
I suspect it of crashing because the connection to the internet via my SIM card is disconnected as well for a short period of time after the WiFi tries to connect to a base station.
How I got here​
Upgraded from LOS 17.1 to 18.1 like so
Installed TWRP as described here
Installed Magisk as described in the "Custom Recovery" section of this guide
Additional Information​
After upgrading to LOS 18.1 I noticed that Magisk did not work anymore, so I tried to find a way to re-root my device.
A long search later I decided that I needed TWRP in order to root the device as many guides I found required this to be the case. Sadly I can't remember how I rooted the device the first time.
The mentioned method for installing Magisk seemed to be the only one working for me. (I did not find anything better.)
I would love to fix my current OS without having to start over, because setting it up again is very tedious.
Previous Setup (Before Upgrade)​
OnePlus 6 (obviously ^^)
Lineage OS 17.1
Magisk
Lineage Recovery
Updates:​
#1 Okay. Now I am even more confused. The phone just connected to my WiFi and it seems to work. I didn't do anything as of yet. I am going to investigate further to find out when exactly the connections fail. Honestly I don't like a 50:50 chance of it working ^^ (Just to be clear. My problem is not fixed as of yet.)
Click to expand...
Click to collapse
Is it not because of your base OOS version?
Just do this and you are 100% okay.
1. Use MSM Tool here (it is like a full factory reset with a clean install - you have to unlock your bootloader again!!!)
2. Download latest OOS Full Update here, latest TWRP here, NikGapps here (Magisk if you like) and copy them into Device
3. Flash OOS, TWRP & Reboot to Recovery
4. Flash OOS, TWRP & Reboot to Recovery
5. Flash LOS-ROM, TWRP & Reboot to Recovery
6. Flash NikGapps (and Magisk) & get back to Menu
7. Select Wipe and just swipe to wipe data
8. Reboot to system
9. Done
Hello @tiga016 and @Pundy,
so here is an update on my situation:
For some reason the WiFi is now working. The only thing that I can think of which might have solve the issue is that I have uninstalled and reinstalled the "F-Droid Privilgeded Extension" for Magisk.
@Pundy
Thank you very much for this guide. For now I will continue to use my device in its current state, but as soon as I try to do a major update I will come back to your guide in order to install everything in a clean manner.
@tiga016
Thank you for your interest in my issue. For now I will consider this problem to be solved.
Pundy said:
Just do this and you are 100% okay.
1. Use MSM Tool here (it is like a full factory reset with a clean install - you have to unlock your bootloader again!!!)
2. Download latest OOS Full Update here, latest TWRP here, NikGapps here (Magisk if you like) and copy them into Device
3. Flash OOS, TWRP & Reboot to Recovery
4. Flash OOS, TWRP & Reboot to Recovery
5. Flash LOS-ROM, TWRP & Reboot to Recovery
6. Flash NikGapps (and Magisk) & get back to Menu
7. Select Wipe and just swipe to wipe data
8. Reboot to system
9. Done
Click to expand...
Click to collapse
Hello Pundy,
I have updated from LOS 17.1 to 18.1 (clean install) sadly wifi was not working with 17.1 and also not with 18.1. Therefore I have installed OOS (without TWRP) one of the latest version and made an update via wifi to the current version. So wifi is ok. Following the LOS howto, I was successful in installing the latest LOS BUT again wifi is not working...
Sadly also using the MSM Tool is not working. The MSM Tool does not connect with the OP6 (Sahara problem). I have tried it many times...
Any alternative?
BR Martin

Ressurection Remix on A8

Hello everyone,
I am creating this post because I would like to know if someone has already installed Ressurection Remix on a Galaxy A8 ?
I saw some tutorials that are explaining this is possible,but when I go to the Ressurection Remix official download page, I cannot find which file is specific to the galaxy A8. Actually, I have some difficulties to understand the files names : Raphael, Sakura, Jason,... Are theses names code names for différents phones ?
I may add that the bootloader of my phone is unlocked, and I am using TWRP to flash zip files.
I didn't treblelize my phone thought.
If you have some other custom rom suggestions, please do not hesitate to advise me.
You can install RR through GSI, by this link
You will have to trebelize your device
Because it's a gsi android 10, you can use vendor quack
Treble Guide
Vendor Quack
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Quentief said:
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Click to expand...
Click to collapse
Treblizing the phone itself does not cause any problem rather it enables you to install different GSIs. Regarding GSIs, each have there own bugs and you have to find them on the GSI thread if available or if they have telegram or github support.
Hey, just made an account to respond to this as I just discovered there are per-device pages on these forums and saw this post, I have done exactly that and been running it for 2+ years now, so far I have had no majour problems wih it, the only majour caviat is that after trebblimg it and installing resurrection remix It seems to freeze when trying to display the charging animation if the phone is off and it plugged in, it still charges without any problems, tho to boot it when in this situation you need to force shut it down using the volume_down + lock buttons and then immidiately after use volume_up + lock buttons to boot into recovery, then you can boot to the normal system from there, I have a TWRP recovery but I think the stock one also allows to resume booting the normal system.
In these last months I had a few weird bugs like the screen brightness beeing locked to automatic but that went away after a reboot and only happened 1 time.
I also installed magisk and a few other small tweaks and things and everything works great, also all resurrection remix customization options.
Actually in the last few months something broke because the safetynet checks fail for the ctsProfile, (most apps like my banking app tho still work fine by using magisk hide (i think it's because the safetynet basicIntegrity check still succeds) and the update page seems also broken (tho no idea about when this broke exactly as I haven't checked it in years), everything else is still fine tho, I might try re-flashing it to update to the new majour resurrection remix when i have time and the will to backup and move everything, something could have corrupted or maybe an update broke it, no idea.
My phone reports resurrection remix 7.0.2 and Android 9.
Hope this is still helpful.
Quentief said:
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Click to expand...
Click to collapse

Help with nexus 7 (2012) rom

Hi. for 2 days I have been googling and looking on this forum on which rom is best for nexus 2012, but I can't find anything at all. most posts are for 2013 version or outdated with dead links.
I was able to get lineage 14.1 on it, but it was missing google play, after following some guide here and installing Gapps, it then stopped booting. it got stuck on the google logo and that's it. lineage 14.1 itself worked fine, installation of gapps succeeded, but simply won't boot. tried several times. always gets stuck on google logo (waited over 15 minutes).
before that i had some kali version on it, but out of the blue it stopped working and wouldn't boot anymore, that's where i deciced to try lineage. i dont want kali on it anymore as it was sluggish to start with.
so I thought I'll just put original rom on it and was looking for original 2012 rom download, but it seems like it comes in pieces like system.img boot.img ..etc and I don't want to overwrite my bootloader or lock the device again or cause other issues. I just want a working rom that can be sideloaded.
can someone please point out which rom is actually working with nexus 7 2012 and can be flashed using sideload or twrp loader.
I already have everything working, such as twrp, fastboot ..etc. I can easily sideload any working zip or img, but I simply can't find a working one.
I find only dead links on this forum and elsewhere, such as this one "xxxxxx" which is suppose to be for some nightly version. and some dead gapps links that point to dead domains or link just doesn't even exist.
please dont start suggesting to buy new tablet. i'm poor and i have no money and i only need this tablet to use with my smart plugs and camera. i'm not going to buy new tablet just for that. i just want to keep it on charger 24/7 so i can monitor my plugs and camera. that's all.
but for that i need working android rom and google play store so i can download and update apps.
I don't have any backups nor important data on it, however i want to keep it unlocked and keep the twrp.
any help would be appreciated. thanks.
Mod Edit: Link removed
so your question is about gapps?
aIecxs said:
so your question is about gapps?
Click to expand...
Click to collapse
uhh, no..
I quote:
mordaxify said:
can someone please point out which rom is actually working with nexus 7 2012 and can be flashed using sideload or twrp loader.
Click to expand...
Click to collapse
lineage 14.1 itself worked fine, or not?
aIecxs said:
lineage 14.1 itself worked fine, or not?
Click to expand...
Click to collapse
it was bit sluggish and got stuck couple times during boot, but it worked.
I think better question to ask is: does any of the ROMs comes with gapps?
It was like 5-6 years ago so i don't remember much, but i installed some version of kali on it and it had everything included (play store and other stuff). however as i mentioned before, for some reason it got really, really sluggish and at some point it just stopped booting completely.
so your question is about gapps. ROMs always should provided without google apps for licence violation.
use older installer. check recovery.log

Categories

Resources