Developer settings get reset afer reboot - Dell Venue

Hey Folks!
I've done quite some research on this problem, but havn't found any solution yet. The problem is, that my Dell Venue 8 7840, running Android 5.1, won't
save any Developer options past a reboot. I have noticed this issue before, but didn't find a solution. This also means, that the oem-unlock setting is lost after
rebooting into the adb bootloader to achieve root. I perform the steps described here --> http://forum.xda-developers.com/dell-venue/general/root-howto-dell-venue-8-7840-t3282532
1.) Enable usb-debugging
2.) oem-unlock --> enable
3.) adb devices --> device is connected
4. adb reboot bootloader --> device reboots
5.) fastboot oem-unlock --> exits with error (failed to change status)
I believe, that this has something to do with the loss of the developer settings. When I then boot again, the oem-unlock setting is set back to locked. Anybody ever encountered similar issues?
Is there a way to work around this?
Really appreciate your input!
Regards

Related

[Q] Restore a bricked device with no usb debugging?

Hi, I'm trying to help a friend unbrick his nexus 7.
The problem is that he is a stock clean user. No root, no custom recovery, all plain stock
This also means that he never enabled usb debugging in dev options
Now im trying to reflash factory image but everytime it gets stuck at the same point of unlocking bootloader (wiping user data)
Will it be possible to reflash factory if adb debug wasn't enabled in the device?
(adb device returns empty, but fastboot works)
If the answer is no, is there any way to edit the build.prop and/or where the adb gets flagged as enabled?
(The only solution i found requires going through adb shell, which in my case isn't working)
thank you for any suggestion

Is there a forum for the Huawei Y5(Y560-L01) / Can anyone help get fastboot working?

I am trying to unlock the bootloader on this thing.
I've gone in to Settings > Developer Options and checked 'OEM unlocking'.
I've enabled USB debugging.
I plugged the phone in and issued 'adb reboot-bootloader'.
...Then the phone powers off, comes on and just gives me the Huawei logo as if it is stuck. It does not respond to 'fastboot devices' or 'adb devices', only solution is battery out/battery in.
I then tried powering on using power+volume up to get to recovery (which works) and choosing the option for 'reboot to bootloader'. I get the same Huawei logo screen as above.
I then tried powering on using power+volume down, this takes me to what appears to be a hardware test page which is all in chinese. Looks the same as this: http://imgur.com/a/eE3hb
I have now rooted with Kingroot and tried again, although I know that it shouldn't make any difference at the bootloader stage whether I am rooted or not. But worth a try.
Anyone have any ideas?
Thanks
There isn't a forum for the Y5...but there is this thread full of general info for the Y5: http://forum.xda-developers.com/android/development/huawei-ascend-y5-codename-y560-l01-t3281367
You may find what you need there....

Can't unlock bootloader (iOcean X8 Mini)

Hello,
A friend of my asked me to install a new version on his iOcean X8 Mini.
After a few minutes into the process, I discovered that I couldn't modify anything at all.
Problems start occuring when I enter Fastboot via ADB (I power up the phone, connect it to PC, give it permission to use Android USB Debugging, then via 'adb rebeoot fastboot' I enter the Fastboot menu). Every command I enter here returns 3 dots just doing nothing. My command prompt is unusable after entering a command (for example 'fastboot oem unlock').
I've tried to push a ROM via ADB but this isn't working as well since it returns something like 'no permission' when trying to install, but I figured this was due to the locked bootloader.
Searched all over the internet for solutions, but so far nothing has really worked. What I somehow did mange to do is root the device (don't know if it was by default, I assume not), via RootGenius.
Anybody got any experience with this, and perhaps know some steps I can undertake to indeed unlock the bootloader of this phone?
Thanks in advance!

Alcatel 9051Q Pixi 4(7) fastboot problem

Hello guys!
My device is not booting in boot loader i have run the command of adb devices and my device is recognize by system but adb reboot boot loader command not rebooting device in boot loader and when i run command fastboot oem unlock it stuck at <waiting for device>.
Kindly help me to solve this problem.
Regards,
Taimoor Javaid
I am having the same problem except i cannot boot into bootloader by using the physical buttons either
timimalik said:
Hello guys!
My device is not booting in boot loader i have run the command of adb devices and my device is recognize by system but adb reboot boot loader command not rebooting device in boot loader and when i run command fastboot oem unlock it stuck at <waiting for device>.
Click to expand...
Click to collapse
Hi...
You apparently have enabled developer options and usb debugging. Did you also enable OEM unlocking from the same menu?
---------- Post added at 00:15 ---------- Previous post was at 00:02 ----------
ronin2011 said:
I am having the same problem except i cannot boot into bootloader by using the physical buttons either
Click to expand...
Click to collapse
On your device, go to Settings -----> About phone. Tap 7 times on the “build number“. You should now have enabled developer mode. Go back to the Settings menu and enter "Developer options" and enable USB debugging. Also check “OEM unlocking“. (It might be that you firstly have to connect the phone to a PC and tick “always allow this computer”and then get back to developer options menu and check “OEM unlocking“.
You may then start working with adb and fastboot.
(ps. Be aware that unlocking the bootloader triggers automatic factory reset - you will lose what you have not backed up)
r&xp said:
Hi...
You apparently have enabled developer options and usb debugging. Did you also enable OEM unlocking from the same menu?
---------- Post added at 00:15 ---------- Previous post was at 00:02 ----------
On your device, go to Settings -----> About phone. Tap 7 times on the “build number“. You should now have enabled developer mode. Go back to the Settings menu and enter "Developer options" and enable USB debugging. Also check “OEM unlocking“. (It might be that you firstly have to connect the phone to a PC and tick “always allow this computer”and then get back to developer options menu and check “OEM unlocking“.
You may then start working with adb and fastboot.
(ps. Be aware that unlocking the bootloader triggers automatic factory reset - you will lose what you have not backed up)
Click to expand...
Click to collapse
Hi,
Yes i have enable OEM unlocking option but no success.
timimalik said:
Hi,
Yes i have enable OEM unlocking option but no success.
Click to expand...
Click to collapse
Ok... Step by step... Please make sure you type exactly the commands as shown here:
1. type adb devices if it works, and shows your device then:
2. type adb reboot bootloader. If it works, and you should boot to bootloader. Next:
3. type: fastboot devices. Is you device stiil listed??? If not then there is some kind of trouble here. Your device is listed by adb, but not fastboot. If that is the case I personally do not have experience to help out. The only thing I can think of is that you may have missing drivers that do not allow correct communication between you device and PC.
If that is not the case and your device is listed by fastboot, then:
4. type: fastboot oem unlock. It will show that it is waiting. You will have to look at your device's screen and by using the devices buttons CONFIRM oem ulocking (on your device, not the windows command prompt)
5. If all goes well, your device should ask ask to reboot. Either reboot from menu, or just hold down the power button for a while.
6. After reboot, if all went well, your device will restart and perform an automatic factory reset. You cannot do anything about it. It just happens with OEM unlocking. At this point let it boot normally, and re-enable developer options and usb debugging to continue with root process, or anything that you want to do.
Can't thing of anything else for the moment... Let us know how it goes, perhaps a more experienced member, could share some insights???
I have already enabled usb debugging and oem unlocking yet neither adb reboot bootloader nor using the volume down + power button boot into bootloader mode, both of them lead to the tablet restarting normally to system
r&xp said:
Ok... Step by step... Please make sure you type exactly the commands as shown here:
1. type adb devices if it works, and shows your device then:
2. type adb reboot bootloader. If it works, and you should boot to bootloader. Next:
3. type: fastboot devices. Is you device stiil listed??? If not then there is some kind of trouble here. Your device is listed by adb, but not fastboot. If that is the case I personally do not have experience to help out. The only thing I can think of is that you may have missing drivers that do not allow correct communication between you device and PC.
If that is not the case and your device is listed by fastboot, then:
4. type: fastboot oem unlock. It will show that it is waiting. You will have to look at your device's screen and by using the devices buttons CONFIRM oem ulocking (on your device, not the windows command prompt)
5. If all goes well, your device should ask ask to reboot. Either reboot from menu, or just hold down the power button for a while.
6. After reboot, if all went well, your device will restart and perform an automatic factory reset. You cannot do anything about it. It just happens with OEM unlocking. At this point let it boot normally, and re-enable developer options and usb debugging to continue with root process, or anything that you want to do.
Can't thing of anything else for the moment... Let us know how it goes, perhaps a more experienced member, could share some insights???
Click to expand...
Click to collapse
The problem is at Step 2 adb reboot bootloader only reboot device not booting it into bootloader.
anyone else getting this problem?
Let's wake this thread in a bang! ?
Come on guys! Did anyone manage to deal with the problem? I have absolutely the same issue. Step 2 is the problem for me too. No fastboot mode neither through adb reboot bootloader nor the tablet physical buttons. I get either a normal reboot or the stock recovery which has not many options.
Any help would be appreciated!
Thanks in advance!

Hotspot

Hi guys,
Anyone else had issues with the wifi hotspot turning itself off? It worked fine for months but now turns off within 10 secs - it's not a time out issue either... Has me stumped.
Running stock 6.0 but I'm presuming it's an app causing the issue, struggling to find the culprit though. Thanks in advance
I had the exact same problem.
The hotspot always worked fine but around June 2017 the Wi-Fi hotspot was turning off after around 10 seconds.
This issue was present even with the phone in safe mode.
So, I flashed the latest official Nougat ROM (7.0) to solve this issue.
After flashing, even with the data on, I was not getting Internet on tethered devices.
I solve this issue by doing this:
1) Make a coffee.
2) Enable developer mode (Go to Settings -> About phone, and click on the Build number until the developer mode is enabled).
3) Enable USB debugging under Settings -> Developer options
4) Connect the Android device with an USB cable to a computer using the "Minimal ADB and Fastboot" software (or another of your choice).
5) Open the Windows command prompt (cmd.exe) with administration permissions. Navigate into the "Minimal ADB and Fastboot" folder.
6) Optional but recommended to make sure that the Android device is recognized. Type: adb.exe devices
NOTE: Keep an eye in your device (phone/tablet) because you must accept the connection.
7) MAKE SURE THE DEVICE IS DETECTED... Some ID must appear like this:
List of devices attached
XXXXXXXXXXXXXXX device
8) Now start an adb shell. Type: adb shell
9) In the adb shell, run this command: settings put global tether_dun_required 0
The 7.0 ROM still has hotspot issues. Sometimes, some devices, can't connect to the hotspot. After turning on/off the Wi-Fi and then turn on again the hotspot the issue disappear. But the issue comes back again very frequently.

Categories

Resources