Develop Bugs

[Q] Bricked Kindle Fire not recognized by either ADB or Windows

Hey guys, I'm a new member to XDA but I've been browsing on it for a while. I figured you guys could help. I rooted my Kindle Fire a couple months ago and had Clockwork Recovery(TWRP is better). I decided I didn't want it rooted so I restored the Kindle thinking it would remove the root, it actually bricked it. Now all that comes up is the Kindle Fire boot screen with the android bot over top of it, it doesn't glimmer or flash, that's all. It isn't recognized by ADB or Windows(and Device Manager). I haven't found a thread exactly like mine so I figured I'd post one. Please help guys, I miss Minecraft PE and Netflix!

Assuming you know how to access recovery...
Download the latest version of FireFireFire and either "adb push" it to your sdcard or use the mount function in recovery and transfer it.
FireFireFire 1.4 can be found here. It comes in a .zip file for flashing in recovery. DO NOT install the .zip file with the "fastboot flash bootloader" command or you will brick your device.
When installed reboot and use your power button at the kindle fire screen as if you were trying to enter recovery. At some point some options will show up on the bottom. Use the power button to select "Normal Boot".

@soupmagnet
what do you mean by ADB Push? Recovery as in turning the kindle on and then holding the power button again until it turns orange?

mrpike9416 said:
@soupmagnet
what do you mean by ADB Push?
Click to expand...
Click to collapse
Actually, it would be easier to explain how to mount your sdcard.
Recovery as in turning the kindle on and then holding the power button again until it turns orange?
Click to expand...
Click to collapse
Yes. While in recovery, there will be a mount to USB function that will mount the sdcard partition to your computer as if it were an external drive, such as a USB thumb drive.

Good thing I know that, however, I can't access recovery..
I think I might've reformatted the system folder while in recovery..

mrpike9416 said:
Good thing I know that, however, I can't access recovery..
I think I might've reformatted the system folder while in recovery..
Click to expand...
Click to collapse
Recovery is in a separate partition from the system files and cannot be formatted while in recovery. I'm not sure why you wouldn't be able access recovery so you'll probably need to reinstall it.
How comfortable are you with using command prompt?

A little experienced, how hard can entering commands be?

mrpike9416 said:
A little experienced, how hard can entering commands be?
Click to expand...
Click to collapse
OMG Don't EVER say that.
Do you have adb and fastboot on your computer? If yes...Is it from AndroidSDK or KFU?

Hahahahha my mistake.
I do have ADB but I don't think I have fastboot(I probably do).

I do have fastboot.

mrpike9416 said:
I do have fastboot.
Click to expand...
Click to collapse
Okay, make sure the you have TWRP version 2.1 and place it in the same folder as fastboot. It would be wise to rename it to something manageable like "twrp.img"
In your command prompt, enter:
fastboot flash recovery twrp.img
Note: version 2.0 will not work with this command
And while you're at it:
fastboot oem idme bootmode 4000
fastboot reboot
[Edit:] That will likely fix your problem (barring driver issues) but you should still install FFF1.4

I just tried a different cable and the computer recognizes my kindle in device manager as Android ADB Interface... the twrp 2.1 cmd thing you told me to do was a no go but I assume we have more options now now that device manager recognizes it?
(EDIT)
It is now recognized on device manager as "Unknown Device" and no longer as Android ADB Interface..

1. What happens when you enter:
Code:
fastboot devices
2. What error message, if any, did you receive when entering the "twrp 2.1 cmd thing"?

"fastboot" is not recognized as an internal or external command, operable program or batch file.
That happened for both instances.

mrpike9416 said:
"fastboot" is not recognized as an internal or external command, operable program or batch file.
That happened for both instances.
Click to expand...
Click to collapse
Do you have fastboot and what folder is it in?

Yeah its an .exe file i believe... under the "Files and Tools" folder when I downloaded ADB from Android SDK.

Better yet...fastboot and adb are programs with a certain set of commands associated with them. Those commands only work with each individual program. In order to issue a certain command that isn't associated with "shell" or "DOS" you have to include an "identifier" so the computer knows from which program to run the commands. In this case it is "fastboot" because you are using the fastboot program. In order issue commands this way, the program you are using must either be listed in your "PATH" or be in the directory from which you are issuing the commands.
The easiest way to do this in Windows is to shift+right click on the folder containing the program and select "Run in Command". The command window that opens is were you will be entering your commands.

error: cannot load "twrp.img"
I typed "fastboot devices!" (out of frustration I must admit).
This is what came up:
C:\Users\Nick\Documents\KindleRoot\tools>fastboot devices!
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
-n <page size> specify the nand page size. default:
2048

Turn your device off then enter the command. When it says "waiting for device" turn it back on.
Fastboot commands only work in fastboot mode. If you have a modified bootloader installed, the first few seconds of the boot process is a temporary fastboot mode which will accept fastboot commands.
If it just hangs at "waiting for device", you need to fix your drivers.

soupmagnet said:
Turn your device off then enter the command. When it says "waiting for device" turn it back on.
Fastboot commands only work in fastboot mode. If you have a modified bootloader installed, the first few seconds of the boot process is a temporary fastboot mode which will accept fastboot commands.
If it just hangs at "waiting for device", you need to fix your drivers.
Click to expand...
Click to collapse
what command am I entering?

jUST BOOTLOADER SCREEN JUST

NO RECOVERY JUST BLUE SCREEN NO DOWNLOAD MODE JUST BLUE SCREEN
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What did you do to get to this state? Please try to list the exact steps in order. Also, what had you done to the phone before you started whatever happened here, i.e., what rom/firmware were you on?

iElvis said:
What did you do to get to this state? Please try to list the exact steps in order. Also, what had you done to the phone before you started whatever happened here, i.e., what rom/firmware were you on?
Click to expand...
Click to collapse
htc m9 asia tw
s-on
firmware update to 5.1 (2.10.709.1) through RUU mode sudden mobile reset and now when it on after that gives blue blank screen just....
just bootloader screen come while pressing vol + and vol - and power button. bt no recovery no download mode no RUU mode while going to download mode blue screen error.
plz someone help. what to do.

We need more detail than that to help.
What file did you try to flash? How exactly did you do it? By "RUU mode" do you mean you used the fastboot oem rebootRUU command, or something else? Or were you running a RUU.exe file? Which one?
You were unlocked; were you running a custom rom before this? Which one? How did you relock?

iElvis said:
We need more detail than that to help.
What file did you try to flash? How exactly did you do it? By "RUU mode" do you mean you used the fastboot oem rebootRUU command, or something else? Or were you running a RUU.exe file? Which one?
You were unlocked; were you running a custom rom before this? Which one? How did you relock?
Click to expand...
Click to collapse
HTC m9 asia tw it was with firmware 1.40.709.8 then i unlocked bootloader from htcdev.com and used venom rom...
after that i started to update to 5.1 i used following commands,
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
fastboot oem rebootRUU
fastboot flash zip firmware-2.10.709.1.zip
fastboot reboot-bootloader
firmware updated successfully but it stuck at htc logo.
then i flash again firmware.zip sudden mobile reset and this blue screen appears. now when going to RUU, download, recovery mode this blue screen appears.
bootloader screen come while pressing vol + and vol - and power button but can't flash anything. while using command on bootloader screen fastboot gives error FAILED (remote: cannot flash this partition in s-on state)
FAILED (remote: Not allow when s-on)

solve this problem
please reply

how can you solve the problem ???

hoang555 said:
how can you solve the problem ???
Click to expand...
Click to collapse
not solved yet....

mnhs1010 said:
not solved yet....
Click to expand...
Click to collapse
theirs nothing you can do but send it to HTC. any fix would require you get into download mode at least

clsA said:
theirs nothing you can do but send it to HTC. any fix would require you get into download mode at least
Click to expand...
Click to collapse
no download mode. no recovery just bootloader screen. otherwise blue screen just......
i have sent it to htc service center in dubai but they did not repair it. they its on our country set. send it to asia tw for repairing. what the hell is this...

mnhs1010 said:
no download mode. no recovery just bootloader screen. otherwise blue screen just......
i have sent it to htc service center in dubai but they did not repair it. they its on our country set. send it to asia tw for repairing. what the hell is this...
Click to expand...
Click to collapse
any solution please tell

hoang555 said:
how can you solve the problem ???
Click to expand...
Click to collapse
please u have any solution please tell me.

https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#
inset Firmware Packs
"WARNING: HTC introduced a new "security feature" with the 2.XX.XXX.X firmware. This "feature" blocks the Bootloader Unlock if the option "OEM unlocking" in the Developer Options isn't activated. Because of that it's not recommended (especially to S-ON Users) to relock the Bootloader and flash these files if you want to update to Firmware 2.XX.XXX.X or newer. You better use a RUU and the Update Function in "Settings>About" for that purpose."
Flash stock rom, RUU.exe

finally replacement of mainboard

Possible Solution!
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on

lizard2k5 said:
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on
Click to expand...
Click to collapse
i have this issus before, that will fix it but for now his phone is S-on so im afraid it will not work

I Did say S-OFF only but thanks for your input - I know a few people who were stuck with S-OFF too.
Arthas92 said:
i have this issus before, that will fix it but for now his phone is S-on so im afraid it will not work
Click to expand...
Click to collapse

I'm stuck at same problem. Does anyone can help?
Is XTC an option?

lizard2k5 said:
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on
Click to expand...
Click to collapse
Hi. I have the same problem which is blue screen on download mode. I tried this method but nothing happen. My HTC is verizon version. I tried to flash all the img from 3.37.605.7 firmware but still the same.

Stuck in Fastboot/No Download Mode

Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !

Try adb fastboot when writing command hope it helps

Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?

cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/

BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?

I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091

BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!

Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?

SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.

Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?

If they found it's rooted or they understand you did something with your software your warrenty is void ?

SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart

miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(

SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done

datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)

Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>

datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...

XT1955-5 bootloader unlock install TWRP & Root with Magisk

So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear

Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.

Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------
toxinburn said:
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
Click to expand...
Click to collapse
I am gonna check one thing I had it all working another method before but after installing something thru magisk it soft bricked I think it was vanced youtube maybe also cant seem to find a way to get vipre to work sadly.

Question
Does this method bypass the screen lock password on the phone? I have this phone that is locked with a passcode, so I can't easily get it into developer mode. Sorry, I'm a total newbie to this but am trying to learn. Thanks in advance!

A tip for linux users. If you are getting "< waiting for any device >" after the "fastboot oem get_unlock_data". Ctrl-c to exit the command. Su to root and then "fastboot oem get_unlock_data".

I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone

Hyoretsu said:
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Click to expand...
Click to collapse
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?

Linux-Lord said:
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
The thing is, "stopped working" literally, it doesn't have out of service, phone number, no signal, not even the "emergency calls only", heck I can't even find my IMEI in settings nor *#0606#, I think that's what's causing the problem. This SIM also came from that Custom ROM device (originally inserted there, but bought as a standalone data plan)
Linux-Lord said:
and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
If you're talking about how it showed up like that on the G7 Play it used to work just fine in there, and no, that's not the original phone, it's just a phone I used to test if my SIM was still working
Linux-Lord said:
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
Click to expand...
Click to collapse
In this phone, G7 Power, it doesn't even recognize a card is in the tray anymore (unlike the G7 Play which at least knows there's one and G5+Custom ROM, in which it works)
Linux-Lord said:
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Click to expand...
Click to collapse
Not that it's gonna help much but OI (Brazil), and if that's on Motorola support page my G7 Power is main phone already.

Is the force encrypt disable necessary? And what does it do?

So, I have successfully rooted my Moto G7 Power by using the method above, but i tried not doing the "format data" and fortunately, I have rooted my phone. For the 1st attempt, I kinda soft-bricked my device by doing the steps briefly, my phone would always bootloop back to recovery mode, but after not doing the "format data" step, it led to a success. So for anyone who are currently experiencing bootloop, flash the stock firmware to your phone and root it again by using the method above but don't do the "format data" step. (flashing the stock firmware would not re-lock the bootloader, so you can try to root your phone again easily.)

error
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
---------- Post added at 08:07 AM ---------- Previous post was at 07:49 AM ----------
gladiatorbong said:
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Click to expand...
Click to collapse
same here

brokenlocked22 said:
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
Click to expand...
Click to collapse
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)

Hyoretsu said:
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Click to expand...
Click to collapse
same thing as always.. no matter what lol

brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
If it's same thing as always then you're still using "adb push magisk adb push Magisk-v20.1(20100).zip /tmp/". There's no "but I'm not", if it's indeed the same error as before you're messing up on the syntax. Make sure you've put Magisk inside Minimal ADB folder, rename it to magisk.zip and run "adb push magisk.zip /tmp/"

why is magisk pushed to tmp and not to internal storage . Why not just push magisk to internal sotrage and just install that way through twrp or that wont work. just wondering.

Anyone tried this on XT1955-4?

dirtyscout said:
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
IM a bit confused should I flash a fresh installed firmware first right after i unlock the boot loader?
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.

[Redacted]

Excellent guide, rooted my Moto G7 from Metro PCS.

brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
I LOVE IT!!! :good:

How to flash stock firmware on my XT2045-2?

Recently I rooted my Moto G8 (XT2045-2) phone, booted up TWRP and tried to install LineageOS. But somethign went wrong (I don't know what exactly) and my phone only booted into bootloader mode.
So now I am unsuccessfully trying to restore the stock firmware.
I downloaded the firmware (version RAV_RETAIL_10_QPJS30.63-35-1-15_subsidy-DEFAULT_regulatory-DEFAULT_CFC) and tried flashing it by doing the following commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
Every single one of those commands completed successfully, but booting the phone still only gets me to the bootloader screen.
Trying to boot into recovery mode also just gets me to the bootloader.
Next I tried to just flash TWRP by doing:
Code:
fastboot flash recovery twrp-3.4.0-0-rav-test6.img
.
Command completes successfully, but booting into recovery mode afterwards still only gets me to the bootloader screen.
I can boot into TWRP via
Code:
fastboot boot twrp-3.4.0-0-rav-test6.img
.
Any idea what the problem is with my phone?
Or what my next step could be to salvage this phone?

You have to be in fastbootd mode when you flash firmware. Try this out from the bootloader...
Code:
fastboot reboot fastboot
That should switch you to fastbootd mode. If it doesn't, then boot up twrp, and from the menu select reboot>fastboot.

Thanks.
When I try
Code:
fastboot reboot fastboot
I just get
Code:
fastboot: usage: unknown reboot target fastboot
TWRP also doesn't show me fastboot option.
The only reboot options I have are:
- System
- Power Off
- Recovery
- Bootloader
- Edl
- Slot A
- Slot B
Any other ideas?

Try updating fastboot/adb.

Spaceminer said:
Try updating fastboot/adb.
Click to expand...
Click to collapse
Thanks, I got one step further with that.
The command actually went through but the phone just booted in normal bootloader mode again and i got the following error:
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

Chaos156 said:
Thanks, I got one step further with that.
The command actually went through but the phone just booted in normal bootloader mode again and i got the following error:
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
That sounds promising. Try this... Flash your stock recovery then rerun that command.

.

Spaceminer said:
That sounds promising. Try this... Flash your stock recovery then rerun that command.
Click to expand...
Click to collapse
Flashing the stock recovery did not work. it said the flashing process was successfull, but the phone still only boots into bootloader mode when I try to boot recovery after flashing.
The following got me into fastbootd though:
Code:
fastboot boot recovery.img
Where recovery.img is the stock recovery.
I tried flashing the stock ROM in fastbootd mode and at first it seemed to be successfull. No error messages.
But rebooting afterwards just gets me back into bootloader mode. Neither system nor recovery are booting.

I think that I have an idea that will work. Boot up twrp. Unzip this and copy the entire folder to /sdcard/TWRP. Then use twrp to restore this recovery image. (The backup name is "z") After that reboot to recovery and see if it works. If it does, then use stock recovery to switch to fastbootd, and try flashing your firmware again.

I unzipped and copied the BACKUP to /sdcard/TWRP.
But sadly I encountered the next problem almost immediately.
My TWRP restore screen looks like this:
{
"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"
}
The only "package" to restore was the empty cache folder.
I tried to switch the storage, but the Micro SD card option and the USB Storage option were not selectable at all.
Next I used TWRPs file manager to copy the BACKUP from sdcard to /cache. Had no luck with that though either.
The cache folder on the Restore screen was still empty.
I selected the cache package just to see what would happen if I try to restore it.
The following happened:
The stuff below [RESTORE STARTED] are the error messages for the restore process.
All the error messages above happen every time i boot into TWRP.

@Chaos156
I'm not sure what to make of that but I have a few ideas. It looks like /data is trashed in some way.
Idea #1
Boot twrp, then wipe>format>type "yes" to continue. Then reboot directly to the bootloader, and from there, boot up twrp again and try restoring that recovery image.
Idea #2
Boot twrp. Rename recovery.emmc.win to recovery.img and try directly flashing it using twrp's install image option.
Idea #3
Also grab the latest twrp from Vache and try using that. I believe we're up to twrp 3.5.0. It should be posted in the development threads.

I got the newest TWRP and did the format/wipe. I think that fixed 50% of my problem!
I no longer get the "failed to mount /data" errors. But the "Failed to mount /metadata" errors continue.
Any idea on how to fix the metadata partition too?
Installing that image didn't work. The installation went well, but after rebooting I was just back in bootloader mode.

Chaos156 said:
I got the newest TWRP and did the format/wipe. I think that fixed 50% of my problem!
I no longer get the "failed to mount /data" errors. But the "Failed to mount /metadata" errors continue.
Any idea on how to fix the metadata partition too?
Installing that image didn't work. The installation went well, but after rebooting I was just back in bootloader mode.
Click to expand...
Click to collapse
From the bootloader try,
Code:
fastboot erase metadata
Edit: If that doesn't work, try it with twrp using fasbootd.

I erased the metadata, but even after flashing an image it just boots into bootloader mode still.
I tried it twice; once from bootloader and once from TWRP fastbootd.
It says your image was flashed successfully but it still doesn't boot afterwards.
The metadata partition errors also still persist.
I can also no longer boot the stock recovery via "fastboot boot stock_recovery.img". It just shows the "No command" error. Same if I try to boot your recovery.img directly via "fastboot boot recovery.img".

You can try to run BlankFlash to fix it

Chaos156 said:
I erased the metadata, but even after flashing an image it just boots into bootloader mode still.
I tried it twice; once from bootloader and once from TWRP fastbootd.
View attachment 5212679
It says your image was flashed successfully but it still doesn't boot afterwards.
The metadata partition errors also still persist.
I can also no longer boot the stock recovery via "fastboot boot stock_recovery.img". It just shows the "No command" error. Same if I try to boot your recovery.img directly via "fastboot boot recovery.img".
Click to expand...
Click to collapse
This is probably your best bet at this point. In order for fastbootd to work, you need either twrp or the stock recovery to flash properly to the recovery partition. You should be able to install the stock recovery from the bootloader since it's not a dynamic partition. Then just reboot into fastbootd and get it fixed up. For some reason, that doesn't seem possible. So I'm not sure what's going on with your phone at this point. Scope out lolinet. They probably have a blank flash for our device. If not, let me know and I'll trying digging one up from some folks on the gsmhosting forums. If you need QPST utilities to run the blank flash, also let me know and I'll link it.

lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

I found the blank flash on lolinet and it included the qboot utility version 3.86.
I tried using the bash script :
Code:
./blank-flash.sh
But it just just said "< waiting for device >" without ever detecting my phone.
Calling "./qboot devices" directly did not list my device where both "fastboot devices" and "adb devices" found my phone.
I tried searching for qboot to see if a newer version than 3.86 might exist, but I can't find any source for qboot at all.

Did you run from bootloader, fastboot oem blanklash

Chaos156 said:
I found the blank flash on lolinet and it included the qboot utility version 3.86.
I tried using the bash script :
Code:
./blank-flash.sh
But it just just said "< waiting for device >" without ever detecting my phone.
Calling "./qboot devices" directly did not list my device where both "fastboot devices" and "adb devices" found my phone.
I tried searching for qboot to see if a newer version than 3.86 might exist, but I can't find any source for qboot at all.
Click to expand...
Click to collapse
You need to be in EDL (emergency download mode) to use a blank flash. Try booting twrp and check the reboot options. It should be there. I'm just not sure if it'll work. If it does work, it might not look like anything is going on. My G7 play in EDL mode, just had a black screen and looked like it was turned off, but the backlight was on. When connected to my PC, it appeared as something like QHUSB in my device manager.