I would like to know how to enter fastbootd! mode???
Enable the USB debug mode in the Developer options, install adb (it's the part of Android Studio, or as a separate tool for Linux available in the official repos) and execute "adb reboot bootloader".
This is FastBootd! mode ??
{
"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"
}
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
uluruman said:
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
Click to expand...
Click to collapse
so I can install GSI by the dynamic partitions
PaulinoBaslio said:
so I can install GSI by the dynamic partitions
Click to expand...
Click to collapse
Probably. May be. From my experience it simply doesn't work. It sorta flashes something but may be it just takes forever to complete or it's really just stuck but there's no response whatsoever. Fastboot mode is absolutely minimalistic, it does not report anything, no progress, nothing, and I guess it's intended to be like that, because it boots before anything else and theoretically allows you to flash even the very first bootloader. Anyway, I tried something like fastboot flash system lir-v316-220325-arm64-bvZ.img and the CLI tool reported Sending 'system' and then nothing else happened for the next 15 minutes or so, after which I just hit Ctrl+C, ran fastboot reboot and observed that nothing changed, the old system booted just like it was, so I guess nothing was really flashed, even partially. I don't know really, may be it's unpacked internally only when the image is fully uploaded and I didn't give it enough time, but for that time Odin would already flash the whole set of firmware. What else is to try, besides waiting more time, is converting the image to/from Android sparse format using the img2simg & simg2img tools, and try other partition names, such as "system_root" but I am sure this latter thing is absolutely wrong. The GSI system partition is called system, it just must be called that, system_root is something else (I guess it's the system root of the recovery mode).
Related
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"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"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma
Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.
Facing the same issue. Tried everything but no success.
After a bunch of research I finally decided to take the plunge to try and move to Lineage OS.
Phone is a Google unlocked 128GB 2 XL.
I was able to get through the unlock portion but after that all the guides went different directions. I was following the process from TWRP and at one point had the TWRP recovery app showing via fastboot but now all I get is the "device is corrupt" warning which then ends up in the white screen with Google logo and small unlocked icon.
Any chance I can get back to scratch or press forward to LineageOS/other ROM or is this thing a brick?
*Update* Not sure what key combination I used but I can get to the following TWRP screen. However the touchscreen does not respond and after the screen hibernates any key returns it to this 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"
}
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Strephon Alkhalikoi said:
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Click to expand...
Click to collapse
Not sure how I can do that.
I can get to the default green START option. If I selection that the system boot to a white screen adn stops.
If I select BOOTLOADER the device pops back to the green START.
If I select RECOVERY it gets to the TWRP screen but the touchscreen nor buttons work.
I've tried connecting the phone via USB to my PC but no matter what mode I put it in ADB never detects it.
The "green Start" is where you want to be here. That's the bootloader. You need to make sure the driver - assuming Windows - is set to ADB Bootloader Interface in Device Manager as well as make sure you have the latest version of the ADB / Fastboot package.
I've got a 65-inch 4K Funai/Philips Android TV. Is this TV rootable or flashable? The OS is so laggy on this device it makes it almost unbearable to use. Opening specific screens takes seconds because of all the quirky animations. I'd much rather prefer flashing a different version of Android TV that doesn't lag any time I scroll to the next app on the home screen.
I have successfully unlocked the bootloader through fastboot. I'm not experienced to go any farther than that though.
Originally,
Code:
fastboot flashing get_unlock_ability
returned "(bootloader) lock"
After running
Code:
fastboot flashing unlock
it appears to unlock bootloader.
It factory resets tv after unlock, and persists through reboots.
{
"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"
}
I'd love nothing more than to get root working on this TV! Any suggestions on what to do next from people smarter/more experienced than me, throw it out there.
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
vincentanzalone said:
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
Click to expand...
Click to collapse
any idea how i go about grabbing the ota firmware or any firmware for my tv ? it's the phillips walmart 75 inch model, i was able to unlock bootloader but mtk client doesn't work with it, no way to get to brom mode to test. want a proper dump before i start essing with anything. Thanks much
vincentanzalone said:
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
Click to expand...
Click to collapse
well, I find myself in a soft brick situation. I cannot get the OTA zip to load from USB, do you happen to have the file as it came or is this it ?
is there any way to fix this
please help me
{
"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"
}
all of my partitions have been lost
IT SHOWS AVAILABLE PARTITIONS: /nothing/
-cant go to recovery mode
-cant go to fastboot mode
-cant go to mtk_gui mode
this happens when trying to get mtk_gui
-cant go to mtk_gui mode
this line just shock me since I have heard MTK cpu is never can be broken...
maybe we should try all manual setting we can attach, is you using tool on win10? I got a lot trouble with that env.
ubuntu 22.04
Python 3.8.10 (default, Mar 15 2022, 12:22:08)
[GCC 9.4.0] on linux
Magisk 22.4
logforjj said:
-cant go to mtk_gui mode
this line just shock me since I have heard MTK cpu is never can be broken...
maybe we should try all manual setting we can attach, is you using tool on win10? I got a lot trouble with that env.
Click to expand...
Click to collapse
it's not the MTK client's problem
I accidentally destroyed all of my partitions
is there any way to recreate all partitions again?
also, I'm so dumb that I tried to do it with the SP flash tool (didn't work) and now I can't even get to this page
now the phone is completely dead and the screen is not turning on.
the only hope is that the phone can be detected by the sp flash tool and mtk_gui (after formating with the sp flash tool)
I'm not doing anything anymore without any advice.
there is no partitions here
The phone turns into a brick after using the MTK client client (GUI) function, please help!
When I click on all the erase options, the client only recognizes them but cannot save me back to the phone. The volume and power buttons are not responding. Please help me!
forum.xda-developers.com
just like me several days ago, In fact I just brick my device again since flash custom rom for UI2.0(jsut wrong), so now I will trace back that thread and replay again, I think it is okay and both of we can revive it as normal, first thing I am going to is reset win10 again since I suppose some security setting just crash SP flash tool make it did not response anything after I use it( despite bypass is going okay).
logforjj said:
The phone turns into a brick after using the MTK client client (GUI) function, please help!
When I click on all the erase options, the client only recognizes them but cannot save me back to the phone. The volume and power buttons are not responding. Please help me!
forum.xda-developers.com
Click to expand...
Click to collapse
I don't understand anything from this page
please make a user-friendly tutorial for me
and also please give me the files you used
and please shere a working firmwere file with real scatter file
EDIT: RESOLVED
I was in TWRP and decided to format-all (checked all the boxes).
Then, for some reason I decided to switch to the other side (Boot_B) and do the same there.
But the TWRP on that side was broken.
And now I'm stuck with no OS installed.
And my PC won't recognize my phone when I plug it in.
I've tried all three of my known-working cables and both of my computers.
Windows Device Manager doesn't see anything being plugged in.
It's not even coming up as an unrecognized device. Windows pretends like I haven't plugged anything in.
So, no ADB device, no Fastboot device, no Qualcomm device, no unrecognized device.... simply NOTHING.
Now the phone just boots to "The bootloader is unlocked" or to the broken (frozen) TWRP where even a USB-OTG mouse won't work.
With phone plugged in:
{
"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"
}
FINALLY got it to boot into fastboot mode!
First, power it all the way off.
Wait a minute then press & hold all three buttons.... Volume (+) & (-) and Power-button until you see fastboot.
And finally my computer sees it.
Cool, and I was able to do a "fastboot set-active a" and then reboot to the properly-working TWRP.
I should be good to go now!
EDIT:
Actually, I still can't get into MSM (nothing in device manager).
And ADB sideload or ROM install from TWRP ends in “kInstallDeviceOpenError”
EDIT 2:
I remembered that TWRP has a "reboot to EDL" option, so I used that and I'm now MSM'ing just fine.
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
EtherealRemnant said:
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
Click to expand...
Click to collapse
I use TWRP for full ROM backup & restore purposes.
And it works fine as long as I don't try to get too fancy.