I bought what appears to be a manufacturer refurb or overstock on ebay that arrived in totally unused condition (protective film on the screen; shrink wrapped oem charger).
I immediately unlocked the bootloader and now it is running Resurrection Remix nougat.
The problem is that when I first plug in *any* charger, it looks like the tablet is charging from the icon in the status bar but Ampere tells me that it is plugged in but not charging. Wiggling various USB cables in the port does not restore charging.
However, if I leave the tablet plugged in and restart, upon restarting the tablet is now charging normally, albeit very slowy, ~450Ma.
I can't tell if this is a hardware or a software problem. If it's software, I guess I could live with going back to stock 7.0 but if the port is faulty I don't know if I want to keep the device.
I can return a defective unit at no cost to me but obviously I would need to return it to the state in which I received it: stock 10c with the bootloader locked.
Will 'fastboot oem lock' in adb mode relock this tablet's bootloader? If so should I relock the bootloader after or before restoring 10c from the stock .kdz via LGUP and Uppercut? Am I correct in thinking I can downgrade to marshmallow stock from RRemix nougat?
Thanks.
Did you ever figure this out?
cookiemonster79 said:
Did you ever figure this out?
Click to expand...
Click to collapse
This worked for me on my V521....
Open 'Command Prompt' and type in 'adb shell'
Enter these commands into ADB Shell for your device:
reboot bootloader
fastboot oem lock
fastboot reboot
Related
Hello,
I have an EVO 3D that was having screen issues.
When I took it to the Sprint store they said my warranty was void for having ViperRom on the device.
The device was HTC unlocked and had ViperRom redline.
I asked them to not note that down and that I would come back tomorrow with the device back to stock settings.
I made a mistake though when I manually flashed a boot.img using adb.
Now I just get a blank screen when the phone starts. I am not able to enable USB debugging or disable fastboot.
Now I can get into the bootloader by using power and the down key.
Since the phone is in Unlocked Mode and S-ON I can't update through ADB without USB debugging or fastboot disabled.
Also any PG86IMG.zip on the SD card doesn't ask for an update when the phone is HTC unlocked
There is no bootloader option to relock the phone either.
If anyone can please help I would greatly appreciate it. I'm supposed to go back there today 9/18/2012 at 4PM PST
Are you able to get into fastboot on your phone? If so what you have to do is relock your bootloader first. Fastboot oem lock is the command. Your phone should pick up the pg86img file and update.
Jsparta26 said:
Are you able to get into fastboot on your phone? If so what you have to do is relock your bootloader first. Fastboot oem lock is the command. Your phone should pick up the pg86img file and update.
Click to expand...
Click to collapse
I can't relock the bootloader using any PC tools. I can get into the bootloader menu by pressing Vol- but since the phone give a black screen when I try to booth I cannot enable USB debugging nor disable fastboot. I think this is what is preventing me from being able to connect to the phone via USB... I'm working on that assumption however I could be wrong.
mateo650 said:
I can't relock the bootloader using any PC tools. I can get into the bootloader menu by pressing Vol- but since the phone give a black screen when I try to booth I cannot enable USB debugging nor disable fastboot. I think this is what is preventing me from being able to connect to the phone via USB... I'm working on that assumption however I could be wrong.
Click to expand...
Click to collapse
I can see when I turn the phone on it's actually functioning, just with a black screen. It still makes noises for receiving text and so on I just can't enable usb debugging and disable fastboot blind. I wonder if I found my HDMI adapter if an external display would work. That would be weird.
mateo650 said:
I can see when I turn the phone on it's actually functioning, just with a black screen. It still makes noises for receiving text and so on I just can't enable usb debugging and disable fastboot blind. I wonder if I found my HDMI adapter if an external display would work. That would be weird.
Click to expand...
Click to collapse
UPDATE: I figured it out that just by selecting fastboot and THEN connecting the USB I could get USB connectivity!
I'm trying to relock my bootloader and unroot because I cracked my screen and wish to use my insurance to get a new DNA. My computer recognizes my phone when the phone is on, but when i boot into bootloader, the computer does the two beeps like a connection has been found but then is followed by 3 low pitched beeps like it failed. I'm S-ON. I can't do any work on my phone when in bootloader. When I try to enter the command "fastboot oem lock," it just says <waiting for device> I've installed the latest version of HTC Sync Manager so i'm sure the drivers are up to date.
HosstaLaVista said:
I'm trying to relock my bootloader and unroot because I cracked my screen and wish to use my insurance to get a new DNA. My computer recognizes my phone when the phone is on, but when i boot into bootloader, the computer does the two beeps like a connection has been found but then is followed by 3 low pitched beeps like it failed. I'm S-ON. I can't do any work on my phone when in bootloader. When I try to enter the command "fastboot oem lock," it just says <waiting for device> I've installed the latest version of HTC Sync Manager so i'm sure the drivers are up to date.
Click to expand...
Click to collapse
Try a different usb port. Uninstall HTC Sync, as I have seen sync cause problems before. Also try using a different cable if you have one. I have an old T-Bolt cable that will let you charge and transfer, but will not recognize phone in bootloader.
when in bootloader make sure that you are in fastboot and it says "fastboot usb"
So I tried Unlocking Bootloader with a made up unlock.bin.
Word of warning be careful if you try it.
This is my experience: OEM UNLOCK with a made up bin phone gives a warning about wiping.
Out of curiosity I wanted to see if it would just fail out it didn't, but instead wiped the phone like it was unlocking the BL, I went into bootloader to check it was still locked (as expected).
But doing the procedure did something to my bootloader. If the phone is off (shutdown) and I plug it into the charger it will immediately boot into bootloader on it's own without me touching the power button.
Also from a powered off state if I power like normal it will boot to bootloader screen instead of system, from which I can boot into the system without issues and the phone works fine.
From a powered up state If I hold the power button for safe mode it will reboot into bootloader mode and then I have to start the phone to get to safe mode.
Has anyone else experienced this? Would reflashing the Nougat firmware correct it?
If not I am fine with the phone the way it is.
Get in bootloader and type: fastboot oem fb_mode_clear
It's a command to close the "startup directly into bootloader". Device should start normal again.
Bender1987 said:
Get in bootloader and type: fastboot oem fb_mode_clear
It's a command to close the "startup directly into bootloader". Device should start normal again.
Click to expand...
Click to collapse
Thank you I will try that when I get home this evening.
Edit: that solved the issue I think I'll leave the boot loader alone for awhile lol.
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
I am trying to install stock firmware through fastboot. After typing below command,
Code:
adb reboot bootloader
the Device reboots but Fastboot mode only shows for 1 second then the Device reboots to system.
I have Usb debugging ON, OEM unlocking ON
Tried on 2 different PC's. Also tried removing Usb after command.
Reason for stock flashing is just that I used this ADB command on my phone and It lost IMEI: By this method and here is the detailed problem.
UPDATE: Took the phone to service center, they changed the Mainboard. But then Fingerprint was not working (couldn't enroll). They took it again and tried stock flash and fingerprint sensor change but the issue persists, still diagnosing.
shantam22 said:
I am trying to install stock firmware through fastboot. After typing below command,
Code:
adb reboot bootloader
the Device reboots but Fastboot mode only shows for 1 second then the Device reboots to system.
I have Usb debugging ON, OEM unlocking ON
Tried on 2 different PC's. Also tried removing Usb after command.
Click to expand...
Click to collapse
Fastboot is locked.
Unlock fastboot official program.
crocodil said:
Fastboot is locked.
Unlock fastboot official program.
Click to expand...
Click to collapse
My phone has lost Network service and IMEI is null. I did not root. I did this: Method
Does that mean I need to unlock bootloader to flash the stock ROM? Is there any other method? I don't want to lose warranty.
The phone does boot to EDL mode.
shantam22 said:
My phone has lost Network service and IMEI is null. I did not root. I did this: Method
Does that mean I need to unlock bootloader to flash the stock ROM? Is there any other method? I don't want to lose warranty.
The phone does boot to EDL mode.
Click to expand...
Click to collapse
Flash stock rom in twrp mode. See the download in guide section
akashavel said:
Flash stock rom in twrp mode. See the download in guide section
Click to expand...
Click to collapse
Can I achieve this without voiding my phones warranty?
I finally took the device to service center. And the executive said he would send the case to Realme and he is not certain that it would be covered under warranty as the imei is broken. But my device's bootloader is untouched and I never tried rooting.