Related
Hi,
I'm creating a new thread because I did not find anything here related to that specific topic.
I would like to backup my radio ROM before flashing a WWE one. My intent is to test the WWE and if anything goes wrong with e.g the simlock I'll restore the original one.
Some directions : all /dev/block/mtdblock* are not used (appart from system, cache & data) should it be there ? maybe not using yaffs2 ?
Any enlightening suggestions appreciated !
Cheers
gelim said:
Hi,
I'm creating a new thread because I did not find anything here related to that specific topic.
I would like to backup my radio ROM before flashing a WWE one. My intent is to test the WWE and if anything goes wrong with e.g the simlock I'll restore the original one.
Any enlightening suggestions appreciated !
Cheers
Click to expand...
Click to collapse
you can find your own radio image inside of the wwe.. nowadays there are 2 radio for tattoo: orange and stock.
let's say I'm not trusting the WWE content downloaded via an untrusted source ?
Is there really no technical way to achieve that when being root on the phone ?
Thanks
gelim said:
let's say I'm not trusting the WWE content downloaded via an untrusted source ?
Is there really no technical way to achieve that when being root on the phone ?
Thanks
Click to expand...
Click to collapse
don't know, but to achieve your own radio.img from the phone you shoud dump it from the internal memory. Maybe a full backup from recovery saves that image.
> you shoud dump it from the internal memory
yes but it's unclear how to do it. There are several kind of memory in the phone... My bet goes on the NAND one but ATM I don't know how to access the first mtdblocks)
# mount -t yaffs2 -o ro /dev/block/mtdblock0 /sdcard/radio
mount: mounting /dev/block/mtdblock0 on /sdcard/radio failed: Invalid argument
Click to expand...
Click to collapse
(same for 1 & 2)
some kernel log to illustrate that :
[ 5261.980407] yaffs: Attempting MTD mount on 31.0, "mtdblock0"
[ 5261.980926] yaffs: NAND geometry problems: chunk size 2048, type is yaffs2, inbandTags 0
[ 5266.192199] yaffs: dev is 32505856 name is "mtdblock0"
[ 5266.192474] yaffs: passed flags ""
Click to expand...
Click to collapse
> Maybe a full backup from recovery saves that image.
No full backup from recovery (using amora's one) doesn't dump radio.img. That's why I'm asking here.
When you open an official RUU from HTC, all .img are extracted on temp folder. So you can take it from here.
Actually my problems changed a little bit after doing the mount yaffs2 whitout success I issued a reboot from adb.
From now on, my Tattoo won't pass the (vibrate)Tattoo boot logo. I can't go into recovery either (should be just after the Tattoo logo displaying). The only functionnal thing is the fastboot menu and doing a fastboot flash boot boot.img (got that from the RUU) I'm left with the classis FAILED (remote: not allow) thing.
I think I'm doomed and I bricked that little piece of hardware :-(
applying an official RUU should unbrick it
it only needs fastboot usb mode
Yes, should.
potattoo: there is a CID check on this device, it needs to be bypassed using the Goldcard technique AFAIK.
Another protection is hboot has S-ON (signature verification) so I'm out of luck with the manual fastboot flash or update (required some *.sig apparently)
I did an RUU flash from Windows XP (inside a Virtualbox) it managed to reboot the phone (I wasn't able to do that with fastboot reboot !) and timeout on the "waiting for bootloader...". During that time the phone is frozen with the HTC logo.
UPDATE: on a physical windows it's better, the RUU WWE cleans userdata, and then tries to flash the zipped ROM... until it fails. I can now reproduce this behavior manually with fastboot.exe. Here are the log messages :
c:\fastboot>fastboot flash zip rom.zip
sending 'zip' (88968 KB)
...
OKAY [ 14.052s]
writing 'zip'...
INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 41.400s
Click to expand...
Click to collapse
Let's try an oem boot to see what it could say :
c:\fastboot>fastboot oem boot
...
INFO[ERR] partition_read::Failed to read page
INFO22912 or it is empy
INFOsetup_tag addr=0xA0000100 cmdline add=0x8D05E538
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x1
INFOTAG:skuid 0x1FC04
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__247
INFOsetting.cid::HTC__247
INFOserial number: HT9BRLG00XXX
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =413
INFOactive commandline: board_bahamas.disable_uart3=0 board_baha
INFOmas.usb_h2w_sw=0 board_bahamas.disable_sdcard=0 diag.enabled
INFO=0 board_bahamas.debug_uart=0 smisize=0 androidboot.baseban
INFOd=3.35.07.20 androidboot.cid=HTC__247 androidboot.carrier=HT
INFOC-FRA-Bouygues androidboot.mid=CLIC10000 androidboot.keycaps
INFO=qwerty androidboot.mode=normal androidboot.serialno=HT9BRLG
INFO00145 androidboot.bootloader=0.52.0001 no_console_suspend=1
INFOconsole=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
INFO0
INFO0
INFOXXXXXXX
INFOXXXXXXX
INFOXXXXXXX
INFOXXXX
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
FAILED (status read failed (Too many links))
finished. total time: 0.657s
C:\fastboot>
Click to expand...
Click to collapse
(I intentionnaly blanked by 'XX'ing some numbers thinking they are not relevant to the analysis)
The "FAILED (remote: 42 custom id check fail)" message when flashing shows clearly that the Goldcard I did following "[HOWTO] Create a GoldCard - Bypassing the RUU/SPL CID check to Root/Downgrade" topic is not recognized by HBOOT. Why ?
I tried as well not reversing the CID (as seen on another site) and doing the online generation again. Same problem : CID check FAILS miserably.
Questions that arise are :
1- what is the difference between the CID "HTC__247" seen in the boot log and the big alpha-numeric chain I got doing an "adb shell cat $path-to-mmc-cid" ?
2- does the CID change by mounting the sdcard on another android device ?
I'm pretty conscious we're derivating from the initial topic of this thread... but thanks for the help anyway.
Okay, I got it solved. Feeling much much better.
The CID reversing was clumsy so my goldcard was not correct. I wiped the card : did a mkfs.vfat -F 32 -S 4096 /dev/sdb1.
Tried that site for CID manipulation http://hexrev.soaa.me/, generated the goldcard.img again via http://psas.revskills.de/?q=goldcard.
dd if=golcard.img of=/dev/sdb.
Guess what, now CID check passes successfuly.
Just for the record here is a successful fastboot flashing log
(yes now I switch to a windows 7 for the fastboot step, it's of course not mandatory, I could have done everything from a linux...)
c:\fastboot>fastboot flash zip rom.zip
sending 'zip' (88968 KB)... OKAY [ 14.695s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,51
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,50
INFO[RUU]WP,boot,100
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,6
INFO[RUU]UZ,radio,14
INFO[RUU]UZ,radio,19
INFO[RUU]UZ,radio,24
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,38
INFO[RUU]UZ,radio,43
INFO[RUU]UZ,radio,48
INFO[RUU]UZ,radio,53
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,67
INFO[RUU]UZ,radio,76
INFO[RUU]UZ,radio,81
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,91
INFO[RUU]UZ,radio,96
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,7
INFO[RUU]WP,radio,12
INFO[RUU]WP,radio,17
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,31
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,41
INFO[RUU]WP,radio,46
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,58
INFO[RUU]WP,radio,63
INFO[RUU]WP,radio,68
INFO[RUU]WP,radio,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,45
INFO[RUU]UZ,recovery,87
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,44
INFO[RUU]WP,recovery,89
INFO[RUU]WP,recovery,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,2
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,8
INFO[RUU]UZ,system,11
INFO[RUU]UZ,system,14
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,19
INFO[RUU]UZ,system,22
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,28
INFO[RUU]UZ,system,31
INFO[RUU]UZ,system,34
INFO[RUU]UZ,system,36
INFO[RUU]UZ,system,39
INFO[RUU]UZ,system,42
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,48
INFO[RUU]UZ,system,51
INFO[RUU]WP,system,0
INFO[RUU]WP,system,2
INFO[RUU]WP,system,5
INFO[RUU]WP,system,8
INFO[RUU]WP,system,11
INFO[RUU]WP,system,14
INFO[RUU]WP,system,16
INFO[RUU]WP,system,19
INFO[RUU]WP,system,22
INFO[RUU]WP,system,25
INFO[RUU]WP,system,28
INFO[RUU]WP,system,31
INFO[RUU]WP,system,34
INFO[RUU]WP,system,36
INFO[RUU]WP,system,39
INFO[RUU]WP,system,42
INFO[RUU]WP,system,45
INFO[RUU]WP,system,48
INFO[RUU]WP,system,51
INFO[RUU]UZ,system,51
INFO[RUU]UZ,system,53
INFO[RUU]UZ,system,56
INFO[RUU]UZ,system,59
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,65
INFO[RUU]UZ,system,68
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,74
INFO[RUU]UZ,system,76
INFO[RUU]UZ,system,79
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,88
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,97
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,51
INFO[RUU]WP,system,53
INFO[RUU]WP,system,56
INFO[RUU]WP,system,59
INFO[RUU]WP,system,62
INFO[RUU]WP,system,65
INFO[RUU]WP,system,68
INFO[RUU]WP,system,71
INFO[RUU]WP,system,74
INFO[RUU]WP,system,76
INFO[RUU]WP,system,79
INFO[RUU]WP,system,82
INFO[RUU]WP,system,85
INFO[RUU]WP,system,88
INFO[RUU]WP,system,91
INFO[RUU]WP,system,94
INFO[RUU]WP,system,97
INFO[RUU]WP,system,100
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
OKAY [132.319s]
finished. total time: 147.015s
c:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.031s
Click to expand...
Click to collapse
Here we go for the NAND restore (I of course did a NAND backup before all the fudging)
Celebration time
Thanks for the support.
C:\android\tools>fastboot oem boot
< waiting for device >
... 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: HT07VNX01365
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =446
INFOactive commandline: board_legend.disable_uart3=0 board_legen
INFOd.usb_h2w_sw=0 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=HT07VNX01365 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.875s
what can i do ??????
Hi man ! Would be nice if you edit your post in order to explain seriously your problem.
Could be useful to know what ROM you are using, what you did before your phone went in trouble...
Is it a bootloop ? Did you try to flash something ? are you rooted ?
Without the minimum to know, people won't be able to help you. I don't know how to read a logcat, but I don't think every answers are in it !
Plus some courtesy is required on this forum, like on every forum... you just throw us a log...
The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
On the device ViperOne running 3.5.0 (4.3)
Now to the problem:
Flashing a recovery is performed, also displayed as OK, but it remains the old (TWRP 2.6.3.3)
Bootloader not lock possible:
(bootloader) Lock successfully ...
(boot loader) mipi display off
(boot loader) mipi_dsi_cmds_tx_ext
(boot loader) pm8921_vreg_disable function, vreg_id = 38
(boot loader) pm8921_vreg_disable function, vreg_id = 1
(boot loader) TZ_HTC_SVC_DISABLE ret = 534 642 044 (0x1FDDFD7C)
(boot loader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.139s
Flashing via sideload possible, unfortunately, according to Rome, it passes through or terminates. After the restart, but is ancient Rome it.
Getvar all the following shows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3893mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you
Fooox1 said:
The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you
Click to expand...
Click to collapse
So if I understand correctly, you don't like the fact that firmware version not showing up; so I guess you have a couple of options:
1- (recommended in my opinion) get s-off using rumrunner
2- download this OTA: http://www.htc1guru.com/dld/ota_m7_..._p_release_325133_signedlqk8p6c09r7kmir2-zip/
and extract the "firmware.zip" inside, then flash that in fastboot ruu mode (TWICE in a row)
(you may need to relock bootloader for that)
Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.
Fooox1 said:
Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.
Click to expand...
Click to collapse
rumrunner should work just fine, but you're not on 4.3 (firmware); you're hboot 1.54 would imply that you are running a 2.24 firmware, so you need a ROOTED 2.24 ROM with unsecured kernel; try this one: oops, looks like mega is down at the moment
find a 2.24 based ROM, rooted, with unsecured kernel, and rumrunner should work fine. maybe try Maximus 10 or 11: http://llabtoofer.com/category/devices/htc-one/page/2/
However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.
Fooox1 said:
However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.
Click to expand...
Click to collapse
1- I understand your current ROM is 4.3, but that has nothing to do with firmware; firmware is <empty>, but hboot is 1.54, so it implies a 2.24 ROM.
2- to get rumrunner to work, you will need a 2.24 RUM
3- can you please boot to bootloader screen and make sure it says UNLOCKED (a screenshot would be nice )
So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.
Fooox1 said:
So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.
Click to expand...
Click to collapse
keep bootloader UNLOCKED!!
download TWRP 2.6.3.0: http://techerrata.com/browse/twrp2/m7
verify MD5
go to bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, then flash one of the maximus 10 or 11 roms.
then go for rumrunner.
Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.
Fooox1 said:
Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.
Click to expand...
Click to collapse
sounds too much like a locked bootloader, would you mind copy/paste command prompt, for example:
Code:
C:\ADB2>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/COLOR][/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\ADB2>
No problem:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C: \ Windows \ system32> cd ..
C: \ Windows> cd ..
C: \> cd fastboot
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.
Fooox1 said:
No problem:
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.
Click to expand...
Click to collapse
1- yes, i am aware that it can be renamed, though I usually just type the first letter of the filename (for example "o") and then press tab, eg:
Code:
C:\ADB2>fastboot flash recovery o
then press TAB, and:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
2-
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
Click to expand...
Click to collapse
mine gives me a lot more info:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
3- 8432KB
What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made a backup is running, I want to restore it, is nothing.
Fooox1 said:
What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made a backup is running, I want to restore it, is nothing.
Click to expand...
Click to collapse
thanks for your kind comments, can i ask one more thing: MD5 of your "recovery.img"
The MD 5 Total:
84F04BFE70C03825689A457009235AD4
Fooox1 said:
The MD 5 Total:
84F04BFE70C03825689A457009235AD4
Click to expand...
Click to collapse
hmm, interesting I now have two versions of 2.6.3.0, one 10570KB and one 8432KB, but both worked fine:
Code:
C:\ADB2>fastboot flash recovery "openrecovery-twrp-2.6.3.0-m7 (2).img"
sending 'recovery' (8432 KB)...
OKAY [ 1.216s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.897s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.059s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.054s
-> bootloader -> recovery and it's there
have you tried using the unlocktocken again? maybe the phone is "semi-locked"
Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?
Fooox1 said:
Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?
Click to expand...
Click to collapse
1- so i just tried the lock command:
Code:
C:\ADB3>[B]fastboot oem lock[/B]
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.126s
--> it rebooted back to the ROM, i went back to bootloader and sure enough it said RELOCKED
2- "I have the internal SD card into suspicion", we could check the partitions, but I doubt that it has anything to do with it, otherwise you would be experiencing a lot of random reboots.
3- also, have you tried other "tools" that work in custom recovery, such as: http://forum.xda-developers.com/showthread.php?t=1646108
just to see if recovery is working
4- did you flash any "boot.img" (kernel)?
5- have you tried "fastboot oem unlock"
6- have you tried flashing firmware (extracted from signed OTA) in ruu mode as mentioned in post #2?
2 The suspicion arises for me, since deleted, can be moved, but the device is, after rebooting, does not run or crashes. I have already backup, Rom.zip placed on the SD, but after rebooting into recovery they're gone.
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
4 I have already tried e.g. from Vodafone Rome. As usual, Ok, Ok, but not adopted.
5 At the command fastboot oem unlock:
C: \ fastboot> fastboot oem unlock
... INFO [ERR] Command error!
OKAY
6 I have tried (OTA_M7_UL_JB_50_Vodafone_UK_1.29.161.11-1.28.161.7_release_315813_signedoj2qp335qmm8qjso) unzipped and used the firmware.zip.
Have the One_All-in One_Kit tried using the. But yes you use Flash Factory RUU zip. In this case, however, the device can not connect. About sideload's not the point. Will be transmitted to mobile phones, but the flash stops.
I also tried to flash the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe . Device is detected and goes to the black screen (HTC ), of course aborts then , since it is not the correct CID .
Fooox1 said:
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
Click to expand...
Click to collapse
It almost sounds like a secured kernel, can u post exact details of the ROM you're running, including link.
Did u ever flash a "boot.img" ?
Sent from my HTC One using Tapatalk
Problem: As after having the notification of latest update regarding stagefright exploit on my XT1052 RetailAsia version of moto x (2013), I downloaded a file named "ghost_retail_51_lpa2312-15_cid9_cfc.xml.zip", and tried flashing.
At first I started my flash-all.bat file which has all the command starting from "fastboot oem fb_mode_set" to "fastboot oem fb_mode_clear" which include commands for partition, system, boot, logo, recovery, modem, fsg, in between .(not in the order the same order as mentioned)
after all the commands done, i start checking the results from the first command, the first one i.e. fastboot oem fb_mode_set was quiet successfully done but starting from second command i.e., from fastboot flash partiton gpt.bin, all command shows same error i.e.
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>mfastboot flash partition gpt.
bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.265s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.562s
my devices info got from fastboot getvar all
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>fastboot getvar all
INFOversion-bootloader: 30BE
INFOversion: 0.5
INFOcpu: MSM8960 Pro CS
INFOram: 2048MB Samsung S4 SDRAM DIE=4Gb
INFOemmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
INFOproduct: ghost
INFOrevision-hardware: 0x8300
INFOradio: 0x3
INFOsecure: yes
INFOmid: 026b
INFOserialno: TA6---30[COLOR="black"]X4[/COLOR]
INFOqe: qe 1/1
INFOunlocked: yes
INFOiswarrantyvoid: yes
INFOmax-download-size: 805306368
INFOuid: 4EABB2050C000100000000000000
INFOimei: 3532---5[COLOR="black"]13--9[/COLOR]9-
INFOmeid:
INFOsku: 000000000000000
INFOcid: 0x07
INFOiccid:
INFOdate: 04-27-2014
INFOcust_md5:
INFOreason: Key pressed
INFOro.build.date: Fri May 8 07:37:44 CDT 2015
INFOro.build.id: LPA23.12-15
INFOro.build.tags: release-keys
INFOro.build.type: user
INFOro.build.user: hudsoncm
INFOro.build.version.codename: REL
INFOro.build.version.incremental: 19
INFOro.build.version.release: 5.1
INFOro.mot.build.customerid: RETASIA
INFOro.product.name: ghost_retasia
INFOro.build.fingerprint[0]: motorola/ghost_retasia/ghost:5.1
INFOro.build.fingerprint[1]: /LPA23.12-15/19:user/release-key
INFOro.build.fingerprint[2]: s
INFOro.build.version.full[0]: Blur_Version.222.21.15.ghost_row
INFOro.build.version.full[1]: .AsiaRetail.en.03
INFOkernel.version[0]: Linux version 3.4.42-g030aaa2 (h
INFOkernel.version[1]: [email protected]) (gcc version
INFOkernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Fri M
INFOkernel.version[3]: ay 8 07:51:10 CDT 2015
now the phone doesn't booting up nor it is going into recovery|
A "No Command" photo with an Android image into it.
i got that file from Here ,
Please tell me what to do!
in my view i thought the file i got is not AsiaRetail version or possibly the file name indicates its a CID9 version and when i checked on my phone using "fastboot getvar cid" it shows mine is 0x07. i.e,
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>fastboot getvar cid
cid: 0x07
finished. total time: 0.109s
While flashing partition gpt.bin it shows following message on bootloader screen
Downgrading security version
Update gpt_main version fail
Preflash validation failed for GPT
Galera, preciso de ajuda.
Instalei a ressurection remix no meu moto z3 play (XT1929-5) e depois tentei voltar para a stock rom. O problema é que eu acho que bloqueei o bootloader e deu loop infinito.
Já tentei:
- Desbloquear o bootloader novamente e recebo o retorno de que tenho que ativar a opção no modo desenvolvedor;
- TWRP, mas sem sucesso;
- Várias Stock Rom pelo fastboot, mas dá "Flash Permission Denied";
- Várias Stock Rom pelo RSDLite, mas dá "The phone failed to switch to fastboot mode.".
Ps.: Drivers Motorola estão instalados.
Pesquisei e vi que dá pra colocar stock rom caso seja da versão atual ou superior. Mas nenhuma funciona.
E:\Recuperar Celular\ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-3f845b6-181030
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0047858774
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 9039D011
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 06-14-2018
(bootloader) sku: XT1929-5
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4242
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.2.r1-07200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf ([email protected]
(bootloader) kernel.version[1]: j-1) (gcc version 4.9.x 20150123 (prerel
(bootloader) kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Sat Sep 15
(bootloader) kernel.version[3]: 02:19:10 CST 2018
(bootloader) git:abl: MBM-3.0-uefi-3f845b6-181030
(bootloader) git:xbl: MBM-3.0-uefi-03d7120-181030
(bootloader) gitmic: MBM-3.0-uefi-03d7120-181030
(bootloader) git:rpm: MBM-3.0-uefi-75767ea-181030
(bootloader) git:tz: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:hyp: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:devcfg: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:cmnlib: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:cmnlib64: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:keymaster: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) gitrov: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:storsec: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.228s
forum rules bro speaka english
Sorry, I did not know.
People, help me, please.
I installed the rom "Ressurection Remix" on my moto z3 play (XT1929-5) and i then tried to go back to the stock rom. The problem is: i think i blocked the bootloader and ocurred infinite loop.
I tried:
- Unlock the bootloader again. Results: "check allow OEM unlock in developer options.";
- Boot in TWRP, but without sucess;
- Many stock roms in the fastboot mode. Results: "Flash Permission Denied";
- Many stock roms in the RSDLite. Results: "The phone failed to switch to fastboot mode";
*The Motorola Drivers are installed*
I searched and saw i can put stock rom if it is the current version or higher, but none work.
*Specifications*
E:\Recuperar Celular\ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-3f845b6-181030
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0047858774
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 9039D011
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 06-14-2018
(bootloader) sku: XT1929-5
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4242
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.2.r1-07200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf ([email protected]
(bootloader) kernel.version[1]: j-1) (gcc version 4.9.x 20150123 (prerel
(bootloader) kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Sat Sep 15
(bootloader) kernel.version[3]: 02:19:10 CST 2018
(bootloader) git:abl: MBM-3.0-uefi-3f845b6-181030
(bootloader) git:xbl: MBM-3.0-uefi-03d7120-181030
(bootloader) gitmic: MBM-3.0-uefi-03d7120-181030
(bootloader) git:rpm: MBM-3.0-uefi-75767ea-181030
(bootloader) git:tz: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:hyp: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:devcfg: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:cmnlib: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:cmnlib64: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:keymaster: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) gitrov: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:storsec: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.228s
First, look for "Lenovo MOTO Smart Assistant" and install it.
It includes a "Rescue" option, and if your phone and FW version are eligible, downloads the firmware and flashing it.
if not, download the lastest firmware according to your carrier and model
https://mirrors.lolinet.com/firmware/moto/beckham/official/
And you must flashing it via fastboot commands
GuzXT said:
First, look for "Lenovo MOTO Smart Assistant" and install it.
It includes a "Rescue" option, and if your phone and FW version are eligible, downloads the firmware and flashing it.
if not, download the lastest firmware according to your carrier and model
And you must flashing it via fastboot commands
Click to expand...
Click to collapse
Lenovo MOTO Smart Assistant results:
"Failed to match the connected device. Please plug it out, and try again."
Flashing via fastboot results:
"Flash Permission Denied"
any suggestion?
Neri23 said:
Lenovo MOTO Smart Assistant results:
"Failed to match the connected device. Please plug it out, and try again."
Flashing via fastboot results:
"Flash Permission Denied"
any suggestion?
Click to expand...
Click to collapse
My sugestion is : Do not mess with your phone, i bricked a G4 play and a G5s, i regret badly.
Neri23 said:
Lenovo MOTO Smart Assistant results:
"Failed to match the connected device. Please plug it out, and try again."
Flashing via fastboot results:
"Flash Permission Denied"
any suggestion?
Click to expand...
Click to collapse
These are the correct commands according to your device active slot (A)
fastboot oem fb_mode_set
fastboot flash gpt_a gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
GuzXT said:
These are the correct commands according to your device active slot (A)
fastboot oem fb_mode_set
fastboot flash gpt_a gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thanks for help me, but it didn't works. :crying:
"Flash Permission Denied"
Does anyone know which version of this rom? (RETUS, RETBR, RETAIL...)?
Neri23 said:
Thanks for help me, but it didn't works. :crying:
"Flash Permission Denied"
Click to expand...
Click to collapse
eestou com o mesmo problema me ajuda se conseguir
[email protected] said:
eestou com o mesmo problema me ajuda se conseguir
Click to expand...
Click to collapse
Então, mano, depois de tentar de tudo e não conseguir resolver o problema, o jeito foi recorrer a assistência. Eles não levaram em conta que o bootloader estava desbloqueado e eu evitei falar sobre isso. Parece que precisou trocar a placa. Agora está rodando lisinho.
The Smart Assist will not work, once you unlock the bootloader it will not work. When they say you are voiding your warranty, they mean it. All I got was "this devie is not supported."
Neri23 said:
Então, mano, depois de tentar de tudo e não conseguir resolver o problema, o jeito foi recorrer a assistência. Eles não levaram em conta que o bootloader estava desbloqueado e eu evitei falar sobre isso. Parece que precisou trocar a placa. Agora está rodando lisinho.
Click to expand...
Click to collapse
Olá, quanto te foi cobrado pra fazer a reparação do aparelho?
No meu caso consegui flashear uma stock porém sem rede nem wifi nem do chip, os imeis estao em "0 e 00"
vc conseguiu achar algum blankflash do aparelho?
Agradeço desde já
Hey everyone,
Just a reminder that when you post, you should be using the English language. As per the XDA Forum Rules, "We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice."
Thanks!
rwilco12
z3 play beckham
[email protected] said:
eestou com o mesmo problema me ajuda se conseguir
Click to expand...
Click to collapse
o meu telefone tambem esta da mesma forma instalei a Resurrectionremix e agora deu pau
socorrrrrrrrrrroooooooooo
ja tentei de tudo mais nao da certo nada
C:\Users\elizeu\Desktop\mfastboot>fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
C:\Users\elizeu\Desktop\mfastboot>flash fastboot gpt_a gpt.bin
'flash' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>fastboot flash bootloader_a bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (9520 KB)...
OKAY [ 0.312s]
writing 'bootloader_a'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.392s
C:\Users\elizeu\Desktop\mfastboot>fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (97831 KB)...
OKAY [ 3.107s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.119s
C:\Users\elizeu\Desktop\mfastboot>flash fastboot fsg_a fsg.mbn
'flash' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>fastboot apagar modemst1
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot apagar modemst2
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot piscar bluetooth_a BTFM.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot dsp_a dspso.bin
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot logo_a logo.bin
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot boot_a boot.img
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot SYSTEM_A system.img_sparsechunk.0
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot SYSTEM_A system.img_sparsechunk.1
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot SYSTEM_A system.img_sparsechunk.2
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot SYSTEM_A system.img_sparsechunk.3
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (517994 KB)...
OKAY [ 16.435s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.448s
C:\Users\elizeu\Desktop\mfastboot>fastboot flash system_a
unknown partition 'system_a'
error: cannot determine image filename for 'system_a'
C:\Users\elizeu\Desktop\mfastboot>sistema.img_sparsechunk.5
'sistema.img_sparsechunk.5' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>fastboot sistema de flash_b system_other.img fastboot flash vendor_a fornecedor.img_sparsechunk.0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot flash vendor_a fornecedor.img_sparsechunk.1
error: cannot load 'fornecedor.img_sparsechunk.1'
C:\Users\elizeu\Desktop\mfastboot>fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (122148 KB)...
OKAY [ 3.884s]
writing 'oem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.897s
C:\Users\elizeu\Desktop\mfastboot>fastboot flash oem_b oem_ouro.img
error: cannot load 'oem_ouro.img'
C:\Users\elizeu\Desktop\mfastboot>fastboot apagar portador
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot apagar ddr
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\Users\elizeu\Desktop\mfastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Users\elizeu\Desktop\mfastboot>
One question, do not you have to see open developer options before all this?
The same thing happened to me after installing RR
After looking for some files I managed to revive my motorola z3.
It's just a matter of flashing the stock rom using flash bank.
First step have all the drivers installed on the pc. 2- Having installed the Qualcomm drivers. 3- Have the stock firmware
---------- Post added at 05:38 PM ---------- Previous post was at 05:31 PM ----------
The same happened to me after installing a few roms. But if you have a solution to that I invite you to follow the steps to revive your motorcycle z3
Benlly said:
After looking for some files I managed to revive my motorola z3.
It's just a matter of flashing the stock rom using flash bank.
First step have all the drivers installed on the pc. 2- Having installed the Qualcomm drivers. 3- Have the stock firmware
---------- Post added at 05:38 PM ---------- Previous post was at 05:31 PM ----------
The same happened to me after installing a few roms. But if you have a solution to that I invite you to follow the steps to revive your motorcycle z3
Click to expand...
Click to collapse
Hi Benlly, how are you? could you do a step by step guide explaining how to fix it? thank you, i aprecciate it
How can I not publish the files I use to help you find the internet flash bank for moto z3 and follow the steps or add me to telegram and I'll explain it better 5.5.4.0.5.6.8.2.5.9 nmro
Hi friends, I did all the procedures and my Moto Z3 Play went into Brick mode and turned into a brick. I have company and experience in TWRP, Bootloader, Unbrick of all Motorola line. But this Moto Z3 Play could not resurrect. Any suggestion ?
The screen goes blank but when I connect the data cable it beeps. Brick occurred after installing ROM RR.