Database Develop

[Q] M7 stuck in boot loop after running RUU.exe

Hello everybody, hope everyone is having a better day than I am. I will try to keep this short but I am more than happy to provide more details as they are needed.
I picked up a replacement HTC One (ATT) after a warranty claim for a bad speaker and I immediately rooted it. After rooting the phone and before flashing a custom rom it started rebooting itself every couple of minutes. I went ahead and flashed a custom rom (many to be honest) and the phone booted up just fine, however, the phone would not recognize the sim card. I tried the sim card in a different phone and it worked fine. Then, with the sim card replaced, all of a sudden the phone worked for about 30 minutes. After that it started rebooting itself at will every couple of minutes. I decided that i must have flashed a bad file or something so i decided to go back to stock with RUU.exe. I locked the bootloader and ran the .exe from my laptop (windows 7) Now my phone i "relocked" and the RUU flashed a recovery that I can not get into. My boot screen now reads this
***relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
(date and time)
this is the RUU.exe I loaded
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2 - HTC1Guru
Now when I start my phone it loads to the ATT screen with the globe, sometimes plays the chim, and then goes to a white screen with the green HTC. after about a minute it reboots and loads to the exact same spot. It will do this until I enter the bootloader and power it down
I don't know what to do anymore as I have read about a thousand threads and I am getting confused on what the next step should be. I would greatly appreciate a point in the right direction.
Although the POS phone I am using with a modified sim card holder is pretty awesome
Thanks in advance

Get ATT to replace to it again?

there is more back story that I did not go into and i don't know if I can get it replaced again.
Now when I turn on the phone it loads to the initial start up screen where it ask to set up my account and set up wifi. but agian after a minute or so it just reboots and loads to about the same spot and then restarts.
I still think this is fixable

Can anyone point me in the right direction?
Thanks

What software version are you on now? I'm not near a computer but my first thought is that because you are s-on, you can not run an RUU that is older than your current version. So if you are on KitKat now, you can't run a Jelly bean 4.3 ruu.
You would need to be s-off in order to do that.
Sent from my HTC One using Tapatalk

to tell you the truth I don't know anymore because i have tried to load so many different things, how can I tell for sure?

another question...Now that I have a relocked bootloader can I try to rerun the RUU.exe file? I will check my getvar this evening to find the correct RUU but just don't know if this will work with a locked bootloader and no recovery.

redraider25 said:
another question...Now that I have a relocked bootloader can I try to rerun the RUU.exe file? I will check my getvar this evening to find the correct RUU but just don't know if this will work with a locked bootloader and no recovery.
Click to expand...
Click to collapse
Sure will work as long as RUU is same level as your phone

I would try re-running the RUU. Sometimes they don't do everything correctly. But done right, it should wipe your phone of any custom software and take you back to clean stock.

Finally made it back home I wanted to post my getvar all so please tell me if you see something bad
c:\miniadb_m7>adb devices
(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: 3.17.502.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: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please advise me if I should still rerun the RUU.exe file above or do I need to do something different first

Well it looks like you are on 3.17 and the Ruu is 3.17 so give it a shot.
Sent from my HTC One using Tapatalk

redraider25 said:
Finally made it back home I wanted to post my getvar all so please tell me if you see something bad
c:\miniadb_m7>adb devices
(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: 3.17.502.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: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please advise me if I should still rerun the RUU.exe file above or do I need to do something different first
Click to expand...
Click to collapse
What about factory reset from bootloader?

42 22435958
Well I tried to RUU.exe again and now the phone will load to the setup. I went through that, but it is not recognizing my sim card. I can sign on to wifi which works and I can navigate the homescreens. after about 2 minutes the phone reboots itself and the whole cycle happens again. i tried to do a software update but with out the sim card being recognized it says Network not available. the signal bar has an "X" and it does not recognize when I try to remove the sim card to reposition it.
should I try a different RUU.exe file? Thanks for all the help, I think we are getting close. One thing I think is strange is when I ran getvar all, it has a strange line I noted it below. Anybody know what this means?
c:\miniadb_m7>fastboot getvar all
(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: 3.17.502.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: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88 THIS LINE HERE!!!!!!!!!!!!!!!!!!!!!!!!!
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance

While the phone is up, can you go to settings > about devices > hardware info> baseband.. is it empty?

The baseband says "unknown"

redraider25 said:
The baseband says "unknown"
Click to expand...
Click to collapse
Its dead Jim.

SaHiLzZ said:
Its dead Jim.
Click to expand...
Click to collapse
really, thats it? No mas htc one for me?
So am I the proud owner of a BRICK?

[Q] Flashed the wrong radio, need help

Hello There,
I have AT&T m7 and recently just S-OFF
I upgraded from 4.4.2 to the 7.15.401.1 firmware in order to flash the GPE 5.1 rom
But now it looks like I flashed the wrong radio or baseband because my cellular data is no longer working (althought I can still make calls)
Here is the output before I began:
Code:
[email protected] ~ $ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34FW910399
(bootloader) imei: 354439053123222
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3875mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
ANd here is the output afterwards:
Code:
[email protected] ~ $ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34FW910399
(bootloader) imei: 354439053123222
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Please help me, I dont know what I did wrong.

fc3211 said:
Hello There,
I have AT&T m7 and recently just S-OFF
I upgraded from 4.4.2 to the 7.15.401.1 firmware in order to flash the GPE 5.1 rom
But now it looks like I flashed the wrong radio or baseband because my cellular data is no longer working (althought I can still make calls)
Here is the output before I began:
Code:
[email protected] ~ $ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34FW910399
(bootloader) imei: 354439053123222
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3875mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
ANd here is the output afterwards:
Code:
[email protected] ~ $ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34FW910399
(bootloader) imei: 354439053123222
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Please help me, I dont know what I did wrong.
Click to expand...
Click to collapse
You flash stock RUU.exe
Sent from my HTC One using XDA Free mobile app

I did not flash the RUU, I had flashed the firmware 7.15.401.1 from https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
And I am thinking that I overwrote the radio with a version that is not proper for my phone.
But I dont really have alot of knowledge about this so please advise me.

fc3211 said:
I did not flash the RUU, I had flashed the firmware 7.15.401.1 from https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
And I am thinking that I overwrote the radio with a version that is not proper for my phone.
But I dont really have alot of knowledge about this so please advise me.
Click to expand...
Click to collapse
it wont effect your phone in that way, if you have signal, then go into your apn settings and reset them to defaults, you will then be taken to the first start up page again and have to select your operator again from the list of available operators, like you did when you first got the phone or when you install a new rom.
remove you IMEI and Serial number from your first post, its not good to post them, they guy who quoted you will also need to do the same.

Seanie280672 said:
it wont effect your phone in that way, if you have signal, then go into your apn settings and reset them to defaults, you will then be taken to the first start up page again and have to select your operator again from the list of available operators, like you did when you first got the phone or when you install a new rom.
remove you IMEI and Serial number from your first post, its not good to post them, they guy who quoted you will also need to do the same.
Click to expand...
Click to collapse
Are you certain about this? The fastboot output indicates that the baseband has changed since I flashed the new firmware

fc3211 said:
Are you certain about this? The fastboot output indicates that the baseband has changed since I flashed the new firmware
Click to expand...
Click to collapse
just try it, its not going to hurt, just goto settings - mobile data - access point names - (3dot menu in the top right corner) select that and then select reset defaults.
Of course the baseband has changed, the newer firmware had a newer radio file in it, its not a radio file like your thinking though, its more of a software controller for a piece of hardw2are in your phone, just like every piece of hardware on your computer needs a driver, so does your phone.
The 401 firmware you flashed is basically WWE (World Wide English), if it had messed up you'd probably be hard bricked.

Seanie280672 said:
just try it, its not going to hurt, just goto settings - mobile data - access point names - (3dot menu in the top right corner) select that and then select reset defaults.
Of course the baseband has changed, the newer firmware had a newer radio file in it, its not a radio file like your thinking though, its more of a software controller for a piece of hardw2are in your phone, just like every piece of hardware on your computer needs a driver, so does your phone.
The 401 firmware you flashed is basically WWE (World Wide English), if it had messed up you'd probably be hard bricked.
Click to expand...
Click to collapse
THanks, for explaining that to me
I just tried the same sim card in my galaxy s3 mini (unlocked) and it doesnt work in that phone at all (no calls or data). I think the sim may be defective, will get a new one and try again.
Thanks for your help
Edit: I did as you said in the m7 and even did a factory reset to make sure and results where the same. Looks like I got a bad sim card

@ Seanie280672: Thanks for your help bro
It just started working again after I installed ViperRom 7
Strange thing, just started working out of the blue but I am happy that is is resolved
fc3211 said:
THanks, for explaining that to me
I just tried the same sim card in my galaxy s3 mini (unlocked) and it doesnt work in that phone at all (no calls or data). I think the sim may be defective, will get a new one and try again.
Thanks for your help
Edit: I did as you said in the m7 and even did a factory reset to make sure and results where the same. Looks like I got a bad sim card
Click to expand...
Click to collapse

[Q] Stock HTC m7 wont boot up and both recovery and hard rest wont work

Hi Guys,
I have been reading around the forum but cant seem to find the answer to my problem. Or the suggestions are going over my head, so hope you can help.
I have a stock htc one m7 that is unrooted but it is sim unlocked. Went to bed with the phone working and then woke up with it stuck on the htc boot screen.
Things I have tried:
- get into HBOOT (which i can), then try recovery. This just reboots the phone to the white htc screen or screen just goes off.
- try and hard reset from hboot, but this does the same and either turns the screen black or reboots.
Both times i have left the phone for a while to see if it is up to anything but nothing happens.
I read about clearing the cache, but I could not get my head around the guides I read, so is there an idiots guide (I usually pretty good with tech stuff but not done much to do with phones etc)
Or any other suggestions. I use my phone for work so would be nice to get it working again without wiping it but most of the stuff should be back up anyway.
Thanks
Tom

From what I have tried I guess I should now try and flash the RRU?
The phone is on UKs EE network, as it is not rooted do I need to flash it with their branded rom or not? If so where can I get that from.
Thanks

Tommy_G5 said:
From what I have tried I guess I should now try and flash the RRU?
The phone is on UKs EE network, as it is not rooted do I need to flash it with their branded rom or not? If so where can I get that from.
Thanks
Click to expand...
Click to collapse
Do you have an sdk installed on your pc for adb/fastboot? If so can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting :good:

Danny201281 said:
Do you have an sdk installed on your pc for adb/fastboot? If so can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting :good:
Click to expand...
Click to collapse
Just downloading sdk now but I used another program i found on my travels. Is this all the info you need?
C:\toolkit>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: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(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
all: Done!
finished. total time: 0.052s
If you need other info ill post it when sdk is downloaded and installed
Thanks for your help!

Tommy_G5 said:
Just downloading sdk now but I used another program i found on my travels. Is this all the info you need?
C:\toolkit>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: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(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
all: Done!
finished. total time: 0.052s
If you need other info ill post it when sdk is downloaded and installed
Thanks for your help!
Click to expand...
Click to collapse
Yep that's what we wanted, unfortunately there's no ruu for your phone
If you've got warranty on the device I would send it in for repair.
If you don't have warranty you gonna need to unlock the bootloader to do anything with it. If your gonna do it go here www.htcdev.com register an account and go to the Unlock My Bootloader section of the site and follow the instructions to unlock :good:

Ok. I will do that.
So once the bootloader is unlocked, what is my solution? installing a different Ruu? Or installing a different Rom (or are they the same thing)
Thanks
Tom

Tommy_G5 said:
Ok. I will do that.
So once the bootloader is unlocked, what is my solution? installing a different Ruu? Or installing a different Rom (or are they the same thing)
Thanks
Tom
Click to expand...
Click to collapse
Once your Unlocked you can flash a Custom or Unbranded Stock Rom. To be able to use RUU's you will need to go s-off. As your on hboot 1.57 the only way to s-off is Sunshine app. But this costs $25 to use. So I would just go with flashing a Custom Recovery and ROM for the time being. :good:

Unlocking the bootloader void warranty. If you have none, then proceed. In my opinion, your phone has suffered hardware failure and will not be recoverable, hence warranty.

Thanks
Thanks for the help guys. Turns out its still under warranty which is good news. I know with other custom roms you can use adb to retrive info off the device.
Any chance I can do the same, as most of the stuff is backed up except some photos ( last couple of months worth).
If not Ill get over it but just in case.
Thanks for your help so far.
Tom

HTC One 801n Black Screen

Hi guys, i flashed Guru' Reset with CWM and after the phone turned on it only shows black screen with statusbar and after 1-2 mins it restarts again. I have (S-ON, Bootloader UNLOCKED)

arber95 said:
Hi guys, i flashed Guru' Reset with CWM and after the phone turned on it only shows black screen with statusbar and after 1-2 mins it restarts again. I have (S-ON, Bootloader UNLOCKED)
Click to expand...
Click to collapse
You have not provided much information.
Which GURU reset you used ? Which firmware you were on before flashing it ?
Also attach you phone to pc in fastboot mode, open command prompt and type in fastboot getvar all
Copy, paste the result over here. Make sure you remove IMEI and Serial No from it.
Also it's generally advised to use TWRP with HTC One.

Judging from my Bootloader mode info my OS Version was 2.24.401 so i flashed Guru_Reset_M7_2.24.401.1 with TWRP (i don't know which firmware it was on because it was bricked when i got it, it kept restarting)
Here is the info from cmd
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
I am a newbie to HTC, sorry ..

arber95 said:
Judging from my Bootloader mode info my OS Version was 2.24.401 so i flashed Guru_Reset_M7_2.24.401.1 with TWRP (i don't know which firmware it was on because it was bricked when i got it, it kept restarting)
Here is the info from cmd
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
I am a newbie to HTC, sorry ..
Click to expand...
Click to collapse
can you go into settings ?
GOOD news is that you can achieve S-OFF on this HBOOT version for free and very easily.
Just do as it is said in this thread.
http://forum.xda-developers.com/showthread.php?t=2487888
S-OFF has many advantages. And if you follow the guidelines and always read before doing anything, you won't get into any trouble.
Once you achieve S-OFF. you can install any firmware on your phone.

abdulwakil said:
can you go into settings ?
GOOD news is that you can achieve S-OFF on this HBOOT version for free and very easily.
Just do as it is said in this thread.
http://forum.xda-developers.com/showthread.php?t=2487888
S-OFF has many advantages. And if you follow the guidelines and always read before doing anything, you won't get into any trouble.
Once you achieve S-OFF. you can install any firmware on your phone.
Click to expand...
Click to collapse
You cant get s-off without a working rom on the phone, so thats got to be fixed first.
@arber95 reflash the guru reset file using TWRP 2.6.3.3 recovery, it should work then.
Hold down power button + volume down, the 2 lights on the bottom will flash approx 15 times, just keep holding, when the lights stop flashing, release to power button only, this will take you back to the bootloader.
Flash TWRP 2.6.3.3 recovery using fastboot commands http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
enter recovery, hopefully the guru reset file is still there on your internal storage, if not you'll have to push it to your internal storage using adb, then uplug your phone and flash it.

Seanie280672 said:
You cant get s-off without a working rom on the phone, so thats got to be fixed first.
@arber95 reflash the guru reset file using TWRP 2.6.3.3 recovery, it should work then.
Click to expand...
Click to collapse
I helped him RUU to stock.
He didn't want S-OFF. Just a working phone. He used ruu after incrementally flashing signed firmwares to 4.19.401.9..
Strangely his phone dialer was Fcing even after stock RUU 4.09.401.9
Last thing I know he catched 4.09.401.11 OTA and updated to it.
Don't know if the problem got solved.

As @abdulwakil noted. I'm back to Stock 4.4.2 with no root and relocked bootloader. Now my problems are: Dialer FC, i cant swipe notification center at all, and the phone restarts every exactly 4 minutes (which is strange), and it's not reading the simcard or getting signal (which it used to before)

@Seanie280672, help needed.

arber95 said:
As @abdulwakil noted. I'm back to Stock 4.4.2 with no root and relocked bootloader. Now my problems are: Dialer FC, i cant swipe notification center at all, and the phone restarts every exactly 4 minutes (which is strange), and it's not reading the simcard or getting signal (which it used to before)
Click to expand...
Click to collapse
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.

Seanie280672 said:
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Click to expand...
Click to collapse
This is my present getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(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!

Seanie280672 said:
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Click to expand...
Click to collapse
his phone was working on cm12, how come ?

arber95 said:
This is my present getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(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!
Click to expand...
Click to collapse
please remove your imei and serial from your post.
You could try flashing this, this is a full wipe firmware, it will wipe everything and re-build your partitions is the same firmware you have now: https://www.androidfilehost.com/?fid=23329332407579671
I would recommend after that to straight away, flash TWRP recovery and then push a custom KK sense rom to your internal storage and flash it, see if you have the same problem., if the problem still persists, you have a hardware issue.

Seanie280672 said:
please remove your imei and serial from your post.
You could try flashing this, this is a full wipe firmware, it will wipe everything and re-build your partitions is the same firmware you have now: https://www.androidfilehost.com/?fid=23329332407579671
I would recommend after that to straight away, flash TWRP recovery and then push a custom KK sense rom to your internal storage and flash it, see if you have the same problem., if the problem still persists, you have a hardware issue.
Click to expand...
Click to collapse
He is on 4.09.401.11 firmware. and S-ON

abdulwakil said:
his phone was working on cm12, how come ?
Click to expand...
Click to collapse
Someone else had the same problem recently, I was just trying to find the thread, i'll call for some expert advice, cant quite remember, CM12 / 11 does something slightly different
@clsA @nkk71 @Danny201281
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
abdulwakil said:
He is on 4.09.401.11 firmware. and S-ON
Click to expand...
Click to collapse
not according to his fastboot getvar all he's not. (bootloader) version-main: 4.19.401.9

Seanie280672 said:
not according to his fastboot getvar all he's not. (bootloader) version-main: 4.19.401.9
Click to expand...
Click to collapse
lol, he hasn't posted the present getvar all output. let him do that.

abdulwakil said:
lol, he hasn't posted the present getvar all output. let him do that.
Click to expand...
Click to collapse
well here is 401.11 full wipe https://www.androidfilehost.com/?fid=23329332407579952

I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(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.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

arber95 said:
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(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.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
And is it still playing up ?
This is all the wipe and non wipe firmware files, https://docs.google.com/spreadsheets/d/tvdrXmIGYk0OWi0jtqih_0g/htmlview?pli=1, obviously you can only go up as your s-on, im surprised though that you can update whilst having those problems and they're not being fixed by the updates, I would be tempted to update as far as 6.09.401.5 full wipe, then flash twrp 2.6.3.3 and flash trhis rom by clsA
https://www.androidfilehost.com/?fid=95916177934521009

arber95 said:
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(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.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Yeah definitely sounds like unknown imei and baseband although I would expect you to only see the HTC logo after unlocking the screen.
For some reason CM roms work even with this issue. I believe it's because there is no Sense overlay with CM But I'm not exactly sure why they work.
Can you go to Settings>About>Phone Identity. And check your IMEI number is it displayed as Unknown?
Also Settings>About>Software information>More. And check your baseband is it displayed as Unknown.?

Seanie280672 said:
And is it still playing up ?
This is all the wipe and non wipe firmware files, https://docs.google.com/spreadsheets/d/tvdrXmIGYk0OWi0jtqih_0g/htmlview?pli=1, obviously you can only go up as your s-on, im surprised though that you can update whilst having those problems and they're not being fixed by the updates, I would be tempted to update as far as 6.09.401.5 full wipe, then flash twrp 2.6.3.3 and flash trhis rom by clsA
https://www.androidfilehost.com/?fid=95916177934521009
Click to expand...
Click to collapse
Again Sim not recognised, dialer FC, notification center doesn't open, and now it restarts more often (every 2 mins or so)

[Q] no version main no os, no roms working HELP PLEASE

hi there hope someone has an idea as im all out, tried loads of how tos from here and so many roms but maybe im just stoopid. my original backupo was on a laptop that got stolen. i have no os s-on tampered unlocked i can flash recoveries and get into bootloader and recovery ,and flashing roms or backups seems to work and be "successful" but then either i get stuck in bootloop or get into setup ie wifi name etc and it keeps rebooting, its usually i get im sorry so and so has stopped working then it reboots. am i missing something simple ? any ideas please.
radio 4A-14-3250-13
open dsp v32-120-274-0909
hboot 1.55.0000
C:\adb>fastboot devices
FA3AHW902739 fastboot
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ()*&^&*(^£$%^%
(bootloader) imei: £$%"!"£$%^^%$££
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(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
all: Done!
finished. total time: 0.110s

tinkerer74 said:
hi there hope someone has an idea as im all out, tried loads of how tos from here and so many roms but maybe im just stoopid. my original backupo was on a laptop that got stolen. i have no os s-on tampered unlocked i can flash recoveries and get into bootloader and recovery ,and flashing roms or backups seems to work and be "successful" but then either i get stuck in bootloop or get into setup ie wifi name etc and it keeps rebooting, its usually i get im sorry so and so has stopped working then it reboots. am i missing something simple ? any ideas please.
radio 4A-14-3250-13
open dsp v32-120-274-0909
hboot 1.55.0000
C:\adb>fastboot devices
FA3AHW902739 fastboot
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ()*&^&*(^£$%^%
(bootloader) imei: £$%"!"£$%^^%$££
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(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
all: Done!
finished. total time: 0.110s
Click to expand...
Click to collapse
Please try and flash this rom: https://www.androidfilehost.com/?w=files&flid=13046
You need to use TWRP recovery 2.6.3.3 to flash it which you can get here: https://dl.twrp.me/m7/twrp-2.6.3.3-m7.img
If it works report back and i'll tell you what to do next.

thanks for the reply seanie im downloading that now, not a great connection so may take a while, i forgot to mention earlier that the baseband version on that was changerdf from 4A-21.3263.04 somehow although i cant remember how i did it dont know how much difference that makes. i only know that because i wrote it all down about a week ago . anyhow ill give those a whirl and get back to you in a bit mate.

ok seanie so the install went through without a hitch via adb sideload using specified recovery i saved the install log but it didnt seem to have any errors or problems, i got all exited when i saw the htc beats audio screen but now its just looping between that and the green htc logo screen. (just as a sidenote the only rom ive managedc to get past a bootloop is HTC-ONE-M7_GPE-5.1_LITE_CMERT_v1.1.zip but it freezes and rebbots at android is upgrading apps screen usually about 9 of 51) dont know if that helps at all with whats going on.

tinkerer74 said:
ok seanie so the install went through without a hitch via adb sideload using specified recovery i saved the install log but it didnt seem to have any errors or problems, i got all exited when i saw the htc beats audio screen but now its just looping between that and the green htc logo screen. (just as a sidenote the only rom ive managedc to get past a bootloop is HTC-ONE-M7_GPE-5.1_LITE_CMERT_v1.1.zip but it freezes and rebbots at android is upgrading apps screen usually about 9 of 51) dont know if that helps at all with whats going on.
Click to expand...
Click to collapse
trouble is, if you downloaded a recent rom, then chances are its a lollipop custom rom, and that's never going to work properly on your phone with your current firmware, its too old.
if that rom boots up ok and is usable, try and get s-off using rumrunner, the rest is easy from there: http://rumrunner.us/
I'm interested to know how you managed to change the baseband, that's basically the radio, have you been trying to flash firmware files ?, it could also be the reason your phone is rebooting all the time, theres not a lot of files about for orange branded phones for some reason.

nothing boots ok as for the radio i managed to get it bavck to original, just downloaded radio from a thread on here pushed to sdcard and installed its now back to original. ? should i not be able to do that?
C:\adb> fastboot getvar all
(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:
(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: 4320mV
(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
all: Done!
finished. total time: 0.118s

tinkerer74 said:
nothing boots ok as for the radio i managed to get it bavck to original, just downloaded radio from a thread on here pushed to sdcard and installed its now back to original. ? should i not be able to do that?
C:\adb> fastboot getvar all
(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:
(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: 4320mV
(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
all: Done!
finished. total time: 0.118s
Click to expand...
Click to collapse
1st any old custom rom like ARHD 36 flash it then
Do S OFF
Then you can whatever you want
If you don't want to do much and wanna simply working stock lollipop rom i can you you that also
But i will recommend S OFF

tinkerer74 said:
nothing boots ok as for the radio i managed to get it bavck to original, just downloaded radio from a thread on here pushed to sdcard and installed its now back to original. ? should i not be able to do that?
C:\adb> fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3AHW902739
(bootloader) imei: 359405051007886
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(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
all: Done!
finished. total time: 0.118s
Click to expand...
Click to collapse
Try this Stock Clockwork mod Nandroid http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-orang001-2-24-61-1-zip/
You will need to flash CWM Recovery to use it. Extract the zip then copy the folder to your Clockwork mod backup folder on the devices internal storage. Then restore the backup from the recovery menu.
If that runs stable, I also recommend you use rum runner to get s-off, as it will give you way more options. And rum runner is free to use. If your firmware is updated you'll have to use Sunshine which costs $25. Better to get it out the way now
Sent from my SM-T230 using Tapatalk

Danny201281 said:
Try this Stock Clockwork mod Nandroid http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-orang001-2-24-61-1-zip/
You will need to flash CWM Recovery to use it. Extract the zip then copy the folder to your Clockwork mod backup folder on the devices internal storage. Then restore the backup from the recovery menu.
If that runs stable, I also recommend you use rum runner to get s-off, as it will give you way more options. And rum runner is free to use. If your firmware is updated you'll have to use Sunshine which costs $25. Better to get it out the way now
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
i did try that nandroid which incidently is actually a twrp copy (if you open the folder its got boot.emmc.img which im pretty sure is twrp) anyhow i tried it with both recoveries and along with the only other available nandroid backup about 5 other custom roms that i thought i could use, and the only one i can get to work is cm-12.1-20150422-UNOFFICIAL-m7.zip with cw recovery and gapps i even managed to run rumrunner with it but keep getting to pouring 1 and WTF .then it finishes with no S-off. its doing my nut in now, either im being extremely stupid or theres something wrong with this m7.am i missing something obvious? im following the correct procedure its just very odd.

tinkerer74 said:
i did try that nandroid which incidently is actually a twrp copy (if you open the folder its got boot.emmc.img which im pretty sure is twrp) anyhow i tried it with both recoveries and along with the only other available nandroid backup about 5 other custom roms that i thought i could use, and the only one i can get to work is cm-12.1-20150422-UNOFFICIAL-m7.zip with cw recovery and gapps i even managed to run rumrunner with it but keep getting to pouring 1 and WTF .then it finishes with no S-off. its doing my nut in now, either im being extremely stupid or theres something wrong with this m7.am i missing something obvious? im following the correct procedure its just very odd.
Click to expand...
Click to collapse
Okay can you with cm 12 go to Settings>About>Phone Identity. Is the IMEI displayed correctly in there?
Also check Settings>About>Software Information>More. Is the baseband displayed correctly there?
Do you have mobile service with CM12?
Sent from my SM-T230 using Tapatalk

Danny201281 said:
Okay can you with cm 12 go to Settings>About>Phone Identity. Is the IMEI displayed correctly in there?
Also check Settings>About>Software Information>More. Is the baseband displayed correctly there?
Do you have mobile service with CM12?
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
yep both are correct as far as they match with what im getting from the getvar command? its also kernel version 3.4.105-ge01a861 oddly the build date is in french ? unfortunately im not sure about mobile service as i dont have an orange sim handy ill try and find one.Actually i just found an ee sim and searched for networks it found about 4 and registered me on the ee network i cant call though as no credit. id really like to try and get s-off on this if you can help.?
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: KO(*()*&&&&&&
(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: 3953mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
ok so mobile data and wifi working fine as well

tinkerer74 said:
yep both are correct as far as they match with what im getting from the getvar command? its also kernel version 3.4.105-ge01a861 oddly the build date is in french ? unfortunately im not sure about mobile service as i dont have an orange sim handy ill try and find one.Actually i just found an ee sim and searched for networks it found about 4 and registered me on the ee network i cant call though as no credit. id really like to try and get s-off on this if you can help.?
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: KO(*()*&&&&&&
(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: 3953mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
ok so mobile data and wifi working fine as well
Click to expand...
Click to collapse
This is a very strange problem, I can see though you flashed a developer edition firmware, its changed your HBOOT to 1.56 and now the only way to get s-off will be to use sunshine which will cost $25, also strange the flash worked as you are s-on.
both rumrunner and sunshine require as close to stock as possible rom to be installed on your phone to work, starting to look more and more like a hardware problem.