I need help my EVO 3D is stuck on the second screen that comes up as it boots. It has been unlocked (HTC dev) flashed (4ext) and has a custom rom (Shooter Sense 3.6) on it. I can get it into the bootloader, and into the recovery, but cleverly i forgot to make a stock backup and can't revert from where im at.
Hboot- 1.49.0012
Radio- 10.13.9020.20_M
eMMC-boot.
Thats pretty much all the information i have, other than its a Telstra phone.
you have to manually flash the boot.img using fastboot
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
http://forum.xda-developers.com/showthread.php?t=1752270
EM|NEM said:
the reason its not booting is probably because you didnt flash the boot.img using fastboot. that is required to get roms to boot when you are s-on.
first install the rom from recovery.
then extract the boot.img from the rom zip file(probably in the kernel/shooteru folder) then place it in the folder where you have adb,fastboot and AdbWinApi.dll which you used to unlock.
then open cmd. change directory to the folder containing adb/fastboot.
Connect your phone in bootloader mode and make your it says "fastboot usb"
then type in cmd "fastboot flash boot boot.img"
it should do a process and show that it completed.
then reboot and it should boot up.
all the info you need is here:
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
EM|NEM said:
you have to manually flash the boot.img using fastboot
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
Just gave it a go still on the boot screen for now. heres to hoping.
AndrewMoulakas said:
Just gave it a go still on the boot screen for now. heres to hoping.
Click to expand...
Click to collapse
No luck.
Maybe try a different rom.
And if all else fails you can always use RUU
http://forum.xda-developers.com/showthread.php?t=1208485
---------- Post added at 02:43 PM ---------- Previous post was at 02:41 PM ----------
go to recovery. do factory reset in 4ext and wipe cache+delvik
then install rom.
then flash boot.img in bootloader mode
Its still not working. stuck on the boot screen still. after manually booting with fast boot.
you could make your life so much easier by doing s-off. the rom you are trying to flash requires a newer firmware(which requires s-off).
I think you can update your firmware using an ICS RUU. or you could take the OTA update if its available
EM|NEM said:
you could make your life so much easier by doing s-off. the rom you are trying to flash requires a newer firmware(which requires s-off).
I think you can update your firmware using an ICS RUU. or you could take the OTA update if its available
Click to expand...
Click to collapse
I have S-OFF and i've tried the RUU, and my carrier does not support the ICS OTA update at the moment.
Im giving it a go again now following your instructions to the T.
If you have s-off then just flash the latest firmware in bootloader
http://d-h.st/Mf1
then install the rom. no need for manual flashing of boot.img
should have stated you were s-off :banghead:
IT WORKED!!!!! thanks man. I would have never figured that out on my own or even stumbled upon that other thread. Thank you so much.
glad i could help
Related
Hello community,
today I've made a terrible mistake. In the past I was using a HTC Desire, I got a lot of experience in flashing and ''playing'' on it.
A few weeks ago I've bought the HTC EVO3D and unlocked it with the HTC unlock method today. Up to this point it all worked very well, so in the next step I've decided to get a shiny new custom rom work on it...
I've choosen this one: http://forum.xda-developers.com/showthread.php?t=1647674
The problem was that I have not installed the 4EXT Recovery system in the right way I think, but at this moment I didn't recognize that...
In the process of flashing the rom, I have flashed the kernel manually as the developer says in post #3 on his thread, before flashing the rom itself...this was very stupid...
I flashed this boot.img with the ''fastboot-method'' (cmd) to my phone, it succesfully worked.
The problem is that now nothing happens on the phone after the first HTC-logo shows up, only a black screen. Going to a nandroid-backup isn't possible because of the ''missing'' recovery system (only black screen appears instead of recovery). When I hit the factory reset option in the bootloader it starts the process but after a while (green loading symbol) it only shows a picture with a phone and a red warning symbol.
Is there anything that can be done to get the phone in a working mode, like flashing another kernel or something over ''fastboot-method''? Or is it totally bricked?
(Sorry for bad language/tenses, I'm from Germany)
FIRST LINK. lol on the other section. lol
http://forum.xda-developers.com/showthread.php?t=1563342
YOU SHOULD have waited until we found the correct way to root instead of using the HTC method. lol. but either way. FOLLOW THE INSTRUCTIONS! DONT' FORGET YOU HAVE TO UNDO THE HTC METHOD BEFORE DOING THE ENTIRE PROCESS! or did they fix that? haha I forget.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
wait a second!!!!!! SORRY just re-read some of your post! you used the HTC method TODAY!?!?!!?!?!!? lmao! like I said, follow the CORRECT instructions. the HTC method is a joke.
Sent from my PG86100 using xda premium
Go on fastboot mode. Type in fastboot boot recovery.img ( or whatever the name of your recovery image is)
*learned this the hard way*
---------- Post added at 11:49 PM ---------- Previous post was at 11:39 PM ----------
And also do you have S-ON or S-OFF ....... HBOOT 1.5 or 1.4??
Oh just a tip, never do a factory reset within the bootloader after you have rooted. Also download twrp and flash the .img through fastboot. Then flash a gingerbread Rom with probably a stock kernel. (Again the kernel through fastboot)
------
3(d)vo one s
Newts my hero.
kiewee3 is correct and also you need to be rooted before you install 4ext recovery
but don't forget that the developer never said to do it on a phone without first making sure S=off with the HTC method. it is left on. right?? or did I word that wrong? but you get what I mean. so you need to fully root your phone to prevent issues. make it easier on yourself.
Why don't you just flash the stock ROM? Copy PG86IMG.zip on the SD card via card reader, enter bootloader, let it flash and you are fine... It overwrites everything.
Then just fastboot connect the phone, type "fastboot oem writesecureflag 3" and you are back on the beginning.
is it avilable to downgrade to 1.49.0007 hboot after 1.53 s off with out any problems like hboot version is older?
Since you are s-off, you should be able to flash the older bootloader in fastboot.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
Since you are s-off, you should be able to flash the older bootloader in fastboot.
Save the Drama for your Mama with Tapatalk 2
Click to expand...
Click to collapse
Thank you,so lets wiretrick
coal686 said:
Since you are s-off, you should be able to flash the older bootloader in fastboot.
Save the Drama for your Mama with Tapatalk 2
Click to expand...
Click to collapse
I bought EVO 3D GSM three days ago updated that on OTA at that time it was on HBOOT 1.53.. later unlocked that and flashed recovery.. flashed SU and then flashed Leedroid tweaks... on that my cellphone got into boot loop... after that i have tried to flash few stock roms as well and few custom roms also but still cant get out of boot loop... please guide me how to come out of this and flash some rom i dont mind stock or any custom but just want to get out of this boot loop.. right now i am still on 1.53 and S-ON
That's the problem with s-on. Some roms are not compatible with s-on. Since your stuck on boot loop there are few options. You will have to flasha rom that is compatible with s-on in recovery. I recommend using 4ext recovery since it has smart flash that let's you flash kernels like having s-off. The problem you are having is that when you flash a Rom in recovery it will not flash the kernel because s-on prevents anyone flashing to the boot partition unless you use 4ext recovery, fastboot or joeykrims flash GUI image. Since you cannot use flash image from being in bootloop. Flashing the recovery from fastboot is your easiest option. I'm not very familiar with gsm so do some research and find the right roms for your current device setup.
---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------
Just make sure when you boot into recovery, you enable smart flash first before anything. Make a backup as always. Please hit the thanks button if I helped you in anyway.
---------- Post added at 02:04 PM ---------- Previous post was at 01:33 PM ----------
If all else fails. You could revert back to unrooted stock ics by downloading the right ruu file for your device. Place it on the root of your sdcard and rename it to PG86IMG in all caps. Then relock your bootloader using fastboot. Type fastboot oem lock to do so. The phone will detect this file. Press up to start the update. Of course when its done you just repeat the commands to unlock your bootloader and start fresh all over again.
Hi all,
How to downgrade the HBOOT 1.53.0007 to 1.49.0007 HBOOT ?
It's possible ?
Thank you
hy evevy body
my phone now got black screen after installed chainfire 3d. using ics, root, hboot 1.50 unlock
now i just can enter fastboot via fastboot via terminal in windows,
i just push vol down+power button and then i push power button again to enter fastboot, my scren still black
when i type fastboot devices it shown my device
what can i do with that
thx 4advice
paijo0708 said:
hy evevy body
my phone now got black screen after installed chainfire 3d. using ics, root, hboot 1.50 unlock
now i just can enter fastboot via fastboot via terminal in windows,
i just push vol down+power button and then i push power button again to enter fastboot, my scren still black
when i type fastboot devices it shown my device
what can i do with that
thx 4advice
Click to expand...
Click to collapse
Can you get into the recovery via fastboot?
DjDom said:
Can you get into the recovery via fastboot?
Click to expand...
Click to collapse
i suposed i can.
the step to enter fasfboot are :
1. press vol down+power
2. wait few seconds and then press vol down
3. press power again
i do that with black screen condition
sorry for my bad english
Flash a new bootloader in Fastboot USB and a recovery and you should be able to tweak your way from there by flashing a new ROM.
MistedEvo said:
Flash a new bootloader in Fastboot USB and a recovery and you should be able to tweak your way from there by flashing a new ROM.
Click to expand...
Click to collapse
is "Flash a new bootloader" change the hboot? i mean i`m using hboot 1.50 and i have to update it?
or just change the boot from an ROM.
thx
Blank screen? Mine got stuck on htc logo a while back. It's not meant to be working on ics. I made a backup before, just in case and restored it. All was fine after. Flashing the same rom over, without cleaning any partitions should work fine too. But in your case i am not sure it will work.
put a recovery.img in your fastboot folder and then put your phone in fastboot mode then type "fastboot flash recovery recovery.img" then try to boot recovery again if it still doesnot work, try "fastboot boot recovery.img" but IMO chainfire should not affect your hboot and recovery. If nothing works you can use RUU.
mnomaanw said:
put a recovery.img in your fastboot folder and then put your phone in fastboot mode then type "fastboot flash recovery recovery.img" then try to boot recovery again if it still doesnot work, try "fastboot boot recovery.img" but IMO chainfire should not affect your hboot and recovery. If nothing works you can use RUU.
Click to expand...
Click to collapse
didn't work man :crying::crying::crying::crying:
my lcd still blank
is chainfire 3d flash my gpu firmware, so my gpu got in wrong 'state' so it wont work?
can i reflash my gpu firmware?
I'm a bit confused. So you said the screen is black even while in hboot?
And you are cdma, right? S-on or s-off? And to get into fastboot usb i think it is more like, power off your phone completely, if you were using sense 3.6 rom i guess it is a good idea to remove the battery for a sec in case fast boot was enabled in settings, then pwr+voldwn, wait a moment, pwr again and now you should be on fastboot.
Then on pc make sure you have installed all the required drivers for your phone and download fastboot. Connect your phone to the pc. Copy a recovery.img on the folder on your pc where fastboot executable is located. Then shift + right click on an empty space in that folder and create a terminal (cmd) there. Run fastboot flash recovery.img. then try to boot into recovery again. So shut down your phone again. Then pwr + voldwn. Again voldwn and now it should boot into recovery. You may also use 'fastboot reboot recovery' from fastboot instead of this i guess. If it doesnt work do fastboot boot recovery.img. If you are s-off you can just flash a ruu if it didn't work, but you will lose root ofcourse. If s-on you need to relock bootloader in fastbbot mode with 'fastboot oem lock' and then flash the ruu. I dont have time to find a ruu for you, so you better google for it yourself. Make sure to choose the appropriate ruu for your phone. To flash the ruu you just open the downloaded ruu.exe file and it will start flashind. It will take time and will tell you when it is done. If you are s-off i am not sure if you need to relock the bootloader but i guess you should not. If you are on a custom hboot(only possible if you are s-off), please no way lock your bootloader it will hardbrick it!
You may send me a pm. And i will do what i can to help you.
---------- Post added at 02:44 AM ---------- Previous post was at 02:11 AM ----------
And if you are not s-off i would reccommend you to go s-off after you have fixed this issue. Wire trick is the easiest way to gain s-off imho. Just go to this page and read the info on how to do this. I got s-off on my second try. It must be timed correctly. If anything goes wrong read the troubleshooting section. http://unlimited.io/juopunutbear.htm
And as always, if you need any help feel free to pm me.
MrJyrks said:
I'm a bit confused. So you said the screen is black even while in hboot?
Click to expand...
Click to collapse
yes, my screen is black while in hboot.
MrJyrks said:
And you are cdma, right? S-on or s-off?
Click to expand...
Click to collapse
yes my evo 3d is CDMA in S-on mode, but unlock
MrJyrks said:
Then on pc make sure you have installed all the required drivers for your phone and download fastboot. Connect your phone to the pc. Copy a recovery.img on the folder on your pc where fastboot executable is located. Then shift + right click on an empty space in that folder and create a terminal (cmd) there. Run fastboot flash recovery.img. then try to boot into recovery again. So shut down your phone again. Then pwr + voldwn. Again voldwn and now it should boot into recovery. You may also use 'fastboot reboot recovery' from fastboot instead of this i guess.
Click to expand...
Click to collapse
i have done that step, I have been success when flashing the recovery. when i turned it off, then turn it on again, my screen still black
when i tried boot from recovery boot,my screen still black too.
MrJyrks said:
If s-on you need to relock bootloader in fastbbot mode with 'fastboot oem lock' and then flash the ruu.
Click to expand...
Click to collapse
i'll try this thing
MrJyrks said:
I dont have time to find a ruu for you, so you better google for it yourself. Make sure to choose the appropriate ruu for your phone.
Click to expand...
Click to collapse
what make the rru different from me and the other? how to make sure is that ruu appropriate for my phone?
thanks for all your advice man, i'll try
paijo0708 said:
my phone now got black screen after installed chainfire 3d. using ics, root, hboot 1.50 unlock
Click to expand...
Click to collapse
Did you see this in the description of Chainfire 3D in the description on the Play Store:
!! For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/Ice Cream Sandwich/Jelly Bean !!
Click to expand...
Click to collapse
Given that "NOT COMPATIBLE" is in caps, I'd suggest contacting the developer via his website or email in the Play Store listing and ask him what happens when it's run on ICS.
ramjet73
The RUU should be different on every carrier model and you must download the ICS RUU. For example, if you have a Sprint branded evo 3d, google for sprint evo 3d ics ruu. Also you should know the cdma version of evo 3d is alternatively named shooter and gsm version shooter u. I think it's relatively easy to find a ruu for your device. Please make sure your phones battery is fully charged before flashing and do not remove the usb cable before the process has completed. The ruu should be with .exe file extension. Just run the ruu and read the onscreen instructions.
---------- Post added at 01:21 PM ---------- Previous post was at 01:14 PM ----------
Oh and btw if you have got the wrong ruu the ruu should not flash. And please, dont ever flash CF3D on anything other than GB. And it is safer to have s off in my opinion but you should not do anything stupid if s off because it's easier to revive a s on device if bricked.
---------- Post added at 01:32 PM ---------- Previous post was at 01:21 PM ----------
Oh and as you are s on dont even bother flashing a new hboot as one has adviced.
---------- Post added at 01:40 PM ---------- Previous post was at 01:32 PM ----------
And if you didnt know a ruu will flash a hboot, rom and firmware. It must fix it. If it does not, there must be a hardware problem.
---------- Post added at 01:50 PM ---------- Previous post was at 01:40 PM ----------
And i dont get it why it didn't work. It works perfectly fine on sense 3.6 roms. At least it worked for me with the experimental driver.
---------- Post added at 01:55 PM ---------- Previous post was at 01:50 PM ----------
And use 4ext touch recovery, it seems to be more stable. To install just download app from play store and select install recovery from the app BUT you must be already rooted to flash the new recovery from the app. So to get s off back just do the htcdev method. fastboot flash recovery. Boot into recovery. Flash the root zip and then dl the app. The full version is a better option imho. It costs a little but its worth it.
Sounds like a hardware issue to me. How can CF3D affect hboot and recovery? It only touches the ROM.
@OP do you see a black light when you turn on the phone or your screen does not even light up.
I have installed CF3D on almost every ROM available for CDMA EVO 3D , just to mess around and it does not affect anything except the 3D graphics in games .They will get better or in worst case no 3D games at all only black screen but 2D HUD menu etc are visible.
And go s-off with juopunutbear. It is super easy with the correct timing. I watched a video to get the correct timing. And as far as i know s off should be required for jellybean roms.
---------- Post added at 02:09 PM ---------- Previous post was at 02:04 PM ----------
You just better flash a ruu. I dont think it is a hw issue if you had the screen functioning just before installing cf3d.
---------- Post added at 02:13 PM ---------- Previous post was at 02:09 PM ----------
If it doesnt work after flashing a ruu there is nothing we could do and you need to send it in for repair.
Nexus 7 (2013) black screen after installing chainfire 3D
paijo0708 said:
hy evevy body
I need help, plss
After install chainfire 3D on my nexus he is turn off,and i turn on but when is turn on,screen is black,and i can't fix.
I'm try wipe reset/factory but don't work,i connect with PC,but i can't see on PC my nexus,
How fix this problem
Plss help me
Thanks
Sry on my bad english
Click to expand...
Click to collapse
Yes, brick my phone, my htc evo 3D with Hboot 1.58, Unlocked Bootloader.. I tried to flash the CyanogenMod Gangnam Style, with 4ext recovery, and stuck on Boot Animation.. I accidentally format system in te recovery, there is a solution? Thanks!
If you are s off you need to do downgrade your boot loader. If you are s on you needed to do the write trick then downgrade your boot loader.
To get your phone in order now, Download a sense 3.6 rom and format everything but sd card in recovery and flash it, Make sure you read up on the requirements to flash next time, All roms have certain hboot's you have to be on.
---------- Post added at 04:33 AM ---------- Previous post was at 04:32 AM ----------
Your the same person I was working to unlock the bootloader this morning with, You've already messed up again
Can't_Live_Without_My_Evo said:
To get your phone in order now, Download a sense 3.6 rom and format everything but sd card in recovery and flash it, Make sure you read up on the requirements to flash next time, All roms have certain hboot's you have to be on.
---------- Post added at 04:33 AM ---------- Previous post was at 04:32 AM ----------
Your the same person I was working to unlock the bootloader this morning with, You've already messed up again
Click to expand...
Click to collapse
I was thinking more about getting cm to work and forgot the part about just getting the phone to work at all. Probably a better route :beer:
isaacsosa said:
Yes, brick my phone, my htc evo 3D with Hboot 1.58, Unlocked Bootloader.. I tried to flash the CyanogenMod Gangnam Style, with 4ext recovery, and stuck on Boot Animation.. I accidentally format system in te recovery, there is a solution? Thanks!
Click to expand...
Click to collapse
You can not install Cm 10 or 9 with Hboot 1.58..... you need to S-off and downgrade it to hboot 1.49 ....do the wire trick to downgrade it.....ATM you still can get to bootloader right?? so it is sofbrick and very easy to fix....download the correct RUU and flash it...With hboot 1.58 you can install rom with sense only...
Can't_Live_Without_My_Evo said:
To get your phone in order now, Download a sense 3.6 rom and format everything but sd card in recovery and flash it, Make sure you read up on the requirements to flash next time, All roms have certain hboot's you have to be on.
---------- Post added at 04:33 AM ---------- Previous post was at 04:32 AM ----------
Your the same person I was working to unlock the bootloader this morning with, You've already messed up again
Click to expand...
Click to collapse
You are my god, look i need the rom, im looking for the rom all the day but nothing :/ where i can get it? And, how i can flash back?
Thanks For all dude
isaacsosa said:
You are my god, look i need the rom, im looking for the rom all the day but nothing :/ where i can get it? And, how i can flash back?
Thanks For all dude
Click to expand...
Click to collapse
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1 .09.00.0706_signed.exe
Search for that on google, Add the word download, Shouldn't be too hard.
Can't_Live_Without_My_Evo said:
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1 .09.00.0706_signed.exe
Search for that on google, Add the word download, Shouldn't be too hard.
Click to expand...
Click to collapse
problem solved! i lock the bootloader and run the RUU, my phone is working now! Thanks! regards
isaacsosa said:
problem solved! i lock the bootloader and run the RUU, my phone is working now! Thanks! regards
Click to expand...
Click to collapse
Alright, You're allowed 8 thanks a day, I expect to see some of them lol.
Ok i am running a stock tmobile rom 1.27.531.11 with s-off , rooted and custom recovery.
I flash the stock recovery and try to install the update it says
finding update package
opening update package
virifying update
installing update
waring: no file_contextsVerifying current system
assert failed: apply_patch_check(/system/bin/app_process",
after the , is to long numbers looks like a checksum mismatch to me but im unsure. I would like to know how to i fix this?
xile6 said:
Ok i am running a stock tmobile rom 1.27.531.11 with s-off , rooted and custom recovery.
I flash the stock recovery and try to install the update it says
finding update package
opening update package
virifying update
installing update
waring: no file_contextsVerifying current system
assert failed: apply_patch_check(/system/bin/app_process",
after the , is to long numbers looks like a checksum mismatch to me but im unsure. I would like to know how to i fix this?
Click to expand...
Click to collapse
I was running a custom ROM with custom recovery, s-off, rooted and my cid was 11111111(? how many 1's is that) . anyways what i did i just flashed a stock RUU and it went through fine then from there i just did a normal update through the phone settings.
---------- Post added at 07:58 PM ---------- Previous post was at 07:55 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
compta5 said:
I was running a custom ROM with custom recovery, s-off, rooted and my cid was 11111111(? how many 1's is that) . anyways what i did i just flashed a stock RUU and it went through fine then from there i just did a normal update through the phone settings.
---------- Post added at 07:58 PM ---------- Previous post was at 07:55 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
Click to expand...
Click to collapse
thanx for the help.
It probably dont mater anymore now tho. I ended up soft brciking the phone, (son was jumpping around and i eneded up hiting factory reset)
I think im going to im going to end up losing all me stuff :crying:
but im doing the ruu now and i will see what happens. Hopefully i can recover some of my pictures and stuff.
And i did do a nano backup but like a dumba.. i didnt transfer it to the laptop. Also forgot that the data/system is one and no sd card
I give from now on ill do weekly data backups.
I have same problem.
Flashed stock recovery , but still same...
I have unlocked bootloader and s-off (with t-mob cid, ect)
What to do? S-on? Don't really think it causes problem
tried S-on , but still same
"warning no file_contexts verifying current system" ...
jkjambo said:
I have same problem.
Flashed stock recovery , but still same...
I have unlocked bootloader and s-off (with t-mob cid, ect)
What to do? S-on? Don't really think it causes problem
Click to expand...
Click to collapse
Dont flash stock recovery. You have to flash the 1.27 RUU which will flash stock hboot, recovery, and ROM.
blackangst said:
Dont flash stock recovery. You have to flash the 1.27 RUU which will flash stock hboot, recovery, and ROM.
Click to expand...
Click to collapse
i have stock recovery and stock rom , so i'll flash now just hboot . if this will not help me , then i'll try whole Ruu (i'm too lazy to download and install that )
don't know why , but i couldn't install htboot , so donwloading 1.27.531.8 (Downgreader) ...