[Q] Help! Can't get past M logo after EOS4 installation on STINGRAY - Xoom Q&A, Help & Troubleshooting

Hi all, I've been rooting and installing custom roms on lots of devices for a couple of years now. I didn't consider myself a noob after successfully getting cyanogen 9 or 10 on tenderloin and cm10.2 on tate.
However, it seems that I have completely missed something while installing EOS4 20130705-199 on the Motorola Xoom.
I had no problems with SDK install, adb, fastboot, got TWRP running w/ root. All this is from stock, mind you, if that makes any difference.
So then I decided to grab teamEOS's EOS4 and run that as the newest Android OS (that is arguably stable) that has been ported to the Xoom.
Well, I think I must have rebooted at a point that I wasn't supposed to, because I lost the ability to load the EOS-stingray-20130705-199.zip via ADB.
So I went into TWRP recovery and attempted to ADB sideload the rom file. Seemed to work for transferring, but after wiping caches and rebooting, I'm stuck on MOTO dual-core logo. I can get back into TWRP, though so I tried doing factory reset, wiping caches, and installing from an 8GB microSD card (/sdcard). Wiped caches again and then reboot... Same result, MOTO dual-core logo.
Ok, so now to barebones... Boot into fastboot mode and flash boot.img from EOS-stingray-20130705-199.zip and then boot back into TWRP and install rom again.... Same result, MOTO dual-core logo.
As you can probably guess at this point I'm getting a bit frustrated. I'm about ready to see how a Xoom flies when launched from a skeet clay launcher. Pull!..... BLAM! Just kidding, but I really do need to get this device back running.
Does anybody have any suggestions?

199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.

airesch said:
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
Click to expand...
Click to collapse
Thanks for the reply. I shall give -197 a try.
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset). The advice alone is worth it's weight in gold.

Bad news.
I just downloaded -197 fresh from goo, in fact I did it twice because I couldn't believe the results.
It actually fails to install giving the error "cannot open zip file" -199 never did that.
I also tried -131 (cdma) just to prove to myself that I have the right model. Same results, MOTO logo no boot.

Can't actually believe i am saying this, looks like goo's version is corrupt (my md5 doesn't match theirs and I just looked up the cached version of the webpage and it has d81cded40671c9c0963f95273859dbdd (which is what mine is.)
I will try to pm you a link of the file I have on my dropbox in a bit.

Thanks for this AIRESCH
Your version of -197 is working perfectly.
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Thanks again.

punishermoose said:
Thanks for this AIRESCH
Your version of -197 is working perfectly.
Click to expand...
Click to collapse
Excellent
punishermoose said:
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Click to expand...
Click to collapse
Not sure this is necessary, goo has been replacing/upgrading hardware and may not have everything up yet (none of the files were there for a good week at the start of the month.) They may get the right files back up before too long. It does suck for anyone trying to get the files right now tho.
I'm glad your up and working.
Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.)
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset).
Click to expand...
Click to collapse
ah, but you don't learn if it's not explained
Reason is: the Xoom only has a 256MB system partition and unfortunately the OS+Gapps (which normally resides in system) as of 4.1 or 4.2 comes to well over this amount. The rom developers HAVE been (they are currently trying to change this) making it so that some of Gapps gets enough copied into the data partition to make everything fit and symlink the files back into system. This has the positive effect of being able to have everything work even without enough space. However the downside is that if you factory reset it will wipe out the files in the data partition, leaving broken symlinks pointing to nothing, and makes it so some of it doesn't work anymore (how much depends on what gapps your using.)
In short: We have awesome devs that are still trying to fix the problem, but their current solution requires you to re-flash gapps (at a minimum, i normally recommend re-flashing both system and gapps) after a factory reset (which is not the end of the world (unless you don't have them both anymore.))

Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app

SgtTeabag said:
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat. Need a good download/copy of 197, please! The goo.im 197 download is borked!!

Related

[Q] Problems with most Roms

I am unlocked and have the recovery of twrp 2.3.3.0. I'm having problems with about every single rom I flash. I wipe everything as you are suppose to and the flash appears to go well but usually right away after the rom boots up the system becomes unresponsive. I have to hold my finger over a button for a couple seconds for it to acknowledge a touch and things just don"t run right.
Its like either the system is almost locked up or the touchscreen just hardly works.... one of the two. I made a backup of my original asus setup and if I restore it the tablet works just fine. I've tried hydro, cm 10.1, blackbean 7, and one or two I'm forgetting. AOKP RC1 is the only custom rom that gives me no problems at all in this regard, unfortunately its an unfinished rom, no camera and my battery dies like crazy with it...
The 2nd best running rom that I really like from what I have seen is blackbean 7. Runs great for first few minutes but after playing a game for a bit or doing some other things and having it run just great all the sudden the dreaded problem occurs and the only fix is a reboot for it to work for a while longer. So frustrated at this point as I have flashed so many roms and resetup so many things just to find myself doing it again trying to fix this and find a rom that works for me.
Any ideas at all on what could do this? Is the difference in the kernels the reason why AOKP RC1 and Asus original work but none of the others? Or does it have to do with my recovery? Fairly certain I have the correct most recommended one with twrp 2.3.3.0 and the process went fine. Any ideas greatly appreciated. I really just want to be able to run blackbean. And knowing that most all roms will not work for me is rather disturbing in regards to the future. Really wanting to like my new tf300t but its making it hard:silly:
Try to downgrade your recovery.
Use this : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
and take a feedback after, thanks
I really appreciate that you took the time to give me something to try but I'm afraid it didn't work. Process went fine I'm on 2.3.1.0 twrp but same problem. First rom I've tried instant non-responsive. Any other ideas?
I've been using ClockWorkMod Recovery on my TF300T, and it's been great. (Used it to upgrade my ROM to CM 10.1.) No issues at all.
If you need instructions for getting it installed on a TF300T, check out my second-to-last post on thoughtsontechnology.com. (NONE of the work is mine, I just compiled the instructions and links in one spot for easier access. Most of the work came from XDA contributors, they've been really great.)
Most roms need 5 to 10 mins to stabilize after a new install, usually as they are building media storage files, etc. Are you giving them enough time?
Failing that I can only think your microsd has something corrupt on it. Boot with it out.
Well I tried cwm again flashed it no problem installed rom no problem but no fix. So guess we have established it definitely isn't the recovery at this point...
Yes I've given roms several reboots and lots of suffering them working for 10min to only fail again for another reboot... So its not that. Still the only Rom that will work is my backup of the original asus and the AOKP RC1. Trying it without the external sdcard right now.
Well no joy on the removal of the external sdcard
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
sbdags said:
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
Click to expand...
Click to collapse
Not sure what a full wipe is? I wipe cache/dalvik system format data and have even tried formatting the sdcard once several roms ago. One thing I have noticed since I am trying so many roms all the time is the sdcard file structure seems odd as I have at the root of the sdcard a 0 directory that continues to be added to. Currently it goes sdcard/0/0/0/0 to actually get to where I have things stored like music, downloads. Is this normal? Its strangely repetitive.
Personally I think you should stop using TWRP if you're having all these issues. Just flash CWM and have fun
touchscreen
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Showme1 said:
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Click to expand...
Click to collapse
Sounds like you have a hardware fault if the issue persists across multiple firmwares.
Also, OP said his SD card directory structure was strange. I'd format both internal and external SD in recovery (in addition to wiping and factory reset) before you flash.
Thanks! Wiping internal has seemed to do the job. Still would like to know what the issue was. I was thinking it was the touch panel firmware, but thought that would be in /system
Sent from my SGH-I747 using xda app-developers app

[Q] Recovery is broken??? I Don't Know.. Please Help

So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.
alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk

[Q] chameleon os superuser or root problem

I run chameleon os custom rom on Samsung infuse 4g. Superuser by Clockworkmod got binded/imbedded into rom. Was working fine, then out of nowhere got disabled under superuser settings and will not change back. I select apps only and all other choices but as soon as I select it, it switches back to disable. Google play no longer shows it as an app that I have downloaded so I can't get updates. I have tried installing it again both by just downloading it and by disabling it under app management and downloading it, but both ways when I open it tries to downloading binaries and fails. Same thing happens with any other superuser I try to download. I cannot get it to work. Please help. I no longer want chameleon as my rom because of too many issues with it constantly rebooting and internet only working sometimes. i want to try another rom but can't with superuser not working. Here is my phone info:
> Model #
> SGH-I997
>
> Android
> 4.2.2
>
> Baseband version
> I997UCLB3
>
> Kernel version
> 2.6.35.7-I997UCLB3-CL9997492-g431d68f
>
> CPU
> ARMv7 Processor rev2 (v71)
>
> ChameleonOS version
> 0.7-20130426-unofficial-infuse4g
>
> Build date
> Fri Apr26 16:05:35 AST 2013
>
> Build number
> cos_infuse4g-userdebug 4.2.2JDQ39
> Cng.andros11.20130426 test-keys
robertmlangdon2 said:
I run chameleon os custom rom on Samsung infuse 4g. Superuser by Clockworkmod got binded/imbedded into rom. Was working fine, then out of nowhere got disabled under superuser settings and will not change back. I select apps only and all other choices but as soon as I select it, it switches back to disable. Google play no longer shows it as an app that I have downloaded so I can't get updates. I have tried installing it again both by just downloading it and by disabling it under app management and downloading it, but both ways when I open it tries to downloading binaries and fails. Same thing happens with any other superuser I try to download. I cannot get it to work. Please help. I no longer want chameleon as my rom because of too many issues with it constantly rebooting and internet only working sometimes. i want to try another rom but can't with superuser not working.
Click to expand...
Click to collapse
You mean to say you cannot boot into CWM recovery and flash a different ROM? Interesting. I have an HTC, and the steps to rooting it are in a different order... that after unlocking the bootloader, you install CWM, and then optionally root the stock ROM with the SuperUser package (those who don't do the last step are usually flashing a ROM instead of mucking around for another second with the stock OS).
SU shouldn't be needed for custom recovery. But maybe Chameleon does something weird like not give you a custom recovery you can boot into? If that's the case, you could pop the device into download mode and go back to stock with Odin, effectively starting from scratch.
still need help, thank you.
I am starting to believe more than before that the actual problem is that somehow my phone got unrooted. How do I set my phone in download mode and use Odin? I usually wipe the cache, install the rom, install gapps, wipe cache partition, and wipe dalvik cache. I have never flashed a rom before. Or even better what is the best way to root my phone again now that I am using chameleon? I believe if I can do that it will fix my problems and I can install cyanfox (the latest rom I have downloaded). Do I use super one click? That is what I think I used before but now that I am not using stock rom I don't know what to use.
robertmlangdon2 said:
I am starting to believe more than before that the actual problem is that somehow my phone got unrooted. How do I set my phone in download mode and use Odin? I usually wipe the cache, install the rom, install gapps, wipe cache partition, and wipe dalvik cache. I have never flashed a rom before. Or even better what is the best way to root my phone again now that I am using chameleon? I believe if I can do that it will fix my problems and I can install cyanfox (the latest rom I have downloaded). Do I use super one click? That is what I think I used before but now that I am not using stock rom I don't know what to use.
Click to expand...
Click to collapse
If you are unable to get into ClockWorkMod recovery (hold Vol-Up+Vol-Dn keys while pressing Pwr button) and have it do anything (so your wipe, install, gapps, dalvik - that process would be called flashing). Then I would Odin back to stock.
For this, you would need to get into download mode. IIRC (just sold my Infuse), it is (with the device fully turned off) hold both volume buttons in while inserting the micro usb cable (that is subsequently inserted into your PC). The ODIN program comes with the download packages (hopefully), so extract the whole package, and run that.
Odin should pick up the phone in the first column as "COMX" (e.g. "COM5"). You are good to flash. To the right, there are PHONE and PDA buttons, click on each, and select the corresponding file (that was also in the package) for each (so PHONE will have something like PHONE.tgz.md5). Once both files are loaded, make sure re-partition is UN-checked, and press Start (or Go, or whatever the action word is). This will take a few minutes, but the COMX column should highlight green with "SUCCESS" in the end.
That's all there is to it. The reason why I'm shying away from SuperOneClick is that it was designed for stock gingerbread/froyo, so it has the potential of breaking something. Hope this helps.
EDIT:
Alternatively, you could try pushing su to the device with adb (depends on how you lost root):
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
adb push su /system/xbin/
adb shell chmod 06755 /system/xbin/su
... with this file (extracted).
Source (with mount point changed)
new problem
I am now running cyanfox which runs android 4.4 and Google.process.gapps has stopped keeps popping up. To get rid of it I have to do a factory reset but after a few days it always comes back. I have Googled the problem and tried numerous things to try to fix it but everything only works temporary. What should I do besides get another phone? I can't afford that right now.
robertmlangdon2 said:
I am now running cyanfox which runs android 4.4 and Google.process.gapps has stopped keeps popping up. To get rid of it I have to do a factory reset but after a few days it always comes back. I have Googled the problem and tried numerous things to try to fix it but everything only works temporary. What should I do besides get another phone? I can't afford that right now.
Click to expand...
Click to collapse
I wouldn;t suggest another phoen is things are working well genrally. The problem could lie in the GApps package or the ROM itself. I use the PA Gapps package. If you are having rouble with that one, try from a different date. Just wipe dlavik in between to prevent any nastyness.
If it still persists, try another ROM, like Carbon.
tried installing the new gapps
So far, so good but I won't know for sure for a few days. I'll keep you up to date. Thank you
what version of android is carbon?
Do you have the link for carbon rom for Samsung infuse 4g? And what version of android is it? My phone runs better with those gapps but I am still getting the same problems. I will give it a try but if carbon doesn't work I am definitely going to have to just get another phone. So far I'm. 0-2 on custom roms for this phone. I thought cyanfox would of worked cause I got it off of xda, which really makes me think this phone has some sort of hardware problem but carbon has been around longer. So maybe it will work better.
Carbon is on XDA as well too, and it is based on CM 11 / Android 4.4 Kitkat:
http://forum.xda-developers.com/showthread.php?t=2137800
Hope this works for you... :fingers-crossed:
problems solved
It appears it was definitely a problem with the ROM. Phone has been operating 100% better. :victory: My cache needs to be cleared frequently and some minor problems with the Facebook back but when isn't there problems with Facebook lol. But as soon as I clean out the cache from my apps, everything is running like new again. I greatly appreciate your help. I can't thank you enough.
Was working great then more problems
Joel,
Carbon was running great for me but then all of a sudden android.process.acore has stopped kept popping up along with all sort of other things stopping then eventually GApps not working again. I have erased my contacts, Erased Media, unchecked all my Syncs, I have tried all sorts of other Gapps packages and even another ROM (cyanogen 11) and they work to begin with then the same problems keep coming back. Is it because I went from Gingerbread right to Kitkat? My phone hasn't worked for about a week now with me trying all different ways to fix it. Do I need to install Ice Cream Sandwich then Jellybean before going to Kitkat or do I just need to try even more GApps? I used to install new ROMs all the time but android has changed so much over the last couple years and when i had to get rid of my old phone and went back to my Infuse 4g the old ROM was just completely outdated and now I can't seem to get this right. The phone itself is still a great phone and I don't understand why I am having these issues. I factory reset, wipe cache, wipe dalvik, install new ROM, install GApps, wipe cache again, and wipe dalvik again. I usually don't wipe the cache or the dalvik until after the ROM and GApps install but just lately have been doing the extra wipe just in-case because nothing else is working. But that has failed too. You have been a great help so far and I can't seem to fix this on my own, so again I turn to you for help. Please help me figure this out.
robertmlangdon2 said:
Is it because I went from Gingerbread right to Kitkat?
Click to expand...
Click to collapse
It's possible. I mentioned this before somewhere, but this could be the after-effect of a small /datadata partition, which having a separate partition is standard in a KitKat ROM (at least for this phone). When it fills up, there's no telling what happens.
Both BeanStalk and CM11 have /datadata partition alternatives (the separate partition has been abandoned) built in. You may want to try one of those:
http://forum.xda-developers.com/showpost.php?p=55574460&postcount=3801
http://forum.xda-developers.com/showpost.php?p=56604749&postcount=593
Unfortunately I couldn't find something similar for Carbon.
Thank you!!!!!!
I hate to count my chickens before they're hatched but I truly believe that was the problem. Even Facebook works now. But I thought I had it fixed before then just under a week and it completely messed up and I couldn't even get it to work for a day after that. But it works now. I can't thank you enough. If you ever come across one for Carbon ROM please let me know. This is a good ROM but I liked Carbon better. Again, thank you Joel. :good::good:
Help!!!!!!!!!!!!!!!!!!!!!!!
Sorry to bother you again Joel but I have a major problem again and I dont even know wht happenned. You have helped me through evrything so far and I couldn't be more thankful. There may be nothing you can do to help me, I don't know. I was using my phone as A Wifi Hotspot when out of know where as soon as i got on facebook on my tablet my phone rebooted on it's own into Clockworkmod recovery. when I reboot it, it goes right back into recovery, it wont read the internal sd card and it wont install any zip off any inserted sd card(it reads them but wont install anything, it always pops up with android guy on his back with a red X and a generic error). it lets me erase cache but won't erase delvik cache or format anything, the screen just flashes and it pops back a screen. I dont think the phone overheated because it wasnt hot to the touch at all. I was only using it as a wifi hotspot for about 30 minutes when it happenned. i had used it as a hotspot many times before with no problems and i dont know how it woud be a virus when i wasnt on any abnormal sites. Any help you can give me would be greatly appreciated. Thank you in advance.
Help!!!!!!!!!!!!!!!!!!!!!!!
Sorry to bother you again Joel but I have a major problem again and I dont even know wht happenned. You have helped me through everything so far and I couldn't be more thankful. The phone might be fried and there may be nothing you can do to help me, I don't know. I was using my phone as A Wifi Hotspot when out of know where as soon as i got on facebook on my tablet my phone rebooted on it's own into Clockworkmod recovery. when I reboot it, it goes right back into recovery, it wont read the internal sd card and it wont install any zip off any inserted sd card(it reads them but wont install anything, it always pops up with android guy on his back with a red X and a generic error). it lets me erase cache but won't erase delvik cache or format anything, the screen just flashes and it pops back a screen. I dont think the phone overheated because it wasnt hot to the touch at all. I was only using it as a wifi hotspot for about 30 minutes when it happenned. i had used it as a hotspot many times before with no problems and i dont know how it woud be a virus when i wasnt on any abnormal sites. Any help you can give me would be greatly appreciated. Thank you in advance.
If you can get into Download Mode, I would Odin back to stock. Are you AT&T or Rogers? There are a couple recent threads in this forum with download links, although people have been having difficulties with finding the AT&T variety.
Unfortunately, that's all I can recommend. Good luck.
we'll see how this works out
I just checked and it will go into download mode. So I guess I just need to find the AT&T thread of Oden and hopefully that works. I have never done it that way before but I read your previous response much earlier in this thread on how to do it and it sounds pretty simple so hopefully I can do it. If you can find a link to the at&t version before me it would definitely help but I will see what I can find.
robertmlangdon2 said:
I just checked and it will go into download mode. So I guess I just need to find the AT&T thread of Oden and hopefully that works. I have never done it that way before but I read your previous response much earlier in this thread on how to do it and it sounds pretty simple so hopefully I can do it. If you can find a link to the at&t version before me it would definitely help but I will see what I can find.
Click to expand...
Click to collapse
Looks like you are all set for the files then.
I just PM'ed everyone who I've recommended those packages in the past. Hopefully I get a bite.
found a thread but need your help
I found a thread with links but with what is written on this thread I am confused. The thread link is
http://forum.xda-developers.com/showthread.php?t=1613523
I'm not sure what to download and if anything needs to be changed after downloading it or if this link is a waste of my time. I was hoping you could help. Thanks.
robertmlangdon2 said:
I found a thread with links but with what is written on this thread I am confused. The thread link is
http://forum.xda-developers.com/showthread.php?t=1613523
I'm not sure what to download and if anything needs to be changed after downloading it or if this link is a waste of my time. I was hoping you could help. Thanks.
Click to expand...
Click to collapse
I would recommend Option D for what you need, but AFAIK, the links on this page are dead.
If you go to the last page though, there is a link for Option C, which would work for your needs. Hope this helps.

[Q] Flashing no longer possible: Flash successful but system does not change

Hello!
I can no longer flash anything to my GT-P5110, even factory reset has no effect. The internal storage seems to be read-only.
I think this is a longer story: About one year ago the stock firmware became incredibly slow, to the point that processes started to force close, then my user data was lost, and after factory reset the tablet went into endless boot loop.
So I decided to give CM10 a try and it worked flawlessly. The tablet was fast again. I even could upgrade to CM11 later. But around 2 month ago, only sometimes processes started to force-close or the tablet randomly rebooted itself - mostly during charging. I left it that way in the charger for some days because I had no time to bother with that issue. Then, I tried to factory reset my device only to find out that this has absolutely no effect. Installing app updates: No effect. Changing system settings: No effect. And apps start to force-close at an insane rate short after boot. The device is unusable. My could only shut down and reboot into recovery. I left the tablet lying around, turned off, out of charger, for 2 months. Now I tried to investigate:
When I "adb shell" into recovery and call dmesg, I see lots of these lines:
Code:
mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
I think something is really broken with the internal storage. I tried to flash a newer recovery but it has no effect, even when done from download mode.
Factory reset sometimes fails with an error. Reinstalling CM fails with an error. Wiping cache seemingly succeeds but I'm sure it has no effect. I tried installing SlimRom instead which seemingly succeeds, too - but after reboot I'm greeted with the CM boot logo again.
I tried to flash stock firmware with Odin. It is very very slow, runs for about 15 minutes, then fails at around 50%. Of course: That "half flashed firmware" does in no way affect the device: It still boots CM11 "without problems", then a few seconds after finishing boot (showing home screen), force-closes start to pop-up.
What should I do? I suppose the device is out of warranty for a few weeks or months, now. And even when not: It has been flashed with CM, the triangle counter is not zero. I suppose that combination of problems (read-only/failing storage, non-stock firmware) voids warranty in a way that Samsung will deny any repair. If at least I could return the device to stock firmware things would be different maybe.
Any ideas what I could try? Is it possible that the internal storage is simply fried? fsck'ing the partitions shows no errors, just the data partition is unclean with unwritten journal data but all data is readable. So the internal storage has probably not died. It just sticks to read-only mode for whatever reason.
I've found some posts with similar problems but those seem to be about older Galaxy Tab 1 devices built 2011 or before.
Just reading over this and it sounds very similar to what I'm currently facing, which is doubly annoying as no one else has chipped in a solution
I had reboot issues with my Tab2 10.1 (GT-P5110) on stock so after realizing I'd need to factory reset bite the bullet and rooted so I could use CM10.
Had occasional reboots but nothing I couldn't live with however from yesterday evening the tablet is seemingly stuck in a boot loop. It comes on, some apps fire up and an update starts. Sometimes apps force close then BOOM I get the boot splash screen.
I've tried factory reset in recovery (CWM 6.0.2.7) to no avail and wiping just about everything which also had no noticeable effect as all my settings and the rom are still the same when I get back in (albeit briefly!).
I've tried flashing new recovery via ODIN which reported a success however that also didn't appear to take. I'm beginning to think it some serious file system or storage corruption ;(
Same problem here...
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
bigg fella said:
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
Click to expand...
Click to collapse
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
hurikhan77 said:
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
Click to expand...
Click to collapse
exactly, can't even uninstall an app. It's as if it boots from a permanent back up because even deleting pictures or files isn't permanently successful. You can uninstall and delete to your hearts content, get false hope, and get crushed after it reboots and everything is unchanged
Not looking very optimistic for this I was getting a similar inkling that it's gone into a permanent RO mode as not even the wipes from recovery have an effect. I'd also tried un-installing apps as I noticed one updating and thought it was crashing it however even when it did fire up and I disabled WLAN to stop Play Store auto-updating and removed the app on the next reboot cycle the app was back:crying::crying:
I fear I may have a big white paperweight....
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Would this method be any different to the way it attempts to reformat the internal partitions when you select to format the various mounts from CWM? If so I'm more then willing to give it a go as I really have nothing to lose as the damn thing is useless atm!
shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Good call......Smart move?
help!!
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
im also having this issue with my galaxy tab2 7".. help is badly needed
Well, the proposed fix I had didn't help. Was worth a shot...
Sent from my Nexus 4 using XDA Premium HD app
hope someone finds a solution for this.
No Access to ADB
shakatu said:
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Shakatu,thanks for the PM, however, my device in ADB is unauthorised, so wont let me get into shell. Is there a way around this please?
sunnytimes said:
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
Click to expand...
Click to collapse
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
same problem please help me... :crying:
seagman said:
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
Click to expand...
Click to collapse
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
sunnytimes said:
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
Click to expand...
Click to collapse
same here too, i have same issue.. unable to flash or do anything to my phone....
Probably this is the end for our tab. As off now the tab is useless.
Sent from my GT-N7000 using XDA Free mobile app

F***ed up badly, now downloading factory rom, need help to continue

Hi guys, I just registered @ xda because it looks like it's the only serious and feedback active community available. In 10 minutes I found most of the info I was looking for, but I still want to make sure what Im planning to do is fine before I mess up again. Here's the issue:
I was fooling around with the tablet and had just rooted it so I could get rid of some bloatware, and decided to go further and install cyanogen, just for the looks. So I got this thing cm-10.1-20130411-EXPERIMENTAL-p3110-M3 from the official site, which was I put on a folder inside the tablets storage (not on the 16gb SDcard it had in it). I downloaded Rom Manager and skipped through the "search and download rom" and went for the option of looking for it inside the SD card. I had the Backup options and the wipe cache and data ON.
So I proceeded and it booted, started to do the backup and at some final point it had an error, something like "could not backup Data!". I had the options of rebooting, some other stuff and the option of installing a rom from the SD Card. I went for it and searched for the .zip inside the storage, and installed it. It did it withouth trouble, and when it finishd it prompted me to install an update, which I didn't (don't know why).
Then, I went for the reeboot option and when it started I get the normal samsung's black screen with the device's name on it, but then I get a fast glitching image that sweeps through the screen and the cyanogen startup logo which gets stuck for ever.
Click to expand...
Click to collapse
Now Im past it, I can get to download or recovery mode, so I moved onto getting the original firmware so I can clean-install again. I got it from sammobile, chose the one belonging to Chile (that's where I got the tablet), and it's 729mb of data. The tablet is a Samsung Galaxy Tab 2 7.0 P3110
If I flash it with Odin will everything be fine? All I have to do is that thing in downloadmode when I rooted it, but with that 729mb file? Should I put it in the external SD or is it more convenient to place it in the internal storage?
I appreciate your help in advance, I know this is as basic as it gets but messing up again would cost me dearly, since I have to do other stuff.
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
billysam said:
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
Click to expand...
Click to collapse
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
aguscanzani said:
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
Click to expand...
Click to collapse
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
billysam said:
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
Click to expand...
Click to collapse
You guys have helped me a lot. I've worked everything out and now i've got to reinstalling android on it, AOSP's 5.1.1 Lollipop. It's beautiful. There's just one problem: Since it came with no apps at all, I wanted to install everything on it again. Problem is, when I go to google play, it shows that i've already got my apps installed, so it wont let me download them, and it doesn't matter if I place the APK's inside the tablet as there's no manager to open them. Even if I download apk's through the tablet's own web browser, it says it can't open the file. Any ideas on this?

Categories

Resources