Hey guys, I ran into a rather odd issue yesterday and can't for the life of me figure out how to get my phone back to normal..
I upgraded TWRP to 3.0.2-0, wiped data, system, dalvik/cache, and attempted to install AOSiP 4.1 + Banks 4/08 Gapps, but after the boot, I get "Unfortunately SetupWizard has stopped", and after getting through the setup, "Unfortunately Theme Provider has stopped", if I click the Theme app it FC's.
This happens on EVERY single ROM I try to install, except Resurrection Remix. (The ROM I was on before flashing AOSiP.) I have tried going back to stock MHC19Q and starting fresh, but I still get FC's. I have also tried every recent TWRP, and MultiROM TWRP. Nothing is working.
Please help...
Edit: @big nu has the same issue..
https://tapatalk.com/shareLink?url=...share_tid=3357511&share_fid=3793&share_type=t
Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.
Eric214 said:
Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.
Click to expand...
Click to collapse
I fastboot everything. I flashed the stock image from my PC but still no luck...
Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.
Casmo said:
Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.
Click to expand...
Click to collapse
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..
adzcache said:
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..
Click to expand...
Click to collapse
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P
jesssiii said:
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P
Click to expand...
Click to collapse
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.
adzcache said:
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.
Click to expand...
Click to collapse
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.
adzcache said:
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.
Click to expand...
Click to collapse
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU! ?
adzcache said:
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU!
Click to expand...
Click to collapse
I had a problem like that. What I did was
Boot into Recover - TWRP 2.8 something
Did the Wipe Data / Factor Reset
Flashed The Rom - For me it was Pure Nexus - April 7, 2016
Flashed The Kernel - For Me Element X
Then wiped Davlik/Cache
Then after that I rebooted let it do what it had to do to boot up. Then rebooted to recovery
Then flashed the GAPPS - for me i used BaNkS-Dynamic-GApps-6.x.x-10-20-15
Then wiped DAvlik/Cache
Then rebooted and let it do its thing again. - I did not get any system startup failed.
Maybe you can not flash the GAPPS all together because the phone is a smart phone but it can still be DUMB.. LOL
Then I did not do a restore of apps from the automatic thing when it asks I just went to pla stoer and let it download what I needed from the my app section.
I'm still facing issues, but at least there are painfully long fixes to make everything work normally... Just pissed, every other android phone I have had, never faced such a persistent issue with rooting and flashing custom ROMs. Especially after restoring to stock..
Sorry to bump this thread, just hoping someone may have a suggestion that may fix up this rather odd issue I've been plagued with?
Quick fix for anyone else facing this:
Downgrade to MHC19I and when flashing recovery, flash TWRP 3.0.0-1, then format userdata in fastboot, copy your files over via PC and flash ROM + Gapps.
Related
So I did everythign I normally do with a new device!
1)I unlocked it through Fastboot
2) I downloaded the latest TWRP recovery image for that device and flashed it with Fastboot
3) I rebooted the device into recovery to check if everything is ok.
4) Proceeded to download Cyanogenmod for Nexus 6p (Angler) and OpenGapps ARM64 for 6.0 stock package and put them on the phone
5) Opened the Zips from the phone to check that none are corrupted
6) Wiped Everything on the phone via Advanced Wipe incl System, Data, Cache etc,
7) Flashed Cyanogenmod Zip first after that the Gapps package
8) Rebooted to System and waited for the phone to finish its first boot
This is where my problems begin. No matter what I do and how much I toubleshoot the first boot never seems to finish. I have played with devices long before I got the 6p and know that the first boot taked a long time but not this long!
I checked if it was the recovery, or the CM zip or Gapps but no matter how many scenarios I try and rule out Im stuck at the CM boot logo (Which seems pretty laggy). I even tried without gapps.
I searched online and cant find ppl with a similar problem. There are people who cant get past the Google logo but I get past that with no problem. Its just that I cant boot the OS.
I even checked a few guides to see if I missed a step when I was doing it on my own but no! I have done everything absolutely correctly and cant seem to find an issue this time (usually finding issues with Android and repairing them is my specialty ).
I can not think of ANYTHING that ive missed here. I just cant seem to find the problem. The hardware boots Stock/Factory imaged perfectly so its working fine. Where am doing wrong?
bogomil4e said:
So I did everythign I normally do with a new device!
1)I unlocked it through Fastboot
2) I downloaded the latest TWRP recovery image for that device and flashed it with Fastboot
3) I rebooted the device into recovery to check if everything is ok.
4) Proceeded to download Cyanogenmod for Nexus 6p (Angler) and OpenGapps ARM64 for 6.0 stock package and put them on the phone
5) Opened the Zips from the phone to check that none are corrupted
6) Wiped Everything on the phone via Advanced Wipe incl System, Data, Cache etc,
7) Flashed Cyanogenmod Zip first after that the Gapps package
8) Rebooted to System and waited for the phone to finish its first boot
This is where my problems begin. No matter what I do and how much I toubleshoot the first boot never seems to finish. I have played with devices long before I got the 6p and know that the first boot taked a long time but not this long!
I checked if it was the recovery, or the CM zip or Gapps but no matter how many scenarios I try and rule out Im stuck at the CM boot logo (Which seems pretty laggy). I even tried without gapps.
I searched online and cant find ppl with a similar problem. There are people who cant get past the Google logo but I get past that with no problem. Its just that I cant boot the OS.
I even checked a few guides to see if I missed a step when I was doing it on my own but no! I have done everything absolutely correctly and cant seem to find an issue this time (usually finding issues with Android and repairing them is my specialty ).
I can not think of ANYTHING that ive missed here. I just cant seem to find the problem. The hardware boots Stock/Factory imaged perfectly so its working fine. Where am doing wrong?
Click to expand...
Click to collapse
I'm not sure but on an old HTC phone I had the same issue which was caused by a mismatch between the rom version and phones firmware. I'm not sure how it works on the nexus hope someone here can help
Try different GAPPS ?
Sent from my Nexus 6P using Tapatalk
Have you tried flashing a vendor zip yet? Sounds like not booting cause missing binaries.
https://www.androidfilehost.com/?w=files&flid=43551
If you're able to get to twrp, wipe everything, flash cyanogen reboot, and then flash a different gappd
Sent from my Nexus 6P using Tapatalk
You must format data in TWRP or it won't boot.
So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik
Chikyu Tenshi said:
So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik
Click to expand...
Click to collapse
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
Try these gapps:
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
You need to perform a full wipe though.
Lennyz1988 said:
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
You need to perform a full wipe though.
Click to expand...
Click to collapse
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik
You need 5.1 gapps then.
Chikyu Tenshi said:
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik
Click to expand...
Click to collapse
My bad. Here is also another gapps
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Lennyz1988 said:
My bad. Here is also another gapps
Click to expand...
Click to collapse
Still :c I only flashed the base tho, Am I supposed to flash the add ons too?
I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)
CHIN3S3_N00B said:
I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)
Click to expand...
Click to collapse
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card
Could you try GearCM? Official CM for i9500 had lots of issues.
Sent from my GT-I9500
Chikyu Tenshi said:
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card
Click to expand...
Click to collapse
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?
CHIN3S3_N00B said:
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?
Click to expand...
Click to collapse
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.
Lennyz1988 said:
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.
Click to expand...
Click to collapse
I think that i didn't express myself very well. Yes it's advisable and strongly recommended to use lastest builds of any recovery available as stable build.
But once i had to use Philz to flash a MIUI ROM because TWRP 2.8.6.0 was unable to execute the installation script didn't know why and that's why i said about different recoveries, and oh.... I forgot to say that after successful install rollback to TWRP because it's pretty new , stable and more user friendly than others.(CMW and the rainbow Easter egg was fine but having to use vol and power keys..... NO THANKS!)
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.
Hi all!
So I have a Moto G4 Plus on 7.1.2 RR with Magisk root. I installed ElementalX kernel and overclocked and disabled fsync. However, as I was watching YouTube, my phone randomly froze and rebooted and wouldn’t boot up. It’d be stuck at the boot animation forever. Seeing this, I took a logcat and here is a link to it. I noticed that this line kept looping:
Code:
java.lang.NullPointerException: Attempt to read from field 'java.lang.String com.android.server.pm.Settings$VersionInfo.fingerprint' on a null object reference
I searched the error up on Google, and it led me to this StackExchange site. I had the same symptoms (the jobs.xml file was empty, I turned off fsync, etc.), so I did as it said (I backed up my data partition and did rm -rf /data/system), and I thought my problem was solved, but when I tried booting up my phone again, it still got stuck at the boot animation. Granted, the logcat was different now (here is a link to it), but it keeps looping at:
Code:
waiting for service sensorservice
or
Code:
waiting for service AtCmdFwd
I tried googling for that, but I couldn’t find any useful results, so I guess now I'm stuck. Any suggestions where to go from here?
Thanks so much!
@strongst and @sd_shadow, would you guys be willing to give some advice? I've been stuck without a phone for a couple of weeks now...
matetoes said:
@strongst and @sd_shadow, would you guys be willing to give some advice? I've been stuck without a phone for a couple of weeks now...
Click to expand...
Click to collapse
I would just reflash firmware, Fastboot.exe
sd_shadow said:
I would just reflash firmware, Fastboot.exe
Click to expand...
Click to collapse
Which partitions? Can I do it without losing my data (i.e. only reflash system or something)?
matetoes said:
Which partitions? Can I do it without losing my data (i.e. only reflash system or something)?
Click to expand...
Click to collapse
You can try reflashing just system, but I wouldn't count on any method saving data.
Sent from my Gemini 4G using XDA Labs
sd_shadow said:
You can try reflashing just system, but I wouldn't count on any method saving data.
Sent from my Gemini 4G using XDA Labs
Click to expand...
Click to collapse
I just gave up and updated to Pie with Arrow OS ¯\_(ツ)_/¯. At least it wasn't a hardware problem.
In these type of cases, flash RR on on top of your current ROM (without wiping anything i.e dirty flashing).
It seems like kernel issue and when you flash RR again, it will replace the custom kernel and you will have your RR kernel back.
Edit: you won't lose any data by this method.
Heeth21 said:
In these type of cases, flash RR on on top of your current ROM (without wiping anything i.e dirty flashing).
It seems like kernel issue and when you flash RR again, it will replace the custom kernel and you will have your RR kernel back.
Edit: you won't lose any data by this method.
Click to expand...
Click to collapse
Yeah, I tried that. I first wiped the data partition as instructed by the [URL="hthttps://android.stackexchange.com/questions/157601/marshmallow-not-bootlooping-but-not-starting]StackExchange post[/URL] then dirty flashed latest RR, but after waiting 10-15 minutes, I could still see those two messages (waiting for service sensorservice and waiting for AtCmdFwd). I have Nandroid backups of that bootlooped state but I'm kinda stumped on how to recover it at this point
matetoes said:
Yeah, I tried that. I first wiped the data partition as instructed by the [URL="hthttps://android.stackexchange.com/questions/157601/marshmallow-not-bootlooping-but-not-starting]StackExchange post[/URL] then dirty flashed latest RR, but after waiting 10-15 minutes, I could still see those two messages (waiting for service sensorservice and waiting for AtCmdFwd). I have Nandroid backups of that bootlooped state but I'm kinda stumped on how to recover it at this point
Click to expand...
Click to collapse
No, no need to wipe any partition......Just reflash RR without wiping anything except cache/dalvik.
And are you using some mods like Xposed? If yes, first flash their uninstalling zip from TWRP i.e uninstall them, then flash RR again(without wiping anything).
If that doesnt work too, then it doesn't seems like kernel issue.
Heeth21 said:
No, no need to wipe any partition......Just reflash RR without wiping anything except cache/dalvik.
And are you using some mods like Xposed? If yes, first flash their uninstalling zip from TWRP i.e uninstall them, then flash RR again(without wiping anything).
If that doesnt work too, then it doesn't seems like kernel issue.
Click to expand...
Click to collapse
I didn't using anything like Xposed. I had systemless root with Magisk and passed SafetyNet.
Actually, I did not wipe data, I just removed /data/system because some files like jobs.xml were empty and the phone didn't know how to start if those were empty. The reasoning was that if /data/system was gone, the phone would regenerate all those files and I could copy those files to my computer, restore the Nandroid backup before the removal of that folder, then copy back those files.
Alas, the phone still would not boot after removing /data/system so there must be some other problem going on (perhaps kernel issue, as you mentioned). I took Nandroid backups before and after every step I took so if you have any idea how to fix it we can always go back if something gets messed up.
So I decided to finally flash OmniROM 9.0 on my XC, and started having some problems.
Basically, I went completely from stock (already unlocked the BL):
1. Installed TWRP 3.3.1-0
2. Rebooted to TWRP and did a factory reset (because it said so on the install guide: https://docs.omnirom.org/Installing_Omni_on_your_device)
3. Flashed OmniROM 9.0 Weekly from the SD card
4. Unsuccesfully installed Open GApps because error 64 (apparently was supposed to use the ARM64 version, even though CPU-Z stated I was on ARM)
5. Installed Magisk 19.3
6. Wiped Dalvik/ART cache and Cache partitions
7. Installed TWRP app to /system and rebooted
Now it gets stuck on the Sony logo every time I power it on.
I tried leaving it for about 15 minutes to see if it was taking so long because of a fresh install, but previously I tried installing Paranoid Android and the boot up took only a few seconds, so obviously that wasn't going to work.
I tried rebooting multiple times, wiping the cache partitions again, uninstalled the TWRP app, did another factory reset, tried fixing contexts, and it still gets stuck on the Sony logo.
At this point I'm not sure if I should just give up, because none of the ROMs I tried flashing actually worked, which includes Resurrection Remix, Paranoid Android and LineageOS, and now OmniROM as well. So far, I haven't found anyone with the same problem as me, except https://www.reddit.com/r/SonyXperia/comments/acot9y/trying_to_install_omnirom_on_my_x_compact_stuck, but that's not quite the same.
EDIT: After flashing the ODM image, the phone booted up, but it's asking me for a password. I tried typing "password", and it said the password was correct, but my data was corrupt. It offered me a factory reset, but it made no difference. This is nothing new to me, the same thing happened when I tried flashing Paranoid Android. Should I do a clean install, like, wipe Internal storage and System?
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
Looks like u skipped Step #3
z0mg.jer1Cho said:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
Looks like u skipped Step #3
Click to expand...
Click to collapse
Right, I'm an idiot. I'll try again and see if that works.
ŽeljkoLončar said:
So I decided to finally flash OmniROM 9.0 on my XC, and started having some problems.
EDIT: After flashing the ODM image, the phone booted up, but it's asking me for a password. I tried typing "password", and it said the password was correct, but my data was corrupt. It offered me a factory reset, but it made no difference. This is nothing new to me, the same thing happened when I tried flashing Paranoid Android. Should I do a clean install, like, wipe Internal storage and System?
Click to expand...
Click to collapse
Did u boot the Phone after u've installed the default firmware?
z0mg.jer1Cho said:
Did u boot the Phone after u've installed the default firmware?
Click to expand...
Click to collapse
Yes, I did. Went through the setup and everything. Ttied it multiple times, didn't make a difference.
ŽeljkoLončar said:
Yes, I did. Went through the setup and everything. Ttied it multiple times, didn't make a difference.
Click to expand...
Click to collapse
Dont boot the Phone after installing the Factory Firmware. After u've installed it, just go on with the flashing procedure as told you in OPs thread
Same issue
I have exactly the same issue. Recovery successfully flashed, did a factory reset, successfully installed Omnirom, and then I reboot into a permanent white screen with the Sony logo in the center...
After several tries I gave up and installed the stock firmware again using Sony's flash tool Emma.