So, I think my Xoom is an MZ602 (don't remember which - it's US Retail with WiFi and a Verizon SIM). I don't care about using the SIM card, so I'm fine with using 604 ROMs.
My Xoom will not boot any ROM I have tried to use - it just gets stuck infinitely looping the boot image. This includes all of the CM11 versions that I've found on here and OmniROM 4.4 and 5.1.
The stock 600 ROM worked just fine. I tried OmniROM 5.1 again after booting stock and it's still looping the boot image. It does, however, reach a point where adb commands work after a while.
I need help getting this thing to run a ROM equivalent to Android 4.4 or later.
If that's not possible, at the very least I'd like to get this back to 4.1.2 because I really can't stand using Honeycomb.
Edit: the 4.1.2 update file that I found did not work. I got the boot image, but it won't go past that.
First you need to repartition your TAB: https://forum.xda-developers.com/showthread.php?t=2506997
Secound Flash this ROM 4.4.4 and this Gapp from this: https://forum.xda-developers.com/motorola-xoom/general/roms-motorola-xoom-t3602655
Related
Ok, this is weird, a while ago i didnt had any problems installing any kind of custom rom, used CWM while wiping everything... eveything was OK, ROM worked OK, etc... But one time i installed a ROM (Slimkat) and i lost signal, tried to use my recovery of stock android but it didnt work, so i tried a lot of things untill i got bootlop without being able to install anything since some files were missing, bad luck
After that, i just reflash stock 4.3 and upgrade from there 4.4.2, everything fine again... except that i cant install any kind of ROM, every ROM says "installation succesful" but everyone is stuck into bootloop.
While i havent tried ALL ROMS i have tried the same ones i was using (Nexus G+, LiquidSmooth and CM11), so i guess this problem is coming from my device.
On a side note, i tried to factory reset, but no luck... it shows the Android working but it inmediately turns the screen off, and then it shows it again and then off again... in an infinite loop
Same problem!
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Liberr said:
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Click to expand...
Click to collapse
Hmmm... Pay attention to which version of Bootloader you are using.
You might want to try both 4.3 and 4.4 to see which one would work.
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Good luck!
neozen21 said:
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Liberr said:
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Click to expand...
Click to collapse
Hmmm.. I see there is a version number on mine, 41.05 dated 2013-12-06, but I'm not sure if that's the version or not.
And yeah... if changing the bootloader doesn't help, you probably would have to restore from the stock image and start over..
Got root and custom roms working after I 1.) downgraded to 4.3 and 2.) flash TWRP (instead of CWM).
So I'm not sure what the problem was. Besides the two main rooting methods (superboot and custom recovery), there are some other methods described on the forum specifically for people who already did a international variant OTA to 4.4.2. and one that is absolete (here) but apparently works for some when the two main methods fail.
However I'm still not sure if this solved everything. I am not sure if I can flash Cyanogenmod (which is 4.4.2) over a 4.3 firmware. Maybe I need to manually flash a 4.4.2 radio or something... Gonna check that out next...
EDIT: No need to downgrade. Not sure how it works but two main root methods (superboot and custom recovery) didn't work for me. Somehow I got stuck in boot animation. Just installed TWRP instead of CWM after Kitkat firmware (EU Retail) and rooted (/installed Super Su) from there. Everything works fine now.
Hello! Recently purchased a used (but like new) S Relay off of Ebay. It came with 4.1.2 already installed.
Basically let me tell you a brief backstory: I started off by installing Custom Recovery (CWM PhilZ 6.07) using ODIN and backing a NANDroid Backup. Then flashed KitKat CM 11 from CWM (wanted to try it out but didn't like it more than Jellybean). So I restored my backup via custom recovery.
Then I tried unlocking the sim network from T-mobile so I can use this phone when I travel abroad (using the method in http://forum.xda-developers.com/showthread.php?t=2255892 ). But apparently I found this doesn't work except on the stock Ice Cream Sandwich rom. So I flashed the LH1 stock rom using ODIN. Then I did the unlock method and it appeared successful. (it recognized an AT&T sim I have without asking for an unlock code)
So long story short, I used the custom recovery again to restore to my stock version of 4.1.2 Jellybean. But my baseband version is still LH1. I want to update it to UVMA2. I tried using a zip to update it from LH1 to UVMA2. But it always fails and aborts. It gives me Error Status 7. Which from google apparently means the device name doesn't match the one on the zip package.
I also try installing other minor packages. Which all incur the same error 7. So I'm not really sure if I'm just a really stupid beginner. Or if I've messed something up when I went to Kitkat and back. Or perhaps when I downgraded to 4.0 to unlock the network....
I tried using this ( http://forum.xda-developers.com/showthread.php?t=2302599 ) guide to fix the packages by removing the initial device name check. Yet it still fails/aborts before trying to install.
Any help or insights for this beginner would be greatly appreciated, thank you
Edit: The device name should be "apexqtmo" apparently...
Was able to flash to UVBMC5 baseband. Is that perhaps the latest version? It appears to be one of the most recent from google.
Hey folks,
i got a serious issue with my MotoG...
I tried to install/flash the GPe Rom (Android 4.4.2) here from xda and it fully worked. After the install process i received the OTA Update to Android 4.4.4 and installed it with the stock recovery. The result was a working up to date GPe rom where i deleted some system apps. I rebooted the phone and got stuck at the boot logo from Google with the unlocked symbol. A full wipe and reflash of the GPe Rom didn't fixed the problem. The phone sticks at the boot logo. After this i tried to reflash the Motorola Rom which didnt fixed it either....
My guess is that the OTA Update from GPe changed something which can't be fixed with older firmware flashes...!?
After a couple of hours of work i pushed via adb my CWM backup to the internal storage and restored it. My Moto booted and i was finally able to get it back to run the stockrom.
Then i saw something weird... The google logo with the unlock symbol stays and then the motorola boot logo appears and im not able to flash via fastboot other rom
Anyone experience similar or the same problem after restore from GPe 4.4.4 to lower Android version 4.4.2?
Thanks in advance for help and tipps
Flamey
many peopla have bricked phones right now
we have to wait for fastboot images of 444 or gpe 444
there are none yet
Yeah I'm luckily half bricked..
Can't flash stock..
Stuck with CM based ROMs..
I go either side and my phone dies..
Sent from my Moto G using XDA Premium 4 mobile app
http://forum.xda-developers.com/moto-g/general/howto-fix-stuck-boot-downgrading-t2808098
you can use that
lol sorry, you fixed the issue by your own guide, lol
Hello,
I have an XT1032 ('falcon') MotoG, purchased from Tesco in the UK. The bootloader was unlocked very soon after I bought it and I purchased an unlock code to allow it to be used on all UK networks. It works well. I think it was supplied with Android 4.3 Jellybean, and it was updated OTA to 4.4.4 KitKat.
I'm trying to install CM11 M6 (dated 4/5/2014) on the 'phone using CWM6.0.4.7. It appears to install fine, but goes to the bootloop, with the CM face in the middle and the rotating arrow running around it - and never progresses from there. This seems to be a common problem as there are a number of threads about it on this forum. It appears that the solution is to downgrade it to 4.3 by flashing it.
Following the instructions here:
http://www.nerdoholic.com/mobiles/restore-stock-firmware-motorola-moto-g/
... the opening instruction is "Download and install Motorola drivers" - which is where the problems start as it appears that the Motorola drivers are only available for Windows and Mac users, but not for Linux users, and I only have Ubuntu machines to play with.
So, where do I go from here? How can I downgrade to 4.3 with a Linux machine? I have tried the instructions, and they don't complete (although they seem to get most of the way there.)
Alternatively, is there any other way of installing CM11 on my 'phone without downgrading? There seem to be some people around who have made it work by installing CM11 twice (which didn't work for me), by wiping the 'phone and the Dalvik Cache (which also hasn't worked) or by using a different Recovery tool ('Philz Advanced CWM Tool' is mentioned occasionally, but I haven't tried it.)
All help welcomed, thanks. (For clarity, the 'phone is an original Moto G, 16GB. It's not the Moto G2, nor is it the 4G/LTE version that was released a little later.)
Oli.
A little more information - I have backed-up the working configuration of the 'phone with CWM and can restore from it fine. This is hence allowing me to tinker with all sort of other configurations and still get back to an operational 'phone - which is great! However I would be nervous about trying anything that would jeopardise this restore capability, which is one of the reasons why I haven't progressed with Philz Advanced CWM Tool.
Oli.
Linux requires no drivers. Fastboot tutorial here:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378http://forum.xda-developers.com/showthread.php?t=2542219
You cannot boot into 4.3 with your 4.4.4 bootloader. I suggest you flash the Retail UK 4.4.4 firmware image available here:
http://forum.xda-developers.com/showpost.php?p=54872143&postcount=362
Lost101,
Thanks - I suspected that it was the case that Ubuntu needed no drivers. Will the fact that I am trying to downgrade from 4.4.4 to 4.3 explain the fact that the flash didn't complete?
If so, and I try using the Retail UK 4.4.4 image then will it subsequently allow me to install CM11 (which is my final goal)?
Thanks again for your help.
Oli.
Personally I am more inclined to suspect the ROM itself and/or your custom recovery version is the problem.
Lost101,
Thanks again. Following the instructions in your first post (above) has successfully installed 4.4.4 from the Retail UK image. It boots and (appears) to work OK. However manually rebooting into fastboot and choosing 'Recovery' has highlighted the fact that CWM seems to have been lost and SuperSU is not in the Apps List - so it really does look like a very stock build (albeit the unlocked bootloader remains unlocked, as you'd expect).
I guess I therefore gain Root Access and re-install CWM and see where we go from there. Thanks again for your help.
Oli.
You have been using an early build of CWM. I recommend Philz Touch or TWRP.
To flash custom recovery in Fastboot:
fastboot flash recovery recovery-name.img
Hi,
I wonder if anyone could offer me a little assistance please ? I have a UK Tesco Moto G 16GB (2013) that I have successfully unlocked the bootloader and rooted and CWM recovery installed. Currently, it's running 4.4.4 Kitkat. I gave up with the OTA update as I was getting the 'preflash validation failed' message. More recently, I have tried following the guide on here to flash the XT1032_GPE_5.1_Optimized_v1.1.zip file using CWM. However, this resulted in what I believe is termed a bootloop - i.e. the coloured dots animation just never stopped - I waited half an hour and it was still going.
I've managed to restore it back to my previous 4.4.4 for the moment, but I would like to move to Lollipop at some point - if I could !
Could someone suggest a method I could try please ?
Many thanks !
Kev.
Hi there.
Well, my device is a XT1032 Retail US but I may have been through the problems you're facing right now.
Here we go:
Go full stock (don't know if you revocer from a backup or already did this but in any case you'd know what to do: This guide helped me a lot. http://forum.xda-developers.com/showthread.php?t=2542219.
Do not install any official update using a custom recovery
Make sure you got the actual latest recovery version. If you went stock from the latest firmware you should have already got it.
If you have your OTA, Install it manually from the stock recovery
This method should work. It is the one I followed.
I got two errors: 1st was because was using custom recovery.
2nd was because my rom was stock but had deleted system apps, so the install failed always at some point.
Once I flashed the latest stock firmware including the stock recovery, I was able to install my OTA update.
Let me know if this works.