Hello,
I tried to unlock the bootloader of my HTC Desire 816 Dual SIM, but the last step does not occur; that is, the page that should appear on the phone's screen and ask me to choose Yes or No (the page you see in the first attachment below), does not appear on my screen.
1. What is wrong?
2. Please help me to unlock the bootloader.
(Some points about the conditions my phone is in:
1. does not boot normally,
2. boots directly into Fastboot page,
3. in fastboot page I can select and enter Hboot page,
4. in Hboot menu, when I select Recovery, or Factory Reset, it only returns to Fastboot page.
5. as the attachment shows, the OS- is blank)
If you connect your phone to pc and select Fastboot, is Fastboot usb written at the top? Does your pc recognize the phone?
Have you tried flashing your original RUU?
For flashing RUU bootloader won't need to be unlocked. Just place your RUU zip on sd-card and it should flash the file on its own.
nukaru said:
If you connect your phone to pc and select Fastboot, is Fastboot usb written at the top? Does your pc recognize the phone?
Have you tried flashing your original RUU?
For flashing RUU bootloader won't need to be unlocked. Just place your RUU zip on sd-card and it should flash the file on its own.
Click to expand...
Click to collapse
1. Yes FASTBOOT USB is written at the top
2. I have installed HTC Sync Manager; when I connect the phone, HTC Sync Manager starts but it says "no device connected". I think this is because the phone is not in normal mode but in fastboot mode.
3. I downloaded an "0P9CIMG_A5_DUG,... 2.34.401.2..." zip and put it in sdcard; it started to update but at the stage [1] BOOTLOADER, -FAIL-PU appeared and at the bottom of the page "Device halted due to Large Image". (see attachment)
Now I want to download "RUU_A5_DUG,... 2.34.401.1...exe" and I will try it. But before downloading, Let me ask the following question:
If 'adb devices' command won't work even if FASTBOOT USB is written on the phone, what does this mean?
(4. Please use "Reply" button in response to my post in order that I get a notification)
Dr.Ghobar said:
1. Yes FASTBOOT USB is written at the top
2. I have installed HTC Sync Manager; when I connect the phone, HTC Sync Manager starts but it says "no device connected". I think this is because the phone is not in normal mode but in fastboot mode.
3. I downloaded an "0P9CIMG_A5_DUG,... 2.34.401.2..." zip and put it in sdcard; it started to update but at the stage [1] BOOTLOADER, -FAIL-PU appeared and at the bottom of the page "Device halted due to Large Image". (see attachment)
Now I want to download "RUU_A5_DUG,... 2.34.401.1...exe" and I will try it. But before downloading, Let me ask the following question:
If 'adb devices' command won't work even if FASTBOOT USB is written on the phone, what does this mean?
(4. Please use "Reply" button in response to my post in order that I get a notification)
Click to expand...
Click to collapse
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/
Plz select another ruu from the link
If the command adb devices doesn't work, it's most likely not the snapdragon version. then the whole flashing process is completely different and most ruus you'll find won't work.
ajeshmanu said:
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/
Plz select another ruu from the link
Click to expand...
Click to collapse
I have seen the link you gave. it does not contain A5_DUG, 401. it only contains 1402.
nukaru said:
If the command adb devices doesn't work, it's most likely not the snapdragon version. then the whole flashing process is completely different and most ruus you'll find won't work.
Click to expand...
Click to collapse
My procssor kind is: Quad-core 1.6 GHz Cortex-A7
The picture of the result of "adb devices" command I have attached.
1. You said "whole flashing process is completely different".
How is the flashing process for non-snapdragon version?
2. You said "most ruus you'll find won't work".
a. Do you know why? b. What kind of RUU might work for non-snapdragon version?
Dr.Ghobar said:
My procssor kind is: Quad-core 1.6 GHz Cortex-A7
1. You said "whole flashing process is completely different".
How is the flashing process for non-snapdragon version?
2. You said "most ruus you'll find won't work".
a. Do you know why? b. What kind of RUU might work for non-snapdragon version?
Click to expand...
Click to collapse
Sorry, I've had issues with my own phone the last few days( bad flash) and have been working to get it back to normal.
1. If you had the Mediatek processor like the 816g you would have to use the MTK toolkit to flash roms to your phone. Your device has a Snapdragon processor so that's not an issue. Nukaru was just saying if your phone wasn't responding to fastboot command then it might not be a Snapdragon but it is so your fine there.
2. No RUU you find will work unless it is the "exact" file for your version. These are signed files from the phone carrier/manufacture and they check your bootloader for the CID/version ID before allowing any rom to flash. Also trying to flash an older version of your rom than the one that was previously on the phone won't work. You can only flash either the last firmware version(401.2) or a newer version if available.
Your problem is twofold. Your phone's firmware is not readily available on the net and your OS seems to be either missing or corrupted with an unlockable bootloader. Unless you can either find or get your phone's carrier to find and give you the stock firmware zip/RUU so that you can restore your rom things aren't looking good and I don't ever like saying that trust me. Contact your carrier and request access to a flashable zip/RUU of your current rom. You haven't modified or changed anything on your phone so what can it hurt to ask? That's the best advice I've got without being able to unlock your bootloader.
Can my phone's lacking a ROM be the cause of non-appearance of "Yes or No" page (described in original post)?
Okay, was saving this for last. Please only post yes or no answers.
1. Are you a 100% sure your phone wasn't tampered with? Was the sealing intakt when you bought it?
2. Have you ever send your device to HTC to get it repaired?
3. Have you tried flashing another RUU before the error first popped up?
4. Did your device lag after you updated to lollipop?
5. Was this (drained battery) the first reboot after OTA update?
6. Have you installed all drivers correctly? HTC, java and adb? If you're not sure, try installing them again. After that try adb command again.
6. In which region did you buy this phone? Is it an Indian dual SIM version?
Dr.Ghobar said:
Can my phone's lacking a ROM be the cause of non-appearance of "Yes or No" page (described in original post)?
Click to expand...
Click to collapse
Probably yes.
nukaru said:
Okay, was saving this for last. Please only post yes or no answers.
1. Are you a 100% sure your phone wasn't tampered with? Was the sealing intakt when you bought it?
2. Have you ever send your device to HTC to get it repaired?
3. Have you tried flashing another RUU before the error first popped up?
4. Did your device lag after you updated to lollipop?
5. Was this (drained battery) the first reboot after OTA update?
6. Have you installed all drivers correctly? HTC, java and adb? If you're not sure, try installing them again. After that try adb command again.
6. In which region did you buy this phone? Is it an Indian dual SIM version?
Click to expand...
Click to collapse
1. Yes. I am sure. because it was sealed.
2. Yes.
3. No. I have tried only one 0P9CIMG.zip and got "Device halted due to Large Image".
4. I am not sure. It worked a long time with 5.0.2 before the problem.
5. No.
6. java and adb are good. I have installed HTC Sync Manager successfully and when I connect the phone to PC, HTC Sync Manager starts but cannot recognize the device.
7 (actully). It has been bought from Iran. HTC middle east chat, told me that its Carrier is "Paratel FZE" which is in United Arab Emirates.
Is there a method(s) or tool(s) for unlocking HTC Desire 816 Dual SIM which has no need to agreement from the user?
Dr.Ghobar said:
Is there a method(s) or tool(s) for unlocking HTC Desire 816 Dual SIM which has no need to agreement from the user?
Click to expand...
Click to collapse
There's S off using the Sunshine app but you need to be rooted first and that means unlocking your bootloader thru HTCDEV first to root it then re locking your bootloader before running the Sunshine app which then unlocks it again. So basically the answer is no. Sorry.
1. Is it possible to flash bootloader?
2. My 0P9CIMG.zip fails at the stage "[1] BOOTLOADER". (look at attachment)
Why it stops at this particular stage?
Dr.Ghobar said:
1. Is it possible to flash bootloader?
2. My 0P9CIMG.zip fails at the stage "[1] BOOTLOADER". (look at attachment)
Why it stops at this particular stage?
Click to expand...
Click to collapse
1. Not unless your bootloader is first unlocked and the phone is rooted and you have the proper bootloader image to flash
2. Are you using an SD card that is formatted fat32( 32gb/64gb?) The larger 128gb cards are formatted exfat I believe. The file your trying to flash was never unzipped after download correct? If your transferring the file to your phone via your USB from your computer you might try using an SD card reader and remove your card and put it in the reader and transfer it from your computer to your card that way to ensure it got transferred ok(not corrupted in the MTP transfer.)
nukaru said:
Okay, was saving this for last. Please only post yes or no answers.
1. Are you a 100% sure your phone wasn't tampered with? Was the sealing intakt when you bought it?
2. Have you ever send your device to HTC to get it repaired?
3. Have you tried flashing another RUU before the error first popped up?
4. Did your device lag after you updated to lollipop?
5. Was this (drained battery) the first reboot after OTA update?
6. Have you installed all drivers correctly? HTC, java and adb? If you're not sure, try installing them again. After that try adb command again.
6. In which region did you buy this phone? Is it an Indian dual SIM version?
Click to expand...
Click to collapse
thoctor said:
1. Not unless your bootloader is first unlocked and the phone is rooted and you have the proper bootloader image to flash
2. Are you using an SD card that is formatted fat32( 32gb/64gb?) The larger 128gb cards are formatted exfat I believe. The file your trying to flash was never unzipped after download correct? If your transferring the file to your phone via your USB from your computer you might try using an SD card reader and remove your card and put it in the reader and transfer it from your computer to your card that way to ensure it got transferred ok(not corrupted in the MTP transfer.)
Click to expand...
Click to collapse
I think the bootloader of my device is ill or damaged, because rom zips or ruu.exe's stop just at bootloader stage.
How can I fix bootloader?
Dr.Ghobar said:
I think the bootloader of my device is ill or damaged, because rom zips or ruu.exe's stop just at bootloader stage.
How can I fix bootloader?
Click to expand...
Click to collapse
It's probably not because you've had no access to it as it is still locked. Even if it was damaged it can't be flashed over unless its unlocked and you'd need the correct bootloader image and that might be hard to find. Might be getting close to the time to consider getting another phone as your operating system is gone or damaged and can't find the correct ffirmware to flash back.
thoctor said:
It's probably not because you've had no access to it as it is still locked. Even if it was damaged it can't be flashed over unless its unlocked and you'd need the correct bootloader image and that might be hard to find. Might be getting close to the time to consider getting another phone as your operating system is gone or damaged and can't find the correct ffirmware to flash back.
Click to expand...
Click to collapse
I have found the correct ruu.exe. The problem is that when the ruu.exe reaches the stage of "Rebooting to bootloader.........." (attachment 1) and sends the command to the phone, the phone is so slow in booting to bootloader that ruu.exe stops and says usb connection error.
I extracted rom.zip from ruu.exe.
Should I rename "rom.zip" to "0P9CIMG.zip" before putting it in sdcard?
Related
Hey guys,
My friend has an HTC Desire 820G+ Dual Sim. It was running Android v 4.x (not sure what version exactly), was on a stock ROM, locked bootloader, and stock recovery, with USB Debugging disabled.
He was performing an OTA update to Lollipop, and after it downloaded (i.e. while installing), it gave an error message (he doesn't recall what it was exactly). It is now stuck at the HTC boot logo. (I think this is called soft brick?)
I can access the phone's recovery menu via Power + Volume Down.
Here's what I have tried to do to fix it:
1. Go to HTCdev and look for stock firmware to install on the phone, by means of copying the downloaded files onto the SD card (the recovery menu has an option to install files from SD card)
The problem with this is that I have found four different downloads for Lollipop, all having the same carrier (hTC Asia), version (5.0.2), region (TW), and kernel (3.10.61) but different "description" (e.g. 1.01.709.8) and "type" (CRC vs MR1).
I was desperate after I tried to look for alternative solutions, including the one outlined below, so I tried to install the .zip files (downloaded all of them), but not one of them would install.
2. Unlock the device's bootloader, install custom recovery, and flash a custom ROM.
The problems with this are:
a. The device has USB debugging disabled. I tried to look around for methods to enable it, and I will continue trying to do so tonight. Please let me know if you know how I can do this.
b. I could not find a TWRP image for the Desire 820. I tried to access the CWM website, but it is (for some unknown reason) blocked in my university, so I will try to look there again tonight.
c. I couldn't find a custom ROM for the Desire 820G+. I could find ones for the 820S and 820N -- can I install them?
d. The phone isn't detected anymore when I run adb devices or fastboot devices. I managed to get it to be detected as "sideload" once, but never again.
To summarize:
1. Phone is HTC Desire 820 G+ Dual Sim.
2. Stock ROM, no root, locked bootloader, and disabled USB Debugging.
3. Phone is stuck on HTC boot logo, but I can access recovery mode.
4. Phone doesn't show in cmd when I run "adb devices" or "fastboot devices" (I know that drivers were installed properly because it worked once earlier).
Let me know what I should do.
Thanks in advance.
ahe25 said:
Hey guys,
My friend has an HTC Desire 820G+ Dual Sim. It was running Android v 4.x (not sure what version exactly), was on a stock ROM, locked bootloader, and stock recovery, with USB Debugging disabled.
He was performing an OTA update to Lollipop, and after it downloaded (i.e. while installing), it gave an error message (he doesn't recall what it was exactly). It is now stuck at the HTC boot logo. (I think this is called soft brick?)
I can access the phone's recovery menu via Power + Volume Down.
Here's what I have tried to do to fix it:
1. Go to HTCdev and look for stock firmware to install on the phone, by means of copying the downloaded files onto the SD card (the recovery menu has an option to install files from SD card)
The problem with this is that I have found four different downloads for Lollipop, all having the same carrier (hTC Asia), version (5.0.2), region (TW), and kernel (3.10.61) but different "description" (e.g. 1.01.709.8) and "type" (CRC vs MR1).
I was desperate after I tried to look for alternative solutions, including the one outlined below, so I tried to install the .zip files (downloaded all of them), but not one of them would install.
2. Unlock the device's bootloader, install custom recovery, and flash a custom ROM.
The problems with this are:
a. The device has USB debugging disabled. I tried to look around for methods to enable it, and I will continue trying to do so tonight. Please let me know if you know how I can do this.
b. I could not find a TWRP image for the Desire 820. I tried to access the CWM website, but it is (for some unknown reason) blocked in my university, so I will try to look there again tonight.
c. I couldn't find a custom ROM for the Desire 820G+. I could find ones for the 820S and 820N -- can I install them?
d. The phone isn't detected anymore when I run adb devices or fastboot devices. I managed to get it to be detected as "sideload" once, but never again.
To summarize:
1. Phone is HTC Desire 820 G+ Dual Sim.
2. Stock ROM, no root, locked bootloader, and disabled USB Debugging.
3. Phone is stuck on HTC boot logo, but I can access recovery mode.
4. Phone doesn't show in cmd when I run "adb devices" or "fastboot devices" (I know that drivers were installed properly because it worked once earlier).
Let me know what I should do.
Thanks in advance.
Click to expand...
Click to collapse
No don't ever flash Desire 820u, 820n or 820s files on 820G+, they are different hardware.
Was the device rooted before installing the OTA?
Gibz97 said:
No don't ever flash Desire 820u, 820n or 820s files on 820G+, they are different hardware.
Was the device rooted before installing the OTA?
Click to expand...
Click to collapse
Alright, noted. Thanks.
And no, the phone has never been rooted. I have no idea how it got bricked.
ahe25 said:
Alright, noted. Thanks.
And no, the phone has never been rooted. I have no idea how it got bricked.
Click to expand...
Click to collapse
Here is the stock firmware for 820G+ which you can flash with SP Flash Tool:
http://easy-firmware.com/index.php?a=browse&b=category&id=2696
SP Flashtool link:
http://easy-firmware.com/index.php?a=browse&b=category&id=2697
How to flash (This will wipe internal storage)
1. Extract both files
2. Open SP Flashtool folder and run flash_tool as administrator
3. Click on scatter loading and navigate to HTC-Desire-820G-PLUS-dual-sim folder and choose MT6592_Android_scatter
4. Select all items except preloader
5. Click on Download
6. Switch off phone and connect it to PC using a USB cable
7. Wait for flashing to end, then disconnect USB cable and switch on phone
Have the same problem. I have tried to install the stock ROM with SP flash... But nothing happens. My phone is also desire 820g+ dual sim grey.
When I start the flash tool and choose the scatter than click download, switch the phone off to connect to PC via USB cable after this procedure nothing happens.
Waiting and waiting.
The USB cable is the original one.
What I'm doing wrong? Give answer as soon as possible.
SUİ3JECT-X said:
Have the same problem. I have tried to install the stock ROM with SP flash... But nothing happens. My phone is also desire 820g+ dual sim grey.
When I start the flash tool and choose the scatter than click download, switch the phone off to connect to PC via USB cable after this procedure nothing happens.
Waiting and waiting.
The USB cable is the original one.
What I'm doing wrong? Give answer as soon as possible.
Click to expand...
Click to collapse
Try other SP Flash Tool versions from this link, at least one should work
https://androidmtk.com/smart-phone-flash-tool
Didn't work.
Same Problem. Didn't Work. I also used SP_Flash_Tool_v5.1604.
But same problem
Nothing Flashed.
Gibz97 said:
Here is the stock firmware for 820G+ which you can flash with SP Flash Tool:
http://easy-firmware.com/index.php?a=browse&b=category&id=2696
SP Flashtool link:
http://easy-firmware.com/index.php?a=browse&b=category&id=2697
How to flash (This will wipe internal storage)
1. Extract both files
2. Open SP Flashtool folder and run flash_tool as administrator
3. Click on scatter loading and navigate to HTC-Desire-820G-PLUS-dual-sim folder and choose MT6592_Android_scatter
4. Select all items except preloader
5. Click on Download
6. Switch off phone and connect it to PC using a USB cable
7. Wait for flashing to end, then disconnect USB cable and switch on phone
Click to expand...
Click to collapse
You correctly install the driver on the Bootloader? Open Device Manager and plug the off-phone if there is an unknown device and disappears, so do not set the driver.
Furious-85 said:
You correctly install the driver on the Bootloader? Open Device Manager and plug the off-phone if there is an unknown device and disappears, so do not set the driver.
Click to expand...
Click to collapse
As he says. Follow the tutorial in this link to install the MediaTek USB drivers:
https://forum.hovatek.com/thread-440.html
I am more than sure that it is not properly installed driver for the bootloader, so Flash Tool can not pick him.
In the all critical condition phones on MTK flashing without any problems. The main thing that was a working memory and a connector.
Upload a photo where we can see that the drivers are installed on the bootloader. The device only a two - three seconds is displayed in the manager, then turns off.
Very often, the drivers are installed crooked, it is necessary to clean and re-deliver them. Very often, drivers are not suitable for the operating system or mobile phone, you have to try others.
Sorry for my English!
Correct MTK VCOM USB Driver Installation!
For those having problems flashing or upgrading with FlashTools, USB connection problems with this phone HTC desire 826G+ or any other Mediatek powered phone, sometimes you have to disable Windows driver signature enforcement (DSE) before installing MTK VCOM USB drivers. Check this post on my blog to properly install MTK drivers and get your phone recognized by the Flashtools program for successful flashing: http://www.selftechgenius.com/andro...-android-5-1-lollipop-latest-official-update/
Jump to the "Installation Process" part.
Hope this helps!:victory:
any update on this?
Recovery(3e) 1.12.401.1→TWRP Recovery2.8.1.0
HTC Desire 820G+ （Android 4.4.2）
1：Download 『HTC Bootloader Unlock 』and install
2：Download 『TWRP_HTC_820G_PLUS.zip(7.672k)』and extract it
（Copy recovery.img put it in adb folder）
3：Turn on mobile and connect to PC with a USB cable，Run HTC Bootloader Unlock to fastboot model
4：On the command prompt, Type:
a：cd C:\adb
b：fastboot flash recovery recovery.img
~~reboot
ahe25 said:
Hey guys,
My friend has an HTC Desire 820G+ Dual Sim. It was running Android v 4.x (not sure what version exactly), was on a stock ROM, locked bootloader, and stock recovery, with USB Debugging disabled.
He was performing an OTA update to Lollipop, and after it downloaded (i.e. while installing), it gave an error message (he doesn't recall what it was exactly). It is now stuck at the HTC boot logo. (I think this is called soft brick?)
I can access the phone's recovery menu via Power + Volume Down.
Here's what I have tried to do to fix it:
1. Go to HTCdev and look for stock firmware to install on the phone, by means of copying the downloaded files onto the SD card (the recovery menu has an option to install files from SD card)
The problem with this is that I have found four different downloads for Lollipop, all having the same carrier (hTC Asia), version (5.0.2), region (TW), and kernel (3.10.61) but different "description" (e.g. 1.01.709.8) and "type" (CRC vs MR1).
I was desperate after I tried to look for alternative solutions, including the one outlined below, so I tried to install the .zip files (downloaded all of them), but not one of them would install.
2. Unlock the device's bootloader, install custom recovery, and flash a custom ROM.
The problems with this are:
a. The device has USB debugging disabled. I tried to look around for methods to enable it, and I will continue trying to do so tonight. Please let me know if you know how I can do this.b. I could not find a TWRP image for the Desire 820. I tried to access the CWM website, but it is (for some unknown reason) blocked in my university, so I will try to look there again tonight.c. I couldn't find a custom ROM for the Desire 820G+. I could find ones for the 820S and 820N -- can I install them?d. The phone isn't detected anymore when I run adb devices or fastboot devices. I managed to get it to be detected as "sideload" once, but never again.
To summarize:
1. Phone is HTC Desire 820 G+ Dual Sim.
2. Stock ROM, no root, locked bootloader, and disabled USB Debugging.
3. Phone is stuck on HTC boot logo, but I can access recovery mode.
4. Phone doesn't show in cmd when I run "adb devices" or "fastboot devices" (I know that drivers were installed properly because it worked once earlier).
Let me know what I should do.
Thanks in advance.
Click to expand...
Click to collapse
any thing new for this position in exact way please?
I have HTC ONE M8 it's definitely bricked, it won't load up stuck on boot screen.
It is S-On
Bootloader unlocked currently(can relock if needed)
HBoot- 3.19.0.0000
Radio- 1.25.21331147A1.06G
OpenDSP- v48.2.2-00564-M8974_FO.1211
Can anyone help me unbrick it? I already tried sideloading roms with no success, not sure about ruu.
Also it's from Rogers.
Thanks
Jackson
justsomegamer97 said:
I have HTC ONE M8 it's definitely bricked, it won't load up stuck on boot screen.
It is S-On
Bootloader unlocked currently(can relock if needed)
HBoot- 3.19.0.0000
Radio- 1.25.21331147A1.06G
OpenDSP- v48.2.2-00564-M8974_FO.1211
Can anyone help me unbrick it? I already tried sideloading roms with no success, not sure about ruu.
Also it's from Rogers.
Thanks
Jackson
Click to expand...
Click to collapse
nvm guys ill just ship it back to htc
justsomegamer97 said:
I have HTC ONE M8 it's definitely bricked, it won't load up stuck on boot screen.
Can anyone help me unbrick it? I already tried sideloading roms with no success,
Click to expand...
Click to collapse
Boot screen coming on, means it almost definitely not a brick.
Sideload is very finicky. More reliable to adb push a ROM, or put ROM on a SD card.
redpoint73 said:
Boot screen coming on, means it almost definitely not a brick.
Sideload is very finicky. More reliable to adb push a ROM, or put ROM on a SD card.
Click to expand...
Click to collapse
Hey, So I tried to adb push a rom doesn't work and when I put a ROM on an SD Card it doesn't recognize anything on the SD Card
justsomegamer97 said:
Hey, So I tried to adb push a rom doesn't work
Click to expand...
Click to collapse
Just saying it "doesn't work" fails to tell me anything about what actually occurred; or any info that would allow me to troubleshoot the issue. Any error messages? Did it hang waiting for device? Any response to command: adb devices
Keep in mind you need to be in recovery for adb to work (not bootloader). Within OS is normally when adb is used, but of course in your case, that isn't an option. But adb also works within TWRP.
Also, what exact command did you use? The syntax is important, as if the destination location is wrong, the command will fail.
Presumably, you have Debugging activated in the phone settings (otherwise, I assume you would not previously be trying to do adb sideload). If not, there isn't a way to turn Debugging on, since the phone won't boot.
adb not working is usually a case of USB connectivity issue, or user error.
justsomegamer97 said:
when I put a ROM on an SD Card it doesn't recognize anything on the SD Card
Click to expand...
Click to collapse
Did you select MicroSD as the storage location on the Install Screen (it may still have Internal Storage selected - common mistake).
Also, in the TWRP "Mount" section, is MicroSD checked? It should be checked by default, but verify that its checked.
redpoint73 said:
Just saying it "doesn't work" fails to tell me anything about what actually occurred; or any info that would allow me to troubleshoot the issue. Any error messages? Did it hang waiting for device? Any response to command: adb devices
Keep in mind you need to be in recovery for adb to work (not bootloader). Within OS is normally when adb is used, but of course in your case, that isn't an option. But adb also works within TWRP.
Also, what exact command did you use? The syntax is important, as if the destination location is wrong, the command will fail.
Presumably, you have Debugging activated in the phone settings (otherwise, I assume you would not previously be trying to do adb sideload). If not, there isn't a way to turn Debugging on, since the phone won't boot.
adb not working is usually a case of USB connectivity issue, or user error.
Did you select MicroSD as the storage location on the Install Screen (it may still have Internal Storage selected - common mistake).
Also, in the TWRP "Mount" section, is MicroSD checked? It should be checked by default, but verify that its checked.
Click to expand...
Click to collapse
Hey so i tried to sideload a stock rom via fastboot oem rebootRUU and the final message is a failed signature check https://gyazo.com/c4ed1ca82faf0ca683c9f861913a2ca0
redpoint73 said:
Just saying it "doesn't work" fails to tell me anything about what actually occurred; or any info that would allow me to troubleshoot the issue. Any error messages? Did it hang waiting for device? Any response to command: adb devices
Keep in mind you need to be in recovery for adb to work (not bootloader). Within OS is normally when adb is used, but of course in your case, that isn't an option. But adb also works within TWRP.
Also, what exact command did you use? The syntax is important, as if the destination location is wrong, the command will fail.
Presumably, you have Debugging activated in the phone settings (otherwise, I assume you would not previously be trying to do adb sideload). If not, there isn't a way to turn Debugging on, since the phone won't boot.
adb not working is usually a case of USB connectivity issue, or user error.
Did you select MicroSD as the storage location on the Install Screen (it may still have Internal Storage selected - common mistake).
Also, in the TWRP "Mount" section, is MicroSD checked? It should be checked by default, but verify that its checked.
Click to expand...
Click to collapse
Hey great news I did not check the microsd in twrp mount section and i was able to install a ruu and went back to stock!
thanks a ton for your help!
Regards,
Jackson L
justsomegamer97 said:
Hey so i tried to sideload a stock rom via fastboot oem rebootRUU and the final message is a failed signature check https://gyazo.com/c4ed1ca82faf0ca683c9f861913a2ca0
Click to expand...
Click to collapse
Glad you sorted it out. But a word of advice, you seem to be using the terms loosely, or maybe not fully understanding them. So I would recommend being a bit more careful with the terms (and being more specific), in order to avoid confusing yourself (or those trying to help you) in the future. The more specific and detailed you are, the easier it is for folks to help you:
1) "stock ROM" is a bit ambiguous. To me a "ROM" usually means something flashable with TWRP. Some folks will call the RUU the "stock ROM" (and that seems to be what you are talking about). But this is very confusing, as the ROM (system or OS partition) is just one of around 41 partitions that are included in the RUU. If you are talking about the RUU specifically, then say "RUU". RUU being either a .exe Windows executable, or zip flashable in fastboot RUU mode.
2) Some folks use the word "sideload" a bit loosely. To me, this means the adb sideload feature in TWRP. Some folks mean this as anything flashed with adb/fastboot (seems to be how you are using the term). But again, the lack of specificity is confusing here. If you mean flash a zip with fastboot, say that. If you mean flash in fasbootRUU mode, say that.
3) You said adb push "didn't work" but never gave any specifics. This command failing is often a case of user error (performed a step incorrectly, or bad command syntax/wrong path). But seeing as you didn't give any details, to me this means you aren't interested in learning how to do it correctly, or learning from your mistakes.
4) The file you tried to flash in the quote above, doesn't seem to be a firmware, nor an RUU. I'm not sure what it is; as you don't give the least bit of specifics of the original file name, source, version number, etc.
Firmware on this device specifically refers to a small firmware.zip package that contains some modules (hboot, radio, WiFi, Bluetooth, several others) for the ROM to work, but does not contain the ROM (system partition) itself. A signed firmware is usually around 40-50 MB. A Sense RUU is over 1 GB, so what you tried to flash here (600 MB) isn't either of these; and I have no idea what it is.
Folks sometimes use the term "firmware" to be synonymous with ROM or RUU. But I would highly recommend not using the term that way, as not to confuse it with the firmware.zip just described in the last paragraph.
Maybe its a Google Play Edition (GPE) RUU (which is smaller than Sense RUU), or some other RUU that has been hacked to remove some things. But its not a stock RUU.
The signature verify fail, means its not a signed official RUU. You can't flash such a file with s-on. Again, this would indicate a hacked/modified RUU.
Hi
This is the first time I'm using a HTC device, before this I had some Nexus devices which were really easy for modification. I'm a little confused with HTC methods.
I'm a GNU/Linux user and I wish to do everything without using Windows. as I see RUU files at least for HTC 10 are .exe files and a Windows machine is needed to flash them. I have found this tool that extracts all the files from RUU file.
1- If I wanna flash exe RUU, can I just download the file from here and run it ? should I consider CID and MID before downloading a RUU file?
2- Considering that I have the right RUU file, can I just use "Universal HTC RUU/ROM Decryption Tool" and make a zip file and flash it?
Use the decrypt tool to get pull the ROM.zip from the RUU.exe, rename the ROM.zip to 2PS6IMG.zip and place that on the root of your sdcard. Boot to download mode and it will find the renamed zip and ask you to press vol up to confirm the flash. When it's done it'll prompt you to press power to reboot.
That's it. Super easy.
After the flash delete the zip or rename it to something else, otherwise every time you boot to download mode, it'll try to update again.
xunholyx said:
Use the decrypt tool to get pull the ROM.zip from the RUU.exe, rename the ROM.zip to 2PS6IMG.zip and place that on the root of your sdcard. Boot to download mode and it will find the renamed zip and ask you to press vol up to confirm the flash. When it's done it'll prompt you to press power to reboot.
That's it. Super easy.
After the flash delete the zip or rename it to something else, otherwise every time you boot to download mode, it'll try to update again.
Click to expand...
Click to collapse
Thank you.
Forgive me if I ask without any testing by myself, My device hasn't been arrived yet. (I'm preparing myself)
Will it wipe anything?
Will it re-encrypt data partition and solve the radio problem? (is flashing the zip exactly like running RUU.exe or it's just something like an OTA upate?)
Will It solve OTA problem? (not being able to receive OTA)
The exact question is
How can I flash the RUU like a factory reset
and how can I flash the RUU like an OTA
(ALL in Linux not Windows)
Thank you so much
Sir-Shadow said:
Hi
This is the first time I'm using a HTC device, before this I had some Nexus devices which were really easy for modification. I'm a little confused with HTC methods.
I'm a GNU/Linux user and I wish to do everything without using Windows. as I see RUU files at least for HTC 10 are .exe files and a Windows machine is needed to flash them. I have found this tool that extracts all the files from RUU file.
1- If I wanna flash exe RUU, can I just download the file from here and run it ? should I consider CID and MID before downloading a RUU file?
2- Considering that I have the right RUU file, can I just use "Universal HTC RUU/ROM Decryption Tool" and make a zip file and flash it?
Click to expand...
Click to collapse
do you not have an sd-card?
why not just use that method?
If you do a full RUU that way, is he going to get a full wipe with radio and firmware update is his question I think, I know it can so that with renaming the zip.
Are you going to s-off your phone first? Have you decided on that yet, because it's a preference but if you use Linux half decent I would recommend s-off with locked bootloader (when it's s-off, its a higher level permission so it works like unlocked but the locked flag is still there)
I'm not really familiar with the RUU method from the beginning, I know there's a lot of options though. My suggestion would be s-off (choose to keep bootloader locked during sunshine process) and then install recovery with fastboot and firmware with fastboot (sneakyghost thread for firmware/radio updates s-off), which works from Linux I believe because I had to learn how to use fastboot and adb with iOS when I remoted in to straighten out a phone on teamviewer. So I think "fastboot reboot oemRUU" method works in Linux, you just do ./ if I remember correctly.
Can some Linux guys help me out?
Sent from my HTC 10 using Tapatalk
andybones said:
do you not have an sd-card?
why not just use that method?
Click to expand...
Click to collapse
I have and I will use, but this is my first time with HTC and I'm still learning the way HTC works.
CharliesTheMan said:
If you do a full RUU that way, is he going to get a full wipe with radio and firmware update is his question I think, I know it can so that with renaming the zip.
Are you going to s-off your phone first? Have you decided on that yet, because it's a preference but if you use Linux half decent I would recommend s-off with locked bootloader (when it's s-off, its a higher level permission so it works like unlocked but the locked flag is still there)
I'm not really familiar with the RUU method from the beginning, I know there's a lot of options though. My suggestion would be s-off (choose to keep bootloader locked during sunshine process) and then install recovery with fastboot and firmware with fastboot (sneakyghost thread for firmware/radio updates s-off), which works from Linux I believe because I had to learn how to use fastboot and adb with iOS when I remoted in to straighten out a phone on teamviewer. So I think "fastboot reboot oemRUU" method works in Linux, you just do ./ if I remember correctly.
Can some Linux guys help me out?
Click to expand...
Click to collapse
I really like to s-off my phone, but as the only way for s-off is Sunshine and I do live in f*ing country, it's not easy for me to pay.
Why do you recommend s-off and keeping bootloader lock? I know s-off is more powerful but why keeping bootloader lock?
Sir-Shadow said:
I have and I will use, but this is my first time with HTC and I'm still learning the way HTC works.
I really like to s-off my phone, but as the only way for s-off is Sunshine and I do live in f*ing country, it's not easy for me to pay.
Why do you recommend s-off and keeping bootloader lock? I know s-off is more powerful but why keeping bootloader lock?
Click to expand...
Click to collapse
The bootloader lock serves no purpose on preventing you from installing things we flash after s off. It's basically a false flag, like a deadbolt on a door but to get in, you can just move the door to the side and walk in.
To unlock bootloader you have to go through HTC and agree to waive your warranty rights. S off unlocks everything, but certain apps looking for a locked bootloader, see a locked bootloader is just a fake sign on the door basically, with benefits to being locked and s off, for apps that require locked bootloaders.
Sent from my HTC 10 using Tapatalk
Sir-Shadow said:
I have and I will use, but this is my first time with HTC and I'm still learning the way HTC works.
I really like to s-off my phone, but as the only way for s-off is Sunshine and I do live in f*ing country, it's not easy for me to pay.
Why do you recommend s-off and keeping bootloader lock? I know s-off is more powerful but why keeping bootloader lock?
Click to expand...
Click to collapse
***On the HTC 10, S-OFF Locked = S-OFF Unlocked (Strange I know, this isn't how it was on previous M9, M8 or M7 etc,,, the HTC 10 is a bit different), Sunshine suggests that you choose S-OFF Locked (you will see this in the disclaimer when you run the application)***
There are several methods to flash RUU (Option 2 isn't viable since you are on Linux, but you still have 2 options) - I don't see why you would have any issues using adb on Linux, but I use Windows mainly, so I've never flashed an RUU on Linux, but I do know that Option 1 (SD-Card) is the safest method, IMO. (No worry of power going out and bricking device or something while it's flashing)
Taken from this thread found here
--------------------------------------------------
Option 1
Copy 2PS6IMG.zip (this is the RUU you rename to 2PS6IMG.zip) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot syst
andybones said:
***On the HTC 10, S-OFF Locked = S-OFF Unlocked (Strange I know, this isn't how it was on previous M9, M8 or M7 etc,,, the HTC 10 is a bit different), Sunshine suggests that you choose S-OFF Locked (you will see this in the disclaimer when you run the application)***
There are several methods to flash RUU (Option 2 isn't viable since you are on Linux, but you still have 2 options) - I don't see why you would have any issues using adb on Linux, but I use Windows mainly, so I've never flashed an RUU on Linux, but I do know that Option 1 (SD-Card) is the safest method, IMO. (No worry of power going out and bricking device or something while it's flashing)
Taken from this thread found here
--------------------------------------------------
Option 1
Copy 2PS6IMG.zip (this is the RUU you rename to 2PS6IMG.zip) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot syst
Click to expand...
Click to collapse
Sir, thank you for this clarification.
Now I'm happy that I can use this device without needing a Windows machine. And I think I have to find a way to S-OFF.
andybones said:
Option 1
Copy 2PS6IMG.zip (this is the RUU you rename to 2PS6IMG.zip) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Click to expand...
Click to collapse
FAT32 isn't needed anymore with the 10. ExFAT works just fine now. :good:
Sir-Shadow said:
Sir, thank you for this clarification.
Now I'm happy that I can use this device without needing a Windows machine. And I think I have to find a way to S-OFF.
Click to expand...
Click to collapse
Sunshine app is the only possible way for most of us to S-OFF our devices.. unless you live somewhere where java cards are prevalent and you are able to find a local business that has java cards and offers S-OFF service.. dunno if that is still a thing or not..
I remember reading that if you ever want to be able to take an OTA, you have to do a RUU flash using the Windows method... that shouldn't be an issue, though. Updates don't really need to be taken over the air, though. They will be available for download very shortly after the OTA.
Hi,
my son's m8 just stopped working, came up with a screen saying something like "illegal use of software....."
It only boots to bootloader. Won't go into recovery, Factory recovery, I've tried a few things but things but fastboot commands won't recognize the phone. The phone does show "fast boot USB" but my PC doesn't seem to recognize the connection.
Phone is original software, locked, S-on, no mods. It does say on the screen "software modified"
Any way around this? I'll upload some screen pics.
Thanks for any advice
Marky_
Marky_ said:
Hi,
my son's m8 just stopped working, came up with a screen saying something like "illegal use of software....."
It only boots to bootloader. Won't go into recovery, Factory recovery, I've tried a few things but things but fastboot commands won't recognize the phone. The phone does show "fast boot USB" but my PC doesn't seem to recognize the connection.
Phone is original software, locked, S-on, no mods. It does say on the screen "software modified"
Any way around this? I'll upload some screen pics.
Thanks for any advice
Marky_
Click to expand...
Click to collapse
Run your device specific RUU via sd card method .
Hit THANKS if somebody help you
hi,
I have "Run your device specific RUU via sd card method . "
I have tried multiple RUU files for my device from a couple of different sources. none worked
see attached pics. fastboot, adb and htc_fastboot won't communicate with my phone either.
any other sources that anyone could recommend that may get this M8 booting again?
regards
Marky_
It's not easy to fix this kind of problem when the correct RUU version is not available and the bootloader is LOCKED
I suggest :
a) Not sure whether this will work as 6.24.841.1 firmware is partial update from 6.12.841.4 but worth a try.
Get the fw_6.24.841.1.zip from my thread : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Since you said your PC is not communicating with your device (which I believe due to lack of HTC USB drivers - you can check in PC Device Manager to make sure), you can install it with microsd method
Rename the fw_6.24.841.1.zip to 0P6BIMG.zip (make sure your PC doesn't have windows extension hidden, it not it may read as 0P6BIMG.zip.zip and won't install)
Put in microsd and go to hboot to update, reboot and see whether it can boot now.
b) if the above fails, you need to try to unlock bootloader thru http://www.htcdev.com/
if it can be unlocked, install TWRP then restore the 6.24.841.1 backup that you can get from my thread linked in my signature.
ckpv5 said:
It's not easy to fix this kind of problem when the correct RUU version is not available and the bootloader is LOCKED
I suggest :
a) Not sure whether this will work as 6.24.841.1 firmware is partial update from 6.12.841.4 but worth a try.
Get the fw_6.24.841.1.zip from my thread : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Since you said your PC is not communicating with your device (which I believe due to lack of HTC USB drivers - you can check in PC Device Manager to make sure), you can install it with microsd method
Rename the fw_6.24.841.1.zip to 0P6BIMG.zip (make sure your PC doesn't have windows extension hidden, it not it may read as 0P6BIMG.zip.zip and won't install)
Put in microsd and go to hboot to update, reboot and see whether it can boot now.
b) if the above fails, you need to try to unlock bootloader thru http://www.htcdev.com/
if it can be unlocked, install TWRP then restore the 6.24.841.1 backup that you can get from my thread linked in my signature.
Click to expand...
Click to collapse
Hi I am back.... doh.
After numerous attempts the above did finally work BUT the phone could not connect to internet or google playstore.
So, I tried the above FW method again, now it just keeps rebooting => HTC screen, optimizing apps then reboots
any other suggestions / links for me to try.
question..... what are the ****diag.zip & ****diag.nbh that HBOOT also looks for when booting to SDcard? Would one of these files be worth a try?
Thanks
Marky_
Marky_ said:
Hi I am back.... doh.
After numerous attempts the above did finally work BUT the phone could not connect to internet or google playstore.
So, I tried the above FW method again, now it just keeps rebooting => HTC screen, optimizing apps then reboots
any other suggestions / links for me to try.
question..... what are the ****diag.zip & ****diag.nbh that HBOOT also looks for when booting to SDcard? Would one of these files be worth a try?
Thanks
Marky_
Click to expand...
Click to collapse
I believe you do have hardware issue. Maybe corrupted data/emmc.
When it was working but no internet .. why didn't you try to unlock bootloader ? It's already out of warranty .. with bootloader unlock, you can try other thing like formatting data partition and restore a non-rooted stock nandroid.
Until now .. I never see a RUU been released for device version.
ckpv5 said:
I believe you do have hardware issue. Maybe corrupted data/emmc.
When it was working but no internet .. why didn't you try to unlock bootloader ? It's already out of warranty .. with bootloader unlock, you can try other thing like formatting data partition and restore a non-rooted stock nandroid.
Until now .. I never see a RUU been released for device version.
Click to expand...
Click to collapse
Hi, I did try to unlock bootloader, when I got the m8 working. yes it is out of warranty
I re-downloaded all files to my PC as HTC Dev asked but the fastbboot service could not recognize the phone. HTC sync was connecting and the phone was showing in my PC but the USB fastboot still would not let me :crying:
so..... without unlocking the bootloader, how do I "try formatting data partition and restore a non-rooted stock nandroid"
thank you
Marky_ said:
Hi, I did try to unlock bootloader, when I got the m8 working.......
I re-downloaded all files to my PC as HTC Dev asked but the fastbboot service could not recognize the phone. HTC sync was connecting and the phone was showing in my PC but the USB fastboot still would not let me :crying: .......
Click to expand...
Click to collapse
fastboot (( service )) only works in fastboot mode ( bootloader ) not while the device booting into android
Marky_ said:
........ without unlocking the bootloader, how do I "try formatting data partition and restore a non-rooted stock nandroid" .....
Click to expand...
Click to collapse
you can't
the only way is the RUU
Good Day, first time posting so here is the huge problem i have.
1 - My power button no longer works
2 - No ROM installed
3 - Vol buttons work
So due to an error on my part i wiped my system , data, delv/cache , and because i was rushing i rebooted the phone before installing the new rom. Now normally i would just boot into recovery and flash a rom, but my power button no longer works. I can get into download mode if the phone dies by holding vol down and plugging into a pc, and such can use fastboot commands, but with no Rom i cant get USB debugging to use "adb reboot recovery" . Is there anyway that i can get into recovery or a way to flash stock recovery, system and such. thanks in advance.
Bloodx32 said:
Good Day, first time posting so here is the huge problem i have.
1 - My power button no longer works
2 - No ROM installed
3 - Vol buttons work
So due to an error on my part i wiped my system , data, delv/cache , and because i was rushing i rebooted the phone before installing the new rom. Now normally i would just boot into recovery and flash a rom, but my power button no longer works. I can get into download mode if the phone dies by holding vol down and plugging into a pc, and such can use fastboot commands, but with no Rom i cant get USB debugging to use "adb reboot recovery" . Is there anyway that i can get into recovery or a way to flash stock recovery, system and such. thanks in advance.
Click to expand...
Click to collapse
Have tried an ruu? I suggest using the sdcard method. Safest.
andybones said:
Have tried an ruu? I suggest using the sdcard method. Safest.
Click to expand...
Click to collapse
i havent tried that, i thought i need stock recovery and to relock the bootloader for RUU, can you explain "SD card method" .
Bloodx32 said:
i havent tried that, i thought i need stock recovery and to relock the bootloader for RUU, can you explain "SD card method" .
Click to expand...
Click to collapse
No you don't need to lock bl. Or need stock recovery, That's outdated info.
Sure:
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
andybones said:
No you don't need to lock bl. Or need stock recovery, That's outdated info.
Sure:
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Click to expand...
Click to collapse
thanks alot, i will give this a try. i can just get the latest RUU from HTC website and be fine right?
Bloodx32 said:
thanks alot, i will give this a try. i can just get the latest RUU from HTC website and be fine right?
Click to expand...
Click to collapse
Absolutely. Are you soff or son?
If son Id have to double check about locking bl but I'm quite sure that's very old info, and ruu has the stock recovery and just overwrites w.e you have
And soff you 100% don't need to mess w anything.
I'm soff/locked bl and flash ruu all the time. :good:
HTC website may even have directions but not sure.
RUU wiil wipe internal ste
andybones said:
Absolutely. Are you soff or son?
If son Id have to double check about locking bl but I'm quite sure that's very old info, and ruu has the stock recovery and just overwrites w.e you have
And soff you 100% don't need to mess w anything.
I'm soff/locked bl and flash ruu all the time. :good:
HTC website may even have directions but not sure.
RUU wiil wipe internal ste
Click to expand...
Click to collapse
i am s-on
Bloodx32 said:
i am s-on
Click to expand...
Click to collapse
Oh shoot I was thinking backwards, sorry. You need be stock ruu to turn from soff to son.
You can flash ruu np son, but it must match your cid/mid - Carrier ID / Mosel ID.
well its like a brick now anyway, im not sure if i did the CID "111111" , something like that a long time ago. well ill see what i can do, thanks for all your help
Bloodx32 said:
well its like a brick now anyway, im not sure if i did the CID "111111" , something like that a long time ago. well ill see what i can do, thanks for all your help
Click to expand...
Click to collapse
That's "SuperCID" and iirc you need soff to achieve, I have it as well set to that. It allows you to flash any ruu to your device.
Very welcome, mention me if you are in need of anything else.
andybones said:
That's "SuperCID" and iirc you need soff to achieve, I have it as well set to that. It allows you to flash any ruu to your device.
Very welcome, mention me if you are in need of anything else.
Click to expand...
Click to collapse
so i just tried "fastboot flash zip ruu.zip" and got security error , so i did "fastboot oem lock" but now i cant lock the bootloader cuz i cant press power to confirm, i will try to put it on the SD card and try to see if it'll auto flash. but other than that any other ideas? just for educational know how, im planning on ordering new a new power/vol flex cable anyway.
Bloodx32 said:
so i just tried "fastboot flash zip ruu.zip" and got security error , so i did "fastboot oem lock" but now i cant lock the bootloader cuz i cant press power to confirm, i will try to put it on the SD card and try to see if it'll auto flash. but other than that any other ideas? just for educational know how, im planning on ordering new a new power/vol flex cable anyway.
Click to expand...
Click to collapse
Dang yea I think you did f need the vol for SD method... Shoot.
But you don't need to lock bl..
That's not correct line: you need to be in rebootRUU mode.
I'm just gunna copy and paste this from vzw thread, applies to all.
"Option 1
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!"