Related
Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Here are the files you will need -
CONQUER-ROOT.zip
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select the SPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.
2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.
3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.
4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.
5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.
I've created a new custom ROM here - http://forum.xda-developers.com/showthread.php?p=29369141
You can just download the new files and follow those instructions if you haven't installed this yet.
it work like charm thank you very much sir very good job done..........
---------- Post added at 04:47 AM ---------- Previous post was at 04:38 AM ----------
there is any custom rom kool one ...
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
AestenD said:
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
Click to expand...
Click to collapse
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
brienj said:
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
Click to expand...
Click to collapse
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
AestenD said:
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
Click to expand...
Click to collapse
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
tar -H ustar -c adsp.mbn amss.mbn appsboot.mbn boot.img cache.yaffs mibib osbl recovery.img system.yaffs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Click to expand...
Click to collapse
You can replace each package_name with whatever you want it called.
brienj said:
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
You can replace each package_name with whatever you want it called.
Click to expand...
Click to collapse
Thanks for your help, took me a bit, because I mistakenly flashed the non-CWM image first, and the bootloader version just wasn't letting me in. Luckily I have a jig for my SGS2, and I'm up and running now. Hopefully just the fact that it's the full image, rather than OTA upgraded will fix some of the issues she's been having. If not, then having root gives me so many more troubleshooting options.
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
"known issue" just keep going, it'll work just fine.
Sent from my SPH-D710 using Tapatalk
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
i did all the step but when i hit start on the odin it says please connect phones what can else can i do. loaded the drive from super one click because my laptop running windows seven wasn't reading my phone. Its reading my phone I downloaded the usb driver from this link http://r2doesinc.bitsurge.net/leaked/
now when i run odin now it say """an unnamed file was not found""" whats to do please help
brienj said:
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
Click to expand...
Click to collapse
i got the phone to be read but now when i hit the start button a window pops out says "unnamed file is not found"
It worked for me.
Question
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
roofus1812 said:
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
Click to expand...
Click to collapse
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Finished
brienj said:
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Click to expand...
Click to collapse
I just finished backing up my Conquer using this guide. It was really easy. Thanks.
Hi guys. Anyone use tethering with this? I had tethering working on the old rom fine and another unrooted phone with the ota update. I got a replacement phone and tethering does not work. It only works for google sites - with any tethering app i tried. Is it the hardware or maybe its the stock fc17? I tried reflashing and clearing everything and the problem persists.
I tried using Odin today to root my Samsung Conquer and had a bit of trouble. When I attached the .tar file it gave me an error but as I read this thread I just kept going as if there was no issue. About half way through the Odin installation my phone just rebooted, I tried again and it rebooted it the same spot. I tried putting my phone back into download mode and continue the process, which it did, and I got a "Pass" message at the end. But I don't have CWM and I'm almost positive its still not rooted. Any suggestions?
Any chance of an update with the new OTA included?
Sent from my SPH-D710 using xda premium
There is a new ota fe17. Does anyone know if it will break root? Will it install?
Sent from my SPH-D600 using XDA
OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
I was going to write some very insulting message, but i don't want to fill this thread with stupid nonsense, as it is completely obvious that you have no clue what you are talking about... Just a few areas where i'v helped...
http://forum.xda-developers.com/showpost.php?p=38886073
http://forum.xda-developers.com/showpost.php?p=26608802
http://forum.xda-developers.com/showthread.php?p=34381433#post34381433
Yes that is my phone in post 3, as i was the first outside of the team to have a rooted LG optimus G, thanks to TeamCodefire, shellnut2, JCase, AutoPrime, thecubed, and many more that contributed to the lg root evolution. If you have any questions about my integrity, you can ask any of them...
I cleaned the offensive posts and the user was infracted. At the OP, thanks for managing this appropriately and not escalating it to a flame war.
Back on topic please.
These steps are NOT needed... Once you complete step 10 and reboot SuperSU is installed and accessible...
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
This is only a temporary solution for root... Why?
And, the Kingroot and Super Sume method works sometimes to get root without tripping KNOX! This info I also posted in another thread...
This recovery/root method will work for mostly ALL Samsung and Nexus devices that have a working recovery... Thanks to Chainfire for his hard work!
K94U said:
These steps are NOT needed... Once you complete step 10 and reboot SuperSU is installed and accessible...
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
This is only a temporary solution for root... Why?
And, the Kingroot and Super Sume method works sometimes to get root without tripping KNOX! This info I also posted in another thread...
This recovery/root method will work for mostly ALL Samsung and Nexus devices that have a working recovery... Thanks to Chainfire for his hard work!
Click to expand...
Click to collapse
Temporary solution is in the meaning of not fully rooted... This method is systemless, and if you want to make full init.d edits, i would not recommend using a systemless root option, as its kinda like a sudo root, for those that use linux, they will understand what i'm talking about. Yes you can allow root access to apps the request it, but as for full system modifications like the sound mixer, and init.d edits, i don't think i would go there, also not really sure if this will work with debloating, I'm not exactly sure about on samsung how it acts when you remove "system" apps (more so apps installed by default by samsung), I do know that one of the quickest ways to brick a lg is to remove system apps, and if you don't have an unlocked bootloader, as well as custom kernel, during boot, you get a kernel panic if system apps are removed, and in some cases has rendered the device unusable, (nothing an insurance claim couldn't fix tho... lol). Oh, and for the final steps, i actually did have to do them, I had no superuser app in my apps drawer, I attempted downloading from the playstore, and it was the wrong version SuperSU, and kept telling me i needed to update my binary. Then did steps 11-13, and all was nice in the world again, and no more nag about updating binaries, as well as it is the correct apk for the su binary that is flashed in step 10.
fiddy619 said:
Temporary solution is in the meaning of not fully rooted... This method is systemless, and if you want to make full init.d edits, i would not recommend using a systemless root option, as its kinda like a sudo root, for those that use linux, they will understand what i'm talking about. Yes you can allow root access to apps the request it, but as for full system modifications like the sound mixer, and init.d edits, i don't think i would go there, also not really sure if this will work with debloating, I'm not exactly sure about on samsung how it acts when you remove "system" apps (more so apps installed by default by samsung), I do know that one of the quickest ways to brick a lg is to remove system apps, and if you don't have an unlocked bootloader, as well as custom kernel, during boot, you get a kernel panic if system apps are removed, and in some cases has rendered the device unusable, (nothing an insurance claim couldn't fix tho... lol). Oh, and for the final steps, i actually did have to do them, I had no superuser app in my apps drawer, I attempted downloading from the playstore, and it was the wrong version SuperSU, and kept telling me i needed to update my binary. Then did steps 11-13, and all was nice in the world again, and no more nag about updating binaries, as well as it is the correct apk for the su binary that is flashed in step 10.
Click to expand...
Click to collapse
Im currently on 4.2.2 with rooted philz recovery.
How can i get to 5.x? If i use OTA I imagine id loose root.
this trick works ...my tab 4 never looked this better
HELP!!!
Having an issue with my sm-237p . Download mode is not allowing me to flash anything via odin. I am trying to root my tab. Recoveries nor firmware wil flash. it starts but never ,akes progress. please help
A samson sm-T237P is sheeped to Nigeria,the problem is that you cannot make call with it because it is not connected with the network here.
Is there an updated way to do this root? I can't get the files I need to root like this
fiddy619 said:
OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
Click to expand...
Click to collapse
Mjme34 said:
Is there an updated way to do this root? I can't get the files I need to root like this
Click to expand...
Click to collapse
Here's the magic: mega(dot)nz/#F!ZkARSbRI!SV3kQ6jmsi9eGwHoRKPfew
(sry first post.. they have rules against posting web links directly.. replace (dot) with . and you should have your recovery file)
had to do a bit of digging myself. The other files should be easy to find via Google.
fiddy619 said:
OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
Click to expand...
Click to collapse
Can you fix the link to the recovery says 404 not found
g7755725 said:
Can you fix the link to the recovery says 404 not found
Click to expand...
Click to collapse
Just Read the posts before yours, the link is right there.
There's a reason posts are added and not just replaced with new ones. This is only a 2 paged thread, not hard at all to read it all.
g7755725 said:
Can you fix the link to the recovery says 404 not found
Click to expand...
Click to collapse
Updated, but like bodyshop said... look up. No offense tho...
Thanks for this, however I can't get wifi to turn on. I saw mention in another thread about deleting wpa_supplicant.conf and using ODIN to upgrade to PF1 (could only find PH4 but it fails), but neither worked. Does anyone know of a fix?
thank you 403sc softbank
thank you for solution 403sc softbank
i find tools 7 hour
thank you again
Im new to andriod, coming from IOS and my friend thought he could root my device and told me it was similar to jailbreak on IOS. After using odin to install twrp and flash SuperSU.zip onto my device, it will not go past the boot screen and has at the top 'Set Warranty Bit : kernel'. I need to get back andriod here is the situation:
No backups
Team win installed on device (If that helps)
Able to access data via computer and Odin can connect.
I have all my important stuff on a sd card so I was able to recover that
System/bin folder is empty
Samsung Galaxy Tab 2 SM-T719Y
Have downloaded the Firmware
SuperSU root
I just need Android back, so data loss isn't a worry. How can i do this in simple terms - Im a noob.
Will using Odin to install the firmware fix this?
cryoscalpel said:
Im new to andriod, coming from IOS and my friend thought he could root my device and told me it was similar to jailbreak on IOS. After using odin to install twrp and flash SuperSU.zip onto my device, it will not go past the boot screen and has at the top 'Set Warranty Bit : kernel'. I need to get back andriod here is the situation:
No backups
Team win installed on device (If that helps)
Able to access data via computer and Odin can connect.
I have all my important stuff on a sd card so I was able to recover that
System/bin folder is empty
Samsung Galaxy Tab 2 SM-T719Y
Have downloaded the Firmware
SuperSU root
I just need Android back, so data loss isn't a worry. How can i do this in simple terms - Im a noob.
Will using Odin to install the firmware fix this?
Click to expand...
Click to collapse
Yes using odin to flash stock firmware should fix it. Did the kernel message appear after you flashed TWRP or after you rooted? I think maybe you flashed a newer version of SuperSU that tried to modify the kernel. On older SuperSU it just puts binary files in /system/xbin.
Also, you said something about /system/bin being empty... Typically that means your /system partition isn't mounted. Go to Mount and check system, then check your /system partition with the File Manager...you may be able to use it to delete the root binary files and get it to boot.
Hi there,
Its been a long time using the Note 3 since 2013. It had many issue but still carried on. But few days back when weak up in the morning saw the phone was off, though it was in charge full night. When turned it on it stuck in the Samsung glowing logo and nothing after that, it keep showing the same logo until it power is gone. Don’t know what happened that night, it was installing an update by itself or not.
Then google it and no steps helps, used odin and reflash with latest firmware from sammobile but that too didn’t help. I’ve lots of data in internal storage including sms and contacts and pictures. I’ve no issue to throwing off the phone but I cant lost all data in it, it will be a huge loss as just became a father and lots of pics on my new born baby, so you can understand the value.
Can anyone suggest how can I recover the data? Check the attachment for its current state. Thanks in advance.
Is your phone rooted?
Sent from my awesome Galaxy S8+
IamVaibhav said:
Is your phone rooted?
Sent from my awesome Galaxy S8+
Click to expand...
Click to collapse
No nothing at all, its complete stock, only official updates installed regularly.
soumen.sam said:
No nothing at all, its complete stock, only official updates installed regularly.
Click to expand...
Click to collapse
When you tried the official update from sammobile, did you add a PIT file in addition to the stock ROM?
chosenroyal said:
When you tried the official update from sammobile, did you add a PIT file in addition to the stock ROM?
Click to expand...
Click to collapse
I didnt have time to to learn all this. Just followed an instruction how to solve this and did, but no where I heard about PIT file, what is its purpose? all said to flash with just the .md5 file. Please advice. Thanks
soumen.sam said:
I didnt have time to to learn all this. Just followed an instruction how to solve this and did, but no where I heard about PIT file, what is its purpose? all said to flash with just the .md5 file. Please advice. Thanks
Click to expand...
Click to collapse
This is a bit long. I copied the explanation of PIT online.
PIT stands for Partition Information Table (PIT) and as the name suggests these are files which contain partition tables for your Samsung Galaxy Android phones. The PIT file contains all the relevant information for each required partition such as Partition Name, Block Size, Block Count, and other technical information. Every device has different PIT file associated with its stock firmware. Hence a correct PIT file is needed in order to properly flash the stock firmware on your device. Also, if there are two models of a device, say 32 GB and 64 GB, then both will have a different PIT file and you cannot use the PIT of the former with the later or vice-versa.
What does the PIT file do?
ROM (Read Only Memory) is similar to a hard disk on a PC where the information is kept permanently unless changed by the user. PIT file will re-partition the ROM of your device...
---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------
So what's your phone's model number? Is it SM-N900? And does it have 32GB internal storage?
chosenroyal said:
This is a bit long. I copied the explanation of PIT online.
PIT stands for Partition Information Table (PIT) and as the name suggests these are files which contain partition tables for your Samsung Galaxy Android phones. The PIT file contains all the relevant information for each required partition such as Partition Name, Block Size, Block Count, and other technical information. Every device has different PIT file associated with its stock firmware. Hence a correct PIT file is needed in order to properly flash the stock firmware on your device. Also, if there are two models of a device, say 32 GB and 64 GB, then both will have a different PIT file and you cannot use the PIT of the former with the later or vice-versa.
What does the PIT file do?
ROM (Read Only Memory) is similar to a hard disk on a PC where the information is kept permanently unless changed by the user. PIT file will re-partition the ROM of your device...
---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------
So what's your phone's model number? Is it SM-N900? And does it have 32GB internal storage?
Click to expand...
Click to collapse
Ok thanks, yes its SM-N900 32GB internal storage. All I want to fix it without formatting the internal storage. I even dont know after flashing it will clear then internal memory and reset or not. Even if I need the PIT file, then where can I get the stock PIT file? Thanks
soumen.sam said:
Hi there,
Its been a long time using the Note 3 since 2013. It had many issue but still carried on. But few days back when weak up in the morning saw the phone was off, though it was in charge full night. When turned it on it stuck in the Samsung glowing logo and nothing after that, it keep showing the same logo until it power is gone. Don’t know what happened that night, it was installing an update by itself or not.
Then google it and no steps helps, used odin and reflash with latest firmware from sammobile but that too didn’t help. I’ve lots of data in internal storage including sms and contacts and pictures. I’ve no issue to throwing off the phone but I cant lost all data in it, it will be a huge loss as just became a father and lots of pics on my new born baby, so you can understand the value.
Can anyone suggest how can I recover the data? Check the attachment for its current state. Thanks in advance.
Click to expand...
Click to collapse
Are you sure that you downloaded the right firmware for your country/career?
DontBrickYourPhone said:
Are you sure that you downloaded the right firmware for your country/career?
Click to expand...
Click to collapse
Checked all, country latest version exact model and all. Juts now trying reflash with the pit file.
If you want to cpy Data from your internal storage try tihis way
1 install official TWRP recovery
2 Reboot into recovery
3 connect your mobile to Pc annd then you can copy data from your internal storage
Hope it help you ?
you can try this method.
1.Root your phone and install twrp recovery.
2.mound and SDCard and reboot into recovery and from file manager in recovery copy all data from internal storage to SDCard by doing this your data will be safe .after that try to flash anr other rom like Resurrection Remix Or lineage to repair your phone.
Hi, if you flashed (completely) an update not compatible you lost your data, your contacts it`s recommendable to synchronise with Google if worst happen, if your data didn`t go away you can try to recover like others users recommended, first root device with this file https://download.chainfire.eu/353/CF-Root/CF-Auto-Root/CF-Auto-Root-ha3g-ha3gxx-smn900.zip, install official TWRP from Google Play and download from it correct version, go to recovery from same app and transfer to pc all that you can.
Sometime ago I tried to flash a rom with odin and result was the same, and issue was just for flashing without connection to internet, maybe help
Amh00200 said:
If you want to cpy Data from your internal storage try tihis way
1 install official TWRP recovery
2 Reboot into recovery
3 connect your mobile to Pc annd then you can copy data from your internal storage
Hope it help you
Click to expand...
Click to collapse
So after few days I got some time to work on it. I've already took the internal backup by TWRP like whats all etc. I did CWM Recovery and took the full backup and the format and reset. Now the phone turned on and restored the backup by CWM but again its in Boot loop. Now what to do? and yes I think its rooted now.
I only need contacts sms and action memo, thats all
raosahab said:
you can try this method.
1.Root your phone and install twrp recovery.
2.mound and SDCard and reboot into recovery and from file manager in recovery copy all data from internal storage to SDCard by doing this your data will be safe .after that try to flash anr other rom like Resurrection Remix Or lineage to repair your phone.
Click to expand...
Click to collapse
Yes I already took the backup and tried many repair fixing software but nothing helpped
SubwayChamp said:
Hi, if you flashed (completely) an update not compatible you lost your data, your contacts it`s recommendable to synchronise with Google if worst happen, if your data didn`t go away you can try to recover like others users recommended, first root device with this file https://download.chainfire.eu/353/CF-Root/CF-Auto-Root/CF-Auto-Root-ha3g-ha3gxx-smn900.zip, install official TWRP from Google Play and download from it correct version, go to recovery from same app and transfer to pc all that you can.
Sometime ago I tried to flash a rom with odin and result was the same, and issue was just for flashing without connection to internet, maybe help
Click to expand...
Click to collapse
I flashed with proper firmware and when it didnt help I tried CWM recovery and took the backup, while it was taking backup I saw it took all apps those I installed. So I'm sure it didnt format the data.
soumen.sam said:
I flashed with proper firmware and when it didnt help I tried CWM recovery and took the backup, while it was taking backup I saw it took all apps those I installed. So I'm sure it didnt format the data.
Click to expand...
Click to collapse
Well, we need to make things clear to try to solve this;
Assuming that you;
- Flashed correct firmware and for some reason process interrupt or apparently reached the end but device don´t boot (bad flashing)
- You took a backup from CWM nor TWRP (then you have a backup of system, data, boot, maybe recovery and probably cache. Then you can try the next:
- Put your backup ever in sdcard
- Flash some custom rom based on stock (zip format) with CWM (maybe necessary to do wipes to boot but probably you lost your data from device flashing before, but you have it in your backup)
- Now select an advanced restore, just restore data (if same native app of mms and notes are installed they took data again), reboot now and look, probably will be necessary restore also cache but let it just if needed)
- If for some reason don´t boot probably your partitions are corrupted but you can try first this. I hope help you and tell us how you go
SubwayChamp said:
Well, we need to make things clear to try to solve this;
Assuming that you;
- Flashed correct firmware and for some reason process interrupt or apparently reached the end but device don´t boot (bad flashing)
- You took a backup from CWM nor TWRP (then you have a backup of system, data, boot, maybe recovery and probably cache. Then you can try the next:
- Put your backup ever in sdcard
- Flash some custom rom based on stock (zip format) with CWM (maybe necessary to do wipes to boot but probably you lost your data from device flashing before, but you have it in your backup)
- Now select an advanced restore, just restore data (if same native app of mms and notes are installed they took data again), reboot now and look, probably will be necessary restore also cache but let it just if needed)
- If for some reason don´t boot probably your partitions are corrupted but you can try first this. I hope help you and tell us how you go
Click to expand...
Click to collapse
Thanks for your feedback. Yes I backup from CWM full system data and all and TWRP I took internal storage backup in PC.
I flashed with latest firmware from sammobile with Odin
I restore the backup in all way, full restore, only data and other one by one, but in all steps its unable to turn on again. I saw the internal memory data is intact but contact call log and sms r gone. I just waht these 3 things, snote is still there.
How do I know my phone is rooted? if I rood can I overwrite these data from the backup files? I installed two file manager but cant access the root. Please let me know. Thanks
soumen.sam said:
Thanks for your feedback. Yes I backup from CWM full system data and all and TWRP I took internal storage backup in PC.
I flashed with latest firmware from sammobile with Odin
I restore the backup in all way, full restore, only data and other one by one, but in all steps its unable to turn on again. I saw the internal memory data is intact but contact call log and sms r gone. I just waht these 3 things, snote is still there.
How do I know my phone is rooted? if I rood can I overwrite these data from the backup files? I installed two file manager but cant access the root. Please let me know. Thanks
Click to expand...
Click to collapse
If device don`t power on you need first of all flash correct firmware to repair partitions, you need to go step by step.
- Flash by odin, good level battery charged, access to internet, depending capacity of your pc don´t use many resources meanwhile flashing, if sucess reboot device completely now power off, put it in download mode
- Now, step 2 you need to root with this file, download it https://download.chainfire.eu/353/CF-Root/CF-Auto-Root/CF-Auto-Root-ha3g-ha3gxx-smn900.zip extract from zip and you have this file in .tar.md5, open odin, go to AP box, search file and flash it (download mode), this file will root device and will install TWRP (is needed to inject some scripts from supersu)
- how your backup is in CWM you need to go now to TWRP and flash CWM.img file via recovery.
- reboot in CWM and select advanced option to restore, just restore DATA, not other partitions, this overwrite your data app for your data backup, and without doing wipes try to boot. maybe system be unstable but you need now just recover some data, when you do that recommend a flash a custom rom or at least keeping root to take a backup with titanium periodically
Hi All, So with the rooted device I've managed to restore all data except call log, which I can ignore. But now the issue is, the system showing the software is not official and not supporting software upgrade and showing the system is custom. Now what to do, where can I get the exact firmware? thanks
sammobile or updato dot com or just search .
I'm seeing so many different posts. Is it rootable or not? I wanna purchase the device but don't want to not be able to root it. Please let me know directly. I'm tmo btw
Got it already, on launch. It's fair, no real stutters at all, quick, but smooth(so don't mess with settings in developer options "drawing" section. There used to be a way, you could build, or "nominate", a twrp for your phone. I don't see that option anymore, just statistics. I'd like a twrp blog.
reggjoo said:
Got it already, on launch. It's fair, no real stutters at all, quick, but smooth(so don't mess with settings in developer options "drawing" section. There used to be a way, you could build, or "nominate", a twrp for your phone. I don't see that option anymore, just statistics. I'd like a twrp blog.
Click to expand...
Click to collapse
I am reading this comment AFTER I replied to your other on a different post and am realizing that your comment was NOT butchered and you DID indeed mean "builder". You can disregard the second half of my comment on that reply because it assumes you meant "build" and an actual "builder" which I had never even heard of. To that note, that actually would be great if there was still one around to utilize for this phone. A TWRP build is much needed to deal with the update problem I am having. The latest update in Lenovo Rescue does not provide the update since it is the same version number. The boot image can not be patched because they are actually different. I guess I can try my hand at capturing the download file if I only knew where it saved it.
There's an experimental build of TWRP for the Edge (NON +). I haven't tried it personally. Mine is BL unlocked and not rooted with Magisk patcher.
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
bronkish said:
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
Click to expand...
Click to collapse
Could you lay out the process in detail, or link us to an existing step by step with the correct download(s) that will work for the Edge? I'd really like to root but want to minimize my chance of creating a brick. Thanks!
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Hi,
could you please give the commands you used?
I have completed steps 1-5
I am not sure how to complete step 6
I have the magisk_patched_j5iak.tar file (there is a bot.img file in the archive)
Should I unpack the created magisk_patched_j5iak.tar file?
Please help
Umm, tell you what - try it both ways and then you'll know.
6: your phone is in fastbootd (I told you how to get there) and you flash the boot.img file that you just patched in magisk.
@bronkish Thanks again! I now have my beloved Titanium Backup again! It's been so long since I was rooted I'm going to have to see what else is available again.
[Edit]
Titanium looks a bit dated. Is there a better app now for doing what titanium did?
Rock ON!! SO many "I's" to follow....
I use to use Titanium (pro), too. Today I just export data from apps (settings, really) and I host a nextcloud server - which is handy as fuk (add a calendar event, or contact, on my phone, it's on my server, too, and vice-versa): I can 'share' dumps (exported nova settings, say) and data to nextcloud and if I take a picture 'in the field' it is immediately uploaded to my local nextcloud server and deleted (optional) from my phone. One can achieve all manner of function with nextcloud.
I restore and sync my calendar and contacts from nextcloud (dav), call log from sms backup & restore, which works great - although titamium, 3C, and others do the same.
I do keep handy an apk of every app I like to have installed on my phone, which, really isn't that many. I sometimes use app manager to export apks, or I use FX file manager. I use 3C to backup apps/data. I restore few apps/data with it. 3C can import titanium dumps, as well. I have less need for app/data dumps these days, though. DOn't care at all about twrp, but I'd be more inclined to use the twrp and full system dump restore methodology, as in the past, than using an app like titanium or 3c which requires setting up the phone again first, flashing or installing the app and then restoring apps/data - in this scenario a google account is required for some apps to function again (3c restore) or market links are broken as is handy to do in titanium. A restore from a twrp dump negates all this. You could also use adb for system level (phone) dumps/restore; it's fast and easy.
What do you need to backup? Why? Can you use app exports and a cloud or SD card or some connection to a server/desktop/drive? Can you employ dav? DO you even generate data worthy of backing up?
phone logs
firewall settings (as an example of app settings)
apps/apks in order to achieve function, if you even need to have them handy
texts (if you save them, I use signal and export a text dump to a folder on my sd card, if I even do, which is rare)
contacts, if you don't use google, or whatever
calendar
any important or usable generated data, apps likely have dump scenario
Like anything, there are myriad ways to accomplish the task.
If I'm gonna wipe or reset my phone I have common immediate dumps on my sd card (of course, the phone must have the slot). So, on my card is a folder with some app settings for a quick restore. AFWall settings are there. I have notification sounds and whatnot on the sd root so the phone picks them up. There's a contacts file and calendar file in the dump folder in case I'm near no network when restoring, which, would be odd. There's a couple text dumps, too. Hell, one is 2 years old - why do i keep it? lol.
Also on the card is a key file I use with keepassx as well as a keepass database dump, in case I need it - it's old but has what I need to 'start from scratch' if necessary. I typically just open the keepass dump from nextcloud I just reinstalled from the apk and bam, keepass opens on my phone with my thumb - fuk'n handy. The sd card dumps are just jump-starts if necessary, like, no networking, or something. But, they are there because they would be sorely missed if they were not.
I keep from setting up a google account on the phone for as ong as I can - everything restored, firewall tight, apps frozen, snuffed, or otherwise mitigated. I set the google account up to check fo app updates and for that pain in the ass poweramp which needs to hit the playstore every time it's reinstalled. Pfft. The sd maid and fx file manager apps are so much better to restore because no need for google to validate the purchase.
pffft.
bronkish said:
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Click to expand...
Click to collapse
After doing all of this I'm stuck on the Motorola boot screen. Is there any way to fix this?
bronkish said:
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
Click to expand...
Click to collapse
Question what update is that mine is the same XT2063-2 except mine reads QPDS30.114-80-2
Mine, too.
adbman said:
After doing all of this I'm stuck on the Motorola boot screen. Is there any way to fix this?
Click to expand...
Click to collapse
FastbootD
I gave instructions.
I don't mean to be a rude necromancer of posts but, I know nothing of these... tar files you speak of. I tried to do some homework and I see .tar.md5 and .tar.gz. Question 1: Does it make a difference? Is there a post somewhere I can learn from?
Question 2: How does one, or what software is available to, perform this work?
Respectfully,
Me
tar.md5 or, anything.md5 is just a text file containing the md5 hash of the file. You need or want it only if and when you do - if you don't know, then you don't. A .tar file is an archive like a .zip file. a tar.gz, or, .tgz is a compressed tar archive. tar only makes an envelope for the file(s), it doesn't compress unless you tell it to. There's lots of compression schemes - leave all that alone unless you wanna get back to it later. Magisk needs a .tar archive with the boot.img file in it - let's root
Rooting, with stock recovery, is just a couple simple steps. Magisk really makes it easy.
1 - get the firmware and extract it. You'll need the boot.img file.
2 - make an archive (*.tar) to contain the boot.img file. So, on linux, in a terminal, cd into the extracted firmware directory, do: tar -cvf boot-for-magisk.tar boot.img
windows user do your thing. I got a right-click, I don't even know anymore, check my command.
3 - drop that archive you just made onto your phone for magisk to use
4 - get and install magisk , the apk is fine
5 - open magisk. Top section, choose to install (touch the word: install), in next screen, choose select and patch file - feed it the tar achive you made of the extracted boot.img. point to the .tar file. do it.
Magisk will do its thing to the boot image and will spit out a new one that you can install to take advantage; to have root. Wicked. I copy it back to my computer for fastboot action. DO it - copy the new boot image that magisk generated to your computer.
6 - boot your phone to fastbootD - listen....plug your phone into your computer - usb-c cable.
reboot to recovery. In a terminal, do: fastboot devices <return> to check for your phone.
in recovery, press the power button for 3 seconds - at 3(onethousand), press the vol up button as well, for 2 more seconds
after you count 5, release the buttons and you should see a new menu - one of the items says to enter fastboot - that is fastbootD. If you attempt the power and vol up button task and it doesn't work, do it again - it works. SOmetimes it takes a time or 2 to catch it right. In any case, enter this fastboot. one onethousand...
FastbootD!
now, back in your terminal, flash the new boot image that magisk made for you. So: fastboot flash boot FILENAMEOFNEWBOOTIMAGE.img
following the successful flash, enter: fastboot reboot in your terminal - you may unplug your phone.
Success!
bronkish said:
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Click to expand...
Click to collapse
I remembered how you got to the firmware
Click this link thing down below the here.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You'll be rooted in no time. Careful, now.