Related
Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB
Don't do like me. I updated to 9.5.6, rebooted and update went ok, but I lost root. Thought there would be a patched boot image already but havent found one.
update: go here
go to Post #299
dy2592 said:
Don't do like me. I updated to 9.5.6, rebooted and update went ok, but I lost root. Thought there would be a patched boot image already but havent found one.
Click to expand...
Click to collapse
Just open the downloaded ota, rip the boot.img from that file. Patch manually in magisk that boot.img. Then install the update, and reboot afterwards to fastboot mode. Flash the patched img and you are done.
Lucifer6 said:
Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB
Click to expand...
Click to collapse
Post 6 in this thread is how I did it and retained root, but I lost TWRP (I knew I would before doing it) I used the steps used for the OnePlus 6t for rooted users, knowing I would lose TWRP.
https://forum.xda-developers.com/oneplus-7-pro/help/t-mobile-converted-to-9-5-4-received-t3934761
These are the steps for the 6t for TWRP users but I know TWRP is having decryption issues so I'm not sure if the below will work.
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss
Lucifer6 said:
Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB
Click to expand...
Click to collapse
A partial ota with unlocked bootloader will brick your phone. Download the full zip and update in TWRP if you have it. If bootloader locked, install as normal, wait for it to finish and ask to reboot, don't reboot and open magisk manager and install to inactive slot. Reboot. That process will cause you to lose TWRP if you have it. If you have TWRP, flash full ROM in TWRP, flash TWRP.zip, reboot recovery and flash magisk.zip.
This way is easy and painless.
Yep performed the system update as well. It saw I was rooted and proceeded to download the full OTA. I let it update, did not reboot. Went to Magisk and Install to Inactive Slot(After OTA) and all is well. Im still rooted.
Posted by another user and the way I just did 9.5.6. Yes you will lose TWRP as usual if installed.
schmeggy929 said:
This way is easy and painless.
Yep performed the system update as well. It saw I was rooted and proceeded to download the full OTA. I let it update, did not reboot. Went to Magisk and Install to Inactive Slot(After OTA) and all is well. Im still rooted.
Posted by another user and the way I just did 9.5.6. Yes you will lose TWRP as usual if installed.
Click to expand...
Click to collapse
So dumb question here since I'm sorta new with this device (I've had Samsung and other devices that I've rooted so I'm aware of the basics).
Where do I download the entire fastboot zip files for say 9.5.6.GM31CB (TMobile variant)? I can't find it on OnePlus or T-Mobile. Also side question, do we still need to use Chinese certain of TWRP to get decryption working for internal storage? Thank you for whatever info you can provide.
I wonder, is there a patch for 9.5.6 yet? Let's say I have a locked bootloader now and stock on 9.5.6, how would I go about rooting my device? Or will I have to wait for the patched boot.img?
Lucifer6 said:
I wonder, is there a patch for 9.5.6 yet? Let's say I have a locked bootloader now and stock on 9.5.6, how would I go about rooting my device? Or will I have to wait for the patched boot.img?
Click to expand...
Click to collapse
Not if you unlock it, install magisk and patch the boot image within the app. I'd suggest looking for full zip of 9.5.6 just to use in case.
Which TWRP are you guys using? I see there is a Chinese version with decrypt working. Is that one safe?
photolarry said:
So dumb question here since I'm sorta new with this device (I've had Samsung and other devices that I've rooted so I'm aware of the basics).
Where do I download the entire fastboot zip files for say 9.5.6.GM31CB (TMobile variant)? I can't find it on OnePlus or T-Mobile. Also side question, do we still need to use Chinese certain of TWRP to get decryption working for internal storage? Thank you for whatever info you can provide.
Click to expand...
Click to collapse
There doesn't seem to be any fastboot ROM for the T-Mobile variant nor any Full OTA zips yet. Just have to keep looking in the PRO Guides, News and Discussion section. Personally I would not use that version of TWRP. Im waiting for the other TWRP by Maurinofrio to get Decrypt working.
schmeggy929 said:
There doesn't seem to be any fastboot ROM for the T-Mobile variant nor any Full OTA zips yet. Just have to keep looking in the PRO Guides, News and Discussion section. Personally I would not use that version of TWRP. Im waiting for the other TWRP by Maurinofrio to get Decrypt working.
Click to expand...
Click to collapse
So weird they claim they are as friendly to developers as pixel yet I don't see links to firmware. Not sure if I'm going to even bother rooting without backup of a full zip with all images inside. I guess I could get 9.5.3 and then do a few upgrades to get back to 9.5.6 but I'd rather have full file for 9.5.6.GM31CB
photolarry said:
So weird they claim they are as friendly to developers as pixel yet I don't see links to firmware. Not sure if I'm going to even bother rooting without backup of a full zip with all images inside. I guess I could get 9.5.3 and then do a few upgrades to get back to 9.5.6 but I'd rather have full file for 9.5.6.GM31CB
Click to expand...
Click to collapse
They are as developer-friendly as Pixel phones, (when you buy unlocked directly from OnePlus) not the T-Mobile version. Buy a Pixel from Google it OEM unlock to unlock the bootloader, buy a 7 Pro from OnePlus it's OEM unlock to unlock the bootloader.
In addition about you going to 9.5.3 and then upgrading to get back to 9.5.6
The 9.5.6 you're currently running on the T-Mobile version is not the same as 9.5.6 on the unlocked version. The unlocked version is a few builds newer.
If I were you I'd wait till the MSM tool that works with the T-Mobile version is released.
bp328i said:
They are as developer-friendly as Pixel phones, (when you buy unlocked directly from OnePlus) not the T-Mobile version.
In addition about you going to 9.5.3 and then upgrading to get back to 9.5.6
The 9.5.6 you're currently running on the T-Mobile version is not the same as 9.5.6 on the unlocked version. The unlocked version is a few builds newer.
If I were you I'd wait till the MSM tool that works with the T-Mobile version is released.
Click to expand...
Click to collapse
Msm tool? I'll get an unlock token Friday. Why would I need that? Newer than 9.5.6.GM31CB? I don't think so. This includes April security patch. I'm guessing the only big difference is the radio image is different for TMobile. Again I'm new to this mfgr so I'm trying. They aren't making it easy for me. I have an unlock phone. So shouldn't matter if I got it from T-Mobile. I can OEM unlock. So I can manipulate at will. Trouble is I'm scared I'll break the phone since I don't know this line of Android devices. I considered changing this to international but afterwards in worried it'll not work well in T-Mobile
photolarry said:
Msm tool? I'll get an unlock token Friday. Why would I need that? Newer than 9.5.6.GM31CB? I don't think so. This includes April security patch. I'm guessing the only big difference is the radio image is different for TMobile. Again I'm new to this mfgr so I'm trying. They aren't making it easy for me. I have an unlock phone. So shouldn't matter if I got it from T-Mobile. I can OEM unlock. So I can manipulate at will. Trouble is I'm scared I'll break the phone since I don't know this line of Android devices. I considered changing this to international but afterwards in worried it'll not work well in T-Mobile
Click to expand...
Click to collapse
There are a lot more changes in the international 9.5.6 GM21AA then that. they optimized double tap to wake and ambient display, fixed Bluetooth headset delays, camera updates, and other things.
The T-Mobile version will always be behind on software verse the international version.
bp328i said:
There are a lot more changes in the international 9.5.6 GM21AA then that. they optimized double tap to wake and ambient display, fixed Bluetooth headset delays, camera updates, and other things.
The T-Mobile version will always be behind on software verse the international version.
Click to expand...
Click to collapse
So are you saying I should update to AA? Even if I'm on T-Mobile network?? Will that not mess with the radio?
photolarry said:
So are you saying I should update to AA? Even if I'm on T-Mobile network?? Will that not mess with the radio?
Click to expand...
Click to collapse
That's the main reason everyone with the T-Mobile version is trying to unlock their bootloader, so they can run the international software. T-Mobile's software will always be behind the unlocked version. 9.5.3 for the unlocked version had the April security patch, that was three versions ago.
I owned the T-Mobile version of the 6t and the unlocked version of the 6t, the reception was the same.
My T-Mobile 7 Pro is unlocked running the international GM21AA software on T-Mobiles network. I uninstalled the Renovate Ice ROM for the screenshot so you can see I have the same model number as you running GM21AA.
But currently if you mess up a T-Mobile version there's no way to get it back because the MSM tool for it is not available yet. If something goes wrong you might be stuck with a phone that doesn't work until it's released.
bp328i said:
That's the main reason everyone with the T-Mobile version is trying to unlock their bootloader, so they can run the international software. T-Mobile's software will always be behind the unlocked version. 9.5.3 for the unlocked version had the April security patch, that was two versions ago.
I owned the T-Mobile version of the 6t and the unlocked version of the 6t, the reception was the same.
My T-Mobile 7 Pro is unlocked running the international GM21AA software on T-Mobile. I uninstalled the Renovate Ice ROM for the screenshot so you can see I have the same model number as you running GM21AA.
But currently if you mess up a T-Mobile version there's no way to get it back because the MSM tool for it is not available yet.
Click to expand...
Click to collapse
Thank you for your feedback. It's helpful to me. I am guessing an msm tool is something that puts stock firmware onto the device fresh in case you brick it. Couldn't I just fastboot flash 9.5.3 full package which I think is downloadable within OnePlus support?
photolarry said:
Thank you for your feedback. It's helpful to me. I am guessing an msm tool is something that puts stock firmware onto the device fresh in case you brick it. Couldn't I just fastboot flash 9.5.3 full package which I think is downloadable within OnePlus support?
Click to expand...
Click to collapse
Correct about the tool, returns the phone to 100% stock out of the box. Not 100% sure about whether or not the fastboot flash would fix a soft bricked device. That could possibly work.
But I know currently it's impossible to go back to T-Mobile software without the tool.
has anyone contact oneplus support either via email and chat and requested full ROM download links?
theyre pretty helpful like that.
I have an SM-A530F and had no issues flashing roms and TWRP. I eventually tried Saboor OneUI from and my phone got completely encrypted and would only allow official binaries to be flashed. I flashed Binary 7 (Pie) to my device and tried to flash TWRP but had come across the error and after researching realised I'd have to wait 7 days with the phone continuously booted up. I have waited 7 days with nothing changed. I'm now on my 25th day and still have a prenormal KG state. But in developer options my OEM states that it is already unlocked and I can switch the toggle. I cannot flash TWRP or magisk though.
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash
Click to expand...
Click to collapse
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Zefpoes23 said:
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Click to expand...
Click to collapse
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
Click to expand...
Click to collapse
youdoofus said:
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
Click to expand...
Click to collapse
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Zefpoes23 said:
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Click to expand...
Click to collapse
youre not going to get the phone to think that TWRP is official. If that was possible, we would all have root and without so much as unlocking the bootloader for that matter
manifesto- posted on another thread-sorry for the dupe
A bit of history gives a bit more depth/ Just when you thought it was okay to go back in the water. I'm Canadian you can probably tell by my accent. My journey with phones has always been Samsung simply due to availability s6 s7 s8 s8+ most recently the a530w.
In order for you to understand my joy finding the A8 and my horror is that the S8 series. in North America S8 uses a Qualcomm Snapdragon chip. g950u is SD g950f is the rest of the world (exnyos) This is probably due to some kind of World Trade Organization antitrust treaty {although qualcom makes great chips} or whatnot I don't care.
i do care about is their bootloader lock policy (g950u and up) so it is impossible to unlock an encrypted Snapdragon bootloader. When I ran into the a530w exnyos, I was like a three-year-old at Christmas now you have to understand I'm not a coder I'm more of a mason I'm familiar with bricks. I'm sure we've all watch the AP file upload and Odin like we watch paint dry. So when I first got the a530w pi version April patch I was able to TWRP install I believe at the time was Pixel project or something else added magisk, xposed you get the idea.
Eventually a file got corrupt (much like @Zefpoes23) and I had to common sense restock it. I think my mistake what is going with the most current pie version (hadn't read this thread yet from @corsicanu) which is binary 7 knowing what I know now I would have probably had the ability to go a binary 4 or so. I haven't done the 7 day challenge simply not to waste my sanity. my bootloader unlock never vanished, it like it's a light switch with no bulb. I've tried to backdated front dated. I refuse to wait 7 days to find out that I'm still at the same place. . The problem is all the fixes are zip files which you need TWRP to flash. I agree, it's not @BlackMesa123 version. it's the prenormal. No I'm certainly not a developer and some of them are mobile gods. My questions maybe Elementary logical. Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort. think we're all about to become in the same boat. we could start a movement lie "#meprenormal2" In Time will tell. As or now "prenormal" is the new "normal" All I can to the devs: help me odin 3 canmodme. your my only hope
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
jthibault27 said:
Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort.
Click to expand...
Click to collapse
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
jthibault27 said:
I refuse to wait 7 days to find out that I'm still at the same place.
Click to expand...
Click to collapse
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
jthibault27 said:
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
Click to expand...
Click to collapse
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
@mchlbenner if you have a moment, could you lend a hand?
Youdoofus said:
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
Click to expand...
Click to collapse
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
jthibault27 said:
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
Click to expand...
Click to collapse
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
mchlbenner said:
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
Click to expand...
Click to collapse
there you are!! so, the A8 is now not rootable?
Youdoofus said:
there you are!! so, the A8 is now not rootable?
Click to expand...
Click to collapse
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
jthibault27 said:
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
Click to expand...
Click to collapse
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
mchlbenner said:
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
Click to expand...
Click to collapse
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Youdoofus said:
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Click to expand...
Click to collapse
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
jthibault27 said:
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
Click to expand...
Click to collapse
yes, from what ive gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before i got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Youdoofus said:
yes, from what I've gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before I got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Click to expand...
Click to collapse
If you ever come across a forum specific to this issue ({completely extrapolating the date by guess} July 1, 2019 9.0) but not necessarily specific to the A8, please share. as it stands now, my findings indicate isolated conversations in different forums on various models, sharing the same problem. We must unite! lol. truth be told, it's challenging searching for such a specific problem relating to a patch on many models.
Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Will this work on the reteu devices (being from a different channel)?
FelixNevorsky said:
Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS
takoa said:
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS
Click to expand...
Click to collapse
My guess is that QSB is for Android 10 (it was called Q for some time). And PSB is 9.0 (aka Pie)
I mean the letters sbs and sb. thanks
takoa said:
I mean the letters sbs and sb. thanks
Click to expand...
Click to collapse
ummmm......Stable build.....maybe
Was Anyone able to root this version?
Wintershade said:
Will this work on the reteu devices (being from a different channel)?
Click to expand...
Click to collapse
Yes, it should. It's been already tested here on the forum with pretty good results. So yeah, I'd say it will. But if you're not in a hurry, maybe you can wait for a bit longer to get the official build for RETEU.
Channel Signification Firmware
Is a list exist for channel signification for https://mirrors.lolinet.com/firmware/moto/troika/official/
or a way to knows the signication ?
RETEU = Europe
RETUS = USA
RETCA = Canada
RETRU = ???
etc ...
Compatibility Variant / Firmware
Is exists a thumb rule for compatibility firmwares in between XT2013-1, XT2013-2, XT2013-3, XT2013-4.
Actually, I have a XT2013-4 device and I would like flash another firmware variant.
Thanks
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards
arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks
Gypsy said:
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks
Click to expand...
Click to collapse
that is very good to know. thank you!
Gypsy said:
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards
Click to expand...
Click to collapse
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time.. ?
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know.. ?
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?
zaqiezsbelelzsinski said:
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time..
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know..
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?
Click to expand...
Click to collapse
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.
arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Click to expand...
Click to collapse
arsradu said:
@zaqiezsbelelzsinski
I can't and more to @arsradu's answers, but just in case you decide to unlock your bootloader for whatever reason, it voids your warranty., there's the link:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Good luck, if you have any difficulty, please ask!
Click to expand...
Click to collapse
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.[/QUOTE]
One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.
arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.
Click to expand...
Click to collapse
Thank you for the feedback
Yes, I understand about the risk. Many years ago I always flashing my device (Nexus 5) while it was release update, but that was then ?. Now, Maybe I will be waiting till my device get update to android 10.
The problem is, there is no valid information from Motorola especially TROIKA XT2013-4 about update to android 10.
Thanks for your advice about flashing ROM..
Cheers ???
You could try to contact your local Motorola Support team. I don't think they will give you an actual ETA. But maybe they can tell you wether or not there will be an update to Android 10 for this particular model (XT2013-4). I think there should be. I see no reason why this particular model would be an exception. But you could double check that. Just in case.
Logic would suggest that there should be one soon. XT2013-1 and XT2013-2 already got the update. So it would make sense for the "-4" model to follow.
Sent from my motorola one action using Tapatalk
arsradu said:
One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.
Click to expand...
Click to collapse
@arsradu
I notice you have experience with security patches, tanks you to had shared!
IF I REALLY NEED TO DOWNGRADE MY SECURITY PATCH ! EVEN with all amounts of troubles, IS THERE A WAY doing it?
Thanks
The Samsung Galaxy A71 model SM-A716U by AT&T which has a normally unlockable bootloader has thanks to afaneh92 been unlocked. And he has made a TWRP version for it. Mine is now rooted with TWRP installed.
The version of TWRP was just built today by afaneh92 and it may still need a few tweaks per afaneh92 to be fully ready for prime time but so far it seems to be working fine. He was also very helpful in installing TWRP and getting root done on this model.
I'm not sure of all the details regarding how this locked bootloader is unlocked but it is a pay service that involves using your phones DID number which is then used to make a customized file for your specific phone and is flashed with Odin. Using afaneh92 for this it had a waiting time of only a couple minutes to get the file.
See this thread for afaneh92's info to get your bootloader unlocked on this model if you want root and TWRP:
Samsung Galaxy Bootloader Unlocks for normally unlockable Bootloaders
If there is interest I'll detail the steps to get all this done. I didn't have all the details when I started so I got help from afaneh92 via Telegram for the process. You will need to have Telegram either on your PC or phone to communicate with afaneh92 and to get the needed info and file built for your phone.
When you decide to unlock your bootloader these directions will help you be prepared and will avoid tying up afaneh92 too much as I know he barely gets any time to sleep with all that he does Since I'll assume you are not unlocking your bootloader for fun of an unlock the directions below will help you get Root and TWRP installed. TWRP is the easiest way to install Magisk and get root.
First you will want to do a complete backup of your phone. I suggest Samsung Smart Switch or MyBackup Pro or both
Then you need to get your phones DID number. You can see it on the download screen. Easy way to get into download is to turn off your phone, then hold volume up and volume down and the plug in USB cable to your computer (charger may also work). Then when you see the aqua color screen hit volume up to go into download mode. There are a couple other methods listed on the page afaneh92 has in the link above.
Save the DID number and it will be good to take a picture of the Download screen also as afaneh92 may request that.
Make sure you have the patched version of Odin from here:
https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/
Also get multidisabler.zip and vbmeta_disabled.tar if you don't have it.
Multidisabler.zip can be found here: https://forum.xda-developers.com/t/pie-10-11-system-as-root-
multidisabler-disables-encryption-vaultkeeper-auto-flash-of-stock-recovery-proca-wsm-cass-etc.3919714/
Also get the Magisk.zip file from here: https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
Then get on Telegram to contact afaneh92 from his link for his channel in the link above. Once you make payment he will get the .tar file for your phone. It can be just a couple minutes or a day or so I believe depending on his source being available. Mine only took a couple minutes. Once you have the fix file
for the bootloader unlock you will use the patch Odin to flash it to the AP section. Upon reboot the phone will take a little while to start up as it's like a factory reset and your data is wiped.
After you have gone through the phone setup wizard you will want to reset Odin, go into Download mode again and flash vbmeta_disabled.tar to the USER_DATA section in Odin. And if afaneh92 has TWRP available you can flash it into the AP section at the same time. Before pressing start in Odin be ready to quickly press volume up and power button once the phone reboots and the screen goes black. The release when you see the Logo. The you will be in TWRP.
Use adb to push multidisabler.zip onto your phone. Since data is encrypted at this point there is no use in
copying it there ahead of time. Just use "adb push multidisabler.zip /" which will copy it to root of phone storage where you can see it with TWRP. After flashing it do not wipe cache / Dalvik.
Then in TWRP choose Format data and type yes to confirm. Then reboot TWRP into recovery (TWRP)
In TWRP flash multidisabler.zip Then format data and answer Yes.
Then the best way to install Magisk is to flash it now from TWRP with "Install".
Reboot and check whether Magisk Manager is installed. If for some reason it isn’t installed automatically,
manually install Magisk Manager and with Wifi on allow it to do any updates.
Here is one other way to get your DID number (also shown in afaneh92's message thread above):
adb shell getprop ro.boot.em.did
or by Android terminal: getprop ro.boot.em.did
After talking to afaneh92 I believe he will be ready to release TWRP for the Galaxy A71 in a day or two. I am not sure yet if it will cover all the Snapdragon A71's or which exact models as I haven't asked about that but the one I tested today seems to work very well on the A716U.
This thread is where you can now get TWRP : [RECOVERY][UNOFFICIAL] TWRP for Galaxy A71 5G (Snapdragon)
Confirmed legitimate. Currently running his custom TWRP as well. He reaponded quickly too. It is worth the money to me.
So nobody's addressed the million-dollar question. What does Afeneh92 charge for this service?
Also, do we need to be on a specific version for this to work? I haven't updated my phone since I bought it because I've been waiting for a root method to be developed. Would he be able to root if I update to the latest software? Will I be able to update it after he roots it?
edit: nevermind the first question, it looks like the current price is $65 for the A71 5G.
droidzer1 said:
The Samsung Galaxy A71 model SM-A716U by AT&T which has a normally unlockable bootloader has thanks to afaneh92 been unlocked. And he has made a TWRP version for it. Mine is now rooted with TWRP installed.
The version of TWRP was just built today by afaneh92 and it may still need a few tweaks per afaneh92 to be fully ready for prime time but so far it seems to be working fine. He was also very helpful in installing TWRP and getting root done on this model.
I'm not sure of all the details regarding how this locked bootloader is unlocked but it is a pay service that involves using your phones DID number which is then used to make a customized file for your specific phone and is flashed with Odin. Using afaneh92 for this it had a waiting time of only a couple minutes to get the file.
See this thread for afaneh92's info to get your bootloader unlocked on this model if you want root and TWRP:
Samsung Galaxy Bootloader Unlocks for normally unlockable Bootloaders
If there is interest I'll detail the steps to get all this done. I didn't have all the details when I started so I got help from afaneh92 via Telegram for the process. You will need to have Telegram either on your PC or phone to communicate with afaneh92 and to get the needed info and file built for your phone.
Click to expand...
Click to collapse
What makes a bootloader More difficult to unlock compared to otherways? Asking because curious.
droidzer1 said:
The Samsung Galaxy A71 model SM-A716U by AT&T which has a normally unlockable bootloader has thanks to afaneh92 been unlocked. And he has made a TWRP version for it. Mine is now rooted with TWRP installed.
The version of TWRP was just built today by afaneh92 and it may still need a few tweaks per afaneh92 to be fully ready for prime time but so far it seems to be working fine. He was also very helpful in installing TWRP and getting root done on this model.
I'm not sure of all the details regarding how this locked bootloader is unlocked but it is a pay service that involves using your phones DID number which is then used to make a customized file for your specific phone and is flashed with Odin. Using afaneh92 for this it had a waiting time of only a couple minutes to get the file.
See this thread for afaneh92's info to get your bootloader unlocked on this model if you want root and TWRP:
Samsung Galaxy Bootloader Unlocks for normally unlockable Bootloaders
If there is interest I'll detail the steps to get all this done. I didn't have all the details when I started so I got help from afaneh92 via Telegram for the process. You will need to have Telegram either on your PC or phone to communicate with afaneh92 and to get the needed info and file built for your phone.
Click to expand...
Click to collapse
Hey man is yours from ATT ? I got my mom one and wanted to useon Cricket AIO . ATT owns Cricket and uses same network so does Safelink . Well cricket sim works for 5 mins no problem the says the imei is uncompatible. Safelink sim works fine . Are there some gsi for this phone ? That may help it or modules to spoof lol .
Hey was wondering if anyone has or can make a backup of modemst1 and modemst2 for A 71 5g snapdragon ? I had an issue registering on network and found a guide using fastbootcommands to erase those and that would fix it. However now it won't recognize any sim card and I've downgraded and did Ota to 3.0 again after formatting data in twrp. I ve tried twrp backup and that didn't fix it .
droidzer1 said:
After talking to afaneh92 I believe he will be ready to release TWRP for the Galaxy A71 in a day or two. I am not sure yet if it will cover all the Snapdragon A71's or which exact models as I haven't asked about that but the one I tested today seems to work very well on the A716U.
Click to expand...
Click to collapse
Hi,
You mentioned the A71 A716U and in the OP mention "AT&T". Is that what the A716U is? The AT&T model?
I ask because I just bought two of them, but they're Unlocked and someone else is using it with my Carrier (MetroPCS, now called Metro by T-Mobile) and so it didn't mention which Carrier the model normally ties to.
If so, I still use this same BootLoader Unlocker that he creates, right? I definitely want to Root both phones.
I didn't see the steps for Rooting here (I think you mentioned listing the steps), but I'll keep looking.
Thank You,
hi Zeus i believe the A716U is the north american A71 5G and diffrent cell carriers can be flashed for the firmware part, the carrier lock is i think controlled by you but you've got to ask your cell provider to unlock it carrier wise if you owe nothing for the device and it it isnt blacklisted or stolen the imei, also the devices are usually? branded one particular carrier, to find that out go into download mode and it should have a csc cell provider code at the top. =) hope this helps?
Hi,
I went to the link where the "multidisabler.zip" file is and got that, but when I looked for the "vbmeta_disabled.tar" file, I don't see it on that page. Where can I get that one, please?
I ask, because I've never heard of that one before and so I don't know if it's specific for this phone and so was worried about just grabbing any file from wherever (on XDA) with that name.
Thanks!
mysticjp said:
hi Zeus i believe the A716U is the north american A71 5G and diffrent cell carriers can be flashed for the firmware part, the carrier lock is i think controlled by you but you've got to ask your cell provider to unlock it carrier wise if you owe nothing for the device and it it isnt blacklisted or stolen the imei, also the devices are usually? branded one particular carrier, to find that out go into download mode and it should have a csc cell provider code at the top. =) hope this helps?
Click to expand...
Click to collapse
Oh, maybe I wasn't clear (my fault). I don't mean the Cell Carrier. I bought that part Unlocked. I'm talking about Unlocking the BootLoader.
Thank you for taking the time to respond! I appreciate it!
Hi no bootloader unlock for DUE4 yet thank you
Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
HopelesRomantc91 said:
Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
Click to expand...
Click to collapse
Wow, thanks for all this info. That is great that you were already able to root and get Magisk on there with minimal issues. This is pretty much what I do with my phones right out of the box. Regarding that link for Gapps, I read through the start of that thread and the package is definitely what we'll probably need for this phone. But, without a working recovery at this point, I don't think there is another way to install it.
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
CCivale said:
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
Click to expand...
Click to collapse
It's worth noting that I cancelled my Giztop purchase and bought from Aliexpress instead. Can't remember if I actually said that or not.
there is twrp, it is experimental
Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
I couldn't find it, can you link it?
Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
Can you link it?
syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
ktitimbo said:
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
Click to expand...
Click to collapse
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
@HopelesRomantc91
Can you share the URL for unlock code request?
I couldn't unlock with global website...
I think I just used the global one here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/
Hello, I have patched boot img to my moto edge S 5g Chinese version and I have magisk root ok but if I restart the motorola it is lost and I have to reinstall boot parched, do you know why?
HopelesRomantc91 said:
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
Click to expand...
Click to collapse
Thanks for info . İs flashing g100 rom need root device or unlocking bootloader ?