Hi,
Can anyone please post the stock recovery for Developer Edition?
I converted to DE using the RUU from this thread - Lollipop RUU exe from HTC's repo: 4.16.1540.8
http://forum.xda-developers.com/htc-...-1-54-t2884777
I see something that might be the correct recovery here:
https://www.androidfilehost.com/?w=files&flid=24260
from this thread:
http://forum.xda-developers.com/showthread.php?t=2701376
But I really want to be sure it is the correct stock recovery img as 4.16.401.10 may not work with 4.16.1540.8.
Thanks!
Been on travel for 2 weeks, and preoccupied with things non-XDA. Catching up on my inbox. Not sure if you solved your issue or not, and determining that is difficult since it looks like you've posted the question in 3 different places. Try to stick to 1 thread in future, as it makes helping you much less confusing.
But if you RUU'ed to DE, you don't need to install stock recovery. RUU installs stock recovery. RUU is a complete stock image, including recovery.
Also, the recovery images you linked are for the "international" M8 (401 software) and not the DE (1540 software). So not the right stock recoveries.
redpoint73 said:
Been on travel for 2 weeks, and preoccupied with things non-XDA. Catching up on my inbox. Not sure if you solved your issue or not, and determining that is difficult since it looks like you've posted the question in 3 different places. Try to stick to 1 thread in future, as it makes helping you much less confusing.
But if you RUU'ed to DE, you don't need to install stock recovery. RUU installs stock recovery. RUU is a complete stock image, including recovery.
Also, the recovery images you linked are for the "international" M8 (401 software) and not the DE (1540 software). So not the right stock recoveries.
Click to expand...
Click to collapse
I apologize. I won't repeat the mistake and will post to one place in the future.
Thank you for confirming the linked recovery images were not correct.
If I RUU upon release of the OTA, I'll lose all of my data, correct? This wasn't an issue for the conversion to the DE but seems more problematic if I just want to receive a smaller OTA update. Does a stock recovery not really exist for the DE without a really difficult time obtaining it (e.g., extracting it from the RUU somehow)?
mirrored said:
If I RUU upon release of the OTA, I'll lose all of my data, correct? This wasn't an issue for the conversion to the DE but seems more problematic if I just want to receive a smaller OTA update. Does a stock recovery not really exist for the DE without a really difficult time obtaining it (e.g., extracting it from the RUU somehow)?
Click to expand...
Click to collapse
I think I understand now what you are trying to accomplish, so correct me if I'm wrong here:
You are now on the stock DE RUU (which means you are on the stock recovery). But you also want an recovery file of the stock recovery on hand so you can revert in order to install future OTAs. Which also means in the interim that you plan to install custom recovery, and flash ROMs or other mods.
Do I have it right?
If so, if another member here hasn't posted the stock recovery for 4.16.1540, its a easy matter of backing it up yourself. There is a trick to remotely boot TWRP custom recovery with fastboot without actually flashing it. Once you've done that, you can use TWRP to backup the existing stock recovery image. Once you have that backed up, you can then flash TWRP as you normally would (for root, flashing ROMs, etc.).
The command is: fastboot boot recovery filename.img
EDIT: The above command should be: fastboot boot filename.img
Where "filename.img" is the actual file name of the TWRP img placed in your fastboot folder.
Note this is different from the command normally used to flash a recovery image: fastboot flash recovery filename.img
After which, you can't backup the stock recovery image, since its been overwritten with TWRP.
---------- Post added at 09:54 AM ---------- Previous post was at 09:47 AM ----------
Also, you should be able to easily open up a firmware.zip and extract the recovery image. For instance, the 4.16.1540 firmware zip is included in the ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
But its packed with the whole ROM, and I'm not in the position at this moment to download the whole thing, and verify that the above is true.
You might be able to find somewhere that a user has posted the firmware.zip for 4.16.1540 by itself.
redpoint73 said:
I think I understand now what you are trying to accomplish, so correct me if I'm wrong here:
Click to expand...
Click to collapse
That's exactly what I want to do. Just root so I can stop a few services, but not flash any ROM's or anything else, then re-flash the stock recovery when an OTA hits as necessary.
I'm trying to use the command you said, "fastboot boot recovery filename.img," but keep getting the error message "cannot load recovery."
Here's a screenshot:
http://i.imgur.com/gSwjw3E.jpg
I believe you don't need to include the word "recovery"...
fastboot boot filename.img
DanGeorges said:
I believe you don't need to include the word "recovery"...
fastboot boot filename.img
Click to expand...
Click to collapse
You are correct. Thanks for the clarification; and my apologies to the OP for the confusion. I've edited the post above to prevent any further mixup.
DanGeorges said:
fastboot boot filename.img
Click to expand...
Click to collapse
redpoint73 said:
You are correct.
Click to expand...
Click to collapse
I'm getting a similar but not the same error message with the command "fastboot boot filename.img"
It is: "cannot load [whatever recovery I try].img"
http://i.imgur.com/jpPbDnm.jpg
mirrored said:
I'm getting a similar but not the same error message with the command "fastboot boot filename.img"
It is: "cannot load [whatever recovery I try].img"
http://i.imgur.com/jpPbDnm.jpg
Click to expand...
Click to collapse
One thing, the syntax "recovery1.img" (no quotes) is not correct. It should be a capitol "R" (per the actual file name) its case sensitive, and all commands need to be completely exact when typing fastboot commands.
Although that doesn't explain why the TWRP and Philz commands didn't work, as the syntax looks fine.
Make sure you don't have the Windows option to hide known file extensions enabled (its typically enabled by default). You may have your files inadvertently named "filename.img.img", and not know it (a fairly common mistake).
Related
So I am looking to flash a recovery image without RomMangaer from the device itself.
Should not be a issue since I can use flash_image to flash it, but ofc my ROM does not have it.
I found this thread here: http://forum.xda-developers.com/showthread.php?t=902493 that has a flash_image file attached to it...
My question is, can I use that flash_image file, even though that is in the G2 forum or do I need one built for the tbolt specifically? If I do can someone please link to it.
TIA.
It is ok to answer, I won't bite.
You need to grab the correct recovery file. Probably easiest to use Revolution to do this.
Sorry.... Revolutionary.
Look here as well.
http://forum.xda-developers.com/showthread.php?t=1179386
arbrouwer said:
You need to grab the correct recovery file. Probably easiest to use Revolution to do this.
Click to expand...
Click to collapse
arbrouwer said:
Sorry.... Revolutionary.
Click to expand...
Click to collapse
arbrouwer said:
Look here as well.
http://forum.xda-developers.com/showthread.php?t=1179386
Click to expand...
Click to collapse
Hi, I am not looking for a recovery file, I have CWMR already installed. I am looking for a flash_image file, so I can use a command such as flash_image recovery recovery.img if I wanted.
Thanks for trying.
Sounds like you want to run adb commands, not my specialty. Why not grab the appropriate img file and flash through hboot or clockwork.
http://rootzwiki.com/forum/11-thunderbolt/
MordyT said:
Hi, I am not looking for a recovery file, I have CWMR already installed. I am looking for a flash_image file, so I can use a command such as flash_image recovery recovery.img if I wanted.
Thanks for trying.
Click to expand...
Click to collapse
If you're meaning system partitions, you have to make those yourself through using dd and some mounting on linux.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://www.slatedroid.com/topic/5799-repack-systemimg/
http://wiki.archosfans.com/index.php?title=Dump_your_Home_Tablet_rom_and_create_a_custom_rom
http://www.androidtablets.net/forum...notes-modifying-system-partition-desktop.html
Someone also JUST ASKED this on the same page of the q/a and got an answer. No one ever reads previous posts anymore
If you mean flashing recovery you have to grab it from the clockwork mod site and flash it using fastboot.
http://android-dls.com/wiki/index.php?title=Fastboot
arbrouwer said:
Sounds like you want to run adb commands, not my specialty. Why not grab the appropriate img file and flash through hboot or clockwork.
http://rootzwiki.com/forum/11-thunderbolt/
Click to expand...
Click to collapse
I do want to run adb commands - a very specific one - on the phone. The adb command is called "flash_image - such as flash_image boot boot.img.
I will be able to flash different partitions without the need of a PC. The only thing is, while a ASOP rom will have the flash_image command (and file called flash_image) a ROM like the one I am on (or even a stock rom) won't. So I need the file... The link I posted in the op has a flash_image file at the bottom, but I don't know if it works for thunderbolt since it is in a g2 forum...
yareally said:
If you're meaning system partitions, you have to make those yourself through using dd and some mounting on linux.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://www.slatedroid.com/topic/5799-repack-systemimg/
http://wiki.archosfans.com/index.php?title=Dump_your_Home_Tablet_rom_and_create_a_custom_rom
http://www.androidtablets.net/forum...notes-modifying-system-partition-desktop.html
Someone also JUST ASKED this on the same page of the q/a and got an answer. No one ever reads previous posts anymore
If you mean flashing recovery you have to grab it from the clockwork mod site and flash it using fastboot.
http://android-dls.com/wiki/index.php?title=Fastboot
Click to expand...
Click to collapse
Actually, I was not asking that. I know how to make them and all. Do you see my low post count? It is because I read and read and read. Thanks for the advise though.
While I am asking about flashing recovery, I was not asking about hwo to do it in fastboot - I was asking how to do it on the device itself. Without ROM Manager.
In fact, I already know how to do it on the device itself... I need to use the command flash_image recovery recovery.img... except I am missing flash_image on my current ROM... so does anyone know where a version of that file is that is compatible with our tbolts?
MordyT said:
I do want to run adb commands - a very specific one - on the phone. The adb command is called "flash_image - such as flash_image boot boot.img.
I will be able to flash different partitions without the need of a PC. The only thing is, while a ASOP rom will have the flash_image command (and file called flash_image) a ROM like the one I am on (or even a stock rom) won't. So I need the file... The link I posted in the op has a flash_image file at the bottom, but I don't know if it works for thunderbolt since it is in a g2 forum...
Actually, I was not asking that. I know how to make them and all. Do you see my low post count? It is because I read and read and read. Thanks for the advise though.
While I am asking about flashing recovery, I was not asking about hwo to do it in fastboot - I was asking how to do it on the device itself. Without ROM Manager.
In fact, I already know how to do it on the device itself... I need to use the command flash_image recovery recovery.img... except I am missing flash_image on my current ROM... so does anyone know where a version of that file is that is compatible with our tbolts?
Click to expand...
Click to collapse
I dont look at post counts, they're deceiving anyways (and join dates).
Without rom manager? Who does it with that anyways (it's prone to issues)? You flash them in recovery. The commands you use to install something in recovery, if you wish to do it with adb in recovery instead of pressing the buttons are located here http://www.londatiga.net/it/how-to-create-android-update-zip-package/
And yes, you can flash stuff very well in fastboot as well, which is what it looks like you're trying to do by your command you listed. If you're not doing it in fastboot or recovery, you're just crazy and looking to screw something up. You can't do it elsewhere because it'll potentially break your phone.
When you named something recovery.img it makes it look like you're trying to flash a new version of recovery though and that is something you do in fastboot.
That file you wanted anyways, flash_image, just pull it out of another ROM. If it's not in there, then it's part of flashing a new recovery itself.
yareally said:
I dont look at post counts, they're deceiving anyways (and join dates).
Without rom manager? Who does it with that anyways (it's prone to issues)? You flash them in recovery. The commands you use to install something in recovery, if you wish to do it with adb in recovery instead of pressing the buttons are located here http://www.londatiga.net/it/how-to-create-android-update-zip-package/
And yes, you can flash stuff very well in fastboot as well, which is what it looks like you're trying to do by your command you listed. If you're not doing it in fastboot or recovery, you're just crazy and looking to screw something up. You can't do it elsewhere because it'll potentially break your phone.
When you named something recovery.img it makes it look like you're trying to flash a new version of recovery though and that is something you do in fastboot.
That file you wanted anyways, flash_image, just pull it out of another ROM. If it's not in there, then it's part of flashing a new recovery itself.
Click to expand...
Click to collapse
ROM Manager has its flaws. I can't flash boot.imgs in it, I can't flash custom recoverys (not cwm) in it, or any other partition I want....
I am not flashing in fastboot or recovery, or even using a PC. Call me crazy if you will but it is how I roll. The non-need of a computer is what I am after.
See this thread. What I am trying to do is something that can be done since day 1 with android..
http://forum.xda-developers.com/showthread.php?t=902493
http://www.clockworkmod.com/rommanager you can probably pull what you want out of the clockwork recovery image or rom manager.apk. Either mount the recovery image on linux or open up rom manager's apk with a zip program and pull it out.
EDIT: flash_image is in the rom_manager apk. Just get it out of that at the link above.
Back from Moto-land with Rezound. I've flashed several ROMS and one I would like to flash now says that I must firs be on the leaked 3.11.605.22 firmware.
I thought that when I flashed a rom and it rebooted into bootloader to install the PH98IMG.zip file, that it was installing the necessary firmware. I'm confused.
How do I get to the necessary Leaked firmware. I've searched and googled, but everything I find, indicates that I cannot install the leak, because I have already used the HTC unlock tool. Again, confused
I appreciate your help!
ruu isn't a Tom that loads the kernel afterwards. the leak is flashed all at once which appears to be how kernels are flashed. flashing the leak requires the lock then it flashes everything together but remember it wipes all data with exception of external sd
Followup Q1: So is it possible to get to the RUU 3.11.605.22 firmware, WITHOUT re-locking and flashing the leak? (not concerned at all about full wipe, do it with each rom)
Q2: If I do have to re-lock and then flash the leak, do I first have to return to a 100% stock state (ie, restore all the bloat-ware and such)? (if you've ever had a Bionic you know what I'm talking about)
http://forum.xda-developers.com/showthread.php?p=23700622
Sent from my ADR6425LVW using Tapatalk
nukeboyt said:
Followup Q1: So is it possible to get to the RUU 3.11.605.22 firmware, WITHOUT re-locking and flashing the leak? (not concerned at all about full wipe, do it with each rom)
Q2: If I do have to re-lock and then flash the leak, do I first have to return to a 100% stock state (ie, restore all the bloat-ware and such)? (if you've ever had a Bionic you know what I'm talking about)
Click to expand...
Click to collapse
Originally Posted by JoelZ9614 View Post
Here are the instructions...
Download...
rename the zip to PH98IMG.zip
put on your sdcard
reboot to bootloader
fastboot oem lock
reboot to bootloader again
flash.
reboot to bootloader
[if it says security warning and tampered at the top flash again..after continue to next step]
fastboot flash unlocktoken Unlock_code.bin [of course only if u have ur original Unlock_code.bin if not do the whole htc thing again]
reboot......
A little confused. Android Police says you have to be fully stock with a locked bootloader to install 605.22. According to this, I don't have to be stock, I just have to relock it, and be aware that the full RUU install with radios will wipe my entire phone except external SD? (I wouldn't ask this except that it directly contradicts the AP post.)
And do we have the ability to re-root the resulting ICS installation?
And there's no other way to apply just the radios and the pre-rooted (Non-RUU?) version?
Does the pre-rooted version also do a full wipe?
cpurick said:
A little confused. Android Police says you have to be fully stock with a locked bootloader to install 605.22. According to this, I don't have to be stock, I just have to relock it, and be aware that the full RUU install with radios will wipe my entire phone except external SD? (I wouldn't ask this except that it directly contradicts the AP post.)
And do we have the ability to re-root the resulting ICS installation?
And there's no other way to apply just the radios and the pre-rooted (Non-RUU?) version?
Does the pre-rooted version also do a full wipe?
Click to expand...
Click to collapse
So far no other way to get the new radios , sounds like the only reason the OTA leak worked was the way it was packaged. This new leak isn't packaged the same way so you would have to relock and run the RUU to get the new radios.
Personally, all I did was reflash stock recovery before hand, but I had to run it a few times to get it to work fully and at one point I just relocked with amon recovery installed and ran it and it worked just fine. It wipes recovery as part of the installation and installs the updated stock recovery.
andybones said:
Originally Posted by JoelZ9614 View Post
Here are the instructions...
Download...
rename the zip to PH98IMG.zip
put on your sdcard
reboot to bootloader
fastboot oem lock
reboot to bootloader again
flash.
reboot to bootloader
[if it says security warning and tampered at the top flash again..after continue to next step]
fastboot flash unlocktoken Unlock_code.bin [of course only if u have ur original Unlock_code.bin if not do the whole htc thing again]
reboot......
Click to expand...
Click to collapse
Sorry for the questions, but when I do all of this, will I still have the Amon Ra recovery, or does this return to the stock recovery (which I assume it does)?
When the PH file is flashed in recovery it will overwrite whatever recovery you had flashed previously and leave you with stock everything...including recovery.
Sent from my ADR6425LVW
I was able to upgrade to the new ROM and then re-unlock my phone. But when I put Amon Ra in SD folder as PH98IMG.zip and reboot to the loader, I am never prompted to install it. Furthermore, attempts to get into recovery result in a green circular icon followed by a red triangle with exclamation point.
I tried all sorts of resets and reboots. Right now I have a green recovery option, but no working recovery. The top line says "UNLOCKED".
I've tried Amon Ra 3.13 and 3.14.
Download this file.
Place it in the same folder that you setup for the HTCdev unlock.
Rename it to "recovery."
Go to the command prompt and type in this command: cd c:\nameoffolder (mine is c:\Android for example)
Boot into Hboot
Select Fastboot
Connect to PC
Then type this exactly : fastboot flash recovery recovery.img
That should get you loaded with Amon Ra.
http://forum.xda-developers.com/showthread.php?p=19205213
Installation instructions are in the OP.
What you see now when you select recovery in hboot is what is considered stock recovery
Sent from my ADR6425LVW using Tapatalk
EmerikL said:
Download this file.
Place it in the same folder that you setup for the HTCdev unlock.
Rename it to "recovery."
Go to the command prompt and type in this command: cd c:\nameoffolder (mine is c:\Android for example)
Boot into Hboot
Select Fastboot
Connect to PC
Then type this exactly : fastboot flash recovery recovery.img
That should get you loaded with Amon Ra.
Click to expand...
Click to collapse
Thank you. I had already figured it out, and this is exactly what the problem was. Last time I flashed with a PH98IMG version of recovery, but this latest version that I have is for Fastboot. Thanks!
Never thought it would be such a relief to see the "TAMPERED" warning, lol.
All is good!
ZIP to fix mainver problems
http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
Hi,
Let me start off by saying that I have viewed other threads but have not been able to find one that has this same exact problem. Can someone please help?
I have an HTC Evo 3D unlocked with the HTC method, S-On.
I put a new rom on my SD card, I was using InfectedRom but it had some issues. I loaded into bootloader and used revolutionary to flash the rom. I didn't do a wipe or anything else, thinking that it would just flash the rom and I would be good to go.
The phone gets stuck on the HTC splash screen when I go to boot it. I have tried everything from restoring from a back up, to wiping the phone to wiping the cache and am at a loss.
Can someone please offer me some advice? I really need to get this phone back up and running.
Thanks in advance.
Did you flash the boot.img for the ROM?
How can I do that?
Jep4444 said:
Did you flash the boot.img for the ROM?
Click to expand...
Click to collapse
Thanks for the quick response. How can I go about doing that?
thealist said:
Thanks for the quick response. How can I go about doing that?
Click to expand...
Click to collapse
Considering you're S-ON, how did you install a custom ROM in the first place without doing so?
thealist said:
Thanks for the quick response. How can I go about doing that?
Click to expand...
Click to collapse
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
Jep4444 said:
Considering you're S-ON, how did you install a custom ROM in the first place without doing so?
Click to expand...
Click to collapse
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
Click to expand...
Click to collapse
Don't S-ON roms still need the boot.img to be flashed to install any ROM?
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Where do I find my recovery image?
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
Thanks. Where would I find this and do I put that into the root sd card portion of my phone and then run through the bootloader? Sorry, I am relatively new to this process. Thanks for your patience.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
That's exactly what I did.
~co~
Click to expand...
Click to collapse
Thanks for all the help. It's very much appreciated.
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
Click to expand...
Click to collapse
Sorry, my last post did not quote correctly.
How do I find my recovery image?
Once I get FlashImageGUI, do I put that into the root of my SD card by plugging it into my mac?
Jep4444 said:
Don't S-ON roms still need the boot.img to be flashed to install any ROM?
Click to expand...
Click to collapse
Well, all ROMs will need to have a boot.img flashed to boot, but since they are included in the ZIP file containing the ROM, they are normally flashed along with the ROM. If you use FlashImageGUI, you can flash from a boot.img or from a kernel zip file. By running the fastboot boot command, this allows the user to flash to partitions that are locked when booted into recovery from the bootloader.
thealist said:
Sorry, my last post did not quote correctly.
How do I find my recovery image?
Once I get FlashImageGUI, do I put that into the root of my SD card by plugging it into my mac?
Click to expand...
Click to collapse
These are two different methods for accomplishing the same task.
Have you loaded a custom recovery (like ClockworkMod Recovery, TWRP, or 4EXT) before? If you've kept the recovery image on your computer, you can just use that one. Instead of flashing it to your recovery partition (fastboot flash recovery [NAMEOFRECOVERY].img), you would boot to it instead (fastboot boot [NAMEOFRECOVERY].img).
If you use want to use FlashImageGUI, you would copy it to your SD card, install it on the phone, and run the app. Make sure that you've got the ROM you want to flash on the SDCard. If I remember correctly, FlashImageGUI will pull the boot.img out of the ZIP and flash it. Then you will have to boot into your custom recovery to flash the rest of the image. Flashing just the boot image will most likely leave you with a phone that won't boot (until you flash the rest of the ROM).
~co~
closeone said:
Well, all ROMs will need to have a boot.img flashed to boot, but since they are included in the ZIP file containing the ROM, they are normally flashed along with the ROM. If you use FlashImageGUI, you can flash from a boot.img or from a kernel zip file. By running the fastboot boot command, this allows the user to flash to partitions that are locked when booted into recovery from the bootloader.
These are two different methods for accomplishing the same task.
Have you loaded a custom recovery (like ClockworkMod Recovery, TWRP, or 4EXT) before? If you've kept the recovery image on your computer, you can just use that one. Instead of flashing it to your recovery partition (fastboot flash recovery [NAMEOFRECOVERY].img), you would boot to it instead (fastboot boot [NAMEOFRECOVERY].img).
If you use want to use FlashImageGUI, you would copy it to your SD card, install it on the phone, and run the app. Make sure that you've got the ROM you want to flash on the SDCard. If I remember correctly, FlashImageGUI will pull the boot.img out of the ZIP and flash it. Then you will have to boot into your custom recovery to flash the rest of the image. Flashing just the boot image will most likely leave you with a phone that won't boot (until you flash the rest of the ROM).
~co~
Click to expand...
Click to collapse
I have never loaded ClockworkMod Recovery, TWRP, or 4EXT to my phone. Is that something I can download online and then transfer to my phone using the bootloader? I have Revolutionary which allows me to mount the SD card. Same thing goes for FlasImageGUI. I can't get past the HTC load screen so is that something I can just transfer and use Bootloader with?
thealist said:
I have never loaded ClockworkMod Recovery, TWRP, or 4EXT to my phone. Is that something I can download online and then transfer to my phone using the bootloader? I have Revolutionary which allows me to mount the SD card. Same thing goes for FlasImageGUI. I can't get past the HTC load screen so is that something I can just transfer and use Bootloader with?
Click to expand...
Click to collapse
What is this 'Revolutionary' that you're talking about? I realize that multiple pieces of software can be called the same thing though. How did you load on the ROM that you're currently on? Also, before I link you anywhere (because I don't want you loading the wrong recovery on your phone), is your phone on Sprint, or another carrier? You'd use Recovery to load ROMs, back them up, and so on.
What exactly was it that you were trying to do? Or rather, how did the phone get to a state where it's frozen on the HTC logo? Do you have a custom ROM loaded, or the stock ROM?
Sorry for all the questions, and hopefully this response doesn't come off rude (I don't mean it to ). I'm just trying to figure out what's going on before I suggest anything.
If you are on Sprint, you can run this recovery from Fastboot USB mode.
Code:
fastboot boot cwm-4.0.1.4-shooter.img
~co~
closeone said:
What is this 'Revolutionary' that you're talking about? I realize that multiple pieces of software can be called the same thing though. How did you load on the ROM that you're currently on? Also, before I link you anywhere (because I don't want you loading the wrong recovery on your phone), is your phone on Sprint, or another carrier? You'd use Recovery to load ROMs, back them up, and so on.
What exactly was it that you were trying to do? Or rather, how did the phone get to a state where it's frozen on the HTC logo? Do you have a custom ROM loaded, or the stock ROM?
Sorry for all the questions, and hopefully this response doesn't come off rude (I don't mean it to ). I'm just trying to figure out what's going on before I suggest anything.
If you are on Sprint, you can run this recovery from Fastboot USB mode.
Code:
fastboot boot cwm-4.0.1.4-shooter.img
~co~
Click to expand...
Click to collapse
Your questions are really appreciated. Sorry I haven't been more clear.I really appreciate the help as I've gotten myself in trouble here.
I went on htcevohack and found how to flash the synergy infectedrom. The rom has some bugs in it so I downloaded a new rom and placed in the root folder of my SD card. Revolutionary is a program that allows me to wipe data, install from zip card, mount storage so and so forth. I tried to flash the zip from the new rom using this program and this is where I have had the problem. I have the Sprint Evo 3D. I am relatively new to this and just want a stable rom that has wifi tether on it. Thanks again for the help and for the patience.
thealist said:
Your questions are really appreciated. Sorry I haven't been more clear.I really appreciate the help as I've gotten myself in trouble here.
I went on htcevohack and found how to flash the synergy infectedrom. The rom has some bugs in it so I downloaded a new rom and placed in the root folder of my SD card. Revolutionary is a program that allows me to wipe data, install from zip card, mount storage so and so forth. I tried to flash the zip from the new rom using this program and this is where I have had the problem. I have the Sprint Evo 3D. I am relatively new to this and just want a stable rom that has wifi tether on it. Thanks again for the help and for the patience.
Click to expand...
Click to collapse
Oh! Now I know what your talking about. Max from HTCEVOHacks put the Revolutionary branded version of ClockworkMod Recovery in that archive. I know that for a fact (I downloaded it). It's actually the same version of ClockworkMod Recovery that I linked you to.
Okay. Here's my suggestion to start out with. Flash the recovery.img he included (CWM) onto your phone by booting it up into the bootloader, connecting it to your computer making sure that the phone is in FASTBOOT USB mode. Instead of running the command:
Code:
fastboot boot recovery.img
Run the command:
Code:
fastboot flash recovery recovery.img
That will put a copy of ClockworkMod Recovery on your phone. It's accessible by selecting Recovery from the HBOOT menu.
Now, because HTC's Unlock method doesn't unlock enough to flash most images to your phone, you'll still have to run the 'fastboot boot recovery.img' command each time you want to flash different image. That's the classic way we have used to get around HTC's restrictions.
From there, you can flash another image. Make sure to wipe data before flashing.
The reason I told you to also flash the recovery image to your phone is because, you can still create NANDroid backups without connecting to a computer. However, to restore those backups, you'll have to 'fastboot boot ...' the recovery image.
Now, his archive is quite dated. I'd personally recommend after you flash a new ROM, that you take a look at the 4EXT recovery thread in the EVO 3D CDMA development forum. It's really very good (I also like TWRP as well).
Now, there probably wasn't a problem with the ROM. I've used it myself, and have found it to be quite stable. If you flash a ROM onto the phone without wiping data first, you'll probably run into problems booting the ROM. If you liked InfectedRom Eternity, you can always try it again.
This is where NANDroid backups are important. If anything gets messed up, you can easily restore from one in your custom recovery (CWM/4EXT/TWRP).
I hope I didn't throw too much out there. Hopefully this gets you off the ground.
~co~
closeone said:
Oh! Now I know what your talking about. Max from HTCEVOHacks put the Revolutionary branded version of ClockworkMod Recovery in that archive. I know that for a fact (I downloaded it). It's actually the same version of ClockworkMod Recovery that I linked you to.
Okay. Here's my suggestion to start out with. Flash the recovery.img he included (CWM) onto your phone by booting it up into the bootloader, connecting it to your computer making sure that the phone is in FASTBOOT USB mode. Instead of running the command:
Code:
fastboot boot recovery.img
Run the command:
Code:
fastboot flash recovery recovery.img
That will put a copy of ClockworkMod Recovery on your phone. It's accessible by selecting Recovery from the HBOOT menu.
Now, because HTC's Unlock method doesn't unlock enough to flash most images to your phone, you'll still have to run the 'fastboot boot recovery.img' command each time you want to flash different image. That's the classic way we have used to get around HTC's restrictions.
From there, you can flash another image. Make sure to wipe data before flashing.
The reason I told you to also flash the recovery image to your phone is because, you can still create NANDroid backups without connecting to a computer. However, to restore those backups, you'll have to 'fastboot boot ...' the recovery image.
Now, his archive is quite dated. I'd personally recommend after you flash a new ROM, that you take a look at the 4EXT recovery thread in the EVO 3D CDMA development forum. It's really very good (I also like TWRP as well).
Now, there probably wasn't a problem with the ROM. I've used it myself, and have found it to be quite stable. If you flash a ROM onto the phone without wiping data first, you'll probably run into problems booting the ROM. If you liked InfectedRom Eternity, you can always try it again.
This is where NANDroid backups are important. If anything gets messed up, you can easily restore from one in your custom recovery (CWM/4EXT/TWRP).
I hope I didn't throw too much out there. Hopefully this gets you off the ground.
~co~
Click to expand...
Click to collapse
Thanks a lot! I am going to try this right now. I have a mac so I am assuming that I need to use terminal which is what I originally used. Do you know if the extension you provided were also for a mac?
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
GaryWS said:
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
Click to expand...
Click to collapse
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
pruano said:
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
Click to expand...
Click to collapse
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
GaryWS said:
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
Click to expand...
Click to collapse
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
pruano said:
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
Click to expand...
Click to collapse
Pruano, using fastboot, the erase command seems to work but format does not. Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
and just for interest i had to use: "fastboot flash modem modem.img"
GaryWS said:
Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit:and just for interest i had to use: "fastboot flash modem modem.img"
Click to expand...
Click to collapse
Did not know fastboot would recognize that partition, not on the docs.
Always learning.
GaryWS said:
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
Click to expand...
Click to collapse
Yes, unlocked bootloaders do not interfere with OTAs
Regarding the modem, in truth it was a long shot, just a step to restore to pristine state.
The knowledge that the P7500 modem works best with custom ROMs and flashing it as a common procedure is relatively new, no wonder one had to guess that it would interfere with OTAs (as its not obvious, probably the OTA install does some kind of background safety check using the modem firmware as base); good to know for the future.
I'm using an Empire ElectroniX D709 tablet, running Android 4.0.4. It's an old low-spec device, and I'm planning to use this device to improve my Android hacking skills.
I've asked the manufacturers to send me the stock ROM, which they did. Pretty cool!
The problem is that there's no flashing tool or instructions included, and the staff I spoke with did not know how to flash it either.
So now I'm on my own, with a big image file I don't know how to flash.
I tried to start a development thread at the Miscelleaneous Android Development section, but because I have almost no posts, I can't post there. So maybe this is a good place to ask. How can I flash or unpack this image?
You can find the ROM here: http://www.needrom.com/download/empire-electronics-d709/
Exeleration-G said:
I'm using an Empire ElectroniX D709 tablet, running Android 4.0.4. It's an old low-spec device, and I'm planning to use this device to improve my Android hacking skills.
I've asked the manufacturers to send me the stock ROM, which they did. Pretty cool!
The problem is that there's no flashing tool or instructions included, and the staff I spoke with did not know how to flash it either.
So now I'm on my own, with a big image file I don't know how to flash.
I tried to start a development thread at the Miscelleaneous Android Development section, but because I have almost no posts, I can't post there. So maybe this is a good place to ask. How can I flash or unpack this image?
You can find the ROM here: http://www.needrom.com/download/empire-electronics-d709/
Click to expand...
Click to collapse
You have to manually flash them using fastboot. Look up how to get fastboot and move the image(s) to the folder were fastboot.exe is located. Boot into your bootloader either via adb reboot bootloader or by physically doing it from the device. Now here is where most people fail. At the end of the file name, before the .img, it should be either boot, fastboot, recovery or system. If it is system, then do fastboot flash system nameofthesystemimg.img and if it is boot, you get the idea.
Thank you. Fastboot is a good idea. Problem is that I don't know which partition this .img file belongs to. I have the feeling that this file contains every partition, yet I'm not sure how to split it up so that I can flash each partition.
Exeleration-G said:
Thank you. Fastboot is a good idea. Problem is that I don't know which partition this .img file belongs to. I have the feeling that this file contains every partition, yet I'm not sure how to split it up so that I can flash each partition.
Click to expand...
Click to collapse
Will you mind sharing the whole file name? If it is an all partition img you can do fastboot flash all (I think). Just type fastboot and see the all option in the help menu.
Sent using a ks01lte (gt-i9506) running cm 13
RAZERZDAHACKER said:
Will you mind sharing the whole file name? If it is an all partition img you can do fastboot flash all (I think). Just type fastboot and see the all option in the help menu.
Sent using a ks01lte (gt-i9506) running cm 13
Click to expand...
Click to collapse
The full file name is D709_n.img. Theres an option fastboot flashall indeed.
Right now, I'm trying to get the device into fastboot, without success. Things I've tried until now:
Code:
adb reboot-bootloader
adb reboot bootloader
adb reboot fastboot
Every time, the device restarts and just enters the normal mode. I can get into stock recovery, but there's no option to restart to bootloader there.
Exeleration-G said:
The full file name is D709_n.img. Theres an option fastboot flashall indeed.
Right now, I'm trying to get the device into fastboot, without success. Things I've tried until now:
Code:
adb reboot-bootloader
adb reboot bootloader
adb reboot fastboot
Every time, the device restarts and just enters the normal mode. I can get into stock recovery, but there's no option to restart to bootloader there.
Click to expand...
Click to collapse
Hmmm, if you type adb devices, do you see your device there? If not, search online for drivers. If that does not work, google your device and how to get it to fastboot.
RAZERZDAHACKER said:
Hmmm, if you type adb devices, do you see your device there? If not, search online for drivers. If that does not work, google your device and how to get it to fastboot.
Click to expand...
Click to collapse
Yes, it's fully recognized, and I can adb in it just fine. I also get an adb prompt in recovery mode that lets me control the device. The only problem right now is getting this thing to fastboot.
Update
After googling its model number (crane-evb), I found out that this device can be flashed using LiveSuite (described here). It's nice to see the device back in its factory condition. Now I need to find a way to extract the partitions.
[QRCODE][/QRCODE]
Exeleration-G said:
Update
After googling its model number (crane-evb), I found out that this device can be flashed using LiveSuite (described here). It's nice to see the device back in its factory condition. Now I need to find a way to extract the partitions.
Click to expand...
Click to collapse
YaY! I was going to say that in stock recovery there is this option called update via adb or something but now that it is working, there is no need for that.