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.
With the differences between the EU, Global variants, and software versions listed in the threads I've gone through, I am having trouble finding a guide that I am sure would be applicable to root my Oneplus 9 LE2117 11.2.5.5-LE54CB. (T-Mobile)(US)
My device is SIM unlocked, and the bootloader is unlocked, but I am unsure of the best method to root.
Could anyone point me in the right direction?
Follow the steps to install magisk.
Superguy said:
Follow the steps to install magisk.
Click to expand...
Click to collapse
Thanks for the response. I believe that's the last step I have to complete to be done, but that is where I seem to be getting lost. I can't find a boot image for the specific model and software numbers I have. From the threads I have read I think I could use the boot image for software version 11.2.2.2 but I am uncertain.
I went ahead and used the boot.img for 11.2.2.2 and it looks like it worked.
captain_howdy said:
With the differences between the EU, Global variants, and software versions listed in the threads I've gone through, I am having trouble finding a guide that I am sure would be applicable to root my Oneplus 9 LE2117 11.2.5.5-LE54CB. (T-Mobile)(US)
My device is SIM unlocked, and the bootloader is unlocked, but I am unsure of the best method to root.
Could anyone point me in the right direction?
Click to expand...
Click to collapse
You need 11.2.5.5 boot.img from any region. Then follow the instructions install magisk.
just use the AA image for tmobile. patch the image with magisk the file will go to your download file then fastboot boot the img file from the one get from magisk after patching and you will gain temp root. direct install with magisk and reboot. if you get into a bootloop. reset devices from recovery and you will still retain root after the reset. i have installed empty slot ota and direct install. bootlooped on ota empty slot but reset from recover fixed problem instantly and retained root. direct install no bootloop retained root.
Does anyone care to comment with insights or experiences in regards
to Rooting with Magisk which will allow for the installation on a Custom ROM at a later time -
that is, when a stable Lineage OS for example is available for the OP-9 (t-Mobile) ?
Thank You in Advance !
I doubt it but anything is possible. with the process to convert to different variants being fairly simple and accessible there will be very little focus on that particular software. It is compatible with gloabal pathched boot image to gain root and from there your pretty much able to customize to do what ever your heart desires.
Superguy said:
Follow the steps to install magisk.
Click to expand...
Click to collapse
Can you direct me where to find that ?
I'm having difficulties getting anything to work...
If you are on the latest Tmobile update,you can use 11.2.8.8.img from either AA,BA or DA. the boot.img are all the same.
Click to expand...
Click to collapse
I'm on 11.2.6.6.LE54CB - and I thought the end two letters were Important ?
avid_droid said:
Negative. Letters don't matter. The latest update from T-Mobile normally correlates with the latest of AA,BA,DA. If you are on the 11.2.6.6 it's 11.2.8.8. any of the boot.img will work.
Click to expand...
Click to collapse
See, the thing is, I was so accustomed to having an Un-Locked device from t-Mo, I didn't realize that the Awesome Dude who un-locks the SIM, does not actually un-lock the Phone. So Much Bull**** from t-Mo...
ANy-Hoo... I just applied thru the OP site to get my 9 completely un-locked.
Thank You for Your Time and Response!
avid_droid said:
Negative. Letters don't matter. The latest update from T-Mobile normally correlates with the latest of AA,BA,DA. If you are on the 11.2.6.6 it's 11.2.8.8. any of the boot.img will work.
Click to expand...
Click to collapse
Quick little bump, but I'm on 11.2.7.7.LE54CB. Has anything still changed or would I still be good to go to use the 11.2.8.8. boot.img to root or the latest 11.2.9.9.LE25AA from OnePlus's site directly?
I have managed to install the Eurepean 11.2.9.9.LE15BA for the 9 PRO le2117
I have the tmobile 9 5g version not the pro. camera doesnt pull up but otherwise runs fine
Need help here! I forgot to backup my oneplus 9 pro LE2127 when I tried to root my phone using TWRP，and I installed TWRP in my phone's boot partition which wiped out all data in that partition. I used TWRP side loaded Global ROM to recover my phone but the phone doesn't have any signal with sim card in. Used MSM tool backe to T-Mobile 11.2.5.5 and still same problem, sim card can be read but no signal. Flashed T-Mobile modem but modem b failed, it says no such partition.
Bought this phone from third party. Any suggestion is appreciated.
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Good news! so you've manged to root Android 12? if so, what steps did you take?
beanbean50 said:
Good news! so you've manged to root Android 12? if so, what steps did you take?
Click to expand...
Click to collapse
Android 12? No, I'm on 11.
TarikVaineTree said:
Android 12? No, I'm on 11.
Click to expand...
Click to collapse
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
VerdandiAmine said:
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
Click to expand...
Click to collapse
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
beanbean50 said:
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
Click to expand...
Click to collapse
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
TarikVaineTree said:
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
Click to expand...
Click to collapse
I've finally managed to root Android 12 after weeks of trying.. Yippee..!
TarikVaineTree said:
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
Click to expand...
Click to collapse
Using phone info my correct CSC is VAU. The software I used to get firmware is Frija and I deployed it with Odin.
So flash the magisk patched boot.img file to AP via Odin as well as flash the firmware BL file to BL? Okay I will try this with VAU firmware and report back with what happens.
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>
Hello,
I bought a Motorola Edge 30 NEO a couple of weeks ago.
Official Page
GSM Arena Review
Unfortunately I couldn't find a corresponding device on this site, so please condone that i'm posting here.
Now for my questions:
Is it possible to install Lineage 19? Currently just Motorola Edge 30 codename "dubai" is officially supported. List of builds
Has anyone tried to install a "dubai" nightly release on the Edge 30 NEO?
Is there a release planned in the future?
Many thanks!
I am unfamiliar with the Motorola Edge, but from what I understand, it is a Project Treble compliant device with an accessible bootloader. All you have to do is flash a LineageOS GSI to /system through ADB: fastboot flash system <drag and drop LineageOS.img here>
@AndyYan has a thread here for the LineageOS 19.1 GSIs; he is also working on 20.0. Keep in mind that if you want Gapps, you'll need to flash an image preloaded with Gapps (one of the bgN builds), and for root, you'll need to patch your boot image in Magisk.
Also, remember that a GSI does not include a kernel, so you can either use your stock kernel, or a custom one. YMMV.
Thanks! I'll take a look
Somebody tried it?
also interested in neo
I have an edge 30 neo & followed the instructions for dubai but after the step of flashing the recover using fastboot flash boot lineage-20.0-20230202-recovery-dubai.img and then restarting, now it's stuck in a boot loop.
It eventually exits, saying Failed to boot. Falling back to fastboot. No bootable A/B slot.
I flashed it to slot a and to slot b, and it's stuck in a boot loop when I restart it. no good so far.
I had to restore it to factory condition using the lenovo rescue tool.
None of the dubai recovery images would work. they all ended up making the phone go into a boot loop.
Rescue and Smart Assistant (RSA) - Lenovo Support US
support.lenovo.com
un_mensch said:
Hello,
I bought a Motorola Edge 30 NEO a couple of weeks ago.
Official Page
GSM Arena Review
Unfortunately I couldn't find a corresponding device on this site, so please condone that i'm posting here.
Now for my questions:
Is it possible to install Lineage 19? Currently just Motorola Edge 30 codename "dubai" is officially supported. List of builds
Has anyone tried to install a "dubai" nightly release on the Edge 30 NEO?
Is there a release planned in the future?
Many thanks!
Click to expand...
Click to collapse
Edge 30 neo code name is miami
How am i able to ask the developers for a build for the 30 neo
Release MMI-S3SSMS32.34-46-1-1 · MotorolaMobilityLLC/kernel-msm
miami push for android 12
github.com
not a dev myself (far from it), but this could be it. now if someone could put his interest in it. how many 30 neo owners do we have here? perhaps we could sponsor a device to someone willing to keep developing LOS over it? it just happen to edge 40 pro thanks to (mostly) @mxz55 and @ThE_MarD.
I would love los ln my edge 30 neo! Im up for support
+1
I am on the bandwagon!
+1
I am also waiting for the Moto Edge 30 Neo Lineage build, this phone is a missing element in range of oversized devices. I am willing to donate the effort.
+1.