Related
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.
***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
Hi everyone,
So couple of year ago I worked at a start-up company that had an Android project. So I'm not new to flashing images (ROM, Recovery, radio...), and I know most basic tools like ADB (and I'm technical person in my daily life). That being said - I remember the pain when the Radio image doesn't fit the firmware, and you have to play around with stuff to make reception work again. or the Recovery image won't fit the ROM etc etc. I'm not sure if any of this probably still happen TODAY, but back then when I got my LG-G2 - I decided not to touch it. I don't need anything besides the basic options (making calls, taking pictures).
I'm still using Stock with 4.4.2 - and the phone is getting lagy each passing day to the point it's time to root it and install a custom rom.
As I mentioned above, I want it to be quick and painless. Sadly, I don't have the time to do insane amount of research right now, mainly because I have a 3 weeks old born at home - and I prefer to use my free time hanging with it that Q&N issues with my phone
So here's what I need your help with:
1. A recommendation for a tool to save all phone settings. Mostly - App settings, and OS settings (even though I probably not going to go for Stock again, but it doesn't hurt to back it up).
2. An instruction how to flash D802 (there' so many options this days...). My Kernel version is 3.4.0.
3. Recommended ROM to use. Here's what I need from a ROM.
a. I probably want to upgrade to more safe rooted Android version (I can't for example handle permissions on 4.4.2).
b. With that, I don't want to install the latest Android only to figure it's running slowly on LG G2, I want the interface to be snappy (the Stock was snappy for a while).
c. I prefer Minimal ROM if possible with Google Apps installed. If I'll need something, I can install it myself.
d. One of the reason I didn't root up until now, was because people mentioned camera quality is meh with non stock roms. If possible, I will like to have a decent Camera quality.
e. I use my phone as a music player often. So good sound quality is important to me (and maybe even build in Parametrized EQ?).
Thank you!
Reading around the forum would have taken just about the same amount of time than writing your post. A post, mind you, that will get you the same as what you can already find with ease.
You managed to write with your kid around. Last time I checked, browsing takes less effort.
Rant out.
Instead of a rant, here's an actual help for people who might find it useful in the future and lack the time to do some proper research (as it took more than the 5 minutes it took me to write the original post). Please note that I won't take any responsibility for possible damages you may do to your system. Please use at your own risk. Also, note that I only tried it on LG G2 802 with Stock Kit Kat (4.2.2) and other version/OS version might not work.
I wasn't clear to me if 'One Click Root' work with Kit Kat bootloader, so I used 'ioroot'. When your done rooting your phone, you will need to flash a TWRP recovery. The easiest way to do it is by using AutoRec. However, the TWRP recovery installed with AutoRec doesn't have Thermal protection, and is dangerous to use according to the forums. So the next thing will be flashing a new TWRP version from the recovery. Blastgater have tweaked TWRP Recovery for LG devices. You can download the latest version here. It's basically a zip file you flash from within your old TWRP.
Regarding ROM, after doing some research - it looks like Lineage will be the best 'all-around' rom to use. Liveage 15/16 were too slow for my liking, so I went with 14.1 (Android 7.1) which was enough for me and snappy to use. However, the tricky part if your plan on using Lineage, is to flash a bootstack as the one coming with Stock won't work. It's just another zip to flash directly from the recovery and can be found here.
So this is just the high-level process, and I highly suggest checking the specific on the links I sent. It also helps if you know how to handle 'adb' and know the basic stuff like what bootloader and recovery are
Good luck.
Hi All
Looking for a best tutorial to follow and the right one for my phone really don't want to brick it, obviously :/. as there seems to be a few versions for the S7
I have the following: S7 android 8.0.0 SM-G930F not sure what else I need to know! I'm in the UK so I assume UK phones come with Exynos cpu's
and as far as I am aware android 8 is Oreo! but when they say Stock Rom I assume they mean the same as what came with the phone the original rom?
if so is there an alternative stable rom without the crap included or is it just as simple to delete every thing you don't want now it's rooted! and does that mean if I reset the phone its back to normal with all the crap included! or is there a way to keep it rooted even after reset! and should anything be disabled I.e prepare the phone before attempting to root like any kind of auto encryption that needs disabling and just one more question
if at anytime the rooting process hangs for a ridiculous amount of time when should I throw in the towel! and what are the chances of retrieving the phone back to original state! or does a dirty shutdown brick it?.
I started the root process but failed at first hurdle!, followed instructions install Odin3_v3.13.1 but when I connected the phone nothing showed up in Odin? though I will have another go just to confirm I followed it correctly, I'll update this when it's done.
this was the tutorial I followed:
Easy 4 Newbie [Root Guide]SM-G930F, G935F, G930FD, G935FD (Samsung Galaxy S7 Edge)
Warning ! Please note that the official TWRP for Nougat on Galaxy S7/ S7 Edge is not available yet but based on my experience the Marshmallow version is working on Nougat. By installing a custom recovery on your S7 and S7 Edge and rooting it...
forum.xda-developers.com
I know alot of questions I would really appreciate any help and clarification on the above.
many thanks
Regards
Daz
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Mohamedkam000 said:
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Click to expand...
Click to collapse
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
CitizenSmith said:
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
Click to expand...
Click to collapse
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Mohamedkam000 said:
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Click to expand...
Click to collapse
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
mooms said:
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
Click to expand...
Click to collapse
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
CitizenSmith said:
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
Click to expand...
Click to collapse
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Mohamedkam000 said:
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Click to expand...
Click to collapse
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
CitizenSmith said:
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
Click to expand...
Click to collapse
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
CitizenSmith said:
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
Click to expand...
Click to collapse
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Mohamedkam000 said:
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
Click to expand...
Click to collapse
Hi
Yes I can transfer files.
Yes phone asks to allow or block file transfer and it ohone shows up in Devices and Drives list and I can access the phone directory and shows up as Samsung s7 icon.
I will try another USB lead but the one I'm using is new and wasn't cheap but still a possibility I have had leads that weren't suitable for other things I was trying so it is worth a try.
Thanks
mooms said:
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Click to expand...
Click to collapse
When I downloaded Odin this was latest one Odin3_v3.13.1 though I have doubts that one version update will fix this issue as I did not see many if any people having my issue so they all used Odin and I believe theirs are fine even with older versions! but as I said Mohamedkam it's worth a try I will down load that version and give it a try.
As for the Samsung usb driver I believe that is where I got mine
SAMSUNG_USB_Driver_for_Mobile_Phones no version visible under properties on file version 1.7.23.0.
The USB connection seems to be fine I have uninstalled then re-download and reinstalled a couple of times.
I can transfer files no problem it shows up as Galaxy S7 Icon with card and phone drive inside.
I'll update shortly thank you.
Update:
I just went to try new Odin and whilst checking my phone have seen I have Offical TWRP app installed? I have no clue as to how that's got in there! as Odin did not show phone so I could select nothing!.
In the phone I open app and if i select backup existing recovery it opens and Select Folder tab and under that Selected Folder: /sdcard Filename: Recovery .img and at the bottom of screen Root access required.
I just hope it's installed correctly!. it is showing in playstore my apps as well just to confirm. if this is now installed what should I do next Now not sure what tutorial to start following.
I am just going to try the new odin and see if it picks up the phone back soon.
OK Seem that it now shows up in the new Odin. at least I think it has! in the log window I see this: <ID:0/004> Added!!
I didn't see that before.
Would be grateful if you could tell me how to proceed from here!
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
mooms said:
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
Click to expand...
Click to collapse
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
CitizenSmith said:
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
CitizenSmith said:
still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Mohamedkam000 said:
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
Click to expand...
Click to collapse
Yer I read that but I've ended up with TWRP installed and did not do that process because I was unaware it installed until it showed up.
As I said I'll just keep looking for now I know I'll find one that works for me from start to finish.
and I've been checking youtube but wouldn't want to use any links their providing but it may help familurise myself with the whole process if i watch enough of them.
Thanks again for your help.
mooms said:
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Mooms
I will check that out many thanks. I wonder if you could help me here. I am in the middle of the rooting process but have hit a snag. again!
I have now installed TWRP successfully then no-verity-opt-encrypt-3.1 all went fine and I'm at point of flashing Magisk but have an issue when I swipe to flash is gives me a error in red saying "invalid zip file format !"
I downloaded it from github here.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I click on "code" tab and then "download zip" and I placed that in a download folder on my sd card when I select it I get the above error any ideas as to why I am getting this am I downloaded the correct file?
thanks for any assistance you could give.
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Enzucuni said:
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Click to expand...
Click to collapse
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
HermitDash said:
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
Click to expand...
Click to collapse
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Enzucuni said:
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Click to expand...
Click to collapse
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
HermitDash said:
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
Click to expand...
Click to collapse
I actually restored it but to no avail. Same errors as described
Enzucuni said:
I actually restored it but to no avail. Same errors as described
Click to expand...
Click to collapse
Welp, back to stock you go then haha ADB it to EDL then run the unbrick tool and you should be at 0
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Enzucuni said:
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Click to expand...
Click to collapse
Might not be stable on first release but yea that's in the rumor pipelines
Yeah, I think I'll wait. A12 is still really nice. Some bugs here and there but perfectly usable and battery is basically infinite.
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
You could try flashing the fastboot ROMs made by @ot_inc (it's not 100% safe for your data so make a backup in any case).
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com
kriistofor said:
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
Click to expand...
Click to collapse
Where is the step by step ? The one that actually works ?
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
Umm.. no, you're not sounding harsh. And I've already done that: "google it" and stuff. This is why I post teh question here. This is not my first time at this lol !
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
You said, "Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm."
Where are you getting this from ?