I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it
BWA_Dallas said:
I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it
Click to expand...
Click to collapse
So, if it's rooted, you won't get an update, or rather you won't be able to apply it. So it won't 'break' root, it just won't happen.
Sure, just crossflash to the newer rom, it has no effect on root. Doing so doesn't affect root, it will stay exactly as it was prior to crossflashing.
BWA_Dallas said:
I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it
Click to expand...
Click to collapse
Forgot you're using an at&t rom, and those kdz aren't available. So, choices, go to an 'open' rom, which should have much of the at&t functionality, but maybe not all. Or, re lock the boot loader, do the update ota, and then root it again.
Be careful though, to relock a boot loader the rom has to be completely stock, no mods whatsoever.
personally, I'd just go with one of the 'open' roms... and I'd never use at&t lol, but that's just me.
AsItLies said:
Forgot you're using an at&t rom, and those kdz aren't available. So, choices, go to an 'open' rom, which should have much of the at&t functionality, but maybe not all. Or, re lock the boot loader, do the update ota, and then root it again.
Be careful though, to relock a boot loader the rom has to be completely stock, no mods whatsoever.
personally, I'd just go with one of the 'open' roms... and I'd never use at&t lol, but that's just me.
Click to expand...
Click to collapse
Do you have a particular open rom you recommend?
BWA_Dallas said:
Do you have a particular open rom you recommend?
Click to expand...
Click to collapse
LG G820QM(LMG820QM) aka LG G8 ThinQ - LG-Firmwares.com
LMG820QM download the firmware for free! Detailed installation instruction. Video review of the model and its features. User feedback and latest news.
lg-firmwares.com
I'd suggest the USA version, it's the us open, should have all the functionality for all the carriers, minus the bloatware.
Except for one thing, some carriers, like at&t, have in the past, not sure if they still do, limit things like volte ability to just their phones / roms.
that, and because they don't make their kdz available, I would never use them.
Related
New firmware T700ZSU1ANL1 and T800ZSU1ANL1 (Hong Kong both).*
Can i install these in europeans tablets?
Thanks
Any ideas?
I have installed it on the US WiFi only version, so I don't see it being a problem, if it doesn't install you can always Odin back to your stock rom... if you have a 3/4g type tablet then you may want to not flash it..... I'm digging the new kernel personally.
Itchiee said:
I have installed it on the US WiFi only version, so I don't see it being a problem, if it doesn't install you can always Odin back to your stock rom... if you have a 3/4g type tablet then you may want to not flash it..... I'm digging the new kernel personally.
Click to expand...
Click to collapse
Thanks
I have installed it in european firmware, portuguese one to be exact (FNAB), no issues at all.
Zootopia said:
I have installed it in european firmware, portuguese one to be exact (FNAB), no issues at all.
Click to expand...
Click to collapse
I installed, thanks, no issues.
Tavocampana said:
I installed, thanks, no issues.
Click to expand...
Click to collapse
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Restorer said:
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Click to expand...
Click to collapse
Theres an app calplled root cloak to hide root from apps. I dont really care on being on stock rom just to get ota lollipop. There would most liekly be a custom rooted lollipop rom when lollipop is out.
DUHAsianSKILLZ said:
Theres an app calped root cloak to hide root from apps. I dont really care on being on stock rom just to get ota lollipop. There would most liekly be a custom rooted lollipop rom when lollipop is out.
Click to expand...
Click to collapse
Unfortunately none of the cloaking apps work on Sky Go or Barclays and other banking apps. Neither does RootCloak or RootCloak Plus Xposed mods .
That is why I asked the question. Not really bothered if it just means losing OTAs - provided everything else is still 100% official unrooted after Odin upgrade of UK tab with HK firmware. That's why I ask will this be the case?
Restorer said:
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Click to expand...
Click to collapse
I do not know.
My intention when the Lollipop version is released is to repeat the procedure and flash via Odin. I live in Argentina and here things come too late.
Tavocampana said:
I do not know.
My intention when the Lollipop version is released is to repeat the procedure and flash via Odin. I live in Argentina and here things come too late.
Click to expand...
Click to collapse
Yeah, I'd do that too. But these apps are too important to me to risk losing them so I will probably just chicken out and wait for the OTA. Thing is, if the update works, I can't see any reason why the root-checking apps would be able to tell except if they were spotting non-UK codes. I do know their checks are a lot more sophisticated than looking only for the presence of SU and busybox. They for sure examine parts of the kernel and the DRM files as well.
My logic tells me that if the apps don't work with the HK firmware then all I need do is to flash back to the official UK XXU1 version. That's why I am just asking is anyone knows of any other differences that might be exposed using the Odin method to update?
Dear LG Friends,
Long time XDA member, coming from the Windows Phone days HTC, then to Android HTC, bunch of Samsungs, and am now thinking about the LG space. More specifically moving from the Note 3 (T-Mobile US) running on the AT&T US, to the LG G3.
Before I do, I need some help from you guys. Which variant should I go for? I know my primary choices will be the T-Mobile and the AT&T variants (I believe they are 851 and 850)? Based on what's important to me, below, can you guys advise which variant to get?:
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
2. This is related to # 1 - But I heard that only T-Mobile has the unlocked Bootloader? However, doing some research, I believe the AT&T and the Verizon and Sprint variants can also be unlocked? Is this true? If so, are they anymore limited than the factory unlocked T-Mobile variant?
3. LTE bands - I will most likely be using the phone on AT&T US, but if development options/support are higher on other variants, I might consider buying those models, even if they are missing some AT&T bands. For the Note 3 - T-Mobile is a Pentaband phone, meaning it had all the bands needed, so it could easily work on AT&T LTE, all the time. The reverse was not true.
And basically that is it. Initial instinct says to go chase the T-Mobile variant, based on my needs above. But please educate me and help me out if I have missed something. Thank you so much in advance!
Any input guys?
ProFragger said:
Any input guys?
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
Click to expand...
Click to collapse
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates and that means missing out on necessary fixes
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it. It essentially just makes installing TWRP easier since you dont have to root before installing it unlike other variants
Nevertheless Lollipop can be rooted on all US Variants right now really easily. But the only downside to it is that removing custom roms sometimes can be a pain since you have to use a way where it sometimes works and sometimes doesnt
itsbighead said:
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it
Click to expand...
Click to collapse
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !
ProFragger said:
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !
Click to expand...
Click to collapse
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.
itsbighead said:
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.
Click to expand...
Click to collapse
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!
ProFragger said:
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!
Click to expand...
Click to collapse
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way
itsbighead said:
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way
Click to expand...
Click to collapse
This is helpful, once again bud. So how would I downgrade back to KK? Would I have to run a stock firmware of some sort? In Samsung, he Flash a .Tar file through their flashing tool called the Odin. Would that be similarly done here?
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
FoxyDrew said:
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
Click to expand...
Click to collapse
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
DarkMidnight said:
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
Click to expand...
Click to collapse
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
For me a lot of it is this is not the most conventional root, not very stable for me and battery life suffered a lot compared to stock, and flashing U firmware has not been very cooperative for me.
So thoughts.... I am on the latest U firmware on my 930V. Should I consider flashing back to the stock Verizon rom? Everything is working great. I do plan on jumping ship from Verizon in the next year or so. I am blown away at how well this phone runs stock and only flashed the U in preparation to take it to another carrier afterwards. Is this a bad idea?
Tried to live with root, but the battery and stability was horrible. Now, I am using the engboot to do any data back up or restore tasks in TiBU then flashing the AP again to unroot. Data is maintained, but now I have to live with ads. I use adguard, by it feel like it hurts battery life. Will try and quantify that soon.
Being able to count on my phone to make a call and hold a charge is too important to me. Rooting the phone to set it up after a reset saves me time. Unfortunately, rooting with our current method is too prohibitive for daily use.
nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
Same here.
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
nrage23 said:
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
Click to expand...
Click to collapse
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
craazy82013 said:
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
Click to expand...
Click to collapse
Been using the same ROM for almost a week with xposed and everything is fine. I feel great without seeing the ads again. haha! BTW, I didn't try the nearby devices so no comment on that.
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Has anyone with ph1 tried flashing another rom such as stang5litre?
dBunny said:
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Click to expand...
Click to collapse
So how did you root if you can't downgrade like the OP stated?
craazy82013 said:
Has anyone with ph1 tried flashing another rom such as stang5litre?
Click to expand...
Click to collapse
Yes it works just fine.
bart77 said:
So how did you root if you can't downgrade like the OP stated?
Click to expand...
Click to collapse
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
So you can't Odin flash back to a stock image if you get in trouble or want to unroot. I guess I'll stay on PG5 for now.
I'm not rooted now, but was able to disable system update notifications using
https://play.google.com/store/apps/details?id=com.hecorat.packagedisabler
By disabling:
System updates (com.samsung.sdm)
System updates (com.samsung.sdmviewer)
and securitylogagent
FoxyDrew said:
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
Click to expand...
Click to collapse
Thanks @FoxyDrew for clarifying that... and I agree.
I used the following GUIDE to root APH1 on my S7 Flat: http://forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
craazy82013 said:
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
Click to expand...
Click to collapse
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image.
Sent from my VS987 using XDA-Developers mobile app
bart77 said:
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image. So if something goes wrong, you have no means of recovery back to stock since there is no ph1 stock Odin image.
Sent from my VS987 using XDA-Developers mobile app
Click to expand...
Click to collapse
The ph1 image is available at this link (http://updato.com/firmware-archive-select-model?record=78F84FCD811E11E69B2DFA163EE8F90B). I have flashed with these files and they work perfect.
Seems bootloader was uograded to version 3. So may be possible to flash between tmo and vzw and vice versa. Both now have v3 bootloader.
Hi. I've posted this under the liniage thread, but I'm hoping more people will see it here since it's not a liniage specific problem, but rather something to do with my device or me. Any help would be greatly appreciated:
I am on the stock Samsung u3 Q firmware and I cannot get any custom Rom working, except for DR. Ketan which is based on the Samsung stock, but otherwise works great, root and all. My main purpose is to get to u1. I've tried liniage 17, 16, lightrom, crdroid and nemesis, all with the same result: after successfully flashing in TWRP, the phone restarts and does not boot. first it does another restart, then goes into download mode on some roms, and recovery in others. I'm sure I'm missing something, or doing something wrong, but I can swear I've followed all the instructions. Any guess to what that might be, or what I can try?
By u3 and u1 you mean bootloader versions?
winol said:
By u3 and u1 you mean bootloader versions?
Click to expand...
Click to collapse
Yes, the security on the boot-loader. Any since all official firmware check, that's not an option. But as long as I'm able to run a custom rom, I should be good, I think.
There is no roll back with bootloaders, I have never tried something of the sort, but it has been said over and over again that bootloaders can not be downgraded
Would that mean that any device with a higher than u1 bootloader will not work with custom roms? That doesn't sound right to me.. Perhaps I haven't asked my question well enough, so first, I'd like to figure out why custom non-samsung based roms all fail on boot.
mancaalberto said:
Would that mean that any device with a higher than u1 bootloader will not work with custom roms? That doesn't sound right to me.. Perhaps I haven't asked my question well enough, so first, I'd like to figure out why custom non-samsung based roms all fail on boot.
Click to expand...
Click to collapse
You said you were on U3. If so, you cannot load ANY rom with a U1 bootloader. Period.
Sent from my SM-N975U1 using Tapatalk
mancaalberto said:
Would that mean that any device with a higher than u1 bootloader will not work with custom roms? That doesn't sound right to me.. Perhaps I haven't asked my question well enough, so first, I'd like to figure out why custom non-samsung based roms all fail on boot.
Click to expand...
Click to collapse
All firmwares, or ROMS, official or custom, have a bootloader version, newer ones have higher number version, you can not install anything with a lower bootloader number than the currently installed one, no matter if official or custom or whatever, this can not be circumvented in any way, so, if your current firmware has a bootloader 3, (U3) as you posted, you will be able to install roms (custom or official) with bootloader number 3 or higher, that's it, I hope you got it this time
donc113 said:
You said you were on U3. If so, you cannot load ANY rom with a U1 bootloader. Period.
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Not what I was hoping for, but understood. Thank you.
Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.
Which phone version do you have?
luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.
skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing
I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!
TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,
I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.