Database Users

[Q] I can't go into Recovery mode. Why?

I have the following problem, I can not go into recovery mode. I know how to do that.I have access only in fastboot menu.when i try to enter from fastboot menu to recovery mode i don't have connection with the PC , because the problem is DRIVERS to start the second step "step2-windows.bat" for rooting.
I HAVE GOLD CARD !!!!!! .I had all drivers before this problem drivers was added to the PC and the phone WAS rooted.
The problem is not in my Windows i try those step on ,Windows7, windows xp ,Linux Ubuntu 10.4. And errors are the same "unknown device" and is impossible to install drivers to ROOT the phone.
Before the phone can not detect the SD card.The problem is fixed now is working .Now the phone is with original ROM and is not rooted.May be I have to flash new bootloader or new recovery.img I don't know.
My cable is not damaged.
the reason that I want to enter in recovery mode is that i want to root the phone again.
!!!!!!!!!!!WHO CAN HELLP ME !!!!!!!!!!!!!
sorry for my bad english

Strange.......... how it could be:
release your battery, push the power to release residual power , maybe 1 minute, in sert the battery and try go to recovery again

BesFen said:
Strange.......... how it could be:
release your battery, push the power to release residual power , maybe 1 minute, in sert the battery and try go to recovery again
Click to expand...
Click to collapse
The same f**** message "device not recognized". And it start to search Drivers on windows 7 x86 (fresh installation before 30 min.).
"Android 1.0, Qualcomm CDMA technologies MSM " - searching for drivers .. and the message "device not recognized" or "unknown device"

problem occurs when app2sd install and replace all programs to sd card.I enter into recovery mode and i wipe all options.After reboot my sd card was unmounted ........
may be this will be helpful

Follow this:
http://android.modaco.com/content/htc-legend-legend-modaco-com/309961/usb-brick-rickrolled-b0rked-fixed/

I've had a similar problem during the rooting-process of my legend
I have Win7 X86 and it also couldn't find any drivers for the legend.
Then I installed the HTC Sync application found on the HTC-Homepage
So i would suggest that you do the same

It is not an usb driver issue.
The phone acting as different device depending of its mode normal/fastboot/recovery/usb mount etc
Boot to bootloader select fastboot
run on your computer "fastboot oem boot"
if you have any of thoose =1 you have to alter it to 0
where the bold down is of importance
Normal output is:
INFOTAG xxxxx
INFOCID is HTC__***
INFOserial numer: *********
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length = xxx
INFOactive commandline:
board_legend.disable_uart3=0
board_legend.usb_h2w_sw=0
board_legend.disable_sdcard=0
diag.enabled=0
board_legend.debug_uart=0
smisize=0
userdata_sel=0
androidboot.emmc=false
androidboot.baseband=7.08.35.21 (or other)
andriodboot.cid=HTC_XXX (different depending on serial )
androidboot.carrier=HTX-
androidboot.mid=
androidboot.keycaps=querty
androidboot.mode=normal
androidboot.serialno=xxxxxxxx
androidboot.bootloader=0.43.00001
no_console_suspend=1
console=null
aArm_partion[0].name=misc
aArm_partion[1].name=recovery
aArm_partion[2].name=boot
aArm_partion[3].name=system
aArm_partion[4].name=cache
aArm_partion[5].name=userdata
partition number=6
Valid partition num=6
mpu_nand_acpu_rw 8F2 1000

result is :
Code:
C:\android SDK\tools>fastboot oem disable_uart3=0
... INFO[ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android SDK\tools>fastboot oem usb_h2w_sw=0
... INFO[ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.016s
C:\android SDK\tools>fastboot oem boot
... INFOsetup_tag addr=0x60000100 cmdline add=0x9D
078D14
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x22F00
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__032
INFOsetting->cid::HTC__032
INFOserial number: HT03YNX02877
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =446
INFOactive commandline: board_legend.disable_uart3=1 board_legen
INFOd.usb_h2w_sw=1 board_legend.disable_sdcard=0 diag.enabled=0
INFOboard_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.baseband=7.05.35.26L androidboot.
INFOcid=HTC__032 androidboot.carrier=HTC-EastEurope androidboot.
INFOmid=PB7610000 androidboot.keycaps=qwerty androidboot.mode=no
INFOrmal androidboot.serialno=HT03YNX02877 androidboot.bootloade
INFOr=0.43.0001 no_console_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw 8F2 1000
FAILED (status read failed (Too many links))
finished. total time: 0.874s
the phone must be rooted main is not this is the problem and what this mean
FAILED (status read failed (Too many links))

this is your problem:
board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1
The FAIL string at bottom is normal.

this is your problem:
board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1
The FAIL string at bottom is normal.
So you tell us that you have succeed with unrooting and lock usbcontroller.
Umm, sounds like and bad combination.
I had the uart3=1 probleb but still rooted and could insert new mtd0.img
have you tested to replace this two files?
http://www.shadowchild.nl/mtd0legend.img
http://www.shadowchild.nl/flash_image
download to your sdcard direct or with other usb/sdcard writer.
install terminal
open run
su
to check if it it still rooted
if so
chmod 755 /data/flash_image
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0legend.img > /data/mtd0.img
/data/flash_image misc /data/mtd0.img
and reboot

I assume you updated your legend to rom >2.03 (or any above 2.xx) you will have to downgrade
http://forum.xda-developers.com/showthread.php?t=725430
when you downgrade, root the legend again (fastboot usb > step1) then recovery mode >> step2
should work, worked for me tho. If not do step1 few times and try step2 again

snakehult said:
this is your problem:
Board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1
the fail string at bottom is normal.
So you tell us that you have succeed with unrooting and lock usbcontroller.
Umm, sounds like and bad combination.
I had the uart3=1 probleb but still rooted and could insert new mtd0.img
have you tested to replace this two files?
http://www.shadowchild.nl/mtd0legend.img
http://www.shadowchild.nl/flash_image
download to your sdcard direct or with other usb/sdcard writer.
Install terminal
open run
su
to check if it it still rooted
if so
chmod 755 /data/flash_image
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0legend.img > /data/mtd0.img
/data/flash_image misc /data/mtd0.img
and reboot
Click to expand...
Click to collapse
thank you !!!

no way.....its not working showing
C:\sdk\tools>chmod 755 /data/flash_image
'chmod' is not recognized as an internal or external command,
operable program or batch file.
C:\sdk\tools>cat /sdcard/flash_image > /data/flash_image
The system cannot find the path specified.

no no
you most run that on your phone.
install terminal emulator or similar
{
"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"
}

i can't download......... showing insufficient storage........i even can't install application through 91pc suite for android..........i need help....

how do i type this in terminal all at once or sentence by sentence?

do exactly what he does :
http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/
after unbricking your usb , install a stock rom not a custom coz you need a clean system.img.
If you don't do that, usb bricking will come again after flashing with a custom rom...
You can install a new stock rom ( like 2.03 etc... ) and use the thread "how to downgrade to 1.31" and root your legend again.
Another solution :
If the rom is not rooted and you can't follow unbrick instructions try this ( it's what i've done but not sure if result will be the same for you... ) :
Go to recovery mode ( power + volume down ) , select fastboot and try step 1 of rooting process, that will push 1.31 rom + some necessary tool to root the rom.
if all succeded , you will have a 1.31 rom apparently not rooted... but ! yes but ! after installing "connectbot" from market and select "local" and type 2 time "su" i got root access ! if not try step 1 of rooting process under fastboot mode.
If all is ok and you have ( like me ) root acces ( after typing 2 times "su" you will past from $ to # at the beginning of the line... ) , follow unbrink process .
Code:
if your phone can't even see the memory card, enable first with:
fastboot oem enableqxdm 0
Do the above step in Recovery mode.
Once the memory card is visible, transfer the files "flash_image" and "mtd0.img" to the memory card
howevor is possible.
Restart the phone, and install connectbot from the market.
Open connectbot, and through terminal (local) issue the following commands:
su [B][U](2 times)[/U][/B]
cat /sdcard/flash_image > /data/flash_image "then press enter"
cat /sdcard/mtd0.img > /data/mtd0.img "then press enter"
chmod 755 /data/flash_image "then press enter"
[B][U]and to finish process type the following command 2 times[/U] :[/B]
/data/flash_image misc /data/mtd0.img "then press enter"
It will give you 2 errors, on the last command, but ignore it and restart the phone
It should be fixed.
after that i had upgraded to an official stock rom to get back a clean system.img and boot.img. oh yes... phone again unrooted... ok... downgrade to 1.31 and root again

Isn't there a noob friendly way to unbrick.i couldn't possibly do all of that.
Sent from my HTC Legend using XDA App

THANK YOU!!!!
My phone lost the ability to read SD-cards and this thread helped me tremendously. I was just about to sell it or go and buy a new one or something.
Hugs to all!

heelp me
Very very much please help me fix my htc my legend. I do not see sd card, I can not root them anymore, can not find drivers. I do only step 1, you want to put up two do not communicate with the PC. Do not know much about Android, where I do not know the commands to be written, please help me. TeamViewer eventually get through to my PC. My address is [email protected] messenger. I pray a lot.

[RUU]M9+ RUU file

“ht”tp:/“/pan.baidu.c”o“m/s/1o6zHTpC 密码（psw）: y571
Now , just has 3 file NAME :
ZhongZhuangbao_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_431201.ZIP
ZhongZhuangbao_HTCCN_CHS_2_1.08.1405.6_Radio_1.1506V24P14.1605.0421__431815_DownLoadModen.zip
ZhongZhuangbao_HTCCN_CHS_2_1.08.1405.6_Radio_1.1506V24P14.1605.0421__431815.zip
I upload speed is only 10-45KB, all the M9+ruu add up to have 50GB.
Now I only upload 3 most people need.
If other people need more, I will upload more.
2GB file takes a week
I've got a question
Publish all the NEWEST RUU What damage to HTC？I don't want to hurt the interests of the HTC company.

Good job, guy!!
TW(709),please!
Thanks!
Sent from my HTC_M9pw using XDA Free mobile app

UAE RUU
Do you have the update ruu for the UAE version .? thnx in advance

Thanks for share it
But,it's only china?

thank you
it is only in chines . can you try to upload it in another website please ?

Thank you so much!!! Could you share HK(708)? =)

I'll upload some too to mega.nz when I'll get back from vacation

0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this on S-On, you must have your device Relocked (on S-Off you don't need to relock) and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800

tbalden said:
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this you must have your device Relocked and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800
Click to expand...
Click to collapse
Hi tbalden,
Even the MD5checksum is verified, still can't find the system.img in the rom.zip
the size in the zip file also seems not right.
May you check it?
{
"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"
}

you need to use a linux, there latest ruuveal, 'ruuveal -D xy.zip' to properly unzip all with system image parts as these are large zips (special format). Then you will have to unify the system img parts with Hima_ImgTool from m9 forum threads. Then you can mount and/or browse them as EXT4 filesystems.
Also, if you are thinking about restoring to stock, it might be better to just flash the whole zip as it's intended by HTC with fastboot.

tbalden said:
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this you must have your device Relocked and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800
Click to expand...
Click to collapse
thanks for the signed RUUs. I'm downloading now I will try them later. I have a question. how can I install different region RUUs? Do I have to change MID like in htc one m8 or m9? If yes, where can I find mid for specific regions/?
---------- Post added at 02:01 AM ---------- Previous post was at 01:22 AM ----------
load_file: could not allocate -2053247557 bytes
error: cannot load '0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip'
I'm getting this error. anyone explain plz/

jura.m said:
thanks for the signed RUUs. I'm downloading now I will try them later. I have a question. how can I install different region RUUs? Do I have to change MID like in htc one m8 or m9? If yes, where can I find mid for specific regions/?
---------- Post added at 02:01 AM ---------- Previous post was at 01:22 AM ----------
load_file: could not allocate -2053247557 bytes
error: cannot load '0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip'
I'm getting this error. anyone explain plz/
Click to expand...
Click to collapse
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.

tbalden said:
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.
Click to expand...
Click to collapse
Code:
D:\M9pw>htc_fastboot oem rebootRUU
...
OKAY [ 0.000s]
finished. total time: 0.000s
htc_fastboot finished. total time: 0.173s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.696s]
writing 'zip'...
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.244s
htc_fastboot finished. total time: 25.291s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.575s]
writing 'zip'...
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
[COLOR="Red"](bootloader) ERR ZIP signature checking failed...[/COLOR]
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.481s
htc_fastboot finished. total time: 30.171s
D:\M9pw>fastboot reboot
rebooting...
finished. total time: -0.000s
Now,try to copy the file to SD card.

yvtc75 said:
Code:
D:\M9pw>htc_fastboot oem rebootRUU
...
OKAY [ 0.000s]
finished. total time: 0.000s
htc_fastboot finished. total time: 0.173s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.696s]
writing 'zip'...
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.244s
htc_fastboot finished. total time: 25.291s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.575s]
writing 'zip'...
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
[COLOR="Red"](bootloader) ERR ZIP signature checking failed...[/COLOR]
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.481s
htc_fastboot finished. total time: 30.171s
D:\M9pw>fastboot reboot
rebooting...
finished. total time: -0.000s
Now,try to copy the file to SD card.
Click to expand...
Click to collapse
Do you have the bootloader on higher version than the zip? I think you can't do that. You need the same main version or lower on the phone boot loader (1.08) to flash it. I used the Chinese zip a few times and it went well but I haven't updated the bootloader over 1.08
http://www.xda-developers.com/misctool-gives-htc-users-power-to-readwrite-main-version/

tbalden said:
Do you have the bootloader on higher version than the zip? I think you can't do that. You need the same main version or lower of phone boot loader (1.08) to flash it. I used the Chinese zip a few times and it went well but I haven't updated the bootloader over 1.08
http://www.xda-developers.com/misctool-gives-htc-users-power-to-readwrite-main-version/
Click to expand...
Click to collapse
I misunderstood the post.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
OK,thanks tbalden.
I know the issue. I forgot this main version I ever used in the era of One X.
I must defraud the RUU of main version in the android-info.
Thanks again!! :good:

About modifying main version: I think that will only work with s-off, or maybe even there not either. You need to modify the main version of your phone, not the zip, because modifying the zip will make the signature invalid on it and it won't flash.

tbalden said:
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.
Click to expand...
Click to collapse
thanks man. I figured that out after I googled that issue I was getting. I downloaded htc fastboot and done that. I got cid error when I tried to install 707 and 709 RUUs. My device was already s-offed and I changed cid to supercid 11111111. after that I managed to install 707 version. thanks for your help.

yvtc75 said:
I misunderstood the post.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?................SuSam
Click to expand...
Click to collapse
Wait for RUU 1.81 release, and now my phone device is 1.61, so 1.08 version is too low, can not be used unless the s-off ~ :crying:

玻璃施工 said:
Wait for RUU 1.81 release, and now my phone device is 1.61, so 1.08 version is too low, can not be used unless the s-off ~ :crying:
Click to expand...
Click to collapse
Wow.......... cool name!! :good:
Yep, wait for the newest RUU.
Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software.

yvtc75 said:
Wow.......... cool name!! :good:
Yep, wait for the newest RUU.........Susan
Click to expand...
Click to collapse
mm... Their ROM is the only antidote to save M9+ (take the Low stool

[Fastboot][Falcon][Peregrine] Hidden Motorola Fastboot Commands

Using this Tutorial, I found the following Hidden Motorola Fastboot Commands contained in the Bootloader (aboot) for Falcon | Peregrine. Use these commands at your own risk. I will update thread as people report back what each command does.
fastboot oem backlight [Options: on | off | <number>]
fastboot oem bp-tools-on (Re-enables access to 'bp-tools')
fastboot oem bp-tools-off (Disables access to 'bp-tools')
fastboot oem cid_prov_req
fastboot oem config [Additional options exist but unknown]
fastboot oem config protect <name> (mark utag as read-only)
fastboot oem config unprotect <name> (unmark utag as read-only)
fastboot oem display [Options: on | off | info]
fastboot oem fb_mode_set (fastboot boot-cycle mode; return to the fastboot menu if Android fails)
fastboot oem fb_mode_clear (Exit fastboot boot-cycle mode)
fastboot oem help (Lists some, but not all, oem commands)
fastboot oem off-mode-charge (Enable or disable display electrostatic discharge detection and recovery in kernel display driver) (Options: false, off, no, disable, 0: Don't use charger mode | true, on, yes, enable, 1 : Default (charger))
fastboot oem partition (Options: <none> (lists all partitions) | <name> (list named partition) | dump <name> [<offset> [size] | md5 <name> [<offset> [size]])
fastboot oem qcom-on (Re-enables access to 'qcom' mode)
fastboot oem qcom-off (Disables access to 'qcom' mode)
fastboot oem regex [Additional options exist but unknown]
fastboot oem read_sv
fastboot oem ramdump enable (Enables ramdumping)
fastboot oem ramdump pull (Retrieve ramdump)
fastboot oem ramdump clear (Discard 'current' ram content?)
fastboot oem wptest [Additional options exist but unknown]​

Reading about the "Pork Explosion" critical vulnerability; I noticed the following OEM command mentioned:
fastboot oem writeimei 1234567899876543​
This could be a way for those that have previously wiped IMEI to restore it fully, not just partially as suggested by this guide.

lost101 said:
Reading about the "Pork Explosion" critical vulnerability; I noticed the following OEM command mentioned:
fastboot oem writeimei 1234567899876543​
Click to expand...
Click to collapse
Unlikely to work since our bootloader doesn't contain the string "writeimei". I think that was just a random example.

off mode charge doesn't work (Lineage 16):
{
"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"
}

Great post! I've been using some of them on various Motorola to repair FRP and reset the mode afterwards.

Has anyone found a Motorola model with a boot loader that supports IMEI write commands for IMEI repairing use?

Do you know the command in fastboot to enable factory mode? And then also possibly a command to rewrite carrier value? So that I can change carriers?

bootloader flash error

Hi guys...
I has flash stock rom in my xt1626 and now I have a erro while I flash bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.411s]
finished. total time: 0.536s
And now, when my phone turn on. I has lost my network activity and my digital tv.
I'm lost with I have to do.
Someone knows how I solve this?

Which rom did you flash? Sounds you've flashed not a rom for xt1626!

this one: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I always flash this. And never had a single problem.
There's not specific rom stock for xt1626. I never found.
My cel phone recognize like xt1626, sim 1 is working, but shows only "no service". sim 2 disappeared and digital tv app too.
{
"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"
}

What is status of both IMEI ? Are those correct with sticker (on backside / box) ?
Have you flashed anything else with or before this ROM ?

IMEI 1 is ok. IMEI 2 not exist cause sim 2 is not working.
I don't know what's happened. But mobile radio doesn't turning on.

Xperia Z5 Lineage OS 17.1(Android 10) GAPPS issue [FIX]

Hi guys so recently i decided to change my Recovery and Firmware on my Xperia Z5 dual (E6683) i decided to flash Lineage OS 17.1 UNOFFICIAL-SUMIRE after that i decided to flash both GAPPS and Magisk But theres an issue "PERMISSION ISSUE" on GAPPS andriod setup i did manage to get it working via these steps hope this helps you
Requirements:
Windows/Mac with ADB installed
Phone (guessing you have TWRP and Lineage installed)
USB cable (obviously you will need this)
ADB SHELL COMMAND FOR SYSTEM UI HAS STOPPED WORKING/ANDRIOD SETUP HAS STOPPED WORKING (LINEAGE OS 17.1 ANDRIOD 10 Q)
FIX:
1ST INSTALL LINEAGE OS THROUGH TWRP RECOVERY (DO NOT INSTALL GAPPS FIRST!)
{
"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"
}
2ND REBOOT DEVICE
3RD SETUP THE DEVICE AS NORMAL THEN AFTER THAT GO TO SETTING>ABOUT PHONE TAP BASEBAND VERSION 4 TIMES TO UNLOCK DEVELOPER MODE
4TH GO TO SETTINGS>SYSTEM>DEVELOPER OPTIONS THEN FIND USB DEBUGGING ENABLE IT
5TH REBOOT DEVICE TO RECOVERY
6TH INSTALL GAPPS
7TH REBOOT TO SYSTEM
8TH OPEN CMD AND TYPE cd C:\Users\(username)\(file directory)\adb CLICK ENTER
9TH TYPE COMMANDS DOWN BELOW....
STAT REPORT:adb shell dumpsys package com.google.android.setupwizard
FIX CMD
adb shell pm grant com.google.android.setupwizard android.permission.CALL_PHONE
adb shell pm grant com.google.android.setupwizard android.permission.GET_ACCOUNTS
adb shell pm grant com.google.android.setupwizard android.permission.PROCESS_OUTGOING_CALLS
adb shell pm grant com.google.android.setupwizard android.permission.READ_CONTACTS
adb shell pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
adb shell pm grant com.google.android.setupwizard android.permission.WRITE_CONTACTS
adb shell pm grant com.google.android.setupwizard android.permission.READ_OWNER_DATA
adb shell pm grant com.google.android.setupwizard android.permission.WRITE_OWNER_DATA
NOTE IGNORE ERROR: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.READ_OWNER_DATA
AFTER SUCCESSFUL COMMANDS CHECK STATUS BAR FOR THE FINISH YOUR SETUP DEVICE AND THERE YOU GO THE SETUP SHOULD GO SMOOTH FROM HERE )