yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
to be able to pull the partition, you either need to be rooted, or use the dd command in a custom recovery.

I'm looking at some of the differences, for example, some of the differences (other than the obvious first part of the block):

[U]offset 0x240[/U]
yours : 0x7B 1D 64 28 43 AD 89 41
mine : 0x00 00 00 00 00 00 00 00
cschmitt: 0x00 00 00 00 00 00 00 00
another : 0x00 00 00 00 00 00 00 00

[U]offset 0x304[/U]
yours : 0x00 00 00 00 00 00 00 00
mine : 0x91 00 00 00 2B 20 04 00
cschmitt: 0x00 00 00 00 AA EC DE AD
another : 0x8B 00 00 00 9A 02 1D 77

[U]offset 0x31C[/U]
yours : RINFO110RINFO110YmBXiSOGQ5zWL319M+nx1FECuitBq6T+
mine : RINFO110RINFO110OORGT6+Z3jigMbRtOh6XaxdcPP6q8+EV
cschmitt: RINFO010RINFO110OORGT6+Z3jigMbRtOh6Xa0eSR8EPMTaP
another : RINFO010RINFO110OORGT6+Z3jigMbRtOh6Xa2HBrqSAbvsG

[MENTION=4513061]cschmitt[/MENTION] what do you think?
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
I don't know anything about theese things, but I saw theese differences. That's why I asked if p19 is device specific. My good sir, you are the greatest. I'll be sure to make a small donation as soon as my pay pal account is sorted [emoji106]
[One (M7) Q&A, Help & Troubleshooting] nkk71:
and then you have at

offset 0x840

"recovery.--wipe_data." and later on the rest of the kernel, that part is easy to get rid of, so is fixing the first part of the block, my main concern is about the ones I mentioned before, and if they would interfere with anything in particular.

Hoping [MENTION=1477137]schmitt[/MENTION], will pass by and give us his valuable input, he's obviously more knowledgeable about these things, than I am.

Don't want you flashing just anything on a working phone, just to end up with a "lost" radio or something (though at least now we have your backup of p19, which you should be able to restore if things don't work out).

I'll start fixing the parts I believe need fixing in your partition (and leave the rest for later), but probably won't get back to you soon... going out with family and friends today :)
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
Thank you a million times!!! I can wait as long as it's needed, didn't even think of doing it right away [emoji4]

Have a good time [emoji486][emoji482]
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
Jackpot! - It appears that 0x800 - 0xC40 is the location of the bootloader command block

0x800 - 32 byte command

0x820 - 32 byte status

0x840 - 1024 byte recovery command (i.e. recovery --wipe_data)

I believe it's this area that's getting overwritten with garbage and causing the active cmdline overflow error by attempting to read values into the kernel command line that don't belong. Usually, these values are null terminated but if there's junk in that location the bootloader will continue reading data and overflow the 1024 byte limit on the kernel command line.

I have several copies of p19 for different times on my phone. I'll compare them and try to come up with some minimum set of what needs to be in there. For the most part, the partition can be zeroed out.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I have two p19 for PN0710000 and they are completely identical except for the values mentioned in post 30.

I can put that together when I'm back home, but any thoughts about the other offsets I mentioned? Which seem different for all MIDs.
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
I've compared 5 copies of p19 that I have pulled from my device over the last year.

0x240 - zeroed in all copies.

0x304 - zeroed in newer copies, but 2 copies from 1.26.502.10 firmware have 00 00 00 AA EC DE AD

ox31C - 3 older copies have: RINFO010RINFO110OORGT6+Z3jigMbRtOh6Xa0eSR8EPMTaP

2 latest versions have: RINFO010RINFO010 and then zeroed out from there.

I've attached the most recent p19 from my device so you can compare, you'll see it's pretty sparse. Mine is PN0712000 AT&T branded m7_ul, but I'm running the GPE 1.54 bootloader now which probably explains the differences from earlier versions.

In general, I think most of the partition is supposed to be empty except for the CID, OS Version, and a few other strings and bytes.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Well attached is the "repaired" (I hope) version; basically, I used my p19 partition

EDIT: details of my device

MID PN0710000

hboot 1.56

CID not there, but nothing to worry about

manufactured 23 April 2013

original CID ORANG001 (ie UK)

original software 1.28.61.7

serial number HT34PWxxxxxx

and only took back the following values from your semi-corrupted one:

[U]offset 0x240 (len 8)[/U]
yours : 0x7B 1D 64 28 43 AD 89 41

[U]offset 0x304 (len 8)[/U]
yours : 0x00 00 00 00 00 00 00 00

[U]offset 0x31C (len 0x30)[/U]
yours : RINFO110RINFO110YmBXiSOGQ5zWL319M+nx1FECuitBq6T+

Instruction to flash it: unrar it to you adb/fastboot folder then

C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx device

C:\ADB3>[B][COLOR="Blue"]adb push mmcblk0p19_donkeykong1_repaired.img /sdcard/[/COLOR][/B]
3641 KB/s (1047040 bytes in 0.280s)

C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
root@m7:/ # [B][COLOR="Blue"]su[/COLOR][/B] <- to ensure you get a [B]#[/B] prompt not a [B]$[/B] prompt
su

root@m7:/ # [B][COLOR="Blue"]dd if=/sdcard/mmcblk0p19_donkeykong1_repaired.img of=/dev/block/mmcblk0p19[/COLOR][/B]
dd if=/sdcard/mmcblk0p19_donkeykong1_repaired.img of=/dev/block/mmcblk0p19
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.293 secs (3573515 bytes/sec)

root@m7:/ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit

root@m7:/ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit

C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]

C:\ADB3>

obviously, I didnt try it the above is simulated.

and probably wait for cschmitt to confirm if the above sounds ok to him too

Good Luck

.
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
Thank you very much

I'll do it as soon as I get home. And thanks cschmitt for your time and knowledge
[One (M7) Q&A, Help & Troubleshooting] nkk71:
you're most likely right about 0x240, they seem all zeroed out in my copies as well,

no clue about the ones at 0x304 and 0x31C

but, by the way, the other p19 (PN0710000) was on 1.28.401.7 (after ruu) and also had no CID in p19... and at the time (if i remember correctly) hboot 1.56 wasn't out yet (though i'm not 100% sure).

Anyway, does the above sound good to you for [MENTION=4780713]donkeykong1[/MENTION] ?

Thanks for all your help!!
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
Yes, it looks good to me. thanks.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
By the way, do you remember which firmware (or other) you flashed that got you into this situation? would help in narrowing down the source of this problem.
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
Of course. 4.19.401.11 officiall HTC OTA. I was on 4.19.401.8 h-boot 1.56. After updating to .11 everything went south
[One (M7) Q&A, Help & Troubleshooting] nkk71:
:confused: really... do you still have the file on your PC? can you upload it somewhere (not a link, cause that would probably been have fixed, if there was an error in it)

though still sound's like a kernel flashing issue do to the beginning part of your corrupted p19 looking like a kernel, especially the beginning:

console=ttyHSL0,115200,n8 androidboot.hardware=[B][COLOR="Red"]dlx[/COLOR][/B] user_debug=31

Anyway, Good Luck!!

EDIT: but your p19 still shows 4.19.401.8!!

.
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
I think I have it, but I think I figured out what I did wrong. I had stock rooted ROM and Elemental kernel on my phone when I tried to update firmware. I totaly forgot I needed to flash stock kernel

It shows 4.19.401.8 because I managed to flash 1.54 dark hboot and 4.19.401.8 firmware. Everything else gave me active cmdline overflow
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
[MENTION=2605798]nkk71[/MENTION] here's an absolutely generic misc partition, should work on any device.

It's set with CID 11111111 and OS version 1.00.0000.0, most everything else is zeroed.

I flashed it on my device and it lived...
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
So, which one should I flash? This one or the one nkk71 posted?
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
Yes, because it has the correct OS version in it. Mine is more of a template that can be edited to match a certain CID and OS version.
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
I just flashed p19 that nkk71 posted for me and IT WORKED!!! You guys are amazing!!! I just flashed Elemental kernel without any problems. No more that cursed active cmdline overflow error. I really don't know how to thank you guys. As I said, when my pay pal account gets sorted out I will send both of you my sign of appreciation. Thanks again nkk71 and cschmitt!!!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Simply excellent news to hear!! :laugh:

As far as I know this is the first, and hopefully not the last

[SOLVED] HTC One M7 ACTIVE CMDLINE OVERFLOW

:good: :good:

Most (if not all ;)) credits to [MENTION=4513061]cschmitt[/MENTION] for nailing it down :highfive: :highfive:

.
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
Yeah, credits to cschmitt and you too!!! You guys rock!!!

One more simple question - I can restore my CID to my original one now? I mean, nothing bad should happen, right?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Let's hope the special recovery by [MENTION=4513061]cschmitt[/MENTION], will also allow the OP to get his phone up and running too :)

---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------

Yeah CID shouldn't be an issue at all.

fastboot oem writecid 11111111 <- whatever CID you want, but exactly 8 character

fastboot reboot-bootloader
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
Well, if you helped me with my problem, I'm 100% sure it will work for OP
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
[MENTION=2605798]nkk71[/MENTION] you get a ton of credit for all your contributions here. Glad we could solve this together. We should write up a thread to outline the problem, it's cause, and the solution.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yep, was a pleasure collaborating with you on this one :highfive:

And I agree we should write up a thread about this. I'm gonna have a look at some more p19 for different MIDs.

But also worth noting, is that since p19

may

only be partially corrupt, it would be better to first pull the corrupt one and attempt a repair, instead of flashing a generic p19...

i'm just wondering what the RINFO string is, and if that could affect radio or bands.

PN0710000 = RINFO110RINFO110

PN0712000 = RINFO010RINFO110

though obviously it's hard to judge based on only comparing 4 p19s

I'll get back to you ;)

[MENTION=5799831]davidliu8023[/MENTION] if you haven't flashed the p19, can first pull it... while in the custom recovery:

adb shell dd if=/dev/block/mmcblk0p19 of=/sdcard/mmcblk0p19_bak.img

adb pull /sdcard/mmcblk0p19_bak.img

and upload for us.
[One (M7) Q&A, Help & Troubleshooting] bored_stupid:
Do you need many p19s to compare. Will gladly upload mine if required. Great work by the way [MENTION=2605798]nkk71[/MENTION] [MENTION=4513061]cschmitt[/MENTION]
[One (M7) Q&A, Help & Troubleshooting] nkk71:
sure, the more the better, from the ones I have, preliminary analysis shows this as a normal p19:
[One (M7) Q&A, Help & Troubleshooting] bored_stupid:
Great. Will upload when I get home. Have used the hboot pre.update flash before, " couldn't flash recovery or an hboot via fastboot". Ran the RUU just once and hey presto.
[One (M7) Q&A, Help & Troubleshooting] bored_stupid:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.23.3263.28

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.12

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 3951mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

And link to P19

https://www.dropbox.com/s/qe4itvzfwefzgod/mmcblk0p19_bak.img
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Thanks mate, almost identical to mine (also PN0710000), except the two offsets i mentioned.

and you also have "recovery.--wipe_data"... did you pull the partition during a booted ROM, or in custom recovery?

PS: 1st draft almost up :D
[One (M7) Q&A, Help & Troubleshooting] bored_stupid:
Took it from adb shell, booted rom

I'll take one from recovery when I get home and compare.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
hmm, mine never has it (at least on I think), but initial draft is up :D

posted in the general section now, as that's where it's supposed to be: http://xdaforums.com/showthread.php?t=2739126

Thanks for the help!
[One (M7) Q&A, Help & Troubleshooting] bored_stupid:
[MENTION=2605798]nkk71[/MENTION]

Thought I would post this here to keep the other thread clean

From booted os

https://www.dropbox.com/s/ns4q44mp195filg/mmcblk0p19_bak.img

From recovery

https://www.dropbox.com/s/qe4itvzfwefzgod/mmcblk0p19_bak.img
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Thanks mate, they're identical :)
[One (M7) Q&A, Help & Troubleshooting] sihom:
@nkk71

I have the same problem, can anyone help me?

HTC ONE (Sprint)

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.65.0000

(bootloader) version-basenband: 1.00.20.1108

(bootloader) version-cpld: None

(bootloader) version-main: 4.06.651.4

(bootloader) version-misc: PUT SHIP S-OFF

(bootloader) serialno: FA364S900240

(bootloader) (bootloader) product: m7_wls

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0720000

(bootloader) cidnum: SPCS_001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4057mU

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-4dab9b12

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

When try to flash TWRP show the next message

Sending 'recovery' (11278 KB)...

OKAY [1.449s]

writing 'recovery' ...

FAILED (remote:not allowed)

finished. total time: 1.485s

**I guess I should open the bootloader, is it correct?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
you really picked a lousy time, as i'm "trying to sleep" :)

anyway, p19 seems to be the misc partition on both m7_u/ul and wls

BUT you will have to ask [MENTION=4513061]cschmitt[/MENTION] if his modded recovery could work on an Sprint device.

the thread is here: http://xdaforums.com/showthread.php?t=2739126

please ask there, if cschmitt's recovery can be use used to backup and restore a Sprint version!!

.... hmmm, so we sort of got something working for m7_u/ul... and.... we get a sprint version :rolleyes: poetic irony !!

PS: have you tried a SPRINT ruu?

PPS: do not attempt anything further unless one of is online... good night.
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
[MENTION=3787505]sihom[/MENTION], yes you will need to unlock the bootloader to flash a recovery. No, the modded recovery will not work with Sprint version. I may be able to build a m7wls version of the recovery, will need some time to figure that out.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yes definitely you'll need an unlocked bootloader.

But just a couple of question: are you able to boot into recovery, or a ROM? or are you always bootlooping back to bootloader?
[One (M7) Q&A, Help & Troubleshooting] panozzz:
good morning to all,

about corrupted partitions, I have a htc m7 with the imsi sim lock pin, it seems that depend on a bad recovery with riff box ...

wonder if restoring one of the 35 partitions of 'EMMC with a corrupt one can not solve the problem.

Code:

major minor #blocks name

179 0 30535680 mmcblk0

179 1 128 mmcblk0p1 sbl1

179 2 256 mmcblk0p2 sbl2

179 3 130671 mmcblk0p3 pg1fs

179 4 1 mmcblk0p4 ?

179 5 16 mmcblk0p5 board_info

179 6 256 mmcblk0p6 mfg

179 7 15577 mmcblk0p7 pg2fs

179 8 256 mmcblk0p8 sbl2_update

179 9 1024 mmcblk0p9 sbl3

179 10 256 mmcblk0p10 rpm

179 11 2048 mmcblk0p11 tz

179 12 2080 mmcblk0p12 hboot

179 13 5120 mmcblk0p13 sp1

179 14 1024 mmcblk0p14 wifi

179 15 1024 mmcblk0p15 dsps

179 16 61441 mmcblk0p16 adsp

179 17 8190 mmcblk0p17 radio_config

179 18 32768 mmcblk0p18 reserve_1

179 19 1022 mmcblk0p19 misc

179 20 4096 mmcblk0p20 modem_st1

179 21 4096 mmcblk0p21 modem_st2

179 22 20480 mmcblk0p22 devlog

179 23 4 mmcblk0p23 debug_config

179 24 256 mmcblk0p24 pdata

179 25 16 mmcblk0p25 control

179 26 1280 mmcblk0p26 local

179 27 64 mmcblk0p27 extra

179 28 1024 mmcblk0p28 cdma_record

179 29 98727 mmcblk0p29 reserve

179 30 54270 mmcblk0p30 reserve_2

179 31 76800 mmcblk0p31 radio

179 32 98303 mmcblk0p32 ?

179 33 16384 mmcblk0p33 boot

179 34 16383 mmcblk0p34 recovery

179 35 1900543 mmcblk0p35 system

179 36 655359 mmcblk0p36 cache

179 37 27262976 mmcblk0p37 userdata

thanks in advance for answers.

---------- Post added at 10:09 AM ---------- Previous post was at 10:05 AM ----------

I beg your pardon, 37 partitions,

other application partitions called "reserv" are perhaps backups in case of loss of any item?
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
HELP ME

I HAVE THE SAME ERROR AND I CAN GET PAST BOOTLOADER, I CANT ACCESS RECOVER BOTH CUSTOM RECOVERY AND STOCK AND KEEP GETTING DOVERTED TO THE SAME WEBSITE PLEASE HELP ME QUICK.

MY GETVAR INFO

C:\fastboot>fastboot getvar all

< waiting for device >

(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:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0714000

(bootloader) cidnum: OPTUS001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3768mV

(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.062s

C:\fastboot>
[One (M7) Q&A, Help & Troubleshooting] clsA:
Edit your post to remove you IMEI and Serial No then look here >> http://xdaforums.com/showthread.php?t=2739126
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
i cant i tried that but it cant work since i cant access recovery to turn on adb and adb cmd doesnt recognize my device

any other thoughts?
[One (M7) Q&A, Help & Troubleshooting] clsA:
Well you didn't even try because it has nothing to do with adb you flash it in fastboot

If your having problems with your PC's Drivers look here >> http://xdaforums.com/showthread.php?t=2541082

Post 2 - FAQ 2
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
i just tried it again and got this error

FAILED (remote: signature verify fail)
[One (M7) Q&A, Help & Troubleshooting] clsA:
unlock your bootloader ?
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
its unlocked
[One (M7) Q&A, Help & Troubleshooting] clsA:
so you can't flash a recovery ?
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
no i have tried every option even using the ruu.exe files to install new rom but theres always an error that says too many links and i cant access the recovery to flash the stock rom nor can i do it from fastboot because of the signature verification
[One (M7) Q&A, Help & Troubleshooting] clsA:
Well the signature verification is normal on a locked bootloader

lock it and unlock it again .. do you still have the unlock_code.bin
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
yes and i will try it now

i tried it and flashing the recovery but still cant access recovery mode
[One (M7) Q&A, Help & Troubleshooting] clsA:
are you still getting the security error ?

and if you can post the command window on what your doing so i can get an idea of whats happening
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
actually i resolved the issue by entering this code and the official new stock rom has been installed

fastboot oem enableqxdm 0
[One (M7) Q&A, Help & Troubleshooting] clsA:
Great !! where did you find that info ?
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
on here

http://www.askabouthugo.com/general...n-fastboot-with-remote-signature-verify-fail/
[One (M7) Q&A, Help & Troubleshooting] dihcar:
Hi, i want to flash a stock ROM through fastboot , but i always get the signature verify fail error, can you plz put a step by step guide, when you flashed the ROM was your bootloader locked or unlocked , and at what step did you issue the command

Fastboot oem enableqxdm 0

Please help I'm really stuck!
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
my bootloader was unlocked. and here

first install cmw recovery by download the recovery from here https://www.clockworkmod.com/rommanager

1. unlock bootloader

2. clear cache <fastboot erase cache>

3. enter command <Fastboot oem enableqxdm 0>

4. hold power button until phone turns off (im assuming u dont have an os currently installed)

5. boot into recovery

6a. first enable adb sideload by going into install from zip and then scroll down and select adb sideload

6b. use adb to install the rom onto the device with this code <adb sideload rom.zip> to whatever ur file name is or change ur file name to mine. if it says signature fail then click on toggle signature verification to turn it off.

7. after its finished click install from zip and select the rom.zip file using power button and volume buttons to move up and down and then wait for the rom to be installed and that is it, i also recommend that u make sure the rom is ment for your device and is the correct one as this could brick your phone even worse and then u wont be able to recover it back.

google gapps: http://androidxda.net/update-galaxy-s3-to-cyanogenmod-based-android-5-0-2-lollipop-custom-rom/

cm12: http://xdaforums.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826
[One (M7) Q&A, Help & Troubleshooting] dihcar:
thanks :good:

i followed the steps but couldn't push zip to sd card through adb.

probably corrupt file, i got to to look for a cleaner one.

my problem is different, i have os but but unknown baseband and imei, it's not stable and reboots every 2 min, despite i installed it many times using RUU.exe.

i couldn't find any solution, so i'm experimenting, by trying to flash a stock firmware zip through fastboot or recovery or anythind hoping to fix this problem.

any idea is welcomed!
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
what os are u currently running

because it might be the one doing the reboots and do u want to return to stock badly or do u just want a phone u can use that doesn't keep shutting down on you.
[One (M7) Q&A, Help & Troubleshooting] dihcar:
After following the steps you described above the phone got bricked, luckily it was a soft brick, I was able to run the ruu.exe. and flash the firmware anew.

This is the latest kitkat 4.4.3 for T-Mobile.

Os 6.10,531.10

I just want a working phone!
[One (M7) Q&A, Help & Troubleshooting] Caesar966:
can u please take screenshots of ur android in bootloader and upload it

and have u tried installing cm12