Long story short I flashed the Root.zip that was posted in the development section without first flashing TDJ Cache wipe. Was getting the reboot hang error so I restored to the backup I made when I flashed CWM after the ICS update. I flashed the TDJ full wipe zip found here http://forum.xda-developers.com/showthread.php?t=1623430 then restored then flashed the cache wipe zip then rebooted. Let android do its thing for a bit then rebooted to CWM and followed instructions to the T this time.....However. Busybox was a little wonkey on update and now even though I have root permissions I no longer have RW access to /system. Any thoughts as I would prefer to avoid ODINing back to stock. I have run fix permissions in both Rom Manager (it hangs and does nothing) and in CWM.
What exactly do you mean "Busybox was a little wonky?"
At first it wouldn't install at all. I assumed it was due to clean and clear symlink options were not checked. After I rebooted it seemed to work fine as in it installed without error. Though now as stated in my previous post I have lost RW
Related
My phone is just rebooting to the Fresh boot animation over and over again. Here is what I've done.
I did a full wipe (3 times), cleared storage in recovery, wiped dalvik cache, pulled the battery, fastboot, wipe cache partition, wipe data/factory reset in recovery and nothing works. I'm using Clockwork Recovery v2.5.0.1 and I rooted via this method for mac:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac.html
I'm pretty sure half the **** I did was not necessary but I had to try something. Any ideas on what to do next?
Usually clearing cache/dalvik works... And you've wiped everything else... Have you checked the MD5 of your ZIP that you're flashing from? Or tried a different ROM?
Furthermore, have you just let the phone sit for a bit? The first boot after wiping cache can take quite a while.
EDIT: Also, did you do NAND unlock/eng hboot when you rooted?
I never did a nand backup. What would happen if I nand backup while having these problems? How do I check MD5?
I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.
Well doing a Nandroid backup of a broken ROM won't do you any good.
As for MD5, you should be able to open adb shell, then use the "md5sum" command to get the MD5 of the file. For example:
Code:
adb shell
md5sum /sdcard/some_rom.zip
You can then compare the MD5 it outputs with the MD5 posted by the ROM maker. If they haven't posted an MD5, you might want to re-think about using that ROM, and the competence of its creator. For example, CM6 Nightly has the MD5 posted in a text file in the same directory as all the ROM zip files for flashing. Amon RA Recovery has the MD5 posted in the OP of the thread, etc.
Philosuffer said:
I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.
Click to expand...
Click to collapse
What I'm trying to do is get my phone to work again. Here's what happened:
I downloaded this Rosie Clear Taskbar zip file that I found in the Themes section and flashed it. It looked horrible and was showing distorted so I figured I'll just reset my whole phone and get rid of it. Well it didn't work and it put me in a boot loop. I have no idea how to do a logcat and I'm pretty much new at this unless you post instructions I can adb with my mac. I need my phone today because it's my daughters birthday and people are going to be calling me left and right for details on the party. My phone just keeps rebooting at the Fresh boot. I can enter recovery just fine:
Is there a command I can do in adb while in recovery to make it ''safe boot''? How do I flash Fresh again?
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.
It's that easy
gqstatus0685 said:
...
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.
Click to expand...
Click to collapse
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.
Jim M said:
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.
Click to expand...
Click to collapse
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.
Apparently in my case it isn't as easy as flashing from the zip. I downloaded the ROM from geekme and put it on my SD card. Flashed it and even though it was successful I still get boot loop. Could it be because I accidentally did a nand backup of the problem?
What else could I do. I'm using Clockwork but is there a way to flash the other recovery through ADB even though my phone won't boot.
I can't take this to Sprint as it's rooted and showing the Fresh boot screen.
I had the same problem. Turns out I had the wrong kernel flashed from a previous rom. I had constant reboots, couldnt access my sd card, and the usb quit working. I had to ship it back to Asurion. Just got my new one back.
Bottom line:
MAKE SURE YOU HAVE THE RIGHT KERNEL BEFORE YOU FLASH A NEW ROM!!
SD Card
Do you have another memory card that you could use? Try putting a copy of a rooted stock ROM on it and try to install that.
http://forum.xda-developers.com/showthread.php?t=743352
As others have mentioned clockwork does not always work well with Fresh, try Amon RA's recovery
TheBiles said:
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.
Click to expand...
Click to collapse
The dalvik cache is under /data but the android cache has it's own partition.
Hi everybody.
I have an Xperia S (LT26i) with stock 4.0.4 (.50) on locked bootloader. I'm using THIS recovery, and I can't mount /cache. That means I can't flash ROMs, restore backups, I can't actually do anything apart from flashing .zips.
I'm reading through that thread and there seems to be no solution yet. Still, I need a recovery for stock ICS with locked bootloader. But I can't really find a working one. I tried installing the one with RecoverX, but nothing changed. Do you suggest to reflash the phone and then install the recovery with RecoverX? Or is there another way to replace this recovery with a working one?
Please, I've been searching for hours... -___-
UPDATE
Solved. Updated to .55 firmware using SUS and wiping everything, rooted with chinese eRoot, flashed recovery using RecoverX (had to do it twice, the first time recovery.tar was not installed properly in /system/bin). Now it works fine. Don't know what the problem was, though. Hope this can help someone with the same problem.
RE-UPDATE
I created a backup, it worked perfectly. Ten minutes later I rebooted and tried to wipe cache. Same errors again. Tried to restore the previous backup (I knew it would have created problems, but... ) and obviously I'm stuck on Sony logo. Couldn't format /system.
I'm reflashing -__-
Could it be a problem with the sdcard?
Guess what? UPDATE
Reflashed, re-rooted, re-installed recovery with RecoverX. The recovery successfully mounts/unmounts all partitions, and can format /cache.
BUT.
After 10 minutes (during which I kept trying mount/unmount, rebooted several times, both directly into recovery and into the OS) it just stopped working. I tried formatting /cache once again, and it gives me an error. Anyway now I'm still able to mount /cache. Just, I can't format it.
AND.
While I was writing, I tried to format /cache again. Now it can't even mount the partition. This doesn't really make sense to me.
I have a T-Mobile SGH-T989 (Galaxy S2), and for a while I had an ICS darkside ROM on it with CWM 5.0.2.4. This evening, though, I decided to upgrade to an Android KitKat ROM (Beanstalk). I first upgraded CWM to the latest version, and then flashed the ROM. Everything seems to have flashed correctly, and I get the Beanstalk splashscreen, but it never seems to go any further than that. It's hung (for around 30mins) on the Beanstalk splash screen with the beanstalk and rain.
When I go into CWM, I can re-flash just fine, but when I try to do a full wipe or a cache wipe, it also gets hung (I eventually rebooted after about a 10 minute cache wipe attempt). It says that it can't open /cache/recovery/last_install, and that the cache file system is read-only. I also attempted to use the super wipe/cache wipe tools here: http://forum.xda-developers.com/showthread.php?t=2235141&nocache=1 but they also hung.
I'm wondering what the best course of action is at this point? I have a full backup, but since it was made with the previous version of CWM, it also appears to not be working.
Thanks,
~j
jwir3 said:
I have a T-Mobile SGH-T989 (Galaxy S2), and for a while I had an ICS darkside ROM on it with CWM 5.0.2.4. This evening, though, I decided to upgrade to an Android KitKat ROM (Beanstalk). I first upgraded CWM to the latest version, and then flashed the ROM. Everything seems to have flashed correctly, and I get the Beanstalk splashscreen, but it never seems to go any further than that. It's hung (for around 30mins) on the Beanstalk splash screen with the beanstalk and rain.
When I go into CWM, I can re-flash just fine, but when I try to do a full wipe or a cache wipe, it also gets hung (I eventually rebooted after about a 10 minute cache wipe attempt). It says that it can't open /cache/recovery/last_install, and that the cache file system is read-only. I also attempted to use the super wipe/cache wipe tools here: http://forum.xda-developers.com/showthread.php?t=2235141&nocache=1 but they also hung.
I'm wondering what the best course of action is at this point? I have a full backup, but since it was made with the previous version of CWM, it also appears to not be working.
Thanks,
~j
Click to expand...
Click to collapse
When all fails always use ODIN, if you know what you're doing. IDK which ROMs here are flashable via ODIN but use any you can find in the dev section in which somebody has uploaded a flashable .tar version (usually it will be rooted stock). If that doesn't save you, you have big trouble.
Also you should still be able to restore backups between different CWM versions, so yeah there is potentially something wrong with your phone.
I'll post my issue in hopes that it helps anyone who has the same problem:
I was going for a clean install of radeonmaya's kitkat since i dirty flashed from JB 4.1.2. and am getting massive drain from wifi. I had CWM from shabbypenguin which i used to flash everything and was working really well. Anyway, i did my backup and was rebooting to backup my stuff from the internal storage when suddenly i got a message in CWM to fix SU. I said yes and the phone rebooted to CWM. Tried not fixing and same result, booted back to cwm. Tried formatting system, cache, data and reflashing everything(including SU update) and still rebooted to cwm. I was pretty frustrated by now so i decided to reflash my backup, rebooted and...still on CWM. Lucky for me i had the hacked TWRP so i flashed that, rebooted and was prompted to fix root, which i did. my phone rebooted and i'm back on the rom(charging my battery since it dropped from 79 to 61% in all that flashing).
Hello,
My galaxy nexus suddenly crashed yesterday. I don't know what happened, I only know that I had the xPrivacy installer and "App Ops". It's a rooted phone with TWRP recovery v2.8.6.0 and CyanogenMod 10.2. The only problem I had so far was WhatsApp not displaying any chats and had to restore my chats. I do suspect these two are linked to each other
When I try to boot it normally, it crashes after a couple seconds and gets stuck booting and crashing again until I take out the battery.
After fiddling around for a while, all the errors pointed at the data partition, but it seems like I just can't write anything to the internal SD.
What I've tried to fix it is (not necessarily in this order):
Wiped (Dalvik)Cache
Factory reset via TWRP
Restore a recent nandroid backup via TWRP (this says it failed)
Restore a nandroid backup that I made after a factory reset via TWRP (this says it failed)
Restore a nandroid backup via Nexus Root Toolkit
Create a backup (just to test if I could write, it said it succeeded but after a reboot there was no backup)
Wipe data partition TWRP
Used "fix permissions" on TWRP
Formatting SD via TWRP
Wiped all partitions via TWRP
"Flash Stock + Unroot" on Nexus Root Toolkit (Soft-Bricked/Bootloop mode)
Flashed CM10.2 via TWRP
Flashed CM10.2 via Nexus Rootkit
Flashed stock ROM via ADB
Deleted all data via Windows Explorer
Hard Factory reset via ADB
Everything says it was successful, except when restoring a backup via TWRP and a single time I tried wiping the Data partition. I once got an error message saying a file was opened too many times, but I think that is just because it couldn't read the file.
Besides unlocking, rooting and flashing CM, I haven't done much software wise. I have done some handiwork hardware wise, because when I got this phone from a friend, the pins for reading the SIM card were broken off. This was a couple months ago and I don't think I broke anything.
I hope that I have been clear enough explaining my problem, I sadly cannot give a logcat file.
Thank you in advance
I'm having your issue too. I wrote here some days ago, here it is my post http://forum.xda-developers.com/galaxy-nexus/help/unable-to-reset-strange-behavior-t3116856.
Hope we will find a solution!
Same issue for me.
I tried also with odin and it dosen't work.
I have Cyanogenmod 11 and clockworkmod recovery.
and same thing here, try to install CWM from flashify app... see if you can wipe and install roms with that... i know that CWM is outdated, but most of the times it still gets the job done...
This is so weird. 2 days ago the same thing happened to me, my phone is stuck in a boot loop, and I can't bring it back to stock, since I can't wipe or flash. This is so frustrating.