Hi I bought my phone as is(^) but I figured it could be brought back to life.
it was stock rom & had s-off, I unlocked the bootloader & rooted. tried giving it factory reset, clear cache reinstalled stock etc,
now I tried putting a custom rom on it hoping to get passed the htc screen no luck
It reboots every 60sec only way to shut it down is through bootloader, I have a custom recovery as well
Has anyone had any similar issues?? - thanks in Advance
jaimemetoyer said:
Hi I bought my phone as is(^) but I figured it could be brought back to life.
it was stock rom & had s-off, I unlocked the bootloader & rooted. tried giving it factory reset, clear cache reinstalled stock etc,
now I tried putting a custom rom on it hoping to get passed the htc screen no luck
It reboots every 60sec only way to shut it down is through bootloader, I have a custom recovery as well
Has anyone had any similar issues?? - thanks in Advance
Click to expand...
Click to collapse
Something similar happened to me today as well. Device just froze and I had to do a hard rest. Same problem. Performed a Factory Reset. Same problem. Left it on the HTC One Screen for two hours, still frozen.
Not having the rebooting issue though.
Try running a ruu
Sent from my HTC One using Tapatalk
Same issue here. Ran an updated RUU which took me to 4.3 and it updated my hboot to 1.55 from 1.44. I can load stock and custom recoveries through fastboot but I cannot boot into recovery. I am **tampered** **unlocked s-on** and cant even relock to run ruu again. Any ideas? Here is a copy of my fastboot getvar all:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: HT346Wxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3967mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Thanks!
Hi, I am experiencing the same issue. Is there any fix? I've deleted my entire internal memory like a dumb ass. I can still access TWRP and bootloader. S-OFF and unlocked. I've tried installing multiple roms: trickdroid, google stock, qx senseless. But they all just reboot after 60 seconds. Can't find my RUU, CID = Roger001. Any help will be appreciated
Related
I hope not to make a duplicate thread but sorry if I do.
I took on this project trying to help a friend out. This is the first VZW phone I've operated on. I've been to multiple threads on different websites and tried various procedures all to no avail.
This phone was all stock b4 the update....tried to take the update and has been in a bootloop ever since.....phone gets stuck at the white HTC quite briliant screen.
I've tried unlocking the bootloader via revone but for some reason adb will not recognize the phone....although fastboot commands are not a problem....
I'm almost at the point of installing some linux distro just so I can try moonshine..
I've tried 2 different RUU's for this phone....both fail....
HTCdev failed me also.....couldnt get the token....smh
Turning the phone back in to VZW wasnt an option because is was opened previously...warranty voided.
any help would be good help as far as I'm concerned.
I'm still trying to figure out how to find out what firmware is on the phone....and I take it "fastboot getvar all" doesnt tell you that...
On both RUU's that I have...they tell me that I have image 4.09.(xxx) <---I cant remember the last digits right now
**SOLVED** HERE'S THE THREAD THAT HELPED ME. https://forum.xda-developers.com/droid-dna/general/official-exe-ruus-s-t2935556
MUCH THANKS TO @dottat :good::good:
DuceTheTruth said:
I hope not to make a duplicate thread but sorry if I do.
I took on this project trying to help a friend out. This is the first VZW phone I've operated on. I've been to multiple threads on different websites and tried various procedures all to no avail.
This phone was all stock b4 the update....tried to take the update and has been in a bootloop ever since.....phone gets stuck at the white HTC quite briliant screen.
I've tried unlocking the bootloader via revone but for some reason adb will not recognize the phone....although fastboot commands are not a problem....
I'm almost at the point of installing some linux distro just so I can try moonshine..
I've tried 2 different RUU's for this phone....both fail....
HTCdev failed me also.....couldnt get the token....smh
Turning the phone back in to VZW wasnt an option because is was opened previously...warranty voided.
any help would be good help as far as I'm concerned.
I'm still trying to figure out how to find out what firmware is on the phone....and I take it "fastboot getvar all" doesnt tell you that...
On both RUU's that I have...they tell me that I have image 4.09.(xxx) <---I cant remember the last digits right now
Click to expand...
Click to collapse
We will need the info on the bootloader screen, all of it please. It will provide info which can be useful
.torrented said:
We will need the info on the bootloader screen, all of it please. It will provide info which can be useful
Click to expand...
Click to collapse
Thanks for replying....
***LOCKED*****
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.01.1112
OpenDSP-v-10.120.274.0520
OS-4.09.605.1
eMMC-boot 2048MB
Mar 13 2014, 19:19:14.0
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4225mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
DuceTheTruth said:
Thanks for replying....
***LOCKED*****
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.01.1112
OpenDSP-v-10.120.274.0520
OS-4.09.605.1
eMMC-boot 2048MB
Mar 13 2014, 19:19:14.0
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4225mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
Click to expand...
Click to collapse
I can tell you that the phone is indeed on the latest update, bootloader, baseband, and version-main all indicate that it is on the 4.09.605.1 update, have you tried to do a factory reset from within the bootloader/stock recovery?
That may help, may not. since you are locked and s-on, there really isnt much else to do.
Just for the heck of it, have you tried to flash the flashable RUU-ROM.zip from my firmware thread? Probably wont work but idk what else there is to do, being as you are still stock and locked.
.torrented said:
I can tell you that the phone is indeed on the latest update, bootloader, baseband, and version-main all indicate that it is on the 4.09.605.1 update, have you tried to do a factory reset from within the bootloader/stock recovery?
That may help, may not. since you are locked and s-on, there really isnt much else to do.
Just for the heck of it, have you tried to flash the flashable RUU-ROM.zip from my firmware thread? Probably wont work but idk what else there is to do, being as you are still stock and locked.
Click to expand...
Click to collapse
Interesting.....
I have tried the factory reset in the bootloader and it just goes to a picture of a green down arrow with two green arrows in a circle facing clockwise.... Then goes back to white HTC screen...
And I did try the flashable RUU zip.... And I will try it again..
Is it true that have to unlock the bootloader before anything else?
I'm searching for ways to do that while in this bootloop state....
And then possibly downgrading?
And if this phone really is stuck I feel that Verizon is at fault here.. . Even if it was dropped and the back came off....
My friend told me that at the time the update came through he had very little memory....
And I've read elsewhere that the exact same issue caused similar problems on some phones....
I'm surprised there's no class action on the horizon.
Htc black screen with four triangles
Man I really need help. ...I tried to flash and something went wrong to where I erased the entire os and I continued to fix this issue because all I had access to was twrp(custom rom) and bootloader. then what was crazy is that it appeared that based on the fact that I was on 4.4.2 kit kat that I was unable to fix it. after researching I found a ruu that didn't have the boot image so I flashed the factory ruu with no boot image and my htc scrren with the status bar filled all the way up but it never moved off of that screen I assume because that ruu didn't have the boot image so I thought that common sense would be to at one of the boot images that I had to the zip file of the ruu without the boot image....that's when I made things worst and now im stuck on this htc screen with the four triangles...my pc wont detect my device and im in need of some serious help....can you help? can anybody help?
I believe i can help!!!
ducethetruth said:
interesting.....
I have tried the factory reset in the bootloader and it just goes to a picture of a green down arrow with two green arrows in a circle facing clockwise.... Then goes back to white htc screen...
And i did try the flashable ruu zip.... And i will try it again..
Is it true that have to unlock the bootloader before anything else?
I'm searching for ways to do that while in this bootloop state....
And then possibly downgrading?
And if this phone really is stuck i feel that verizon is at fault here.. . Even if it was dropped and the back came off....
My friend told me that at the time the update came through he had very little memory....
And i've read elsewhere that the exact same issue caused similar problems on some phones....
I'm surprised there's no class action on the horizon.
Click to expand...
Click to collapse
whats your current status? I just got myself out of a very bad situation with my htc dna just read some of the stuff ive posted in your thread.....are you s-off or s-on?
CHRIST STARZ said:
whats your current status? I just got myself out of a very bad situation with my htc dna just read some of the stuff ive posted in your thread.....are you s-off or s-on?
Click to expand...
Click to collapse
it is s-on
I'm in the same boat. OTA update crashed and now phone wont boot. It's S-ON with the latest radio and hboot. Apparently you can't downgrade with an older RUU. I cannot seem to find a 4.09.605.5 RUU anywhere. Any suggestions?
Thanks
-CMY
cmylxgo said:
I'm in the same boat. OTA update crashed and now phone wont boot. It's S-ON with the latest radio and hboot. Apparently you can't downgrade with an older RUU. I cannot seem to find a 4.09.605.5 RUU anywhere. Any suggestions?
Thanks
-CMY
Click to expand...
Click to collapse
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
Yah...I was able to recover with some other files. But I have downloaded this and archived it just in case I run into problems in the future. Thanks!
-CMY
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
Here is what I used to resolve my issues back in Nov...
http://forum.xda-developers.com/showpost.php?p=56405268&postcount=4
-CMY
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
That's a rom BTW, and won't flash on an S-on phone. S-on requires encrypted and signed images to restore.
Hence ruu
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
man....i just pulled this phone out the drawer and wiped the dust off lol.....
now im trying to figure out how to make this work
thanks for the post by the way
please can anyone help, firstly i made a massive error installing elitekernel, was running latest viper rom, and s-on
the issue was my internal storage has disappeared....
so firstly i loaded up twrp and wanted to recover to a backup, unfortunately i cant view or mount the internal memory :/
so the xda i came, i found team nocturnals guide, ie booting into fastboot, and flashing the recovery.img then loading factory recovery, everything went like he described. but once twrp was re-installed in adb, still no internal storage
even installed cwm, still no luck
getvarall
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 3.1204.171.33
version-cpld: None
version-microp: None
version-main: 2.18.401.2
product: enrc2b_u
platform: HBOOT-T30S
modelid: PM3511000
cidnum: HTC__001
battery-status: good
battery-voltage: 3642mV
devpower: 16
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
any advise would be great pulling my hair out, can i manually partition the nand flash?
or should i return to stock?
thanks in advance
any help would be great ps i am in the uk, phone is a uk model, unlocked
anyone else had this issue?
hey i am going to return to stock my
CID is htc_001
hboot 1.72.0000
radio is 3.12.4.171.33 version-baseband
version-main: 2.18.401.2
what rru should i use? http://www.androidruu.com/?developer=ENRC2B
any advise would be great, i am totally stuck now....
cant find the ruu i need, i have tried the 02 and voda ruus just gives me an error.....
how can i sort this internal storage issue.....please help
hey guys, so i sort of have sorted this....after trying a few things, i wasn't confident in installing a ruu to factory(dont want to brick my phone)
so i have a sort of fix,
using adb to side load insertcoin.zip, to do this i made sure my bootloader was unlocked, and the latest twrp was installed. once in twrp(i went to advanced and adb side load). then opening a command prompt, i used (adb sideload insertcoin.zip). this loaded over to my phones memory(you will see this as a percent). then installed insertcoin. last step as always due to one x+ having s-on, i used flashed the boot.img from the insertcoin.zip. whoop whoop, system now boots and is usable.....
now the but.....the issue is i have 3 partitions only (system/cache/data=all my usable memory 64gb) no sdstorage partition!!!!!! i cant mount these partitions in twrp. not sure how bad this is????
anyway to repartition my internal memory??? any advised please guys
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(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: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(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: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
The Guru Reset would put you back at stock if you so choose. You are given the option in Aroma to "root", chose that option since you are going on to flash ViperOne.
The Guru Reset should have the same firmware in Aroma check that you want the stock radio this will help in ViperOne. I believe the issue you had earlier was the result of incompatible firmware/radio.
Purple haze issue is more likely hardware, but there has been a lot of pseudo fixes.
Thanks for your reply! Just finished backup so starting on it now. Wish me luck!
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
bzowk said:
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
Click to expand...
Click to collapse
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
majmoz said:
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
Click to expand...
Click to collapse
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
bzowk said:
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
Click to expand...
Click to collapse
You are welcome, glad that you are back up and running! :good:
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(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: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
Theirs one big Flaw in your method DO NOT SKIP from 3.x firmware to 5.x firmware .. you'll end up in QHSUSB_DLOAD mode and that's No fun at all.
The correct way to get to the 5.x firmware is
3.x.502 RUU to 4.x.502 Firmware to 5.x.502 firmware
then the Guru reset
So I managed to break the screen on my OnePlus One so i had to go back to my HOX+ and since i had let a friend borrow it and use while they got their own phone i went to wipe and install a new ROM on it. it was already rooted and unlocked with CM11 running.
i'm not a noob when it comes to android root and stuff but i messed up. i had everything ready, a few different roms i wanted to try out, gapps and superSU all downloaded on my computer and transferred to my phone. i went and did a clean wipe in TWRP 2.8.7.0, installed MIUI7, gapps, and su. it booted fine but i had used the AROMA insaller for gapps and apparently didn't have a keyboard.
so back to recovery i go and for some reason i decided to wipe the phone again instead of doing a dirty reflash and i accidentally checked the mark to wipe the sd storage as well and didnt catch it in time.
now normally you'd just say "dont panic, just go to adb sideload and install through there" np, right?
well it's not that simple for me. every time i try to go through adb sideload i just get an error and i cant figure out why. i've tried different TWRP versions with all the same result, ive even tried Phillz recovery and trying to mount usb storage in that just does nothing.
next step would be to try re doing the phone with a RUU right? well i tried that too and i get error code 158 every time (yes, i remembered to relock the bootloader) i'm gonna be trying the different international RUU's to see if anything will work but i doubt it at this point.
i even tried searching for something to flash from fastboot to hopefully get the device to at least boot so i can transfer things to it so i can get a proper ROM, but nothing.
So, please help me, this is frustrating me to hell and back and i just want this thing to work.
here's the stuff from boot loader in case it helps
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-NONE
MICROP-NONE
RADIO-3.1204-171.33
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013, 17:36:36
and from fastboot getvar all
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 3.1204.171.33
version-cpld: None
version-microp: None
version-main: 2.18.401.2
serialno: FA2C5W102628
imei: 353567051621523
product: enrc2b_u
platform: HBOOT-T30S
modelid: PM3511000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 3791mV
devpower: 35
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
So after giving up on this once and revisiting it i finally figured it out, all thanks to this youtube video /watch?v=H-vf5eHV3_s (im too noob on the forums to post links apparently)
if anyone else has this problem in the future here's the steps i took
install the stock recovery
go into bootloader and hit factory reset
wait and reboot into fastboot
flash twrp or another recovery
enter recovery
and bam, all usb transfers working again
Hello,
After searching for hours and hours, I was not able to find any way to fix the situation. I will try to write out everything that I tried to give a better idea of what works, and possible solutions that I missed. I will really appreciate it if anyone could help me out. Heck, If anyone helps me out, I will make a donation through PayPal. Obviously, I am a little desperate
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: SH365W903916
imei: 357-------------611
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: VODAP001
battery-status: good
battery-voltage: 4328mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-7661b1d7
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Also: this is the RUU I need (or something, I don't really know too much about this) x.xx.161.x – Vodafone UK (United Kingdom)
I accidentally flashed a HTC Droid DNA stock rom.
Now it is stuck on bootloader. When trying to enter recovery it simply reboots into bootloader.
I have a nandroip backup that I made on my PC, but am unable to restore it because I cannot enter recovery. Maybe there is another way of restoring it?
I cannot find a VODAP001 RUU online no matter how hard I look. Any website I find with such an RUU, when I press the link to download, it redirects to the bugsylawson website with the grey screen with a bar.
I have found multiple OTAs but either it is not possible to install it, or I am doing something wrong. I believe I need to do it through recovery, but I can't access recovery.
I found in another thread with a similar problem where they suggest to install a modified recovery. Something with no BCB. This is the thread: https://forum.xda-developers.com/showthread.php?t=2739126
I tried to install the no BCB recoveries but I am still not able to enter recovery. That thread seems to address the problem directly to what I have, but if I can't get into recovery, I can't get past step 1.
When I try to use the CMD command: fastboot boot "name of recovery".img, the bootloader freezes. I have to hold down the power button for a while to unfreeze it. Also, when it is frozen, fastboot does not allow me to erase cache or anything else. Maybe this will mean anything to you.
I can't change CID to be able to RUU using a different RUU because I am S-ON. I can't S-OFF because HBOOT is 1.61. I found that sunshine can make HBOOT above 1.54 S-OFF, but it is an app. I have no rom so this cannot work for me.
I probably missed some other things I tried because I literally tried everything I could find online and in all of the forums.
If anyone can offer any kind of solution, please don't hesitate to write it. Even if you think it will probably not work, I'll still try it