Develop Bugs

[HOWTO]Endless Bootloop FIX (no wipe)

Hi I got a solution to endless bootloops (at least working for me ) every time I flash new ROM I got stuck with bootloops so I experimented little bit and this solution seems to be working ...
I am using CM10 with Semaphore JB
You will need fixrecovery.tar and Odin (I used v1.83) you can download them in attachments.
For those who don't have flashable kernel on Internal SDCard can skip step 5 and second half of step 3.
1. So first of all you have to remove SIM and SDCard.
2. Flash fixrecovery.tar with Odin and uncheck Auto Reboot
3. Get into recovery and wipe only cache and flash kernel you want
4. Flash normal kernel with Odin and again uncheck Auto Reboot
5. Get into recovery and again flash kernel of your choice
6. Now you should be ready to switch your phone on
Maybe this excessive flashing of kernel is not necessary but I did it this way

Did you make this fix by yourself? There is already a fix for bootloop from stratosk!

Yes I did... can you post stratosk's fix please ?

Syntaxer said:
Yes I did... can you post stratosk's fix please ?
Click to expand...
Click to collapse
sorry, my mistake, it's probably made by someone else. Search the thread.
Anyway, thanks for the fix...

No problem I hope someone will find this fix useful

Syntaxer said:
Yes I did... can you post stratosk's fix please ?
Click to expand...
Click to collapse
sure you did ... [Q] Cannot boot or enter recovery (CM9 20120425)

Didn't see that post earlier, but it's not working for me anyway ... I had to clear cache additionally

Thats big development time... Clear cache ftw!
Sent from my XT910 using xda premium

Hello there,
Thanks for the guide. This hasn't worked for me?
I was upgrading versions of aways ROM (from ICS to Jellybean) and once I had flashed the ROM and GAPPS the phone rebooted. The link for the GAPPS was broken on the ROM website but it found me a replacement that I used. The phone does boot but FC on setup and no longer boots into recovery and is stuck in bootloop.
I thought this would fix the issue as I could still enter download mode but I still have the same problem? Phone won't boot into recovery and just loops...
Any thoughts?
Thanks in advance : )

I have a device that is experiencing bootloop just stop at the logo, I think this is the kind of Mtk, rooted, Kitkat. I do not know exactly what causes it bootloop, Before bootloop I edit files and install Tweaks build.prop through the application My pimp and when I restart the device bootloop ensued, do you think this is file damage build.prop or else. So that my device bootloop

Note 4 Marshmellow root not working!

So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.

imsuckk said:
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
Click to expand...
Click to collapse
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!

aaron74 said:
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
Click to expand...
Click to collapse
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.

imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.

aaron74 said:
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
Click to expand...
Click to collapse
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.

imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Oh. That explains it. TWRP ISN'T installed. Let me explain.
1 Download Twrp here.
2 Odin Twrp to phone. Make sure to uncheck auto reboot in odin first. After odin completes it'll say something like all operations done. Just make sure odin is done. It don't take long. Then you have to unplug usb from phone and pull out battery for 10 sec. Put battery back in and hold Vol up + Home + Power button until Twrp boots.
3 now twrp is installed and you can install root.
Also backup your phone.
Sorry I'm busy right now and can't post a good post with pics. If that all makes sense then you should be good to go. If you don't understand what I mean I can message you later with some screenshots

imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
tar.img is what you should flash in Odin for TWRP. If you are already on TWRP recovery, you can use the .img file to update within TWRP. TWRP makes both these files in flash form; one for Odin flash, the other for TWRP recovery flash. No need to convert. See link below for the Odin flashable TWRP.
Your kernel must already be patched or custom. (Possibly the reason it can't be patched).
When you boot your ROM, check your kernel and bootloader using Galaxy Tools or PhoneInfo for Samsung. If they don't match your last known update, it's possible you've not successfully updated because your reactivation lock is enabled and you didn't notice you failed to update. Nonetheless, check your reactivation lock by going into Settings/Security and uncheck the option.
If failures persist, flash the stock tar in Odin and make sure it flashes.
For the record, latest update for CF AutoRoot for Note 4 does in fact work. But note, you should flash that in Odin over full stock only. Don't try to flash it if you already flashed TWRP. It's intended to back up stock recovery and stock kernel to restore if you full un-root within the SuperSU application. It's been reportedly to be an unknown or dysfunctional but I can confirm it worked for me back on PB5 leaked MM tar. I used the latest update for CF AutoRoot for Note 4 then. Can't imagine anything broke since then but when I realized it was just systemless root, I lost interest. But hey, it has its purpose for those not interested in TWRP recovery and want yo test if OTA is possible with the limited modification. I've yet to test the theory that it may allow OTA update if system ro partition is left untouched. I like sound mods too much to leave system fully stock.
I can recommend an easier way though (if uninterested in systemless root): you don't have to pre-root if flashing a custom ROM. Once you determine your issue or just Odin flash and confirm the stock PE2 tar. Flash the TWRP tar.img file and then factory reset and flash Freeza's Note 4our beta 3.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
https://androidfilehost.com/?fid=24591023225176402
Note: Thank freeza if the clean flash suggested goes as expected. His thread is in the development forum for Sprint Note 4.
Sent from my SM-N910P using Tapatalk

imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
aaron74 said:
AmmO0702 said:
looking for the best way to root my sprint note 4. can you help me
Click to expand...
Click to collapse
First off some things you should do before ever flashing or rooting your phone.
1. Make sure ReActivation Lock is OFF. (Its in Settings>Security>Reactivation Lock = make sure its unchecked)
2. Turn on Developer options. (Goto Settings>About device and tap Build Number 4 to 5 times; then develepers options will be in settings menu, goto that and turn on USB Debugging)
3. You'll need Official Samsung Drivers HERE! Install this to your PC!
4. Always Backup Phone!!
Now your set to Flash and Root.
IM gonna assume your on a Stock ROM. To root your gonna need to use Odin to flash TWRP, then once thats done we'll root from there.
You'll need these files :
Odin3.11 from Here. , Thanks to @LMMT, Thank him here. You'll install this to your Windows PC.
TWRP 3.0.2.0 from Here. This file is only for the Sprint Note4 SM-N910P, So that better be the phone you have!! Download and save to PC! You can Thank @bigbiff at this Thread.
Lastly you need SuperSU Here! Thanks to @Chainfire at this Thread! Download and save to your Phones SD card or Internal memory.
Now you have the files. Make sure you dont have samsung Kies running while installing or flashing your phone. Actually Dont have any other programs running when Flashing your phone.
1st - Install Samsung Drivers to your PC.
2nd - Install Odin to your PC.
3rd - Copy SuperSU zip file to your phone.
Now unplug your phone and turn it off. And open Odin Program as Admin. Now on your phone hold down the Vol down button + Home button + Power button at same time until a screen shows a Warning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you'll press Volume up to continue to Download Mode.
Once in Download mode plug into usb cord to PC. Your pc should install some drivers then Odin will show your device as connected. Goto options tab in Odin and make sure all the boxes are unchecked except F. Reset Time.
Then click the log tab so we can watch the progress were gonna make. Then click the AP button and load the Twrp file you downloaded into that. If everything looks like my pic then click start. Let it do what it does, dont touch anything until it done. Once down unplug phone and take out battery for 5 seconds.
Put battery back in and press Vol up + Home + Power until phone boots into Twrp Recovery.
Once in Recovery I sugessst to do a Full Backup.
Then you can Hit Install button in Twrp and find the Super SU file you saved on phone and Install and reboot when it says. Your ROOTED!!
Hope this isnt confusing. It really isnt that hard. But Id be able to show you better in person than in writing.
Click to expand...
Click to collapse
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.

aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Hooked my phone up to Smart Watch and noticed I had a software update. Gonna update my phone then check back in here and try it out! Thanks!
Sent from my SM-N910P using Tapatalk

aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk

imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
Really do not understand why Cf-autoroot do not work for you. I rooted my device just yesterday with Odin and Cf-autoroot works just fine
Sent from my SM-N910P using XDA-Developers mobile app

aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.

samep said:
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
imsuckk said:
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
Click to expand...
Click to collapse
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?

aaron74 said:
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
When I flash SuperSU it says that, and yes i am able to get into TWRP still.

imsuckk said:
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
Click to expand...
Click to collapse
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?

aaron74 said:
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
Click to expand...
Click to collapse
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)

imsuckk said:
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
Click to expand...
Click to collapse
Ok Im gonna PM you so not to fill this thread with bunch of mess

aaron74 said:
Ok Im gonna PM you so not to fill this thread with bunch of mess
Click to expand...
Click to collapse
Alright thanks man!
Sent from my SM-N910P using Tapatalk

imsuckk said:
Alright thanks man!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Besides the stuff we disgust. If that dont work. You could install a pre rooted rom. Or if you really want to figure out why it wasnt working.
I would start with clean slate and download the PE2 tar. Wipe phone and flash it. Reinstall Twrp and Supersu.
Hope it works! Have to get off here for awhile!!
Let me know if you got it!

Will the same method work on pj1 ?

LG G4 keeps booting in recovery mode (TWRP)

Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !

gdoucou said:
Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !
Click to expand...
Click to collapse
Try to install my latest BETA (check my signature)

steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse

gdoucou said:
steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse
Please try build 186
Click to expand...
Click to collapse

dont work for me same Probleme

TooThPicK said:
dont work for me same Probleme
Click to expand...
Click to collapse
Try my latest beta and if that is not working build 186
And which nightly causes that problem?

i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery

TooThPicK said:
i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery
Click to expand...
Click to collapse
Which cm version? tell exact build date.
Try to reflash stock kdz

Is there a way to Flash kdz from fastboot or recovery lgup dont find my device
ok i find the download mode now lgup find my device i downloading 20g and test

The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.

Lgup dont find my device i only have recovery and fastbood

ceanth said:
The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.
Click to expand...
Click to collapse
The change in Google code was the reason for one of the beta series I made. I was able to fix that in twrp even when this is no twrp issue. The internal updater worked fine afterwards when using any build after 15 of dec while using my latest beta.
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.

TooThPicK said:
Lgup dont find my device i only have recovery and fastbood
Click to expand...
Click to collapse
Not sure dude, best to post in the dedicated TWRP or cm14.1 thread.

its fixt thank you for your help the trick is turn off the g4 hold the + button and plugin the cabel now the device comes to downloadmode and now lgup is working
---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------
steadfasterX said:
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.
Click to expand...
Click to collapse
on my is the nigtly from 23.12

I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?

xXfreshXx said:
I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?
Click to expand...
Click to collapse
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
If you don't know how to get that log it is easy. Check my FAQ #4 A.
http://forum.xda-developers.com/showpost.php?p=68249027&postcount=3
.

steadfasterX said:
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
.
Click to expand...
Click to collapse
Thanks for your reply
https://paste.omnirom.org/view/6e5948df

xXfreshXx said:
Thanks for your reply
https://paste.omnirom.org/view/6e5948df
Click to expand...
Click to collapse
Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.

Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.
Click to expand...
Click to collapse
Here you are.
https://paste.omnirom.org/view/594df4ce

xXfreshXx said:
Here you are.
https://paste.omnirom.org/view/594df4ce
Click to expand...
Click to collapse
Hm the reason for that reboot lays somewhere else...
Please tell me exactly what you had done to produce that loop:
Which exact version of cm installed before upgrading?
Upgraded with internal cm updater or by flashing new zip in twrp?
The above would help me to reproduce the issue.
Besides the short questions above it would be great if you could test 2 things for me and if not skip to 3 (if you're in hurry):
1. The hw key combo test
2. The force twrp test
3. Last resort LG up
1. The hw key combo test
Flash the latest beta twrp and reboot into this twrp
Create a full backup if not already done so!!!
Power off the device and pull out the battery
Use the hardware key combo to get into factory reset screen (press vol down + power and keep them pressed. plugin battery. Wait until you see the LG logo and then release only the power button for 1 sec then press it again and keep both pressed until you see the factory reset screen)
Follow through this process and twrp will showing up without resetting anything
Grab the recovery log and paste it again
Then try to reboot to system
2. The force twrp test
If the first method hasn't worked it would be great to see the log anyways but then try the the following:
Boot into twrp (doesn't matter how for this test)
Flash again the latest twrp beta with twrp itself (choose img button at the bottom) and now when getting asked flash it to BOOT partition! Yes this is no problem or causes any damages. Just do it.
Then choose reboot into system and twrp will popup again (but now it starts from boot partition)
Now install the cm version of your choice or any other rom
Do NOT reboot yet
before rebooting grab the recovery log again and paste it again
3. LG up
If the above does not work and as I believe you need your device back soon the best bet would be do a full backup with the latest twrp beta version. Then use LG up to flash stock kdz again to get a working device.
.

Haven't flashed in over 2 years. Missing anything?

I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.

We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...

Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!

You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.

Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING

ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"

ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html

k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device

Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:

beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS

ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me

[Rom][Android 10][T830/T835] [Rooted/Debloated][TF5][Weta Kernel][July 26]

Hey Guys,
I present you the Custom Rom for T830 :good: Clean, Fast, Smooth and will be updated in regular basis.
And as we say always "VOTE" and if you Vote Not working please take the time to explain. Thank you
Now V2.3
Credits:
Thank you to @sevsman that create this beautiful ROM, Incredible job making it so fast. I am only the tester and I am glad to be able to share with you all.
Thank you to @Mentalmuso for his great kernel Weta latest TF5
Thank you to @topjohnwu for Magisk
Thank you to the creator of the Encryption Disabler @ianmacd
As usual I am not responsible for any damage cause to your tablet flashing this ROM:angel:
Some advice for newbies:
DRIVERS
There is no way to use PC with USB cable and flash with ODIN if you have not intaled the Samsung Drivers, search for these with your PC browser
OEM UNLOCKING
Go to settings/ About tablet/ Software information/ press build number 7 times to activate DEV mod
Go bac to setting down Developer Options that now apear
Tick Unlock OEM Your tablet will reboot and wipe everything so backup
Redo all setup Finish it even update if needed
FORCE REBOOT
Press and hold 3 keys Power/ Vol+/ Vol-
RECOVERY MODE
Power off tablet
Press and hold Power/ Vol+
DOWNLOAD MODE
For me the only thing that works is is at the same time force reboot when tablet off and connect usb cable to computer.
FLASHING ANYTHING WITH ODIN
ROM:
Place AP in AP
CSC_CSC_xxxxx in CSC
Place BL in BL
TWRP
Untick reboot in second tab
Place TWRP in AP
CHECK IF YOU NEED TO FORMAT DATA IN RECOVERY MODE
Boot in recovery mode
Select install
Select Storage on the bottom
If internal is 0mb you need to format data before doing anything that will allow you to wipe or zip anything but will cleann all you have on the tablet so Backup before
ROM FEATURES
Stock TF5
Rooted with Magisk latest and Weta Kernel latest
Heavy Debloat, most of the stuff you can install with Playstore is gone + some unneeded Samsung and Google stuff. No Knox, No Bixby, no Kids stuff, No digital wellbeing, No Microsoft stuff. It could definitely be cleaner; well that's for next version with maybe some more tweaking on Google and Samsung to reinforce privacy and improve battery life. Give us your ideas.
For now you still get Samsung Account, Samsung Store, Samsung DEX, Samsung Notes, Google Account, Google Playstore and Google
If you want to debloat more install Debloater module in Magisk and run it from Termius (Playstore) Example I got rid of Samsung Video Player, My Files, and hide Phone and Message as I don't use these and my App screen has no more than 11 apps before installing what I need.
Also for some interesting tweaking follow this thread and get rid of all: https://forum.xda-developers.com/galaxy-tab-s4/how-to/tweak-tab-s4-debloat-root-plugins-t4088699 still work pretty good except XPosed (Too bad!), Proca and few others but to disable big brothers It works fine. This is a great thread by @doggydog2
How To Flash this Rom:
OEM SHOULD BE UNLOCKED. THERE IS NO WAY TO TO THE FOLLOWING WITHOUT THIS STEP.
You need TWRP Installed. You can use flashify if you are already rooted to flash the new TWRP. If you don't know how refer to this thread from Mentalmuso: https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278
Reboot in Recovery
Factory reset, Wipe all but SD, Format Data (Very Important) (YOU WILL BE LOSING ALL YOUR DATAS SO BACKUP WHAT YOU NEED)
Flash the Zip file
Flash Encryption Disabler for now https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278 Thread from Metalmuso, look in Android 10 forlder
Reboot
Finish setup
Update Google Apps
Update Samsung Apps
Launch Magisk and press OK , device will reboot
Enjoy!
If you need to pass ctsProfile to true, flash "[MODULE] MagiskHide Props Config - SafetyNet, prop edits" from here: https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/post83146179 Downlaod magisk module,open termiux SU, Launch props select "2 Basic Autentification"
That doesnt fix Netflix in L1 even hidding Magisk. We wiill not implement that in the next update.
If you have issues with Bluetooth pairing not sticking after reboot go to Magisk, download module Bluetooth Library patcher 1.9 and install itin magisk, that will solve the issue.
Changes v2.3:
Fix /data not mounted
Fix Bluetooth not keeping devices BT after reboot
Downloads:
T830 v2.3
https://drive.google.com/file/d/10TPT-c9o_DNKZDUvshO2OQer6urVUwmc/view?usp=sharing
T835 v2.3
https://drive.google.com/file/d/1eqQkG-IgxIfK2FbItPqzu_Ujk4NHc0eR/view?usp=sharing
We need comments on T835 install please
For T835, I have 2 report that Iris detection is not working, that's need confirmation. It works perfectly for T830
Now with this ROM you don't need Odin after installing TWRP
Game add https://forum.xda-developers.com/attachment.php?attachmentid=5079465&d=1597424859
Please comment if you test it
Thanks
enotar
Beer Fund : https://www.paypal.me/ion513

Thanks looks interesting. Will this be available for the SM-T835? if so i will definitely like to try it out

A huge thanks to @ianmacd for the disabler because without it we'd all be in the can :good:
Here's v1 for the T835 and @enotar will update the first post later today.
https://drive.google.com/file/d/1A8YHmPy7zSEY8sOz8qE3Achl1qTmu3hA/view?usp=drivesdk

Sweet! Nice to see our Tabs have not been forgotten about. Look forward to giving this a try!

Google Drive folder T830 and link to T830 rom shared to all.

@enotar This is extremely exciting as I didn't think there'd be support like this for the Tab S4! I just have a question before I attempt this: Do I need to already be on Android 10 before flashing this rom or am I able to flash it from Android 9? I'm asking because I have the WETA Kernal + TWRP + Magisk installed, but on Android 9 (T830). Because of this, I'm not able to use system update to update to Android 10. If not, is there another way to flash this rom?

SavXL said:
@enotar This is extremely exciting as I didn't think there'd be support like this for the Tab S4! I just have a question before I attempt this: Do I need to already be on Android 10 before flashing this rom or am I able to flash it from Android 9? I'm asking because I have the WETA Kernal + TWRP + Magisk installed, but on Android 9 (T830). Because of this, I'm not able to use system update to update to Android 10. If not, is there another way to flash this rom?
Click to expand...
Click to collapse
ive used same combination, and upgrade method looks like this: flash frresh twrp 3406 img right from twrp, wipe everything from recovery, and flash this rom.
---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------
found 1 bug:
if you use iris unlock, there are glitches instead of eyes reflections

shoonari said:
ive used same combination, and upgrade method looks like this: flash frresh twrp 3406 img right from twrp, wipe everything from recovery, and flash this rom.
---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------
found 1 bug:
if you use iris unlock, there are glitches instead of eyes reflections
Click to expand...
Click to collapse
Can you explain more detailed as I have no issue here with Iris
And yes Android 10 is not needed just TWRP and BTW you need to come with something, 8, 9 or 10 to install TWRP
I will repeat myself do not wipe SD dont cross the box, you'll be very sad.
Sent from my SM-T830 using Tapatalk

enotar said:
Can you explain more detailed as I have no issue here with Iris
And yes Android 10 is not needed just TWRP and BTW you need to come with something, 8, 9 or 10 to install TWRP
I will repeat myself do not wipe SD dont cross the box, you'll be very sad.
Sent from my SM-T830 using Tapatalk
Click to expand...
Click to collapse
May I ask what BTW is?

This is how it looks for me(see attached file)
Moreover, i can't use intelligent scan, cause it says "can't open camera"
I thought this is because backup i used(who knows), but with second clean install everything is still the same

wings516 said:
May I ask what BTW is?
Click to expand...
Click to collapse
BTW = By the way.
---------- Post added at 05:17 PM ---------- Previous post was at 04:55 PM ----------
enotar said:
Hey Guys,
I present you the Custom Rom for T830 :good: Clean, Fast, Smooth and will be updated in regular basis.
Please comment if you test it
Thanks
enotar
Click to expand...
Click to collapse
Installation went so smoothly. Thank you for this excellent rendition of a debloated Stock ROM. I had a debloated version on my old Tab S2 tablet. So far so good. :good::good::good::good::good:

shoonari said:
This is how it looks for me(see attached file)
Moreover, i can't use intelligent scan, cause it says "can't open camera"
I thought this is because backup i used(who knows), but with second clean install everything is still the same
Click to expand...
Click to collapse
Strange, not getting that. Anyway I will review.
If this is not too much can you completly clean flash following OP please
Thank you

wings516 said:
May I ask what BTW is?
Click to expand...
Click to collapse
BTW means "by the way", it's not a file, lol. (Also I didn't see that someone mentioned this before me, sorry)

I keep getting "Failed to mount '/data' when I go to install... hmm... does anyone have any idea?
Currently running TWRP 3.4.0.4 and Android 9.0.1
Do I need to use a lower version of twrp?
I reboot, and I just get the bootloop now.

wings516 said:
I keep getting "Failed to mount '/data' when I go to install... hmm... does anyone have any idea?
Currently running TWRP 3.4.0.4 and Android 9.0.1
Do I need to use a lesser twrp?
Click to expand...
Click to collapse
You need to use TWRP 3.4.0-6 not -4 and this thread Post 2 step by step: https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278
Follow OP
Thank you

enotar said:
You need to use TWRP 3.4.0-6 not -4 and this thread Post 2 step by step: https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278
Follow OP
Thank you
Click to expand...
Click to collapse
Hmm ok, I upgraded to 3.4.0-6 and still the same error and bootloop. I flashed the image and not through ODIN to install it to recovery.
I will go through and install the WETA kernel and encryption disabler.

wings516 said:
Hmm ok, I upgraded to 3.4.0-6 and still the same error and bootloop. I flashed the image and not through ODIN to install it to recovery.
I will go through and install the WETA kernel and encryption disabler.
Click to expand...
Click to collapse
Just followthe steps and it will work.

enotar said:
Just followthe steps and it will work.
Click to expand...
Click to collapse
Followed exactly, but every operation I try to do be it wipe or install, I get "Failed to mount '/data' (Invalid argument)
I'm assuming there is a corruption in my /data and I need to reformat. I'll report back after.

wings516 said:
Followed exactly, but every operation I try to do be it wipe or install, I get "Failed to mount '/data' (Invalid argument)
I'm assuming there is a corruption in my /data and I need to reformat.
Click to expand...
Click to collapse
Well formating data is one of the steps of the thread to install TWRP

enotar said:
Strange, not getting that. Anyway I will review.
If this is not too much can you completly clean flash following OP please
Thank you
Click to expand...
Click to collapse
Unfortunately, that doesn't help: (
What i did:
Downloaded once again
Full wipes, thru menu and twrp
Totally clean install, even no accounts added
And still same issue...btw, 1st boot takes 17 minutes! It's it normal?
---------- Post added at 12:26 PM ---------- Previous post was at 12:08 PM ----------
Forgot to add: iris scan is working asis and unlocks a tablet, issue is that i see glitches in popup window (instead of eyes), and not working intelligent scan