Database Users

Issue: not entering fastboot, does not recognized by USB

Hi,
I have a blocking issue with my P8 Lite (ALE-L21C432B614): it does not enter the fastboot and is not recognized when connected through USB.
The history of the issue: my Nokia Steel 8HR watch stopped suddenly syncing with my phone. After trying everything (reinstall, wipe cache, etc) and confirming my watch syncs with other smartphones, I decided to root my phone to see if I can try downgrade Nokia app. However, it did not go was expected ...
My steps:
1) I was on (ALE-L21C432B612), when my watch Nokia Steel 8HR stopped syncing with my phone;
2) I unblocked bootloader with Huawei code;
3) Before going to root stuff, I decided it was wiser to try newer firmware (ALE-L21C432B614) using app Firmware Finder (OTA, Wifi proxy method);
At this point:
- firmware update succeeded
- watch still does not sync
- does not enter fastboot
- USB recognition stopped (not recognized by ADB)
4) I reinstalled firmware (ALE-L21C432B614) using app Firmware Finder (this time, full OTA, Wifi proxy method);
- firmware update succeeded
- watch still does not sync
- does not enter fastboot
- USB recognition stopped (not recognized by ADB)
5) I reinstalled firmware (ALE-L21C432B610) using app Firmware Finder (this time, full OTA, Wifi proxy method);
- firmware update succeeded
- watch still does not sync
- does not enter fastboot
- USB recognition stopped (not recognized by ADB)
6) reinstalled firmware (ALE-L21C432B614) using app Firmware Finder (this time, full OTA, Wifi proxy method);
- firmware update succeeded
- watch still does not sync
- does not enter fastboot
- USB recognition stopped (not recognized by ADB)
7) tried *#*#2846579#*#* then Background > Google mode with no effect
Whenever I turn off my phone and then press volume down and connect USB, it does not go to fastboot.
Any ideas on how I can recover my fastboot without PC connection (before throwing it to the garbage bin)?
Thanks a lot!
Luis

...

cmmx said:
Try this:
https://forum.xda-developers.com/p8lite/help/phone-p-8-lite-rescue-mode-t3658993/post73470050
It worked for me when Magisk screwed my boot image.
In my case it always went to rescue mode and wouldn't flash, no matter the button combination, and adb wouldn't detect the phone either, so I also though I'd lost the phone or needed a jtag box.
Click to expand...
Click to collapse
dc phoenix try this, much better than simple adb, but be carefull it is strong software it can destroy your phone.

cmmx said:
Try this:
https://forum.xda-developers.com/p8lite/help/phone-p-8-lite-rescue-mode-t3658993/post73470050
It worked for me when Magisk screwed my boot image.
In my case it always went to rescue mode and wouldn't flash, no matter the button combination, and adb wouldn't detect the phone either, so I also though I'd lost the phone or needed a jtag box.
Click to expand...
Click to collapse
Hi, thank you for you answer. I tried it:
1. I turned off the phone,
2. connected it to USB port, waited for charging,
3. disconnected,
4. reconnected it and then pressed up + power :
It shows Huawei logo and then go to EMUI menu with 3 options ("Reboot system now", "Wipe data/factory reset", "Wipe cache partition".
What did I do wrong? I was expecting the gray screen showing "bootloader unlocked" ...

...

[Q] LG G6 H870 | Turning on WiFi does not work, but "/data/misc/wifi/config" is ok

[Q] LG G6 H870 | Turning on WiFi does not work, but "/data/misc/wifi/config" is ok
After Reboot from TWRP, it was no longer possible to activate WiFi.
The "/data/misc/wifi/config" contains the correct MAC address, Bluetooth works.
Neither a factory reset nor the installation of another ROM solved the problem.
What can disable WiFi permanently regardless of the ROM and correct configuration file?
How do I reactivate WiFi?
Details:
- was on "Fulmics ROM 4.2" with TWRP from Eliminater74
- flashed Magisk-v18.0.zip, wiped Dalvic and cache
- after Reboot the WiFi switch can no longer be activated
- Factory reset does not help
- flashed "Oreo 8 OPEN EU 20C ROM" with factory reset, which hasn't helped either
- checked "/data/misc/wifi/config" - MAC present
- pulled misc.img, checked at HEX 600 - MAC present
- checked hidden call menu - MAC present

Bud Cord said:
After Reboot from TWRP, it was no longer possible to activate WiFi.
The "/data/misc/wifi/config" contains the correct MAC address, Bluetooth works.
Neither a factory reset nor the installation of another ROM solved the problem.
What can disable WiFi permanently regardless of the ROM and correct configuration file?
How do I reactivate WiFi?
Details:
- was on "Fulmics ROM 4.2" with TWRP from Eliminater74
- flashed Magisk-v18.0.zip, wiped Dalvic and cache
- after Reboot the WiFi switch can no longer be activated
- Factory reset does not help
- flashed "Oreo 8 OPEN EU 20C ROM" with factory reset, which hasn't helped either
- checked "/data/misc/wifi/config" - MAC present
- pulled misc.img, checked at HEX 600 - MAC present
- checked hidden call menu - MAC present
Click to expand...
Click to collapse
I turn on airiplane mode, then 2 seconds later turn airiplane mode off and wifi works.
Matt

Unfortunately this trick (activate WiFi in flight mode) does not work.
But thanks for the idea! :good:
During my long research I had read somewhere that WiFi worked again on a LG with the same symptoms after disconnecting the battery cable.
I don't want to try this during the warranty period.
I know why I don't like fixed batteries!
I probably have no choice but to install a KDZ firmware, lock the bootloader and send the phone in for repair.
Or does anyone else have an idea how I can bring the WiFi back to life?

I have now flashed H87020c_00_OPEN_EU_OP_0817.kdz and locked the bootloaders again.
Even after a final reset to factory defaults, WiFi stays impossible to activate.
Any further suggestions before I send the phone in for repair?

The smartphone has now been repaired under warranty.
Parts of the hardware were defective and had to be replaced.

Factory reset has me stuck on "Checking for updates" - Can I re-flash?

Hi all,
:crying: - Looking for a way to get my Mi Note 2 back to life!
This device has never been unlocked or ROMed before (although it has been re-flashed successfully via Xiaomi's own pushed updates).
It is running MIUI 10.0.something (cannot access menus to verify exact).
The problem
----------------
I did a standard factory reset on the phone.
Once restarted, it takes you through the normal setup screens such as 'language', 'region', 'wifi network' after which I am given the option to select "copy your data from an old phone" or "set up as new", no matter which I select, my phone goes to the next screen which shows "Checking for updates". Here it stays - endlessly...
What have I tried?
----------------------
I have tried a different wifi network but it does the same.
I have also tried selecting "copy your data" instead of "set up as new" but it does the same.
Thoughts
------------
I thought I would try to install a new stock ROM to see if that would fix the issue. However, in order to unlock with the Mi bootloader unlock tool (and then use their flashing tool), apparently to do this, I need to enable something under developer options - clearly impossible when I cannot get to any android menus.
The phone *can* be re-started into the fastboot screen but does this help me at all?
On the MIUI website I noticed the following in the tips and tutorials forum: How to install a MIUI update without unlocking the bootloader: https://en.miui.com/thread-3852597-1-1.html
The above got me slightly excited before I realised that I have no way to place a ROM into the ‘downloaded_rom’ folder in the internal storage of my device (as the article instructs). Note that the reason for this (on my phone at least) is that although a Windows explorer window does open when I connect the phone to my laptop, it is empty (i.e. you cannot see any files/folders in it). BTW - I know what causes that specific issue as that bug was present in the device ages ago - basically, the phone seems to default to be in USB charge mode and in order to see the folders in Windows Explorer, you have to go into developer options and manually change the USB mode and then change it back to MTP mode. Once that is done, you can see the files/folder structures. However, I cannot get to any developer options as I cannot get to Settings at all.
What can I do?
------------------
So my burning question is this: How can I re-ROM this theoretically 'working' device, given the above constraints?
Is there any way to do anything while the phone is in the fastboot mode perhaps?
Is there some method maybe used to recover a bricked device that I could employ here?
Thank you for any help offered!
Cheers!

Nook Simple - Touch Network Problem

Hello! My Nook shows an error "Network Problem". Whatever I tried to do I cannot fix this problem. I've watched a lot of videos on Youtube how to reset it, but with no luck.
The screens it shows after I turn it on are:
1. Your Nook is starting up
2. Welcome to your all-new Nook
3. Terms and Conditions
4. Select your Time Zone (I choose Eastern time)
5. Choose a Network to Use (I tried a few different networks - it connects)
6. Network Problem
Factory button doesn't show on any page I try to call.
I tried to call factory menu after the Nook is booting - it doesn't show up.
I uploaded the latest firmware 1.2.2 in the main directory. It is not upgrading automatically.
I bought the reader a few years ago brand new from store. I've never had problems until now.
The reader is not rooted.
Could you please help me to solve the problem?
Thank You!

thesaint11111 said:
Factory button doesn't show on any page I try to call.
I tried to call factory menu after the Nook is booting - it doesn't show up.
I uploaded the latest firmware 1.2.2 in the main directory. It is not upgrading automatically.
I bought the reader a few years ago brand new from store. I've never had problems until now.
The reader is not rooted.
Could you please help me to solve the problem?
Thank You!
Click to expand...
Click to collapse
It may be that for some reason a factory reset is in order, but before you try that I suggest you download a fresh copy of the 1.2.2 update zip, just in case the one you have is corrupted. The update is supposed to happen after the device goes to sleep. When I have done this recently, I've booted up the device and stopped at the welcome screen, then connected it to my PC via USB and copied over the update zip. Then I just left it. Eventually it goes to sleep and eventually it installs the update. That's what has worked for me. If it doesn't work for you, then the factory reset may be needed.

I uploaded the latest firmware, but the update doesn't start by itself. I don't mind doing factory reset. The problem is I can't call the factory reset menu. I followed the instructions holding down forward button and sliding from left to right on the top of the touch screen area.

thesaint11111 said:
I uploaded the latest firmware, but the update doesn't start by itself. I don't mind doing factory reset. The problem is I can't call the factory reset menu. I followed the instructions holding down forward button and sliding from left to right on the top of the touch screen area.
Click to expand...
Click to collapse
I think that method will not result in a factory re-image, which is what you really want (even if you could get it to work for you).
I know of two ways to trigger a factory re-image (i.e., return the device to its out-of-the-box state, with a clean copy of whatever firmware was placed on it at the factory). This can be done by preparing a NookManager card. It is not necessary to use the card to root the device. One of the menu options on the card is to initiate a factory reset. This simulates eight failed boot attempts which is the default method for initiating a re-image. Here's what I wrote in another thread:
"To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no. Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update."
Eight failed boot attempts. The device is designed to react to repeated failed boots in desperation and trigger a factory re-image. This is really painful in practice. You must interrupt the boot sequence successfully eight times in a row (any miss and the count starts over....). I've done it once. It's very nerve-wracking. But it does take you to the factory re-image option.

You can always install an update zip manually.
You need to be running something that is not using /system, like Neo Noogie or TWRP or something.
This should probably even work in the standard system if you "stop".
Extract META-INF/com/google/android/update-binary from the update zip.
Code:
# stop
# umount /system
# setprop ro.product.device ntx_6sl
# update-binary 2 1 /wherever/update.zip
(The first three commands may not be necessary.)

@nmyshkin ... I just tried logging into the B&N website, I got a 'your password has expired' ... i changed the password and now my device shows 'Unavailable' for the the 'Account' and 'Owner' fields ... How do i log back in with the new changed password ?
will Device Registrator be of any help ?
as you already know ... I am on 1.2.2 ...

aiamuzz said:
@nmyshkin ... I just tried logging into the B&N website, I got a 'your password has expired' ... i changed the password and now my device shows 'Unavailable' for the the 'Account' and 'Owner' fields ... How do i log back in with the new changed password ?
will Device Registrator be of any help ?
as you already know ... I am on 1.2.2 ...
Click to expand...
Click to collapse
Mmmm.....do you mean on your PC? And so then now with the new password the NSTG is not recognized?
Well, you might have to start over (deregister and register again with the new password.
You can try DeviceRegistrator. As my work with the UK ROM showed, it actually is capable of completing both authentication and registration. See step 22 here.

nmyshkin said:
Mmmm.....do you mean on your PC? And so then now with the new password the NSTG is not recognized?
Well, you might have to start over (deregister and register again with the new password.
You can try DeviceRegistrator. As my work with the UK ROM showed, it actually is capable of completing both authentication and registration. See step 22 here.
Click to expand...
Click to collapse
oh thank you for the step 22 reference , I didnt' know the correct sequence, ... What will be the preferred url ? I can see 3 of them, do we have to try each one until we succeed or the 1st one in the list is the best choice to try first ?

MDM Locked Galaxy Tab A

I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.

Hello,
I have the same exact same issue, have you been able to unlock it?
Thank you!

I can fix it remotely the last hope

Same Issue here,

Any one had any luck with MDM T307U. Please assist.

rittnerb said:
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Click to expand...
Click to collapse
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.

lewmur said:
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
Click to expand...
Click to collapse
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.

mindlery said:
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
Click to expand...
Click to collapse
This method works up to step 7 for me. I can't seem to enable usb debugging before knox kicks in. With or without wifi. I'm experimenting to see if I can get past that step.

How to Remove MDM Control from Android?​For anyone suffering from this issue, the following are the steps to bypass Samsung Knox factory reset protection:
First of all, create a password for the device.
Make sure that your device is charged to an 80% or greater charge.
Next, you’ll need to go to Settings and Security Encrypt Device tabs respectively.
Set a PIN/password for your device.
After you have secured your device and it’s gone through. Reboot the device, and when it boots, it will ask you to enter a password in order to access your device to view encrypted data. If you type the wrong password 15-20 times (it depends on your device), it’ll wipe your device of any information and will restart and then appear like you’re registering as a brand new device after a factory reset.

Thats the 2th!!! Try it
Video - Samsung SM-T307U Galaxy Tab A 8.4 2020 Knox Remove || Tab a 8.0 MDM Remove
the Tool from the Video Tutorial is here >> SamFwToolSetup_4.3