Related
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.
I have tried to update my chinese XT1635-03 to 7.1.1 with OTA through ADB sideload and unfortunately it is not working.
I have sucessfully flashed the phone with reteu latest firmware with April security patch (ADDISON_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) through fastboot.
But once I try to sideload 7.1.1 OTA (Blur_Version.26.1.22.addison.retail.en.US) the process terminates at 47% with notification that the package expects product name "addison" but actual value is "addison_retcn"
Is it possible to either change the product name or disable such check of product name? It seems to me, that at the moment there is no way to flash OTA and I need to wait for full 7.1.1 image.
Reading similar questions around, I have to ask. Why you people cannot wait couple of weeks to get OTA? Instead of risking to brick your device?
New update is not bringing revolutionary/awesome/amazing/mind blowing... new features. I understand if it's update to completely new Android version or that your device/region will not get update at all.
Sent from my XT1635-02 using Tapatalk
You have XT1635-03 and the update is for XT1635-02. So if you have a reteu phone you can really update over sideload without issues. And yes, I need android 7.1.1 and I wouldn't wait one day longer. I need app-shortcuts, because I had this on my old phone, too. There was android 7.1 since the first day. But if you don't have it before you can't miss it. So you can wait much easier For me it was important for other issues, too. For example Wifi problems and stability fixes and over 100 security fixes. Many reasons for the update
Edit: And one more reason for the update: To help google to get more than 0.6% for android 7.1 We should update all, otherwise android 7.1 will never get 1%
Everybody should help to get this 1% maybe next month. So update, just do it for the 1%, yes xD
:silly::good:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
The point is, how can you change the channel...
freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
OK, makes sense for you but for many/most others is just matter of time.
I'm not blaming anyone. Do whatever you want with your phone, just be ready if something goes wrong
The surprise was a different phone name. Different channel is usually not a problem
freeman_g said:
The surprise was a different phone name. Different channel is usually not a problem
Click to expand...
Click to collapse
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
flashallthetime said:
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
Click to expand...
Click to collapse
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
allrightlite said:
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
Click to expand...
Click to collapse
I have no idea
flashallthetime said:
I have no idea
Click to expand...
Click to collapse
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
allrightlite said:
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
Click to expand...
Click to collapse
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
dandrumheller said:
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
Click to expand...
Click to collapse
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
allrightlite said:
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
Click to expand...
Click to collapse
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
dandrumheller said:
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
Click to expand...
Click to collapse
It feels not like a beta. It's more like a big bug fix with much patches. For example my Wifi is now stable as hell and never reconnections anymore. Hope it keeps stable, but looks very very good. I think this beta will be the final release in few months, or weeks? But it's much better than 7.0. And better than LOS14.1, which is not so stable (on my other phone). And I have no app crashes anymore. Gboard was crashing with 7.0 one time and few other apps like firewall. So, 7.1.1 is pure stable as hell and must have :laugh:
Afaik, it's not beta. It's soak. So, if test users reported as stable, it will be pushed to all as the final build. If not, Moto has to fixed and not all users around the world will be affected.
Regular and recommend way of releasing update.
Sent from my LG-V940n using Tapatalk
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
If you are on XT1635-03 with reteu frmware you will not receice any OTA. My experience told that you can't even sideload an update. So no worry about bricks.
Very often devices are hardbricked when you are downgrading bootloader but once I have hardbricked my Nexus 6 with OTA (sideloading it). Well, it was not full brick, but I can't load the system (only fastboot) and my bootloader was locked. Without system loaded you can't allow unlocking procedure so the first thing I do with new phone is unlocking.
allrightlite said:
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
Click to expand...
Click to collapse
I know the build is not a beta. I'm referring to the fact that once you leave the official upgrade path, taking any update is a scenario not tested by Moto. So you are testing for them. Maybe you win, maybe you brick.
It seems that the problem with "addison_retcn" may be fixed with editing build.prop but in this case systemless root is required (AFAIK there us no systemless root for Nougat)
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
awarman said:
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
Click to expand...
Click to collapse
are you rooted?
Yes but I have removed root and tried, same thing. Cleared dalvik cache, same thing.
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
hallo dare said:
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Click to expand...
Click to collapse
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
awarman said:
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
Click to expand...
Click to collapse
You won't get incremental if rooted, only full updates.
hallo dare said:
You won't get incremental if rooted, only full updates.
Click to expand...
Click to collapse
So in theory, if I unroot then run OnePlus updater I should be able to get the update. Then reboot after. Correct?
Maybe I did something wrong, but I tried unrooting for the last OTA and still received the same error. I had to wait until the full version was on the OnePlus site, I think OnePlus updater grabs the zip from there too. It also took a month longer for the full zip to hit the OnePlus site.
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
I have global unlocked varient and when I first received it I just flashed BA/EU on both slots(local upgrade twice) and I've been able to get all full zip updates(via system updates and/or O2 updater app) staying rooted the whole time. I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Initially I was getting that error. Then I ran the uninstall in Magisk and chose to RESTORE IMAGES. I then just hit retry on the OTA from the phone settings (NOT Oxygen Updater) and the update installed. Initially this did not for 11.2.3.3 as it would still give the error after unrooting by uninstalling Magisk, then it worked for 11.2.4.4 and 11.2.5.5. So YMMV. You can look here for my update process as I was having an issue post-OTA:
No cell service after update to 11.2.4.4AA while keeping root
I'll try to keep this short. Global OP9 Pro on 11.2.2.2AA, bootloader unlocked, rooted w/Magisk. Been trying to find the best way to update. Decided on trying this: 1. Un-rooting by going in to Magisk and doing UNINSTALL->RESTORE IMAGES 2...
forum.xda-developers.com
jammin6996 said:
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
Click to expand...
Click to collapse
This worked, btw. Never had to do this with my OP8P. Hopefully this isn't a regular occurrence.
Shooter7889 said:
I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Click to expand...
Click to collapse
Not knowing that the AA variant would have dog**** updates from the start, and already having restored my old phone's data and not wanting to go through setup and restore again.
Edit: The goal is also to eventually get on crDroid anyway so it's whatever. I'm not resetting until there's an official crDroid build out.
Every time I got update but I can't install it for some reason so I need to do that myself because sometimes updates doesn't work out very well while using a Magisk, so anything idea where I can find LE2127_11_C.19 firmware?
cat139lyleb said:
Every time I got update but I can't install it for some reason so I need to do that myself because sometimes updates doesn't work out very well while using a Magisk, so anything idea where I can find LE2127_11_C.19 firmware?
Click to expand...
Click to collapse
To get OTA updates, you need to uninstall magisk and restore the stock image in the Magisk app. Been there and done that. However, I would suggest staying with Android 11 and not update to A12. A12 is the pits...besides that with A12 you can have custom bootanimation and a custom systemwide font... Just like me. I have the LE2127 OnePlus 9 Pro 5G as well!
cat139lyleb said:
Every time I got update but I can't install it for some reason so I need to do that myself because sometimes updates doesn't work out very well while using a Magisk, so anything idea where I can find LE2127_11_C.19 firmware?
Click to expand...
Click to collapse
Plus T-Mobile doesn't like their builds out there in the wild. You can use msm read back to get images also.
Yeah, I guess you're right. Mine is LE2127_11_C.17, and it is Android 12... I don't see any problem or bug coming to me, but we noticed two problems: an annoying update from itself (need to install C.19) and recovery firmware. Unfortunately, I have no idea how to install custom recovery firmware; maybe you have any idea for me?
Oh! I almost forgot to ask you, WHERE is ROM, image, that already downloaded the file (update)? Path in Root Explorer or something? That might help us find a way to do the stupidest manual update.
The slightest question is, is it in the path at system/cache that update file already downloaded or somewhere?
If you can manage to convert it to 2125 I would highly recommend doing so.. I have the 2127 and converted to 2125 it's so much smoother and no issues on A12 running version C.62
Is 2125 causing any issue after you flashed real 2127?
cat139lyleb said:
Is 2125 causing any issue after you flashed real 2127?
Click to expand...
Click to collapse
I mean, deepest issue?
luckylui said:
If you can manage to convert it to 2125 I would highly recommend doing so.. I have the 2127 and converted to 2125 it's so much smoother and no issues on A12 running version C.62
Click to expand...
Click to collapse
Can you have a custom systemwide font and custom bootanimation? Will Fontfix app change your font?
TheGhost1951 said:
Can you have a custom systemwide font and custom bootanimation? Will Fontfix app change your font?
Click to expand...
Click to collapse
That I am not sure... Don't use any of that. But, if you do want that, I'd recommend going to 2123 which is EU or 2125 which is NA/Global depending on your region and installing a custom ROM after the conversion.
cat139lyleb said:
I mean, deepest issue?
Click to expand...
Click to collapse
So far the conversion from 2127 to 2125 has been going great! I'd highly recommend reading the instructions on how to do the conversion before jumping in blind. Took me a bit to convert because I skipped a step or two, but finally managed to get it done. Plus, you won't have all that T-Mobile bloatware running.
I'm still on LE2127, albeit on stock 11.2.9.9 firmware, fully rooted with R/W mounted partitions, no bloatware, custom bootanimation and custom systemwide font....smooth as silk. Tried A12 and didn't like it at all. Went back to A11....
TheGhost1951 said:
I'm still on LE2127, albeit on stock 11.2.9.9 firmware, fully rooted with R/W mounted partitions, no bloatware, custom bootanimation and custom systemwide font....smooth as silk. Tried A12 and didn't like it at all. Went back to A11....
Click to expand...
Click to collapse
2127 converted to 2125, A12 over here. So much smoother!
luckylui said:
2127 converted to 2125, A12 over here. So much smoother!
Click to expand...
Click to collapse
Maybe so, but you don't have full root privileges. Try installing FontFix app from the play store and see if you can change your font....
cat139lyleb said:
Every time I got update but I can't install it for some reason so I need to do that myself because sometimes updates doesn't work out very well while using a Magisk, so anything idea where I can find LE2127_11_C.19 firmware?
Click to expand...
Click to collapse
Use the system update for Android 12 apk but uninstall the system update app after you install the update but before you reboot or it won't let you use it again. After you uninstall the system update app. Then manually restart with the power button.
LE2127_11.C.19_0190_202208020022 incremental
https://android.googleapis.com/packages/ota-api/package/d2eb4ccd7fefc991d3bae6a2d7b914521ecd8ecb.zip
How did you find this link? And how am I uninstalling that update from the system app since I got an error that uninstalls failed? So please help and teach us way easier to do step by step for whom having problems with this issue.
Plus, I noticed that I felt like I failed to understand because I have no idea which kind of update software must be removed from the system first before we can go ahead and install a local update; that's why I'd ask you, please help anyone who is in the boat as I have an issue with following the steps are because some of you didn't explain clearly and how to do right step by step.
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.