Hi,
I'm new here so I'll make it the most clear I can.
Device: LG P760
Date of production: on battery it is 02.2013 but it was in repair back in the middle of 2014 and god knows what it has been done there. Probably change of whole mainboard
Soft: Stock 10(someting) on Android 4.0.4 -Branded > Update to 20h JellyBean - Branded >>service>> not branded 20h > Flashed manually 20b Europe Open
EDIT: AP Bootloader Version: LK May-2012 (From hidden menu)
Target: Unlock bootloader
What have I done so far:
Windows 7
1. Standard console
Code:
adb reboot oem-unlock
2. RomToolkit 2
3. LGL9Toolkit
4. Bunch of scripts found here
5. Omap4boot
Result: Pretty much reboot of system without any effects
Linux Ubuntu 14.10
1. Standard console
Code:
adb reboot oem-unlock
Result: reboot of phone without any effects
2. Connecting via fastboot and
Code:
fastboot oem unlock
using modified by myself script found somewhere
Code:
#!/bin/sh
which fastboot || echo install fastbooot first, e.g. on ubuntu sudo apt-get install android-tools-fastboot
which fastboot || exit
echo 'Connect LG L9 *without battery* to PC using data cable'
sudo ./usbboot p940-aboot.2nd p940-u-boot_fastboot.bin && echo usbboot ok || exit
echo 'DO NOT disconnect usb cable. Insert battery, then press enter'
read x
sleep 10
echo fastboot devices:
sudo fastboot devices
echo 'UNLOCK'
sudo fastboot oem unlock
which resulted in:
Code:
/usr/bin/fastboot
/usr/bin/fastboot
Connect LG L9 *without battery* to PC using data cable
waiting for OMAP44xx device...
reading ASIC ID
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: de1584c8b14d699fb234d5c31e2cdd6a9932669d
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
[*] msg size = 4
[*] data size = 21552
waiting for 2ndstage response...
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
** Done **
usbboot ok
DO NOT disconnect usb cable. Insert battery, then press enter
fastboot devices:
0A3F08331801D013 fastboot
UNLOCK
...
FAILED (remote failure)
finished. total time: 0.000s
That is pretty much everything. I've read about some magic cable and something about encrypted bootloader but I'm more than confused now. Am I doing someting wrong, especially on Linux (more acquainted in this type of system)? On Windows I have to exclude drivers problems, tried on 3 different machines, waited long before unlocking
Well, I'm in your same situation, but mine has been produced the 31/5/2013, so it have an encrypted bootloader.
Related
Hi, well a friend of a friend gifted me an LG L9 Model P778G (Carrier: Personal Telecom Country: Argentina). The only thing that he told me was that he dropped his phone and it didn´t turn on back anymore. I externally charged the battery. The phone doesn´t turn on, sometimes when I connect it to my PC (windows XP) it recognizes it as OMAP4430 but only when battery is not connected (when I connect battery it says unrecognized usb device, when I press Vol+ and Vol- with or without battery it also says unrecognized device. Already tried to flash with LG Mobile Support and KDZ but it says phone not connected. I would like to know how can i get the phone back working and if possible with Jelly Bean (I don´t know if phone had JB or ICS, but of what I almost certain is that it was never modified because it belonged to an old person). Please explain with detail though I'm not used to LG (HTC & Samsung owner) and don't know much of it.Thanks to everyone!
USB connection is unstable, it comes nad goes
philohtc said:
USB connection is unstable, it comes nad goes
Click to expand...
Click to collapse
Hi philohtc, you could read and try thishttp://forum.xda-developers.com/showthread.php?t=2677611
Cheers. Good luck.
BajoPrimate said:
Hi philohtc, you could read and try thishttp://forum.xda-developers.com/showthread.php?t=2677611
Cheers. Good luck.
Click to expand...
Click to collapse
Hi, my device doesn´t turn on at all, the only signal i have is the OMAP driver coming and going and sometimes staying a little while, the LG Mobile Support Tool doesn't see the cellphone, hope you can help me, thanks!
philohtc said:
Hi, well a friend of a friend gifted me an LG L9 Model P778G (Carrier: Personal Telecom Country: Argentina). The only thing that he told me was that he dropped his phone and it didn´t turn on back anymore. I externally charged the battery. The phone doesn´t turn on, sometimes when I connect it to my PC (windows XP) it recognizes it as OMAP4430 but only when battery is not connected (when I connect battery it says unrecognized usb device, when I press Vol+ and Vol- with or without battery it also says unrecognized device. Already tried to flash with LG Mobile Support and KDZ but it says phone not connected. I would like to know how can i get the phone back working and if possible with Jelly Bean (I don´t know if phone had JB or ICS, but of what I almost certain is that it was never modified because it belonged to an old person). Please explain with detail though I'm not used to LG (HTC & Samsung owner) and don't know much of it.Thanks to everyone!
Click to expand...
Click to collapse
I believe you still need to install the fastboot driver again.
Take a look at lelus fastboot script thread here - http://forum.xda-developers.com/showthread.php?p=41768774
Read the part in the thread about installing the drivers and about the original fastboot thread.
That should get you ready to be able to do the offline or online kdz flash
xdrc45 said:
I believe you still need to install the fastboot driver again.
Take a look at lelus fastboot script thread here - http://forum.xda-developers.com/showthread.php?p=41768774
Read the part in the thread about installing the drivers and about the original fastboot thread.
That should get you ready to be able to do the offline or online kdz flash
Click to expand...
Click to collapse
Hi, now the phones stays for a while, but still can't get it recognized at KDZ or LG MST.
PS: when installing fastboot drivers after connecting battery it says an LG Logo should appear on screen but it doesn't, thanks for your support
philohtc said:
Hi, now the phones stays for a while, but still can't get it recognized at KDZ or LG MST.
PS: when installing fastboot drivers after connecting battery it says an LG Logo should appear on screen but it doesn't, thanks for your support
Click to expand...
Click to collapse
Use the fastboot script and flash the ICS Uboot and Xloaders
xdrc45 said:
Use the fastboot script and flash the Uboot and Xloaders
Click to expand...
Click to collapse
Sorry to bother, could you give me links to those files for this model? It's my first LG
philohtc said:
Sorry to bother, could you give me links to those files for this model? It's my first LG
Click to expand...
Click to collapse
It's in the lelus fastboot script, option #4
http://forum.xda-developers.com/showthread.php?p=41768774
xdrc45 said:
It's in the lelus fastboot script, option #4
http://forum.xda-developers.com/showthread.php?p=41768774
Click to expand...
Click to collapse
I selected option 6 because option 4 gaved error
This is my log
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[* said:
read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 2f8a54c5c2fdd39e7dbe73b14991c29b1b9d0ec8
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
Click to expand...
Click to collapse
philohtc said:
I selected option 6 because option 4 gaved error
This is my log
Click to expand...
Click to collapse
OK so you flashed the JB Uboot and Xloader? I'm not at my PC to see the screen options. Try running the kdz now.
xdrc45 said:
OK so you flashed the JB Uboot and Xloader? I'm not at my PC to see the screen options. Try running the kdz now.
Click to expand...
Click to collapse
This happened when I flashed the JB Uboot and Xloader
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
-----------------------------------------------------------------
I ran KDZ and got the following as usual:
[R&D Test Tools Log File]
21:58:55 : Launching SW update
21:58:55 : Unpacking KDZ
21:59:12 : KDZ file extraced
21:59:30 : Files were extracted.
21:59:30 : LGMobileDL Load.
21:59:30 : Port = -1
21:59:30 : Connecting to phone
21:59:30 : PHONE WAS NOT FOUND!
21:59:32 : ===FINISHED===
philohtc said:
This happened when I flashed the JB Uboot and Xloader
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.219s
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.547s
Done
-----------------------------------------------------------------
I ran KDZ and got the following as usual:
[R&D Test Tools Log File]
21:58:55 : Launching SW update
21:58:55 : Unpacking KDZ
21:59:12 : KDZ file extraced
21:59:30 : Files were extracted.
21:59:30 : LGMobileDL Load.
21:59:30 : Port = -1
21:59:30 : Connecting to phone
21:59:30 : PHONE WAS NOT FOUND!
21:59:32 : ===FINISHED===
Click to expand...
Click to collapse
Run the lesus fastbot script again and select option 1 and make sure the drivers are installed. Then try running option #4 again... If successful then try the offline flash here - http://forum.xda-developers.com/showthread.php?t=2085344
And check out this thread - http://forum.xda-developers.com/showthread.php?p=48834061
xdrc45 said:
Run the lesus fastbot script again and select option 1 and make sure the drivers are installed. Then try running option #4 again... If successful then try the offline flash here - http://forum.xda-developers.com/showthread.php?t=2085344
And check out this thread - http://forum.xda-developers.com/showthread.php?p=48834061
Click to expand...
Click to collapse
It says
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 31
usb_read got GEN_FAILURE - got: 0, expected: 4, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
< waiting for device >
AND STAYS THERE ??
philohtc said:
It says
waiting for 2ndstage response...
usb_read 4
usb_read got: 0, expected: 4, errno: 31
usb_read got GEN_FAILURE - got: 0, expected: 4, errno: 31
usb_read failed: 31
usb read = 0
unexpected 2ndstage response
< waiting for device >
AND STAYS THERE ??
Click to expand...
Click to collapse
Ok have you tried put the device into S/W mode now and see if it's detected? Power off the device, press and hold the volume (+) up button and connect the USB cable from the PC to the device.
xdrc45 said:
Ok have you tried put the device into S/W mode now and see if it's detected? Power off the device, press and hold the volume (+) up button and connect the USB cable from the PC to the device.
Click to expand...
Click to collapse
I could complete step 4 it sended uboot and xloader but it gaved error when it tried to write them, I dont know when it is in S/W mode though Screen is always black. In the offline method I deactivate the wifi card and get the connection in line error but it doesn't appear the pop-up of the language.
philohtc said:
I could complete step 4 it sended uboot and xloader but it gaved error when it tried to write them, I dont know when it is in S/W mode though Screen is always black. In the offline method I deactivate the wifi card and get the connection in line error but it doesn't appear the pop-up of the language.
Click to expand...
Click to collapse
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
xdrc45 said:
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
Click to expand...
Click to collapse
Under Android Phone > OMAP4430FastBoot USB Device. Can't see where to select model, apparently is automatic recognition
xdrc45 said:
You can try to run the B2CAppSetup.exe, after opening the app, select you phone model and letting it install the drivers, then unplug and plug the USB cable back in and see what happens.
Edit - Also when you connect the device to your PC when in fastboot mode what does it show up as in the PC's device manager?
Click to expand...
Click to collapse
any idea?
philohtc said:
any idea?
Click to expand...
Click to collapse
I'm not sure yet... We need to get the ICS Uboot and Xloaders to install so that you can get into S/W mode.
I'm trying to research on an answer for you.
These L9 are a real pain in the butt.
---------- Post added 30th March 2014 at 12:06 AM ---------- Previous post was 29th March 2014 at 11:47 PM ----------
philohtc said:
any idea?
Click to expand...
Click to collapse
Run the lelus fasrboot again and flash the JB Uboot and Xloader and show mW the log again
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
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?
Hey all i ran into a problem yesterday i downgraded my fire hdx tablet to 13.3.2.8 and everything went fine except that my boot image and recovery partitions got messed up so now when i turn it on it goes straight into fastboot mode i have the 32 GB model 2013 edition which is a 7 inch thor based tablet i heard someone was able to flash fastboot via linux but i cant get it to work on windows 7 64 bit so im going to try flashing a new boot image and recovery partition via linux to see if that will fix the problem but i would appreciate the assistance. Thanks
blue9a said:
Hey all i ran into a problem yesterday i downgraded my fire hdx tablet to 13.3.2.8 and everything went fine except that my boot image and recovery partitions got messed up so now when i turn it on it goes straight into fastboot mode i have the 32 GB model 2013 edition which is a 7 inch thor based tablet i heard someone was able to flash fastboot via linux but i cant get it to work on windows 7 64 bit so im going to try flashing a new boot image and recovery partition via linux to see if that will fix the problem but i would appreciate the assistance. Thanks
Click to expand...
Click to collapse
There is no known (or at least widely recognized) recovery from a catastrophic 3.2.8 boot failure. As the bootloader remains locked (and hence fastboot crippled) I do not believe you will have success restoring recovery or flashing a new boot image. Sorry - I'm afraid you now own a brick.
Davey126 said:
There is no known (or at least widely recognized) recovery from a catastrophic 3.2.8 boot failure. As the bootloader remains locked (and hence fastboot crippled) I do not believe you will have success restoring recovery or flashing a new boot image. Sorry - I'm afraid you now own a brick.
Click to expand...
Click to collapse
im testing it on ubuntu linux 14.04 LTS its reporting failure unknown command then ready so i guess thats something
blue9a said:
im testing it on ubuntu linux 14.04 LTS its reporting failure unknown command then ready so i guess thats something
Click to expand...
Click to collapse
Believe response would be similar regardless of host. With a locked bootloader only a few fastboot commands work - none of them useful. Maybe you'll find a workaround!
Davey126 said:
Believe response would be similar regardless of host. With a locked bootloader only a few fastboot commands work - none of them useful. Maybe you'll find a workaround!
Click to expand...
Click to collapse
python3 /home/jeremy/Desktop/cuberHDX.py 0x45202b1325
File "/home/jeremy/Desktop/cuberHDX.py", line 64
print 'Usage: %s [boot.img|serial]' % path.basename(argv[0])
^
SyntaxError: invalid syntax
hmm not sure if i did this right
[email protected]:~$ fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: true
OKAY [ 0.036s]
finished. total time: 0.036s
[email protected]:~$ -i 0x1949 oem unlock 0x45202b1325
-i: command not found
[email protected]:~$ /fastboot -i 0x1949 devices
bash: /fastboot: No such file or directory
[email protected]:~$ fastboot -i 0x1949 devices
D0FCA0A03523013E fastboot
[email protected]:~$ fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
error: cannot load 'unlock.signed': No such file or directory
[email protected]:~$ fastboot -i 0x1949 flash boot '/media/jeremy/MULTIBOOT/boot.img'
target reported max download size of 536870912 bytes
sending 'boot' (6884 KB)...
OKAY [ 0.290s]
writing 'boot'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.341s
[email protected]:~$ fastboot -i 0x1949 flash unlock '/media/jeremy/MULTIBOOT/unlock.img'
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.084s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.141s
[email protected]:~$ python cuberHDX.py 45202b1325
python: can't open file 'cuberHDX.py': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py 45202b1325
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ '/media/jeremy/MULTIBOOT/cuber.py' 45202b1325
bash: /media/jeremy/MULTIBOOT/cuber.py: Permission denied
[email protected]:~$ '/home/jeremy/Desktop/cuber.py' 45202b1325
bash: /home/jeremy/Desktop/cuber.py: Permission denied
[email protected]:~$ python '/home/jeremy/Desktop/cuber.py' 45202b1325
Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Traceback (most recent call last):
File "/home/jeremy/Desktop/cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: No module named gmpy2
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py 45202b1325
Your unlock code is in '45202b1325.unlock'.
[email protected]:~$ fastboot -i 0x1949 flash unlock '/home/jeremy/45202b1325.unlock'
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.085s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.142s
[email protected]:~$ /cuber_unlockbl --sign ./'/home/jeremy/Desktop/unlock.img' ./ '/home/jeremy/45202b1325.unlock'
bash: /cuber_unlockbl: No such file or directory
[email protected]:~$ python ./cuber_unlockbl --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file './cuber_unlockbl': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py ./cuber_unlockbl --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ python cuber.py --sign '/home/jeremy/Desktop/unlock.img' '/home/jeremy/Desktop/45202b1325.unlock'
python: can't open file 'cuber.py': [Errno 2] No such file or directory
[email protected]:~$ python /home/jeremy/Desktop/cuberHDX.py ./cuber_unlockbl --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cuberHDX.py [boot.img|serial]
[email protected]:~$ python /home/jeremy/Desktop/cuber.py ./cuber_unlockbl --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cuber.py --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock Usage: cuber.py [bits] [<data] [>sig]
[email protected]:~$ python /home/jeremy/Desktop/cublock.py --sign ./home/jeremy/Desktop/unlock.img ./home/jeremy/Desktop/45202b1325.unlock
Usage: cublock.py manfid serial
[email protected]:~$
well i added a txt file that contains my device info if you can get a .unlock and .img file that would really help me btw my fire os was 13.3.2.8
blue9a said:
well i added a txt file that contains my device info if you can get a .unlock and .img file that would really help me btw my fire os was 13.3.2.8
Click to expand...
Click to collapse
Can't unlock bootloader versions >3.2.3.2; can't flash with a locked BL. Your device is bricked.
My phone does not enter into FastBootD mode when I enter "fastboot reboot fastboot"..
The screen on my phone doesn't change at all when I enter the command, and my computer adb window reads the following, it's some sort of help menu;
Any advice? Thank you it's very much appreciated.
PS C:\adb> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
You need to update your adb/fastboot. Download the latest platform tools from the link above.
That seems a bit odd since I just downloaded it 2 days ago from Google! Could have got an old link but I doubt it...
Didn't work unfortunately!
I downloaded the zip file from the link, unzipped with 7zip and got "platform-tools_r30.0.5-windows". Within there is a folder named Platform Tools.. I held shift and right clicked on the white space in that folder and opened a powershell.. Ran this:
PS C:\Users\CSW\Downloads\platform-tools_r30.0.5-windows\platform-tools> fastboot devices
ZY227FVPN4 fastboot
PS C:\Users\CSW\Downloads\platform-tools_r30.0.5-windows\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
And received the same help menu and no change on my phone.. Same result.
Listen.....reboot to recovery. It's an empty barren wasteland, until: hold the power key down for a 3 second count, now, continuing to hold the power key down, hold the volume up key down for a 2 count: 1, and 2, and...release.
On the new menu enter fastboot - this is fastbootd.
bronkish said:
Listen.....reboot to recovery. It's an empty barren wasteland, until: hold the power key down for a 3 second count, now, continuing to hold the power key down, hold the volume up key down for a 2 count: 1, and 2, and...release.
On the new menu enter fastboot - this is fastbootd.
Click to expand...
Click to collapse
I've done that button pressing. Android robot with a warning triangle is shown. And it is stuck.
sevasnex said:
I've done that button pressing. Android robot with a warning triangle is shown. And it is stuck.
Click to expand...
Click to collapse
hold power an hit vol-up once then release
The trick for our SOFIA is to execute the ADB command while the phone is POWERED ON (System booted up like normal - like when use the phone, make calls, etc) and NOT in fastboot/bootloader mode:
Enable USB Debugging in developer options on phone
Connect USB cable
Answer confirmation/security prompts on phone and PC
Type "adb reboot fastboot" at ADB CLI
FASTBOOTD will now appear in red letters at the top - you are in FASTBOOTD mode
Hope this helps!