Related
Hello,
I am a new user, but I will do my best at providing as much information as possible to help the experts out here.
My TF700 device is currently rooted, and unlocked. I am on JB 4.2.1 using build 10.6.1.14.8 (US). I have also installed the newest available TWRP from the play store. USB debugging is enabled on my tablet.
I am attempting to follow the steps in sbdags fantastic guide to installing CROMi-Xenogenesis 5.3 DEODEX: http://forum.xda-developers.com/showthread.php?t=2425383
I would have posted to that thread with my question, but I am not allowed as I am a new user.
I have had no problem following the steps up until I reached the part where I needed to download Scott's Custom Recovery Tool. The instructions are quite unclear. I have downloaded the recovery tool, put the folder on my desktop. I did some digging around and realized I have to rename a .blob file to recovery.blob and put it in the file. I believe that I downloaded the correct version and renamed it to recovery.blob. The version I downloaded was openrecovery-twrp-2.6.3.2-tf700t.blob
I renamed the file to recovery.blob and ran "Scott's TF700T Recovery Install Tool.bat". The following appeared:
Here we go! Rebooting to bootloader now! (this didn't actually do anything on my tablet)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
There is an adb that came with the recovery tool I downloaded from the thread I linked, but I'm not sure what I am missing. Other threads mention it was straightforward so I am not sure what I am missing.
Any help would be greatly appreciated! Thank you!
Deetrixx said:
Hello,
I am a new user, but I will do my best at providing as much information as possible to help the experts out here.
My TF700 device is currently rooted, and unlocked. I am on JB 4.2.1 using build 10.6.1.14.8 (US). I have also installed the newest available TWRP from the play store. USB debugging is enabled on my tablet.
I am attempting to follow the steps in sbdags fantastic guide to installing CROMi-Xenogenesis 5.3 DEODEX: http://forum.xda-developers.com/showthread.php?t=2425383
I would have posted to that thread with my question, but I am not allowed as I am a new user.
I have had no problem following the steps up until I reached the part where I needed to download Scott's Custom Recovery Tool. The instructions are quite unclear. I have downloaded the recovery tool, put the folder on my desktop. I did some digging around and realized I have to rename a .blob file to recovery.blob and put it in the file. I believe that I downloaded the correct version and renamed it to recovery.blob. The version I downloaded was openrecovery-twrp-2.6.3.2-tf700t.blob
I renamed the file to recovery.blob and ran "Scott's TF700T Recovery Install Tool.bat". The following appeared:
Here we go! Rebooting to bootloader now! (this didn't actually do anything on my tablet)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
There is an adb that came with the recovery tool I downloaded from the thread I linked, but I'm not sure what I am missing. Other threads mention it was straightforward so I am not sure what I am missing.
Any help would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try my recovery guide here
http://forum.xda-developers.com/showthread.php?t=2646279
sbdags said:
Try my recovery guide here
http://forum.xda-developers.com/showthread.php?t=2646279
Click to expand...
Click to collapse
Thanks so much! This is much more detailed than what I've been able to dig up anywhere else.
I will give this a try when I get home.
sbdags said:
Try my recovery guide here
http://forum.xda-developers.com/showthread.php?t=2646279
Click to expand...
Click to collapse
Thanks so much for the guide, was very easy to follow and appeared to work well, one question though.
I was able to follow the steps, the device seemed to have flashed ok (at least the .bat file didn't give me any errors, nor did anything appear out of the ordinary on the tab when it was going through the steps.
However, when I hold down vol down + power following happens:
"Key driver not found.. Booting OS" appears at the top left of the screen, along with 2 other lines regarding bootloader and firmware version info, and "starting fastboot USB download protocol" on another line.
Then I hit vol up on the RCK icon
"Booting recovery kernal image" appears on the top left of the screen.
The android appears and it says "installing system update" below it.
Within about 3 seconds the android changes to lying on his back with the red warning symbol above him with "Error!" below.
Any ideas what this is, or how to fix it? I know my tab still works okay because I can still load my old OS fine, but wondering how to get this working properly.
Thanks again for your help!
Deetrixx said:
TI was able to follow the steps, the device seemed to have flashed ok (at least the .bat file didn't give me any errors, nor did anything appear out of the ordinary on the tab when it was going through the steps.
However, when I hold down vol down + power following happens:
"Key driver not found.. Booting OS" appears at the top left of the screen, along with 2 other lines regarding bootloader and firmware version info, and "starting fastboot USB download protocol" on another line.
Then I hit vol up on the RCK icon
"Booting recovery kernal image" appears on the top left of the screen.
The android appears and it says "installing system update" below it.
Within about 3 seconds the android changes to lying on his back with the red warning symbol above him with "Error!" below.
Any ideas what this is, or how to fix it?
Click to expand...
Click to collapse
This is the stock recovery. Are you sure you followed step 6? (you must not hold volume-down at the *first* reboot directly after flashing the new recovery)
_that said:
This is the stock recovery. Are you sure you followed step 6? (you must not hold volume-down at the *first* reboot directly after flashing the new recovery)
Click to expand...
Click to collapse
I have it working now, I just followed all the steps again and this time it seemed to work fine. That must have been what I missed.
Thanks for your help! Let the fun begin!!!!
Hi everyone,
after days of researching this issue I'm finally at wits end. After installing the Playstore version of ROM Manager, my Asus has been stuck in CWM recovery mode with the inability to mount any drives. When I re-boot the tablet gets stuck on the load screen. I have tried several methods to flash the tablet using:
- NVFLASH
- EASY FLASHER
- FASTBOOT
- ONE CLICK RECOVERY
- ADB PUSH
The recurring issue that I seem to be encountering using these methods is that my PC recognizes the tablet in APX mode (I have tried both naked & usbpcdrivers) but the utility software does not. When I boot into recovery mode ADB recognizes my device but does not in APX mode. When I run NVFLASH while in APX mode my tablet gets disconnected from the PC and I receive a USB write error from NVFLASH.
Prior to the failure I successfully rooted my device using Baidu Root. At this point I don't even know how to power off the device as the only way to exit the loop is to boot into recovery or APX mode.
Any help would be greatly appreciated, as my experience with these matters are limited.
Thanks
roniinn said:
Hi everyone,
after days of researching this issue I'm finally at wits end. After installing the Playstore version of ROM Manager, my Asus has been stuck in CWM recovery mode with the inability to mount any drives. When I re-boot the tablet gets stuck on the load screen. I have tried several methods to flash the tablet using:
- NVFLASH
- EASY FLASHER
- FASTBOOT
- ONE CLICK RECOVERY
- ADB PUSH
The recurring issue that I seem to be encountering using these methods is that my PC recognizes the tablet in APX mode (I have tried both naked & usbpcdrivers) but the utility software does not. When I boot into recovery mode ADB recognizes my device but does not in APX mode. When I run NVFLASH while in APX mode my tablet gets disconnected from the PC and I receive a USB write error from NVFLASH.
Prior to the failure I successfully rooted my device using Baidu Root. At this point I don't even know how to power off the device as the only way to exit the loop is to boot into recovery or APX mode.
Any help would be greatly appreciated, as my experience with these matters are limited.
Thanks
Click to expand...
Click to collapse
First recommendation, stay away from ROM Manager, our device doesn't like it. You need to try and uninstall all usb drivers associated with tf101 and start over. I used the drivers from BRK's v.8 Tool Kit. You may need to find some newer adb files to swap out with his, but try first. To clean all the drivers may require connecting the tab to pc in different modes to even see some of the drivers, but see what's in Programs & Features - Remove function in Windows. You will also need the stock ROM downloaded from Asus site before you start. If you can get into recovery, then you should have an option in there to power off the device. If you get that far, then his tool has the nvflash pieces to start from scratch and get rooted and install an older custom recovery. Go with the CWM version there and, ultimately, change it out to the latest TWRP as soon as possible. Getting the drivers for Windows working is the hardest part, assuming everything else works. Conflicting USB drivers will be nothing but headaches, as you've found out.
Hi,
just to be clear, when the tablet is in APX mode, is ADB supposed to be able to detect it when the adb devices command is used?
roniinn said:
Hi,
just to be clear, when the tablet is in APX mode, is ADB supposed to be able to detect it when the adb devices command is used?
Click to expand...
Click to collapse
I don't think so. It's like download mode on other Android devices. You should be able to access via adb in Android, with USB debugging enabled, or in some custom recoveries, my TWRP builds for one. I believe nvflash is the only method to communicate with APX mode.
Sent from my SM-N900T using XDA Premium HD app
Hi,
I have re-installed drivers, but the PC still disconnects my tablet when running NVFLASH, I have read that a utility named WHEELIE might assist in unlocking the bootloader on my device allowing NVFLASH to run successfully. The problem is I can not locate the windows version of this file anywhere. All of the links point to a website named AndroidRoots, but the file seems to have been removed from the site.
Any Ideas where I can locate this program?
Thanks again.
roniinn said:
Hi,
I have re-installed drivers, but the PC still disconnects my tablet when running NVFLASH, I have read that a utility named WHEELIE might assist in unlocking the bootloader on my device allowing NVFLASH to run successfully. The problem is I can not locate the windows version of this file anywhere. All of the links point to a website named AndroidRoots, but the file seems to have been removed from the site.
Any Ideas where I can locate this program?
Thanks again.
Click to expand...
Click to collapse
BRK's version 8 tool I referenced uses wheelie to cover all possible skus of tf101 and works well for me. As far as drivers, you have to make sure there's only one set installed for tf101.
Sent from my SM-N900T using XDA Premium HD app
Does the wheelie script run automatically when I invoke the rootkit app, or do I have to manually run it from a CMD window?
Thanks for all your help,
roniinn said:
Does the wheelie script run automatically when I invoke the rootkit app, or do I have to manually run it from a CMD window?
Thanks for all your help,
Click to expand...
Click to collapse
It runs it where needed within a windows app interface, completely transparent once you start the program executable by double clicking it. You'll see a command window, but it just shows you the progress.
Sent from my SM-N900T using XDA Premium HD app
Thanks for your help,
I have finally got my device up and running again.
My next step is to flash the new KatKiss ROM, can I do this using BRK's toolkit by substituting my stock rom file with the new one, or is it to better to install the new rom from recovery and external SD card?
roniinn said:
Thanks for your help,
I have finally got my device up and running again.
My next step is to flash the new KatKiss ROM, can I do this using BRK's toolkit by substituting my stock rom file with the new one, or is it to better to install the new rom from recovery and external SD card?
Click to expand...
Click to collapse
I would just install it from recovery and ext sdcard, easier if you've already cleaned and repartitioned, etc with a stock rom.
Sent from my SM-N900T using XDA Premium HD app
Hi All,
It took me about a week to resolve this after following all the guides I could find on the Internet, using all the various tools out there and nothing worked.
I will begin describing the situation.
I have totally wiped my device, including system and OS, don't ask me why, I don't have the answer to that :silly:
What I have realized next is that the TWRP recovery is gone and all I have is a stock Cyanogenmod recovery.
Then I have found out that the bootloader is locked and I am unable to flash a new recovery.
Also, adb, require the user to approve on first connection via a message on the handset screen, however, in Stock Cyanogenmod recovery, no message appeared.
So, how do I get out of this?
At first, I have tried to make a brick from it, as in the described situation above, it was not a software brick, nor hardware brick - I call it "The Limbo state".
eventually, I have used adb version 1.0.32, it was able to access the handset via sideload update and managed to sideload "cm-11.0-XNPH22R-bacon-signed.zip" as an update (both will be linked to this post at the bottom).
So, how this was done:
1. download adb 1.0.32
2. download cm-11.0-XNPH22R-bacon-signed.zip
3. boot the handset into Cyanogenmod Stock Recovery
4. Connect the handset to the computer (I used Windows 7)
5. open cmd.exe as an administrator and cd to the location where you have extracted adb
6. On the handset go to Update-> via sideload
7. run the following commands:
7.1 adb devices (you should see your device ID and next to it it should show "sideload"
7.2 adb update <path to where cm-11.0-XNPH22R-bacon-signed.zip is located>
8. What you will see next on the handset, is that the package is being uploaded and the update begins. This phase took about 25 minutes to complete so be patient, as at some times it looked stuck but it is running.
9. When completed, I was able to reboot the handset into working state, then was able to load SuperSU and TWRP to go with the regular process of upgrading to a newer CM version ROM.
Hope you will find this helpful.
I still can't post an external link for the cm-11.0-XNPH22R-bacon-signed.zip - so you can PM me to get the link to download it.
Hi and thanks for using your time to take a look at my post. I am trying to install cyanogenmod 12.1 on my TF300T.
I went to the Asus website and downloaded the unlock tool v8, installed on tablet, and ran it without any issues. Tablet reboots shows little "this device is unlocked" in top left corner. However when it boots up and I try to run an app like titanium backup pro or supersu app, the app say they cannot get root access....
Has anyone experienced this before?
Am I missing a step?
I have android ver. 4.2.1.
Any info is greatly appreciated.
Unlock unlocks the boot loader allowing you to load custom roms via additional boot loader as per rom instructions, it does not give root access. You will need to search to a process to root the tablet, I used Kingo root, some do not like using this......although I had no problems. Using custom roms and rooting is at your own risk!
So this is the process that ive Followed... I ran the unlock tool, everything completes without issue. Nexissue the command adb reboot bootload to get my tablet into correct mode. Once the tablet is ready I flash a recovery image (TeamWin TWRP) to the device and boot the recovery. From here, it seems that recovery does not permission to mount any of the drives/folders. I look at the log file and see errors sayin unable to find partitions and unable to mount folders/drives. Below is a link to an image of the errors.
I am not sure if this link will get posted correctly to this thread: https:// drive.google.com/file/d/0B-bmj1Mkq-xzMkQyMHVPU0poSjQ/view?usp=sharing
BTW, thanks for your quick reply.
FYI, for the link above, there is a space between the HTTPS:// and the word drive which start the web address. The forum would not allow me to post a link since I am new.
Sorry, I'm no expert. When I installed Kang TWRP for KatKiss Lollipop, I did lots of research before diving in. Carefully followed instructions and all went well. When you flashed TWRP did you then reboot into bootloader?
fastboot reboot-bootloader
I think you will have to give all the steps you took, then perhaps someone will come along with more guidance.
Just to add some clarity to my situation, in hopes that someone can help shine a light:
1) Installed and ran Unlock device app V8 on the Asus webiste. It claims this is compatible with android version 4.2, i have version 4.2.1. Unlock ran then needed to reboot device. Upon reboot I saw the message "This device is unlocked" in the top right of the screen.
2) Once device rebooted, I installed adb/fastboot on my pc and ran it using CMD.
3) Connect tablet to PC using usb cable.
4) Ran the command "adb reboot bootloader" to get the device into required mode.
5) Next I run the command "fastboot devices" to verify the PC can see the tablet.
6) Run the command "fastboot -i 0xb05 flash recovery Recovery.img" to flash over the Recovery image file I have. Flashing goes through without any errors.
7) Once flash completes, I press up volume button to go into recovery.
8) Recovery boots and I am at the screen with the various options to install, backup, restore, wipe, etc.... I have Team win recovery project v2.8.7.0
9) If i try to use the backup option, it shows my internal storage as (0MB). I look at the log file (https:// drive.google.com/file/d/0B-bmj1Mkq-xzMkQyMHVPU0poSjQ/view?usp=sharing) and see that it cant find or mount various drives. If you want to view link, copy url and remove the space between https:// and the word drive.
**** ALSO, if you have a better or proven method, please feel free to suggest.*****
imnotorginal said:
Hi and thanks for using your time to take a look at my post. I am trying to install cyanogenmod 12.1 on my TF300T.
I went to the Asus website and downloaded the unlock tool v8, installed on tablet, and ran it without any issues. Tablet reboots shows little "this device is unlocked" in top left corner. However when it boots up and I try to run an app like titanium backup pro or supersu app, the app say they cannot get root access....
Has anyone experienced this before?
Am I missing a step?
I have android ver. 4.2.1.
Any info is greatly appreciated.
Click to expand...
Click to collapse
This issue has been resolved. It looks like the version of TWRP I was using (2.8.7.0) was not getting access to the file systems to be able to make changes or install.
I downloaded version 2.8.7.2 and everyone went flawlessly after that.
Special thanks to bonzoe for telling me that he was using Kang TWRP which led me to google that and get a new version.
Hi. I am hoping someone can assist, I have an HTC one sv LTE. I think it's rooted it says S off in the bootloader. It is running Android 4.0.4,
I keep getting notifications for system updates. I download them but they won't install. I have tried to install a recovery ROM through bootloader/recovery but so far through it fails. Tried running RUU but when connect to PC it doesn't find the phone.
When started phone by pressing pwr with volume button down it gives this info
*** locked ***
K2_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.00.0000
RADIO-1.15.40a.00.04
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 29 2013,17:51:12:16090
Any assistance will be thankfully received
Somebody messed around on this phone! Hboot 2.0 means, it had Android 4.1 or 4.2.2 already installed.
But when you say, your running 4.0.4 it should be hboot 1.0.
The RUUshould run in your case, so what error do you get? Is USB Debugging on in Settings? Adb & fastboot driver installed? HTC Sync installed?
old.splatterhand said:
Somebody messed around on this phone! Hboot 2.0 means, it had Android 4.1 or 4.2.2 already installed.
But when you say, your running 4.0.4 it should be hboot 1.0.
The RUUshould run in your case, so what error do you get? Is USB Debugging on in Settings? Adb & fastboot driver installed? HTC Sync installed?
Click to expand...
Click to collapse
hi sorry about the delay I had to work late, the phone was bought from ebay by my son, it is has it came from ebay.
I have adb and fastboot drivers installed, but when I connect the phone to the laptop the laptop does not even see the phone.
when I run ruu from the laptop it says can not connect to android device
when I download update on the phone for the os it started to install gets about 3rd of the way through and stops showing a red triangle with an ! in the centre of it, only way to turn it off then is by pulling the battery. when I start phone in bootloader then select recovery it gives options to install from sd card where I coped the recovery file, it starts to install then stops saying signature verification failed installation aborted, I have taken some screen images so you can see, maybe you can work out what is going on
jules2510 said:
hi sorry about the delay I had to work late, the phone was bought from ebay by my son, it is has it came from ebay.
I have adb and fastboot drivers installed, but when I connect the phone to the laptop the laptop does not even see the phone.
when I run ruu from the laptop it says can not connect to android device
when I download update on the phone for the os it started to install gets about 3rd of the way through and stops showing a red triangle with an ! in the centre of it, only way to turn it off then is by pulling the battery. when I start phone in bootloader then select recovery it gives options to install from sd card where I coped the recovery file, it starts to install then stops saying signature verification failed installation aborted, I have taken some screen images so you can see, maybe you can work out what is going on
Click to expand...
Click to collapse
Well, your device is S-off, there are many ways to get latest software.
And this brings the question in my mind: what is the goal you wanna get? Latest Software?
Easiest way would be, to flash twrp recovery and restore a backup from 4.2.2. Should be an easy task, when the device is S-off.
To the RUU "thing", i have copied a guide from HTC website, how tro flash a RUU:
Performing the ROM Update:
1. Download and save the HTC One™ ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, open Play Store and tap the Menu icon, then select My apps and ensure all installed apps are updated.
9. After initial setup and updating all apps, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
Click to expand...
Click to collapse
old.splatterhand said:
Well, your device is S-off, there are many ways to get latest software.
And this brings the question in my mind: what is the goal you wanna get? Latest Software?
Easiest way would be, to flash twrp recovery and restore a backup from 4.2.2. Should be an easy task, when the device is S-off.
To the RUU "thing", i have copied a guide from HTC website, how tro flash a RUU:
Click to expand...
Click to collapse
hi, I guess my ultimate goal is to have an stable working phone with the latest software the htc one sv can have,
yes it is S off, but I downloaded twrp app on the phone but when I open it I get the message the phone needs to be rooted and it closes so even though it says S off twrp does not recognise that its rooted,
when I connect the phone to the computer, the computer does not see the usb device and on the phone just the light to show is charging comes on, does not say usb debugging started or sync etc.
I do not know what has been done to this phone but seems nothing I try works,
I am not the most experienced I need expert help thats why I'm here.
jules2510 said:
hi, I guess my ultimate goal is to have an stable working phone with the latest software the htc one sv can have,
yes it is S off, but I downloaded twrp app on the phone but when I open it I get the message the phone needs to be rooted and it closes so even though it says S off twrp does not recognise that its rooted,
when I connect the phone to the computer, the computer does not see the usb device and on the phone just the light to show is charging comes on, does not say usb debugging started or sync etc.
I do not know what has been done to this phone but seems nothing I try works,
I am not the most experienced I need expert help thats why I'm here.
Click to expand...
Click to collapse
If it isn't broken, we will get it done
We start with "minimal adb/fastboot" -> [TOOL]Minimal ADB and Fastboot or go to the direkt download at afh
Install the exe file and choose a place like desktop, for installation.
Download HTC Sync, install it (software & drivers get installed), then uninstall HTC Sync (only the software, so drivers should stay on your pc).
Download this TWRP backup, which is the latest software for your device.
Unzip it (you will get a k2ul-3114011-422-sense5 folder with some boot, data, system files in it) and put it into a folder on external sdcard that has this folder structure:
TWRP\BACKUPS\Put in here the Serial number of your device (in UPPERCASE LETTERS)\k2ul-3114011-422-sense5
Connect your phone to your pc with usb cable, boot to fastboot mode (bootloader), go to your minimal adb folder and open a cmd window. Type into this window
Code:
fastboot devices
You should get an output with the serial number of your device.
Then we go to www.htcdev.com
Make an account and follow the unlock guide/process until you bootloader is unlocked. Note: you will loose all userdata, so backup everything what is important to you.
Download the TWRP_2871_Recovery.img.zip file here, unzip it, rename it to recovery.img and copy it to your minimal adb folder.
Go to the cmd window in your adb folder (device is again in fastboot mode) and flash the recovery by typing into the cmd
Code:
fastboot flash recovery recovery.img
Now we boot to recovery and there go to wipe -> advanced (steps here could be named a little different, because this is an 2 years old version od TWRP and meanwhile some things have changed, so i'll explain how i remember the things).
Check system, boot, data & cache and swipe to wipe.
Go back to main menu -> restore and if everything was correct, you will see the backup you have downloaded before. Choose it and swipe to restore.
After the restore you should be able to boot into android 4.2.2 software.
If that was fine, we should flash latest firmware for the 4.2.2 software, but that step i'll explain if you are ready for it.
first let me express my thanks for your expert assistance and patience
ok now
download minimal adb/fastboot and install to desktop....... check
download htc sync complete with usb drivers install the uninstall sync leaving drivers installed ..... check
download twrp backup and unzip to sd card with file structure TWRP\BACKUPS\Put in here the Serial number of your device (in UPPERCASE LETTERS)\k2ul-3114011-422-sense5......... check
Download the TWRP_2871_Recovery.img.zip file here, unzip it, rename it to recovery.img and copy it to your minimal adb folder.......... check
connect phone to computer with usb with phone in bootloader...... fail
I opened cmd window in minimal adb, booted the phone in bootloader, put into fastboot
connected usb cable but it still said fastboot, didn't change to fastboot usb so anyway from cmd window I typed fastboot devices but nothing happen just the same line of code appeared on the line below
eg c:\ users\jules\desktop\minimal adb and fastboot> fastboot devices, hit enter
but all that happens is the same line appears below without the fastboot devices
c:\ users\jules\desktop\minimal adb and fastboot>
Ok, not sure whats the problem, but lets try another way first:
Make sure your phone is charged at least up to 50%.
Download this RUU: https://www.androidfilehost.com/?fid=24369303960683578
Rename it to PL80IMG.zip (make sure it is not named PL80IMG.zip.zip) and copy it in the external sdcard. Boot into the bootloader and let the phone recognise the zip. Confirm to update with vol+ and let it run until its finished.
i have just done as you directed but it does not recognise the file, it just says no or wrong image ??
looks like some one has done a real crap job on this phone previously
Well, it seems so...
Few things: check if
- the name of the ruu is named correctly
- you have the file in root of your external sdcard
- the md5 sum of the downloaded file is the same as on the afh download site
About the fastboot not recognised:
- try another usb cable
- try another usb port
- or even try another pc
Other suggestion: Sunshine is an app to unlock/soff htc devices. One Sv is supported, as far as i know.
Maybe this app can unlock the phone without to use fastboot/adb connection. But it is a paid app and cost 25,- $.
Only if already used on the phone, the second unlock is free. Maybe worth a try...
would if work if I try through recovery in the bootloader menu?
jules2510 said:
would if work if I try through recovery in the bootloader menu?
Click to expand...
Click to collapse
Tbh, i don't know. Never tried this way, but the ruu should work, from root of external sdcard, when you are in bootloader (not fastboot mode).
Did the same yesterday with my One M8, without problems.
right now I am booting up my older desktop pc, it is windows 7, as laptop is windows 10, will download all software and drivers and try again, heres hoping lol
i have used my desk top computer, downloaded all again but still same result. phone does not see computer and computer does not see the phone,
this maybe a stupid question and if it is please forgive but could the charge/usb port on the phone be faulty?
Yes, possible.
Lets try another thing: go to tis thread http://forum.xda-developers.com/showthread.php?t=2386426 and follow the guide to downgrade hboot (download k2ul version). So we can see if your bootloader accepts PL80IMG.zip. And if succesful, the bootloader will match the software version.
please old.splatterhand i have HTC One SV but i can't do it S-OFF Because His S-ON
and i can't goback to stock rom 4.2.1
please help me
Hi! Could somebody help? I have a factory unlocked HTC One SV. The phone doesn't turn on when I try to power it on. I also tried the volume up+power button hard reset, but it didn't worked.
When I connect it to the pc, the device manager says: Relink HS-USB Qdloader 9008 (com 5)