Database Users

Cant figure out how to install custom rom, without loosing root acces

Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: ​SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati

Nepoznati said:
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: ​SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Click to expand...
Click to collapse
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).

antique_sonic said:
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
Click to expand...
Click to collapse
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?

Nepoznati said:
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Click to expand...
Click to collapse
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.

SOLVED
antique_sonic said:
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
Click to expand...
Click to collapse
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!

Nepoznati said:
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Click to expand...
Click to collapse
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.

antique_sonic said:
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
Click to expand...
Click to collapse
It could probably be a problem with TWRP as you mentioned earlier. After using CWM everything went smooth after updating my kernel. Last night I couldnt hold me back to try one more time, and I flashed X-NOTE with TWRP and I got the same problem as described in #1 post. Then I installed CWM and flashed X-NOTE again and everything got messed up. Then I restored everything, force installed the kernel and bootlaoder. After that installed CWM and then I was able to run X-NOTE without any problem.
I am not a professional developer but I may think that the problem is TWRP when it tries to flash the kernel under the process with may results in some problems. When using CWM from the beginning I do not get any problems but when using TWRP I need to restore everything back.

[Q] Gapps does not install while flashing with cm12.1 - Nexus 4

Hey guys,
Recently I flashed
ClockWorkMod recovery - v 6.0.1.9
Cyanogenmod 12.1 nightly -cm-12.1-20150706-NIGHTLY-mako.zip
It all worked out (with great difficulty) and the phone works fine.
However, I have no google apps. Coming from stock factory setting to a rom with no google apps is quite difficult.
So, i tried flashing the gapps along with the rom but i keep getting a status 7 error message and the installation gets aborted, the result being when i reboot my phone i get a plethora or error messages of all the google apps which stop working (i.e none of the gapps work).
I have tried flashing the following (file names) gapp zip files with no luck.
gapps-5.1-2015-06-02-15-21
gapps-5.1-2015-07-03-13-41
gapps-L-4-21-15
gapps-lp-20150211-signed
BaNkS-dynamic-gapps-L-6-21-15
pa_gapps-modular-mini-5.1-20150315-signed
Even the gapps link on the cyanogenmod wiki page does not work. ( i think i included that filename in the above list)
On reading other forums, members say that the recovery must be updated.
Quite honestly i am quite apprehensive to do anything to the recovery as i got stuck into a bootloop once and it took me a day to get out of it.
P.S i am a complete amatuer in this process, this is the first custom rom i flashed after staying on stock factory images for 2 years.
I really do need help, as no other rom works well except the cm 12.1 and itwould be absoutely brilliant if i have the google apps too!
Thanks in advance.

solution found
Hey there, I have the s4 (GT-i9505)
I had the same problem until today and I have found the solution to it,
I updated my cm12.1 nightly to 20150706,
Downloaded slim gapps 5.1.x mini latest (20150706), [I searched for it on Google]
Tried flashing the cm and then the gapps but it didn't work, and gave me all the errors of apps that have stopped which was very annoying.
So then I did a little research and figured out that I was using twrp v2.6.0.0 which was quite old , so I never gapps after the root. So then I updated it to the latest version by connecting my phone to the PC in download mode and downloaded the twrp v.2.8.0 (latest) and recovery booted my phone.
Factory reseted my phone, installed both the cm12.1 and gapps by selecting the zip files and then flashing them. Wiped the dalvik cache. Finally rebooted my phone.
And to my surprise it actually worked. Thank god that now I have the play store and all the other apps without any annoying popups.
I'm on my phone so I can't seem to be able to upload any links .
I'm sorry you gotta have to search on Google for the download links.
Have fun buddy. Hope it works on your nexus 4. Enjoy !!

Got it working!!
So, followed some forums ( including mehsan23) and updated my custom recovery. The most surprising thing is that you can do this by downloading zip files of the latest cmw recovery and flash them on to your existing recovery and the recovery automatically updates.
Then flashed the gapps on cm12.1 wiki page and it worked! So relieved! However the Google app crashes but its alright I can do without it.
Thanks guys!!
P.s thanks again mehsan23

Bootloop after first restart with multiple CFWs!

Hi guys,
I have the standard note III 9005 and I had always installed CFWs on it.
I wanted to update to newer 6.0.1 Roms (had 6 roms before) but I seem to have a VERY annoying bug:
I tried to install Temaseks rom and resurrection rom but I had huge issues with it. I got bootloops although I got the newest 3.0.2.0 Team Win Recovery Project
I installed rom, GAPPS (correct version of course 6.0.1) , install rom again then delete cache and then it worked on both roms.
So a simple "install rom, GAPPS, then clean cache" didnt work. I tried to install multiple times until I got the installation! YAY! BUUUT!
Here is the fun part:
If I restarted the phone acidentally or on purpose I got stuck in a bootloop. After that the phone was unuseable again so the installation was useless.
Only solution is to completely wipe and reinstall and experiment with the order of installation until it works!
I did install STOCK rom because I was so freaked out and then went with ODIN the complete rooting guide for clean rooting, but still problem exists.
I tried two other roms but the problem was that while flashing the phone restarted automaticly and then TWRP said no installed rom? ???
Huge thanks for helping me!

New info:
I was able to make the rom work. I restarted and got stuck into bootloop!
I could boot normally after deleting dalvik cache!
But after rebooting I got into bootloop. Tried deleting cache again but this time it never booted properly.
How can I avoid by always deleting dalvik whenever I have to restart my phone (if battery dies or purpose)?
PPS: Stock Rom flash works flavlessly. I am waiting in stock rom until I find a proper solution :"(

Suggest you read the roms faqs and Q&A particularly with regard to TWRP .

G900F Bricked after update: cm-14.1-20161219-NIGHTLY-klte.zip

Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.

I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you

LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!

Cant install LineageOS 14.1 on G2 D802 (TWRP deletes root)

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