Related
hi, i have been reading up alot today on how to root and install a rom on my xoom, i rooted it fine then i went to the ics thread and downloaded the latest build, v17... put the zip on the sd card and went into recovery mode, choose to install zip from sd and installed it, then went to reboot device and it rebooted but came to a black screen that says android across the middle, its been on that screen for 20 mins now, help please lol
sorry... sorted problem, im guessing its bcos i wasnt installing google apps from zip too, sorry again
Honestly I have run into the same issues...hold down the volume up button + power...your Xoom should reboot.
Then you see the red Motorola logo wait 3 seconds and hit volume down...you should see "Android Recovery Mode" in the upper left corner.
Hit volume up to select....your device should enter recovery mode.
From here wipe data factory reset...wipe cache partition...then go to advanced...and wipe dalvik cache.
Then go to install zip from SD card and reinstall the ROM and Gapps and you should be fine, the first boot can take up to 10 minutes so don't panic...
XOOM Running Team EOS latest ICS build v.17 OC'd @ 1.5Ghz
Sent from my DROIDX using xda premium
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Boarder277 said:
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Click to expand...
Click to collapse
No, don't be sorry. That was a great explanation.
I know you got it fixed but I will say this:
Always do a full wipe when flashing a new rom. In this case, the ICS build was a new ROM and you should have wiped.
Usually you do not need to do a full wipe if you are just flashing a new build of the same ROM (if you go to a new nightly for instance). Just need to clear cache/delvik and reinstall gapps.
Hi guys
Before I explain I'd like to say that yes, I have read other threads on similar topics, although none seem to have the same symptoms as me...
This week I bought a software-bricked Defy on eBay with the hopes of fixing it and giving it to a friend. I first tried flashing an old Eclair SBF to no avail (only switched on to bootloader) and thought that it could be failing due to it being on a newer firmware. So then I tried Froyo, and when that didn't work either (bootloops like when I received the phone) I thought my last resort was a CG 5 SBF, so I went for the JORDN_U3_97.21.51 build. This seems to get further into the booting process, with the MotoBLUR animation appearing but I get a BP Panic - 0x00080010 above the animation before the phone switches off. Thinking I had nothing to lose I tried a Gingerbread ROM, but that just bootlooped too so I went back to 97.21.51. I realise I've probably painted myself into a corner by flashing these
I'm all out of ideas with how to get the phone any further and have searched for the BP panic to no avail. I can get into stock recovery and bootloader, although the recovery seems to have issues with accessing the cache sometimes.
Thanks for reading
The same panic have y for the last 2 weeks, after flashing hangs in bootloader (red logo and no animation), after other flash hangs on a animated red logo and thats where you must give it time 3 or 4 min. wating, when its dont works you can try to pul out battery and do it in again while you hold the start and vol. down button, then in recovery menu wipe Dalvik cache and wipe cahe. Maby it works then, when not you can try like me to go again tho recovery and there restore stockrom, thats the way ym getting my defy work again. There are many ways to get it back to work again and it cost me 2 weeks after flashing maby 15 diverend roms to get it works and even than when it works, 2 days work whit rooting it and get 3G alive. So when you think its dead, maby RSDlite can bring it back to live, just like here.
Now my Defy MB525 working like a Defy 526 on Gingerbread.
So don't give up, when you can see whit RSDlite the phoon, it must be possible to get it work, only problem here was on a moment when the battery was empty, but here on XDA you can find the megayver method (charging on a ohter cell like a duo) or what y have don, get my old nokia loader (5V) and whit 2 wires hangs on the battery power it up to 4.1 V, succes.
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
ben_duder said:
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
Click to expand...
Click to collapse
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
nogoodusername said:
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, although I'm pretty sure I did wipe cache and data... and I definitely did (several times ) after flashing Gingerbread. I feel like whatever is preventing Froyo and Gingerbread from booting is the same thing as what is giving me the BP panic on the CG 5 Eclair ROM.
I would suspect a hardware issue here.w
Sent from my MB525 using Tapatalk
I think it might be too It's a shame because I can enter recovery and bootloader okay, and the seller said it broke during a failed software update so I thought it would be a simple matter of reflashing an SBF.
what is bp panic?
what happens when it is booting?
Sent from my MB525 using xda premium
When I try to boot the CG 5 Eclair I get past the static Motorola logo (hence further than any other build) but the MotoBLUR animation is stuttery, with a BP panic at the top (see picture). This goes on for quite a while, then the phone switches off and this loops.
Ok if occurred during a software update, find out which he was installing and try that one. May also be worth trying motoupdate.
Sent from my MB525 using Tapatalk
I might try that, but won't it be useless now that I've flashed CG 5? I'll look into MotoUpdate
Is the general consensus that this is an unfixable hardware issue, then?
Apolgoies if you've already tried this, but I had a Defy which would do the same, either stuck on M logo or error in bootloader.
Each time I just plugged it into PC / USB at bootloader screen, and used RSD Lite to try another ROM. Eventually I found one which worked. I think I tried 5 before finding one which didn't cause any problems.
My defy was a ME525+ and the ROM which finally worked was "DEFYPLUS_U3_4.5.1-134_DFP-132_BLUR"
So, if you haven't already, I'd just suggest try a few more ROMS, flashed from Bootloader / RSD Lite.
Hope it helps somehow
everytime i flash a rom, it gets stuck at the bootanimation or the setup wizard any suggestions? i used to flash roms before but it started happening recently and i cant pinpoint why it freezes
My friend had that issue too. It turned out he wasn't wiping /system before he flashed. Too much crap built up in there from too many ROMs.
estallings15 said:
My friend had that issue too. It turned out he wasn't wiping /system before he flashed. Too much crap built up in there from too many ROMs.
Click to expand...
Click to collapse
I use 4ext app and do a ext 4 wipe and it seems to work okay for me. sometimes ill manually wipe all partitions but usually dont need to.
Yeah I tried wiping everything
I did factory and cache
Then dalvik
Then under mounts and storage I format system,data,and cache
Maybe I'll try 4 ext
Look at the logcat.
If you have clockworkmod lower than v3, and you flash a gingerbread rom, it naturally get s stucked by bootanimation. But if you have the latest one of the recovery, which supports ext4, and it stuck at the bootanimation (not the white splash screen), then you must wait until the drivers are initialized.
Sent from my Black Ice'd Glacier using XDA App
My cwm is the latest one I believe (5.0.2.0 or something like that)
I tried loading zipnets ice rom and it hangs at the clock animation
I tried the new sense 3.6 rom. (Forgot name) and sometimes it freezes at the bootamimation,setup, or at the home screen
What do you mean wait for drivers to install?
Sent from my Transformer TF101 using XDA
The first start after a rom install is always the longest one. That is usual. Try to wait about three - five mins and then it is done. After that you can use it.
Sent from my Black Ice'd Glacier using XDA App
Also after it boots, give it a few minutes to settle in and turn on mobile netowork ect.
Sent from my Sense 3.6 Glacier using XDA Premium.
How long should I wait? Last time I waited 20 mins and it was still frozen
edit: ok i tried 4ext and used the format everything except sd card and still get a frozen boot animation any other suggestions?
Did you follow Jack_R1's suggestion and run logcat?
so after hours of tinkering around these boards and through everyone's help, i found out i have the bad emmc which is what im assuming the problem is but why was i able to flash roms before? or was it just luck?
Hi,
I flashed the google edition rom a few weeks ago, all was working fine. This morning, I decided to flash a stock rom from sammobile (was this a bad idea)? I used CF autoroot and twerp custom recovery. It failed. So wiped everything, reflashed the google edition rom, but when I reboot the phone it gets stuck showing "Samsung galaxy s4" white text.
To boot it again i have to wipe data, cache and dalvik, then reflash the ROM, then qipe cache and dalvik, then it reboots. But when I turn it off then on again the whole process starts again.
Can anybody tell me what I'm doing wrong? This is the same ROM that worked faultlessly for weeks...
Thanks
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
richard2311 said:
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
dickson123 said:
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
Click to expand...
Click to collapse
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
mobileguynz said:
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
Click to expand...
Click to collapse
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
dickson123 said:
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
Click to expand...
Click to collapse
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
mobileguynz said:
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
Click to expand...
Click to collapse
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
dickson123 said:
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
Click to expand...
Click to collapse
If you flashed the latest stock ROM it maybe be one with Knox and that has a secure boot loader and kernel secure Selinux Knox stops you from modifying and installing.
Try using ausdims v16 kernel or wadams Adam kernel for stock roms. Note when I flashed the last ROM waited 10 minutes and had do a wipe and reset for it to boot see last pages for discussion http://forum.xda-developers.com/showthread.php?t=2250824
http://forum.xda-developers.com/showthread.php?t=2250824
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
I also think there's a problem with your battery, it might need to be replaced.
ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped