Related
so I took my sprint htc one with viperone loaded and did an ruu back to 4.3 version wiping everything, I successfully got my over the air update to 4.4.2 and decided I'd try to back down to 4.3 so I could restore my twrp viper backup however twrp won't flash currently and I think I caused issues with my bootloader. Since there is no 4.4.2 ruu available yet and I can still get to bootloader, but not recovery, I think I'm still not completely bricked. I've tried a factory restore but I end up at the white screen with green htc letters and it never goes further. Could flashing the 4.4.2 stock recovery fix my issue?
Any attempt to do manual ruu flash, fastboot flash zip rom.zip, fails with this message
target reported max download size of 1514139648 bytes
sending 'zip' (1082662 KB)...
OKAY [ 53.293s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 68.408s
current revs
m7_wls pvt ship s-on rh
hboot-1.56.0000
radio-1.00.20.1108
os-4.06.651.4
at this point I'd just like it to boot to android, any help would be greatly appreciated.
Thanks
Lock bootloader and run the latest ruu
Sent from my HTC One using Tapatalk
elvisypi said:
Lock bootloader and run the latest ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for responding, I think I'ved tried every combination of locked and unlocked bootloaders but hey what have I got to lose at this point.
ran fastboot oem lock
ran latest ruu I could find, RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.04.651.2_Radio_1.00.20.0913_3_NV_SPCS_4.38_003_release_335355_signed_2.exe
I get error [155] unknown error
this worked to flash from viper one then take all the OTA updates to 4.4.2 but now I get this 155 error
I think I have to wait for the 4.4.2 ruu to be released to get back to a fully functioning but I wanted to check around.
You could try this... http://forum.xda-developers.com/showthread.php?t=2634256
[Guide] How to Downgrade from KK to JB S-OFF Required
jstn76rs said:
You could try this... http://forum.xda-developers.com/showthread.php?t=2634256
[Guide] How to Downgrade from KK to JB S-OFF Required
Click to expand...
Click to collapse
yeah I was starting there originally but getting s-off on 1.56 isn't possible yet.
InvaderSkooge said:
yeah I was starting there originally but getting s-off on 1.56 isn't possible yet.
Click to expand...
Click to collapse
AFAIK that's not correct. Try firewater http://firewater-soff.com
Sent from my HTC One using Tapatalk
elvisypi said:
AFAIK that's not correct. Try firewater http://firewater-soff.com
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
looks like firewater requires being able to boot into android and I can't get past the white screen with green HTC letters, I can get into the bootloader and fastboot but can't get further than that.
btw I really do appreciate the comments and suggestions, I feel like I'm just being negative and shooting each one down but I really am trying them as you post them before replying just in case I've missed something.
I can understand the older ruu versions failing as it won't let you downgrade firmwares with s-on but I'd think that some of the posted roms would work. is it possible to extract the boot and recovery from a 4.4.2 upgraded handset for flashing on another?
InvaderSkooge said:
looks like firewater requires being able to boot into android and I can't get past the white screen with green HTC letters, I can get into the bootloader and fastboot but can't get further than that.
Click to expand...
Click to collapse
Reflash the latest TWRP and than flash a 4.4.2 rom, I don't see why it shouldn't work. If you really messed up(flashed some gsm rom or whatever) you'll probably have to wait for the 4.4.2 ruu to come out
Sent from my HTC One using Tapatalk
elvisypi said:
Reflash the latest TWRP and than flash a 4.4.2 rom, I don't see why it shouldn't work. If you really messed up(flashed some gsm rom or whatever) you'll probably have to wait for the 4.4.2 ruu to come out
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ok I'm an idiot, thanks for bearing with me here, I had tried twrp load again several times, using 2.6.3.3 instead of 2.6.3.0....
InvaderSkooge said:
ok I'm an idiot, thanks for bearing with me here, I had tried twrp load again several times, using 2.6.3.3 instead of 2.6.3.0....
Click to expand...
Click to collapse
There is no twrp 2.6.3.3 for Sprint
[Q&A] [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmwar
Q&A for [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmware
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmware. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
s_off question
liam_davenport said:
I had no problem with receiving update with the stock recovery installed
---------- Post added at 10:49 AM ---------- Previous post was at 10:47 AM ----------
Don't go from 4.x.xxx.xx to 5.xx.xxx.xx I've had the firmware bug that bricks you're device, it's a pain have to set up linux and run some commands
Click to expand...
Click to collapse
will the process retain s off? Thanks in advance
crazyandroid said:
will the process retain s off? Thanks in advance
Click to expand...
Click to collapse
the only way your phone can turn back to s-on is if you enter the right command manually "fastboot writesecureflag 3"
S-OFF will never turn back to S-ON by itself
alray said:
the only way your phone can turn back to s-on is if you enter the right command manually "fastboot writesecureflag 3"
S-OFF will never turn back to S-ON by itself
Click to expand...
Click to collapse
Thank you for the quick reply.
running into a problem
First time back with an HTC since the nexus one. so bear with my on the of the HTC exclusive setting, options and what not.
I keep getting an error code "FAILED (remote: 99 unknown fail)" when i try and flash the ROM, I get the error code in the same spot i would get an error the first time I ran the code. this is a different code than what he said I would get. any direction on what i need to change is greatly appreciated!
Here is the code i get --------------------------------
Tanners-MacBook-Pro:Mac Tanner$ ./fastboot flash zip RUU-HTC_One_GE-4.4.2-3.62.1700.1_Rooted.zip
sending 'zip' (514596 KB)...
OKAY [ 20.864s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 21.109s
Tanners-MacBook-Pro:Mac Tanner$
--------------------------------------------------------------
sOther Information:
Build Number 4.18.502.7 CL302626
Baseband Version "Unknown"
HBOOT 1.44
Radio 4A.17.3250.20
That might be a corrupted download. Did you try redownloading it?
I may have actually found the problem. This phone is all sorts of messed up, when i got it, it had a custom ROM, (Which was stuck on the HTC Logo), a CWM recovery, but still S-ON.
I have ran firewater and Revone methods to turn S-Off. The first time i ran it is said successful, but I never bothered to confirm.
I got it working and i was able to grant root access to applications but their were reboots ever 1-2 minutes. so i flashed a new ROM.
now, i have a working ROM (still have the random reboots), SuperSU tells me i need to update my binaries, and i still have S-ON.
I am sure they are all related, and my main goal is to get S-OFF, but i don't know how. i should quit messing around with HTC and just stick with what i know, the Nexus phones.
teport said:
I may have actually found the problem. This phone is all sorts of messed up, when i got it, it had a custom ROM, (Which was stuck on the HTC Logo), a CWM recovery, but still S-ON.
I have ran firewater and Revone methods to turn S-Off. The first time i ran it is said successful, but I never bothered to confirm.
I got it working and i was able to grant root access to applications but their were reboots ever 1-2 minutes. so i flashed a new ROM.
now, i have a working ROM (still have the random reboots), SuperSU tells me i need to update my binaries, and i still have S-ON.
I am sure they are all related, and my main goal is to get S-OFF, but i don't know how. i should quit messing around with HTC and just stick with what i know, the Nexus phones.
Click to expand...
Click to collapse
you indeed need s-off to flash this ruu and you'll (maybe) have to change your cid/mid to match the android-info.txt file packed in that ruu.
Achieving s-off on hboot 1.44 is simple:
flash ARHD 31.6 (this rom is pre-rooted and have the correct unsecured kernel for the s-off exploit to work)
Then follow instructions from Revone thread.
when s-off is acheived, confirm that your cid and mid match the android-info.txt file of the ruu (or change CID/MID so they match)
Flash the ruu in RUU mode:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip
fastboot reboot
Never s-on and relock bootloader when using GPE
Can I just flash the newest firmware? Or there is a different firmware for gpe?
htc one m7 convert GPE questions.
htc one m7
model pn07100
android 4.3
htc sense 5.0
hboot 1.55
unlocked
I want to convert my m7 to a GPE. before i do anything to my phone ,I have a few questions to ask...
i want to install the RUU-HTC_One_GE-4.4-3.62.1700.1.zip rom (non rooted) http://forum.xda-developers.com/showthread.php?t=2358781
- does that mean i dont need to root my phone if im flashing the non rooted rom?
- my device is unlocked but in the bootloader is says that its locked in the menu. does that mean i still have to unlock the bootloader? is there a difference between having an unlocked phone and having an unlocked bootloader?
- do i need to install sync manager and install drivers for my phone?
- will i be able to receive updates from google OTA? do i need to flash stock recovery in order to receive OTA updates from google?
- how would i back up my stock rom (android 4.1.2 w/ htc sense 5.0) if i decide to go back.
- after the flash will i have to re-install all my apps?
thanks.
S-off mandatory
Hello, is absolutely essential s-off? If the device is only unlocked bootloader via HTCdev? The procedure will fail completely?
duzera said:
Hello, is absolutely essential s-off? If the device is only unlocked bootloader via HTCdev? The procedure will fail completely?
Click to expand...
Click to collapse
are you asking seriously or....?
Prerequisites
S-Off, <--------
ADB knowledge
Fastboot knowledge
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43459658&postcount=1
i installed the google play edition for htc one m7 4.4.2 rom. how do i add/remove panels? i dont see any personalize settings in the menu? i've tried a search and no results.
graphic glitches
I have successfully converted my phone to GPE4.4.2 using the exact methods. There is no problem with that. Problem started once I did an OTA to update it with 4.4.3 where there are graphic glitches on the status bar and the bottom part of the screen. Also the power off panel won't appear after pressing (holding) the power button. Anyone suffered this? any solutions?
Edited : Problem solved by changing phone's CID. I can't change the RUU android-info's CID because the glitch would be there as the OTA's CID is GOOGL001.
Sprint?
Hey guys, does this RUU work with Sprint yet?
when upgrade to lollipop
have this problem: mount failed to mount /dev/block/mmcblk0p037 at /data device or resource busy
how to solve it ?
in 4.4.4, stuck recovery, unrooted
It doesn't affect anything. Just let it keep going. The update takes a while because it is using the older patch method.
recovery
where can I find stock recovery for gpe rom 4.4.4/4.9.1700.1 thanks in advance
I get this too but I get FAILED (remote: 42 custom id check fail) when I reboot it just reboots back into cyanogenmod11
Cillian.K said:
I get this too but I get FAILED (remote: 42 custom id check fail) when I reboot it just reboots back into cyanogenmod11
Click to expand...
Click to collapse
wrong cid make sure your cid is compatible with the ruu
I'm trying to get back to complete stock to grab OTAs for my HTC One m8. I have s-off and I was following the guide here http://venomroms.com/viperonem8_3-0-0-requirements/ and while following the guide and looking for my Main version number and CID Number the MainVer showed up as empty and my CID Number as SPCS_001. The CID does not match anything from here http://forum.xda-developers.com/showthread.php?t=2701376 What should I do next?
Use this guide:
http://forum.xda-developers.com/showthread.php?t=2826343
You'll need the latest RUU which can be found in the first post in the thread linked below. You can use the RUU for software version 3.31.651.2.
http://forum.xda-developers.com/showthread.php?t=2729173
I would also suggest sticking to the Sprint section.
You may do something to your phone that is not for the Sprint variant and really mess up your phone.
Magnum_Enforcer said:
Use this guide:
http://forum.xda-developers.com/showthread.php?t=2826343
You'll need the latest RUU which can be found in the first post in the thread linked below. You can use the RUU for software version 3.31.651.2.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?
sadway15 said:
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?
Click to expand...
Click to collapse
Ruu is used through a pc
sadway15 said:
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?
Click to expand...
Click to collapse
The RUU will install the stock recovery. If you need info on how to run a RUU click the second link in my sig and read the RUU section.
Magnum_Enforcer said:
The RUU will install the stock recovery. If you need info on how to run a RUU click the second link in my sig and read the RUU section.
Click to expand...
Click to collapse
Okay so I think I get it now please confirm, I run the RUU with my PC then once its finished put the stock recovery corresponding to the RUU I installed in the phone then install the stock recovery using TWRP in my phone then I will have a stock htc rom with stock recovery and the phone will update from there.
sadway15 said:
Okay so I think I get it now please confirm, I run the RUU with my PC then once its finished put the stock recovery corresponding to the RUU I installed in the phone then install the stock recovery using TWRP in my phone then I will have a stock htc rom with stock recovery and the phone will update from there.
Click to expand...
Click to collapse
The RUU will put you back to completely stock...only difference is your bootloader will say ***RELOCKED*** instead of ***LOCKED***
BD619 said:
The RUU will put you back to completely stock...only difference is your bootloader will say ***RELOCKED*** instead of ***LOCKED***
Click to expand...
Click to collapse
Complete stock meaning stock rom and stock recovery right? Also what will happen if my bootloader is locked/unlocked?
sadway15 said:
Complete stock meaning stock rom and stock recovery right? Also what will happen if my bootloader is locked/unlocked?
Click to expand...
Click to collapse
Correct.
You will need to re-lock your bootloader to run the RUU if you are s-on, if s-off no need to re-lock.
BD619 said:
Correct.
You will need to re-lock your bootloader to run the RUU if you are s-on, if s-off no need to re-lock.
Click to expand...
Click to collapse
I'm trying to get to stock too but I'm s-on, besides locking the bootloader is there anything else I need to modify?
guissepi said:
I'm trying to get to stock too but I'm s-on, besides locking the bootloader is there anything else I need to modify?
Click to expand...
Click to collapse
No, just relock and run the RUU.
Magnum_Enforcer said:
No, just relock and run the RUU.
Click to expand...
Click to collapse
I tried relocking and when I ran the RUU this was the output:
Code:
./fastboot flash zip rom.zip
target reported max download size of 1830612992 bytes
sending 'zip' (1652270 KB)...
OKAY [ 47.785s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 108.972s
guissepi said:
I tried relocking and when I ran the RUU this was the output:
Code:
./fastboot flash zip rom.zip
target reported max download size of 1830612992 bytes
sending 'zip' (1652270 KB)...
OKAY [ 47.785s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 108.972s
Click to expand...
Click to collapse
Which RUU are you trying to run? Are you on Windows, and why are you trying to fastboot flash it? If you're on Windows simply double-click the RUU to start the installer. It's a exe file, unless you've pulled the ROM zip from the RUU file.
Also, since you've started a separate thread regarding this same issue, I would stick to it to minimize any confusion instead of posting back & forth. Makes it easier to keep up with what's going on
it's the non-hk from htc's page I'm on mac but I pulled the zip from the exe using parallels desktop, I could try doing it on parallels desktop with the windows exe though
Hi all,
I've tried to install WWE stock rom on this device, but now is bricked. I can get into fastboot and bootloader, but I can't install anything now. I've tried from fastboot to install the one's dedicated to my device from here:
http://forum.xda-developers.com/showthread.php?t=2617159
device info (before trying to re-install) were:
tampered/unlocked
m7 cdug pvt ship s-on rh
hboot: 2.23.000
radio: u2.05.3501.18
open dsp-v28.120.274.0328
qsc-1237.18.19.0528
os-2.25.1402.1
e-mmc-boot 2048mb
cid/mid: HTCCN703
now CID is gone, but it's still unlocked and S-ON, and
hboot is 2.27.0000
radio u3.08.35.07.17
open dsp-v31.120.274.0617
qsc-1237.25.32.0717
os-2.25.1402.1
eMMC-boot 2048mb
PN0771000
How can I restore it in a way, then to install a WWE version?
ady_uaic said:
Hi all,
I've tried to install WWE stock rom on this device, but now is bricked. I can get into fastboot and bootloader, but I can't install anything now. I've tried from fastboot to install the one's dedicated to my device from here:
http://forum.xda-developers.com/showthread.php?t=2617159
device info (before trying to re-install) were:
tampered/unlocked
m7 cdug pvt ship s-on rh
hboot: 2.23.000
radio: u2.05.3501.18
open dsp-v28.120.274.0328
qsc-1237.18.19.0528
os-2.25.1402.1
e-mmc-boot 2048mb
cid/mid: HTCCN703
now CID is gone, but it's still unlocked and S-ON, and
hboot is 2.27.0000
radio u3.08.35.07.17
open dsp-v31.120.274.0617
qsc-1237.25.32.0717
os-2.25.1402.1
eMMC-boot 2048mb
PN0771000
How can I restore it in a way, then to install a WWE version?
Click to expand...
Click to collapse
post here for windows HTC phone mate, you'll get a quicker response, beside, alot of us here are anti-windows phones lol even if you do just live down the road from me: http://forum.xda-developers.com/htc-8x
Seanie280672 said:
post here for windows HTC phone mate, you'll get a quicker response, beside, alot of us here are anti-windows phones lol even if you do just live down the road from me: http://forum.xda-developers.com/htc-8x
Click to expand...
Click to collapse
I'm not sure I follow you. This is 802W, not windows phone.
The error: remote not allowed.
ady_uaic said:
I'm not sure I follow you. This is 802W, not windows phone.
Click to expand...
Click to collapse
Sorry, your cid related to a windows phone when I googled it, ive never seen those details before, I think you've already found everything to do with the 802w, but i'll have a look around too.
Seanie280672 said:
Sorry, your cid related to a windows phone when I googled it, ive never seen those details before, I think you've already found everything to do with the 802w, but i'll have a look around too.
Click to expand...
Click to collapse
thanks a lot mate!
I think the only thing I need is to flash a stock RUU (doesn't matter which version, as long as it works, then to do again all the processes: unlock bootloader, s-off, custom recovery, root, stock WWE RUU).
ady_uaic said:
thanks a lot mate!
I think the only thing I need is to flash a stock RUU (doesn't matter which version, as long as it works, then to do again all the processes: unlock bootloader, s-off, custom recovery, root, stock WWE RUU).
Click to expand...
Click to collapse
trouble is, your current OS is 2.25.1402.1 and thats an OTA not an RUU, you need a full RUU, this one may work:
PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zip http://d-h.st/NAf which is the next full RUU up from yours.
Seanie280672 said:
trouble is, your current OS is 2.25.1402.1 and thats an OTA not an RUU, you need a full RUU, this one may work:
PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zip http://d-h.st/NAf which is the next full RUU up from yours.
Click to expand...
Click to collapse
I already tried that mate, thanks!
it returns after signature checking...:
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
ady_uaic said:
I already tried that mate, thanks!
it returns after signature checking...:
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Click to expand...
Click to collapse
Umm, im a bit confused, its a zip file not an official RUU, im just downloading it to take a closer look, how are you trying to flash it ?
EDIT: ok its an RUU zip, it need to be flashed in fastbootRUU mode, using fastboot commands, bootloader needs to be locked as you are s-on, Its should work as this OTA states that RUU was your next update if you got it via OTA, OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_TO THIS ROM VERSION 2.30.1402.1 --------------------- FROM THIS ROM VERSION-2.25.1402.1 SAME AS YOURS_release_332539.zip - 50.49 MB
Seanie280672 said:
Umm, im a bit confused, its a zip file not an official RUU, im just downloading it to take a closer look, how are you trying to flash it ?
EDIT: ok its an RUU zip, it need to be flashed in fastbootRUU mode, using fastboot commands, bootloader needs to be locked as you are s-on, Its should work as this OTA states that RUU was your next update if you got it via OTA, OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_TO THIS ROM VERSION 2.30.1402.1 --------------------- FROM THIS ROM VERSION-2.25.1402.1 SAME AS YOURS_release_332539.zip - 50.49 MB
Click to expand...
Click to collapse
from fastboot, using the command line:
fastboot flash zip ....zip
I've locked back the bootloader, and still doesn't work:
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
and no, it was an UNICOM version, and my friend tried to update to WWE.
ady_uaic said:
from fastboot, using the command line:
fastboot flash zip ....zip
I've locked back the bootloader, and still doesn't work:
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
and no, it was an UNICOM version, and my friend tried to update to WWE.
Click to expand...
Click to collapse
You cant change to WWE without s-off, tell your friend to leave it alone lol, it requires you to change cid and mid etc first, then flash the corrisponding firmware and then the RUU.
Rename your RUU to rom.zip for ease, then issue these commands :
make sure its this RUU, not the WWE one PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zi p
fastboot oem rebootRUU (case sensetive, type it exactly like that)
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately) HTC typo, should be please flash immediately
Make sure device is still in ruu mode(black HTC screen)
now simply reflash the rom.zip, fastboot flash zip Rom.zip
Let it run and it should finish this time, make sure it says successfull at the end, if it does then fastboot reboot, you'll be full stock, if failed, report back here before doing anything else, dont reboot out of RUU mode.
The first flash is just a preupdate, the 2nd flash flashes the rom and firmware files.
Yes mate, I know that. Now I'm trying to put back any ROM then I will do the right procedure to install WWE.
But, now doesn't work at all. not even with that command (and it's not necessary to rename the zip file, as long as it's only one in the adb folder). I already tried that, and it doesn't work .
L.E. oh, wait mate! I think it works now! I'm waiting for the installation to be finished. do you have a good tutorial to upgrade to WWE version?
ady_uaic said:
Yes mate, I know that. Now I'm trying to put back any ROM then I will do the right procedure to install WWE.
But, now doesn't work at all. not even with that command (and it's not necessary to rename the zip file, as long as it's only one in the adb folder). I already tried that, and it doesn't work .
L.E. oh, wait mate! I think it works now! I'm waiting for the installation to be finished. do you have a good tutorial to upgrade to WWE version?
Click to expand...
Click to collapse
Im not really familiar with the dual sim versions, dont know how to s-off them, all the knowlege im giving you is just based on my M7, but to convert you will need to get s-off first, change your cid and mid to match the WWE RUU and then you'll need to flash the WWE full RUU as close to as possible to the version number you have now so that the firmware swap over goes smoothly.
Seanie280672 said:
Im not really familiar with the dual sim versions, dont know how to s-off them, all the knowlege im giving you is just based on my M7, but to convert you will need to get s-off first, change your cid and mid to match the WWE RUU and then you'll need to flash the WWE full RUU as close to as possible to the version number you have now so that the firmware swap over goes smoothly.
Click to expand...
Click to collapse
will do, thanks!
ady_uaic said:
will do, thanks!
Click to expand...
Click to collapse
When the flash has finished, let me know if it boots ok please and was successful.
Seanie280672 said:
When the flash has finished, let me know if it boots ok please and was successful.
Click to expand...
Click to collapse
with the chinese version yes, it boots ok. now I'm trying to use this tutorial for WWE: http://forum.xda-developers.com/showthread.php?t=2559891
ady_uaic said:
with the chinese version yes, it boots ok. now I'm trying to use this tutorial for WWE: http://forum.xda-developers.com/showthread.php?t=2559891
Click to expand...
Click to collapse
just had a quick read through it, I would be cautious flashing HBOOT before getting s-off, if I was you I would use the moonshine s-off method for your HBOOT and device version first before flashing the HBOOT, make sure these have not changed after flashing an updated RUU.
A bad HBOOT flash will hard brick your device.
Seanie280672 said:
just had a quick read through it, I would be cautious flashing HBOOT before getting s-off, if I was you I would use the moonshine s-off method for your HBOOT and device version first before flashing the HBOOT, make sure these have not changed after flashing an updated RUU.
A bad HBOOT flash will hard brick your device.
Click to expand...
Click to collapse
I will have a look right now. what do you mean by device version?
ady_uaic said:
what do you mean by device version?
Click to expand...
Click to collapse
sorry, forget that, they are all for the 802w, threw me out a bit as he labelled the moonshine one as (for the 802w version)
ps, firewater no longer works, its been discontinued, lets hope your not on that HBOOT. :fingers-crossed:
Seanie280672 said:
sorry, forget that, they are all for the 802w, threw me out a bit as he labelled the moonshine one as (for the 802w version)
ps, firewater no longer works, its been discontinued, lets hope your not on that HBOOT. :fingers-crossed:
Click to expand...
Click to collapse
problem solved. now it has wwe. thanks mate!
Hi fellas,
Hoping to get some direction on my problem. My HTC One was flashed to T-Mobile or some GSM version couple of years ago. Now I've tried to flash it back to Sprint, following directions from here, it didn't work, now I can only get to the bootloader on my HTC One that shows Tampered, Relocked, S-On.
When I tried to flash the rom files using instruction on that page, I get
Code:
(bootloader) Read zipped android_info fail
Failed (status read failed (Too many Links))
I tried to use RUU update tool, it shows my current Non-sprint rom version is: 4.06.651.4 then tries to update to 1.29.651.10, which then fails...
Can someone point me in the right direction on what steps I need to take to correctly flash a stock (or any Sprint) rom on this?
Thank you in advance...
http://forum.xda-developers.com/showthread.php?t=2658910
Sloth said:
http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
Thank you sir!