Related
I had an issue with my phone a couple of weeks ago where I'm only able to the bootloader screen and the fastboot screen. Fortunately, I got a replacement EVO 3 days later but I'm still trying to get my old phone up and running. But after trying everything I can find, still nothing.
So my question is, when do I say that the phone is officially bricked?
Sent from my PC36100 using Tapatalk
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
dwelder said:
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
Click to expand...
Click to collapse
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Were you using CM7 before your phone started bootlooping?
Concordium said:
Were you using CM7 before your phone started bootlooping?
Click to expand...
Click to collapse
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
andygu3 said:
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
andygu3 said:
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Have you tried flashing the images via fastboot?
Concordium said:
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
Click to expand...
Click to collapse
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
teh roxxorz said:
Have you tried flashing the images via fastboot?
Click to expand...
Click to collapse
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
andygu3 said:
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
andygu3 said:
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
andygu3 said:
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Concordium said:
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Click to expand...
Click to collapse
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
andygu3 said:
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Oh crap I forgot you were the one having the issue with the boot.img. If you can't get that to work then the post I gave you will most likely not work either. It's worth a try....but I doubt it.
teh roxxorz said:
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Click to expand...
Click to collapse
Well sh**, that's a downer! If this is the case, I'm definitely sol! But hopefully I can get something out of the phone but I seriously doubt it!
Thanks guys for your input, again much appreciated. I will report back if I have any breakthrough!!
Sent from my PC36100 using Tapatalk
Im having the same issue
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot
teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
No luck!
I know someone posted the EVO Brick_fix, I believe cutthroat but since no PC36IMG.ZIP is being recognized on my sdcard. I may officially say my phone is toast.
Any other suggestions are welcome!
Sent from my PC36100 using Tapatalk
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
andygu3 said:
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Did you unbrick your EVO
I tried to use unbrick method and now phone will not boot at all
It just stays at black screen and vibrates once after pressing the power button
When i press volume down + Power button and go to HBoot
it tells me that i am using Clockwork MOD Recovery v3.0.0.6
i want to update it to latest version i downloaded recovery-clockwork-5.0.2.0-buzz and copy this Zip file on SD card and installed Clockwork MOD Recovery v5.0.2.0
i can see that it changes menu & font color into blue
but when ever i restarts or shut down the phone and go back to HBoot ( volume down + Power button ) i see the same old v3.0.0.6
any suggestions...
help
use this from your bootloader, you need to rename it pc49img.zip (make sure its not named .zip.zip) it should come up saying recovery update, flash? push volume up. after that let it boot to to the boot animations, the battery pull. take out the sdcard and then reboot the bootloader. then go to recovery and it should be up to 5.0.2.0
enjoy
Done... Thanks
Cateye said:
Done... Thanks
Click to expand...
Click to collapse
always here to help people
all part of the fun
Will this work on s on?
Sent from my MB525 using xda premium
Android Flasher...
I have used the following utility to flash the radio, bootscreen, and, just a while ago, the CWM recovery version to v5.0.2.0. As Buzz ain't listed on the list of supported devices, I used Other Device, booted the unit to flashboot, and flashed whichever I wanted by way of the interface.
Thread could be found here: http://forum.xda-developers.com/showthread.php?t=794638&highlight=android+flasher
All credit goes to danward http://forum.xda-developers.com/member.php?u=2693950.
Hope this helps.
nogoodusername said:
Will this work on s on?
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
nah man, you need to be s-off for this method. sorry
heavy_metal_man said:
nah man, you need to be s-off for this method. sorry
Click to expand...
Click to collapse
Ohk...
Then in Dev section it says zip for s on...
M sry. But I don't have a wildfire m just helping out My friend to get some custom rom running...
Sent from my MB525 using xda premium
nogoodusername said:
Ohk...
Then in Dev section it says zip for s on...
M sry. But I don't have a wildfire m just helping out My friend to get some custom rom running...
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
are you tried to revolutionary the phone for s-off? hunt down that and you`ll be on your way
heavy_metal_man said:
are you tried to revolutionary the phone for s-off? hunt down that and you`ll be on your way
Click to expand...
Click to collapse
Whats the worst that can happen with rev??
i dont wanna brick it and pay for it...
Worst I've heard of is it just wont work unless you have the right hboot version and the right drivers etc,, just follow the guides correctly read them a few times first. I haven't heard of a bricked wildfire from unlocking and rooting as yet.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
Worst I've heard of is it just wont work unless you have the right hboot version and the right drivers etc,, just follow the guides correctly read them a few times first. I haven't heard of a bricked wildfire from unlocking and rooting as yet.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Ok then ill try it on his...
Sent from my MB525 using xda premium
nogoodusername said:
Ok then ill try it on his...
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
im sure it will be fine man good luck
hyy.. i tried to update recovery.. when i get to hboot..it recognise the update.. it even says parching pc49img.. and thaan nothing. zip file is ok..because if i choose in recovery..it work.
what to do?
and thaaanks!
papaver said:
hyy.. i tried to update recovery.. when i get to hboot..it recognise the update.. it even says parching pc49img.. and thaan nothing. zip file is ok..because if i choose in recovery..it work.
what to do?
and thaaanks!
Click to expand...
Click to collapse
hmmmm. does it not give you the option of flashing up? by volume up in hboot? if it keeps failing try a different sdcard. this shouldnt work in recovery as far as i know.
no it's not..
hmm.. so on other sd card i just give on the zip file and try or i have to do anythin else to?
papaver said:
no it's not..
hmm.. so on other sd card i just give on the zip file and try or i have to do anythin else to?
Click to expand...
Click to collapse
just the update.zip should do. are you definatly s-off?
yes i am s-off. still not working.
Some steps that I told to another person wanting to update their recovery.
Do you have fastboot?
do you have fastboot in with your SDK tools?
Download [RECOVERY][MOD][Wildfire][02-Nov-2011] Clockwork 5.0.2.7.111102
Extract the zip, and rename to recovery.img to make it simple in ADB.
move the recovery.img to the same folder as your fastboot is in so FOR ME it will be in C:\ ANDROID \ ANDROID-SDK \ TOOLS \ recovery.img
as fastboot is located in ANDROID-SDK / TOOLS / fastboot.exe
then follow these commands EXACTLY as I tell you.
reboot phone in to bootloader - Power off, then HOLD volume down and press power, use volume keys for up and down and select fastboot.
now, open command line and start ADB - This part I expect you to know if you have a rooted phone, but just in case run these commands: - start adb, remount, and open a shell - the commands are "adb remount", then enter "adb shell"
1) adb start-server
2) adb remount
3) adb shell
then enter the command "fastboot flash recovery recovery.img"
FINALLY, enter "fastboot reboot"
Recovery update complete... try rebooting into recovery to confirm this and it should show a new recovery
Click Thanks if this works
I have rooted and unlocked my phone using he tool kit which worked like a charm.
My question now is how to boot into recovery? I have a galaxy nexus and I just hold the power button and down volume and it works fine.
Using TWRP recovery that was installed with the root kit.
With this device, it will just boot into safe mode.
My goal here is to install a custom rom.
Also, I am used to flashing the ROM and Gapps with my Galaxy Nexus , but the instructions or this phone always having something about extracting a zip and flashing it after the gapps. What is this for?
Thanks
Sent from my iPad using Tapatalk HD
You have to zip a ROM, gapps, and then flash the kernel. If you're using the all in one toolkit then all you have to do is press "boot into recovery," otherwise you'll have to power your phone off, go into boot loader by pressing your power and volume down button for a bit then in boot loader scroll down to recovery.I'm not 100% sure about how to work your recovery cause I use cwm. I hope this helps though. Good luck.
Sent from my One V using xda premium
When i try to hold down the power button and down volume it will boot into safe ode not recovery.
Regarding flashing the kernels, Do they not come with the rom itself like JB Sourcery and all the roms for the Galaxy Nexus?
I would flash another kernel sometimes, like Franco, but that was optional.
Thanks
Sent from my iPad using Tapatalk HD
I basically just want "vanilla" JB installed .
How can I do this?
Sent from my iPad using Tapatalk HD
sambrooke said:
I basically just want "vanilla" JB installed .
How can I do this?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
no u have to use fastboot to flash kernel boot img and twrp has the option on the main screen to flash zip on it when u get to the main screen it is pretty self explanitory but, to get to recovery using adb just do the command adb reboot recovery in fastboot just replace the adb with fastboot if no p.c. then turn phone of power on and after hiting powerr botton just do power and bottom down and it should take u to bootloader screen
where do I get kernel boot.img? Is that something that comes with the rom like when i flash in my Galaxy Nexus
if I'm not mistaken, this forum is for the HTC One V... maybe the guys in the galaxy nexus forum can help you more?
Please do not post questions in the development sections. Moved to Q&A.
http://forum.xda-developers.com/showthread.php?t=1996665
Hey Guys,
I know there are many Threads online here but I cant find the information I need.
I've got an HTC Desire Z, bought in Germany without Branding. I need to ship it for warrenty, because it's not booting anymore: HTC Logo then 7 times vibration and off.
If I plug the powercord: Orange LED on ... 7 times vibration and off.
I cant checksum the parition and I cant restore factory, both crash with freeze.
There is cyanogen mod on it and I'm able to boot it on boot menu:
Code:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.08.04.30_M3
eMMC-boot
Sep 8 2010,15:56:38
If I plug USB its saying FASTBOOT USB.
So I should be able to use adb to push an image.
So ... my question is how do I push the image and which image should I push?
Best Regards,
Ruben
If they will fix it for free just brick the whole damn thing so it won't turn on, make sure a non booting phone is covered first!
Open a shell and
dd if=/dev/zero of=/dev/block/mmcblk0p18
sync
reboot
Now your phone won't even boot
If you want though you can just flash stock recovery via fastboot
fastboot flash recovery recover.img
If you can't find the stock recovery image and you want to do this let me know and ill dig one up
Sent from my HTC Vision using Tapatalk 2
Thanks for your hint.
I cant find the Stock image for my german one, every Link goes to this Page:
htt p://shipped-roms.com/index.php?category=android&model=Vision
But there is only an exe installer for European ones.
And I need to flash the radioimage again to stock, there is a different version on it...
demkantor said:
If they will fix it for free just brick the whole damn thing so it won't turn on, make sure a non booting phone is covered first!
Open a shell and
dd if=/dev/zero of=/dev/block/mmcblk0p18
sync
reboot
Now your phone won't even boot
If you want though you can just flash stock recovery via fastboot
fastboot flash recovery recover.img
If you can't find the stock recovery image and you want to do this let me know and ill dig one up
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Not willing to completley brick it huh
Sent from my HTC Vision using Tapatalk 2
demkantor said:
Not willing to completley brick it huh
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Well ... it might be a Problem on ship for warrenty if the Filesystem is completly empty, isn't it?
Not really, if you say hey it slowly stopped turning on and then one day nothing then what do they say, there is no proof of failure. Many people seem to do this when they need a warranty and can't get back tgo stock.
Sent from my HTC Vision using Tapatalk 2
demkantor said:
Not really, if you say hey it slowly stopped turning on and then one day nothing then what do they say, there is no proof of failure. Many people seem to do this when they need a warranty and can't get back tgo stock.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Allright, but it this also overwriting the radio image? or are they checking this?
They couldn't, phone won't boot.
But if you would rather I don't have you stock image but I'm sure nipqer does, look for his thread on returning to stock with a broken digitizer, he has put to gether a bunch of stock roms for the g2/dz and has them mirrored in his server, be sure to thanks him!
Sent from my HTC Vision using Tapatalk 2
demkantor said:
If they will fix it for free just brick the whole damn thing so it won't turn on, make sure a non booting phone is covered first!
Open a shell and
dd if=/dev/zero of=/dev/block/mmcblk0p18
sync
reboot
Now your phone won't even boot
If you want though you can just flash stock recovery via fastboot
fastboot flash recovery recover.img
If you can't find the stock recovery image and you want to do this let me know and ill dig one up
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
I just tried to follow your instructions, but how do I open a commandline via fastboot?
You don't, no adb in bootloader mode, just fastboot
Do it in recovery
Sent from my T-Mobile G2 using Tapatalk 2
demkantor said:
You don't, no adb in bootloader mode, just fastboot
Do it in recovery
Sent from my T-Mobile G2 using Tapatalk 2
Click to expand...
Click to collapse
sorry, but still not getting it :/
Which commands do I need now exactly for fastboot?
There is now adb access in bootloader, not even in fastboot mode, hence nothing to type in there (as to brick phone)
You will need to boot into recovery or have a working operating system to use adb, that's similar to fastboot.
You don't have an os so you need to boot to recovery and open cmd, then type the command I posted earlier
Sent from my Nexus 7 using xda premium
demkantor said:
There is now adb access in bootloader, not even in fastboot mode, hence nothing to type in there (as to brick phone)
You will need to boot into recovery or have a working operating system to use adb, that's similar to fastboot.
You don't have an os so you need to boot to recovery and open cmd, then type the command I posted earlier
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Allright, how do I boot to recovery?
When in bootloader mode choose recovery
Sent from my T-Mobile G2 using Tapatalk 2
demkantor said:
When in bootloader mode choose recovery
Sent from my T-Mobile G2 using Tapatalk 2
Click to expand...
Click to collapse
This lead to a crash... =(
https://www.dropbox.com/s/qz8id18my196ru8/VID_20121230_034021.m4v
Yeah you are showing all the signs of a fried emmc, so you couldn't return to stock even if you wanted to as your chip has lost read/write cappabilities.
To completley brick try and flash either an incompatable hboot or radio or do a battery pull during the flash, may need to do it a few times to work
Sent from my T-Mobile G2 using Tapatalk 2
Just for other Guys which might find this, I found the original rom on my harddisk:
http://ompldr.org/vZ3hvaw/htc desire z original rom backup.7z
demkantor said:
Yeah you are showing all the signs of a fried emmc, so you couldn't return to stock even if you wanted to as your chip has lost read/write cappabilities.
To completley brick try and flash either an incompatable hboot or radio or do a battery pull during the flash, may need to do it a few times to work
Sent from my T-Mobile G2 using Tapatalk 2
Click to expand...
Click to collapse
I'll try this, thanks!
I have an HTC Incredible 2 for Verizon version 2.2.1 and its is GSM Unlocked. I use GSM not CDMA. I want to root my phone to get the venom rom and version 4.0.3. I was able to get S-OFF on my phone but I am having problems unlocking bootloader. I either got the errors: COMMAND ERROR!!! or it would be stuck on "Waiting for Device". I tried to also update my version 2.2.1 to 2.3.3 but that won't work either everytime I try to update with bootloader it keeps saying wrong zip. Can someone help me out unlock the bootloader and root my phone. I really wanna root my phone and get custom roms. Please help me out. Thank You.
So, its S-OFF and you need to unlock bootloader to install Clockworkmod recovery, correct? I did it with HTC Dev's site ( www htcdev com / bootloader )
Just followed the steps and I got my bootloader unlocked, then installed recovery and ran the root.zip file from there.
jeinnerabdel said:
So, its S-OFF and you need to unlock bootloader to install Clockworkmod recovery, correct? I did it with HTC Dev's site ( www htcdev com / bootloader )
Just followed the steps and I got my bootloader unlocked, then installed recovery and ran the root.zip file from there.
Click to expand...
Click to collapse
I did that all the steps but I keep getting errors. Does updating to 2.3.work?
If its s-off already you don't have to worry about unlocking. Just fastboot flash a recovery.img
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
tylerlawhon said:
If its s-off already you don't have to worry about unlocking. Just fastboot flash a recovery.img
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
Click to expand...
Click to collapse
Recovery doesn't work in the bootloader when I click on it shows me a phone with a hazard sign. If I don't need that recovery then how do I flash the rom
Mine is S-Off n unable to download bootloader from htcdev.. no idea y its not recognizing/ not able to give me a code.. pls suggest smtin
Sent from my HTC Incredible S using xda app-developers app
I have the same problem Still got no luck.
farees107 said:
Recovery doesn't work in the bootloader when I click on it shows me a phone with a hazard sign. If I don't need that recovery then how do I flash the rom
Click to expand...
Click to collapse
Boot phone into boot loader/fastboot, fastboot flash cwm.img (on your computer) ...Profit
Sent from my ADR6350 using xda app-developers app
FordNate said:
Boot phone into boot loader/fastboot, fastboot flash cwm.img (on your computer) ...Profit
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
how u do that?? im so confused I also heard carrier branded phones cant unlock bootloader. my phone is carrier branded to Verizon but its gsm unlocked and s-off.
farees107 said:
how u do that?? im so confused I also heard carrier branded phones cant unlock bootloader. my phone is carrier branded to Verizon but its gsm unlocked and s-off.
Click to expand...
Click to collapse
google is your friend. Google it. You are already unlocked. FIND THE CWM.img files in these threads. Even look around there might be a guide or 3 that'll help.
FordNate said:
google is your friend. Google it. You are already unlocked. FIND THE CWM.img files in these threads. Even look around there might be a guide or 3 that'll help.
Click to expand...
Click to collapse
I did it showed me alot of things that confused me. I would appreciate it if you helped me by sending me a link
farees107 said:
I did it showed me alot of things that confused me. I would appreciate it if you helped me by sending me a link
Click to expand...
Click to collapse
[URL="http://forum.xda-developers.com/showthread.php?t=1751796"]http://forum.xda-developers.com/showthread.php?t=1751796
http://forum.xda-developers.com/showthread.php?t=1466295
http://forum.xda-developers.com/showthread.php?t=1726134
FordNate said:
[URL="http://forum.xda-developers.com/showthread.php?t=1751796"]http://forum.xda-developers.com/showthread.php?t=1751796
http://forum.xda-developers.com/showthread.php?t=1466295
http://forum.xda-developers.com/showthread.php?t=1726134
Click to expand...
Click to collapse
I'm a newbie at this and I have no clue how any of threads are going to help my situation. I want to root my phone its Verizon carrier branded HTC incredible 2 phone. Its suppose to be CDMA but I got it unlocked by someone to make it work for GSM. Now I wanna root it i had someone gain me s-off but couldn't unlock the bootloader. I can't even open up recovery from my cell phone it gives me the phone with a hazard sign error. I wanna root it so bad but had no progress to root after s-off. Can you please help me root. My firware is 2.2.1
farees107 said:
I'm a newbie at this and I have no clue how any of threads are going to help my situation. I want to root my phone its Verizon carrier branded HTC incredible 2 phone. Its suppose to be CDMA but I got it unlocked by someone to make it work for GSM. Now I wanna root it i had someone gain me s-off but couldn't unlock the bootloader. I can't even open up recovery from my cell phone it gives me the phone with a hazard sign error. I wanna root it so bad but had no progress to root after s-off. Can you please help me root. My firware is 2.2.1
Click to expand...
Click to collapse
This is the last help I'm giving other then that Google will be your friend. Power down the phone. Hold volume - (down) and power. This will take you to your bootloader screen. Hit volume up or down and scroll to fastboot hit power button. FIND the cwm .img from one of those threads and flash that through adb on your computer using the command given in one of those links to Root threads. You phone is S off you already had root. That's all the help I'm willing to give.
Sent from my ADR6350 using xda app-developers app
Didn't work
FordNate said:
This is the last help I'm giving other then that Google will be your friend. Power down the phone. Hold volume - (down) and power. This will take you to your bootloader screen. Hit volume up or down and scroll to fastboot hit power button. FIND the cwm .img from one of those threads and flash that through adb on your computer using the command given in one of those links to Root threads. You phone is S off you already had root. That's all the help I'm willing to give.
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
sorry if am asking @ the wrong time..but does it mean that i can root and flash roms,kernels..with a locked bootloader but with s-off?
Frazercrib said:
sorry if am asking @ the wrong time..but does it mean that i can root and flash roms,kernels..with a locked bootloader but with s-off?
Click to expand...
Click to collapse
S-off is unlocking the bootloader. Basicalky taking the normal security flags or checks that happen during boot process n dropping/overriding them.
Sent from my SCH-I545 using Tapatalk
ok i did all u guys said...but i get this after typing fastboot flash cwm.img
unknown partition 'cwm.img'
error: cannot determine image filename for 'cwm.img'
don't know if i did something wrong
Frazercrib said:
ok i did all u guys said...but i get this after typing fastboot flash cwm.img
unknown partition 'cwm.img'
error: cannot determine image filename for 'cwm.img'
don't know if i did something wrong
Click to expand...
Click to collapse
the command is fastboot flash recovery cwn.img
ArslanQureshi said:
the command is fastboot flash recovery cwn.img
Click to expand...
Click to collapse
ok silly me...i corrected my error...now i am getting this
sending 'recovery' (3726 KB)...
OKAY ( 1.147s)
writing 'recovery'...
FAILED (remote not allowed)
finished. total time: 1.150s
....and still no recovery