Related
OK so I have the Sprint EVO 4G LTE with 1.22.651.3 on it, rooted, S-ON. I have the Team Win Recovery Project v.2.1.8 on it as well with hboot 1.15. I tried loading the newest rooted software 2.13.651.1 710RD and voila.... paperweight. I tried reloading 1.22.651.3 and nothing. I can still boot to the bootloader and TWRP recovery, but nothing seems to work and now because sprint screwed up and removed my total equipment protection service from my plan, I don't have insurance on the phone. PLEASE HELP!!!
You just need to flash the kernel, extract it from the Rom (boot.img) and place it in adb folder, connect phone I'm bootloader and type fastboot flash boot boot.img
You can also flash meanrom, it has a working kernel installer, just let it sit because the kernel installer does take awhile 5-10 minutes
om4 said:
You just need to flash the kernel, extract it from the Rom (boot.img) and place it in adb folder, connect phone I'm bootloader and type fastboot flash boot boot.img
You can also flash meanrom, it has a working kernel installer, just let it sit because the kernel installer does take awhile 5-10 minutes
Click to expand...
Click to collapse
Can you explain how to do this in greater detail? I'm experienced only enough to be dangerous to myself lol
This program should install the kernel that you need. If not you are supposed to be able to swap boot.img files that it will install.
http://forum.xda-developers.com/showthread.php?t=1917106
http://forum.xda-developers.com/showthread.php?t=1752270
This is for the One S but it's the same process for our phones also.
Sorry I've been in a low coverage area and just got home. Open the Rom, extract the boot.img, open adb folder or SDK, hold shift and right click, select open command window here, connect phone in fastboot and type fastboot flash boot boot.img
So I tried to use that program to flash the boot.img from the fastboot screen but the computer wouldnt connect to the phone... now what?
Boot from system into hboot and fast boot while plugged in via USB. Helps your PC determine drivers.
Also, if you need a guide for setting up adb/fastboot, Google a YouTube vid by qbking77 on how to unlock galaxy nexus bootloader, it links to a great tutorial.
from my flying AOKP'd Evo LTE and xda premium
do you have SDK installed on your computer? If not install it. Go through the setup (set up your your environment variables) for fastboot.
Make a copy of the boot.img from a ROM of your choice. Place it in a folder on your desktop name the folder (android) leave the folder open.
Open cmd
Type cd Desktop press enter
Type cd android press enter
Type fastboot flash boot boot.img
After that it should say sending then OK
After that go into recovery then flash the ROM
you should be good to go then...
Sent from my EVO using xda app-developers app
The full SDK is not necessary, just the debug tools
ADB Tools
Also you can directly open the command prompt from within the folder by holding shift and opening the context menu (shift+right click) then select open command window here
i keep getting a message in windows "usb device not recognized" so i switched usb cables and finally got that program to load the boot.img file, then flashed a rom in bootloader but its still not booting... any ideas?
Did you make sure to wipe the phone first? What rom are you trying to flash?
wiped phone first and now trying to flash 2.13.651.1 after loading boot.img thru that program
you have to find a way to update your twrp to version 2.2.0 cause this is the culprit that gave you the issues. did you make a backup try doing a restore to get back up and running then download goomanager from the google play store and install the latest twrp here is a video to update to the latest twrp through goomanager.
twrp downloads I dont know if you have to be s-off to install in bootloader or not. maybe someone could clarify that
ok so i tried flashing twrp 2.2.2.0 and got a message saying "main verison is older" then it said "update failed!" which is weird since i had version 2.1.8.0 to begin with i think.
anyone? any ideas? I feel like my only resort is to have it replaced
You could fastboot flash the recovery image. Thats how I usually do it
So download the recovery image from twrp website and place it in your a dB folder. I don't have my PC but I think the command is fastboot flash recovery "recovery image"
Sent from my EVO using xda premium
corcgaigh said:
You could fastboot flash the recovery image. Thats how I usually do it
So download the recovery image from twrp website and place it in your a dB folder. I don't have my PC but I think the command is fastboot flash recovery "recovery image"
Sent from my EVO using xda premium
Click to expand...
Click to collapse
this should be the correct code to type
fastboot flash recovery openrecovery-twrp-2.1.8-jewel.img
Or
fastboot flash recovery openrecovery-twrp-2.2.2-jewel.img
Depending on how twrp names their recovery image
Sent from my EVO using xda app-developers app
Ok so i updated the twrp by changing the txt file to the proper software number.... then i flashed the lastest software version and NOW IT STARTS!!! WOOOHOOO!!!! Thanks everyone!!
I'm working on rooting my very first android phone for the very first time, and I've run across a snag. I've been following Luckythirteen's guide to rooting found here, but so far I've been unable to flash the TWRP recovery. Here's what I posted in the original thread:
Help! I've followed the steps to the T, but I'm struggling with installing the recovery. I've unlocked my bootloader, downloaded the TWRPrecovery.img, put it in the right folder. As soon as I boot into the bootloader, my phone seems to disconnect from the computer. I still have fastboot usb selected, but my device no longer shows up under adb devices. When I try to >fastboot flash recovery TWRPrecovery.img, I get an error "error: cannot load 'TWRPrecovery.img' : Unknown error"
I've got the international HOX+ and a computer running Win7. Any assistance in the matter would be super appreciated.
I hope I've provided enough information for someone to help me out here. I'm a complete Android beginner so this is all a little overwhelming. Thanks.
It is normal that your device does not show using "under adb devices" when in fastboot. You have to use "fastboot devices" instead. Try and see if your dive shows up there.
Also did you try redownloading the recovery.img and/or reinstallung HTC Drivers?
reaper90 said:
It is normal that your device does not show using "under adb devices" when in fastboot. You have to use "fastboot devices" instead. Try and see if your dive shows up there.
Also did you try redownloading the recovery.img and/or reinstallung HTC Drivers?
Click to expand...
Click to collapse
Hey, thanks for the reply. You're right, I did end up finding it under fastboot devices, but it still wouldn't work. Since then I've tried flashing a recovery using the all in one kit found in this, and adb shows that the flash was successful, however when I select recovery under the HBOOT menu, it just shuts off my phone, and when I power up again it reboots normally. Any idea what's up now?
christmas_time said:
Hey, thanks for the reply. You're right, I did end up finding it under fastboot devices, but it still wouldn't work. Since then I've tried flashing a recovery using the all in one kit found in this, and adb shows that the flash was successful, however when I select recovery under the HBOOT menu, it just shuts off my phone, and when I power up again it reboots normally. Any idea what's up now?
Click to expand...
Click to collapse
Where exactly did you see that flashing process was successful? What about your HTC drivers? Are they up to date? What version of TWRP did you try to install?
reaper90 said:
Where exactly did you see that flashing process was successful? What about your HTC drivers? Are they up to date? What version of TWRP did you try to install?
Click to expand...
Click to collapse
The adb command window shows the flashing process just like the images in the initial tutorial. I've tried reinstalling the drivers a few times now, would it show me the device under fastboot devices if my drivers weren't working? I tried the latest TWRP, 2.5.0.0. Sorry for double-posting, I wasn't aware you were the same guy from the other thread!
christmas_time said:
The adb command window shows the flashing process just like the images in the initial tutorial. I've tried reinstalling the drivers a few times now, would it show me the device under fastboot devices if my drivers weren't working? I tried the latest TWRP, 2.5.0.0. Sorry for double-posting, I wasn't aware you were the same guy from the other thread!
Click to expand...
Click to collapse
did you see the following two things in the command window? "sending recovery.img" an then "done"?
and just to be sure: you picked the right recovery version for the One X+?
reaper90 said:
did you see the following two things in the command window? "sending recovery.img" an then "done"?
and just to be sure: you picked the right recovery version for the One X+?
Click to expand...
Click to collapse
I must admit to my embarrassment that yes, it turns out I was trying to flash the wrong recovery (HOX instead of HOX+) and now I feel like an idiot, but I've finally gotten it to work, and I'm finally rooted! Thanks so much!
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.