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!!
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.
Was running cm10 did a a wipe and restored to previious rom, and it won't boot.. Just boot loops.. Anyway to get my phone working again> I can access recovery still
most likely an s-on issue, you need to flash the kernel separately in fastboot. it has to match your backup's rom base
om4 said:
most likely an s-on issue, you need to flash the kernel separately in fastboot. it has to match your backup's rom base
Click to expand...
Click to collapse
Can you go in detail for me please
You need the boot image from the Rom you made a back up of, it has to match the base at the time of the backup 1.22, 2.13 or what have you and it needs to be flashed in fastboot. To do so you need the mini SDK (adb tools) or the full sdk. Place the boot.img (kernel) into the directory and open a terminal. Navigate to the directory or open it directly in the folder (windows) by holding shift and right click and slecting open command window here. You then boot to bootloader and connect the phone in fastboot. Type devices to make sure its connected and then fastboot flash boot boot.img and reboot
Easiest way is download flashgui and then download meanrom and open up meanrom via flashgui on phone and flash the stock kernel then boot into recovery and then flash your.restore and wala!!! That's what I had to do being s on
Sent from my EVO using xda app-developers app
on my phone i tried updating to the Mean bean and of course i didnt read it all i used the flash apk app to get the rom wiped data all that installed fined boot animation came up and evey thing and i found out you need to be on latest firm ware and wich im not and my phone did not boot and i have nan droid back up is there a way to flash a new kernel in adb or no ? please helpp im s-on 1.15 and yes i still can go into recovery
You need to be S-Off to get the updated firmware. Without S-Off you would need to RUU and take the OTA to get the firmware. Read here: http://forum.xda-developers.com/showthread.php?t=1671577&highlight=ruu
To flash kernels while S-On download from Market "Flash image GUI" extract the "boot.img" file and push it in with this app. Then immediately go to recovery and flash the ROM zip.
slagle96 said:
on my phone i tried updating to the Mean bean and of course i didnt read it all i used the flash apk app to get the rom wiped data all that installed fined boot animation came up and evey thing and i found out you need to be on latest firm ware and wich im not and my phone did not boot and i have nan droid back up is there a way to flash a new kernel in adb or no ? please helpp im s-on 1.15 and yes i still can go into recovery
Click to expand...
Click to collapse
All you've got to do is fast boot the kernel, the firmware is recommended not a necessity
Mean bean has s-on kernel installer so maybe that's not the issue
{ParanoiA} said:
Mean bean has s-on kernel installer so maybe that's not the issue
Click to expand...
Click to collapse
how can i fast boot the kernel ?
{ParanoiA} said:
Mean bean has s-on kernel installer so maybe that's not the issue
Click to expand...
Click to collapse
it may not be but when i was s on i found that the kernel did not flash right every time best i can say is to start over wipe system and data it is a os upgrade and is manditory then flash rom if still a no boot fastboot the kernel. or let the raccoon out of the fridge to get s off not that hard to do
fast boot
This looks long, buts its just the initial setup too
If you aren't familiar with doing things from fastboot, chances are the first thing you are going to need to do is properly setup the folders to carry out the fastboot flash command. This setup is going to take the most time and after you have it all set up its very quick to do after that.
Setting up ADB:
1) Download the mini-SDK here and move it to something like C:\Android\platform-tools
http://androidforums.com/attachment...90-adb-guide-updated-12-05-2011-sdk-tools.zip
It contains:
adb.exe - Windows adb utility
fastboot.exe - Windows fastboot utility
fastboot-windows.exe - Windows fastboot utility
AdbWinApi.dll - adb link library for Windows
AdbWinUsbApi.dll - adb link library for Windows
These files will be used to push the boot.img (contains the kernel) from a ROM to your phone via fastboot.
2) Download your ROM and open it,
3) Copy the boot.img from the ROM to the same folder as the mini SDK you've downloaded.
4)Plug your phone into the computer via USB and power the phone off. Then press volume down + Power to get to fastboot
5)Once there, we need to open up a command prompt in the location where your sdk-tools are. If you are in windows 7 you can just shift+right click to select "open command prompt from here"
If you don't have win 7 you can manually move to the file location with the command cd to change directory.
6)Once you are in the correct directory you just type in
Code:
fastboot flash boot boot.img
and hit enter
7)reboot
or use this choose the JB only version http://forum.xda-developers.com/show....php?t=1917106
Alright, so i have an EVO 4g lte and i attempted to root it today. It didnt turn out very well to say the least... I unlocked bootloader and flashed TWRP recovery.I then flashed superSU, and at the same time i flashed a custom rom and gapps zip. Then hit reboot. It has not booted up since.. It will just sit at the white HTC screen. i tried clearing cache and Dalvik cache, also did a factory reset. tried flashing cm10 rom onto the device as well as a rooted stock rom. nothing works! the farthest i have gotten was with the cm10 rom and it went to the cyanogenmod boot logo but was in bootloop still. I downloaded the ADT tool bundle but the phone wont show up on the device list. Can anyone help? im completely stumped.. Im fairly new to rooting and custom roms, but i have rooted multiple tablets and samsung galaxy phones and havent had any issues. this is my only phone also, i just gave my backup to my mother because her phone broke... please if anyone knows how to fix this let me know. when i boot into recovery mode it says Tampered and Unlocked at the top as well as S-On. I can also go into TWRP recovery with no problems. just cant use fastboot with my computer (windows 7 PC).
I am pretty sure i know what i did wrong, I flashed SuperSU to gain root at the same time i flashed the custom rom and gapps.. on all the other devices i would reboot after root and then flash the custom rom seperately.. but is there a way to correct my mistake?
Since you are s-on you have to fastboot flash the boot.img/kernel first and then flash CM and gapps
Any questions PM me
OK sorry to be a noob but how do I do that? I used cmd.exe while rooting but now it won't recognize my device. Much thanks for any help!!
Sent from my GT-P5110 using xda app
If in bootloader type fastboot devices
In recovery type adb devices
See if you get a reply
In fast boot USB menu on the phone, I typed fastboot devices on cmd and it came up blank.
Sent from my GT-P5110 using xda app
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
bigdaddy619 said:
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
Click to expand...
Click to collapse
ok ill uninstall all that and give it a try. is pm a better contact method for you?
AUSRA15 said:
ok ill uninstall all that and give it a try. is pm a better contact method for you?
Click to expand...
Click to collapse
Here is fine
bigdaddy619 said:
Here is fine
Click to expand...
Click to collapse
OK rebooting now I'll see if it uninstalled everything.
:fingerscrossed:
OK were connected now, now what? :good:
PC and phone are talking ?
fastboot devices
yes they are talking now. fastboot devices and my phone shows up.
i tried fastboot flash boot.img but it wont recognize the command, i placed the boot.img file into the platform-tools folder inside my C drive. what am i doing wrong? its late at night and im frustrated so i know im screwing something up...
ok good BTW which version of twrp are you using? Let me know before you continue.
pull the boot.img from the rom zip and copy it to the folder you opened your cmd window from
then type fastboot boot boot.img
once it says successful press the power button to return to HBOOT and use the vol keys to navigate to recovery
Once there choose wipe and wipe cache/dalvik cahce/system/data or factory reset depending which version of twrp you are using
then flash CM and gapps
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
AUSRA15 said:
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
Click to expand...
Click to collapse
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
bigdaddy619 said:
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
Click to expand...
Click to collapse
same thing, cannot load unknown error. also i am using twrp 2.6.0.0
Ok lets try something different at least it will get you up and running
Get twrp v2.4.1.0 from http://techerrata.com/browse/twrp2/jewel
put it in the same folder you are using and we will downgrade your twrp for now
copy and paste this in the cmd window
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
then fastboot erase cache
ok got the twrp done succesfully as well as the wipe cache. whats next? i think i figured out what i was doing wrong, i hadnt opened the file directory. cd downloads, cd android files, etc.
should i try going into recovery now on the phone and flash a rom, or should we stay on fastboot and push the boot.img?
Easiest way to open a cmd window is to press shift and right click inside the folder and choose open cdm window here
That way you know you are in the correct folder.
Yeah go ahead and try to flash the boot.img again
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.