Hi, can someone upload their nandroid backup files? I don't know how; but, the system on my phone is shown as 0MB. I used 4ext recovery to format all partition and decided to try Slim Bean (coming from Jelly Baby). The phone stuck on the slim bean loading page for about 10 minutes and I decided to take out the battery and restart. That's when the problem started.... I can still boot into 4ext recovery; but, it says the recovery is in safe mode and I need to format the system. When I tried to re format all my partition I got "make_extf4fs failed on dev/block/mmcblk0p25" message.
I have tried to just ignore the message, flash a ROM; but, it won't boot. When I go to "info" on 4ext recovery it says that system, data, and cache size are all --MiB (which I think means that there is no data there).
I have tried to push the system.img from http://forum.xda-developers.com/showthread.php?t=1085624 to the /dev/block based on some google search and it still failed.
I also tried to do an RUU using the T-Mobile Froyo stock rom found in this thread: http://forum.xda-developers.com/showthread.php?t=1178912. When I tried to do update it, it just says it failed in my phone and the only option left is to reboot.
I am able to access the recovery; so, my last option is to try a nandroid backup. I thoughtI got a nandroid backup when I tried to do this whole thing and turned out I don't have one.... So, any help on uploading the file is truly appreciated. This is pretty much the last thing I hope will work....
I doubt a nandroid would do anything, can you post all info from bootloader screen?
Also see here
http://forum.xda-developers.com/showthread.php?p=43195539
You will find links to a bunch of info including toward the bottom of the first post there is a link to important brick info, I suggest reading through this as well
Sent from my Nexus 4 using xda premium
Here are some information about my bootloader recovery, etc
S-off
HBOOT - 0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
4ext recovery touch v1.0.0.5 RC5
Thanks for the link. I read some other similar thread and so far, I think I tried most of them.... For whatever reason even after flashing a fresh rom, pushing system.img that I previously mentioned does not help.
When I check on "info" in 4ext recovery, it shows that system, data, and cache size are all "--MiB"
Does the bootloader say ship soff or eng soff?
Also can you confirm you used gfree to root?
Sent from my Nexus 4 using xda premium
demkantor said:
Does the bootloader say ship soff or eng soff?
Also can you confirm you used gfree to root?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It says Vision pvt eng S-off.
I don't remember which method I used to root since it has been more than a year ago. But, I think it was gfree because I remembered reading somewhere that root using visionary has a chance to brick the device...
Feel free to try one of the custom PC10IMG.zips I made, youll find a link in the brick thread (post thirty I believe) also has instruction on how to test if you used gfree to exploit (although others have used it and reported it works without true s-off, I'm just overly cautious at times)
Sent from my Nexus 4 using xda premium
demkantor said:
Feel free to try one of the custom PC10IMG.zips I made, youll find a link in the brick thread (post thirty I believe) also has instruction on how to test if you used gfree to exploit (although others have used it and reported it works without true s-off, I'm just overly cautious at times)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So, I got the same result with your PC10IMG.zip with the other PC10IMG.zip that I've tried.
When I choose to update, it just says -Fail-PU on the first one (which is the bootlader). This is how it looks:
Parsing... [SD ZIP]
[1] BOOTLOADER - Fail-PU
[2] RADIO_V2
[3] RADIO_CUST
[4] RECOVERY
[5] SPLASH1
[6] TP
[7] TP
So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)
Sent from my Nexus 4 using xda premium
demkantor said:
So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hmm, I haven't tried flashing the engineering hboot yet. I will try to flash that through fastboot later today when I got home. Hope this works :good:
demkantor said:
So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
When I tried to flash the hboot, I used command "fastboot flash hboot g2hboot.img"
The result is:
sending 'hboot' (1024 KB)... OKAY
writing 'hboot'... FAILED (remote: image update error)
Any clue on what else I should do that might help this old phone?
Check and see which emmc you have, instructions are in the link I provided earlier
Sent from my Nexus 4 using xda premium
demkantor said:
Check and see which emmc you have, instructions are in the link I provided earlier
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
All I got is
'grep' is not recognized as an internal or external command,
operable program or batch file.
All the other adb command works so far; but, I don't know what happened with this grep is not recognized.... Do I need to update my android sdk? Or is it something else?
Edit:
Nevermind... I just re-tried it by separating the adb shell command following this thread that I found: http://forum.xda-developers.com/showthread.php?t=1854558
I followed both of the commands and for the first one which is:
adb shell
dmesg | grep mmc0
I got good result (as in the internal is not fried, I think); but using the second command (which seems to be the same with your thread), this is what I got:
C:\android-sdk-windows\platform-tools>adb shell
~ # cat /proc/kmsg | grep 'mmc0:0001'
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 6.152069] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
Does that mean I just got a bad luck with that chip and there is no salvation for this phone?
That chip has a very high brick rate, with the issues your having my guess is its fried, sorry
Sent from my Nexus 4 using xda premium
demkantor said:
That chip has a very high brick rate, with the issues your having my guess is its fried, sorry
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well... I guess that's just my luck.... Thanks for the help!
Is there anything else that might worth a shot?
you could try to boot off sd card, There is info on how to in the first link i sent, which may not work if your bootloader partition is whats fried, but worth a shot anyway
best of luck!
Related
Hi
I wonder if someone could help with a problem I'm having trying to flash HBOOT CM7.
I am s-off with revolutionary and with 4ext recovery.
This is what I've been doing:
- full wipe / factory reset using 4ext
- go to fastboot and use Android flasher to flash CM7 which it does successfully as I can see the pink heading change to CM7 on the phone's HBOOT screen.
- Boot into recovery
- Recovery opens but I get the error messages E can't open cache ... ... ... and it continuously reboots.
At this point I return to fastboot flash back to stock HBOOT and all is well.
I had a search for this problem and the advice was to completely wipe before the flashing the CM7 HBOOT. The first time I hadn't done this but the second and third time I did. The third time was with a new download.
Am I missing something?
Thanks in advance for your help.
Rich
Bad download of the image maybe. Did you downloaded it again and checked the file. More info on the way you flashed your hboot would be great.
Sent from me myself and i
MarcelHofs said:
Bad download of the image maybe. Did you downloaded it again and checked the file. More info on the way you flashed your hboot would be great.
Sent from me myself and i
Click to expand...
Click to collapse
Phone would most likely be bricked if that was the case.
SwiftKeyed from my HTC Desire using XDA App.
Try "fastboot reboot-bootloader" And Then "fastboot erase cache" After flashing cm7r2
That should resolve The problem
Sent from my HTC Desire using XDA App
I had to reflash the cmr7 hboot file from fastboot 1time again after the first time....had a recovery bootloop....kept on refreshing over and over. After the second flash of the ext4 recovery all worked fine
Sent from my HTC Desire using XDA App
Depends if it affects the bootloader, in this case the problem lies with the recovery that can ne flashed through the bootloader menu....or am i wrong ? Still learning here so don't know if i am right
erklat said:
Phone would most likely be bricked if that was the case.
SwiftKeyed from my HTC Desire using XDA App.
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App
Im Not able to understand you, i try to answer anyway: The recovery doesnt affect the bootloader
Sent from my HTC Desire using XDA App
Thanks everyone for your prompt responses. Will try loler90's suggestion tomorrow and report back.
Thanks this worked. I did it using Android Flasher and the command line and used the following commands:
fastboot erase system
fastboot erase cache
fastboot reboot bootloader
thanks again.
Rich
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
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!
Not sure what to do here...
I rooted this G2 earlier this evening and decided I wanted Cyanogenmod 7 as the rom.
I flashed Clockworkmod and installed the rom and then gapps directly after without rebooting, I'm not sure if that screwed it up. Anyway, now I'm in a boot loop.
I held volume down and power and can get in to that screen but it won't seem to let me select fastboot. I just noticed earlier when I plug it in with the power off it will open up Clockworkmod Recovery but after a few seconds the screen goes dark and whatever process began, stops.
When I do open it up with volume down + power it automatically starts up hboot after a few seconds and examines the froyo rom (PC10IMG) I still have on my SD card (at least I assume that's the one it's looking at) and it says the "main version is older / Update fail"
Also on the recovery screen (volume down + Power) it previous said s-off and now it's back to s-on. I think I can get access to adb btw.
I looked through the threads but I couldn't seem to find a definitive answer so I apologize in advance if I didn't scour them as well as I should have. Thanks for any help you can offer!
Sounds like you let your pc10img.zip run again, what method did you use to root? Write down everything on your bootloader screen
Sent from my HTC MyTouch 4G Slide using xda premium
stuck in boot loop
demkantor said:
Sounds like you let your pc10img.zip run again, what method did you use to root? Write down everything on your bootloader screen
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I used the adb method. I downgraded from GB to Froyo and then used the adb commands here (http://forum.xda-developers.com/showthread.php?t=834228) to perm root. I had a stable root after that was all said and done it just went in to the boot loop after I installed Cyanogenmod and the Gapps.
After the boot loop began it DID re-run the pc10img.zip Or well, I should say, I, re-ran it
I downloaded the RUU but I didn't attempt it because I figured I've already gotten myself in enough trouble as it is.
stuck in boot loop
Oh yeah, here's exactly what the bootloader screen says.
It fires up and gives the normal options although it won't scroll down to any of them besides Hboot and it auto selects Hboot.
vision pvt ship s-on
hboot-0.02.0000
microp-0425
radio-26.02.01.15_M2
eMMc-boot
Sept 2 2010, 17:59:38
Fastboot
recovery
factory reset
simlock
image crc
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
HBOOT
SD checking..
loading ...(pc10diag.zip)
No image!
loading ... (pc10diag.nbh)
No image or wrong image!
loading ... (pc10img.zip)
Checking ... (pc10img.zip)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Main Version is Older!
Update fail!
press <power> to reboot.
Yeah you are in tough place right now, never heared of the bootloader you have and the method you used to root can be dangerous, hopefull we can still use clockwork. Remove the pc10img.zip from sdcard and try to boot to hboot and then choose recovery, see if it lets you flash a rom
Sent from my HTC MyTouch 4G Slide using xda premium
stuck in boot loop
demkantor said:
Yeah you are in tough place right now, never heared of the bootloader you have and the method you used to root can be dangerous, hopefull we can still use clockwork. Remove the pc10img.zip from sdcard and try to boot to hboot and then choose recovery, see if it lets you flash a rom
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I removed the pc10img.zip from the SD card and NOW the bootloader allows me to actually make selections. I chose recovery and it went right in to Clockworkmod.
I tried to reflash Cyanogenmod 7 and it seemed to work but it is still in the boot loop. I think the reason it didn't go through correctly was because my phone is now s-on? when I originally rooted it and attempted to flash it, it was s-off. I am beginning to understand the scope of the problem here.
Would it be possible to download a t-mobile stock recovery rom image and flash that with clockworkmod? never tried that before.
Or, should I use the RUU, hope it works and start from scratch?
Or some other option that's beyond me.
Thanks for your help! This isn't my main phone and I was merely rooting it as a backup/experimental phone. I'd rather not have a paper weight but we shall see I guess. Thanks again!
I rooted my other G2 with the described method and it worked like a charm but for future reference is there any safer method available?
See the xda wiki for the proper root method, at this point you should try and flash an ruu through fastboot and start from scratch with the downgrade and root via gfree (xda wiki)
Sent from my HTC MyTouch 4G Slide using xda premium
stuck in boot loop
demkantor said:
See the xda wiki for the proper root method, at this point you should try and flash an ruu through fastboot and start from scratch with the downgrade and root via gfree (xda wiki)
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
So just so I have it straight - root the phone first and then try and flash a stock rom through fast boot? Not sure if that's possible because I'm not sure if I have access to usb debug but I'll check and get back.
I downloaded the RUU from the htc website. Should I just follow the instructions included with that program?
Thanks for the advice!
Start with ruu, if it lets you return to stock great, then move on to the xda wiki, here it will link you to downgrade instructions and then go back to wiki to root and soff via gfree
Sent from my HTC MyTouch 4G Slide using xda premium
Stuck in boot loop.
demkantor said:
Start with ruu, if it lets you return to stock great, then move on to the xda wiki, here it will link you to downgrade instructions and then go back to wiki to root and soff via gfree
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Thank you! RUU worked like a charm! Live to root another day!
Help Help
just brought HTC desire z
try to install ROM but stucked with black screen able to access Recovery but unable to do anything error came up Signature verification failed help me
ComptUnix said:
Help Help
just brought HTC desire z
try to install ROM but stucked with black screen able to access Recovery but unable to do anything error came up Signature verification failed help me
Click to expand...
Click to collapse
Will need more info than that for help, maybe look through this thread a bit, if your question isn't answered post again with as much info as possible
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
Thanks
demkantor said:
Will need more info than that for help, maybe look through this thread a bit, if your question isn't answered post again with as much info as possible
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
what actually happened . i show you
ComptUnix said:
what actually happened . i show you
Click to expand...
Click to collapse
Looks like the zip is signed incorrectly. If you know what I mean by an md5 sum, check it corresponds to the one the developer lists. If you don't know what I mean by an md5 sum, then try to download the ROM again and flash the new download. Which ROM is it by the way?
HTCDreamOn said:
Looks like the zip is signed incorrectly. If you know what I mean by an md5 sum, check it corresponds to the one the developer lists. If you don't know what I mean by an md5 sum, then try to download the ROM again and flash the new download. Which ROM is it by the way?
Click to expand...
Click to collapse
used
http://www.xda-developers.com/android/cm10-1-test-builds-for-the-htc-g2-desire-z/
http://uploadingit.com/file/view/gr83oiqs1usscjac/aosp-4.2.2-20130307-vision.zip
both gave error ..
I am noob in doing this but can do just give me a way to install or by pass this signature check in this bootloader.
can install bootloader from SD card ?
Tried aosp-4.2.2-20130307-vision.zip shows updated successfully but no display after restart . any idea
Slightly out of my depth here, but go to the thread demkantor posted a few posts up and read carefully, it will be very informative.
Also you appear to be using stock Android recovery, I'm not certain this is a problem but just to make sure I would find out how to use fastboot to flash clockworkmod recovery. Just Google "flash clockworkmod recovery fast boot" or something along those lines... If you already have android SDK set up, etc. Which I assume you must have being as you're rooted, it shouldn't be too difficult.
Sorry this is about as much as I can help, I'm sure demkantor will be able to help you through anything more than this.
HTCDreamOn said:
Slightly put of my depth here, but go to the thread demkantor posted a few posts up and read carefully, it will be very informative.
Also you appear to be using stock Android recovery, I'm not certain this is a problem but just to make sure I would find out how to use fastboot to flash clockworkmod recovery. Just Google "flash clockworkmod recovery fast boot" or something along those lines... If you already have android SDK set up, etc. Which I assume you must have being as you're rooted, it shouldn't be too difficult.
Sorry this is about as much as I can help, I'm sure demkantor will be able to help you through anything more than this.
Click to expand...
Click to collapse
thanks buddy ,
yes having andriod sdk .
THIS THREAD will teach you how to use fastboot to do
various things such as flash a new recovery. problem is you dont have a bootloader with fastboot
capabilities, well at least not many. do you know how the phone was rooted? if it was
done using the gfree method than you can simply flash one of the PC10IMG.zips from
post 30 in the thread linked above (done via bootloader) if not it could be an issue to use do this.
you can only flash update.zips through the recovery you have now and they more than likely would need to be signed by htc. if you dont have a working os right now then
you may need to flash an ruu (one that matches your phone) let me know where you stand on all this
demkantor said:
THIS THREAD will teach you how to use fastboot to do
various things such as flash a new recovery. problem is you dont have a bootloader with fastboot
capabilities, well at least not many. do you know how the phone was rooted? if it was
done using the gfree method than you can simply flash one of the PC10IMG.zips from
post 30 in the thread linked above (done via bootloader) if not it could be an issue to use do this.
you can only flash update.zips through the recovery you have now and they more than likely would need to be signed by htc. if you dont have a working os right now then
you may need to flash an ruu (one that matches your phone) let me know where you stand on all this
Click to expand...
Click to collapse
i used a app to check root status it says access granted . that means rooted ??
i have uploaded my bootloader screenshoot .
i am unable to connect over adb
ComptUnix said:
i used a app to check root status it says access granted . that means rooted ??
i have uploaded my bootloader screenshoot .
i am unable to connect over adb
Click to expand...
Click to collapse
give me link for rom for htc desire z which work fine on my phone
https://www.dropbox.com/sh/ucdfd91qn7h1dbm/kTTY8yOJLN/PC10IMG
That's the link for some custom PC10IMG.zips but again I can't promise they are safe to flash if you just rooted your phone with some app.
Adb won't work being all you have is a stock recovery and no os, adb won't work in bootloader mode
As for an ruu, I don't what was specific to your phone, you can see if this command works to check, may not though
fastboot getvar all
Sent from my SGH-T839 using Tapatalk 2
demkantor said:
https://www.dropbox.com/sh/ucdfd91qn7h1dbm/kTTY8yOJLN/PC10IMG
That's the link for some custom PC10IMG.zips but again I can't promise they are safe to flash if you just rooted your phone with some app.
Adb won't work being all you have is a stock recovery and no os, adb won't work in bootloader mode
As for an ruu, I don't what was specific to your phone, you can see if this command works to check, may not though
fastboot getvar all
Sent from my SGH-T839 using Tapatalk 2
Click to expand...
Click to collapse
thanks buddy i test this..
this can can help you
Vision PVT SHIP S-OFF
HBOOT-0.85.0012
MICROP-0425
RADIO-026.08.04.16_M
eMMC-boot
shows on bootloader
Done
ComptUnix said:
thanks buddy i test this..
this can can help you
Vision PVT SHIP S-OFF
HBOOT-0.85.0012
MICROP-0425
RADIO-026.08.04.16_M
eMMC-boot
shows on bootloader
Click to expand...
Click to collapse
thanks to all
Is your phone up and running then?
Sent from my Nexus 7 using xda premium