I hope an expert on this phone can help me. Ive looked all over the net and I cant find anyone with the issue I have. I have a F3213 single sim. I rooted with no problems and have been using the phone for a while now. Well after I installed some xposed modules my phone started acting up really bad. So i went to restore the initial backup I made right after rooting. It goes through the process of restoring everything and then automatically reboots but gets to the Sony logo and thats it. Am I missing a step? When i did the backup I checked all the boxes to backup everything. Was that a mistake? Should I be doing something before I restore with TWRP? Any help would be great.y appreciated.
P.S. I let it sit for 30 minutes and still stuck at Sony logo. I also usually clear everything out when I have used TWRP for my other phones. System, data, both caches. Should I have done that here?
P.S. Should I have wiped both caches, the system and data before restoring? I know i was very limited on space before trying to restore.
Hi, Can you tell me how you rooted it? I tried almost everything and not can
Related
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
I installed avast mobile security and set everything up as a root user. I'm on the stock ROM and as soon as I was done setting everything up I rebooted and now Im' stuck in a boot loop. It does not boot loop every time... sometimes it boots up and after about a minute it reboots itself, then bootloops.
I removed avast as an administrator / rebooted / then did a clear data and uninstall. Same thing happens so I booted into amon and did a clear cache and dalvik cache.
I've also booted into Amon and wiped all caches. Still no go and I notice that I'm not getting any signal bars (yes, I remembered to put the cover back on). Any help would be greatly appreciated...
Try this.. http://forum.xda-developers.com/showthread.php?t=1394659
sent from ics land
edit: try what the person above me posted first.
Are you on the stock kernel too? I would recommend doing a full nandroid backup and an internal SD card backup and RUU from scratch if you can't get the loops to stop.
I ran avast! for a while with no issues. Could be the link above is what you need.
Thank you all, trying option #1 now. I do have a Nandroid backup I did after I first rooted, and I am on the the stock Kernel.
Holy Cow, it was set to WCDMA Preferred! I'm really surprised that avast changed that setting. I put it back to the correct setting and now my signal is back. I'm rebooting now to see if it sticks.
Thank you all a ton! I'll post back in a few and let you know if that did the trick *fingers crossed*....
Update: Been about 15 minutes and no bootloop or auto reboot so the fix seemed to have worked. Once again, thanks a ton you guys for the help, I appreciate it.
I doubt it was avast that did it. It seems to happen randomly to certain people.
Hey guys, last night my s3 ran out of battery while I was sleeping. I woke up to charge it and turn it on although it's just stuck on boot loop now. Any ideas? I don't really want to have to restore it through clockwork recovery if I can avoid it.. any ideas?
Running CyanogenMod 10
Recovery and wipe caches .
jje
Thanks for your reply. Wiping the cache hasn't seemed to have done anything, any more suggestions?
well, try formatting system and reflashing
Thank you, just need to re root, re flash and restore from backup now.
I'm having a similar issue. Last night my S3 ran out of battery and it went off. I tried to power it on again, and it started to show the boot logo. But it went off again because there was no battery. I changed the battery and now I have a bootloop. I made a backup, and then I started trying solutions. The only one that works is wiping data/factory reset. And then, if I restore ONLY the data partition from the backup the boot loop comes back. So whatever it is, is on the data partition. But how to diagnose it or solve it? I don't wanna lose my apps or their configuration!!
Any help??
eXtremeDevil said:
I'm having a similar issue. Last night my S3 ran out of battery and it went off. I tried to power it on again, and it started to show the boot logo. But it went off again because there was no battery. I changed the battery and now I have a bootloop. I made a backup, and then I started trying solutions. The only one that works is wiping data/factory reset. And then, if I restore ONLY the data partition from the backup the boot loop comes back. So whatever it is, is on the data partition. But how to diagnose it or solve it? I don't wanna lose my apps or their configuration!!
Any help??
Click to expand...
Click to collapse
Well done for searching but this thread is from last year so a better option would of been to start a new one and linked to this one in your post saying what you have done.
If the phone turns off do to a empty battery there's a chance it can corrupt files. This is what this sounds like, no option to clean install.
Thanks for the info, I ended up using a backup.
So I have had Cyangenmod 10 installed for several months now and it's been working fine until I would say the last 2 weeks. Now, sometimes it will lock up or slow down and when I restart it, it will get stuck on the cyangenmod logo and never fully boot. After several restarts, I can sometimes get in and all is fine. But today, I have rebooted the Nook Tablet about 10 times now and the Cyangenmod logo will spin for a bit, then stop and then spin and then stop, etc but I can never get in
Ideally, I don't want to restore as I have a number of things on the Tablet that I want to keep. Any suggestions before going that route?
Try going into recovery and wiping cache and dalvik-cache, and then reboot. When oddball things happen, this should be your first trouble shooting step.
Good luck
Sent with my Dinc4G
tried the wipes and still gets stuck on the cyangenmod logo..just spins and stops for a bit, then spins some more
any other ideas
Titanium backup the apps/data you want to keep then full wipe - data/factory reset.
Sent with my Dinc4G
can't do titanium backup if I cant even get passed the cyangenmod logo
Ya good point.
You may have to reflash the rom (or another rom) after a full wipe. I know you are trying to avoid this, but you may not have a choice. You should, however be able to restore your data through advance restore in recovery (make sure you do a backup first though). And it is possible something you put on your nt is causing this - not likely but possible.
Had you done any mods or such on you nt prior to this?
Edit - Another thought too, try flashing the latest update of cm10.1, Just wipe cache and dalvik cache. Flash over the top your current build.
Good luck
Sent with my Dinc4G
I'm on Lollipop and the ROM I'm using is the unbloated ROM (http://forum.xda-developers.com/showthread.php?p=67340331#post67340331).
My phone died, I got back in my hotel room and currently charging my phone. I turned it on and it's stuck on the LG logo. I've let it sit for an hour and still never fully booted.
Can anyone tell me what I can do? I can get into TWRP and all that.
Restore your latest backup
Double0EK said:
Restore your latest backup
Click to expand...
Click to collapse
Don't have one. Do I need an sdcard for creating backups?
Also, I ended up doing a factory reset, it kept the ROM. Reinstalled all my apps, the phone died again and it got stuck on the LG boot logo again.
Just did another factory reset.
Trying to narrow it down to what is causing it. I doubt updated apps are causing it?