I have had my g2 rooted for over a year with no problems running some form of cyanogen mod the whole time and yesterday my phone was acting up and I restarted it and it wont get past the cyanogen mod boot animation. I have tried flashing back up imgs and other roms but none will successfully load and I have wiped before trying to load any thing new and tried factory reset. Can anyone help me get my phone back in action?
post a logcat of the booting and also write down everything on your hboot screen
Sent from my HTC Vision using xda premium
demkantor said:
post a logcat of the booting and also write down everything on your hboot screen
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I have android sdk on my computer but I have never used it and am not to sure how to go about getting the logcat but I am working on figuring it out but in the mean time here are some pics of the hboot screens if that helps with anything.
once sdk is installed then you need to run it and download at least all the platform tools, then well here : SEE POST THREE for more info on setting up adb and fastboot
the command prompt is
adb logcat
anyway, it looks like you should have true radio s-off with the g2 engineering hboot, this is good as long as its not a fried emmc youll be just fine
which recovery do you have? if you have 4ext then go and reformat all partitions, then flash a known stable rom like cm7.
if you have clockwork flash THIS, after it reboots to recovery flash cm7
let me know what happens
demkantor said:
once sdk is installed then you need to run it and download at least all the platform tools, then well here : SEE POST THREE for more info on setting up adb and fastboot
the command prompt is
adb logcat
anyway, it looks like you should have true radio s-off with the g2 engineering hboot, this is good as long as its not a fried emmc youll be just fine
which recovery do you have? if you have 4ext then go and reformat all partitions, then flash a known stable rom like cm7.
if you have clockwork flash THIS, after it reboots to recovery flash cm7
let me know what happens
Click to expand...
Click to collapse
This is what it said after I ran the SuperWipeG2. Not sure I went right what next?
No it crashed, try just wiping everything you can from clockwork and then reinstall rom, if it still won't run you'll need to get adb and fastboot working to keep going
Sent from my HTC Vision using xda premium
foroudi9 said:
I have android sdk on my computer but I have never used it and am not to sure how to go about getting the logcat but I am working on figuring it out but in the mean time here are some pics of the hboot screens if that helps with anything.
Click to expand...
Click to collapse
you can try the tool at my signature(AIOlog) to get the logcat easily
demkantor said:
No it crashed, try just wiping everything you can from clockwork and then reinstall rom, if it still won't run you'll need to get adb and fastboot working to keep going
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
That link didn't help much b/c I have a mac :/
demkantor said:
No it crashed, try just wiping everything you can from clockwork and then reinstall rom, if it still won't run you'll need to get adb and fastboot working to keep going
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
maybe the sdcard has given up?
PNuT. said:
maybe the sdcard has given up?
Click to expand...
Click to collapse
I can still add and remove things from the sd card if I put it in my computer or does that not mean anything?
Sd is probably fine, just do a quick google or xda search for how to setup adb or fastboot on mac
Debugging android is far easier when you have these super important tools at hand
Sent from my HTC Vision using xda premium
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Oh and one more thing you can try if you just can't get adb/fastboot to work, in the link I sent I did post a dropbox links with some pc10img.zips I made to help people quickly get newer radio,hboot,4extrecovery, I think its post 30
Just grab one (usualy dzhboot is best but it really won't matter much if you don't use sense roms) rename pc10img.zip and put it on root of sdcard (not in any folder) then boot into bootloader and hit yes on the prompt, the phone will probably reboot halfway through update, don't worry, when its all done (you'll know when it is) choose reboot to recovery
From here format all partitions (you'll have 4ext recovery, just play around in there untill you find out where options are) then see if the rom flashing will work
Sent from my HTC Vision using xda premium
demkantor said:
No it crashed, try just wiping everything you can from clockwork and then reinstall rom, if it still won't run you'll need to get adb and fastboot working to keep going
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Okay I got adb and fastboot working and this is where I am at. I'm not exactly sure how to get the logcat now.
Open up a command prompt and type
adb devices
Some things may differ in osx but I'm sure there are guides for this
If you see your serial # good, if not then trouble shoot
Try it in recovery first
once running, in command type
adb logcat
While the phone is booting
If you can get it running, copy and paste the output here (preferably in pastebin)
If you can't get anything while booting try and get your emmc
In adb type
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Hope its not the SEM04G as its prone to failure
Sent from my Nexus 7 using xda premium
demkantor said:
Open up a command prompt and type
adb devices
Some things may differ in osx but I'm sure there are guides for this
If you see your serial # good, if not then trouble shoot
Try it in recovery first
once running, in command type
adb logcat
While the phone is booting
If you can get it running, copy and paste the output here (preferably in pastebin)
If you can't get anything while booting try and get your emmc
In adb type
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Hope its not the SEM04G as its prone to failure
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Finally got it! I couldn't get pastebin to submit it so I used zerobin. Let me know if that works. Thanks for all your help so far.
http://sebsauvage.net/paste/?efc68f7ab2e5db9c#ZbvCJEEIkOvjIpTQZjiSXxeLHfJ4WkUIuX6On+fuzPE=
well your definitely stuck in a loop and a short one at that. there are some memory read issues but i dont think its a failed emmc.
boot to recovery and try the command i listed above only i forgot the first command to put you in a shell
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
this will tell you which chip you have
also now that you have adb working, i will presume fastboot works too
follow the guide i linked you and flash 4ext recovery via fastboot (commands may differ do to mac) if you get absolutely stuck use the pc10img.zip
demkantor said:
well your definitely stuck in a loop and a short one at that. there are some memory read issues but i dont think its a failed emmc.
boot to recovery and try the command i listed above only i forgot the first command to put you in a shell
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
this will tell you which chip you have
also now that you have adb working, i will presume fastboot works too
follow the guide i linked you and flash 4ext recovery via fastboot (commands may differ do to mac) if you get absolutely stuck use the pc10img.zip
Click to expand...
Click to collapse
well i used the pc10img.zip and it never finished updating on the hboot screen (the progress bar on the right of the screen never finished loading) so it stayed that way for a few hours and I pulled the battery b/c it was completely unresponsive. Now I cant power on to hboot or recovery or anything for that matter. I'm guessing it is bricked... is that a good assumption?
Hopefully not, flashing a pc10img.zip through hboot can be risky when in a situation like yours. Its less risky through fastboot as you can choose not to reboot untill all is fixed. Depending on where the flashing got stuck you could be in trouble as if it flashed an incomplete radio or hboot then its bad news. Hopefully this isn't the case. Battery won't charge in hboot mode so if it is possible batt is dead. Charge it with phone off, does the led come on? If so let it charge until green. If it does that then I'm thinking it will turn on again (hopefully)
if it won't then try leaving the battery out for a day and trying again (don't know why this works but some says it does) let me know what happens
Sent from my HTC Vision using xda premium
demkantor said:
Hopefully not, flashing a pc10img.zip through hboot can be risky when in a situation like yours. Its less risky through fastboot as you can choose not to reboot untill all is fixed. Depending on where the flashing got stuck you could be in trouble as if it flashed an incomplete radio or hboot then its bad news. Hopefully this isn't the case. Battery won't charge in hboot mode so if it is possible batt is dead. Charge it with phone off, does the led come on? If so let it charge until green. If it does that then I'm thinking it will turn on again (hopefully)
if it won't then try leaving the battery out for a day and trying again (don't know why this works but some says it does) let me know what happens
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
The led dosnt come on but i will give it a shot leaving it out. I am sure i remember there being a conformation that the radio did finish but I dont remember what else it said but it was nearly done when it froze. I'll get back to you in a day with the results.
I believe it flashes radio and hboot first, the rest wouldn't cause a brick so if it passed that then ok. Unless your partitions were super curropt and somehow the flash didn't but the phone thought it did.
I guess for now just hope the battery is dead or something like that but I hate to say that no led is a bad sign...
Sent from my HTC Vision using xda premium
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
I pulled my phone out of my pocket it and saw that it was on the HTC boot screen. It stayed like the for a while so i shut it down using Power, Volume UP&Down.
I tried to boot again but was freezing at the HTC boot screen.
I booted into recovery and it said it couldnt load /cach/x (command and log and last_log)
Ive tried everything from flashing RUU to new HBOOTS, nothing is working.
Now my laptop keeps saying a USB port is malfunctioning everytime i plug the phone in.
Im two seconds away from smashing this with a sledgehammer.
I was running Aeroevan's Unofficial CM10 Jelly Bean With the v12 Kernel w/ Video Drivers.
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Yes, when i go to install it, it does a few things.
It p****s the zip
bypasses the bootload
and freezes at boot saying updating and at the bottom is says can not roll back hboot version.
Its been at this screen for about 45 minutes THIS TIME
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The only issue now is I only have FastBoot Support but no ADB support. I have no idea why but my phone only shows up under fastboot devices and not adb devices. so i have no idea how to use that guide
The Inc 2 ports often go bad. Try wiggling and plugging it in not all the way. Also sometimes had to push on the cable and hold for it to recognize the USB.
________________________________
Easy as 3.1415926536
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
sjpritch25 said:
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
Click to expand...
Click to collapse
I did??
Sent from Kangdemnation
CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
When i type in Fastboot device my phone shows up, but when i type in adb devices it doesnt. i set up the android sdk and assorted tools the way i always have because i use them for development in eclipse, but ive never had a problem with adb before.
sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
this is what it should look like.
CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
Lol I think he had just looked at your contact picture. They look very similar at a glance
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
CondemnedSoul said:
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
Click to expand...
Click to collapse
Everything i try keeps freezing in the bootloader screen when i go to install any RUU or image file or zip including that PG32IMG thing or whatever.
My phone recognizes it in fastboot but not adb.
I am S-Off. I rooted the phone the day i got it 6 months ago and have flashed a new rom weekly. never had a problem like this before.
dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The download links in this do not work or else id try that too.
Try it
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
flydoug9 said:
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
Click to expand...
Click to collapse
Yes i would try this except ClockWorkMod isnt working when i attempt to boot into it. It starts to load then freezes.
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
TheValk said:
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
Click to expand...
Click to collapse
Yeah i've been trying everything. When i install any RUU or anything it keeps getting hung up at recovery and i tried flashing that seperately and that isnt doing anything.
Have you tried doing anything in fast boot like wiping data and cache?
Sent from my Incredible 2 using xda premium
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!
Finally rooted the phone today, but when I try to go into an alternate recovery, or install a ROM (which I've never done before) the phone reboots (like it should I'm assuming) begins to load what I told it to do, and then I get an image of my phone with a red question mark above it, and my phone just reboots again.
What's causing this?
R: [Q] Finally took the plunge and rooted it, but can't do anything else?
ghostspectrum said:
Finally rooted the phone today, but when I try to go into an alternate recovery, or install a ROM (which I've never done before) the phone reboots (like it should I'm assuming) begins to load what I told it to do, and then I get an image of my phone with a red question mark above it, and my phone just reboots again.
What's causing this?
Click to expand...
Click to collapse
Did you flash a custom recovery? If no, flash it and try again
Sent from my One V using xda app-developers app
mr_nooby said:
Did you flash a custom recovery? If no, flash it and try again
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I tried using ROM manager but I get the exact same results
Sent from my HTC One V using xda app-developers app
Tried using TWR got similar results with the image of the phone with a red triangle and exclamation mark :'(
Sent from my HTC One V using xda app-developers app
How are you flashing the recovery. The description you are describing is the stock recovery to flash a new recovery do it in fastboot (fastboot flash recovery name of recovery here)
Get the all in one tool from the dev section and it will do it for you.
All you need to do is choose which one you want CDMA or gsm, twrp or cwm (i prefer twrp for the one v)
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Tehwafflez said:
How are you flashing the recovery. The description you are describing is the stock recovery to flash a new recovery do it in fastboot (fastboot flash recovery name of recovery here)
Get the all in one tool from the dev section and it will do it for you.
All you need to do is choose which one you want CDMA or gsm, twrp or cwm (i prefer twrp for the one v)
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Click to expand...
Click to collapse
Hey thanks when I get home I'll give it a shot
Sent from my HTC One V using xda app-developers app
'Ok the All in one tool worked. I flashed TWRP, wiped my caches and installed AOKP JB 4.1.2, i've got the "Initiating swagger" screen, how long should this take?It's been about 10 minutes...
So as far as i can tell, the rom install failed because i didnt complete the wipe (because the wipe through TWRP failed...) what causes this?
It will say it failed because the sd-ext didn't wipe (THAT'S A GOOD THING) the /sd-ext is your SD card lol. So did you get into the actual ROM for aokp? So when you clicked swaggerfy it froze? Hmm I'd try a different ROM or different kernel what kernel are u using. I reccomend Jan 3rd super slick (anything newer breaks the camera).
Edit: i noticed you said caches? Do did you click factory reset? I usually do factory and dalvik but i think factory does it all.
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Tehwafflez said:
It will say it failed because the sd-ext didn't wipe (THAT'S A GOOD THING) the /sd-ext is your SD card lol. So did you get into the actual ROM for aokp? So when you clicked swaggerfy it froze? Hmm I'd try a different ROM or different kernel what kernel are u using. I reccomend Jan 3rd super slick (anything newer breaks the camera).
Edit: i noticed you said caches? Do did you click factory reset? I usually do factory and dalvik but i think factory does it all.
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Click to expand...
Click to collapse
I hope I get a fairly quick response to this Followed some advide in that thread, flashed a kernel (I thought) using the All In One Tool, ever since, I've been stuck in a bootloop. Obviously I have access to my bootloader and TWRP (thankfully). My recovery backup returns the same results though.
Im new to this so I'll try toprovide all the info I can.
Followed the TUT on how to Unlock Bootloader and Root 2 days ago.
Yesterday, using the All In One tool, flashed TWRP onto phone.
Was unable to Flash AOKP JellyBean 4.1.2 so I asked for help again (ROM was flashed, but stuck on Initiating Swagger Boot)
Tried using All-In-One to flash (what I thought was) a kernel, since then, my phone just boots continuously or not at all (depending on if I wipe or whatnot)
While at work, I was able to Flash the AOKP rom and Boot into it, but after about 1 minute of use, it reboots.
This is where I'm at now.
My bootloader says
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT- 1.57.0000
RADIO- 1.00.05.0929
eMMC-boot
Jun 18 2012, 10:22:43
I'm using the latest version (2.3.3.) of TWRP
Is there anyway I can find, and delete, the boot.img I flashed with All-In-One, that caused this bootloop?
Found out why: radio is the new version aka .0928
HTC provided a new radio release and it screwed up being able to flash new JB roms. The fixable solution is to find the virgin mobile ruu exe and do that long process to get the old radio: .0521_2(?) back. I'll link you to the ruu thread in a sec let me find it first
Here:
http://forum.xda-developers.com/showthread.php?t=2018518
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Tehwafflez said:
Found out why: radio is the new version aka .0928
HTC provided a new radio release and it screwed up being able to flash new JB roms. The fixable solution is to find the virgin mobile ruu exe and do that long process to get the old radio: .0521_2(?) back. I'll link you to the ruu thread in a sec let me find it first
Here:
http://forum.xda-developers.com/showthread.php?t=2018518
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!
Click to expand...
Click to collapse
The only problem right now is when I'm in FASTBOOTUSB my computer doesn't recognize my phone.
You get fastboot USB and you're headed in the right direction
mihirengg19 said:
You get fastboot USB and you're headed in the right direction
Click to expand...
Click to collapse
But I'm having a hard time flashing that new RUU because when I'm in my Bootloader, and in Fastboot USB, my computer doesn't see my phone.
WHen I try to enter the fastboot code into the cmd shell, It just says that fastboot is not a recognized command...
That's because you aren't changing the directory to the fastboot folder.
mihirengg19 said:
That's because you aren't changing the directory to the fastboot folder.
Click to expand...
Click to collapse
How do I do that?
ghostspectrum said:
How do I do that?
Click to expand...
Click to collapse
All right do this.
Create a folder as fastboot on c drive of PC(hope you're on windows)
Download fast boot files.
Put in c:/Fastboot
Go in fastboot mode on phone.
It should say fastboot USB.
Open command prompt.
Type cd c:/fastboot/
Hit enter. The prompt should say this address now.
Type your fast boot command you want
Sent from my HTC One V using xda app-developers app
soham_sss said:
All right do this.
Create a folder as fastboot on c drive of PC(hope you're on windows)
Download fast boot files.
Put in c:/Fastboot
Go in fastboot mode on phone.
It should say fastboot USB.
Open command prompt.
Type cd c:/fastboot/
Hit enter. The prompt should say this address now.
Type your fast boot command you want
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Ok thank you, I do have that fastboot folder haha, gonna have to let my phone charge over night thought (I assume) so I'll try a crack at it tomorrow.
ghostspectrum said:
Ok thank you, I do have that fastboot folder haha, gonna have to let my phone charge over night thought (I assume) so I'll try a crack at it tomorrow.
Click to expand...
Click to collapse
Do NOT charge it over night. It damages the battery, and this is experience talking to you. Leave your phone charging for 3 hours, and that's sufficient.
Sent from my HTC One V using xda app-developers app
soham_sss said:
All right do this.
Create a folder as fastboot on c drive of PC(hope you're on windows)
Download fast boot files.
Put in c:/Fastboot
Go in fastboot mode on phone.
It should say fastboot USB.
Open command prompt.
Type cd c:/fastboot/
Hit enter. The prompt should say this address now.
Type your fast boot command you want
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
SCratch that. Completed the process, the program said it did everything, but back in bootloader, it still shows Radio- 1.00.05.0929 :/ and I can't get out of boot loader lol
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Aireon said:
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Click to expand...
Click to collapse
mount the sdcard inside the recovery and copy the rom
Mr Hofs said:
mount the sdcard inside the recovery and copy the rom
Click to expand...
Click to collapse
Sorry, I'm completely new to this. Do you mean normal recovery from bootloader or a custom recovery that I should of done but completely skipped due to my ignorance? (I also haven't unlocked bootloader so I'm assuming that's a misstep as well?)
Because all I get when I do the normal recovery is a picture of a phone with a red triangle and "!" combo.
Thanks
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Mr Hofs said:
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Click to expand...
Click to collapse
Thanks for the tips!
After a while of toiling to try and unlock the boot loader manually and getting stuck at the load error for Unlock_code.bin, I found Hasoon2000's tool, so he is my god for now.
My query that I have is, Do I need a custom recovery like ClockWorkMod to create a nandroid back up? Because all I get when I try to go into recovery from the bootloader is this (img attached, not mine because I don't have another camera in the house but luckily I managed to find one on google img.)
I can't find anything saying that I do need a custom recovery, but then again it's not working when I try without one, so I'm not too sure where to go from here.
Thanks again
Please read carefully what i write, i know exactly what to do !
You need a custom recovery !
Sorry to be back again so soon but I'm stuck again, haha.
When I try to flash cwm I get "error: cannot load 'recovery.img'". When I try to use Hasoon2000's tool kit to do it for me it doesn't work either as it just says device not found and in the second command window it says that it can't load it's .img file either.
The recovery.img is in the same location as fastboot. My phone is in Fastboot in bootloader.
I'm typing "r:\Android\adt\sdk\platform-tools\fastboot flash recovery recovery.img". Trying to auto complete recovery.img using tab does nothing (if that might indicate some sort of problem).
The only thing I can think of is that the MTP drivers never install properly but I read on this forum that it shouldn't affect fastboot.
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ah, I probably should of said it earlier, sorry. I'm using windows 7.
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
If javaj jdk is just normal java then yes. In programs and features it's called Java 7 Update 45?
Do you mean the phone drivers on my PC?
Edit: Noticed jdk was the dev kit. Downloaded and installed. Will try again.
Edit2: Still not working, same errors.
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I just updated the phone drivers (without HTC sync) from http://forum.xda-developers.com/showthread.php?t=2376761 to 4.2.0.001 from the 4.0 version I had that HTC sync had installed previously for some reason.
Shows up in fastboot devices now. Still doesn't show up in adb devices. Still getting the can't load recovery.img error.
Would it be worth it to try doing it on another computer?
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ok so I still couldn't do it manually on the other computer. Got the same errors as with the first. I tried flashing with Hasoon2000's tool again and noticed that it was trying to flash CWM.img while the recovery for it was actually called recovery.img. Renamed it to CWM.img and it flashed perfectly.
I assume it would of done the same on the original PC I tried it on.
No idea why it wouldn't work when I tried it manually, but yolo. Hasoon2000 is love. Hasoon2000 is life.
Holy hell Hasoon2000 has saved me again.
I flashed the kernal by accident and it got stuck in boot. So i just sideloaded the rom in H2K's tool and everything turned up Milhouse.
Yay congrats
Sent from my GT-I8190 using xda app-developers app
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Mr Hofs said:
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Click to expand...
Click to collapse
Hmmm, I'm not sure what it would of been as a tried flashing recovery.img.img as well. But everything worked out well in the end .
Thank you both the help.
Glad to hear that it worked
Sent from my GT-I8190 using xda app-developers app