(My Download Mode screen while stuck in boot-loop)
*** UNLOCKED ***
htc_pmewh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.42.651.6
Jan 18 2017, 11:10:08(857212)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security checking failed GT_CONNECT_FAIL
Security Warning
Bla bla bla
SD MOUNTED
OTG NOT MOUNTED
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
So, I had Viper10 5.9 with TWRP, Magisk, and SuperSu but somehow messed with one of my color settings and just couldn't figure out how to fix it, this went on for weeks... so I decided to restore it and reflash the ROM. Somewhere in that process S-OFF went to S-ON, I believe, not sure if it makes a difference but from all the searching I've done trying to figure this out it seems like a big deal. Anyway, I can tell you this...
1) When I tried to format data through TWRP before it said something like "failed to mount bla bla bla device is busy or in use" (maybe something to do with encryption? or root? maybe not having root anymore since I had uninstalled SuperSu?
2) Now when I try to format data through TWRP it acts as if everything is fine and then I reboot and I'm stuck in a never-ending boot loop again
3) When I try to flash my firmware zip (which I got from here) in Download Mode I get
"22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
4) When I try to ADB sideload through TWRP it says the zip file is corrupt
5) When I try the HTC RUU (while in Download Mode) it never gets past the first screen where InstallShield or whatever is setting up
6) I just flashed Viper10 5.9 through TWRP and it worked all of a sudden (wasn't working before, while stuck in the loop)... I went with Magisk and MagiskSu this time to avoid a future conflict (not that I now what I'm doing or anything)
So I'm wondering if I'm okay... I'm still S-ON (I thought it went S-OFF when rooted?) and everything seems to be working fine... My Download Mode screen is exactly the same, including the "Security checking failed GT_CONNECT_FAIL"
Although I have this tiny itch to format my data through TWRP at some point and do a "fresh" install/ROM flash to be sure there isn't a hidden issue. Am I good? Seems like it's not quite perfect yet.
Thanks for your help.
WutUpCuuuz said:
(My Download Mode screen while stuck in boot-loop)
*** UNLOCKED ***
htc_pmewh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.42.651.6
Jan 18 2017, 11:10:08(857212)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security checking failed GT_CONNECT_FAIL
Security Warning
Bla bla bla
SD MOUNTED
OTG NOT MOUNTED
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
So, I had Viper10 5.9 with TWRP, Magisk, and SuperSu but somehow messed with one of my color settings and just couldn't figure out how to fix it, this went on for weeks... so I decided to restore it and reflash the ROM. Somewhere in that process S-OFF went to S-ON, I believe, not sure if it makes a difference but from all the searching I've done trying to figure this out it seems like a big deal. Anyway, I can tell you this...
1) When I tried to format data through TWRP before it said something like "failed to mount bla bla bla device is busy or in use" (maybe something to do with encryption? or root? maybe not having root anymore since I had uninstalled SuperSu?
2) Now when I try to format data through TWRP it acts as if everything is fine and then I reboot and I'm stuck in a never-ending boot loop again
3) When I try to flash my firmware zip (which I got from here) in Download Mode I get
"22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
4) When I try to ADB sideload through TWRP it says the zip file is corrupt
5) When I try the HTC RUU (while in Download Mode) it never gets past the first screen where InstallShield or whatever is setting up
6) I just flashed Viper10 5.9 through TWRP and it worked all of a sudden (wasn't working before, while stuck in the loop)... I went with Magisk and MagiskSu this time to avoid a future conflict (not that I now what I'm doing or anything)
So I'm wondering if I'm okay... I'm still S-ON (I thought it went S-OFF when rooted?) and everything seems to be working fine... My Download Mode screen is exactly the same, including the "Security checking failed GT_CONNECT_FAIL"
Although I have this tiny itch to format my data through TWRP at some point and do a "fresh" install/ROM flash to be sure there isn't a hidden issue. Am I good? Seems like it's not quite perfect yet.
Thanks for your help.
Click to expand...
Click to collapse
Update: Since re-flashing Viper I haven't had any issues, although I haven't tried anything in depth. I still wonder about it not wanting to format data in TWRP before (remembering that it said it couldn't do something with /data).
Is there a way I can still format my device and get it back to stock, S-OFF and locked so I can start from scratch? The /data thing and the GT_CONNECT_FAIL are bothering me. Or, if there's a better route I should go I'm definitely open to suggestions.
Sent from my 2PS64 using Tapatalk
WutUpCuuuz said:
Update: Since re-flashing Viper I haven't had any issues, although I haven't tried anything in depth. I still wonder about it not wanting to format data in TWRP before (remembering that it said it couldn't do something with /data).
Is there a way I can still format my device and get it back to stock, S-OFF and locked so I can start from scratch? The /data thing and the GT_CONNECT_FAIL are bothering me. Or, if there's a better route I should go I'm definitely open to suggestions.
Click to expand...
Click to collapse
Put an ruu on an SD card and run that. Will take you back to complete stock and remove everything from the phone.
Also, regarding s-off, it's not clear if you ever had s-off to begin with. You had previously paid for it via sunshine??
Tarima said:
Put an ruu on an SD card and run that. Will take you back to complete stock and remove everything from the phone.
Also, regarding s-off, it's not clear if you ever had s-off to begin with. You had previously paid for it via sunshine??
Click to expand...
Click to collapse
I'm not exactly sure either... maybe I'm just imagining it. Looked into Sunshine but have yet to pump the trigger on it.
At one point I had found an RUU zip, put it on the SD, and renamed it to 2PS6IMG.zip, but it wouldn't run. I'll try again. Think I could use one of HTC's RUU executables? (that might be a dumb question [emoji6])
Thanks for your help
Sent from my 2PS64 using Tapatalk
WutUpCuuuz said:
I'm not exactly sure either... maybe I'm just imagining it. Looked into Sunshine but have yet to pump the trigger on it.
At one point I had found an RUU zip, put it on the SD, and renamed it to 2PS6IMG.zip, but it wouldn't run. I'll try again. Think I could use one of HTC's RUU executables? (that might be a dumb question [emoji6])
Thanks for your help
Click to expand...
Click to collapse
If you're not sure you ever had s-off, then you didn't have it. S-off is a separate procedure, not be confused with bootloader unlocking or rooting.
If the ruu didn't run, most likely you tried one made for another mid/cid, or the software version was older than what you had already on your phone. Make sure both of these are corrected and report back if it works. And yes the ruu.exe would work, but the two points I just mentioned need to be taken into account.
Double checked that it was the correct RUU... still correct as far as I can tell. Rebooted to download mode, didn't see it on the SD. Renamed the RUU to 2PS6IMG.exe, still didn't see it. ??? I'm stuck, my PC isn't here with me so I can't try it that way.
Related
Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse
master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....
master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse
master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse
master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse
master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse
master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!
Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.
Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.
That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.
Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?
double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...
I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?
double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.
double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe
Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.
This is pretty much my first time doing such things in my phone. I rooted my phone and installed ARHD 11.2 without any trouble following the instructions. When ARHD released 21.0, I tried flashing the ROM but my WiFi stopped working which I did my research and found out that it requires a firmware update (3.28.xxxx) to work. So I tried FireWater which didn't work for some reason and bought SunShine which work out as expected and my M8 is now S-OFF & set my CID to 11111111.
Now, here comes the problem. I flashed 3.2.8.401.7 firmware downloaded from ARHD blog and it returns a SUCCESSFUL but with an ERROR 90, which I also did search and said that I just have to flash the firmware again without reboot in between. Now when I boot up my phone, it's stuck on the HTC Logo with an android text below it and doesn't boot up. I went into the bootloader and tried going into recovery but it went to a black screen with and phone with a red triangle and exclamation mark in between. I erased the cache with fastboot erase cache but still didn't work. Also, I noticed that on the top of my bootloader, it says "*** Software status: Modified ***". I don't know if that is supposed to be there. I remembered TAMPERED banner was supposed to be there. My M8 is unlocked as well.
TWRP 2.8.1.0
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
I followed this guide: VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
EDIT: Solved thanks to lukes91
Solution: Flash custom recovery and then flash ROM via ext_sd and you should be good to go.
Serenity13 said:
This is pretty much my first time doing such things in my phone. I rooted my phone and installed ARHD 11.2 without any trouble following the instructions. When ARHD released 21.0, I tried flashing the ROM but my WiFi stopped working which I did my research and found out that it requires a firmware update (3.28.xxxx) to work. So I tried FireWater which didn't work for some reason and bought SunShine which work out as expected and my M8 is now S-OFF & set my CID to 11111111.
Now, here comes the problem. I flashed 3.2.8.401.7 firmware downloaded from ARHD blog and it returns a SUCCESSFUL but with an ERROR 90, which I also did search and said that I just have to flash the firmware again without reboot in between. Now when I boot up my phone, it's stuck on the HTC Logo with an android text below it and doesn't boot up. I went into the bootloader and tried going into recovery but it went to a black screen with and phone with a red triangle and exclamation mark in between. I erased the cache with fastboot erase cache but still didn't work. Also, I noticed that on the top of my bootloader, it says "*** Software status: Modified ***". I don't know if that is supposed to be there. I remembered TAMPERED banner was supposed to be there. My M8 is unlocked as well.
TWRP 2.8.1.0
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
I followed this guide: VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Click to expand...
Click to collapse
it looks like you still have stock recovery... flash a custom one and try to boot, but you might need to reflash the rom... let me know
lukes91 said:
it looks like you still have stock recovery... flash a custom one and try to boot, but you might need to reflash the rom... let me know
Click to expand...
Click to collapse
Thanks lukes91, I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware. I'll give it a try and update this post.
edit: I'm afraid that for some odd reason. I can't get my phone connected with ADB. It's just says device not found when bootloader says FASTBOOT USB. I reinstalled the drivers from HTC Sync and tried it with HTC Sync installed and uninstalled but I still can't get it to work. I'm plugged into USB 2.0 port.
edit2: I tried plugging in my phone while it's stucked on the HTC logo. My computer detects the Phone and opens up the Internal Storage from my Computer. I have bunch of folders inside which is empty and about 0.3GB storage are used. I'm afraid that it might have to do with the USB Debugging option is off which I do not know how to get it on in bootloader.
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Serenity13 said:
Thanks lukes91, I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware. I'll give it a try and update this post.
edit: I'm afraid that for some odd reason. I can't get my phone connected with ADB. It's just says device not found when bootloader says FASTBOOT USB. I reinstalled the drivers from HTC Sync and tried it with HTC Sync installed and uninstalled but I still can't get it to work. I'm plugged into USB 2.0 port.
edit2: I tried plugging in my phone while it's stucked on the HTC logo. My computer detects the Phone and opens up the Internal Storage from my Computer. I have bunch of folders inside which is empty and about 0.3GB storage are used. I'm afraid that it might have to do with the USB Debugging option is off which I do not know how to get it on in bootloader.
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Click to expand...
Click to collapse
put the rom zip inside ext_sd and flash from there
it's the easiest way...
lukes91 said:
put the rom zip inside ext_sd and flash from there
it's the easiest way...
Click to expand...
Click to collapse
Best answer :good:
lukes91 said:
put the rom zip inside ext_sd and flash from there
it's the easiest way...
Click to expand...
Click to collapse
Alright I'll give it a try. I did try it and placed it in the internal storage but the file went missing after I rebooted into recovery. I'll try your directory instead and give a reply asap.
I actually felt embarrassed on that and my stupidity lol.
edit: Thanks very much! I flashed ARHD 21.1 and now it worked. Now I feel more embarrassed after the ext_sd incident...that actually works.
Serenity13 said:
Alright I'll give it a try. I did try it and placed it in the internal storage but the file went missing after I rebooted into recovery. I'll try your directory instead and give a reply asap.
I actually felt embarrassed on that and my stupidity lol.
edit: Thanks very much! I flashed ARHD 21.1 and now it worked. Now I feel more embarrassed after the ext_sd incident...that actually works.
Click to expand...
Click to collapse
Great! Glad i helped
Sent from here
Serenity13 said:
I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware.
Click to expand...
Click to collapse
If the firmware zip contains stock recovery, of course its going to overwrite TWRP with stock recovery. Sometimes, folks here will intentionally remove stock recovery from the firmware zip (for the express purpose of preventing custom recovery from being wiped when flashing the firmware). But as it comes with an OTA, it will contain stock recovery.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
Serenity13 said:
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Click to expand...
Click to collapse
I know you solved your issue another way. But the adb syntax needs to contain the actual file name, in place of "rom.zip" (with no quotes). This is assuming from the error message that you did not actually rename the file to "rom.zip"(which is another way to do it).
redpoint73 said:
If the firmware zip contains stock recovery, of course its going to overwrite TWRP with stock recovery. Sometimes, folks here will intentionally remove stock recovery from the firmware zip (for the express purpose of preventing custom recovery from being wiped when flashing the firmware). But as it comes with an OTA, it will contain stock recovery.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
I know you solved your issue another way. But the adb syntax needs to contain the actual file name, in place of "rom.zip" (with no quotes). This is assuming from the error message that you did not actually rename the file to "rom.zip"(which is another way to do it).
Click to expand...
Click to collapse
Well I did rename the original name(Android_Revolution_HD-One_M8_21.1.zip) to rom.zip since it's way long and it didn't work the first time I entered adb side load Android_Revolution_HD-One_M8_21.1.zip. I renamed to rom.zip just to see whether if it works but I still received the same error. It could be something wrong with the ADB Sideload. It got stuck at "Starting ADB Sideload feature..." but "adb devices" listed the device with sideload tag on it. Thanks to lukes91, the method he posted above, which was the most simplest method that I should have done at the first place works perfectly.
Serenity13 said:
It could be something wrong with the ADB Sideload.
Click to expand...
Click to collapse
Could be, I've found adb sideload to be finicky, and adb push to be more reliable. Although sideload is good to have in your bag of tricks "just in case". And of course the method you eventually used (putting it on the removable SD) works, as well.
The other common cause for the error message "cannot read file" is that the file is accidentally named rom.zip.zip due to the user not realizing they have the Windows option selected to hide file extensions (and erroneously adding ".zip" to the file name). But as you loaded and flashed the file successfully by putting it on the removable SD, this likely is not the case either.
You had the ROM zip in the same folder as your adb executable, right (when trying to sideload)? An obvious thing, probably. But just asking, since its sometimes the seemingly obvious things that trip us up.
redpoint73 said:
Could be, I've found adb sideload to be finicky, and adb push to be more reliable. Although sideload is good to have in your bag of tricks "just in case". And of course the method you eventually used (putting it on the removable SD) works, as well.
The other common cause for the error message "cannot read file" is that the file is accidentally named rom.zip.zip due to the user not realizing they have the Windows option selected to hide file extensions (and erroneously adding ".zip" to the file name). But as you loaded and flashed the file successfully by putting it on the removable SD, this likely is not the case either.
You had the ROM zip in the same folder as your adb executable, right (when trying to sideload)? An obvious thing, probably. But just asking, since its sometimes the seemingly obvious things that trip us up.
Click to expand...
Click to collapse
Yep I had the ROM zip at the same folder as the adb executable. I did tried both rom.zip and rom.zip.zip in case it was the extension setting mistake. Still it was a happy ending. I got my firmware and ARHD updated. It feels so good to be updated. :good:
Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53
stormsight said:
Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53
Click to expand...
Click to collapse
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
If not we turn our attention to your hboot. The error is because it is not updated enough to have that command. So we have two choices here. You can either upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom. Or you could create a Goldcard, flash a ruu that has the same hboot as the one you have. This should fix your rom and enable the phone to boot again.
In any event you will need to extract the rom.zip from whichever ruu you choose. To do that have a quick google search for a guide but its easy enough. After that rename the rom.zip to PC49img.zip and place it onto your sdcard, boot into hboot and allow it to flash it. The golcard process should be covered in one of my downgrade threads or one of the others from this forum.
Post back here if your having and trouble or need a hand
heavy_metal_man said:
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
Click to expand...
Click to collapse
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
heavy_metal_man said:
You can upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom.
Click to expand...
Click to collapse
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
heavy_metal_man said:
Or you could create a Goldcard
Click to expand...
Click to collapse
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?
stormsight said:
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?
Click to expand...
Click to collapse
All usb debugging is for is so that adb can reboot the device to hboot. If you google for how to extract the rom.zip from the ruu and then put it on the sdcard (after renaming it to PC49IMG.zip) and boot to hboot it is the same thing. Just without usb debugging needed.
You will need a micro sdcard adapter pal.
alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
stormsight said:
alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse
good stuff pal.
when you are in clockworkmod recovery the controls are different. use the trackball to scroll and select. power button is now the back button.
I would recommend this custom rom as it is stable and has a stock vibe to it. just follow its install instructions and you should be good to go
Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..
stormsight said:
Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..
Click to expand...
Click to collapse
That suck man.
Hmmm. Slow boot times are normal on this phone to a certain degree. Usually 20secs to 3 minutes at first boot aftet rom flash.
Once the phone has booted up does the trackball still work? Could just be a damaged digitizer. They are fairly cheap these days. Look here http://m.ebay.co.uk/itm/281644653982 and here http://m.ebay.co.uk/itm/281644653982 fairly straight forward to install, but you could buy a used version of the phone for £30 minimum so its up to you
Edit: although, on reflection 15 boot time and constant reboots are not a good sign. I was hoping it was a software issue. If the trackball is functional you could go into settings, enable usb debugging and then get a logcat. That would at least give us somewhere to work from :-/
the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD
stormsight said:
the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD
Click to expand...
Click to collapse
Lol! Well at least thats a plus :-/ theres not much else we can do here. We could try to enable usb debugging fron within clockworkmod by editing the build.prop and see if we can get a logcat but if the phones just locking up we might not even get one :-/
Hello everybody this morning I've encountered something very strange, I woke up and saw a unusual page on my phone that said "Your phone is encrypted" it told me to put in the passcode that is used on the lock screen to DECRYPT my data when I did so the phone without needing any time to think told me that the decrypt of the data was unsuccessful and that the only way is to factory reset
Now the thing is that I have twrp installed so the phone didn't even reboot to recovery it just rebooted and the same page appeared again telling me to input my passcode
What I've attempted to do is to flash the ruu for my device from sd but the phone doesn't see the file
I've tried to flash a different recovery as twrp was unable to mount any partition except the system partition and the SD partition
I will try to flash cm12 from twrp and see how that goes but until then does anyone have any clue of what happened with my device?
Update: twrp cannot boot the system partition either so now I guess I'm officially bricked
Update 2: Looking at bootloader it sees the ruu on the sd but skips it as it says "No image or wrong image!" under each one except 0PKVIMG.zip
Anyone?
I think you can run RUU only from pc, might be wrong tho as I've run only 1 RUU in my life
Have you tried restoring a backup of your current rom? If you don't have one you can also try one from here (read instruction tho, as you need to same cid as your phone)
Can you use the phone at all? Like go past the pin screen? In settings > security you can disable it (i think its there)
Edit: This has happened before
Hi,
it has recently happened to my mom's phone as well. I can't boot into recovery. It just boots straight to the OS and asks for the encryption key. I've tried to reload the stock recovery image, but it failed with wrong signature message. I've also tried unlocking the bootloader with my htcdev bin file, but it doesn't work anymore. I've tried the RUU that I previously used to go back to stock, but it fails with wrong signature as well. It appears the phone is completely bricked. BTW, The phone was relocked, S-On and with stock recovery.
I'm afraid this is a new ransomware, because before that happened my mom said something about message asking her to make a payment to unlock the phone... Is it possible those dbags were able to swap the certificate?