Related
Hi,
So I'm new to these forums and have been browsing all of the rooting guides for my HTC M8. I am running official Marshmallow and really want to root my phone (again) as far I know I have unlocked boot loader. I had to factory reset my phone last year and never got round to re rooting, but now with marshmallow I wish to do so again.
My issue is I can't seem to understand the steps the guides are outlining. I download the links and try and open them, but nothing happens. Is there a step by step fluid guide in rooting my phone? As all the guides I have found have basically blown over my head. I used a toolkit in the past which did everything for me automatically. If no such post exists would someone be able to explain the steps in a simplified manner? (If possible)
Many thanks in advance to any who help
Optcpsi said:
as far I know I have unlocked boot loader
Click to expand...
Click to collapse
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
redpoint73 said:
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
Click to expand...
Click to collapse
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Schmix said:
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Click to expand...
Click to collapse
You need to allow modifications for root. At least traditional root. Systemless root, I would think would work if you stay read only - but do the research especially if you don't know the difference between traditional root and systemless root.
You can't install OTA updates with a rooted device in any case, so that point is irrelevant.
If/when ever an OTA comes, you would need to return to stock never rooted ROM and stock recovery, in order to OTA update (there are guides on this forum). This would remove any modification by TWRP.
But that's mostly just FYI/academic. Its extremely unlikely we'll get an OTA update to Nougat. Your best bet for Nougat will be custom ROMs, anyway.
1. UNLOCK bootloader with HTC Dev site.
2. Flash latest twrp recovery
3. Flash Stable v2.65 SuperSU
4. Flash wp mod.
5. Update SuperSU on Play Store.
Latest SuperSU 2.76 zip kills Boomsound. Permissive zip can fix that.
Hello. I'm pretty terrible at all this rooting stuff (or at least, I only do it once for each android phone I get, and then don't really look into it or stay up to date on all of it afterwards, I just use a few pluses that come along with being rooted).... Anyways, I really do need some help this time, as the confusion has really gotten to me, and I've lacked being able to find some simple answers (probably because they are just THAT simple) on google/reddit/on this forum.
Anyways, I've rooted my phone awhile back, lost it when my verizon pixel auto updated to 7.1.1 (idk how or why, pretty sure I had that disabled with root even, very frustrated) and even attempted to regain root by flashing SU with TWRP, but for some reason SU said I didn't have root still, and eventually just gave up in frustration. But now, my verizon pixel has been shutting off at ~40% battery power, and I read in the google forums that this was patched in the 7.1.2 update for pixels, and it was a software glitch rather than a malfunctioning/bad battery... So now I really want to upgrade to 7.1.2 from 7.1.1 not only to fix the battery/software issue, but also because I really want root.
I have an unlocked bootloader from when i first got my pixel and did this stuff, but now im unrooted on 7.1.1 because of that update awhile back, and want to update to 7.1.2 and root, but I've heard theres issues with rooting on the verizon because of bootloader, but that shoulden't be an issue since I unlocked it already (right? at least, I think? please let me know).
My only question (since i think i'll be able to follow this guide once I get the answer to this) is in the post he says: "Works with 7.1.2 (NJH47F, Aug 2017)".......... but since i have the verizon pixel (small version, not XL), should i be downloading this version: 7.1.2 (NHG47Q, Aug 2017, Verizon).... Or would it just be acceptable to allow my phone to auto download the update i have on it right now? Or must I download the NON verizon version as stated in the post and flash that one? Thanks for the help guys!
Thanks for any help!
-Synk
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
jhs39 said:
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
Click to expand...
Click to collapse
Thank you so much for the explanation. Truly, it's actually crazy how I was unable to find all of this neatly, nicely, and simply stated. Great to hear, I'm going to go on rooting, here's to hoping I don't blow it up.
Hi,
My HTC 10 is rooted, S-On, SU, boot loader unlocked, and running stock Nougat 7.0. As such, it doesn't get onlver the air {OTA}. I want OREO, and I understand that requires me to unroot. How do I unroot?
I hope to do an OTA and then reroot. If I really don't have to unroot, tell me please what to do to get OREO. My main attraction to rooting is to install AdAway.
Thanks,
Ndmand
These are what I did;
1. restore my stock rom via TWRP (which I backed-up long time ago)
2. flash back stock recovery (which I found form XDA). It will replace TWRP
3. OEM relocked
By then, I could get couple OTAs until I reach to Oreo.
After that, I went all the ways again => unlock bootloader (HtcDev) => flash latest TWRP => and so on.
Ndmand said:
Hi,
My HTC 10 is rooted, S-On, SU, boot loader unlocked, and running stock Nougat 7.0. As such, it doesn't get onlver the air {OTA}. I want OREO, and I understand that requires me to unroot. How do I unroot?
I hope to do an OTA and then reroot. If I really don't have to unroot, tell me please what to do to get OREO. My main attraction to rooting is to install AdAway.
Thanks,
Ndmand
Click to expand...
Click to collapse
You really only need steps 1 and 2 from bita's post. If you don't have a stock system backup you can probably find one in the Backups thread.
Else, you can flash an ruu which will take you back fully stock but will also wipe your phone in the process.
bita said:
These are what I did;
1. restore my stock rom via TWRP (which I backed-up long time ago)
2. flash back stock recovery (which I found form XDA). It will replace TWRP
3. OEM relocked
By then, I could get couple OTAs until I reach to Oreo.
After that, I went all the ways again => unlock bootloader (HtcDev) => flash latest TWRP => and so on.
Click to expand...
Click to collapse
Thank You,
This is exactly what I need. I interpret "OEM relocked" to mean that after flashing, you system was relocked, and you didn't have to separately relock your bootloader. I appreciate your help.
Ndmand
Tarima said:
You really only need steps 1 and 2 from bita's post. If you don't have a stock system backup you can probably find one in the Backups thread.
Else, you can flash an ruu which will take you back fully stock but will also wipe your phone in the process.
Click to expand...
Click to collapse
Great, Thank You, Tarima,
Oddly, I was hoping you'd see my post because if the great help you have given to others. I deleted my stock backup by mistake last year.
My TWRP and Titanium backups are on an SD card, so I will remove the card to protect them during the process in case things go crazy.
I noticed that SU has an unroot button, but I guess that only covers part of the process.
Thank You,
Ndmand
Ndmand said:
Great, Thank You, Tarima,
Oddly, I was hoping you'd see my post because if the great help you have given to others. I deleted my stock backup by mistake last year.
My TWRP and Titanium backups are on an SD card, so I will remove the card to protect them during the process in case things go crazy.
I noticed that SU has an unroot button, but I guess that only covers part of the process.
Thank You,
Ndmand
Click to expand...
Click to collapse
No problem. Yes, once you root with superSU, your system partition will be flagged permanently as modified even if you unroot. That's why you need to flash a virgin system backup image. This is also why I root with Magisk, as it makes taking OTA much easier. You may want to consider that as well when you root again.
I don't quite understand Magisk yet, but I will look into it. Thanks for making this doable and understandable.
Ndmand
Do a RUU and update ota , no need to relock bootloader, you will lose data if you do RUU
Which RUU is the right for the Oreo OTA?
I have installed the developer version, but I haven't received it. Also I knew that HTC had removed the OTA
Enviado desde mi HTC 10 mediante Tapatalk
oxineitor said:
Which RUU is the right for the Oreo OTA?
I have installed the developer version, but I haven't received it. Also I knew that HTC had removed the OTA
Enviado desde mi HTC 10 mediante Tapatalk
Click to expand...
Click to collapse
U.S Unlocked has not yet received OTA. To go to Oreo you'll have to run the RUU.
Take the RUU posted by santod on this page:
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page254
Newbie Here
Hi guys,
For several years now I've been getting help from you people and for that I am very appreciative. This is my first, of what I hope are many more posts.
I recently purchased a Sprint HTC 10 phone here in the Dominican Republic. It was factory unlocked already. It came with stock Oreo software. Yesterday I received an Oreo update, and this immediately locked my phone sim. I couldn't use it. Now thanks to you guys, I slept like at 1 am, but finally managed to get the phone unlocked thanks to this thread.
Now I have a problem. I'm not that of a techie guy to leave the phone rooted. Is it wise to unrooted back again? My main concern is, if I unroot the phone it will revert to having the sim lock, and that's a no go. So my question is: Do I unrooted? Can I, without damaging the phone? And if the answer is no, how do I proceed with my rooted phone to get the best out of it? I saw this video on youtube, it seems nice, but it is from 2015. Do I follow those steps or do something else to take advantage of my rooted device.
I would really appreciate your help.
Yank1llaz said:
Hi guys,
For several years now I've been getting help from you people and for that I am very appreciative. This is my first, of what I hope are many more posts.
I recently purchased a Sprint HTC 10 phone here in the Dominican Republic. It was factory unlocked already. It came with stock Oreo software. Yesterday I received an Oreo update, and this immediately locked my phone sim. I couldn't use it. Now thanks to you guys, I slept like at 1 am, but finally managed to get the phone unlocked thanks to this thread.
Now I have a problem. I'm not that of a techie guy to leave the phone rooted. Is it wise to unrooted back again? My main concern is, if I unroot the phone it will revert to having the sim lock, and that's a no go. So my question is: Do I unrooted? Can I, without damaging the phone? And if the answer is no, how do I proceed with my rooted phone to get the best out of it? I saw this video on youtube, it seems nice, but it is from 2015. Do I follow those steps or do something else to take advantage of my rooted device.
I would really appreciate your help.
Click to expand...
Click to collapse
The only downside to being rooted is that you won't be able to take OTA updates any longer, or use certain apps that don't work with rooted devices (mostly banking apps). I'm almost 100% sure we won't get any more OTA updates for this phone, so unless you really need to use banking apps, I would leave the device rooted. Plus there are some nice things you can do while being rooted.
If you're rooted with Magisk you can still do all of the above.
Tarima said:
The only downside to being rooted is that you won't be able to take OTA updates any longer, or use certain apps that don't work with rooted devices (mostly banking apps). I'm almost 100% sure we won't get any more OTA updates for this phone, so unless you really need to use banking apps, I would leave the device rooted. Plus there are some nice things you can do while being rooted.
If you're rooted with Magisk you can still do all of the above.
Click to expand...
Click to collapse
Thx Tarima. If so, what can I do with a rooted device? What are my inmediate options to upgrade the phone. Any ideas?
I thought you could take OTA?
I am WAY out of the info as I don't take them, but I'll search a little an come back with any findings.
andybones said:
I thought you could take OTA?
I am WAY out of the info as I don't take them, but I'll search a little an come back with any findings.
Click to expand...
Click to collapse
Unless you're rooted with Magisk systemless root, you can't take OTA from a rooted state until you restore a stock system image, which I'm thinking might undo the SIM unlock procedure the OP had to do on his Sprint device.
---------- Post added at 02:43 AM ---------- Previous post was at 02:35 AM ----------
Yank1llaz said:
Thx Tarima. If so, what can I do with a rooted device? What are my inmediate options to upgrade the phone. Any ideas?
Click to expand...
Click to collapse
That's what I was saying, there will 99% for sure be no other updates for this phone, so that's a non-issue. And if there is, you can run an RUU, return to stock, take the update, then do the sim unlock procedure again.
I do with root:
- Use Titanium Backup (great app backup app)
- Use F.lux app for blue light reduction
- Use Adaway ad blocker
Tarima said:
I do with root:
- Use Titanium Backup (great app backup app)
- Use F.lux app for blue light reduction
- Use Adaway ad blocker
Click to expand...
Click to collapse
Process for those. Sorry for being such a pain in the behind.
Yank1llaz said:
Process for those. Sorry for being such a pain in the behind.
Click to expand...
Click to collapse
What do you mean by "process for those"? They're apps, you just install them from the play store
Actually I think Adaway needs to be downloaded from their own site
Tarima said:
What do you mean by "process for those"? They're apps, you just install them from the play store
Actually I think Adaway needs to be downloaded from their own site
Click to expand...
Click to collapse
Downloaded the one for blue light. How about the adaway one? When dowloading the files within the app, it does not allow me and reads:
"copying of host file failed"
Yank1llaz said:
Downloaded the one for blue light. How about the adaway one? When dowloading the files within the app, it does not allow me and reads:
"copying of host file failed"
Click to expand...
Click to collapse
Sorry not sure about that, you'll have to ask in the appropriate forum.
I was trying to root/custom rom/etc in a hurry and I was interrupted a million times, so I screwed up. SM-N910v. I started out on kitkat, 4.4.1. I tried this guide: https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
I odin N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5. That upgraded me lollipop 5.5.1. I then follow a guide similiar to this: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Its not the exact one, but there is several guides that are the same. I temporary rooted with kingoroot, installed TWRP. One of the guides said not to let it boot normally, so I freaked out and made sure I didn't do that. I booted back into twrp. Using this guide: https://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I can't remember or find the exact guide I was on... But I flashed these files in the following order:
BETA-SuperSU-v2.71-20160331103524.zip
Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip (this was really dumb)
cm-13.0-20160919-UNOFFICIAL-trltevzw.zip
I tried to boot, I left it on for atleast 30 mins, and the clockworkmod logo kept animating abnormally fast.
I then installed N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 again (... doh ...).
Now it bootloops.... so I said.. 'ok, maybe I just need my TWRP recovery back'. Tried to install TWRP and fail....
I can boot into safe mode fine, but not normal mode. The problem with safe mode is you can't install apps.
I've tried factory reset, wipe cache, dalvik, etc etc. Nothing. I've also tried a different firmware I believe as well.. I am lost...
Current Android Info:
5.1.1
security patch level: 2015-12-01
baseband version: N910VVRU2CPD1
Kernel version: 3.10.40 Jan 20 2016
Build Number: LMY47X.N910VVRU2BPA1
The information above indicates that I am still in this version: N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Ok so.. I just odin this file N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5
Same story, I can boot into normal mode, but not safe mode.
I check my info:
5.1.1
security patch level: 2015-12-01
baseband version: N910VVRU2BPA1
Kernel version: 3.10.40 Jan 20 2016
Build Number: LMY47X.N910VVRU2BPA1
Factory reseting now... and seeing if that fixes my problem... nope... same bootloop problem...
my thinking is... if I undo "samsung_unlock_n4-fix" and that would fix my bootloop. If thats true..... I guess my biggest question is: if the boot loader is unlocked, then why can't I flash TWRP like I was able to the first time??
I appologize, I will be unaviable for the next 5 or 6 days..... any help would be much appreciated!
I followed Max Lee's guide on youtube for rooting/unlocking the bootloader I recommend downloading the files he has linked, just ensure that your phone is the SM-N910V the hardest part or more time consuming part is getting kingo root to get you that temporary root needed to unlock your bootloader/root phone. Kingo root is very unstable and your phone will freeze/restart many times, You definitely need a spare sd card, at least a 2GB from my experience and patience, set aside a few hours because your follow through is crucial. If all goes well you will be able to install TWRP. I hope this helps. Tip, if you decide to follow his method, the file titled 'samsung_unlock_n4-2' you need to rename it to say 'samsung_unlock_n4-fix' good luck!
UmbrellaTakedown said:
I followed Max Lee's guide on youtube for rooting/unlocking the bootloader I recommend downloading the files he has linked, just ensure that your phone is the SM-N910V the hardest part or more time consuming part is getting kingo root to get you that temporary root needed to unlock your bootloader/root phone. Kingo root is very unstable and your phone will freeze/restart many times, You definitely need a spare sd card, at least a 2GB from my experience and patience, set aside a few hours because your follow through is crucial. If all goes well you will be able to install TWRP. I hope this helps. Tip, if you decide to follow his method, the file titled 'samsung_unlock_n4-2' you need to rename it to say 'samsung_unlock_n4-fix' good luck!
Click to expand...
Click to collapse
I appreciate your post. However I don't think you quite understand whats going on.
https://galaxynote4root.com/cwmtwrp-recovery/
His site specifically states: "Verizon SM-N910V unless you have a developer’s edition phone as retail version come with locked bootloaders meaning you cannot install regular CWM or TWRP!!!"
It also shows that comment in the video. I definitely DO NOT have the developers edition.
In summary: I flashed the firmware that has the bootloader unlock vulnerability->Installed twrp->Installed CWM->Installed Firmware with bootloader vulnerability, which replaced everything I did. Now it seems like the bootloader is re-locked, and I can't boot into normal mode, which means I can't run kingo again. I can't flash TWRP, the only things I can do are: adb sideload, odin, boot any 5.1.1 in safe mode.
TouchOdeath said:
I appreciate your post. However I don't think you quite understand whats going on.
https://galaxynote4root.com/cwmtwrp-recovery/
His site specifically states: "Verizon SM-N910V unless you have a developer’s edition phone as retail version come with locked bootloaders meaning you cannot install regular CWM or TWRP!!!"
It also shows that comment in the video. I definitely DO NOT have the developers edition.
In summary: I flashed the firmware that has the bootloader unlock vulnerability->Installed twrp->Installed CWM->Installed Firmware with bootloader vulnerability, which replaced everything I did. Now it seems like the bootloader is re-locked, and I can't boot into normal mode, which means I can't run kingo again. I can't flash TWRP, the only things I can do are: adb sideload, odin, boot any 5.1.1 in safe mode.
Click to expand...
Click to collapse
I did not have a developers edition either, I have retail, this method makes your phone into the developer edition. This method is designed for verizons note 4. So what i'm saying is, I followed his method using a retail note 4 branded verizon and this exploit makes it into a developers edition so you may install twrp and roms. You are able to odin flash stock firmware for marshmallow and then downgrade to 5.1 to run max's method.
Ok so.. I managed to get everything working... so I'm happy. Thank you UmbrellaTakedown for invoking thought and thank you for replying, your the only person who replied, so much appreciated!
1. Boot into safe mode
2. Install app by: adb install c:\kingoroot.apk
3. At this point, its installed but the launcher needs to be refreshed for the icon to show up. I don't know how to refresh the launcher without a reboot.. so...
4. Find the kingoroot package name: adb shell 'pm list packages -f'
5. In my case it said: package:/data/app/com.kingo.root-1/base.apk=com.kingo.root So your answer is: com.kingo.root
6. Now in order to launch kingo, you need to find the activity of the package: adb shell pm dump PACKAGE_NAME | grep -A 1 MAIN
7. Start the activity: adb shell am start -n com.kingo.root/com.kingoapp.root.MainActivity
From here I was able to temp root through kingo, and run samsung_unlock_n4-fix. This time I had to only run samsung_unlock_n4-fix once. After that, TWRP installed no problem (where before it would not).
Update:
I am now officially on Jasmine ROM marshmallow. I had to copy the jasmine folder to /data/media/0/TWRP/BACKUPS/xxxx/jasmine
xxxx= you get that from adb devices
Then simply do a restore, after restore, restore the partial firmware file (it has to be done in that order or else it won't work)
TouchOdeath said:
Ok so.. I managed to get everything working... so I'm happy. Thank you UmbrellaTakedown for invoking thought and thank you for replying, your the only person who replied, so much appreciated!
1. Boot into safe mode
2. Install app by: adb install c:\kingoroot.apk
3. At this point, its installed but the launcher needs to be refreshed for the icon to show up. I don't know how to refresh the launcher without a reboot.. so...
4. Find the kingoroot package name: adb shell 'pm list packages -f'
5. In my case it said: package:/data/app/com.kingo.root-1/base.apk=com.kingo.root So your answer is: com.kingo.root
6. Now in order to launch kingo, you need to find the activity of the package: adb shell pm dump PACKAGE_NAME | grep -A 1 MAIN
7. Start the activity: adb shell am start -n com.kingo.root/com.kingoapp.root.MainActivity
From here I was able to temp root through kingo, and run samsung_unlock_n4-fix. This time I had to only run samsung_unlock_n4-fix once. After that, TWRP installed no problem (where before it would not).
Update:
I am now officially on Jasmine ROM marshmallow. I had to copy the jasmine folder to /data/media/0/TWRP/BACKUPS/xxxx/jasmine
xxxx= you get that from adb devices
Then simply do a restore, after restore, restore the partial firmware file (it has to be done in that order or else it won't work)
Click to expand...
Click to collapse
Just an FYI, you need to run the sasmung_unlock_n4 application twice. The first time, it will write your eMMC CID to the correct one, and the second time you execute, it will write the CID signature/blob to the bootloader - completing the unlock process. Glad to see you got it working.
Bought this to replace an LG V20. Was really looking forward to transferring everything using Swift Backup but it requires root access. Googled for a guide or instructions but nothing. Kingo Android Root gives me Connection Server Failed, and KingRoot gives me no option to even perform the operation. Need some help here since root access opens up many of the apps that I use. Thank you!
You need to extract the boot image from an OTA, patch it in the Magisk app, and then fastboot flash boot.img after unlocking the bootloader.
Is it that easy? I got one a month back. I got the android 11 update and now it’s time to root. i have heard it was tough to root but I just really started checking for a good clean process.
pdnorman said:
Is it that easy? I got one a month back. I got the android 11 update and now it’s time to root. i have heard it was tough to root but I just really started checking for a good clean process.
Click to expand...
Click to collapse
Yes, it shouldn't be that hard. As long as full OTAs can be found, and the bootloader can be properly unlocked, it should just work. Lmk
NateDev said:
You need to extract the boot image from an OTA, patch it in the Magisk app, and then fastboot flash boot.img after unlocking the bootloader.
Click to expand...
Click to collapse
Not possible. Every single update so far is a patch update that only comes with parts of files. No update so far has given the ability to get a full boot.img to patch, hence why there's no root. I have downloaded every update so far, so far no full boot.img
Also, at least on US models, there's zero ways to unlock the bootloader. I contacted their customer service about it and they stated they don't give out info on how to unlock it