Alright so I got a deal on an AT&t m7 to replace my well worn old m7. I feel like I have done my part on searching I got several hours into this and I feel like im so close there is just something I am missing. This was my first time trying anything along these lines of modding a phone so be gentle please.
I am trying to install the tmobile rom nothing fancy I just want everything to work properly
First off I followed this guide EXACTLY took me a while but I finally did all the steps
http://forum.xda-developers.com/showthread.php?t=2601356
When I go to install the tmobile rom that I got from htc.com I get an ERROR 155 saying that its not the right file.... I have also tried installing the developers rom and got the same error.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4339mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
bmxguy08 said:
Alright so I got a deal on an AT&t m7 to replace my well worn old m7. I feel like I have done my part on searching I got several hours into this and I feel like im so close there is just something I am missing. This was my first time trying anything along these lines of modding a phone so be gentle please.
I am trying to install the tmobile rom nothing fancy I just want everything to work properly
First off I followed this guide EXACTLY took me a while but I finally did all the steps
http://forum.xda-developers.com/showthread.php?t=2601356
When I go to install the tmobile rom that I got from htc.com I get an ERROR 155 saying that its not the right file.... I have also tried installing the developers rom and got the same error.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4339mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Click to expand...
Click to collapse
change your mid to the Tmo mid using this, flash it in TWRP recovery https://www.androidfilehost.com/?fid=23622183712469376
change your cid to the Tmo Cid T-MOB010
find the corresponding firmware to the RUU you are trying to flash, we do recommend though as you are on an old 3xxxxxx firmware, you first find a 3xxxxxx firmware, then a 4xxxxxx then a 5xxxxxxx and finally a 6xxxxxxx, flash them all 1 at a time and now run the RUU, heres the 3 xxxxx and 4xxxxx ones to get you started: http://forum.xda-developers.com/showthread.php?t=2355814
Seanie280672 said:
change your mid to the Tmo mid using this, flash it in TWRP recovery https://www.androidfilehost.com/?fid=23622183712469376
change your cid to the Tmo Cid T-MOB010
find the corresponding firmware to the RUU you are trying to flash, we do recommend though as you are on an old 3xxxxxx firmware, you first find a 3xxxxxx firmware, then a 4xxxxxx then a 5xxxxxxx and finally a 6xxxxxxx, flash them all 1 at a time and now run the RUU, heres the 3 xxxxx and 4xxxxx ones to get you started: http://forum.xda-developers.com/showthread.php?t=2355814
Click to expand...
Click to collapse
Thank you! I did exactly as you said and installed all the firmware files one by one until I got to 6xxxxxxx then I was able to install the tmobile RUU with no problem!
Related
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(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.039s
Pls pls help.Thank You.
erinar88 said:
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(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.039s
Pls pls help.Thank You.
Click to expand...
Click to collapse
Couldn`t work as you are S-On. I think you`re stuck bro afaik. Maybe someone else knows a solution. Good luck.
That's odd. It shouldn't have run at all since you can't downgrade using a RUU without s-off. It should have prompted a RUU error noting that you were on a later version.
Is your phone rooted and unlocked yet? Did you do anything to it besides run the RUU?
Can't you just use fastboot to push a custom recovery and then sideload a custom or stock ROM?
AllAboutTheCore said:
Can't you just use fastboot to push a custom recovery and then sideload a custom or stock ROM?
Click to expand...
Click to collapse
Looks like his only option. Surprised that the RUU wiped his device before getting the error.
There's no way to downgrade hboot with s-on atm.
I'm gonna be 'that guy'... What the heck were you doing flashing an RUU on S-on with 'limited IT knowledge'...
There's a reason RUUs aren't released. It's to prevent this.
On a side note I would try another RUU download. Where are you getting the error at? What's the phone doing?
Sent from my HTC One using Tapatalk 4 Beta
I'm wondering now. Did you actually try to fastboot flash the 1.44 WWE firmware.zip in RUU mode despite being s-on? Because if you really did that, the phone is dead. You're getting a signature error because the phone is s-on and you managed to corrupt something important. Being s-on, I doubt there is any way to fix it.
An expensive lesson, but maybe you'll be more careful next time. Gaining s-off isn't worth bricking your phone.
This is confusing as the official RUU's (exe's and zips) will simply not allow you to downgrade the hboot or to flash an older version of the firmware without having s-off so my thoughts are exactly the same as iElvis.
I cannot see how you managed to do what you did.
So questions....
Are you running a custom recovery?
Is your bootloader locked or unlocked?
Have you tried holding vol down and power for about 15 to 30 seconds to see if you can get into the bootloader?
Did you do something like reboot into bootloader, fastboot oem rebootRUU and then fastboot flash zip firmware.zip?
TELL US the exact steps you went through so we can try to help you and worst case scenario you have bricked your phone.
I am having a similar problem only i have S-off but i cant find the right RUU or the right recovery.img to fastboot it .
If you have rumrunner_HTC_0.5.0.zip you could gain s-off very easy .
erinar88 said:
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(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.039s
Pls pls help.Thank You.
Click to expand...
Click to collapse
Sorry m8. Hate to break it to you but I accidentally did this too and I've found no solution for it. Ended up buying a new One...... I don't think there is a fix for this at all.
Sent from my HTC One using xda app-developers app
This began with a stock HTC one from Sprint
I updated all drivers and began with installing Cwm, rooting the device and then installing the latest Cyanogenmod
Everything was fine but then I wanted to make the device work with T-Mobile
So I embarked on doing so, proceeding I turned S-ON to S-OFF obtained super CID changed my MID to T-Mobile's MID relocked the bootloader installed T-Mobile's RUU and then everything went downhill.
After clearing the cache and rebooting the device it began to boot-loop and after that I tried using Cwm to install cyanogenmod through sideloading but adb did not recognize the device
After reading a few forums I thought the best course of action was to relock the bootloader and try installing T-Mobiles RUU once again
And... It failed, it began boot looping again and now im stuck with a cycling device.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA*******
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.095s
My intention is to get this Sprint HTC one to work T-Mobile on either stock ROM but preferably Cyanogenmod.
Thanks, First forum post ever.
I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(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: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
When I use ruus matching my config i get this error "Invalid sparse file format at header magi"
THC Butterz said:
I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(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: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
Click to expand...
Click to collapse
Remove your IMEI number and serial number from your first post.
Just use this to return to stock by @clsA put TWRP recovery on your phone, do a full wipe, push or sideload the zip file to your internal storage and then flash it.
http://www.htc1guru.com/dld/guru_reset_m7_5-12-502-2_clsa-zip/
You don't get rid of dirty, its normal, they all say that.
THC Butterz said:
I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT38WW902359
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
When I use ruus matching my config i get this error "Invalid sparse file format at header magi"
Click to expand...
Click to collapse
Which RUU do you want to flash. A link would be great :good:
I tried to flash every att ruu I could find, but I got it done, had to find a decrypted one, and extract it, then re insert and flash it piece by piece, radio, recovery, hboot, system... etc thanks for the replies, especially the imei/sn comment, forgot that was in the vars, made me check another post i made yesterday too :good:
THC Butterz said:
I tried to flash every att ruu I could find, but I got it done, had to find a decrypted one, and extract it, then re insert and flash it piece by piece, radio, recovery, hboot, system... etc thanks for the replies, especially the imei/sn comment, forgot that was in the vars, made me check another post i made yesterday too :good:
Click to expand...
Click to collapse
in all honesty, you should of just found the firmware matching the RUU you were trying to flash and flashed that first as you are s-off, you've pretty much done that just manually, glad you got it sorted though :good:
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
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.