My phone is totally unresponsive to everything I try to do with it. Its a MT3G 1.2.
I tried rooting it. Created a goldcard, flashed the sappimg from the unlockr guide. then tried various combinations of stock files, all with the same "signature error". Today, I decided to try and go back to the stock with the RUU. it went fine, til it flashed the System partition, which it sat there for 30mins and did nothing... Now im stuck with a phone that only goes into RUU, and refuses to let me flash ANYTHING to it, reguardless of version/type/size/extension/ect. NOTHING works. every file I try gives me either a signature error or model ID error. The RUU fails, everytime. and Ive tried all three T-MO ones and a few from europe. RUU says my version is 2.53.707.2... Yet when i try flashing that RUU it says gives a wrong model error. I dont get it. My goldcard, which worked to flash the HTC Magic sappimg, is in the phone thru all of its. its like it doesnt see my sdcard. I know the goldcard is good, I just used it.
Displayed on phone:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CLD-13
RADIO-2.22.23.27
-----
fastboot oem boot displays:
-----
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x98070CA0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 32
(bootloader) TAG:hwid 0x1
(bootloader) TAG:skuid 0x22800
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x2
(bootloader) radio_flash_id=0x1543BCEC
(bootloader) die_size=0x2
(bootloader) radio_flash_id=0x1543BCEC
(bootloader) die_size=0x2
(bootloader) TAG:die_size = 0x2
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB010
(bootloader) setting.cid::T-MOB010
(bootloader) serial number: HT03YPB02450
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =337
(bootloader) active commandline: board_sapphire.disable_uart3=1 board_sap
(bootloader) phire.usb_h2w_sw=1 board_sapphire.disable_sdcard=1 smisize=3
(bootloader) 2 androidboot.baseband=2.22.23.02 androidboot.cid=T-MOB010
(bootloader) androidboot.carrier=TMUS androidboot.keycaps=qwerty androidb
(bootloader) oot.mode=normal androidboot.serialno=HT03YPB02450 androidboo
(bootloader) t.bootloader=1.33.0013 no_console_suspend=1 console=null
(bootloader) PARTITIOM_NUM_MAX =6 Valid partition num=6
FAILED (status read failed (Too many links))
finished. total time: 7.701s
-----------
Does this mean my SD Card is disabled??? Ive tried the codes to re-enable it, but they do nothing. "Fastboot oem enableqxdm 0" gives an error, and "fastboot -c board_sapphire.ect=0" says finished but nothing ever changes.
Im running out of ideas... am I missing something, or have i successfully bricked my phone... please help!
Run these commands and post here the output:
Code:
fastboot getvar version-main
fastboot oem h
Try also this:
Code:
fastboot oem enableqxdm 1
Tried those.
C:\Documents and Settings\Ryan>fastboot oem h
...
(bootloader) command list
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) task
(bootloader) rtask
OKAY [ 0.000s]
finished. total time: 0.030s
C:\Documents and Settings\Ryan>fastboot getvar version-main
version-main: 2.53.707.2
finished. total time: 0.000s
C:\Documents and Settings\Ryan>fastboot oem enableqxdm 1
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------
I vaguely remember erasing the misc partition... and im pretty sure thats what screwed it all up. Now im stuck with a perfected hboot and no system or userdata partitions, and a blank mtd0 partition. Every time I try and flash a .zip, the image signature fails. If i try to flash a SAPPIMG.nbh or ROM.zip (extracted from RUU) it says "adopting signature" but then fails for either model ID or main version. it looks like i need a HTC signed SAPPIMG.zip with main version 2.53.707.2 and a model ID of SAPP31000... where on earth I can find said file, i have no idea.
either that, or a zip/recovery file that will pass the signature check...
Do you use a goldcard... if so, it seems like you are using a bad one..
yeah i actually bought a new sandisk 2gb card just to use for it. i just remade it last night. Im going to try making another one with a 4gb lexar card, and a 256mb kingmax. Maybe RUU mode doesnt like the sandisk?
Execute reset to try to get out of the ruu mode:
Code:
fastboot oem reset
-----
FAILED (status read failed (Too many links))
finished. total time: 0.010s
-----
I made two more goldcards, and it does the same thing: keeps kicking back signature and model id errors when i try to flash files. running out of ideas other than jtag or a custom file. but i have no idea how to do either
Well... you cannot flash files from fastboot using the coldcard...
It must be done from hboot mode ( Hold volume - (decrease) and power), then the process should pick up the sappimg.zip or sappimg.nbh file from the sdcard...
It wont go into fastboot... that key combo makes it go right back to the RUU screen.
I think what I need is the RUU file for the FRG83D update... it has a newer main version, so it should go thru. But I cant find it. I found the one for the SAPP30000 but not for my 31000.... i guess it hasnt been leaked yet.
OK so I downloaded the official 2.2.1 update file from google's servers... tried to flash it with fastboot update and flash zip. One gave an error for no android-info file. The other failed, yet again, for security failures. what the hell is up with this phone? absolutely no files, including files from google, pass the signature check. What fricken signature is it looking for? The only files ive had pass the security check, its failed for some other reason (model ID, main version). I made my goldcard again, but I got the CID using my cousins Samsung Fascinate (gag), so I'm wondering if it spit out the right number. not sure. thou it did let me flash the 2.53.707.2 file with it... so i think it worked? Im seriously about to lose my mind. Im fairly confident that if I can somehow get the System and Userdata partitions flashed, it will be fine. Cuz the RUU successfully flashed everything except those last two partitions. Someone leak the RUU pleaseeeee
i have the same issue with my phone (3g 1.2)
i've tried so many things, goldcard, etc.. nothing worked.
when flashing sappimg, i always got stuck at system unzipping.
the one time i got RUU to actually flash the phone, it hung on the system partition. Now i cant even get it to go that far. every file either hangs or fails signature check or model/main version. luckily Im getting a Fender LE tomorrow so until the mythical RUU appears, my MT3G will be a charger dock.
My RUU update was stuck on system- unzipping for like half hour. i didnt know what to do so i turned off the phone and restarted it, it went into RUU mode and i couldnt update anything else, cuz all RUU upates would give me wrong version/ID, etc.
now i think it is because i dont have eng spl on the phone, thus it not allowing to update. the only thing i can think of to do, is get an eng RUU, to update it, and then it should get out of RUU mode.
and btw, How to flash it using goldcard, when i cant get to Hboot??
I believe yours is salvageable. U can fastboot from RUU so try flashing the engineering SPL from there. My understanding is the phone should "see" the goldcard and let RUU/Fastboot flash whatever files you want it to. This however hasnt been the case for me.
i will try to do that, but how do i flash an engineering spl?
get eng sappimg.zip?
and how do i do it?
i just made another goldcard with my friend's phone.
I have been working with Android for a few years now. My Nexus 7 has no problems. A friend tried to update her 7 to 4.4.4 via the standard system update. Hers was completely stock, not rooted, not unlocked. She ended up stuck in the bootloader afterward.
The bootloader is locked. When I try to unlock it I get the following error.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (unknown error code))
finished. total time: 5.299s.
I have tried 2 computers, 3 usb cables. I have tried WUGS toolkit as well without luck. Nothing seems to get this bootloader unlocked.
Is there anyway to flash the factory files with a locked bootloader?
Any other options?
@gotbeer: Have you tried unlocking it with fastboot?
Sadly the string above is what I get when I used fastboot to unlock.
fastboot oem unlock
I have completely drained the battery and am going to try again. Three other Nexus 7's and a Galaxy Nexus and Ive never had a problem with unlocking the bootloader. Im beginning to suspect a hardware failure on this one.
Is there another way besides fastboot to unlock the bootloader I can try? The system partition is erased so I cant get into there to do anything. Im sure she never enabled USB debugging, so ADB is out of the question?
I have Moto X play XT1563. It was stuck in a boot loop - moto logo->circle and "erasing"->reboot
Fastboot and ADB works
I tried to flash new firmware (stock image) - failed:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
based on that and research I decided to unlock bootloader, which ended up with:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
since phone is unalbe to boot I cannot go to dev options. Is there any way to have it done using adb or fastboot? even low level linux way to change something in the config?
or (easier way) - anyone aware where can I find new Bell firmware? now I have M8936_2020632.44.03.21.57R LUX_BELLCA_CUST
Appreciate any suggestions
Check here
https://github.com/motoxplay/stock
there is a bell firmware but is tagged with a BELL? so, don´t know if will it work
Cheers.
Thanks - checked that before - this one is 6.0.1 and I need 7.1.1
Version NPD26.48-21-1 to be exact
I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s
stingu said:
I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
Did you try to install TWRP ? It's not bootloader unlocked, is it ?
Bootloader is locked, while trying to unlock it I get:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Flashing and booting fails, for stock and TWRP
Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?
Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?
OP. After downloading Lineage last update through updater in settings, my phone was hardbricked.
I tried to follow this guide https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 without success. My phone recovered from hardbricking with blankflash and now I'm into a barebone bootloader screen.
The point is I cannot continue with the steps because it seems I'm trying to downgrade the gpt and bootloader
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Please, help me, thanks.
It lives now, I don't know why.
I tried a yolo and flashed a stock ROM in that barebone fastboot. Almost everything failed but, surprise, Lineage booted in a clean state.
Hello all,
I am not very familiar with flashing devices and therefore I'm asking for help before trying further be myself.
In short: I flashed Lineage OS 17.1 to my daughters Moto G4 Play (as described in the Lineage-Wiki), recognized an incompatibility of LineageOS with "Google Family Link", reflashed (not the latest) stock rom, started the phone, first ota-update went through, after the 2nd phone didn't start anymore.
Found the threat "[HARDBRIK] Moto G4 Play XT1603..."(didn't recognize the different "variant") , executed the blankflash but now :
my bootloader is locked again
my Product/Variant displays "harpia radio5" (instead of "harpia XT1601")
Could someone give me an advice how to proceed?
Many thanks, Chris
Tried to proceed by myself but didn't get far.
When trying to unlock my bootloader again I receive the following:
>fastboot oem get_unlock_data
(bootloader) Failed to get unlock data, please try again!
FAILED (remote: '')
fastboot: error: Command failed
When trying to flash an recovery image it fails:
>fastboot.exe flash recovery twrp-3.5.0_9-0-harpia.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16106 KB) OKAY [ 0.623s]
Writing 'recovery' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Can anybody give me a hint?
same problem here
you need the stock firmware of your variant flashing first the GPT.bin
you bootloader is lock when blankflash and you need flash all firmware ,then unlock the bootloader with your code without forgetting to put oem unlock in the developer options
angelgs826 said:
you need the stock firmware of your variant flashing first the GPT.bin
Click to expand...
Click to collapse
Thank you, your comment was very useful.