Related
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Firmware/Rockchip_CPU_based/Rockchip_Batch_Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Hi, the multiupload link seems down, would it be possible to re-up? thanks!
And how exactly are you supposed to install the drivers from the driver folder? Because those are not Runable files, theyre drivers, with no install command. So, my daughters nextbook is bricked, wont install drivers(says not successfully installed after i plug it in) and there is no way to install the drivers from the batch file. Anything you left out??? Id like to unbrick this thing. Thanks..
SOLVED
I found out how to install the drivers on windows 7!
Follow this:
click the start button > type in the search box right above the start button "device manager"
(make sure the tablet is plugged in and in USB MODE)
right click the tablet or unknown device
select install/update driver manually
browse for the driver in the download folder then it should be updated
worked for me.
Nextbook 8 stuck in bootloop
I am a noob. My Nextbook 8 is stuck in bootloop, the last app i downloaded was firefox. Ive read that this can be fixed by starting safe mode and doing a factory reset, how do i do this?!? Im desperate, and would greatly appreciate any help that works, thanks.
Hi guys,
Phone is unrooted. I just upgraded to windows 10 and laptop no longer recognizes device. I tried doing a search and nothing comes up
Can someone point me in the right direction please?
install drivers but first use this. now you open prompt command with administrator permission and write this: bcdedit -set TESTSIGNING ON. Restart and try to reinstall driver
Xandros97 said:
install drivers but first use this. now you open prompt command with administrator permission and write this: bcdedit -set TESTSIGNING ON. Restart and try to reinstall driver
Click to expand...
Click to collapse
Which drivers? I do not believe the win 10 driver is out. The only one that I found is for win 8.1
Try pc companion. I'm on Windows 10 with my test computer and it recognizes my phone. Only problem I'm having is with flashing rooms but apparently that's a known issue for my particular problem.
texaslittleangel said:
Which drivers? I do not believe the win 10 driver is out. The only one that I found is for win 8.1
Click to expand...
Click to collapse
Windows 10 can use Windows 8 drivers no problem. As previously stated, you may need change your start-up settings to disable driver signature verification.
Message I get
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>bcdedit -set TESTSIGNING ON
An error has occurred setting the element data.
The value is protected by Secure Boot policy and cannot be modified or deleted.
texaslittleangel said:
Message I get
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>bcdedit -set TESTSIGNING ON
An error has occurred setting the element data.
The value is protected by Secure Boot policy and cannot be modified or deleted.
Click to expand...
Click to collapse
Did run the command prompt as admin? Either way, just do this:
1) Go to start
2) Click "Power"
3) Click "Restart" while holding down the Shift key
4) In the next screen that comes up, click the "Troubleshoot" option
5) Now click "Advanced Options"
6) Click "Startup Settings"
7) On the next screen click "restart"
8) On the next screen hit "7" on your keyboard for "Disable Driver Signature Enforcement"
Then install whichever drivers you need. After they're installed, you can reboot normally and enjoy the drivers.
Bloodlvst said:
Did run the command prompt as admin?
Click to expand...
Click to collapse
Yes I did.
Bloodlvst said:
1) Go to start
2) Click "Power"
3) Click "Restart" while holding down the Shift key
4) In the next screen that comes up, click the "Troubleshoot" option
5) Now click "Advanced Options"
6) Click "Startup Settings"
7) On the next screen click "restart"
8) On the next screen hit "7" on your keyboard for "Disable Driver Signature Enforcement"
Then install whichever drivers you need. After they're installed, you can reboot normally and enjoy the drivers.
Click to expand...
Click to collapse
THIS worked like a charm!!! THANK YOU :victory: :good:
One fix down a few more to go. I'm having several issues with Win 10 on my laptop.
Glad it worked! Let me know if you have any more Windows 10 related issues
Bloodlvst said:
Glad it worked! Let me know if you have any more Windows 10 related issues
Click to expand...
Click to collapse
That is very kind of you. I have all sorts of issues with win 10 with my laptop no others with my phone (thus far)
Which driver did you use please? I've installed the PC companion but that made no difference
texaslittleangel said:
Yes I did.
THIS worked like a charm!!! THANK YOU :victory: :good:
One fix down a few more to go. I'm having several issues with Win 10 on my laptop.
Click to expand...
Click to collapse
vilvic said:
Which driver did you use please? I've installed the PC companion but that made no difference
Click to expand...
Click to collapse
There a driver included in the Xperia Flashtool. Install that and you're good to go.
This unfortunately didn't work for me either.
After u did all the steps with the right drivers, i tried first time and did not worked, then i conected in flashmode and select the image again, i had the message runing that is conected in flashmode. I run it and worked
I'm gonna try I will get back to ya!
Unable to update Xperia Z3V
So i'm on a windows 10 machine with a sony xperia Z3V i'm unable to get the pc and phone to flash and to get this updated on the new version of Lollipop or marshmellow. I get to the flashboot and when i try to run it i get
04/059/2016 01:59:02 - INFO - Checking header
04/059/2016 01:59:02 - ERROR - Processing of loader.sin finished with errors.
04/059/2016 01:59:02 - INFO - Ending flash session
04/059/2016 01:59:02 - ERROR - Error in processHeader : 1 : Incorrect function.
04/059/2016 01:59:02 - ERROR - Error flashing. Aborted
04/059/2016 01:59:02 - INFO - Device connected in flash mode
I'm not sure why this isn't working i've been looking for something all night on this and I can't find jack. All i keep seeing is no matter what windows 10 installs the MTP USB Device for the xperia and the windows 10 Phone companion takes over from there. I tried using the sony companion and it never shows that i can do anything with the software but "restore" the phone. I've done several resets on the phone taking it back to stock and runing version 4.4.4 kitkat but I'd really like to get this updated or possibly find something else that will run on the machine.
Can anyone help? I've done all this stuff on alot of Samsung Devices and it seemed so much easier. I'm not sure if its because its a sony phone or because i'm on windows 10 now.. I'm thinking it could be a combination of both.
My friend also has the same model and tried to contact sony but they said because we are in the USA they can't help us. The updates from verzion keep failing on both our phones as well that can take us to atleast 5.1 Lollipop
Haveing Same Issue With My Xperia L and ZR, It Only Charges, But Can Browser Storage, Did Everything From Booting In Disable Driver Signature Installed Xperia Companian, Flashtool Drivers Still Cant See My Device Storage On Pc, But Can USe Flashtools
Hi,
I have a rooted Xperia Z5 and I would like to update my firmware to 32.2.A.0.305.
I used to do firmware updates many times before using flashtool on my windows 7 machine.
Recently I switched to windows 10 and now need to reinstall the fastboot driver.
I downloaded the driver from sonymobile webstie:
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Unzipped the file, and got a directory with the "android_winusb.inf" file.
Booted the phone in "bootloader" mode via the TWRP recovery (LED on phone is blue).
The regular method of power down, volume up+connect to USB did not work. The LED was blue for a second and then turned off.
When in "bootloader/fastboot" mode, opened the windows "device manager" and found the problematic S1 device.
Right click on it, update driver, browse my computer, pointed to the directory where the ".inf" file is located.
Windows "makes sounds" as if it is installing the driver, but then gives an error:
"Windows found a driver software for your device but encountered an error while attempting to install it"
"Android ADB interface"
"The system cannot find the flie specified"
I have no idea what the problem is.
A few posts suggested that this might be a driver-signing problem with windows 10.
They suggested removing the "driver-signing" option and try. Did not work.
I also tried this with a virtual machine Windows 7 that I have installed, and got the same error, so I'm not sure it is a windows version problem.
I read in one place that this is an error with the location of the file and that it should be located under the "C:\Windows\WinSxS" directory.
Tried that as well, and no luck.
Does someone have any idea what the problem is?
Alernatively, if someone can explain or point me to a post of how to use fastboot and flashtool with linux,
that can also help.
Thank you.
Avi
driver signature verification
1. Goto START (windows icon);
2. Keep pressing SHIFT, klick POWER and RESTART
(shift is pressed all the time along);
3. Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button.
When your computer restarts you'll see a list of options.
4. Press F7 on your keyboard to select Disable driver signature enforcement.
Your computer will now restart and you’ll be able to install unsigned drivers.
This is firt to do, but didnt quite get it if you tried this allready. Greetings
Have the same problem. Disabled driver signature enforcement. Did not help
Are you sure it's disabled? Some pc's don't have the option to disable the driver signature enforcement. If that's the case you need to enter the bios settings and look for the tk keys and delete them, then restart your pc and you can install the fastboot driver.
Hope this helps
Had the same issue on my new setup.
This solved all my problems: https://forum.xda-developers.com/xperia-z/help/help-findiing-installin-s1boot-fastboot-t2218143
dim4x4 said:
Have the same problem. Disabled driver signature enforcement. Did not help
Click to expand...
Click to collapse
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
L33Tgod said:
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
Click to expand...
Click to collapse
Nice and cool - but we still dont have a Sony Xperia Z5 Driver from it in the List
First let's get the warnings out of the way:
This is a dangerous tool. It can render your device permanently unusable.
If you use it, your warranty will likely be void.
You accept all responsibility for the consequences.
This is not an official ZTE unlock tool. The official ZTE unlock tool is in another thread.
Acknowledgments
Special thanks to @rombdeta for providing the OEM programmer binary. This would not be possible without his help.
What is tuliptool?
This tool allows you to:
Check status of your boot loader
Unlock your boot loader
Lock your boot loader
Install a custom recovery
Install a custom boot image
NOTE WELL
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Locking and unlocking will erase all user data. Make sure you backup first!
The zip includes:
tuliptool for Linux
tuliptool for Win64
tuliptool for Win32
tuliptool for MacOS
Preparation
1. Extract the package.
You will find the binary files listed above. Note: This is a command line utility, so you must open a command prompt to run it.
2a. Setup for Linux
Create a file named /etc/udev/rules.d/99-qcom.rules with this content exactly as shown:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
Ensure your login user is in the plugdev group.
2b. Setup for Win32/Win64
Download zadig.
Connect your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so you can cancel if you wish, but it won't hurt anything.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Disconnect the device.
2c. Setup for MacOS
No setup should be necessary.
3. Download boot and/or recovery files to flash.
You will find these in other threads in this section.
Connecting in EDL mode
Via adb
This should work for all models, but you need adb access.
adb reboot edl
Via key combo
If you have a US model device (or the aboot from a US model device) you may use the key combo:
Power off and unplug the device.
Hold both volume buttons.
Plug device into your PC.
Wait about 3 seconds and release the buttons.
Note: There will be no feedback on the device -- no lights, no vibration, nothing. The only way to verify that the device is in EDL mode is that device 05c6:9008 is visible on the PC.
Usage: (un)locking
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, unlocking seems to be completely unnecessary. This section is mostly provided for completeness.
tuliptool lock status
tuliptool lock unlock
tuliptool lock lock
Usage: reading boot/recovery
Note command line options have changed
tuliptool read boot
tuliptool read recovery
Usage: writing boot/recovery
Note command line options have changed
tuliptool write boot <filename>/I]
tuliptool write recovery <filename>
So, for example, to write a TWRP image, run:
tuliptool write recovery tulip-twrp-7.1-r1.img.
Multiple operations
This is a "one shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish do perform multiple operations (eg. backup, unlock, flash), simply hold down the volume buttons while the device resets and it should go back to EDL mode.
Download
tuliptool.zip
md5=58f34850005510b51a832d27a6bce607
Common problems
Device not found: first enter EDL mode, then run the tool.
Device is visible in device manager or lspci but cannot be found by the tool: connect directly to the PC, not through a hub.
Windows says bad file descriptor: the WinUSB driver is not installed.
Linux says permission denied: your login user is not in the plugdev group.
Why call it tuliptool?
Tulip is the device "code name" for the Axon 7 Mini (at least the US version).
first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
Perhaps try running it as administrator? I'm heading home from work and then I'll be taking a shot at this myself.
I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Meme Queen said:
first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
Click to expand...
Click to collapse
tdm said:
I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Click to expand...
Click to collapse
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I guess im stuck waiting for the update.zip because Zadig is refusing to install drivers. no matter what i do it will not install drivers. it keeps telling me "Remote Source Not Allocated: Driver install Aborted"
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Meme Queen said:
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse
tdm said:
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Click to expand...
Click to collapse
thanks! if there's any information you want me to provide, just let me know.
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
pxzei said:
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
Click to expand...
Click to collapse
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
MrWhite0429 said:
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
Click to expand...
Click to collapse
tdm said:
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
Click to expand...
Click to collapse
Device Shows connected and drivers installed under device manager.
Command prompt is being run as so:
Start --> type cmd ---> Right click on Command prompt ---> Run as Administrator
cd C:\users\admin\desktop\tuliptool
C:\users\admin\desktop\tuliptool> tuliptool-win64.exe lock status
Device Not Detected
---------- Post added at 03:59 AM ---------- Previous post was at 03:38 AM ----------
UPDATE:
I found that I had to use a USB 3.0 hub in order to get the phone to be detected.
Once detected I ran commands as followed.
tuliptool-win64.exe lock unlock
(The unlocking procedure said it failed, phone bootlooped three times, then it showed as unlocked when I ran the Lock status command)
tuliptool-win64.exe read boot
(This created the backup-boot.bin file in the directory)
Tuliptool-win64.exe read recovery
(This created a backup-recovery file in the directory)
tuliptool-win64.exe write boot
Its at this point here I get a Runtime Error as well. The entire process comes to a halt.
Thsnks, tried that, but no luck. It's still stuck on the splash screen.
Update: The device is running B09 7.1.1, The charger seems to be ZTE authentic. Single sim variant. If you need more info, let me know.
rombdeta said:
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
Click to expand...
Click to collapse
tdm said:
This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device.
[/B][/COLOR]
Click to expand...
Click to collapse
Awesome you got the tool out, I think I am going to wait for the 'Official' tool so if I ever need to send it in for repair in the next 2 years I can say 'well I used your tool' lol
Can't wait to see the roms @tdm, keep it up and I think the mini is going to get a lot more interesting.
I'd like to get a bloat removed(if any) and more lightweight faster rom on mine, maybe try the latest cyanogenmod or w/e they call it now and AOKP, etc.
New roms without MiFavor would be awesome too and ones that improve performance!
ZTE
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.
CRAFTER0302002 said:
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.
Click to expand...
Click to collapse
First post:
"This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device."
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
tdm said:
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
Click to expand...
Click to collapse
as in rename to recovery.bin?
Yes, that.
MrWhite0429 said:
as in rename to recovery.bin?
Click to expand...
Click to collapse
The ZTE blocks all attempts to install rooting app/apk. 3rd party installation is selected the thing is that when the waring box appears and I hit the drop down tab, the area is blank and there is no option to continue. I have no network connectivity on my laptop so PC methods fail. Have unlimited 4lte data on my stylo 3 m430 but cannot use wifi or USB tethering, didn't pay for it. Any ideas? More complicated is my soft bricked Lgls751zv5, boot loop with Security Error: authentication fail #9]. I believe the underlying problem, if I remember and am correct it is a matter of a bad path but idk. Have been able to boot into recovery menu, soft reset menu, firmware update screen and briefly a screen with a Android character, chest open, with the words no command. I have many tools only some of which work: LG Flash Tool 1.8(LG USB/Parallel Lock Key is not detected, LGUserCSTool(inert dialog box with question marks does not detect devices,)SPFlashToolv5. 1720win,... Actually I got a bunch, all but only LG Bridge works. I have used ADB/ADB Master to issue several commands with varied success. The only option from the recovery menu is ADB Sideload where the device is recognized. Remount, USB, sync, push etc fail. I did install a zv5 boot zip which it accepted and went into mode I described with android figure(bootloader??? ). In recovery menu [LGE] [Recovery] frst_status is 5 where it previously was status 6 before I fd with it. Repeatedly attempted SD card installation but always get footer is wrong, Signature failure. Tried running my zip and img files thru a signature app but no luck. Recovery logs say, got arguments from boot message locale is [en_US], stage is [d], reason is [{null}], can't open /dev/ttyo: no such file or directory. Build properly says it got 01/11/2015 security patch. Fastboot oem unlock fails.. Every thing fails. Any advice is welcome and I appreciate all who take the time to respond. *frustrated *