Related
Hello everyone,
I have an HTC One 802w bought from china unicom version.
I followed this tutorial to S-OFF which worked successfully after unlocking with the HTCDEV method
I then went about changing it to a Google Edition using this tutorial , all was going smoothly until I needed to change the model id using this tutorial.
I believe writing the new model number failed here.
I rebooted using
fastboot oem rebootRUU
Click to expand...
Click to collapse
and got the htc logo up and then I began transferring the modified zip downloaded from that tutorial and I got a 75% status bar at which point under instruction from another poster on that thread manually rebooted.
Now at this point I have an HTC One with a black screen and no charge light, I can't see anything but I can get it recognised by the PC so her is my getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3510mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Can you offer me any help here, it would be greatly appreciated, in NZ where I live these phones cost over $1000 to import.
Cheers
I think you messed partition table . Now you have two choices. One is to flash original firmware and second is to search to find right partition to change model id. That happent because our partition table is different from international one. Anyway congrats for courage of trying that and my advice is second choice. I myself will search for that.
edit: found app in g play : partition table, getting more info
edit2: from what can i see on tutorial you folow >>>> '' Step 3: Change Your Model ID (if Necessary)
Changing your MID is actually not necessary, even if you have a different Model ID. I'll leave this here just in case you want to check, and because we still need to connect our phone and open a command prompt. '' WHY DID YOU TRYED ?
edit3: i think you must write cid to 11111111 and flash that google RUU.
Sent from my HTC 802w
criszz said:
I think you messed partition table . Now you have two choices. One is to flash original firmware and second is to search to find right partition to change model id. That happent because our partition table is different from international one. Anyway congrats for courage of trying that and my advice is second choice. I myself will search for that.
edit: found app in g play : partition table, getting more info
edit2: from what can i see on tutorial you folow >>>> '' Step 3: Change Your Model ID (if Necessary)
Changing your MID is actually not necessary, even if you have a different Model ID. I'll leave this here just in case you want to check, and because we still need to connect our phone and open a command prompt. '' WHY DID YOU TRYED ?
edit3: i think you must write cid to 11111111 and flash that google RUU.
Sent from my HTC 802w
Click to expand...
Click to collapse
Thanks for your reply Criszz,
I originally tried it without changing my model number but it failed without doing so.
I have tried a huge multitude of things of being writing a new cid but when trying to write 11111111 as you suggested i get
fastboot oem writecid 11111111
...
(bootloader) Start Verify: -1
OKAY [ 0.040s]
finished. total time: 0.044s
Click to expand...
Click to collapse
It seems the whole boot loader is fuct. I have tried heaps of roms with different variations of fastboot update, fastboot flashall, fastboot flash **individual img's** nothing seems to work.
Anymore advice or greatly apprecated I will try whatever anyone can throw at me.
Douggyt said:
Thanks for your reply Criszz,
I originally tried it without changing my model number but it failed without doing so.
I have tried a huge multitude of things of being writing a new cid but when trying to write 11111111 as you suggested i get
It seems the whole boot loader is fuct. I have tried heaps of roms with different variations of fastboot update, fastboot flashall, fastboot flash **individual img's** nothing seems to work.
Anymore advice or greatly apprecated I will try whatever anyone can throw at me.
Click to expand...
Click to collapse
flash all firmware from scratch
http://forum.xda-developers.com/showpost.php?p=44033765&postcount=765
criszz said:
flash all firmware from scratch
http://forum.xda-developers.com/showpost.php?p=44033765&postcount=765
Click to expand...
Click to collapse
Thanks again, trying that now, I think the biggest problem is the bootloader rebooting ready for RUU will update here shortly with the exact results.
Douggyt said:
Thanks again, trying that now, I think the biggest problem is the bootloader rebooting ready for RUU will update here shortly with the exact results.
Click to expand...
Click to collapse
Results
fastboot oem rebootRUU
... INFOStart Verify: -1
OKAY [ 0.044s]
finished. total time: 0.045s
Click to expand...
Click to collapse
fastboot flash zip firmware.zip
< waiting for device >
sending 'zip' (40930 KB)... OKAY [ 4.792s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 4.794s
Click to expand...
Click to collapse
fastboot reboot
rebooting...
finished. total time: 0.045s
Click to expand...
Click to collapse
Any thoughts?, thanks again.
criszz said:
flash all firmware from scratch
http://forum.xda-developers.com/showpost.php?p=44033765&postcount=765
Click to expand...
Click to collapse
Sorry I didn't reply with a quote so wasn't sure you would see my update.
that must be working, try another firmware or flash ruu.
did you runn that command as post said TWICE?
criszz said:
that must be working, try another firmware or flash ruu.
did you runn that command as post said TWICE?
Click to expand...
Click to collapse
Apologies, i just put it one return for the second command buut yes each time i run it I get
sending 'zip' (40930 KB)... OKAY [ 4.220s]
writing 'zip'... FAILED (remote: not allowed)
Click to expand...
Click to collapse
Am downloadling some other firmwares to try.
I am still less than an amatuer when it comes to doing these things but the more I read I'm guessing the is restarting really quickly rather than going into Fastboot or Ruu.
When i hold down the power and down vol it quickly disconnects then reconnects to the pc.
Look forward to your next thought and of course will update straight away if one of the other firmwares help.
Cheers
You tried to install on Dual Sim firmware from HTC One. Of course it will not work for you. Firmware from the HTC One does not fit into the HTC Dual Sim.
In addition, you have to reinstall native hboot one that was in the firmware HTC One. And this is very dangerous. Restoring the damaged hboot at home is almost impossible.
drpweb said:
You tried to install on Dual Sim firmware from HTC One. Of course it will not work for you. Firmware from the HTC One does not fit into the HTC Dual Sim.
In addition, you have to reinstall native hboot one that was in the firmware HTC One. And this is very dangerous. Restoring the damaged hboot at home is almost impossible.
Click to expand...
Click to collapse
criszz said:
that must be working, try another firmware or flash ruu.
did you runn that command as post said TWICE?
Click to expand...
Click to collapse
Thanks for your input here guys, as drpweb stated it had the wrong firmware put on it.
After alot of trial and error I have sent it away to be flashed back to stock, if the company come through for me I will put up their details and costs here in case anyone else finds themselves in the same situation.
Cheers
Do you have solved this probelem
Douggyt said:
Thanks for your input here guys, as drpweb stated it had the wrong firmware put on it.
After alot of trial and error I have sent it away to be flashed back to stock, if the company come through for me I will put up their details and costs here in case anyone else finds themselves in the same situation.
Cheers
Click to expand...
Click to collapse
I have the same problem like you? Did you solved it?
When yes, how to do that?
theFAY89 said:
I have the same problem like you? Did you solved it?
When yes, how to do that?
Click to expand...
Click to collapse
I have sent the phone away to multiple repair agents even authorised HTC agents and no one can seem to reflash the chinese dual sim 802w's yet but fingers crossed soon.
I would just be very careful whom you send it to check with HTC they are authorised, I think Taiwan would be your best bet, thats where im going to try next will update this post with results and contact details of the repairer if successful.
Cheers
Douggyt said:
I have sent the phone away to multiple repair agents even authorised HTC agents and no one can seem to reflash the chinese dual sim 802w's yet but fingers crossed soon.
I would just be very careful whom you send it to check with HTC they are authorised, I think Taiwan would be your best bet, thats where im going to try next will update this post with results and contact details of the repairer if successful.
Cheers
Click to expand...
Click to collapse
I had the same issue. My Phone got repaired by doing a boardswap. Gonna pick it up today, no idea about the costs yet.
WreckTangle said:
I had the same issue. My Phone got repaired by doing a boardswap. Gonna pick it up today, no idea about the costs yet.
Click to expand...
Click to collapse
Thanks for the feedback WreckTangle (Dig the handle btw)
It would be great if its a successful repair if you could let me know the contact details of the repair agent and what it cost you.
The repair agent (HTC Authorized and Recommended) I sent it to couldn't seem to source any parts, they also seemingly couldn't be bothered trying.
Cheers
Douggyt said:
Hello everyone,
I have an HTC One 802w bought from china unicom version.
I followed this tutorial to S-OFF which worked successfully after unlocking with the HTCDEV method
I then went about changing it to a Google Edition using this tutorial , all was going smoothly until I needed to change the model id using this tutorial.
I believe writing the new model number failed here.
I rebooted using and got the htc logo up and then I began transferring the modified zip downloaded from that tutorial and I got a 75% status bar at which point under instruction from another poster on that thread manually rebooted.
Now at this point I have an HTC One with a black screen and no charge light, I can't see anything but I can get it recognised by the PC so her is my getvar all
Can you offer me any help here, it would be greatly appreciated, in NZ where I live these phones cost over $1000 to import.
Cheers
Click to expand...
Click to collapse
1. extract firmware.zip from OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.39.1402.1-2.36.1402.1_release_339019
2.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
3. :victory:
style_arun said:
1. extract firmware.zip from OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.39.1402.1-2.36.1402.1_release_339019
2.
3. :victory:
Click to expand...
Click to collapse
I have the same problem... Black screen, no charge light, but PC connection sound. Fastboot working.
I can't flash firmware zip (error: not allowed)
Any update??
Got the same problem here. Any update??
Alright guys. I've had this problem exactly 12 months ago. after I flashed a wrong RUU or something. I was told there was no solution. I am checking back now and see that there is still no solution. Is my HTC One 802W officially a paperweight?
I am having the exactly same problem as discussed here. Anyone on this page got the solution or know the solution or successfully repaired by an external expert from shop please tell the solution...
Hi everyone,
I'm having some issues with my HTC One and might need to send it back for Warranty repair. I can't find the RUU anywhere for Three UK.
Does anyone know a way for me to unroot my HTC One, so to speak?
I am a bit of a noob, so go easy on me!
Thanks.
mrgreeny said:
Hi everyone,
I'm having some issues with my HTC One and might need to send it back for Warranty repair. I can't find the RUU anywhere for Three UK.
Does anyone know a way for me to unroot my HTC One, so to speak?
I am a bit of a noob, so go easy on me!
Thanks.
Click to expand...
Click to collapse
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)
nkk71 said:
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)
Click to expand...
Click to collapse
So is your route not possible with Windows 8, then?
mrgreeny said:
So is your route not possible with Windows 8, then?
Click to expand...
Click to collapse
The main problem is Win8.1, it should work with Win8 (as far as most users said)... if you do get stuck just have an Ubuntu Live USB ready (it's under the FAQs), Ubuntu won't give you a hard time with drivers etc.
nkk71 said:
The main problem is Win8.1, it should work with Win8 (as far as most users said)... if you do get stuck just have an Ubuntu Live USB ready (it's under the FAQs), Ubuntu won't give you a hard time with drivers etc.
Click to expand...
Click to collapse
Ok, thank you!
nkk71 said:
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)
Click to expand...
Click to collapse
(Sorry for double post)
So I don't have a RUU for Three UK, so I'd go down the CWM route? I believe my thing is x.xx.771 from what I've read.
Then all I need to do is follow those steps in the fourth post for the CWM route, and then I'll be completed unrooted and hopefully back to normal for warranty repairs?
mrgreeny said:
(Sorry for double post)
So I don't have a RUU for Three UK, so I'd go down the CWM route? I believe my thing is x.xx.771 from what I've read.
Then all I need to do is follow those steps in the fourth post for the CWM route, and then I'll be completed unrooted and hopefully back to normal for warranty repairs?
Click to expand...
Click to collapse
Three UK is CID H3G__001 so yes, use the CWM method and you can even use the files mentioned in post #4, since the example I was using is Three UK.
About the S-On part: from what I've seen, the UK seems pretty lenient with all that, but if you do intend on going S-Off to S-On, you do so as mentioned in the guide before any OTA to 3.xx
nkk71 said:
Three UK is CID H3G__001 so yes, use the CWM method and you can even use the files mentioned in post #4, since the example I was using is Three UK.
About the S-On part: from what I've seen, the UK seems pretty lenient with all that, but if you do intend on going S-Off to S-On, you do so as mentioned in the guide before any OTA to 3.xx
Click to expand...
Click to collapse
I assume to make sure it's definitely safe to return for warranty I should go back to S-On, though?
Is there any risk of bricking the device?
mrgreeny said:
Is there any risk of bricking the device?
Click to expand...
Click to collapse
Can I say that 100% -> no, you could have a power outage, your favourite pet, your "favourite" child , mess with your phone / usb / pc connection at exactly the right (wrong) nanosecond when hboot is being flashed. which may or may not result in a brick.
So I scared you a little there
But in general, no, there is no bricking involved as long as you flash things made for your phone. (ie don't go flash HTC Droid stuff on the M7)
at least nobody has complained in my thread causing a brick.
mrgreeny said:
I assume to make sure it's definitely safe to return for warranty I should go back to S-On, though?
Click to expand...
Click to collapse
If you want your phone to look 100% out of the box, I would say yes to the s-on part, though most posts about UK repairs have shown that they don't really care. but no harm in going S-On.
BUT, please follow the guide correctly, if you have questions, feel free to ask.
the guide has worked for many people (and was actually written after having it done in various threads, so it's sort of a result of experience, not only theory),
but if something isnt clear or doesn't make sense, you should ask; I have no issues with people asking why THIS, and why THAT, and why NOW
I prefer a question before, rather than a question after .... (yeah so I skipped step x cause I thought I didn't need it... so now what ... and yeah I didnt bother with reading it once or twice including the FAQs cause you probably wrote them for someone else )
nkk71 said:
Can I say that 100% -> no, you could have a power outage, your favourite pet, your "favourite" child , mess with your phone / usb / pc connection at exactly the right (wrong) nanosecond when hboot is being flashed. which may or may not result in a brick.
No silly childrena round
So I scared you a little there
But in general, no, there is no bricking involved as long as you flash things made for your phone. (ie don't go flash HTC Droid stuff on the M7)
at least nobody has complained in my thread causing a brick.
Click to expand...
Click to collapse
Haha besides those points obviously! Thank you!
nkk71 said:
If you want your phone to look 100% out of the box, I would say yes to the s-on part, though most posts about UK repairs have shown that they don't really care. but no harm in going S-On.
BUT, please follow the guide correctly, if you have questions, feel free to ask.
the guide has worked for many people (and was actually written after having it done in various threads, so it's sort of a result of experience, not only theory),
but if something isnt clear or doesn't make sense, you should ask; I have no issues with people asking why THIS, and why THAT, and why NOW
I prefer a question before, rather than a question after .... (yeah so I skipped step x cause I thought I didn't need it... so now what ... and yeah I didnt bother with reading it once or twice including the FAQs cause you probably wrote them for someone else )
Click to expand...
Click to collapse
Thank you very much. I shall do it later today or on Monday. Hopefully it will all go to plan!
mrgreeny said:
Haha besides those points obviously! Thank you!
Thank you very much. I shall do it later today or on Monday. Hopefully it will all go to plan!
Click to expand...
Click to collapse
sure no problem,
remember: if something doesn't make sense to you, go ahead and ask.... no harm in asking
nkk71 said:
sure no problem,
remember: if something doesn't make sense to you, go ahead and ask.... no harm in asking
Click to expand...
Click to collapse
Can't get S-Off to work. Just posted in http://forum.xda-developers.com/showthread.php?t=2632351&page=45 still waiting on a reply.
You may have an idea?
C:\Users\Michael>adb reboot
C:\Users\Michael>adb wait-for-device push Desktop/firewater /data/local/tmp
3116 KB/s (4432776 bytes in 1.389s)
C:\Users\Michael>adb shell
[email protected]/# su
su
[email protected]/# chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]/# /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.4.6 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
C:\Users\Michael>
Click to expand...
Click to collapse
Any ideas what's happening here? If I leave it too long on the Yes/No it also kicks back to C:\ Have to type Yes really quickly.
mrgreeny said:
Can't get S-Off to work. Just posted in http://forum.xda-developers.com/showthread.php?t=2632351&page=45 still waiting on a reply.
You may have an idea?
Any ideas what's happening here? If I leave it too long on the Yes/No it also kicks back to C:\ Have to type Yes really quickly.
Click to expand...
Click to collapse
Not really, but can you post output of fastboot getvar all and which version of viperone you're using?
nkk71 said:
Not really, but can you post output of fastboot getvar all and which version of viperone you're using?
Click to expand...
Click to collapse
Just done a nandroid backup, and when rebooting it said I needed to fix root?
For firewater to work, should I change from CWM to TWRP and use ARHD do you think?
As for the fastboot getvar all, it's hanging on < waiting for device >
I'm using ViperOne 5.7.0
edit; fastboot getvar all worked earlier today just before I used firewater
edit2; DUH! Forgot to boot to Fastboot haha!!!
C:\Users\Michael>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
mrgreeny said:
Just done a nandroid backup, and when rebooting it said I needed to fix root?
For firewater to work, should I change from CWM to TWRP and use ARHD do you think?
As for the fastboot getvar all, it's hanging on < waiting for device >
I'm using ViperOne 5.7.0
edit; fastboot getvar all worked earlier today just before I used firewater
edit2; DUH! Forgot to boot to Fastboot haha!!!
Click to expand...
Click to collapse
(bootloader) version-main: 2.24.771.3
your best bet would be with a 2.24 ROM, try this one:
Android_Revolution_HD-One_13.4_(4.2.2).zip 1.01 GB
https://mega.co.nz/#!3VVEjKiJ!ekbbghB0fEx-aSRyppzjG3ITeuAT4xEoO9gXBo0vPpI
MD5: D8529CA3F59CDFA4947FD76333B2F5F8
credits to @mike1986.
then use rumrunner of firewater.
Good Luck
nkk71 said:
(bootloader) version-main: 2.24.771.3
your best bet would be with a 2.24 ROM, try this one:
Android_Revolution_HD-One_13.4_(4.2.2).zip 1.01 GB
https://mega.co.nz/#!3VVEjKiJ!ekbbghB0fEx-aSRyppzjG3ITeuAT4xEoO9gXBo0vPpI
MD5: D8529CA3F59CDFA4947FD76333B2F5F8
credits to @mike1986.
then use rumrunner of firewater.
Good Luck
Click to expand...
Click to collapse
Can I flash this ROM with CWM?
Also, on reboot it says "Root access possibly lost. Fix? Yes - Fix Root (/system/xbin/su)
any ideas?
mrgreeny said:
Can I flash this ROM with CWM?
Also, on reboot it says "Root access possibly lost. Fix? Yes - Fix Root (/system/xbin/su)
any ideas?
Click to expand...
Click to collapse
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.
nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.
Click to expand...
Click to collapse
I will keep you up to date.. Thank you very much
nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.
Click to expand...
Click to collapse
S-Off done - now I'm downloading all the files for when they're needed.
Which stock recovery (From http://d-h.st/users/Guich/Stock Recovery M7) should I use?
version-main in fastboot getvar all is version-main: 2.24.771.3 so should I download that from the above link?
nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.
Click to expand...
Click to collapse
Okay. this is where I'm stuck at
C:\Users\Michael>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Users\Michael>fastboot flash zip ruu.zip
< waiting for device >
sending 'zip' (104391 KB)...
OKAY [ 5.840s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 6.033s
C:\Users\Michael>fastboot flash zip ruu.zip
sending 'zip' (104391 KB)...
OKAY [ 5.645s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 5.843s
C:\Users\Michael>fastboot flash zip ruu.zip
sending 'zip' (104391 KB)...
OKAY [ 5.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 6.077s
C:\Users\Michael>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.044s]
finished. total time: 0.044s
Click to expand...
Click to collapse
Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
ERROR [140]: BOOTLOADER VERSION ERROR
Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
Click to expand...
Click to collapse
Post getvar all.
Post screen shot of bootloader.
Are you unlocked/relocked/locked.
Are you S-On/S-Off.
Have you changed Cidnum or modelid.
What rom are you currently using, is it original stock/custom.
Tell the buyer that you have a custom rom installed and would he/she like you to return it to stock.
He/she might want to root it the moment they buy it.
Sent from my Nexus 7 using XDA Premium HD app
bored_stupid said:
Post getvar all.
Post screen shot of bootloader.
Are you unlocked/relocked/locked.
Are you S-On/S-Off.
Have you changed Cidnum or modelid.
What rom are you currently using, is it original stock/custom.
Tell the buyer that you have a custom rom installed and would he/she like you to return it to stock.
He/she might want to root it the moment they buy it.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Relocked
hboot 1.44
S-On
Didn't change cid or modelid
Latest Venom Rom was on it..
This is what I get trying installing RUU I downloaded:
ERROR [140]: BOOTLOADER VERSION ERROR
Rolando88 said:
Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
ERROR [140]: BOOTLOADER VERSION ERROR
Click to expand...
Click to collapse
that RUU is no good in any case, you need to use the 1.28.401.7 version (provided you meet the requirements, which can only be checked using the output of "fastboot getvar all")
and with S-On, your phone will only show RELOCKED not LOCKED, so the buyer will know that you had it unlocked at one point.
Post a fastboot getvar all please
Sent from my Nexus 7 using XDA Premium HD app
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW909481
(bootloader) imei: *************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3879mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.042s
Try this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
And this guide to flash the RUU
http://www.htc1guru.com/downloads/ruu-zip-downloads/
Sent from my Nexus 7 using XDA Premium HD app
bored_stupid said:
Try this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
And this guide to flash the RUU
http://www.htc1guru.com/downloads/ruu-zip-downloads/
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
Of course it fails. You are trying to downgrade your phone while you are S-ON.
You are trying to flash:
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4
but you version is 1.29.xxxxx.
1.20 is less than 1.29. You could only do that if you were S-OFF. So you need to download the same version or higher than yours...so 1.29.401.12 or higher.
Deleted
Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
You need to unlock your bootloader again. Flash recovery and then s-off follow this guide
http://www.htc1guru.com/guides/get-s-off/
Then follow the guides to return to stock.
Sent from my HTC One using XDA Premium HD app
gartner83 said:
Of course it fails. You are trying to downgrade your phone while you are S-ON.
You are trying to flash:
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4
but you version is 1.29.xxxxx.
1.20 is less than 1.29. You could only do that if you were S-OFF. So you need to download the same version or higher than yours...so 1.29.401.12 or higher.
Click to expand...
Click to collapse
I got this error message when I tried to flash
RUU Zip M7 UL JB 50 HTC Europe 1.29.401.16 R Radio 4A.14.3250.13 10.33.1150.01 Release 318486 Signed 2 4 Decrypted
Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
Easiest thing to do is S-OFF the phone, then you can flash any ruu you want without an issue.
Then once you've flashed it, you can put s-on back on if you want.
That's what I did when sent my phone back to HTC for warranty.
danlat1415 said:
Easiest thing to do is S-OFF the phone, then you can flash any ruu you want without an issue.
Then once you've flashed it, you can put s-on back on if you want.
That's what I did when sent my phone back to HTC for warranty.
Click to expand...
Click to collapse
I agree, this I think also, is the best solution. After that, you can also set your booloader status to "LOCKED", as if it was never touched.
gartner83 said:
I agree, this I think also, is the best solution. After that, you can also set your booloader status to "LOCKED", as if it was never touched.
Click to expand...
Click to collapse
You can even leave leave the phone as s-off.
Won't be an issue, still covered by HTC warranty. They only care about boot loader status.
I tried with the all in one tool pffff
\adb push revone /data/local/tmp/
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
adb reboot
adb shell /data/local/tmp/./revone -s 0 -u
still S-On this should work for hboot 1.44
Rolando88 said:
I tried with the all in one tool pffff
\adb push revone /data/local/tmp/
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
adb reboot
adb shell /data/local/tmp/./revone -s 0 -u
still S-On this should work for hboot 1.44
Click to expand...
Click to collapse
what ROM are you on?
Recommend this one for revone: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250
otherwise try http://firewater-soff.com/
ok it finally worked!! got S-Off with rumrunner!
Now i Installed RUU but when i started Phone and walked through the wizard i got on a page with:
Tell HTC:
This is a test device: Tell HTC is automatically enabled so that HTC can collect critical information aboout the device during testing. It is not possible to turn this ffeature on on this Phone...
I guess I still don't have a stock rom on it now!!!? Anyone knows what i have to do?!
Rolando88 said:
ok it finally worked!! got S-Off with rumrunner!
Now i Installed RUU but when i started Phone and walked through the wizard i got on a page with:
Tell HTC:
This is a test device: Tell HTC is automatically enabled so that HTC can collect critical information aboout the device during testing. It is not possible to turn this ffeature on on this Phone...
I guess I still don't have a stock rom on it now!!!? Anyone knows what i have to do?!
Click to expand...
Click to collapse
This is normal, it's due to s-off.
Sent from my HTC One using Tapatalk
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.
Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.
Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-
Hello all.
The name is Daecca and first off, this was not my first phone to Costumize with Rom. or just ROOT for that matter.
But, it was the first HTC to root.
Now after doing everything by the proverbial book (Or sites) HTCdev and such.
And rooting with SuperSU (2. something as that was the newest version. I have a softbrick.
Meaning, the root removed my OS. I have tried all kinds of things found on this forum. posts from 2012 to 2015 I found here., But to no avail.
Here's the specs I can read in my Hboot.
***Tampered ***
*** Relocked ***
M7_UL PVT SHIP s-on RH
HBOOT-1.61.000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
os-
eMMC-boot 2048MB
Nov 16 2015 20:23:35.129
below that are the usual options.
I have gotten multiple errors while trying to flash through the bootloaderRUU option.
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
< waiting for device >
sending 'exe' (1014749 KB)...
OKAY [ 52.421s]
writing 'exe'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 135.899s
and
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe
sending 'exe' (1494393 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.268s
the later one was I'm guessing a wrong firmware as that was not Europe.
I am in the netherlands. So guessing europe should be it.
I have tried the Erase Cache thing aswell as the Restore thread (WHich is currently open on my computer as a separate tab)
Could anyone help me in the right Direction? I'm off to sports now and will check in a couple hours.
This is about my main phone so I am hoping for a swift solution. But I know I need patience for this.
Thanks in advance.
Daecca
PS: I know I could have responded in a different thread, But my loading time on PC is crazy atm due to all the stuff I have been looking for and downloading.
DaeccaD said:
Hello all.
The name is Daecca and first off, this was not my first phone to Costumize with Rom. or just ROOT for that matter.
But, it was the first HTC to root.
Now after doing everything by the proverbial book (Or sites) HTCdev and such.
And rooting with SuperSU (2. something as that was the newest version. I have a softbrick.
Meaning, the root removed my OS. I have tried all kinds of things found on this forum. posts from 2012 to 2015 I found here., But to no avail.
Here's the specs I can read in my Hboot.
***Tampered ***
*** Relocked ***
M7_UL PVT SHIP s-on RH
HBOOT-1.61.000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
os-
eMMC-boot 2048MB
Nov 16 2015 20:23:35.129
below that are the usual options.
I have gotten multiple errors while trying to flash through the bootloaderRUU option.
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
< waiting for device >
sending 'exe' (1014749 KB)...
OKAY [ 52.421s]
writing 'exe'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 135.899s
and
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe
sending 'exe' (1494393 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.268s
the later one was I'm guessing a wrong firmware as that was not Europe.
I am in the netherlands. So guessing europe should be it.
I have tried the Erase Cache thing aswell as the Restore thread (WHich is currently open on my computer as a separate tab)
Could anyone help me in the right Direction? I'm off to sports now and will check in a couple hours.
This is about my main phone so I am hoping for a swift solution. But I know I need patience for this.
Thanks in advance.
Daecca
PS: I know I could have responded in a different thread, But my loading time on PC is crazy atm due to all the stuff I have been looking for and downloading.
Click to expand...
Click to collapse
Are you using htc_fastboot?? Doesn't look like it!
DaeccaD said:
Hello all.
The name is Daecca and first off, this was not my first phone to Costumize with Rom. or just ROOT for that matter.
But, it was the first HTC to root.
Now after doing everything by the proverbial book (Or sites) HTCdev and such.
And rooting with SuperSU (2. something as that was the newest version. I have a softbrick.
Meaning, the root removed my OS. I have tried all kinds of things found on this forum. posts from 2012 to 2015 I found here., But to no avail.
Here's the specs I can read in my Hboot.
***Tampered ***
*** Relocked ***
M7_UL PVT SHIP s-on RH
HBOOT-1.61.000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
os-
eMMC-boot 2048MB
Nov 16 2015 20:23:35.129
below that are the usual options.
I have gotten multiple errors while trying to flash through the bootloaderRUU option.
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
< waiting for device >
sending 'exe' (1014749 KB)...
OKAY [ 52.421s]
writing 'exe'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 135.899s
and
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe
sending 'exe' (1494393 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.268s
the later one was I'm guessing a wrong firmware as that was not Europe.
I am in the netherlands. So guessing europe should be it.
I have tried the Erase Cache thing aswell as the Restore thread (WHich is currently open on my computer as a separate tab)
Could anyone help me in the right Direction? I'm off to sports now and will check in a couple hours.
This is about my main phone so I am hoping for a swift solution. But I know I need patience for this.
Thanks in advance.
Daecca
PS: I know I could have responded in a different thread, But my loading time on PC is crazy atm due to all the stuff I have been looking for and downloading.
Click to expand...
Click to collapse
First thing you should do is post your fastboot getvar all, but erase your IMEI and serial no from it. That way we will be able to determine the exact RUU for you. Second - and this is confusing, you flashed SU, and that erased your ROM? Impossible, you did something wrong, or you just ended up in a bootloop
Third - you don't flash a .exe file via fastboot. Exe is executable file which you execute via wizzard it comes with.
mb_guy said:
Are you using htc_fastboot?? Doesn't look like it!
Click to expand...
Click to collapse
Was not sure about that since I got two. one was htc and one was not, one didn't work.
donkeykong1 said:
First thing you should do is post your fastboot getvar all, but erase your IMEI and serial no from it. That way we will be able to determine the exact RUU for you. Second - and this is confusing, you flashed SU, and that erased your ROM? Impossible, you did something wrong, or you just ended up in a bootloop
Third - you don't flash a .exe file via fastboot. Exe is executable file which you execute via wizzard it comes with.
Click to expand...
Click to collapse
C:\Android\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.647s
PS: I flashed superSU using CWM now, it could be the SU I used was not superSU and something that deleted my OS. as shown in the first post. there is no OS. (Atleast, it doesnt show in HBOOT)
and there was before I put up SU
PPS: I also tried several ZIP files. similar filenames. all with the same happening.
C:\Android\fastboot-htc\fastboot>fastboot flash zip OTA_M7_UL_JB_50_S_HTC_Europe_2.24.401.1-1.29.401.12_P2_release_324936_signedma8j1sa3e2o09s35.zip
sending 'zip' (426741 KB)...
OKAY [ 17.450s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 59.543s
Next try this time with the fastboot that was saved as HTC fastboot. still this. probably the wrong ROM?
PS: Also, thinking it indeed wasn't the superSU, I might have wiped the wrong thing (wanting to wipe cache and accidentally wiped the os.)
DaeccaD said:
C:\Android\fastboot-htc\fastboot>fastboot flash zip OTA_M7_UL_JB_50_S_HTC_Europe_2.24.401.1-1.29.401.12_P2_release_324936_signedma8j1sa3e2o09s35.zip
sending 'zip' (426741 KB)...
OKAY [ 17.450s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 59.543s
Next try this time with the fastboot that was saved as HTC fastboot. still this. probably the wrong ROM?
PS: Also, thinking it indeed wasn't the superSU, I might have wiped the wrong thing (wanting to wipe cache and accidentally wiped the os.)
Click to expand...
Click to collapse
Find 7.19.401.51 signed http://forum.xda-developers.com/showthread.php?t=3053944, and try to flash that, but be sure to use htc fastboot
donkeykong1 said:
Find 7.19.401.51 signed http://forum.xda-developers.com/showthread.php?t=3053944, and try to flash that, but be sure to use htc fastboot
Click to expand...
Click to collapse
Thank you DonkeyKong will try this as soon as possible. My computer just froze while trying the first time. now it won't see the usb in fastboot on phone. Gonna check out what happened with my drivers. Soon as I know more on it working or not I will let you know!
DaeccaD said:
Thank you DonkeyKong will try this as soon as possible. My computer just froze while trying the first time. now it won't see the usb in fastboot on phone. Gonna check out what happened with my drivers. Soon as I know more on it working or not I will let you know!
Click to expand...
Click to collapse
Good luck mate [emoji106] [emoji4]
donkeykong1 said:
Find 7.19.401.51 signed http://forum.xda-developers.com/showthread.php?t=3053944, and try to flash that, but be sure to use htc fastboot
Click to expand...
Click to collapse
Hey, am I doing something wrong here or?
C:\Android\fastboot-htc\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
load_file: could not allocate 1688539299 bytes
error: cannot load 'PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip'
Thats what I got
And then I read instead of jumping in. It's doing what it needs to do now. (Just got the growing list)
DaeccaD said:
Hey, am I doing something wrong here or?
C:\Android\fastboot-htc\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
load_file: could not allocate 1688539299 bytes
error: cannot load 'PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip'
Thats what I got
And then I read instead of jumping in. It's doing what it needs to do now. (Just got the growing list)
Click to expand...
Click to collapse
Did you flash it in RUU mode?
fastboot oem rebootRUU
donkeykong1 said:
Did you flash it in RUU mode?
fastboot oem rebootRUU
Click to expand...
Click to collapse
Yes, doing it in that way. it worked out in the end. now the cmd prompt is ready. giving me the ability to type again, the phone shows the RUU HTC logo with a green bar which is now at about 90% filled up. Has been like that for about 15 minutes now. maybe 10.
Can I proceed with rebooting it into bootloader or should I wait? (Waiting could just get me an alnighter and not sure if the bar should fill up even if the CMD is done)
DaeccaD said:
Yes, doing it in that way. it worked out in the end. now the cmd prompt is ready. giving me the ability to type again, the phone shows the RUU HTC logo with a green bar which is now at about 90% filled up. Has been like that for about 15 minutes now. maybe 10.
Can I proceed with rebooting it into bootloader or should I wait? (Waiting could just get me an alnighter and not sure if the bar should fill up even if the CMD is done)
Click to expand...
Click to collapse
What exactly does cmd say at the bottom? If it' something alongst "finished..." you're good to go. Just type fastboot reboot, and enjoy
donkeykong1 said:
What exactly does cmd say at the bottom? If it' something alongst "finished..." you're good to go. Just type fastboot reboot, and enjoy
Click to expand...
Click to collapse
(bootloader) ...... Successful
OKAY
Flash Zip Complete
Execution time is 536(s)
And indeed, looked at that link of yours and gathered from that that indeed I should reboot it into bootloader.
Right now, my phone is working on upgrading 252 android apps.
Thank you very much!
Tomorrow I am going to try again with the superSU and CWMtouch. (Unless you think I should use another recovery which would be better) I want it rooted because the HTC thing comes with facebook installed. and some other things I don't want on my phone. Which is why I started this whole ordeal in the first place.
After that perhaps a good ROM for a newer android. But We'll see.
Again, thank you very much. I shall keep this forum under close watch and perhaps become a contrib myself eventually. Always wanted to deepen my knowledge on ROMs and such. perhaps this is the forum to guide me there. (After reading around a bit. I am guessing yes haha)
Cheers and thank you again, (Can't say that enough.)
DaeccaD said:
(bootloader) ...... Successful
OKAY
Flash Zip Complete
Execution time is 536(s)
And indeed, looked at that link of yours and gathered from that that indeed I should reboot it into bootloader.
Right now, my phone is working on upgrading 252 android apps.
Thank you very much!
Tomorrow I am going to try again with the superSU and CWMtouch. (Unless you think I should use another recovery which would be better) I want it rooted because the HTC thing comes with facebook installed. and some other things I don't want on my phone. Which is why I started this whole ordeal in the first place.
After that perhaps a good ROM for a newer android. But We'll see.
Again, thank you very much. I shall keep this forum under close watch and perhaps become a contrib myself eventually. Always wanted to deepen my knowledge on ROMs and such. perhaps this is the forum to guide me there. (After reading around a bit. I am guessing yes haha)
Cheers and thank you again, (Can't say that enough.)
Click to expand...
Click to collapse
TWRP recovery is the best for M7. CM stopped development a long time ago. Also, be sure to flash superSU 2.65, not lower. And when you flash recovery, make a backup of your current OS to be on the safe side
donkeykong1 said:
TWRP recovery is the best for M7. CM stopped development a long time ago. Also, be sure to flash superSU 2.65, not lower. And when you flash recovery, make a backup of your current OS to be on the safe side
Click to expand...
Click to collapse
All righty, will check that out tomorrow, thank you very much (again haha)
Cheers and good night
Daecca *Flails off, phone in hand shouting "It's alive, Ali i i ive":victory:
:victory: Problem Solved :victory:
DaeccaD said:
All righty, will check that out tomorrow, thank you very much (again haha)
Cheers and good night
Daecca *Flails off, phone in hand shouting "It's alive, Ali i i ive":victory:
:victory: Problem Solved :victory:
Click to expand...
Click to collapse
Great! Glad I could help! Enjoy your phone, and if you have any questions feel free to ask. You can shoot me a PM if you don't want to make a new thread [emoji6]
donkeykong1 said:
Great! Glad I could help! Enjoy your phone, and if you have any questions feel free to ask. You can shoot me a PM if you don't want to make a new thread [emoji6]
Click to expand...
Click to collapse
Will do, thank you very much, added you to contacts (And I think a friendrequest aswell. Ticked a box so guess so)
I am better with Samsung devices (Ace, S, S2, Note2 and Note 4), but getting to know HTC this intimately is amazing haha.
DaeccaD said:
Will do, thank you very much, added you to contacts (And I think a friendrequest aswell. Ticked a box so guess so)
I am better with Samsung devices (Ace, S, S2, Note2 and Note 4), but getting to know HTC this intimately is amazing haha.
Click to expand...
Click to collapse
You did send me a friendship request. I'll sort that out when I come home and get my hands on my laptop. I'm out now (having a beer) and I don't know how to accept things on tapatalk ?
EDIT: Sorted, request accepted [emoji4]