Develop Bugs

[Q] Issue installing SEAL ROM on SM-T210R

Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.

savidon said:
Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.
Click to expand...
Click to collapse
Try removing any spaces in the zip name.

gr8nole said:
Try removing any spaces in the zip name.
Click to expand...
Click to collapse
Thanks for the suggestion .. I just tried that and got the same errors.
Strange.
FWIW .. I also had issues trying to install the RocketTab ROM as well. Different problem, but still never worked. As I said, I was able to flash a debloat script that seems to have helped with the performance somewhat but still not great.
Thanks again.

savidon said:
Hi all ... I am working with a Samsung Galaxy Tab 3 7.0 (SM-T210R) and was interested in speeding the device up.
I flashed TWRP 2.6.3 and rooted and then tried to flash the SEAL ROM after watching the video.
During the install. I got a bunch of errors ... I don't have a screenshot, but it said the following:
ASSERT FAILED package_extract_file ("boot.img") ...
E: Error Executing updater binary in zip '/external_sd/ROM/SEAL V2 Official.zip' ....
Error Flashing Zip 'external_sd/ROMS/SEAL V2 ...
Luckily, the backup is working fine and I was able to restore.
I finally was able to flash a debloat script that I saw on XDA to speed it up a bit, but I really wanted to try this rom.
Any ideas are appreciated. Thanks very much.
Click to expand...
Click to collapse
I followed these directions (minus the rooting, as the ROM is already Rooted) yesterday and installed RocketTab 3.1 without a hitch:
http://forum.xda-developers.com/showthread.php?t=2660588

tsg2513 said:
I followed these directions (minus the rooting, as the ROM is already Rooted) yesterday and installed RocketTab 3.1 without a hitch:
http://forum.xda-developers.com/showthread.php?t=2660588
Click to expand...
Click to collapse
I've tried RocketTab multiple times ... and after flashing I get a message that the device appears to not be rooted, and offers to install SuperSU ... whether I say install or not, after I reboot ... the tablet freezes on the Samsung opening screen. I have no idea what else to try.
Thanks.

savidon said:
I've tried RocketTab multiple times ... and after flashing I get a message that the device appears to not be rooted, and offers to install SuperSU ... whether I say install or not, after I reboot ... the tablet freezes on the Samsung opening screen. I have no idea what else to try.
Thanks.
Click to expand...
Click to collapse
Did you check the MD5 of the zip, it could be a bad download.
Sent from my SCH-I605

gr8nole said:
Did you check the MD5 of the zip, it could be a bad download.
Sent from my SCH-I605
Click to expand...
Click to collapse
I did .. it matched. I think I'll try downloading again just in case though. Not sure what else to try at this point.
Thanks.

So I re-downloaded the SEAL ROM files and this time it installed without any errors, but I still got the not rooted message when I tried to reboot the device in TWRP. Again, whether or not I choose to install SuperSU, it hangs on the Samsung Galaxy Tab screen and I need to boot back into recovery and restore from backup to get working again.
For some reason, the root in the ROMs is not taking or something? Is that what is causing the problem? Does that make any sense?
Any other ideas? Thanks again!

savidon said:
So I re-downloaded the SEAL ROM files and this time it installed without any errors, but I still got the not rooted message when I tried to reboot the device in TWRP. Again, whether or not I choose to install SuperSU, it hangs on the Samsung Galaxy Tab screen and I need to boot back into recovery and restore from backup to get working again.
For some reason, the root in the ROMs is not taking or something? Is that what is causing the problem? Does that make any sense?
Any other ideas? Thanks again!
Click to expand...
Click to collapse
Sound like the system is not flashing correctly. Maybe try a different recovery.
Sent from my SCH-I605

Try the normal CWM coz touch-based are allergic to my device too....no worries you can still still scroll down the menu list of options using your finger tips
Sent from my SM-T211 using XDA Premium 4 mobile app

So here is the latest update in my custom rom saga ...
I downgraded TWRP to 2.6.1 .. and attempted to re-flash both SEAL and RocketTab. Both installs seemed to complete without any errors this time, but after rebooting, my device froze on the Samsung Galaxy Tab logo screen .. before the boot animation. This happened for both the SEAL and RocketTab roms. I also no longer got the not rooted error message, so it looked like it was fine.
Any thoughts on why these custom roms are not booting? I appreciate the help.
I restored back to my de-bloated stock backup, and it works fine. A little faster definitely, but not speedy by any means.
Thanks again.

Try philz touch recovery. I also had problems with cwm and twrp. But philz touch does the charm for me.
Sent from my SM-T210R using xda app-developers app

dualrecovery not working when coming from D5503_14.4.A.0.108 ?

Hello folks,
I just spend a couple of hours trying to get some new software on my Z1C. My inital plan was to flash PA 4.4 final, but that didn't really work out. Here's what happend:
1) I received the 108 update OTA. I used EasyRootTool ( ht tp://forum.xda-developers.com/showthread.php?t=2784900) with option 2 to regain root access. That seemed to work so far. Afterwards I tried to installed lockeddualrecovery using the Z1C-lockeddualrecovery2.7.129-BETA.installer, and here things started to get strange. I couldn't boot into CWM, so I made a backup using TWRP.
2) I unlocked my bootloader
3) I flashed PA following the instructions given in the thread: ht tp://forum.xda-developers.com/showthread.php?t=2764775
4) I was stuck with a bootloop, showing the PA start screen.
So I tried to roll back using the TWRP I made before unlocking the bootloader, but TWRP won't recognize the backup. I tried putting it in a folder named TWRP, directly into the root folder, interal SD, external SD...all the same, it just doesn't show up. I also can't install one of my older CWM backups, as trying to boot into CWM leads to a bootloop showing the "SONY" screen.
So I decided to flash a stock ROM (D5503_14.4.A.0.108_GenericDE_(1279-6978)) and repeated the procedure. Again, I'm stuck with a TWRP that won't recognize its own backup and a broken CWM. Therefore my question: Am I doing something wrong? Did this tool chain (upgrade to 108 -> EasyRootTool -> lockeddualrecovery) work for anybody else?

matt.s said:
Hello folks,
1) I received the 108 update OTA. Afterwards I tried to installed lockeddualrecovery using the Z1C-lockeddualrecovery2.7.129-BETA.installer, and here things started to get strange. I couldn't boot into CWM,
Click to expand...
Click to collapse
You should use search function or read a bit more in the Recovery thread:
.129 beta doesn´t work with 14.4.A.0.108.
Use instead .128 beta recovery and everything runs fine!

czrtst said:
You should use search function or read a bit more in the Recovery thread:
.129 beta doesn´t work with 14.4.A.0.108.
Use instead .128 beta recovery and everything runs fine!
Click to expand...
Click to collapse
Thanks, I read a lot but somehow this skipped my attention... :-/

matt.s said:
Thanks, I read a lot but somehow this skipped my attention... :-/
Click to expand...
Click to collapse
No problem

czrtst said:
You should use search function or read a bit more in the Recovery thread:
.129 beta doesn´t work with 14.4.A.0.108.
Use instead .128 beta recovery and everything runs fine!
Click to expand...
Click to collapse
Hmm strange, im on 14.4.A.0.108 and .129 Beta work like a charm....

ThreeMMM said:
Hmm strange, im on 14.4.A.0.108 and .129 Beta work like a charm....
Click to expand...
Click to collapse
Yes, only TWRP but not CWM.

how about 131?

acme64 said:
how about 131?
Click to expand...
Click to collapse
Try it with .132 and let us and @[NUT] know if it works !
http://forum.xda-developers.com/showpost.php?p=53809938&postcount=2392

14.4.A.0.108
for me been exactly same,i still on 757

[B]PLEASE HELP[/B] I'm stuck in a Custom Recovery Reboot Loop!

Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.

jonstowe78 said:
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
Click to expand...
Click to collapse
Read the First part of this post. http://forum.xda-developers.com/showpost.php?p=55490325&postcount=1014
There is a stock recovery zip in my rom addons.

gr8nole said:
Read the First part of this post. http://forum.xda-developers.com/showpost.php?p=55490325&postcount=1014
There is a stock recovery zip in my rom addons.
Click to expand...
Click to collapse
Thanks for responding and offering your help ... and a BIG thanks to all that you do with giving us all that you do.
In response to your suggestion: That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD! Do you have any idea what would cause the Custom Recovery to keep rebooting to itself?

jonstowe78 said:
Thanks for responding and offering your help ... and a BIG thanks to all that you do with giving us all that you do.
In response to your suggestion: That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD! Do you have any idea what would cause the Custom Recovery to keep rebooting to itself?
Click to expand...
Click to collapse
The bootloop in recovery is caused by the bottloader. Some people appear to have this bootloader version even if they didn't flash the 4.4.2 firmware. I suspect that Samsung started including the new bottloader on devices before the KK firmware was released.

[SOLVED] SGH-i317 Custom Rom Installation (No Rom Works)

Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help

are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105

I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.

yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
I m not sure about it. Do they actually differ ? i317 and n7105 (My thoughts they are same, Actually ALL Canadian versions of note 2 are same)

xtacydima said:
I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.
Click to expand...
Click to collapse
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.

First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
lsdhillon said:
Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
Click to expand...
Click to collapse

yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
majicmazo said:
First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
Click to expand...
Click to collapse
I m gonna go to twrp 2.8.5. Hopefully it works. Will be back with results soon.

i get this error after installation (Using twrp 2.8.5.0 now)
"unmount of /system failed; no such volume"
Probably this is cause?
How to fix it?
and
I m using twrp for t0lte (i have SGH-i317m) I hope its all right with that.

lsdhillon said:
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.
Click to expand...
Click to collapse
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.

that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane

xtacydima said:
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.
Click to expand...
Click to collapse
Could you please guide me to stable risk-free custom kernel for my sgh-i317

yaro666 said:
that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane
Click to expand...
Click to collapse
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
lsdhillon said:
Could you please guide me to stable risk-free custom kernel for my sgh-i317
Click to expand...
Click to collapse
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp

xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
Click to expand...
Click to collapse
really stock kernel with MJ5 modem and old bootloader up until this year january, as I updated to RR 5.1.1 and then updated bl, modem to OC and flashed CM13

xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp
Click to expand...
Click to collapse
I flashed AGNI kernel but the results were still same. Now gonna flash http://d-h.st/JUm as xtacydima suggested(Thanks).
Hope it works.
Will be back with results soon.
Do i need to update modem? to install RR (Marshmallow)?

With http://d-h.st/JUm as xtacydima suggested
It doesnt pass note 2 logo
Just goes blank after note 2 logo, So i think it isnt supported.
i m on 4.4.2 stock now.
Another thing i note is that my baseband is "unknown".
Any suggestions?

I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help

[ROM] MOAR MM Rom v4.1 - Toasted Edition - 07/22/2016

Not my work but it works now.
How to
Reboot in recovery
Wipe device
Flash Rom and kernel:
Download for rom:
Flash this after:
Reboot
Recommend using twrp 3.0.0.1

what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?

FingerBlastJ said:
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
Click to expand...
Click to collapse
Kernel fixes hardware issues

and if I'm on note 5 moar rom with patch.... no issue flashing right?

Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!

Blzfrost said:
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Click to expand...
Click to collapse
Just flash Rom and kernel everything will work.

MonkeyAround said:
Just flash Rom and kernel everything will work.
Click to expand...
Click to collapse
Oh I'm setting everything up right now for the flash! I'm so excited. Once I realized you linked to a note 5 Rom most of my questions got answered. My favorite part, the kernel was posted on my bday.

i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?

FingerBlastJ said:
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
Click to expand...
Click to collapse
Update your TWRP.
https://dl.twrp.me/zenltespr/

yea I tried doing that with Odin and it would freeze mid way. I also tried flashing a twrp update zip file on twrp and that didn't work either.
you think I should flash with flash fire?

bricked my phone by trying to flash newer version of twrp with twrp manager
been trying to flash unbrick tar and pit file to get back up and running but its not working.
any help is much appreciated

fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel

FingerBlastJ said:
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
Click to expand...
Click to collapse
Have you checked for root with root checker? I have lost root access a few times in the past?

yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?

FingerBlastJ said:
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
Click to expand...
Click to collapse
Last thing I can think of is when opening TWRP the first time. It asks if you want to make the system 'read only'. Did you select No?

I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?

FingerBlastJ said:
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
Click to expand...
Click to collapse
Not sure. You can click mount and see what is mounted. I am not sure that will work. I am not sure exactly what you are trying to wipe, but mount the items you are attempting to wipe and make sure the read-only is unchecked.

Try this:
Check to see if oem is checked
Re-root via root tar/odin
twrp 3.0.0.1 from edge files post in general
Backup stock
Wipe
Flash Moar
Don't reboot
Flash skyhigh kernel
Flash xposed(don't have to)
Reboot
Allow it to boot loop a couple time (from sky kernel)
Give 5-10 minutes to boot
I just did it with no issues and I've personally had more luck with 3.0.0.1 than any of the others.

heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding

FingerBlastJ said:
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
Click to expand...
Click to collapse
Your on Lp bootloader that's your issue.
Download Marshmallow tar from the general post I made for rooting Bpg1.
Flash tar and follow post.
twrp. 3.0.x.x is more for marshmallow. You need to be on 6.0.1 not 5.1.1.
Don't use fireflash on this device.
Fireflash is more for phones with locked bootloaders like Verizon s4 on the of1 update.
Fireflash isn't really up to date with our phone and could easily brick your device.