Hello,
I have recently been trying to flash and try out Android MM on my xt1031. A problem I face is a series of reboots upon the ending of OS boot, while the first time it happens on one of those "updating contacts storage" after "optimization of apps". I'd like to know what would be the cause of this or how I can find it (idk how to record a logcat while booting) since I haven't heard of it around here. I have tried with several ROMs and tried without gapps, leading to the same result. Any nudge would be well appreciated.
Flash a proper TWRP for Marshmallow, then wipe all before flashing custom rom.
ong14 said:
Flash a proper TWRP for Marshmallow, then wipe all before flashing custom rom.
Click to expand...
Click to collapse
I do. I'm flashing the one located here: forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621 . Thr one I used is twrp 2.8.7.0 falcon M stocl no theme.img. Am I using one incompatible with my phone?
Related
I just flashed the pacman nightly over cm11 using philz recovery. and my phone keeps trying to boot up. I get the moto logo for a few seconds then it goes blank and comes back up.
not sure where to begin fixing this. Ive tried to get back into recovery but cant.
any help would be appreciated
oscar the grouch said:
I just flashed the pacman nightly over cm11 using philz recovery. and my phone keeps trying to boot up. I get the moto logo for a few seconds then it goes blank and comes back up.
not sure where to begin fixing this. Ive tried to get back into recovery but cant.
any help would be appreciated
Click to expand...
Click to collapse
You dirty flashed it over CM11? You didn't wipe system, data, cache and dalvik? I always do that, even when I'm flashing an AOSP-based ROM over another AOSP-based ROM.
The only time I won't do this is if I'm flashing say CM11 over CM11.
If you dirty flashed, that might be your problem, but I don't know for sure as I don't use PacMan ROM.
I didn't dirty flash. Cm11 was on there before. I used philz wipe forfor new rom like I always do.
I can get into the fastboot menu. Is there something I can do there to reflash cm11?
oscar the grouch said:
I didn't dirty flash. Cm11 was on there before. I used philz wipe forfor new rom like I always do.
I can get into the fastboot menu. Is there something I can do there to reflash cm11?
Click to expand...
Click to collapse
Not sure then. I always use TWRP to wipe and flash. Could be an issue with the ROM itself or you got a bad download. You might want to try and download the ROM again to ensure it wasn't a bad download.
figured it out. must have had something happen to the recovery file.
in fast boot i flashed a new recovery image and was able to boot into recovery.
Maybe you have the JB bootloader and you flashed a KitKat bootloader based CM11 build... That could explain why your phone is not booting properly.
If nothing works you just can flash a STOCK FIRMWARE to begin again.
The phone has stock kitkat. How can I confirm?
joel_sinbad said:
Maybe you have the JB bootloader and you flashed a KitKat bootloader based CM11 build... That could explain why your phone is not booting properly.
Click to expand...
Click to collapse
That's a no-go. You won't be able to flash a KK-based ROM on a system with a JB Bootloader. The device will abort the installation immediately with a friendly reminder. At least the XT926. Been there, tried that.
^ agree. My atrix HD has a jbbl and I can Confirm this
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?
FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!
My phone is rooted. I have CM recovery installed. I am trying to flash a ROM but the installation is failing at 47%. It shows this message "Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and restarts the phone. When I try to wipe data or wipe media from recovery it restarts the phone. Even if I try to install from emulated storage it restarts the phone. I think there is something wrong with the storage. Can anyone help?
Karthikprabhu22 said:
My phone is rooted. I have CM recovery installed. I am trying to flash a ROM but the installation is failing at 47%. It shows this message "Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and restarts the phone. When I try to wipe data or wipe media from recovery it restarts the phone. Even if I try to install from emulated storage it restarts the phone. I think there is something wrong with the storage. Can anyone help?
Click to expand...
Click to collapse
Hi, are you on latest version of CWM corresponding to your phone model ? (let us know what phone model too )
Have you tried to flash and try with TWRP's latest version for your model ? (what's model, once again...)
What rom are you trying to flash (brand and build) ? Is your bootloader up to date ?
Not easy to help you without some precise informations...
satanas17 said:
Hi, are you on the latest version of CWM corresponding to your phone model? (let us know what phone model too )
Have you tried to flash and try with TWRP's latest version for your model? (what's model, once again...)
What ROM are you trying to flash (brand and build)? Is your bootloader up to date?
Not easy to help you without some precise information...
Click to expand...
Click to collapse
I had TWRP earlier. But it suddenly stopped working. I tried to reflash it didn't work. Then I tried CWM which was flashed successfully but was freezing. Currently, I have the latest recovery by CyanogenMod. It works fine.
My phone is Moto G XT-1033 (falcon).
I haven't updated my bootloader. I will try doing it.
Thank you
I am facing same problem in twrp recovery but now everything working fine after flashing stock recovery and twrp again
Tjsdj said:
I am facing same problem in twrp recovery but now everything working fine after flashing stock recovery and twrp again
Click to expand...
Click to collapse
:good:
I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......
iHackIt said:
I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......
Click to expand...
Click to collapse
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:
karanksj said:
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:
Click to expand...
Click to collapse
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.
iHackIt said:
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.
Click to expand...
Click to collapse
I quoted 5.0.1 not 5.1 brother It worked for me every time.
karanksj said:
I quoted 5.0.1 not 5.1 brother It worked for me every time.
Click to expand...
Click to collapse
Sorry for misreading...:silly:
I cant flash 5.0.1, 4.4.2,4.4.4
When i try to flash it gives errors and warnings (only 5.1 works )
i will share errors...
works in the sense it was flashed perfectly but it also boots to the recovery everytime like CM13
My bootloader version is 41.1A..
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!
Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241
Thanks a lot, once again
Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode