Related
Hello,
I want to root my friends sprint note 4 (lolipop i believe). I was looking at this guide http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4note-edge-on-android-5-1-1/ and it seems straightforward. A little different than what I had to do with my phone becuase I had to unlock the bootloader and then flash the recovery and supersu. (I've never used odin) Does this mean the bootloader is already unlocked by default since all I have to do is install the recovery and then the kernel?
I'm a little confused, once I get the recovery, can I flash roms to it? Do I have to change the kernel again if I want to install a ROM? I don't plan on putting a custom ROM on his phone but I want reflash the stock rom or a debloated stock rom because he said even after a factory reset it was buggy (if you can link me to a proper stock rom that supports xposed I would be grateful).
And I also want xposed to work, is there a specific xposed version I should install?
And also, if I do flash something, is this method correct?
Backup data
factory reset
flash
clear cache
restore data
reboot
or do I restore the data later?
The thread and video are dated. A few key elementary facts are still relevant but as a whole, just not up to date. I wouldn't trust it and it lends to repeated help threads in this forum. If one read the OPs and threads of current ROMs in development and recent help threads, maybe less questions and help would be needed.
He omits current ROMs, didn't mention where the reactivation lock is for TW Android ROMs: Settings/Security/Reactivation lock (should be disabled). He doesn't mention Chainfire Auto root for Note 4 has been updated for 5.1 and will be key again for marshmallow (but that's only needed for rooting stock Odex). He also didn't tell you how to get to those old ROMs on his site. Some think you just Odin an old update but not so. That requires a 5.1 kernel matched with current bootloader rather than Odin downgrade.
The bootloader, while not locked to block root, is considered unlocked but actually is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Kernels should be kept in zip form because backing up a kernel in TWRP doesn't backup /system/lib/modules to restore and some custom kernels modify or add modules which may not work restored boot.img And restoring stock kernel on a rooted phone would cause a boot loop. So to restore that, you'd need to full un-root in SuperSU to avoid the boot loop there as well as restore the stock /system/lib/modules.
Root methods: unless you're using the full un-root or wiping everything but extSdCard (particularly user data and internal memory), you don't fully remove systemless root. Flashing a ROM or SuperSU with system based SuperSU over systemless root without the wipes would break things like root. Not seeing the SuperSU app or loss of ability to add new apps to superuser would be impacted but also a boot loop is possible if but patching stock kernel su.img to boot.
The basic principal is that to flash the custom deodexed ROM you need for Xposed, just make sure you're on the right update, Odin TWRP and follow the OP closely. If wiping internal memory is suggested by OP, I'd suggest that. To keep things simple, I backup and wipe everything but extSdCard for ports or where Xposed or systemless SuperSU is used. I typically do the same for stock tar updates as well.
As to recommended ROMs, I'd suggest any deodexed OK1 ROM for Xposed. tx_dbs_tx has a variety of OK1 ROMs. Freeza has one with Xposed integrated with Xposed modules in system. If Note 5 Moar port is a good fit, I'd recommend trying without Xposed until you determine the minimum of Xposed mods you're lacking so you're not overlapping features and you're getting to know the stability of it, first.
Rooting a friend's phone? IMO, you should be very sure and confident before proceeding and advise rather than do all the work and take the risks yourself. Use the correct USB driver, not just one that works. Setup his computer to root and sustain that phone.
Sent from my SM-N910P using Tapatalk
How is it dated exactly? I thought 5.1 is highest OTA for Note 4? Do OTA security patches change how things work now? I wouldn't know about security patches since I have a moto x 2013, we are left in the dust.
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version? Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
rapiollymega said:
How is it dated exactly? I thought 5.1 is highest OTA for Note 4?
Click to expand...
Click to collapse
I answered that in detail.
rapiollymega said:
Do OTA security patches change how things work now?
Click to expand...
Click to collapse
No; it's the bootloader and updates that did that.
rapiollymega said:
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
Click to expand...
Click to collapse
Good choice.
rapiollymega said:
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version?
Click to expand...
Click to collapse
Answered. Use Phone Info from Google Play or Galaxy Tools.
rapiollymega said:
Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
Click to expand...
Click to collapse
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
samep said:
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Click to expand...
Click to collapse
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
rapiollymega said:
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
Click to expand...
Click to collapse
It's the INTERNET that's ambiguous towards Touchwiz Android 5.1 There has been a few updates and each changed the way we do things. So when you say you're on Android 5.1, I say you need to be on the latest 5.1 update to have the greatest compatibility with the ROM you're choosing to flash.
Yes. You use Odin to install TWRP when rooting from full stock un-root to custom pre-rooted ROM. Perhaps my direction to Odin TWRP was ambiguous? Flash this in Odin AP slot with auto reboot unchecked- use the other option defaults from latest Odin:
https://dl.twrp.me/trltespr/twrp-3.0.0-0-trltespr.img.tar.html
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
I would restore data after installing Xposed. Keep in mind that these installation boots of custom ROM and Xposed take time. The less apps and data, the shorter the boot times will be. Plus the ROM will have more time to stabilize. After you've verified the last three of the bootloader and modem matches OK1, you can proceed with TWRP, then install ROM per the 1st post and immediate posts from OP. When you get to the Wi-Fi connection in setup wizard, make sure you have radio signal before connecting Wi-Fi. Make sure everything is stable and functional before Xposed installation.
Again, about the long boot times on installation. Best to keep case off the phone and ventilate phone with not too cool or ambient air. This will speed the process and possibly prevent component failure.
When your ready for Xposed, you need the Wanam unofficial Xposed framework.
http://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
You'll need sdk22 arm for Lollipop, not 64 bit Exynos or MM.
Currently it's the one labeled: xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip
Grab the uninstaller too, just in case. You shouldn't need it but be prepared.
Edit: be sure to get the deodexed version of that ROM. Makes things easier for Xposed and Xposed compatibility when adding system applications, if that applies to anytime later.
Sent from my SM-N910P using Tapatalk
Thanks for all the help, did it over the weekend and everything went smoothly. Well except for one part before installing the new ROM, I deleted everything in data/system and forgot that the zip was In the internal storage instead of the sd card . And for whatever reason the PC usb connection wasn't working in TWRP so I had to use a flash drive and otg cable to put the zip ROM back in the phone.
Hi,
I've been running Oxygen OS 3.2.8, rooted, with TWRP fine for a bit. I had downgraded from Oxygen OS Community Beta 9, by using the Full Unbrick Tool (detailed here: http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700) to downgrade to 3.1.2, and then I upgraded to 3.2.8 using the official OTA file, and using the USB ADB sideload in the stock OOS recovery. I did go though the motions of setting up 3.1.2 before updating to confirm that it works.
However after updating to 3.2..8, the phone bricks itself again, and when I boot I get the OnePlus logo for about half a second, and then a black screen with the LED being white. I even tried updating OOS using the OTA updater in Android, and it boots into the recovery, apparently does the update but then bricks itself again!
I can boot into Fastboot fine, but I can't boot into the recovery.
I have noticed that when I boot, because my bootloader is unlocked, I get the screen about the bootloader being unlocked, blah blah blah, but the link to learn more says "g.co/placeholder". After I attempt to update to 3.3.8, I get the proper link, indicating that the firmware has updated in some way.
If I install TWRP straight after using the unbrick tool, I can boot into it fine, and then install CM13 just fine, and it boots. However the fingerprint reader doesn't work, and I assume this is a firmware issue.
Correct, it's a firmware issue. With CM13 you have to use older firmware (from 3.2.4 or older, if I remember correctly).
Sesrch XDA for a thread with firmwares and flash that, done
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Correct, it's a firmware issue. With CM13 you have to use older firmware (from 3.2.4 or older, if I remember correctly).
Sesrch XDA for a thread with firmwares and flash that, done
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
I've got a 3.2.4 firmware file, what's the best way of flashing it?
I did attempt to flash this with stock TWRP, but it appeared to brick the device again.
Additionally, when I boot into fastboot mode it doesn't show me the bootloader version.
Someone did suggest using the commands:
Code:
Fastboot erase modemst1
fastboot erase modemst2
after flashing OOS, would this help at all?
Stock TWRP should work with that ... But you may try modified 3.0.2.1-28 by eng.stk, nothing to lose (it works with ALL ROMs and firmwares to date).
Dunno about that other suggestion, I think that's more related to IMEI problems, but I'm not 100% sure.
Sent from my OnePlus 3 using Tapatalk
I think I'm going to book a session with OmePlus and see if they can unbrick it properly, or just return it to O2 where I bought the phone.
I still find it perplexing that updating to 3.2.8 from 3.1.2 using the Android OTA updater bricks the phone!
I neglected my phone for a while because it seemed like I was updating all the time. Now i am not sure of the best way to get current. I am currently on version 7.1.2. any advice? Thanks in advance
You should be able to flash the 8.0.0 OTA and then I'd flash the latest security update. Flashfire should work fine if you're rooted
Sent from my Nexus 5X using XDA-Developers Legacy app
The thing I am looking at says
"1. You'll need bootloader, radio and vendor images from latest Google OTA ( Current: OPR4.170623.006 )"
How do I get this? I already had it rooted and twrp installed.
Krazy_Calvin said:
The thing I am looking at says
"1. You'll need bootloader, radio and vendor images from latest Google OTA ( Current: OPR4.170623.006 )"
How do I get this? I already had it rooted and twrp installed.
Click to expand...
Click to collapse
If you are already rooted I would recommend checking out this guide https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930. Scroll down to the section labeled "9. How To Update To A New Build Of The Stock ROM".
The stock nexus images can be downloaded from https://developers.google.com/android/images.
After flashing you would have to root again using your preferred method. I haven't had any problems rooting with Magisk.
You'll have to reinstall twrp and any system mods you've previously installed when flashing this way though.
Hey, this worked perfect. Thank you.
so i updated to OOS 10.0.9 Global on HD1900(China), but there is no patched boot or fastboot rom yet, so i patched it with his guide: guide by @gpz110
Boot.img patched with MAGISK 20.4 on OOS 10.0.9 HD65AA (GLOBAL)
Only for OOS 10.0.9 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_9.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_9.img
patched boot.img download: https://drive.google.com/file/d/1mHbDV0t_TKrhV2XqT7YySoHsl8623Bc4/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1RzUHNfp0Zns2FrfOHA9mwoDW9BKKeZVH/view?usp=sharing
My model is an HD 1905 but my current build number is 10.0.9 HD65AA... I bought it directly from OnePlus it's a 7T. Is this the boot image I need? I spent hours looking all over in different boot images patched with magisk. I haven't even unlocked my bootloader yet because I'm not sure what my options are... Lol also I noticed you have the patched boot image and a stock boot image I said just in case something goes wrong?
Sent from my OnePlus7T using XDA Labs
groovemetal81 said:
My model is an HD 1905 but my current build number is 10.0.9 HD65AA... I bought it directly from OnePlus it's a 7T. Is this the boot image I need? I spent hours looking all over in different boot images patched with magisk. I haven't even unlocked my bootloader yet because I'm not sure what my options are... Lol also I noticed you have the patched boot image and a stock boot image I said just in case something goes wrong?
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
it should work, but first u need an unlocked bootloader...
u can test it as described with the first and second step("fastboot boot" command only boot once, if u get bootloop, just restart and your device will boot as usual) , if it boot and u got root with no problems, then u can finish the process with the third and fourth step
boot image patched for EU version is possible 10.0.9.HD65BA ?
Yeah I just upgraded from a 6t and that was capable of a custom recovery but I'd run into trouble all the time because of the dual partition.. so that patched boot image with magisk all's I need is the APK file 7.51 correct I shouldn't need the magisk 24 .0zip
Sent from my OnePlus7T using XDA Labs
EmiRap said:
boot image patched for EU version is possible 10.0.9.HD65BA ?
Click to expand...
Click to collapse
check my tool here
Thx Thx Thx it worked properly
Thanks. Worked like a charm. The only thing is that I cannot find Advanced option and SafetyNet check is missing in Magisk Manager like I had previously in my OP6T. Also, with this root Google Pay and the likes work, as I also do not see Magisk Hide, but did enalbe in Settings. Thumbs up.
Update: Seems like WiFi is not working now! Any tips?
EazyVG said:
Thanks. Worked like a charm. The only thing is that I cannot find Advanced option and SafetyNet check is missing in Magisk Manager like I had previously in my OP6T. Also, with this root Google Pay and the likes work, as I also do not see Magisk Hide, but did enalbe in Settings. Thumbs up.
Update: Seems like WiFi is not working now! Any tips?
Click to expand...
Click to collapse
Are you sure, that you are on OOS 10.0.9 Global?
To revert back to stock boot image, grab the boot image from a fastboot rom here
be sure to grab the right one!
Definitely it is 10.0.9 HD65AA (GLOBAL) which I got over OTA. But I'll download the one from link again and update locally and then again re-run the steps for root.
Update: Reinstalled 10.0.0.9 and the steps ... all working, no above mentioned issues now. Thanks!
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
AboNaya said:
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
Click to expand...
Click to collapse
Did you already flashed or just booted the image?
HD1905BA Europe Patched boot
10.0.9 HD1905BA (Europe)
Stock boot : drive.google.com /file/d/1yyfzh6HbjrdZG3WDeyTv1d04fBgX3yzl/view?usp=sharing[/url]
Patched boot: drive.google.com /file/d/1ZCX7CWpRX-sZrb_ICOg64q2Abdumynmf/view?usp=sharing
guys!
Just a quick question: does this method pass the safetyNet check?
KyoshiDev said:
Did you already flashed or just booted the image?
Click to expand...
Click to collapse
I think I'll second his problem. I did first couple steps, confirmed root, everything seemed ok. Reboot and performed remaining steps. Now I have major stability problems. System UI eventually FCs then phone restarts. I'm able to get to settings and check version, still shows OOS 10.0.8 HD65AA. The signal bars showed no bars but LTE+ logo. Running another app called Signal Check Pro I confirmed that I had data. It seemed to get more stable the more it booted. The updater still wants to do a full update and wipe, it detects root and says that doing the full upgrade will lose root. I'm probably going to let mine do the full update and then reroot.
How did you patch the image? I get a non working patched boot.img when using the latest version of Magisk Manager.
AboNaya said:
I did the whole steps but the phone application continues to stop and then the data network does not work What is the problem I have updated wirelessly to 1009
Click to expand...
Click to collapse
im having a similar problem, after full ota update (2.6gb) from rooted 10.0.8 im losing mobile network (two SIM icon, greyed out, with a slash sign over it and no baseband infromation) after booting/flashing this boot, even creating mine. Mobile network restores after returning to stock. any clue? Im on 10.0.9.HD65AA
Sacob said:
guys!
Just a quick question: does this method pass the safetyNet check?
Click to expand...
Click to collapse
Yes
Nice Work with that .bat file
It works on Oneplus 7t 10.0.9Hd65BA. EU
Thanks for that super cool tool
To others that need to root a Oneplus 7t 10.0.9Hd65BA. EU i share my magisk boot file whit you all
#drive.google.com/open?id=1vGlNWrw2JAXmtb2ibst2BEQhKCM5ceMl #
Download the file an follow the guide in #1
Hi, I've just received my OP7t Global HD1900.
I installed OTA 10.0.9 and already unlocked the bootloader.
Please, does TWRP recovery work on this phone with 10.0.9? If not, which recovery should I use?
Do I have to flash a patched boot.img to get the phone rooted?
I used the boot image and it rooted my phone..great and many thanks!
Now...which recovery should I flash?
Thanks..
So I updated my phone to Oxygen OS 10.0.12 which was released today and like an idiot I forgot to repatch magisk before rebooting so I lost root. Since this is a new version I knew there wouldn't be a prepatched boot.img yet so I went to the oneplus support website, downloaded the update (and not checking the version number), extracted boot.img with payload_dumper.py, patched it, and flashed it to my phone. Unfortunately, the latest version up on their website is 10.0.11.HD65AA while my phone is on 10.0.12.HD65AA, and the mismatched boot.img broke wifi and bluetooth, so I cannot enable or use them, and cellular has the "no sim card" symbol but still seems to be working. What would the quickest way to fix this? I assume flashing a correct version boot.img would fix it, but I have no idea where to get the newest version.
(yes, yes I know I made many stupid mistakes to get to this point but it's too late now)
nytpu said:
So I updated my phone to Oxygen OS 10.0.12 which was released today and like an idiot I forgot to repatch magisk before rebooting so I lost root. Since this is a new version I knew there wouldn't be a prepatched boot.img yet so I went to the oneplus support website, downloaded the update (and not checking the version number), extracted boot.img with payload_dumper.py, patched it, and flashed it to my phone. Unfortunately, the latest version up on their website is 10.0.11.HD65AA while my phone is on 10.0.12.HD65AA, and the mismatched boot.img broke wifi and bluetooth, so I cannot enable or use them, and cellular has the "no sim card" symbol but still seems to be working. What would the quickest way to fix this? I assume flashing a correct version boot.img would fix it, but I have no idea where to get the newest version.
(yes, yes I know I made many stupid mistakes to get to this point but it's too late now)
Click to expand...
Click to collapse
flash the full system update zip again and this time don't flash the boot image, instead just boot the patched boot image and modify original boot image with magisk app itself.
Aswin08 said:
flash the full system update zip again and this time don't flash the boot image, instead just boot the patched boot image and modify original boot image with magisk app itself.
Click to expand...
Click to collapse
But the problem is that there's no way that I can find to download the newest update, downgrading just results in a bootloop. If you know where I could find the worldwide version of the 10.0.12 ota (either full or incremental version) then that would solve the problem.
nytpu said:
But the problem is that there's no way that I can find to download the newest update, downgrading just results in a bootloop. If you know where I could find the worldwide version of the 10.0.12 ota (either full or incremental version) then that would solve the problem.
Click to expand...
Click to collapse
That should be it:
OnePlus 7T OOS 10.0.12 Global: https://otafsg1.h2os.com/patch/amaz...gen_14.O.18_OTA_018_all_2007240040_cce2fc.zip