Related
EDIT: PROBLEM SOLVED, IT WAS MY FAULT, MY ZIP EXTRACTOR MALFUNCTIONED AND EXTRACTED FAULTY FASTBOOT. Sorry for the confusion
Hey guys!
I've been running into this problem for about 24 hours now, and through all of my searching I have found nothing. The problem has to do with downgrading hboot on a new Inc2 Red: I can't seem to get even temporary root from zergRush. The error is as follows:
Code:
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
I have tried on 3 OSes (Ubuntu, Windows Vista, Windows XP), done it both through the automated scripts and manually, and yet I get the exact same error. I have previous experience with rooting, though not through terminal (I do have much experience with terminal though).
zergRush claims to have worked, and
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
both work.
So many thanks ahead of time.
Crap... so you have to downgrade the HBoot on a DInc2 Red? I just bought my wife one for Christmas and have yet to get my hands on it to work on rooting it.
Do you have a direct link to the downgrade instructions? Just want to know what I have to look forward to...
WorldOfJohnboy said:
Crap... so you have to downgrade the HBoot on a DInc2 Red? I just bought my wife one for Christmas and have yet to get my hands on it to work on rooting it.
Do you have a direct link to the downgrade instructions? Just want to know what I have to look forward to...
Click to expand...
Click to collapse
Here's the link for the Downgrade Kit:
http://forum.xda-developers.com/showthread.php?t=1298990
BTW, thanks for hijacking this guy's thread.
---------- Post added at 09:18 AM ---------- Previous post was at 09:12 AM ----------
Sebas310 said:
Hey guys!
I've been running into this problem for about 24 hours now, and through all of my searching I have found nothing. The problem has to do with downgrading hboot on a new Inc2 Red: I can't seem to get even temporary root from zergRush. The error is as follows:
Code:
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
I have tried on 3 OSes (Ubuntu, Windows Vista, Windows XP), done it both through the automated scripts and manually, and yet I get the exact same error. I have previous experience with rooting, though not through terminal (I do have much experience with terminal though).
zergRush claims to have worked, and
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
both work.
So many thanks ahead of time.
Click to expand...
Click to collapse
Sounds like the ROM.zip file may be corrupt. Have you tried redownloading the Downgrade Kit again and compared the MD5 checksum? Better yet why not download the RUU/ROM.zip directly from the Development section?
tpbklake said:
Sounds like the ROM.zip file may be corrupt. Have you tried redownloading the Downgrade Kit again and compared the MD5 checksum? Better yet why not download the RUU/ROM.zip directly from the Development section?
Click to expand...
Click to collapse
+1 the RUU file is definitely corrupted, if you check its MD5 file, it will confirm the error. Use the original link(s) to d/l again, check the MD5 and then flash it, your adb/fastboot should be working, just run adb from the command line and watch it go to work, took less than 10 minutes to update/downgrade. Then, power off & reboot into Recovery, check it as you should be good to go. The bootloader (HB.98) has been unlocked & downgraded to HB.97 - once you finish the above steps & get SU on the mSD card to run, you device will truely be rooted and ready for the optional custom ROMs of choice. Be sure to do a CWM Recovery along the way.
tpbklake said:
Here's the link for the Downgrade Kit:
http://forum.xda-developers.com/showthread.php?t=1298990
BTW, thanks for hijacking this guy's thread.
---------- Post added at 09:18 AM ---------- Previous post was at 09:12 AM ----------
Sounds like the ROM.zip file may be corrupt. Have you tried redownloading the Downgrade Kit again and compared the MD5 checksum? Better yet why not download the RUU/ROM.zip directly from the Development section?
Click to expand...
Click to collapse
The MD5SUM checked out fine.
This is the RUU I need to download, correct?
Sebas310 said:
The MD5SUM checked out fine.
This is the RUU I need to download, correct?
Click to expand...
Click to collapse
No the script is set up to use this one:
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_signed
tpbklake said:
No the script is set up to use this one:
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_signed
Click to expand...
Click to collapse
+1 please see log file from command prompt while running adb unlocking my Red DI2 with HB.98 downgrade, S-Off and root (in case you've missed it in another post or couldn't find it in the search)
If everything worked, the INFOsignature check will show no errors and run smoothly ....
Okay, after looking at your log, I think I can tell what's wrong:
You have
Code:
writing 'zip'... INFOadopting the signature contained in this image...
and mine never does that. Log file attached. Redownloading fastboot and trying again in the meantime.
Did anyone ever figure this out? I'm having the same problem.
EDIT: Actually, I do get the:
writing 'zip'...INFOadopting the signature contained in this image...
But I still get the:
FAILED <remote: 12 signature verify fail>
as well.
I am using the RUU from the downgrade package here: http://forum.xda-developers.com/showthread.php?t=1298990
I'm really at a loss here. I've tried debugging this as best I can, but I'm not an Android developer per se. The vwhk-12102011-c.zip download matches the MD5. My device info is:
version: 0.5
version-bootloader: 0.98.0000
version-baseband: 1.09.01.1111
version-cpld: None
version-microp: None
version-main: 2.18.605.3
product: vivo_w
platform: HBOOT-7630
modelid: PG3210000
cidnum: VZW__001
security: on
build-mode: SHIP
boot-mode: RUU
hbootpreupdate: 12
All of which matches the android-info.txt file in the RUU. I've tried just flashing the hboot:
fastboot flash hboot hboot_0.97.0000_21273.nb0
but still get the error:
FAILED <remote: signature verify fail>
Help?
Hello XDA,
I have here a HTC Desire HD and it's Vodafone Branded, but that doesn't need to be a problem.
I want to make an Goldcard so I can flash Stock rom, because it's soft-bricked by trying to make a goldcard and trying tools that doesn't work.
I know the tools from: http://forum.xda-developers.com/showthread.php?t=2169515 but they are forwarding me to http://psas.revskills.de/?q=goldcard to request an goldcard image file, but that site is down.
I got the tool from Revskills but I don't understand it to make an goldcard.
I have also done this earlier by an other Desire HD and that one runs custom rom now and works well and I want to do this also to my current HTC Desire HD.
Now the only problem is, the HTC Desire HD is not booting to OS, it restarts over and over and I can only enter Recovery and Fastboot(also bootloader ofc.)
How can I get this done ?
Turkdale said:
Hello XDA,
I have here a HTC Desire HD and it's Vodafone Branded, but that doesn't need to be a problem.
I want to make an Goldcard so I can flash Stock rom, because it's soft-bricked by trying to make a goldcard and trying tools that doesn't work.
I know the tools from: http://forum.xda-developers.com/showthread.php?t=2169515 but they are forwarding me to http://psas.revskills.de/?q=goldcard to request an goldcard image file, but that site is down.
I got the tool from Revskills but I don't understand it to make an goldcard.
I have also done this earlier by an other Desire HD and that one runs custom rom now and works well and I want to do this also to my current HTC Desire HD.
Now the only problem is, the HTC Desire HD is not booting to OS, it restarts over and over and I can only enter Recovery and Fastboot(also bootloader ofc.)
How can I get this done ?
Click to expand...
Click to collapse
You phone can not be stuck in a bootloop for trying to create a goldcard, which is done in in the sdcard and not in the device itself. Besides, the tools provides you another tool to create a goldcard, quoting:
...IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:
Create a goldcard using this tool: http://d-h.st/VMw, once you have the .img file patch it using the SimpleGoldCard Tool included in the tools folder. (you need a working phone for this)
Find a RUU which main version is supported and higher than yours and flash it in the PD98IMG.zip way, that is what is the goldcard for. If you have a .exe RUU, then extract the rom.zip file using this method: http://www.xda-developers.com/xda-tv...-an-ruu-xdatv/
Re run the tool and you will be able to update the hboot and unlock it...
Click to expand...
Click to collapse
What did you flash to get your device in that state? To create a goldcard you will need a working phone, so you can use the other DHD to do it.
glevitan said:
You phone can not be stuck in a bootloop for trying to create a goldcard, which is done in in the sdcard and not in the device itself. Besides, the tools provides you another tool to create a goldcard, quoting:
What did you flash to get your device in that state? To create a goldcard you will need a working phone, so you can use the other DHD to do it.
Click to expand...
Click to collapse
I tried to use AAHK for HTC Desire HD, but the website of the developer of it, is offline.
Now the phone starts, after HTC splashscreen, I see Vodafone Splash Screen and after that It keeps rebooting from HTC splashscreen.
How can I solve this ? Factory reset and format data/factory reset @ recovery doesn't solve the issue.
Turkdale said:
I tried to use AAHK for HTC Desire HD, but the website of the developer of it, is offline.
Now the phone starts, after HTC splashscreen, I see Vodafone Splash Screen and after that It keeps rebooting from HTC splashscreen.
How can I solve this ? Factory reset and format data/factory reset @ recovery doesn't solve the issue.
Click to expand...
Click to collapse
Of they did not...in fact they made things worse as you deleted the usb debugging drivers from the phone. Hack Kit hasn't been online for about 6 months now and so is support.
Your only way to get out of that is to flash a RUU.
glevitan said:
Of they did not...in fact they made things worse as you deleted the usb debugging drivers from the phone. Hack Kit hasn't been online for about 6 months now and so is support.
Your only way to get out of that is to flash a RUU.
Click to expand...
Click to collapse
Yes I understand that, but the problem is that I can't find a RUU that works for my HBOOT version. I tried 2 RUU's. If you can find a working one, it won't be a problem anymore.
Can you do a printout of your Phone via fastboot mode with
fastboot getvar all
please.
hacktrix2006 said:
Can you do a printout of your Phone via fastboot mode with
fastboot getvar all
please.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.52.27
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.161.5
(bootloader) serialno: HT0BWRX11664
(bootloader) imei: *secret*
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: VODAPE17
(bootloader) battery-status: good
(bootloader) battery-voltage: 3679mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.008s
I would hide the IMEI if i was you.
Use http://forum.xda-developers.com/showthread.php?t=2288012 which is from glevitan to make a goldcard then once you have done that download the right RUU run the .exe and in %temp% look for rom.zip
once you have done this place rom.zip in the same folder as fastboot and adb then open command prompt and cd into the directory that fastboot and adb is in.
Then type the following with the goldcard in the phone.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (Just to make sure)
fastboot reboot
This should then fix your phone.
Thank you very much for your tip en help. Didn't notice about the IMEI I would try your advice tonight when I'm home and will keep you updated.
Sent from my GT-I9300 using xda premium
hacktrix2006 said:
I would hide the IMEI if i was you.
Use http://forum.xda-developers.com/showthread.php?t=2288012 which is from glevitan to make a goldcard then once you have done that download the right RUU run the .exe and in %temp% look for rom.zip
once you have done this place rom.zip in the same folder as fastboot and adb then open command prompt and cd into the directory that fastboot and adb is in.
Then type the following with the goldcard in the phone.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (Just to make sure)
fastboot reboot
This should then fix your phone.
Click to expand...
Click to collapse
I am not sure that flashing that way will fix the device as the goldcard is in the sdcard and not the device. To locate the goldcard in the device he would need to have temp root access.
He needs to flash the ruu in the PD98IMG.zip way from the root of the sdcard.
Goldcard works both ways also if he is S-ON which he is he can't use the PD98IMG.zip way on the fastboot oem rebootRUU way to flash
hacktrix2006 said:
I would hide the IMEI if i was you.
Use http://forum.xda-developers.com/showthread.php?t=2288012 which is from glevitan to make a goldcard then once you have done that download the right RUU run the .exe and in %temp% look for rom.zip
once you have done this place rom.zip in the same folder as fastboot and adb then open command prompt and cd into the directory that fastboot and adb is in.
Then type the following with the goldcard in the phone.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (Just to make sure)
fastboot reboot
This should then fix your phone.
Click to expand...
Click to collapse
I did try this and just getting this:
Code:
sending 'zip' (293949 KB)...
OKAY [ 49.289s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(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: 89.611s
right that means the goldcard was not made successfull
"FAILED (remote: 42 custom id check fail)
the card is not valid or the process is not done correctly"
which means you need to try another sdcard and remake the goldcard.
I take it you have no custom recovery? If you really need help PM with a Teamviewer ID and password. I will then try and help.
hacktrix2006 said:
right that means the goldcard was not made successfull
"FAILED (remote: 42 custom id check fail)
the card is not valid or the process is not done correctly"
which means you need to try another sdcard and remake the goldcard.
I take it you have no custom recovery? If you really need help PM with a Teamviewer ID and password. I will then try and help.
Click to expand...
Click to collapse
I can't make a goldcard because the phone isn't booting, it has a bootloop. Could you please provide me support by Google Talk(Hangout) or something else what would be faster and easier to communicate ?
I won't share your private account details like your username, but It would be easier for me and you to talk to each other.
If you could wait till tomorrow i can get you the HTC Dev bootloader in a oem rebootRUU .zip and give you instructions on how to restore the phone fully with S-Off as well.
I am on GMT timezone and its late. PM me tomorrow and i will give you my google hangout or better still get teamviewer installed so i can remotely do the whole thing for you.
hacktrix2006 said:
If you could wait till tomorrow i can get you the HTC Dev bootloader in a oem rebootRUU .zip and give you instructions on how to restore the phone fully with S-Off as well.
I am on GMT timezone and its late. PM me tomorrow and i will give you my google hangout or better still get teamviewer installed so i can remotely do the whole thing for you.
Click to expand...
Click to collapse
I'm a IT guy and ofcourse I have Teamviewer and I will be glad if you can help me tomorrow... It will be finally again that's someone is connecting to me by Teamviewer hahaha and I'm also on GMT timezone, 1:56 here (Netherlands) I will PM you now for tomorrow, with my Gmail for Hangout
I have added you will not be around till after 11:00am like, best to teamviewer in that way i can just restore your phone to working order and have S-OFF
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
mtt_73 said:
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
Click to expand...
Click to collapse
im going to assume your phones is s-off?
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Thank you.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Click to expand...
Click to collapse
You can't install custom recovery with a (re)locked bootloader.
With s-off, you shouldn't ever relock the bootloader, as its no longer a requirement to RUU once s-off. But that's neither here nor there at this point, just info for future reference.
Any response to: fastboot devices
Make sure the phone is in fastboot mode.
Try to run the GPE RUU with phone in fastboot mode, to get the phone back up and running at least. Assuming you are still on the GPE CID and MID.
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Click to expand...
Click to collapse
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT.............8
(bootloader) imei: 35...........30
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
redpoint73 said:
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Click to expand...
Click to collapse
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Click to expand...
Click to collapse
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
mato123 said:
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
Click to expand...
Click to collapse
I would highly suggest not to post to another user's troubleshooting thread like this, as it doesn't look like the same problem at all (and in my experience rarely is, even when folks will post "I have the same issue"). You really should have just started your own thread, and would have been justified doing so IMO. Posting here just confuses matters for you, the OP and those trying to help.
But DON'T start another thread now (and add even more confusion). I'll ask the mods if they can move this post to its own thread.
ok, sorry
redpoint73 said:
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
Click to expand...
Click to collapse
Thanks for reply.
I went now in fastoob mode and tried to flash the RUU GPE again.
The error is:
macbooks-MacBook-Proownloads macbook$ ./fastboot-mac flash RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
unknown partition 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
error: cannot determine image filename for 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
Just to clarify. I successfully when in GPE (with conversation). The problem was when going back to Sense. I do not know exactly what I did wrong.
My CID is 11111111
My MID is 0P6B10000
Really do not know how to proceed.
M
I unfortunately don't know jack about how to use fastboot and other actions on a Mac. I'm also not that familiar with running the RUU as a zip (I always do it on a PC with the RUU .exe).
But it looks like you just have the command syntax wrong. I think it should be:
fastboot oem rebootRUU
fastboot flash zip filename.zip
But it also look to me like nothing is actually "wrong" (aside from adb not working?). The phone not booting after relocking the bootloader is normal and intentional. You should just be able to run the desired Sense RUU, provided you have the right MID.
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
mtt_73 said:
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
Click to expand...
Click to collapse
hehe try watch this movie: https://www.youtube.com/watch?v=CCGj0rOuiR4
Most important is the firmware flash... so partition layout etc is changed to sense like after that you can flash sense roms etc. (for example viper rom as in video)
0kk0 said:
Most important is the firmware flash... so partition layout etc is changed to sense
Click to expand...
Click to collapse
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
redpoint73 said:
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
Click to expand...
Click to collapse
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Sent from my HTC One_M8 using xda Forum
mtt_73 said:
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Click to expand...
Click to collapse
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
redpoint73 said:
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
Click to expand...
Click to collapse
I did it. I am back to Sense now.
Any advice to remove tell HTC problem? I mean it says that I have a testing device. Is it because I am s-off? Should I go for s-on again? And how?
TY!
Trying to recover an HTC One (M7) Verizon m7wlv for a friend of mine.
He wasn't trying to do anything "developery" to the phone. He said he installed some app off the market, and after a reboot it was softbricked.
UPDATE The App he tried installing was MobileIron which is a corporate app designs to encrypt the phone for corporate security needs. It was a requirement of the company he is working for.
So if you had this issue after installing MobileIron, then this is a good thread for you to read.
It comes up to the OS and complains, in blue:
Encryption unsuccessful
Encryption was interrupted and can't
complete. As a results, the data on your
phone is no longer accessible.
To resume using your phone, you need to
perform a factory reset. When you set up
your phone after the reset, you'll have an
opportunity to restore any data that was
backed up to your Google Account.
>Reset Phone<
When I click Reset Phone, the "Factory data reset" window open, then the phone reboots.
For a moment, it loads an upgrading phone screen(I believe)
And then hits recovery, and has the following errors at the bottom:
E: missing bitmap oem_unlock_bg
(Code -1)
E: missing bitmap oem_unlock_bg_yes
(Code -1)
E: missing bitmap oem_unlock_bg_no
(Code -1)
E: missing bitmap icon_ruu
(Code -1)
Backup necessary files in data partition
E:failed to mount /data (Invalid argument).. try emmc mount
Data wipe failed.
From the error screen, I am able to work my way to setting, by pressing home twice, and then, the ... menu in the top right, then Running Apps, then I can use the arrow left at the top left of the screen to reach the rest of the system menus.
I can get to build version, enable dev mode, enable usb debugging, and access adb shell.
Version information:
Android version: 5.0.2
Software number: 6.22.605.3
I can also get in to fastboot, and here is a fastboot getvar all:
INFOversion: 0.5
INFOversion-bootloader: 1.61.0000
INFOversion-baseband: 1.13.41.1209
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.22.605.3
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXXX
INFOimei: XXXXXXXXXXXXXX
INFOmeid: XXXXXXXXXXXXXX
INFOproduct: m7_wlv
INFOplatform: HBOOT-8064
INFOmodelid: PN0731000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 4324mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-0e2a13e5
INFOhbootpreupdate: 11
INFOgencheckpt: 0
This is S-ON and Locked, so in theory, I can't flash an RUU unless it's a current or greater version, but I haven't seen an unmodded RUU for 6.22.605.3 or greater.
Any help would be appreciated.
nkk71 requested the getvar all above. Any further help is greatly appreciated.
mugendai said:
INFOversion-main: 6.22.605.3
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_wlv
INFOplatform: HBOOT-8064
INFOmodelid: PN0731000
INFOcidnum: VZW__001
This is S-ON and Locked, so in theory, I can't flash an RUU unless it's a current or greater version, but I haven't seen an unmodded RUU for 6.22.605.3 or greater.
Any help would be appreciated.
Click to expand...
Click to collapse
the signed RUU you mentioned earlier: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
should work
reboot to bootloader screen, and try running it again, check the log in C:\ruu_log\ folder if it get's stuck
EDIT: don't interrupt the ruu process, if the .exe doesnt work we'll switch to .zip
Alright thanks, I'll go give it a shot now
Tried it, and got further than before. Not sure if it's because I ran the utility while in rebootRUU mode, or if it's because I found a different driver, but it did at least try, before it failed.
The RUU is trying to flash to:
5.28.605.2
The phone is at: 6.22.605.3
I think it's failing because of the version number.
It gives this error in the GUI:
Code:
ERROR [140]: BOOTLOADER VERSION ERROR
The Firmware Update Utility cannot update your Android phone.
Please get the correct Firmware Update Utility and try again.
And here is what I believe is the relevant section of the ruu logs:
Code:
<T144720><DEBUG><OUT>(bootloader) checking main version...</OUT>
</DEBUG></T144720>
<T144720><DEBUG><OUT>Execution time is 9(s)</OUT>
</DEBUG></T144720>
<T144720><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T144720>
<T144720><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
mugendai said:
The RUU is trying to flash to:
5.28.605.2
The phone is at: 6.22.605.3
<T144720><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T144720>
<T144720><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>[/CODE]
Click to expand...
Click to collapse
the zip should work
mugendai said:
Tried it, and got further than before. Not sure if it's because I ran the utility while in rebootRUU mode, or if it's because I found a different driver, but it did at least try, before it failed.
The RUU is trying to flash to:
5.28.605.2
The phone is at: 6.22.605.3
I think it's failing because of the version number.
It gives this error in the GUI:
Code:
ERROR [140]: BOOTLOADER VERSION ERROR
The Firmware Update Utility cannot update your Android phone.
Please get the correct Firmware Update Utility and try again.
And here is what I believe is the relevant section of the ruu logs:
Code:
(bootloader) checking main version...
Execution time is 9(s)
FAIL43 main version check fail
FAILED (remote: 43 main version check fail)
Click to expand...
Click to collapse
I have that version uploaded. Let me dig up the link.
Edit..
https://www.androidfilehost.com/?fid=24052804347761412
Rename it to rom.zip and copy it into the exe folder.
Sent from my HTC6535LVW using Tapatalk
nkk71 said:
the zip should work
Click to expand...
Click to collapse
The zip won't work if the mainver is older since he is s-on.
Sent from my HTC6535LVW using Tapatalk
dottat said:
The zip won't work if the mainver is older since he is s-on.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
the zip flashed just fine, proper, LargeZip, proper signature/encryption, proper, version
Code:
[B][email protected][/B]....³êÖ..nQ#£ÕêH%$SX............³éÖ.Mƒz £g™%‚Nh.ø.m.................„’{)................................................................................................................................................................................–A?úû.#q.Nê«uEB.ã...2½ØÒ¬ä:hêesº‚}.Ô8»=¿…ô.VËõhM.¼÷ą̃XèFý±€¬.¿N..}V¤.¦Ü...ÅFŒ$p«<›Ø³.Ž.{NV..žÐ®KÒtÈî§ùV...)7f9±ÿ´.7.•§5Æ<Sð£.f˜š*(g*å·ž..âÒ¡ÁK計•‹;H.Ê.[’..Õó*.ˆ“ƒÔµ0.Ù.-.y.ƒ“.V‡/B·«xÆês.”A:m},³æœæ~.V*.õdô[email protected]Í….¬¯9ìl°.ÿ..v-o8rFhÕÔä*·•=.¨µ·E%.i0.ˆ±_Šc.è[email protected]$.“.ÿÿÿÿÿÿÿÿÿÿ[B][COLOR="Blue"]6.22.605.3[/COLOR][/B]
edit: didnt seem to have solved the encryption thingy... maybe that's in misc... just guessing
nkk71 said:
the zip flashed just fine, proper, LargeZip, proper signature/encryption, proper, version
Code:
[B][email protected][/B]....³êÖ..nQ#£ÕêH%$SX............³éÖ.Mƒz £g™%‚Nh.ø.m.................„’{)................................................................................................................................................................................–A?úû.#q.Nê«uEB.ã...2½ØÒ¬ä:hêesº‚}.Ô8»=¿…ô.VËõhM.¼÷ą̃XèFý±€¬.¿N..}V¤.¦Ü...ÅFŒ$p«<›Ø³.Ž.{NV..žÐ®KÒtÈî§ùV...)7f9±ÿ´.7.•§5Æ<Sð£.f˜š*(g*å·ž..âÒ¡ÁK計•‹;H.Ê.[’..Õó*.ˆ“ƒÔµ0.Ù.-.y.ƒ“.V‡/B·«xÆês.”A:m},³æœæ~.V*.õdô[email protected]Í….¬¯9ìl°.ÿ..v-o8rFhÕÔä*·•=.¨µ·E%.i0.ˆ±_Šc.è[email protected]$.“.ÿÿÿÿÿÿÿÿÿÿ[B][COLOR="Blue"]6.22.605.3[/COLOR][/B]
edit: didnt seem to have solved the encryption thingy... maybe that's in misc... just guessing
Click to expand...
Click to collapse
You sent him to my thread for 4.4.3 signed zip....which is I posted the zip for 5.0.2 (6.22.605.3).
So I'm guessing you got the zip for 6.22.605.3 from somewhere else.
Sent from my HTC6535LVW using Tapatalk
dottat said:
You sent him to my thread for 4.4.3 signed zip....which is I posted the zip for 5.0.2 (6.22.605.3).
So I'm guessing you got the zip for 6.22.605.3 from somewhere else.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
yours as well from here: https://www.androidfilehost.com/?fid=24052804347761412
nkk71 said:
yours as well from here: https://www.androidfilehost.com/?fid=24052804347761412
Click to expand...
Click to collapse
I just put two and two together from Zanzibar asking me about it earlier.
OK. So let's get the op to try this while booted to fastboot.
Fastboot oem task 28
Fastboot oem task 29
Then flash ruu zip and cross fingers.
Sent from my HTC6535LVW using Tapatalk
dottat said:
Fastboot oem task 28
Fastboot oem task 29
Click to expand...
Click to collapse
I'm curious now what are those , i've only dealt with a few [usually not used] oem commands as a [possibly sloppy] workaround for the misc partition fix, but never posted them openly due to my lack of knowledge of what they actually do :angel:
nkk71 said:
I'm curious now what are those , i've only dealt with a few [usually not used] oem commands as a [possibly sloppy] workaround for the misc partition fix, but never posted them openly due to my lack of knowledge of what they actually do :angel:
Click to expand...
Click to collapse
so 28 will wipe /data from fastboot
29 will format binary file system for /cache /data /system (system only on an s-off phone).
and I should add that most of the time if the phone doesn't have EMMC issues these commands will fix being locked out due to encryption issues.
dottat said:
so 28 will wipe /data from fastboot
29 will format binary file system for /cache /data /system (system only on an s-off phone).
and I should add that most of the time if the phone doesn't have EMMC issues these commands will fix being locked out due to encryption issues.
Click to expand...
Click to collapse
oh boy, you do realize i'm gonna run those (and bad encryption) on my m7 tomorrow
dottat said:
I have that version uploaded. Let me dig up the link.
Edit..
https://www.androidfilehost.com/?fid=24052804347761412
Rename it to rom.zip and copy it into the exe folder.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I tried this zip, and it DID flash, however, I got errors during the flash:
Code:
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (FA37HS903177)...
< waiting for device >
sending 'zip'... (46522 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
The flash did not stop there, it kept going all the way through.
I tried running it a second time, and got the same error.
I tried rebooting, but the phone is still in the same state with the encryption error, and can't wipe /data
So close, totally expected the RUU to fix this.
You posted some other things to try, below, I will test those and reply.
Thanks for your time!
mugendai said:
I tried this zip, and it DID flash, however, I got errors during the flash:
Code:
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (FA37HS903177)...
< waiting for device >
sending 'zip'... (46522 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
The flash did not stop there, it kept going all the way through.
I tried running it a second time, and got the same error.
I tried rebooting, but the phone is still in the same state with the encryption error, and can't wipe /data
So close, totally expected the RUU to fix this.
You posted some other things to try, below, I will test those and reply.
Thanks for your time!
Click to expand...
Click to collapse
Yes. That is a normal flash.
Let us know the results of the added commands
Sent from my HTC6535LVW using Tapatalk
I did OEM 28 only, and did a reboot, and have a very promising "Android is upgrading..."
Will update you when it gets through the 278 apps...
Phone is back up and running. I suspect that this command alone would have resolved the origional problem.
Thank you very much for your help. I'll update the OP tonight with the solution.
mugendai said:
Phone is back up and running. I suspect that this command alone would have resolved the origional problem.
Thank you very much for your help. I'll update the OP tonight with the solution.
Click to expand...
Click to collapse
good deal....back from the land of despair.
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
unlock with fastboot
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
yotamh said:
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
Click to expand...
Click to collapse
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
yotamh said:
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
Click to expand...
Click to collapse
It seems like you're talking about the android version not the firmware version since there is no 5.0.XXX.X firmware for the M9. For now it might be the best solution to wait until you're home.
yotamh said:
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
Click to expand...
Click to collapse
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
LLegion said:
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
Click to expand...
Click to collapse
the problem is I can't unlock the bootloader. ADB devices doesn't work
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
yotamh said:
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
Click to expand...
Click to collapse
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in my google sheet (link can be found in my signature). Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Flippy498 said:
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in the google sheet in my signature. Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Click to expand...
Click to collapse
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
yotamh said:
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
Click to expand...
Click to collapse
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Flippy498 said:
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Click to expand...
Click to collapse
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
yotamh said:
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
Click to expand...
Click to collapse
yotamh said:
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
Click to expand...
Click to collapse
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Click to expand...
Click to collapse
Hi thanks for the top about the IMEI I've changed it.
and sorry, I didn't understood the the original comment and got in to the a wrong line in the comment. I'll try again with the correct file (2gb will take some to download). Again, thank you for your answer and patient. It's nice to see people try to help. :good:
THANK YOU so much! everything is working and even updated! thanks!
it seems i have a strange issue after all.
my phone doesn't detect my htc headphones. It recognize other headphone and the HTC headphones works with other devices.
it looks like a software issue.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. [REMOVED BECAUSE I'M A NEWBIE]I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature[/URL].
Click to expand...
Click to collapse
Hi I know this is probably old but I was in this exact same predicament and I had "tried everything" and your instructions brought my phone back to life!! I am so grateful after almost a week of adb commands and zip files that got me nowhere! THANK YOU SO MUCH!!!:good: