My S-Off, Alfarev Desire running the latest CM7 RC has been working very well for some time until recently I used it for navigating. It got very hot until it turned off. I thought it was nothing out of the ordinary (very hot and sunny over here, wasn't too surprised) until in the evening, after it had cooled off for several hours it simply refuses to get past the splash screen (the joker screen). I'd be happy to reflash and see if that's the problem, but I can only access fastboot and hboot: if I select recovery, it just gets stuck on the splash screen again. I've tried leaving it for a while, but turned it off after an hour as it was obviously going nowhere.
What should I do?
Thanks to all the gurus that may have some lifesaving advice.
Should be in the Q&A section.
@lucchini please explain to me why is there a Q&A (QUESTION AND ANSWER) section.
ooops, sorry about that - I'll see if I can get somebody to move it.
Anybody that actually has some advice?
look here mate http://www.youtube.com/watch?v=JmvCpR45LKA
Put it in the refrigator for a while (im not kidding), it helped numerous people with same issue.
You say that you can enter bootloader, so that means that you can flash RUU
Sadly, I tried that already to no avail. I also tried leaving it for a few days and then restarting, but nothing's changed.
Then find a good solid hammer and show that bitc* what she desirves
lucchini said:
Sadly, I tried that already to no avail. I also tried leaving it for a few days and then restarting, but nothing's changed.
Click to expand...
Click to collapse
Is your phone recognized in fastboot?
Try running:
fastboot devices
Did you rooted and s-offed your phone with revolutionary? If us, you have to flash bravo downgrader before you can apply ruu.
Or did you (also) get cid error when you wanted to apply ruu?
TouchPaled from Oxygen with Transparent XDA App
Thanks for all the replies.
update: It was indeed recognised in fastboot devices, so I followed jeremija8's suggestion and ran the RUU. Everything was going smooth until it got to the system files, when it said the partition didn't exist. It has since been stuck in the black HTC screen with a /!\ sign in each corner. As I understand it, it's still in fastboot, but I'm starting to feel a sense of impending doom now.
Any ideas?
Again, thanks to all.
SOLVED: I finally figured it out - I had a damaged system partition. Managed to fix it by using fastboot from within Teppik74's downgrade tool [http://forum.xda-developers.com/showthread.php?t=768256] to erase everything, then ran the latest official WWE RUU which set everything to stock. Finally back in business.
A big thank you for everybody's suggestions, especially howdid's video - very entertaining.
lucchini said:
SOLVED: I finally figured it out - I had a damaged system partition. Managed to fix it by using fastboot from within Teppik74's downgrade tool [http://forum.xda-developers.com/showthread.php?t=768256] to erase everything, then ran the latest official WWE RUU which set everything to stock. Finally back in business.
A big thank you for everybody's suggestions, especially howdid's video - very entertaining.
Click to expand...
Click to collapse
Have exactly the similar problem , stuck on Alpharev splash screen. Can you please explain what do you mean by erase everything or if you can give details of the steps you performed ?
Thanks
ridhavm said:
Have exactly the similar problem , stuck on Alpharev splash screen. Can you please explain what do you mean by erase everything or if you can give details of the steps you performed ?
Thanks
Click to expand...
Click to collapse
This is what I did last night when I was stuck on the alpharev logo (albeit with a CACHE error having no space, but this should erase the partitions so you can start from scratch again):
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/show....php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
Good luck
EddieN said:
This is what I did last night when I was stuck on the alpharev logo (albeit with a CACHE error having no space, but this should erase the partitions so you can start from scratch again):
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/show....php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
Good luck
Click to expand...
Click to collapse
Thanks . Just to add some more information, when I took out the memory card earlier today, windows detected it as corrupt and asked to reformat it.
I have used Fastboot and followed these steps, but getting this message :
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
I believe I recently formatted my windows system and its missing drivers.
Is there any way to install the drivers without connecting phone ?
Thanks again for your help.
Got it , Here is the Device Info:
SPL/hboot version: 0.93.0001.
Radio version: 5.11.05.27.
Main software version: 2.12.110.4.
cid: t-mob005.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
I had RCMIX v2.x installed on my desire
ridhavm said:
Thanks . Just to add some more information, when I took out the memory card earlier today, windows detected it as corrupt and asked to reformat it.
I have used Fastboot and followed these steps, but getting this message :
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
I believe I recently formatted my windows system and its missing drivers.
Is there any way to install the drivers without connecting phone ?
Thanks again for your help.
Click to expand...
Click to collapse
Now that you say it, it might be your SD card acting up. So try and reformat it and prep it according to this: http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3.
I wouldnt recommend 512mb ext though, people usually recommend 1gb
After this you'll have to reflash the rom again and do a full wipe
Thanks, Tried reformatting SD card , was still stuck on boot loop.
Got Screwed up further now , Tried installing the official TMo RUU, it detected the phone in fast boot mode but aborted in the middle with error relating to verifying signature.
Now stuck with a Black bricked screen. No display , not able to get to FastBoot mode now.
ridhavm said:
Thanks, Tried reformatting SD card , was still stuck on boot loop.
Got Screwed up further now , Tried installing the official TMo RUU, it detected the phone in fast boot mode but aborted in the middle with error relating to verifying signature.
Now stuck with a Black bricked screen. No display , not able to get to FastBoot mode now.
Click to expand...
Click to collapse
Tried with a new recovery through ADB?
EDIT: Try this http://forum.xda-developers.com/showthread.php?t=831734
Related
First off, this forum rocks. First post but have read a tremendous amount since learning to root and rom my Thunderbolt.
I upgraded to the Galaxy Nexus (CDMA), and decided to try the "one-click root" which left me with the followign problem.
It seemed to work ok, however when I booted into recovery, recovery failed to load and I got the android w/ exclamation.
I tried a few other things to no avail, at one point I hit a volume up and down and got a limited clockwork menu on the screen, one which was factory wipe (as I was intending to install a ROM).
The wipe hung, so I pulled the battery and was left in a loop.
I booted back into fastboot, and it shows as unlocked, but I can't get it to show as a device in ADB.
I'm assuming this may be a driver issue. I did re-download the Android SDK but this didn't seem to make a difference.
I get the USB connection, but the phone displays "Fastboot Command Read Error -2147483647". I did try to kill server and try again as I saw suggested in some other posts but no luck.
In device manager it shows as "SAMSUNG Android ADB Interface" for the driver 2.9.310.1125.
I'm thinking fastboot should be a non-samsung branded driver?
Anyhelp is appreicated.
thanks!
soulman1980 said:
First off, this forum rocks. First post but have read a tremendous amount since learning to root and rom my Thunderbolt.
I upgraded to the Galaxy Nexus (CDMA), and decided to try the "one-click root" which left me with the followign problem.
It seemed to work ok, however when I booted into recovery, recovery failed to load and I got the android w/ exclamation.
I tried a few other things to no avail, at one point I hit a volume up and down and got a limited clockwork menu on the screen, one which was factory wipe (as I was intending to install a ROM).
The wipe hung, so I pulled the battery and was left in a loop.
I booted back into fastboot, and it shows as unlocked, but I can't get it to show as a device in ADB.
I'm assuming this may be a driver issue. I did re-download the Android SDK but this didn't seem to make a difference.
I get the USB connection, but the phone displays "Fastboot Command Read Error -2147483647". I did try to kill server and try again as I saw suggested in some other posts but no luck.
In device manager it shows as "SAMSUNG Android ADB Interface" for the driver 2.9.310.1125.
I'm thinking fastboot should be a non-samsung branded driver?
Anyhelp is appreicated.
thanks!
Click to expand...
Click to collapse
When you boot back into fastboot look under device manager on your computer and you will probably find a yellow question mark by your device. You will need to download the Samsung driver and manually install it at that screen. Then you can fastboot oem lock and then fastboot oem unlock and that should fix your boot loop issue. The android with exclamation point is the factory recovery, if you rooted and still have root download rom manager in the market and flash clockworkmod through it.
badassirocz said:
When you boot back into fastboot look under device manager on your computer and you will probably find a yellow question mark by your device. You will need to download the Samsung driver and manually install it at that screen. Then you can fastboot oem lock and then fastboot oem unlock and that should fix your boot loop issue. The android with exclamation point is the factory recovery, if you rooted and still have root download rom manager in the market and flash clockworkmod through it.
Click to expand...
Click to collapse
definitely check for any drivers, but i haven't heard anybody needing to re-lock & unlock before. once you have the drivers you should be able to use 'fastboot' from the fastboot screen. not adb. after your drivers, type 'fastboot devices' and see if anything comes up.
also, if you can get into clockwork recovery, look at your device manager again for yellow errors....often there is another driver that doesn't install itself properly; the one that allows you to use adb while in CWM.
cancerouspete said:
definitely check for any drivers, but i haven't heard anybody needing to re-lock & unlock before. once you have the drivers you should be able to use 'fastboot' from the fastboot screen. not adb. after your drivers, type 'fastboot devices' and see if anything comes up
Click to expand...
Click to collapse
Fastboot OEM lock and the Fastboot OEM unlock is a known fix to correct a loop soft brick issue that he noted
badassirocz said:
Fastboot OEM lock and the Fastboot OEM unlock is a known fix to correct a loop soft brick issue that he noted
Click to expand...
Click to collapse
which is because it is just doing a factory wipe correct? if he fixes his drivers & fastboot issue, he should be able to just flash an image without wiping the whole phone
I guess in some aspect yes but if the phone is not softbricked anymore that he should be fine not doing it. Most of the time the ADB issue is like you stated that when you boot into fastboot the driver is not recognized so you need to do a manual install to fix it. If his battery pull left the phone stuck in a boot loop he will have to re-lock and then unlock to fix it.
You guys really are a godsend.
So, the drivers all seemed good and installed properly (no exclamation or question mark in Device Manager).
Ultimately, I knew there was a driver issue so I just went to a different computer (running win7 64). Coulnd't get that to work, then found drivers arn't supported. I also found the PDANET work around.
This allowed me to install the driver and fastboot WAS able to detect the device.
Following some advice and some other posts I tried "fastboot oem lock", which worked successfully.
I then rebooted, was still in a loop, then pulled the battery.
I ran "fastboot oem unlock", then rebooted.
This time I got past the "google" screen and got the graphic screen.
This sat for awhile (3-4 minutes)??
Then it rebooted again (I almost cried) and I was back to the google logo. Again, it went past this point and displayed the graphical animation again.
Than, on the second time around came the "Welcome!" screen!!!!!!
As well as a rush of relief that is indescribable....
I spent 5 minutes living as Phillip Seymour Hoffman in Boogie Nights sitting in his car outside the party - then did a human xanax reboot and am happy to go to bed!
I'm only posting all of this in detail as an update, and so it is available for anyone else who may come into this problem.
It seems there are many ways to get stuck into this boot-loop besides what I did.
NOW - the next problem....
I'm in my phone, everything works. HOWEVER, I apparantly have a corrupt or bad install of Clockworkmod on my phone.
Do I just try everything again from scratch, or is there something I should do differently to reinstall CWM Recovery?
Thanks again!
glad you got booted. drivers are supported for windows 7 64x, using them currently btw.
i would download a new copy of cwm, confirm its md5 checksum first, and flash it again if you think its corrupt, or if you have rom manager you should be able to do it from there.
good luck
Glad you got it fixed. The lock and unlock fixes the boot loop issues as you found out. I would root your phone with cf-root using adb which you can find here on xda. Then install clockworkmod through rom manager which you can download free in the market.
Thanks again guys, all is good in the hood.
I followed the instructions to re-install CWM here:
http://forum.xda-developers.com/showthread.php?t=1392336
I picked up where I had left off (I already had phone unlocked).
All is perfect!
can't thank you all enough
Hello everybody,
This is my first post on XDA, although I've visited the site oftne
Anyways:
Yesterday I successfully rooted my One X and unlocked its bootloader. I also installed CWM recovery.
As the day came to a close I tried to install LC_MOD in an attempt to change the multitasking softkey to a menu button.
I did not make a backup, and the phone had no backups.
Needless to say the phone wouldnt boot. I panicked and in blind fear sortof erased everything off of my phone. everything. What I basically did was i went into advanced settings and formatted my /sdcard and all those other folders, hoping that would solve the issue (a simple data/cache wipe didnt work). So much data has been erased from the phone that I cannot even mount usb storage through CWM because im missing a file.
So, I come to you all, you gods of the tech world, with my head bowed, to ask for your help. I have literally tried everything in my power to fix the issue. I tried to install custom roms manually, that didnt work. I tried to install an RUU, and even that didnt work (the software could not detect my device). This was all made even more difficult because I myself have a mac, and much of the software I had to use was windows based, which led me on a journey to create a virtual machine.
I know i messed up, and what I'm really hoping someone out there cn do is upload one of their own backups of their One X's software, and show me how to use that to restore my phone.
Somebody out there please please help me :'(
Hi;
There is a reason all developers here shout out loud:
1- BACKUP YOUR PHONE BEFORE YOU F*** IT UP
2- DO NOT DO ANYTHING UNLESS YOU ABSOLUTELY KNOW HOW TO
But anyways, you ruined it, you should get it back, Hopefully you did not drain the battery below 30%, in that case keep on reading the next paragraph, but if you dropped the battery below 30, you should go to CWM Recovery, connect your phone to charger, and wait until it's charged properly...
After charging the phone, you need the correct RUU for your phone... As it seems, you don't know what you're doing, so go to fastboot, type this command:
Code:
fastboot oem readcid
Then post the code here in this topic, so someone can help you find the correct RUU for your phone...
After that go to THIS topic and follow the part where it says "If you DON'T have custom rom or Nandroid backup on internal SD card"
Thanks
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Xial649 said:
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Click to expand...
Click to collapse
Don't worry, with the correct version of RUU you can restore your phone...
Sent from my HTC One X using XDA
Next?
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Xial649 said:
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Click to expand...
Click to collapse
Your phone is from Voda Germany, and most probabely your correct RUU is this:
Code:
http://www.filefactory.com/file/t7qugfd3ey9/n/RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed.exe
Download it. Hopefully it would be the correct RUU for your phone.
1- Now open the exe file you just downloaded and make sure that it fully started.
2- Don't click anything, just open "Computer" (formerly known as my computer) in windows and enter %temp% in your address bar.
3- You will now see some folders, just search through these folders for the ROM.zip (using windows search function)
4- When you found it, copy it to your desktop.
5- Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
6- Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
7- Go to your One X, go into the bootloader and go into fastboot mode. then connect your phone to computer.
8- Open CMD and navigate to the folder in which you have the two images and the fastboot file. (using cd command and after that the address you want to go to)
9- Now type in that
Code:
fastboot flash boot boot_signed.img
10- Now this one
Code:
fastboot flash system system.img
if all this is successful, you can just reboot your phone and everything is OK.
If you can't do any of these, let us now, we will help you through it...
Good lock
---------- Post added at 03:52 PM ---------- Previous post was at 03:41 PM ----------
In other note, RUUs are build to do an stand alone recovery of your phone. So you can first try, just running the RUU application and following the instruction given in the RUU. it may work correctly
This is good
Alright so i got everything going after downloading the RUU and it was in the process of restoring my phone, but then it said my battery went below 30% so i needed to recharge. At that point i had to leave, and so I noticed that if i left my phone in the booting animation (HTC logo) the LED light indicated that the phone was charging. Since I wasnt entirely convinced that my CWM recovery was actually charging the phone, i left it on booting while connected to my pc and hopefully itll be fully charged and ready to be restored tomorrow..... I really appreciate all the help you've given me man you've practically saved my life here , and I'd like to say that you've made my first cry for help a simple and smooth one.... Thank you very much my friend :victory: :highfive:
Problem
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Xial649 said:
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Click to expand...
Click to collapse
That's another method you can try, boot_signed is the stock kernel (and yes it's that small) and the recovery_signed is the stock recovery...
Since my previously mentioned method didn't work, do this:
1- flash the boot_signed.img into your device (fastboot flash boot boot_signed.img)
2- flash the recovery_signed.img in the device (fastboot flash recovery recovery_signed.img)
3- erase cache (fastboot erase cache)
4- lock your phone (fastboot oem lock)
5- now try again to flash the system image (fastboot flash system system.img)
And also, try having around 40% battery to do all this, don't let the battery drops under 30%
ALRIGHT!!!!
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Xial649 said:
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Click to expand...
Click to collapse
Your phone is "Vodafone Germany" version and the link I gave you is the "Voda DE" which seems right, but you can try that as well, doesn't heart...
No, for original ROM (RUU) you should have a locked boot-loader, unlocking is just for custom ROMs.
ok
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Xial649 said:
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Click to expand...
Click to collapse
The two first commands should work on a LOCKED boot-loader, so I think step 1 would not be necessary... If your phone is locked you should be able to do all steps 2, 3, 5 without problem (step 1 and 4 are the exact opposite of each other and if the phone is locked already I think can be skipped)
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Xial649 said:
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Click to expand...
Click to collapse
Any luck in running the RUU itself directly?
i gave up
alright so nothig worked. Not the manual flash, and not the RUU itself. So ive resolved to visit my local help center for HTC devices, and see what they can do, if they cant fix it the least they can do is send it to the german branch for repairs. Thanks for all your help mate, you've really proven to be a great guide, but I guess something just isnt clicking in this case :/.......... i love u man
I'm not sure if this would work.
If you are still htcdev unlocked:
1. Enter bootloader in fastboot usb
2. Fasboot flash recovery -your recovery .img here"
3. Boot into recovery
4. Go to "mounts and storage"
5. Mount SD(I think this is right) and your sd should show up in your pc
6. Copy your rom zips and other zips you need/want
7. Unmount SD
8. By this time you should be able to flash your rom
9. Make sure you flash boot.img again in bootloader.
Hope this helps
Sent from my HTC One X using xda app-developers app
Isn't it mount usb storage?
Sent from my HTC One X using XDA Premium App
You couldn't mount the USB storage / sdcard because you were running CWM from the bootloader. If you connect it to the pc you can put the recovery file you flashed into the fastboot folder and do:
fastboot boot *recoveryfilename*.img
Then you can mount the sdcard etc.
If you have photos and things you don't want an ruu to get ride of, you can fix the ROM. You broke it by trying to install an deodrexed mod for an odexed Rom. If you're interested I can tell you how to fix it.
You could also take this opportunity to install a custom Rom, with which I can also help.
Following on from this problem:
http://forum.xda-developers.com/showthread.php?p=39472437
Phone has been working fine after install of AOKP (http://forum.xda-developers.com/showthread.php?t=1642443).
Until I swapped SIM cards to try EE vs. GiffGaff for service and running costs.
I switched SIM card back and phone started boot loop.
HTC screen then AOKP screen with Unicorn head, then phone resets and starts loop again.
So tried booting without SD card and SIM get to home page for a few second and then reboots.
So tried wipe data/factory reset and wipe cashe partition, now get as far as first page of new android user, then reboots.
With power button and - key I get:
vision pvt eng s-off
hboot- 0.76.2000 (PC1011000)
microp-0425
radio-26.03.02.18_M3
eMMC-boot
Suggested next course of action? As I assume AOKP and/or Android is damaged.
I have read most of the boot loop topics, but do not seem to cover this version of boot loop (So new topic). Do not want to go any further until I was sure I would not make things worse.
Ive heard a couple people complain about similar things before but truthfully the reason why doesnt make too much sense to me, do you mind capturing a logcat?
also may be interested in reading through THIS PAGE if you havent already. also will find info on logcats here if youre unaware
my guess is there is a corrupt partition somewhere as after doing some wiping you still have a bootloop
to fix it youll be best of starting with a full wipe and format, either by formatting all partitions in 4ext recovery,
flashing a superwipe script, or the aio nullifier script (both linked in the thread above)
or booting into fastboot and wiping from there
fastboot erase system -w
or do all those, im a bit ocd when it comes to wiping so i would
if this fails then it could be within a firmware partition, like radio or hboot, this seems unlikely to me as
there shouldnt be an write to these at all, but your situation is uncommon and a bit strange so
if you want flash a new radio and or hboot via fastboot OUTLINED HERE or go to the 30th thread and flash a PC10IMG.zip
good luck!
I'm facing a similar bootloop and can't figure out why
@demkanator
Can you please have a look at my thread?
http://forum.xda-developers.com/showthread.php?t=2214813
Re: [Q] Desire Z bootloop with JB roms
Can you post a logcat? Also will you boot into your bootloader and write down EVERYTHING on that screen here?
Sent from my Nexus 7 using xda premium
Requested information
demkantor said:
Can you post a logcat? Also will you boot into your bootloader and write down EVERYTHING on that screen here?
Click to expand...
Click to collapse
I only have clockwork recovery 5.0.2.7 on phone, not sure I can put on or use 4ext recovery, flashing a superwipe script, or the aio nullifier script.
I have wipe data/factory reset which got this result
"Formatting /data
Formatting /cache
Formatting /sd-ext
No app2sd partition found. Skipping format of /sd-ext.
Formatting /sdcard/.android_secure
Data wipe complete."
Also did wipe Dalvik Cache:
"Dalvik Cache wiped"
At this point phone will still do reboot loop.
But on booting into fastboot and wiping from there fastboot erase system -w. Phone now sits on HTC screen.
Though I can still get to clockwork recovery and Hboot/Fast boot.
Again here I will stop so as not to make anything worse.
Here information you asked for:
System Info
SN-HT0AJRT03242
LCD-S0
Touch Panel-ATEMEL224_20aaY
Commit-97743036
OS Ver.01.34.707.3
IMEI-352212040170091
CID-11111111
eMMc-unknown 2223MB 4554751sectors
IMAGE CRC:
hboot: 0x6570C0DB
boot: 0x70A9908C
recovery: 0xB983BB96
system: 0x61EF2FF9 (THIS was result before I did fastboot erase system -w")
system: 0x0 (Is result after fastboot erase system -w")
With ADB running I plug USB into phone, phone boots to clockwork recovery menu (Which I can move up and down menu with -/+).
Note: I use the menu for about 25 seconds and regardless of any pressing - or + before screen go's blank. But orange LED on (I assume charging?).
I type: "adb devices"
I Get "HT0AJRT03242 recovery"
I type: "adb logcat > logcat.txt"
File saved has just "/sbin/sh: exec: line 1: logcat: not found"
You are missing the first bit of info in hboot, can you please add this, lines starting at
Vision pvt.....
Also is fastboot working?
Sent from my SGH-T839 using Tapatalk 2
More information
demkantor said:
You are missing the first bit of info in hboot, can you please add this, lines starting at
Vision pvt.....
Also is fastboot working?
Sent from my SGH-T839 using Tapatalk 2
Click to expand...
Click to collapse
Booting phone (Holding power + -Key) I get:
Vision PVT ENG S-OFF
HBoot-0.76.2000 (PC1011000)
MICROP-0425
EMMc0-boot
Aug 20 2010, 16:51:01.
Hboot screen shows "HBoot USB PLUG", when I select FASTBOOT from menu screen displays "FASTBOOT USB".
But with phone on this screen displaying "HBoot USB PLUG" or "FASTBOOT USB", I type "adb devices" and get nothing but text "List of of devices attached" nothing after that.
But if I repeat "With ADB running I plug USB into phone, phone boots to clockwork recovery menu (Which I can move up and down menu with -/+)."
I type: "adb devices"
I Get "HT0AJRT03242 recovery"
adb will only work in recovery and in os (so long as debugging on etc)
in fastboot mode use fastboot, similar but different
HERE ARE SOME TIPS ON FASTBOOT i suggest to study them as they can be just as handy as adb
but for now try to get into fastboot mode and type this is cmd
Code:
fastboot devices
if you see yours good, if not read the linked thread
then go with
Code:
fastboot oem check_emmc_mid
see if it says samsung or sandisk
the above is goo information to know, so check it out and respond back.
but i believe you will find your fix HERE
read and ask questions if needed
good luck!
Contining understanding
demkantor said:
adb will only work in recovery and in os (so long as debugging on etc)
in fastboot mode use fastboot, similar but different
HERE ARE SOME TIPS ON FASTBOOT i suggest to study them as they can be just as handy as adb
but for now try to get into fastboot mode and type this is cmd
Code:
fastboot devices
if you see yours good, if not read the linked thread
then go with
Code:
fastboot oem check_emmc_mid
see if it says samsung or sandisk
the above is goo information to know, so check it out and respond back.
but i believe you will find your fix HERE
read and ask questions if needed
good luck!
Click to expand...
Click to collapse
Typing "Fastbook devices" shows my device.
Typing "fastboot oem check_emmc_mid" I get:
"<bootloader> Manufacturer ID, MID=45
<bootloader> eMMC should be unkonwn
OKAY [ 0.000s]
finished. toal time: 0.016s"
Trying to understand why this happened and what was damaged, but seem next stage is to re-do and clear old install (You link above)?
Could I just put Android 4 rom back on at this point, if that was only damage? or better to check and other parts of install?
These are the guides I originally used to setup Android.
http://wiki.cyanogenmod.org/w/Install_CM_for_vision
http://forum.xda-developers.com/showthread.php?t=1642443
Well I don't like that lit says unknown but there really isn't much more you can do @ this point. I would just flash one of those PC10IMG.zips and if it works flash a new ROM, you'll either have a working phone or be in the same place you are right now
Good luck!
Sent from my Nexus 7 using xda premium
Trouble ahead?
demkantor said:
Well I don't like that lit says unknown but there really isn't much more you can do @ this point. I would just flash one of those PC10IMG.zips and if it works flash a new ROM, you'll either have a working phone or be in the same place you are right now
Good luck!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
PC10IMG.zip on SDCARD booted Hboot and get:
SD Checking
Loading...[PC10DIAG.zip]
No Image
Loading...[PC10DIAG.nbh]
No Image or Wrong image!
Loading...[PC10IMG.zip}
No Image
Loading...[PC10IMG.nbh]
No Image or Wrong image!
There seem to be alot of PC10IMG.zip am I using wrong one? If so do you have a link for HTC Desire Z version?
Use one of the two that I made, dont use others, I linked them to you earlier, the instructions on how to flash is there as well.
The reason you are getting this message though is you either didn't name it right, its not on root of SD, SD is not formatted properly, etc
Sent from my Nexus 7 using xda premium
Up and running.
demkantor said:
Use one of the two that I made, dont use others, I linked them to you earlier, the instructions on how to flash is there as well.
The reason you are getting this message though is you either didn't name it right, its not on root of SD, SD is not formatted properly, etc
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for your help, from a person who just about understand which way up to hold phone
After following your links and all stages and then reinstalling Android Open Kang Project builds for HTC Vision, phone working again (For the moment).
But still trying to understand why this happened, as switching SIM cards should not do this.
So one I had finished setting up phone again I when back to some of your previous questions and comments.
re-tried "fastboot oem check_emmc_mid" result:
"<bootloader> Manufacturer ID, MID=45
<bootloader> eMMC should be Scandisk
OKAY [ 0.016s]
finished. toal time: 0.016s"
Which is different from last time (and was something you did not like before). Let me know I can make any other checks that might help someone else out of the same problem?
Can't say for sure why this happened but you had a severely corrupt partition on the emmc and phone wasn't even reading its id. Changing the sim shouldn't do this and it could have been some kind of coincidence but I've heard others say the same thing before so.... Your guess is as good as mine.
Glad its all working!
Sent from my Nexus 7 using xda premium
Try reflashing the baseband changer.zip and then the simunlock.zip after changing the SIM Cards.
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
MerkyBlud said:
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
Click to expand...
Click to collapse
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
MaratabHashmi said:
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
S-off requires rooting it first, am I right? Not having much luck with that - HTC Quickroot claims its been done but none of the apps such as SuperUser are present when it reboots...
Suggestions anyone? efforts to S-OFF not working so far...:fingers-crossed:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
bananagranola said:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
Click to expand...
Click to collapse
I'm trying running the .exe file from the pc, I'm 99.9% sure its the correct region (3UK stock). It gets as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (tried 3 different cables and there is no issue with faulty cables, or either end being unplugged, ). ADB doesnt see the phone as connected. Fastboot doesnt seem to do much as usually when the phone reboots as part of the process it freezes or goes back into bootloop. I've tried putting ROMs on the sd card and updating from the recovery menu but the phone doesnt see the card as mounted in this mode (when it does boot and run ok for a few minutes it does eventually see the card).
I'm confused. You have a recovery menu? Is your phone's bootloader unlocked?
Sorry, I mean the menu accessed through power on + vol down. No, tried unlocking it through the HTC site but no joy.
That's the bootloader. What procedure are you using for fastboot?
Via ADB commands - havent tried with fastboot methods recently though so I forget which particular guide I was using. I'm sure there are all kinds of noob alarms and flashing lights going off somewhere
You cannot run a RUU from adb. Only fastboot.
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
MerkyBlud said:
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
Click to expand...
Click to collapse
You need to change to the correct folder on your PC where your fastboot.exe file is, thats why your getting your error.
Why you trying to flash stock recovery? Unless I missed it, From what I can see on your posts your still s-on, so you can't flash anything like that from fastboot anyway.
Sent from my GT-I9505 using xda app-developers app
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
bananagranola said:
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
Click to expand...
Click to collapse
Yeah, I was initially trying to run the RUU.exe but that method wasn't working as I mentioned, so I tried extracting the rom it created and flashing that via fastboot.(Didn't know that shift/rightclick thing, thanks). As for s-off I haven't found a way of doing that without rooting, hence why I thought I couldn't get anywhere without rooting the phone first.
When I try and unlock the bootloader ( at http://www.htcdev.com/bootloader/ruu-downloads) , it wants to update the HBOOT first, this is how far I get with the process:
"BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
To install the RUU, simply follow these instructions:
On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes. After your computer has found your phone, double click on the RUU to start the process"
I get as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (so exactly the same problem trying to update the HBOOT as trying to run the RUU.exe) so I'm not sure how I'm going to unlock the bootloader if this method isn't working - direct .exe method doesnt work, and the process I need to unlock the bootloader so I can flash via fastboot doesnt work for the same reason.
Have you tried booting into bootloader and choosing fastboot before trying the RUU?
Yep. Same USB connection error despite having 'FASTBOOT USB' showing....
Type "fastboot devices." What does it say? Do you have your drivers from HTC Sync installed?
Hi all, had the phone working ok for a while, it wanted to do a software update which froze at 12%, however after cancelling it the phone seems to be problem free. Dont really get this as surely the incomplete update wouldnt take..? but something must have changed. The phones been ok for over a week now although I havent rebooted it or let the battery run flat...still dont trust it entirely!
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Look at the following thread, may be this can help
http://forum.xda-developers.com/showthread.php?t=2662787
Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse
Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2
Just a little more info Gizmoe please
Gizmoe said:
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2
Click to expand...
Click to collapse
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.
Dugoutdog said:
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.
Click to expand...
Click to collapse
Can you send fastboot commands like
Code:
Fastboot devices
And see your device listed?
PS: to above
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).
Dugoutdog said:
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).
Click to expand...
Click to collapse
Did you read my other post. Can you confirm if you have fastboot connectivity? RUU mode is a command not a list option.
gizmoe
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.
Dugoutdog said:
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.
Click to expand...
Click to collapse
You have connectivity then. It's not going to list it in " my computer" unless its booted into Rom. Just use this thread
http://forum.xda-developers.com/showthread.php?p=46286588
To flash RUU. Don't do relock or s on just flash the stock RUU.
This is where I'm lost again
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.
Dugoutdog said:
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.
Click to expand...
Click to collapse
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.
my sub-directory
Gizmoe said:
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.
Click to expand...
Click to collapse
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.
Dugoutdog said:
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.
Click to expand...
Click to collapse
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
now waiting
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Waiting for download to finish and getting ready for work. It will be close to see if I get it done before I have to leave. If not will finish at 3:00am when I get home and get back to you either way.
almost home
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.
Dugoutdog said:
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.
Click to expand...
Click to collapse
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.
Command Error
Gizmoe said:
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.
Click to expand...
Click to collapse
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.
Dugoutdog said:
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.
Click to expand...
Click to collapse
First type fastboot devices and make sure its connected. Phone needs to be in fast boot mode. Screen should read fastboot usb in red letters. Then type exactly
Fastboot oem rebootRUU
Then
Fastboot flash zip RUU.zip
RUU.zip needs to be in the same directory cmd is reading.
Something is happening . . . . . "sending zip"
resent as failed like you said.
failed as you stated . . . resent. It also said failed resend immediately. something is gyrating.
OK. at bottom of command prompt it says "Successful OKAY 249.248s" Finished total time 312.192 sec.
My phone has HTC in white small letters and a solid green bar below it.
Before I screw anything from this point, what do I do now? Just press the power button?