Database Info

[Q] "Installation aborted" with 4.4.4 OTA and CWM

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:

6045i usa latest 5.0.2-01001

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.

How do I turn my VZW into a normal phone?

Hi,
A couple of years ago I bought my HTC One m8 via eBay. It did say it was a VZW one, but me not being a US citizen nor living in the US, it didn't set off any alarm for me...
And so it took me by surprise that I am unable to tether my internet connection via bluetooth nor wifi, and that VZW went the extra mile to disable the FM receiver. Further more, living outside the US, I'm still running the Kitkat version, since no OTA update can reach me
And now to my actual question - I have bought a sunshine licence and got it running but I am not sure what are the next steps. My goal is to get the regular stock ROM (perhaps still rooted), so ill be able to enjoy FM, tethering and regular updates.
I'll much appreciate your help, and though I'm sure this kind of question has already been asked, I was unable to find it.
Thanks,
Saar.

Guttmann said:
Hi,
A couple of years ago I bought my HTC One m8 via eBay. It did say it was a VZW one, but me not being a US citizen nor living in the US, it didn't set off any alarm for me...
And so it took me by surprise that I am unable to tether my internet connection via bluetooth nor wifi, and that VZW went the extra mile to disable the FM receiver. Further more, living outside the US, I'm still running the Kitkat version, since no OTA update can reach me
And now to my actual question - I have bought a sunshine licence and got it running but I am not sure what are the next steps. My goal is to get the regular stock ROM (perhaps still rooted), so ill be able to enjoy FM, tethering and regular updates.
I'll much appreciate your help, and though I'm sure this kind of question has already been asked, I was unable to find it.
Thanks,
Saar.
Click to expand...
Click to collapse
If you are on KitKat you can get S-OFF using sunshine.
If you already bought a license then you may already be S-OFF. Check in bootloader. Power down device. Then turn back on using volume down + power to check in bootloader.
If you are S-OFF you can update to latest Android 6.0 Marshmallow, and flash a stock rooted ROM to enable tethering.
You could flash the RUU or flash firmware + ROM.

andybones said:
If you are on KitKat you can get S-OFF using sunshine.
If you already bought a license then you may already be S-OFF. Check in bootloader. Power down device. Then turn back on using volume down + power to check in bootloader.
If you are S-OFF you can update to latest Android 6.0 Marshmallow, and flash a stock rooted ROM to enable tethering.
You could flash the RUU or flash firmware + ROM.
Click to expand...
Click to collapse
Thank you!
I'm also unable to connect to the LTE network, so I'm on 3G. What should I be looking for, if I want an RUU (I'm a total noob around the whole flashing and ROMing territory... seems to me the RUU is the "safer" bet), FM, tethring, LTE, and preferably staying with Sense? I read a bit about the GPe port, but I guess it wouldn't have Sense.
I'm sorry if that's the wrong place to ask.
Thanks!
Saar.

Guttmann said:
Thank you!
I'm also unable to connect to the LTE network, so I'm on 3G. What should I be looking for, if I want an RUU (I'm a total noob around the whole flashing and ROMing territory... seems to me the RUU is the "safer" bet), FM, tethring, LTE, and preferably staying with Sense? I read a bit about the GPe port, but I guess it wouldn't have Sense.
I'm sorry if that's the wrong place to ask.
Thanks!
Saar.
Click to expand...
Click to collapse
I'm not sure about LTE, as you're not on Verizon network.
but GPe ROM is great now that we have the Marshmallow firmware.
FM Radio was removed from Verizon devices, but great Devs have gotten it working again I do believe.
Anyway, IF you are S-OFF, which you haven't confirmed yet, but I am going to assume you are, as if you aren't you shouldn't have any issues getting to S-OFF (and for $25 it's very much worth it).
Ok, once you are confirmed S-OFF, you want to flash the new MM firmware.
This can be found here.
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
flash this one:
"6.21.605.3_FULL_firmware.zip"
You will need an SD-Card or know how to use adb - guide will be in thread I linked above.
After you are on the latest firmware, you want to fastboot flash the latest TWRP custom recovery found here:
http://forum.xda-developers.com/showthread.php?t=2717928
Then you can flash a stock MM ROM, a GPe ROM, or a custom MM ROM.

andybones said:
I'm not sure about LTE, as you're not on Verizon network.
but GPe ROM is great now that we have the Marshmallow firmware.
FM Radio was removed from Verizon devices, but great Devs have gotten it working again I do believe.
Anyway, IF you are S-OFF, which you haven't confirmed yet, but I am going to assume you are, as if you aren't you shouldn't have any issues getting to S-OFF (and for $25 it's very much worth it).
Ok, once you are confirmed S-OFF, you want to flash the new MM firmware.
This can be found here.
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
flash this one:
"6.21.605.3_FULL_firmware.zip"
You will need an SD-Card or know how to use adb - guide will be in thread I linked above.
After you are on the latest firmware, you want to fastboot flash the latest TWRP custom recovery found here:
http://forum.xda-developers.com/showthread.php?t=2717928
Then you can flash a stock MM ROM, a GPe ROM, or a custom MM ROM.
Click to expand...
Click to collapse
Thanks!
Oh, right, I forgot to mention I've achieved S-Off. Shouldn't I use the m8vzw_AllInOne_Firmware first? I'm real scared getting my phone bricked..

Guttmann said:
Thanks!
Oh, right, I forgot to mention I've achieved S-Off. Shouldn't I use the m8vzw_AllInOne_Firmware first? I'm real scared getting my phone bricked..
Click to expand...
Click to collapse
I wouldn't steer you the wrong way.
If you read closely that's for Lollipop, we're want Marshmallow

andybones said:
I wouldn't steer you the wrong way.
If you read closely that's for Lollipop, we're want Marshmallow
Click to expand...
Click to collapse
after fastboot of firmware the phone is stuck on the htc powered by android screen... IT wont shut down nor power on. just stuck on it

Guttmann said:
after fastboot of firmware the phone is stuck on the htc powered by android screen... IT wont shut down nor power on. just stuck on it
Click to expand...
Click to collapse
This is because you only flashed the Marshmallow firmware, but are not on a Marshmallow ROM.
You want to hold volume up + volume down + power for about 10-15 seconds, the phone will reboot, let go of all except volume down, this will get you back into bootloader.
Now you will need to flash the TWRP custom recovery I linked to you above.
Then in TWRP recovery you will flash the Marshmallow ROM of your choice.
There are a number of great ROMs out that support Marshmallow, and I'll be kind enough to link you all of them.
Lyapota Jazz #10 Marshmallow - SENSE ROM
- Lyapota is one of the nicest and smartest Developers.
-- his MODs are found in many many ROMs, including mine, he used to put out MOD Packs, but now he releases ROMs, and they are top notch, I highly suggest one of these
Lyapota Blues #021 Marshmallow - Google Play Edition ROM
- again one of the best ROMs you can flash, this one is Google Play Edition, the one above this is Sense.
Google Play Edition Marshmallow 6.0 MRA58K.H10
- stock based ROM ported from the HTC One M8 Google Play Edition Phone with Verizon support.
Pure Stock Verizon Marshmallow ROM
- stock pure ROM made from the latest Verizon Marshmallow OTA
-- the best choice if you want something stock
ViperOne Marshmallow
- one of the most customization Sense ROMs ever made.
-- also is very stable, but this has basically every tweak you can dream or think of, worth messing around with.

andybones said:
This is because you only flashed the Marshmallow firmware, but are not on a Marshmallow ROM.
You want to hold volume up + volume down + power for about 10-15 seconds, the phone will reboot, let go of all except volume down, this will get you back into bootloader.
Now you will need to flash the TWRP custom recovery I linked to you above.
Then in TWRP recovery you will flash the Marshmallow ROM of your choice.
There are a number of great ROMs out that support Marshmallow, and I'll be kind enough to link you all of them.
Lyapota Jazz #10 Marshmallow - SENSE ROM
- Lyapota is one of the nicest and smartest Developers.
-- his MODs are found in many many ROMs, including mine, he used to put out MOD Packs, but now he releases ROMs, and they are top notch, I highly suggest one of these
Lyapota Blues #021 Marshmallow - Google Play Edition ROM
- again one of the best ROMs you can flash, this one is Google Play Edition, the one above this is Sense.
Google Play Edition Marshmallow 6.0 MRA58K.H10
- stock based ROM ported from the HTC One M8 Google Play Edition Phone with Verizon support.
Pure Stock Verizon Marshmallow ROM
- stock pure ROM made from the latest Verizon Marshmallow OTA
-- the best choice if you want something stock
ViperOne Marshmallow
- one of the most customization Sense ROMs ever made.
-- also is very stable, but this has basically every tweak you can dream or think of, worth messing around with.
Click to expand...
Click to collapse
Iv'e flashed TWRP but am unable to load into it... I keep on ending either in the regulare recovery mode or the white screen. Any thoughts?

Guttmann said:
Iv'e flashed TWRP but am unable to load into it... I keep on ending either in the regulare recovery mode or the white screen. Any thoughts?
Click to expand...
Click to collapse
doesn't sound as if it flashed correctly.
can i see the output of the cmd?

andybones said:
doesn't sound as if it flashed correctly.
can i see the output of the cmd?
Click to expand...
Click to collapse
some progress... Ive managed to load TWRP. but how do I flash the rom so i could see it in twrp?

Guttmann said:
some progress... Ive managed to load TWRP. but how do I flash the rom so i could see it in twrp?
Click to expand...
Click to collapse
UPDATE: got the zip file on the phone, installed the ROM. - and now it goes straight into hboot everytime i try to boot the phone

Guttmann said:
UPDATE: got the zip file on the phone, installed the ROM. - and now it goes straight into hboot everytime i try to boot the phone
Click to expand...
Click to collapse
I need more info, how are you flashing the ROM. is it saying successful after flashing, which ROM are you flashing? are you wiping before?
I just put the rom onto a sdcard, find the rom on sdcard in TWRP, wipe and flash.
as long as you are on the correct MM firmware, and one of the linked MM ROMs there won't be any issue.
I've tested each ROM I posted for you to make sure to run into as little issues as possible.
that or you can always flash the RUU
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972

andybones said:
I need more info, how are you flashing the ROM. is it saying successful after flashing, which ROM are you flashing? are you wiping before?
I just put the rom onto a sdcard, find the rom on sdcard in TWRP, wipe and flash.
as long as you are on the correct MM firmware, and one of the linked MM ROMs there won't be any issue.
I've tested each ROM I posted for you to make sure to run into as little issues as possible.
that or you can always flash the RUU
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
Click to expand...
Click to collapse
I really appreciate your help!
Thats the ROM: http://forum.xda-developers.com/ver...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Does it matter if I put it on the internal or external storage?
It says everything was ok as far as the installation is concerned, but says "Failed to mount '/carrier' (Invalid argument" and "Failed to mount '/reserver' (Invalid argument"

Guttmann said:
I really appreciate your help!
Thats the ROM: http://forum.xda-developers.com/ver...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Does it matter if I put it on the internal or external storage?
It says everything was ok as far as the installation is concerned, but says "Failed to mount '/carrier' (Invalid argument" and "Failed to mount '/reserver' (Invalid argument"
Click to expand...
Click to collapse
the failed to mount carrier could be the issue.
hmm.
try the lyapota blues ROM

andybones said:
the failed to mount carrier could be the issue.
hmm.
try the lyapota blues ROM
Click to expand...
Click to collapse
i read online this error has something to do with the TWRP version, so i downgraded and it went away...
any how, I tried another ROM first, (dont remember which one now) and it seemed to work. It booted, asked me a couple of questions, and then went crazy, so I wiped it.
But now i cant seem to be able to copy the lypota zip to the SD card. Windows says it seems as if the device is unplugged or unresponsive... I made sure to wipe beforehand, but no luck.

Guttmann said:
i read online this error has something to do with the TWRP version, so i downgraded and it went away...
any how, I tried another ROM first, (dont remember which one now) and it seemed to work. It booted, asked me a couple of questions, and then went crazy, so I wiped it.
But now i cant seem to be able to copy the lypota zip to the SD card. Windows says it seems as if the device is unplugged or unresponsive... I made sure to wipe beforehand, but no luck.
Click to expand...
Click to collapse
You want the latest TWRP3.0.0
If you can't figure out how to flash ROM, ID suggest running the RUU so you at least have a working device.
:good:

OK.
So I switched back to the latest TWRP, and was able to upload lyapota's ROM and flash - and finally it worked!!!!! ? I'm not sure what the problem was with previous ROMs, but I'm happy it finally worked out.
Walking to University, listening to live FM radio and being able to share my mobile data with my tablet... Finally I got what I paid for.
Thank you!

hi, i saw what you dis for him, you are most kind, i was wondring if you could elp me too, i also bought a phone from ebay and also live outside the us, nd i cant seem to get te from my carrier wich is att mexico, ive flashed several roms after getting marshmallow from htc's software from my pc, today fastbooted baseband and nothing Please help, i can post any info of the phone that you like
thanks in advance
skp

Changing rom used smp900

Good day everyone, just got my note pro WiFi version? Already rooted and has custom kernel civz, tablet feels slow so I'm planning on changing rom maybe lineageOS but I'm concerned about the procedure because I'm not sure where I'm standing with every change done to this device, any help is appreciated I just don't want to brick this device trying to flash a new rom.
Currently it's running stock rom 5.0.2, 3.4.39 civz kernel and knox 2.3, if someone could provide a step by step on what should I do or check in this device to be on the safe road id really appreciate it. Btw I don't even know what recovery I have or how do I access it.

Bump

honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/

xxjahasotoxx said:
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
Click to expand...
Click to collapse
someone told me that I just need to install twrp as it is and start flashing roms, dont know if this the best way to do it what do you think?

It could work just keep in mind that you don't know exactly what the previous owner did to it so if they installed a custom kernel you'll be stuck with that, could be a good thing could be a bad thing
You could always give it a shot and if it gives you problems go back to stock then TWRP then start rom-ing

Redmi 9 issue

When I restart my redmi 9 it opens automatically recovery mod even if I choose to reboot system it goes back to recovery mod once more plz help

When I restart my redmi 9 it opens automatically recovery mod even if I choose to reboot system it goes back to recovery mod once more plz help
Click to expand...
Click to collapse
What exactly happened? You provided no information at all... That quote was ALL what you provided, do you realize how unreasonable your request is?
Are you purposely leaving the details out for anticipation or a surprise post later on? Want someone to guess your problem?
Like, did you flash a custom ROM? It might be because you flashed a custom ROM on a stock bootloader.
Did you flash TWRP maybe? It's a known issue in old TWRP versions flash the newest one and you're good to go.
Explain in detail what you did and post the necessary information. Like ROM version, wether you unlocked your bootloader, what is your rollback protection index and what did you flash on your phone. Your phone model might also help so someone can get you a stock ROM.

XDHx86 said:
What exactly happened? You provided no information at all... That quote was ALL what you provided, do you realize how unreasonable your request is?
Are you purposely leaving the details out for anticipation or a surprise post later on? Want someone to guess your problem?
Like, did you flash a custom ROM? It might be because you flashed a custom ROM on a stock bootloader.
Did you flash TWRP maybe? It's a known issue in old TWRP versions flash the newest one and you're good to go.
Explain in detail what you did and post the necessary information. Like ROM version, wether you unlocked your bootloader, what is your rollback protection index and what did you flash on your phone. Your phone model might also help so someone can get you a stock ROM.
Click to expand...
Click to collapse
My problem is simple when I restart my phone it boot's automatically to recovery mod by it's own
I did not flast any TWRP or custom rom what so ever I don't have root access too all I did is some miui 12 update

No your problem isn't simple.
Based on the information you provided. What just happened is a soft brick and it can happen due to various reasons one of which is when updating android's firmware.
The solution is backing up everything then installing a new ROM. Beware the rollback index of your phone as it may cause hard brick.
I highly recommend going to your nearest service center and asking them nicely to unbrick your phone with no memory loss since you don't sound like you speak the mumbo jumbo language. (Basically a noob. No offense)
Again you provided little to no information at all, therefore i can only do as much.