Related
I have a rooted Moto G with CWM Recovery and by stupidity installed the 4.4.4 OTA.
CWM aborts the installation, the phone reboots and unfortunately after the ROM is booted it automatically reboots to once more try and install the OTA.
So what are my options now? When a similar thing happened on my Nexus 7, I just flashed the factory image and all was fine. But I'm not sure what image to use for the Moto G. Is there even an official flashable image? If not, which is closest to stock?
Or is it possible to prevent the phone from automatically rebooting? I can access it with adb and have 10-20 seconds after the boot where I could open some apps.
bur2000 said:
I have a rooted Moto G with CWM Recovery and by stupidity installed the 4.4.4 OTA.
CWM aborts the installation, the phone reboots and unfortunately after the ROM is booted it automatically reboots to once more try and install the OTA.
So what are my options now? When a similar thing happened on my Nexus 7, I just flashed the factory image and all was fine. But I'm not sure what image to use for the Moto G. Is there even an official flashable image? If not, which is closest to stock?
Or is it possible to prevent the phone from automatically rebooting? I can access it with adb and have 10-20 seconds after the boot where I could open some apps.
Click to expand...
Click to collapse
You can find all the stock firmware images here:
http://sbf.droid-developers.org/phone.php?device=14
Flash either with RDS (http://forum.xda-developers.com/showthread.php?t=2637338) or fastboot (http://forum.xda-developers.com/showthread.php?t=2542219)
Thanks, there's no 4.4.4 for O2 Germany though. Do I need the right carrier/country? Otherwise I'll just go with 4.4.2
I also found this ROM (it's 4.4.4 despire thread titel). Is there any harm in trying it? I did a backup of the current half-broken system.
bur2000 said:
Thanks, there's no 4.4.4 for O2 Germany though. Do I need the right carrier/country? Otherwise I'll just go with 4.4.2
I also found this ROM (it's 4.4.4 despire thread titel). Is there any harm in trying it? I did a backup of the current half-broken system.
Click to expand...
Click to collapse
You can flash any firmware you want, except the ones for dual sim version (but if you want to be totally safe flash the retail de image). 4.4.4 images aren't available currently, you have simply to restore the stock 4.4.2, flash the stock recovery and take the OTA update.
The ROM you linked is for Moto G dual sim variant (XT1033), flashing it will probably cause a soft brick.
I have the exact same problem.
1. Is there any way to get the phone out of this loop and get it usable again without a computer?
2. How can I flash the rom if the phone keeps doing this?
Any help would be much appreciated. Thank you.
fertchen said:
I have the exact same problem.
1. Is there any way to get the phone out of this loop and get it usable again without a computer?
Click to expand...
Click to collapse
I would say no. Theoretically it might be possible to quickly do something before the phone reboots.
2. How can I flash the rom if the phone keeps doing this?
Click to expand...
Click to collapse
Just follow the fastboot link in the post by Azarielz. WARNING: If you don't want to loose you user data don't do the mfastboot erase userdata step. For me that still removed the reboot loop while retaining my data and apps. I had some problems with the mobile connection though, only after I manually searched for available carriers and pressed "select automatically" it connected. After that no problems.
bur2000 said:
After that no problems.
Click to expand...
Click to collapse
Thank you very much. I will try that when I get home next week. Will be a nice exercise in living without a phone for some time...
bur2000 said:
I would say no. Theoretically it might be possible to quickly do something before the phone reboots.
Just follow the fastboot link in the post by Azarielz. WARNING: If you don't want to loose you user data don't do the mfastboot erase userdata step. For me that still removed the reboot loop while retaining my data and apps. I had some problems with the mobile connection though, only after I manually searched for available carriers and pressed "select automatically" it connected. After that no problems.
Click to expand...
Click to collapse
Just did the same mistake with unlocked & rooted XT1032. I use TWRP and ended up there after every reboot. What I did is use the File Manager under "Advanced" to delete the .zip under /cache. Alternatively you could just wipe cache/ dalvik cache and the update zip should be gone, phone should reboot normally and after app optimization (if you wiped dalvik cache) everything should be back to normal. The first few seconds I got an error when checking for an update, but it went away after a minute.
Not sure if I should go through the trouble of updating to 4.4.4 or wait for Android L that's supposedly coming to the Moto G and X...
I was in the same situation, with bootloader active from cmd:
mfastboot erase cache
or whatever you use
Any improvement?
Hello everyone,
I had the same problem and had to restore a backup.
But can anyone tell us why this happens? Is Google aware of this and is a fix on the way?
I've seen that the update would fix the annoying incompatibility problem with the class 10 SDCards so I'd like to install this update.
I have seen that some of the improvements would also be :
- coloured tiles in the phone dialer
- ability to pause when you record a video
But I can already do that with my phone right now (I'm in 4.4.3 on a Moto G 4G), is this normal ?
Thank you.
suiller said:
I was in the same situation, with bootloader active from cmd:
Click to expand...
Click to collapse
Thank you very much, suiller. This:
fastboot erase cache
did it for me.
gnayug said:
Not sure if I should go through the trouble of updating to 4.4.4 or wait for Android L that's supposedly coming to the Moto G and X...
Click to expand...
Click to collapse
What would be the easiest/most foolproof way to apply an OTA update when the Moto G is rooted?
fertchen said:
What would be the easiest/most foolproof way to apply an OTA update when the Moto G is rooted?
Click to expand...
Click to collapse
That's what I want to know as well. XDA has all these devs and freaks and advanced tutorials but nothing at all for the most simple and popular issues for the average user such as applying an OTA with a rooted device. Apparently it's supposed to work with Phil's Flash Recovery, well it didn't, it gave me the same error message that CWM gave me. Or you're supposed to use "stock recovery", but nobody tells you how to get that in the first place.
...Help?
gnayug said:
That's what I want to know as well. XDA has all these devs and freaks and advanced tutorials but nothing at all for the most simple and popular issues for the average user such as applying an OTA with a rooted device. Apparently it's supposed to work with Phil's Flash Recovery, well it didn't, it gave me the same error message that CWM gave me.
Click to expand...
Click to collapse
My guess is that there are just too many versions of phones out there and too many different prerequisites (differences in how the phone was rooted, which apps might have been de-installed, which rom/recovery installed etc) that it is extremely hard and laborious to provide a truly foolproof way. That might be different if there was one standardized manual/tutorial on "Hot to root foolproof and OTA proof for the future" and everyone would follow that precisely.
gnayug said:
Or you're supposed to use "stock recovery", but nobody tells you how to get that in the first place.
Click to expand...
Click to collapse
There is a page that lists all the available stock Moto G Roms in different versions. It would be great if there was such a page for the recovery as well.
If there was a person that decided to take care of all these issues for the Moto G on this forum, he or she could maintain a page with direct links to all the tools, roms and recoveries as well as one general (foolproof) and possibly a handful of alternate ways and fixes.
That is a lot of work, particularly dealing with people who are not willing to read more than one sentence in order to get what they want. And certainly it must be frustrating for a "freak" or dev to encounter us newbies on a daily basis. A 101/primer on what boot/recovery/rom etc is would be helpful - and it does even exist in the wiki. It's that many of us don't find it. That could be changed by a very well thought-out and structured sticky post that provides all the necessary links and knowledge but not too much so that a beginner is frightened by 10 pages of instructions.
But I am certain that a person would be willing to do that if this forum allows it (which I assume is the case). Maybe this person has not been identified yet. Or maybe we have just missed it. I know I will not be this person simply because it would take me a lot of time to gather the necessary knowledge for such a position and right now I have other priorities and I usually use my phone once every 10 days or so.
I am aware that as a user I am not entitled to anyone providing this service. At the same time I am pretty sure that there is someone, maybe even within this great community, who would be willing to do it.
By the way, here is how I ultimately fixed the rooted-Moto G-OTA-update-problem: http://forum.xda-developers.com/moto-g/help/how-to-update-rooted-moto-g-t2828857/post54528345
Thank you for the link and everything you wrote! I was actually thinking the same the last few days... If only I was qualified enough or had the time to gather and polish all the information. I realize I shouldn't have written "Freaks". They're hard-working, skilled individuals that provide us with all this amazing software for us to use free of charge. I just wish they'd put some effort into explaining and laying out the basics etc. for all the "newbs" they encounter each day, because what good do their stuff do when nobody knows how to use it? All those devs that put out kernels and ROMs and then make a thread with changelogs and download links WITHOUT actually saying what they contain and why anyone should use them - I'm looking at you.
I'll go try to get my Moto G to 4.4.4 without losing my stuff using your link now, thanks again!:good:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.
Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..
lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.
What I don't understand is there are all these talented people out there, finding ways to do virtually anything to their phones, but there doesn't seem to be any normal solution to receiving an OTA update on a phone that has twrp and rooted and just install the update. The phone is obviously getting the right update, it restarts to install and twrp fails with error 7. There are all kinds of people saying "unpack the zip, remove the asserts line, which doesn't work, at least for this update. Also try using the dload method, but really the ultimate question is, why hasn't a simple solution to just installing this ever have been found? Is the way that all this stuff works in the background just so difficult that a legit update cannot be installed because the stock recovery isn't present? and if so, why can't a way around this obstacle be found.
I would just like to install updates as they come down (i assume by now this phone is trying to work its way up to android 8, or oreo) but i am stuck just ignoring it. I don't mind a little messing around to get things to work, i just haven't found any that actually do and don't involve wiping out the phone and installing everything again. Any answers are appreciated.
Dude. There is a way. I had the same thought before I pressed search on XDA and spent the next 3 hours digging in every Honor Forum and XDA and here is my tried and tested solution.
Make sure you have TWRP installed.
Download Firmware Finder from the Play store, enter your Model Number and download latest FULL-OTA for it. Only Full OTA will work.
Search for and Download Hurupdater from thread. Specifically Hurupdater 0.4
Rename files as specified in Hurupdater thread. Transfer them and Hurupdater to same folder on SD card. i.e all 4 files need to be in same folder. Now boot into TWRP and select Only Hurupdater to flash. Press Volume down when promoted and sit back for a few minutes. Once it completes wipe Dalvik Cache and Reboot.
Now you are on the firmware you wanted without factory reset.
A few things to note.
Your device shouldn't be Rooted. Unrooted first.
First boot will take some time approx. 10 mins. Don't Panic
After update TWRP will be overwritten. Reflash TWRP.
Don't use this to go from EMUI 5 to 8. You will brick your phone
In Firmware Finder there will be three Zips. Rename them as follows:
Update.zip -> don't rename
Update_data_full_public.zip -> update_data_public.zip
Last one will be region specific with your model number. Rename it to update_all_hw.zip
Good Luck.
Mannan Qamar said:
Dude. There is a way. I had the same thought before I pressed search on XDA and spent the next 3 hours digging in every Honor Forum and XDA and here is my tried and tested solution.
Make sure you have TWRP installed.
Download Firmware Finder from the Play store, enter your Model Number and download latest FULL-OTA for it. Only Full OTA will work.
Search for and Download Hurupdater from thread. Specifically Hurupdater 0.4
Rename files as specified in Hurupdater thread. Transfer them and Hurupdater to same folder on SD card. i.e all 4 files need to be in same folder. Now boot into TWRP and select Only Hurupdater to flash. Press Volume down when promoted and sit back for a few minutes. Once it completes wipe Dalvik Cache and Reboot.
Now you are on the firmware you wanted without factory reset.
A few things to note.
Your device shouldn't be Rooted. Unrooted first.
First boot will take some time approx. 10 mins. Don't Panic
After update TWRP will be overwritten. Reflash TWRP.
Don't use this to go from EMUI 5 to 8. You will brick your phone
In Firmware Finder there will be three Zips. Rename them as follows:
Update.zip -> don't rename
Update_data_full_public.zip -> update_data_public.zip
Last one will be region specific with your model number. Rename it to update_all_hw.zip
Good Luck.
Click to expand...
Click to collapse
Ok, I'll give it a shot and respond later. Like I said, I don't mind jumping through a few hoops. One question, how can I make sure whatever latest full OTA is doesn't have emui 8 in it? will that firmware finder point out what is in it?
If it has EMUI 8 it will be mentioned in the title of the firmware like 8.0.0.536 or something. Currently only India and China have EMUI 8. However to be safe I advise you to go to system update and Download & install. It will Download firmware and ask you to install. Hit cancel and using file explorer go to internal storage. There will be a folder named HwOUC. You will find three firmwares archives there. Use them. Make sure they are Full OTA by checking the size of archives. Update.zip should be at least greater than 1 GB
Mannan Qamar said:
If it has EMUI 8 it will be mentioned in the title of the firmware like 8.0.0.536 or something. Currently only India and China have EMUI 8. However to be safe I advise you to go to system update and Download & install. It will Download firmware and ask you to install. Hit cancel and using file explorer go to internal storage. There will be a folder named HwOUC. You will find three firmwares archives there. Use them. Make sure they are Full OTA by checking the size of archives. Update.zip should be at least greater than 1 GB
Click to expand...
Click to collapse
Yeah, I looked in the changelog, and it isn't emui 8. Plus it not being available in the USA kinda answers that as well I was going to ask if i could just use the files that are sitting in my HWOUC folder already, but you beat me to that question. so i should just move that over to my sd card into a temp folder along with that hurupdater app?
jackmeat said:
Yeah, I looked in the changelog, and it isn't emui 8. Plus it not being available in the USA kinda answers that as well I was going to ask if i could just use the files that are sitting in my HWOUC folder already, but you beat me to that question. so i should just move that over to my sd card into a temp folder along with that hurupdater app?
Click to expand...
Click to collapse
Ouch...this locks the bootloader....so can't get twrp or SU back on without losing my data (well, i have a backup, but would have to restore everything, at least i assume) if i unlock the bootloader
If it's stock firmware it will. Forget that download from firmware Finder
Mannan Qamar said:
If it's stock firmware it will. Forget that download from firmware Finder
Click to expand...
Click to collapse
Well, it was too late anyway, so the OTA files that were existing on my phone for B376 did flash fine, but now I lost TWRP and root. Beyond that, B377 tried to install today, and even though now my phone is back to factory (i assume, since those changes had been made) Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
Am I stuck now using your method above for each and every OTA update that comes through? If so, how would that be possible since I am unable to get TWRP back onto my phone.
jackmeat said:
Well, it was too late anyway, so the OTA files that were existing on my phone for B376 did flash fine, but now I lost TWRP and root. Beyond that, B377 tried to install today, and even though now my phone is back to factory (i assume, since those changes had been made) Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
Am I stuck now using your method above for each and every OTA update that comes through? If so, how would that be possible since I am unable to get TWRP back onto my phone.
Click to expand...
Click to collapse
Just reflash TWRP. It should flash fine. And yes, if you plan on using EMUI 8 the above mentioned method is the only way to update. Normally I would recommend you to Ditch EMUI and install a custom ROM. There are a lot of great ROM available for our device. If you want to flash one I will be more than happy to guide you.
Mannan Qamar said:
Just reflash TWRP. It should flash fine. And yes, if you plan on using EMUI 8 the above mentioned method is the only way to update. Normally I would recommend you to Ditch EMUI and install a custom ROM. There are a lot of great ROM available for our device. If you want to flash one I will be more than happy to guide you.
Click to expand...
Click to collapse
Well, I am still on EMUI 5 right now. I was kind of hoping not to go through flashing a custom ROM since I went through doing that on my LG nexus 5, and yes, it was great once it worked, it was a real pain to get to that working part. I was hoping the standard OTAs were going to get me up to android 8, and then just be happy with that. So I am unsure how I can flash TWRP again since my bootloader is locked again. Basically if I am going to be stuck wiping my phone out again, then I suppose I would be inclined to going the route of a custom ROM. So I guess it is just a matter of if I can get twrp on here again without wiping my phone again (unlocking the bootloader)
Um, no. You can't get TWRP with a locked bootloader. And also you can't go from EMUI 5 to 8 via Hurupdater. In Oreo partition table changes and Hurupdater can't flash that. So you will have to upgrade to Oreo manually. You can easily do that. It will take an hour to get to Oreo as well as flashing a ROM.
Mannan Qamar said:
Um, no. You can't get TWRP with a locked bootloader. And also you can't go from EMUI 5 to 8 via Hurupdater. In Oreo partition table changes and Hurupdater can't flash that. So you will have to upgrade to Oreo manually. You can easily do that. It will take an hour to get to Oreo as well as flashing a ROM.
Click to expand...
Click to collapse
so in essence what you are saying is that I can't go any further at all right now without wiping my phone again so i can unlock the bootloader? As of right now, I don't even know Huawei is going to release Oreo for this phone OTA, and even if it does, right now I can't get it. So since you have been so helpful (and very much appreciate it btw) what do you think is my best course? I don't think unlocking the bootloader will be an issue. i have the code saved somewhere around here. I wasn't all dead set on EMUI, it was just kind of nice staying somewhat in the realm of legit. And no, I have no qualms about straying outside of that. I just didn't want the nightmare I had with my nexus occurring again and not having use of my phone as a phone for the longest time. I'll await to see what you think I should do. Thanx again
Well. Flashing is easy. I'd recommend you to unlock your bootloader. And after that download HWOTA from thread. I will provide link. Next I want you to decide that wether you want stock EMUI 8 or want to flash a custom ROM. Depending on that I would advise you to either get Indian or Chinese EMUI 8. Indian is good for daily driver. Chinese for flashing custom ROM
Edit: heres the link
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page15
Mannan Qamar said:
Well. Flashing is easy. I'd recommend you to unlock your bootloader. And after that download HWOTA from thread. I will provide link. Next I want you to decide that wether you want stock EMUI 8 or want to flash a custom ROM. Depending on that I would advise you to either get Indian or Chinese EMUI 8. Indian is good for daily driver. Chinese for flashing custom ROM
Edit: heres the link
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page15
Click to expand...
Click to collapse
Looks like I will be stuck either way with wiping the phone, so I may as well go the custom ROM road. Don't really need to bother with the HwOTA then I wouldn't think. Unless I am missing something here. So who are the players for custom these days? still cyanogen? I saw on a search thay had android oreo 8.1. I used their custom ROM on my nexus as well. I most likely won't be getting to this now until tomorrow. I'll backup my phone...oh ****, titanium isn't gonna work. no more root....ok, i'll unlock bootloader, get twrp and root back on my phone and backup so definitely not until tomorrow. Only question for tonight is do I still need that HwOTA? I think I am a bit confused on what exactly I am trying to achieve. is it EMUI 8 with custom ROM of android 8? or nixing EMUI completely. Pardon my ignorance, but I really am just a bit hazy here on how this all works. all this for some stupid security update only because I thought it would open my phone back up to getting the OTAs and Huawei would release 8.....
Well. Since you are on EMUI 5 you will have to use HWOTA once you get to EMUI 8 as all custom ROMs require that. It also adds Project Treble support. So you will be flashing EMUI 8 once. After that, it's your choice. Either stay in stock or take the custom road. In terms of stock, there are currently 3 Android 8.1 ROMs available by OpenKirin and one Pie ROM available by Askuccio Droid. OpenKirin ROMs have stock camera in built while Pie ROM is.... Well Android Pie. All of them are smooth, have tweaks and great battery life and are infinitely better than stock EMUI 8. If you want the stock road, upgrade to BLN-AL20. That's the Chinese EMUI 8 and better for custom ROM. If you want stock EMUI 8 then go for BLN-L22.
Mannan Qamar said:
Well. Since you are on EMUI 5 you will have to use HWOTA once you get to EMUI 8 as all custom ROMs require that. It also adds Project Treble support. So you will be flashing EMUI 8 once. After that, it's your choice. Either stay in stock or take the custom road. In terms of stock, there are currently 3 Android 8.1 ROMs available by OpenKirin and one Pie ROM available by Askuccio Droid. OpenKirin ROMs have stock camera in built while Pie ROM is.... Well Android Pie. All of them are smooth, have tweaks and great battery life and are infinitely better than stock EMUI 8. If you want the stock road, upgrade to BLN-AL20. That's the Chinese EMUI 8 and better for custom ROM. If you want stock EMUI 8 then go for BLN-L22.
Click to expand...
Click to collapse
Ok, I must just be really tired. Is there not some way for me to just get back to whatever is causing this next OTA to stop? Meaning even though it is just some stupid piddly update, just get my phone to accept that without going totally overboard and what seems to be a bit above what I know how to do. That way the OTAs will just come at their own pace and I'll live with not having all the bells and whistles. Just going back to stock sort of thing. That is kind of what I thought was going to happen when you so very graciously and successfully got that last update to work. That way I can try something new and just be patient until Huawei forces out android 8 on their own.
jackmeat said:
Ok, I must just be really tired. Is there not some way for me to just get back to whatever is causing this next OTA to stop? Meaning even though it is just some stupid piddly update, just get my phone to accept that without going totally overboard and what seems to be a bit above what I know how to do. That way the OTAs will just come at their own pace and I'll live with not having all the bells and whistles. Just going back to stock sort of thing. That is kind of what I thought was going to happen when you so very graciously and successfully got that last update to work. That way I can try something new and just be patient until Huawei forces out android 8 on their own.
Click to expand...
Click to collapse
So you want to remain on stock EMUI 5? Well it's your choice. Anyway check a few things.
1. Is your bootloader locked? Do you get a warning screen when phone turns on?
2. Do you have TWRP recovery? Or stock?
3. Lastly is your phone rooted?
If your bootloader is locked, you have stock recovery and your phone isn't rooted, then congratulations. You are on stock EMUI 5 and you should receive OTA normally. Or at least I hope so.
Mannan Qamar said:
So you want to remain on stock EMUI 5? Well it's your choice. Anyway check a few things.
1. Is your bootloader locked? Do you get a warning screen when phone turns on? Yes the bootloader is locked now. And no, I do NOT get that warning screen anymore
2. Do you have TWRP recovery? Or stock? NO, I don't have TWRP anymore
3. Lastly is your phone rooted? No, I removed root to perform theinstall of B376-FULL and was obviously not able to root it after due to the previous
If your bootloader is locked, you have stock recovery and your phone isn't rooted, then congratulations. You are on stock EMUI 5 and you should receive OTA normally. Or at least I hope so.
Click to expand...
Click to collapse
Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
This shows the EMUI 5.0 screen
jackmeat said:
Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
This shows the EMUI 5.0 screen
Click to expand...
Click to collapse
Can you tell me what is it that you're trying to do and what's failing. I can't tell much from this.
Mannan Qamar said:
Can you tell me what is it that you're trying to do and what's failing. I can't tell much from this.
Click to expand...
Click to collapse
I am not trying to do anything. The phone has received an OTA update, B377, and after it downloads, it says install. click to restart now. After restarting to do the install (the everyday, normal OTA update method, nothing fancy) then it goes to that error. Only option from that black EMUI screen is "reboot now"
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
grego34 said:
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
Click to expand...
Click to collapse
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
[email protected] said:
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
Click to expand...
Click to collapse
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
grego34 said:
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
Click to expand...
Click to collapse
I have had luck with this downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
TexnoViking said:
I have had luck with //oxygenos.oneplus.net/fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
Click to expand...
Click to collapse
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
grego34 said:
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
TexnoViking said:
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
Click to expand...
Click to collapse
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
grego34 said:
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
Click to expand...
Click to collapse
Great! I am glad you managed to fix your phone! Enjoy
Flash with TWRP, choose one or the other.
H91020i_rooted.zip
You probably want this one. It is stock with the following modifications:
engineering bootloader (aboot)
TWRP 3.5.2_9-0 (recovery)
mk2000 kernel, Magisk v23.0 patched (boot)
hidden bootloader warning (raw_resources)
H91020i_stock.zip
Lose root, revert to stock. After installing, shut the phone off and then do a factory reset.
Lol, thanks for the package. It works just like h91020h, only slightly newer, but i don't have to do the kernel, twrp, or the fixed boot graphic. I can just install this, and debloat.
Works great, installed it with latest TWRP on nougat firmware (initially rooted using dirtysanta)
twrp-3.6.1_9-0-h910.img
H91020i_rooted.zip
Auto_Debloat 2.1
mk2000 2.3 beta 1 kernel
Magisk-v24.3 - Rename .apk to .zip or not, worked both ways in TWRP
Loving it, flashing other mods now like gps, high imp., quad dac mod, etc...
See updates here
Howdy!
Sorry to be asking, but I'm trying this after having been on LOS for ages since I need VoLTE access. After flashing this, I get no service of any sort. Keeps trying to connect, never actually connects. My IMEI is still correct, I've sent my old modem files through fastboot, I've flashed 910 Oreo modem images, no dice.
Any ideas as to what I'm missing in this process? 910 on AT&T, USA, thanks much for your time!
TratosDM said:
Howdy!
Sorry to be asking, but I'm trying this after having been on LOS for ages since I need VoLTE access. After flashing this, I get no service of any sort. Keeps trying to connect, never actually connects. My IMEI is still correct, I've sent my old modem files through fastboot, I've flashed 910 Oreo modem images, no dice.
Any ideas as to what I'm missing in this process? 910 on AT&T, USA, thanks much for your time!
Click to expand...
Click to collapse
See reply here
Skylined said:
See reply here
Click to expand...
Click to collapse
I really appreciate the super comprehensive reply, thanks so much! It was on the carrier's end, it was just a strange case of timing, a worsening of the AT&T nonsense that got me to switch back to Oreo in the first place.
Thank you!
I flashed the rooted zip from this thread after fallowing this guide https://forum.xda-developers.com/t/...irtysanta-most-variants-noobfriendly.3722278/ now the phone only boots the Fastboot. Oddly it even goes to fast mode when I try to enter TWRP it even still makes you choose yes twice like normal but instead of twrp I get fastboot.
Anyone care to point me in the right direction?
Something went wrong, you need to verify you can go into download mode and flash stock kdz and start from there....
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
***WARNING*** This is ONLY for the H910. If you flash H915 firmware on an H918 -- you WILL brick it. If you are currently on Oreo, you can root your phone, but you CAN NOT keep Oreo - for now. This will downgrade you back to Nougat, which is...
forum.xda-developers.com
I formatted data/ and flashed H91020i_rooted.zip onto my H910 (rooted with DirtySanta and flashed to H91020h_Oreo_full_rooted.zip approximately 2.5 years ago). It appeared to work, but it looks like I lost root... whenever I try to do something that requires root, I get "Unfortunately, Magisk has stopped" as soon as the app tries to become root.
Any ideas what to try next?
so could this be used after the root procedure here https://forum.xda-developers.com/t/root-howto-at-t-h910-up-to-v20g-fully-tested.3664500/ ? Because the full stock 910r package used there is no longer available