Related
The Situation:
I a currently stuck in ClockworkMod Recovery with no backups, no usable flashable ROMs, no ROM installed, a screwed up internal SD, and virtually no way to use the ADB or ODIN in Download, because my phone rarely, if ever, recognizes USB cords for anything but charging (This is a hardware, not software issue. It persists from ROM to ROM.)
Thoughts?
Additional Info
There's a lot, so I will be clear, as concise as possible, and will try to remember everything.
You might ask, "How did this happen?" or even "WTF?"
These are the steps I've taken:
Originally, I used OCLF for rooting + ext2 lag fix, followed by Team Whiskey's latest Bionix ROM. I hadn't removed the lag fix as I was told it should not matter. I was having a multitude of problems, so I wished to revert to Stock. When a standard nandroid restore didn't work, I searched and learned that flashing back to J12 should let my nandroid restore work. This did NOT work, however, and, once again, I was stuck in the boot sequence. I re-flashed the Bionix ROM to see if I could just live with it, and, no, I couldn't. I looked some more and found that, given I could flash a JFD or J16 (I believe) image, I could then perform a restore, then install a 2.1 kernel. I found the image and flashed it. THAT worked, but the nandroid was still refusing to cooperate.
Today, I flashed Team Whiskey's Obsidian V4.2 ULF Kernel ROM, succeeded, and found that my internal SD partition that hosts apps existed, but was 0.00KB. I thought about installing App2SD, but I decided I had too much room internally to want to deal with that. I tried to add a partition via CWM ROM Manager, but did not take into consideration the fact that it would need a ROM to flash once it had wiped and partitioned. I'm not sure how that partition creator is supposed to work, because it wipes the drive that the ROM is on. At that point, I somehow managed to get back in business by formatting w/ backup.
I tried flashing Obsidian V4.2 w/o the lag fixed kernel, thinking this was the issue with my internal partition system, but I never found out because install, post-wipe, failed at line 11. I could not turn the phone back on because it had no complete install, and nandroid was still not restoring, so I went through Recovery and factory reset, wiped cache, tried mounting and unmounting different file systems, including the sd-ext which refuses to mount, citing "E:INFO is WRONG Error mounting SDEXT:!".
I've installed Superuser, messed with the Lagfix and Tweak options, and reset default permissions in the ULF Kernel Menu. All to the effect of allowing the ROM flash to progress to line 85 before failing. I can't remember the errors it gave, and can't flash again, because, in my frenzy, I formatted the system, data, cache, and sdcard. I still have a nandroid available, but it has an md5 sum mismatch. There are three more viable ROMs on my external SD card, but I have no way of moving them to the internal, and the "install zip from sd card" menu won't access the CWM backup folder or the external because it says there aren't any there, which isn't true.
I am completely at a loss as to what to do. Is there any way to move files from external -> internal sd in recovery?
ANY help that isn't "You're screwed" would be appreciated.
Semi_Interested said:
The Situation:
I a currently stuck in ClockworkMod Recovery with no backups, no usable flashable ROMs, no ROM installed, a screwed up internal SD, and virtually no way to use the ADB or ODIN in Download, because my phone rarely, if ever, recognizes USB cords for anything but charging (This is a hardware, not software issue. It persists from ROM to ROM.)
Thoughts?
Click to expand...
Click to collapse
Email me [email protected]
Sent from my SGH-T959 using XDA App
Semi_Interested said:
There's a lot, so I will be clear, as concise as possible, and will try to remember everything.
You might ask, "How did this happen?" or even "WTF?"
These are the steps I've taken:
Originally, I used OCLF for rooting + ext2 lag fix, followed by Team Whiskey's latest Bionix ROM. I hadn't removed the lag fix as I was told it should not matter. I was having a multitude of problems, so I wished to revert to Stock. When a standard nandroid restore didn't work, I searched and learned that flashing back to J12 should let my nandroid restore work. This did NOT work, however, and, once again, I was stuck in the boot sequence. I re-flashed the Bionix ROM to see if I could just live with it, and, no, I couldn't. I looked some more and found that, given I could flash a JFD or J16 (I believe) image, I could then perform a restore, then install a 2.1 kernel. I found the image and flashed it. THAT worked, but the nandroid was still refusing to cooperate.
Today, I flashed Team Whiskey's Obsidian V4.2 ULF Kernel ROM, succeeded, and found that my internal SD partition that hosts apps existed, but was 0.00KB. I thought about installing App2SD, but I decided I had too much room internally to want to deal with that. I tried to add a partition via CWM ROM Manager, but did not take into consideration the fact that it would need a ROM to flash once it had wiped and partitioned. I'm not sure how that partition creator is supposed to work, because it wipes the drive that the ROM is on. At that point, I somehow managed to get back in business by formatting w/ backup.
I tried flashing Obsidian V4.2 w/o the lag fixed kernel, thinking this was the issue with my internal partition system, but I never found out because install, post-wipe, failed at line 11. I could not turn the phone back on because it had no complete install, and nandroid was still not restoring, so I went through Recovery and factory reset, wiped cache, tried mounting and unmounting different file systems, including the sd-ext which refuses to mount, citing "E:INFO is WRONG Error mounting SDEXT:!".
I've installed Superuser, messed with the Lagfix and Tweak options, and reset default permissions in the ULF Kernel Menu. All to the effect of allowing the ROM flash to progress to line 85 before failing. I can't remember the errors it gave, and can't flash again, because, in my frenzy, I formatted the system, data, cache, and sdcard. I still have a nandroid available, but it has an md5 sum mismatch. There are three more viable ROMs on my external SD card, but I have no way of moving them to the internal, and the "install zip from sd card" menu won't access the CWM backup folder or the external because it says there aren't any there, which isn't true.
I am completely at a loss as to what to do. Is there any way to move files from external -> internal sd in recovery?
ANY help that isn't "You're screwed" would be appreciated.
Click to expand...
Click to collapse
Well, adb would be able to move files from external sd card to the internal one but if you don't know how to use it then Odin might be simpler. I'll pm you some instructions but if you cannot get your phone to be recognized in Odin because of USB issues then I'm not sure how to help.
So I flashed the latest nightly 9-2-02 and I kept on getting the error in my camera app external device storage needed. I figured the problem was not with my sdcard, but with my internal sdcard folder. When I go to flash via recovery, it says e:/unable to mount internal sd card. Is there anyway to remount this card?
I have Hboot 1.15, s-on. I know some other people have been having this problem, anybody have any ideas?
midfieldmaestro said:
So I flashed the latest nightly 9-2-02 and I kept on getting the error in my camera app external device storage needed. I figured the problem was not with my sdcard, but with my internal sdcard folder. When I go to flash via recovery, it says e:/unable to mount internal sd card. Is there anyway to remount this card?
I have Hboot 1.15, s-on. I know some other people have been having this problem, anybody have any ideas?
Click to expand...
Click to collapse
it may some how have gotten corrupted. update twrp to the latest if you dont have it (2.2.2) and then boot into recovery and do a back up, go to advanced and install htc dumlock and reboot, i dont personally like dumlock but it is the most flexible solution barring a few extra steps, go into apps and launch dumlock, here it will write recovery to boot and then reboot directly into twrp because you technically no longer have a boot, it has been replaced by twrp, then go to advanced again and restore boot and go back to menu, go to wipe select internal, this will reformat it, then do the usual factory reset, wipe cache, dalvik, system and then flash cm10, gapps, and reboot, if all goes well you can go ahead and flash any extras you might have had prior
note: with dumlock there is no need to fastboot the kernel, with dumlock in boot it can write directly, the reason this method isnt the most ideal is that you are writing to boot multiple times but like i said i think it is the most flexible for newer users
om4 said:
it may some how have gotten corrupted. update twrp to the latest if you dont have it (2.2.2) and then boot into recovery and do a back up, go to advanced and install htc dumlock and reboot, i dont personally like dumlock but it is the most flexible solution barring a few extra steps, go into apps and launch dumlock, here it will write recovery to boot and then reboot directly into twrp because you technically no longer have a boot, it has been replaced by twrp, then go to advanced again and restore boot and go back to menu, go to wipe select internal, this will reformat it, then do the usual factory reset, wipe cache, dalvik, system and then flash cm10, gapps, and reboot, if all goes well you can go ahead and flash any extras you might have had prior
Click to expand...
Click to collapse
Thank you for this explanation, but I believe (thanks to a user from the CM10 thread) that it is indeed corrupted like you said. But instead of going through that, I went and mounted my internal drive via TWRP to my computer. So I have a macosx (ugh) and I reformatted it, but it had trouble doing it and it didn't work properly. Normally in windows it would do a much better job as you are able to set it FAT32 etc etc. So when my phone started up, the phone recognized it was a corrupted drive and repaired it itself, and voila, everything is working, I am able to side load apps and actually download things.
well i wrote those directions to give you the best chance at getting it to work, I always prefer a fresh start when possible. my instruction is also non reliant on a computer which to me is also a plus as windows/mac/and linux can interfere with usb. Glad to hear you got it working
Formatting work
I would like to thank everyone who posted, I rebooted my EVO to TWRP recovery, mounted the USB drive and connected to my windows PC. The USB drive popped up and windows asked if I wanted to fix it, I said yes and formatted as fat32 adn after unmounting and rebooting, the sdcard mounted perfectly!
Thanks you!
g_brownell said:
I would like to thank everyone who posted, I rebooted my EVO to TWRP recovery, mounted the USB drive and connected to my windows PC. The USB drive popped up and windows asked if I wanted to fix it, I said yes and formatted as fat32 adn after unmounting and rebooting, the sdcard mounted perfectly!
Thanks you!
Click to expand...
Click to collapse
So you got the internal to work.
Have you had any issues with mounting the external?
I'm having some trouble right now.. I rooted my phone, I put Hellybean onto my microsd card. I booted to android system recovery > reinstall packages, and then i deleted cache, formatted system, deleted the other cache etc.
I tried to find the hellybean zip on my microsd card but it was no where to be found.. So I rebooted my phone and now I have no OS, and when I boot into recovery and go to reinstall packages to try and get back to clockwork mod recovery menu it's not there either (assuming I'm missing the files to go there now).
What can I do guys? Do I need to get 2.3 back on here again and redo everything.. when I get back to where I'm going to flash the hellybean rom how do I find the file on my sd card? I went to SD folder and it wasn't there but I checked my sd card and it is there on the computer.
The ROM zip needs to be on your internal storage.
Mount on your PC, if your internal storage shows move ROM there with update.zip for Clockwork Mod.
Reinstall packages and once in cwm you'll be able to install HB from the zip.
If you can't see internal storage I'd Odin back to stock and then try again.
Toast6977 said:
The ROM zip needs to be on your internal storage.
Click to expand...
Click to collapse
Yeah I've come to realize this
Toast6977 said:
The ROM zip needs to be on your internal storage.
Mount on your PC, if your internal storage shows move ROM there with update.zip for Clockwork Mod.
Reinstall packages and once in cwm you'll be able to install HB from the zip.
If you can't see internal storage I'd Odin back to stock and then try again.
Click to expand...
Click to collapse
Sorry I didn't understand what you meant in the beginning. Mount on your pc? Explain a little?
If that doesn't work how do I use Odin to flash back to stock, what do I need to do, i don't need a full detailed guide but just what files and what buttons to press on odin.
There are lots of very detailed Odin guides. Look around. I wasn't real clear at first if you could get in CWM recovery. If you could, then you could Mount Storage and your PC would have seen the internal storage, thus allowing you to put the ROM.zip on it..
Look in the stickies for Odin guide. They are easy to follow. I'd tell you how to do it, but if you read it yourself you'll understand what your doing, and it will help you in the long run.
blasteryui said:
I'm having some trouble right now.. I rooted my phone, I put Hellybean onto my microsd card. I booted to android system recovery > reinstall packages, and then i deleted cache, formatted system, deleted the other cache etc.
I tried to find the hellybean zip on my microsd card but it was no where to be found.. So I rebooted my phone and now I have no OS, and when I boot into recovery and go to reinstall packages to try and get back to clockwork mod recovery menu it's not there either (assuming I'm missing the files to go there now).
What can I do guys? Do I need to get 2.3 back on here again and redo everything.. when I get back to where I'm going to flash the hellybean rom how do I find the file on my sd card? I went to SD folder and it wasn't there but I checked my sd card and it is there on the computer.
Click to expand...
Click to collapse
It concerns me that you said: "Do I need to get 2.3 back on here again"
The t959 never received an official 2.3 update. Does your device have a front facing camera? If so you have the t959v which is a very different device and is in a different section on xda.
sent from the depths of helly bean
The guide to ODIN back to factory stock is in the first sticky thread of this section: http://forum.xda-developers.com/showthread.php?t=849028
But also make sure you are using the Vibrant and flashing roms for it, not the S 4G.
I've attempted to flash a newer version of cyanogenmod on my phone (10.1.3 to 11). I'm using TWRP 2.6.1.0
I can not boot because I've wiped the phone (dalvik, system, data, internal storage, cache), and I suspect the ROM I have is corrupted but I can't connect it to my computer and transfer the file via USB because I have no ROM installed and can not boot. I also can't take the SD card (since there's non) and put the file that way.
My phone is Oppo find 5
My root file flashing was successful, but installation of the ROM cm-11-20140204-NIGHTLY has failed. I assume the file was corrupted, but I have no way to find out what it is.
I now realize my mistakes, like wiping the system unnecessarily.
Is there any way to get another file on the device? any other suggestions?
Also, I'm not sure if this is the correct place to post this, but I was not able to find the right place. I apologize in advance.
Eyal,
http://forum.xda-developers.com/showthread.php?t=2141817
Check that thread, set up adb and push a ROM to the internal sd of your phone via adb. You can use adb in recovery mode (I could in CWM, dont know about your recovry) so if you can boot into recovery, you can push the rom. (There is info on the thread about adb pushing/pulling)
Sent from my GT-S5660
Cwm has an option to mount storage to PC in mounts & storage menu
Check if twrp has the option
You can mount it that way:good:
vneogi199 said:
Cwm has an option to mount storage to PC in mounts & storage menu
Check if twrp has the option
You can mount it that way:good:
Click to expand...
Click to collapse
it doesn't seem to recognize anything.
I'm hoping to get something clarified when it comes to installing ROMs. My phone was working fine for a couple of months since I acquired it, I started getting a bootloop yesterday, and I decided to use TWRP to do a factory reset. Still bootloop. I did another factory reset + wiped out internal storage, and reinstalled the ROM. Checked file manager in TWRP, and saw that internal storage is still empty, with the exception of the TWRP folder, and the ROM zip I transferred back on using my laptop.
I tried booting up anyway, and still have a boot loop.
Is it normal for a successful ROM flash to have an empty internal drive? Are the folders Android, data, DCIM, and the rest all populated on the internal drive upon successful bootup? Or is it something that's supposed to be there right after a successful ROM flash?
I'm having a had time figuring out what I need to do at this point.