Database Users

Installing Atrix-MROM on an Atrix 4G with 4.5.145 update.

Just incase anyone with an Atrix 4G and 4.5.145 firmware, I followed the instructions in the following threads to successfully install Atrix-MROM on a brand new Atrix 4G ATT with the latest update.
1- Bootloader Unlock: http://forum.xda-developers.com/showthread.php?t=1182871
2- Root: http://forum.xda-developers.com/showthread.php?t=1769497
3- CWM Flash: http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot
4- Atrix-MROM Flash: http://www.montuori.net/android-mrom/atrix-mrom/
Thank you Michael Montuori, the Atrix-MROM is awesome.

Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.

ravilov said:
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
Click to expand...
Click to collapse
I think this is because, normally, they would need it to flash CWM. But it doesn't happen on Atrix. .

Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.

ravilov said:
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
Click to expand...
Click to collapse
This is my first smart phone, and I am absolute noob in this field.
I have been using Nokia 1216 and similar monochrome display phones before it.

In that case, I gues you're actually doing quite well really... If you came from mono dumbphones straight to this and have already flashed a custom ROM, that's actually kinda impressive.

Thanks!!!
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM

pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Glad it helped you.

pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.

aarizaga said:
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
Click to expand...
Click to collapse
It is in that thread. You can search: automatic_unlock_v4.2.zip
Or here it is:
h t t p s:// w w w . d r o p b o x . com/s/sr6ooho4zf9wqvo/automatic_unlock_v4.2.zip
Scan it first..

The MROM is simply amazing. Best battery life so far trying the cm7 based roms!
Sent from my MB860 using xda app-developers app

I am a neewbie, and when i learned how to flash custom roms, i was wondering, it is really necesary to root if you want a custom ROM?
now i was clarified.
So if want original firmware, and root acces, i just need an unlocked bootloader? And for rooting, can i just flash a fruitcake?
Sent from my MB860 using xda app-developers app

Hi, Thank you mmontuori for the excellent Rom and hard work to do it, and to Ravilov for the help.
I want to thanks in the post of the MROM in the development forum, but I can't do it because I don't have enough posts.
Well I finish yesterday to put all in order, only my contacts information I fail to restore.
The Go Backup didn't work.
One question, I don't installed the sv kernel, is necesary? because I feel that the battery it drain very quickly.
The rest appear so far to work very well, checking the holo launcher.

are you 100% sure everything on first post works with an ATRIX 4G 4.15.1455 from AT&T wiht the original motoblur?
i am newbee but wants to learn. its probably could i kill the phone?
thx!

Atrix 4g ATT 4.5.145 working well with CM 7.2
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence

Vengaence said:
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Click to expand...
Click to collapse
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app

palmbeach05 said:
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!

Vengaence said:
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Click to expand...
Click to collapse
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app

CWM versions for Atrix 4g
palmbeach05 said:
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence

Vengaence said:
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Click to expand...
Click to collapse
Ah, correct and incorrect my friend. While my signature may point out what device i am currently on, it does not reflect my past. A peice of supporting evidence is over in AtrICS v2.0 (see home button fix)
As far as cwm goes, cwm has unofficial builds as well. Look through one of the threads, it will point you to a link about recoveries and there does exist a 5.0.2.8. EDIT It was Romracer's recovery, accesed through the unlock bootloadrr thread a few threads down from this one. The 5.0.8.x i think was more like a 5.8.1.8, but i think that was a touch version? Now CM and the other threads may say the 5.x is ok for all of our roms, but as android moves forward, so must our support from libs, apps, kernels, scripts, and of course, recoveries. That is why i promoted the 6.0.4.6 revision both here and in the new 4.3.1 thread.
Sent from my MB886 using xda app-developers app

[q] lg leon lte h345

I'm in desperate need of a stock rom if anyone can help me out, was fiddling with root access and ended up losing my entire notification drawer and home button and whatever you call the square button. I have twrp installed but no rom.
Also this is a general LG LEON LTE thread because there seems to be almost no support for the phone.

Hey I know there are others or there looking for the same thing, any help would be appreciated.

seriously there are other people out there looking for the same thing someone give us a back up image.

HEY
jeremiah.m.gustafson said:
seriously there are other people out there looking for the same thing someone give us a back up image.
Click to expand...
Click to collapse
will a nandroid backup do for you? If so i can definitely help you out

i was looking for a link or two
I recently just got back into carrier devices an havent bothered with moddin devices in about two years i own two nexus devices an have sideloaded them for years with corporate emails an only have gone as far as tweakin boot images an on my older droids flashing custom mods daily... My only question remains with these newer junky devices how does one gain su if needed safely for things like otg access. It seems to me almost every carrier device is worth rooting an modding nowadays, an nexus devices are still the only ones that have a program thats stable an universal for all manufactuers as far as updating an management of a os whether it be stock or the user decides to go third party.
With that said.. Thats why awhile ago i stopped modding phones, using a windows tablet (for a full version of msdos) an since i had mastered my PB9110 version of my nexus one, i would flash my images via adb and sideload images with command line, in time ive sampled nexus after nexus, never using (play) an now back to a carrier device with no program support except 3rd party mods... Which in reality is great once you do have a nandroid backup an a stock rom... Thus the ability with the nexus factory image. Where are the steps and how tos my friends????

T-Mobile LG Leon H345 LTE 5.1.1 Version 10f Root
T-Mobile LG Leon H345 LTE 5.1.1 Version 10f Root. method worked for me. Not responsible if u brick ur phone.
I am not the author of this file.All the credits to the guys in below link
androidforums.com/threads/leon-one-click-root-works-on-10d-10e-ms345-h345-no-kingroot.938062
1) Install the latest LG USB drivers
2) USB debugging should be enabled, go to Settings to allow it.
3) Enable OEM Unlock in developer options
4) Download the attached files and extract into a folder
wxx.androidforums.com/attachments/lg_leon_ocr_v2-zip.93091/
5) Go to the folder, hold the Shift Button on the Keyboard and Right-Click on the Folder
6) Click on the ‘Open Command Window Here’ Option
4) Connect LG Leon to computer and set it to MTP.
5) Type root.bat in command window
6) Just wait until everything is finished and check for root
7) Download TWRP recovery image
wxx://dl.twrp.me/c50/twrp-2.8.7.0-c50.img
8) Use flashify app to install the recovery image and Quick boot app to boot into recovery

Flashify (Google App Store App) OEM Backups
jeremiah.m.gustafson said:
I'm in desperate need of a stock rom if anyone can help me out, was fiddling with root access and ended up losing my entire notification drawer and home button and whatever you call the square button. I have twrp installed but no rom.
Also this is a general LG LEON LTE thread because there seems to be almost no support for the phone.
Click to expand...
Click to collapse
Hey! I just used a program called Flashify (Found on Google Play Store) to back up both my Kernel (Boot) and System (Recovery) for my LG LEON LTE. I haven't attempted to reinstall these backups using Flashify as of yet, since I just rooted my phone and installed TWRP bootloader so I can try out a ROM... so, I have no idea how it works or if you can use it with any other bootloader app. However, I am attempting to offer you some kind of OEM Backup. I'm pretty new at some of this. I haven't posted enough to add links yet, but I'm going to try.
I have a LG Leon LTE for T-Mobile. My OEM details are as follows:
Android Version: 5.1.1 Lollipop
Baseband Version: MPSS.DPM.2.0.c11-00021-M8936FAAAANUZM-1.19638.1.19833.1
Kernel: 3.10.49
Build: LMY47V
Software Version: H34510f
These downloads are only available until 11/26/2015 due my only having a free account on the hosts site. I hope they help!
Kernel (Boot): OEM 3.10.49 @ http: //sabercathost. com/5Y7 (60 second wait for free download)
System (Recovery): OEM @ http: //sabercathost. com/5Y8 (60 second wait for free download)
Again.. I used Flashify (for root users) free from Google Play Store to create these backups. I have no clue if they can be used by any other programs for recovery. If you have/or can get Flashify, I'd like to believe they can be used for your STOCK recovery.
I may try and make a more common backup of these using ROM Toolbox Pro and see if I can host the files elsewhere that isn't limited to 7 days before paying for premium. If I do, I'll come back and update you or anyone else in need with the new locations.
Wish you luck!

Could u please post that I need a nandroid of that desperately
Aurey24 said:
will a nandroid backup do for you? If so i can definitely help you out
Click to expand...
Click to collapse
Messed up my phone and lossy original backup if u could post that nandroid I would really appreciate it. Thanks

For all the repeat questions on ROM threads

I frequent the JasmineROM and CyanogenMod threads in this forum and have noticed (and answered) many repeat questions: questions that have already been answered maybe a page or two back. I've noticed frustration in the answers to these questions (I've felt it myself), so I decided to start a new thread that will address the questions and provide the answers. It won't stop the questions from happening, but at least we can all just paste a link instead of writing the same paragraph over and over to people who don't seem to do any research.
---------------------------------------------------------------
Here's the format I'll be using for the questions and answers. I'd really appreciate it if suggestions could follow it, but it isn't necessary at all.
[SIZE="4"][B]Q: LE QUESTION[/B][/SIZE]
[SIZE="3"][I]A: ZE ANSWER[/I][/SIZE]
Sorry for not adding this in earlier.
---------------------------------------------------------------
(This may be in the wrong section, but I figured General would fit it best. Please move it if it's better somewhere else.)
---------------------------------------------------------------
I know I'm going to forget to include quite a few things. If you've seen a repeat question, I believe (I don't know for sure ) that replying to this post with at least the repeat question and then allowing me to edit it into this post will be a good way to go about this (I'll give credit with a name and link to the post).
---------------------------------------------------------------
Without further ado, here's the "FAQ":
Q: How do I root my Note?
A: http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
Q: How do I upgrade to the MM bootloader and modem?
A: http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
Q: I have no WiFi after using the latest version of CyanogenMod, JasmineROM, PaulPizz or any other Marshmallow-based ROM.
A: Make sure you have upgraded the bootloader and modem to Marshmallow. Guide here.
Q: On CyanogenMod, I'm losing LTE and only getting 3G.
A: Reboot into Recovery and then back to System. It won't fix it permanently, but it will restore LTE for a while.
A2: Delete the StraightTalk APN from your APN settings. (Obviously, you shouldn't do this if you have StraightTalk.) (Not everyone has a problem with the ST APN, but I figure I'll put this here.)
Q: Screen rotation isn't working on JasmineROM 6 or 7.
A: Many people have reported that this is a result of debloating. Not everyone has the issue, but those who have say one they remove Facebook and DT Ignite (among others), screen rotation breaks.
Q: Bluetooth audio is stuttering in CyanogenMod 13.
A: The workaround for this is to enable Daydream. That will prevent the phone from going to sleep, but will display a dark background with a clock, allowing you to still get a fast charge. The problem with BT audio lies in a CyanogenMod change that caused some problems with Bluetooth discovery upon device wake. hsbadr is working on a new build with the fix incorporated.
---------------------------------------------------------------
---- Thanks to @douger1957 || Post ----
Q: I'm already on Marshmallow with a locked bootloader. Is there hope for me?
A: Yes. You need to downgrade to Lollipop first. Flash the full firmware (thanks, @hsbadr!) on ODIN. Make sure that auto reboot is unchecked. When you get a "pass" in ODIN, boot into recovery and do a factory reset, otherwise you could get a bootloop. It takes a while for the first boot... upwards to 15 minutes... so be patient. Then you can start to unlock the bootloader. The bootloader must be unlocked before you can root.
Q: What ROMs can I flash?
A: That's a tough one. If you have a Lollipop unlocked bootloader you can only flash a ROM based on a Lollipop bootloader. Often the developer of the ROM will put the base of his ROM in the title of the thread as the bootloader firmware name (ie N910VVRU2BPA1) is a Lollipop firmware. Otherwise, you'll find the information at the lower left corner of the opening post. If you don't know, ask in that thread.
Subsequently, you must have an unlocked Marshmallow bootloader in order to flash a Marshmallow bootloader based ROM.
Confusing the issue more is the fact that it's possible to have a Marshmallow ROM use a Lollipop bootloader.
You can find all of the ROMs that are specifically for the N910V Note 4 variant (Verizon) here.
Q: I hear there are ROMs for other Note 4 variants. What's up with that?
A: True deal. Some of the other variants, the international models specifically, have been unlocked for awhile and there's a thriving development community. You can find those ROMs here. You've gotta know some stuff before you can flash one of their ROMs.
1) Stick with ROMs developed for the N910F and N910G variants. The radios are closest to ours. Flash a ROM for another variant and you're now a test pilot.
2) The same rules apply to their ROMs: Lollipop bootloader on your phone? Lollipop based ROM. Same for Marshmallow.
3) You'll need to flash a data fix to make their ROMs work on the Verizon network. Further, you may need to flash a kernel to make wifi work. I had luck with the Oscar kernel when I tried the Noble ROM last week.
(Note by Zacharee1: I've only had luck with the data fix on TouchWiz ROMs. AOSP ROMs, like CyanogenMod and Resurrection Remix, have problems with the data fix, resulting in reduced performance and still no cellular.)
Q: I've gotta, gotta, gotta have wifi calling.
A: At this time, you're pretty much stuck with a stock based ROM like Jasmine or PaulPizz. @hsbadr is working on getting it to work on CM13 but I'm waiting for other issues with that ROM to clear up and I am not current on its features. You will not find it on any of the international based ROMs.
(Note by Zacharee1: WiFi calling still does not work on CM. I have hopes for it in the future, but I may be moving to T-Mobile, where I'll probably have it anyway, so I won't be current on this either.)
Q: What are some tips about choosing and flashing custom ROMs on my Note?
A: Read these tips:
1) Find a ROM that interests you and has the features you can't live without. Most ROM developers are pretty thorough in the opening post or so regarding what you can expect.
2) Read the thread cover to cover. But Douger, some of those threads have hundreds upon hundreds of pages. Why? Because you'll know what issues others have had with the ROM and you'll find possible workarounds. You'll find out whether or not there are any showstoppers that'll keep you from using it as a daily driver.
3) Before you flash anything, do a full nandroid backup. In TWRP, check off all of the blocks. If crap blows up in your face, you can be using the phone again in about ten minutes of recovery time. Otherwise, you can spend hours setting the phone up again after flashing a ROM again.
4) Speaking of spending hours, plan on it. If you don't have the time, wait till you do because you;
5) Need to do a full wipe. That means data, system, cache and ART/Dalvik. Often when flashing ROMs, things don't get cleaned out properly, and artifacts will remain. Most ROM developers will include the instruction to wipe, which brings us to the next point;
5) Follow the directions exactly. Do not freelance unless you know what you are doing. That means flashing kernels, modems, bootloaders, etc. Follow the instructions in the order they are presented. If you don't understand any of the instructions, don't proceed until you do.
6) Perform a factory reset after flashing a new ROM but before booting.
7) Before rooting, I strongly suggest that you move anything you have stored on internal storage such as pictures or music, off the phone. Before you flash your first ROM, format the internal storage. The root process involves Chinese software and if you're not one who keeps up with the news, the Chinese are notorious hackers. Make sure you get all of the cooties off your phone.
8) It takes a long time for a phone to fully boot once you've flashed a ROM. Usually, it's over in about ten minutes but twenty minutes isn't unheard of. Be patient and resist the urge to pull the battery.
9) If you can get into recovery and download modes, you did not "brick" your phone. Contain your panic and think things out. The best advice I can give is to try to get back to the last time things worked.
Q: How do I know whether to use ODIN or flash in recovery?
The developer will usually tell you. But, if the file you're flashing has a ".tar" or ".md5" extension, it's flashed in ODIN. Often that file is zipped (extension ".7z") and needs to be unzipped. If the file has a .zip extension it's flashed in recovery.
Q: What is Odin?
A: Not the Norse god in this case. http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Q: What is TWRP?
A: TWRP is what's known as a custom recovery, which is what allows you (for the most part) to flash custom ROMs and packages to your phone. Each build of TWRP is device-specific. Make sure you downloaded the correct version for your device. http://www.xda-developers.com/how-to-install-twrp/
Q: What should I do if I'm having an issue with the ROM?
A: PLEASE don't just complain that something isn't working. See if you can fix it yourself; maybe it was something you installed or changed? If it's not unique to you or even a clean flash doesn't fix it, then you should look into providing some logs for the dev. Check out LogCat. Ask the developer how they want the log delivered.
Don't complain if you dirty flashed the ROM (meaning you didn't wipe /system and /data before flashing -- leaving internal storage and SD card alone is perfectly fine). While it's possible your issue is something wrong with the ROM, the developer will just ignore you. Also don't lie about having done a clean flash. It's pointless, and the developer can probably tell from any logs you provide that you actually dirty flashed. It's not fair to others if you take up their time by helping you try to fix a problem that can be solved by flashing the ROM the way it was meant to be flashed.
Q: Things on my screen are too small/large.
[SIZE="3"[I]A: You can actually change what's known as the DPI. Here's a method for that for the Note 4 on TouchWiz: [url]http://forum.xda-developers.com/note-4-verizon/development/solution-dpi-change-camera-dialer-t3422699[/url][/I][/SIZE]
[SIZE="4"]Q: I really like the ROM I'm using. Is there something I can do to help the developer out?
A: Luckily for you (and the dev), there is. Many developers will have a DONATE button in the sidebar on their posts. Remember, this is the only way most of them get anything from what they do. Developing these ROMs is usually done as a hobby, and considerable time and effort are put into producing something for you to use on your phone.
If you can't donate (or don't want to -- it's understandable), hit the THANKS button on the developer's posts. It's a nice gesture that shows you are interested in their work and that you would like to see more.
Q: What's this Xposed thingy I've heard about?
A: Xposed is a framework that allows almost unlimited customization and feature unlocking. As such, it is not something to play with lightly. This is the forum devoted to Xposed. This is where you'll find the framework, installers, and the modules.
@wanam has done much of the development for Samsung phones. Here's where you'll find his work. Since his is made especially for Samsung ROMs, I strongly recommend sticking with his base until you're more comfortable with using Xposed.
Q: There are so many downloads for Xposed. Which one do I use?
A: As always, RTFT (read the f'ing thread). However, here's a shortcut. Note 4 phones are ARM. Version 86 is current. Use that for AOSP based ROMs. Use the "alt" version for TouchWiz based ROMs. You need both the framework and the installer.
---------------------------------------------------------------
It's not very much so far (it's hard to come up with this on the spot), but I hope you'll all help out by posting the other frequent questions you see around these forums.

Q: What's this Xposed thingy I've heard about?
Xposed is a framework that allows almost unlimited customization and feature unlocking. As such, it is not something to play with lightly. This is the forum devoted to Xposed. This is where you'll find the framework, installers, and the modules.
@waram has done much of the development for Samsung phones. Here's where you'll find his work. Since his is made especially for Samsung, I strongly recommend sticking with his base until you're more comfortable with using Xposed.
Q: There are so many downloads. Which one do I use?
As always, RTFT (read the f'ing thread). However, here's a shortcut. Note 4 phones are ARM. Version 86 is current. Use that for TouchWiz based ROMs. Use the "alt" version for ASOP based ROMs. You need both the framework and the installer.

douger1957 said:
Q: I'm already on Marshmallow with a locked bootloader. Is there hope for me?
Yes. You need to downgrade to Lollipop first. Flash the full firmware (thanks, @hsbadr!) on ODIN. Make sure that auto reboot is unchecked. When you get a "pass" in ODIN, boot into recovery and do a factory reset, otherwise you could get a bootloop. It takes a while for the first boot... upwards to 15 minutes... so be patient. Then you can start to unlock the bootloader. The bootloader must be unlocked before you can root.
Q: What ROMs can I flash?
That's a tough one. If you have a Lollipop unlocked bootloader you can only flash a ROM based on a Lollipop bootloader. Often the developer of the ROM will put the base of his ROM in the title of the thread as the bootloader firmware name (ie N910VVRU2BPA1) is a Lollipop firmware. Otherwise, you'll find the information at the lower left corner of the opening post. If you don't know, ask in that thread.
Subsequently, you must have an unlocked Marshmallow bootloader in order to flash a Marshmallow bootloader based ROM.
Confusing the issue more is the fact that it's possible to have a Marshmallow ROM use a Lollipop bootloader.
You can find all of the ROMs that are specifically for the N910V Note 4 variant (Verizon) here.
Q: I hear there are ROMs for other Note 4 variants. What's up with that?
True deal. Some of the other variants, the international models specifically, have been unlocked for awhile and there's a thriving development community. You can find those ROMs here. You've gotta know some stuff before you can flash one of their ROMs.
1) Stick with ROMs developed for the N910F and N910G variants. The radios are closest to ours. Flash a ROM for another variant and you're now a test pilot.
2) The same rules apply to their ROMs: Lollipop bootloader on your phone? Lollipop based ROM. Same for Marshmallow.
3) You'll need to flash a data fix to make their ROMs work on the Verizon network. Further, you may need to flash a kernel to make wifi work. I had luck with the Oscar kernel when I tried the Noble ROM last week.
Q: I've gotta, gotta, gotta have wifi calling.
At this time, you're pretty much stuck with a stock based ROM like Jasmine or PaulPizz. @hsbadr is working on getting it to work on CM13 but I'm waiting for other issues with that ROM to clear up and I am not current on its features. You will not find it on any of the international based ROMs.
---------- Post added at 06:17 PM ---------- Previous post was at 05:55 PM ----------
Douger's tips for success:
1) Find a ROM that interests you and has the features you can't live without. Most ROM developers are pretty thorough in the opening post or so regarding what you can expect.
2) Read the thread cover to cover. But Douger, some of those threads have hundreds upon hundreds of pages. Why? Because you'll know what issues others have had with the ROM and you'll find possible workarounds. You'll find out whether or not there are any showstoppers that'll keep you from using it as a daily driver.
3) Before you flash anything, do a full nandroid backup. In TWRP, check off all of the blocks. If crap blows up in your face, you can be using the phone again in about ten minutes of recovery time. Otherwise, you can spend hours setting the phone up again after flashing a ROM again. Douger also creates a full nandroid backup when he's got his phone all set up with the apps loaded, just in case the ROM blows up or something.
4) Speaking of spending hours, plan on it. If you don't have the time, wait till you do because you;
5) You need to do a full wipe. That means data, system, cache and ART/Dalvik. Often when flashing ROMs, things don't get cleaned out properly, and artifacts will remain. Most ROM developers will include the instruction to wipe, which brings us to the next point;
5) Follow the directions exactly. Do not freelance unless you know what you are doing. That means flashing kernels, modems, bootloaders, etc. Follow the instructions in the order they are presented. If you don't understand any of the instructions, don't proceed until you do.
6) Perform a factory reset after flashing a new ROM but before booting.
7) Before rooting, I strongly suggest that you move anything you have stored on internal storage such as pictures or music, off the phone. Before you flash your first ROM, format the internal storage. The root process involves Chinese software and if you're not one who keeps up with the news, the Chinese are notorious hackers. Make sure you get all of the cooties off your phone.
8) It takes a long time for a phone to fully boot once you've flashed a ROM. Usually, it's over in about ten minutes but twenty minutes isn't unheard of. Be patient and resist the urge to pull the battery.
9) If you can get into recovery and download modes, you did not "brick" your phone. Contain your panic and think things out. The best advice I can give is to try to get back to the last time things worked.
10) Douger does not use Titanium Backup to restore his apps, especially if he's flashing a different ROM than the one he was on when he created that backup.
11) If you didn't do a full wipe before you flashed that ROM (dirty flash) do not complain about things not working properly on the developer's thread. Do send the developer a logcat so he can look into the issue.
---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------
Q: How do I know whether to use ODIN or flash in recovery?
The developer will usually tell you. But, if the file you're flashing has a .tar5 extension, it's flashed in ODIN. Often that file is zipped and needs to be unzipped. If the file has a .zip extension it's flashed in recovery.
Click to expand...
Click to collapse
Added. Thanks!

Zacharee1 said:
Added. Thanks!
Click to expand...
Click to collapse
From now on, I'm just going to link all questions to this thread. If they're too thick to use it, tough cookies. It'll be all they get from me. I just reported this post to see if we can get it stickied.
And thank you for fixing my boo boos.
---------- Post added at 07:42 PM ---------- Previous post was at 06:49 PM ----------
What you need to know about ODIN.
Everything you wanted to know about TWRP but were afraid to ask yo mama. TWRP is phone specific. Don't try to flash any old copy of TWRP.
Giving back to the community. How to logcat.If you're having an issue with the ROM you're on and you did a clean install, generate a logcat, then PM the developer and ask him how he'd like it delivered. It's basically a system dump which shows where errors were generated. It's helpful to narrow down the bugs. Don't fib about doing a clean install. The logcat knows, and is worthless to the developer.
How to change your DPI Thanks, @charly211297!
Almost forgot the most important thing: If you enjoy using the ROM or kernel and have gotten value from it, please consider sending the developer some beer money. Most of these guys spend considerable time in development and fixing bugs. Remember that no one here gets paid for what they do and if nothing else, hit that thanks button.

douger1957 said:
From now on, I'm just going to link all questions to this thread. If they're too thick to use it, tough cookies. It'll be all they get from me. I just reported this post to see if we can get it stickied.
And thank you for fixing my boo boos.
---------- Post added at 07:42 PM ---------- Previous post was at 06:49 PM ----------
What you need to know about ODIN.
Everything you wanted to know about TWRP but were afraid to ask yo mama. TWRP is phone specific. Don't try to flash any old copy of TWRP.
Giving back to the community. How to logcat.If you're having an issue with the ROM you're on and you did a clean install, generate a logcat, then PM the developer and ask him how he'd like it delivered. It's basically a system dump which shows where errors were generated. It's helpful to narrow down the bugs. Don't fib about doing a clean install. The logcat knows, and is worthless to the developer.
How to change your DPI Thanks, @charly211297!
Almost forgot the most important thing: If you enjoy using the ROM or kernel and have gotten value from it, please consider sending the developer some beer money. Most of these guys spend considerable time in development and fixing bugs. Remember that no one here gets paid for what they do and if nothing else, hit that thanks button.
Click to expand...
Click to collapse
I'll add these after dinner. Thanks again.

Wanna mess with your kernel? Here's a pretty good primer. As always backup first.

Need Beginner's Guide, so Custom Rom can be installed

***UPDATE***
Thanks to reply, I have now successfully done everything I set out to do, and created follow-up guide!
You can find it HERE
Original Post below:
Hello Everyone!
I'd like to start off saying I used to have a Nexus 4, with TWRP and Lollipop-based CyanogenMod. I was able to install this all by myself, and keep both TWRP and the ROM updated. I also flashed custom radio to unlock the LTE capability on that phone. My tool of choice to help customize the phone was Nexus Root toolkit.
I was able to follow guides posted long ago on these forums, to do what I wanted with the Nexus 4 back in 2013/2014, but it seems I'm not so capable these days. I've hit such a roadblock with lack of root and constant stutters/slowdowns with everyday use on my current device, the Axon 7, that I must get away from the stock software. I heard it was not so easy with other devices, and while a few devs have posted wonderful guides for users, it's just not enough for a true beginner like me. From skimming guides posted, it seems like devs already expect you to have installed custom recovery, or unlocked bootloader. Then when I try to do these things, so I can move onto custom ROM, it seems the guides are out of date or just not step-by-step enough for me to use, and I don't want to take a risk and brick my device trying things that I'm not sure about. I'm a power user through and through, but not so up-to-date or knowledgeable enough to be able to follow the guides already on the forums. Consider me 1 out of 5 on tech level for Android software.
Here's the model/software already on my device: Stock everything, from bootloader and recovery, to ROM.
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
will my ROM of choice have Daydream VR support? if not what would be needed?
this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through how to use it once installed to help me unlock bootloader/root on another device, Zenphone Zoom if anyone is interested.
PLEASE, don't link me to other guides for any part of this process, if the steps are thorough and relevant, please copy here, of course with all due credit given to original poster.
Feel free to let me know if more info about my knowledge level or device is needed to help you work on my request.
Thanks for reading, here's to several years more of everyone enjoying this wonderful device!

ok there is three real steps, but it can be aheadache, mainly because you didn't unlock before going to nougat.
Step 1. Downgrade to B29 Marshmallow - go here https://www.zteusa.com/axon-7/ and on the support tab in software updates is a full B29 software package. Download it, unzip it once, then put the update.zip file on your SD card.
- on the phone, in developers options, turn on OEM unlocking (it is needed to flash from sd card)
- boot phone to recovery, choose update from sd card, pick the update.zip from the sdcard, the phone will flash the B29 software. It is a bit slow, let it do what it needs to do.
Step 2. Unlock phone and install TWRP - go here https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 download the miflash program, fastboot unlock program, and twrp for B29.
- instructions are all there, just do what it says.
Step 3, Install LineageOS - https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679 very straight forward. Don't forget to install first the bootloader, then the rom, then gapps.
What makes this so hard is not being easily able to unlock in nougat. Most of us here unlocked way before marshmallow

No need to downgrade to b29.

lafester said:
No need to downgrade to b29.
Click to expand...
Click to collapse
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.

gpz1100 said:
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
Click to expand...
Click to collapse
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works

Help needed
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?

kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers

kaiso said:
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
Click to expand...
Click to collapse
Did you downgrade to Marshmallow B29 first or skip this step?

[email protected] said:
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
Click to expand...
Click to collapse
I'm praying that someone will compile the information spread about into 3 guides that are model specific so people like us won't rack our heads trying to figure out what on earth to do.

[email protected] said:
Hello Everyone!
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
1with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
2will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
3will my ROM of choice have Daydream VR support? if not what would be needed?
4this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
5NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through
Click to expand...
Click to collapse
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
nolimit78 said:
I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.
Click to expand...
Click to collapse
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.

nolimit78 said:
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
Click to expand...
Click to collapse
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????

KyJelly69 said:
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
Click to expand...
Click to collapse
Yup.

kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128

[email protected] said:
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Click to expand...
Click to collapse
Thank you for the guide, but I managed to get everything done without having to downagrade from Nougat. I was having issues with my Windows variant recognizing my phone after drivers were installed so I used Linux Mint 18.1 and everything went smooth as a whistle. I think the mods should pin your thread post.

I followed the rootjunkie YouTube videos, worked perfectly and the files were all available.
Sent from my ZTE A2017U using Tapatalk

N00b w/ "new SGH-I337 that is running original kernel & 4.2.2 & needs to be updated

N00b w/ "new SGH-I337 that is running original kernel & 4.2.2 & needs to be updated
I am going to apologize from the start. I've read through a lot of threads here and have ended up more confused (and somewhat scared lol). I am a tad more skilled than average when it comes to PCs but I'm a complete mess when it comes to phones!
For various reasons, I like my old ATT Samsung S4 SGH-I337 but am hard on them and need to replace them about every 2 years (I usually wear out the power port among other things). I buy a replacement, copy over my apps, etc, maybe run a minor update and I'm good to go. This time, I bought a "new" open box S4 on Ebay for a great price but when I went to install all my apps, discovered that it was STILL (since it was "brand new") running Android 4.2.2 and the original kernel from the release in 2013! Ok, no big I thought, I will just run the ATT update and I will be good. Nope. Too far out of date and no one at ATT or Samsung is willing to help. I did learn that if I can get 4.4.4 on the phone, then I should be able to update it via ATT to 5.0.1 but I can't even find those files (or at the least any links to them that are still any good!)
Due to life issues, it is critical that I get this phone updated ASAP. Please, can someone spell out step by step in N00b-speak where I can get the needed files and how I update this phone to 5.0.1 or better? I'd really rather not root it if I can avoid it but will do what is needed. I'll buy you a beer (or reasonable beverage of your choice! )
Samsung Galaxy S4 (ATT) SGH_I337
Android 4.2.2
Baseband ver: I337UCUAMDL
Kernel ver: 3.4.0-453947
[email protected]#1
Sat April 27 17:06:05 KST 2013

SilkRoadDog said:
I am going to apologize from the start. I've read through a lot of threads here and have ended up more confused (and somewhat scared lol). I am a tad more skilled than average when it comes to PCs but I'm a complete mess when it comes to phones!
For various reasons, I like my old ATT Samsung S4 SGH-I337 but am hard on them and need to replace them about every 2 years (I usually wear out the power port among other things). I buy a replacement, copy over my apps, etc, maybe run a minor update and I'm good to go. This time, I bought a "new" open box S4 on Ebay for a great price but when I went to install all my apps, discovered that it was STILL (since it was "brand new") running Android 4.2.2 and the original kernel from the release in 2013! Ok, no big I thought, I will just run the ATT update and I will be good. Nope. Too far out of date and no one at ATT or Samsung is willing to help. I did learn that if I can get 4.4.4 on the phone, then I should be able to update it via ATT to 5.0.1 but I can't even find those files (or at the least any links to them that are still any good!)
Due to life issues, it is critical that I get this phone updated ASAP. Please, can someone spell out step by step in N00b-speak where I can get the needed files and how I update this phone to 5.0.1 or better? I'd really rather not root it if I can avoid it but will do what is needed. I'll buy you a beer (or reasonable beverage of your choice! )
Samsung Galaxy S4 (ATT) SGH_I337
Android 4.2.2
Baseband ver: I337UCUAMDL
Kernel ver: 3.4.0-453947
[email protected]#1
Sat April 27 17:06:05 KST 2013
Click to expand...
Click to collapse
I too was lucky enough to snag a S4 off ebay with the original kernel still on it. So with that said....do NOT update your phone! You're on the very special Android 4.2.2 jelly bean MDL bootloader! If you update, you will lose the ability to boot AOSP ROMs and install a custom recovery like TWRP.
AOSP ROMs can take you past Android 5.0.x lollipop and give you Android 6.0.x marshmallow or 7.0.x nougat. You can also boot custom touchwiz ROMs that will take you to Android 5.0.x lollipop. Use the towel root app to root the phone and then freeze any OTA with the titanium backup app. You can also benefit from my guide here:
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122

StoneyJSG said:
I too was lucky enough to snag a S4 off ebay with the original kernel still on it. So with that said....do NOT update your phone! You're on the very special Android 4.2.2 jelly bean MDL bootloader! If you update, you will lose the ability to boot AOSP ROMs and install a custom recovery like TWRP.
AOSP ROMs can take you past Android 5.0.x lollipop and give you Android 6.0.x marshmallow or 7.0.x nougat. You can also boot custom touchwiz ROMs that will take you to Android 5.0.x lollipop. Use the towel root app to root the phone and then freeze any OTA with the titanium backup app. You can also benefit from my guide here:
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you for your reply. So I root it, then where do I go from there? How do I know what ROM is what and which one will give me at the least what I had on the old phone (less bloatware would be nice but right now I am so up a creek that I would be ok with stock)? Also, do you have good links to the tools you recommend? One issue I have been having searching here is that the 3-4-year-old posts here have sketchy or dead links.

SilkRoadDog said:
Thank you for your reply. So I root it, then where do I go from there? How do I know what ROM is what and which one will give me at the least what I had on the old phone (less bloatware would be nice but right now I am so up a creek that I would be ok with stock)? Also, do you have good links to the tools you recommend? One issue I have been having searching here is that the 3-4-year-old posts here have sketchy or dead links.
Click to expand...
Click to collapse
No problem, I always try to help when possible. After rooting you can follow my guide to get Loki doki installed. Then you can install a custom recovery like TWRP or clock work mod. My guide gets you clock work mod recovery installed but it's an old version. I use it though and it works fine for me. If you want TWRP recovery, you will have to search the web on how to install it with loki doki.
After a custom recovery is installed you can choose to boot touchwiz based ROMs or AOSP based ROMs like cyanogen mod. Custom touchwiz ROMs will look just like stock only modified (deodex, debloated, etc.) and AOSP ROMs will look like bone stock Android only with added features.
You can find AOSP ROMs in the original Android development forum here in the s4 forums. You can find touchwiz ROMs in Android development which is right under original Android development forum. Sorry, but I don't have any links to tools handy except for the link to my guide which I posted above in my last post. I use golden eye ROM on my s4 which is a stock based touchwiz ROM on Android 5.0 lollipop.
When booting ROMs, be sure that they do not have a bootloader update or else it'll override everything and will patch the loki doki exploit and lock down everything for good.

StoneyJSG said:
No problem, I always try to help when possible. After rooting you can follow my guide to get Loki doki installed. Then you can install a custom recovery like TWRP or clock work mod. My guide gets you clock work mod recovery installed but it's an old version. I use it though and it works fine for me. If you want TWRP recovery, you will have to search the web on how to install it with loki doki.
After a custom recovery is installed you can choose to boot touchwiz based ROMs or AOSP based ROMs like cyanogen mod. Custom touchwiz ROMs will look just like stock only modified (deodex, debloated, etc.) and AOSP ROMs will look like bone stock Android only with added features.
You can find AOSP ROMs in the original Android development forum here in the s4 forums. You can find touchwiz ROMs in Android development which is right under original Android development forum. Sorry, but I don't have any links to tools handy except for the link to my guide which I posted above in my last post. I use golden eye ROM on my s4 which is a stock based touchwiz ROM on Android 5.0 lollipop.
When booting ROMs, be sure that they do not have a bootloader update or else it'll override everything and will patch the loki doki exploit and lock down everything for good.
Click to expand...
Click to collapse
Thank you so much for the reply. While I am very grateful, with all due respect, I understood only about half of it. Here is the deal. I'm an older guy N00b with chronic pain issues under an extreme amount of stress, and my cognitive abilities are not what they should be. There was a step by step guide posted back in 2015 that is what I need but most of the links are bad or sketchy. Like I said above, I really need something along the lines of "go here and here to get this software and put it in "X" place. Then press these keys and do "Y", then press those keys and do "Z". I'm really sorry to be so difficult but I am trying my best to get it.

SilkRoadDog said:
Thank you so much for the reply. While I am very grateful, with all due respect, I understood only about half of it. Here is the deal. I'm an older guy N00b with chronic pain issues under an extreme amount of stress, and my cognitive abilities are not what they should be. There was a step by step guide posted back in 2015 that is what I need but most of the links are bad or sketchy. Like I said above, I really need something along the lines of "go here and here to get this software and put it in "X" place. Then press these keys and do "Y", then press those keys and do "Z". I'm really sorry to be so difficult but I am trying my best to get it.
Click to expand...
Click to collapse
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.

StoneyJSG said:
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
Click to expand...
Click to collapse
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.

SilkRoadDog said:
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
Click to expand...
Click to collapse
Your instructions say " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you." Do I do that before "loki doki installed and clockwork mod recovery."? If so, where is a good source for them? If not, when do I do I install them?
".

StoneyJSG said:
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
Click to expand...
Click to collapse
Ok, forget anything I typed here in the last hour lol. Somehow there were two locals and I was in the wrong one. So far so good. So back to the other question above. " " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you."" I still need to do that, right? if so, where do I find those apps?
Thank you so much.

SilkRoadDog said:
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
Click to expand...
Click to collapse
Touchwiz is the "skin" user interface that Samsung puts on top of Android. It is the stock SAMSUNG rom. Just Google touchwiz then Google stock Android, you'll see a difference. I like touchwiz so I am running a custom ROM called "Golden eye". You can download it from the Android development forum here in the S4 section. Other people like stock Android. The magic of being on the MDL bootloader is that you can boot touchwiz and bone stock Android ROMs. Most custom ROMs both stock Android and touchwiz based will let you access Google apps and the play store.
---------- Post added at 10:36 PM ---------- Previous post was at 10:21 PM ----------
SilkRoadDog said:
Ok, forget anything I typed here in the last hour lol. Somehow there were two locals and I was in the wrong one. So far so good. So back to the other question above. " " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you."" I still need to do that, right? if so, where do I find those apps?
Thank you so much.
Click to expand...
Click to collapse
You can get all those app except towel root on the play store. Once installed you can use ES file explorer to back them up to apk files then use the my files app that's on ya phone to move them to your SD card for use with your new ROM or keep them where they are since my guide tells you how to keep your data in tact...well for touch wiz ROMs anyway.

StoneyJSG said:
Touchwiz is the "skin" user interface that Samsung puts on top of Android. It is the stock SAMSUNG rom. Just Google touchwiz then Google stock Android, you'll see a difference. I like touchwiz so I am running a custom ROM called "Golden eye". You can download it from the Android development forum here in the S4 section. Other people like stock Android. The magic of being on the MDL bootloader is that you can boot touchwiz and bone stock Android ROMs. Most custom ROMs both stock Android and touchwiz based will let you access Google apps and the play store.
---------- Post added at 10:36 PM ---------- Previous post was at 10:21 PM ----------
You can get all those app except towel root on the play store. Once installed you can use ES file explorer to back them up to apk files then use the my files app that's on ya phone to move them to your SD card for use with your new ROM or keep them where they are since my guide tells you how to keep your data in tact...well for touch wiz ROMs anyway.
Click to expand...
Click to collapse
Since this is a "new" phone and I have nothing to back up yet, do I need to run a backup or can I follow your guide from that point, clean things up and install the ROM of choice?

SilkRoadDog said:
Since this is a "new" phone and I have nothing to back up yet, do I need to run a backup or can I follow your guide from that point, clean things up and install the ROM of choice?
Click to expand...
Click to collapse
It's always good to make a backup in case anything goes wrong with your phone down the road you can get back to where you started without having to flash the MDL stock Rom in ODIN by connecting your phone to your computer. You should though keep a copy of ODIN and the MDL bootloader .tar ODIN file. However, it's entirely optional to make a back up so you could just follow the guide from that point and clean up for a ROM install if you don't want to make a backup.
You can also boot a ROM and then make a backup after you have everything set up. You can back up the stock Rom or any ROM you boot/install. That's the magic of having a custom recovery like TWRP or clock work mod.

StoneyJSG said:
It's always good to make a backup in case anything goes wrong with your phone down the road you can get back to where you started without having to flash the MDL stock Rom in ODIN by connecting your phone to your computer. You should though keep a copy of ODIN and the MDL bootloader .tar ODIN file. However, it's entirely optional to make a back up so you could just follow the guide from that point and clean up for a ROM install if you don't want to make a backup.
You can also boot a ROM and then make a backup after you have everything set up. You can back up the stock Rom or any ROM you boot/install. That's the magic of having a custom recovery like TWRP or clock work mod.
Click to expand...
Click to collapse
Unfortunately, since I already started the install before seeing this, I have no idea what I backed up or where it is. :crying:
First off, I want to thank you so much for the help. I owe you and would like to buy you a beer or the like. I have my phone back now! There were issues with the Golden Eye install (it froze at the Samsung logo for over an hour) and I had to wipe everything and start over then I was able to get it up and running. Is this the right one? https://forum.xda-developers.com/showthread.php?t=2313469
Quick question: Do you know if that ROM supports an external SD card larger than 32gig?
I am having some issues and so far am not thrilled with this ROM and am wondering if it's the right one or if I screwed up. It hasn't been worked on since 2015 and the dev is hasn't been responsive in years. On my phone, it's really buggy. It boots slow, apps hang when loading, a few don't work right, the screen can flash or freeze and TouchWiz keeps crashing like it was doing at the end on my old phone's life. Any ideas as to why?

SilkRoadDog said:
Unfortunately, since I already started the install before seeing this, I have no idea what I backed up or where it is. :crying:
First off, I want to thank you so much for the help. I owe you and would like to buy you a beer or the like. I have my phone back now! There were issues with the Golden Eye install (it froze at the Samsung logo for over an hour) and I had to wipe everything and start over then I was able to get it up and running. Is this the right one? https://forum.xda-developers.com/showthread.php?t=2313469
Quick question: Do you know if that ROM supports an external SD card larger than 32gig?
I am having some issues and so far am not thrilled with this ROM and am wondering if it's the right one or if I screwed up. It hasn't been worked on since 2015 and the dev is hasn't been responsive in years. On my phone, it's really buggy. It boots slow, apps hang when loading, a few don't work right, the screen can flash or freeze and TouchWiz keeps crashing like it was doing at the end on my old phone's life. Any ideas as to why?
Click to expand...
Click to collapse
If you made a nandroid backup with TWRP recovery or clockwork mod recovery, then the backup file will be on your phone SD card or internal memory. Use the my files app to find it. It should be under a folder called TWRP or clockwork mod.
Hey no problem man, I know how it is to goto a forum and have 87,000 people view your post yet nothing is said. Yes that link is the correct link to golden eye ROM. When booting a ROM for the first time it will get stuck at the Samsung logo for awhile, this is normal but it shouldn't be more than 20 minutes. I think the S4 can handle SD cards up to 128GB, it might only be 64GB though.
Very odd golden eye ROM is giving you issues, I have only had one problem with it and that was the text message app acting up every so often. When you booted golden eye did you use the Aroma installer so it just asks you questions and you pick what you want? If not wipe and start over using aroma, it's built into the ROM. Also be sure to tell Aroma you want to use the "imperium kernel". That's the kernel I am using. Golden eye ROM doesn't have a bootloader update in it, so you'll stay on MDL and not have to worry about your phone patching the loki exploit.
I think you can also use the hybrid max kernel, but I don't think it's in the Aroma installer so if you want it you will have to download it from the forums here and flash it separately.
Another thing you can try is just "nuking your phone" as explained in my guide that wipes everything and gives you a nice clean install. The only reason I included the "keep your data" method in my guide is because I just stumbled upon it by doing it on my phone.
If all else fails and as a last ditch effort, you could send the phone to me and I will see if I can get it up and running with golden eye ROM, then send it back. No guarantees though as I'm no developer or anything, just a guy that knows the basics of Android ROMs and root.

Final report. It turns out the problems I've been having were related to the SU Super App. There have been complaints about the recent version. I thought that it was a corrupt install of Golden Eye so got a clean DL from another mirror and was getting ready to start all over. This time I was going to follow the dev's install instructions step by step instead of yours and his. However, I couldn't install TWRP as he instructed. It hung at 100% and never completed. I thought that maybe Super SU was the issue there so I uninstalled it and all of my other problems went away! So happy. Thank you for everything. I do owe you a drink!

SilkRoadDog said:
Final report. It turns out the problems I've been having were related to the SU Super App. There have been complaints about the recent version. I thought that it was a corrupt install of Golden Eye so got a clean DL from another mirror and was getting ready to start all over. This time I was going to follow the dev's install instructions step by step instead of yours and his. However, I couldn't install TWRP as he instructed. It hung at 100% and never completed. I thought that maybe Super SU was the issue there so I uninstalled it and all of my other problems went away! So happy. Thank you for everything. I do owe you a drink!
Click to expand...
Click to collapse
Hey glad it finally worked out for you. You will need superSU though, try a different version of it and that might fix the issue you're having with the latest version. That is unless you have the kingroot super user app, then you can use that but it's not as good as superSU. I had problems with it authorizing my root apps so I got rid of it and installed superSU. No problem glad to help and no thanks needed but if you really wanna buy me a beer go for it lol.