Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.
Related
I have searched everywhere for an answer to this. I apologize if its been answered before. here is my issue:
I acquired an amaze 4g. S-on no rom. Freezes at white HTC screen. tried stock GB RUU but apparently it has ICS. So I loaded ICS OTA RUU. 3 different ones OTA and leaks. I also have ADB shell access if this matters. I can get to my sd card through CWM but not through 4ext because I am unable to mount the internal sd. I have pulled my hair out for days on end trying to fix the unable to mount /internal_sdcard issue. I did however find a CWM ICS stock recovery download and tried that through CWM since that seemed to be able to acces my external SD somehow (apparently the same way the bootloader does when updating the ph85img). But i get an MD5 sum error. so... this leads me to a new post. How do I fix the mounting issue? Also before the mounting issue happend (i think after trying to install a ROM using a super wipe method). And once that is clear apparently the "roms" hang at the boot animation and go into a bootloop. But first things first. got to get the mount issue fixed. anyhelp will be greatly appreciated!
one last thing. I also have hansoon2000's toolkit v. 3.1 & 3.2 although i prefer 3.1 because 3.2 seems to be very buggy.
Johnny.Sleven said:
I have searched everywhere for an answer to this. I apologize if its been answered before. here is my issue:
I acquired an amaze 4g. S-on no rom. Freezes at white HTC screen. tried stock GB RUU but apparently it has ICS. So I loaded ICS OTA RUU. 3 different ones OTA and leaks. I also have ADB shell access if this matters. I can get to my sd card through CWM but not through 4ext because I am unable to mount the internal sd. I have pulled my hair out for days on end trying to fix the unable to mount /internal_sdcard issue. I did however find a CWM ICS stock recovery download and tried that through CWM since that seemed to be able to acces my external SD somehow (apparently the same way the bootloader does when updating the ph85img). But i get an MD5 sum error. so... this leads me to a new post. How do I fix the mounting issue? Also before the mounting issue happend (i think after trying to install a ROM using a super wipe method). And once that is clear apparently the "roms" hang at the boot animation and go into a bootloop. But first things first. got to get the mount issue fixed. anyhelp will be greatly appreciated!
one last thing. I also have hansoon2000's toolkit v. 3.1 & 3.2 although i prefer 3.1 because 3.2 seems to be very buggy.
Click to expand...
Click to collapse
When you flashed the stock ruu, did you allow it to boot up properly before attempting any flashing or custom recovery using of any sort?
Dark Nightmare said:
When you flashed the stock ruu, did you allow it to boot up properly before attempting any flashing or custom recovery using of any sort?
Click to expand...
Click to collapse
what do you mean by "boot up properly"?
after ruu loads, checks, then updates... i wait until it turns off before i jump into bootloader/recovery. Should i have let it continue to the HTC screen? it just freezes there.
update: ok, reloaded OTA ICS RUU... when it was done I went to fastboot and rebooted left it on htc screen for a few min. then pulled battery > bootlader > unlocked with hansoons > reflashed 4ext > rebooted > no good > did it a second time and went to fastboot > reboot let it load and freeze on HTC. cleared the /internal_sdcard error and its working now. THANKS!!! would have never guessed that all i had to do is reboot and thats all it needed. I was just taking battery out after it was done. on to next issue :/
formatted and cleared everything 3 times... loaded stock ICS rom.. gets half way through boot animation and locks... formatted again.. loaded energy rom, bootlooped at boot animation once, rebooted. and VOILA!
THANK YOU SOOOOOOOOO MUCH MAN! I would give you a thanks but I have no idea how. This is my first post.
There's a button right there , always let the phone boot properly, you may think it freezes on the HTC screen but it's actually setting up files, etc. Don't disturb it, let it be and the set up screen will pop up in a minute or so, it need to add files, remove files and properly map everything on first boot.
Thanks again man! Running perfect. I saw the thanks button, it was right in front of me. haha. :good:
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
GoogleFap said:
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
Click to expand...
Click to collapse
this seem to becoming a more frequent problem maybe something TWRP is responsible for i came to this same obstacle when trying to flash a new rom like a week ago. i tried all the nifty moves i could but no luck even went to sprint looking for answers ultimately i was forced to format (with windows) both internal and external SD. end result. yep u got it i lost everything almost 26gigs of music and files i had backed up no where else. so i formatted (heart broken) got over it now i back up files daily on my laptop thats the only way ive come to see out of this one. but check around forums a solution might work for i saw a couple didnt work for me tho.
JB ROMs rewrites the addresses of your SD cards, good chance the internal is corrupted. Boot to recovery and go to mount/mount USB storage, if you have windows then as soon as you plug it in windows will tell you to reformat, if you have Mac or Linux manually reformat the card
Thanks for the replies, guys.
Tried reformatting, but that didn't seem to help. On #twrp on freenode, they said it looked from my recovery.log that the internal and sdcard storage is hosed, and the maintainer of TWRP said to RUU back to stock. SIGH. . . .
So, since I don't have Windows at work, going to try these at home tonight:
(Great. Was trying to post links, but wasn't allowed. Suffice it to say, I was going to post my recovery.log link and the links to the instructions I am going to follow to RUU back to stock.)
Well that sucks, I'm lucky that I haven't hosed my emmc yet. I can't decide whether to stay on aosp or not, must have flashed back and forth a million times by now
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
GoogleFap said:
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
Click to expand...
Click to collapse
Did you ever find a solution to this? I'm in the same boat...
llaen said:
Did you ever find a solution to this? I'm in the same boat...
Click to expand...
Click to collapse
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I had backed up my sdcard so I didn't really care about not losing it. I think the problem was at least partially caused by having it encrypted.
I ended up flashing to stock and it let me format the sdcard from within the phone - that did it.
Thanks for the suggestion.
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This just advice just saved my life. I thought for sure I bricked my phone, and right before memorial day weekend toooo! I did run into issue with the latest Lollipop RUU. I had to resort to using the old Kit Kat RUU I had saved to my computer from before. It worked like a charm.
I am a relative noob at flashing roms and rooting phones, but last night I ran into an issue. My phone was having all sorts of problems so I was going to put it back to factory, then start from scratch. I then decided to just flash a different rom. here is what happened.
I deleted SuperSU - this was done as part of the process to unroot and put back to factory, after this step I decided to flash a different rom
Put new ROM on phones internal memory as well as SD card
Wipe data
wipe cache and delvic cache
install new rom
Black screen
In an attempt to unbrick I relocked my bootloader.
Now, my phone can power on (Give white screen and HTC logo), then go black, and I can access Recovery mode. That is all.
I have plugged the phone to my computer and tried running the RUU, but the RUU will not recognize the phone.
I am not sure what to do to unbrick my phone and get it working again. Any and all help would be most appreciated!
Sorry I can't be more eloquent with my words, but I'm at work. I will be responding throughout the day, though.
thanks again so much to anyone that can help!
Try running it straight from bootloader
I loaded into Bootloader, selected Fastboot(USB), ran the .exe and it still won't recognize the phone. However, I did get recovery unlocked again. So I can get into recovery mode, flash all the ROMs I want, mount and unmount, yet still everytime I flash a new ROM it still boots to a black screen. Am I doing this right?
Try a Rom with kernel installer
Thanks! Since I am still a little new could you tell me how I would spot a ROM with kernel installer or could you point me to any one that could work? From then, it's the same process as flashing any other ROM? Do I need to do something with the kernel?
Meanbean and stock with goodies are the 2 that I'm certain of. Meanbean needs to be flashed twice the first time
Thanks so much for your help, I will post my results soon!
Failed
Here's what it says. Sorry for the blurry picture. I followed directions closely.
What version of recovery are you using? You may need to update it. Assuming you have a pc, try mounting the internal memory to pc through twrp. Windows will automatically tell you to format if its damaged
2.1 Updating now
omg it finally worked! Updated TWRP using fastboot and flashed MeanBean. Thank you so much!!!
I'm s-off, on hboot 1.19, my baseband is 1.12.11.1210.
I just tried to change roms from meanrom ics to paranoid 3.99. Everything went fine in twrp. When I rebooted the phone it ran thru "upgrading android apps" & when it got to the spot where you'd start entering all your info, I got an error saying unfortunately, the process com.android.phone has stopped. There was another message underneath that one. I couldn't really read it but it said something about IU issues. I've tried reflashing the rom but the same thing happens. I have backups made & went to them in twrp, but they aren't a flashable zip like I thought they'd be. I can still get into the bootloader, but when I select fastboot I can't get my phone to connect to my cpu anymore. It was working before I tried all this. I even tried reinstalling meanrom but it gets about a 1/3 of the way thru the install & reboots to the splash screen & it just sits there. I know I'm probably missing something minor, but I could really use some fresh eyes.
Thanks in advance for the help.
ETA...I'm on twrp v.2.6.3.0 & can still get into the bootloader & recovery. Fastboot USB just won't work. I've tried doing system wipes & installing different roms & they either fail or get stuck in bootloop. I found my backups in twrp but they all fail to install when they get to /data. Some of them don't even make it that far.
Well, I went ahead & booted up off of one of my b/u that said it failed. I got my phone back to where I could start entering wifi info,ect...but I'm getting another error unfortunately the process android.process.acore has stopped. I went into twrp & did the "fix permission" thing. I now get the same error as before...unfortunately, the process com.android.phone has stopped.
Well I've been wanting to leave sprint...I guess today is as good a day as any.
As a last ditch effort, I did the factory reset in the bootloader. I then went into twrp & formatted my sd card thru windows. I then tried to install meanbean & it came up with no errors. I must've done something wrong when I tried to install paranoid android & got my sd card corrupted. Now I just have to figure out why I can't connect via fastboot usb...but that will be for another day. I'm just glad I don't have to switch carriers just yet. I'm holding out for the new htc one.
buddahj said:
As a last ditch effort, I did the factory reset in the bootloader. I then went into twrp & formatted my sd card thru windows. I then tried to install meanbean & it came up with no errors. I must've done something wrong when I tried to install paranoid android & got my sd card corrupted. Now I just have to figure out why I can't connect via fastboot usb...but that will be for another day. I'm just glad I don't have to switch carriers just yet. I'm holding out for the new htc one.
Click to expand...
Click to collapse
By not beig able to connect to fastboot, do you mean you get a message saying no devices found?
numel007 said:
By not beig able to connect to fastboot, do you mean you get a message saying no devices found?
Click to expand...
Click to collapse
So........I'm an idiot. I was forgetting to open the command prompt in the platform tools folder. My fastboot usb works fine. Right now, I'm just having trouble installing the htc mtp drivers.
Have the drivers been updated?
Took the red pill. HTC evo 4G LTE evilution red pill.
So, maybe someone can help me out here. I wanted to install Kit Kat Killer. This is what happens:
Rooting Process
1. I used Odin to install the root automatically.
2. I verified the root.
3. SuperUser and BusyBox installed.
4. Used Odin to install TWRP.
Recovery
1. Booted into TWRP.
2. Accidentally forgot to Nandroid Backup.
3. Wiped internal data, wiped everything else except SD Card.
4. Went to install Kit Kat Killer. Got some failed messages about some usb folder being unable to be mounted.
5. Rebooted phone. Re-downloaded everything and moved to SD.
6. Still fails.
Google time...
1. Downloaded some files from the links/forums I came across. None of these two files will flash through Odin, saying FAIL!
a. N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar
b. N900PVPUBMI3_N900PSPTBMI3_N900PVPUBMI3_HOME.tar
2. TWRP can't be added through ODIN anymore as far as I know. I was using version
Now...
1. TWRP is gone.
2. Phone is stuck in "ODIN MODE" for recovery (?).
3. I can't get past the Samsung Galaxy Note 3 screen.
4. When I get the yellow triangle about needing Kies3 for an emergency firmware repair, it does NOT recognize my phone. Yes, I am using Kies 3. It says I am using an unsupported phone.
5. It does say SW REV CHECK FAIL.
I am at a total loss here. I know it's a soft brick, but for the life of me, I can not figure out what to do next.
Thanks for all your help!!
Just got it back into TWRP mode. It keeps saying:
"E: Unable to mount /usbstorage"
Then when it tries to install KitKatKiller, it checks for the MD5 (on the SD too in the same directory), it says FAIL. I think this whole issue is based on the usbstorage thing.
Right now, I am going to download the latest Sprint stock ROM and see if I can flash it in TWRP. This will take at least 50 minutes to get going (30 for download/20 for file transfer). So plenty of time for you guys to jump in and say otherwise
Really, I appreciate all of your help!!! I am sure I made a n00b mistake. I had no real problems with my GSIII or EVO 4G once I got the hang of things
I think you guys can close this thread. I am not sure what the hell happened, but I wiped my SD card after copying the KitKatKiller ROM to another folder on the internal SD. I had forgotten to include the MD5 file in the same folder as well, but it finally installed. Right now, the phone is showing KitKatKiller logo spinning and booting up, so I presume the phone will be fine from this point, and if not, I will use Kies 3 to return it to stock and give it a try again. Again, you can close this thread, I feel like an idiot but it all worked out for some odd reason. I'm still not sure why I was getting "unable to mount usbstorage" errors.
Thanks again for everyone taking a look!!!!!!
jacobmiw said:
I think you guys can close this thread. I am not sure what the hell happened, but I wiped my SD card after copying the KitKatKiller ROM to another folder on the internal SD. I had forgotten to include the MD5 file in the same folder as well, but it finally installed. Right now, the phone is showing KitKatKiller logo spinning and booting up, so I presume the phone will be fine from this point, and if not, I will use Kies 3 to return it to stock and give it a try again. Again, you can close this thread, I feel like an idiot but it all worked out for some odd reason. I'm still not sure why I was getting "unable to mount usbstorage" errors.
Thanks again for everyone taking a look!!!!!!
Click to expand...
Click to collapse
Glad you figured your issues out. Just popped into tell you that twrp fails mounting USB because it's looking for an external USB. Not to worry its supposed to fail unless you have a USB drive plugged in through an otg cable.