So when i entered the fastboot getvar all command in adb
Heres what i got
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 134217728
(bootloader) partition-size:userdata: 17329be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-size:LOGO: 380000
(bootloader) partition-type:LOGO: unknown
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: unknown
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-size:EXPDB: 1160000
(bootloader) partition-type:EXPDB: unknown
(bootloader) partition-sizeKB: 100000
(bootloader) partition-typeKB: unknown
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) off-mode-charge: 1
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: FORD
(bootloader) version: 0.5
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0xaXXXXXXXXXXX
(bootloader) prod: 1
all: Done!!
finished. total time: 0.180s
Im wondering if the unlock code can be used to unlock it or its just the binary data on true or false.
@sd_shadow Your thoughts on this?
This maybe useful or maybe not.
Link for the kindle hdx 8.9
[DEV] Bootloader unlock procedure and software by @dpeddi
Ugh wish i had another kindle fire
sd_shadow said:
This maybe useful or maybe not.
Link for the kindle hdx 8.9
[DEV] Bootloader unlock procedure and software by @dpeddi
Click to expand...
Click to collapse
Apparently I just tried this with the one Getvar gave me it didnt work. gave me an unlock code error
I bought this fire for my son. The hdx unlock worked until 3.2.4 firmware and is based on a bug on image verification. Probably we can't unlock any more the bootloader..both on newer HDx and on this cheap fire.
@sd_shadow So what's the status on the bootloader unlock? Anything us common users can do to help?
Would making a petition online to Amazon help our cause? Or maybe get @geohot involved if possible?
rjmxtech said:
@sd_shadow So what's the status on the bootloader unlock? Anything us common users can do to help?
Would making a petition online to Amazon help our cause? Or maybe get @geohot involved if possible?
Click to expand...
Click to collapse
Dude can you layoff for a bit? You're saying the same things in every thread. The bootloader isn't unlocked, most likely won't be. Amazon won't break for a petition, and geohot works for google. Be patient, the constant hounding doesn't make it work faster...
ldeveraux said:
Dude can you layoff for a bit? You're saying the same things in every thread. The bootloader isn't unlocked, most likely won't be. Amazon won't break for a petition, and geohot works for google. Be patient, the constant hounding doesn't make it work faster...
Click to expand...
Click to collapse
Um, this is one of the only threads I have posted this in. Calm yourself. I am just trying to see what I can do. Trying to do things is better than sitting and doing nothing and waiting for others to do them for you.
rjmxtech said:
Um, this is one of the only threads I have posted this in. Calm yourself. I am just trying to see what I can do. Trying to do things is better than sitting and doing nothing and waiting for others to do them for you.
Click to expand...
Click to collapse
look, I get it, you really want the bl unlocked. You posted in 3 threads about it, one had to be cleaned. But unless you know anything about the process, there's nothing to help with. I'm not discouraging, it's just the way it is. Let those in the know alone, leave them to their work. Trust me, you won't miss anything if it happens
ldeveraux said:
look, I get it, you really want the bl unlocked. You posted in 3 threads about it, one had to be cleaned. But unless you know anything about the process, there's nothing to help with. I'm not discouraging, it's just the way it is. Let those in the know alone, leave them to their work. Trust me, you won't miss anything if it happens
Click to expand...
Click to collapse
That one I posted in the wrong place I changed to "nvm" when I realized I posted in the wrong place but I get what you're saying.
well i bricked my fire today trying to install cm12:crying: seems the recovery img was corrupted some how so ill need the bl to be unlocked to flash a custom one. i have reached the limits of my knowledge, as limited as it may be. rooting for those of you that know what you are doing. thank you for the effort, even if it doesnt result in a fix.
jwalb89 said:
well i bricked my fire today trying to install cm12:crying: seems the recovery img was corrupted some how so ill need the bl to be unlocked to flash a custom one. i have reached the limits of my knowledge, as limited as it may be. rooting for those of you that know what you are doing. thank you for the effort, even if it doesnt result in a fix.
Click to expand...
Click to collapse
What are the symptoms of your brick? Can you get to fastboot?
Drax TD said:
What are the symptoms of your brick? Can you get to fastboot?
Click to expand...
Click to collapse
I do have access to fastboot, but not to recovery as stated so no adb commands for me... on normal boot it goes to the cm12 boot logo, and continues attempting to boot.
Shouldn't he be able to recover if he gets boot image and fastboot?
Sent from my KFFOWI using Tapatalk
Franzferdinan51 said:
Shouldn't he be able to recover if he gets boot image and fastboot?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fastboot mode doesn't work with 5.1.1 bootloader
Sent from my XT1060 using Tapatalk
sd_shadow said:
fastboot mode doesn't work with 5.1.1 bootloader
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Are you sure because I'm pretty sure I used fastboot to restore my tablet when it bricked though I could be wrong may have been adb side load
Sent from my KFFOWI using Tapatalk
Franzferdinan51 said:
Are you sure because I'm pretty sure I used fastboot to restore my tablet when it bricked though I could be wrong may have been adb side load
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
jwalb89 said:
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
Click to expand...
Click to collapse
Ahh well good luck can't wait too see what you come up with would love to have a real recovery instead of flash fire
Sent from my KFFOWI using Tapatalk
jwalb89 said:
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
Click to expand...
Click to collapse
Any luck getting a update.zip that can restore stock using fastboot?
Thanks
Related
*** SOLVED - Problem was my own stupidity ***
Got the HTC One a couple of days ago. Came back to Android after a few months on iPhone. Figured I'd jump right back into rooting and flashing custom ROMs.
Anyway, unlocked the phone, wanted to install Android Revolution 51, tried to upgrade firmware, and that's when things went sideways. Now, I can't do anything. Can Fastboot, but can't ADB. Have tried to load every driver in the book, but to no avail. CID is CWS_001 if that helps. Have been at this for a day and a half now. I need ideas.
thoughts?
Does it get detected on your window device manager when you plug it in?
sent from my mobile device
SaHiLzZ said:
Does it get detected on your window device manager when you plug it in?
sent from my mobile device
Click to expand...
Click to collapse
Yes. It shows up under Android USB Devices and says "My HTC"
diceman725 said:
Yes. It shows up under Android USB Devices and says "My HTC"
Click to expand...
Click to collapse
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...
Iz3man said:
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...
Click to expand...
Click to collapse
Would be very grateful. I agree, it would seem logical that I could ADB my way out, but at the moment, ADB doesn't recognize the device.
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I don't have a ROM loaded in the Virtual SD. And unless I'm mistaken, I can really only use ADB sideload at this point to load one up
Can you get into basic HTC recovery on the phone? I'm assuming you can if you can get fastboot working.
If so can't you just reflash a actual recovery from there, and then a rom from that? Apologies if this is completely irrelevant, I base all my android knowledge off my Desire.
Sent from my HTC Desire using Tapatalk 2
Adb reboot
sent from my mobile device
Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.
Iz3man said:
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.
Click to expand...
Click to collapse
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.
diceman725 said:
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.
Click to expand...
Click to collapse
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!
Iz3man said:
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!
Click to expand...
Click to collapse
I can get into recovery, yes...
If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device
SaHiLzZ said:
If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device
Click to expand...
Click to collapse
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.
diceman725 said:
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.
Click to expand...
Click to collapse
No luck on flashing the RUU file. It sends successfully, but fails on the write.
You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device
also nearly bricked
..
Please make a new thread.
sent from my mobile device
SaHiLzZ said:
You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device
Click to expand...
Click to collapse
(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) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(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
hi @ all,
im semi-familiar with rooting and flashing on several phones and tablets , learning by doing for one year or so ...
... but in this case i think my phone is at the end of trial and error so i hope to find some one who realy knows what to do
look
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3654mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
this HTC one 801n (m7ul) was htcdev unlocked s-off by rumrunner,tempered removed , latest darkboot firmware from htc1guru , normaly runing renovate with elementalx but even every other rom-kernel combination i used worked quite well so as backup and restore
in TWRP i made a fullwhipe and flashed CM11 M3 and boot to system , made some settings it seemed to be ok , i boot to recovery ,whipe and flash elementalx kernel , while flashing the screen went black and i find my phone in this condition :
no light at all , no reaction at all , -i am on win 7- in system there is a "myHTC" device and fastboot seemed to work but every try to flash :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip 4.19.401.8_firmware_darkboot.zip
target reported max download size of 452980736 bytes
sending 'zip' (24782 KB)...
OKAY [ 1.105s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.109s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: -1
OKAY [ 0.044s]
finished. total time: 0.045s
after this the phone does not answer any more :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip 4.19.401.8_firmware_darkboot.zip
< waiting for device >
is there some one to take my hand and lead me out off this darkness, please
muezae said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 35xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
Click to expand...
Click to collapse
not again :crying:
Is that really the output of your getvar? in particular the ones in bold-red?
nkk71 said:
not again :crying:
Is that really the output of your getvar? in particular the ones in bold-red?
Click to expand...
Click to collapse
Well if that really is the output of the getvar.. it don't look good
Wish the noobs would read and then re-read all the guides, befor messing with their phones
nkk71 said:
not again :crying:
Is that really the output of your getvar? in particular the ones in bold-red?
Click to expand...
Click to collapse
yes it is ,
i can fastboot oem writecid and imei but at next reconect settings are gone agin , also serialnumber is not correct
muezae said:
yes it is ,
i can fastboot oem writecid and imei but at next reconect settings are gone agin , also serialnumber is not correct
Click to expand...
Click to collapse
So do you want to explain how the phone got in this condition or should we just guess ?
flashed CM11 M3 and boot to system , made some settings it seemed to be ok , i boot to recovery ,wipe and flash elementalx kernel , while flashing the screen went black and i find my phone in this condition :
Click to expand...
Click to collapse
Seems you were intentionally trying to brick the phone
Does everyone mix and match OS and Kernels like this ?
From the ElementalX thread
Kernel for Google Play Edition and Sense-based ROMs
Click to expand...
Click to collapse
where does it say CM 11 ?
muezae said:
yes it is ,
i can fastboot oem writecid and imei but at next reconect settings are gone agin , also serialnumber is not correct
Click to expand...
Click to collapse
Sorry mate, I think it's best to send it to repair, your mfg partition is corrupt, and there's no redundancy for that, and it contains a lot more info than just your serial number and modelid.
Just out of curiosity, do you also have Active Commandline overflow, in the bootloader screen? and can you share the links and version numbers of:
"in TWRP i made a fullwhipe and flashed CM11 M3 and boot to system , made some settings it seemed to be ok , i boot to recovery ,whipe and flash elementalx kernel , while flashing the screen went black and i find my phone in this condition"
bored_stupid said:
Well if that really is the output of the getvar.. it don't look good
Wish the noobs would read and then re-read all the guides, befor messing with their phones
Click to expand...
Click to collapse
thanks for relay but what do you think did i noob not read and reread ? this was happen to me during normal flash with correct kernel , i like to know my mistake but i dont see , do you ?
muezae said:
thanks for relay but what do you think did i noob not read and reread ? this was happen to me during normal flash with correct kernel , i like to know my mistake but i dont see , do you ?
Click to expand...
Click to collapse
This "im semi-familiar with rooting and flashing on several phones and tablets , learning by doing for one year or so ..." means you're not a noob.
And you're not the first in this situation, but I'd appreciate it if you could answer my previous question, about links and versions.
Thanks
nkk71 said:
Sorry mate, I think it's best to send it to repair, your mfg partition is corrupt, and there's no redundancy for that, and it contains a lot more info than just your serial number and modelid.
Just out of curiosity, do you also have Active Commandline overflow, in the bootloader screen? and can you share the links and version numbers of:
"in TWRP i made a fullwhipe and flashed CM11 M3 and boot to system , made some settings it seemed to be ok , i boot to recovery ,whipe and flash elementalx kernel , while flashing the screen went black and i find my phone in this condition"
Click to expand...
Click to collapse
thak you
CM11 M3 : http://download.cyanogenmod.org/?type=snapshot&device=m7
TWPR is 2.6.2.4 at the moment i dont know from where i got it
elementalx : http://forum.xda-developers.com/showthread.php?t=2249774 ; now i see this is not what i whant to flash ,
Just out of curiosity, do you also have Active Commandline overflow, in the bootloader screen? SORRY ???
muezae said:
thak you
CM11 M3 : http://download.cyanogenmod.org/?type=snapshot&device=m7
TWPR is 2.6.2.4 at the moment i dont know from where i got it
elementalx : http://forum.xda-developers.com/showthread.php?t=2249774 ; now i see this is not what i whant to flash ,
Just out of curiosity, do you also have Active Commandline overflow, in the bootloader screen? SORRY ???
Click to expand...
Click to collapse
1- you mean TWRP 2.6.3.4 right?
2- which version of elementalX, do you remember?
3- look at first screenshot here: http://forum.xda-developers.com/showpost.php?p=50678849&postcount=23 do you have "Active cmdline overflow" too?
This is not helping you, I'm sorry for that.
I'm just trying to trace how/why/what could have corrupted your mmcblk0p6 [mfg] partition (the one in the screenshot is s-on, so it didn't get corrupted, but no solution yet either even with S-On)
On the other hand, the guy in this thread is in exactly the same situation as you, and here you can see what the mfg partition is about: http://forum.xda-developers.com/showpost.php?p=50712531&postcount=37
clsA said:
So do you want to explain how the phone got in this condition or should we just guess ?
Seems you were intentionally trying to brick the phone
Does everyone mix and match OS and Kernels like this ?
From the ElementalX thread
where does it say CM 11 ?
Click to expand...
Click to collapse
yes thank you , i dont know why i guess it is for CM11 ...
muezae said:
yes thank you , i dont know why i guess it is for CM11 ...
Click to expand...
Click to collapse
Sorry but you made many mistakes in a row and now it's not recoverable(that I can tell)
nkk71 said:
1- you mean TWRP 2.6.3.4 right?
2- which version of elementalX, do you remember?
3- look at first screenshot here: http://forum.xda-developers.com/showpost.php?p=50678849&postcount=23 do you have "Active cmdline overflow" too?
This is not helping you, I'm sorry for that.
I'm just trying to trace how/why/what could have corrupted your mmcblk0p6 [mfg] partition (the one in the screenshot is s-on, so it didn't get corrupted, but no solution yet either even with S-On)
On the other hand, the guy in this thread is in exactly the same situation as you, and here you can see what the mfg partition is about: http://forum.xda-developers.com/showpost.php?p=50712531&postcount=37
Click to expand...
Click to collapse
yes TWRP 2.6.3.4 , ElementalX-m7-13.0 , i got a black screen so dont know cmdline overflow
clsA said:
Sorry but you made many mistakes in a row and now it's not recoverable(that I can tell)
Click to expand...
Click to collapse
yes
but all my backup and copy will not help ?
muezae said:
yes
but all my backup and copy will not help ?
Click to expand...
Click to collapse
no .. the wrong kernel totally scrambled the partition ...no idea why
that's all i can make of it
muezae said:
yes
but all my backup and copy will not help ?
Click to expand...
Click to collapse
No they will not help you at all.
As nnk71 said " you have corrupted your mmcblk0p6 [mfg] partition. Has of yet, there is no way of restoring your phone to a usable condition.
clsA said:
no .. the wrong kernel totally scrambled the partition ...no idea why
that's all i can make of it
Click to expand...
Click to collapse
ok so just delete and reststore partition from backup?
muezae said:
ok so just delete and reststore partition from backup?
Click to expand...
Click to collapse
you don't seem to be getting it ...your phone is Dead
take it to a service center and tell them you got up this morning and it was like that ...play dumb and don't admit to doing anything
bored_stupid said:
No they will not help you at all.
As nnk71 said " you have corrupted your mmcblk0p6 [mfg] partition. Has of yet, there is no way of restoring your phone to a usable condition.
Click to expand...
Click to collapse
even when i got the original file named mmcblk0p6 ?
muezae said:
even when i got the original file named mmcblk0p6 ?
Click to expand...
Click to collapse
try restoring it and see .. you have nothing to loose
Yesterday, I attempted to install a new rom. I had been using CM11 nightlies up till this point, and after being annoyed about certain aspects of my phone not working. I wanted to try something new.
I found ViperOne, and went to install it, thinking that it'll be the standard, run-of-the-mill install with no problems to be had. After getting through the install procedure and attempting to reboot to system, my phone dropped me back off at the bootloader. Thinking that I had forgotten to wipe something, I went into the recovery, wiped data, dalvik cache, and the cache, and attempted the install again. Once again, my phone dropped me off at the bootloader.
I thought, maybe I had a bad download. Re-downloaded the rom, same result. "Oh, I'll just try something else then". I found a Google Play Edition rom for my device, and decided to try that. It got stuck in a bootloop. After some googling, I attempted wiping the data/cache/dalvik cache again hoping it would help. Nope, still stuck in bootloop.
At this point (and after having running into a very similiar situation before) I decided to go for broke. I did a full wipe of the phone, and sideloaded CM10.1.3 (only stable CM rom for this device afaik). As it was installing, I noticed an error. "Unable to mount /data". I've had this problem before, and the way I fixed it last time was to install and run a stock rom. At this point in time, I was also getting frustrated and decided to put the stock rom back on my phone so it would at least be functional.
I found a stock rom and installed it just fine. The phone didn't even get stuck in a bootloop either. However, once the phone had finally booted up, I found that the touchscreen was unresponsive. I remember having this issue the last time I tried to use a stock rom. After a little bit of research, I had found that the problem stems from installing the wrong version of the rom. It was suggested on one of the websites to put "fastboot getvar version-main" into adb to find out what version I needed. It returns "version-main: ".
It was at this point that I remembered that I had made a backup of my phone before I attempted rooting. After some searching around, I managed to find it. That being said, I have no idea what to do with it. The folder where I made the backup contains a handful of .win files and some md5 checksums.
Since then I have been attempting seemingly random RUU versions in hopes of stumbling across the right one. It's been 5 hours, and I haven't had any success.
I would greatly appreciate any and all help that can be provided. If you guys need additional information (I'm not sure what I should include), let me know. I know some of the more basic ADB commands and their functions, so bear with me if I ask some questions about how to do certain things.
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
BD619 said:
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
BTW I removed
serialno:
imei:
meid:
BD619 said:
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
Click to expand...
Click to collapse
I've tried several different RUU's, including the one's I could find here, and none of them have worked. Not sure if it really matters, but I attempted the 4.06.651.4 RUU earlier, but it failed.
BD619 said:
BTW I removed
serialno:
imei:
meid:
Click to expand...
Click to collapse
Why shouldn't those be shared? Are they considered sensitive information?
Ooops for got the link
http://forum.xda-developers.com/showthread.php?t=2503646
Yes they could be considered sensitive.
BD619 said:
Yes they could be considered sensitive.
Click to expand...
Click to collapse
I have no idea what those numbers represent. Why are important?
crazy-asian said:
I have no idea what those numbers represent. Why are important?
Click to expand...
Click to collapse
I have always been told not to include those...could be a way for someone to hack your device but that's just my guess.
http://en.wikipedia.org/wiki/Mobile_equipment_identifier
I had this happen to me also. Ends up i had to flash a new firmware on the phone and it booted right up. Also make sure you are using twrp recovery when you flash this rom. I used cwm and think that is where all my problems started. Hope ya get it worked out and may not be your problem but is exactly what happened to me and have i fixed it.
BD619 said:
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
I had tried all but one of those in that list. That one that I hadn't used yet appears to be working. Thank you so much for the help.
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
crazy-asian said:
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
Click to expand...
Click to collapse
I'm running BadSeed Sixth Sense
But it's all personal preference everyone will have a different opinion.
Fastboot, on the phone side, isn't connecting to my computer.
crazy-asian said:
Fastboot, on the phone side, isn't connecting to my computer.
Click to expand...
Click to collapse
Are you in bootloader?
BD619 said:
Are you in bootloader?
Click to expand...
Click to collapse
Yes, and it is in fastboot mode.
crazy-asian said:
Yes, and it is in fastboot mode.
Click to expand...
Click to collapse
When you type fastoot devices you don't get a response?
BD619 said:
When you type fastoot devices you don't get a response?
Click to expand...
Click to collapse
correct
crazy-asian said:
correct
Click to expand...
Click to collapse
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
BD619 said:
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
Click to expand...
Click to collapse
Didn't solve the problem, phone still isn't in "fastboot USB"
crazy-asian said:
Didn't solve the problem
Click to expand...
Click to collapse
Try a different port(usb2 are best)
Try a different cable
Different PC
If you have android sdk setup try updating it.
Hey guys, i never really need anyones help but this is annoying me now. My problem is that i have converted my HTC One to the google edition firmware and all was going great. Earlier today i wanted to try the latest MIUI Rom so i downloaded it and flashed it. Everything went smoothly until it came to reboot (i totally wiped phone before i installed MIUI) and now it wont turn on or charge and show only signs of life in the form of fastboot which i can use getvar all to pull my system info. Some fields are blank which arent meant to be. I cannot flash anything as screen wont turn on or even vibrate. Kind of at a loss now and any help will be appreciated.
Noel
noel8211 said:
Hey guys, i never really need anyones help but this is annoying me now. My problem is that i have converted my HTC One to the google edition firmware and all was going great. Earlier today i wanted to try the latest MIUI Rom so i downloaded it and flashed it. Everything went smoothly until it came to reboot (i totally wiped phone before i installed MIUI) and now it wont turn on or charge and show only signs of life in the form of fastboot which i can use getvar all to pull my system info. Some fields are blank which arent meant to be. I cannot flash anything as screen wont turn on or even vibrate. Kind of at a loss now and any help will be appreciated.
Noel
Click to expand...
Click to collapse
not positive but the MIUI rom may require a special version custom recovery. did you check that you have the correct recovery before flashing ?
clsA said:
not positive but the MIUI rom may require a special version custom recovery. did you check that you have the correct recovery before flashing ?
Click to expand...
Click to collapse
hey thanks for replying. i used the latest 2.8.0.0 twrp recovery. my getvar all is:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3662mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
C:\Program Files (x86)\Minimal ADB and Fastboot>
im not sure if thats all ok or not
noel8211 said:
hey thanks for replying. i used the latest 2.8.0.0 twrp recovery. my getvar all is:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3662mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
C:\Program Files (x86)\Minimal ADB and Fastboot>
im not sure if thats all ok or not
Click to expand...
Click to collapse
Is that your real MID and CID?
You should correct those and RUU back to stock and start over. Your phone is having an identity crisis [emoji2]
clsA said:
Is that your real MID and CID?
You should correct those and RUU back to stock and start over. Your phone is having an identity crisis [emoji2]
Click to expand...
Click to collapse
lol yeah thats what it said after i flashed MIUI. what would be the best way to sort them out?
Theirs a MID change tool you use in Twrp
And changing the CID is a simple fastboot command
clsA said:
Theirs a MID change tool you use in Twrp
And changing the CID is a simple fastboot command
Click to expand...
Click to collapse
ah CID will be easy but MID wont as i cant even get to recovery or anything. not even bootloader. I didnt realise MIUI would screw up this bad, or could it be something to do with the 'latest' twrp being too new?
noel8211 said:
ah CID will be easy but MID wont as i cant even get to recovery or anything. not even bootloader. I didnt realise MIUI would screw up this bad, or could it be something to do with the 'latest' twrp being too new?
Click to expand...
Click to collapse
Flash TWRP 2.6.3.3 it's the most reliable version
clsA said:
Flash TWRP 2.6.3.3 it's the most reliable version
Click to expand...
Click to collapse
i have been trying that for a while now but keep getting remote: not allowed errors
Is your bootloader relocked?
clsA said:
Is your bootloader relocked?
Click to expand...
Click to collapse
i didnt relock it after i flashed. can it relock itself?
noel8211 said:
i didnt relock it after i flashed. can it relock itself?
Click to expand...
Click to collapse
No and don't relock it. Their are people stuck and can't unlock coming from GPE
clsA said:
No and don't relock it. Their are people stuck and can't unlock coming from GPE
Click to expand...
Click to collapse
ah thats good then. i never bothered to re-lock it when i flashed the firmware as didnt see the point. all the guides i can find are to change things through adb which doesnt work as comupet dont pick it up. when however i do a fastboot devices, my device instaed of numbers , is ???????????????. im sure thats not normal.
by the way, thanks for helping me
noel8211 said:
ah thats good then. i never bothered to re-lock it when i flashed the firmware as didnt see the point. all the guides i can find are to change things through adb which doesnt work as comupet dont pick it up. when however i do a fastboot devices, my device instaed of numbers , is ???????????????. im sure thats not normal.
by the way, thanks for helping me
Click to expand...
Click to collapse
Well adb is only going to work in recovery so ignore that
So you flashed firmware ? Which one?
Did you try and get in stock recovery and do a factory reset
clsA said:
Well adb is only going to work in recovery so ignore that
So you flashed firmware ? Which one?
Did you try and get in stock recovery and do a factory reset
Click to expand...
Click to collapse
I flashed the latest MIUI from MIUIandroid and then just rebooted afterwards. the phone seems dead but i can get fastboot to partially work as my computer recognises it
noel8211 said:
I flashed the latest MIUI from MIUIandroid and then just rebooted afterwards. the phone seems dead but i can get fastboot to partially work as my computer recognises it
Click to expand...
Click to collapse
I'm going to need my PC to get you the links you need to try and get back up and running. I'll be back home in an hour or so
clsA said:
I'm going to need my PC to get you the links you need to try and get back up and running. I'll be back home in an hour or so
Click to expand...
Click to collapse
Thank you very much, i really appreciate it
noel8211 said:
Thank you very much, i really appreciate it
Click to expand...
Click to collapse
Ok I'm back
First lets try and get a working recovery on your phone
download and flash this >> twrp-recovery-2.7-m7-nobcb.img
fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery
We are following nkk71 guide here if you want to jump ahead
http://forum.xda-developers.com/showthread.php?t=2739126
also could you give me the name of the MIUI you downloaded
clsA said:
Ok I'm back
First lets try and get a working recovery on your phone
also could you give me the name of the MIUI you downloaded
Click to expand...
Click to collapse
i think he has a lot more to fix than just the misc partition, not sure if this is fixable, i believe the updater-script wrote to hboot partition, and he's unlikely to even be able to "fastboot oem rebootRUU" to fix that,
if by some chance he's able to get to recovery, then he'd have to manually dd all the messed up partitions.
OP, can you upload the updater-script (it's in <nameofrom>zip /META-INF/com/google/android) to pastebin (or zip it and attach it here).
nkk71 said:
i think he has a lot more to fix than just the misc partition, not sure if this is fixable, i believe the updater-script wrote to hboot partition, and he's unlikely to even be able to "fastboot oem rebootRUU" to fix that,
if by some chance he's able to get to recovery, then he'd have to manually dd all the messed up partitions.
OP, can you upload the updater-script (it's in <nameofrom>zip /META-INF/com/google/android) to pastebin (or zip it and attach it here).
Click to expand...
Click to collapse
yeah this could get complicated, I don't know the actual MIUI he used and he mentioned flashing a firmware, I hope he just meant flash a rom.
Hello Folks
My bootloader of my Desire 510 is unlocked and i want it back locked, but dont know how to do it
i hope someone can help me
Regards Marco
Addicted2Bass said:
Hello Folks
My bootloader of my Desire 510 is unlocked and i want it back locked, but dont know how to do it
i hope someone can help me
Regards Marco
Click to expand...
Click to collapse
Hello Marco,
Here is how to relock your bootloader:
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button until you get into the bootloader
3. Release "Down" and "Power" button
A different way to do it other than steps 1 - 3 is follow steps 6 - 8 and type in a command prompt
Code:
adb reboot bootloader
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background
5. Connect your USB cable and it will say "FASTBOOT USB"
6. Navigate to the folder you have your adb.exe, fastboot.exe stuff from Android Studio or wherever you obtained it from (Mine is in C:\myusername\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up your phone
10. You should see something like: "HT42PXU99475 fastboot" if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Type
Code:
fastboot oem lock
in the command window
You should see something like:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 596539196 (0x1FFFFD6C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 9
(bootloader) [INFO] Reset reason in IMEM is 0x77665800
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
Your phone will automatically reboot and your bootloader will be locked
You can check by booting into the bootloader and it should say *** RELOCKED *** at the top in white letters and purple background
Thanks Dude!
Its locked indeed!!
Do i need to use this step in order to return to stock? and what are the steps to return to stock,i have stock image?
is there a certain kernal to flash along with stock image,if someone could provide steps to return to stock,id be grateful! thanks
donthateme702 said:
Do i need to use this step in order to return to stock? and what are the steps to return to stock,i have stock image?
is there a certain kernal to flash along with stock image,if someone could provide steps to return to stock,id be grateful! thanks
Click to expand...
Click to collapse
You only need to follow those steps if you plan to use the RUU from here.
If you have a stock recovery, you can use TWRP. If you have the file boot.emmc.win in the recovery folder, that is the stock kernel. Just put the stock image on your sdcard and Restore it in TWRP.
It worked... A little too well.
blaqueknight said:
You only need to follow those steps if you plan to use the RUU from "I can't post links yet, but you get the idea..."
If you have a stock recovery, you can use TWRP. If you have the file boot.emmc.win in the recovery folder, that is the stock kernel. Just put the stock image on your sdcard and Restore it in TWRP.
Click to expand...
Click to collapse
I had been bricked, or at least I'm pretty sure I was. However... Upon trying to unlock the bootloader via the WinDroid deal offered here in xda, the bootloader now won't re-unlock.
The word *RELOCKED* has been frickin' glaring at me for over 3 hours now, and I can't seem to find the answer or help anywhere. :crying:
MN-StormChaser said:
I had been bricked, or at least I'm pretty sure I was. However... Upon trying to unlock the bootloader via the WinDroid deal offered here in xda, the bootloader now won't re-unlock.
The word *RELOCKED* has been frickin' glaring at me for over 3 hours now, and I can't seem to find the answer or help anywhere. :crying:
Click to expand...
Click to collapse
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.
MrMike2182 said:
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.
Click to expand...
Click to collapse
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!
MN-StormChaser said:
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!
Click to expand...
Click to collapse
WinDroid is a great tool. The only problem with it comes when you have adb installed already and you install the drivers that come with WinDroid. They cause a conflict.
I hope the manual method of unlocking works for you. It has always worked for me, unless I made a mistake. When I correct the mistake, it goes off without a hitch.
You can find the RUU here for your respective carrier.
MN-StormChaser said:
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!
Click to expand...
Click to collapse
If you need help with manually unlocking it let us know because it's really easy.
More details...
I may need some more help, pertaining the specific step-by-step stuff... Downloading the stock ... Rom/RUU?... from the HTC website. I'll be up all night trying to get this fixed, mainly due to needing my phone for my new job early this week. My end goal through all of this is to get a rom/kernel, or whatever else is needed, installed on it and either have it with write-protection removed or just completely blank so I don't have to worry about Boost hacking my phone and installing a bunch of crap and changing my screen setup. I really appreciate your help, guys. I will admit that, yes, I am slow to catch on to this stuff, but once I completely get the hang of this I want to be a big contributor to XDA and start helping others and developing/testing roms, etc.
Unlocking
MN-StormChaser said:
I may need some more help, pertaining the specific step-by-step stuff... Downloading the stock ... Rom/RUU?... from the HTC website. I'll be up all night trying to get this fixed, mainly due to needing my phone for my new job early this week. My end goal through all of this is to get a rom/kernel, or whatever else is needed, installed on it and either have it with write-protection removed or just completely blank so I don't have to worry about Boost hacking my phone and installing a bunch of crap and changing my screen setup. I really appreciate your help, guys. I will admit that, yes, I am slow to catch on to this stuff, but once I completely get the hang of this I want to be a big contributor to XDA and start helping others and developing/testing roms, etc.
Click to expand...
Click to collapse
If you go to http://www.htcdev.com/bootloader/ create an account, then they will walk you right through the method to unlock, and it is exactly the same method used to reunlock.
Hey do u know how to find which carrier the mobile is ??
Bcoz when i bought it,,the cover is of boostmobile...so is my carrier boost??
deepak oli said:
Hey do u know how to find which carrier the mobile is ??
Bcoz when i bought it,,the cover is of boostmobile...so is my carrier boost??
Click to expand...
Click to collapse
If that's what the cover says then that's what it is.. Boost Mobile. Where did you buy this phone from?
My relatives bought it from u.s!
deepak oli said:
My relatives bought it from u.s!
Click to expand...
Click to collapse
I'm pretty sure I can fix the phone now, since I finally have all the information I've needed for the last week!
Do you have a Boost Mobile over there in your Country? If not it's going to be pretty hard to use the phone since it's locked to Boost..
Hey, yooo hooo @deepak oli Answer me!!
---------- Post added at 10:09 PM ---------- Previous post was at 09:37 PM ----------
Fine don't answer me then, do it when you want to..
Ok here we go, you need to flash twrp from right here ---> twrp-2.8.7.0-a11.img This is going to be flashed after you unlock your boot loader so go use your unlock token and unlock the boot and then from a computer flash the twrp by doing fastboot flash recovery twrp-2.8.7.0-a11.img after you flash that go to the HBoot and tell it to reboot to recovery and while you're in recovery tap backup to make a backup because it needs to be done to move certain files/folders... Then go to the XDA thread and download the modded cm11 by me and follow the directions on which file to put it in and after this your phone will boot... CM11 Modded on XDA
Will this work and will i be able to use my phone again???
If yes then thhhaaaannnnkkkk uuuuuu!!!!!!
deepak oli said:
Will this work and will i be able to use my phone again???
If yes then thhhaaaannnnkkkk uuuuuu!!!!!!
Click to expand...
Click to collapse
It should have worked already if you did what I told you.
RUU for htc desire 510
MrMike2182 said:
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.
Click to expand...
Click to collapse
hey can you by any chance get a RUU for me. I have been searching for days (literally).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA49GY405962
(bootloader) imei: 123456789231654
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
Thats the phone info. i NEED it because i cant use my phones mobile data
Dopekyd said:
hey can you by any chance get a RUU for me. I have been searching for days (literally).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA49GY405962
(bootloader) imei: 123456789231654
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
Thats the phone info. i NEED it because i cant use my phones mobile data
Click to expand...
Click to collapse
Is your carrier Cricket or something else?