Related
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.
Hello, few weeks ago I bought a brand new Realme Pad LTE. This is really a very underestimated device considering it has on average more ram than competitors at better pricetags and a respectable octa-core processor with all the usual amenities a tablet should have along good lasting battery, no company bloatware and a solid construction in 2022. Unfortunately there is no support topic on XDA or elsewhere, and can't find a way to root it. There is no TWRP, no OTA or firmware available to download from the manufacturer nor a specific tool to dump the boot.img from the device, just unlock the bootloader and that's all. I am desperate, because otherwise I will have to return it and buy Samsung at an higher price - which I dumped for many reasons - just for the peace of mind of having support from LOS community, a working Magisk build and TWRP flashed for my backups and screw-ups. What can I do?
Because you're able to unlock tablet's bootloader you also should be able to dump tablet's boot.img by means of ADB applying Android's shell command named dd - what of course requires tablet's Android is got ( at least temporarily ) rooted.
xXx yYy said:
Because you're able to unlock tablet's bootloader you also should be able to dump tablet's boot.img by means of ADB applying Android's shell command named dd - what of course requires tablet's Android is got ( at least temporarily ) rooted.
Click to expand...
Click to collapse
That's why I am trying to get a boot.img. I need to root my device, and for that I need - to my understanding - to patch boot.img from this device on the Magisk app. I am a noob at all this terminal stuff, and struggled for days only to find an answer on how to unlock the bootloader on such a poorly documented/ignored device. I honestly don't understand what do you mean by "temporarily rooted" and I am also clueless on how *dd* command works or how/what path should I input over adb shell. Can you or everyone else help me out on this?
Android OS is rooted if it has su ( read: switch user ) functionality implemented.
By default this functionality is left of by OEM. Hence you've to add it by your own.
This can get achieved by means of ADB - if temporary root is your goal - or Magisk - if permament root is your goal - where the latter method patches Android's boot.img and other system files, so you no longer have a boot.img in it's initial state.
If to have a temporary root is intended, then all what is needed is to push a suitable su binary to Android's filesystem and make this binary executable.
With regards to su and dd commands: as always GIYF.
xXx yYy said:
Android OS is rooted if it has su ( read: switch user ) functionality implemented.
By default this functionality is left of by OEM. Hence you've to add it by your own.
This can get achieved by means of ADB - if temporary root is your goal - or Magisk - if permament root is your goal - where the latter method patches Android's boot.img and other system files, so you no longer have a boot.img in it's initial state.
If to have a temporary root is intended, then all what is needed is to push a suitable su binary to Android's filesystem and make this binary executable.
With regards to su and dd commands: as always GIYF.
Click to expand...
Click to collapse
I have pretty much a stock Android 11 as OEM firmware so its my assumption it could be enabled, otherwise I have no idea of how to find out or where to find a suitable su binary for it. Anyway, my goal is to have a permanent root, so I can backup or remove system apps or eventually flash the **** out of this tablet if ever a dev pulls out a custom build for it. Also, to my understanding, flashing a Magisk zip from stock recovery or attempting adb sideload without a TWRP are a no-go, meaning I have Magisk only as apk package available to install.
From Google (the irony, I had to search for GIYF to find out what meant) I only found - for now - people that either describe a situation with a specific device that requires extra steps, or do a 180° and start rambling over TWRP stuff like it was taken for granted everyone has access to an official/unofficial build to extract that damn file. *sighs*
Dingo_Dash said:
Hello, few weeks ago I bought a brand new Realme Pad LTE. This is really a very underestimated device considering it has on average more ram than competitors at better pricetags and a respectable octa-core processor with all the usual amenities a tablet should have along good lasting battery, no company bloatware and a solid construction in 2022. Unfortunately there is no support topic on XDA or elsewhere, and can't find a way to root it. There is no TWRP, no OTA or firmware available to download from the manufacturer nor a specific tool to dump the boot.img from the device, just unlock the bootloader and that's all. I am desperate, because otherwise I will have to return it and buy Samsung at an higher price - which I dumped for many reasons - just for the peace of mind of having support from LOS community, a working Magisk build and TWRP flashed for my backups and screw-ups. What can I do?
Click to expand...
Click to collapse
It's got to the point where I'm considering learning how to compile a rom for it!
ssouthall6 said:
It's got to the point where I'm considering learning how to compile a rom for it!
Click to expand...
Click to collapse
Well that would be super appreciated. Wish you the best luck!
Dingo_Dash said:
Hello, few weeks ago I bought a brand new Realme Pad LTE. This is really a very underestimated device considering it has on average more ram than competitors at better pricetags and a respectable octa-core processor with all the usual amenities a tablet should have along good lasting battery, no company bloatware and a solid construction in 2022. Unfortunately there is no support topic on XDA or elsewhere, and can't find a way to root it. There is no TWRP, no OTA or firmware available to download from the manufacturer nor a specific tool to dump the boot.img from the device, just unlock the bootloader and that's all. I am desperate, because otherwise I will have to return it and buy Samsung at an higher price - which I dumped for many reasons - just for the peace of mind of having support from LOS community, a working Magisk build and TWRP flashed for my backups and screw-ups. What can I do?
Click to expand...
Click to collapse
Hello,
Did you manage to root the tablet? I'm considering buying it however cannot find any confirmation of successful rooting so far.
kanines said:
Hello,
Did you manage to root the tablet? I'm considering buying it however cannot find any confirmation of successful rooting so far.
Click to expand...
Click to collapse
Hi, unfortunately I returned the tablet since there was no way up to this day to root it. You can indeed unlock the bootloader but fastboot prevents you from using sideload and since there is not a recovery for this specific tablet, and Realme support will flip you off if you ask for a firmware download, you're on your own.
Dingo_Dash said:
Hi, unfortunately I returned the tablet since there was no way up to this day to root it. You can indeed unlock the bootloader but fastboot prevents you from using sideload and since there is not a recovery for this specific tablet, and Realme support will flip you off if you ask for a firmware download, you're on your own.
Click to expand...
Click to collapse
Thanks for the answer. That's really stupid customer approach as for the brand trying to get into tablet market. In this case I'll probably buy samsung tab a8 or lenovo p11 instead.
kanines said:
Thanks for the answer. That's really stupid customer approach as for the brand trying to get into tablet market. In this case I'll probably buy samsung tab a8 or lenovo p11 instead.
Click to expand...
Click to collapse
Yeah, definitely. On one thing tho this tablet rocks; basic stuff like managing Netflix and using Android Auto for navigation from the tablet itself; the S6 Lite I now own can't even do that, in fact Netflix sucks and no support for AA has been even integrated despite having even the most community support. Who knows if there isn't even a longer list of unsupported daily use apps out there... By the way check P11 and A8 respective forums before making a decision; there is no certainty of support for root, recovery and all that good stuff despite being devices of recent production.
Guys, there is custom rom support for realme pad. Go to this telegram page .
Realme Pad | UPDATES
Welcome To The Official Channel For Realme Pad Group: @realmepadofficial
t.me
sarnz said:
Guys, there is custom rom support for realme pad. Go to this telegram page .
Realme Pad | UPDATES
Welcome To The Official Channel For Realme Pad Group: @realmepadofficial
t.me
Click to expand...
Click to collapse
So there is hope after all! THANK YOU!
Hello.
Chek and the yt. Existing video there, with steps, for all.
Yeah, you can also discuss about it on the official telegram group here :
Realme Pad | OFFICIAL
Welcome To The Official Group For Realme Pad Channel: @realmepadupdates
t.me
Hello..Somebody to update realme pad to latest OTA EEA RMP2103_11_A.09 version?
Has anyone rooted this device yet?
Could a get a play by play?
panossnake said:
Hello.
Chek and the yt. Existing video there, with steps, for all.
Click to expand...
Click to collapse
Where is the video?
Hak_Init said:
Where is the video?
Click to expand...
Click to collapse
Search for tech fancier in yt..there is all steps for unlocking bootloader, twrp, root, etc..
But you must have the latest system update. Just for that, i am asking!!!
hello
I cant change the stock launher. Always any new installed launcher,has conflict, lagg, and not working properly.
Somebody to use a difrent launcer without problem
thanks
Hello, Can any smart person because I'm slow lol help me get the Recovery or the Boot.img for a Motorola Edge 2021, My version is 12 (S1RMS32.48-18-11-2-3). Thanks
You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com
ruq said:
You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com
Click to expand...
Click to collapse
I understand that yes but my problem is that I don't have a laptop or PC to run the program so I'm trying to find another way to get the firmware for my Edge 2021, And if I can't do that is there any custom ROM compatible with this device that I could use to patch it with magisk?
So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com
oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.
ruq said:
oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.
Click to expand...
Click to collapse
I already solved that problem I use another phone to flash the images
ruq said:
So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com
Click to expand...
Click to collapse
My firmware is android 12 so would it be alright if I install this android 11 image?
Imparel said:
My firmware is android 12 so would it be alright if I install this android 11 image?
Click to expand...
Click to collapse
An android DOWNGRADE might cause issues...
ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
Okay I understand, I'll just take my chances and hopefully I don't brick my device...
ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
I did try it but instead of fully flashing the img I just did fastboot boot so that it would only boot into it one time and it didn't work at all so my only chance of rooting my device is using a PC to get the firmware of my phone, And thanks for the help.
Z flip 4 is supposed to get OneUI 5.0 with A13 in November, but it just received the November security patch without A13. Do you think that A13 will get delayed for our phone?
I read here that beta 2 was released recently. Usually they will issue beta 3 before it will be final. So yes, I can see the A13 can be delayed till December.
But that's no biggie really. Not that much changed from A12 to A13 anyway.
Beta 4 ZVK3 is under testing at the moment
I am still stuck in beta 1 ZVK9. I manually load this one, after that, keep looking for beta 2, 3 and 4 now. No luck. For those if you are still in A12, maybe be patient. Google Pay won't work in beta software, I don't see other issues.
johnny8910 said:
Beta 4 ZVK3 is under testing at the moment
Click to expand...
Click to collapse
Oh, good to know.
I guess my part regarding delay is irrelevant then.
What about performance? Any significant variances against A12? How's the battery life?
starche_old said:
What about performance? Any significant variances against A12? How's the battery life?
Click to expand...
Click to collapse
No massive changes, but does seem snappier. Ram Memory management is improved over A11 in my opinion.
Battery life for me is exactly the same.
Has anyone managed to get the firmware file or the fetch the ota update file, for the US model, for the stable release yet?
I too, curiously any one (service/model) combination in US get official A13 update?
I have F721U1 directly purchased from samsung.com. I am with US mobile service (VZW MVNO). I manually apply A13 beta 1. Phone runs fine and does not hit any issues as I am aware in my usage pattern.
However, Gpay won't work with beta SW. Keep googling without any luck for official download Link. Tired for read all different web site post update screen and news announcement. None of them has download link.
Missed previous Pixel phones, Google post Full and OTA as soon as they announce update news. I can always download and apply myself.
Maybe a couple days more.....
https://www.sammobile.com/news/galaxy-z-flip-4-fold-4-android-13-update-stable-released/
krusir said:
Missed previous Pixel phones, Google post Full and OTA as soon as they announce update news. I can always download and apply myself.
Click to expand...
Click to collapse
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Thank you. I will try it when I find download link.
SandFromUndertal said:
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Click to expand...
Click to collapse
SM-F721B A13 CSC SLK is official
Download from Samfirm
SandFromUndertal said:
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Click to expand...
Click to collapse
I knew that u1 is the Google Fi version. But what exactly is the software different between the two? You can use non fi sim card on an u1.
Flashed One UI 5 yesterday. From the SM-F721B EUX to SM-F721B SRI, dirty flash.
Worked fine, it feels a little more smooth but I was expecting more changes tbh.
EUX upgrade live today for me.
One day later for me. Also EUX.
acytoo said:
I knew that u1 is the Google Fi version. But what exactly is the software different between the two? You can use non fi sim card on an u1.
Click to expand...
Click to collapse
The only difference between the two is the carrier (U) firmware has carrier specific features, not apps, that aren't in the unlocked (U1) firmware. For example, people who have AT&T as their carrier, such as myself, can get AT&T's 5G+ an I have no idea what AT&T's 5G+ even is. Also the U1 version isn't the Google Fi version, I'm guessing when you buy a Google Fi Z flip they use the unlocked variant and just put a sim card inside of it.
krusir said:
Thank you. I will try it when I find download link.
Click to expand...
Click to collapse
In case you haven't found it yet, and one UI 5 is out, you can use samloader, which is a terminal/command line tool that allow you to download firmware straight from Samsung's servers. On Linux it is as simple as running pip install git+https://github.com/samloader/samloader.git and on windows I don't know what to do as I don't primarily use it. The only Idea I have is to download python for windows, clone the repository and copy the files to the same directory of python.exe.
The command to download the firmware using samloader - samloader -m SM-F721U -r TMB -v F721USQU1BVK3/F721UOYN1BVK3/F721USQU1BVK3/F721USQU1BVK3 -o <name of file, e.g. flip4-oneui5.zip or SM-F721U-OneUI5.zip>
I have a Russian (thanks Amazon !!) Redmi 9a 32Gb/2gb. It is currently running latest 12.0.x ROM version, but i would like to upgrade it to 12.5.
I see on xiaomi ROM site there is currently a 12.5.x version for Russian version, but the OTA never arrived and if i download the recovery zip file and install it manually, it fails verification and stops.
Is there a way to install 12.5 without unlocking the bootloader ?
Is 12.5 supported on this specific redmi 9a ?
thanks !
mmm... spflashtool might work, but Ive only ever used it on a bircked device to unbrick it, never on a functional device to just change the ROM version, but if you really wanna do it without unlocking bootloader thats your best choice.
I will say anyway, its probably safer to unlock bootloader install recovery and install the rom from there, its your call tho.
Heres how I unbricked my device
[GUIDE] Unbrick hard-bricked device
Condition Phone does not turns on Phone not detected via USB Phone handshake/memory hash failed Requirements Unplug battery Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM Download Scatter File for 12.5.4.0.RCDMIXM Download SP Flash Tool Download...
forum.xda-developers.com
here are some useful files
REDMI 9A - Google Drive
drive.google.com
Thanks
Right now I cannot unlock the bootloader, maybe in the next months I might try (I want to wait for the warranty to expire). My concern is that my version of Redmi 9A with just 2G of Ram is actually not compatible with MIUI 12.5. The 12.5 rom is actually available, but OTA will leave me in the 12.0 branch and verification fails if I try to install the ROM manually. I would not want to brick it by installing an unsupported ROM.
My phone model is M2006C3LG and the ROM I have right now says I have 1.8Gb of available RAM, I don't think you have a different device from mine.
Im a total n00b so I may be wrong about this next thing, but, I think the only difference is what version of MIUI they were sold with since the hardware doesn't allow downgrades further than the stock ROM that came with the device.
There is always antirollback after MIUI 10, but I think its even further locked for the original stock ROM that came to the device, but yeah, this is all my own speculation due to a bricking incident I faced.
The model number is the same, but the 9A was available with different sizes of RAM 2 or 3 or 4 Gb. Mine is the low end 32/2 which is the model still on sale today. If you still have 1.8 Gb of free RAM you very likely has the 3 or 4 GB model.
Maybe you are right, the OTA allows only for updates within the same MIUi version; I saw several guides on-line and i think i will try the miflash tool and switch to the global version. I have to find a way to unlock bootloader without Xiaomi account (no way in hell I'm signing up for that) and without sim card (this phone is used as a smaller wi-fi only tablet). There are some tools for an offline unlock, I will try those first.
It is incredible how Xiaomi is making it complex just to update to a stable official ROM; given also how much bloatware is shovelled with the stock ROM, I'm not sure I will ever consider Xiaomi again.
enryfox said:
The model number is the same, but the 9A was available with different sizes of RAM 2 or 3 or 4 Gb. Mine is the low end 32/2 which is the model still on sale today. If you still have 1.8 Gb of free RAM you very likely has the 3 or 4 GB model.
Maybe you are right, the OTA allows only for updates within the same MIUi version; I saw several guides on-line and i think i will try the miflash tool and switch to the global version. I have to find a way to unlock bootloader without Xiaomi account (no way in hell I'm signing up for that) and without sim card (this phone is used as a smaller wi-fi only tablet). There are some tools for an offline unlock, I will try those first.
It is incredible how Xiaomi is making it complex just to update to a stable official ROM; given also how much bloatware is shovelled with the stock ROM, I'm not sure I will ever consider Xiaomi again.
Click to expand...
Click to collapse
In my opinion, DON'T UPGRADE. I upgraded it with recovery and fastboot and my phone got an message everytime when I boot it : dm verity corrupted and I will need to press power button again to work. Maybe i didn't did that correctly ( I have Global 12.0.20 32/2gb)
Rares6567 said:
In my opinion, DON'T UPGRADE. I upgraded it with recovery and fastboot and my phone got an message everytime when I boot it : dm verity corrupted and I will need to press power button again to work. Maybe i didn't did that correctly ( I have Global 12.0.20 32/2gb)
Click to expand...
Click to collapse
Thanks for the info. So you upgraded to latest 12.0 without moving to 12.5, any reason for not trying 12.5 ? The phone is currently barely usable with Android 10, maybe Android 11 is even heavier, but why not give it a try ?
I saw several youtube videos and guides and by using MI Flash with a Fastboot image (scattered tgz) it should be a total reflash of the phone.
enryfox said:
Thanks for the info. So you upgraded to latest 12.0 without moving to 12.5, any reason for not trying 12.5 ? The phone is currently barely usable with Android 10, maybe Android 11 is even heavier, but why not give it a try ?
I saw several youtube videos and guides and by using MI Flash with a Fastboot image (scattered tgz) it should be a total reflash of the phone.
Click to expand...
Click to collapse
Idk, android 11 may will use more resources but give it a try , good luck
The updates come over time so we must have patience
the_arxyn said:
The updates come over time so we must have patience
Click to expand...
Click to collapse
True but sometimes u won't get the update
Rares6567 said:
True but sometimes u won't get the update
Click to expand...
Click to collapse
in this situation flash the wanted version via recovery or fastboot
the_arxyn said:
in this situation flash the wanted version via recovery or fastboot
Click to expand...
Click to collapse
Yea.