I know there are a couple of other threads out there, but I want to make sure I get the right solution for my problem...
Hboot 1.12
S-ON
I've been running SuperLTE 2.0 for a few weeks, and when i plugged into the charger last night it started bootlooping. In TWRP I cleared both caches, but I am unable to mount the internal SD CARD and bootloops continued. I am able to mount the external SD just fine...
I've made no other changes while I ponder a solution. Looking at other threads, should I try reformatting the SD somehow, run an RUU (which one? never done that...), or run one of the twrp advanced menu apps like dumloc?
Solved, see third reply...
Well at least your not alone. I am running Stock rom with root, Hboot 1.12, and S-off (LazyPanda). On saturday my phone froze up, then rebooted. It immediately started boot looping and i could not get it back. Wiped cache, dalvik, nothing worked except a factory reset. I did make a backup of it to try and fix it but needed the phone back up ASAP. If anyone knows what is going on please help us.
Tried this three times and it did not work:
1. Remove external sd card
2. Boot into bootloader then recovery
3. Mount USB (to internal SD)
4. Windows recognized unformatted drive so I reformatted to fat32
5. Copied SuperLTE rom to SD card
5. Restarted and reinstalled ROM with full wipe
6. Boot to rom, everything seems to work
7. Shut down, insert external SD CARD, power on
8. Bootloops
looks like something besides the internal sd is FUBAR perhaps... The data seems to be good on the internal and external, so I'm left scratching my head
I think I finally fixed it by running the RUU:
(RUU_JEWEL_CLICS_40_S_Sprint_WWE-2.13.651.1_Radio_1.12.11.0809_NV_SPCS-2.45_003_release_277028_signed.exe)
I was reticent to do this because I had flashed radios and didn't want to upgrade my hboot, but it turns out that it was easy and didn't matter. Rerooting was via the stickied method instead of the old 1-click for 1.12 hboots, but that was easy enough.
1. Download the RUU
2. adb, fastboot oem lock
3. run RUU from fastboot usb
4. Reboot, then root via stickied post
5. Nandroid backup the stock rom for posterity
6. wiped, wiped, wiped til there were no brown stains
7. Changed format in twrp to rm-rf because on the superlte insructions it says to do so because of ext4 optimizations
8. wiped again
9. flashed superlte via the aroma installer
10. Yay
I should have bit the bullet and done the RUU yesterday... Everything is now up to date on the firmware side and re-rooting was easy. Hopefully it works good lasts long time.
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.
I had originally run RegawMOD rooter on 1.13.651.1 and the phone ran great. Yesterday, I decided to do LazyPanda S-OFF and then try out some of the 1.22.651.3 ROMs. LazyPanda said everything completed successfully. I went into TWRP, wiped System/Cache/Dalvik, then went to install a ROM but it failed because it couldn't mount sdcard2. I read through the LazyPanda thread and noticed that there were sometimes data loss issues with the SD card - no biggie, I had all my data backed up. I didn't have an adapter on hand to hook up the SD card directly to the computer, so I went out and picked up a SD card + adapter combo.
Today, I put the brand new SD card into the device and boot into TWRP; however TWRP takes a long time to boot. I look at the console spew and there are a bunch of "E:failed to mount /sdcard (invalid argument)" errors and even a "E:failed to mount /cache (invalid argument)" one. Of course, this is the internal memory. I'm pretty sure I didn't see these errors last night, so I'm not sure what happened between then and now.
So my question is: how do I get back to a usable state? I don't care about losing any of the data (it's backed up elsewhere), I just need a working phone.
Trioculus said:
I had originally run RegawMOD rooter on 1.13.651.1 and the phone ran great. Yesterday, I decided to do LazyPanda S-OFF and then try out some of the 1.22.651.3 ROMs. LazyPanda said everything completed successfully. I went into TWRP, wiped System/Cache/Dalvik, then went to install a ROM but it failed because it couldn't mount sdcard2. I read through the LazyPanda thread and noticed that there were sometimes data loss issues with the SD card - no biggie, I had all my data backed up. I didn't have an adapter on hand to hook up the SD card directly to the computer, so I went out and picked up a SD card + adapter combo.
Today, I put the brand new SD card into the device and boot into TWRP; however TWRP takes a long time to boot. I look at the console spew and there are a bunch of "E:failed to mount /sdcard (invalid argument)" errors and even a "E:failed to mount /cache (invalid argument)" one. Of course, this is the internal memory. I'm pretty sure I didn't see these errors last night, so I'm not sure what happened between then and now.
So my question is: how do I get back to a usable state? I don't care about losing any of the data (it's backed up elsewhere), I just need a working phone.
Click to expand...
Click to collapse
I have had this problem before. It started when I booted twrp without my external ad card,then when I put it back in it recognizes it but it somehow got the sd ext mixed up with int sd so it tried to write roms to the ext sd,no matter how many times I reset it to recovery its still the same. The only solution I have found was to re-flash twrp I was using 2.18 or something now on 2.2 and I would recommend it. Here's how I fixed it easy. Downloaded evo 4g lte toolbox from the lte dev forum (not sure if its the orig forum or not),installed and opened toolbox,installed HTC drivers from toolbox,restart my phone in bootloader (vol-d+power) went into fastboot and clicked on push recovery from toolbox,reset into recovery and viola everything mounts properly. I am htcdev unlocked and I'm not sure if its different when your s-off. You should still be able to push recovery from fastboot. Let me know if this works
Sent from my EVO using xda premium
I wasn't able to find the toolbox you mentioned; however I was able to resolve the problem. I ended up running the RUU mentioned here to restore the internal memory to a installable state.
Trioculus said:
I wasn't able to find the toolbox you mentioned; however I was able to resolve the problem. I ended up running the RUU mentioned here to restore the internal memory to a installable state.
Click to expand...
Click to collapse
When in recovery touch mount and then touch external card so there is an x in the box then back out then touch the second choice thing with like two or three dots and select sdcard. that is what I did
PS: TOUCH SO THERE IS A DOT NEXT TO USING EXTERNAL SDCARD AT THE BOTTOM - THEN BACK OUT AND DO ABOVE.
No internal memory
Trioculus said:
I wasn't able to find the toolbox you mentioned; however I was able to resolve the problem. I ended up running the RUU mentioned here to restore the internal memory to a installable state.
Click to expand...
Click to collapse
So are you saying you completely unrooted your phone and went back to step one to fix this problem? I am trying to get my internal memory back myself.
if this happens again, there have been reports that mounting your phone to windows while in TWRP and formatting it will fix the issue. no need to RUU...but atleast it fixed your problem :victory:
Have same mounting issues with TWRP
bog3nator said:
if this happens again, there have been reports that mounting your phone to windows while in TWRP and formatting it will fix the issue. no need to RUU...but atleast it fixed your problem :victory:
Click to expand...
Click to collapse
I'm using samsung galaxy i9001. Have installed TWRP. But unable to access sd card on PC.
where can I find this format option?
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?
Hey everyone last night I rooted my phone and this morning I attempted flashing a ROM called ViperOneS that you can look at here -->http://forum.xda-developers.com/show....php?t=2105863. So in order to install it the OP wrote in the instructions to factory restore the phone which I did. When I cleared the cache and everything and went to install it TWRP said it failed so I just erased it. Then when I went to reboot it was stuck on the screen with the red writing so I rebooted it in Recovery and it said there was no OS installed. I looked for this problem online and found that if I mounted the phone to my computer I could copy and paste a new ROM for my phone which I eventually tried to do but for some reason it does not allow me to check off either of the boxes next to "Mount SD Card" or "Mount Internal." It does let me mark all the other boxes. Could somebody explain what I should do so the computer recognizes the phone as a "Removable Disk" like it used to so I can just drag and drop a new OS into my phone and put this thing behind me already? If you can't tell already I'm a newby at this stuff so if you can make simple steps that'd be great. Thanks in advance.
try this:
1-flash recovery again (fastboot flash recovery recovery) or change to CWM
2-erase dalvik cache and cache
3-connect as mass storage via recovery
---------------------------------------------------------------------
remember always have a backup of your system specially when is your first rom
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.