Here's the deal.. I don't understand this AT ALL and I have no idea where to even begin troubleshooting it.
My friend's SDCARD in his phone was reading properly. I decided to pop it in my phone to try and see if I could pull her pictures off for me. I remove my card and pop her card in, try to boot.. stuck at HTC logo. Had to remove battery.
So I go into recovery and recovery can't even mount my internal storage...? So I freak out, remove ALL the sdcards, and try to go into recovery again (EXT4 recovery)
I get into recovery. error mounting /internal_sdcard
what the heck?
I try to mount /sdcard through the mount menu, just says error mounting /sdcard. I don't know what to do at this point.
there's no SDcard in the drive (tried to put my SDCARD back, nothing). The phone simply cannot mount the internal SD card for some reason.
Is there anything I can do? Or did inserting my friend's SDCARD somehow manage to kill my internal storage? ( i really don't know how this could possibly happen )
Please, if someone can help me / give me ANY advice I'd really appreciate it.. I don't know if I have to 'lose' my phone now for a warranty replacement or what.. because this doesn't make ANY SENSE to me whatsoever.
Please, anyone? Everything I try to do in 4ext simply throws the error "unable to mount /internal_storage"
I tried manually mounting through the mount menu, throws "Error, unable to mount X" I tried to restore, but it can't because it can't mount the internal storage... this doesn't make ANY SENSE to me whatsoever.
4ext tells me I'm in safe mode and I'm unable to mount any internal partition, please wipe all internal partitions.. so I go to wipe, and it spits out a crapton of errors
"Formatting /system...
E:format_volume: make_extf4fs failed on /dev/block/mmcblkk0p29 (does this twice)
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p31 (2 times)
It does this for every partition.. what the? I really don't understand
I'm at a complete loss, please help.. it's like my internal storage completely stopped working the minute I put that SDcard in my phone.. which makes zero sense to me, but maybe it makes sense to someone else? Agh.. this is so frustrating, phone was working great beforehand.
Too much pr0n maybe? Anyways, you'll have to restore your software via a stock ruu to remap the sd card, I don't get how your story screwed it up to begin with, last guy that told me this actually did something else, how do I know that? After I restored the soft brick, I saw the files. If you're on tmobile, head on over to the development section for the amaze, look for the stock ruu/ota thread, grab the very first tmobile ICS file, rename it PH85IMG, place it on your external sd card, put this back into your phone and reboot into hboot, once hboot finds it, volume up to update, if you're not s-off, then you'll have to relock the bootloader before attempting this.
Let it boot at least once, it's gonna remap the internal sd and whatever other partitions that were screwed.
Probably pulled the card when the device was on or accessing it? Maybe, I dunno, kind of odd though.
---------- Post added at 01:01 AM ---------- Previous post was at 01:00 AM ----------
And before someone else says it, wrong forum dude! Post all questions in q&a!
Good night, I'm sleepy now.
ericdjobs said:
Here's the deal.. I don't understand this AT ALL and I have no idea where to even begin troubleshooting it.
My friend's SDCARD in his phone was reading properly. I decided to pop it in my phone to try and see if I could pull her pictures off for me. I remove my card and pop her card in, try to boot.. stuck at HTC logo. Had to remove battery.
So I go into recovery and recovery can't even mount my internal storage...? So I freak out, remove ALL the sdcards, and try to go into recovery again (EXT4 recovery)
I get into recovery. error mounting /internal_sdcard
what the heck?
I try to mount /sdcard through the mount menu, just says error mounting /sdcard. I don't know what to do at this point.
there's no SDcard in the drive (tried to put my SDCARD back, nothing). The phone simply cannot mount the internal SD card for some reason.
Is there anything I can do? Or did inserting my friend's SDCARD somehow manage to kill my internal storage? ( i really don't know how this could possibly happen )
Please, if someone can help me / give me ANY advice I'd really appreciate it.. I don't know if I have to 'lose' my phone now for a warranty replacement or what.. because this doesn't make ANY SENSE to me whatsoever.
Please, anyone? Everything I try to do in 4ext simply throws the error "unable to mount /internal_storage"
I tried manually mounting through the mount menu, throws "Error, unable to mount X" I tried to restore, but it can't because it can't mount the internal storage... this doesn't make ANY SENSE to me whatsoever.
4ext tells me I'm in safe mode and I'm unable to mount any internal partition, please wipe all internal partitions.. so I go to wipe, and it spits out a crapton of errors
"Formatting /system...
E:format_volume: make_extf4fs failed on /dev/block/mmcblkk0p29 (does this twice)
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p31 (2 times)
It does this for every partition.. what the? I really don't understand
I'm at a complete loss, please help.. it's like my internal storage completely stopped working the minute I put that SDcard in my phone.. which makes zero sense to me, but maybe it makes sense to someone else? Agh.. this is so frustrating, phone was working great beforehand.
Click to expand...
Click to collapse
In ext click format then format sdcard then internal and yes and it will do it by the way questions go in Q&A not general you probably took the sdcard out without unmounting it
Here, I even did the leg work for ya: http://d-h.st/3VD
Sportstar that won't work bro, dealt with this on a one s, only way to fix it was restoring the ruu, think someone had said restoring the stock recovery, then clearing storage in hboot, then proceeding into stock recovery and wiping the device helped to fix it as well, I dunno, he can give it a shot.
Terribly sorry for posting in the wrong forum, was in a panic heh.. won't happen again.
Going to try and put teh stock RUU on the SDcard and put it back in phone and see what happens, thanks for the suggestions guys, will definitely let you know.
And yeah, I can't do anything in 4ext.. it fails every time I try to format any partition, saying it's unable to mount the internal storage.
Dark Nightmare said:
Too much pr0n maybe? Anyways, you'll have to restore your software via a stock ruu to remap the sd card, I don't get how your story screwed it up to begin with, last guy that told me this actually did something else, how do I know that? After I restored the soft brick, I saw the files. If you're on tmobile, head on over to the development section for the amaze, look for the stock ruu/ota thread, grab the very first tmobile ICS file, rename it PH85IMG, place it on your external sd card, put this back into your phone and reboot into hboot, once hboot finds it, volume up to update, if you're not s-off, then you'll have to relock the bootloader before attempting this.
Let it boot at least once, it's gonna remap the internal sd and whatever other partitions that were screwed.
Probably pulled the card when the device was on or accessing it? Maybe, I dunno, kind of odd though.
---------- Post added at 01:01 AM ---------- Previous post was at 01:00 AM ----------
And before someone else says it, wrong forum dude! Post all questions in q&a!
Good night, I'm sleepy now.
Click to expand...
Click to collapse
No need to install the entire RUU. Assuming you know how to use adb, boot your phone into recovery and type in this command EXACTLY. And by exactly, I mean follow the case too. If it shows as a capital letter, type it as a capital letter!
Alright here's the command. Make sure you're booted into recovery, then plug in your phone. Don't do anything BUT this command.
adb shell /sbin/newfs_msdos -F 32 -L INT_SD -c 64 /dev/block/mmcblk0p36
note the switches (-F, -L) is in UPPERCASE, and the switch (-c) is in LOWERCASE.
It should spit out some stuff, just ignore it. The internal SD card should now be fixed.
Keylogger_0 said:
No need to install the entire RUU. Assuming you know how to use adb, boot your phone into recovery and type in this command EXACTLY. And by exactly, I mean follow the case too. If it shows as a capital letter, type it as a capital letter!
Alright here's the command. Make sure you're booted into recovery, then plug in your phone. Don't do anything BUT this command.
adb shell /sbin/newfs_msdos -F 32 -L INT_SD -c 64 /dev/block/mmcblk0p36
note the switches (-F, -L) is in UPPERCASE, and the switch (-c) is in LOWERCASE.
It should spit out some stuff, just ignore it. The internal SD card should now be fixed.
Click to expand...
Click to collapse
RUU already on there and blue bar filling up.. but you are all god among men, seriously.
Hopefully this works.
Anyone care to take the time to explain (in a little detail, possibly) what happened here? I did remove the external SDcard while the phone was on, I think.
How in the world did toying with the external SDcard manage to make the internal SD card unable to be mounted? This doesn't make sense in my brain, but then again I'm pretty new at this stuff... attempting to learn what exactly caused this as to not have it happen again.. if this works that is. Oh you know what, I think I forgot to relock the bootloader so this is probably going to fail anyhow. I will try your method first and see if that fixes it, then I can just flash my custom ROM.
Keylogger_0 said:
No need to install the entire RUU. Assuming you know how to use adb, boot your phone into recovery and type in this command EXACTLY. And by exactly, I mean follow the case too. If it shows as a capital letter, type it as a capital letter!
Alright here's the command. Make sure you're booted into recovery, then plug in your phone. Don't do anything BUT this command.
adb shell /sbin/newfs_msdos -F 32 -L INT_SD -c 64 /dev/block/mmcblk0p36
note the switches (-F, -L) is in UPPERCASE, and the switch (-c) is in LOWERCASE.
It should spit out some stuff, just ignore it. The internal SD card should now be fixed.
Click to expand...
Click to collapse
Ey, I'm no dev, like you are, just giving the options I know about, . Lol
When I try that command, I get
"/sbin/newfs_msdos: /dev/block/mmcblk0p36: No such file or directory"
Guess I will try the RUU method
I want to let you all know that I really do appreciate this.. more than you'll ever know heh.. if it saves me $130 you rock my socks. Well, you rock my socks either way.
Relocked bootloader and stock RUU is loading up now (blue bar) *crosses fingers* sure hope this is successful, I can't be without a phone haha
Trying to flash RUU I get
"Update failed!"
"Main Version is older"
so I try the Mainver older fix in hansoon's tool
"C:\HTCAmaze\data>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\HTCAmaze\data>adb push misctool /data/local/tmp/misctool
error: device not found
C:\HTCAmaze\data>adb shell chmod 777 /data/local/tmp/misctool
error: device not found
C:\HTCAmaze\data>adb shell "./data/local/tmp/misctool w 1.00.000.0"
error: device not found
"
Now I can't even get into recovery because the bootloader is locked, I presume? But how do I unlock the bootloader if ADB is giving me device not found? Tried it from fastboot, no dice.
Agh I'm so lost, I'm going to try and download a later version of the RUU, used an older one I had stored on my dropbox for faster download
My bad, I see that unlocking bootloader is a fASTBOOT command and not ADB, doh... here we go again.. lol
Okay, was able to get mainver set to 1.00.000.0 manually. Now I will try to restore the stock RUU I have after relocking the bootloader..
Still not sure what that previous command simply refuses to work saying directory doesn't exist, scares me a bit.. but here we go
I tried to do the new_fs manually.. and it tells me it straight doesn't exist
"newfs_msdos: /dev/block/mmcblk0p36: No such file or directory"
Yeah unclocking bootloader is fastboot flash unlocktoken Unclock_code.bin (or any other file name that contains your unlock code from HTCdev).
And the only reason I can see for loosing access to your internal SD by removing the external one is that it corrupted a file or something kind-of that is needed to drive the sdcards and as the two cards are the same type it just can't do anything with both of them. Far to be an expert though.
Sent from my HTC_Amaze
Now it's telling me Hboot version is older... ugh.. what the hell
I guess I will try with teh latest RUU it's almost finished downloading.
Did one of the ICS RUUs update hboot or something? I didn't think so.
HBOOT is 1.93.0002
But to use the older fix you have to be in recovery with at least read access to /dev to see the block specified in the command. I think I read that you can't access recovery which is wierd since you can boot in it even with everything locked, you just can't flash it while locked. So maybe reflashing it from fastboot is worth a try. (fastboot flash recovery your_recovery.img)
Sent from my HTC_Amaze
Where is keylogger at?
Dark Nightmare said:
Where is keylogger at?
Click to expand...
Click to collapse
Wut?
We're discussing it through PM. He pm'd me
Already tried to reflash the recovery, and keylogger is helping me out via PM
Sorry guys, just really at a loss for what's going on here
Oh and I can access recovery, it was because bootloader was locked that I was unable..
Going to try with the latest RUU now.. I guess hboot was updated? on HBOOT 1.93.0002.. with the RUU I was using (slow internet here..) I was getting MainVer older error.. fixed that using Hansoon's method.. then got an Hboot Older error.. ugh so frustrating. Trying the latest RUU now (the R2 version)
ericdjobs said:
Already tried to reflash the recovery, and keylogger is helping me out via PM
Sorry guys, just really at a loss for what's going on here
Oh and I can access recovery, it was because bootloader was locked that I was unable..
Going to try with the latest RUU now.. I guess hboot was updated? on HBOOT 1.92.0002.. with the RUU I was using (slow internet here..) I was getting MainVer older error.. fixed that using Hansoon's method.. then got an Hboot Older error.. ugh so frustrating. Trying the latest RUU now (the R2 version)
Click to expand...
Click to collapse
As I've already mentioned in the PM, let us know how the RUU flash goes. God forbid if you get a Fail-PU error.
Keylogger_0 said:
As I've already mentioned in the PM, let us know how the RUU flash goes. God forbid if you get a Fail-PU error.
Click to expand...
Click to collapse
Attempting it right now with the latest RUU
We'll see, heh. Time to cross my fingers again, it seems
So if I do get this "Fail-PU" is it time for a warranty exchange along with $130 deductible? Bah, that will really suck.
It's under HTC warranty but I guess that doesn't matter considering I've unlocked the bootloader.. or do you think T-Mobile would replace the phone anyhow? I'm more worried that they will replace it under their phone replacement program, send it to HTC.. then bill me $500 or whatever because HTC will claim it wasn't covered.. any advice in that particular situation?
It really stinks because it seems to be a genuine hardware error if that indeed does happen...and I've only had the phone for a handful of months. The blue bar is almost done! Next is the yellow bar then the moment of truth.
ericdjobs said:
Attempting it right now with the latest RUU
We'll see, heh. Time to cross my fingers again, it seems
So if I do get this "Fail-PU" is it time for a warranty exchange along with $130 deductible? Bah, that will really suck.
It's under HTC warranty but I guess that doesn't matter considering I've unlocked the bootloader.. or do you think T-Mobile would replace the phone anyhow? I'm more worried that they will replace it under their phone replacement program, send it to HTC.. then bill me $500 or whatever because HTC will claim it wasn't covered.. any advice in that particular situation?
It really stinks because it seems to be a genuine hardware error if that indeed does happen...and I've only had the phone for a handful of months. The blue bar is almost done! Next is the yellow bar then the moment of truth.
Click to expand...
Click to collapse
Just wait and see if you do get it first. Let's not jump to conclusions.
I'm no expert but based on my experiences with the Amaze ... here's my two cents
Whatever you are flashing and getting an error ... Just flash it again.
I've got the Amaze from the first day it launched and learnt how to unlock/root/flash/S-off from this forum .... Many times I got error - be it ADB/RUU/Toolkit/flashing ROM or RUU ect - just do it twice (and even three time to get it done.)
Doesn't hurt to try again after it failed. Just do it twice my friend
Good luck
Related
Hi, I've had lot's of problems with my HTC recently, no adb access etc, device not being recognised and recovery playing up, ie not being able to wipe install roms etc... however I fixed the recovery issue and managed to do a nandroid backup, I put on I think it was 1.5 HTC sense hero rom... and recently realised that i can only flash 1.5 roms, not 2.1 anymore? would any developer know what would of caused this problem? Any 2.1 rom just locks on the Hero logo, and I've left it for over an hour in some cases and nothing happens. Again, I used to be able to put on any custom rom.... I'm all out of ideas.
wipe
did you wipe? what recovery image you using etc etc?
1. post in the correct section.
2. remove the ext4 partition from your sdcard, or change it to ext2 or ext3.
3. get adb logcat, otherwise this is like the question "my car won't run, can anybody tell me why?"
I have wiped numerous times... sorry for the "my car won't run type question etc...." just that I've done my research, gooogled, posted detailed info previously on here and another forum, I even fixed my own problem of the recovery image, without fixing that I would have nothing. But anyway the card is partitioned with swap, ext2, fat32 using the latest Amon_Ra image 1.6? something... i've spent weeks trying to resolve this and learnt a lot along the way.
Obviously not where to find the adb logcat... don't worry I'll google it.
Apologies for posting in the wrong forum, if it can be moved could a mod do so?
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Thanks for your reply, I will approach this method again at some point and give it a try, but I think I read somewhere that I couldn't do it for whatever reason, but I'll look into it again seeing as you've had the same issues. Thanks.
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Actually I believe I didnt attempt this because I was no longer able to get my HTC hero working with ADB, as soon as I plug the device in, it comes up as device unrecognised, so I think goldcard method it out.. :-(
on the risk of offending you again (even though i am trying to help here...): you did not provide really much valid info. for most things you just said "doesn't work". what happens if you start by pushing home+power? saying the recovery doesn't boot up tells what does NOT happen, for a diagnosis we need the info what DOES happen.
anyway, if i get you right your recovery is now working. now repartition your sdcard (ext2 and fat, NO swap), do a full wipe, then install the rom you desire to use, then move the log to sdcard ("other" in recovery). reboot your phone and execute "adb logcat > c:\logcat.txt" on your pc. if it doesn't boot up after five minutes stop logcat with ctrl-c and post the two logfiles (recovery.log and logcat.txt). you need to set up adb, if you have problems with that sort them out, there is no way to get any information about your problem without the log.
oh, and about the goldcard: i don't know too much about goldcard'ing, but i can't see how this should help here. my strongest guess is that the swap partition interferes with the boot process...
No worries no offence taken. Pushing Home+Power works and takes me to recovery. Back+Power takes me to bootloader and USB Bootloader device is recognised, so I am able to get Fastboot.
Just recently installed stock rom, to see if that solved the USB and ROM issues but no such luck, re-rooted, put anom latest recovery back on, and went on to do what you have advised to help.. i've attached only the recovery.log in zip format only, as when doing adb logcat command use mentioned(after installing new rom), all I get is "waiting for devices" whilst the phone is stuck on the Hero logo, I waited about 10 minutes, exited from the adb, and the log file was empty as I guessed. I've tried every possible way that I found on the web to try and get the ADB function working again and I realise this is important to get some info.. but I've ran out of ideas for that.
Maybe the recovery(attached) may show something, all I noticed is that the cache and something else was not wiped for some reason? If you or someone has time, have a look through maybe someone knows what is going on.
Thanks for your help and patience
Here's what's happenning.
- Device was rooted using HTC unlock method with HB00t 1.5
- Was running Synergy Rom
- Wanted to get latest OTA from Sprint so I followed the steps from another thread :
http://forum.xda-developers.com/showthread.php?t=1447839&page=2- Went through steps and unlocked my device again
Used file from post #16
- Did my updates, unlocked device, booted back into HBoot
- Decided I would try the Infected Eternity Rom this time so I followed those steps as stated in their thread. Did a clean flash. Flashed Superwipe, flashed data ext optimizer tool, flashed eternity rom w/ 3.5 sense
- after message said installation was complete, i got error message when i went back to main menu in recovery:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lastçlog
E:Can't open /cache/recovery/last_log
- device wouldn't boot once I rebooted from CWM. It would hang a the HTC white screen, then reboot again, keeps repeatedly doing this.
- Then I rebooted back in HBoot by pressing Vol Down and Power buttons. Went to recovery, flashed Synergy rom. Install was fine, still can't boot up device. Having the same issue. Device would hang at HTC white screen and continue to cycle on and off trying to reboot.
- Rebooted back to HBoot by pressing Vol Down and Power buttons. Went into recovery with CWM, restored my back up. Everything went fine except I got message:
sd-ext.img not found. Skipping restore /sd-ext.
As of right now, I can still boot into HBoot. I've tried reflashing Synergy rom again, but still nothing.
From my search, it says that based on my error message:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lastçlog
E:Can't open /cache/recovery/last_log
It could be a HW or SW issue.
Phone is still under HTC warranty, if I need to return it, what do you say to support department?
Thank you.
Have you tried flashing through fast boot through a usb connection? I know the h boot 1.5 are tough to do when you need to change kernals which is what happens when you got to a 3.5 Rom. I had some trouble too if you open recovery through fast boot and do everything that way all should be good.
Edit: as long as you can get into recovery I think you'll be okay.
I can definitely still get into recovery and HBoot. So I would assume those are good things.
Read another thread suggesting to use TWRP instead of CWM.
Will try both flashing with fastboot from usb and twrp and see if that helps.....
If anyone else have other suggestions,
fastbook using android sdk...
it's never bricked unless it won't turn on.
next time, don't try to fix it if it aint broken.
Unlocking via htc will require you to follow the following. The kernel can't be written unless you follow the directions below which can cause the issue you stated.
http://forum.xda-developers.com/showthread.php?t=1239821
Just let us know what happens it is most likely just a kernal problem. Look up how to do the fast boot to make sure it works right. Fingers crossed.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
That's not a brick a brick is where you can't even get into hboot tho if your slick enough you could still fix a bricked phone lol
cobraboy85 said:
next time, don't try to fix it if it aint broken.
Click to expand...
Click to collapse
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
kyaj9 said:
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
Click to expand...
Click to collapse
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
you should give that set up a shot man. most reliable rom in my opinion.
k2buckley said:
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
The only back ups I have when I first rooted the device.
As long as formatting the SD card doesn't mean I am losing anything vital to the operation of the device, I would have no issues with having to put everything back on manually.
cobraboy85 said:
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
Click to expand...
Click to collapse
No it's the 3.5. I wanted to try the one with Sense 3.5.
For the good news!!! Finally got it to work. Backing up my apps with Ti Back up as I am writing this.
The only difference I did this time around was that after flashing Superwipe, I DID NOT flash the optimizer tool.
In all my other attempts, whether with TWRP or CWM, I was also flashing the optimizer after flashing Superwipe. Don't know if that was the actual cause or not with the install, but that was the ONLY step I did not do this time around.
From what I read, the optimizer is suppose to make the rom run faster because of the ext 4 partition. So my question now that I have up and running is will NOT having it flashed have any significant results?
On another thought, I did flash the optimzer as needed when I re-flashed Synergy. Does this carry over to the new rom or was I suppose to do again also for Eternity?
In any matter, thank you to all who helped. I will run Eternity for a week or so and see how stable it is first before trying anything else.
EDITED NOTE: Perhaps it should also be noted that I did download the latest build of Eternity also beforing getting it flashed and finally getting it running. Build 180. The file I couldn't get running was build 155.
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
kyaj9 said:
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
Click to expand...
Click to collapse
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
cobraboy85 said:
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
Click to expand...
Click to collapse
cobraboy85 said:
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
Click to expand...
Click to collapse
Making sure I wiped out everything was the first priority I took. I did re-download the rom just to be sure it was a good download also.
Can't seem to get 3.5 version working propperly, but I did get 3.0 version up and running. Have had it for a couple days now with no issues so just gonna stick with that. Wanted to try out the sense 3.5 first, but the fact that there's no 4g support for it yet means I am probably better off with just using the 3.0 Sense.
Thanks for your help....
mahmutmuratdemir said:
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
Click to expand...
Click to collapse
Not familar with Black Rose....but if I am not mistaken, isn't that just a HBoot for the Nexus 1?
yes it is made for nexus one to flash higher andrid versions but i think it can be used in some other models for partitioning internal memory
Sent from my Nexus One using XDA App
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've spent about well over 8 hours fixing my issue of unable to mount /sdcard/ and it not recognizing my microsd card; researching, learning, trying this, trying that. After I got that fixed, now when I try to install SuperSU through TWRP 2.5 I get the message unable to mount /data.
I am stuck in bootloop for CM10 which was released in October 2012, using Hboot 1.5 S-ON
I don't mind formatting everything and losing data because I've already backed it up and formatted. My goal right now is to go back to completely stock rooted. I can't do anything since SuperSu won't install due to "unable to mount /data".
I am relatively a beginner; I read ONE thread here who had the same problem, but I couldn't understand if it was the same problem as mine or if there was an easier way or understand what to do.
http://forum.xda-developers.com/showthread.php?t=1838204
Try fastboot flashing and older version of twrp v2.3.1.0 and see if that helps click the link in my sig
bigdaddy619 said:
Try fastboot flashing and older version of twrp v2.3.1.0 and see if that helps click the link in my sig
Click to expand...
Click to collapse
I somehow got extremely lucky. I had just downloaded your twrp zip and wanted to try SuperSU one more time....so in TWRP 2.5,
My Steps:
Tried to install SuperSu -- Failed due to /data and /sdcard again
I went to Mount -> Mount USB Storage
In windows open Computer -> Right click phone storage -> Quick Format FAT32
Immediately back to Mount and click Data & Internal Storage to mount
Adb push Supersu.zip to /sdcard
Install SuperSu.zip --- Successful!!!
It seems on every reboot I have to keep formatting my internal storage, but maybe I can google a fix for that. First I'm going to try RUU for HBoot 1.5 to see if that fixes it.
Thank you for your help so far; I have low hopes for RUU working on my first attempt since everything has been not working every time I've tried to fix it. I've actually been using no external SDcard or Internal SDcard (they wouldn't mount) for going on 4 months now since I tried to upgrade to a different CM version.....of course tonight was the night I tried to fix it and I have visiting family coming in tomorrow, so I need to make my phone useable.
Glad you got it
Oh yea S-OFF that mo-fo
bigdaddy619 said:
Glad you got it
Oh yea S-OFF that mo-fo
Click to expand...
Click to collapse
That's the plan stan...but after I get a working RUU. S-OFF is so much easier than it was less than a year ago it seems.
RUU isn't finding my phone on this PC; even HTC Sync manager isn't finding the phone, I've tried every driver I can find. I guess I'll try on my laptop; if it's not 1 thing, it's another.
metroins said:
That's the plan stan...but after I get a working RUU. S-OFF is so much easier than it was less than a year ago it seems.
RUU isn't finding my phone on this PC; even HTC Sync manager isn't finding the phone, I've tried every driver I can find. I guess I'll try on my laptop; if it's not 1 thing, it's another.
Click to expand...
Click to collapse
Try rebooting your PC with the phone plugged in it has helped others (I have never tried it though) so go with your gut
or try this http://forum.xda-developers.com/showpost.php?p=40674775&postcount=31
bigdaddy619 said:
Try rebooting your PC with the phone plugged in it has helped others (I have never tried it though) so go with your gut
or try this http://forum.xda-developers.com/showpost.php?p=40674775&postcount=31
Click to expand...
Click to collapse
Finally done at 3am:
Phone is S-Off
Phone is back to basically stock via VipeRUU
Phone is activated
Phone works
Plans for future:
Root tomorrow, not sure if TWRP is gone, if so add TWRP
Possibly switch to another Sense based rom, but close to stock
Maybe switch to Viperrom since I'm S-Off now
Problems ran into switching back with RUU:
All of the ones listed above
Phone was not activated once I was S-Off
Phone had more issues connecting to adb
Fixes to some problems:
Phone activation fixed by using Sense based rom -- probably could've called Sprint Customer Service
Adb drivers worked when I uninstalled, rebooted, and reinstalled using drivers from RUU uploaded by above poster Bigdaddy
http://d-h.st/users/BigDaddy619
Multiple tries for hours and lots of learning
I even tried to use adb through my fiances mac, but it wouldn't recognize adb....I think this was more of an issue with the rom maybe, dunno?!? My phone hadn't been completely updated since October and I think that was a beta
Night Night; thanks for your help sir, if you have any suggestions of stable roms I'm willing to try them out again, I think using a beta rom for so long coupled with no SDcard access taught me to appreciate the minor things such as: Working 4g, Working Wifi, Working Camera, Downloading stuff, No nag screens upon bootup, No random shutoffs etc. etc.
I like fixing things even if it's a hassle, but I think I need some hassle-free time easy to use stableness.
What did you do to fix the SD issue, I'm having the same issue with SD
Sent from my EVO using xda premium
Daughter handed me her phone today and said it "turned off and would not turn back on"... I could use some help figuring out what went wrong and how to fix it. I have flashed many roms, built a few from source, installed recoveries, rooted devices, etc. Though not a complete noob, I do have no formal training on this stuff and consider myself a novice compared to many here at XDA.
The phone was unlocked and rooted using Hasoon2000's HTC Rezound All In One Tool Kit about 1 month ago...
The rom that was fully functional for the past month, until today, is Liquidsmooth JB v2.9 Official vigor. It has worked exceptionally for her, until today. AT this point, if you pull the battery and then put it back in - it will boot to a white HTC screen for a few seconds and then go BSOD indefinitely. The only way to get any action after that is to pull the battery and try again... You can use the power & volume down to get into fastboot (if I pull out the external sd card) or into recovery (if I leave the external sd card in place).
Here's what the status on the fastboot screen shows:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Here's where I'm stuck at trying to get it back up and running - I do not think it is hard bricked:
1) I can boot into recovery and was able to open TWRP 2.5.0.0 and move around in it. However, it seemed to be saying there is no internal memory on the phone (cant mount or open) cache, data, system, sdcard (internal), NO ROM. I can not wipe any of the above partitions or format either...but it does see everything on the external sd card, though you can't flash anything to the internal sdcard or system, etc... Therefore, I decided to try another recovery, so...
2) Eventually I figured out how to fastboot flash a new recovery (after lots of reading here on several forums) and managed to get CWM Touch v6.0.3.6 Installed... it also does not see the system, cache, data, sdcard (internal)... but it does see my external sd card, as did TWRP. Again, no flashing to internal memory or formatting of the aforementioned partitions...
3) I have tried to fastboot flash boot.img from the aforementioned rom - fastboot flash boot boot.img - which appears to work, yet there is no change in status after rebooting or pulling the battery. Same problems exist...
4) I have tried fastboot flashing the RUU - fastboot flash ruu radio.img - appeared to do something, but still no change in status...
5) I have tried fastboot flashing the system image - fastboot flash img Liquid.zip (I changed the name of the file in an act of desperation trying various methods I read about online) - appeared to do something, but still no change in status...
6) If I boot into recovery, ADB can see the device and shows it in recovery mode. I have tried to ADB INSTALL the rom and boot.img - no luck there either (though I could be doing something wrong)...
7) If I boot into recovery, my windows 8 computer sees the external sd card of the device if I mount it as a USB MASS STORAGE device, but does not see the internal sdcard.
8) I have tried using Hasoon2000's tool to do various things and had no luck with making any more progress than using fastboot or adb.
9) I have tried to fastboot boot several different recoveries, but could not get any of them to boot up... though the process looked like it was working and rebooted - and just stuck at the white HTC screen...
I have been hacking away at this phone for about 7 hours now, reading forums, trying many things (some of which are listed above), and I've run out of ideas...
If anyone has any experience with this situation and knows of a positive solution that does not involve me flushing this thing down the toilet, I'd be really appreciative of your detailed advice. Though I have some basic experience, I can get lost quickly if you skip the details in any suggested solutions.
I appreciate any help or advice you may have to offer. I'm not thinking it's bricked - I just don't know enough to have the solution and have been reading for hours... getting a bit delirious at this point.
Thanks for you time...
It honestly sounds like some partitions are corrupt or damaged. Try using amon ra and see if it can see the internal partitions, if it can, format ext3 then ext4. Fstrim can corrupt the partition and amon ra can fix that.
If that doesn't work, you might be SOL as there is no full ruu for global OTA at the moment which may be your last resort. If you are on the recent OTA, which by your hboot, sound like it, you'd need S-off to RUU.
Sent from my Infected Rezound using xda app-developers app
Its deffinately not bricked...being able to boot to bootloader is a good thing...But as Uzephi said your best bet is to S-Off to make any further progress...that way it makes it easier to do things...fstrim especially used by LagFix app has caused this error in the past and what Uzephi said i will second to...in recovery you can try converting from ext4 to ext3 and back to ext4 and try wiping the internal within the recovery and that may fix it...if it doesnt there is a few fastboot and adb command tricks for formatting...however with s-off downgrading or upgrading the ruu is possible which may fix it also...i ran into this error once actually shortly after i modded my rezound the first time while it still only had sense...luckily i s-offed and was able to throw a few tricks at it
Guys, THANK YOU both for throwing some ideas at me... I will try as you both suggested and give an update once I'm done.
I will see if I can figure out how to s-off this thing... Then,
I will fastboot flash amonra and see if I can reformat internal with it.
If neither work, I will research adb and fastboot reformatting the internal memory.
Thanks again... This give me some more things to work on today. I will keep you posted.
Sent from my GT-I9505G using xda premium
still stuck...
So, I have spent the better part of my day working on this phone and still no luck...
From what I can tell reading various posts through the forums, I can't do the s-off thing without having the stock ruu installed... (If I'm understanding things correctly, which it is entirely possible I'm missing something obvious here...) I also run Ubuntu 12.04 on my computer in a 64bit virtualbox environment (windows 8 64 bit is my native os)- which 64 bit virtual Ubuntu seems to not be compatible with doing s-off.
I also can't get amon ra to install via fastboot flash or fastboot boot - again, entirely possible I'm missing something obvious.
I have gone over and over flashing and re-flashing twrp and cwm, trying various things to no avail... After being up late last night working on this and up early this morning, I'm officially throwing in the towel (for now). I'm really tired and a bit frustrated.
Of the dozen or so android devices that my family owns, I have rooted every one of them and installed roms, built a few fully functional roms from source, installed recoveries, etc... I have never run in to such a thing.
I still don't think it's bricked, but I'm feeling like the fix is above my head. If anyone thinks of something that I might be able to try, I will check back in a little later today. I need to get some work done around the house right now.
Thanks again for your help.
dandroid7 said:
So, I have spent the better part of my day working on this phone and still no luck...
From what I can tell reading various posts through the forums, I can't do the s-off thing without having the stock ruu installed... (If I'm understanding things correctly, which it is entirely possible I'm missing something obvious here...) I also run Ubuntu 12.04 on my computer in a 64bit virtualbox environment (windows 8 64 bit is my native os)- which 64 bit virtual Ubuntu seems to not be compatible with doing s-off.
I also can't get amon ra to install via fastboot flash or fastboot boot - again, entirely possible I'm missing something obvious.
I have gone over and over flashing and re-flashing twrp and cwm, trying various things to no avail... After being up late last night working on this and up early this morning, I'm officially throwing in the towel (for now). I'm really tired and a bit frustrated.
Of the dozen or so android devices that my family owns, I have rooted every one of them and installed roms, built a few fully functional roms from source, installed recoveries, etc... I have never run in to such a thing.
I still don't think it's bricked, but I'm feeling like the fix is above my head. If anyone thinks of something that I might be able to try, I will check back in a little later today. I need to get some work done around the house right now.
Thanks again for your help.
Click to expand...
Click to collapse
you can s-off straight from windows...i was actually able to do it on windows 7 64 bit. you can still find the latest ruu and flash it via a ph98 img file Hasoons toolkit has the appropriate files for the s-off tools...besides just flashing twrp did you use any of the format/convert/ or wipe sd card methods within them...also amon ra does have a ph98 img you can install through the bootloader itself....if worst comes to worst you can always send it to someone who can....not saying verizon but someone like me.who has done this before.
REV3NT3CH said:
you can s-off straight from windows...i was actually able to do it on windows 7 64 bit. you can still find the latest ruu and flash it via a ph98 img file Hasoons toolkit has the appropriate files for the s-off tools...besides just flashing twrp did you use any of the format/convert/ or wipe sd card methods within them...also amon ra does have a ph98 img you can install through the bootloader itself....if worst comes to worst you can always send it to someone who can....not saying verizon but someone like me.who has done this before.
Click to expand...
Click to collapse
I have an old beater pc that has windows 7 32 bit on it... I can try it from there. Am I supposed to just run s-off as juopuntubears instructions, eventhough I would be using a windows pc? Actually, I may still have a dual boot of Ubuntu 12.04 running on that machine... I'll have to take a look at it and see.
As for the latest RUU - I have downloaded "global_ota_radio_PH98IMG" that I found off the xda forums and it said it is the latest radio. I have tried to fastboot flash it and also to flash it through hasoons aiotk, neither seemed to get me functional. I also put it at the root of my sdcard, and though it appeared to be doing something when I boot into fastboot, I still have the same issues as I started with (nothing showing up on the internal memory). The version of Hasoons toolkit that I have does not appear to have any s-off features. I will have to look at older versions, I recall seeing something somewhere on xda with that feature.
As for TWRP and CWM, since they can't mount the internal partitions - they don't format or convert anything - since they fail to mount them.
I have also tried to install amon ra through the bootloader, to no avail.
I'm going to research the aiotk with s-off tools as well as check out my old pc to see if I can s-off through win7 or my dualboot Ubuntu (if it is still there)...
I do appreciate you helping point me in the right direction.
dandroid7 said:
I have an old beater pc that has windows 7 32 bit on it... I can try it from there. Am I supposed to just run s-off as juopuntubears instructions, eventhough I would be using a windows pc? Actually, I may still have a dual boot of Ubuntu 12.04 running on that machine... I'll have to take a look at it and see.
As for the latest RUU - I have downloaded "global_ota_radio_PH98IMG" that I found off the xda forums and it said it is the latest radio. I have tried to fastboot flash it and also to flash it through hasoons aiotk, neither seemed to get me functional. I also put it at the root of my sdcard, and though it appeared to be doing something when I boot into fastboot, I still have the same issues as I started with (nothing showing up on the internal memory). The version of Hasoons toolkit that I have does not appear to have any s-off features. I will have to look at older versions, I recall seeing something somewhere on xda with that feature.
As for TWRP and CWM, since they can't mount the internal partitions - they don't format or convert anything - since they fail to mount them.
I have also tried to install amon ra through the bootloader, to no avail.
I'm going to research the aiotk with s-off tools as well as check out my old pc to see if I can s-off through win7 or my dualboot Ubuntu (if it is still there)...
I do appreciate you helping point me in the right direction.
Click to expand...
Click to collapse
juopuntubears s-off method is meant for windows...for the latest ruu all you need to do is make sure it looks like PH98IMG.zip and place it to the root of your external sd card then run in bootloader and it will go through the process of install from there. I havent seen the other all in one kit in action but juopuntubears method is what i used....im pretty sure its somethjing very simple but i would load the ruu first n see where we go from there....my guess is your internal sd card was either in the middle of a reformat and was interrupted or if lagfix was used it caused the error or files were improperly deleted or the possibility of someone trying an s-off method on the s-on device....ive gotten the tampered message before and that usually means a improper hboot flash method was used
I have no clue what would have caused this issue, but my 13 year old daughter uses the phone as a WiFi only android device for Facebook, instagram, pinterest, etc... It is not even hooked up to a phone provider. She was sitting on the couch using it, her brothers were nearby using their tablets... One minute its working, the next minute it turns off...
The only thing I can think of is that I had installed goomanager when I unlocked, rooted it, and flashed a recovery and ROM. I'm wondering if she may have gotten a notice of an update for her rom or gapps through goomanager and let it start the update process without knowing what was going on... If she stopped it in the process of an update, I could see this happening somehow... I don't use goomanager much, so I'm not even sure if what I'm saying is possible?
I have a long week ahead of me with work... Not sure how much I will get to this until next weekend. Hopefully I can give it a bit of time in the evenings... But I have some extra training to do this week...
Thanks again. I will update this thread once I have taken additional steps. I do really appreciate your help.
Sent from my GT-I9505G using xda premium
dandroid7 said:
I have no clue what would have caused this issue, but my 13 year old daughter uses the phone as a WiFi only android device for Facebook, instagram, pinterest, etc... It is not even hooked up to a phone provider. She was sitting on the couch using it, her brothers were nearby using their tablets... One minute its working, the next minute it turns off...
The only thing I can think of is that I had installed goomanager when I unlocked, rooted it, and flashed a recovery and ROM. I'm wondering if she may have gotten a notice of an update for her rom or gapps through goomanager and let it start the update process without knowing what was going on... If she stopped it in the process of an update, I could see this happening somehow... I don't use goomanager much, so I'm not even sure if what I'm saying is possible?
I have a long week ahead of me with work... Not sure how much I will get to this until next weekend. Hopefully I can give it a bit of time in the evenings... But I have some extra training to do this week...
Thanks again. I will update this thread once I have taken additional steps. I do really appreciate your help.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Ya that may of done it...it is a possibility....again if all else fails someone can work on it for you....me personally id do it for you free of charge and you can trust me...i hate seeing people without and to be honest mine was completely hard bricked to no return and Neo has done me a great deed of help so im passing along the karma...but by the sounds of it yours isnt hard bricked which i know is fixable
10-4... I may take you up on your offer at some point THANK YOU for the kind offer.
I'm pretty stubborn... I may figure this out yet. S-off seems like my next conquest to overcome. Fortunately this isn't my work phone or anything, so im less stressed about having an immediate fix. My daughter will survive without it...
As well, I still don't feel like its hard bricked, so I know there is a solution out there to resurrect it from the dead. I just have to learn how to do it. That's what I love about android and the community of great people out there to learn from.
My line of work is construction management... But I'm an android ninja in training at home These android challenges cause me to learn and grow in new ways. Critical thinking, logic, problem analysis... Its all part of learning android. I enjoy the challenge and opportunity to learn from people like yourself who are willing to teach people like me, who would otherwise have no way to learn a thing like android.
Thanks again. Time to crash for the night....
Sent from my GT-I9505G using xda premium
dandroid7 said:
10-4... I may take you up on your offer at some point THANK YOU for the kind offer.
I'm pretty stubborn... I may figure this out yet. S-off seems like my next conquest to overcome. Fortunately this isn't my work phone or anything, so im less stressed about having an immediate fix. My daughter will survive without it...
As well, I still don't feel like its hard bricked, so I know there is a solution out there to resurrect it from the dead. I just have to learn how to do it. That's what I love about android and the community of great people out there to learn from.
My line of work is construction management... But I'm an android ninja in training at home These android challenges cause me to learn and grow in new ways. Critical thinking, logic, problem analysis... Its all part of learning android. I enjoy the challenge and opportunity to learn from people like yourself who are willing to teach people like me, who would otherwise have no way to learn a thing like android.
Thanks again. Time to crash for the night....
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
well your internal memory is borked but phone isnt bricked...hard bricked is when your phone wont even boot to the bootloader but reads as a certain different device in device manager...ill look into many other ways to fix this for you and i do hear you on being stubborn...im the same way when it comes to this sorta stuff and push myself to learn more....great devs learn and come from that same influence and drive to do so
Can you restore your partitions? Or can you not because you can't format them? If you can't, I suggest just flashing a stock RUU from you bootloader, being very careful though, you don't wanna get bricked. From there you can just flash your recovery and restore what you can, hopefully. Do you want a link to the RUU?
Sent from my ADR6425LVW running EclipticRezRavampedV9 (Lunar Kernel) using xda app-developers app.
Because I'm s-on right now, I don't believe I can flash an ruu, can I? I'm pretty sure I can't go backwards to an earlier ruu being s-on. Also I thought I read there is not a full ruu available of the current one I have on the phone. I could be wrong to all of the above, but I thought I read this somewhere recently.
I have been reading about s-off, but have not had time to do it. I also am unclear if it is even possible to do s-off in the current state the phone is in.
I can't format because it won't mount any internal partitions. I dont know how to restore a partition... But if the internal memory won't mount, I'm not sure if a restore would work.
I'm willing to try stuff, just not today... Had a reeeaaally long day. If you want to send me a link for an ruu or have any other ideas, I am interested in getting past this issue. But it may not be until this weekend that I have time to get back to it.
Thanks.
Sent from my GT-I9505G using xda premium
dandroid7 said:
Because I'm s-on right now, I don't believe I can flash an ruu, can I? I'm pretty sure I can't go backwards to an earlier ruu being s-on. Also I thought I read there is not a full ruu available of the current one I have on the phone. I could be wrong to all of the above, but I thought I read this somewhere recently.
I have been reading about s-off, but have not had time to do it. I also am unclear if it is even possible to do s-off in the current state the phone is in.
I can't format because it won't mount any internal partitions. I dont know how to restore a partition... But if the internal memory won't mount, I'm not sure if a restore would work.
I'm willing to try stuff, just not today... Had a reeeaaally long day. If you want to send me a link for an ruu or have any other ideas, I am interested in getting past this issue. But it may not be until this weekend that I have time to get back to it.
Thanks.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
if your on hboot 2.28 that is the most recent up to date leaked radios...however the most up to date full ruu comes with 2.27...if you are s-off its kind of hard...a user posted in the threads earlier that he completely removed his external card and his windows was able to detect the 2 internal partitions...and he formatted the 10.5 gb fartition and worked flawless...if all else fails...how well do you know about using linux and or a linux based rescue disk for partitions
Holy cow - its alive!!!
THANKS to everyone who has been helping point me in the right direction.
I'm now close to functional again... bootlooping at the splash screen for a rom is much better than no internal partitions on the device...
I relocked the bootloader using hasoon2000s all in one kit...
After doing much research, I was finally able to flash a PH98IMG file that someone had posted here on the xda forum that was here (said it works for S-on):
http://forum.xda-developers.com/showthread.php?t=2250494
http://d-h.st/BIj - had to rename the file to PH98IMG and flash from sd card in bootloader/hboot.
Once I did that, I unlocked the phone again using hasoon2000s all in one kit, then installed amon ra recovery.
I flashed a new rom via amon ra recovery.
I then fastboot flash boot boot.img that I pulled from the new rom
I now see paritions on the internal memory when I'm in recovery, and the splash screen of the new rom is bootlooping... I'm soooo close to being functional again.
I'll let you know when I get passed the bootloop...
dandroid7 said:
THANKS to everyone who has been helping point me in the right direction.
I'm now close to functional again... bootlooping at the splash screen for a rom is much better than no internal partitions on the device...
I relocked the bootloader using hasoon2000s all in one kit...
After doing much research, I was finally able to flash a PH98IMG file that someone had posted here on the xda forum that was here (said it works for S-on):
http://forum.xda-developers.com/showthread.php?t=2250494
http://d-h.st/BIj - had to rename the file to PH98IMG and flash from sd card in bootloader/hboot.
Once I did that, I unlocked the phone again using hasoon2000s all in one kit, then installed amon ra recovery.
I flashed a new rom via amon ra recovery.
I then fastboot flash boot boot.img that I pulled from the new rom
I now see paritions on the internal memory when I'm in recovery, and the splash screen of the new rom is bootlooping... I'm soooo close to being functional again.
I'll let you know when I get passed the bootloop...
Click to expand...
Click to collapse
Use CWM or TWRP for flashing. Amon ra is known to have flashing/wiping issues. And did you clean wipe? Even though you have RUU you still need to wipe.
Sent from my Infected Rezound using xda app-developers app
Thanks for the info... I never used amon ra before, I read about it being buggy.
I actually wiped everything, repartitioned it, then flashed ROM with amon ra, then fastboot flashed boot image.
I have to get up a 4am... So I'm calling it quits for tonight. I have another long day tomorrow... I'm feeling like I'm in the home stretch now. Tomorrow I will switch back to twrp 2.6 or cwm touch 6 and see what happens. I will do a full wipe, flash ROM, then fastboot flash the boot image.
Fingers crossed...
Thanks again. I'm always learning here on xda and other android forums. I really appreciate your kindness in pointing me in the right direction and giving me ideas of things to try. I did a ton of reading to get this one figured out as far as I have, though I'm still not done yet.
I will touch base again once I do the things above.
Sent from my GT-I9505G using xda premium
dandroid7 said:
Thanks for the info... I never used amon ra before, I red about it being buggy.
I actually wiped everything, repartitioned it, then flashed ROM with am on ra, the fastboot flashed boot image.
I have to get up a 4am... So I'm calling it quits for tonight. I have another long day tomorrow... I'm feeling like I'm in the home stretch now. Tomorrow I will switch back to twrp 2.6 or cwm touch 6 and see what happens. I will do a full wipe, flash ROM, then fastboot flash the boot image.
Fingers crossed...
Thanks again. I'm always learning here on xda and other android forums. I really appreciate your kindness in pointing me in the right direction and giving me ideas of things to try. I did a ton of reading to get this one figured out as far as I have, though I'm still not done yet.
I will touch base again once I do the things above.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Hey i may have found a fix...another user had the same issue and fixed it by using TWRP and wiping emmc first. Once he did that he wiped the internal sd card. Should then work... Format afterwards just to be safe.
K good to know. Have a great night... I will give it a rip tomorrow... I'm pretty stoked to have gotten this far today.
Sent from my GT-I9505G using xda premium