Motorola xoom doesn't boot after bigPart - Xoom Q&A, Help & Troubleshooting

Hello there. I was flashing bigPart recovery to use a some kitkat rom on my xoom (everest), but when I wiped cache and dalvik partition(after I installed bigPart recovery ) I had a red "failed" write. Since that moment I'm not able to make boot my tablet. If I do it normally, it stay stucked on Motorola bootlogo, if I try to flash an other rom, the recovery doesn't find the external Sd where I put the files. So, I tried to restore stock ICS using Motorola RSD Lite tool, but when I connect the device to my pc it's not recognized. I'm getting very mad to try solving this !! What can I do ??
inviato dal tabellone ultragalattico s4

gab_ITA said:
Hello there. I was flashing bigPart recovery to use a some kitkat rom on my xoom (everest), but when I wiped cache and dalvik partition(after I installed bigPart recovery ) I had a red "failed" write. Since that moment I'm not able to make boot my tablet. If I do it normally, it stay stucked on Motorola bootlogo, if I try to flash an other rom, the recovery doesn't find the external Sd where I put the files. So, I tried to restore stock ICS using Motorola RSD Lite tool, but when I connect the device to my pc it's not recognized. I'm getting very mad to try solving this !! What can I do ??
inviato dal tabellone ultragalattico s4
Click to expand...
Click to collapse
up. please, it's important

Related

[Q] [q] ???help bricked maybe????

Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.
jekovenatinsley said:
Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.
Click to expand...
Click to collapse
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.
Hey man try this, it works for me (Same situation but i'm 17 xD)
1) Download this http://www.mediafire.com/?5diezc69u1b16f8
2)Extract the "recovery1" folder in C:\ drive
3)Plug the tablet to PC and turn it on while pressing VOL- and POWER, then go to the fastboot mode (is the USB symbol)
4)Download from here ( http://support.asus.com/Download.asp...300T&p=20&s=16 ) the WW of US instead of the version of the tablet you have got, the extract the blob file in the "recovery1" folder
5)Open CMD, type cd c:\recovery1 then press enter
6)Type dir to see if all the files are in the folder
7)type this command fastboot -i 0x0B05 flash system blob
8)After is done, type fastboot -i 0x0B05 reboot
9)Enjoy!
If you can't do any of this steps, post here and I will help you
Fixed It!
ZerOMKD said:
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.
Click to expand...
Click to collapse
Hey actually like 10 mins after I posted I was able to install Clean Rom.
I formated every partition except sd card in v6.0.1.2 cwm recovery as well as factory reset and wipe dalvik.
Actually I like cwm recovery better and it does support microsd cards now. This is the jb/touch bootloader.
Thanks for the Help anyways.
.
Same problem, when i try to flash JB Hydro 3.6... i stuck into bootloop... i flash the official asus update and it works... But when i try to flash the hydro rom it doesn't work.... Why?
I guess you have the new JellyBean Bootloader... because of that you can only flash ROM's which are made for it...
.
I know... i update from jb ota to hydro... but when i flash the 3.6 i got bootloop... and now i can flash this rom...

[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] Stuck in recovery restart limbo

Hello all,
Last night I was trying to install the latest Gummy release on my Verizon Galaxy S3. This was the first time I have tried to flash a rom on this phone. It failed, and I rebooted my phone, and now it will only boot into the clockwork recovery.
I thought it may have been damaged as i was transferring the file to the device. I had an SD card in my droid X, So I put it in my Galaxy and formatted it with clockwork. Then I transferred the gummy release (that I also re-downloaded) from my computer to the SD card via a memory card reader. I put it in my Galaxy and tried to install the release, and it gave me a different error
Code:
E: Can't Open /external_sd/Gummy-2.1-01-09-14-NIGHTLY-d2vzw.zip
(bad)
Installation aborted.
Edit: Tried a few other roms and they had the same issue, but Cyanogen Mod 10.2 worked. Anybody have any guesses why?
Edit2: Further developments, Trying to do the latest nightly fir the CM yields the same issue that Gummy's release gave me initially. It reports as follows:
Code:
E: Error in /external_sd/cm-11-20140110NIGHTLY-d2vzw.zip
(Status 7)
Installation aborted
Is there possibly a firmware issue at play?
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
twistedillutions said:
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
Click to expand...
Click to collapse
Sorry, forgot to mention, I did unlock with EZunlock. Would the clockwork on the play store be the latest one, or is there another place with more up to date versions?
Cappurnikus said:
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
Click to expand...
Click to collapse
Do you get the same error on install that I'm getting, ro are the installs finishing, but not booting?
Try goo manager or ez-recovery to install the latest recovery
right now i can think of
factory reset format data. Make sure u backup ur internal
Wen changing from rom to rom is a good thing to do a clean install
get the right gapps.
The 1st boot always takes time at least on me.
Sorry i cant think of more helpful things.. Been drinking
Looks like my recovery just needed an update. Thanks everyone.
Sent from my Nexus 7 using Tapatalk
Confirmed also an old recovery for me as well. Thank you very much!

[Q] Need help, transfer archives via recovery

Hi guys i need help, i wanted flash a ROM but i make format system, wipe data and i forgot transfer the ROM, now i don't know how transfer the Zip of the ROM, because i only. can enter into bootloader and recovery because the phone ovbiously don't start, help me.
PD: i can't use adb in recovery :c
If you wiped the data, there's nothing to recover.
Having the same issue now :crying:
Flashed my ROM and boot screen is stucked now, wiped all my data...
Have tried using TWRP and CWM old 4.3x but no luck, as when I try to boot recovery it just go straight pass it to boot the ROM. (Bootloader -> Recovery -> Volume Up)
I have noticed that my computer (Windows 8.1) is missing out driver for XT1034, however it should be identified as XT1032 not XT1034?
If I could get a driver software for XT1034, I could possibly use either Recovery mod to mount the /SDcarrd/ and then transfer the ROM zip file.
What I've currently using:
Tesco Moto G (8GB)
CWM v6.0.4.6
Previous ROM is Stock KK
Motorola DeviceManager Software - contains the drivers for Moto G
What I know was that my phone was definilty recognised as XT1032 and not sure why it changed to XT1034...
Please someone shed some light
Got it sorted now, back on 4.3!
http://forum.xda-developers.com/showthread.php?t=2542219

Pls help deleted official OS - stock ROM

Hi,
could you pleas help me. I was installing, wiping ROMs in safestrap and didnt pay attention and wipe stock ROM all the system everything. I can get to recovery mod but dont know what to do? Is it possilbe just download and install something in recovery?
Thank you
What device is it?
Sent from my Xperia Go using Tapatalk
Its Droid 4. I put it in forum there. but looks like nobody now. And I dont know if this problem is same for every android device? Sorry if it should be in different place.
I wanted wipe CM 10.2 but I have the stock rom in safestrap nad wipe everything from it and restart device
From my search online it appears that the original version was Gingerbread. The link below should still work even if you flashed to ICS because it would still be a stock update.
http://forums.androidcentral.com/mo...your-motorola-droid-4-stock-windows-only.html
Good luck and don't give up. A few days ago i totally wiped my Hisense Sero 7 Pro tab and though all was lost and was about to use it for spare parts until i kept scouring the net for the stock ROM.
I have the stock rom downloaded everything. But I cant open safestrap. Only I can do is system recovery which what I understand I cant flash any rom in it. Or I can open bootloader and use fastboot where is problem that I cant find the phone in rsd :/
So you put your phone in RSD mode and then connected your USB cable and then couldn't find your phone?
wirelesshead65 said:
So you put your phone in RSD mode and then connected your USB cable and then couldn't find your phone?
Click to expand...
Click to collapse
yes tried install the last rsd, all the drivers everything. the battery in phone died. So I have to buy factory cabel first now
Put the flashable zip in an sd card and flash from recovery..
Sent from my Xperia Go using Tapatalk
Your battery has to be at least 70% before you do anything. Then find where your Safestrap recovery is on your device. Then you go into RSD mode and as 74NK suggested with the ROM you downloaded on sd flash it to your device.
Again, good luck.
here's a solution
go it into the recovery mode by pressing(VOLUME UP+HOME+POWER)
wipe data/factory reset
wipe cache partition
wipe dalvik cache(optional according to your rom) @advanced
there you click install zip from sd card
there you choose your rom zip files then install zip
flash it
reboot system
enjoy your custom rom
@op did it work out for you?
Sent from my Xperia Go using Tapatalk

Categories

Resources