Related
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.
Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774
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
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
OK, no one is helping....ive tried some things, learned a few but this seems to be over my head....can anyone really help ? I managed to get past the white HTC screen by fastboot flashing a new recovery (philz then dees troy version of twrp)....I got a bootable commotio build....I also flashbooted 2.22.401.5, i thought it had fixed everything but in recovery i am getting the following errors.....
unable to mount /cache
failed to wipe dalvik
did I somehow mess up my partitions ? I need to wipe dalvik cache and cache in order to get a working rom on this damn phone.....
The issue has been fixed....
jxcorex28 said:
The issue has been fixed....
Click to expand...
Click to collapse
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
redpoint73 said:
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
Click to expand...
Click to collapse
Im not exactly sure what went wrong in the first place. I never pulled a logcat (from an app or through adp) since the problem no longer exists it looks like I never will unless I go through another similar thing. I wish I did know because it's killing me to know. I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
I have flashed atleast 500 times over a 8 year period on 4 different android phones, and Ive never once experienced the problem I had 2 days ago. Ive had 2 HTC phones, although, the experience with basebands were similar they were actually very different in every aspect. I had a TMO HTC G1 back in the day ( I had to learn how to do everything back when scripts or programs werent doing the grunt work (root)...
I had a TWRP backup of beanstalk saved (so kiddies, do your backups) that is what saved my ass. I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
I actually had to repartition my computer's hard-drive and reinstall windows 7 home edition, so I had to start over with practically everything...Im not going to use toolkits anymore. As you said earlier, it's just the easy way out. You wont learn anything about how to use ADB or Fastboot (although I applaud the one's who make the scripts or toolkits for those of us on the go).....
P.S.......If I can ever manage to break away from my dueling school schedule and my other priorities in life I plan on learning more about starting from the ground up and building roms, and not just throwing a few things together in the kitchen.....
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
jxcorex28 said:
I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
Click to expand...
Click to collapse
Yeah, I'm going to pull back on my previous statement that "3.28 will likely cause reception issues on AT&T's network" to instead say "may cause issues". And feel free to try it at your own discretion.
Reason being, I've seen maybe 3 reports now of this firmware working ok on AT&T, and no reports to the contrary so far.
Although, when folks tried the 2.22.401 "international" firmware on AT&T, there were several (even numerous reports) of signal issues, even NO SIGNAL. No reports of this so far on 3.28, so I'll be cautiously optimistic for the time being (until I see reports otherwise). Haven't personally tried it, and not sure I will as I don't really have time ATM to mess around with the possibility of signal issues or no signal.
jxcorex28 said:
I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
Click to expand...
Click to collapse
Did you try fastboot erase cache before trying to re-install recovery, or a different recovery? I've seen this simple step alleviate some pretty drastic issues with recovery.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
jxcorex28 said:
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
Click to expand...
Click to collapse
I can't speak personally, I'm not a Linux PC person. But my friends that are, seem to split among various distros: Ubuntu, Kubuntu, and Arch. One friend that is a particular Linux aficionado is on Arch, and said he was very happy with it.
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
jxcorex28 said:
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
Click to expand...
Click to collapse
Id highly rrecommend Linux Mint 17 Qiana MATE Edition .I use it with Windows 7. It is my favorite Linux OS. Not to mention that its perfect for Linux beginners.
That info would of been great a few days ago, but my laptop is screwed up now. Earlier I tried logging on,and couldn't because of some kind of remote error near the password field box on win7 HE...So I tried a system restore,and it failed so I f8 into recovery options and try using HP Recovery..everything went smooth into the first boot. I ended up getting a recovery installation incomplete and a 205 UIA failed 3 times. I believe my laptops recovery partition is corrupt,and I don't have a HP recovery disk, a win7 recovery DVD / Win7 recovery USB stick... I found what I need on HPs website, but its 30 bucks...BestBuy GS wants to charge me $69.99 for a diagnostics test and a retail version of win7 cost like 130
Its a 2011 HP Pavilion G-series laptop with windows 7 Home edition. What makes matters worse is I just partitioned the system a few weeks ago by using the recovery option HP makes for their devices...
Everything was great til about 10pm tonight...FML...now I actually gotta go to school to do my damn school work
jxcorex28 said:
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
Click to expand...
Click to collapse
I had that exact same issue yesterday... Twrp couldn't wipe anything and eventually kept rebooting after 20 or 30 sec in recovery.
I had to download the 1.58 RUU and run that, then flash Twrp back, reroot, then restore one of my backups from earlier in the day.
As far as fw goes, I had updated to 2.22.401.4, had that for a couple days, then updated to the 3.xx fw to install arhd 20.3. I liked it, but decided I love my dirty unicorns rom so decided to go back to the 2.xx fw. I tried to flash renovate 4.5.0, and that's when all the issues in twrp started. From what you're saying, it sounds like the issue could be caused from the fw updates.
How did you end up restoring your backup when they issue happened? I tried to restore mine with fastboot, but it was compressed and I couldn't extract the img files from the win files
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
jxcorex28 said:
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
Click to expand...
Click to collapse
I got it from skulldreamz thread on flashing fw by renaming it and putting it on root of ext SD card
Did you look into the contents of that zip to see if there was a recovery.img or boot.img file ? Those files usually overwrite the custom recovery (ie...TWRP or CWM). There are two ways to correct those red error messages you get in TWRP...
1. by flashing partition-fixer.zip (I have a copy if you need it)
2. By using a terminal emulator,and typing this command...
mke2fs /dev/block/mmcblk0p46
I believe this command is essentially what's included in the flashable partition fixer ( I haven't actually taken a look in that zip,so I could be wrong)...
I haven't had any problems as of late...either I'm starting to get back in the hang of dealing with HTC devices or I'm just lucky...
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
jxcorex28 said:
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
Click to expand...
Click to collapse
With the ones I got from skulldreamz' thread, I believe they were modified bc I didn't have to flash a custom recovery again after I flashed the fw. I never fastboot flashed them, I've always just renamed it 0P6BIMG.zip and put it on the root of the ext SD card
That's probably because skull removes those 2 files before uploading for download. I'm not sure if he does that for every zip....