hey,
the past, well, almost half a year i was happy with my slim rom, but yesterday i thought, lets try something new.
a mistake obviously. i tried fresh flushing enother rom, but for some reason twrp recovery hes failed to install. then i flushed my old rom and everything was back to normal.
i googled the problem, and came to the conclusion the my version of twrp is old. the installed newer version, the 2.7, and tried flushing again.
here is the part the gone weird. the 2.7 failed to flush my rom, the i rebooted my device, and it got stuck. so i tried going back to the recovery. and from out of nowhere comes cwm. i remember installing it like a year ago. but i didnt see it since then.
ok so after this long ass story, now im stuck without rom, with cwm, witch i sort of hate, and to top it off, he cant boot ****. everything i try ends with an error. "e:can't mount /sdcard"
or
"e: cant open /cache/recovery/[email protected]
i tried like 4-5 different roms, nothing. it just says that installation is aborted.
i might add that i use adb to push files into the sd card, because the computer doesnt recognize my phone.
i really need help. :cyclops:
thanks in advance.
never mind. managed to solve this weird pickle....
thanks for listening to my heartbreaking story
Related
I lov using my phone explorer app, Everything works great except I used to be able to control my phone using my PC keyboard n mouse in the phone view.
I've upgraded my my phone to CM7 and it give an option to select My phone explorer as an external keyboard.
I cant get it working without selecting the option of external text in the appropriate input on my phone which sort of defeats the whole remote angle.
Can anyone help please ....
Bootloop solved
I read this thread trying to figure out why my phone (marvelc A510c virgin mobile) went into bootoop after trying to installing simonsense3.5 rom, and thought I'd share my success story. This is actually my first post. I want to hopefully save someone like me HOURS of heartache over a stupid solution.
Background (roughly):
Unlocked bootloader via htcdev, worked great.
Used Simonsimon34's htc utility and it worked okay. I still had to use the htc supertool to get root.
Got cwm 5.0.2.8 installed and made a backup rom
Downloaded simonsense3.5 rom and attempted to flash it, but phone hanged in recovery. After that, I was stuck in a bootloop. Could still get into recovery, but cwm would hang ALL the time doing things like wiping and I couldn't get it passed "Opening Update Package" when flashing new roms. I read forum after forum, reformatted my sd, wiped partitions, got a second sd, tried 3 or 4 roms people swore would work, did it all over again. Nothing! I found a thread that said to back cwm down to 5.0.2.6, but that didn't work. This went on for two days and I was getting desperate.
SOLUTION:
I finally found a thread (http://forum.xda-developers.com/showthread.php?t=1213229) that posted cwm 4.0.xx (the "previous version" link) and at my wits end flashed that, and wouldn't you know it, success! CWM was the problem the whole freaking time! I used the cwm partition creator to make a fresh 1024b partition on a fresh sd, wiped everything, put the rom on, and installed simonsense3.5 on the first damn try. The rom works okay, but I'm having some bugs... but that is another forum.
Good luck!
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
bobolinko said:
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
Click to expand...
Click to collapse
It seems to be an issue with the latest version of TalkBack on most roms. I had the issue already and from what I read in the forums, many other people have to. My advice, as soon as you flash a rom, uninstall or freeze talkback and DO NOT let it update to the latest version. Im not too sure what the issue is but hope Google fixes that soon.
I think also that I had a problem before when I installed the stock 4.1.2, it seemed to take my sdcard and renamed it to 0 on the sdcard. Took me a few hours to figure that out. I then copied everything that was in the folder 0 over everything in the root of the sdcard and it was back to normal.
Thanks! (Clicked it already)
I did notice a LOT of stuff was on the external card after the final recovery to the older version and had to clean up the external SD card.
You were right! I had no means to freeze the TalkBack, or do anything at all while within the OS itself, so no alternative was available to me at that time except a Factory Restore. The re-installation of my software was just going to take too long, so I did a recovery using the same version of CWM and was back where I was before the fiasco. Good thing I got it going.... Ida been really screwed! LOL. I'll try again maybe later, when I get home.
When I do try again, I'll remove the SD Card and then do the install using a spare one.
Have a great day!
Hi guys,
I had already suffered in the past for sudden reboots, but at least i was able to use the phone for a decent amount of time and fix it. After last night, though, the situation seems desperate. When i woke up i was able to turn off the alarm clock, check my email, but then hell started...
My phone is a gsm Nexus (maguro i9250), with CyanogenMod11 snapshot M5 and the appropriate google apps (at least they were appropriate about 1 month ago). I recently had some minor issue with the Google+ app, after it was updated: it kept crashing, until i uninstalled it and reinstalled after downloading from the Play Store. Should i instead search for a newer gapps packet?
Now the situation is pretty awful. The phone will reboot after at most 2 minutes. I don't really know what makes it crash so bad.
I also have two weird problems. Whatever change i manage to make before the phone reboots doesn't get persisted. For example, the alarm clock will always start activated, no matter if i managed to deactivate it before the reboot.
I'm also not able to reset it to factory defaults. I am using ClockworkMod 6.0.4.7. If i try the reset procedure, the /data and /cache partitions are formatted, but not the sdcard one. Indeed, i get the following output:
Code:
Formatting /data
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Data wipe complete
When i reboot the phone after this procedure, everything is still there, and the phone will keep doing its reboots after 1-2 minutes.
What can i do? Is there an hardware way to hard-reset the phone? Is there a program i could use?
Thanks in advance!
Fried EMMC (memory)
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Fried EMMC (memory)
Click to expand...
Click to collapse
Maybe, but if everything is still there after a reboot, sounds doubtful.
Have you tried installing a different rom? Can you connect via adb? Do you have a nandroid?
Format /system under Mounts and Storage in CWM and reflash ROM and GApps?
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
You can try by downloading a clean google factory image and then flash it using bootloader and see it helps, it could be a bad script inside. If this doesn't help then you should totally get the Nexus 5. I got GNex only recently and its still a good device I reassure you. A little tweak and a little overclock makes it as good as a stock N4 minus the bad graphics.
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
Well I got bad news well not really bad but kinda. If you wiped efs data while you were wiping your phone will never properly connect to the network anymore. That obviously won't matter unless you somehow get out of this bootloop.
Hi all, Strange thing happening to me. I was running Tweaked Rom for the longest time, then I decided to try Liquid Rom (as it does not update my bootloader), flashed as always and when it booted I had no signal, IMEI,etc. quick heart attack then decided to use my Tweaked nandroid. Which worked fine was back in action. Now when I go into recovery I get all kinds of errors saying cannot mount DATA,CACHE,DALVIK,INTERNAL. I tried updating my TWRP to the latest ... No Luck. they still wont mount and show 0mb space. Phone is still working. Anyone have any input or guidance for me.
Much Appreciated
Sorta Fixed, switched to CWM recovery and all is well, although if I go back to twrp it still shows cant mount internal sd, data,dalvik etc...
Thanks for Looking and maybe this will help others that run into this problem
rail205 said:
Hi all, Strange thing happening to me. I was running Tweaked Rom for the longest time, then I decided to try Liquid Rom (as it does not update my bootloader), flashed as always and when it booted I had no signal, IMEI,etc. quick heart attack then decided to use my Tweaked nandroid. Which worked fine was back in action. Now when I go into recovery I get all kinds of errors saying cannot mount DATA,CACHE,DALVIK,INTERNAL. I tried updating my TWRP to the latest ... No Luck. they still wont mount and show 0mb space. Phone is still working. Anyone have any input or guidance for me.
Much Appreciated
Sorta Fixed, switched to CWM recovery and all is well, although if I go back to twrp it still shows cant mount internal sd, data,dalvik etc...
Thanks for Looking and maybe this will help others that run into this problem
Click to expand...
Click to collapse
I got the same thing on my Samsung Galaxy s3.
Hey guys, i've been loving bringing new life to my s2, but i went to put the latest PA on today and it said "make sure you have the latest TWRP". So i hit up the twrp site and it listed a new 2.8.7.0 version. I did note that most threads showed the 2.8.6 rev but i figured since it was on the official site it would be safe. I booted into my current TWRP, i think it was ancient, like 2.7.x, and i loaded the img, no problem and it flashed fine. I rebooted into recovery and say the 2.7.8 at the top and thought "ok great". but when i went to install my new rom, i don't have the SD card accessible. It only shows me the main system, which is also odd because if i go to factory reset or wipe cache or anything, it tells me "no os installed". If i go to reboot it also tells me "no os installed", and i relaunched in a bunch of times and i can't get it to read my SD card to flash down or anything.
Any help / ideas would be greatly appreciated.
*i should note, it still boots into my old system, so it's still there, but sadly I can't get pas the sim card screen so i can't use the os to circumvent the above error..
no ideas eh? man i hope i'm not screwed. luckily it's a secondary device but still..
*edit. after going through a ton of things i figured out i might still be able to odin over a new recovery. So i'm messing with CWM mod now and going to see if i have better luck there. I can't belie i didn't think to just odin out after the last go, but admittedly i was pretty frustrated at the time.
update
ended up using the CM13 guide and flashing between the TWRP versions listed in the guide and getting the re-partition on the phone for larger systems. After that i was able to get all kinds of stuff going that was giving me hell before. currently (and happily) running cm13 after a brief flash to PA. Can't believe how well the community has a marshmellow based rom on this ol geezer.
I ran into the same problem too when I did my first recovery installation so basically we can't use the TWRP from the official site. The one we can use is from our forum. I used the one from Paranoid 5.1.1 or CM13. Thanks to the community, S2 is still alive.