Can't flashback to JB after KK - Xoom Q&A, Help & Troubleshooting

Hello to all.
Here's the problem:
I installed KK 4.4.2 on my Xoom 3G (stingray) using bigPart TWRP. Everything works well except battery life - full charged battery goes to 0% in a day or two (in standbye mode).
Then I decided to roll-back to JB (or ICS) (eos-stingray-2.0 firmware). It flashes normally but device hangs on boot - when displaying Motorola's logo.
I can flash again to KK and it boots and works. But I finally decided to have my old firmware installed on Xoom.
Can anyone help me to flash correctly the device and make it boot to OS?
BR, akadimka

akadimka said:
Hello to all.
Here's the problem:
I installed KK 4.4.2 on my Xoom 3G (stingray) using bigPart TWRP. Everything works well except battery life - full charged battery goes to 0% in a day or two (in standbye mode).
Then I decided to roll-back to JB (or ICS) (eos-stingray-2.0 firmware). It flashes normally but device hangs on boot - when displaying Motorola's logo.
I can flash again to KK and it boots and works. But I finally decided to have my old firmware installed on Xoom.
Can anyone help me to flash correctly the device and make it boot to OS?
BR, akadimka
Click to expand...
Click to collapse
I dont think there ia a procedure to roll back from Bigpart.
The only way is , to reflash the original firmware of your device - root - instal CWM etc

mermigas said:
I dont think there ia a procedure to roll back from Bigpart.
The only way is , to reflash the original firmware of your device - root - instal CWM etc
Click to expand...
Click to collapse
Thanx for the answer.
Here's what I did:
1. Flashed recovery to TWRP 2.6.3.0 (not bigPart)
2. Flashed Xoom to eos-stingray_cdma-2.0.0.zip
3. Rebooted Xoom -> now I passed the Moto's logo but hanged on booting OS itself - EOS logo spinning round and round and nothing happens. Look like there's smth more need for OS to boot. But what exactly?
How now pass this issue?
Please help me!
BTW, tried to flash original ROM - error during flashing via recovery.

akadimka said:
Thanx for the answer.
Here's what I did:
1. Flashed recovery to TWRP 2.6.3.0 (not bigPart)
2. Flashed Xoom to eos-stingray_cdma-2.0.0.zip
3. Rebooted Xoom -> now I passed the Moto's logo but hanged on booting OS itself - EOS logo spinning round and round and nothing happens. Look like there's smth more need for OS to boot. But what exactly?
How now pass this issue?
Please help me!
BTW, tried to flash original ROM - error during flashing via recovery.
Click to expand...
Click to collapse
Use fastboot method
http://forum.xda-developers.com/showthread.php?t=1049485

mermigas said:
Use fastboot method
http://forum.xda-developers.com/showthread.php?t=1049485
Click to expand...
Click to collapse
Did it. Just after UNLOCK process via fastboot Xoom booted to OS normally. So no flash to stock firmware required.
BIG thanx for your help!

Hi I'm in a similar situation, the process that took at the actual status is the same as your.
Now I cannot flash any img, I receive writing 'system'... FAILED (command write failed (Unknown error)) also after flashing with RSD stock rom.
I had opened a thread http://forum.xda-developers.com/showthread.php?t=2611538 this morning but without any luck noone replied.
Thanks

Related

[Q] Red Triangle, Dead Android

After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.

[Q] Unroot not possible & Bootloop after 4.2.2. Rom update

It looks like a bigger problem, I updated my xoom MZ601 and installed the 4.2.2 Omnirom and at first it worked - http://forum.xda-developers.com/showthread.php?t=2593414
Then I installed some apps and after half an hour my xoom crashed and now it's stuck in a boot loop. Installing the rom again does not work, any other rom too - always a boot loop.
Allright, I thought, let's do a full reset and use adb and fastboot to install the original software and firmware in my xoom. (the link is german, but it works and yes, i have the right files) http://www.android-hilfe.de/root-ha...al-firmware-einspielen-softbrick-loesung.html
My problem now is: intalling the original files does not may any difference. I still have the teamwin recovery mode, still the omni logo and still a boot loop - even istalling the original firmware looked like it worked. No errors, right files...
Have no idea at the moment what do to, help would be great!
Problem still there - really need help
Hi - as still all ideas dit not work out (several roms and recoverys, locking and unlocking bootloader, access and new installation via RSD Lite...) I really would appeciate any idea to bring my Xoom back to life. Thanks for your help!
lowindustry said:
It looks like a bigger problem, I updated my xoom MZ601 and installed the 4.2.2 Omnirom and at first it worked - http://forum.xda-developers.com/showthread.php?t=2593414
Then I installed some apps and after half an hour my xoom crashed and now it's stuck in a boot loop. Installing the rom again does not work, any other rom too - always a boot loop.
Allright, I thought, let's do a full reset and use adb and fastboot to install the original software and firmware in my xoom. (the link is german, but it works and yes, i have the right files) http://www.android-hilfe.de/root-ha...al-firmware-einspielen-softbrick-loesung.html
My problem now is: intalling the original files does not may any difference. I still have the teamwin recovery mode, still the omni logo and still a boot loop - even istalling the original firmware looked like it worked. No errors, right files...
Have no idea at the moment what do to, help would be great!
Click to expand...
Click to collapse

[Q] Only fastboot accessible to flash / restore my TF700

Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Hey Your in the right place
Shoot me an email, we can review your issues and if we find a solution we can post back here to help
XDA users with there issues....
My email is everywhere talke a look around
Thx Josh
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Sounds like you are on an old bootloader. Flash the stock rom from asus by unzipping the zip you download from their website and placing in the root folder of your micro sd and then go into rck from the bootloader menu (power + volume down whilst booting)
Or you could just flash it from recovery....
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Asphodele said:
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Click to expand...
Click to collapse
I buy a tf700 with cm 11 a few days ago i am really interessted on how this steps works. I really want to make it unbrickeable, But i dont really understand how it works. I can not enter in fastboot. at least i got cwm interface when rebooting with adb into recovery.
Can u explain how you did it?
It invovles flashing a modified bootloader and the flatline recovery and then using Wheelie to generate your nvflash blobs.
Step-by-step instructions (which you need to follow to the letter) are here:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Stuck in boot loop, fastboot and recovery accessible
Hello,
I'm having a similar issue and I need help! Initially my tablet was rooted with Cromi-X 5.4. Then I decided to try Crombi-KK.
Here is what happened:
- Updated TWRP recovery
- Did a full wipe as recommended
- Flashing got stuck at the Crombi-KK loading sign
- Tried to reflash but TWRP wasn't detecting data partition anymore
- Instead installed the other recommended recovery CWMR.
- Flashed Crombi-KK, it worked. Played around with it for a few days, it was wonderful, fast and responsive.
- Battery died out and when I turned it back on I got a UIDs system inconsistent error.
- I found online many recommendations to reflash so I tried to do that
- Since then I'm stuck in a boot loop. I see the initial "bios" Asus logo then it restarts over and over.
- I am able to access bootloader and recovery
I've tried reflashing the asus stock blob. I've tried wiping the data through CWMR but it starts working and then it restarts. I don't know what to do anymore, so if anyone can help me, I would really appreciate it!
Thanks
Which recovery and bootloader version do you have now?
A (for KK) outdated bootloader seems the most likely culprit.
You can try save the recovery log when you flash or grab a logcat of the bootloop, but probably it'll only tell you that the recovery cannot mount /data.
Determine that you are on the correct bootloader, if not update it. If you're lucky the tablet will start right up. If it doesn't, formatting /data is the only way I know to get it back. Not just wiping - formatting it. You will loose everything on internal SD, so I hope you have a nandroid you can restore from later.
If you use TWRP 2.7+ be aware that formatting can take more than an hour. Let it finish!
For good measure, download CROMBi-KK again, check the md5 and then flash that file.
I'm on 10.6.1.14.10 bootloader which I think is the latest one
I have 6.0.4.7 CWMR
I'm trying to format data completely but when i do it in CWMR it starts and then the tablet reboots on it's own after a couple of minutes.
How can I retrieve the logs, I never had to do it before.
Thanks for your help
Mhh, getting a little more complicated.
Your BL is ok...
What do you see in CWM when you go into Mounts and Storage? What is mounted?
The recovery logs are under Advanced > show logs.
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
yasyas said:
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
Click to expand...
Click to collapse
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
sbdags said:
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
Click to expand...
Click to collapse
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
yasyas said:
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
Click to expand...
Click to collapse
To be in the safe side, yes, that is what I would do. TWTRP 2.7.+ takes a long time to format and it may seem the process got stuck. Give it at least 90 minutes to finish.
Then reflash CROMBi
I'm back up and running !!!
This time installing TWRP, everything was mounted (maybe my previous flash before CWMR wasn't good), did a format data, waited until it was done, flashed latest Crombi-KK and going through setup now. Hopefully won't have the same UID issue on next shutdown. I didn't enable fsync or journaling so hopefully it won't happen again.
Thanks both of you for your help!
Good deal! Happy for you!
Rooting google pixel zl

[Q] can't install 44s tried everything!

Hi all,
I need the pros here. It's NOT the regular wipe/clean/factoryreset bla bla issue.
received OPO from china with colorOS. Having the strangest behavior ever! I just can't install cyanogenmod 44S.
First I'll describe what I did:
unlock bootloader + TWRP with root + installed 44S using that comes prerooted from here: http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph44s-t2932551
device stuck on boot (powered by android msg)
wipe dalvik/cache didn't help.
wiped again ((format dalvik cache data system) and installed using fastboot official 44s from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
eventually after almost having a heart attack and trying all the permutation of wiping/installing official/unofficial cyanogem 44S - I thought installing an older version.
I can'ts emphasize how many times and effort I put into installing 44S.
I then wiped everything again (format dalvik cache data system), rebooted to recovery and installed 25s official.
It's working!
now I try to update but OTA doesn't find anything. tried reverting to cyanogenmod recovey also but that didn't help.
so I thought installing the zips one by one (the OTA ones) but that doesn't work because I get error executing updater binary in zip and something with apache.xml
In addition, I hate the fact I don't have native OTA...
Please help me upgrade to 44s and if possible - restore OTA functionality. I have this strange feeling that I destoryed something in the device internally or something. I don't see a reason why 44S won't work on my device after having full wipe....
I love you all please help!!! Thanks!!!!
p.s - One time I did succeed booting to 44S but when I reset the device (after factory reset) It was stuck again in boot screen.
Exactly what happens when you flash the 44S fastboot images? Can you please copy/paste the text from the command prompt here?
Transmitted via Bacon
I can flash using fastboot 44s without any issues. But after that I can't pass the "developed by android" boot screen...
Just tried again and this is the fastboot log: http://pastebin.com/TyaBn85F
Everything seems ok.
Does the fastboot zip that comes from cyanogenmod download page includes the stock kernel as well?
Did you wait enough time for it to boot? I find initial bit after a flash takes quite a long time. Sometimes up to 5 min
Sent From Lollipopified Bacon Goodness!
ron.r said:
I can flash using fastboot 44s without any issues. But after that I can't pass the "developed by android" boot screen...
Just tried again and this is the fastboot log: http://pastebin.com/TyaBn85F
Everything seems ok.
Does the fastboot zip that comes from cyanogenmod download page includes the stock kernel as well?
Click to expand...
Click to collapse
Yes it does, that's the boot partition.
Transmitted via Bacon
ek69 said:
Did you wait enough time for it to boot? I find initial bit after a flash takes quite a long time. Sometimes up to 5 min
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
i'm 20 minutes since installing. still boot screen.
I suspect it's something to do with either Color OS that came with my device handles file differently and left some buggy stuff that cyanogemnod can't handle OR cyanogenmod changed the ROM in 44s to raise somekind of a flag for china OPO (however with 25 I still can't use OTA or manual OTA zip)
It really sucks...I don't know what else to do.
Is there a special cleaning methodology I can use? (except format system/data/cache/dalvik from TWRP) to make the device as clean as possible before installing using fastboot?
Try reading the color os thread. There has to be someone who wanted to go from color os to another os and maybe there's a different way for that
Sent From Lollipopified Bacon Goodness!
ek69 said:
Try reading the color os thread. There has to be someone who wanted to go from color os to another os and maybe there's a different way for that
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Actually Iv'e been stuck on google (xda especially) trying to find answers for the past two days...and nada...
ron.r said:
Actually Iv'e been stuck on google (xda especially) trying to find answers for the past two days...and nada...
Click to expand...
Click to collapse
Go back to Stock Color Os and try this. Might just work.
https://forums.oneplus.net/threads/oneplus-one-coloros-to-cm11s-the-right-way.77361/
and no I am not a pro
Thanks. Saw that link. Just thought it's usless to go back to Color OS and do the whole process again...
UPDATES:
was able to install 33R using fastboot and everything works amazing including OTA...
BUT - after updating to 38R I have the same issue again. The device doesn't pass the boot screen.
UPDATE 2: After going to sleep frustrated with the device Off I woke up and tried to turn it on - and - it's working. how weird is that?
UPDATE 3: with 38R working (I really don't know how) I got OTA to 44S. I gladly updated. after pressing 'Install Update' the device turned off and didn't show the regular update script running in TWRP. Now the device stuck on boot screen again...so i'm back to square one.
Could it be that cyanogen changed something to block china versions?
UPDATE 4: turned the device in recovery mode and the update script (from 38R to 44S) ran immediately and when it's done it restarted the device.
The device is now back on. seems to be working with 44s. I'll do some more tests and if everything is fine i'll mark as solved.
BTW - the magic was probably installing 33R and from there start updating using OTA. However I don't know how to explain that after 38 OTA and short night sleep the device decided to wake up and work...
Ok. I know what's happening but I can't explain that.
Unless the device is powered off and after 30 seconds turned on - there's no way to pass the boot screen.
Restarting normally from working state doesn't work, restarting from recovery, power off and power on immediately doesn't work as well.
The ONLY way for me to pass the boot screen is to power the device off completely, go drink a small beer, come back (30 seconds is enough) and turn the device on.
Any advice???
ron.r said:
UPDATE 4: turned the device in recovery mode and the update script (from 38R to 44S) ran immediately and when it's done it restarted the device.
The device is now back on. seems to be working with 44s. I'll do some more tests and if everything is fine i'll mark as solved.
BTW - the magic was probably installing 33R and from there start updating using OTA. However I don't know how to explain that after 38 OTA and short night sleep the device decided to wake up and work...
Click to expand...
Click to collapse
Hello RON,
I'm in the same situation; did you solve the problem?
Briefly follows my tests:
- after updating from OTA to 44S the opo stuck at logo.
- reflashed the stock 38r...
- Applied 44s update from recovery but after restart the system stuck.
- installed the calkulin 44S and radio file from twrp... the opo stuck at logo "1"
- FLASHED stock 44s and new kernel from https://cyngn.com/products/oneplusone/ : stuck at logo.
gioninardo said:
Hello RON,
I'm in the same situation; did you solve the problem?
Briefly follows my tests:
- after updating from OTA to 44S the opo stuck at logo.
- reflashed the stock 38r...
- Applied 44s update from recovery but after restart the system stuck.
- installed the calkulin 44S and radio file from twrp... the opo stuck at logo "1"
- FLASHED stock 44s and new kernel from https://cyngn.com/products/oneplusone/ : stuck at logo.
Click to expand...
Click to collapse
reboot to recovery
it should install the 44s update
then restart normally.
if stuck on boot - turn the device off. after 30 seconds turn it on.
that worked for me.
ron.r said:
reboot to recovery
it should install the 44s update
then restart normally.
if stuck on boot - turn the device off. after 30 seconds turn it on.
that worked for me.
Click to expand...
Click to collapse
thank you.
Already done... but without result!
Just flash the 44S ROM using fastboot. You can find them on the forum.
Why flash an old ROM and uwe OTA if the most updated ROM is available...

Moto G 1st Gen XT1033 Boot Loop on Stock Lollipop

My Moto G (XT1033) 1st Gen with stock lollipop has stuck in a boot loop.
I am still able to go in to recovery mode. Have tried clearing cache, but that didn't seem to work.
I don't have CWM installed it's pure android as stock have installed updates only through OTAs.
Have googled about it and many are stating that a factory reset will solve the issue. But I don't want to lose data in the phone.
Main reason for the boot loop could be App as I use beta versions of Facebook, Whatsapp and Nova launcher from apkmirror.
What can be done to recover data or just get this boot loop fixed?
P.S: My device is not rooted and does not have any CWM or TWRP recovery.
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
BBThumbHealer said:
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
Click to expand...
Click to collapse
oh okay mate. I have been googling for such issue but the mostly suggested method is reset that I haven't done (not to lose data). Will wait for a day if I get any solution otherwise will reset it.
Let me know what happened to your phone. Hope it gets fixed soon
okay so here's the update. Was successful to take backup as per http://forum.xda-developers.com/showthread.php?t=2426426
And made factory reset after that but now it is still getting stuck on bootloop with M logo and powered by android screen. :crying:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
BBThumbHealer said:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Click to expand...
Click to collapse
Damn mate ! I am going to follow same steps.
1) Unlock bootloader
2) Flash custom recovery if needed
3) Flash Custom rom
btw did you had unlocked the bootloader? @BBThumbHealer
lost101 said:
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
Thank you for you reply mate. :good:
I have somehow managed to backup data by script. but the problem is now even after resetting it is still stuck into bootloop.
But I am a bit confused here in steps.
1) Unlock bootloader
2) Flash custom recovery like TWRP and clear dalvik cache
3) and then flash any custom rom
correct me if I am wrong. I am going to follow these steps. @lost101
Phone started! yeeey!
So heres the update bro @BBThumbHealer.
Unlocked bootloader.
Flashed TWRP.
Cleared cache/dalvik cache/data.
Flashed http://forum.xda-developers.com/moto-g/development/nx-nexus-experience-rom-10-0-3-ambient-t3268555/
And device is working smooth as silk now and that too with Marshmallow !:fingers-crossed:
Let me know your status bro. Hope I could help you in some way
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Hello guys, My phone is stuck on bootloop
I have already rooted device and now it is stuck on bootloop even the Recovery isn't opening. I know I would have to reset the phone with mfastboot but I want my internal storage to be backed up before doing all this Is there anyway to do so? Anyone here can help me out?
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
BBThumbHealer said:
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
Click to expand...
Click to collapse
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
sahil_arora05 said:
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
Click to expand...
Click to collapse
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
BBThumbHealer said:
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
Click to expand...
Click to collapse
Ok going to try that. Is there anyone who can provide me a link to download STOCK recovery for moto G xt1033. Can't find that.
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
BBThumbHealer said:
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
Click to expand...
Click to collapse
tThanks again buddy.
BBThumbHealer said:
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
I already gave you the solution in post #6. Stop ignoring what I say and do it.
BBThumbHealer said:
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
Thank you @BBThumbHealer.
Damn man that's the basic steps that you are following and that too pretty neat and right. Even though it is causing issues then there might be some other hardware bug may be ! Hope your phone gets started soon!
Hi Guys,
phone : Moto G (XT1033), Falcon
- stuck in bootloop
- able to go to recovery
- unable to flash custom recovery such as twrp or cwm
- as suggested,
1. Unlocked the bootloader successfully, can see code status = 3 in recovery mode
mfastboot oem unlock <CODE>​2. Unable to flash twrp. It writes successfully but shows stock recovery only
mfastboot flash recovery twrp-3.0.2-0-falcon.img​3. so tried booting twrp using with success
mfastboot boot twrp-3.0.2-0-falcon.img​4. cleaned cache, dalvik etc.
5 using twrp, used ADB which enables MTP which let me transfer Android6.0.1_NX_R10.3.3_MotoG2013.zip to internal memory
6 Using twrp to flash ROM - Android6.0.1_NX_R10.3.3_MotoG2013.zip​
It seems it started installing but its been more than one hour and it seems its still doing something.
It has stuck at - "Patching system image unconditionally..."
is this normal? Did I miss anything?
Appreciate help in advance. thank you for your time...
Best Regards,
Jignesh

Categories

Resources