Database Users

Flashing won't work unless I wipe data

UPDATE: After completely wiping everything(recovery, ROM, bootloader, etc), and putting it back in with fastboot I no longer have this problem. My recovery probably just got corrupted or something while getting sent over to the device.
Got my Nexus 7 3 days ago, had it unlocked and all that jazz within the hour(thanks to the people who put the stuff together). It's great, but I have a problem with flashing .zip files in recovery. It doesn't matter what type of thing I'm wanting to flash(ex-kernel,rom, or even the uber-simple 720p camera mod), if I don't do a full wipe before flashing, then it just ends up boot looping my device. The boot loop doesn't turn the phone all the way off, just the boot animation. Sometimes the launcher will pop up for half a second and then go back to the boot animation.
For example, whenever I flashed the rasbeanjelly rom, I first flashed that, then rebooted(got excited and forgot about gapps) and checked it out. Remembering about gapps, I went back to recovery and flashed gapps. Then it boot looped the animation. After flashing gapps again(trying different combos of wiping cache/davlik), I flashed the rasbeanjelly rom again, and then gapps immediately afterwards. Still a bootloop. So I did a full wipe(including data this time), sideloaded my .zips, and then it flashed and rasbeanjelly booted up with gapps just fine.
This exact same problem has been happening with every .zip that I try to flash(running TWRP, yes all my stuff is updated). If I want to flash a kernel, I have to flash it when I flash my ROM or else I'll get boot loop. I can't really make any modifications without having to completely wipe my device(which is annoying because I carry a lot of data around on my stuff)
I'm asking if there is a way to flash a .zip without having to completely wipe my device. I'm not a noob to android at all(ROM cooker over at androidforums), but I can't figure it out, I'd love to make stuff for the grouper but this is kind of a big roadblock for me. Logcat isn't helping either. Hopefully I just skimmed over something and it's a simple fix. Thank you for your tips/suggestions/solutions.
EDIT: forgot to mention something. When I flash a new ROM and get it going, I always make a full backup in recovery. If I flash something, and boot loop it, I can't restore it correctly. Recovery says that it restores all good, but it still boot loops(even though I just restored a backup of a non-boot looping system from no more than 5 minutes ago).

If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.

korockinout13 said:
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
Click to expand...
Click to collapse
I've actually used several, and it seems to be happening on all of them. I've tried flashing things with PA, CM10, Stock, and RasberryJelly. The kernels I have attempted to flash have been Trinity, Motley, and Franco. All with no success and boot looping me :/

[Q] question: infinite boot image with custom rom

I know it has been asked before, and I have searched the threads. reverting to stock is not a problem.
nexus 7 grouper when installing a custom rom (liquid smooth v2.9 specifically) I get stuck on the liquid boot image.
I have successfully installed v2.7 and am able to revert back to stock or custom.
after a data format, factory reset, and wiping all caches, installing the zip file from abd sideload, or directly from the device the new rom that has flashed will not get past the boot image. am I doing something wrong, or could I do something differently so that the new v2.9 boots up correctly?
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
thank you.

aircooledbusses said:
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
Click to expand...
Click to collapse
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:

ameinild said:
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
Click to expand...
Click to collapse
I will keep trying. getting liquid to run on the fascinate was curious as well, but after a few flashes it took. I'll keep trying on the nexus.
Update: yes, persistence is the key. thanks
What I did was from v2.8 a factory reset, wipe cache and dalvik and flash from sideload
as expected it boot looped. manually booted into fastboot and flashed v2.9 again with only a cache and dalvik wipe.
this time it booted and I flashed gapps.
at the reboot I set up the rom to my liking and it seems to boot normally now.

aircooledbusses said:
at the reboot I set up the rom to my liking and it seems to boot normally now.
Click to expand...
Click to collapse
Yes, after it boots through the first time, I've only seen it boot normal from that point on.

[Q] Stuck at Paranoid Android boot logo!

Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.

Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.

Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4

leandronb said:
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Click to expand...
Click to collapse
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
andyabc said:
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)

Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4

Nigeldg said:
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Click to expand...
Click to collapse
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!

12ian34 said:
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
Click to expand...
Click to collapse
I had exactly the same issue you had at first boot, it remained at Google logo forever when i first flashed PA 3.92. This issue came because i was flashing PA 3.02 with Franco nightly 165, franco nightly 165 is for 4.2.2m and if you were in 4.2.2 then you will never know new releases as that one was the last 4.2.2 kernel. I suggest you flash PA 3.92 + gapps from 0802, without Franco, it will boot fine. Also, as explained in big letters in PA download, first step is to download radio and bootloader for the update, i did not have to wipe my memory for the upgrade.
I don't recommend downloading Franco 175 for 4.3, as it has conflicting issues with PA, so use PA with the stock kernel and you should be good meanwhile this gets solved.

12ian34 said:
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Click to expand...
Click to collapse
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Click to expand...
Click to collapse
But how do I go about backing it up before I wipe it give that I can only access fastboot and recovery (CWM) ?!?!
OK, I've found a way to do it using
./adb-mac pull /sdcard/0/ sdcardbackup
do I need to backup anything else?
Also, I've downloaded the link you sent me, just to be clear, first, I wipe data, factory reset, then I send the radio and baseband to my phone using adb, then flash them in recovery and then flash PA 3.69, GApps, Franco Kernel r165 then wipe cache, dalvik cache, then reboot, then go about restoring all my data. Is this correct?

Mee too
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!

jsmonu said:
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
Click to expand...
Click to collapse
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.

molesarecoming said:
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
Click to expand...
Click to collapse
Moles! Help me! I refer you to my first post in this thread, I want to stay on 4.2.2 and PA 3.69 for the moment, and preferably not wipe everything. I accidentally updated to PA 3.92 and then stuck at the PA logo on boot forever. Now I've tried to go back to 3.69 many times and still get stuck at PA logo. currently using adb pull to get all my important stuff off phone.
Is there a shortcut for me, which doesn't involve wiping??
EDIT:
... OK, I just downloaded the 4.3 radio and bootloader, pa 3.94, gapps and sent them to my phone, flashed each one in turn and then wiped caches, reboot. I skipped the wipe, and now my phone is working for the first time in three days - [optimising apps]. Let's see if this works....
Yep, phone works absolutely fine, didn't have to wipe and now have 4.3 and PA 3.94, which wasnt my original intention, but it had to happen sometime! Thanks for all the help people, I think we can consider this one solved

12ian34 said:
Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Click to expand...
Click to collapse
Download the nexus 4 toolkit and flash stock rom from it

soft brick phone flashing rom

I downloaded twrp and CM 10.1 CR2 for my MK2 4.3JB galaxy S4.
I made nandroids on the extra then went in used the wipe feature in twrp then loaded cm and gapps. Worked great and I love the ROM.
Went to put back nandroids. Used the wipe feature again then restored nandroid. Bootleg and stuck on the yellow sprint screen. Tried to flash Odin .tar and it started with a ton of FC then said something about data partition.
I had no choice but to factory wipe and I wanted to keep all my internal stuff. The stock to CM worked fine but just doing general wipe did not work to restore my nandroid.
The CM I noticed is 4.2.2. Is this an issue going back to stock 4.3 nandroid ?
I'm restoring the phone completely so it's fresh out of the box then rooting then using twrp to try to get back my old nandroid.
What did I do wrong in the process that caused it to stall on the yellow sprint screen ?

Now that I think about it I did probably a "dirty" flash since. I did not completely factory wipe the phone just the dalvik cache, cache and the last item on TWRP.

Once you go to 4.3...aka MJA or MK2 you cannot go backwards. So that may have been your issue. Try stayin with 4.3 or up
If you say "Please"... be sure and "Hit Thanks!!!"

OK I tried again after wiping, flashing 4.3, rooting, setting up TWRP.
I wiped everything and when I made my nandroids I checked ALL the boxes. I'm currently on CyanogenMod which works fine but I cant restore my nandroid. I wiped all then used restore from my SD card. I have twrp 2.6.3.0 I think.
I'm still getting stuck on the sprint screen. Help !

Don know about checking everything?? I make sure that SE Linux is checked (i use philz) and then save to SD. Have had zero issues so far and I bounce from 4.3 TW to 4.4 AOSP daily. Sorry I've never used TWRP so I cannot begin to help troubleshoot.
If you say "Please"... be sure and "Hit Thanks!!!"

I just want to make sure you are not wiping before you create the nandroid backup. I reread your post and it was unclear. When creating the backup you should not wipe first. Next, when switching between AOSP and Touchwiz things can get tricky. Usually a failure to boot is after doing a nandroid is caused by the kernel not being correct for the rom installed. It would probably be best to keep an AOSP kernel and a Touchwiz Kernel on your sdcard so you can flash it after you restore the nandroid backup to ensure the proper kernel is in place.
Secondly, it was mentioned above that you can't go back to 4.2.2 after going 4.3. This is actually incorrect. You cannot flash a stock tar of an older 4.2.2 rom through odin if you have the MJA (AKA Knox bootloader). You can however flash a 4.2.2 rom using recovery since it does not attempt to change the bootloader.

cruise350 said:
I just want to make sure you are not wiping before you create the nandroid backup. I reread your post and it was unclear. When creating the backup you should not wipe first. Next, when switching between AOSP and Touchwiz things can get tricky. Usually a failure to boot is after doing a nandroid is caused by the kernel not being correct for the rom installed. It would probably be best to keep an AOSP kernel and a Touchwiz Kernel on your sdcard so you can flash it after you restore the nandroid backup to ensure the proper kernel is in place.
Secondly, it was mentioned above that you can't go back to 4.2.2 after going 4.3. This is actually incorrect. You cannot flash a stock tar of an older 4.2.2 rom through odin if you have the MJA (AKA Knox bootloader). You can however flash a 4.2.2 rom using recovery since it does not attempt to change the bootloader.
Click to expand...
Click to collapse
I don't think I wiped before making the nandroid, but I'm not sure. I have the Sprint GS4, and the nandroid was a 4.3 (Dec 2013) firmware.
Can you help me out here, I'm really lost. Do I need to flash a Touchwiz kernel on top of the nandroid through TWRP (flashing multiple zips) ? Where do I get the kernel ?

Made a nandroid of my Cyanogen Mod. Wiped phone and restored Cyanogen Mod nandroid. No problem. Worked fine. Just the original that I made is not working.

mikeprius said:
Made a nandroid of my Cyanogen Mod. Wiped phone and restored Cyanogen Mod nandroid. No problem. Worked fine. Just the original that I made is not working.
Click to expand...
Click to collapse
There are a lot of people that have had problems switching between Cyanogen Mod and Touchwiz using nandroid restores. It usually is the Touchwiz kernel not being restored when restoring the backup. When you boot up, you won't get past the initial boot screen. If this happens, you should just have to reboot back in to recovery and flash a TW kernel then reboot or after your restore your nandroid backup, just flash the TW kernel before rebooting. Look in the Android Development section for a custom TW kernel or you can try this kernel that unkownforce posted from his Triforce rom: http://www.androidfilehost.com/?fid=23321874045862620

cruise350- You are my hero. The nandroid DID come back and is working This has racked my brain all night and I am so so glad that I got my nandroid back.
I do have a few more questions:
1. The Wifi is not working ?
2. It appears that my Sprint is on 3G, and not going to 4G LTE ? Do I need to do something with this ? I also am getting errors trying to update my profile and PRL.
3. Is a custom TW kernel always required to be used, is there a stock Samsung TW kernel ?
Thanks a TON ! I couldn't figure out it for the life of me. Other than that I have been enjoying Cyanogen Mod. Using goomanager it looks like some CM versions are not flashable with TWRP and only by Clockworkmod.

on some roms i know that if you don't use the kernel that comes with it the wifi doesn't work. maybe try stock? in your mobile network settings, is your preferred network type "lte/cdma/evdo'? i'm sure there's a stock kernel on the forum somewhere.

It was set on global, so I switched it thanks for the heads up. Wifi still out of commission though. Once I get this set up, I'm eager to try new ROMs. I'm still on the fence about TWRP though. It's a nice interface vs. Clockwork, but it seems like most files out there cater more to CWM

mikeprius said:
It was set on global, so I switched it thanks for the heads up. Wifi still out of commission though. Once I get this set up, I'm eager to try new ROMs. I'm still on the fence about TWRP though. It's a nice interface vs. Clockwork, but it seems like most files out there cater more to CWM
Click to expand...
Click to collapse
i can't really give advice on that since all i've used is cwm. idk what kernel that one is, but i think it now comes with kt-sgs4. maybe the one from before? i looked around and i couldn't find a stock kernel by itself for mja or later. if you extract the boot.img from a stock rom the kernel and ram disk are in there. how easily you could screw up your phone doing that is beyond my experience, so maybe try a different custom kernel and wait for somebody else's advice for the boot.img thing?

Wifi AND booting (as @cruise350 mentioned) are almost always a kernel issue.
What ROM are you actaully on?
How did you get there, your nandroid?
What kernel are you now using and how did you flash it?
Have you tried gonig into settings, turning off wifi, wait a moment and then trying to turn back on?
Sounds like you should flash a stock(based) TW ROM and go from there. That often clears up connection issues.
Also might want to set your 'network type' back to automatic.
As for CWM and TWRP both are superb just make sure you follow the ROM developers recommendation as to which to use. (Philz is a CWM based recovery). There are .tars and zips of the latest of each here in these forums.
Please spend some time here reading, searching and then reading some more. You will find all the answers to your questions and it will give you a huge grasp of what is what and how to do things properly.
Good luck.

I am currently on the L720VPUEMK2 ROM 4.3 for Sprint. Android version 4.3 (Dec 2013 update).
I used TWRP 6.2.3.0 to flash Cyanogen Mod 10.2 nightly version (not sure if matters specifically which one).
My kernel was from TriForceKernel on the link above. It says 3.4.0-gb72521e-dirty. I flashed it after I flashed my recovery after wiping the device including internal data, cache, dalvik cache via install .zip in TWRP then rebooted.
The phone has loaded up but does not seem to be toggling between 4G LTE and the wifi is busted. I checked my nandroid and it says there is a boot file in it.
When I created my nandroid, I checked all the boxes, then slide the toggle which was supposed to create a back up for all 6 segments. I'm not sure why the boot.img isn't loading, it's part of the recovery that saved it. The settings seem to be as I left them....there are just some little things that are problematic.
I have a boot.emmc and boot.emmc.win both that are part of the nandroid recovery that has been flashed yet it gets stuck on the splash screen.

Well I'd just wipe and try any one of the FIVE TW ROMs that have been dropped in the last 7 days.
Trying to fix whatever is your issue could take hours or days.
Wiping completely (as per whichever dev's ROM you choose), installing said ROM, and starting from scratch will assure you phone works AND give you the best chance to get stuff working.
I dirty flash, restore and install ROMs all the time.
However When I absolutely want to know I'll have a good working ROM I clean flash. Wipes, setup, let Google restore apps, debloat restored (and stock apps!) then setup each setting and app to my liking. Titanium comes in real handy - after all my apps are re-downloaded I can selectively restore data to those that need it (Kindle, newsreader, SMS, Call Logs etc.)
Try that - installing clean new ROM and see what happens. Then go from there. Or don't and spend another couple days without a completely working phone.

Moto x pure XT1575 What am i doing wrong?!

I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.

cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.

I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk

Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.

RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.

cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120

RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!

cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.

RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again

cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.

RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!

cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.