Database Develop

Help with radio upgrade

I wasn't going to bother with upgrading my radio as don't have any issues, however I get LTE as part of my service plan now and thought, maybe it would be beneficial to do so.
I've got the international HTC One, I bought it before the first OTA update I think, and I rooted it just after. That means I missed out on the 4.2 and 4.2.2 OTA if I'm correct, maybe more updates if there were any.
The only reason I even found out that I may need a radio update is because when I went to get my AR52 update, I got mad and decided to S-Off as well (God bless you firewater!)
I'm not a noob but I'm not up on the differences in radios for the HTC One. Should I flash the latest? And if I do, do I have to re-lock the bootloader? I read in comments that I don't, and I really don't wanna go through the hassle of re-installing and backing up my pics and etc etc.

RAMBOcoder said:
I wasn't going to bother with upgrading my radio as don't have any issues, however I get LTE as part of my service plan now and thought, maybe it would be beneficial to do so.
I've got the international HTC One, I bought it before the first OTA update I think, and I rooted it just after. That means I missed out on the 4.2 and 4.2.2 OTA if I'm correct, maybe more updates if there were any.
The only reason I even found out that I may need a radio update is because when I went to get my AR52 update, I got mad and decided to S-Off as well (God bless you firewater!)
I'm not a noob but I'm not up on the differences in radios for the HTC One. Should I flash the latest? And if I do, do I have to re-lock the bootloader? I read in comments that I don't, and I really don't wanna go through the hassle of re-installing and backing up my pics and etc etc.
Click to expand...
Click to collapse
Post the output of your getvar all

RAMBOcoder said:
I wasn't going to bother with upgrading my radio as don't have any issues, however I get LTE as part of my service plan now and thought, maybe it would be beneficial to do so.
I've got the international HTC One, I bought it before the first OTA update I think, and I rooted it just after. That means I missed out on the 4.2 and 4.2.2 OTA if I'm correct, maybe more updates if there were any.
The only reason I even found out that I may need a radio update is because when I went to get my AR52 update, I got mad and decided to S-Off as well (God bless you firewater!)
I'm not a noob but I'm not up on the differences in radios for the HTC One. Should I flash the latest? And if I do, do I have to re-lock the bootloader? I read in comments that I don't, and I really don't wanna go through the hassle of re-installing and backing up my pics and etc etc.
Click to expand...
Click to collapse
1- No need to (re)lock bootloader if you're S-Off.
2- the firmwares 4.19.401.8 or .9 have the latest WWE radio (working very nicely for me): http://forum.xda-developers.com/showthread.php?t=2365506
3- if you want to try different radios, you can find them here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable zips in custom recovery, no need to wipe or anything, you can change them anytime and try different ones)

Same Question. Here is my GetVAR-ALL
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35VWxxxxxxxx
(bootloader) imei: 35443xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.058s
nkk71 said:
1- No need to (re)lock bootloader if you're S-Off.
2- the firmwares 4.19.401.8 or .9 have the latest WWE radio (working very nicely for me): http://forum.xda-developers.com/showthread.php?t=2365506
3- if you want to try different radios, you can find them here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable zips in custom recovery, no need to wipe or anything, you can change them anytime and try different ones)
Click to expand...
Click to collapse

abdoulwane said:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
finished. total time: 0.058s
Click to expand...
Click to collapse
1- edit your post and remove IMEI
2- same answer as above, except you should use GPE firmware if your using GPE. (radio can be any, try different ones... see which one is best for you)

thanks so much. I'll flash the radio sometime soon. I LOVE S-OFF!!!!

RAMBOcoder said:
thanks so much. I'll flash the radio sometime soon. I LOVE S-OFF!!!!
Click to expand...
Click to collapse
Recommend you keep a few on the phone, and try different ones when you think you're getting bad reception.
(That's what I do :silly: , since no wiping is involved, I just enter recovery, flash radio reboot, and see if it changed anything),
but for me the radio from 4.19.401.8/9: Radio_4A.23.3263.28_10.38r.1157.04L is proving to be the best.
BTW: you can even flash radios with S-On (but not firmware)

raghav kapur said:
Post the output of your getvar all
Click to expand...
Click to collapse
how to get my get var all?
i'm gonna have to do it from my phone right now i'm at work on a pc

RAMBOcoder said:
how to get my get var all?
i'm gonna have to do it from my phone right now i'm at work on a pc
Click to expand...
Click to collapse
1) https://docs.google.com/uc?export=download&id=0B2JzZ_fh3QOGTjdyLUxyYWp4Vms
2) Extract the zip into a folder. Name this folder as 'fastboot'. (Well, u can name it as anything u want)
3) Install HTC Sync Manager from the HTC website
4) On your HTC One, go 2 settings and disable fast boot in power settings
5) Turn off your One
5) Keep the power+volume down pressed till u reach a white screen
6) Press the power button when u see 'FASTBOOT' highlighted. This will put your phone in fastboot mode
7) Open the 'fastboot' folder (or whatever u named it) which u created
8) Shift+Right click inside the folder. Open command prompt here
9) Type this in command prompt WITHOUT the quotation "fastboot getvar all"
10) Ull see a long output. Remove the imei and S/N. Post it here

stuck in boot mode

hi guys, I am stuck in boot mode after removing cyanogen mod, I have tried installing the RUU.exe but it will not complete - I think the reason for this is that S-ON. I can't seem to find a solution to achieve S-off anywhere without having to be into the phones OS.
I have tried pushing the rom to my phone but I just keep getting 'no device found'
The usb recognises the phone but the adb commands do not work at all
any further info suggested would be massively appreciated.
edit:
got adb commands working by following this guide
(not allowed to post links yet)

progress so far:
I have managed to sideload a relevant ROM but it has now been saying 'installing update' for quite a while and I am not sure whether to touch it
on another note, the image verification thing on this forum is very, very annoying.

ok so I sideloaded a ROM and it aborted the installation, totally at a loss now

grantymc said:
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
Click to expand...
Click to collapse
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.

alray said:
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
Click to expand...
Click to collapse
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W914634
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b0a25cb2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

grantymc said:
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
Click to expand...
Click to collapse
Ruu.zip are not installed with a custom recovery/sideloaded!! It must be flashed via fastboot ruu mode. Anyway this ruu is not for your phone, its a .401 base and you need a .61 base ruu of same version or higher than 3.63.61.1 but afaik there is no ruu for your phone... BTW the 1.20.401.1 ruu is a pre-release version without OTA updates so it a bad idea to use it.
grantymc said:
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
Click to expand...
Click to collapse
Either because of a bad rom/download or because your recovery version is outdated. Flash twrp 2.6.3.3 or 2.6.3.4. Also clear cache every time your flash something and md5 check your roms/recovery before you flash them.
grantymc said:
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
Click to expand...
Click to collapse
S-OFF is not require to flash a custom rom like CM only if you want to convert your phone using a ruu not intended for your version.

[Q] Bootloop - Green HTC logo, sometimes Android

Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
My major screwups:
No nandroid backup.
No s-off
I have Sprint
Current State:
I can get to fastboot, recovery and adb works fine. But no matter which recovery/rom combination I try, I get the same end result. My phone will boot to the "HTC One" screen, then go the green HTC logo/white background screen then reboot. Sometimes it stays active long enough to begin the "Welcome to Android" stuff (pick your language, wifi connection, etc...), but not nearly long enough to get through all the screens.
What I've tried so far:
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
ROMS: ARHD 31.6 and 62.0 (I know this doesn't work with Sprint), Viper 6.1 and some "stock" rom I found somewhere (filename One_4.19.401.11_odexed.zip).
I don't remember exactly the order, but I know I did TWRP 2.6.3.4 and ARHD 62.0 first. Then did Viper 6.1, then ARHD 31.6. Since then, I've tried every combination of recovery and ROM that I can think of.
Here's getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.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: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4205mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
I'm willing to try anything at this point. So suggestions are welcome. You're also welcome to berate me for the above mentioned screwups, but it won't be very helpful.
TIA

Goto_End said:
Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
TIA
Click to expand...
Click to collapse
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: http://techerrata.com/browse/twrp2/m7wls
(make sure to check MD5 on the download)

nkk71 said:
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: (can't post links yet)
(make sure to check MD5 on the download)
Click to expand...
Click to collapse
Downloaded the 2.6.3.0 from the link you provided (checked md5), flashed recovery. Did an adb push to get the Viper ROM (also checked the md5) back to /sdcard and flashed the ROM. Same results as before.
Additional info:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
The screen will timeout on the green HTC logo screen. If I hit Power to bring it back to life, I have to "pull to unlock" and either the logo screen is still there or it's made it to "Welcome to Android".
I actually got to the Welcome screen this time. Picked the language, wifi network and started with my Google login before it rebooted.
Maybe an incompatible ROM issue? If so, I'm out of ideas as to what to try next.
I've downloaded what I believe to be the RUU for this model phone, but since I can't see the phone in Windows, I haven't even tried the RUU.

Goto_End said:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
...before it rebooted.
Click to expand...
Click to collapse
That's usually caused by the modem not initializing properly, and you could have some corrupt partitions due to using an m7_u/ul and it's time for ruu i guess.
Better head over to the HTC One Sprint forum: http://forum.xda-developers.com/sprint-htc-one should be plenty of help there.
Most of us here are on m7_u/ul so can offer only limited assistance... could be as simple flashing a radio for Sprint... but like I said, I'm not too familiar with Sprint unbrick.
Sorry & Good Luck

There's an awesome Rescue Tutorial over in the Sprint HTC One forum for people like me who flashed a GSM ROM on a CDMA phone. I can't post links yet, or I'd link to it just for posterity.
In essence, the GSM ROMs screw up the partition table. The fix was really easy. Most of the time was spend downloading the correct ROM and waiting for the adb push.

HTC ONE Bootloop

Hello,
I hope somebody can help me with a new HTC One. It stucks in bootloops. Sometimes I can get to the lockscreen: But when I unlock the device the HTC-logo shows up and the phone restarts again. Some ideas to solve my problems? I thought I could flash the ruu with fastboot? but it failed - well, maybe it was the wrong firmware or did another mistake..
The device is locked - so no recovery and no root, but I can reach the bootloader
Hboot 1.57.0000
firmware 5.12.206.3
UPDATE
Oh well. It is an O2-model.. so I need an O2-ruu and if I can't find an O2-ruu I can't unbrick my phone??!!

seven09 said:
Hello,
I hope somebody can help me with a new HTC One. It stucks in bootloops. Sometimes I can get to the lockscreen: But when I unlock the device the HTC-logo shows up and the phone restarts again. Some ideas to solve my problems? I thought I could flash the ruu with fastboot? but it failed - well, maybe it was the wrong firmware or did another mistake..
The device is locked - so no recovery and no root, but I can reach the bootloader
Hboot 1.57.0000
firmware 5.12.206.3
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
UPDATE
Oh well. It is an O2-model.. so I need an O2-ruu and if I can't find an O2-ruu I can't unbrick my phone??!!
Click to expand...
Click to collapse
1st of all delete IMEI No & serial number from your post above
Go to bootloader select recovery
In recovery wipe cache and restart
( If recovery not show menu then press volume up 1st + power button 2nd for 5 secs then leave power button then volume it will show menu )
If wipe cache not working you have to factory reset your phone from bootloader
This problem arises when any installed app trouble with boot or corrupt app data

Thanks for your reply..
but nothing worked. I opened the bootloader and installed cwm. After that I tried to restore an old backup, which I found on the Internet and flashed a custom rom as well... :S
Oh now it boots
But every 2 min my device reboots... ??

seven09 said:
Thanks for your reply..
but nothing worked. I opened the bootloader and installed cwm. After that I tried to restore an old backup, which I found on the Internet and flashed a custom rom as well... :S
Oh now it boots
But every 2 min my device reboots... ??
Click to expand...
Click to collapse
what backup version? If using a backup it must be the same version as your firmware (version shown in bootloader).
You should try to flash a custom like ARHD 83, easiest way to get your device booting again. (use TWRP 2.6.3.3)
There is no RUU for this version, so forget RUU unless you want to convert your phone to another version (s-off required)

alray said:
what backup version? If using a backup it must be the same version as your firmware (version shown in bootloader).
You should try to flash a custom like ARHD 83, easiest way to get your device booting again. (use TWRP 2.6.3.3)
There is no RUU for this version, so forget RUU unless you want to convert your phone to another version (s-off required)
Click to expand...
Click to collapse
hmmm, I already tried AHD 83. but I still get reboots very often
Yes there is no RUU. I thought I could maybe try to get s-off, change the cid and install another RUU.. But I dunno if it would solve my Reboot-problem.. Maybe, but I do not want to pay 25 bucks for nothing (sunshine - HBoot 1.57)

seven09 said:
hmmm, I already tried AHD 83. but I still get reboots very often
Yes there is no RUU. I thought I could maybe try to get s-off, change the cid and install another RUU.. But I dunno if it would solve my Reboot-problem.. Maybe, but I do not want to pay 25 bucks for nothing (sunshine - HBoot 1.57)
Click to expand...
Click to collapse
If you achieve S-Off to flash a Ruu, and your phone still have the rebooting issue, then youll know its an hardware problem. 25$ worth it imo

[Q] Cannot install any ROM's at all, but can access bootloader.

Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.

Loafmanuk said:
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Click to expand...
Click to collapse
ok first of all, you need to use TWRP latest for Lollipop custom roms, 2.6.3.3 is too old, use 2.8.6.0, also, expect problems with Lollipop roms whilst your still on KitKat firmware (hboot 1.57), you really need to be on Lollipop firmware to use Lollipop custom roms.
People using the latest Lollipop custom roms on KK firmware are reporting no wifi, Bluetooth issues etc.
can you post your fastboot getvar all please without imei and serial number please.

Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.

BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.

Loafmanuk said:
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
Click to expand...
Click to collapse
yup shows me a lot of info: 6.16.61.8 this shows me your on Orange UK network, although its now T-Mo & Orange together as EE, sorry but they've not released the Lollipop update yet for the 61's which is the 3rd set of numbers pulled from that long number above, this also confirms your on orange UK ORANG001 and so does this: PN0710000 kind of......... long story
m7_ul this tells me you have the LTE version of the M7
4275mV battery info = good
4T.28.3218.04 radio version
1.57.0000 hboot version
(bootloader) security: on (bootloader) build-mode: SHIP PVT SHIP S-ON basically your s-on
it would show your imei number and serial number too, but you want to keep those 2 numbers to yourself.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Loafmanuk said:
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Click to expand...
Click to collapse
plug your phone into the computer whilst its booted into recovery main screen only, the internal storage of your phone should open on your computer, copy the rom.zip to your internal storge, unplug and flash it.
I'm pretty sure 2.8.6.0 supports usb otg, you may have to select it as a storage option first as it defaults to internal storage, cant quite remember as I'm on an M8 now.
edit: yes it does, select install and then at the top change from internal storage to usb otg.

I've re installed TWRP 2.8.6.0 and finally got it to see the USB stick (reformatted it). But when I try and install it seems to be going ahead, but after a minute or to I get the TeamWin splash screen flash up as though recovery is booting and it returns to the main menu. Oddly, the LED on the memory stick is still flashing!?!
I'll try installing from the phones internal memory like you suggested and hopefully that will work. Thank you so much for this, I'll update in a while.

Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.

Loafmanuk said:
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Click to expand...
Click to collapse
you are very welcome, I just use my USB OTG for backup's and restores, never tried flashing a rom from it.