Azpen A729 fastboot interface - Android Q&A, Help & Troubleshooting

For those of you who have inter-connectivity through ADB with your Azpen A729 , but have lamented that fastboot seems not to work with this device, listen up. Please note, however that I will not be responsible for what you may do to your Azpen tablet whilst at the fastboot command line. From there you're on your own.
It's all quite easy. This Azpen tablet presents itself with USB vendor id 1f3a to your PC. Surely you're aware of this already as you've been communicating with your tablet through the ADB shell and have included something similar to SUBSYSTEM=="usb", SYSFS{idVendor}=="1f3a", MODE="0666" in your udev rules. Oh yeah, remember that... {idVendor}=="1f3a"? It all comes back to you now. All you need to do with fastboot is to explicitly identify the USB vendor id as 0x1f3a on the command line. Let's give it a try:
First put the Azpen A729 in bootloader mode:
Code:
# adb root
# adb reboot bootloader
Have a sip of coffee.
Now invoke fastboot with the following:
Code:
# fastboot -i 0x1f3a devices
Android Fastboot fastboot
Notice now that your tablet responds as an Android device in fastboot mode and all fastboot command-line arguments are available to you. Please be careful. May I suggest this one:
Code:
# fastboot -i 0x1f3a continue
resuming boot...
OKAY [ 0.009s]
finished. total time: 0.009s
That simply continues the boot process and you're back to normal on your tablet.
Once again, please be careful. Be safe. You've been empowered.
- PoFolk

How do you unlock the Azpen A729 bootloader?
Again, this is quite simple. You must do absolutely nothing. The Azpen A729 tablet ships with the bootloader unlocked and with the super user (su) binary enabled. Here is the fastboot response from my unrooted, stock Azpen A729:
Code:
# fastboot -i 0x1f3a oem unlock
...
FAILED (remote: system is not locked)
finished. total time: 0.016s
Now if you are adventurous, skeptical, curious, or all of the above and need further "proof" that your Azpen is already unlocked, you could very easy toggle its bootloader status with the following command. HOWEVER, I suggest that you firstly backup your user data as you'll want to unlock it again and in the process of toggling between lock and unlock the user data will be wiped. Still want to do it? Here ya go:
Code:
# fastboot -i 0x1f3a oem lock
...
OKAY [ 0.016s]
finished. total time: 0.016s
Now your Azpen is locked. To unlock it again simply execute:
Code:
# fastboot -i 0x1f3a oem unlock
...
OKAY [ 10.707s]
finished. total time: 10.707s
Notice that it took a little more than 10 seconds to unlock. Why? Your user data was being wiped, but not-to-worry. You backed it up before running this experiment.
Once again, be careful. Be safe. You've been empowered.
- PoFolk

Have you tried flashing a backup of your system img yet?

Related

Unlock Nexus Q

Unlocking Your Nexus Q
To unlock your device
1. cd to platform-tools
2. Reboot to the bootloader - adb reboot bootloader
3. Unlock your device* (with fastboot tool type): fastboot oem unlock
*You will have to accept and erase all the user data on the tablet.
*You must run this as sudo in Linux
Credits to FadedLite (very similar steps)
Figuring out the rooting next
If you just need "su"....
1. Download su from your busybox installation from say Galaxy Nexus.
2. Download the modified clockworksmod for Nexus Q that this guy put together:
bliny.net/blog/post/How-to-Root-Nexus-Q-%28Temporarily%29.asp
3. Boot into that recovery image will give you write access to /system
4. adb push su into /system/xbin/su
Did you already have your nexus Q in debug mode? I do not have the slider button on my Nexus 7 to put it into debug mode. It's not recognized in "adb devices" or "fastboot devices"
EDIT ***
I found out that the USB Debugging menu in the Nexus Q app shows up when you turn on Developer Options in the Settings > Developer Options menu of Jellybean on the Nexus 7. You might want to test this as well on your variety of devices.
Just me that thinks this thing needs google TV?
nevermind it worked now
Stuck in oem unlock
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
took me a few tries to get it but it needs to be entered within five seconds of the first command
enriquealo said:
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
Click to expand...
Click to collapse
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
silfa718 said:
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
Click to expand...
Click to collapse
the easiest way, assuming you are running windows, is to enter the comands once, and then just use the up arrow key to do it again. also, you may want to be sure its not already unlocked "fastboot getvar unlocked" will return "yes" if unlocked

[GUIDE][BRICKED] [BOOTS ONLY TO RECOVERY][All ASUS TRANFORMERS]

This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ....
Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog
Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME
A message from _that
_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx for all your help @_that

HDX 7 only fastboot posible

hi
i try to install a custom firmware. i think i do many wrong things(i try many of the instructions). before i started the hdx had the latest firmware!
Now when i start the hdx7 it show "Kindle Fire"(gray), then the display is red for less then a second. after this it shows fastboot logo (also, if the cable is not connected)
On my WINDOWS 10 PC i have install "Minimal ADB and Fastboot". When i enter fastboot devices. i get this:
00D2070834110HS3 fastboot
any chance?
thx
atik03 said:
hi
i try to install a custom firmware. i think i do many wrong things(i try many of the instructions). before i started the hdx had the latest firmware!
Now when i start the hdx7 it show "Kindle Fire"(gray), then the display is red for less then a second. after this it shows fastboot logo (also, if the cable is not connected)
On my WINDOWS 10 PC i have install "Minimal ADB and Fastboot". When i enter fastboot devices. i get this:
00D2070834110HS3 fastboot
any chance?
thx
Click to expand...
Click to collapse
See last couple paragraphs in this post.
Davey126 said:
See last couple paragraphs in this post.
Click to expand...
Click to collapse
i get this:
Code:
fastboot -i 0x1949 erase aboot
erasing 'aboot'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.003s
Code:
fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.009s
Code:
wmic partition where index=22 get diskindex
Keine Instanzen verfügbar.
(No instances available)
atik03 said:
i get this:
Code:
fastboot -i 0x1949 erase aboot
erasing 'aboot'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.003s
Code:
fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.009s
Code:
wmic partition where index=22 get diskindex
Keine Instanzen verfügbar.
(No instances available)
Click to expand...
Click to collapse
Appears you are out of luck. Sorry ...

Ematic EGQ375 Help with Root & Bootloader Unlock

I just bought a Ematic EGQ375 tablet and I'm looking to root it.
These are the specs of my device:
Model: EGQ375
Android Version: 7.1.2
Android security patch: January 5, 2018
Kernel version: 3.10.104
[email protected] #1
Thu Feb 8 17:26:56 CST 2018​Build number: EMATIC_EGQ375_20180208
I searched around in here and on Google but haven't been able to find anything relevant for my device only for older devices. The solutions that were given didn't work for my device.
For Unlocking Bootloader this is what I tried:
Code:
adb devices
This worked fine. Then I did
Code:
adb reboot fastboot
On this there was no results it just gave me back the prompt. I checked to see if fastboot worked as follows
Code:
fastboot devices
0123456789 fastboot
This did not seem right. I still went and tried to unlock with the following
Code:
fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
But when I do
Code:
fastboot oem device-info
...
FAILED (remote: device is locked)
finished. total time: 0.003s
This seems to show me that it didn't unlock.
I also tried fastboot flashing unlock instead of fastboot oem unlock but I got the same results. (Only one difference if failed with this message "FAILED (remote failure)"
Please see attached picture for the actual command I typed in.
Any help in unlocking and in rooting this device will be greatly appreciated.
Isr

i try to install lineageOS and got a black screen

Hello i have a sony xperia Z1 and try to install lineageOS. I follow this guide : wiki.lineageos.org/devices/yuga/install
when i try :
Code:
adb push twrp-x.x.x-x-yuga.img /sdcard
bash say permission denied. But previously i have
Code:
Bootloader unlock allowed: Yes
As i am totally new, i try to restart all the install instruction in bash with root access # (command su).
And now a i have a black screen and adb doesn't work
Code:
[email protected]:/$ adb shell
error: no devices/emulators found
but it seem that fastboot mode is ok because i can flash rom
Code:
[email protected]:~$ fastboot devices
BH915GK90D fastboot
[email protected]:~$ fastboot flash boot twrp-2.5.0.0-yuga.img
target didn't report max-download-size
sending 'boot' (9038 KB)...
OKAY [ 0.357s]
writing 'boot'...
OKAY [ 0.604s]
finished. total time: 0.961s
After that if i try to reboot to the TWRP recovery:
Code:
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.052s
[email protected]:~$
the notification light turn red, off, red, off, green and after off.
So i got a black screen.
If i press the power button, nothing happen.
So i anyone could help me ... Thank you in advanced.

Categories

Resources