getting device id manually - Defy Q&A, Help & Troubleshooting

can we extract bootloader keys manually to get device id??
RETRIEVING YOUR DEVICE ID
Put your device in fastboot mode (Power+Vol Down) and connect over USB
Open a command prompt or Terminal session
Go to the Directory where you installed the Android SDK tools, and type:
$ fastboot oem get_unlock_data
This fastboot command will return a character string. This is the Device ID which you will be using to generate your unique unlock key.
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
one more question where can i find boot loader on my device/ or is it possible to extract bootloader related files?
does the key above (in bold) varies from device to device?

rishi2100 said:
can we extract bootloader keys manually to get device id??
RETRIEVING YOUR DEVICE ID
Put your device in fastboot mode (Power+Vol Down) and connect over USB
Open a command prompt or Terminal session
Go to the Directory where you installed the Android SDK tools, and type:
$ fastboot oem get_unlock_data
This fastboot command will return a character string. This is the Device ID which you will be using to generate your unique unlock key.
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
one more question where can i find boot loader on my device/ or is it possible to extract bootloader related files?
does the key above (in bold) varies from device to device?
Click to expand...
Click to collapse
YOU CANNOT UNLOCK DEFY BOOTLOADER. ITS NOT SUPPORTED AND MAYBE NEVER WILL BE!
Sent from my sending thing (copyright by domini99 )

Related

[how to]change your MID without the eng bootloader

this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
please note that s-off is required!
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)change your MID
warning: *do not try and type the command. please copy and paste it
-AT&T,developer,google play MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0712000 for modelid
fastboot reboot
________________________________________________________________________________________
-t mobile MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0713000 for modelid
fastboot reboot
________________________________________________________________________________________
-HTC_Europe MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0710000 for modelid
fastboot reboot
________________________________________________________________________________________
your command window should look like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links:
remove tampered banner: http://forum.xda-developers.com/showthread.php?t=2477792
change lock status flag(lock/unlock bootloader): http://forum.xda-developers.com/showthread.php?t=2475914
i dont think im going to add any more MIDs in the above post,as i dont think many(any?) will be flip flopping to something other than those 3. it could be dnagerous to try and convert m7_ul to m7_u or m7_wlv
if you need to change to something different let me know,and i can put it here,so all the comands are in one place. this post is for reference only.
for HTC_Europe international m7_ul PN0710000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
for m7_u PN0711000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
for other gsm international m7_ul PN0714000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x34\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
for verizon,m7_wlv PN0731000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
*please note that neither sprint nor vzw devices can be converted to gsm or vice versa
for sprint, m7_wls PN0720000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
*please note that neither sprint nor vzw devices can be converted to gsm or vice versa
for htc one dual sim PN0751000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x35\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
@scotty1223
My MID is currently: PN0711000 and i want to change it to: PN0710000
Can you add the correct command line in adb shell?
Great!
Please make for MID: PN0710000.
Kudos 2 u man. Another really useful post. I would appreciate the code for PN0710000 also as I am currently planning on converting to the google edition, but would like to know the code to revert back to the above if I need to return to HTC at sometime. Much more convienient (and less risky) than using eng boot method to change.
Nerekan said:
Great!
Please make for MID: PN0710000.
Click to expand...
Click to collapse
I think this is the command for "PN0710000"
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
but wait scotty1223 to confirm my theory.....
see U!
electronical said:
@scotty1223
My MID is currently: PN0711000 and i want to change it to: PN0710000
Can you add the correct command line in adb shell?
Click to expand...
Click to collapse
zaphodbeeb said:
Kudos 2 u man. Another really useful post. I would appreciate the code for PN0710000 also as I am currently planning on converting to the google edition, but would like to know the code to revert back to the above if I need to return to HTC at sometime. Much more convienient (and less risky) than using eng boot method to change.
Click to expand...
Click to collapse
what model/variant do you guys have? if this is another variant of m7_u,let me know if you run into any snags or issues with the conversion to google play,wich is an m7_ul. id really appreciate reports of success or failure for OTAs.
id like to convert my dads m7_u(PN0711000) to HTC__001 and PN0712000 so he could recieve european updated. not sure if OTAs will catch some other flag since the m7_u has no provisions for LTE.
feel free to post here or pm me anything you learn while converting,and if you intend to OTA or not
ervius said:
I think this is the command for "PN0710000"
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
but wait scotty1223 to confirm my theory.....
see U!
Click to expand...
Click to collapse
looks fine- x30 = 0 so just need to replace the 31,wich obviously = 1
I have a m7_ul.
zaphodbeeb said:
I have a m7_ul.
Click to expand...
Click to collapse
and are PN0711000?
edit:
i see,you are international. outside the us m7_ul is the PN710000. had some MID confusion,lol.. move along,nothing to see here
OK I have a uk HTC one my current mid is PN0710000
I would like the gpe MID is this the att developer edition you have listed on the first page?
Edit also guessing you need root?
ngagephone said:
OK I have a uk HTC one my current mid is PN0710000
I would like the gpe MID is this the att developer edition you have listed on the first page?
Edit also guessing you need root?
Click to expand...
Click to collapse
correct,to the best of my knowledge,the GPE shares PN0712000 along with dev edition,att,and canadian variants.
yes,you need root and s-off.
Thank you
Just clarify,
If I have an US T-mobile One, I wanna convert to International version as I can get the x.xx.401.xx OTA, I have to change my CID to HTC_001 and MID to PN0710000. Is this correct?
Sent from my HTC ViperOne
tommy0411 said:
Just clarify,
If I have an US T-mobile One, I wanna convert to International version as I can get the x.xx.401.xx OTA, I have to change my CID to HTC_001 and MID to PN0710000. Is this correct?
Sent from my HTC ViperOne
Click to expand...
Click to collapse
correct
That's one neat hack. Thank you for this!
Sent from my HTC One using Tapatalk
io53 said:
That's one neat hack. Thank you for this!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
glad it was helpful. basically the same idea as hex editing p4 to change cid with evita and ville,so its not a new concept. all i did was locate the mid and apply the same idea
Is the MID on the same place in the GE bootloaders?
Sent from my HTC One using Tapatalk
io53 said:
Is the MID on the same place in the GE bootloaders?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
The mid is not located in the bootloader,it's in p6. I'm fairly certain the mid is in the same location,but I've not checked it. You're welcome to dump it and we can verify.
Sent from my HTC One VX using Tapatalk
Change MID to 710000 from 714000 (S-off)
scotty1223 said:
this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
please note that s-off is required!
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)change your MID
warning: *do not try and type the command. please copy and paste it
-AT&T,developer,google play MID:
enter the following:
adb shell
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0712000 for modelid
fastboot reboot
________________________________________________________________________________________
-t mobile MID:
enter the following:
adb shell
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0713000 for modelid
fastboot reboot
________________________________________________________________________________________
your command window should look like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links:
http://forum.xda-developers.com/showthread.php?t=2477792
http://forum.xda-developers.com/showthread.php?t=2475914&highlight=+how+to+lock+unlock
Click to expand...
Click to collapse
Hi,
I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error (error 24)
---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------
Hi,
I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error (error 24)
papubhai said:
Hi,
I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error
Click to expand...
Click to collapse
you just enter the adb command in the second post for 710000. if you need more guidance than what the OP states,you maybe not should do this.
im not sure you should do this,anyway. there is likely a reason the eng method failed. what variant is 714000?
if you are m7_ul it should be ok to switch to 710000.but if you are something else(m7_u,m7_wls,etc) it may not be safe to convert to that cid/mid

[how to] change your MID without an eng bootloader

READ THIIS!
*this thread is for m8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
_____________________________________________________________________________________________________________________
this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
please note that s-off is required!
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
*i dont have m8 yet. if you want to test,ill add you to the credits.
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)change your MID
warning: *do not try and type the command. please copy and paste it
-AT&T, unlocked, developer MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0P6B12000 for modelid
fastboot reboot
________________________________________________________________________________________
-google play MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x37\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0P6B17000 for modelid
fastboot reboot
________________________________________________________________________________________
-t mobile MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0P6B13000 for modelid
fastboot reboot
________________________________________________________________________________________
-HTC_Europe MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0P6B10000 for modelid
fastboot reboot
________________________________________________________________________________________
your command window should look like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links:
remove tampered banner: http://forum.xda-developers.com/showthread.php?t=2708565
change lock status flag(lock/unlock bootloader): http://forum.xda-developers.com/showthread.php?t=2708571
other MIDs
Rogers MID
0P6B16000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x36\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
*thanks @craig0r
___________________________________________________________________________________________
wind(canada) MID
0P6B13000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
___________________________________________________________________________________________
verizon MID
0P6B20000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or sprint device to this in attempts to use it on vzw and convert to a vzw device(or vice versa)
___________________________________________________________________________________________
sprint MID
0P6B70000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).
___________________________________________________________________________________________
0P6B11000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
___________________________________________________________________________________________
europe m8 dual sim MID
0P6B64000
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x36\x00\x34\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
*thanks @EddyOS
warning! provided by request. i would strongly advise against attempting to convert single sim m8 to dual sim,or vise versa
___________________________________________________________________________________________
one more
So proud to see you here man.
I've converted my M7 from AT&T to Europe version and received OTA successfully.
Thanks for your great instructions.
Sorry if this is a dumb question, but I want to be clear before I try this sort of thing out.
Am I to understand that the developer edition, Google Play edition, and AT&T version all have the same MID?
Sent from my HTC One using XDA Premium HD app
craig0r said:
Sorry if this is a dumb question, but I want to be clear before I try this sort of thing out.
Am I to understand that the developer edition, Google Play edition, and AT&T version all have the same MID?
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
We have recently learned gpe is different.
T-Mobile US please.
Sent from my HTC One_M8 using Tapatalk 2
Would anyone happen to know if the unlocked edition is the same as AT&T,developer, google play?
yourunlikegus said:
Would anyone happen to know if the unlocked edition is the same as AT&T,developer, google play?
Click to expand...
Click to collapse
i do not believe so. do you have an unlocked version,or you want to convert to it?
scotty1223 said:
i do not believe so. do you have an unlocked version,or you want to convert to it?
Click to expand...
Click to collapse
I'll be getting one delivered tomorrow. If one hasn't shown up by the time it gets here I'll post it. After getting the Google drive upgrade was planning on changing to developer
cool.let me know what the mid is, if its same ill add that to the OP,and if its different,ill list the command to go back to that if needed in the second post.
scotty1223 said:
cool.let me know what the mid is, if its same ill add that to the OP,and if its different,ill list the command to go back to that if needed in the second post.
Click to expand...
Click to collapse
Right on
yourunlikegus said:
Right on
Click to expand...
Click to collapse
The MID for unlocked edition is the same as at&t, developer and google play edition
yourunlikegus said:
The MID for unlocked edition is the same as at&t, developer and google play edition
Click to expand...
Click to collapse
awsome,thanks!
Change MID for HTC One M8 EE UK
I am s-off and rooted, will this work for M8
(I see all comments are from M7)
Should I change my CID from ORANG001 to supercid?
What benefits can I get? Will this remove the EE simlock?
Advice welcome please
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.14.213315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.61.17
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I know this thread is about mid but whats the cid for the unlocked version? I was told before that it was htc__001 and that its mid was the european version on this thread, but i see the mid is different on here. Either way I changed both my cid to htc__001 and the mid on here for unlocked devices since im trying to change my t-mobile version to unlocked. Am i go to go to flash the correct firmware? I'm s-off as well
dachat said:
I am s-off and rooted, will this work for M8 yes. (you are in m8 general)
(I see all comments are from M7)
Should I change my CID from ORANG001 to supercid? i dont know,should you? what do you want to achieve?
What benefits can I get? first thing said in the first post. if you dont fit that scenario you dont need to change your nid. Will this remove the EE simlock? no
Advice welcome please
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.14.213315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.61.17
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Gja88 said:
I know this thread is about mid but whats the cid for the unlocked version? I was told before that it was htc__001 and that its mid was the european version on this thread, but i see the mid is different on here. Either way I changed both my cid to htc__001 and the mid on here for unlocked devices since im trying to change my t-mobile version to unlocked. Am i go to go to flash the correct firmware? I'm s-off as well
Click to expand...
Click to collapse
not sure what the cid is for the unlocked version. maybe @yourunlikegus can provide that info.
if youve changed your cid/mid to htc europe,you can now run an unbranded(x.xx.401.x) ruu if one exists,to complete the conversion.
if the unlocked cid is not HTC__001 and does not match your mid,you cannot ruu and OTAs will not happen.
Change from ORANG001 to HTC_001
I am hoping to change my device to enable it to have the unlocked Europe stock rom getting stock ota's
Is this possible and how should I set about it?
I have S-off rooted ul_M8 Originally on EE
Running Android Revolution HD 5.0
I know it specifies Windows 7 and older but just looking to confirm. This can't be done with a Mac, can it? I have adb running on it, but in the shell, the super user command isn't recognized.
dachat said:
I am hoping to change my device to enable it to have the unlocked Europe stock rom getting stock ota's
Is this possible and how should I set about it?
I have S-off rooted ul_M8 Originally on EE
Running Android Revolution HD 5.0
Click to expand...
Click to collapse
-change cid
-change mid
-run a release keys ruu for the build you want to run
dave.michael said:
I know it specifies Windows 7 and older but just looking to confirm. This can't be done with a Mac, can it? I have adb running on it, but in the shell, the super user command isn't recognized.
Click to expand...
Click to collapse
Yes it can be done on a Mac,but you're on your own getting adb/fastboot working. I've zero Mac experience
Sent from my HTC PG09410 using Tapatalk 2

[GUIDE][MM][6.12.1540.4] HTC One M8 to Developer Edition with Original RUU EXE File

Device MUST be S-OFF!
Requirements
HTC Fastboot and ADB : Google Drive
Firmware : Google Drive
RUU EXE : http://www.htc.com/us/support/htc-one-m8/news/
First Step
Change your MID and CID from yours to Developer Edition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open your Command Prompt on your installation folder with "Left Shift + Right Mouse Click"
MID Change
adb.exe shell
su (if needed to get a # prompt)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit (if you have #, 2 times)
adb.exe reboot-bootloader
CID Change
htc_fastboot.exe oem writecid BS_US002
htc_fastboot.exe reboot-bootloader
htc_fastboot.exe oem rebootRUU (you have to see black screen with green HTC logo)
Flash firmware-6.12.1540.4
htc_fastboot.exe flash zip firmware-6.12.1540.4.zip (you have to get error, try again this time it will do)
htc_fastboot.exe reboot-bootloader ( do this when firmware process done, you have to see a green bar at 100%)
htc_fastboot.exe erase cache
Flash 6.12.1540.4 RUU
You have to open RUU EXE which downloaded from htc news website.
Wait until UNCOMPRESSING done.
You have to see "License Agreement", DO NOT close this window.
Open your file explorer or run command and type %TEMP% , and click ENTER
You have to be in there "C:\Users\*your pc name*\AppData\Local\Temp"
Find last edited Folder, it must have "corecomp.ini" , "dotnetinstaller.exe" , "ISBEW64.exe" and another Folder.
Open this folder and copy "rom.zip" into your installation folder where htc_fastboot.exe exist.
htc_fastboot.exe oem rebootRUU (you have to see black screen with green HTC logo)
htc_fastboot.exe flash zip rom.zip (first you have to get error, but the process restart automatically)
You have to wait about 5-10 minutes until all processes done.
htc_fastboot.exe reboot-bootloader
htc_fastboot.exe erase cache
PRESS volume down button to do Factory Reset and PRESS power button to select.
Phone restart automatically, when the factory reset done
All done, be happy
Boss pls help me
HTC M8 Sprint
CID : BS_US002
MODEL : OP6B70000
Pls help Me .... when i am try to flash firmware-6.12.1540.4 then error massage
C:\Users\MONOAR\Desktop\One_M8_All-In-One_Kit_v\data>fastboot.exe flash zip firm
ware-6.12.1540.4.zip
< waiting for device >
target reported max download size of 1826414592 bytes
error: cannot load 'firmware-6.12.1540.4.zip': No error
[email protected]
monoar30 said:
HTC M8 Sprint
CID : BS_US002
MODEL : OP6B70000
Pls help Me .... when i am try to flash firmware-6.12.1540.4 then error massage
C:\Users\MONOAR\Desktop\One_M8_All-In-One_Kit_v\data>fastboot.exe flash zip firm
ware-6.12.1540.4.zip
< waiting for device >
target reported max download size of 1826414592 bytes
error: cannot load 'firmware-6.12.1540.4.zip': No error
[email protected]
Click to expand...
Click to collapse
dunno if i m reading that paths wrong but it looks you did something wrong related to the filepaths of the firmware and adb itself. - go into your folder were adb is located. might be inside your One-M8-All-In-One_Kit folder ....then paste the firmware zip in just the same folder. ( location of adb ) ....after that, navigate to that adb location/folder, (you should actually be there because you have just copied the firmware zip into that folder ..so skip that .... press shift + right mousebutton on empty space inside of the folder ( so dont start any program or click on a file, just hold shift and press the right mousekey to open die normal windows dialog window where you can change the view of the folder or add new files etc. )
by using the shift+right mouse key combi, u will see another option inside of that dialog apart from the common stuff you normally have listed. -> "open command prompt right here" ( or something similar, dunno the exact wording in english )
so click that order, it will open up the windows console (cmd) -> make your phone reboot to the bootloader by writing "adb reboot-bootloader" ( i guess it should be obvious that your phone needs to be connected via usb allready )
- ( you can also just hold the power button on your phone and pick bootloader at the boot-menu, just as you like.
- arrived at bootloader, make sure you phone shows "fastboot-usb"
- write "fastboot oem rebootRUU" inside the cmd window -> phone should boot into the RUU modus.
- write "fastboot flash zip firmware-6.12.1540.4.zip" (not fastboot".exe" - just fastboot ... ) -> make sure you use the correct name of the zip. - you need use the filename of the firmware that you ve copied into the adb folder at the beginning. - to prevent issues, you should rename the firmware zip to something simple. - like just firmware.zip or firm.zip, without that versionsnumber. - its just easier for you to write that into the cmd window and you will be sure that issues might be not related to some wrong written filename.
done.
edit: @sceryavuz is htc_fastboot anything special or just the normal adb? if it is different, may you explain to me what it is?
What is the advantage of the Developer edition?
Can I do this with a vzw m8? I want to see if this helps me run GPE and AOSP roms without the cellular issues I've been having. Also, can I change back as well?
Sent from my HTC6525LVW using XDA-Developers mobile app
edit: @sceryavuz is htc_fastboot anything special or just the normal adb? if it is different, may you explain to me what it is?[/QUOTE]
htc_fastboot you need this for flashing firmware. Security reasons. You can't flash recovery, for example with this.
fastboot it's for everithing else, other than firmware.
For me it was like that, at least..
vladaxx said:
What is the advantage of the Developer edition?
Click to expand...
Click to collapse
It is the full unlocked rom, you can do anything with Developer Edition without any errors. This is the most stable version.
Dan Tekle said:
Can I do this with a vzw m8? I want to see if this helps me run GPE and AOSP roms without the cellular issues I've been having. Also, can I change back as well?
Sent from my HTC6525LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't know if it is work or not? I have AT&T device and it works. Sprint and verizon device may have specific modem.
_moelle said:
dunno if i m reading that paths wrong but it looks you did something wrong related to the filepaths of the firmware and adb itself. - go into your folder were adb is located. might be inside your One-M8-All-In-One_Kit folder ....then paste the firmware zip in just the same folder. ( location of adb ) ....after that, navigate to that adb location/folder, (you should actually be there because you have just copied the firmware zip into that folder ..so skip that .... press shift + right mousebutton on empty space inside of the folder ( so dont start any program or click on a file, just hold shift and press the right mousekey to open die normal windows dialog window where you can change the view of the folder or add new files etc. )
by using the shift+right mouse key combi, u will see another option inside of that dialog apart from the common stuff you normally have listed. -> "open command prompt right here" ( or something similar, dunno the exact wording in english )
so click that order, it will open up the windows console (cmd) -> make your phone reboot to the bootloader by writing "adb reboot-bootloader" ( i guess it should be obvious that your phone needs to be connected via usb allready )
- ( you can also just hold the power button on your phone and pick bootloader at the boot-menu, just as you like.
- arrived at bootloader, make sure you phone shows "fastboot-usb"
- write "fastboot oem rebootRUU" inside the cmd window -> phone should boot into the RUU modus.
- write "fastboot flash zip firmware-6.12.1540.4.zip" (not fastboot".exe" - just fastboot ... ) -> make sure you use the correct name of the zip. - you need use the filename of the firmware that you ve copied into the adb folder at the beginning. - to prevent issues, you should rename the firmware zip to something simple. - like just firmware.zip or firm.zip, without that versionsnumber. - its just easier for you to write that into the cmd window and you will be sure that issues might be not related to some wrong written filename.
done.
edit: @sceryavuz is htc_fastboot anything special or just the normal adb? if it is different, may you explain to me what it is?
Click to expand...
Click to collapse
htc_fastboot is stock fastboot that released by htc. You can use your fastboot already have. htc_fastboot check all zip or img file for compatibility.
null0seven said:
edit: @sceryavuz is htc_fastboot anything special or just the normal adb? if it is different, may you explain to me what it is?
htc_fastboot you need this for flashing firmware. Security reasons. You can't flash recovery, for example with this.
fastboot it's for everithing else, other than firmware.
For me it was like that, at least..
Click to expand...
Click to collapse
Yes, mostly agreed (security and compatibility reasons). You can flash TWRP with htc_fastboot
@monoar30 @_moelle @Dan Tekle @null0seven @sceryavuz
hey guys just to make it sense
you can't convert CDMA ( device) firmware to GSM firmware
sprint and Verizon can't be converted to any other GSM firmware
HTC_fastboot used to flash big .zip as you can flash any thing by regular fastboot but RUU.zip needs to be flashed by HTC_fastboot
Did anyone with Verizon M8 manage to install it?
I managed to change CID, MID and install firmware without any errors, but when I try to flash rom.zip it says file is too large. Also the device doesn't recognize SIM card when on Developer Edition firmware. I guess this is because of the hardware difference, we won't be able to get this ROM working.
M.Ned said:
Did anyone with Verizon M8 manage to install it?
I managed to change CID, MID and install firmware without any errors, but when I try to flash rom.zip it says file is too large. Also the device doesn't recognize SIM card when on Developer Edition firmware. I guess this is because of the hardware difference, we won't be able to get this ROM working.
Click to expand...
Click to collapse
you are lucky if your device still working
read the post above yours
you can't flash GSM firmware on CDMA device because the hardware is different
i have a verizon htc one M8, unlocked, S-OFF, SuperCID, rooted, boot loader unlocked working with GSM carrier in India, I unlocked couple more LTE bands etc. Can I flash this as I don't have the CDMA only device?
Chandresh204 said:
i have a verizon htc one M8, unlocked, S-OFF, SuperCID, rooted, boot loader unlocked working with GSM carrier in India, I unlocked couple more LTE bands etc. Can I flash this as I don't have the CDMA only device?
Click to expand...
Click to collapse
if your device hardware match the GSM variant then you can
if didn't then you can't
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**************
(bootloader) imei: 99**************
(bootloader) imei2: Not Support
(bootloader) meid: 99**************
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
--------------------------------------------------------------------------------
Successfully able to change my cid as well as mid as previous its was 0P6B70000
So now i am still not able to install developer version rom
And Successfully flashed firmware-6.12.1540.4.zip
{F:\Utility\Softwares\Mobile Flushing\HTC one m8>fastboot flash zip firmware-6.12.1540.4.zip
sending 'zip' (31625 KB)...
OKAY [ 1.994s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) total_image_number=8
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
(bootloader) current_image_number=7
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.177s
F:\Utility\Softwares\Mobile Flushing\HTC one m8>fastboot flash zip firmware-6.12.1540.4.zip
sending 'zip' (31625 KB)...
OKAY [ 2.004s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=16
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,65
(bootloader) [RUU]UZ,adsp,75
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,45
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=3
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1,0
(bootloader) [RUU]WP,sbl1,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=6
(bootloader) start image[sdi] unzipping & flushing...
(bootloader) [RUU]UZ,sdi,0
(bootloader) [RUU]UZ,sdi,100
(bootloader) [RUU]WP,sdi,0
(bootloader) [RUU]WP,sdi,100
(bootloader) ...... Successful
(bootloader) current_image_number=7
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) [RUU]WP,sensor_hub,0
(bootloader) [RUU]WP,sensor_hub,4
(bootloader) [RUU]WP,sensor_hub,8
(bootloader) [RUU]WP,sensor_hub,12
(bootloader) [RUU]WP,sensor_hub,16
(bootloader) [RUU]WP,sensor_hub,20
(bootloader) [RUU]WP,sensor_hub,24
(bootloader) [RUU]WP,sensor_hub,28
(bootloader) [RUU]WP,sensor_hub,32
(bootloader) [RUU]WP,sensor_hub,36
(bootloader) [RUU]WP,sensor_hub,40
(bootloader) [RUU]WP,sensor_hub,44
(bootloader) [RUU]WP,sensor_hub,48
(bootloader) [RUU]WP,sensor_hub,52
(bootloader) [RUU]WP,sensor_hub,56
(bootloader) [RUU]WP,sensor_hub,60
(bootloader) [RUU]WP,sensor_hub,64
(bootloader) [RUU]WP,sensor_hub,68
(bootloader) [RUU]WP,sensor_hub,72
(bootloader) [RUU]WP,sensor_hub,76
(bootloader) [RUU]WP,sensor_hub,80
(bootloader) [RUU]WP,sensor_hub,84
(bootloader) [RUU]WP,sensor_hub,88
(bootloader) [RUU]WP,sensor_hub,92
(bootloader) [RUU]WP,sensor_hub,96
(bootloader) [RUU]WP,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=8
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=9
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ..... Bypassed
(bootloader) current_image_number=10
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ..... Bypassed
(bootloader) current_image_number=11
(bootloader) start image[tz] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=12
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=13
(bootloader) start image[radio] unzipping & flushing...
(bootloader) trying to rename MBA
(bootloader) ...... Successful
(bootloader) current_image_number=14
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=15
OKAY [ 59.617s]
finished. total time: 61.621s }
---------------------------------------------------
and when i am flashing rom.zip then its saying
F:\Utility\Softwares\Mobile Flushing\HTC one m8>fastboot flash zip rom.zip
load_file: could not allocate 1574717756 bytes
error: cannot load 'rom.zip'
so what should i do
Shakil Murm said:
(bootloader) product: m8_whl
Click to expand...
Click to collapse
Your device is m8_whl and this RUU is meant for m8_ul or m8_ul_ca only.
Return to stock .. if you're lucky you still can use your device but lose the ability to connect to 3G/4G/LTE.
(because you most probably already bricked the radio after your flash the firmware which is not meant for your device variant)
ckpv5 said:
Your device is m8_whl and this RUU is meant for m8_ul or m8_ul_ca only.
Return to stock .. if you're lucky you still can use your device but lose the ability to connect to 3G/4G/LTE.
(because you most probably already bricked the radio after your flash the firmware which is not meant for your device variant)
Click to expand...
Click to collapse
i'm trying to tell them that this method works on GSM devices only but no one read
please @sceryavuz ADD IT TO OP THIS METHOD WORKS ON GSM DEVICES ONLY NO VERIZON OR SPRINT
please ckpv5 am i right or not ??
RUU Not Working?
Hi,
I followed your instructions and the Developer Edition rom flashed and appears to be working fine, thanks very much.
After setting the phone up I wanted to try and test flashing again with RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe . The process fails after "Verifying information on your Android phone. Please wait..." with ERROR 170 USB CONNECTION ERROR. I've checked and the USB connection seems to be fine. Is this to be expected?
Thanks again.
0graham0 said:
Hi,
I followed your instructions and the Developer Edition rom flashed and appears to be working fine, thanks very much.
After setting the phone up I wanted to try and test flashing again with RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe . The process fails after "Verifying information on your Android phone. Please wait..." with ERROR 170 USB CONNECTION ERROR. I've checked and the USB connection seems to be fine. Is this to be expected?
Thanks again.
Click to expand...
Click to collapse
run the RUU while the device boot into fastboot and use USB 2 not USB 3
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
run the RUU while the device boot into fastboot and use USB 2 not USB 3
Click to expand...
Click to collapse
ah, that did the trick. thanks very much.
I was unable to flash the rom.zip with google's fastboot.exe (recogniced wrong size, header error, etc.....)!
Use htc_fastboot.exe found in the same temporary folder as rom.zip!
Worked for me. Why flash firmware first??
OP instructions worked for me . Was coming from US AT&T / Cingular (Cricket?)
Why did we flash firmware zip firmware and THEN flash the RUU pulled from the temp folder?

Unlocking Bootloader on Moto G (3rd Generation) 2015

Note: Not all Moto G 2015 are unlockable, though the procedure for all of them is the same.
Also it would be great to keep this page open while following through on your PC instead of your phone as you'll be rebooting and resetting your phone by following this procedure.
Click to expand...
Click to collapse
Prerequisites:
ADB (Android Debugging Bridge) tools for your OS (Windows/Linux/Mac)
Windows: https://dl.google.com/android/repository/sdk-tools-windows-3859397.zip
Mac: https://dl.google.com/android/repository/sdk-tools-darwin-3859397.zip
Linux: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip
Custom Recovery Image (TWRP or some other that you prefer):
https://forum.xda-developers.com/devdb/project/?id=11051#downloads
(Official TWRP web hosted version)https://twrp.me/motorola/motorolamotog2015.html
https://dl.twrp.me/osprey
https://eu.dl.twrp.me/osprey
USB Cable to Connect the phone to the computer
The Phone: Moto G 2015 (preferably Fully Charged)
The device drivers (for Windows and Mac): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
A good and active Internet Connection
An active Email address and client to quickly view it.
In this tutorial I'll be referring to Linux terminal, Mac Terminal & Windows Command prompt/Powershell simply as terminal.
Click to expand...
Click to collapse
Installing adb and fastboot
Google hosts zips including only adb and fastboot. You can set these up for use with the instructions below.
On Windows
Download the Windows zip (Full version: https://dl.google.com/android/repository/sdk-tools-windows-3859397.zip)(barebones version: https://dl.google.com/android/repository/platform-tools-latest-windows.zip) from Google.
Extract it somewhere - for example, %USERPROFILE%\adb-fastboot
• On Windows 7/8:
1. From the desktop, right-click My Computer and select Properties
2. In the System Properties window, click on the Advanced tab
3. In the Advanced section, click the Environment Variables button
4. In the Environment Variables window, highlight the Path variable in the Systems Variable section and click the Edit button
5. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• On Windows 10:
1. Open the Start menu, and type “advanced system settings”
2. Select “View advanced system settings”
3. Click on the Advanced tab
4. Open the “Environment Variables” window
5. Select the Path variable under “System Variables” and click the “Edit” button
6. Click the “Edit Text” button
7. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• Install the device drivers linked in prerequisites (or from Motorolla support site), and reboot.
On macOS
Download the macOS zip (full version: https://dl.google.com/android/repository/sdk-tools-darwin-3859397.zip)(Barebones version: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.bash_profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
On Linux
Download the Linux zip (Full version: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip)(Barebones version: https://dl.google.com/android/repository/platform-tools-latest-linux.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
You may also need to set up udev rules: see this repository (https://github.com/M0Rf30/android-udev-rules#installation) for more info.
Setting up adb
To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.
2. Tap on “Build number” seven times.
3. Go back, and select “Developer options”.
4. Scroll down, and check the “Android debugging” entry under “Debugging”.
5. Plug your device into your computer.
6. On the computer, open up a terminal/command prompt and type adb devices.
7. A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”.
Congratulations! adb is now ready to use with your device.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down and Volume Up to scroll and Power to select.
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at Motorola Support (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) to unlock your bootloader, you will need to register at this site with a working/active email to recieve the OEM unlock code.
Note: If your device is not supported by the Motorola Bootloader Unlock
website, you will need to use an alternative bootloader unlock method like
SunShine (http://theroot.ninja/index.html).
Installing a custom recovery using fastboot
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone. This needs to be done again due to resetting of your phone.
3. Download recovery - visit twrp.me to obtain the latest version of Team Win
Recovery Project for your device. Moto G 2015 does have an official TWRP recovery that you can find here: https://twrp.me/motorola/motorolamotog2015.html
4. Connect your device to your PC via USB.
5. Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down and Volume Up to scroll and Power to select.
Click to expand...
Click to collapse
6. Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>" , try running
Code:
fastboot
as root/Administrator.
7. Flash recovery onto your device:
Code:
fastboot flash recovery your_recovery_img.img
This command assumes the recovery image is present in your current working directory (Check using DIR on command prompt or ls command on terminal)
If it isn't you can change your current directory to the directory containing the recovery image or copy/move the recovery image to your current working directory.
8. Now reboot into recovery to verify the installation:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down to scroll to recovery and then use Power to select.
That's all folks. You may now root your phone, or even flash a custom ROM. I suggest getting openGapps for the custom ROM if you wish to use Google play services on the custom ROM.
Popular adb commands
Code:
adb shell
Launches a shell on the device accessed through the terminal on your computer.
Code:
adb push <local> <remote>
Pushes the file <local> to <remote>
Code:
adb pull <remote> [<local>]
Pulls the file <remote> to <local>. If <local> isn’t specified, it will pull to the current folder.
Code:
adb logcat
Allows you to view the device log in real-time. You can use adb logcat -b radio to view radio logs, and adb logcat -C to view logs in colour
Code:
adb install <file>
Installs the given .apk file to your device
<local> refers to location on your computer (like c:\\Users\%USERPROFILE%\adb-fastboot on windows or ~/adb-fastboot on unix based OS), while <remote> refers to location on your android device (like "/sdcard/", without quotes)
Thanks to @acejavelin for helping members troubleshoot problems that they faced
Nice tutorial... I have nothing to add, this is pretty comprehensive. Well done!
I have unlocked the device with this guide, but unable to flash recovery. I downloaded the file twrp-osprey-3.1.0-r1 & copied it in adb-fastboot folder. Now when I try to flash the recovery it says "no such file or directory" Does anyone know the fix? I tried extracting the file but winzip gives an error!
Dhaval1703 said:
I have unlocked the device with this guide, but unable to flash recovery. I downloaded the file twrp-osprey-3.1.0-r1 & copied it in adb-fastboot folder. Now when I try to flash the recovery it says "no such file or directory" Does anyone know the fix? I tried extracting the file but winzip gives an error!
Click to expand...
Click to collapse
This is a command line error in Windows, you are not issuing the command properly. Assuming you are using the current file from here: https://dl.twrp.me/osprey/ and have placed the file in your adb-fastboot folder, the command is:
Code:
fastboot flash recovery twrp-3.1.1-0-osprey.img
If edited name of file will need to put for example recovery.img. img not just .img found this out the hard way
Sent from my Robin using Tapatalk
toxicmender said:
Note: Not all Moto G 2015 are unlockable, though the procedure for all of them is the same.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down and Volume Up to scroll and Power to select.
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at Motorola Support (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) to unlock your bootloader, you will need to register at this site with a working/active email to recieve the OEM unlock code.
Note: If your device is not supported by the Motorola Bootloader Unlock
website, you will need to use an alternative bootloader unlock method like
SunShine (http://theroot.ninja/index.html).
Click to expand...
Click to collapse
Hey...
I'm not able to do so. There is no chance to get to developer mode or usb debugging mode. what can i do now?
please help. thx
wavebooster said:
Hey...
I'm not able to do so. There is no chance to get to developer mode or usb debugging mode. what can i do now?
please help. thx
Click to expand...
Click to collapse
Not able to do what?
USB Debugging Mode is not needed, but you need to have OEM Unlocking enabled... If that isn't possible, try Sunshine but it isn't free.
acejavelin said:
Not able to do what?
USB Debugging Mode is not needed, but you need to have OEM Unlocking enabled... If that isn't possible, try Sunshine but it isn't free.
Click to expand...
Click to collapse
OK, I checked to enable the OEM Unlock but with the step 4 on motorola website I have some problems. There is no code when I follow the instructions. According to the list I should be able to unlock my phone.
Here the Code when I tried to get the code to enter it on the moto website:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.CB
(bootloader) product: osprey
(bootloader) board: osprey
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x4
(bootloader) emmc: 8GB Samsung REV=07 PRV=01 TYPE=57
(bootloader) ram: 1024MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY22228MXD
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 1856E20A00000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: "i deleted this"
(bootloader) meid:
(bootloader) date: 07-11-2015
(bootloader) sku: XT1541
(bootloader) battid: SNN5959A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Feb 25 9:46:27 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_reteu/osprey_umts:
(bootloader) ro.build.fingerprint[1]: 6.0.1/MPI24.107-55/33:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.61.55.osprey_rete
(bootloader) ro.build.version.full[1]: u.reteu.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband[0]: M8916_2020632.44.03.21.54R OSPREY_EMEA
(bootloader) version-baseband[1]: _CUST
but when I try to "fastboot oem get_unlock_data" then I get following:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.388s
I tried it with different usb cables, on different PC's, with android sdk and minimal adb...
no chance..
Do you have any ideas?
wavebooster said:
but when I try to "fastboot oem get_unlock_data" then I get following:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.388s
[/SIZE][/SIZE]
I tried it with different usb cables, on different PC's, with android sdk and minimal adb...
no chance..
Do you have any ideas?
Click to expand...
Click to collapse
The bootloader "slot" thing is nothing, in newer devices that shipped with Nougat they use an A-B software slot configuration, the message in red just means that fastboot didn't detect any software slots which is normal with this device but has no effect on functionality.
Try a factory reset then see if you can get the unlock token. Otherwise I would suggest trying to find an older version of fastboot, or even Moto's mFastboot and see if that gives different results.
Otherwise, Moto is not very forthcoming for help unlocking and there is nothing we can do if we can't get the unlock token, although they do have an official forum and discussions related to unlocking are in the Development area, but since this is not a "developer" edition device, they often will not help very much.
What OS are you using? Another thing is many people find that using Linux works better than using Windows, since most Linux distros have fastboot and ADB bundled and it is a little older version.
Hello, thank you very much for your work, just one question, since I'm setting up all of this for a friend and can't try it up for myself.
In the sdk-tools-windows-3859397.zip there's a folder called 'tools' is it the way it should be? Thank you again for your consideration
--------------update
Since no one answered me yet I'm going to add some info:
I did try it and I can't seem to get it to work, where should I open the cmd? And should I actually digit: "adb drivers"? Because the console output is "adb command not recognised".
Thank you again ☺
Alberto.Laurella said:
Hello, thank you very much for your work, just one question, since I'm setting up all of this for a friend and can't try it up for myself.
In the sdk-tools-windows-3859397.zip there's a folder called 'tools' is it the way it should be? Thank you again for your consideration
--------------update
Since no one answered me yet I'm going to add some info:
I did try it and I can't seem to get it to work, where should I open the cmd? And should I actually digit: "adb drivers"? Because the console output is "adb command not recognised".
Thank you again
Click to expand...
Click to collapse
There are instructions for adding the directory of tools to windows (Check Installing adb tools -> on windows) but if you don't want to do something like that, then you could open the command prompt/powershell/terminal in the directory containing all the tools like "adb.exe" or "adb" (on *nix devices) and run all the commands with "./" prefix at the beginning of each adb command like "./adb devices" on *nix devices or if you're using powershell on windows 10, the prefix is not required if you're using cmd.exe (command prompt on windows 7 or older) . In case you wish to flash a file you can either copy paste it into the folder containing "adb.exe" or just "adb" (on *nix devices) or type the full path to the file you wish to use.
hola como les va les comento mi problema
yo intento cargarle el sistema pero como el bootloader no esta desbloqueado no me deja eh intentado desbloquearlo y tampoco me deja no tengo la depuracion usb abilitada ni la opcion de oem ay alguna posibilidad de que se pueda desbloquear el bootloader para reinstalarle el sistema operativo el sistema me lo carga pero antes de cargar con el sistema se reinicia eh intentado de todo ya muchas grasias colegas les habla walter desde argentina
walter19941994 said:
hola como les va les comento mi problema
yo intento cargarle el sistema pero como el bootloader no esta desbloqueado no me deja eh intentado desbloquearlo y tampoco me deja no tengo la depuracion usb abilitada ni la opcion de oem ay alguna posibilidad de que se pueda desbloquear el bootloader para reinstalarle el sistema operativo el sistema me lo carga pero antes de cargar con el sistema se reinicia eh intentado de todo ya muchas grasias colegas les habla walter desde argentina
Click to expand...
Click to collapse
I don't understand Spanish (i think you typed spanish), if you could try to explain it in English that would be great or type simple spanish which translates easily through services like translate.google.com
walter19941994 said:
hola como les va les comento mi problema
yo intento cargarle el sistema pero como el bootloader no esta desbloqueado no me deja eh intentado desbloquearlo y tampoco me deja no tengo la depuracion usb abilitada ni la opcion de oem ay alguna posibilidad de que se pueda desbloquear el bootloader para reinstalarle el sistema operativo el sistema me lo carga pero antes de cargar con el sistema se reinicia eh intentado de todo ya muchas grasias colegas les habla walter desde argentina
Click to expand...
Click to collapse
Hola Walter, comentanos un poco mejor tu problema. El teléfono no inicia? Cómo llegaste a esa situación?
Need help
toxicmender said:
Prerequisites:
ADB (Android Debugging Bridge) tools for your OS (Windows/Linux/Mac)
Windows: https://dl.google.com/android/repository/sdk-tools-windows-3859397.zip
Mac: https://dl.google.com/android/repository/sdk-tools-darwin-3859397.zip
Linux: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip
Custom Recovery Image (TWRP or some other that you prefer):
https://forum.xda-developers.com/devdb/project/?id=11051#downloads
(Official TWRP web hosted version)https://twrp.me/motorola/motorolamotog2015.html
https://dl.twrp.me/osprey
https://eu.dl.twrp.me/osprey
USB Cable to Connect the phone to the computer
The Phone: Moto G 2015 (preferably Fully Charged)
The device drivers (for Windows and Mac): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
A good and active Internet Connection
An active Email address and client to quickly view it.
Installing adb and fastboot
Google hosts zips including only adb and fastboot. You can set these up for use with the instructions below.
On Windows
Download the Windows zip (Full version: https://dl.google.com/android/repository/sdk-tools-windows-3859397.zip)(barebones version: https://dl.google.com/android/repository/platform-tools-latest-windows.zip) from Google.
Extract it somewhere - for example, %USERPROFILE%\adb-fastboot
• On Windows 7/8:
1. From the desktop, right-click My Computer and select Properties
2. In the System Properties window, click on the Advanced tab
3. In the Advanced section, click the Environment Variables button
4. In the Environment Variables window, highlight the Path variable in the Systems Variable section and click the Edit button
5. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• On Windows 10:
1. Open the Start menu, and type “advanced system settings”
2. Select “View advanced system settings”
3. Click on the Advanced tab
4. Open the “Environment Variables” window
5. Select the Path variable under “System Variables” and click the “Edit” button
6. Click the “Edit Text” button
7. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• Install the device drivers linked in prerequisites (or from Motorolla support site), and reboot.
On macOS
Download the macOS zip (full version: https://dl.google.com/android/repository/sdk-tools-darwin-3859397.zip)(Barebones version: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.bash_profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
On Linux
Download the Linux zip (Full version: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip)(Barebones version: https://dl.google.com/android/repository/platform-tools-latest-linux.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
You may also need to set up udev rules: see this repository (https://github.com/M0Rf30/android-udev-rules#installation) for more info.
Setting up adb
To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.
2. Tap on “Build number” seven times.
3. Go back, and select “Developer options”.
4. Scroll down, and check the “Android debugging” entry under “Debugging”.
5. Plug your device into your computer.
6. On the computer, open up a terminal/command prompt and type adb devices.
7. A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”.
Congratulations! adb is now ready to use with your device.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down and Volume Up to scroll and Power to select.
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at Motorola Support (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) to unlock your bootloader, you will need to register at this site with a working/active email to recieve the OEM unlock code.
Note: If your device is not supported by the Motorola Bootloader Unlock
website, you will need to use an alternative bootloader unlock method like
SunShine (http://theroot.ninja/index.html).
Installing a custom recovery using fastboot
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone. This needs to be done again due to resetting of your phone.
3. Download recovery - visit twrp.me to obtain the latest version of Team Win
Recovery Project for your device. Moto G 2015 does have an official TWRP recovery that you can find here: https://twrp.me/motorola/motorolamotog2015.html
4. Connect your device to your PC via USB.
5. Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>" , try running
Code:
fastboot
as root/Administrator.
7. Flash recovery onto your device:
Code:
fastboot flash recovery your_recovery_img.img
This command assumes the recovery image is present in your current working directory (Check using DIR on command prompt or ls command on terminal)
If it isn't you can change your current directory to the directory containing the recovery image or copy/move the recovery image to your current working directory.
8. Now reboot into recovery to verify the installation:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down to scroll to recovery and then use Power to select.
That's all folks. You may now root your phone, or even flash a custom ROM. I suggest getting openGapps for the custom ROM if you wish to use Google play services on the custom ROM.
Popular adb commands
Code:
adb shell
Launches a shell on the device accessed through the terminal on your computer.
Code:
adb push <local> <remote>
Pushes the file <local> to <remote>
Code:
adb pull <remote> [<local>]
Pulls the file <remote> to <local>. If <local> isn’t specified, it will pull to the current folder.
Code:
adb logcat
Allows you to view the device log in real-time. You can use adb logcat -b radio to view radio logs, and adb logcat -C to view logs in colour
Code:
adb install <file>
Installs the given .apk file to your device
<local> refers to location on your computer (like c:\\Users\%USERPROFILE%\adb-fastboot on windows or ~/adb-fastboot on unix based OS), while <remote> refers to location on your android device (like "/sdcard/", without quotes)
Thanks to @acejavelin for helping members troubleshoot problems that they faced
Click to expand...
Click to collapse
I want to unlock the bootloader of Moto g3. But I'm facing some problem
1, OEM unlocking not enabled
2, device in software brick condition
3, can't enter into recovery option ( when it enter into recovery mode it will show no command message for 1/2 sec and turn display off and turn on,same loop again)
https://drive.google.com/file/d/1lPBuEij-Wl1COHMH_5FT0_0VFS6Mfbuq/view?usp=drivesdk
Is there any way to fix this problem???? ?
akhiltj114 said:
I want to unlock the bootloader of Moto g3. But I'm facing some problem
1, OEM unlocking not enabled
2, device in software brick condition
3, can't enter into recovery option ( when it enter into recovery mode it will show no command message for 1/2 sec and turn display off and turn on,same loop again)
https://drive.google.com/file/d/1lPBuEij-Wl1COHMH_5FT0_0VFS6Mfbuq/view?usp=drivesdk
Is there any way to fix this problem???? ?
Click to expand...
Click to collapse
Assuming you tried "fastboot erase userdata"?
Otherwise probably not much you can do... Unlocking the bootloader in this condition is impossible, but it might not matter because it sounds like your eMMC (the internal storage chip) may have failed. It is not replaceable except by mainboard swap.
Bootloader locked and unable to access recovery, not much anyone except Moto can do to help that situation.
Is there any way to check eMMC status (using fastboot command )
akhiltj114 said:
Is there any way to check eMMC status (using fastboot command )
Click to expand...
Click to collapse
No... Fastboot doesn't have anything that in-depth in it. Sorry.
Anyone got an idea why I can't unlock the bootloader with the on the Moto site ?
Moto G3
(bootloader) 3A55840906041441#5A593232323236
(bootloader) 4A4E56004D6F746F4733000000#F708
(bootloader) F4ADF4333F57809EAC2EF3FB1C464B2
(bootloader) AD819#CAD5D20A00000000000000000
(bootloader) 0000000
D:\Incomming\platform-tools-latest-windows\platform-tools>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.CF
(bootloader) product: osprey
(bootloader) board: osprey
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x4
(bootloader) emmc: 8GB SKHynix REV=07 PRV=08 TYPE=57
(bootloader) ram: 1024MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY22226JNV
(bootloader) cid: 0x0007
(bootloader) channelid: 0x41
(bootloader) uid: CAD5D20A00000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxx
(bootloader) meid:
(bootloader) date: 07-11-2015
(bootloader) sku: XT1541
(bootloader) battid: SNN5959A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed May 23 20:25:40 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_reteu_2gb/osprey_u
(bootloader) ro.build.fingerprint[1]: 2:6.0.1/MPIS24.107-55-2-17/19:user
(bootloader) ro.build.fingerprint[2]: /release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.226.17.osprey_ret
(bootloader) ro.build.version.full[1]: eu_2gb.reteu.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband[0]: M8916_2020632.44.03.21.54.01R OSPREY_E
(bootloader) version-baseband[1]: MEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-g2e9678a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld83) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Apr 6 10:50:21 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-V80.CF-0-g7abea31
(bootloader) rpm.git: git=MBM-NG-V80.CF-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.CF-0-gf07dc55
(bootloader) hyp.git: git=MBM-NG-V80.CF-0-gf07dc55
(bootloader) aboot.git: git=MBM-NG-V80.CF-0-g8bfe213
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeSmiley Very HappyDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeSmiley TongueadA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-typeSmiley TongueadB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeSmiley Tongueersist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-typeSmiley TongueadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-typeSmiley Surprisedem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:customize: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeSmiley Very HappyDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-sizeSmiley TongueadA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-sizeSmiley TongueadB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000300000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-sizeSmiley Tongueersist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001019000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-sizeSmiley TongueadC: 0x000000000087e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-sizeSmiley Surprisedem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:system: 0x0000000091000000
(bootloader) partition-size:userdata: 0x0000000121fe0000
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.373s
cid: 0x0007
Should work.
freshmike said:
Anyone got an idea why I can't unlock the bootloader with the on the Moto site ?
Moto G3
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxx
(bootloader) meid:
(bootloader) date: 07-11-2015
(bootloader) sku: XT1541
(
Should work.
Click to expand...
Click to collapse
Nope, looks fine. If you can't get the token from the site, you have to go to Moto. Unfortunately, there is no other option as there is nothing we can do. Your bootloader state is 0, and I assume you have OEM unlocking set in Dev Options and are entering the key correctly. There is nothing anyone can do to assist you except Moto.

i need downgrade u ultra dual sim for oreo to noguet

Code:
Send: fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_ocedugl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) version-main: 1.64.401.10
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF20000
(bootloader) cid: HTC__A07
all:
finished. total time: 0.006s
htc_fastboot finished. total time: 0.106s
i need stock rom or ruu.
Try this RUU
https://www.androidfilehost.com/?fid=3700668719832236904
thanks ur reply
minhnewpro said:
Try this RUU
https://www.androidfilehost.com/?fid=3700668719832236904
Click to expand...
Click to collapse
i trying it now.
please help me imei null.
I'm a little weak to speak English. Sorry for my english.
i installed this rom Link. 2PZFIMG_OCEAN_[email protected]70515_56.34_release_507305_signed_2_4.zip than after setup i locked BL. imei null.
https://androidfilehost.com/?fid=962187416754474071 i install this room. again imei null.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>mke2fs -t ext4 /dev/block/bootdevice/by-name/persist
'mke2fs' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
i hate this mistake.
Adream09 said:
i hate this mistake.
Click to expand...
Click to collapse
10. After flashing, your device can boot into Android but no signal or IMEI received, dont worry, continue these steps
11. Reboot into download mode, reflash TWRP, then boot to TWRP
12. At cmd windows, type
Code:
adb devices
adb shell
mke2fs -t ext4 /dev/block/bootdevice/by-name/persist
13. Reboot device to check if IMEI received
14. If IMEI received, you should reflash stock recovery from RUU.zip, but reflash the RUU is recommended.
If not, try to format the persist partition manually again (step 12)
15. Done
thanks ur reply
minhnewpro said:
10. After flashing, your device can boot into Android but no signal or IMEI received, dont worry, continue these steps
11. Reboot into download mode, reflash TWRP, then boot to TWRP
12. At cmd windows, type
Code:
adb devices
adb shell
mke2fs -t ext4 /dev/block/bootdevice/by-name/persist
13. Reboot device to check if IMEI received
14. If IMEI received, you should reflash stock recovery from RUU.zip, but reflash the RUU is recommended.
If not, try to format the persist partition manually again (step 12)
15. Done
Click to expand...
Click to collapse
thanks bro

Categories

Resources