Related
Hi everybody. I've been working on making rom's for our amazing device (g Flex 2), mine being a h950 with h950PR rooted firmware on it. .. Now I've come in to some difficulty (understatement). Long Story Short, I was wondering if anybody possesses proper Source Build Tree Files for the Flex 2.
Looking for the files on the web, I have come to no avail, well, ONE tree I did find was for an outdated version of cyanogen mod... and even that was incomplete... and in its code it points to a thousand (exaggerating) other phones in its tree codes. making it a debuggers worse nightmare.
I'm here today to ask of my esteemed fellow XDA developers... Does anybody possess the G Flex 2 Build Tree Files requires to successfully build a rom for our great device? Writing all the files by hand myself will take, forever, indeed we may even have a G Flex 3 by then....
May anybody please pleaser help me out
P.S. I know the boot loader is locked... for now...
constnt.mcc said:
Hi everybody. I've been working on making rom's for our amazing device (g Flex 2), mine being a h950 with h950PR rooted firmware on it. .. Now I've come in to some difficulty (understatement). Long Story Short, I was wondering if anybody possesses proper Source Build Tree Files for the Flex 2.
Looking for the files on the web, I have come to no avail, well, ONE tree I did find was for an outdated version of cyanogen mod... and even that was incomplete... and in its code it points to a thousand (exaggerating) other phones in its tree codes. making it a debuggers worse nightmare.
I'm here today to ask of my esteemed fellow XDA developers... Does anybody possess the G Flex 2 Build Tree Files requires to successfully build a rom for our great device? Writing all the files by hand myself will take, forever, indeed we may even have a G Flex 3 by then....
May anybody please pleaser help me out
P.S. I know the boot loader is locked... for now...
Click to expand...
Click to collapse
bootloader is locked
I did with aosp a time ago, but security error 9.
So the bootloader not only locks the kernel, It locks system too.
So you can mod /system, but some changes locks bootloader, and with a custom rom, there is no way...
We need unlocked bootloader to do this.
pelelademadera said:
bootloader is locked
I did with aosp a time ago, but security error 9.
So the bootloader not only locks the kernel, It locks system too.
So you can mod /system, but some changes locks bootloader, and with a custom rom, there is no way...
We need unlocked bootloader to do this.
Click to expand...
Click to collapse
damn... I appreciate the reply though. I know LG has released a process for unlocking the G4 (Europe Edition)... I’ve begun working on seeing if there’s a way to port that (after all some of our roots were based off G4's).. though the board is not a msm8994.... and there process involves you sending them your phones info... damn Safe Boot why, why do you do this to us. (I ran into this same issue porting linux kernel to my Hp ah155nr laptop) Anyway I’ve been exploring Qualcomm's tools, and using other Snapdragon 810 boards builds... one day we will have this working....
Hi I have seen a method used in the past on LG devices to root using the LAF partition. Certain devices, like the LG G2, had fastboot turned off so people "nuked' the LAF partition (where LG keeps their download mode) as in here, which allowed for fastboot to be able to be accessed.
I also saw a post here where someone was discussing flashing a custom recovery directly in place of the LAF partition so the button combination to access the download mode would instead boot into recovery.
I understand that since the T-Mobile LG G5 has an unlocked bootloader it should be a simple thing to get a custom recovery on our device. However, it has still been a challenge. For those more knowledgable than me please let me know if this is at all a possibility.
On an unrelated note:
A Vietnamese dev team has gotten root on the LG V10 H901 on Marshmallow. Hopefully that bodes well for us also!
http://forum.xda-developers.com/tmobile-lg-v10/general/hopefully-root-h901-t3374723
arjuna) said:
On an unrelated note:
A Vietnamese dev team has gotten root on the LG V10 H901 on Marshmallow. Hopefully that bodes well for us also!
http://forum.xda-developers.com/tmobile-lg-v10/general/hopefully-root-h901-t3374723
Click to expand...
Click to collapse
yes, for sure. on tmo G5 it's the same method for sure.
Maybe another method different from one Codefire used.
We will see
arjuna) said:
On an unrelated note:
A Vietnamese dev team has gotten root on the LG V10 H901 on Marshmallow. Hopefully that bodes well for us also!
http://forum.xda-developers.com/tmobile-lg-v10/general/hopefully-root-h901-t3374723
Click to expand...
Click to collapse
That is awesome news!
I've been on mm 6.0 and back to 5.1 .
I restored a twrp 5.1 recovery directly back from 6.0 using twrp . My boot loader
Is unlocked and I've used my own rooting
Method and flashifyed my twrp on both lp and mm. Since i'm on 5.1j with my bootloader still unlocked indicated on my
Splash screen can i safely flash the skinny rom on my metro g stylo with out a boot loop or a soft brick
Why did you go back to 5.1 if you wanted to flash the Skinny ROM?
I am going to try this Skinny debloated ROM soon. I have rooted T-Mobile Marshmallow on my MetroPCS Stylo and am missing some features that didn't flash correctly on my T-Mobile marshmallow.
I am always building stuff. I was working on a complete one click unlock Bl, Root and twrp and then another mm Rom build or two.
I always go back to my own builds cause I personalize them just for me but ran across the skinny while surfing and it caught my attention. I've been around for years and been doing this as a hobby since i retired and keeping myself busy.
viperdink said:
I am always building stuff. I was working on a complete one click unlock Bl, Root and twrp and then another mm Rom build or two.
I always go back to my own builds cause I personalize them just for me but ran across the skinny while surfing and it caught my attention. I've been around for years and been doing this as a hobby since i retired and keeping myself busy.
Click to expand...
Click to collapse
Makes sense now.
Let me know how it goes when you (if) flash that Skinny debloated MM ROM.
I am curious if it works and if all the features like advanced text msgng and video calling and all the MM stuff is on it.
This rom works great so far. With the metro update and this it shouldn't take much to get both versons 6.0 mm. Sure would get custom roms going.
Thanks for your enlightenment.
Skinny Rom works great. The new MS63120B_00_0429.KDZ IS OUT. My Metropcs version phone can be set back to stock and I was wondering If using the new LG UP flasher will care that My Bootloader is UnLocked. I don"t know if it will Interfer and check its status.
viperdink said:
Skinny Rom works great. The new MS63120B_00_0429.KDZ IS OUT. My Metropcs version phone can be set back to stock and I was wondering If using the new LG UP flasher will care that My Bootloader is UnLocked. I don"t know if it will Interfer and check its status.
Click to expand...
Click to collapse
thats a good question...i sure hope it doesnt matter to that tool that the bootloader is unlocked...if for some reason it did, maybe you could use lg flash tool 2014 and flash the lollipop kdz?
I went from t--mo mm to metro Loli..to get the metro mm...
I noticed that the bootloader was still unlocked after the Loli flash and kinda got concerned...
But, it never caused any probs...updated to mm metro and rooted smoothly....
I was kinda wondering if i could just wipe and flash skinny without extra caution and precautions...and then if i thought it was ( in my own opinion I'm entitled to) kinda not what i want..flash my mm metro back up...
Doesn't seem like it's been done..i could be wrong..
The drive to dev for this phone isn't as strong as i was hoping...
But, being the first android I've kept vanilla rooted with few tricks...it's not disappointing.
@Cyconumnum
Does the splashscreen still show
" unlocked bootloader "
And did you take the ota or
Flashed metro mm with lg up or the 2014 tool
I don't know what was debloated. The "Skinny" ROM itself is fine but what was taken out?
viperdink said:
@Cyconumnum
Does the splashscreen still show
" unlocked bootloader "
And did you take the ota or
Flashed metro mm with lg up or the 2014 tool
Click to expand...
Click to collapse
I used the flash tool to flash metro lollipop..
After that I went into fastboot to unlock the bootloader ...and it reported to be already unlocked...
It still showed "bootloader unlocked" at the top of the LG splash on the initial metro lollipop boot...
And reported it again booting the metro mm update
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
Sorry..the LG flash tool
I'm back on my personal juicy lp. I gotta get some new fast sd cards. I am working on another twrp for a friend in my spare time and have to hold up on roms and the total one click project. I would like to do the kdz 6.0 but i need parts .
Update; Found 16gb class 10 and worked skinny Rom, metro ota, and lg up flash tool. They both, metro ota and Lg Flash Kdz never showed skinny rom id'd. It said unknown device firmware. So bye bye skinny Rom. They both left the bootloader unlocked when finished flashing metro updates. As i stated before adb pkg and SuperSu needed updating and reinstalling for root and recovery was required. Splash screen still indicated an unlocked bootloader and loading the kdz from 5.0 kept data partition and required all out of date apps to be updated. Namely goggle playservices, adaway 311 needed (thanks guys) and xposed modules i uninstalled till I get time. Advance messageing was an Lg update not inclued in metro updates. Plenty of bloatware to lighten the load but still seemed less than skinnys bloatware. Good to be back on metro software and all the advance messaging and video calls worked. Now i DO gotta get more new sd's. Really out of parts to work with . Going to best buy to hold me over..
CHEERS ALL hope it helps you guys.
Edit; Forgot to add "Quickboot.apk" works 100% take you into all available modes.
i'm actually really content with it being on a stock rooted with various mods.....wish i could get the soft buttons to theme..that's nothing bad thou lol..
MM is a nice environment ..i wish i could install themes from cm13 .....but, as much i do ..i'm not gonna brick my phone with themes...did it before just changing the font on my F6...ha
but, it's great....makes enough sense....
my guess about the bootloader not getting changed with the ROM would be a bios type thing...i'm not toooo android savy..
Cyconumnum said:
i'm actually really content with it being on a stock rooted with various mods.....wish i could get the soft buttons to theme..that's nothing bad thou lol..
MM is a nice environment ..i wish i could install themes from cm13 .....but, as much i do ..i'm not gonna brick my phone with themes...did it before just changing the font on my F6...ha
but, it's great....makes enough sense....
my guess about the bootloader not getting changed with the ROM would be a bios type thing...i'm not toooo android savy..
Click to expand...
Click to collapse
I like the Stock ROM. There are several options for themes.
Layers in the Play Store
G4 Tweaksbox (requires root)
LG Apps Theme Engine (requires root)
LG SmartWorld (no root required but only available on Marshmallow T-Mobile Stylo ROM)
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.
You can manually update to latest Android 11 (April patch)
Bootloader unlock may be required.
Download the ROM https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml.zip
Unpack the zip and enter bootloader (turn the phone off and press and hold volume down and power it on)
Flash everything EXCEPT radio.img. Failure to do it will result in NO SIM error!
Everything is better with this version ROM. Do not update to Android at this time because it's a mess.
I manually upgraded to A12 on my XT2141-2 as soon as I was able. The only issue I've had was SIM not detected with 1 specific Lsposed module enabled, disabling that one module resolved that though. And ofc not having Gravity Box yet kinda sucks but I've had a blast with new theming possibility with A12 thanks to Repainted and Project Themed apps.
Could you elaborate on any issues you experienced yourself?
Sorry to have to ask this, but what happens if I somehow screw things up? unless I'm mistaken there's no TWRP for this phone (yet) to help with recovery...and how might I go about backing things up before I try to flash a new ROM build on my device? (Still new to things)
edit: addition: probably a stupid question, but I've only ever flashed the `boot.img` file, am I supposed to "fastboot flash" every file over?
ruq said:
Sorry to have to ask this, but what happens if I somehow screw things up? unless I'm mistaken there's no TWRP for this phone (yet) to help with recovery...and how might I go about backing things up before I try to flash a new ROM build on my device? (Still new to things)
edit: addition: probably a stupid question, but I've only ever flashed the `boot.img` file, am I supposed to "fastboot flash" every file over?
Click to expand...
Click to collapse
will this unlock verizon edge 5g
jakethesnake24 said:
will this unlock verizon edge 5g
Click to expand...
Click to collapse
No. Everything I've read states that Verizon Phones are hard-locked-down and cannot be rooted, unless there exists or is discovered at some point in the future an exploit to crack such phones. Sorry if that means you're out of luck.
I believe the preferred way of having a rootable phone is to always outright purchase it independently of any carrier. I purchased mine unlocked at a Best Buy.
In case anyone is reading this and getting a 404 on the OG post link for the ROM I found it under this updated link.