[Q] Need help flashing non partitioned ROM on wingray. - Xoom Q&A, Help & Troubleshooting

I recently flashed OMNI ROM 4.4 big part using TWRP, and I didn't like the UI. I am back to clockworkmod recovery, but I can't seem to flash any of the roms that I was able to before Like cm 10, 10.1 and eos. I have tried factory reseting, wiping data, cache, system, etc. In every way that I can think of with no success. It just freezes at the dual core tech startup screen. Can someone help get back to a non-partitioned ROM?

I recently reverted to EOS4 to use the EOS boot logo changer. I flashed the EOS ROM, then flashed the boot image from the BigPart support thread over it.
http://forum.xda-developers.com/showthread.php?t=2598962
That worked just fine for me, but some commenters on the BigPart thread said I could've borked my Xoom.

Working on a step-by-step guide now, but what the other guy said will work, especially if you want to use full GApps and not the gimped-down Xoom ones we were stuck with prior to BigPart.
Sent from my HTC6435LVW using xda app-developers app

Thanks for the help! That worked great, and a step-by-step guide would be nice to refer to in the future.

Related

[Q] CM10 Stable not working?

Ok. I just flashed CM10 stable on my SGS2 Skyrocket, and LOVE it, so I wanted to give it a shot on my Xoom (MZ604). I was having problems getting into CWM, due to the recovery image being overwritten (I was running stock, unrooted 4.1.2 until tonight).
I got that all sorted by flashing the stock, rooted ROM found here, and that was humming away fine. Rebooted into the bootloader, and flashed the CWM linked here. Rebooted into that version of CWM, only to find that I can't access my external SD card where I have the CM10 image stored.
Flashed back to the original CWM I had when first rooting, and flashed CM10. Flash went well, rebooted, and now I'm stuck at the CM load screen. The one with the circle going around and around.
I thought maybe something was wrong with my tablet, so I rebooted into CWM again, and reflashed the stock, rooted version, and it was fine. Flashed back over to CM10, and the same thing. Stuck at the load screen,. It has been there for at least 30 minutes.
I did wipe the cache and Dalvik before every flash of both ROMs.
Any ideas anyone? TIA
EDIT: Is it possible to put the CM10 image on internal SD card and flash it from there? I had assumed that wouldn't work because of formatting and the like, but if it's on /sdcard and not /system...
Edit 2: Just did a factory reset(can't believe I forgot this!!), and all is well now. Mods, please lock this thread. Thank you

[Q] Custom ROMs hanging on boot screen

Hi everyone, I'll go ahead and apologize for being a bit of a noob. I've got the TF300T, it's unlocked, rooted, running 4.2.1 bootloader, and I've installed TWRP 2.5.0.0. I've tried flashing the latest CM 10.1 nightly from here as well as the AOSPA 3+ from here. Both of them gave me the same result, after wiping the cache and dalvik, I rebooted and they both get hung up on the boot animation. I made a recovery before flashing that I keep going back to when this happens so it's definitely not bricked. Am I missing a step somewhere? I'll probably give one of the other ROMs a shot tomorrow, but in the meantime any help would be appreciated
Robo_Bear said:
Hi everyone, I'll go ahead and apologize for being a bit of a noob. I've got the TF300T, it's unlocked, rooted, running 4.2.1 bootloader, and I've installed TWRP 2.5.0.0. I've tried flashing the latest CM 10.1 nightly from here as well as the AOSPA 3+ from here. Both of them gave me the same result, after wiping the cache and dalvik, I rebooted and they both get hung up on the boot animation. I made a recovery before flashing that I keep going back to when this happens so it's definitely not bricked. Am I missing a step somewhere? I'll probably give one of the other ROMs a shot tomorrow, but in the meantime any help would be appreciated
Click to expand...
Click to collapse
The CM 10.1 ROM you are trying to flash will not work with 4.2.1 bootloader. You will need to either downgrade or use f69m's unofficial version for your bootloader version,, which can be found in Development section.
I would recommend the latter. Not that downgrading is difficult, but it does involve an element of risk of bricking your device if you do not flash correct version of custom recovery. There are excellent guides written for this, which should be easy to find.
Thanks for your quick response, I really appreciate it. I'll look around tomorrow and see if I can get it all sorted.
Robo_Bear said:
Thanks for your quick response, I really appreciate it. I'll look around tomorrow and see if I can get it all sorted.
Click to expand...
Click to collapse
You're welcome. If you choose to downgrade for using the official CM 10.1 nightly here is a guide:
http://forum.xda-developers.com/showthread.php?t=2195883
Choose the latest JB 4.1 version (10.4.2.20) and follow the guide. Make sure you flash the correct TWRP as stated in the guide. This is where far too many bricked their device.

Help with flashing ROMs

I've crawled through the development. I've flashed a ROM before, but went back to a rooted stock version because of the bugs in the builds I was using. But now, basically any time I flash something new, it bricks at the Galaxy Tab 2 7.0 screen.
I've done:
Flashed back to non-root stock firmware (newer)
Then flashed the CF Autoroot, installed Mobile Odin, flashed CWM official 6.0.2.3 for the 3113. When I install CM9, brick.
PA doesn't brick immediately but sticks at the splash with the shark.
So, I flashed back to non-root stock, CF Autoroot, installed CWM 6.0.1.1 and tried again. All ROMS besides PA hang at boot screen (like before), PA hanging at the shark.
I figured it was a kernel issue? So, I've tried both Dhollmen and AGNI. No change.
I can get it to rooted stock JB, but I don't *want* that, I want something that isn't so freaking bloated and buggy.
Ideas?
*edit*
So, after installing TWRP 2.5 on top of stock, I downloaded Rom Manager, installed CWM and CM9 through that. Got past the initial boot screen, but seem to be stuck on CM Splash. Would flashing older stock image and trying from there help?
This might seem like a dumb question since you say you have flashed ROMs before: are you doing a "clean" install? I also will wipe cache and dalvic cache AFTER each install. I only have "bricked" a device one time and that is when I tried short cuts. I also ALWAYS follow the developers instructions to the letter.
Sent from my GT-3113 running DF-2

[Q] Installing Any New ROM, No Boot, Stuck in Standard ROM FOREVER

I hate myself, for I am a noob.
Actually, I have just never posted because someone else has always posted the issue and fix for my problems, but this one make me want to paint the walls with my brains.
Obviously I have an Asus TF300T, and I have successfully unlocked and installed a custom recovery. I have TWRP 2.5.0.0 because apparently ClockWorkMod does not like the Asus 4.2 bootloader.
So I have the TWRP 2.5.0.0 Custom Recovery and Asus Stock Android 4.2.1, and every time that I install a new ROM and reboot I get stuck in the "Asus" window, the window it shows right before it loads the oparating system. So it tells me that it cannot read or there is no operating system found. I am doing a wipe Dalvik Cache, System, Cache, and Data before I do the install of the new ROM, but it never gets to the new operating system.
I am wanting to get to CyanogenMod, and I have tried all versions of if with the same result. I have also tried AOKP and Baked Bean and I still get the same thing.
So I found another post earlier and they suggested there was an issue with the Asus 4.2 BootLoader, and I was excited because I was sure that was the problem all along! ... Not...
So I was able to get the .zip of the Asus Stock Android 4.1.1, and I was able to get into TWRP and install that. Magically, that worked and I am now on Asus Stock Android 4.1.1, which to my understanding should mean I have the Asus 4.1 Boodloader. Since the OS Version changed, I also had to change the version of TRWP. It is still TWRP 2.5.0.0, but for Asus 4.1. So I install a new ROM and I get the same exact issue as before...
At this point, I have no idea. I feel ashamed to have to post a question and ask, but does anyone have any ideas what else I might be able to try? Or it looks like I am stuck with the default version of Android and I should have never unlocked it.
Thank you!
Mostly Fixed
I was able to finally get to CM 10.1, but only after I installed Asus 4.1 Boot loader.
But all versions of CM 10.2 just get to the ASUS menu and it flashes and goes back to that screen every 45 seconds. Any ideas, or I suppose I should go to a CM forum at that point?
JEYoung4545 said:
I was able to finally get to CM 10.1, but only after I installed Asus 4.1 Boot loader.
But all versions of CM 10.2 just get to the ASUS menu and it flashes and goes back to that screen every 45 seconds. Any ideas, or I suppose I should go to a CM forum at that point?
Click to expand...
Click to collapse
If you itch so much to install CM 10.2 on your tab, the dedicated thread in development recommends that you run it with 4.2 bootloader. Give it a try to see if it solves your problem.
if you want to run cm10.2 just upgrade to latest stock, flash twrp2.6.0.1/ 2.6.0.0 and flash cm10.2.
cheers
Buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Why did this happen?

My father has a Skyrocket and he didn't like how slow and clunky it was from stock, so I decided to flash a ROM that I knew well and would make his phone a more enjoyable experience. I flashed TWRP, put Carbon ROM (latest nightly) and the latest 4.3 Gapps on his SD Card, and flashed. Keep in mind I wiped data, dalvik, cache, and system before I flashed anything. Everything went well, phone booted, I got it configured and installed most of the apps he likes to use and it was good to go. A while earlier, I rebooted the phone normally, not into recovery or bootloader, just a normal reboot. The phone shut off, buzzed, and wouldn't come back to life. Pulling battery, button combinations, it would only go to the Battery Icon screen. PC wouldn't recognize, etc. Managed to get it into Odin, flashed stock, it hung at Samsung screen so I had to wipe data in stock recovery. It is running fine now on stock 4.1.2 but I'm really scratching my head at why a simple reboot soft bricked his phone. Used TWRP 2.6.0.0 btw.
That recovery is old to begin with. Second, 4.3 isn't the most stable right now
Sent from my HTC One using Tapatalk 4
Yea, use twrp 2.6.3.0. If you want 4.3 cm 10.2 is working pretty well right now.
Agreed, this is 100% because you used TWRP 2.6.0.0. 2.6.0.3 is the minimum required version for and 4.3 based ROM, and as mentioned 2.6.3.0 is the latest official release.
Thank you all very much. It didn't even cross my mind that the recovery version could be the issue. I guess I might try again later on the newest TWRP.
Sent from my MB886 using xda app-developers app
I have recently had a similar issue with a 4.3 ROM, and I am using 2.6.0.3. Only I could get into recovery after a battery pull and button combo. I just kept following the same steps of wiping flashing and it eventually it took and is running fine now(just jinxed myself I am sure).

Categories

Resources