Unlocked, rooted and S-ON. I can get into Fastboot, and I'm trying to get into recovery. I can't. It just reboots to the white HTC screen and sits there. Same with Factory Reset.
Everything I do with Hasoon's kit fails. Either the device is never found, or I get this-
sending 'recovery' (6346 KB)... FAILED (status malformed (1 bytes))
I simply can't get into recovery.
I've taken zip files of RUU's, recoveries, kernels and everything, renamed them to PH85IMG.zip and tried loading. They just go through the loader icon on the top left, then returns back to fastboot. I'm just not getting nowhere. I've been on the forums searching for several hours now.
HBOOT recognizes when USB is plugged in. But the phone is never found when I run commands from the toolkit.
I put my SIM in my old iPhone2 while I try to get this working. It's a horrible phone!
What else should I try?
RobsSXT said:
Unlocked, rooted and S-ON. I can get into Fastboot, and I'm trying to get into recovery. I can't. It just reboots to the white HTC screen and sits there. Same with Factory Reset.
Everything I do with Hasoon's kit fails. Either the device is never found, or I get this-
sending 'recovery' (6346 KB)... FAILED (status malformed (1 bytes))
I simply can't get into recovery.
I've taken zip files of RUU's, recoveries, kernels and everything, renamed them to PH85IMG.zip and tried loading. They just go through the loader icon on the top left, then returns back to fastboot. I'm just not getting nowhere. I've been on the forums searching for several hours now.
HBOOT recognizes when USB is plugged in. But the phone is never found when I run commands from the toolkit.
I put my SIM in my old iPhone2 while I try to get this working. It's a horrible phone!
What else should I try?
Click to expand...
Click to collapse
The toolkit cannot send commands through hboot, only fastboot. You have to boot into hboot and then select the fastboot option
Sent from my Amaze using xda app-developers app
Keylogger_0 said:
The toolkit cannot send commands through hboot, only fastboot. You have to boot into hboot and then select the fastboot option
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
Yes you have to be in fast boot in order to use hansoons tool kit... And yet to flash your recovery again (I suggest 4ext) then use the toolkit to boot into recovery using the shortcut commands
Sent from my HTC Ruby using xda premium
Keylogger_0 said:
The toolkit cannot send commands through hboot, only fastboot. You have to boot into hboot and then select the fastboot option
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
Awesome, thanks. I don't remember having this much trouble last spring when I rooted and unlocked this phone. It went really smooth.
I'm having a really hard time right now with it. I can't get any OS to load. I can load Recovery, but then 4EXT won't mount SD card.
Anyone see this before?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I can get myself out of this mess, I don't think I'm going to hack my phones anymore. I'm not on top of it enough.
RobsSXT said:
Awesome, thanks. I don't remember having this much trouble last spring when I rooted and unlocked this phone. It went really smooth.
I'm having a really hard time right now with it. I can't get any OS to load. I can load Recovery, but then 4EXT won't mount SD card.
Anyone see this before?
If I can get myself out of this mess, I don't think I'm going to hack my phones anymore. I'm not on top of it enough.
Click to expand...
Click to collapse
Will it let u format the internal sd?
sent from my
NRGized amaze
powered by Faux
aj_2423 said:
Will it let u format the internal sd?
Click to expand...
Click to collapse
No, on that screen I just posted it- it shuts down right there (I took that a millisecond before it shut down). Then it reboots to the white screen where it just hangs.
EDIT
I got this working to this point. Just dealing with the new issue-
Error mounting /internal_sdcard!
Searching forums now...........
RobsSXT said:
No, on that screen I just posted it- it shuts down right there (I took that a millisecond before it shut down). Then it reboots to the white screen where it just hangs.
EDIT
I got this working to this point. Just dealing with the new issue-
Error mounting /internal_sdcard!
Searching forums now...........
Click to expand...
Click to collapse
Do you know how to use adb? Well, if not, you're gonna need to.
boot into recovery and WHILE it's loading, input this command in the command prompt window EXACTLY as it is presented! Meaning that if a letter is capitalized, you need to do so too. For best results, I recommend copying the command in its entirety and paste it in the prompt.
The command is as follows:
adb shell /sbin/newfs_msdos -F 32 -L INT_SD -c 64 /dev/block/mmcblk0p36
It should spit out some stuff, that is usually normal, and then in the prompt, also type in:
adb reboot-recovery
after that, your woes should be gone.
EDIT: You should, however, reinstall whatever ROM you were using. This trick only fixes the internal SDCard.
Keylogger_0 said:
Do you know how to use adb? Well, if not, you're gonna need to.
Click to expand...
Click to collapse
Thanks. I got familiar with ADB. I put in your commands in the command prompt, and not only were your instructions easy to read and follow, but it worked. My SD card is now readable. I also cleaned all my caches and re-partitioned the card. 4EXT is working 100% and all is well.
I downloaded the Fourth Bar: Infusion ROM and installed it through the 4EXT. It seemed to work- I was provided with several options to choose from in terms of defaults (kernel, boot animation, launcher, camera, lockscreen, etc), however the actual install happened way too fast. I left all of the options as default. Before I knew it, the install was done and rebooting. However, it went back to the white screen where it sat there and didn't budge. I left it for over 10 minutes.
I have tried both the stock kernel and the Faux kernel, neither make a difference.
RobsSXT said:
Thanks. I got familiar with ADB. I put in your commands in the command prompt, and not only were your instructions easy to read and follow, but it worked. My SD card is now readable. I also cleaned all my caches and re-partitioned the card. 4EXT is working 100% and all is well.
I downloaded the Fourth Bar: Infusion ROM and installed it through the 4EXT. It seemed to work- I was provided with several options to choose from in terms of defaults (kernel, boot animation, launcher, camera, lockscreen, etc), however the actual install happened way too fast. I left all of the options as default. Before I knew it, the install was done and rebooting. However, it went back to the white screen where it sat there and didn't budge. I left it for over 10 minutes.
I have tried both the stock kernel and the Faux kernel, neither make a difference.
Click to expand...
Click to collapse
You may have to mount the /data and /system partitions in recovery as writable
Sent from my Amaze using xda app-developers app
Keylogger_0 said:
You may have to mount the /data and /system partitions in recovery as writable
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
Good idea. Here's what I did.
In Mounts | Storage I have /data, /internal/sdcard, /sdcard plus others.
When I load into Mounts| Storage, they are ALL unmounted except /cache. So I go and mount them all.
Install the OS from .zip and it does it's thing.
Reboot, and hangs at white screen.
OR
Don't reboot, and go back to Mounts | Storage, and /sdcard needs to be mounted again.
If I reboot, all need to be mounted again except for /cache.
I doing some searches, I read that maybe my SD card needs formatting, or there's a format issue. I have run a few formats of my card and checked it's health, and it seems okay.
RobsSXT said:
Good idea. Here's what I did.
In Mounts | Storage I have /data, /internal/sdcard, /sdcard plus others.
When I load into Mounts| Storage, they are ALL unmounted except /cache. So I go and mount them all.
Install the OS from .zip and it does it's thing.
Reboot, and hangs at white screen.
OR
Don't reboot, and go back to Mounts | Storage, and /sdcard needs to be mounted again.
If I reboot, all need to be mounted again except for /cache.
I doing some searches, I read that maybe my SD card needs formatting, or there's a format issue. I have run a few formats of my card and checked it's health, and it seems okay.
Click to expand...
Click to collapse
Another possibility is that the recovery got glitchy. Maybe reinstall 4EXT recovery and make sure the smart flash thing is enabled.
Sent from my Amaze using xda app-developers app
I got the OS to load. I ran all the format options in 4EXT (every option available).
When I rebooted, it loaded the OS.
Finally.
im having the similar problem but mine constantly reboots every 5 seconds is there any fix
Related
Hi
I'm trying to change my boot screen to a loading semi circle. I cannot remove bootanimation.zip from /system/media
when I cd to /sys.media and type "rm bootanimation.zip" it asks me with a ?
If I type Y and press enter it says cannot remove "bootanimation.zip":read only file.
what can I do to get rid of the stock skateboard bootscreen?
PS Before typing in any adb cmd's I am typing "su"
First trying doing:
adb remount
Then try your rm command.If the rm command does not work after that, you could try:
adb push bootanimation.zip /system/media/bootanimation.zip
adb reboot
If neither of those work, push it to /data/local. On KaosFroyo, I use this method.:
adb push bootanimation.zip /data/local/bootanimation.zip
adb reboot
synesthete said:
First trying doing:
adb remount
Then try your rm command.If the rm command does not work after that, you could try:
adb push bootanimation.zip /system/media/bootanimation.zip
adb reboot
If neither of those work, push it to /data/local. On KaosFroyo, I use this method.:
adb push bootanimation.zip /data/local
adb reboot
Click to expand...
Click to collapse
I would just adb push to /data/local. It should read from their first.
adb is just over some peoples heads, flashing a zip is easier.
he got his bootani on his phone using my flashable zip from the red cyanogen, he PM'd me
I love how supplying 1 thing to the community can have different uses, that's cool!
Ya that script is awesome. Though this post is about trying to get rid of the 3 skateboard dudes. Unless I'm mis understanding that boot screen and boot animation are the same thing?
Sent from my nonsensikal froyo using XDA App
shatterpoints said:
Ya that script is awesome. Though this post is about trying to get rid of the 3 skateboard dudes. Unless I'm mis understanding that boot screen and boot animation are the same thing?
Sent from my nonsensikal froyo using XDA App
Click to expand...
Click to collapse
Those are there to stay
Poopy. Oh well. Thanks again for the help
Sent from my nonsensikal froyo using XDA App
shatterpoints said:
Hi
I'm trying to change my boot screen to a loading semi circle. I cannot remove bootanimation.zip from /system/media
when I cd to /sys.media and type "rm bootanimation.zip" it asks me with a ?
If I type Y and press enter it says cannot remove "bootanimation.zip":read only file.
what can I do to get rid of the stock skateboard bootscreen?
PS Before typing in any adb cmd's I am typing "su"
Click to expand...
Click to collapse
You can use this to get replace the skateboarding droids -
It works beautifully with Eris, provided you follow directions
Here is the bootscreen I was using on my Eris before getting Fascinate.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
goldenstorm said:
You can use this to get replace the skateboarding droids -
It works beautifully with Eris, provided you follow directions
Here is the bootscreen I was using on my Eris before getting Fascinate.
Click to expand...
Click to collapse
but the little skateboard droids did nothing to you!!
Two words....root explorer.
Sent from my Droid Eris using XDA App
goldenstorm said:
You can use this to get replace the skateboarding droids -
It works beautifully with Eris, provided you follow directions
Here is the bootscreen I was using on my Eris before getting Fascinate.
I'm having a hard time with this. My eris is already rooted, I cannot flash to the splash1 partition, I only just get an "error cannot load <my file name>" in fast boot. I don't see any clear instructions to flash a different fastboot without re- rooting my phone?
*edit* I got it to want to flash accept now it says "FAILED <remote: not allow>"
*edit2* also I cannot get the s-off bootloader the only place it was available now says its not due to inactivity
Click to expand...
Click to collapse
Ok, now I'm confused. Are you trying to change the boot animation or the boot image? The boot animation is simple to change. Copy new bootanimation.zip to your sd card. Download root explorer, open it and select R/W . Navigate to the sd card and copy the new boot animation. Navigate to system/media and paste. It must be named bootanimation.zip.
If you want to change the boot image (first image you see at boot) that's a completely different process. Go here http://forum.xda-developers.com/archive/index.php/t-654042.html for a how to. I had a little trouble with this at first but got it to work. Scroll down and see my comment for a how to that worked for me.
Good luck!
Sent from my Droid Eris using XDA App
joshw0000 said:
Ok, now I'm confused. Are you trying to change the boot animation or the boot image? The boot animation is simple to change. Copy new bootanimation.zip to your sd card. Download root explorer, open it and select R/W . Navigate to the sd card and copy the new boot animation. Navigate to system/media and paste. It must be named bootanimation.zip.
If you want to change the boot image (first image you see at boot) that's a completely different process. Go here http://forum.xda-developers.com/archive/index.php/t-654042.html for a how to. I had a little trouble with this at first but got it to work. Scroll down and see my comment for a how to that worked for me.
Good luck!
Sent from my Droid Eris using XDA App
Click to expand...
Click to collapse
Yes this is it. But all of the required files are not available for download. From what I gather I have to completely wipe my phone to unlock my HBOOT.
My HBOOT is S=ON I want the S-OFF bootloader but cannot find complete instruction/files to do so.
I'm ready to pull my hair out. I followed those steps for engeneering hboot to the letter... 2wice and it did not work. When pb001 is done flashing it sits at the hboot screen and still reads S-ON and when I try to flash a recovery from there it says "waiting for device" and nothing ever happens because the hboot screen is asking me to flash pb001 even though I already did. Those instructions are spectacularly bad. Does anyone have clearer or better instructions?
All this has done is waste an hr of my time and its making me see red.
Are you using the steps from this post? I was a little challenging at first however I was able to do it (more than once), although I was sad the first time that I had to re-flash the rom I was using and set up the phone all over again.
I no longer have a eris, however I will do what I can to help if you haven't already got it working.
shatterpoints said:
I'm ready to pull my hair out. I followed those steps for engeneering hboot to the letter... 2wice and it did not work. When pb001 is done flashing it sits at the hboot screen and still reads S-ON and when I try to flash a recovery from there it says "waiting for device" and nothing ever happens because the hboot screen is asking me to flash pb001 even though I already did. Those instructions are spectacularly bad. Does anyone have clearer or better instructions?
All this has done is waste an hr of my time and its making me see red.
Click to expand...
Click to collapse
Honestly, I don't know much about that because I rooted with the old method. What method did you use? Perhaps you can unroot and root with the old method (using cmd prompts to push custom recovery).
Sent from my Droid Eris using XDA App
If you don't already have it, download Titanium from the market. It's a great tool for backing up and restoring your phone.
Sent from my Droid Eris using XDA App
joshw0000 said:
Honestly, I don't know much about that because I rooted with the old method. What method did you use? Perhaps you can unroot and root with the old method (using cmd prompts to push custom recovery).
Sent from my Droid Eris using XDA App
Click to expand...
Click to collapse
I rooted with Eris one click. It gives you Amon's ra and I have several custom roms downloaded + I have a couple nadroid backups. I just can't figure out the engineering boot loader.
Flashing PB00 does unroot the phone so I'm not sure where to go from here.
shatterpoints said:
I rooted with Eris one click. It gives you Amon's ra and I have several custom roms downloaded + I have a couple nadroid backups. I just can't figure out the engineering boot loader.
Flashing PB00 does unroot the phone so I'm not sure where to go from here.
Click to expand...
Click to collapse
I am assuming you are following the guide here, for me it was confusing at step 5 in the beginning. Did you flash the engtools or push the flash image? Personally I pushed the flash tool.
Step 6 is tricky, you have to be patient as it does take a while and best to do it with plugged in. If I remember right it I did the very last step (flashing recovery.img) before rebooting when it asked me if I wanted to restart.
I lost root after doing it, however 1 click from the market was my friend and savior. I booted into bootloader and verified I had 1.49.2000 s=off, so it was worth it in the end.
At what point is it not working for you?
goldenstorm said:
I am assuming you are following the guide here, for me it was confusing at step 5 in the beginning. Did you flash the engtools or push the flash image? Personally I pushed the flash tool.
Step 6 is tricky, you have to be patient as it does take a while and best to do it with plugged in. If I remember right it I did the very last step (flashing recovery.img) before rebooting when it asked me if I wanted to restart.
I lost root after doing it, however 1 click from the market was my friend and savior. I booted into bootloader and verified I had 1.49.2000 s=off, so it was worth it in the end.
At what point is it not working for you?
Click to expand...
Click to collapse
Yes I am following Jcase's steps. I also flashed the image. When it asks me to reboot the boot loader it reboots to fastboot and does not ask me to install pb00 unless I go to HBOOT. When I flash PB00 in HBOOT it does so ok, but then it check's the sd card and keeps asking me to flash pb00 even though I already did. While in this screen I cannot see the device in adb or fastboot and I cannot flash a recovery to it. So all I can do is yank the Batt and boot to a unrooted 2.1 eris....
I had my tablet running CM7 and I'm not sure what went wrong but I can't recover it. When I boot it I get this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So far I've tried Adam Outlers recovery method as well as trying to adb the partitions but I can't get the tablet to boot off an SD card.When I try to adb into the device I cannot see the device ID on the nook but I can see my Droid X2.
Anybody?
Sent from my MB870 using Tapatalk 2
I'm not a techie but I know some of the tablets will boot off of the SD card when the tablet is pulled in, the charger would work. Push the power and "N" at the same time.
Nikkiel
Sent from my Barnes & Noble Nook Tablet using xda premium
scuzzo500 said:
...
So far I've tried Adam Outlers recovery method as well as trying to adb the partitions but I can't get the tablet to boot off an SD card.
...
Click to expand...
Click to collapse
Most NT will boot off an SD card only from its power-off state and upon insertion of a powered USB cable.
Ok. I can now get the nook to boot into cmr, but not into Adams recovery. When I try to boot into Adams method all I get is a multitude of colors across the screen. I let it do its thing leaving it plugged in until the battery died, still no love. Anything else? I'm willing to pledge money (at least $10 but if I can get more together I will) to whomever gives me the solution. And offering the $$ is my way of saying I know this may take some effort and I want to say thanks to whoever puts in the time to help.
Sent from my MB870 using Tapatalk 2
I take it you have tried the super easy way with "repart.img" and it didn't work?
http://forum.xda-developers.com/showthread.php?t=1663836
scuzzo500 said:
Ok. I can now get the nook to boot into cmr, but not into Adams recovery. When I try to boot into Adams method all I get is a multitude of colors across the screen. I let it do its thing leaving it plugged in until the battery died, still no love. Anything else? I'm willing to pledge money (at least $10 but if I can get more together I will) to whomever gives me the solution. And offering the $$ is my way of saying I know this may take some effort and I want to say thanks to whoever puts in the time to help.
Click to expand...
Click to collapse
I think this method might solve your missing BCB problem. To execute it you'll need CWM on a bootable SDcard (which you can get from here if needed) and adb shell
on your PC/laptop.
I can boot cmw on an sd card, but I cannot mount boot data so I can reset my boot count. When I boot off the repart image I do get the screen that tells me it's installing new software but I never get a green check nor does it reboot, it just shuts down.
Sent from my MB870 using Tapatalk 2
only nook cable works
digixmax said:
Most NT will boot off an SD card only from its power-off state and upon insertion of a powered USB cable.
Click to expand...
Click to collapse
Even a normal usb cable does not work, only the one that came with the nook. Thanks, but wierd
Hm, my NT can boot off SD using any regular USB cable.
Any other ideas? I'm willing to try anything.
Sent from my MB870 using Tapatalk 2
scuzzo500 said:
I can boot cmw on an sd card, but I cannot mount boot data so I can reset my boot count. When I boot off the repart image I do get the screen that tells me it's installing new software but I never get a green check nor does it reboot, it just shuts down.
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
I get same thing in cwm I can't mount as card to redo partitions and when I do regard from as I get a red x. I am lost I have no more options to try. Wish there was a utility to rebuild patrons and return to stock like on my moto Droid bionic and razr
The locked bootloader the moto series has is nice for recovery. It keeps idiots like me from screwing up too bad. But I like having everything open.
Sent from my MB870 using Tapatalk 2
First off, what NT do you have 16G or 8G? This will determine the fix and if I can even offer up help.
Also, do you have a couple of sd cards to work with? One is fine, it just makes the process easier with two.
scuzzo500 said:
Any other ideas? I'm willing to try anything.
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Take a look at Ray Waldo's site http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
DavDoc said:
First off, what NT do you have 16G or 8G? This will determine the fix and if I can even offer up help.
Also, do you have a couple of sd cards to work with? One is fine, it just makes the process easier with two.
Click to expand...
Click to collapse
I have the 16 GB and I have 4 cards 2GB 4GB 8GB 16GB. I have done everything for the past 4days. I found a adb pusher utility that shows me everything on my nook through adb and I see the sdcards but when I click them they are empty. Try to mount in cwm and troughs me an error. Thanks for the help its my wife's nook. Look for that utility its quite nice.
ok perfect.
I am not in front of a computer right now to see what files they are, but I think you can get back to original stock with a two step flash. I am guessing the privious owner tried to factory reset without stock recovery.
Sent with my Dinc4G
scuzzo500 said:
Any other ideas? I'm willing to try anything.
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Also Adam's and repart.IMG methods can take several hours (not minutes) to complete. I would suggest running Adam's method overnight. Don't touch it. Just go to bed and check it in the morning. Plug in charger just in case. Report back in the morning after you wake up.
gowboy84 said:
I have the 16 GB and I have 4 cards 2GB 4GB 8GB 16GB. I have done everything for the past 4days. I found a adb pusher utility that shows me everything on my nook through adb and I see the sdcards but when I click them they are empty. Try to mount in cwm and troughs me an error. Thanks for the help its my wife's nook. Look for that utility its quite nice.
Click to expand...
Click to collapse
OK, I'm in front of a computer now.
Try this - I just ran this on my own device and it brings it back to stock 1.40. It may or may not work for you, but it is worth a try. It should replace your stock recovery and then allow you to run the acclaim.update.zip file from an SD card.
So first go to Succulent's post here http://forum.xda-developers.com/showthread.php?t=1545766 (ignore the subject of the thread, you just need the file in his repository) Scroll down and click on the link for Flash-Restore-Stock.zip. You will need to download the zip file by that name.
Once you have this zip file go into CWM and flash it. I only mention using two SD cards for this because the one I use for CWM only leaves ~15MB of space after setting it up. You will need more space than this.
Go ahead and reboot system. You will most likely be in a bootloop or worse - don't sweat. What you need next is to go to this link from AdamOutler http://forum.xda-developers.com/showthread.php?t=1402190 and download the file he has in the OP. This is the acclaim_update.zip
put this on the root of an SD card (don't put it in any folders) put it into your NT and turn the thing on. It should start a download process and put the original OS onto your device. After completing the process, you may not be out of the woods yet. You will most likely have to complete 8 failed boots or just try shutting your NT off and turning it back on holding the power and home button at the same time. This will initiate a factory reset and you will be home free back on stock operating system.
Good Luck
Edit: This was for the OP. Sorry Gowboy84, I got the two of you mixed up when you jumped into the thread answering a question I asked the OP. I don't think this will work for you. I noticed in another thread you flashed the 10 touch firmware. You may want to read up on all the "10 touch firmware" Posts, or get help in your own thread.
I have tried Adam's method several times across two SD card and with several d/ls of the file to make sure that I got a good copy and I can't even get the tablet to boot from the SD card with his method. I can get the repart.img method to boot, it runs for about 10 seconds and then it shuts down the nook. When I try to reboot I get nothing (again several d\ls and several cards). I can load CMW and boot into it from an SD card
but then I can't mount any drives when I get into CMW. I've used bn_142_factory_recovery.zip and no love there either.
And as a side note I just want to say thanks to everyone who has contributed to this thread. This is a $150 investment I've screwed up and just knowing that there's a glimmer of hope here from all of you means a lot to me.
@DaveDoc, I'm off work in 6 hours, I'll try and report back.
Help! I have accidentally erased everything from my HOX+ and now i have no OS and my device's internal memory will not be read by my pc. Is there any way i can get something back on there?
If you can get to bootloader, and I'm sure you can.. (holding volume down while turning the phone on)
You could start by flashing the appropriate recovery. (non att is here , and the att recovery is here )
Then reboot to recovery, and side mount the sd card, and dump a rom on there. (i had to format my sd card at this time using windows.. it's ok if you need to)
Be sure to extract the boot.img to flash in fastboot before you reboot or you'll bootloop (if you have no idea what i just typed, let me google that for you)
you'll need these three files: https://www.dropbox.com/sh/q5u67wv5jjbz2te/1dV9Voar26
This thread may help.
http://forum.xda-developers.com/showthread.php?t=2051032
Bear in mind that's for the att model just be cognizant to flash international files.
Sent from my HTC EVARE_UL using xda app-developers app
can"t load the rom please help
borg00 said:
can"t load the rom please help
Click to expand...
Click to collapse
you cannot be helped
no dice
i have already tried using adb sideload and i must be doing something wrong because it says "device not found"
pelucaz491 said:
i have already tried using adb sideload and i must be doing something wrong because it says "device not found"
Click to expand...
Click to collapse
I don't know where any instructions said that.
Did you get the recovery installed?
if so, you need to click here to MOUNT sd card.. at that time, CONNECT the phone to the computer with a usb cable and then put a rom on the SD card.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: i don't recommend the toolkit; it breeds ignorance.
The sideloading is not necessary. Just mount the SD, dump the rom, unmount the SD, and flash the rom.. then, when that's done, choose the reboot option in TWRP, reboot to bootloader, choose fastboot, and fastboot flash boot boot.img the boot.img you pulled out of the .zip from the rom you chose.
please excuse my ignorance and now that i have clicked MOUNT is something supposed to happen?
pelucaz491 said:
please excuse my ignorance and now that i have clicked MOUNT is something supposed to happen?
Click to expand...
Click to collapse
well, not on the phone. but, if you plug your phone into your computer, the SD card will magically pop up as storage on the computer. Just mount the SD, dump the rom, unmount the SD, and flash the rom.. then, when that's done, choose the reboot option in TWRP, reboot to bootloader, choose fastboot, and fastboot flash boot boot.img the boot.img you pulled out of the .zip from the rom you chose.
wdkingery said:
well, not on the phone. but, if you plug your phone into your computer, the SD card will magically pop up as storage on the computer. Just mount the SD, dump the rom, unmount the SD, and flash the rom.. then, when that's done, choose the reboot option in TWRP, reboot to bootloader, choose fastboot, and fastboot flash boot boot.img the boot.img you pulled out of the .zip from the rom you chose.
Click to expand...
Click to collapse
It does nothing on the computer either. No removable storage options or auto-play. however, HTC sync does come up.
did you go to my computer and make sure there's no extra storage on there that wasn't there a minute ago?
if there isn't, you have reached the end of my knowledge.
wdkingery said:
did you go to my computer and make sure there's no extra storage on there that wasn't there a minute ago?
if there isn't, you have reached the end of my knowledge.
Click to expand...
Click to collapse
yes i have. it does give a message "USB device not recognized" i have the drivers installed.
pelucaz491 said:
yes i have. it does give a message "USB device not recognized" i have the drivers installed.
Click to expand...
Click to collapse
I had a big driver fight when i first rooted my one x+.
only thing i can tell you is to press start button and type in device manager and hit enter.
if you see your phone with a yellow ! triangle.. you need to fix that.
make sure to disable antivirus software, and reboot after any driver installs.
also, i have seen a few posts where the USB cable was the problem; try a different one, or the one that came with the phone is preferred.
---------- Post added at 10:31 PM ---------- Previous post was at 10:25 PM ----------
also, i found this (it's for a one x but might work for you as well.. it looks promising)
I found this worked to get Win7 x64 to recognize the SD Card and ADB:
1. Uninstall the driver completely from the system (HTC MTP Device). This has to be done under the device properties. This should force the system to see a new device called "One" without a driver, under "Other Devices" in the Device Manager.
2. Install HTC Sync from http://www.htc.com/www/software/htc-sync/. Once installed, it has to update to the latest version. This is needed to install all additional drivers for SD Card access.
3. Latest HTC Drivers will be listed under C:\Program Files (x86)\HTC\HTC Driver\Driver Files
4. For ADB access, go to http://onexroot.com/one-x-root/how-to-unlock-bootloader-and-root-att-htc-one-xhtc-one-xl/ and download appropriate drivers for your Windows flavor. These are the ADB drivers. I only tested out the 64-bit drivers though as all my machines are 64-bit.
5. Download the zip, and extract. Remember the location of the files. Go into Device Manger, find "One" under "Other Devices" and Update Driver Software. Point to the new directory you made and install. The One X will now be listed in Device Manager as "My HTC" under "Android USB Devices"
6. To verify ADB, open a CMD prompt, point to Android directory and type in "adb devices". Your beautiful HTC One X should be listed.
don't give up pelucaz491. you are close.
You can't mount this phone's sd card from recovery because it is ext4, you have to use side load.
Sent from my HTC EVARE_UL using xda app-developers app
Someone with more experience has spoken. Maybe he can carry you the rest of the way; I tried.
If what he says is true, then I can no longer help, as I don't have experience with this issue. I only knew all that from my one X issues. Evidently what I was telling you is wrong for an x+.
GL
never.
mfpreach said:
You can't mount this phone's sd card from recovery because it is ext4, you have to use side load.
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
well as i said before, i have tried using that but i must have been doing something wrong. what are your ideas? im willing to try again.
pelucaz491 said:
Help! I have accidentally erased everything from my HOX+ and now i have no OS and my device's internal memory will not be read by my pc. Is there any way i can get something back on there?
Click to expand...
Click to collapse
If you have an ATT/Telus or INTL HOX+ then you can go to my TUT and get a rom back on your phone. My tut can be found here. I know it has already been mentioned in this thread but since people are trying to help out with the wrong info that is not intended for this device you might want to look at my tut and see if it will help you out.
Also, your phone is not bricked...
Cheers
Clonz said:
Can you give us anymore info? What carrier are you on...is the phone an att/telus or intl...what hboot are you running...
If you can provide more info we can more than likely help you out.
Cheers
Click to expand...
Click to collapse
of course
ATT
EVITARE_UL S-ON
UNLOCKED
HBOOT-1.32.0000
RADIO-SSD:1.09.55.17
Mistakenly erased everything including os from phone.
pelucaz491 said:
of course
ATT
EVITARE_UL S-ON
UNLOCKED
HBOOT-1.32.0000
RADIO-SSD:1.09.55.17
Mistakenly erased everything including os from phone.
Click to expand...
Click to collapse
Perfect...so I did the exact same thing with I unlocked my bootloader and put a custom recovery on...not realizing how the storage was setup I deleted my nandroid backup and everything else that was stock on the phone. So, you can definitely use my tut to get a rom back on...or you now have the choice to flash an RUU that has been provided by Football that is also listed in my tut.
If you have some specific questions for me or get stuck just let me know
Cheers
I had successfully flashed my phone and installed Cyanogenmod 11. After several weeks I decided to take my phone back to Stock Sense and in the process I messed up terribly. Somehow I erased everything off of my internal memory and the phone sits in the cyanogenmod bootloader. Apparently I had saved my backup to internal storage like an idiot and it is gone now. I do have an SD card accessible. The status is as follows:
1. Phone is unlocked
2. S-ON Status showing (not sure how to get it to S-Off but not sure if this is my biggest issue)
3. When the phone powers on it goes to the Cyanogenmod Boot Screen and the little blue guy staring at me stares at me with the spinning blue circle until the phone actually goes dead.
4. Once phone goes dead I can attain access to my bootloader by holding volume down and the power button and I can get into TWRP recovery.
5. I connect the phone to my PC and when I access by command prompt and type adb devices it shows the phone either in fastboot or recovery or sideload mode depending on where I am at in the accessible system.
6. I have loaded cyanogenmod 11 nightly on my external sd card and flashed it and it says successful but when I reboot the phone still remains locked on the bootscreen until it dies again.
7. I have tried sideloading the ROM and when I do that it tells me that it can not access internal storage or any type of storage and says it is using RAM for storage....not sure how that works but once the ROM has been sideloaded I can not find it.
Here is what I want....I simply want to be able to reinstall Sense 6 or Cyanogenmod 11 back onto my phone so it will work once again but I am lost. I have followed numerous how tos on the web and I am getting nowhere.
If anyone can help it would be greatly appreciated. Ask as many questions as needed and I will supply you with as detailed of an answer as I can.
Thanks in advance.
okay try this first and see if it gets at least cm11 working again...
1. Go and put cm11 on your external sdcard
2. boot into recovery mode
3. factory reset the device
4. manually wipe /system (this is needed under certain circumstances)
5. now flash cm11 and the gapps package
6. reboot
this should get cm11 back up and running for you at least. Now once cm11 is back up and running do the same thing with the sense rom that you were trying to go to. it should work.
EDIT: also, keep a copy of your nandroid backup on a computer somewhere that way if something like this happens again you dont loose your backup.
ziggy46 said:
okay try this first and see if it gets at least cm11 working again...
1. Go and put cm11 on your external sdcard
2. boot into recovery mode
3. factory reset the device
4. manually wipe /system (this is needed under certain circumstances)
5. now flash cm11 and the gapps package
6. reboot
this should get cm11 back up and running for you at least. Now once cm11 is back up and running do the same thing with the sense rom that you were trying to go to. it should work.
EDIT: also, keep a copy of your nandroid backup on a computer somewhere that way if something like this happens again you dont loose your backup.
Click to expand...
Click to collapse
When I attempt to factory reset the device it tells me it has failed.....and unable to mount '/data'
unable to mount internal storage
and does it matter that it is in S-On?
Thanks again
scruff72 said:
When I attempt to factory reset the device it tells me it has failed.....and unable to mount '/data'
unable to mount internal storage
and does it matter that it is in S-On?
Thanks again
Click to expand...
Click to collapse
okay ive had a phone of mine do that before, it should be okay as long as you wipe /system. after doing that try and flash the rom again and let me know if it works right.
and no it being s-on shouldnt matter with this.
scruff72 said:
When I attempt to factory reset the device it tells me it has failed.....and unable to mount '/data'
unable to mount internal storage
and does it matter that it is in S-On?
Thanks again
Click to expand...
Click to collapse
Did not work...still hung in boot loop......just fyi....there is NOTHING on my internal storage....it says 0 MB...here is a screenshot of what shows after I flash or do anything else about it not being able to mount....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ziggy46 said:
okay ive had a phone of mine do that before, it should be okay as long as you wipe /system. after doing that try and flash the rom again and let me know if it works right.
and no it being s-on shouldnt matter with this.
Click to expand...
Click to collapse
I will send you a screenshot of what I get when I try to wipe the system - it states that it fails. Should be able to attach screenshot in a few minutes.
Waiting on phone to die again because it will not power down.
I'm not 100% sure what's going on man.
Sent from my HTC One_M8 using Tapatalk
ziggy46 said:
I'm not 100% sure what's going on man.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
No problem. I appreciate your help. I know it can be saved because I can still get into the bootloader and recovery.....just not sure what to do.
ziggy46 said:
I'm not 100% sure what's going on man.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I fixed it....your advice got me to digging and I actually formatted the partition and then was able to load CM11. Thanks again...greatly appreciated.
scruff72 said:
I fixed it....your advice got me to digging and I actually formatted the partition and then was able to load CM11. Thanks again...greatly appreciated.
Click to expand...
Click to collapse
no problem man glad you got it working again [emoji1]
Sent from my HTC One_M8 using Tapatalk
Did you ever try to factory reset in bootloader?
This is the second post today I've seen where a person was having trouble wiping /data, which is usually a breeze. I wonder what is causing this. I'm just reaching a bit here, as the only time I've seen such issues, is on my old One X (EVITA) where doing a factory reset in bootloader would corrupt the internal storage. And the fact you said that formatting the storage fixed the issue, also reminds me of that same issue on the EVITA.
I'm in the same boat.
scruff72 said:
I fixed it....your advice got me to digging and I actually formatted the partition and then was able to load CM11. Thanks again...greatly appreciated.
Click to expand...
Click to collapse
Hi, I'm in a similar situation with my newly acquired HTC One M8.
I have access to bootloader and recovery (TWRP v.2.7.0.2), but I'm getting all the same "failed to mount ***" errors as you were having.
Can you please elaborate on how to "format the partition" or point me to a detailed thread/article on how to do that?
And any notes on how you got it back to work are very appreciated - I've spent hours and hours researching a trying things without any success.
I'm sorry I'm somewhat new to this...
Let me know if you need any more info and thank you for your help in advance.
scruff72 said:
I fixed it....your advice got me to digging and I actually formatted the partition and then was able to load CM11. Thanks again...greatly appreciated.
Click to expand...
Click to collapse
But how do you formatted the partition?! i´m in all most the same situation, and i think the things are clear, mi internal storage is corrupted, but the cuestion is How do i manually format it?
Thanks in advanceeeed!
AkaDeast said:
But how do you formatted the partition?! i´m in all most the same situation, and i think the things are clear, mi internal storage is corrupted, but the cuestion is How do i manually format it?
Thanks in advanceeeed!
Click to expand...
Click to collapse
You posted to a thread that is over a year old, its a stretch (to say the least) that you are in the "same situation".
If you can boot or flash TWRP, go to the Wipe options, then try the "Format Data" option.
Otherwise, try to relock the bootloader and RUU back to stock.
HTC One (M8) recovery fix
I have be stuck almost Vb. this worked with (M7) /(M8) AT&T. The quick fix would be to reflash BusyBox in recovery. Because more than likely your partition is out of wake due to flashing to many roms. If you get into recovery and are getting errors when trying to mount .Zip ie: all files completely missing or not enough space/storage est. When you the error its looking for an 4 dig number. try 0000 not work 1111. That works 90% for me. This assuming you are using TWRP 7.2++ or later. If still Stuck just flash same TWRP using over the top. Should be fine, I only know this because I have done the same and had worked great.
redpoint73 said:
You posted to a thread that is over a year old, its a stretch (to say the least) that you are in the "same situation".
If you can boot or flash TWRP, go to the Wipe options, then try the "Format Data" option.
Otherwise, try to relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
I tried to get help last year to set up my HTC Wildfire S and ended up hard bricking it.
I have a Evo 3D now and tried to unlock using the universal toolkit, but the toolkit did not work. At the final stage the phone just restarted with no changes. Tried the old fashioned method using stk pack and HTC sync manager, but just with the Wildfire S, the Manager could not recognize the EVO 3D. I really like this phone and don't want to hard brick it as well.
I don't see any reason to try, as I really enjoy the 3D camera and every ROM I've seen either does not support 3D or the camera works poorly.
Is there something to the contrary that I missed?
LyleVertigo said:
I tried to get help last year to set up my HTC Wildfire S and ended up hard bricking it.
I have a Evo 3D now and tried to unlock using the universal toolkit, but the toolkit did not work. At the final stage the phone just restarted with no changes. Tried the old fashioned method using stk pack and HTC sync manager, but just with the Wildfire S, the Manager could not recognize the EVO 3D. I really like this phone and don't want to hard brick it as well.
I don't see any reason to try, as I really enjoy the 3D camera and every ROM I've seen either does not support 3D or the camera works poorly.
Is there something to the contrary that I missed?
Click to expand...
Click to collapse
Only ICS Sense 3.6 ROMs have fully working 3d and some of them have great camera software. So, if you want a custom ROM, my advice is to go with ISC Sense 3.6. All newer have issues. As for unlocking the phone, did you try Htc dev? Easiest and most secure way to unlock your bootloader
Sent from my Xceeded black M7 ul
donkeykong1 said:
Only ICS Sense 3.6 ROMs have fully working 3d and some of them have great camera software. So, if you want a custom ROM, my advice is to go with ISC Sense 3.6. All newer have issues. As for unlocking the phone, did you try Htc dev? Easiest and most secure way to unlock your bootloader
Sent from my Xceeded black M7 ul
Click to expand...
Click to collapse
Thanks for the info on the rom. I tried the HTC Dev after the Universal tool failed. Unfortunately, the HTC Sync cannot locate the EVO 3D, it was the exact same problem I had with the Wildfire S. There is another way if I recall but I forgot what it was that lets you enter the token. I think it was a custom program someone made.
LyleVertigo said:
Thanks for the info on the rom. I tried the HTC Dev after the Universal tool failed. Unfortunately, the HTC Sync cannot locate the EVO 3D, it was the exact same problem I had with the Wildfire S. There is another way if I recall but I forgot what it was that lets you enter the token. I think it was a custom program someone made.
Click to expand...
Click to collapse
What OS do you use on your PC? Windows 8 had some problems with htc drivers
Sent from my Xceeded black M7 ul
donkeykong1 said:
What OS do you use on your PC? Windows 8 had some problems with htc drivers
Sent from my Xceeded black M7 ul
Click to expand...
Click to collapse
I use Windows 7 64x ultimate. Could the micro usb cable be able to transmit data to the SD card np but still have a flaw that is causing this problem? The downloads I use are not corrupted, I've redownloaded them several times to be sure.
LyleVertigo said:
I use Windows 7 64x ultimate. Could the micro usb cable be able to transmit data to the SD card np but still have a flaw that is causing this problem? The downloads I use are not corrupted, I've redownloaded them several times to be sure.
Click to expand...
Click to collapse
I don't think so, but try another cable if you have one. Also, don't use USB 3 port. Did you enable USB debuging on your phone?
Sent from my Xceeded black M7 ul
donkeykong1 said:
I don't think so, but try another cable if you have one. Also, don't use USB 3 port. Did you enable USB debuging on your phone?
Sent from my Xceeded black M7 ul
Click to expand...
Click to collapse
Not connected to usb 3, and yes, phone is set to usb debugging. I'm very careful and follow directions to the T. I have read several "how to" threads but no success. I am being very careful with this phone however, and I don't want to do anything to it unless it is safe to do so.
Ok, I tried this tutorial
http://youtu.be/M3jbZZWKwkY?t=15m6s
And was able to unlock the bootloader using this. However, when I tried su-2.3.6.3-efgh-signed to root it, I got can't open error. (bad).
using revolutionary cwm v4.0.1.4
Now I tried this tutorial: http://youtu.be/Q21rX13hnUY
This one uses uses EX4 and SU 3.1.3 Instead of Revolutionary and 2.3.6.3.
Again, everything is fine until I try to install the SU. Why can't any of these zips install???? Ugh.
and that one has the exact same specs as mine. Same ver. software, android ver. ect.
I'm at a complete loss on what's going on.
All of these tutorials go from unlocking to flashing recovery to flashing Superuser, but do you need to have S-Off before you can flash Superuser?
Curious as I'm currently unlocked with 4ext and S-Off.
LyleVertigo said:
All of these tutorials go from unlocking to flashing recovery to flashing Superuser, but do you need to have S-Off before you can flash Superuser?
Curious as I'm currently unlocked with 4ext and S-Off.
Click to expand...
Click to collapse
It is not necessary to be S-OFF in order to flash a ZIP. S-OFF is mainly for getting onto new bootloader version to run newer ROMs.
Are you able to mention the errors you get from flashing the SU ZIP?
h4z3d said:
It is not necessary to be S-OFF in order to flash a ZIP. S-OFF is mainly for getting onto new bootloader version to run newer ROMs.
Are you able to mention the errors you get from flashing the SU ZIP?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I renamed the files as someone mentioned it could cause it too. Didn't help though.
LyleVertigo said:
I renamed the files as someone mentioned it could cause it too. Didn't help though.
Click to expand...
Click to collapse
Are you able to link me to the download for that ZIP and also get the MD5 of the one on your SD card? I believe you might have a corrupted download. You can even try extracting the contents of the ZIP on Windows to a folder and if it shows an error, it's a bad download.
h4z3d said:
Are you able to link me to the download for that ZIP and also get the MD5 of the one on your SD card? I believe you might have a corrupted download. You can even try extracting the contents of the ZIP on Windows to a folder and if it shows an error, it's a bad download.
Click to expand...
Click to collapse
It's not a bad download, I've downloaded both versions from multiple sources. If you want to test the ones I have currently anyway, here they are.
LyleVertigo said:
It's not a bad download, I've downloaded both versions from multiple sources. If you want to test the ones I have currently anyway, here they are.
Click to expand...
Click to collapse
I just tried what you said, and I cannot unzip them in Windows. How in the world could that every download I've found be corrupt?
I DL multiple times for both files, the 3.1.3 came from SuperUser's own website and 2.3.6.3 came from this site.
LyleVertigo said:
I just tried what you said, and I cannot unzip them in Windows. How in the world could that every download I've found be corrupt?
I DL multiple times for both files, the 3.1.3 came from SuperUser's own website and 2.3.6.3 came from this site.
Click to expand...
Click to collapse
Sometimes it happens. I used to have a hard time downloading small files for some reason, they'd always corrupt, but larger files did not, it was odd. What I would personally try is downloading them via your mobile data, may work.
Also, both of your attachments were seen as corrupt on my end. You could try downloading from here:
download.chainfire.eu
h4z3d said:
Sometimes it happens. I used to have a hard time downloading small files for some reason, they'd always corrupt, but larger files did not, it was odd. What I would personally try is downloading them via your mobile data, may work.
Also, both of your attachments were seen as corrupt on my end. You could try downloading from here:
download.chainfire.eu
Click to expand...
Click to collapse
Finally, a clue. It appears that the SU zips are not corrupted when I download them, however when the recovery tries to flash them, it is then they become corrupted.
At first, one would think that it may be a bad recovery, but keep in mind I've tried Revolutionary before EXT4 and the problem was still occuring.
What could be causing the zips to become corrupt upon flashing? It can't be flashing in general, because it has been able to flash both recoveries just fine.
LyleVertigo said:
Finally, a clue. It appears that the SU zips are not corrupted when I download them, however when the recovery tries to flash them, it is then they become corrupted.
At first, one would think that it may be a bad recovery, but keep in mind I've tried Revolutionary before EXT4 and the problem was still occuring.
What could be causing the zips to become corrupt upon flashing? It can't be flashing in general, because it has been able to flash both recoveries just fine.
Click to expand...
Click to collapse
Hey, a fellow Texan!
Anyways, is it becoming corrupt after you transfer and attempt the flash, or is it becoming corrupt after the transfer (try transferring it and opening it again from the mounted drive). If it's the first, you could attempt to download another recovery, you don't have to flash it, you can simply type:
fastboot boot recovery.img
Here's a link to the recovery I'm currently using: http://forum.xda-developers.com/htc...overy-unoffical-twrp-2-7-1-0-selinux-t2831444
There's a link to 2.8.1.0 in the second post that you can attempt to use. If it's the second circumstance, what I would try to do is push the ZIP via adb. You can do this while in recovery as adb is recognized in it. Run this command to do it:
adb push file.zip /sdcard/file.zip
h4z3d said:
Hey, a fellow Texan!
Anyways, is it becoming corrupt after you transfer and attempt the flash, or is it becoming corrupt after the transfer (try transferring it and opening it again from the mounted drive). If it's the first, you could attempt to download another recovery, you don't have to flash it, you can simply type:
fastboot boot recovery.img
Here's a link to the recovery I'm currently using: http://forum.xda-developers.com/htc...overy-unoffical-twrp-2-7-1-0-selinux-t2831444
There's a link to 2.8.1.0 in the second post that you can attempt to use. If it's the second circumstance, what I would try to do is push the ZIP via adb. You can do this while in recovery as adb is recognized in it. Run this command to do it:
adb push file.zip /sdcard/file.zip
Click to expand...
Click to collapse
How would I push it? Keeps telling me device not found. adb is in C:/PhoneTools/ I have the file (Superuser3.1.3.zip) in both that folder and on SD card. I tried C:\PhoneTools>adb push Superuser313.zip /sdcard/Superuser313.zip but got a Error: device not found. Same if I tried adb push Superuser313.zip C:\PhoneTools\Superuser313.zip
LyleVertigo said:
How would I push it? Keeps telling me device not found. adb is in C:/PhoneTools/ I have the file (Superuser3.1.3.zip) in both that folder and on SD card. I tried C:\PhoneTools>adb push Superuser313.zip /sdcard/Superuser313.zip but got a Error: device not found. Same if I tried adb push Superuser313.zip C:\PhoneTools\Superuser313.zip
Click to expand...
Click to collapse
Try booting back into your phone and then pushing it through adb. Chances are not everyones device gets detected in recovery. Mine did at one point I think.