Related
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
Hi there,
I tried to update my Moto G4 Plus and I think I made some big mistakes..
I can only start into Bootloader with the following text shown below:
AP Fastboot Flash Mode (Secure)
BL: B0.0E (sha-4986429, 2016-104-13 14:23:47)
Baseband: [bla] ATHENE_EMEA_DSDS_CUST
Product/Variant: athene_16mp XT1642 16GB P2A
Serial Number: [bla]
CPU: MSM8952
eMMC: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=5f
Console [NULL]: null
Battery OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
Click to expand...
Click to collapse
- No TWRP or other Recovery
- No OS
- No Fastboot connection to my Win10 64bit anymore (
I think the problem is the "AP Fastboot Flash Mode (Secure)" Mode.
Any ideas how to solve it?!
thanks alot anyway
The AP Fastboot Flash mode(secure) seems okay to me. However it is highly possible that your drivers aren't installed on the phone. So in this case try to first connect the phone to the computer and see if it get's detected or not, and then you should manually install the fastboot USB driver. Download the driver zip from Google's repository and extract it, later choose the .inf file and then the Android Bootloader Interface.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
PS: This driver and the fastboot adb binaries are completely different thing. fastboot won't work unless you have this USB driver.
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
The latest stock ROM is the NPJS25.93-14-10 (Sept 2017 security patch) build https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You'll have to flash the stock ROM in fastboot, which would wipe TWRP off your device again. You cannot properly flash stock firmware in TWRP (only can flash the system in TWRP).
Once you've flashed the stock ROM and TWRP, you can use ElementalX, I'm using the 1.0.4 stock version on the NPJS25.93-14-10 build with magisk 13.3 (to root) and it's running stably on my XT1642.
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
stefanhanz said:
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
Click to expand...
Click to collapse
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
sersrendon said:
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
Click to expand...
Click to collapse
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Rog Ballester said:
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Click to expand...
Click to collapse
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
echo92 said:
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
Click to expand...
Click to collapse
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Rog Ballester said:
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Click to expand...
Click to collapse
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
echo92 said:
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
Click to expand...
Click to collapse
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Rog Ballester said:
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Click to expand...
Click to collapse
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
echo92 said:
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
Click to expand...
Click to collapse
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Rog Ballester said:
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Click to expand...
Click to collapse
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
echo92 said:
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Click to expand...
Click to collapse
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
echo92 said:
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Click to expand...
Click to collapse
You're welcome
Please, in future, avoid downgrading your stock firmware if you can. If you do downgrade stock firmware, avoid OTA updates. Custom ROMs do not appear to matter in this regard.
I do not know if blankflashes will keep working as Motorola keeps updating the stock firmware. We may eventually need a new blankflash. Blankflashes are also rare as Motorola does not formally release them (luckily, we have a working one). So, do not rely on a blankflash to always bail you out of trouble.
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
ILLUSORYINK said:
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
Click to expand...
Click to collapse
How did you get into this state in the first place?
I see from your other post you installed AICP, so you must have TWRP on your device already?
If you need to re-flash TWRP, then boot your device to the bootloader.
Connect your device to your computer, preferably with the original USB cable.
Open the ADB terminal on your computer, and ensure you have the TWRP flashable image on your computer, in your ADB folder.
In the ADB terminal, type 'fastboot devices' without quotes, ensure you get a serial number response from your device.
If you get a response, then type 'fastboot flash recovery <name of TWRP image>' without quotes, where the <name of TWRP image> is the TWRP image file name as on your computer. Ensure the file name is the same, taking into account file name extensions.
You should have flashed TWRP to your recovery partition on your device - use the volume keys on your device to select 'Recovery' then press the power button to boot to recovery. You should be booting to TWRP recovery.
In there, you should be able to copy a custom ROM and flash that within TWRP. Alternatively, you could download a fastboot stock ROM and flash that within fastboot (not TWRP) to restore your device, but ensure it's the correct and latest stock ROM for your device.
After accidentally and stupidly update the latest official Android update the cell keeps rebooting in TWRP.
I can temporarily solve the issue going to bootloader and choose start or factory mode but when I turn off the phone it goes back to TWRP.
What can I do? I don’t mind deleting everything cos I have everything backed up.
Any idea or suggestion is highly appreciated. Thanks in advance, Joe!
Joe2090 said:
After accidentally and stupidly update the latest official Android update the cell keeps rebooting in TWRP.
I can temporarily solve the issue going to bootloader and choose start or factory mode but when I turn off the phone it goes back to TWRP.
What can I do? I don’t mind deleting everything cos I have everything backed up.
Any idea or suggestion is highly appreciated. Thanks in advance, Joe!
Click to expand...
Click to collapse
>Reboot into bootloader
>get adb/fastboot setup
>use below commands
* Fastboot oem fb_mode_set
* Fastboot oem fb_mode_clear
You need to try this code few more times if doesn't work for first time.
If this command doesn't work for you (even after using many times) then there is no other way than flashing complete stock ROM.
____Mdd said:
>Reboot into bootloader
>get adb/fastboot setup
>use below commands
* Fastboot oem fb_mode_set
* Fastboot oem fb_mode_clear
You need to try this code few more times if doesn't work for first time.
If this command doesn't work for you (even after using many times) then there is no other way than flashing complete stock ROM.
Click to expand...
Click to collapse
Thaks for your help! Unfortunately it didnt work.
Where can I get the latest flashable stock through TWRP for moto g4 plus?
Joe2090 said:
Thaks for your help! Unfortunately it didnt work.
Where can I get the latest flashable stock through TWRP for moto g4 plus?
Click to expand...
Click to collapse
As strongst has said you in another thread,
You can't flash Stock ROM through TWRP, stock firmware is flashable only by fastboot method.
And for your problem, TWRP flash (of custom or stock modified) will not work, you need to flash complete ROM by fastboot method.
It will erase your data, so take backup of internal memory.
Follow this [ https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ]
Thread, and keep your discussion to only one thread, don't use multiple thread for same question.
I apologize for the multithread post, it was no my intension…
Hope you have read the other post since I couldn’t get it connected to my PC through USB, fastboot can’t see the device and I can’t enter the phone, it keeps going into TWRP.
I finally solved the problem!!!
I just want to say thank you for your help and other people from the forum. I hope it can help others in the same situation.
Everybody can find the solution here
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Best regards!!1 Joe.
Hi all.
I am going to flash LilneageOS 15.1 on my brand new A1.
We all know it DOESN'T contain any firmware blob (I mean, the stuff that usually drives the baseband modem, the wifi, the touch screen and so on) so I'd need to be sure I am on the latest one before flashing the ROM.
I've been unable to find here a "firmware only" release, also because in a few threads the word "firmware" is used as "ROM".
Is there anyone willing to point me to the proper post?
Please, be patient with me as I'm new to the Xiaomi world, but not new at all with Android and custom ROMs and recoveries.
Thanks in advance.
Hi, I recently flashed Lineage OS 15.1(Latest version) coming from Stock 8.1 August Update.
I suggest you follow the guide on the Mi A1 Lineage OS wiki which I followed and also use GApps(this survives OTA updates or something) provided by Lineage OS maintainer in his thread + 17.x magisk.
However ok Google does not work from Google App, assistant, maps, etc but the mic works fine.
I have seen people say flashing 8.1 May Beta modem(firmware available here) fixes the issue - see attached image - although I haven't tried it myself.
Hope you have no issues with Lineage OS, it's a bit complicated to flash on this device as it is A/B partition. Ok Google hotword is the only problem I have faced which is outweighed by the many essential features Lineage provides over stock.
If you need additional help please ask, because I myself found it tough to flash initially.
Edit: Having flashed stock GApps zip I also had the issue of camera FC, which was fixed by installing this camera through Magisk, which I will recommend anyway for better photo quality.
I have just started the process with TWRP recovery by following the LineageOS wiki up to step no.5.
The device is not booting to recovery but rather to system. So I am stuck here.
Uqbar said:
I have just started the process with TWRP recovery by following the LineageOS wiki up to step no.5.
The device is not booting to recovery but rather to system. So I am stuck here.
Click to expand...
Click to collapse
Have you already done fastboot OEM unlock?
iG0tB0lts said:
Have you already done fastboot OEM unlock?
Click to expand...
Click to collapse
I am strictly following the official wiki. Could it be a problem with the A/B partitions?
Uqbar said:
I am strictly following the official wiki. Could it be a problem with the A/B partitions?
Click to expand...
Click to collapse
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.
iG0tB0lts said:
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.
Click to expand...
Click to collapse
Yes, I did the unlock.
What you say deviates from the original wiki.
I am now updating the system so maybe I get the latest firmware.
I will try again soon after.
iG0tB0lts said:
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.
Click to expand...
Click to collapse
Nope. It doesn't reboot, even if the command line says it did.
I have found something about this problem, but am really puzzled as the official wiki isn't mentioning anything about A/B slots.
Hallo everybody,
I hope someone can help me, I am at my wits end. Fastboot does not see my phone in bootloader mode, after I flashed LineageOS. This is a great problem, because I wanted to flash magisk, but am now unable to do so.
Please can anybody tell me how to enable fastboot? Or tell me how to switch to slot b without fastboot or how I can flash stock firmeware without fastboot. ADB does not see the LineageOS Recovery even if ADB is enabled in the recovery, so sideloading does not work either. I realy are at a loss.
Thanks in Advance.
PS: Not even with lsusb can I see my phone anymore.
sndgsisnshs said:
Hallo everybody,
I hope someone can help me, I am at my wits end. Fastboot does not see my phone in bootloader mode, after I flashed LineageOS. This is a great problem, because I wanted to flash magisk, but am now unable to do so.
Please can anybody tell me how to enable fastboot? Or tell me how to switch to slot b without fastboot or how I can flash stock firmeware without fastboot. ADB does not see the LineageOS Recovery even if ADB is enabled in the recovery, so sideloading does not work either. I realy are at a loss.
Thanks in Advance.
PS: Not even with lsusb can I see my phone anymore.
Click to expand...
Click to collapse
Just in case someone stumbles about the same problem. It turns out, it was a Lineageos problem of some sort, I think.
The option under developer options, standard usb configuration was set to no data transfer. After I changed that fastboot did find my phone.
But the problem, that I was unable to change the slot in the lineageos recovery persisted. Neither can I flash something from within the recovery nor can I flash twrp, after that lineageos doesn't boot. Sadly I have to switch to a different rom. Maybe if the recovery gets better or lineageos is usable with twrp, I might reconsider.