Related
I buddy of mine gave me this mytouch fender because he tried to root the phone and he's an idiot.
Now the phone is stuck at the "HTC Magic" splash screen and won't boot into android and won't boot into any kind of recover.
I can get into hboot though by holding down volume and power.
Where do I start? I have a Sprint Epic 4g that I rooted for my wife so I'm not a complete moron I just need a push in the right direction for this phone.
Start by post ALL fastboot info, ALL.
Plus the outcome of this command:
Code:
fastboot getvar version-main
I didn't want to get it wrong so I just took some pics
{
"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"
}
Actually, I might be a little closer to a moron than you think.
(I just meant that I can follow directions easily enough to get through a guide or tutorial)
You are in a very good shape...
Download this combo i made for you:
EDIT new link: http://rapidshare.com/files/432674806/MagicFenderCombo.zip
Download my fastboot commander, magic version. (check my signature)
Download rom: http://cyanogenmod-mirror.local.host.name/desire/cm/stable/update-cm-6.0.2-Desire-signed.zip
Download gapps: http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-tiny-20101020-signed.zip
Guide:
1) boot into fastboot mode
2) Start my tool
3) using the first tab, load hboot, radio and recovery respectively.
4) Push "flash all"
5) If all good, go to misc tab and push "reboot device". If not, post here and do not reboot the device or shutdown the tool.
6)Your fastboot info should have changed now :0)
7) Reboot into recovery
8)choose usb-toggle
9)now you have your sdcard mounted in your OS. Move the rom and gapps to the root of the sdcard.
10)Unmount the sdcard
11)Flash the rom
12)Flash the gapps
13)Reboot and enjoy :0)
I assume you know how to use the custom recovery!!!!
Good luck.
everything looked good until it tried to flash recovery. I have my system running still and I haven't rebooted yet.
From your tool log window:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder and fastboot file(s) created.
The folder containing the IMG files was not found.
MagicFiles folder found.
hboot-1.33.2010.img found.
hboot-1.76.2007.img found.
radio_htc_pvt_32a_3.22.20.17.img found.
radio_htc_pvt_32a_6.35.16.19.img found.
recovery-ra-magic_6.35-v1.7.0.1.img found.
recovery-ra-sapphire-v1.7.0h.img found.
"Flash old" button enabled.
"Flash new" button enabled.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 3.22.20.17.
SPL/hboot version: 1.33.2010.
product: sapphire.
mid: sapp31000.
security: off.
build-mode: eng.
-----------------------------------.
Print of device info SUCCESSFUL.
Hboot, radio & recovery files set - FlashAll button enabled.
STARTING FLASH OF CUSTOM FILES.
Flashing "radio" - PLEASE WAIT.
"radio" flash SUCCESSFUL.
Flashing "hboot" - PLEASE WAIT.
"hboot" flash SUCCESSFUL.
Flashing "recovery" - PLEASE WAIT.
"recovery" flash FAILURE.
FLASH OF CUSTOM FILES FAILURE - RECOVERY FAILURE.
I noticed on the phone that all the other progress bars fill up and disappear but when it gets to the purple progress bar and tries to flash recovery it just sits there without filling in any color at all.
Somebody else was telling me that I needed a "gold card" because this is a Fender T-Mobile phone?
Anyway, I still have the phone in the last state it was in when the recovery failed to flash and I haven't rebooted yet. Waiting to here what to do next.
Try to flash the recovery alone!!!
Also provide the info inside the "actual tab".
Do not reboot, do not shutdown the tool....
You do not need any goldcard... you have eng spl...
Don't worry... as long the hboot and radio was ok, you are in no harm :0)
Same result when I try to flash recovery alone.
"Actual output" tab:
###Calling fastboot with: getvar version-baseband###
version-baseband: 3.22.20.17
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar version-bootloader###
version-bootloader: 1.33.2010
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar product###
product: sapphire
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar mid###
mid: SAPP31000
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar security###
security: off
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar build-mode###
build-mode: ENG
finished. total time: 0.000s
********************************
###Calling fastboot with: flash radio C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\radio.img###
sending 'radio' (21504 KB)... OKAY [ 5.938s]
writing 'radio'... OKAY [ 37.688s]
finished. total time: 43.625s
********************************
###Calling fastboot with: flash hboot C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\hboot_7201A_1.33.0013G_091021.nb0###
sending 'hboot' (512 KB)... OKAY [ 0.484s]
writing 'hboot'... OKAY [ 0.563s]
finished. total time: 1.047s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.719s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.531s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.719s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.531s
********************************
Ok... go misc tab. Select only the recovery in red square. Push "erase chosen partition". Now try to flash the recovery from the first tab again...
Remember to post the output from the "actual tab" here... i don't want the other info..
try to flash this instead:
http://rapidshare.com/files/387932920/recovery-RA-sapphire-v1.7.0G-cyan.img
It didn't work again after erasing recovery partition. Here's the output. I'm downloading that other file right now. You want me to flash that as recovery?
###Calling fastboot with: erase recovery###
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.704s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.522s
yes as recovery
also try this: http://www.androidspin.com/download...Y/&file=recovery-RA-sapphire-v1.6.2G-blue.img
tried cyan version and same result. The purple progress bar on the never starts to fill up.
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\Fender\recovery-RA-sapphire-v1.7.0G-cyan.img###
sending 'recovery' (4528 KB)... OKAY [ 1.703s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.517s
********************************
mumilover said:
yes as recovery
also try this: http://www.androidspin.com/download...Y/&file=recovery-RA-sapphire-v1.6.2G-blue.img
Click to expand...
Click to collapse
same result:
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\Fender\recovery-RA-sapphire-v1.6.2G-blue.img###
sending 'recovery' (4580 KB)... OKAY [ 1.703s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.517s
********************************
check your pm
Flash the eng spl again, the 1.33.2010... find it under magicfiles bundled with the tool.
If it goes well, then reboot into fastboot again... then try to flash the recovery... if it goes well, then flash the hboot that was meant to the fender (the one you downloaded to begin with) and, reboot if that want well to.
brotha its beastie here is your answer
You need to revert back to a HTBOOT that will accept the update. Here is your instructions.
http://forum.xda-developers.com/showthread.php?t=622530
... and here is some help for AFTER you have downgraded
you should be able to apply the directions the original gentlemen told you after you downgrade. in order to downgrade you MUST have a goldcard. If his solution does not work do not fear but follow this http://forum.xda-developers.com/showthread.php?t=623141 and THEN apply his fix. Let me know via text or not if this works ... and get your ass back to work you too brent!
beastiezee said:
you should be able to apply the directions the original gentlemen told you after you downgrade. in order to downgrade you MUST have a goldcard. If his solution does not work do not fear but follow this http://forum.xda-developers.com/showthread.php?t=623141 and THEN apply his fix. Let me know via text or not if this works ... and get your ass back to work you too brent!
Click to expand...
Click to collapse
Brent and work in the same sentence. That's an oxymoron isn't it?
Hi, i know some of you are not very happy with the update, and ONLY if you took the OTA (and not flashed the full image) there is still hope for you.
im not sure if this will work, i need someone with a Droid Turbo (DT) to try.
the risk is 0, if this metod doesnt work, it will simply not flash, so no risk on it.
First you have to download the original Kitkat Firmware of Droid Turbo:
https://mega.co.nz/#!hZVThbjC!SqvNd7KYqYEvnbHRulVKJ2N9dsjMuNXpkcl1h-ENL3g
Requisites:
Android Studio or Minimal ADB and Fasboot (i personally recommend Minimal Adb and Fastboot because thats all we gonna need and its lighter than Android Studio 2 Mb vs 800Mb)
Kitkat Firmware
mFastboot (motorola Fastboot) i uploaded it for you: https://mega.co.nz/#!MVtz1DLb!CZTh_-wCl-qyta4Q0yZuPk_TB6Wq7Z4zElk6eArXrXk
Installation:
1.- Install MAaF
Install Minimal ADB and Fastboot
2.- Install mFastboot
Copy the contents of mfastboot.zip and put them on Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot)
Now you have working Fastboot AND mFastboot
3.- Copy Firmware
Copy the contents of your desired firmware to Minimal ADB and Fastboot Folder like this:
VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml
unzip and put all content of the file on the Minimal ADB and Fastboot Folder
Now you are ready to flash!
First turn off your device and Put it on fastboot mode (Power and volume down for 2 seconds with your phone off)
4.- Get Detected
type
Code:
fastboot devices
on minimal adb to see if your pc detects your phone on fastboot mode
if you get some numbers and letters like the picture you are ready to go.
if not, you are missing drivers, looks for Motorola Device Manager
5.- Install
Copy and Paste these commands on Minimal ADB and Fastboot:
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot erase cache
mfastboot reboot
Click to expand...
Click to collapse
and thats all, as easy as copy from here and paste on cmd.
i highly recommend that you erase everything for a smoother experience, but some people want to keep all their files, so this line its optional
mfastboot erase userdata
Click to expand...
Click to collapse
and thats all, as easy as copy from here and paste on cmd.
when your phone finishes flashing just press enter to execute mfastboot reboot and you will boot kitkat again
Once again i have not tried this, the bigger risk is that you will have to flash lollipop again in case it doesnt work.
Anyone willing to try? be the first to downgrade to Kitkat!
Gonna test it out now!!
Thanks man!!!
Also below is a link for the 21.128-15_15_CFC_SVC.xml (got errors when trying to unzip your download @Jaocagomez)
http://www.rootjunkysdl.com/files/Droid%20Turbo/Firmware/VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml.zip
You are going to get a Preflash Validation failed error message from fastboot. This was attempted when people had soft bricks from sideloading the ota and there was no img available.
http://gyazo.com/c5d1be6c5a88265bf13af3cbce30ce12
I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
{
"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"
}
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(
weaver11b said:
I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(
Click to expand...
Click to collapse
what happens if you skip bootloader.img?
This happens:
C:\adb>mfastboot flash radio radio.img
target max-sparse-size: 256MB
sending 'radio' (85544 KB)...
OKAY [ 2.682s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
OKAY [ 1.734s]
finished. total time: 4.420s
C:\adb>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.786s
C:\adb>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 0.472s]
finished. total time: 0.994s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\adb>
weaver11b said:
This happens:
C:\adb>mfastboot flash radio radio.img
target max-sparse-size: 256MB
sending 'radio' (85544 KB)...
OKAY [ 2.682s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
OKAY [ 1.734s]
finished. total time: 4.420s
C:\adb>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.786s
C:\adb>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 0.472s]
finished. total time: 0.994s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\adb>
Click to expand...
Click to collapse
Looks like its not gonna work, damn
weaver11b said:
I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(
Click to expand...
Click to collapse
Side loading the OTA zip and taking the OTA update are the samething.
There is the same amount of hope as there has always been. This method was already tried at least two weeks ago, there is nothing special about it. It is the same way you flash any motorola image from fastboot.
what about flashing kitkat with mofo?
not free but it could work
How is this any different than RootJunky's youtube method of reverting back to stock KK firmware? If you click on the VRZ_XT1254_KDF21.128-15_15_CFC.bat in the folder you download from his site file in fastboot it runs these commands which are similar to yours.
SET fastboot=fastboot.exe
%fastboot% oem fb_mode_set
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot bootloader.img
%fastboot% flash radio radio.img
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
%fastboot% flash system system.img_sparsechunk4
%fastboot% flash system system.img_sparsechunk5
%fastboot% flash system system.img_sparsechunk6
%fastboot% erase ddr
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% oem fb_mode_clear
pause
This is the standard way of reverting back to the original KK firmware and I've been able to do it from a Mofo'd CF Lollipop image fine. If you took the Lollipop OTA this method is gonna be incompatible with the updated Lollipop bootloader. You need the original KK bootloader for this to work.
sorry, dont work after flash original image brazil 5.0.2 rsdlite?
Jaocagomez said:
Looks like its not gonna work, damn
Click to expand...
Click to collapse
based on this I am closing this thread
I tried everything with no lock, and the device is bricked
I get this
C:\adb>fastboot devices
HT6680101762 fastboot
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5fe000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x10d000000
(bootloader) serialno:HT6680101762
all:
finished. total time: 0.369s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: Not allow when s-on)
finished. total time: 0.047s
C:\adb>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.016s
leonardojt said:
I tried everything with no lock, and the device is bricked
I get this
C:\adb>fastboot devices
HT6680101762 fastboot
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5fe000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x10d000000
(bootloader) serialno:HT6680101762
all:
finished. total time: 0.369s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: Not allow when s-on)
finished. total time: 0.047s
C:\adb>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
unfortunately I hope it's not like these:
https://forum.xda-developers.com/htc-10/help/stuck-bootloader-getvar-empty-t3597375
https://forum.xda-developers.com/htc-10/help/stuck-bootloop-unlocked-bootloader-twrp-t3596968
https://forum.xda-developers.com/htc-10/help/enter-download-mode-t3406529/page3
andybones said:
unfortunately I hope it's not like these:
https://forum.xda-developers.com/htc-10/help/stuck-bootloader-getvar-empty-t3597375
https://forum.xda-developers.com/htc-10/help/stuck-bootloop-unlocked-bootloader-twrp-t3596968
https://forum.xda-developers.com/htc-10/help/enter-download-mode-t3406529/page3
Click to expand...
Click to collapse
yes
that is my problem.
any solution sir? is it fixable? or what do I do in this situation?
the only partition I could flash is hosd plus it is only possible to flash in white bootloader using vol+, vol- and power
I tried to do as others did but the I could not extract the RUU zip it sort of has 1 to 27 little zips which I don't even know how to combine them coz when I open one with winrar I see the all the required files but I can't extract. also where can I get RUU.exe of Nougat for Htc 10 Verizon? thanks
leonardojt said:
the only partition I could flash is hosd plus it is only possible to flash in white bootloader using vol+, vol- and power
I tried to do as others did but the I could not extract the RUU zip it sort of has 1 to 27 little zips which I don't even know how to combine them coz when I open one with winrar I see the all the required files but I can't extract. also where can I get RUU.exe of Nougat for Htc 10 Verizon? thanks
Click to expand...
Click to collapse
Here's one place.
{
"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"
}
Sent from my HTC6545LVW using XDA-Developers Legacy app
hgoldner said:
Here's one place.
Click to expand...
Click to collapse
thank you, but I am on s-on is this signed firmware?
vdChild said:
View attachment 4208998
Sent from my HTC6545LVW using XDA-Developers Legacy app
Click to expand...
Click to collapse
you mean the thread that could help me has been deleted?
If you are bootloader LOCKED and S-ON, I don't see how you could be flashing anything whatsoever. Did you leave something out?
hgoldner said:
If you are bootloader LOCKED and S-ON, I don't see how you could be flashing anything whatsoever. Did you leave something out?
Click to expand...
Click to collapse
Somehow HTC allow hosd to be flashed without S-off unlike the rest partitions
leonardojt said:
Somehow HTC allow hosd to be flashed without S-off unlike the rest partitions
Click to expand...
Click to collapse
Then that would explain why you're bricked, wouldn't it?
hgoldner said:
Then that would explain why you're bricked, wouldn't it?
Click to expand...
Click to collapse
Is it possible to S-off in this mode?
leonardojt said:
Is it possible to S-off in this mode?
Click to expand...
Click to collapse
I doubt it, since Sunshine only works on a booted handset that is pre-Nougat. I have no idea whether @beaups or @jcase could somehow S-OFF it without being able to boot it. You might want to ask in that thread.
I am getting error on my moto G4 plus when trying to paste the key
fastboot oem unlock YSRYD556PVZFLG36GGJI
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.008s]
finished. total time: 0.010s
But now I am getting this unlocked bootloader warning screen.
I think something is messed up....
It was so easy in nexus and one plus devices ..
{
"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"
}
@nitinvaid that "not found" things is common i have seen with few others too but it works fine.
As well you got that warning for unlocked bootloader, it means it got unlocked successfully. You can try to flash TWRP.
Update: there is thread to hide that unlock message, see in themes section of this device.
____Mdd said:
@nitinvaid that "not found" things is common i have seen with few others too but it works fine.
As well you got that warning for unlocked bootloader, it means it got unlocked successfully. You can try to flash TWRP.
Update: there is thread to hide that unlock message, see in themes section of this device.
Click to expand...
Click to collapse
Nope tried flashing recovery
"I:\android-sdk\platform-tools>fastboot flash recovery twrp-3.1.1-athene_shreps.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13674 KB)...
OKAY [ 0.436s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.360s]
finished. total time: 0.799s"
nitinvaid said:
Nope tried flashing recovery
"I:\android-sdk\platform-tools>fastboot flash recovery twrp-3.1.1-athene_shreps.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13674 KB)...
OKAY [ 0.436s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.360s]
finished. total time: 0.799s"
Click to expand...
Click to collapse
TWRP is flashed bro!
nitinvaid said:
Nope tried flashing recovery
"I:\android-sdk\platform-tools>fastboot flash recovery twrp-3.1.1-athene_shreps.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13674 KB)...
OKAY [ 0.436s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.360s]
finished. total time: 0.799s"
Click to expand...
Click to collapse
That message of 'image not signed or corrupt' is normal. You've got OKAY which indicates the flash worked. Reboot to recovery after flashing to ensure TWRP is not overwritten by the stock recovery. Afterwards, you may boot as normal.
echo92 said:
That message of 'image not signed or corrupt' is normal. You've got OKAY which indicates the flash worked. Reboot to recovery after flashing to ensure TWRP is not overwritten by the stock recovery. Afterwards, you may boot as normal.
Click to expand...
Click to collapse
I'll check that when I reach home... I thought that's the error....
I will be going to flash the RR ROM
nitinvaid said:
I'll check that when I reach home... I thought that's the error....
I will be going to flash the RR ROM
Click to expand...
Click to collapse
I think it's more a warning to remind you that TWRP is not cryptographically signed with the expected keys that the bootloader is programmed with. As such, you're flashing an image in fastboot that is different to what the bootloader is expecting, which may explain the message.
Either way, as I and abhi212b mentioned, the flash worked, but stock recovery will overwrite TWRP if you boot to system, rather than recovery.
Good choice of ROM, good luck with the flashing.
Yes it worked thanks everyone.... It looks like that all are false error....
nitinvaid said:
Yes it worked thanks everyone.... It looks like that all are false error....
Click to expand...
Click to collapse
Hi Sir,
im facing this error any help..!!!
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock NGJNEFR3NSLXSYPTOPAI
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.015s]
finished. total time: 0.020s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp-sanders-r16.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (15082 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.802s
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
After an unsuccfessful flash to downgrade from Android 12 to Android 11 i hard bricked the device due to validation errors on the preloader (see below). Unfortunately i had a reboot lastly in my batch file...
Now I have no response on power button, and no recognition via USB. Just dead.
I need to figure out how to enter BROM mode for the G31, I assume this is going to be via test points.
Anyone here has that information or any other unbricking ideas?
Here are the errors:
writing 'preloader'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.032s
writing 'lk_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.097s
writing 'tee_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.047s
writing 'sspm_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.044s
writing 'gz_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.148s
Exactly the same problem here... any luck?
Looks like we must use the "fastbootd" mode to flash... not the regular fastboot... as shown on this video:
But now... I cannot get it to even turn on or connect to the pc...
After a lot of research on the topic, my conclusion is:
If it is not recognize when plug in USB...
doesn't show on the Device Manager... There is no hope to revive it!
That's a Mediatek issue... there is no "Force USB Connection" test point...
RIP G31...
FritzSM said:
After a lot of research on the topic, my conclusion is:
If it is not recognize when plug in USB...
doesn't show on the Device Manager... There is no hope to revive it!
That's a Mediatek issue... there is no "Force USB Connection" test point...
RIP G31...
Click to expand...
Click to collapse
I followed that exact same youtube video when mine was bricked. This is terrible
DivineSEnse said:
After an unsuccfessful flash to downgrade from Android 12 to Android 11 i hard bricked the device due to validation errors on the preloader (see below). Unfortunately i had a reboot lastly in my batch file...
Now I have no response on power button, and no recognition via USB. Just dead.
I need to figure out how to enter BROM mode for the G31, I assume this is going to be via test points.
Anyone here has that information or any other unbricking ideas?
Here are the errors:
writing 'preloader'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.032s
writing 'lk_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.097s
writing 'tee_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.047s
writing 'sspm_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.044s
writing 'gz_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.148s
Click to expand...
Click to collapse
Without unlocked bootlader this flashing will not work. That's why it is giving you error Failed (remote failure).
You can try to connect device by pressing volume up and down buttons simulataneously to get it into BROM mode.
Please make sure to have all the MTK drivers installed and use libusb to install the device filter for MTK port.
Only official Motorola Service Center has tool to flash the device in locked state.
You can easily find the test point of your phone if you are comfortable in disassembling the device, the test point is usually located near the memory chip.
Please refer to this video. You may get some idea on how the device is flashed.
Thank you!. But I already had gone through the process of unlocking the bootloader. The phone gave me the unlocked bootloader splash screen on startup so It should have been unlocked.
I have tried various combinations of button presses while connecting but nothing seems to work.
I'm quite comfortable opening the phone up and I already have, but I would need some further instructions locating the BROM test point. Is it under the metal shield perhaps? If I find it, I just ground it right?
I believe I have installed all the drivers mentioned, several times.
DivineSEnse said:
Thank you!. But I already had gone through the process of unlocking the bootloader. The phone gave me the unlocked bootloader splash screen on startup so It should have been unlocked.
I have tried various combinations of button presses while connecting but nothing seems to work.
I'm quite comfortable opening the phone up and I already have, but I would need some further instructions locating the BROM test point. Is it under the metal shield perhaps? If I find it, I just ground it right?
I believe I have installed all the drivers mentioned, several times.
Click to expand...
Click to collapse
Can you please send in a picture of both side of your phone's motherboard?
mvikrant97 said:
Can you please send in a picture of both side of your phone's motherboard?
Click to expand...
Click to collapse
I'll do that! Give me a day or two
Should have said a week or two ;P
S
DivineSEnse said:
Should have said a week or two ;P
Click to expand...
Click to collapse
Sure
Here is one side @mvikrant97, need to disassemble a bit to get the other side... hold on.
{
"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"
}
Here is the other side.
DivineSEnse said:
Here is the other side.View attachment 5937639
Click to expand...
Click to collapse
Does your phone shows up in device manager as Mediatek Preloader Vcom when connected to PC?
mvikrant97 said:
Does your phone shows up in device manager as Mediatek Preloader Vcom when connected to PC?
Click to expand...
Click to collapse
No, it does not show up at all. So I need to force it into BROM somehow.
DivineSEnse said:
No, it does not show up at all. So I need to force it into BROM somehow.
Click to expand...
Click to collapse
To force into BROM we need to see if it connects in MTK Preloader mode