Related
Hi everyone
Having trouble with these commands. I reinstalled Windows the other day and I cant get it set up properly now. It worked perfectly before.
I have installed Android SDK, the platform-tools pack which has ADBWinAPI.dll in it and I have the Java development installed.
Here is what happens when I try to flash a splash screen:
...android-sdk/tools/fastboot flash splash splash1.img
sending 'splash' [750kb] ...
OKAY [ 0.176 s]
writing 'splash' ...
FAILED <remote: partition does not exist!>
finished. total time: 0.0227s
I haven't seen this happen before.
If anybody can give me some advice I would be very grateful.
The partition name is 'splash1' (not 'splash'), so if your image is called splash1.img the correct command would be:
Code:
fastboot flash splash1 splash1.img
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Hi
Thanks very much for the reply. However I managed to flash it by putting it in a blank PD98IMG.zip.
Thanks anyway
Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.
You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium
Thanks sir, I'll try.
sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.
See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command
sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA
Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!
Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.
Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!
I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?
All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?
When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
Nobody can help me?!! ((
where r the experts? really need help flashing "PJ46IMG_1.29.709.12.zip" stock rom
Folks, my RUU does not exist or leaked at all, after months of searching i managed to get its "PJ46IMG_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.12_Radio_1.1204.107.14_release_261362_signed.zip"
i have no USB-Y cable, and it's really hard to get it in my country.
so is there any workaround to flash this rom? plzzzzzzzzzzzzzzz
also please note that MY RUU DOES NOT EXIST at all common servers, unless if some one has it so may be he can share it to restore my mobile back to stock.
If that is truly a signed zip and the correct one for your device then do the following
Make sure you have plenty of battery and re lock your bootloader and have stock recovery
Boot to fastboot
Fastboot oem rebootRUU
new screen should appear with HTC logo
Fastboot flash zip nameofdownloadedfile.Zip
It will take a while to send and if the info all matches up your phone will perform the steps exactly the same as the ruu
Sent from my Nexus 7
it fails as shown below any suggestions?
D:\OneX\OneXStock>fastboot flash zip PJ46IMG.zip
sending 'zip' (598534 KB)...
OKAY [ 81.530s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 118.028s
ok then if there are no solutions for this signature verify error, would u please guide to to any location/link to get my RUU or to buy it if necessary, or maybe a higher RUU image version to be able to update, as mine is "1.29.709.12" my CID: 621, hboot: 0.95
I have a Verizon ADR6350VW HTC Incredible 2. I decided to 'upgrade' it to a new ROM.
I unlocked the boot loader and installed ClockwrkMod Recovery v5.0.2.0
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-boot
Jul 18 2011,12:39:36
I tried putting an incredible 2 ROM (Viper) and since then it won't fully boot, it gets stuck forever on the green HTC logo on the white background.
I can get to the bootloader, and tried reflashing the same or other downloaded ROMs (all meant for the HTC incredible 2). Without much luck.
The original flashing process was not interrupted. I did a lot of googling and reading (but missed the S-ON/S-OFF part originally), and have tried many different ways to get out of this without luck.
3rd party ROM will flash and complete the process (but still won't boot), Verizon ROMs will give me an error (cannot open flash, bad). I did check the md5 checksums on ALL the files I used, and tried flashing from adb to no avail.
Before anyone asks, Yes I do clear the data, cache and Dalvik cache before flashing. I am at a loss of what to try next, short of finding someone reputable online to do it for a fee.
Thanks,
Wahran
wahran99 said:
I have a Verizon ADR6350VW HTC Incredible 2. I decided to 'upgrade' it to a new ROM.
I unlocked the boot loader and installed ClockwrkMod Recovery v5.0.2.0
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-boot
Jul 18 2011,12:39:36
I tried putting an incredible 2 ROM (Viper) and since then it won't fully boot, it gets stuck forever on the green HTC logo on the white background.
I can get to the bootloader, and tried reflashing the same or other downloaded ROMs (all meant for the HTC incredible 2). Without much luck.
The original flashing process was not interrupted. I did a lot of googling and reading (but missed the S-ON/S-OFF part originally), and have tried many different ways to get out of this without luck.
3rd party ROM will flash and complete the process (but still won't boot), Verizon ROMs will give me an error (cannot open flash, bad). I did check the md5 checksums on ALL the files I used, and tried flashing from adb to no avail.
Before anyone asks, Yes I do clear the data, cache and Dalvik cache before flashing. I am at a loss of what to try next, short of finding someone reputable online to do it for a fee.
Thanks,
Wahran
Click to expand...
Click to collapse
1st recommendation: go s-off
2nd recommendation: flash the boot img from the rom in fastboot...I don't know the exact process because I am s-off, but it is discussed in many of the development threads, so now you know what terms to search for at least.
gtdtm said:
1st recommendation: go s-off
2nd recommendation: flash the boot img from the rom in fastboot...I don't know the exact process because I am s-off, but it is discussed in many of the development threads, so now you know what terms to search for at least.
Click to expand...
Click to collapse
Thank you for your reply.
Going S-OFF: I tired, most guides online will show you how to do by going to the OS first (and enabling USB debug). The only one I found from Revolutionary involved doing it from the adb. When I boot into ClockwrkMod, I can run adb just fine (doing adb devices returns the correct S/N amongst other things), but revolutionary tool complains it can't find the device.
I will google again your second recommendation.
wahran99 said:
Thank you for your reply.
Going S-OFF: I tired, most guides online will show you how to do by going to the OS first (and enabling USB debug). The only one I found from Revolutionary involved doing it from the adb. When I boot into ClockwrkMod, I can run adb just fine (doing adb devices returns the correct S/N amongst other things), but revolutionary tool complains it can't find the device.
I will google again your second recommendation.
Click to expand...
Click to collapse
From Nitsuj17 in the viper thread post 2:
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
The process will be the same for any rom as long as you are dev unlocked.
gtdtm said:
From Nitsuj17 in the viper thread post 2:
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
The process will be the same for any rom as long as you are dev unlocked.
Click to expand...
Click to collapse
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
wahran99 said:
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
Click to expand...
Click to collapse
I'm really guessing here, but try fastboot flash boot boot.img
---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------
wahran99 said:
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
Click to expand...
Click to collapse
Try this one. The author includes 2 ways to flash boot.img
http://forum.xda-developers.com/showpost.php?p=22639929&postcount=1
gtdtm said:
I'm really guessing here, but try fastboot flash boot boot.img
---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------
Try this one. The author includes 2 ways to flash boot.img
http://forum.xda-developers.com/showpost.php?p=22639929&postcount=1
Click to expand...
Click to collapse
fastboot flash boot boot.img worked without error, then I followed it with "fastboot reboot", it took about 15mn, but now it's booted to the SIM unlock screen (that would be my next step).
Thank you very much for all your help! I just registered today to these forums, I see a thank you meter next to the avatar, but can't see I way to 'officially' click and thank you, I will look again....
wahran99 said:
fastboot flash boot boot.img worked without error, then I followed it with "fastboot reboot", it took about 15mn, but now it's booted to the SIM unlock screen (that would be my next step).
Thank you very much for all your help! I just registered today to these forums, I see a thank you meter next to the avatar, but can't see I way to 'officially' click and thank you, I will look again....
Click to expand...
Click to collapse
I'm glad you got it going. You'll probably want to remember that method since you'll have to do it any time you flash a rom.
gtdtm said:
I'm glad you got it going. You'll probably want to remember that method since you'll have to do it any time you flash a rom.
Click to expand...
Click to collapse
Since I posted that message, I had to put back the Verizon stock ROM, so I can SIM unlock the phone (apparently you cannot use the unlock code with a 'cooked' ROM, something I didn't know), and while doing that, HBOOT got downgraded to 0.97, which allowed me to S-OFF the phone with revolutionary. I got the phone SIM unlocked and put back the Viper ROM on it.
In summary, learning from my mistakes, and if I am not mistaken:
1. If you plan to SIM unlock the phone, do it while it is still on stock firmware, it will save you a lot of time and headaches.
2. If you are unlocking the boot loader, S-OFF the phone as well (and put Clockworkmod on it as well), it would make life a lot easier.
3. Then you can go an experiment with ROMs....
gtdtm: Thank you again for your help and patience, and most importantly for keeping me going, as I was about to give up on this phone.
Wahran99
wahran99 said:
Since I posted that message, I had to put back the Verizon stock ROM, so I can SIM unlock the phone (apparently you cannot use the unlock code with a 'cooked' ROM, something I didn't know), and while doing that, HBOOT got downgraded to 0.97, which allowed me to S-OFF the phone with revolutionary. I got the phone SIM unlocked and put back the Viper ROM on it.
In summary, learning from my mistakes, and if I am not mistaken:
1. If you plan to SIM unlock the phone, do it while it is still on stock firmware, it will save you a lot of time and headaches.
2. If you are unlocking the boot loader, S-OFF the phone as well (and put Clockworkmod on it as well), it would make life a lot easier.
3. Then you can go an experiment with ROMs....
gtdtm: Thank you again for your help and patience, and most importantly for keeping me going, as I was about to give up on this phone.
Wahran99
Click to expand...
Click to collapse
No problem. Next challenge: Put TWRP on it instead of Clockwork.
Hello everyone, I started to play around with all the diff things you can do with a rooted phone had plans for getting a custom ROM for my phone. Let me stat by saying that I am very new to all this.
I day ago i was getting ready to install the custom ROM for viper (ViperOneM8_1.7.1) reason being is coming from a htc one m7 with sense i wanted to get back to sense from my stock GPe m8.
I was able to unlock my bootloader and get my phone rooted I fallowed this video (How to Root your HTC One M8 - Full Guide) From Sakitech... or least I think im rooted still... I'll come back to you as to why I say "I think I'm rooted".
I thought it would be very simple just fire up the custom recovery and flash the ROM and sit back while it flashed, well everything went down hill from this point. Let me tell you what i did.
First i got to the custom recovery and I did a wipe I did advanced wipe and checked the boxes this is where I think I deleted the OS(after this I could not get back on the phone to do anything only will boot to recovery and it say no OS installed then asks if I want to get SuperSU installed this is where I already thought I was rooted but maybe on not??? I'm very confused about that
Then I used the sideload method to push the rom zip and try to flash the rom at this point I cant get it to flash. First I was getting the MD5 error I checked that off now it will just fail either saying error executing the binary from the zip or that zip is corrupted. (I tried re-downloading the ROM even from mirror link)
At this point I am very frustrated and feel helpless. I tried my best to keep from posting this and try to research to see if i can find the solution myself but I'm having no luck I have my days off from work to get my phone up and running or ill just have to go but another phone. At this point I really need some help. All I want is a working phone if i can get back to GPe stock that would be fine or make the ViperOne work.
Attempts to solve my problem: I tried flashing GPE4.4.3_m8.zip and other stock GPe ROMs nothing works
Thanks for reading and all your help I will sit nest to my comp and answer anything to try make everything as clear as possible. Thank you again
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Demonwarrior said:
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Click to expand...
Click to collapse
no offense, buy you need to read before you continue anything else.
rbouza1 said:
no offense, buy you need to read before you continue anything else.
Click to expand...
Click to collapse
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Demonwarrior said:
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Click to expand...
Click to collapse
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Mr Hofs said:
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Click to expand...
Click to collapse
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
fastboot flash img boot.img
---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------
try that command, and what model did you have originally and did you convert to gpe or flash a gpe ROM.
gave me an error
Code:
FAILED (remote: signature verify fail)
Its a stock Google play edition I bought from the Google paly store, I didnt flash any other rom the ViperOne rom was going to be the first flash on the phone
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
iHagbani said:
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
Click to expand...
Click to collapse
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
ckpv5 said:
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Demonwarrior said:
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Click to expand...
Click to collapse
I know, but I told you this way in case that the adb didn't flash the whole zip file!
Demonwarrior said:
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Click to expand...
Click to collapse
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
j to the 4n said:
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
Click to expand...
Click to collapse
I tried the instruction on the thread it didnt work... I think its because i have s-on
Code:
C:\Users\owner\Desktop\htc one\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.058s]
finished. total time: 0.061s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.483s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.846s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.484s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.665s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.479s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.662s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.478s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.661s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.458s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.641s
C:\Users\owner\Desktop\htc one\platform-tools>
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.470s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.650s
C:\Users\owner\Desktop\htc one\platform-tools>
The post says to try it a few times but still giving me the say error