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.
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
atharvvvg said:
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
Click to expand...
Click to collapse
Hello members,
Last week i'v also installed the latest lineageOS version ( 17.1, android 10) Gapps nano, on my Samsung A3 2017. With the TWRP tool., Nice ROM!
Unfortionally with the same issue as above, Samsung and other camera app's very often not working, need to reboot to fix that.
The flashlight does not work either then, and much more irritating BlueTooth not working anymore, my A3 always had perfect connection with my Parrot carkit CK3100.
I'v found in several forum some workarounds for this but these do not solve the issues long enough.
But the issues are also found in older releases from LineageOS.
Will there be a update for these mentioned 3 issues?
If not, i need to install another ROM which is not based on LineageOS.
The Cam and BT must work without any problems.
Thank you very much.
Frank.
Preamble / RamblingHello 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 ProblemWhen 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 / RamblingHello 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 ProblemWhen 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
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