I found similar problem wich one user had with HTC Desire that now I have with my friend's Vivid. Here what he have posted:
Whompa 1 said:
Hi all. I have a major issue with my fiancée's phone. I tryed to downgrade from Alpharev CM7 hboot using an RUU. My mistake as I got an error saying "incorrect version". In the hboot it displays as the system did not load after the RUU error. So now I get a black HTC screen with 4 exclamation marks 1 in each corner View attachment 700934 this appears when I connect the phone via USB. But when I take it off USB it displays this View attachment 700933. So these are the only 2 screens I have access to, I can flash stuff via fastboot using CMD prompt but nothing has succeeded so far. I do not have access to the normal hboot and fastboot menus. Any ideas are very welcome.
Save me.
Click to expand...
Click to collapse
So my history started 3 days ago from the call from my friend, to whom I am godfather of his son, and told me that his Vivid can't load and stuck on white screen with htc letters and can't load. I was looking throw this forum and decided that bootloader is broken. So I downloaded the file PH39IMG.zip of ~35 MB and after loading in fastboot with Power+Volume Down have updated. After this the Vivid rebooted and was working good so I returned the phone to my friend. In 2 days after he told me that he has problems again: he tried using wi-fi at home and as he told "It was not working" so he went into settings and chosen Factory reset. After this phone stucked on white screen and nothing else, so he asked me to help him again (because everything he can do with Android is backing up his contacts ) also he asked me to flash some custom ROM on JB. But I decided to recover in stock ROM first. So I started from copying the stock ROM renamed into PH39IMG.zip to sd card. Then loading into bootloader I confirm the update. It has checked and updated all strings and rebooted. After this it has started updating again but there were more strings than before. On the string User data update was stucking in about the half. I was waiting for more than 3 hours and realized that something wrong with it. So I switched the phone off by taking the battery out, I loaded in bootloader and decided not to spent the time but to start unlocking bootloader, getting S-OFF, flashing the CWM or other Recovery and finally flashing the custom ROM. I have to say that I have drivers installed from Android SDK, as I was working before with different Android devices and everything was successful. I have to thanks you guys as all I did before were found on this forum which I am regularly reading for more than 1 year. I also have adb tools and Vivid_All-In-One_Kit_v2.2 installed. So using the last one I started from unlocking bootloader. I did all steps and after receiving Unlock_code.bin file and pressed Unlock bootloader in Vivid_All-In-One_Kit I got screen on the phone for unlocking the bootloader. Off course with the help of Volume Up key I've chosen Yes BUT (!!!!!) pressing the Power button of the phone did not do any action - it just like this button was not working! I had to take the battery off and boot in bootloader with Power and Volume Down and it is loaded, so Power button is working, but the banner of bootloader was "LOCKED"!!! So after reading different topics as I didn't make unlocking, S-OFF etc. I decided to update stock ROM with the help of RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
It has started with such screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then it was going and stucked on 34%. I was waiting for more then 1 hour (it was a notification that update process will take about 10 minutes) but the screnn was the same 34% and looking like still updating as status indicated by dots running was in progress:
So with no any ideas I decided to unplug the USB cable and I got the following:
So I have plugged again and followed all steps with unlpugging/taking battery off and in/plugging and here what screens I've seen:
And after resuming update I got the same stuck on 34%!!!!:crying:
And the worth was that now I got a black HTC screen with 4 exclamation marks 1 in each corner:
and when I take the battery off and then put it on it shows the same after turning the phone on (and it's no matter if I just press the Power button or trying to load bootloader with Power+Volume Down) - same screen. If I plug the USB cable and then unplug it will show the following:
What is interesting is that when I plugging USB and run cmd under Win7 and no matter where to go in root of my Win: ADB_Tools or Android or Vivid_All-In-One_Kit_v2.2 folders and running the fastboot devices - it can see the phone:
but when i am trying different tricks in Vivid_All-In-One_Kit_v2.2 such as unlock bootloader it is give such error as device not found:
and when I am trying to flash the kernel I got such result which seemed to stucking:
As I understand I got the soft-brick?
I even have no ideas what to do, as I am in Ukraine and Vivid is US model, so I am afraid visiting the service centre will take so much time to do something with the phone...:crying:
So I have only the last hope - suppose on your help, guys!
Sorry for possible mistakes as I am f...ing with this Vivid the second day and have slept only 3 hours yesterday and will sleep only 2 hours today as it is already 5:39 AM in Ukraine and I have to get up at 7:30 to send my kids to school
Have you tried a ph39.img update instead of an ruu? You said stock ROM not sure what you meant
Sent from my HTC Vivid 4G
Well you could us a ph39img.zip for this phone you will have a strong chance to recovering it.... Just grab a gingerbread version of the ph39 IMG.zip or an ics one with the new hboot.IMG in it too
Sent from my ADR6410LVW using xda premium
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Because I had the same issue when I owed the phone. And it seems after reading your process to get to the point you are I did the exact same, but I just download a ruu.zip for that phone and updated it thru hboot and my problem was fixed.
Sent from my ADR6410LVW using xda premium
ZeRo2o9 said:
Have you tried a ph39.img update instead of an ruu? You said stock ROM not sure what you meant
Sent from my HTC Vivid 4G
Click to expand...
Click to collapse
Yes, I did. I mentioned it at the beginning of my thread:
I decided to recover in stock ROM first. So I started from copying the stock ROM renamed into PH39IMG.zip to sd card. Then loading into bootloader I confirm the update. It has checked and updated all strings and rebooted. After this it has started updating again but there were more strings than before. On the string User data update was stucking in about the half. I was waiting for more than 3 hours and realized that something wrong with it.
Click to expand...
Click to collapse
The stock ROM was used, downloaded by link from this forum and renamed into PH39IMG.zip.
As I see nobody know what to do?
I was thinking, is it possible if I have another Vivid working fine to copy system from it or make image of internal memory data and load on this one. But I don't know how to do it
Is there any possibility to make this
same prob
hi guys,
same problem here, no luck with my Bravo PVT4 S-On
C:\Users\azur\Desktop\Win32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0001
(bootloader) version-baseband: 5.11.05.27
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: 2.33.161.2
(bootloader) serialno: SH0ALPL12639
(bootloader) imei: 355302044178565
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: VODAP102 // is this cid for Vodafone UK ??????
(bootloader) battery-status: good
(bootloader) battery-voltage: 4035mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: a7cdbe26
(bootloader) hbootpreupdate: 11
all: Done!
C:\Users\azur\Desktop\Win32>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E0800C4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26A12
(bootloader) TAG:hero panel = 0x3
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is VODAP102
(bootloader) setting->cid::VODAP102
(bootloader) serial number: SH0ALPL12639
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =458
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=V
(bootloader) ODAP102 androidboot.carrier=VODA-Germany androidboot.mid=PB9
(bootloader) 920000 androidboot.keycaps=qwerty androidboot.mode=normal an
(bootloader) droidboot.serialno=SH0ALPL12639 androidboot.bootloader=1.02.
(bootloader) 0001 zygote_oneshot=off kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:203918 msec
FAILED (status read failed (Too many links))
finished. total time: 20.378s
Did you try locking the bootloader before starting the RUU???
I think it's in your best interest in making the phone Super CID. The one above is indeed a Vodafone CID, so you can only run Vodafone RUU's on it.
I made an acrobat .pdf file (copied from the original thread on it). See the attachment.
After you Super CID you can run any RUU on the phone and it will take it.
As for the OP: I believe he has to download and install the proper ph39img.zip for the phone. I don't think renaming a file to that will cause it to work correctly. Currently his bootloader is messed up.
Related
Hi i recently bought a second hand incredible s, it has black rose and custom rom.In the back cover inside the phone in the place that writes the imei the serial number and the model number witch mine is PG3213, so i decided to download the ruu for this model id , i run it and i got error 130.I then start typing fastboot get var all and i saw that the model number was PG3212!!!!!Some how the previous user change the model id number.So i extract the rom from the ruu i change the model id number in the android-info.txt, i zip it in a PG32IMG.ZIP and it installed successfully.I then go to make the updates and the update fails.I have stock recovery but i think that the black rose stop the update.So i want to ask how i can change the model id back to the original to rum the ruu for fully stock again and update over the air.
Thanks
Anoubis282 said:
Hi i recently bought a second hand incredible s, it has black rose and custom rom.In the back cover inside the phone in the place that writes the imei the serial number and the model number witch mine is PG3213, so i decided to download the ruu for this model id , i run it and i got error 130.I then start typing fastboot get var all and i saw that the model number was PG3212!!!!!Some how the previous user change the model id number.So i extract the rom from the ruu i change the model id number in the android-info.txt, i zip it in a PG32IMG.ZIP and it installed successfully.I then go to make the updates and the update fails.I have stock recovery but i think that the black rose stop the update.So i want to ask how i can change the model id back to the original to rum the ruu for fully stock again and update over the air.
Thanks
Click to expand...
Click to collapse
You aren't supposed to be using an RUU when you have blackrose. Instead, you're supposed to be reverting blackrose...... Blackrose is a custom bootloader and an RUU will not run because of it (or if your bootloader is unlocked for that matter).
Yes i understand that i have unistalled black rose but the model id remains changed.I extracted the rom zip from the ruu and instaled successfully via PG32IMG but when i perform ota it goes to the red triangle of recovery and fails.I check the otas android info.txt and the model id is different than mine.so i think that this is the reason the update fails....I have stock recover with stock hboot alla stock after the PG32IMG......I want to change the model id i think.....
Anoubis282 said:
Yes i understand that i have unistalled black rose but the model id remains changed.I extracted the rom zip from the ruu and instaled successfully via PG32IMG but when i perform ota it goes to the red triangle of recovery and fails.I check the otas android info.txt and the model id is different than mine.so i think that this is the reason the update fails....I have stock recover with stock hboot alla stock after the PG32IMG......I want to change the model id i think.....
Click to expand...
Click to collapse
That's because you're not supposed to run RUU's with Blackrose bootloader. You need to revert it first....
I uninstall blackrose but it happens the same .I am sure that the probem is in the different mid.....If anyone knows if the blackrose supports the fastboot oem wite mid command???
Anoubis282 said:
I uninstall blackrose but it happens the same .I am sure that the probem is in the different mid.....If anyone knows if the blackrose supports the fastboot oem wite mid command???
Click to expand...
Click to collapse
Can u post whats in your bootloader
Sent from my Nexus 5 using XDA Free mobile app
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.03.0000
(bootloader) version-baseband: 3805.06.03.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: HT17PTD05680
(bootloader) imei: 8888888888888888
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3212***
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4030mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3b35dcea
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
Hi i have problems on changing mid.it dose not chage it says Main MID dose not match [PG3211] OR [PG3211]!
Anoubis282 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.03.0000
(bootloader) version-baseband: 3805.06.03.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: HT17PTD05680
(bootloader) imei: 8888888888888888
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3212***
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4030mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3b35dcea
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
Hi i have problems on changing mid.it dose not chage it says Main MID dose not match [PG3211] OR [PG3211]!
Click to expand...
Click to collapse
Does it say blackrose in yiur bootloader?
Sent from my Nexus 5 using XDA Free mobile app
Yes..i have blackrose instaled.......
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://postimg.org/image/7ntzpdhnj/
Anoubis282 said:
Yes..i have blackrose instaled.......
http://postimg.org/image/7ntzpdhnj/
Click to expand...
Click to collapse
so revert it..... what the heck? you told me you reverted it before....
I put it back
072665995 said:
so revert it..... what the heck? you told me you reverted it before....
Click to expand...
Click to collapse
Yeah i installed it again.....When i uninstalled it then i instal the pg32img that extracted from ruu and installed successfully.but when i receive the ota and the phone restart to update it stucks in red triangle....so i thought that the problem is in different mid so i put back blackrose to change the mid but i cant i am getting the error i mentioned in previous post.When i tried to run the ruu.exe i got error in mid number....so i cant run the ruu exe from the pc....
Anoubis282 said:
Yeah i installed it again.....When i uninstalled it then i instal the pg32img that extracted from ruu and installed successfully.but when i receive the ota and the phone restart to update it stucks in red triangle....so i thought that the problem is in different mid so i put back blackrose to change the mid but i cant i am getting the error i mentioned in previous post.When i tried to run the ruu.exe i got error in mid number....so i cant run the ruu exe from the pc....
Click to expand...
Click to collapse
Ok revert blackrose because there is no way you're running an RUU properly with a custom bootloader installed. Second, when you run the RUU from your PC, report the error number (i suspect it is 131 but post it anyways)
Error 130
072665995 said:
Ok revert blackrose because there is no way you're running an RUU properly with a custom bootloader installed. Second, when you run the RUU from your PC, report the error number (i suspect it is 131 but post it anyways)
Click to expand...
Click to collapse
It says error 130......
Phone Info:
SPRINT HTC ONE M7
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: #my number#
(bootloader) imei: #my number#
(bootloader) meid: #my number#
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Symptoms:
No Service
Doesnt show my Basband num, IMEI, MEID, NetWork, IP in UI (but it shows up when i Run "Fastboot getvar all".
Progress com.htc.htcdialer isn't responding.
Boot loops every 5-7 min.
What I did:
Last weeks i bricked my sch-i500 so even though I have Verizon I went out to buy HTC one on sprint (hoping i cant make it work on Verizon).
So i unlocked BootLoader and Rooted the device. Yet for some reason SU wasn't working right - i didnt have root rights.
So i decided to Mod flash it. Made a backup in TWRP, wiped: dalvik, cache, data. and successfully flashed Android Revolution HD 53.0.
But I guess not. Because once i rebooted my screen tripped pink right before the boot animation and never loaded into UI.
I restarted it and gave it another 10 min of loading time - nothing.
I wiped after the previous ROM and flashed Venom ROM, ViperOne 6.2.0.
This one took long to boot up as well but once it did it would just show HTC logo screen upon screen unlock.
I gave it time and it actually brings up the "get started page" 5 min in - problem is it would reboot 1 min after.
After i flashed kernel.
Newest version of Gapps.
Tried LiquidSmooth Rom - that would boot me up but didn't solve my issue plus it didn't have google play and other apps.
I even tried going back to the recovery. It would SPRINT it back into stock yet have the acquired issues since i installed the mod: show HTC logo screen once it entered the UI and the rest of bs
I managed to get the get started page and run through it real quick before it rebooted.
But it had no service, and all those issues i stated above.
Now i came back to ViperOne and once the logo screen flashed to "get started" i ran through it real quick and now thats where im at. But it restarts. And has initial issues.
My Plan:
I researched and came to conclusion that i need to flash the radio.
But before i see i need to flash the Firmware.
In order to flash the firmware i need to Get S-OFF.
Ran RumRunnerr, FireWater, MoonShine they all crash at one point or another.
So Im stuck and idk what to do. Unable to go stock or fix the present. Any ideas?
Screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other Comments:
Im kinda new to this. had a few successful Roots but when it came to mods I bricked two phones now.
Level of knowledge 4/10. Have basic Terminology down.
ShoutOut: ViperOne is beast. Love it - if it would work. But Venom Team did an outstanding job. :good:
Oh and btw my HTC ONE is Blue lol.. hope that helps x)
TimFUSE said:
Phone Info:
SPRINT HTC ONE M7
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: #my number#
(bootloader) imei: #my number#
(bootloader) meid: #my number#
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Symptoms:
No Service
Doesnt show my Basband num, IMEI, MEID, NetWork, IP in UI (but it shows up when i Run "Fastboot getvar all".
Progress com.htc.htcdialer isn't responding.
Boot loops every 5-7 min.
What I did:
Last weeks i bricked my sch-i500 so even though I have Verizon I went out to buy HTC one on sprint (hoping i cant make it work on Verizon).
So i unlocked BootLoader and Rooted the device. Yet for some reason SU wasn't working right - i didnt have root rights.
So i decided to Mod flash it. Made a backup in TWRP, wiped: dalvik, cache, data. and successfully flashed Android Revolution HD 53.0.
But I guess not. Because once i rebooted my screen tripped pink right before the boot animation and never loaded into UI.
I restarted it and gave it another 10 min of loading time - nothing.
I wiped after the previous ROM and flashed Venom ROM, ViperOne 6.2.0.
This one took long to boot up as well but once it did it would just show HTC logo screen upon screen unlock.
I gave it time and it actually brings up the "get started page" 5 min in - problem is it would reboot 1 min after.
After i flashed kernel.
Newest version of Gapps.
Tried LiquidSmooth Rom - that would boot me up but didn't solve my issue plus it didn't have google play and other apps.
I even tried going back to the recovery. It would SPRINT it back into stock yet have the acquired issues since i installed the mod: show HTC logo screen once it entered the UI and the rest of bs
I managed to get the get started page and run through it real quick before it rebooted.
But it had no service, and all those issues i stated above.
Now i came back to ViperOne and once the logo screen flashed to "get started" i ran through it real quick and now thats where im at. But it restarts. And has initial issues.
My Plan:
I researched and came to conclusion that i need to flash the radio.
But before i see i need to flash the Firmware.
In order to flash the firmware i need to Get S-OFF.
Ran RumRunnerr, FireWater, MoonShine they all crash at one point or another.
So Im stuck and idk what to do. Unable to go stock or fix the present. Any ideas?
Screens:
Other Comments:
Im kinda new to this. had a few successful Roots but when it came to mods I bricked two phones now.
Level of knowledge 4/10. Have basic Terminology down.
ShoutOut: ViperOne is beast. Love it - if it would work. But Venom Team did an outstanding job. :good:
Oh and btw my HTC ONE is Blue lol.. hope that helps x)
Click to expand...
Click to collapse
okay qiute a lot of work you did there... i personally recommend mooshine s-off.. i also didnt get s-off in rumrunner and firewater kept crashing... try moonshine on a windows 7 pc, it'll work for sure... and after that run RUU of your preferred choice of base band and it should fix your problem...:fingers-crossed:
praveensk.rcb said:
okay qiute a lot of work you did there... i personally recommend mooshine s-off.. i also didnt get s-off in rumrunner and firewater kept crashing... try moonshine on a windows 7 pc, it'll work for sure... and after that run RUU of your preferred choice of base band and it should fix your problem...:fingers-crossed:
Click to expand...
Click to collapse
yea.. i forgot to write moonshine in there
I've tried all them bottles out there and none of em buzz me up right.
TimFUSE said:
yea.. i forgot to write moonshine in there
I've tried all them bottles out there and none of em buzz me up right.
Click to expand...
Click to collapse
are you trying it in windows 7 pc or in windows 8.1... because in windows 8.1 there is no driver support and there is chances of bricking the phone...:fingers-crossed:
praveensk.rcb said:
are you trying it in windows 7 pc or in windows 8.1... because in windows 8.1 there is no driver support and there is chances of bricking the phone...:fingers-crossed:
Click to expand...
Click to collapse
It doesnt matter .. i am able to do everything on win8.1 pc as i am in win7. All you have to do is find and install correct drivers if they dont install automatically.
Although attempting S-OFF methods were done on win7 PC.
But in any case I appreciate your input because i started getting a feeling that no-one replies to new posts now.
Apart from that you pushed me to go out and research more and i found a simple method that took me back to stock in about 20 min.
This post saved my crying soul.. thank you - O.M.J
And thank you - praveensk.rcb. You're a good friend :fingers-crossed:
Important note
If anyone will find the method above helpful - something to keep in mind - it wipes your internal storage.
So if you have somth on your internal SDCard that you dont wanna loose - u know what to do.
TimFUSE said:
Important note
If anyone will find the method above helpful - something to keep in mind - it wipes your internal storage.
So if you have somth on your internal SDCard that you dont wanna loose - u know what to do.
Click to expand...
Click to collapse
its ok timFUSE... glad your phone is up and running...:highfive::victory:
praveensk.rcb said:
its ok timFUSE... glad your phone is up and running...:highfive::victory:
Click to expand...
Click to collapse
I also found out what the problem was.
My TWRP was not designed for Sprint HTC One.
Sprint requires its own TWRP to flash properly.
So now i ROMed into ViperOne 6.2.0 :highfive:
Need Help!
Hey guys i'm getting an active cmdline over flow on my Sprint Htc One that i sim unlocked to use on a GSM network. Sadly along with that i'm constantly dropping and reconnecting to the network.
It appears that my mmcblk0p19 seems to be corrupted.
So my question is can anyone who has a Sprint Htc One PN072 pull the misc partition from their phone and upload it so that i may compare and fix mine?
in custom recovery, do the following adb commands:
adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img
adb pull /tmp/mmcblk0p19_bak.img
Any assistance will be greatly appreciated
relic626 said:
Hey guys i'm getting an active cmdline over flow on my Sprint Htc One that i sim unlocked to use on a GSM network. Sadly along with that i'm constantly dropping and reconnecting to the network.
It appears that my mmcblk0p19 seems to be corrupted.
So my question is can anyone who has a Sprint Htc One PN072 pull the misc partition from their phone and upload it so that i may compare and fix mine?
in custom recovery, do the following adb commands:
adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img
adb pull /tmp/mmcblk0p19_bak.img
Any assistance will be greatly appreciated
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showpost.php?p=42351491 :fingers-crossed:
Thanks but.....
praveensk.rcb said:
try this http://forum.xda-developers.com/showpost.php?p=42351491 :fingers-crossed:
Click to expand...
Click to collapse
Seems legit but like i said my mmcblk0p19 appears to be corrupted here's a SS of the fist page of code.
Keep in mind i have no idea of how it's supposed to look.
https://www.dropbox.com/s/rmfk256r1wtl8fm/Screenshot 2014-05-16 22.45.07.png
Problems. Lots of Problems.
TimFUSE said:
I also found out what the problem was.
My TWRP was not designed for Sprint HTC One.
Sprint requires its own TWRP to flash properly.
So now i ROMed into ViperOne 6.2.0 :highfive:
Click to expand...
Click to collapse
I had no signal on my ROM after fixing a bunch of other issues, Now my HTC is relocked, tampered, and i get the "unfortunately qualcomm enhanced location service has stopped" error after I get past the lockscreen. I really need help the sooner the better thank you in advanced!!
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *************
(bootloader) imei: *****************
(bootloader) meid: ***************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
As the Title suggests this is the root problem of why I have gone through all the stuff I have. I have an HTC One that doesnt have any data (when I say data in this instance I also mean no cell service too).
My father-in-law has given me this phone to see if I can do anything with it. Data shows it is unavailable. Every once in a while bars will be full but will be on either G or E network, and if a text message is waiting to be sent or delivered, it will eventually come through. When I say eventually I mean after an hour or so--I guess when it hits that exact moment I get cell service, but then bars are gone and nothing. So cell service and data are pretty much shot and do not work at all. Only thing is said that has happened just recently is he had it in his back pocket and sat on it very briefly and noticed it immediately. But he didnt notice any problem until about a few days later when all of a sudden no data at all--couldn't make phone calls or browse the internet unless on WiFi. Wifi by the way works perfectly.
So I am approaching it from both Software and Hardware side. I approached Software first mainly because I saw videos on how to open this and it looks like a nightmare that only ends in a cracked screen. Here is what I did
1. Unlocking Bootloader
2. Installing TWRP and rooting
3. Different Roms (No roms seem to help)
So I have a HTC One that is fully rooted with recovery. The only thing I don't have is S-Off which I will be willing to try if it will help with Sunshine S-Off.
I figure Hardware could be a problem, because maybe when he sat on it, it just so happened that he pulled an antenna away from the connection. I noticed from the videos that there are 3 antenna located on the back. And I was just thinking maybe one of these got pulled away and is barely making a connection.
So my questions before I try to open this thing is as my last resort are:
1. Does this sound like a Radio Issue? I was always under the impression that the Radio is flashed with the Rom, but I could be mistaken? If it isn't flashed with a Rom, do I have to be S-Off to flash the Radio? Or is it a simple zip that you install from fastboot or Recovery.
2. Would S-Off help me in this problem maybe by doing something else. I know I read that reflashing the boot.img helped some, but for the life of me, I cannot get it done. I have extracted the boot.img from the rom I am using but I cannot get it flashed. It just stops on <waiting for device> when adb devices show that the phone is recognized and authorized. When I tried moonshine s-off everything is being recognized but it errors out at the rom is incompatible.
Any help is greatly appreciated in this problem. Thanks a lot for any replies
beeson76 said:
As the Title suggests this is the root problem of why I have gone through all the stuff I have. I have an HTC One that doesnt have any data (when I say data in this instance I also mean no cell service too).
My father-in-law has given me this phone to see if I can do anything with it. Data shows it is unavailable. Every once in a while bars will be full but will be on either G or E network, and if a text message is waiting to be sent or delivered, it will eventually come through. When I say eventually I mean after an hour or so--I guess when it hits that exact moment I get cell service, but then bars are gone and nothing. So cell service and data are pretty much shot and do not work at all. Only thing is said that has happened just recently is he had it in his back pocket and sat on it very briefly and noticed it immediately. But he didnt notice any problem until about a few days later when all of a sudden no data at all--couldn't make phone calls or browse the internet unless on WiFi. Wifi by the way works perfectly.
So I am approaching it from both Software and Hardware side. I approached Software first mainly because I saw videos on how to open this and it looks like a nightmare that only ends in a cracked screen. Here is what I did
1. Unlocking Bootloader
2. Installing TWRP and rooting
3. Different Roms (No roms seem to help)
So I have a HTC One that is fully rooted with recovery. The only thing I don't have is S-Off which I will be willing to try if it will help with Sunshine S-Off.
I figure Hardware could be a problem, because maybe when he sat on it, it just so happened that he pulled an antenna away from the connection. I noticed from the videos that there are 3 antenna located on the back. And I was just thinking maybe one of these got pulled away and is barely making a connection.
So my questions before I try to open this thing is as my last resort are:
1. Does this sound like a Radio Issue? I was always under the impression that the Radio is flashed with the Rom, but I could be mistaken? If it isn't flashed with a Rom, do I have to be S-Off to flash the Radio? Or is it a simple zip that you install from fastboot or Recovery.
2. Would S-Off help me in this problem maybe by doing something else. I know I read that reflashing the boot.img helped some, but for the life of me, I cannot get it done. I have extracted the boot.img from the rom I am using but I cannot get it flashed. It just stops on <waiting for device> when adb devices show that the phone is recognized and authorized. When I tried moonshine s-off everything is being recognized but it errors out at the rom is incompatible.
Any help is greatly appreciated in this problem. Thanks a lot for any replies
Click to expand...
Click to collapse
First can you tell us a little more about your phone (post the output of "fastboot getvar all" except your imei and serialno). That will help determine what you can try on the software side.
Also make sure that your IMEI isn't blacklisted (shouldn't happen if the phone isn't declared lost/stolen or linked to unpaid bills). You might also want to try another sim card and check if its better or not (also try your sim card in another phone).
alray said:
First can you tell us a little more about your phone (post the output of "fastboot getvar all" except your imei and serialno). That will help determine what you can try on the software side.
Also make sure that your IMEI isn't blacklisted (shouldn't happen if the phone isn't declared lost/stolen or linked to unpaid bills). You might also want to try another sim card and check if its better or not (also try your sim card in another phone).
Click to expand...
Click to collapse
Thanks Alray for the reply. I guess I should of mentioned that my father-in-law is on ATT. After the loss of network, he tried his wifes sim card in his phone. It didnt work. So he tried his sim card in his wife's phone and it worked fine. So he went to the ATT store and got another sim card just thinking something happened to the sim card and that new sim card didn't work as well in his phone. So when I got it, I put in my sim card which is off the Straight Talk Network which is using the ATT network and it didnt' work. So after troubleshooting it with the Sim Cards, I feel the Sim Cards are not the problem.
This is where I am having a problem. Whenever I type anything fastboot all I get is <waiting for device>.
ADB recognizes the phone being connected and I can do anything ADB.
Any other way of using "fastboot getvar all" to get the information.
Thanks again for the help. Keep it up I really appreciate it.
This is what I am getting when I type "fastboot getvar all"
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT36XXXXX720 device
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>fastboot getvar all
< waiting for device >
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>adb devices
List of devices attached
HT36XXXXX720 device
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>
X's are what I put in there. "adb devices" was used before and after the fastboot getvar all command. So it is seeing the device. Just not doing anything fastboot. I know this is probably something simple. What I do is make a platform tools folder that I keep everything in and I keep that on my Desktop of my computer. For me it keeps everything organized for the project I am working on. Would that mess anything up with Fastboot.
beeson76 said:
This is what I am getting when I type "fastboot getvar all"
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT36XXXXX720 device
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>fastboot getvar all
< waiting for device >
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>adb devices
List of devices attached
HT36XXXXX720 device
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>
X's are what I put in there. "adb devices" was used before and after the fastboot getvar all command. So it is seeing the device. Just not doing anything fastboot. I know this is probably something simple. What I do is make a platform tools folder that I keep everything in and I keep that on my Desktop of my computer. For me it keeps everything organized for the project I am working on. Would that mess anything up with Fastboot.
Click to expand...
Click to collapse
fastboot commands only works from the bootloader as opposed to adb commands which are working from the OS or from a Custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome Alray. Thanks for your help and for the nice chart your provided. Here are the results of the fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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.094s
Thanks for the help and I hope this can help getting the problem solved
beeson76 said:
Awesome Alray. Thanks for your help and for the nice chart your provided. Here are the results of the fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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.094s
Thanks for the help and I hope this can help getting the problem solved
Click to expand...
Click to collapse
Maybe you should try to flash the latest AT&T RUU (7.23.502.1). If the problem persist after flashing the RUU and setting the correct AT&T APN, its probably an hardware problem since the RUU will flash everything (software and firmware) back to stock.
The 7.23.502.1 RUU can be found in this thread at post #1: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944. Instructions how to flash the RUU in the same post. BUT you'll need to follow instructions at the end of post #2 before flashing the RUU (downgrading the version-main from 7.23.502.4 to 7.23.502.1).
SOLVED - SEE POST #5 2)
I'm starting this thread for @Utz2006, he contacted me via PM since he couldn't post relevant pictures/links of his problem because of the 10 posts rule.
So here it goes:
'Standard' M7 with 4.4.3 (bought like this) -
Whatever I tried so far didn't work, system updates from htc don't install, unlocking with unlock_token results in "remote: partion does not exist" . Strangely enough the 'Device serial number' is composed of 12 zeros...etc etc - I have attached some pictures with the basic info...any help and pointers in the right direction will be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Regards Utz
The pictures are also in my profile album...
Kind regards
Utz
Click to expand...
Click to collapse
First thing that is really interesting is the bootloader picture showing "M7_UL PVT MFG RH" instead of "M7_UL PVT SHIP RH". MFG afaik stands for Manufacturing.... You probably got your hands on a test unit, I guess that phone wasn't supposed to be sold on the market
2nd, the Hboot version is 1.55.1. Never seen this hboot version before, we all know 1.55 but 1.55.1 ? Also really strange to see the MID written on the same line just after the hboot version.. Probably related to the PVT MFG thing.
I don't know if your bootloader unlocking problem is because the phone being a PVT MFG instead of a regular PVT SHIP version or because something else. Can you be more precise about system updates? They are not installing or updates are not detected at all? Any error message/code when trying to install an update?
Would like to see your output of "fastboot getvar all" first. Also make sure that only your M7 is detected by fastboot using the "fastboot devices" command. Maybe its trying to send the Unlock_code.bin to another device (if fastboot detects more than one).
Well...it's detecting the updates (actually pestering me all the time to download it) but neither the ota nor the ruu versions install...downloading works, but installing stops somewhere and just goes back to the installed version (not that I am particularly interested in the stock version). Maybe it doesn't work with the developer version...? I also got a reply from Hansoon stating that the bootloader IS unlocked and has s=off. So the next step is trying to flash a custom recovery...when I bought the phone it said actually something about 'refurbished test unit'...which at that time didn't mean anything to me ...
Utz2006 said:
Well...it's detecting the updates (actually pestering me all the time to download it) but neither the ota nor the ruu versions install...downloading works, but installing stops somewhere and just goes back to the installed version (not that I am particularly interested in the stock version). Maybe it doesn't work with the developer version...? I also got a reply from Hansoon stating that the bootloader IS unlocked and has s=off. So the next step is trying to flash a custom recovery...when I bought the phone it said actually something about 'refurbished test unit'...which at that time didn't mean anything to me ...
Click to expand...
Click to collapse
The bootloader is locked (see your pictures). Can you please post your fastboot getvar all? I think it might be possible to ruu but youll need to flash firmware first. Ive seen a post on gsm forum of someone having the same problem
Result of getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.1000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT MFG
(bootloader) serialno: HT44GW904068
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4044mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: MFG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ca9de410ef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Result of trying alternative recovery :
C:\fastboot>fastboot boot recovery.img
downloading 'recovery.img'...
OKAY [ 1.607s]
booting...
OKAY [ 0.001s]
finished. total time: 1.609s
Htc recovery screen locked…second issue of above command wants to download non-existing boot.img…
Just checking (again) what’s connected…
C:\fastboot>fastboot devices
HT44GW904068 fastboot
Trying to flash the recovery….
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (12936 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
Utz2006 said:
Result of getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.1000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT MFG
(bootloader) serialno: HT44GW904068
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4044mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: MFG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ca9de410ef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Result of trying alternative recovery :
C:\fastboot>fastboot boot recovery.img
downloading 'recovery.img'...
OKAY [ 1.607s]
booting...
OKAY [ 0.001s]
finished. total time: 1.609s
Htc recovery screen locked…second issue of above command wants to download non-existing boot.img…
Just checking (again) what’s connected…
C:\fastboot>fastboot devices
HT44GW904068 fastboot
Trying to flash the recovery….
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (12936 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
Click to expand...
Click to collapse
It's S-OFF so it should be easy to convert it to a retail (PVT SHIP) version. I see 2 possibilities:
1- You can flash a custom recovery masked in a firmware.zip file instead of flashing it using "fastboot flash recovery" (btw, "fastboot boot recovery.img" was only working on hboot 1.44, command was disabled on newer hboot version). The custom firmware.zip should be accepted by your phone since it's S-OFF. (This is a well known method used to flash recovery on a locked but s-off bootloader)
e.g:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
where "firmware.zip" is a zip file containing twrp recovery .img file and the android-info.txt file matching your phone info (if you are unsure about that, I can make a firmware.zip for you, just ask if you need.
Once the recovery is flashed you could flash a custom rom of your choice
Problem (if its a problem) is that your phone will still run that strange 1.55.1 hboot, still be a pvt-mfg version.
2-You can update your firmware (i.e from 6.09.401.5 to 6.09.401.10) and then flash the 7.19.401.51 ruu. This is what someone from gsmdevelopers.com/ did to convert his pvt-mfg phone to a "normal" pvt-ship and updated version. (this is what I would personally do).
https://www.androidfilehost.com/?fid=95784891001603802
https://www.androidfilehost.com/?fid=24369303960689843
https://www.androidfilehost.com/?fid=24341993505161791
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_6.09.401.10.zip
fastboot flash zip M7_UL_Firmware_6.09.401.10.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_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
fastboot reboot
BIG THANKS for the info and research ! Since I rarely touch the gadgets once they do what I (!) want...
Alray you're my hero - at least for today )
I used the second method and everything worked like a charm...BIG THANKS!
Now the ten thousand dollar question...which rom ? Something not too fancy which is reliable, no battery hog and only minimal Google installs.....any suggestions?
Utz2006 said:
BIG THANKS for the info and research ! Since I rarely touch the gadgets once they do what I (!) want...
Alray you're my hero - at least for today )
I used the second method and everything worked like a charm...BIG THANKS!
Now the ten thousand dollar question...which rom ? Something not too fancy which is reliable, no battery hog and only minimal Google installs.....any suggestions?
Click to expand...
Click to collapse
Glad to know it worked :highfive:
What rom type do you want? With HTC sense or not?
I was using InsertCoin 7.1.3 for a while and it was really stable (Android 5.0.2 + Sense 7)
Not tried any 6.0 roms since they were apparently unstable and not battery friendly...
Now I'm using Resurrection Remix 5.8.0 (android 7.1.1) Which i found is the most stable Nougat rom for me at the moment. You can flash the minimalist gapps package on it. You really have to try a few roms to know which one is the best for you.
out of curiosity, is your phone still s-off or the conversion turned it back to s-on ? Does the bootloader still says PVT MFG or its now PVT SHIP ?
...I was so happy that I didn't even look at the bootloader....I'll keep you posted!
As to the rom...is there any real advantage with the nougat version? Or is it more the experiment thrill?
Utz2006 said:
...I was so happy that I didn't even look at the bootloader....I'll keep you posted!
As to the rom...is there any real advantage with the nougat version? Or is it more the experiment thrill?
Click to expand...
Click to collapse
There are some interesting new features like long-pressing an app icon brings up a menu of common in-app actions, split windows, the possibility to use the Pixel launcher... Nice features but I could live without them. The biggest letdown for me is that Xposed isn't compatible yet (not for to long I hope).
Thank you so much for this. I had exactly the same problem as OP and this solved it beautifully.
Hi. Everyone I just bought a second hand HTC One M7 and the phone has software issues. I already researched hours into it and tried to fix it by my self but it seems that HTC phones are the hardest phones to fix... So when I start the phone it goes into a infinite bootloop, if I start the bootloader by holding volume down + power, the phone goes into hboot and shows this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it looks like the phone's bootloader is Locked and S-ON.
Now going deeper into the rabbits hole, the phone appears to be SuperCID 11111111, but who knows? Maybe the previous owner changed its CID...?
(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: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA416W901137
(bootloader) imei: 3594050*******
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3795mV
(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
Anyway I tried, Factory Reset, NOTHING, I tried Recovery, nothing, still infinite bootloops. I tried making the phone S-OFF with rumrunner_HTC_0.5.0 and damn I can't even do that. It says "Failed"....
I tried flashing this zip RUU with fastboot: PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip
And it says FAIL file too large or something... the file is about 1.56GB
I even tried copying the RUU archive on a memory flashdrive and connect it via OTG cable. I saw on many threads on this forum suggestions that if the phone can't be flashed through a computer + fastboot, then it must be flashed via "SD card method". What in the world does this even mean? I don't understand?? M7 does NOT have a SD card slot.
Maybe the previous owner accidentally flashed a wrong rom? I don't know, all I know is that this phone consumed at least 12 hours of my time and all for nothing, I still haven't fixed it.
Can someone help me fix this phone? I would be very grateful!
Ok, forget all of that. I finally managed to flash the ROM PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip, I was stunned when I was greeted with a "Success!" message in fastboot, I rebooted the phone but the phone is still not repaired. I still get bootloops, same behavior, any ideas? Should I try a different ROM? What do you recommend? The phone behaves as if I didn't flash anything....
Thanks!
myrunes said:
Ok, forget all of that. I finally managed to flash the ROM PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip, I was stunned when I was greeted with a "Success!" message in fastboot, I rebooted the phone but the phone is still not repaired. I still get bootloops, same behavior, any ideas? Should I try a different ROM? What do you recommend? The phone behaves as if I didn't flash anything....
Thanks!
Click to expand...
Click to collapse
7.18.709.151 is a M7_U ruu (for the non-LTE variant).
Try with the 7.19.401.51 version and post results (a screenshot or cpoy/paste of your cmd window)
Don't forget that you must use htc_fastboot.exe to flash the ruu (not fastboot.exe form google)
alray said:
7.18.709.151 is a M7_U ruu (for the non-LTE variant).
Try with the 7.19.401.51 version and post results (a screenshot or cpoy/paste of your cmd window)
Don't forget that you must use htc_fastboot.exe to flash the ruu (not fastboot.exe form google)
Click to expand...
Click to collapse
I also tried this:
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_4588 03_signed.zip
and this
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed_2_4.zip
and it didn't work! I even unlocked the Bootloader, its all good it says "unlocked tampered" now, then installed both TWRP and CWM the phone said "OKAY" after installing but then when I go to recovery, NOTHING! It says "Entering Recovery..." then the phone goes into endless restarts. Perhaps my phone has hardware damage such as a failed NAND chip? At this stage I'm really leaning towards believing that the hardware part, (motherboard) is defective, not just software issues...
There's also a possibility that the phone was flashed with a wrong RUU and this is why its behaving like this however, no matter how wrong the RUU might have been, its still strange that with a unlocked bootloader I cannot properly install a custom recovery such as TWRP.
If Im doing something wrong then please let me know. Thanks
myrunes said:
I also tried this:
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_4588 03_signed.zip
and this
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed_2_4.zip
and it didn't work! I even unlocked the Bootloader, its all good it says "unlocked tampered" now, then installed both TWRP and CWM the phone said "OKAY" after installing but then when I go to recovery, NOTHING! It says "Entering Recovery..." then the phone goes into endless restarts. Perhaps my phone has hardware damage such as a failed NAND chip? At this stage I'm really leaning towards believing that the hardware part, (motherboard) is defective, not just software issues...
There's also a possibility that the phone was flashed with a wrong RUU and this is why its behaving like this however, no matter how wrong the RUU might have been, its still strange that with a unlocked bootloader I cannot properly install a custom recovery such as TWRP.
If Im doing something wrong then please let me know. Thanks
Click to expand...
Click to collapse
When you phone is S-ON it must have a locked or re-locked bootloader to flash RUU. Only with S-OFF you can flash a ruu with an unlocked bootloader. TWRP should flash fine if your bootloader is unlocked. Try MDMower's universal version of twrp: https://android.cmphys.com/twrp-m7/
Try flashing this 7.19.401.51 RUU.zip file.
https://androidfilehost.com/?fid=24369303960689843
Don't forget to relock the bootloader and use htc_fastboot.exe to flash the zip