Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.
Related
Hello! Sorry for posting this here, Idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, I have searched the forums before to see If someone had found a solution while I was having the error!
Sorry for this, but I posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 So moderators will you please delete the above post! Thanks so much!
This has happened to me so many times, I got frustrated, then I tried this out of the blue and it seemed to work..
Some examples of ROMS that froze on boot on my HTC EVO 3D HBOOT 1.5
All Infected ROMS
MIUI
Synergy
Senseless ROM
CleanRom
and some others..
These are the steps I took to fix the issue!
1. Flash ROM and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (Power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into PC or MAC
4. Make sure you have the latest android SDK, im pretty sure you do if you have been flashing roms!
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands
PC:
Code:
fastboot flash boot boot.img
Ive done it on the PC and most of the time I have issues.. like failing of transferring over of the boot.img.. So far I don't know a way around this besides to keep trying!!
MAC:
Code:
./fastboot flash boot boot.img
Ive done it on my mac as well, and so far I have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~Bairdog35
Bairdog35 said:
Hello! Sorry for posting this here, Idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, I have searched the forums before to see If someone had found a solution while I was having the error!
Sorry for this, but I posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 So moderators will you please delete the above post! Thanks so much!
This has happened to me so many times, I got frustrated, then I tried this out of the blue and it seemed to work..
Some examples of ROMS that froze on boot on my HTC EVO 3D HBOOT 1.5
All Infected ROMS
MIUI
Synergy
Senseless ROM
CleanRom
and some others..
These are the steps I took to fix the issue!
1. Flash ROM and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (Power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into PC or MAC
4. Make sure you have the latest android SDK, im pretty sure you do if you have been flashing roms!
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands
PC:
Code:
fastboot flash boot boot.img
Ive done it on the PC and most of the time I have issues.. like failing of transferring over of the boot.img.. So far I don't know a way around this besides to keep trying!!
MAC:
Code:
./fastboot flash boot boot.img
Ive done it on my mac as well, and so far I have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~Bairdog35
Click to expand...
Click to collapse
Your problem lies in your HBOOT 1.5.... you need to flash the kernel separately, either the way you described it, or I think theres an app called FlashGUI
or just access recovery from fastboot & flash like normal.
This should be moved
Lulz. 10 char.
Sent from my PG86100 using xda premium
SketchyStunts said:
or just access recovery from fastboot & flash like normal.
This should be moved
Click to expand...
Click to collapse
This.
Maybe OP doesn't know about it so I'll guide him.
OP, we appreciate you trying to help but if you follow the steps below you should have no problem.
1. Download the Rom you want and place it on your sd card.
2. Plug your phone in to your computer and open a cmd file where 'adb' is located and type "adb reboot bootloader".
3. Your phone will now restart and boot into bootloader. Now type in "fastboot boot recovery.img". Your phone will now boot into your recovery.
(At this point, you can unplug your phone.)
4. Use the recovery as how you normally would and wipe/flash, etc.
Enjoy.
arozer said:
This.
Maybe OP doesn't know about it so I'll guide him.
OP, we appreciate you trying to help but if you follow the steps below you should have no problem.
1. Download the Rom you want and place it on your sd card.
2. Plug your phone in to your computer and open a cmd file where 'adb' is located and type "adb reboot bootloader".
3. Your phone will now restart and boot into bootloader. Now type in "fastboot boot recovery.img". Your phone will now boot into your recovery.
(At this point, you can unplug your phone.)
4. Use the recovery as how you normally would and wipe/flash, etc.
Enjoy.
Click to expand...
Click to collapse
Yes I do this, and I still have to do what I provided up above. Idk what is wrong with my phone.
Your recovery can't flash kernels. Hence the boot loop.
There is a program in the evo3d theme and apps forum for us 1.5 boot loader users to flash the kernel using an app in android then you reboot to recovery and flash rom.
The app is called flash image GUI
http://forum.xda-developers.com/showthread.php?t=1192527
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Sent from my PG86100 using xda premium
shadowmike said:
Your recovery can't flash kernels. Hence the boot loop.
There is a program in the evo3d theme and apps forum for us 1.5 boot loader users to flash the kernel using an app in android then you reboot to recovery and flash rom.
The app is called flash image GUI
http://forum.xda-developers.com/showthread.php?t=1192527
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
If you use that app and flash the boot.img from the rom and then go into recovery and flash the rom it should work
Sent from my HTC Evo 3D using XDA App
bairdog35 said:
hello! Sorry for posting this here, idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, i have searched the forums before to see if someone had found a solution while i was having the error!
Sorry for this, but i posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 so moderators will you please delete the above post! Thanks so much!
this has happened to me so many times, i got frustrated, then i tried this out of the blue and it seemed to work..
Some examples of roms that froze on boot on my htc evo 3d hboot 1.5
all infected roms
miui
synergy
senseless rom
cleanrom
and some others..
these are the steps i took to fix the issue!
1. Flash rom and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into pc or mac
4. Make sure you have the latest android sdk, im pretty sure you do if you have been flashing roms!
5. Extract the .zip file of the rom that you are using that freezes.
6. Open the folder and copy the boot.img from that rom
7. Paste that .img into the folder that has your adb and fastboot files for the android sdk!
8. In terminal navigate to that folder, and do the following commands
pc:
Code:
fastboot flash boot boot.img
ive done it on the pc and most of the time i have issues.. Like failing of transferring over of the boot.img.. So far i don't know a way around this besides to keep trying!!
mac:
Code:
./fastboot flash boot boot.img
ive done it on my mac as well, and so far i have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~bairdog35
Click to expand...
Click to collapse
this worked for me it was hanging at the htc white logo screen did this steps and the phone passed the first boot logo and it turned on fine!!!
That's due to not flashin a kernel right or you skipped a part of the wipe.
Virus has this guide for flashing the kernel on his page
The problem with using this "Flash Image GUI" is the FACT that if an individual can't boot a ROM, they obviously can't run the apk.
Individuals with HBOOT 1.5 have two choices in this situation (bootloop)...
Either
1. "adb reboot bootloader" after which you run "fastboot boot recovery.img" (recovery.img must be placed in fastboot directory), then you flash the ROM/kernel in question...
Or
2. Flash boot.img through fastboot (which is what the above "should" do in the fist place).
BTW: If you always have a problem with bootloops, you aren't loading recovery the way you should...
You can either run the commands mentioned earlier in this post, or go to
forum.xda-developers.com/showthread.pho?t=1403148
and download the batch in the second post "jthein1989_batch.zip" (you will still need to download and copy the recovery.img to the folder).
Just download twrp or clockwork and copy it as "recovery.img" to the directory that you unzipped the batch to... Then, just follow the OP of my thread...
Sent from my PG86100 using XDA App
Maybe I'm a noob,
But you mean you can't select Recorery from Hboot menu? Even if you installed twrp? I don't know much of what I'm doing only had 3d for week. but its locks up at white HTC screen all the time.
Or you could try...
Fastboot boot my kernel or ill kill you.img
Sent from my HTC EVO 3D using xda premium
jcfunk said:
Maybe I'm a noob,
But you mean you can't select Recorery from Hboot menu? Even if you installed twrp? I don't know much of what I'm doing only had 3d for week. but its locks up at white HTC screen all the time.
Click to expand...
Click to collapse
With HBOOT 1.5 you "can" start recovery without ABD, but "S-ON" will not allow you to properly flash to the BOOT partition (limitation of the HTC unlock method). Therefore, users with HBOOT 1.5 need to go to extra lengths to flash the BOOT partition.
Sent from my PG86100 using XDA App
Having HBOOT 1.5, I've ran into this very problem. I'm not sure if it's hardware or what, but my phone will not run any Sense 3.5 ROM's I've tried. The phone just won't boot! I gave up trying 3.5 ROM's. I used ABD to put a 3.0 kernel back on and restore the recovery and everything is fine again. This will probably be my last HTC phone. Hoping something better besides the S2 is coming soon.
Ok... This is my 4th android phone.. And I love this phone... And only had it for a week.... and just now got it bricked.... here's what happen... Today I tried to flash a sense 4.1 rom, but im so new at this, and I'm half way done, and I went in a rush because I was nervous, and I accidentally press "install and keep data" and that was my mistake. I factory reset it b4 so I tried to flash it... So I thought it wouldn't be a problem. So I waited till the phone finish flashing. And when I rebooted the phone.... Nothing happened, just stuck on the white screen.... vibrating and etc... And I tried to restore all my data in clockworkmod recovery like I never even tried flashed it.. and it kept saying "won't mount sd card" and I tried to clear my cache/dalvik-cache, and like it still wont fix the issue. I even tried to restore wat I backup b4 I tried to flash it... and It was gone!!! Even my windows 8 laptop won't even detect my resound nor my sd card(unless its on a different android). But How can I fix my Rezound?!? plzzzz How can I fix this soft bricked issue? pllzzzzzzz help!!!
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
xkjonathanxk said:
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
Click to expand...
Click to collapse
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
@acejavelin
acejavelin said:
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
Click to expand...
Click to collapse
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Multidex24 said:
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Click to expand...
Click to collapse
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Dont know how to work ubuntu.. help again
acejavelin said:
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Multidex24 said:
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Click to expand...
Click to collapse
For the things you need to do, its not much different than Windows. Download and install adb, copy images to same places, and the commands are pretty much the same. If you can dualboot you obviously have some knowledge of such things.
If this is all do difficult, just grab a thumb drive, put mini-adb, recovery.img, and your ROM on it and go to a buddies computer with Win7 for 20 minutes and get it done that way.
I know this seems like a huge, potentially fatal problem, but it is minor...
Another thought I had... Download TWRP, go into CWM recovery and copy the TWRP file and ROM to the sd card, and FLASH TWRP recovery ZIP with CWM recovery, reboot into recovery and you will then be on TWRP and you can use TWRP's HTC Dumlock to flash the ROM and the boot.img without a PC at all... In theory, it should work.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Cap'n Jazz said:
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Click to expand...
Click to collapse
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Click to expand...
Click to collapse
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
http://img854.imageshack.us/img854/6248/ismh.png
This is how far I got in cmd if I'm headed in the right direction at all..
Cap'n Jazz said:
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
This is how far I got in cmd if I'm headed in the right direction at all..
Click to expand...
Click to collapse
You start fastboot in the phone, that puts it in a mode to enter fastboot commands from a PC... You Don't do anything in the phone in fastboot, you use the fastboot command that is part of the ADB package. The same way you would have unlocked the phone on HTCdev.com to allow root or CWM to be installed.
Sent from my Nexus 4 using Tapatalk
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
mjones73 said:
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
Click to expand...
Click to collapse
Thank both of you so much! I'm sorry I had to have you completely spell it out for me, but I appreciate the help and this forum in general so much!
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Did you flash the boot.img this time? I would suggest after you get booted, trying rumrunner to go S-off... It saves sooo much time... I'm always switching between multiple ROMs because I'm s-off....
Sent from my HTC EVO 4G Running AOKP 4.2.2
Cap'n Jazz said:
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Click to expand...
Click to collapse
... you should remember one thing for sure. Because you are s-on whenever you flash any custom rom, you have to flash its corresponding boot.img file in fastboot separately otherwise you are gonna get bootloop ...
---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------
... and yeah. you should try to get s-off as you are already been suggested above ...
Ohh.... Help please!!
I was flashing rom but I skipped a step and end does not pass the white HTC screen.
The fact is that it was installing the rom and Gapps but I miss the boot.img I have it on PC, the problem is that as the phone will not start, i can enter to bootloader but does not recognize the pc, I get the normal bootloader but how i do to pass the boot.img again if the phone does not recognize it??
And sorry for my bad english---- Help please!
rikrdoVe said:
Ohh.... Help please!!
I was flashing rom but I skipped a step and end does not pass the white HTC screen.
The fact is that it was installing the rom and Gapps but I miss the boot.img I have it on PC, the problem is that as the phone will not start, i can enter to bootloader but does not recognize the pc, I get the normal bootloader but how i do to pass the boot.img again if the phone does not recognize it??
And sorry for my bad english---- Help please!
Click to expand...
Click to collapse
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
ethanon said:
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
adb reboot bootloader
ethanon said:
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
rikrdoVe said:
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
Click to expand...
Click to collapse
rikrdoVe said:
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
Click to expand...
Click to collapse
Well you do need to have the Android SDK tools download but if you select the "Platform Tools" at the SDK manager , that will only install the platform tools on your hard disk. and yes the device drivers needs to installed , to work with ADB ,
Any ways this tutorial by LUCKY_THIRTEEN just might help you
http://forum.xda-developers.com/showthread.php?t=2213910
ethanon said:
Well you do need to have the Android SDK tools download but if you select the "Platform Tools" at the SDK manager , that will only install the platform tools on your hard disk. and yes the device drivers needs to installed , to work with ADB ,
Any ways this tutorial by LUCKY_THIRTEEN just might help you
http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
I cant install sdk and use adb... I resume: Dowloaded sdk from the page, and when i start sdk manager "Platform Tools" cant update i got this error: Stopping adb server succeeded. Failed to rename directory C:\adt.bundle.windows-x86-20131030\sdk\platform-tools to C:\adt.bundle.windows-x86-20131030\sdk\temp\PlatformToolPackage.old01. Nothing was installed"
I dont know if sdk was installed or what. only have the folder in C:
I put the boot.img file in platform-tools and tried to flash the image using the command fastboot flash boot boot.img but tells me the boot.img arrchivo not be found.
The phone does not recognize the pc, the bootloader is relocked.
Thanks for your support bro, I would like resolve this as soon as possible.
rikrdoVe said:
I cant install sdk and use adb... I resume: Dowloaded sdk from the page, and when i start sdk manager "Platform Tools" cant update i got this error: Stopping adb server succeeded. Failed to rename directory C:\adt.bundle.windows-x86-20131030\sdk\platform-tools to C:\adt.bundle.windows-x86-20131030\sdk\temp\PlatformToolPackage.old01. Nothing was installed"
I dont know if sdk was installed or what. only have the folder in C:
I put the boot.img file in platform-tools and tried to flash the image using the command fastboot flash boot boot.img but tells me the boot.img arrchivo not be found.
The phone does not recognize the pc, the bootloader is relocked.
Thanks for your support bro, I would like resolve this as soon as possible.
Click to expand...
Click to collapse
Well it seems you have installed the Android SDK all right. and make sure you put the file in the platform tools folder, and also make sure you have installed the HTC drivers for your PC to detect your phone , you can also try uninstall the driver and re install
ethanon said:
Well it seems you have installed the Android SDK all right. and make sure you put the file in the platform tools folder, and also make sure you have installed the HTC drivers for your PC to detect your phone , you can also try uninstall the driver and re install
Click to expand...
Click to collapse
Ok, i updated Platform-Tools to rev. 19.0.1, I had to start windows in safe mode.
But, yestarday Android sdk tools appeared in the list of installed programs in windows, i uninstalled and install today again but now i dont see sdk in list. Anyway, i open cdm and type "adb reboot-bootloader" and it says "error: device not found".
Then y type: fastboot flash boot boot.img and it says "error: cannot load boot.img"
I put the boot.img in C:\adt-bundle-windows-x86-20131030\sdk\platform-tools
And now... I dont know what to do
rikrdoVe said:
Ok, i updated Platform-Tools to rev. 19.0.1, I had to start windows in safe mode.
But, yestarday Android sdk tools appeared in the list of installed programs in windows, i uninstalled and install today again but now i dont see sdk in list. Anyway, i open cdm and type "adb reboot-bootloader" and it says "error: device not found".
Then y type: fastboot flash boot boot.img and it says "error: cannot load boot.img"
I put the boot.img in C:\adt-bundle-windows-x86-20131030\sdk\platform-tools
And now... I dont know what to do
Click to expand...
Click to collapse
Install the windows drivers , better try installing the the HTC sync manager. that way your device will be detected.
ethanon said:
Install the windows drivers , better try installing the the HTC sync manager. that way your device will be detected.
Click to expand...
Click to collapse
Ready, installed the HTC Sync Manager, and same result. "Device not Found"
if only I could get the phone to be recognized by the pc, I think it could solve the problem.
rikrdoVe said:
Ready, installed the HTC Sync Manager, and same result. "Device not Found"
if only I could get the phone to be recognized by the pc, I think it could solve the problem.
Click to expand...
Click to collapse
From where are u trying the commands.............
u must put ur phone in recovery mode.......
Connect ur phone to PC......
from the platform-tools folder try "adb devices"........
The adb commands will work in recovery only........
in bootloader the fastboot commands will work..........
[email protected] said:
From where are u trying the commands.............
u must put ur phone in recovery mode.......
Connect ur phone to PC......
from the platform-tools folder try "adb devices"........
The adb commands will work in recovery only........
in bootloader the fastboot commands will work..........
Click to expand...
Click to collapse
The phone is not recognized by the pc.
I can not get into recovery because the bootloader is relocked. I can only enter fastboot, but when executing commands, either with adb, All in One Toolkit, Flasher Venom or the phone is not recognized "Error: Device not found"
I have the drivers installed, htc sync manager, and I'm afraid that this phone unusable ... Also I did have a backup but on PC, but if the phone is not recognized I can not run any command ...
Also, I was trying to run teh Stock RUU:
RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1204.168.32_release_299688_signed
But When I run the. Exe signature throws an error (132) "find the correct signature and try again" and which is not correct. had sense 5 and 4.2.2 HTC One X + International.
Help please ... : (
same issue, cannot access recovery fastboot only
I hope this adds to this post if I miss speak I apologize in advance but I do not have the time or knowledge to post 10 times before strating my own thread so if this doesn't add value to this post, I have been reading and researching all week and now that I cannot use my phone I must intensely focus on this until it is fixed
Fed up with 4.3 and lower limitations and looking to get my monies worth on my phone, I look to upgrade to 4.3.1 or higher just started this week so I am a total newb, and if it means anything to anyone I would be happy to donate to contributors via papal once a solution is found I am a working professional and I am happy to pay you to save my time/phone
with that said here is what I have done
HTC One X+ (AT&T US) Quad Core Tegra 3
OTA upgraded 4.2.2 Android Firmware 2.15
Unlocked BL via HTCDev
Was using;
Recovery-clockwork-6.0.3.7-enrc2b.img
With intent to upgrade to 4.3.1
Used the following Rom and GAPPS to load .zips via CWM
cm-10.2.1-enrc2b (stable)
gapps-jb-20130813-signed.zip
Did not work
Tried more recent gapps
Did not work got stuck on Circling Cyanogenmod screen
//goo.gl/YzZ75o
THEN
I realized I was not flashing boot.img taken from the CM 10.2.1 zip so I followed directions to use the boot.img then load the zip files, since doing this I can no longer use my recovery
Erase Cache (from fastboot)
COMMANDs:
./fastboot erase cache
./fastboot reboot-bootloader
Results:
White HTC “Quietly Brilliant” Screen for a few seconds then turns off
Plug in charger and Red light turns on grey empty battery symbol appears with a lightning bolt inside then disappears
red light turns off :-/
//goo.gl/JrBJph
Current state: I can fastboot, but I cannot load recovery
//goo.gl/43F6XT
Also, if I can get back into recovery
The last time I was in it, last night I believe I reformatted my internal SD, because when I was looking for my backup, and my zips they were all gone...I was very tired and should haven't pushed it.
I don't care about loss of data I just need to get my phone working again, thanks for your time and careful considerations
UPDATE+++
Used WinDroid HTC One X+ Toolkit 3 to flash custom recovery CWM 6.0.3.7 back in recovery again, now I think I need to side load a ROM because I deleted what I had internally
cclifford81 said:
I hope this adds to this post if I miss speak I apologize in advance but I do not have the time or knowledge to post 10 times before strating my own thread so if this doesn't add value to this post, I have been reading and researching all week and now that I cannot use my phone I must intensely focus on this until it is fixed
Fed up with 4.3 and lower limitations and looking to get my monies worth on my phone, I look to upgrade to 4.3.1 or higher just started this week so I am a total newb, and if it means anything to anyone I would be happy to donate to contributors via papal once a solution is found I am a working professional and I am happy to pay you to save my time/phone
with that said here is what I have done
HTC One X+ (AT&T US) Quad Core Tegra 3
OTA upgraded 4.2.2 Android Firmware 2.15
Unlocked BL via HTCDev
Was using;
Recovery-clockwork-6.0.3.7-enrc2b.img
With intent to upgrade to 4.3.1
Used the following Rom and GAPPS to load .zips via CWM
cm-10.2.1-enrc2b (stable)
gapps-jb-20130813-signed.zip
Did not work
Tried more recent gapps
Did not work got stuck on Circling Cyanogenmod screen
//goo.gl/YzZ75o
THEN
I realized I was not flashing boot.img taken from the CM 10.2.1 zip so I followed directions to use the boot.img then load the zip files, since doing this I can no longer use my recovery
Erase Cache (from fastboot)
COMMANDs:
./fastboot erase cache
./fastboot reboot-bootloader
Results:
White HTC “Quietly Brilliant” Screen for a few seconds then turns off
Plug in charger and Red light turns on grey empty battery symbol appears with a lightning bolt inside then disappears
red light turns off :-/
//goo.gl/JrBJph
Current state: I can fastboot, but I cannot load recovery
//goo.gl/43F6XT
Also, if I can get back into recovery
The last time I was in it, last night I believe I reformatted my internal SD, because when I was looking for my backup, and my zips they were all gone...I was very tired and should haven't pushed it.
I don't care about loss of data I just need to get my phone working again, thanks for your time and careful considerations
Click to expand...
Click to collapse
ummm your flashing the X+ International CM rom and not the evitareul one, reboot into the bootloader and then enter recovery from there.
Lloir said:
ummm your flashing the X+ International CM rom and not the evitareul one, reboot into the bootloader and then enter recovery from there.
Click to expand...
Click to collapse
Will do, thanks!
evitareul? Does that mean Flash TWRP recovery and then use evita ROM?
cclifford81 said:
Will do, thanks!
evitareul? Does that mean Flash TWRP recovery and then use evita ROM?
Click to expand...
Click to collapse
Evitareul = X+ AT&T
Sent from my Nexus 5 using Tapatalk
Lloir said:
Evitareul = X+ AT&T
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok so I just need the evitareul Rom, I'm looking for it now, I just need something stable at 4.3 or higher with GAPPS anyone have any links
cclifford81 said:
Ok so I just need the evitareul Rom, I'm looking for it now, I just need something stable at 4.3 or higher with GAPPS anyone have any links
Click to expand...
Click to collapse
look in original development
Lloir said:
look in original development
Click to expand...
Click to collapse
Ok, from what I can tell I think I have to go with this?
[ROM][2/18/2014][AT&T X+ S5 eXtreme V1.0.3.3]
I will be very happy if I can get this to work, and I will just "stay tuned" for when I can flash a stable 4.3 or higher for my phone
Under downloads I see the following: (would post picture but still too n00b)
S6 eXtreme RC1
S5 RC2 Patch
Native WiFi
Hotspot Patch
S5 eXtreme
V1.0.3.2
S5 eXtreme
V1.0.3.3
I am not sure what to download here, I will continue reading these directions as I believe this is my best option, please confirm if I am on the right path, thanks guys!
Update+++
Downloaded S5_eXtreme_V1.0.3.3_Signed.zip
about to flash this ROM, is GAPPS included in this?
Update+++
Downloaded S5_eXtreme_V1.0.3.3_Signed.zip Rom
Extracted the boot.img file and followed instructions
Extract boot.img from zip file and place in your sdk platform tools folder, (or wherever your adb tools are located)reboot device to bootloader and connect it to your PC.
From a command prompt type:
1. fastboot flash boot boot.img
2. fastboot erase cache
reboot to recovery and flash ROM.
but I am not sure how I flashed the ROM, I tried sideloading from recovery with WinDroid HTC One X+ Toolkit, before and after and it said no package loaded
Then I tried to load from fastboot, finally I figured "well I might as well reboot" and amazingly enough it booted...not sure what exactly but I am back on 4.2.2 so thank you!
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.