Related
Q&A for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
no calls or data
I have an xt1031 flashed to page plus. I have bootloader 41.19 from a failed lollipop update attempt. I flashed the 4/8 build and I can't make calls and do not have 3g. The network shows as 31000. What should I do?
I have been trying each of his builds and anything newer than 4/8 data hasnt worked I'm on boost if that makes any difference
Verizon?
Good morning,
I'm on an XT1028 still with service through Verizon Prepaid; my bootloader is unlocked and I'm on an optimized KK stock ROM at the moment. I've been following the development of Meticulus' CM12.1 through the primary thread and there has been a lot of discussion as to problem solving and issues on the XT1031 and various carriers but little mention as to the status of the latest weekly builds on the XT1028 still on Verizon in terms of functionality or hiccups from users. Does anyone have the latest versions running on their 1028? Are any of the data or service issues present when running it on Verizon?
Thanks.
Followup: Installed the latest 4/25 weekly on my XT1028 on Verizon Prepaid. Installed fine, got phone and SMS, but the network is identified as Boost Mobile and I have no mobile data. Is there a fix? Is a build.prop edit necessary for Verizon? Thanks.
Reboot then bootloop
Hi, I've been trying to get my installation of this ROM working for two days now, but keep running into an issue that I cannot seem to solve
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
The issue has been occurring on build 4/8, 4/25, and 5/2.
The exact steps I have been taking to install this ROM (for all builds) and then what happens:
Bootloader is unlocked
Going into recovery and wiping dalvik cache then factory reset (wipe)
Installing CM11 (latest snapshot) [on my first attempts only, not afterwards since it made no difference anymore]
Factory reset again (just to be certain)
Installing the zip for a build specified above
Installation always succeeds with no errors
Installing gapps-L-3-28-15 with success
Reboot into android
First boot always succeeds (and takes appropriate length of time)
Set up the phone (connect to wifi, google account, restore my apps [18 of them, just common popular ones, mostly Google actually], and apply a theme
Use it for a couple minutes (enable root and usb debug in Developer Settings, set my apps up, etc)
Restart two or three times without any hiccups
Suddenly, after a random reboot, the boot animation happens twice (instead of only once how it supposed to be)
Phone boots and shows "Android is starting..." and optimizes the apps (104 of them) one by one
Goes to "Starting apps..." and succeeds
The phone shows the lockscreen, but only for approximately 1-2 seconds
Phone reboots
CM boot animation runs twice, once for a long time then again for a shorter period of time
Phone goes through process described above (Android is starting, optimizes, then flashes lockscreen)
This just happens again and again and again
Steps I've taken to try and remedy the issue:
Run: "adb reboot" from computer while phone is optimizing apps
Hard reset the phone by holding the power button for 15 seconds
Run: "adb reboot bootloader" from computer when possible, then go into recovery and wipe both dalvik and normal cache
Swipe on the lockscreen as soon as I see it to see if I can get in (lockscreen does not respond though)
Go into recovery and shut the phone off, then start again
Let it loop for about 2 hours
I had also tried leaving the phone overnight looping, and when I woke, it was still looping, but after a eight or so more hours, I came back and found that it had booted and stayed on (and was working completely normally).
The phone was running stock 4.4.2 completely fine before this (with no reboot issues). I attempted installing the latest version of BlissPop, which exhibits a similar but still different issue (it would always boot into android [and not loop], but after a couple restarts, it showed an error about the System UI crashing that would pop up every time I dismissed it, and continued doing so after each restart after that). CM11 seems to be running well on the phone (but only in my very limited test while transitioning between ROMs and such).
I unfortunately cannot provide a log due to not being able to run any logging app during bootup, but hopefully I have provided enough details above to allow understanding of the issue and maybe bring suggestions on how to fix it. I can provide any more information needed on request. I really would like to get this phone back up and running (and especially on this ROM as I do love the work the creator has put into it).
Sorry for the very large wall of text :| Thank you in advance for any suggestions on how to proceed from here
tartilc said:
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
Click to expand...
Click to collapse
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
a_gert said:
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
Click to expand...
Click to collapse
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
I now have a logcat! I'm having trouble understanding what it is talking about, but I started logging as soon as the "Android is starting..." box changed status from "Optimizing apps x of x" to "Starting apps" and then stopped logging after a couple seconds of the boot animation. It is attached below (split into three parts).
EDIT: Attached what might be a better logcat reading (recording started right before lockscreen showed, I tried unlocking it, then stopped as soon as I saw the blue animation)
tartilc said:
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
Click to expand...
Click to collapse
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
XPOSED on Meticulous Rom?
Is there any way to get XPOSED working? I really want gravity box for LL.
Awesome. I was going to download this from your site today but it is showing an error with connecting to its database. None of the computers i have access to can get on your site.
no wifi no cellular network
and after i flashed cynogenmod 12.0 in my moto g 2014, there is no wifi nor network :'( what am i suppose to do now?
Ui crash
Is there anything special i need to do to flash this update? i'm running on the 408 build and every time i try ti go the next version there is an issue. Either data stops working or i get a system Ui crash like on the 530 build. I would love to get this issue fixed with the 606 build. Besides that, great job.
a_gert said:
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
Click to expand...
Click to collapse
Yeah that is a lot of jumps I'd be hella nervous myself lol
K well guys today is your day , as a_gert stated there is a boost 5.02 , and it does work fine on any cdma xt1031 so first flash that
-depending on signal you may wish to update your modem also there is only 4.4 modem for boost public
Buuuutttt nvm all that for now
The problem the ONLY problem I have had when bootlooping was that it was not prepped correctly and my phone came with 41.19 and came unlocked-
1.) Make sure you are on c/O SuperR-Developer -- PhilZ-Touch-6.59.0_LPK .img OR twrp * twrp-2.8.6.0.1-falcon_STOCK.img
**Notice For Even PhilZ I only Named the -IMG- Version which means flash it with adb properly please
***if ever after you flash it via recovery it will show partition mismatch which apparently is no problem just that the custom recovery does not match the factory one is all.. ..
1.) Download PhilZ-Touch-6.59.0-LPK.img to PC
2.) Reboot to bootloader
3.) Plug phone into PC
4.) Open terminal in directory where the img is located
5.) Issue the following command:
Code:
fastboot flash recovery twrp-2.8.6.0.1-falcon_STOCK.img
2.) Do a format of System w/EXT4 AND REBOOT INTO RECOVERY
3.) Format dalvik/art + Cache + Data w/EXT4 & REBOOT INTO RECOVERY
4.) Format Data PLUS data/media with f2fs then Do the 'factory wipe' then manually format data/media with f2fs again please ..
- SIDELOAD THE ATTACHED STOCK LOLLIPOP NO GAPPS GIVE IT TEN MINUTES REBOOT FEW TIMES/ POWER DOWN ONCE & REBOOT AGAIN
5.) Reboot into recovery and flash the first zip I have attached (I_nomodem is just IF you find your 4.4 radio baseband worked better and want to format it for LP again in the future WITHOUT LP radio included)
****EDIT - SEE VERY BOTTOM OF POST CENTERED AREA LOL
6.) Power off & reboot into recovery manually
7.) Flash your Rom (OR STOCK LOLLIPOP DEBLOATED AGAIN) + Kernel(if any custom one) + Gapps -wait 5-15 minutes for initial boot
* I recommend AeroKernel for the included stock lollipop 5.0 debloated if not the stock kernel or after flashing and few reboots to settle ,just follow instructions from that thread if any are needed..
Please anyone with any moto g don't think updating your bootloader is needed or even really safe whatsoever it is THE main reason moto phones get bricked or messed up otherwise it is not necessary or any kind of improvement yes once you are on an LP one leave it be..
Other flashing yeah okay, bootloader no if so proceed with utmost caution.
After this your modem will be updated with the cdma LolliPop one, if you have any signal issues or what not go to the stock modems section for your specific phone and flash the one for your specific carrier and/or find the "update RIL" flash thingie on here in moto G section and follow instructions but the boost modems work on all cdma variants of Moto G..
For whatever reason I could not upload files to xda I tried five times it kept dying so here there are on googldrive :good:
**Do not Click individual Item Use the Download Arrow At the Very Top of Page to DL the zip properly plz
1.) Falcon LolliPop Part Updater + Modem
2.) Falcon LolliPops Part Updater (No Modem)
_____________________________________________________________________________________________________________________________
--EDIT #2-- LolliPop 5.0 Falcon XT1031 debloated
SIDENOTE: IF YOU FORMAT DATA/MEDIA & DO NOT KNOW HOW TO SIDELOAD THE ABOVE STOCK DEBLOATED ZIP I'M PRETTY SURE YOU'RE NOT GONNA LIVE TO TELL BOUT IT
BE PREPARED TO SIDELOAD - REBOOT IMMEDIATELY AFTER SIDELOAD THE ZIP ROM IS COMPLETE NOT INTO RECOVERY NOT ANYWHERE ELSE SYSTEM REBOOT
-And wait 5-10 Minutes For First Boot - You Only Need to Do this for the first LP rom loadin after that normal flashing do NOT format data/media anymore after this initial setup
--You can try to just use the script, but it did not work for me after many tries the above was the real solution and has been perfect since
2,3,4,5,6,7
·Install flashable (Boost Mobile/CDMA XT1031 only):
·Download falcon_PhilZ-Touch-6.59.0_LPK.zip to phone
·Reboot into current custom recovery
·Flash zip
·Enjoy!
Use the script again to prepare you partition properly anytime you are about to flash a new rom clean after factory wipe/ format is done..
As I said before data/media is never necessary again after this and MAY not be this time but it is the only thing that kept me out of bootloops ,and if you do it yeah it will force you to sideload your rom it erases all leftovers and your rom zips off the internal card and formats them for fresh start The script does not format /media guys k no worries
------TWRP 2.8.6..1 does not seem to restore properly- -system write only thing .. PhilZ-Touch is fine as is twrp-2.8.6..0 also
Nice, got 41.19 BL!
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
rammsteinaus said:
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
Click to expand...
Click to collapse
K welcome
Arrite guys for a little clearer step by step see here please apologies carrying on and on I have been gone quite some time here http://forum.xda-developers.com/mot...-moto-g-xt1031-lollipop-t3132974#post61346260
It actually Runs really nice, really REALLY nice once the system app package I am adding shortly was used and tweaked out ..
Is it safe to flash cyanogenmod onto the verizon moto G - 1028 4.3 plus
Hello community ,
I had serious problems flashing cyanogenmod onto a galaxy S3 that was running stock 4.3 , verizon bricked my S3 , and said that the software was not authorized by Verizon. Does this problem exist across the board for any verizon phone running 4.3 or higher ?? If so ... then anything to do with flashing cyanogenmod onto a verizon phone should have warnings in BIG RED LETTERS ... because you cannot even buy a new phone with 4.2 on it anymore.
Issues flashing cm12.1 on XT1031 Please Help
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Moto G CDMA issues
citizen3rased said:
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Click to expand...
Click to collapse
Hello Citizen 3 , You are farther along than me. I have only successfully flashed cyanogenmod once , and that was on an S3 so it was straightforward. I still have not unlocked my bootloader. I have not been able to copy and paste the long strings of characters from motorola , inside command prompt. It would be so nice if Meticulus or one of the other developers could get this to be an official release. The Moto G , and a few other inexpensive phones ( LG realm , Kyocera Hydro latest version ) would work like greased lightning , if they were running CM12. Any help that you could offer with pasting the strings of unlock code would be so appreciated.
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.
I was able to install the first of the two updates earlier for the 5.1.1 update on my Verizon Galaxy Note Pro 12.2. The second downloads, prompts for install, reboots and begins installing but errors out and reboots back into the OS home screen. The Verizon software update manager shows Failed software update error code 402. I have factory reset my tablet a couple of times and still same issue. I do not have my tablet rooted and no apps disabled.
I downloaded the latest available Samsung firmware md5 file, version VZW-P905VVRUANK1-20141205133604 and tried flashing using Odin 3.07 while in download mode. It starts and after a few seconds, Odin fails and on the tablet screen, I get the error, SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1. I have re-downloaded the firmware along with older versions and still same issue.
I was reading somewhere that my tablet could be "soft bricked" and that is why it will not install the second part of the OTA. As for the Odin/download mode error, I had read that the firmware version I am trying to flash in Odin has an older version of bootloader than my current and Samsung does not let you downgrade the bootloader. I may be wrong on both accounts, which is why I am seeing if anyone else has had this same issue or have any advice on what I can try.
Thanks in advance!
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
dansto82 said:
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
Click to expand...
Click to collapse
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
tdetroit said:
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
Click to expand...
Click to collapse
I was able to get mine to update using ODIN and the firmware file from sammoble. Factory reset on the tablet, factory reset in recovery and finally ODIN worked.
I was having the same problems as the OP listed. Once I decided to live without root and I would be okay with wiping the tablet, I performed exactly what dansto82 said he did and I'm now on 5.1.1.
Now hoping someone comes up with a way to root.
Hey, I have the p905v and it is running 4.4.4, I rooted it with towelroot and it was completely fine. I then tried putting twrp recovery on it the wrong way through flashify and now I don't have a recovery mode and can't update it to 5.1.1. Other than that the tablet runs perfectly fine. Is there a way I can fix it?
Sent from my SM-P905V using XDA Free mobile app
Here's to hoping someone can help me out. My phone details before I messed up: LG G3 D850, rooted, TWRP 3.0, running Fulmics 5.2 for about 1 1/2 weeks
I noticed that I was not seeing the LTE indicator on my phone. I checked the HUB and saw the BootD850-30012016 data patch and figured that I just needed to install. So I flashed it and my phone wouldn't start. I was able to boot into recovery, so I figured I would do a clean install of the ROM so I did a full wipe, accidentally wiping EVERYTHING except for my external SD.
Result was that I can access TWRP but am unable to flash any of my backups or zips from my external SD, or OTG. I can see the files, but don't have the option to "swipe". I also am unable to 'mount' or 'install'.
At this point, I noticed that AT&T has finally released the OTA for Marshmallow, so I figured I would just use LG FlashTool and totally un-root and give the update a try. (BTW, I have used the flash tool many times with no problems/issues on both my phone and my son's D855).
Unfortunately, I am getting the dreaded "unable to change to download mode" after 15 seconds. I have uninstalled and re-installed Flash Tool, the LG Drivers and all files and used every port on both of my computers (Windows 10 btw) but can't get past the download error.
So...after many hours of digging, I took a leap of faith and was able to sideload Fulmics 5.1 successfully and install the 5.2 update from the HUB. I made backup of the ROM but TWRP still won't allow me to "swipe" and install/restore. I reinstalled TWRP using Flashify and it installed version 2.8 but still no go on flashing from recovery.
I realize that I'm lucky to have been able to figure out how to get the phone back using the sideload function in TWRP, but I really do want to go back to stock and it bugs me that I am unable to use my backups.
Sorry for the novel, but I wanted to be sure to include everything I did....if anyone can help me out I would be much obliged. My 11 year old is anxiously waiting on me to figure this out before she gets this phone (I'm moving up to the HTC 10 in a couple of weeks!). She still thinks I'm 'SuperMommy' so if I can fix this I get to keep my swagger!
I was also running fulmics 5.1 and updated to 5.2 in my phone but now i was having pretty good laggs and i finally realised that the update provided by the phone was corruped so i went on the official site and downloaded the same 5.2 OTAs from there and flashed it into TWRP recovery to finally get the latest version 5.3..know that is it always advisable to flash zip file when in recovery mode using TWRP recovery...The big mistake was cleaning also the internal memory of your phone.this caused the malfunction of twrp.
The issue is that most often i have seen cases of lagg in those updating to fulmics 5.2 from the Hub .sometimes in twrp recovery the update files will not successfully wipe and then reboot system with 5.2 installed but with many lagg the file downloaded there may be corrupted and not give you permission to swipe..if you really like fulmics and still update to the latest..Try this it may help you solve your problem:1 reinstall the fulmics 5.1 go to xdadevelopers.com/fulmics follow the link given by xpirit to www.fulmics.com and download the OTA 5.2(file size maybe 46 mb).. 2.reboot your phone now in twrp recovery it should now be able swipe and install..(if not then install Twrp 3.0 and try) 3-search the files in your internal memory or wherever you have downloaded it and flash it ..4.reboot system.That should be done!! In case you want to come back to stock and cant install from Twrp then the problem is with Twrp just download the latest version that goes with your phone.
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
dcli23 said:
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
Click to expand...
Click to collapse
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
SofaSpud said:
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Hey there....you can access the Hub after you flash the Fulmics ROM. It's where you can get your tweaks, downloads, mods, etc. You'll find it in your app drawer.
After searching around and not being 100% sure on how I should go about fixing this particular bootloop I decided to post a thread. Bootloader unlocked, phone unlocked, FRP unlocked, and TWRP installed. Can't seem to get the phone recognized when plugged in no matter where I'm at and hisuite recovery doesn't work, nor does the erecovery or whatever it's called. I had the phone running just fine with supersu but after installing my usual Xposed/Busybox and rebooting I got caught in a bootloop. (might have been caused by being on Oreo and having some problems with a version made for Nougat or something). I've seen there are various ways to exit the loop and at this point I'd be open to any but I do notice some posts saying they almost bricked their phone while doing so. Currently on my microSD I've got a hwota update I was going to try to use. I've got no backups in TWRP either because I'm irresponsible (my fault). What can I do to just wipe the phone, reinstall any version of android and get back to where I was at. I'm a little new to this as I've only ever rooted my tablet. Thanks for the help and all the info I've taken from this forum before and hopefully now. Forgot to mention I don't know my full device number only MHA-L29 in the US.
Ok Well after laying in bed and thinking about it I wound up running HWOTA8 from TWRP since I could access that. Seemed to just bring me back to eRecovery, and I factory reset my phone. I'll reinstall TWRP and flash supersu then make a backup and try again. Not sure what happened but I seemed to be in a pretty good spot since I could access TWRP even though my phone wouldn't show up on my computer while in fastboot/Recovery mode.
edit: oh I got a new problem now. I'm on testkeys firmware, camera, sim, and bluetooth work but I can't update from 7 back to 8. I'll do more testing around before bothering to unlock bootloader or install TWRP.
I've been trying to follow the guide in this thread but to no avail. I just get software install failed and then I have to start again.
Well another day of searching google and XDA trying to figure out guides and I don't think I'm any closer to a solution to getting off test-keys. Some seem to suggest that you need to go back to MM, some suggest running HWOTA, some suggest the three button recovery and others say that won't work at all. I'm not sure I've ever felt this confused haha. I'll keep at it but there has to be some way to get to a build that has the updater on it since that's all I seem to be lacking to get off test-keys. I can even search the settings for the updater but when you press it nothing happens. It's like they completely removed any sort of updating this build can do.
KittyCat5eUTP said:
Well another day of searching google and XDA trying to figure out guides and I don't think I'm any closer to a solution to getting off test-keys. Some seem to suggest that you need to go back to MM, some suggest running HWOTA, some suggest the three button recovery and others say that won't work at all. I'm not sure I've ever felt this confused haha. I'll keep at it but there has to be some way to get to a build that has the updater on it since that's all I seem to be lacking to get off test-keys. I can even search the settings for the updater but when you press it nothing happens. It's like they completely removed any sort of updating this build can do.
Click to expand...
Click to collapse
What is your full build number? Please, post screenshot.
5[Strogino] said:
What is your full build number? Please, post screenshot.
Click to expand...
Click to collapse
Model: MHA-L29
Build: NRD90M test-keys
EMUI version: 5.0.1
Android version: 7.0
I believe I was originally on some variant of MHA-L29C567 since I'm US based and its the dual sim version
I've tried using HWOTA a few times to either upgrade/update or rebrand and no matter what I choose when my phone restarts to install I just get software install failed. Usually I'll have to run through first time setup again. I've read that some people said this particular issue had to do with the update zips but mine seem to be named correctly so all I can think of doing is getting another firmware and trying again with that.
haha okay so I found out I was putting the update zips in the wrong folder. I fixed that and re ran HWOTA. update started/finished and my phone started booting and restarting a lot then went into erecovery. I'm downloading the update package right now and it's slow as hell but it's moving. And that failed leaving me to boot a few times and then get back to erecovery. I'll try getting into fastboot or recovery.
Edit: Well that seems to have resolved itself now. After having the erecovery fail I wiped/factory reset and booted the phone into oreo 8.0.0.321 with all the apps and updater. Thanks to everyone who dropped in and I'll be getting emails if someone replies that needs help too. I'm not very knowledgeable but I can give it a shot.