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.
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
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Lipticon said:
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Click to expand...
Click to collapse
Ok so you don't say what firmware you had and which one you want to flash., there are lots of firmware for the G930. You can download them from several places , sammobile, SamFirm Tool and updato.com.
Use the latest version of Odin if you want Oreo, preferably unbranded.
With regard to Samsung health, this app will not work on a rooted device, just like banking apps, network provider apps and any other app which hold personal info.
Lipticon said:
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Click to expand...
Click to collapse
As @cooltt said use SamFirm tool (search it on google, it's here on xda) and download the latest firmware for your variant (ex. SM-G930F if you own the international S7 flat).
Flash with odin. Make sure you put all the files in the right tabs.
Let the phone boot completly (until the tutorial shows up, if you used the CSC file instead of the HOME_CSC one)
To be able to use SHealth you will need to edit the build.prop. To do so:
1) flash twrp
2) boot to twrp and wipe data (you will loose everything you have in the internal storage so make a backup)
3) Reboot to recovery (twrp menu > reboot > recovery)
4) Flash Magisk 18.1
5) Reboot to system and wait until the phone boots (it may take 5-10minutes)
6) Set up everything and go to play store. Download BuildProp Editor
7) Open BuildProp Editor and make sure you grant it superuser access in Magisk
8) Search for the property: ro.config.tima and set its value to: 0
9) reboot the phone and you should be good to go.
If you want OTAs you will need to 1) uninstall magisk and 2) wait until the next update is released and flash it with odin using the HOME_CSC file.That will revert the kernel to its original state (non-rooted), the recovery to the stock one and the system and binary status to Official (which will allow you to receive OTAs once again)
Sent from my SM-G930F using Tapatalk
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
ewingr said:
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
Click to expand...
Click to collapse
Rooting is 'full', just that technology (Android 9/10) is changing.
For AdAway app you must enable Systemless hosts (option/module in Magisk Manager), for modules Magisc automatically handles symlinking to the read-only System
So, even from root explorer (sugested MiXPlorer), you see as if AdAway wrote directly to the file system/etc/hosts, or that BusyBox tools are applied directly to system/xbin
Since EMUI 8, Huawei replaced Boot with Ramdisk, and since EMUI 9.1 Ramdisk is also read-only, hence Magisk must patch to Recovery instead
Because of that, you cannot have TWRP if you go for root (don't consider an alternative solution to flash TWRP over erecovery). But formally speaking, TWRP is not part of root (on the old systems, you could have TWRP without root, vice versa, or both). Even with TWRP, TWRP could not change read-only System, and it cannot see dynamical linking active only when system is running (Magisk running). Plus, because of new encryption since EMUI 8, TWRP cannot handle Internal storage (don't consider alternative solution to completely wipe Internal storage and format it without encryption)
All together, from system, systemless works fully seemlessly (as 'full' root). Just you don't use TWRP
To root:
- Install Huawei UpdateExtractor (PC), download update.zip for your 9.1.0.252 c432 from FirmwareFinder, unzip and extract Recovery_Ramdisk.img
- Copy Recovery_Ramdisk.img to the phone, install Magisk Manager, choose Install and then Patch a file, check all three options Preserve AVB, Preserve encryption, Recovery file
- Copy patched_boot.img (rename to patched_recovery.img or so) to PC and flash from Fastboot to Recovery (similar like flashing TWRP) - of course, Bootloader must be unlocked (you have code) and OEM/FRP must be unlocked
- You must boot to system through recovery (because Magisk was patched to recovery), if Magisk Manager shows rooted, you are done
To unroot:
- In case of bootloop or anything: just flash stock Recovery_Ramdisk.img back to Recovery, and you are back to stock
- Regular unrooting: take Uninstall from Magisk (and later, optionally, flash stock recovery_ramdisk.img)
- In case of OTA: unroot (regularly, as above), accept OTA, root again
Btw, you could update your sig now (no more EMUI 5)
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
ewingr said:
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
Click to expand...
Click to collapse
Font size can be changed in Settings /Display
I never changed system fonts but there are Magisk modules to do so, search by Google, eg:
https://forum.xda-developers.com/apps/magisk/avfonts-march-6-t3760827
https://forum.xda-developers.com/apps/magisk/module-midnightcore-one-midnight-modules-t3762758
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
ewingr said:
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
Click to expand...
Click to collapse
Look for MHA-LGRP2-OVS - see screenshots.
You can also find through Web:
https://pro-teammt.ru/firmware-database/?firmware_model=MHA-LGRP2-OVS
Btw, there are several b252 packages there, all the same size (and probably all ok) but I was told that package number #279403
is the one that is distributed by OTA
Thanks.
I saw the MHA-LGRP2-OVS ones, but I thought I needed to find one with identical name to the one I'm on.
This stuff doesn't make much sense...at least not logical. Only experience and/or help makes it possible to get it done.
Appreciate y our help.
Well, I don't know what's going on. I downloaded the FW from the link you provided, as well as from FF on the phone.
The one from the phone, once I transferred it to the PC, wouldn't extract anything from the zip.
The one from the link extracted, but when I loaded the Update.app into Update EXtractor, I got this error:
So, I then downloaded a different version from the web site (282444), and got this in Update Extracter:
Maybe it's warning me to not root:silly:
I am going through the thread about the extracter tool now to see if I find anything helpful. First blush looks like I'd need to make a profile file that is outside the limits of my knowledge. We'll see.
I found a post saying:
Try with crc check off (in settings) for extracting
Click to expand...
Click to collapse
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
ewingr said:
I found a post saying:
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
Click to expand...
Click to collapse
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
zgfg said:
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
Click to expand...
Click to collapse
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
WARNING:
If your phone runs Android 8 or later with latest security patch - then this service won't work!
Click to expand...
Click to collapse
I'm on Android 9 with security patch 3.
ewingr said:
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
I'm on Android 9 with security patch 3.
Click to expand...
Click to collapse
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
zgfg said:
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
Click to expand...
Click to collapse
OMG, yes, you have. BUT the site that provided the method to do it says it won't, per the quote I put in my post. I'm inclined to believe you, you have been a very good source and patient. But, I was wondering why would they say it won't work? That is their exact words, about their tool.
That being said, I guess as that I had the code before upgrading to 9, then just following the fastboot commands with that code will work, and in fact doesn't even use their tool. . So, I'll continue with that then. The information out here can sure be confusing.
Thanks...
[EDIT]
I figured that likely it would be the ramdisk.img file, and through Google search I found a thread that verified that. So, I'm continuing on.
Thanks...
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
56_kruiser said:
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
Click to expand...
Click to collapse
So, are you the same as previously, @ewingr?
If so, have you successfully unlocked Bootloader with that old code
OpenKirin instruct to patch Ramdisk and that was correct for EMUI 8.
(If) yu are on EMUI 9.1, hence you need to patch and flash Recovery Ramdisk
When patching from Magisk Manager (MM), you have to check all three options: Preserve AVB 2.0 DM-Verity, Preserve Force Encryption and Recovery Mode.
Does MM report any error while flashing or success/ok?
You can rename patched_boot.img to like patched_recovery.img, doesn't matter, but you must flash it to Recovery (like flashing TWRP to Recovery).
Right after flashing, boot by key combo to that patched Recovery (like booting to TWRP by key combo, after flashing TWRP).
Of course, you will not flash/use TWRP here
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
fastboot flash ramdisk Patched_RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
I got this response:
target reported max download size of 471859200 bytes
sending 'ramdisk' (32768 KB)...
OKAY [ 0.721s]
writing 'ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.757s
Click to expand...
Click to collapse
56_kruiser said:
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
I got this response:
Click to expand...
Click to collapse
Again, if you are on EMUI 9.1, forget Open Kirin instructions (for EMUI 8).
You must patch Recovery Ramdisk and flash to Recovery Ramdisk, so:
fastboot flash recovery_ramdisk Patched_RECOVERY_RAMDIS.img
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
56_kruiser said:
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
Click to expand...
Click to collapse
Magisk by default means you have root. You can install and disable modules in Magisk Manager, but you cannot disable root - for that you must Unistall Magisk (an option in Magisk Manager).
In MM you have a tab/menu showing all apps that were granted root - you can suspend or even revoke to some
Check in Settings/About, does it show you have b252 or b252 Patch03. I think that it thinks you are on b252 without Patch03, and it wants to install that patch.
But I don't know would you loose Magisk if you accept (or even get bootloop), so better disable authomatic OTA updates for now.
Believe me, similar 'Important' patches were receiving users (starting at the same time) with various Huawei phones running EMUI 9.1, discussing on XDA what it was, but there was never an answer, nobody detected any change for something better or worse.
So you don't loose anything if About showing b252 without Patch03
To boot to Magisk you must boot with Vol+ pressed - with USB discinnected.
If connected by USB to charger or PC, booting with Vol+ pressed will boot to eRecovery.
Normal booting (without Vol+ pressed) boots to the system (Android), but with Magisk disabled (MM will say that Magisk is not installed), so no root.
Reboot again with Vol+ and you are again rooted
If it ever comes an OTA for higher than b252, you will have to Uninstall Magisk from Magisk Manager and then accept OTA (and root by yhe same procedure one more time, with recovery_ramdisk.img from the new firmware).
Anomoly with root...
Root is working, albeit with anomalies.
If I boot w/o going through the recovery/Magisk, the phone boots up w/o root, and all works fine. When I go through recovery/Magisk, it comes up rooted, but with the following untenable anomalies: Dialer/Phone does not load; Contacts are not available; As result calls I receive do not show who is calling, and I cannot make calls out.
Given that changing fonts do not give me the fix I was chasing (see this thread), I may, unroot. But given that I can boot up w/o root and it works fine, I'll hold off un-rooting for a bit.
I'm a total noob, and was scared pant-less at the thought of bricking my device, but I was successful!
First off, I backed up my data. First by manually copying off photos, and creating a SMS backup (I have QKSMS), etc., then:
adb backup -all
In retrospect, I should've used --shared to also backup the apps themselves.
Anyways, then I downloaded the latest stock ROM for my device; I used the Lenovo Rescue and Smart Assistant for this. You have to plug the phone in, and follow the rescue process up to the point of getting it to download the ROM, and stop there. It tells you where it downloads the ROM (dropdown download menu), and you can open it in the file browser. DO NOT KEEP GOING OR THE RESCUE ASSISTANT WILL WIPE YOUR PHONE AND DO A FRESH INSTALL OF THE ROM. Thankfully it's very easy to tell when you get up to this point, so you can't really just accidentally let it do that.
Once you navigate to the folder where the ROM files are located, you'll see many files. I was overwhelmed at first, not knowing what I might have to flash over. Thankfully, there is a file called flashfile.xml, this file details the files needed to be flashed over. We cannot directly use this file, but we can infer from the file which files need to be flashed onto which partitions.
For more info: https://www.droidwin.com/flash-stock-firmware-via-fastboot-commands/
First however, we'll need to patch the boot.img file. Copy it over to your phone, use the magisk app to patch the file, and overwrite the original boot.img file.
Then open and read the xml file and you'll see "<step" lines. Which look like:
<step MD5="0e28dd7d9c003732a01c9c675c387dd3" filename="gpt.bin" operation="flash" partition="partition"/>
The important bits we need are "filename=" and "partition=". from there you can interpolate those into the "fastboot flash" command to flash the required files over.
fastboot flash [partition] [filename]
Repeat this process for each line that has "operation="flash"" in it. Ignore the lines with "operation="erase"", since those wipe various parts of your phone, such as with a clean install.
Once finished, you can reboot your phone to Android 12.
That should be it. I hope this helps someone out. Please PLEASE give me feedback, if there was anything wrong, or things you think I could've done better. Thanks.
Whoa this is way overkill. You just need to restore the boot image, take the ota, and patch the new inactive boot before rebooting.
If magisk doesn't have a backup of the boot image, you can create supply one for it, or just manually write the boot image.
Supplying magisk:
1. Calculate sha1 of the original boot.img.
2. Create directory /data/magisk_backup_<SHA1>
3. Gzip original boot.img and save boot.img.gz in the new directory.
4. In Magisk, uninstall magisk => restore images.
Otherwise, just write the original boot.img to /dev/block/by-name/boot_a or boot_b depending on which one is active with dd.
Make sure to install magisk to inactive slot after taking the ota and before rebooting. This automatically saves the new original boot for next time.
--
Unrelated, but I had forced ro.vendor.hw.dualsim to true, and was about to order a dual sim tray to test. IMEI1 was intact, but 2 was blank as expected (hadn't cleared modemst1/2 yet, but would've expected imei2 to goto 0 at best). But upon taking the July OTA, IMEI1 went to 0 (imei2 still blank) and I had no cell (sim disabled and untoggleable). Erased modemst1/2 to no avail, but reverting to single sim and wiping modemst1/2 brings the imei back. Anyone else test dual sim on berlna?
ziddey said:
Whoa this is way overkill. You just need to restore the boot image, take the ota, and patch the new inactive boot before rebooting.
If magisk doesn't have a backup of the boot image, you can create supply one for it, or just manually write the boot image.
Supplying magisk:
1. Calculate sha1 of the original boot.img.
2. Create directory /data/magisk_backup_<SHA1>
3. Gzip original boot.img and save boot.img.gz in the new directory.
4. In Magisk, uninstall magisk => restore images.
Otherwise, just write the original boot.img to /dev/block/by-name/boot_a or boot_b depending on which one is active with dd.
Make sure to install magisk to inactive slot after taking the ota and before rebooting. This automatically saves the new original boot for next time.
--
Unrelated, but I had forced ro.vendor.hw.dualsim to true, and was about to order a dual sim tray to test. IMEI1 was intact, but 2 was blank as expected (hadn't cleared modemst1/2 yet, but would've expected imei2 to goto 0 at best). But upon taking the July OTA, IMEI1 went to 0 (imei2 still blank) and I had no cell (sim disabled and untoggleable). Erased modemst1/2 to no avail, but reverting to single sim and wiping modemst1/2 brings the imei back. Anyone else test dual sim on berlna?
Click to expand...
Click to collapse
I tried doing the OTA method based off a guide, but it didn't work.
How am I supposed to restore the boot image without a reboot? In the guide I followed, you "uninstalled Magisk", then directly went and got the OTA, before then patching Magisk to the OTA version and finally rebooting.
The problem was, there was no update, or so the updater told me.
I also don't really understand what the whole "Supplying Magisk" bit is about.
This is why I'm a noob lol. I did the "overkill" method because I didn't know any other way of doing it. How else am I to supply Magisk with a boot image, if the OTA method doesn't work?
Addendum Edit: Please forgive me for my ignorance. Sorry. I really appreciate you trying to enlighten me on better methods.
For the record, I have used and understand (at least the basics) of gzip, dd, calculating checksums, and using magisk. I'm just still clueless of what exactly your instructions are trying to accomplish.
ruq said:
I'm a total noob, and was scared pant-less at the thought of bricking my device, but I was successful!
First off, I backed up my data. First by manually copying off photos, and creating a SMS backup (I have QKSMS), etc., then:
adb backup -all
In retrospect, I should've used --shared to also backup the apps themselves.
Anyways, then I downloaded the latest stock ROM for my device; I used the Lenovo Rescue and Smart Assistant for this. You have to plug the phone in, and follow the rescue process up to the point of getting it to download the ROM, and stop there. It tells you where it downloads the ROM (dropdown download menu), and you can open it in the file browser. DO NOT KEEP GOING OR THE RESCUE ASSISTANT WILL WIPE YOUR PHONE AND DO A FRESH INSTALL OF THE ROM. Thankfully it's very easy to tell when you get up to this point, so you can't really just accidentally let it do that.
Once you navigate to the folder where the ROM files are located, you'll see many files. I was overwhelmed at first, not knowing what I might have to flash over. Thankfully, there is a file called flashfile.xml, this file details the files needed to be flashed over. We cannot directly use this file, but we can infer from the file which files need to be flashed onto which partitions.
For more info: https://www.droidwin.com/flash-stock-firmware-via-fastboot-commands/
First however, we'll need to patch the boot.img file. Copy it over to your phone, use the magisk app to patch the file, and overwrite the original boot.img file.
Then open and read the xml file and you'll see "<step" lines. Which look like:
<step MD5="0e28dd7d9c003732a01c9c675c387dd3" filename="gpt.bin" operation="flash" partition="partition"/>
The important bits we need are "filename=" and "partition=". from there you can interpolate those into the "fastboot flash" command to flash the required files over.
fastboot flash [partition] [filename]
Repeat this process for each line that has "operation="flash"" in it. Ignore the lines with "operation="erase"", since those wipe various parts of your phone, such as with a clean install.
Once finished, you can reboot your phone to Android 12.
That should be it. I hope this helps someone out. Please PLEASE give me feedback, if there was anything wrong, or things you think I could've done better. Thanks.
Click to expand...
Click to collapse
Thank you for sharing your findings! I recently purchased this phone and was able to install the July OTA update & maintain root by following this video: