[Q] Wont load past white HTC screen. - HTC Rezound

Just flashed the latest MIUI Rom and now I can't get passed the White screen with the green "HTC"
Do I have to have S-off?
I've had my rezound unlocked since the day I got it 8 months ago but just now decided to flash it, I used to have a INC and rooted and flashed that years ago but i'm a little rusty now,

Burnz92 said:
Just flashed the latest MIUI Rom and now I can't get passed the White screen with the green "HTC"
Does I have to have S-off?
I've had my rezound unlocked since the day I got it 8 months ago but just now decided to flash it, I used to have a INC and rooted and flashed that years ago but i'm a little rusty now,
Click to expand...
Click to collapse
If you are s-on, you have to flash the kernel separately. I'm not familiar with the MIUI rom, but go back and read the installation instructions but it certainly sounds like that is your problem.

topgun1953 said:
If you are s-on, you have to flash the kernel separately. I'm not familiar with the MIUI rom, but go back and read the installation instructions but it certainly sounds like that is your problem.
Click to expand...
Click to collapse
This. If you're S-ON, you have to extract the boot.img from the .zip and flash it manually.

shrike1978 said:
This. If you're S-ON, you have to extract the boot.img from the .zip and flash it manually.
Click to expand...
Click to collapse
How do I manually flash it?

Burnz92 said:
How do I manually flash it?
Click to expand...
Click to collapse
fastboot flash boot boot.img
Sent from my ADR6425LVW using Tapatalk 2

shrike1978 said:
fastboot flash boot boot.img
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
whenever I go to fastboot on my phone(it says "FASTBOOT USB" in highlighted red) and type 'adb devices" it doesn't return anything.
What ive done leading up to the point.
1. Booted in to rec from my phone and flash the rom
2. Rebooted phone with down vol pressed
3. Went to fastboot
4. Pulled up CMD and did cd:...etc
5. Typed adb devices and it doesnt retun anything.
Im about to turn s-off unless im missing something here.
Btw WAR EAGLE

shrike1978 said:
This. If you're S-ON, you have to extract the boot.img from the .zip and flash it manually.
Click to expand...
Click to collapse
How does one manually flash the boot.img?
Sorry I did not see the previous post. I assume you must use a PC for this action and have the fastboot.exe from the SDK toolkit.

Burnz92 said:
whenever I go to fastboot on my phone(it says "FASTBOOT USB" in highlighted red) and type 'adb devices" it doesn't return anything.
What ive done leading up to the point.
1. Booted in to rec from my phone and flash the rom
2. Rebooted phone with down vol pressed
3. Went to fastboot
4. Pulled up CMD and did cd:...etc
5. Typed adb devices and it doesnt retun anything.
Im about to turn s-off unless im missing something here.
Btw WAR EAGLE
Click to expand...
Click to collapse
Fastboot and adb are two different things.

Burnz92 said:
whenever I go to fastboot on my phone(it says "FASTBOOT USB" in highlighted red) and type 'adb devices" it doesn't return anything.
What ive done leading up to the point.
1. Booted in to rec from my phone and flash the rom
2. Rebooted phone with down vol pressed
3. Went to fastboot
4. Pulled up CMD and did cd:...etc
5. Typed adb devices and it doesnt retun anything.
Click to expand...
Click to collapse
What version of Windows are u running? I was having similar problems on Windows 8 and I think it was a driver issue. I never resolved the problem, just switched to a laptop running something other than Win8. Worked like a charm then! Are you using Hasoon All In One tool? That may help if ur a little n00bish like me!
Sent from my Rezound using xda app-developers app

stankopp said:
How does one manually flash the boot.img?
Sorry I did not see the previous post. I assume you must use a PC for this action and have the fastboot.exe from the SDK toolkit.
Click to expand...
Click to collapse
yes you need a pc. have fastboot as well as adb installed and working. if you do not have fastboot downloaded and installed, it will NOT work. if you dont have it just google it and it shouldnt be hard to find. Also, you must have the correct drivers installed for the rezound
1. Open the rom.zip file (that you download) and extract the boot.img file to the same directory that fastboot is installed.
2. Put the rom.zip file on the root of your sd card.
the rest is done from the command line
3. In command prompt, run "adb devices" and confirm that your phone shows up. (if yes, proceed) (if not, go back and confirm you have the correct drivers installed)
4. run "adb reboot recovery", wipe, and flash your rom in recovery (self explanitory) if you need help with this part, im sorry.
5. after the rom finishes its flashing process, run "adb reboot bootloader"
6. when the bootloader comes up, run "fastboot flash boot boot.img"
7. after that flashes, you should be good to go. just run "fastboot reboot" and youre done

Related

sd card not recognized s-off

After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
iflawdya said:
After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
Click to expand...
Click to collapse
Download this:
http://dl.dropbox.com/u/14779955/jb_hboot.zip MD5: b05336c08f709bf0a909205bcb95b951
but the file in the adb folder where you use cmd
Put the phone in fastboot mode, then run the follwoing commands:
Code:
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot
iflawdya said:
After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
Click to expand...
Click to collapse
You haven't got s-off right? You got stuck there while trying to?
Sent from my HTC Vigor
Andro X said:
You haven't got s-off right? You got stuck there while trying to?
Sent from my HTC Vigor
Click to expand...
Click to collapse
Correct. Not there and screwed up 2 16gb cards in the process.
iflawdya said:
Correct. Not there and screwed up 2 16gb cards in the process.
Click to expand...
Click to collapse
You should only have used the one. It seems others have been able to correct the issue by simply reformatting the card with the phone, not via a USB connection to a computer.
a.mcdear said:
You should only have used the one. It seems others have been able to correct the issue by simply reformatting the card with the phone, not via a USB connection to a computer.
Click to expand...
Click to collapse
How would I reformat the card with the phone? I am stuck at juopunutbear screen. I can only get to fastboot screen. From there it says no image.
iflawdya said:
How would I reformat the card with the phone? I am stuck at juopunutbear screen. I can only get to fastboot screen. From there it says no image.
Click to expand...
Click to collapse
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
cflo360 said:
Download this:
http://dl.dropbox.com/u/14779955/jb_hboot.zip MD5: b05336c08f709bf0a909205bcb95b951
but the file in the adb folder where you use cmd
Put the phone in fastboot mode, then run the follwoing commands:
Code:
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot
Click to expand...
Click to collapse
cflo360 when I get to fastboot flash zip jb_hboot.zip it gets an erroe that says failed remote: 99 unknown fail. Any ideas? Would it be possible to just put a rom on another sd card and flash it?
a.mcdear said:
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
Click to expand...
Click to collapse
sorry I was typing a question and did not see what you wrote before I sent it.
a.mcdear said:
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
Click to expand...
Click to collapse
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
iflawdya said:
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
Click to expand...
Click to collapse
Pull your battery.. reinsert and hold volume down and the power button. Make sure phone is plugged in or replug in phone if you took it off to reboot. Should be in Hboot now, press power to select fastboot if it is white lettering over blue background. If it is red background your already in fastboot and if connected should say fastbootusb.
1. open a copy of the rom your on either with 7 zip or since your not adding anything to it unzip it .
2. find the folder that says kernel, now you will either see a PH98IMG.zip or you will see a file that his white with a silver circle called boot. That is the raw boot.img. If it is the ph zip simply unzip it and you will see the boot.img.
3. Now , remove the boot.img and place it in the same folder your fastboot is located , generally the place you unlocked with.
4. Then, bring up a command prompt the same way you did to unlock. change directory if needed by cd c:\thenthenameofthefoldrecontainingfastboot.
5. Simply type fastboot boot boot.img
6. you will see sending " size of img".. receiving "size of img ", then writing .. and it will end and tell you how many seconds it took.
Now, simply use the reboot selection from bootloader or with the command prompt type abd reboot and your phone should reboot and you will be back on your rom.
The reason you keep booting to the jBear screen is because the jBear process replaced your KERNEL. You need to find the kernel img file for YOUR operating system or ROM. If you are on GB, find a GB kernel. If on the ICS Leak, you need to find the ICS Leak kernel. If on a ROM, get that ROM's kernel file.
Then the commands on the PC are:
fastboot flash boot boot.img
fastboot reboot
Another option is to use Hansoon's Rezound All-in-one-kit to flash the stock kernel for you.
Howard
iflawdya said:
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
Click to expand...
Click to collapse
no offense, but if you honestly cannot at least search to figure out how to do a fastboot command as simple as fastboot flash, then you should stay clear of s-off...
but that's my opinion.
and I'm really not saying this to be an ass.
just don't want to see you brick your phone.
mjh68 said:
Pull your battery.. reinsert and hold volume down and the power button. Make sure phone is plugged in or replug in phone if you took it off to reboot. Should be in Hboot now, press power to select fastboot if it is white lettering over blue background. If it is red background your already in fastboot and if connected should say fastbootusb.
1. open a copy of the rom your on either with 7 zip or since your not adding anything to it unzip it .
2. find the folder that says kernel, now you will either see a PH98IMG.zip or you will see a file that his white with a silver circle called boot. That is the raw boot.img. If it is the ph zip simply unzip it and you will see the boot.img.
3. Now , remove the boot.img and place it in the same folder your fastboot is located , generally the place you unlocked with.
4. Then, bring up a command prompt the same way you did to unlock. change directory if needed by cd c:\thenthenameofthefoldrecontainingfastboot.
5. Simply type fastboot boot boot.img
6. you will see sending " size of img".. receiving "size of img ", then writing .. and it will end and tell you how many seconds it took.
Now, simply use the reboot selection from bootloader or with the command prompt type abd reboot and your phone should reboot and you will be back on your rom.
Click to expand...
Click to collapse
mjh68 I LOVE YOU MAN!! Thank you so much.
HowardZ said:
The reason you keep booting to the jBear screen is because the jBear process replaced your KERNEL. You need to find the kernel img file for YOUR operating system or ROM. If you are on GB, find a GB kernel. If on the ICS Leak, you need to find the ICS Leak kernel. If on a ROM, get that ROM's kernel file.
Then the commands on the PC are:
fastboot flash boot boot.img
fastboot reboot
Another option is to use Hansoon's Rezound All-in-one-kit to flash the stock kernel for you.
Howard
Click to expand...
Click to collapse
I tried the all in one and it did not work. I was stuck at htc splash screen.
andybones said:
no offense, but if you honestly cannot at least search to figure out how to do a fastboot command as simple as fastboot flash, then you should stay clear of s-off...
but that's my opinion.
and I'm really not saying this to be an ass.
just don't want to see you brick your phone.
Click to expand...
Click to collapse
None taking but if I don't know whats wrong how am I gonna search? Instead of telling me about the search button which yields thousands of threads how about helping me out. As you can see I have been a member for a long time. I didn't just pop on this site because I screwed up. I was up till 4 am trying to figure this out before asking for help.

relocking rezound

Trying to re-lock my Rezound using fastboot. When I dbl click fastboot on PC, a black cmd window briefly flashes then disappears. help?
fastboot is a command line app. Open a command window and type "fastboot oem lock"
that's what i tried first, then got a "waiting for device" message. I figured i didn't have my phone set right? here was my process...
1. rebooted phone to hboot
2. connected to computer
3. opened command window
4. cd to the correct directory
5. typed the "fastboot oem lock" command
6. received "waiting for device" message
???
novakrj said:
that's what i tried first, then got a "waiting for device" message. I figured i didn't have my phone set right? here was my process...
1. rebooted phone to hboot
2. connected to computer
3. opened command window
4. cd to the correct directory
5. typed the "fastboot oem lock" command
6. received "waiting for device" message
???
Click to expand...
Click to collapse
Make sure you go into fastboot once you're in the HBoot menu or it won't be able to communicate with the device
Make sure you have HTC Sync or some other Rezound-compatible drivers installed. It needs that for fastboot and adb to communicate with your phone.
dplane said:
Make sure you go into fastboot once you're in the HBoot menu or it won't be able to communicate with the device
Click to expand...
Click to collapse
You have to be I fast boot, hboot
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
Same thing happened to me. Make sure when you plug in the usb cable, the phone connects as a disk drive, not charge only.
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
ended up i needed both bits of advice.
I hadn't reinstalled htc sync files since a pc reformat a month ago, and i needed to enter fastboot once in hboot.
thanks guys
Mr. Boom said:
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
no.
fastboot oem lock is changing hboot to relocked
s-on command is something like fastboot write secureflag3 or something- look it up don't use what i just posted. if you do go s-on make sure you just ran a RUU
Mr. Boom said:
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
"Fastboot OEM lock" is to lock the bootloader.
"Fastboot OEM writesecureflag3" is to go back to s-on
Sent from my Galaxy Nexus
1. Reboot to fastboot.
This can be done in 3 ways:
A. from the power menu (assuming the rom has it
B. Shut down completely. Battery pull to make sure. Then hold press amd hold Vol Down, then press and hold Power and keep holding down both.
C. Use the command:
adb reboot bootloader
2. Use fastboot to relock bootloader.
Sent from my Rezound
since last we spoke...
was able to relock
flashed the ruu to get back to stock
updated OTA to ICS
unlocked again
flashed aman ra in fastboot
rebooted
the plot thickens...
when i reboot to recovery, it reboots to android stock, not aman ra, hence, no root?
thoughts?
novakrj said:
since last we spoke...
was able to relock
flashed the ruu to get back to stock
updated OTA to ICS
unlocked again
flashed aman ra in fastboot
rebooted
the plot thickens...
when i reboot to recovery, it reboots to android stock, not aman ra, hence, no root?
thoughts?
Click to expand...
Click to collapse
just try flashing Amon Ra again
should i wipe anything first?
novakrj said:
should i wipe anything first?
Click to expand...
Click to collapse
No, just fastboot flash.
Sent from my Rezound
still no go on second flash attempt. still showing android system recovery, not aman ra. tried to install su superuser in the developer menu in android system recovery to achieve root but didn't take.
thanks if anybody has any ideas. I'll just keep searching threads...i usually miss something pretty obvious.
edit: just in case this helps...
when i boot into recovery the top of the screen reads "Android system recovery"
at the bottom of the screen it says:
RA Revamped
Build: RA VIGOR-v3.15-getitnowmarketing
novakrj said:
still no go on second flash attempt. still showing android system recovery, not aman ra. tried to install su superuser in the developer menu in android system recovery to achieve root but didn't take.
thanks if anybody has any ideas. I'll just keep searching threads...i usually miss something pretty obvious.
edit: just in case this helps...
when i boot into recovery the top of the screen reads "Android system recovery"
at the bottom of the screen it says:
RA Revamped
Build: RA VIGOR-v3.15-getitnowmarketing
Click to expand...
Click to collapse
Yeah that's amon ra.
Now flash the SuperSu zip file.
(the install su doesnt work last time I checked.)
You can get the SuperSu zip in Ashton's ICS thread.
Sent from my Rezound
beautiful....Thank you!

Bootloop please help.

*Fixed*
uppon2 said:
I just go the phone today and I have unlocked it and it all went well. I was looking at installing ViperDNA on to my phone. So I started to follow instructions in the Viper thread
1. I "tried" to install TWRP through the Goo method and after downloading the file it told me that recovery was no installed.
2. I rebooted in to bootloader and hit power button to enter fastboot then I scrolled down to where it says recovery and I hit power again. Phone displayed a message up the top that it was now entering recovery. The phone did not go to recovery it simply rebooted all the way back to my phones home screen.
I then though hmm well maybe I didn't install it properly so I follwed the instructions using Goo again but still nothing happened.
I noticed there was an alternative method to flash recovery by using ADB. I put the file in to the same directory as where my adb/fastbood reside and I booted in to fastboot again and in cmd prompt I entered "flash recovery openrecovery-twrp-2.4.0.0-dlx.img"
It seemed to flash and gave me a response which I can't remember now but it said OK!.
I then proceeded to try and enter recovery again but this time it has sent my phone in to a bootloop. It will not pass the Droid splashscreen. I can however still access bootloader mode.
I also noticed now in my Bootloader above where it says Unlocked it also says Tampered?
Phone doesn't seem to be recognised by ADB anymore neither. adb devices returns with a blank space
I'm a long time Samsung user so usually in this situation I would use Odin and flash a stock firmware but I don't know the process with HTC
I don't have a backup because I hadn't got to this stage yet!
Any advice as to what to do now
Click to expand...
Click to collapse
if you can still get the phone into fastboot mode then you should be fine.. when in fastboot mode the command "adb devices" will not return any entries.. when in fastboot you should use the command
fastboot devices
and see if your phone shows up there.. also the command for flashing a recovery in fastboot is:
fastboot flash recovery "your recovery filename.img" without the quotations though..
so the exact command would be the fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img if that is what the recovery file on your computer is named.
then hit enter it should say sending etc...
I always then do the command
fastboot reboot-bootloader then the phone will reboot into the fastboot screen, then manually select recovery and see that it worked that time.
lazarus2297 said:
if you can still get the phone into fastboot mode then you should be fine.. when in fastboot mode the command "adb devices" will not return any entries.. when in fastboot you should use the command
fastboot devices
and see if your phone shows up there.. also the command for flashing a recovery in fastboot is:
fastboot flash recovery "your recovery filename.img" without the quotations though..
so the exact command would be the fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img if that is what the recovery file on your computer is named.
then hit enter it should say sending etc...
I always then do the command
fastboot reboot-bootloader then the phone will reboot into the fastboot screen, then manually select recovery and see that it worked that time.
Click to expand...
Click to collapse
After attempting this it hangs here:
C:\Android-adb>fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img
< waiting for device >
EDIT* Rookie mistake for it hanging. I was only in bootloader not Fastboot. However, this worked and I love you. I will now flash Viper. Do I still need to flash the Kernel Modules?
uppon2 said:
After attempting this it hangs here:
C:\Android-adb>fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img
< waiting for device >
EDIT* Rookie mistake for it hanging. I was only in bootloader not Fastboot. However, this worked and I love you. I will now flash Viper. Do I still need to flash the Kernel Modules?
Click to expand...
Click to collapse
flashing the modules for the kernel is always a good idea just flash that after you flash your ROM..
and you are welcome just glad I could help!!
lazarus2297 said:
flashing the modules for the kernel is always a good idea just flash that after you flash your ROM..
and you are welcome just glad I could help!!
Click to expand...
Click to collapse
lol. Now Aroma is being a pain in the ass. It won't let me click Next to install. haha
EDIT* Maybe because of the smaller TWRP or maybe not but I had to try again and then click next but about 2" higher than where it says it :S
I am not a huge fan of aroma... i had issues when i tried to flash my DNA the first time.. that is something that you just have to keep trying unfortunately it seems... i have seen where people had to aroma freeze on them multiple times before finally completing the flash... some tips i have seen is keep the phone flat... also keep it plugged in.. I can't vouch for any of these being actual fixes but hey "it's only weird if it doesn't work"
Do you know the load time on a ROMs first boot after flash?
The ROM said it was installing and at about 8% the screen went all grey and then rebooted in to the HTC splash screen and hasn't changed for about 15 minutes. Tried it twice
EDIT* Would only flash using CWM
uppon2 said:
Do you know the load time on a ROMs first boot after flash?
The ROM said it was installing and at about 8% the screen went all grey and then rebooted in to the HTC splash screen and hasn't changed for about 15 minutes. Tried it twice
EDIT* Would only flash using CWM
Click to expand...
Click to collapse
glad to hear it sorry for the slow response.. i was away for a bit..
lazarus2297 said:
glad to hear it sorry for the slow response.. i was away for a bit..
Click to expand...
Click to collapse
All good. Thanks for your assistance
I am usually the guy helping other people. It's quite an unusual change going from Samsung to HTC!

[Q] EVO stuck in bootloop

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

Boot loop problem! Please help!

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 ...

Categories

Resources