Database Info

"Developer mode" and debug USB problem on Honor8

Hi all guys
i'm going to tell you my little problem, this morning, in my honor8 with stock rom:
my operations, step by step:
- unlock the bootloader, via adb and fastboot
- twrp installed
- from twrp, magisk installed
- Root OK, SafetyNet OK
- then I started to play with the apps, deleting the system that I could not uninstall before (such as gmail, the various pre-installed games etc etc, but no particular app, only known stuff)
- I tried to install a trivial apk inside the system folder. then I realize that now the SafetyNet gives negative result (I do not assure that it was the fault of the app installed on the system folder, but I realized after this operation).
- so, i wanted to restart from the beginning: I wiped and formatted the whole operating system
- with HuaweiUpdateExtractor e fastboot i reinstalled the os (official rom FRD-L09C432B389) with the files BOOT.img, CUST.img, RECOVERY.img, SYSTEM.img
- first problem: when i pressed vol.up+vol.down+power, I started the installation but shortly after I get stucked with the words "Software install failed". Restarting the system, I have seemingly functioning android.
- Apparently, cuz everything works, except for the developer options. I enable it, I click on it, crashes the "settings" app, making me return to the phone's home.
You know:
if i can't enter in the developer mode, i can't activate the "debug usb" options
if i can't activate the Debug usb, i can't recognize the smartphone with fastboot
if i can't recognize the smartphone with fastboot, i can't install twrp
if i can't install twrp, i can't do anything, root included
The only thing I have is the bootloader unlocked (in fact when I start the phone, it warns me of this).
By the way, pressing vol.su or vol.giù + power no longer enters me either in fastboot mode, or in, of course, twrp.
Has anyone come across my own problem?
Do I have a way to reinstall a rom (not necessarily the official) in my situation?
Hopefully, ideas on how to solve?
ps: the phone, in any case, works: google play it's ok, I get calls, internet it's ok etc etc .... the only thing is these developer options are not working and the inability to re-lock the bootloader to send it in assistance with the warranty
I add one thing:
I read that in the Q2 2018, honor8 should receive Oreo.
Is it possible that I solve the problem via the OTA update?
I apologize for my bad English, I hope I was clear enough

Had a similar issue when I was trying to go back to stock. Couldnt boot into an OS because there was not one, and I couldnt get USB debugging to work.
I then flashed the original OS through the original erecovery by loading it onto my SD card. I loaded the entire file onto it unzipped, not with just the 4 img files. For some reason, it came up as a half baked version of the OS (probably because of not flashing the region zip), but it was enough to get me to USB debugging and fastboot. I then flashed TWRP, flashed the operating system, did a factory reset, and went from there.
EDIT: Your English is plenty good enough for most people.
EDIT2: Have you also tried to maually go into download mode and see if you are able to flash TWRP from there? I've done that before as well.

Deemo13 said:
Had a similar issue when I was trying to go back to stock. Couldnt boot into an OS because there was not one, and I couldnt get USB debugging to work.
I then flashed the original OS through the original erecovery by loading it onto my SD card. I loaded the entire file onto it unzipped, not with just the 4 img files. For some reason, it came up as a half baked version of the OS (probably because of not flashing the region zip), but it was enough to get me to USB debugging and fastboot. I then flashed TWRP, flashed the operating system, did a factory reset, and went from there.
EDIT: Your English is plenty good enough for most people.
EDIT2: Have you also tried to maually go into download mode and see if you are able to flash TWRP from there? I've done that before as well.
Click to expand...
Click to collapse
thx for your help Deemo!
Last night i solved the problem just like you said:
the initial difficulty (not possible to enter in fastboot or twrp) was solved in the most banal way I could imagine: with phone off, hold the vol.down button and attach the usb cable. the terminal starts in fastboot mode....I didn't know this method
I found another thread here, where to download the official rom (link to the discussion)
instead of the one I used before, this have the dload folder (never found in previous downloads). I immediately put the dload folder (with the update.app in it) in the microsd.
once in there, everything was easy:
- reinstalled twrp from cmd.exe with fastboot
- started twrp from the mobile phone (a cell turned off, vol.up+power)
- wiped cache, data and dalvik
- turned off the phone
- press vol.up+vol.down+power, the installation starts, but this time, ends correctly.
at the first start, the honor logo in the blue background was there for several minutes (i was worried ) but then, started the initial configuration and the developer options are back to work!
Obviously the phone now no longer has the bootloader unlocked or the root. As if it were new!
This weekend I start all over again, at least I try to do other damages

Gabbbo85 said:
thx for your help Deemo!
Last night i solved the problem just like you said:
the initial difficulty (not possible to enter in fastboot or twrp) was solved in the most banal way I could imagine: with phone off, hold the vol.down button and attach the usb cable. the terminal starts in fastboot mode....I didn't know this method
I found another thread here, where to download the official rom (link to the discussion)
instead of the one I used before, this have the dload [/ B] folder (never found in previous downloads). I immediately put the dload folder (with the update.app in it) in the microsd.
once in there, everything was easy:
- reinstalled twrp from cmd.exe with fastboot
- started twrp from the mobile phone (a cell turned off, vol.up+power)
- wiped cache, data and dalvik
- turned off the phone
- press vol.up+vol.down+power, the installation starts, but this time, ends correctly.
at the first start, the honor logo in the blue background was there for several minutes (i was worried ) but then, started the initial configuration and the developer options are back to work!
Obviously the phone now no longer has the bootloader unlocked or the root. As if it were new!
This weekend I start all over again, at least I try to do other damages
Click to expand...
Click to collapse
Glad I could help!
You should be able to unlock the bootloader again if you kept your original bootloader code.

How I downgraded from Pie to Oreo

This is how I downgraded from Pie to Oreo. I can't guarantee it works for everyone but it worked for me. It required an SD card and a computer.
This is not a guide for the android development savy users but for people who preferred oreo to pie. It works without an unlocked bootloader and an unrooted phone. You will have to wipe your data so backup everything beforehand!
STEP 0) Remove your google account from your phone so you can prevent it automatically updating to Pie on first boot. Go to Settings > Accounts and remove your google account from the phone.
1) First download the zips that include Oreo with the November security patch and the December security update. Put these in the root of the SD card and rename them so you remember which is which.
I have found November Oreo links for both TA1012 and TA1004 but reportedly they both work for all Nokia 8 phones as the main payload.bin file is the same. I used the TA1012 zip with my TA1012 phone.
THMSP said:
https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
Don't worry about the TA-1004 stuff, all Nokia 8 software is generic, only google makes a difference between the model IDs.
Click to expand...
Click to collapse
MD5: 07e5b0c46e86919a66d2e6279613047d
TeddyBeers said:
Rollback for TA-1012 from Pie Beta to Latest Oreo
Official link just captured a minute ago.
https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip
Click to expand...
Click to collapse
MD5: e00affc410525d63200c0c18bc8e0622
December Security update can be downloaded here (file is called NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip):
https://tmsp.io/fs/xda/nb1/ota/
MD5: a8ed8cac0cf4dd7763f9dd0fb00971d5
2) Boot into recovery mode.
a) To do this on Pie, plug your phone into a computer and wait for the drivers to get installed. Windows 7 downloaded a few megabytes from windows update for this.
b) Unplug your phone and turn it off. Hold Volume up and plug your phone into your computer. Keeping holding volume up.
c) When the sad android appears with 'No command' showing, release Vol+. Hold the power button and press Vol+ to get into the recovery menu.
3) Use the Vol+ and Vol- to navigate down to 'Apply Update From SD card' click the power button to select it. In the next menu select the November Oreo zip file. It'll then verify the downloaded zip and install it. This takes a few minutes.
4) Select Wipe data/factory reset from the recovery menu. You need to do this cause data created on Pie doesn't work on Oreo.
6) Repeat steps 3 & 4 for the December security update. I don't know whether you need to factory reset both times but it shouldn't do any harm.
5) Finally select Reboot system now and it'll boot into Oreo. This takes a few minutes.
6) Don't connect to any wifi during setup. Go to settings > system > about phone. Tap the build number at the bottom until you unlock developer options. Go to settings > system > developer options and disable Automatic system Updates.
Hopefully this helps someone. Thanks to @THMSP, @TeddyBeers and @al mak for various posts that helped me downgrade and write this guide.

That's exactly the way to do it.
Actually works both ways as upgrade or downgrade, as Nokia kindly provides full rom oreo/pie instead of just incremental update.

Usb debug need to be enabled or not?

Setup updates from Android 8 back to Android 9 Again
Useful guide, thanks, but after downgrading from Pie to Oreo how do you avoid being forced to upgrade to Pie again in setup, after you Wipe data/factory reset the phone?
I downgraded back to Oreo from Pie, but when I restart in setup I get forced to search for updates and it finds, downloads and installs the Pie update again, and I dont seem to be able to avoid it?

Disable in Developer Options
nb111 said:
Useful guide, thanks, but after downgrading from Pie to Oreo how do you avoid being forced to upgrade to Pie again in setup, after you Wipe data/factory reset the phone?
I downgraded back to Oreo from Pie, but when I restart in setup I get forced to search for updates and it finds, downloads and installs the Pie update again, and I dont seem to be able to avoid it?
Click to expand...
Click to collapse
You have to enable Developer Options then disable Automatic system updates. You will always get the notification that a system update is available but it will not download automatically. Going further, you can even turn this notification off and forget about it.

The problem is that it happens before you get to a point where I know how to access the developer menu to do that.
It happens during the setup wizard, which I can't see how to complete without selecting a wifi network or mobile network, it then searches for downloads and installs the update before it sets up the phone and drops me at the home screen.

nb111 said:
The problem is that it happens before you get to a point where I know how to access the developer menu to do that.
It happens during the setup wizard, which I can't see how to complete without selecting a wifi network or mobile network, it then searches for downloads and installs the update before it sets up the phone and drops me at the home screen.
Click to expand...
Click to collapse
I've been having the same issue. I think it is new. I've done the process as early as January 9th with no forced update. As of yesterday it is forced. I've posted my experience in the thread for NOST. Pie may be life now because there are no custom ROMs and I expect all Oreo ROMs to have the force update thing inside them.

ululalbab said:
Usb debug need to be enabled or not?
Click to expand...
Click to collapse
Not as far as I am aware, though it might be needed if you are booting into recovery mode bia adb.

@nb111 @hodiedodie
Is it possible to either get through the entire setup without connecting to any network - you will have to forgo logging into a google account at first. Or only use mobile data in the hopes that google is smart enough to realise that people don't want to download 1.5GB on their data plans?

Optimus_Toaster said:
@nb111 @hodiedodie
Is it possible to either get through the entire setup without connecting to any network - you will have to forgo logging into a google account at first. Or only use mobile data in the hopes that google is smart enough to realise that people don't want to download 1.5GB on their data plans?
Click to expand...
Click to collapse
I doubt I'll do this myself but I would suggest doing a man in the middle attack on the phone with arpspoof in a Linux distro. Use Wireshark to see what servers it calls out to. Then I would go in my home WiFi router and block those IP addresses. Then reset the phone and connect to the WiFi network and see if that works.

Ok solved this one, had to Update to P remove the Google Account linked to the Device and downgrade again.
It's Part of the Factory Reset Protection that you cant skip the Wifi and Update Screens.

thanks a lot ，my ta1052 downgraded successfully use your 1004firmware

fushanhu said:
thanks a lot ，my ta1052 downgraded successfully use your 1004firmware
Click to expand...
Click to collapse
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?

jskamxmxm said:
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?
Click to expand...
Click to collapse
I didn't try out dua sim because i have only 1 sim and it works well . don't worry bro, any problem can be solved as long as you done downgrade，it's easy to unlock BootLoader under Oreo ，so you can flash your original official firmware use OST tool or NOST in case any issue . （i downloaded my TA 1052 firmware from google，but i didn't flash it because this 1004 so far no problem）
i downgraded because my battery drained very fast and phone became hot frequently ，but i cant find any other way to downgrade or unlock BootLoader under Pie ，the official unlocking method doesn't working with Pie. i unlock it successful after downgrading by flash this 1004 stuff .
There's a small surprise when flash 1004 firmware，it's showing failed:'version old ，not support downgrade' or something i dont remember，my phone off and stucked at starting log and can restart even holding power button 1 minute，so i thought it fu*ked and bricked，after some time i tried hold power and volume + button finally it switched off and in recovery mode i did factory reset and restart ，Oh sh*t ....... it's Oreo already ！！!
haha i wrote too much！

jskamxmxm said:
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?
Click to expand...
Click to collapse
thanks for reminding the dual sim，i think better to flash my 1052 firmware again，i'm not sure could there be any issue in future in case two sim in use

i have trouble please help me
My friend who hadn't elect Wipe data/factory when downgrade pie to oreo , so the phone can't open into system . Can't go through the Recovery too!
How can I do?

[email protected] said:
My friend who hadn't elect Wipe data/factory when downgrade pie to oreo , so the phone can't open into system . Can't go through the Recovery too!
How can I do?
Click to expand...
Click to collapse
Force shutdown the phone by keeping volume up, volume down and power pressed for some time (2 - 3 minutes). Then directly boot into recovery by holding down volume up while connecting the phone to the PC via. USB.

Optimus_Toaster said:
This is how I downgraded from Pie to Oreo. I can't guarantee it works for everyone but it worked for me. It required an SD card and a computer.
This is not a guide for the android development savy users but for people who preferred oreo to pie. It works without an unlocked bootloader and a rooted phone. You will have to wipe your data so backup everything beforehand!
1) First download the zip that includes Oreo with the November security patch and put it in the root of the SD card.
I have found links for both TA1012 and TA1004 but reportedly they both work for all Nokia 8 phones as the main payload.bin file is the same. I used the TA1012 zip with my TA1012 phone.
MD5: 07e5b0c46e86919a66d2e6279613047d
MD5: e00affc410525d63200c0c18bc8e0622
2) Boot into recovery mode.
a) To do this on Pie, plug your phone into a computer and wait for the drivers to get installed. Windows 7 downloaded a few megabytes from windows update for this.
b) Unplug your phone and turn it off. Hold Volume up and plug your phone into your computer. Keeping holding volume up.
c) When the sad android appears with 'No command' showing, release Vol+. Hold the power button and press Vol+ to get into the recovery menu.
3) Use the Vol+ and Vol- to navigate down to 'Apply Update From SD card' click the power button to select it. In the next menu select the downloaded zip file. It'll then verify the downloaded zip and install it. This takes a few minutes.
4) Select Wipe data/factory reset from the recovery menu. You need to do this cause data created on Pie doesn't work on Oreo.
5) Finally select Reboot system now and it'll boot into Oreo. This takes a few minutes.
Hopefully this helps someone. Thanks to @THMSP, @TeddyBeers and @al mak for various posts that helped me downgrade and write this guide.
Click to expand...
Click to collapse
hi everyone,
just now want to try downgrade Pie to Oreo, but struggling to entry the recovery mode.
i already 'success' to access "android sad - no command" but after that, when i press-hold vol up and power always going to home screen (android pie)
can you guys please advise what should i do?
should i unlockbootloader? i try with HMD unlock bootloader but error message "device not support"
fyi, i check on developer option, "OEM unlocking" still grey
also on my device manager, only appear "android composite adb interface"
{
"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"
}
thanks as so much for help

worked for me (downgraded from Pie, January 2019), thanks

I successfully rolled back to Oreo.
I wonder if removing the Google account before the rollback prevent you from rollback - install the forced updates - rollback again (I had to do it because I was forced to install the updates the first time, while the second one I had the possibility to skip the configuration)

Root newbie

Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.

Unfortuently there is no clear tutorial to root this phone but you car read here: [GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018

Snypie said:
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Click to expand...
Click to collapse
1. Do i need custom rom?
no
2. Do i need custom kernel?
no
3. Will the android self update as now?
if you flashed TWRP, no

1. Do i need custom rom? No
2. Do i need custom kernel? No
3. Will the android self update as now? depend on your settings
1-to root it the first thing is to have OEM Unlock available and enabled in Dev Options
if not keep the device fully on and with data on dont restart, power off or reset for at least 7 days continuously (or a bit more) and you should have it
if it's not shown dot bother with the rest
2-to have Dev Menu available go to settings >> about phone >> software information >> on build number tape multiple times 10 times i guess, you will have a pop up confirmation
once back at settings menu you will find a new choice at the very bottom "Develper Options"
3-next step with to plug ur phone with PC with usb cable
after installing SAMSUNG DRIVERS & ODIN and downloading TWRP (custom recovery)
in ODIN 2nd tab, untick "AUTO REBOOT" VERY VERY IMPORTANT
chose the TWRP file using AP button/option in ODIN
put your phone in download MOD power off completely >> power back on while holding vol+ and vol- at the same time
flash the file using ODIN to your phone
4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so, after flashing TWRP, press vol- + power button to reboot the phone
AT THE VERY PRECISE MOMENT WHEN PHONE TURN OFF BEFORE POWERING BACK ON WHEN IT BLINK
RELEAS POWER BUTTON AND VOL+ and PRESS POWER BUTTON + VOL+ AGAIN VERY VERY QUICKLY
if successful you should boot into TWRP directly
5-once you are in TWRP wipe everything then format the device (ALL DATA WILL BE LOST)
of course you need to have the needed files already copied in the SD CARD
from twrp after the wipe and formatiing
go to install and flash in that order RMM_Bypass_v3_corsicanu or RMM-State_Bypass_Mesa_v2
then no-verity-opt-encrypt-6.0
then at the end flash Magisk-v19.3
once its done reboot the phone normally, you will have your phone working as normal
once you are in, install Magisk APK MagiskManager-v7.3.2
reboot again
and voilaaa, you should have root and everything shoul be functional for you
allthow of course I will not be responsible for any kind of software or hardware damage, and certainly not ressponsible for any data loss
as it is completely you responsibility
I would like to attach all the files mentioned above, to help better but dnt sems to find how
so you will have to download and gather them from previous posts

Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.

Snypie said:
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Click to expand...
Click to collapse
its virtually impossible to brick samsung devices these days. Well, perma-brick that is. I have spent entire evenings after work bricking phones just so i could figure out what caused the brick and then fix it. the worst thing that would happen if the FRP lock gets enabled again is that youd have to go re-disable it.
i guess i didnt really explain that clearly after re-reading it. So, when he says "stuck" he means with TWRP installed and no method of rooting. The phone will boot normally in the situation described in point #4

Help rescuing a S7 in boot loop and no access to recovery

Hello guys
First of all, thanks to everyone who shares their knowledge and experiences here on XDA. I've been learning stuff here for years, and every time I made a mistake, I could find a solution, but I'm afraid this time the noob here has made too many mistakes.
My S7 G930F DBT stock is in a boot loop, with the "no command" screen, and the only thing I'm able to do is access download*mode. I would like your help to figure out if there's still something I can do on my own.
So, what happened was that I followed this tutorial about a year ago and converted*my S7 to dual sim. I encountered some issues, one of them being that I wasn't able to keep TWRP installed (the system removed it after the first boot), but in the end I was able to make the phone work again, dual sim. This week, I was having some issues with short battery life and wanted to boot into recovery to wipe cache. I tried that and the boot loop started, and when I tried to access recovery it said that there*was no recovery (I can't recall the exact*message). Since then I tried some things*and realized later I made things worse:
- I tried to flash the stock rom via Odin, but did so with the latest firmware (S8), not with the one on the phone (S4).
- Tried to flash all except the BL file on Odin- I tried to flash TWRP, but it failed because of FRP lock.
- I tried to flash a combination rom, but since I had flashed S8, I couldn't*because the latest combination available is U5
- I'm not sure if it's relevant or not, but when following the dual sim conversion tutorial last year and editing the cert file, the serial number was 00000. I kept it that way because I didn't realize it's written on the back of the phone (duh).
Nothing worked, the phone is still in boot loop, I can't access recovery (not even the "no recovery*message" shows up anymore) and I can only put it in download mode. I thought about maybe removing FRP Lock with the z3x 29.5 I used for the dual sim tutorial, flash TWRP and follow all the steps again, to put the serial number in the cert file, but I'm not sure it would be possible, since I flashed a newer firmware.
So, what do you think? Have I messed up beyond repair this time?
Thanks in advance

drlemmy said:
Hello guys
First of all, thanks to everyone who shares their knowledge and experiences here on XDA. I've been learning stuff here for years, and every time I made a mistake, I could find a solution, but I'm afraid this time the noob here has made too many mistakes.
My S7 G930F DBT stock is in a boot loop, with the "no command" screen, and the only thing I'm able to do is access download*mode. I would like your help to figure out if there's still something I can do on my own.
So, what happened was that I followed this tutorial about a year ago and converted*my S7 to dual sim. I encountered some issues, one of them being that I wasn't able to keep TWRP installed (the system removed it after the first boot), but in the end I was able to make the phone work again, dual sim. This week, I was having some issues with short battery life and wanted to boot into recovery to wipe cache. I tried that and the boot loop started, and when I tried to access recovery it said that there*was no recovery (I can't recall the exact*message). Since then I tried some things*and realized later I made things worse:
- I tried to flash the stock rom via Odin, but did so with the latest firmware (S8), not with the one on the phone (S4).
- Tried to flash all except the BL file on Odin- I tried to flash TWRP, but it failed because of FRP lock.
- I tried to flash a combination rom, but since I had flashed S8, I couldn't*because the latest combination available is U5
- I'm not sure if it's relevant or not, but when following the dual sim conversion tutorial last year and editing the cert file, the serial number was 00000. I kept it that way because I didn't realize it's written on the back of the phone (duh).
Nothing worked, the phone is still in boot loop, I can't access recovery (not even the "no recovery*message" shows up anymore) and I can only put it in download mode. I thought about maybe removing FRP Lock with the z3x 29.5 I used for the dual sim tutorial, flash TWRP and follow all the steps again, to put the serial number in the cert file, but I'm not sure it would be possible, since I flashed a newer firmware.
So, what do you think? Have I messed up beyond repair this time?
Thanks in advance
Click to expand...
Click to collapse
Hello, so if you've flashed a newer bootloader than the one in the tutorial then yes it's game over for dual SIM as there isn't a newer version of that bootloader and there isn't going to be. The S7 is getting on abit now.
The best you can now hope for is to install the latest German firmware and have your phone working as a single SIM again.
To exit no command press volume up + power.
When you install TWRP stock recovery is removed. When you uninstall TWRP stock recovery is still missing until you flash stock firmware, that's why you have No command.

cooltt said:
Hello, so if you've flashed a newer bootloader than the one in the tutorial then yes it's game over for dual SIM as there isn't a newer version of that bootloader and there isn't going to be. The S7 is getting on abit now.
The best you can now hope for is to install the latest German firmware and have your phone working as a single SIM again.
To exit no command press volume up + power.
When you install TWRP stock recovery is removed. When you uninstall TWRP stock recovery is still missing until you flash stock firmware, that's why you have No command.
Click to expand...
Click to collapse
Thanks for replying!
I have no problem loosing dual sim, as long as I can get it back up. When I press volume up + power, nothing happens, it only turns off completely. I flashed the the latest firmware again (G930FXXS8ETC6 - CSC file, not HOME_CSC). But the result was the same, "no command" screen and no access to recovery, I tried volume up + power and volume up + home button + power, at the same time and alternating.

I was able to get to were the recovery was supposed to be and this is the error it's showing:
{
"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 flashed the phone in Odin once again, this time with "nand erase" and "repartition" checked, and the pit file in the third tab. But it didn't work, afterwards the "no command" screen poped up and the same error showed up when trying to access recovery. Tried to flash TWRP again and got the FRP lock message. Nothing changed, basically.
I thought about finding a way to bypass FRP and install TWRP, but there's some shady stuff online on how to do it. The Z3x tool used in the dual sim tutorial has an option for that, but it shows "card error" when I try it and nothing happens.
So, I'm kinda lost here, any suggestion on the next steps would be much appreciated.

I tried to find a way to bypass FRP, tried many tools, like Z3X and Miracle, but it didn't work. The best I could get out of two of these softwares was a "Custom Binary(Userdata) Blocked by FRP Lock" line in download mode when the procedure was finished, not even a reboot. When I manually reboot the phone after getting this message, it shows something different, "An error has occurred while updating" blue screen saying to use SmartSwitch, but that obviously doesn't work either.

drlemmy said:
I tried to find a way to bypass FRP, tried many tools, like Z3X and Miracle, but it didn't work. The best I could get out of two of these softwares was a "Custom Binary(Userdata) Blocked by FRP Lock" line in download mode when the procedure was finished, not even a reboot. When I manually reboot the phone after getting this message, it shows something different, "An error has occurred while updating" blue screen saying to use SmartSwitch, but that obviously doesn't work either.
Click to expand...
Click to collapse
It's unlikely you'll be able to bypass FRP lock with any tool as most don't work anymore.
You just need to flash the latest firmware for your region with Odin. Boot into download mode to do this, can you still access download mode?
After a successful flash the FRP lock will still ask for the Google account and password used with the phone. Follow the steps and your phone should start normally.
It does not matter what modifications you have done prior, the default recovery is always flash latest firmware with Odin.
In future REMOVE Google account from phone BEFORE modification.

cooltt said:
It's unlikely you'll be able to bypass FRP lock with any tool as most don't work anymore.
You just need to flash the latest firmware for your region with Odin. Boot into download mode to do this, can you still access download mode?
After a successful flash the FRP lock will still ask for the Google account and password used with the phone. Follow the steps and your phone should start normally.
It does not matter what modifications you have done prior, the default recovery is always flash latest firmware with Odin.
In future REMOVE Google account from phone BEFORE modification.
Click to expand...
Click to collapse
It wasn't intentional, the phone was working fine and I was logged in my Google account, but the battery life was getting shorter. I just wanted to wipe cache to try and fix that. When I tried to boot to recovery, the boot loop started.
I think that happened because of the dual sim modification last year, I must have done something wrong and the phone lost the recovery mode or something. But the first thing I did was flashing the latest stock firmware, and after that I couldn't get into the system anymore. I probably should have flashed the same binary I had installed, at least it would give me the combination file option.
Download mode is the only thing working. The FRP lock bypass route was the best I could come up with, since it would allow to install TWRP, access to ADB, etc

drlemmy said:
It wasn't intentional, the phone was working fine and I was logged in my Google account, but the battery life was getting shorter. I just wanted to wipe cache to try and fix that. When I tried to boot to recovery, the boot loop started.
I think that happened because of the dual sim modification last year, I must have done something wrong and the phone lost the recovery mode or something. But the first thing I did was flashing the latest stock firmware, and after that I couldn't get into the system anymore. I probably should have flashed the same binary I had installed, at least it would give me the combination file option.
Download mode is the only thing working. The FRP lock bypass route was the best I could come up with, since it would allow to install TWRP, access to ADB, etc
Click to expand...
Click to collapse
I understand all that you've said the only solution is to install correct firmware with Odin via download mode then sign into Google account.

I downgraded from android 10 to android 8.1

So I was fed up with Xiaomi latest updates on this Phone Mi A2 lite and decided to give it a go to downgrade to android 8.1 back when this phone was A REAL BEAST!
Guess what happened. Firstly there was no mobile network so I flashed again with android 10 modem.img and everything was looking fine the phone was snappy, blazingly fast then i noticed that video camera could not record normal video only short,slow motion and timelapse videos. When it was with android 8 original modem this was not happening. So after reading some stuff here on XDA I tried to flash modem.img of the first ever fastboot rom available for mi a2 lite. it was 9.6.4.0 and after i flashed that, i had mobile data doing just fine, tried the video recorder and everything was smooth.
During that time i enjoyed using my phone, I had oppened PES 2020 since morning that day, and when i tried to play at midnight before sleep it was still on the ram and I was like WOW thats fantastic.
Sadly after i went to sleep and i woke up I noticed the phone to be updated to android 9 pie. And i was frustrated because it was so great i completely forgot the part i was seeing to buy another fast phone. And yesterday I tried again with the same steps but even i had video not working, or i had not mobile network. I couldnt make it work. So if anyone knows how to make it happen please help.
Bugs that appeared since android 9 was not there in android 8.1
WIFI AND BLUETOOTH
I thought this was an hardware issue but no! Even if it still had some interference like from 43Mbps I got like38 Mbps with both on while on oreo but not like 43 with 4-8 Mbps on Pie or Android 10.
The only two things that on oreo wesre bad was that camera had no option for 60fps record and no FM Radio!
BUT I WOULD DO EVERYTHING TO GET OREO ONE MORE TIME WORKING

Oreo was the only smooth rom ever ya.. i guess when you try again,make sure auto update is off in developer settings

ttdom said:
Oreo was the only smooth rom ever ya.. i guess when you try again,make sure auto update is off in developer settings
Click to expand...
Click to collapse
If only i could get it working one more time, im sure it will hold my tasks for another year

AnonymousAL said:
If only i could get it working one more time, im sure it will hold my tasks for another year
Click to expand...
Click to collapse
Try flashing in edl mode , in fastboot mode , fastboot command " fastboot oem edl". device will go black whit blinking led. in flashtool , device is com7 or something like that. Choose the Oreo rom you want and check "clean all"at the right bottom all your data will be wiped but bootloader remains unlocked.when you see "succes " your phone is flashed, keep the phone connected and press and hold power button till you see it boots ( about 20 sec.) Now go true boot-up wizard. Before installing apps etc... go to settings and enable developer options, by tapping buildnr several times. In dev. settings disable "automatic update" now your phone will stick to Oreo.

Thank you very much but i was able to do myself with some commands in twrp adb mode i found in a thread! This phone is a suppppeer beast now! I can keep this phone for another year with no problem at all! Its super smooth and snappy??

AnonymousAL said:
Thank you very much but i was able to do myself with some commands in twrp adb mode i found in a thread! This phone is a suppppeer beast now! I can keep this phone for another year with no problem at all! Its super smooth and snappy
Click to expand...
Click to collapse
Can you share the steps you follow to downgrade it? Please! I'm really thinking about it, I miss having the apps in background for real.

Hello together, same for me. With the latest Android my A2 Lite is really crappy. Even freezes while using Chrome. Reading that there might be issues while downgrading I would appreciate if someone could support with a proper how-to.
Thanks

p4f456 said:
Hello together, same for me. With the latest Android my A2 Lite is really crappy. Even freezes while using Chrome. Reading that there might be issues while downgrading I would appreciate if someone could support with a proper how-to.
Thanks
Click to expand...
Click to collapse
Fastboot flashing
1. Download desired Android One version from here: https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
2. Download platform tools from here: https://developer.android.com/studio/releases/platform-tools
3. Unpack Android One till you will have images folder and other files
4. Unpack platform tools and open it in CMD (you can do it by writing "cmd" in folder path)
5. Go into developer settings and turn on OEM unlocking and usb debugging
6. Boot your phone into fastboot mode (connect your phone to the pc and write "adb reboot bootloader)
7. Unlock bootloader by "fastboot oem unlock" command
8. Boot to fastboot again
9. Copy your android one path and paste it into adb and add /flash_all.bat and hit enter
a) flash_all.bat - installs android one and removes everything
b) flash_all_lock.bat - same as the one above but will also lock the bootloader (phone might not work after locking the bootloader)
c) flash_all_lock_crc.bat - lock bootloader and encrypts data
d) flash_all_except_storage.bat - flashes android one but doesn't remove any apps or reset setting (not recommended if downgrading or updating from 8 to 9 for example)
10. Once you finish configuring your device unlock developer settings and turn off automatic updates
Xiaomi Flash Tool
From point 1 to 8 it's the same
9. Download Xiaomi Flash Tool from here: https://www.xiaomiflash.com/
10. Unpack it and open it
11. Connect your phone to the computer
12. In the right bottom corner choose which one of .bat files you want to use
13. Boot to edl mode by "adb reboot edl" or "adb restart edl" (don't remember which one works)
14. Click flash and wait till it says "done" or "finish"
15. Disconnect your phone and hold power button for about 10s
16. Configure, disable automatic updates and enjoy
Personally I didn't notice any diffirence between flashing through fastboot and Flash Tool, but a lot of people recommend using flash tool to downgrade
Also I hope this guide is quite easy to understand
Edit: Also while configuring update will start downloading so just go to Updater and stop it

Thanks a lot, will try it via fastboot. But what about the issues with modem.img etc as mentioned during the downgrade from Q to Oreo?

For what i have read people normally flash and old android 8 rom, and then by recovery they update to the final build of oreo to solutionate errors
Enviado desde mi Mi A2 Lite mediante Tapatalk

p4f456 said:
Thanks a lot, will try it via fastboot. But what about the issues with modem.img etc as mentioned during the downgrade from Q to Oreo?
Click to expand...
Click to collapse
Oh yeah forgot that, to solve them I think you need to flash modem.img alone after flashing whole system, basically copy modem.img to platform tools, open it, boot to fastboot and write "fastboot flash modem modem.img". Not sure if that will work, but from what I remember it solves all issues

I managed to install android 8.1
Now i have everything working and the steps i followed are in the image!
This is the link mentioned in the photo
https://forum.xda-developers.com/showpost.php?p=78736646&postcount=195
{
"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"
}
Remember that firstly i flashed android 8.1 with android 10 modem.img

Divolka said:
Fastboot flashing
1. Download desired Android One version from here: https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
2. Download platform tools from here: https://developer.android.com/studio/releases/platform-tools
3. Unpack Android One till you will have images folder and other files
4. Unpack platform tools and open it in CMD (you can do it by writing "cmd" in folder path)
5. Go into developer settings and turn on OEM unlocking and usb debugging
6. Boot your phone into fastboot mode (connect your phone to the pc and write "adb reboot bootloader)
7. Unlock bootloader by "fastboot oem unlock" command
8. Boot to fastboot again
9. Copy your android one path and paste it into adb and add /flash_all.bat and hit enter
a) flash_all.bat - installs android one and removes everything
b) flash_all_lock.bat - same as the one above but will also lock the bootloader (phone might not work after locking the bootloader)
c) flash_all_lock_crc.bat - lock bootloader and encrypts data
d) flash_all_except_storage.bat - flashes android one but doesn't remove any apps or reset setting (not recommended if downgrading or updating from 8 to 9 for example)
10. Once you finish configuring your device unlock developer settings and turn off automatic updates
Xiaomi Flash Tool
From point 1 to 8 it's the same
9. Download Xiaomi Flash Tool from here: https://www.xiaomiflash.com/
10. Unpack it and open it
11. Connect your phone to the computer
12. In the right bottom corner choose which one of .bat files you want to use
13. Boot to edl mode by "adb reboot edl" or "adb restart edl" (don't remember which one works)
14. Click flash and wait till it says "done" or "finish"
15. Disconnect your phone and hold power button for about 10s
16. Configure, disable automatic updates and enjoy
Personally I didn't notice any diffirence between flashing through fastboot and Flash Tool, but a lot of people recommend using flash tool to downgrade
Also I hope this guide is quite easy to understand
Edit: Also while configuring update will start downloading so just go to Updater and stop it
Click to expand...
Click to collapse
Finally I used the instruction as mentioned by Divolka (thanks again!) via Fastboot. First flashed 9.6.4.0 then 9.6.11.0 and immediately deactived the updates in the settings after setup.
Well currently everything seems to work fine, just SIM 1 and SIM 2 slots are switched and I only can use the current "SIM 2" slot with working mobile data etc. "SIM 1" slot is not working properly but I can live with that as I only use 1 SIM.
I hope there are no other bugs somewhere as I did not flash modem.img or anything else separate, just the full stock roms and locked the bootloader at the end again.

p4f456 said:
Finally I used the instruction as mentioned by Divolka (thanks again!) via Fastboot. First flashed 9.6.4.0 then 9.6.11.0 and immediately deactived the updates in the settings after setup.
Well currently everything seems to work fine, just SIM 1 and SIM 2 slots are switched and I only can use the current "SIM 2" slot with working mobile data etc. "SIM 1" slot is not working properly but I can live with that as I only use 1 SIM.
I hope there are no other bugs somewhere as I did not flash modem.img or anything else separate, just the full stock roms and locked the bootloader at the end again.
Click to expand...
Click to collapse
I have my phone running since 9 days since the day i flashed oreo, there isss noo problem! Its super great!
Only if you miss 60 fps recording and fm radio that were not available on android 8

Yes it is true, the speed of the phone is amazing compared to Android 10. But now I am facing battery issues phone does not go into deep sleep anymore, therefore battery lost almost 30% in half a day without using. In the settings I can only see that system / Android OS is the root cause but even the battery analitics apps can't tell me which app is the reason.
edit: according to BBS it is netmgr_wl what leads to the wakelocks so indeed related to the modem issue. Anyone has any advice? Should I flash the modem.img from the Android 10 Rom and if yes how?

Divolka said:
Fastboot flashing
1. Download desired Android One version from here: https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
2. Download platform tools from here: https://developer.android.com/studio/releases/platform-tools
3. Unpack Android One till you will have images folder and other files
4. Unpack platform tools and open it in CMD (you can do it by writing "cmd" in folder path)
5. Go into developer settings and turn on OEM unlocking and usb debugging
6. Boot your phone into fastboot mode (connect your phone to the pc and write "adb reboot bootloader)
7. Unlock bootloader by "fastboot oem unlock" command
8. Boot to fastboot again
9. Copy your android one path and paste it into adb and add /flash_all.bat and hit enter
a) flash_all.bat - installs android one and removes everything
b) flash_all_lock.bat - same as the one above but will also lock the bootloader (phone might not work after locking the bootloader)
c) flash_all_lock_crc.bat - lock bootloader and encrypts data
d) flash_all_except_storage.bat - flashes android one but doesn't remove any apps or reset setting (not recommended if downgrading or updating from 8 to 9 for example)
10. Once you finish configuring your device unlock developer settings and turn off automatic updates
Xiaomi Flash Tool
From point 1 to 8 it's the same
9. Download Xiaomi Flash Tool from here: https://www.xiaomiflash.com/
10. Unpack it and open it
11. Connect your phone to the computer
12. In the right bottom corner choose which one of .bat files you want to use
13. Boot to edl mode by "adb reboot edl" or "adb restart edl" (don't remember which one works)
14. Click flash and wait till it says "done" or "finish"
15. Disconnect your phone and hold power button for about 10s
16. Configure, disable automatic updates and enjoy
Personally I didn't notice any diffirence between flashing through fastboot and Flash Tool, but a lot of people recommend using flash tool to downgrade
Also I hope this guide is quite easy to understand
Edit: Also while configuring update will start downloading so just go to Updater and stop it
Click to expand...
Click to collapse
Do you know how to do this steps on Ubuntu? The Flash Tool looks like it's only for WIndows

p4f456 said:
Yes it is true, the speed of the phone is amazing compared to Android 10. But now I am facing battery issues phone does not go into deep sleep anymore, therefore battery lost almost 30% in half a day without using. In the settings I can only see that system / Android OS is the root cause but even the battery analitics apps can't tell me which app is the reason.
edit: according to BBS it is netmgr_wl what leads to the wakelocks so indeed related to the modem issue. Anyone has any advice? Should I flash the modem.img from the Android 10 Rom and if yes how?
Click to expand...
Click to collapse
I am not having any battery issues with the method I followed, do not know if that is the reason or not. And I am having the best battery life i have ever had on this phone with android 8.1.
I am playing hard with my phone and it still gets 6+ screen on time. Without playing pes 2020 i get 8-10+ screen on time
EDIT: I keep bluetooth Always On to be connected with my mi band 3. Because before i couldnt use it with wifi turned on because we all know what it does to internet speed

AnonymousAL said:
I am not having any battery issues with the method I followed, do not know if that is the reason or not. And I am having the best battery life i have ever had on this phone with android 8.1.
I am playing hard with my phone and it still gets 6+ screen on time. Without playing pes 2020 i get 8-10+ screen on time
EDIT: I keep bluetooth Always On to be connected with my mi band 3. Because before i couldnt use it with wifi turned on because we all know what it does to internet speed
Click to expand...
Click to collapse
Finally I tried some other instructions but none worked. I followed your instruction eith 9.6.11.0 and now I can confirm it also works perfectly for me at the moment.
Can't give any long term results yet but at least no network issues anymore, no SIM swap, everything is fast and stays in RAM, and seems that also thr battery is fine now.
So thanks again for the great hint Lucky again with this phone!

p4f456 said:
Finally I tried some other instructions but none worked. I followed your instruction eith 9.6.11.0 and now I can confirm it also works perfectly for me at the moment.
Can't give any long term results yet but at least no network issues anymore, no SIM swap, everything is fast and stays in RAM, and seems that also thr battery is fine now.
So thanks again for the great hint Lucky again with this phone!
Click to expand...
Click to collapse
Great That worked!
Yeah i am enjoying my phone too. Its reborn!:victory::victory::victory:

omg now I want to downgrade so bad, the latest android 10 update is working "good" in comparison how it was but I still remember how good was the phone before the first version update and it hurts