***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
Related
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
fir1996 said:
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
Click to expand...
Click to collapse
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
JudgeDread11 said:
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
Click to expand...
Click to collapse
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Dylan2232 said:
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
JudgeDread11 said:
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
Click to expand...
Click to collapse
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Dylan2232 said:
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Click to expand...
Click to collapse
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying anything is learning how to backup and restore.
JudgeDread11 said:
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying any freething is learning how to backup and restore.
Click to expand...
Click to collapse
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Dylan2232 said:
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Click to expand...
Click to collapse
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
hi , good news for Huawei y5 2017(MYA-L22) users.
Download latest lineage14.
visit to my blog.
cheers
https://p55novo.blogspot.com/2018/07...e-141-for.html
JudgeDread11 said:
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
Click to expand...
Click to collapse
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Dylan2232 said:
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Click to expand...
Click to collapse
For rooting you need unlocked bootloader ( if you don't do ir then below won't work).
1)download the 4pda app from google play store and register an account .
2) download the TWRP.img file from 4pda website here is the link
https://4pda.ru/forum/index.php?showtopic=823938&view=findpost&p=74424572
3) enable developer mode in your phone by going to setting about phone , tap 6 times on the build number.
4)go to developer mode and enable usb debugging and oem factory unlock .
5) go to your pc install adb here link https://forum.xda-developers.com/showthread.php?t=2588979
6) now conect the phone to the pc and run cmd , type adb reboot bootloader . (Your device ahould restart and enter bootloader mode (white screen)).
7) now take the TWRP.img (must be copyied to desktop ) and type in cmd cd desktop.
8) type fastboot flash recovery TWRP.img (change the file name to TWRP ).
9) type fastboot reboot.
Now you have successfully install TWRP on your device.
Continue... If replied
Guys, I'm at my wits end here. I don't know what to do. And it's driving me crazy.
After saving for 3 months, I got a used Essential Ph-1 from craigslist (for sprint). It came with Android 9, and a February 5, 2019 security patch.
All I want to do is to root the phone. And I have tried everything in my power to get it to work. It just does not. I have unlocked the bootloader, I'm seeing the device in adb and fastboot, but unable to sideload, or flash anything. I've been following different threads on here and youtube looking for directions, but my phone will just not do it.
Can someone please help me? I will send my phone over to you and pay you to have it done. I've tried almost everything to do it, and nothing works. I've even tried to flash android 8 and 7, it still doesn't do it. Someone please help me. I don't know what more i can do. Any guidance is appreciated.
Can someone please help me? I don't know what more to do. Please.
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
goofball2k said:
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
Click to expand...
Click to collapse
No. I can't sideload or boot into anything other than the android 9
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
kt-Froggy said:
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
Click to expand...
Click to collapse
I tried that too. But it kept saying unable to unpack boot image | installation failed.
I tried it with the stock images from the Essential website, both the OTA and fastboot versions. I'm getting the error for both files.
I would suggest checking out the PH1 Dev telegram group https://t.me/EssentialPH1DEV . not only will you find pre rooted stock boot images along with ones with TWRP as well you will also find help flashing them if you need it. Hope this helps you out.
Thank you everyone for all your help. Special thanks to kt-Froggy. I got it to work. I had to change my usb port from 3 to 2 and i was able to get it to work!
Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.
Brotinger said:
Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.
Click to expand...
Click to collapse
If you download the lmsa tool, plug in the tablet and go to recovery it will download the full stock firmware. Then you can find it c/program data/LMSA/downloads.
I did that then downloads magisk manager. Extract the boot.img from firmware and put in storage of tablet. Then used magisk manager and patch the boot.img it will tell where it is stored. Extract from tablet and put it in same folder as adb/fast boot. Then put tablet in fastboot and fastboot flash boot magisk-patched.img. then fastboot reboot. The will be rooted with magisk
I forgot. You must unlock bootloader to do this.
Dear 11mackey11,
thank you so very much for caring enough to share your knowledge with me!
So the guide I mentioned earlier is pretty much applicable for the newer model as well? What a relief!
I am also grateful for the hint on how to obtain the stock firmware. For all the dirty things I did to my devices in the past, it never became necessary to put the LMS-Assistant to use, but I will gladly change that now.
As soon as my device arrives, I will try to root it as you suggested and will report back how I fared.
Again, many thanks!
It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!
Brotinger said:
It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!
Click to expand...
Click to collapse
Hi. I just purchased the same tablet. I would appreciate it if you could write up a guide on this forum. It would be a help for everyone.
I'm not even sure how you unlock the bootloader on this thing!
Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).
Tutorial
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I want to apply it to my device, have you tried this method?
Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.
b4nd0ler0 said:
Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.
Click to expand...
Click to collapse
thanks, I'm waiting for news from you. The tablet is sold very much in our country. like this in the world. I'm sure the developers will do something about this device.
b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I rooted my device with this method
this method doesn't work
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
This method is working!
Use the Official Lenovo website to access your original "rom" file and get the "boot.img" file.
Program: Lenovo Rescue And Smart Assistant https://lnv.gy/3d8FHLi
For an article on how to download the Rom file via the program, see here. (Step 3)
https://bit.ly/2yE1nQf
Good Luck!
adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
You did not enable Magisk Hide
mingkee said:
You did not enable Magisk Hide
Click to expand...
Click to collapse
That was it! Thanks! You're smarter & more helpful than Google!!! ))
Hi.
After i root the tablet, i tried to delete youtube and gdrive. Then i restart the tablet but it stuck in fastboot mode. Not booting.
i couldn't install stock rom. What i must do
I did this..
i patched the boot img from the lenovo program. and i like to shut down my devices when i dont use them and now i cant make it boot. im stuck in a bootloop and its says orange alert when i boot the device. i can only get into the fastboot menu. when i try to boot with vol + and power nothing happens and when i release it starts up again in a bootloop. i cant shut it down either. it just loops and loops. cant do the rescue thing with the program either.. anybody that knows how i can fix this?
I have an out of topic question regarding this tablet.
Can The Lenovo M10 Plus (2nd Gen) 10.3" TB-X606F Output Display via HDMI to TV ???
I tried using a powered USB-C to HDMI adapter to output/mirror the tablet to a TV, but it didn't work.
Brotinger said:
Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).
Click to expand...
Click to collapse
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.
unlock not possible
CMX939 said:
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.
Click to expand...
Click to collapse
I have the same issue, "waiting for device" and adb dies.
I assume, the latest lenovo updates (Android 9) block unlocking.
The current! LMSA tool does not allow to restore an old separately downloaded firmware
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
ertech said:
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
Click to expand...
Click to collapse
It seems that the bootloader files for OS 6 (TZ and LK) are incompatible with OS 7.3.1.5. I found that you could not even shut down the tablet when it was bootlooping: holding the power button down for >30 seconds did nothing. To stop it you need to open the tablet and disconnect the battery.
You will need to copy a version of OS 6 onto a micro SD card (change the file extension from '.bin' to '.zip'). Insert the micro SD, after reconnecting the battery and putting the rear shell back on. You should be able to boot into recovery (TWRP) with the left volume button/ power button. Wipe system and data then flash the OS 6 zip.
Locate the newer thread for unlocking the HD 8/ 8th gen. tablet (amonet-3) and download the latest amonet version (currently 3.0.1) and the 'return to stock' zip, then follow the instructions in that thread to return to stock. Essentially you unzip the two downloads, merge, and run the return to stock script. From TWRP you boot the tablet into hacked fastboot mode and the script will restore stock boot and recovery images (unpatched). After a reboot you should be able to enter standard Amazon recovery mode. If you then ADB sideload the OS 7.3.1.5 software you will eventually boot into OS 7 (Pie).
Link to 'amonet-3' thread: https://forum.xda-developers.com/showpost.php?p=80166353&postcount=1
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
madman said:
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
Click to expand...
Click to collapse
I've had no luck unlocking the Karnak (or Mustang). I think there a couple of issues. The unlock doesn't work with the OS 7.3.1.5 bootloaders, you get a bootloop. I expected this as it is only the very first version of the Karnak LK file (OS 6.3.0.0) that has the necessary vulnerability for a full unlock. However if you use a modified version of Amonet to flash the OS 7.3.1.5 PL and TZ plus the OS 6.3.0.0 LK you get a bootloop, even without unlocking and unpatched stock boot and recovery images. It may not be impossible, I am hoping that the unlock authors (@xyz` and @k4y0z) will take a look at some point.
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
ertech said:
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
Click to expand...
Click to collapse
OK, if you just want to unbrick it is quite easy. If you have the latest TWRP (you will have if you unlocked with amonet version-3 for thIs tablet) it is likely that your bootloaders are unchanged. To get out of the bootloop you can either disconnect the battery or let it run down. Then you should be able to boot into recovery. From there you can flash a backup of your previous OS, or wipe system and data and reflash a stock OS 6 update.
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.