Related
So I got my Kindle Fire a few months ago, already rooted. I went from TWRP to a CWM-based recovery, and I've been installing ROMs ever since without any issues. I'm currently running a CM9-based ROM, and I decided to play around with the softkeys, because I was tired of the bland white look. So I found some custom softkeys and flashed the .zip. I made sure to make a Nandroid before flashing, of course.
Upon rebooting from the flash, my KF got stuck in a bootloop. No biggie, this has happened before. I shut it down and rebooted to recovery, to restore the backup. But when it boots into recovery, it automatically reflashes the softkeys zip, and then reboots into the never-ending bootloop.
So the KF isn't necessarily bricked, I just can't get into recovery without it flashing a corrupted zip. I've tried two different unbricking tools, neither had any effect on it. Any ideas?
Can you mount SD card in Recovery and delete the Zip file through your PC?
linktohack said:
Can you mount SD card in Recovery and delete the Zip file through your PC?
Click to expand...
Click to collapse
I only wish I could. As soon as I boot into recovery, it flashed the zip, then reboots into the bootloop. I suspect this happens because I used ROM Manager to flash the zip, and recovery hasn't reset itself because the device isn't booting up all the way. So every time I try to access recovery, it performs the last action I gave it, which was to flash the zip.
I hope you aren't using Hashcode's (older) CWMR or you might be looking at a much larger problem.
http://forum.xda-developers.com/showthread.php?t=1651413
I'm not sure what's going on with your device, but the only way I know to get the recovery to do something on start up is to create a /cache/recovery/command file. That file should be a one time use command and get deleted after use, so your report of it happening each time you boot into recovery is puzzling.
If you want to take that out of the equation, I think you should either get to a shell prompt and delete the file manually or erase the cache partition entirely. Try getting to fastboot mode, boot a copy of the TWRP image, and hopefully it won't reboot on you automatically so you can use adb shell. Alternatively, erase the cache partition entirely with fastboot. If you do the latter, you'll probably need to remake the ext4 filesystem on the cache partition. Here are some fastboot references to get you started...
http://forum.xda-developers.com/showthread.php?t=1668159
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
kinfauns said:
I hope you aren't using Hashcode's (older) CWMR or you might be looking at a much larger problem.
http://forum.xda-developers.com/showthread.php?t=1651413
I'm not sure what's going on with your device, but the only way I know to get the recovery to do something on start up is to create a /cache/recovery/command file. That file should be a one time use command and get deleted after use, so your report of it happening each time you boot into recovery is puzzling.
If you want to take that out of the equation, I think you should either get to a shell prompt and delete the file manually or erase the cache partition entirely. Try getting to fastboot mode, boot a copy of the TWRP image, and hopefully it won't reboot on you automatically so you can use adb shell. Alternatively, erase the cache partition entirely with fastboot. If you do the latter, you'll probably need to remake the ext4 filesystem on the cache partition. Here are some fastboot references to get you started...
http://forum.xda-developers.com/showthread.php?t=1668159
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
Click to expand...
Click to collapse
Thanks for all that, but I managed to fastboot into it, and then wipe system and data. Then I rebooted to recovery and restored my backup. Never fastbooted into a device before, or done anything with adb commands, so it was a fun experience.
same symptoms: KF bootlooping, no recovery
Hi there,
I have a rooted/modded KF with MIUI, FFF 1.4a and TWRP.
After I gave it away to someone, who only "used it", it is now stuck in a bootloop.
I can get into fastboot via fastboot.exe and re-flashed FFF and TWRP, but no change: KF boots with the white/blue logo, I can press the powerbutton to get into recovery, but TWRP doesn´t show up. When I boot normally, it looks the same: Black screen after a few seconds.
I read about the battery issues, so I booted the KF with a fastboot command waiting to the device. The white/blue KF logo showd up and I left the device at the USB port at my PC for a complete night: no change
I tried to set another bootmode via fastboot.exe but the code doesn´t seem to make any difference.
I have a second KF which runs just fine (now with AOKP M5.1).
Is it bricked now?
Elviz42 said:
Hi there,
I have a rooted/modded KF with MIUI, FFF 1.4a and TWRP.
After I gave it away to someone, who only "used it", it is now stuck in a bootloop.
I can get into fastboot via fastboot.exe and re-flashed FFF and TWRP, but no change: KF boots with the white/blue logo, I can press the powerbutton to get into recovery, but TWRP doesn´t show up. When I boot normally, it looks the same: Black screen after a few seconds.
I read about the battery issues, so I booted the KF with a fastboot command waiting to the device. The white/blue KF logo showd up and I left the device at the USB port at my PC for a complete night: no change
I tried to set another bootmode via fastboot.exe but the code doesn´t seem to make any difference.
I have a second KF which runs just fine (now with AOKP M5.1).
Is it bricked now?
Click to expand...
Click to collapse
I'm not an expert on the KF, but from what you've described, I don't think it's bricked. Have you tried fastboot wiping system and data?
Mardenator said:
I'm not an expert on the KF, but from what you've described, I don't think it's bricked. Have you tried fastboot wiping system and data?
Click to expand...
Click to collapse
I just did:
D:\root>tools\fastboot erase system
erasing 'system'... OKAY [ 51.245s]
finished. total time: 51.246s
D:\root>tools\fastboot erase data
erasing 'data'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
D:\root>tools\fastboot erase userdata
erasing 'userdata'... OKAY [108.555s]
finished. total time: 108.577s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.001s
D:\root>
I tried to get into Recovery but no change.
Maybe it's a problem with TWRP. Have you tried fastboot flashing a CWM-based recovery?
Doesnt sound like you have twrp installed or its broken just resend twrp it should overwrite whatever is there
Thepooch said:
Doesnt sound like you have twrp installed or its broken just resend twrp it should overwrite whatever is there
Click to expand...
Click to collapse
He might want to fastboot erase recovery and then reflash TWRP.
I tried CWM:
D:\root>tools\fastboot flash boot recovery\fff.bin
sending 'boot' (243 KB)... OKAY [ 0.065s]
writing 'boot'... OKAY [ 0.052s]
finished. total time: 0.117s
D:\root>tools\fastboot flash recovery recovery\cwm.img
sending 'recovery' (5198 KB)... OKAY [ 1.321s]
writing 'recovery'... OKAY [ 1.418s]
finished. total time: 2.740s
D:\root>tools\fastboot oem idme bootmode 5001
... OKAY [ 0.667s]
finished. total time: 0.668s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.002s
D:\root>
No change, same behavior: Starts with white/blue letters and than "off". Entering recovery is not working.
Are you pushing the power button several times quickly when you see the white kindle blue fire and selecting recovery?
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
You need to select with the power button or the new fff will just tell it to boot normal also twrp is better if you intend to flash anything ics related
Thepooch said:
Are you pushing the power button several times quickly when you see the white kindle blue fire and selecting recovery?
Click to expand...
Click to collapse
Yes. I also tried to enter recovery just by setting bootmode to 5001 with fastboot. This didn´t work either.
Try setting the bootmode to normal then use the power button to toggle to recovery after reflashing twrp also how your flashing them is incorrect
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
fastboot -i 0x1949 flash recovery <file path> <name of recovery>
fastboot -i 0x1949 flash bootloader<file path><name of bootloader>
not fff.bin to recovery as you are doing but to bootloader
D:\root>tools\fastboot flash boot recovery\fff.bin
sending 'boot' (243 KB)... OKAY [ 0.065s]
writing 'boot'... OKAY [ 0.052s]
finished. total time: 0.117s
this one is really wrong your flashing the bootloader to the recovery partition dunno your doing something strange and thats your issue
you may wanna use firekit to get your bootloader and recovery correctly sent to avoid further issues http://forum.xda-developers.com/showthread.php?t=1430038
or like this leaving the id out
fastboot flash bootloader \path\to\fff.bin
fastboot flash recovery \path\to\twrp.img
Hi,
i did flash fff.img to boot(loader) , and after that CWM.img to recovery. But the image is in a folder called "recovery", perhaps this was confusing.
you wrote that you flashed it to boot not bootloader but yes its confusing
try again after an erase I guess
fastboot erase bootloader
fastboot erase recovery
or with the id -i 0x1949
Did that, no success:
D:\root>tools\fastboot getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
D:\root>tools\fastboot erase bootloader
erasing 'bootloader'... OKAY [ 0.511s]
finished. total time: 0.512s
D:\root>tools\fastboot erase recovery
erasing 'recovery'... OKAY [ 2.429s]
finished. total time: 2.429s
D:\root>tools\fastboot flash bootloader recovery\fff.bin
sending 'bootloader' (243 KB)... OKAY [ 0.065s]
writing 'bootloader'... OKAY [ 0.052s]
finished. total time: 0.117s
D:\root>tools\fastboot flash recovery recovery\openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)... OKAY [ 1.404s]
writing 'recovery'... OKAY [ 0.543s]
finished. total time: 1.947s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.001s
D:\root>
ok unplug it then hold your power button down for 1 min then power it on use power button to toggle to recovery option in boot menu see what you get if that doesnt work redownload twrp img and send that again without erase also there is a small chance you could be remaining in fastboot but I doubt it try select reset bootmode as well but you have no system at this point so getting to recovery is imperative
What does "fastboot boot twrp.img" do for you?
Running fastboot on my HOX and getting this result:
Code:
C:\Users\Michael\Documents\Handheld\Android\fastboot>fastboot format system
formatting 'system' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.143s
Same happens with data and userdata.
Terrarist said:
Running fastboot on my HOX and getting this result:
Code:
C:\Users\Michael\Documents\Handheld\Android\fastboot>fastboot format system
formatting 'system' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.143s
Same happens with data and userdata.
Click to expand...
Click to collapse
Ofcorse will fail no comanf fastboot format system only fastboot flash recovery recovery.img and for the boot fastboot flash boot boot.img, fastboot erase cache and some minnor commands if you want to format system do it from custom recovery
Thant said:
Ofcorse will fail no comanf fastboot format system only fastboot flash recovery recovery.img and for the boot fastboot flash boot boot.img, fastboot erase cache and some minnor commands if you want to format system do it from custom recovery
Click to expand...
Click to collapse
This is a big problem. I've got the burnt out IC that blacks out the screen so unless I connect to a monitor I can't see anything. And I have a working MHL cable but it doesn't work in recovery or bootloader mode. Sweating profusely now
I try updating via abd, Now hard brick, as it cannot update boot.img
Use Vol Down + Power to attempt to get to bootloader, it boot the Teamwin screen this reboot back Google logo then reboot back to Teamwin screen again, cannot get into trwp at all.
On the Teamwin sreen it saying wiping something, but I cannot read it quick enough.
Abd No luck as well, help please.
Can you please explain what to do now, I would greatly appreciate your help, or I going to throw it in the bin.
Edit: Managed to get into Bootloader now problem below
C:\adb>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.138s]
writing 'bootloader'...
OKAY [ 1.426s]
finished. total time: 1.570s
rebooting into bootloader...
OKAY [ 0.012s]
finished. total time: 0.016s
error: update package missing boot.img
Press any key to exit...
I check the zip file it has boot.img inside it?
Ok how to flashboot manually as I've unpack the zip what the procedure?
Ok I found flash manual.bat
Here the script:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-flo-flo-04.05.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
exit
echo Press any key to exit...
pause >nul
exit
Anyway cross fingers I rebooting now, and hope to see Android I let you in 15 minutes,
Well it won't boot into Android 6? what now?
right got it going again when back to mra58k, i found nrt 2.06 has issue which cause my problem in the first place.
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Thank you very much. I will try it.
BL1ND4D0 said:
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Click to expand...
Click to collapse
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
[email protected] said:
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
tys0n said:
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
Click to expand...
Click to collapse
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
[email protected] said:
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
Click to expand...
Click to collapse
Did you follow all instructions from twrp thread. like flashing modified vbmeta and wipe data before booting twrp?
Also take a look at the original thread for one vision as it has a newer zip that contains only one modified vbmeta.img instead of two different ones in the older zip that is posted in one action's twrp thread.
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
goofball2k said:
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
Click to expand...
Click to collapse
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
[email protected] said:
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
Click to expand...
Click to collapse
You don't need to modify vbmeta.img. I am using the older version of the root Moto Vision package, which has a vbmeta.img file, and a patched vbmeta.img file.
For the modified boot img, I downloaded the full image from https://mirrors.lolinet.com/firmware/moto/troika/official/
Extract, and then take the boot.img file, you will want that saved to a phone that has Magisk installed.
Follow these instructions to patch
https://www.ytechb.com/how-to-patch-a-file-in-magisk-manager/
Once you have that, you will want that patched file into the fastboot directory on your computer. You will also want the vbmeta and the patched vbmeta img files (from the root moto vision package) in this directory. I have not used the updated version, I am using the older. I don't know about using the newer package which only has 1 vbmeta file.
Put your phone into fastboot mode.
Flash the vbmeta.img file, then the magisk patched boot file, then the vbmeta patched file. Then do a fastboot wipe of the phone.
Reboot the phone.
Set it up again, install magisk manager, then open it, and it should ask to configure. Let it do that, it should reboot and after that, you should be rooted.
[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Thank you
binary**# said:
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Click to expand...
Click to collapse
Thank you very much for your input.
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Polnareff said:
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Click to expand...
Click to collapse
You aren't flashing, your command is trying to boot from vbmeta.img. You are missing the flashing command.
Redmi note 8 (unlocked bootloader) stuck on "Your system has been destroyed" (I was trying to install PixelExperience 12, but was not able to boot into the PitchBlack recovery itself). Unable to boot to recovery or fastboot (no button combination is working).
If connected via USB (while just charging too), it just keeps rebooting & shows "Your system has been destroyed".
When disconnected from external power supply, it shuts down automatically after a few seconds, but when I try to boot into the bootloader (or try to turn it on), it again goes to the system destroyed screen.
Here are the set of commands I ran just after unlocking the bootloader:
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.404s]
Writing 'recovery' OKAY [ 0.385s]
Finished. Total time: 1.824s
PS D:\Android\ADB> ./fastboot boot ginkgo_recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 1.391s]
Booting OKAY [ 0.148s]
Finished. Total time: 1.591s
PS D:\Android\ADB> ./fastboot devices
97900a40 fastboot
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.414s]
Writing 'recovery' OKAY [ 0.381s]
Finished. Total time: 1.808s
PS D:\Android\ADB> ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.003s
PS D:\Android\ADB> ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PS D:\Android\ADB> ./fastboot devices
PS D:\Android\ADB> ./fastboot devices
What I believe is that I forgot to disable vbeta verification before flashing the new recovery (when I tried flashing a new recovery in my POCO, I got an error regarding this, but this time none of that happened). Is there any way to do it now? without having to go into EDL mode & stuff?
Rocker_2102 said:
Is there any way to do it now? without having to go into EDL mode & stuff?
Click to expand...
Click to collapse
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
loopypalm said:
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
Click to expand...
Click to collapse
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Rocker_2102 said:
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Click to expand...
Click to collapse
did you try the comand while "system destroyed" is displayed ?
No.. but I tried connecting using adb and it did not work. I think I event tried "fastboot devices" which too didn't show anything .
But I'll try again now to confirm this.
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Rocker_2102 said:
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Click to expand...
Click to collapse
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
loopypalm said:
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
Click to expand...
Click to collapse
It wasn't my phone so just bringing it back to working condition is pretty awesome for me . On my phone I keep trying new ROMS (just tried Projet Elixir)
bro how did you booted into fastboot i also in same situation
how did you fixed i also in same situation
Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
same here, it's not booting to fastboot even tho I tried the combination when "Your system has been destroyed" was displayed ;-;
Rocker_2102 said:
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Click to expand...
Click to collapse
I got it to working condition this way only, unfortunately.