Hi
Have anyone faced this before? yesterday i updated the viper4android from magisk and when reboot i got stucked on bootloader warning, android wont boot. After few reboots and turn the phone off, it still the same. So i imagined doing a full wipe and clean install everything will make the device usable, BUT... it persist and now my device is somehow tethered. I cannot boot to android without fastboot commands or otherside i wil get stucked forever on bootload warning, some things i tried is flash magisk from 16.4 to 16.7, clean install rom, install only rom and gapps only, not flashing any external kernel.
crazy uh? now everytime i reboot or turn off the phone, i have to use fastboot to get into android, not aways I will have computer nearby to send:
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot reboot
I can get to twrp recovery and fastboot, maybe there is a fastboot commands to "untether" my phone?
Model: xt1802
Current flashed rom: xtended x9
Current kernel: arsenic r4 (early mount)
Related
Hi, picked up my Urbane 6C55 (build LCA44B) yesterday and today have oem unlocked and then did a fastboot flash recovery of twrp-2.8.7.0-bass.img; two issues:
1. Internal storage is showing as 0 in TWRP so can't do a backup;
2. More worrying is the watch only boots into TWRP now, even when doing reboot system!
I reflashed the stock recovery and thankfully after that long first boot I'm back into a usable watch, but would like to get TRWP installed and skin1980's custom kernel...
What am I doing wrong as I've followed the instructions here http://forum.xda-developers.com/watch-urbane/development/everything-urbane-root-how-tos-files-t3243975?
When I did the fastboot oem unlock the device didn't reboot (as per above instructions), it wiped and stayed in bootloader - LOCK STATE shows unlocked , but SECURE BOOT is enabled, is that related (I haven't seen any reference to Secure Boot so not sure)??
I've answered my own question In case anyone else does the same as me the steps should have been:
1. fastboot oem unlock
2. REBOOT WATCH (as oem unlock doesn't reboot by itself)
3. adb reboot bootloader
4. fastboot flash recovery
5. reboot to bootloader and select recovery to boot into TWRP
6. do a backup and reboot into the OS as normal
If you have some difficulties finding fastboot rom for some G5S+ variant, I suggest using Lenovo Moto Smart Assistant (LMSA). You can download it from here and install on your PC.
How to download latest specific stock fastboot rom for your G5S+
You must:
Using stock rom (locked or unlocked bootloader).
Install Lenovo Moto Smart Assistant on your PC.
Restore stock firmware, recovery, and boot image (if you changed it before).
Steps:
Reboot your phone to bootloader.
Open "Lenovo Moto Smart Assistant".
Connect your phone to PC using the USB cable.
Choose "Flash" menu on LMSA.
Choose "Moto Phone".
Choose "Moto G Plus (5th Gen S)".
Choose your phone models.
Wait for a minute while LMSA checking your phone, and then choose "Rescue". It will download the latest 1.5+ GB stock fastboot rom based on your phone model. You can find it on "C:\ProgramData\LMSA\Download\RomFiles".
Click "Rescue" to flash latest rom and accept some confirmations. Your phone will be rebooted after flashing process completed.
Now your phone is back to stock rom. Of course, if you have unlocked it before, those steps wouldn't lock your bootloader. If you want to lock it, I suggest you do it immediately after flashing process completed.
Here to lock your phone after successful stock rom restoration.
You must:
Have ADB fastboot driver installed.
Get extracted fastboot rom from "C:\ProgramData\LMSA\Download\RomFiles".
Steps
Reboot to bootloader.
Open "Command Prompt" on your PC, and go to the location of extracted fastboot rom.
Connect your phone to PC using the USB cable.
Check first that your phone is connected using "fastboot devices" command.
Do all below commands in sequence:
Code:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
Your phone will be restarted. There will be no unlocked bootloader message anymore. And you'll have your phone locked. Ta-da .
Note:
Check "system.img_sparsechunk.x" files (where "x" is sequential numbers) in extracted fastboot rom folder. Newer rom may have more files than the older one. You must flash ALL those "system.img_sparsechunk.x" files in sequence.
If you have issues, please share here. Thanks are appreciated.
I did all above steps but my G5 plus is still saying it has an unlocked bootloader with a ID: Invalid key error.
My phone simply avoids the bootloader to be relocked... it's just pure garbage...
What is the reason for relocking the bootloader? You don't get the warranty back...
should i setup my devices and come back to bootloader or without setup please clear this
thanks in advance
Will Moto Smart Assistant also work for the G7 (Play)?
Motorola support sais no (and that there is no way at all to restore the images after unlocking the bootloader)... will try to find out myself later today.
And another question, do people have experience with updating Motos via Moto Smart Assistant? Reason is that latest models (G7) do not allow for OTA updates with bootloader unlocked. Am wondering if it will still be possible via the Smart Assistant - provided that works at all
Does it require only stock rom?
Can i flash the stock rom using lenovo smart assistant when the phone is with custom rom?
Tried it all, but no good news.
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Install Pixel Experience ROM
voliveira92 said:
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Click to expand...
Click to collapse
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Abhimlv12345 said:
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Click to expand...
Click to collapse
hello i was looking around to fix my revvl xt-1952-t ( motola g 7)
its stuck in boot loop flashing bad key ( always had bad key since unlocking the phone. )
i have done a couple roms on samsung devices and never on any thing else .
fast boot is some what new to me. i love it vr oden installs . so i went to reinstall
stock rom on a extra phone
and didnt not get it to load i have whipped and reinstalled 4 tines checked the models var etc seems like it is all correct . is there any ideas or tricks i could be missing
I think i did it without flashing the sparsechunk
I just flashed the latest AEX, Pico GApps & Gabriel Kernel. There were no error message in the TWRP. I then wiped cache and then rebooted it. Suddenly my phone stucks at Fastboot logo.
I tried press the power button & recovery combo multiple time but it will always comes back to Fastboot logo. I can't turn it off at all, I can't reboot it to the system, I can't boot it to TWRP either. Nothing works.
I tried booting it using fastboot on computer. Tried using
Code:
fastboot flash recovery twrp_name.img
command. It succesfully flashed the twrp. But when I try to boot to TWRP using the
Code:
fastboot boot twrp_name.img
] command, it always fails. The error messages are either
Code:
FAILED (Status read failed (Too many links))
or
Code:
FAILED (remote: 'dtb not found')
Tried some other commands like
Code:
fastboot reboot bootloader
but they always come back to the Fastboot logo screen. The Fastboot has also been unlocked.
What should I do? Anyone has an idea? It's been more than an hour and everyone I asked no one has a clue how to solve it.
flash miui stable rom through fastboot
Download stock miui fastboot image from official miui website.
Extract the zip. (7zip Preferred)
Extract the file inside it. (If any)
Select clean_all.bat
Wait till the process completes.
Reboot.
This will fix the issue.
Dont flash ROM + Gapps + Kernel all together.
Just flash ROM and Gapps let first device boot after setting device later flash kernel.
I have a problem
I just tryed to install last firmware
(first installed RMX1931EX_11_OTA100,
Flash vbmeta.img in vbmeta and reboot,then Flash Magisk fron canary(//github.com/topjohnwu/magisk_files/blob/canary/magisk-debug.zip))
Evrything going ok witout any error but after reboot I'm in bootloop just relame logo and then start twrp recovery.
then I erase all data with wipe+yes from twrp,my phone only restar in OS without any posibility to go into fastboot.
"PS C:\adb> adb devices
List of devices attached
ce8bf9af recovery
they find phone,but when I try to use adb just folowing message:
PS C:\adb> fastboot + any command
< waiting for device >"
Phone bootet normaly in OS but it is not posible to get fastboot mode or boot into twrp recovery.
Magisk working and Official TWRP app to.
I find over youtube video this boot.img "https://www.youtube.com/watch?v=4wsa81bG6II"
can something like this resolve my problems.Maybe to flash some boot. Img over twrp official app?????
Any sugesstion.
Thanx
You did adb reboot bootloader first and then try fasboot reboot recovery ?
that I know vbmeta should be flashed last
also check if magisk are u usiing need a fix
slicuga said:
I have a problem
I just tryed to install last firmware
(first installed RMX1931EX_11_OTA100,
Flash vbmeta.img in vbmeta and reboot,then Flash Magisk fron canary(//github.com/topjohnwu/magisk_files/blob/canary/magisk-debug.zip))
Evrything going ok witout any error but after reboot I'm in bootloop just relame logo and then start twrp recovery.
then I erase all data with wipe+yes from twrp,my phone only restar in OS without any posibility to go into fastboot.
"PS C:\adb> adb devices
List of devices attached
ce8bf9af recovery
they find phone,but when I try to use adb just folowing message:
PS C:\adb> fastboot + any command
< waiting for device >"
Phone bootet normaly in OS but it is not posible to get fastboot mode or boot into twrp recovery.
Magisk working and Official TWRP app to.
I find over youtube video this boot.img "
"
can something like this resolve my problems.Maybe to flash some boot. Img over twrp official app?????
Any sugesstion.
Thanx
Click to expand...
Click to collapse
I have a fix for this , either try linux software , there it will work 100% device will be detected in fastboot mode , another method is to try luck with the usb drivers provided by the official realme flashtool and make sure if you are using desktop then don't plug your device in cabinet usb port, plug it into motherboard , as i had past issues with cabinet usb port and it worked perfectly with motherboard usb port ...
Some drivers don't seem to work with cabinet usb ports , but they very well work with motherboard usb ports !! So give it a try ....
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
same problem here... were you able to fix it?
You might have to use the QFIL method to get your phone going again. Remember you MUST backup the EFS partition and anything associated with your phones imei and SN
Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
flash the boot partition then flash stock recovery then try to flash twrp then try to flash a custom or stock rom what you want.
Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
Anyone solve this problem?
Juninalilla said:
有人解决这个问题吗?
Click to expand...
Click to collapse
这两个可怕的重锁码吓了我一跳,以为手机没电了。幸运的是,我找到了解决方案。你可能需要找个老股rec,跟着视频操作,不用拆机,重点解压。进入adb文件夹,生效
Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...