STUCK at bootloader after flash stock ROM from CM13 - Galaxy Note 4 Q&A, Help & Troubleshooting

Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.

Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
https://www.youtube.com/watch?v=ck6e8y4S3tQ

ithehappy said:
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
Click to expand...
Click to collapse
Same with you, but I got this problem after I flash from CM13 and want back to eRobot / stock ROM

That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.

ithehappy said:
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
Click to expand...
Click to collapse
I already try it using the WanamLite Modem + Bootloader. Still didnt work

Hmm, no idea then. If you find any solution kindly don't forget to tag me.

AlStarsKyz said:
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Click to expand...
Click to collapse
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.

ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
And when even flashing CM 13 the phone don't start ?

ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
Yes i used CM13 and function smoothly, but there couple bugs such Spen, and 4G didn't work in my country and when i try to flashing the stock rom, it's stuck on samsung logo.
*Simpati ra kenek 4Gne mas )

i got the same issue on my note 4 n910h is frustrating there is any solution to this or just wait until Samsung release a new update of 6.0 for the note 4

Try this 4 part factory firmware it's full wipe rom https://mega.nz/#!eJIUiLQD!r-HcKWRWd...VriCeWYdNpxeTo
Or http://d-h.st/EPj8

http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk

HmanA6399 said:
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
Click to expand...
Click to collapse
Gonna try that. Thanks m8 for the help )

Hey, guys as we all know The stock marshmallow for note 4 is out. Is it possible to flash it without boot looping to famous Samsung-logo. If there is a way I would really appreciate the help.

Related

If Anyone Need Help I Help Here

You Can Ask Help Here
Send From My SM-G900F Using XDA-Developers Mobile App
Recently updated my old Nexus 10/Manta to OmniROM 6.0.1 and I couldn't be happier. I had a fair bit of messing around on the first try until I got the sequence right...full wipe, flash ROM, flash Gapps pico and everything works REALLY well.
However, installing nightly updates is the same for me as the initial flash...I have to do a full wipe or I get the Google Services loop.
Am i doing something wrong is that how nightlies work currently?
Thanks.
Omnirom 5.1.1 on Nexus7, i can't use any of custom kernel. The installation work fine but after reboot the kernel is not install.
Thanks
Sent from my Nexus 7 using XDA-Developers mobile app
Hi,
i'm rather new with rooting, flashing and all the stuff that comes with it.
Now i have an Oppo Find7 and i managed to install the following:
-TWRP recovery
-OmniRom 5.1 nightly
-Gapps 5.1
I'm pleased everything worked but now i saw OmniRom 6.0, when i tried to flash it with gapps i encountered the first problem:
-The install of OmniRom went well but when i try to install Gapps 6.0 stock, it is saying i dont have enough storage? Can i somehow increase or free up this storage to it can fit?
Second question: If the above is possible, is there a way to flash OmniRom 6.0 and Gapps 6.0 without the loss of data? or do i still have to backup and restore with titanium backup?
Thanks in advance
Hi ...I'm using SM-N900 with lollipop 5.0 ...
I need to update my framrware by installing new rom (marshmallows ). However most what I found is that they have problem with the camera ...
IS THERE ANY STABLE ROM SO I CAN USE IT ?
Regards
Sent from my SM-N900 using XDA-Developers mobile app
Request Icon Resize inbuilt utility for omni rom 6.0.1
Dear Concern,
I am using omni rom 6.0.1 rom on my oppo find 7a the room is very smooth with all working function.
but the apps icon size are very big please add some functionality to resize the icon ASAP.
or please confirm if i am missing this option in ROM
Thanks & Regards.
Balvinder Singh
[email protected]
Hi there,
I have a Nexus 7 2013 wifi. Latest omni marshmallow but I have one issue. Battery drain.
It seems as it does not suspend. Maybe someone could point me in the right direction to help squash this pesky bug.
What I can add is that I have a Nexus 5 with same apps and settings without the issue .
Thank you
wich to download for Find 7a
Hi I'm glad to see omni back, as I was a user on samsung galaxy s2 !!!
I left the rom when i moved to find 7a, but now i absolutely want to try it !
So simple question as I didn't found it anywhere:
For my Find 7a, should I download rom from folder :
1) Find7
2) Find7op
Thanks to all
St Exupery said:
Hi I'm glad to see omni back, as I was a user on samsung galaxy s2 !!!
I left the rom when i moved to find 7a, but now i absolutely want to try it !
So simple question as I didn't found it anywhere:
For my Find 7a, should I download rom from folder :
1) Find7
2) Find7op
Thanks to all
Click to expand...
Click to collapse
Find 7. Find7op is the One Plus One.
Clear, Precise, Thanks you !
Installing this we
Recently updated my old Nexus 10/Manta to OmniROM 6.0.1 and I couldn't be happier. I had a fair bit of messing around on the first try until I got the sequence right...full wipe, flash ROM, flash Gapps pico and everything works REALLY well.
However, installing nightly updates is the same for me as the initial flash...I have to do a full wipe or I get the Google Services loop.
Am i doing something wrong is that how nightlies work currently?
Thanks.
"I have version SuperSU-v2.65-20151226141550 and this I flashing automatically after each OTA.
Just copy SuperSU zip to "/sdcard/OpenDelta/FlashAfterUpdate" and disable Secure mode in settings of system update."
I got this step from oppo forum, and it work perfectly and now my question is :
can i do samething like that but this is for font ?
because everytime after update omni nightly, i need too flash my font again
thx u
Really Need Help..... I have a mediatek 6572 device called Innjoo i1k .....
And stock rom which is flash able through sp flash tool.... guide me that how i port mt6572 rom into my device actually it need some replacement of file that have in the stock rom... but i have stock rom in sp flash tool firmware format not in zip format... waiting for your reply .... will be very thank full to u..... thanks.....
Recently updated my old Nexus 10/Manta to OmniROM 6.0.1 and I couldn't be happier. I had a fair bit of messing around on the first try until I got the sequence right...full wipe, flash ROM, flash Gapps pico and everything works REALLY well.
However, installing nightly updates is the same for me as the initial flash...I have to do a full wipe or I get the Google Services loop.
Am i doing something wrong is that how nightlies work currently?
Thanks.
Help with Galaxy Express 3
ModeFX01 said:
You Can Ask Help Here
Send From My SM-G900F Using XDA-Developers Mobile App
Click to expand...
Click to collapse
I just upgraded from ZTE Maven running Android 5.1, to a Galaxy Express 3 running Android 6.0.1. love the phone, but for one thing. I playing a game called Walking War Robots. It played good on the 5.0, but really lags bad on the 6.0.1.. I thought the better phone would be better but it's worse. I've also noticed that the graphics are better for the 6.0.1, including shadows for robots, etc. I believe it adds to the problem. What I'd like to know, is there a way to improve the performance of my phone to get rid of the lag, or is there a way to disable enhanced graphics and make the game think I'm running 5.0 to get rid of the shadows and enhanced graphics. I can do without robot shadows for the sake of smooth gameplay. Any help will be greatly appreciated... YodaXIII
password reset?
I decided to try the official Nougat for my 6P. Before going there, I made a TWRP backup, which I used "adb pull" to get to my computer. After trying Nougat and deciding I didn't like it, I went back to Omnirom from the TWRP backup. At boot it asks for the decryption password, which works fine, and omnirom starts up correctly. It then prompts me for password after restart, and it insists that I enter the wrong one. What options do I have to get past this, other than a clean install and then recover my apps/data from backups?
[edit: solved it] I entered the file manager of TWRP and removed /data/system/locksettings* After this, the next reboot required decryption password, as expected, but did not require a lockscreen password, so all was fine and I could again set a new lockscreen protection.
I have a micromax unite 4 pro (Q465) but on google there is no recovery img for any recovery I request u to help me how can I install a custom recovery to flash a zip filee please help me
Need custom Rom for honor 6 h60-l04
Hi i'm using huawei honor 6 h60-l04...There is no custom rom available for this phone. Its a nice mobile with 3gb ram ..but no custom rom available.so anyone please build any custom rom ???:crying:
How can i upgrade HTC DESIRE 820
Hi,
i have htc desire 820s ,i want to upgrade my mobile 4.4.4 to 5.1 or other update version ,
any one guide me about that ,i have already my device rooted ,so please tell me how can i do
thanks

[help needed] note 4 n910c bootloop

Hello, I needed help regarding my note 4 boot looping.
1. I installed the CM13 on my note 4 N910c and after that, I cannot go back to stock or to any other ROM like S6 experience or Ditto Rom.
Here is the list of things I tried so far:
* Flashing the factory Rom from SamMobile - Marshmellow 6.0.1, Lollipop and even Kitkat still Bootloops.
* Tried flashing other Roms no luck.
*But when I tried to flash AOSP Rom Bliss I was able to load into operating system. Unfortunately, it was a bad Rom which was in its early stage and had a lot of bugs.
* Tried to fix the efs folder but the methods are not 100% working the comments on the forum says they were not able to figure out the method.
My question is as Stock Marshmallow Rom is out is there a way to revert to Stock because Cm13 for Note 4 N901c is buggy and randomly reboots.

HELP regarding Upgrade to MM STOCK ROM OR CM 13.0 !!!

Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.

Custom Rom Install Issues on Sprint Note 3 (SM-N900P)

OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
I would also ask in the SPRINT forum .
JJEgan said:
I would also ask in the SPRINT forum .
Click to expand...
Click to collapse
Good idea, thanks.
jdd1960 said:
OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
Click to expand...
Click to collapse
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
ShaDisNX255 said:
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
Click to expand...
Click to collapse
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
jdd1960 said:
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
Click to expand...
Click to collapse
You're welcome. Happy flashing!

Why do none of ROMs work anymore especially for SM-T530NU?

This is still a damn good tablet yet every Rom I try and flash beyond 3.2 Blisspop fails. They just hang at the Samsung boot screen.
People leave their topics with no caution to anyone. It's no wonder the people I directed here no longer message me.
Sent from my P00C using Tapatalk
You might have to reflash stock and start over. I, as an example, am running 7.1.1 on my 530NU and I just flashed stock just for the fun of it. In the past 4 hours, I've successfully flashed stock twice and 3 custom Roms. Flash stock through Odin and flash Dirty Unicorn or CrDroid. Both of them are running like clocks on the 530NU.
Sorry but I'm a huge Noob and really need some help. Can I use a Samsung S7 in place of a computer to root my Samsung Galaxy Tab 4 SM-T530NU? ( Android version 5.0.2 ; Kernel version 3.4.0-10845349 [email protected]#1 ; Build number LRX22G. T530NUUEU1BQC1 ) The phone is brand new and I want to start with the tablet first, thank you.

Categories

Resources