Hi all,
I have a Xoom, running one of the nightlies from Team EOS (#34) and it was running fine until it started to get a lot of force closes. I figured thats fine ... I'm running a nightly, but then I started noticing that when I delete or install apps, then do a reboot, the apps are either not there (if I'd done an install) or still there (if I'd removed).
So then I figured, oh well, high time I got up to the latest nightly or even the stable build, and tried that, but low and behold after flashing the stable version of the Team EOS rom, when I booted back into the OS it was still the nightly #34.
So I tried restoring to the stock Motorola rom via fastboot, same result: booted into the OS on nightly #34. I tried a simple factory reset but when I boot back in all my data is still there.
So this is what I've tried:
- install Team EOS 1.0.0 stable build via CWM
- install Motorola stock rom via fastboot
- wipe data and cache via fastboot
- wipe data and cache via CWM
- factory reset via OS
... all with the same result - it just boots back into the OS with apps still there that I've deleted many times, and apps not there that I've installed many times. One slight point of note is that when I do the factory reset via OS, for some reason it boots into recovery, rather than back into the OS ... not sure if this is significant
Please help? I've searched around and people have mentioned this problem, but the threads always end without an answer
you could try to unlock your xoom again (even if it is not locked!), that should wipe your /data partition. As to why it doesn't through fastboot (assuming you used fastboot erase userdata), no clue... Also, if you're flashing something through fastboot and you don't get an error message and it still didn't work, that sounds like serious trouble...:-\
Thanks for your reply.
I'll try that out (the unlock) and I'll give fastboot another go with that command. I may have used fastboot -w on one occasion, and:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
on another.
I was wondering if I can do anything tricky with mounting/unmounting in CWM, but thats an area I have little of my own knowledge. Any thoughts?
I tried both of those suggestions, with no luck. And no error messages either.
Please continue to help .. I appreciate it!
Must say ive got the same problem - getting spurious erros after updating to the final build (3.0) - even after a hard reset and then going through the startup stuff i still end up with my desktop wallpaper from before....although i must confess i havent done the command line stuff yet...
Sorry buddy, but the bad news is that i put mine in for repair, and they were unable to fix it. They said that some aspect of the hardware had been fried and would need an expensive replacement, which would not be worth the cost. One of the risks of custom ROMs .....
Related
Hi to all (especially the EOS guys top roms as always)
Since ive flashed the final EOS 3.0 release ive been having stability problems. Lost count of how much stuff ive tried with regards to reflashing etc etc.
1. after countless reflashing of the eos software and wiping caches etc etc i went to return to stock.
2. After reflashing back to stock i relocked the bootloader which formatted the tablet and then booted but failed with SOS 0x0002 or something like that....
3. Did a fastboot unlock which again reformatted the drive and then when i went back into recovery the TEAM eos CWM was still in there (the latest rc3 - the touchscreen build with the blue logo.
4. Reflashed eos 3.0 (downloaded again from the web just incase) and im back where i started but in all of this somewhere somehow my tablet shows as an MZ602 not a 601 (602 i believe is the 4g US tablet) - i think this has something to do with the CWM software as when i did the fastboot unlock the eos recovery was still in there.
So im back on eos 3.0 side effects are in play some packages wont install with errors - its a bit jittery - email keeps hanging - lots of little things
Anyone else had this??
Cheers a bunch to anyone that can help.
Comfy
Start over and do this..
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
ok - i take it i do this with the stock from from motorola (which ive got - yes??)
im guessing youre going to say yes so im doing it now.....almost done - its so long ago i must confess ive forgotten how to root it!!
ok - im there - back on stock honeycomb.....blast from the past....
yup - i think im there....all reflashed and back on as an MZ601 - just for anyone else who's reading this (i hope this helps)....
1. Did as Tumpy said (i did this earlier) but i must have missed something as i followed what tumpy said and it all reflashed and booted fine. (this part you need to go to motorola and download their stock image to carry out those commands and have adb/fastboot installed and running.
2. Found a tool (or collection of tools called "LAIOT") a bunch of rooting tools with CWM in there as well.
3. Followed through that - very easy and then reflashed the eos build. Back as an mz601 - i know its working properly now as the market it auto downloading my apps.
Cheers - thanks very much.
It's probably due to you flashing in the wrong ROM. Hence you got the wrong radio flash or something along those lines.
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?
Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.
You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium
Hi everyone, i've got my OPO when CM12 still wasn't a thing, and it always did his job wonderfully, i've updated to CM12 when it first came out, then updated it every time a new stable version was out, YNG1TAS2I3 version included (with root access and TWRP). A few days ago, while i was listening to some music with Google Play Music, the phone started to reboot itself for no apparent reason, and after around 10 reboots with random timings, i found out there was a problem with google play services, so i blocked them with Titanium Backup, deleted updates, updated them again, reactivated, and everything went fine.
Yesterday, my phone once again rebooted by itself, but every time it was rebooting, while showing the boot logo, it rebooted again without actually loading android. I first tried to wipe cache, then dalvik cache, then data and system partitions, factory reset, but it kept rebooting no matter what, until i tried to flash CM11S on it. After a few tries and total wipes, CM11S was running with no reboots, and it worked flawlessly, no root, no custom recovery, everything stock flashed from official fastboot images zip.
After that, i tried to update via OTA to the more recent versions of CM11S, no problems so far, but as soon as i updated to CM12 via OTA once again, the phone started to reboot itself after the update, it says "Upgrading Android" like when you wipe the dalvik-cache, and then it freezes for a second, then reboots.
Things i've tried so far:
full wipe and factory reset from TWRP
erase and flash again all partitions
erase and flash again persist partition
flash colorOS and then flash CM12
After flashing the persist partition it managed to work for a minute on CM12, but then it started rebooting itself again, and i've managed to save the last part of logat log , but i'm not sure if it's worth anything to find out the problem! (i can't post it on forum because of the new user link restriction, but if you want to have a look at it, let me know)
So, basically, my phone works only on android 4.x and not on 5.x, I would think some app on it can make it crash, but even after a full wipe it still behaves like this, what could be the reason and how can i try to fix it? thanks in advice!
I recommend you to flash fastboot images of CMOS12 without skipping any file
Steps to flash >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
xKylesx said:
Hi everyone, i've got my OPO when CM12 still wasn't a thing, and it always did his job wonderfully, i've updated to CM12 when it first came out, then updated it every time a new stable version was out, YNG1TAS2I3 version included (with root access and TWRP). A few days ago, while i was listening to some music with Google Play Music, the phone started to reboot itself for no apparent reason, and after around 10 reboots with random timings, i found out there was a problem with google play services, so i blocked them with Titanium Backup, deleted updates, updated them again, reactivated, and everything went fine.
Yesterday, my phone once again rebooted by itself, but every time it was rebooting, while showing the boot logo, it rebooted again without actually loading android. I first tried to wipe cache, then dalvik cache, then data and system partitions, factory reset, but it kept rebooting no matter what, until i tried to flash CM11S on it. After a few tries and total wipes, CM11S was running with no reboots, and it worked flawlessly, no root, no custom recovery, everything stock flashed from official fastboot images zip.
After that, i tried to update via OTA to the more recent versions of CM11S, no problems so far, but as soon as i updated to CM12 via OTA once again, the phone started to reboot itself after the update, it says "Upgrading Android" like when you wipe the dalvik-cache, and then it freezes for a second, then reboots.
Things i've tried so far:
full wipe and factory reset from TWRP
erase and flash again all partitions
erase and flash again persist partition
flash colorOS and then flash CM12
After flashing the persist partition it managed to work for a minute on CM12, but then it started rebooting itself again, and i've managed to save the last part of logat log , but i'm not sure if it's worth anything to find out the problem! (i can't post it on forum because of the new user link restriction, but if you want to have a look at it, let me know)
So, basically, my phone works only on android 4.x and not on 5.x, I would think some app on it can make it crash, but even after a full wipe it still behaves like this, what could be the reason and how can i try to fix it? thanks in advice!
Click to expand...
Click to collapse
1)Are u tried cm 12.1
after u flashing cm 12 then reboot and again go back to recovery and flash cm 12.1
2) try to use different kernels supporting to cm 12 like boeffla /AK etc
3) try to flash cm 12 firmware via fastboot flash installation process
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please could you help me with resurrecting my phone? I would be happy to clarify and elaborate upon any point of information.
Kind regards,
Sami
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
audit13 said:
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
Click to expand...
Click to collapse
I actually have tried to flash stock Android ROMs, from KitKat to Marshmallow, however, this didn't work as there was a 'write failure' and CyanogenMod wasn't removed. I did erase the cache, but to no luck.
Sounds like the memory module on the phone is defective. I had a Nexus 5 that would constantly re-lock the bootloader after I reboot. I had another N5 where the bootloader remains unlocked and a full wipe in recovery would finish in about 3 seconds which is far too short.
I could only solve both problems by replacing the motherboard.
Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!
You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links
audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!
Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.
It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.
The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.
Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.
Could be an emmc problem which would require a motherboard swap.
Is that likely to happen when the previous owner said it was fine before they tried to root?