1st comes 1st lg ls740 this is to backup the laf partition, i recomend yall bakup,recovery an boot as well just in case
Note: This assumes you've already rooted manually or with Towelroot and know what adb/fastboot is.
First, backup your LG Download mode (laf) with this code, so you can use LG Flash if necessary.(make sure phone is on and pluged in and android debuging is enabled
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
Run the following code to zero out laf:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(i did this and my volt told me the memory was full but this still got me into fastboot
adb reboot
For whatever reason, you won't be able to access fastboot via "reboot to bootloader" like most phones, so you've got to do a key combo:
Power Off
Unplug USB
Hold Volume Up
Plug in USB
step 2
fastboot oem device-info
should look something like this ...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.013s
step 3, fastboot oem unlock
should look like this,
...
OKAY [ 0.004s]
finished. total time: 0.005s
DO NOT skip this step before shutting off or rebooting the phone
WHEN YOU ARE DONE IN FAST BOOT MAKE SURE TO RESTORE THE LAF.IMG
fastboot flash laf laf.img
p.s if you backup your laf.img make sure to move it off of the internal storage to the sd card or computer or you will not be able to acsess it
notreal456789 said:
1st comes 1st lg ls740 this is to backup the laf partition, i recomend yall bakup,recovery an boot as well just in case
Note: This assumes you've already rooted manually or with Towelroot and know what adb/fastboot is.
First, backup your LG Download mode (laf) with this code, so you can use LG Flash if necessary.(make sure phone is on and pluged in and android debuging is enabled
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
Run the following code to zero out laf:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(i did this and my volt told me the memory was full but this still got me into fastboot
adb reboot
For whatever reason, you won't be able to access fastboot via "reboot to bootloader" like most phones, so you've got to do a key combo:
Power Off
Unplug USB
Hold Volume Up
Plug in USB
step 2
fastboot oem device-info
should look something like this ...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.013s
step 3, fastboot oem unlock
should look like this,
...
OKAY [ 0.004s]
finished. total time: 0.005s
DO NOT skip this step before shutting off or rebooting the phone
WHEN YOU ARE DONE IN FAST BOOT MAKE SURE TO RESTORE THE LAF.IMG
fastboot flash laf laf.img
p.s if you backup your laf.img make sure to move it off of the internal storage to the sd card or computer or you will not be able to acsess it
Click to expand...
Click to collapse
One question is it to unlock the phone from a carrier?
Juniluis said:
One question is it to unlock the phone from a carrier?
Click to expand...
Click to collapse
What kind of unlock is this??? Does this allow sim unlock?
???
What??
I'm confused. Is this to unlock the phone to use it in any carrier?
Bootloader unlock sounds like.
Sent from my HUAWEI Y536A1 using XDA Free mobile app
So i have both the short story with some important explanation and the long story on what I've already tried.
Short story
So my dad bought a oneplus one 16GB from someone and the phone has a bootloop when you try the boot into the system.
I tried to unlock the bootloader, but it runned the command and it just reboots to recovery and the bootloader is still locked.
Also the tamperflag is true so that means that the bootloader has already been unlocked and is relocked.
I can't also boot from a custom recovery image because the bootloader is locked (I think it can with CM11S).
Rom: I guess it is CM12S (with the blinking Cyanogen logo at startup).
Recovery: probably the recovery from CM12S (Cyanogen recovery as text and it is a touch recovery).
Long story
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem device-info” and it told me that the bootloader was still locked but it was tampered.
I tried after that to boot from a TWRP recovery image but i wasn't able to because the bootloader was locked.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
ninjawulf98 said:
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem get-lockstate” and it told me that the bootloader was locked but it was tampered.
Sadly enough when I typed the command now it takes forever to answer, after more than 10 minutes it still displays that it is waiting.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
Click to expand...
Click to collapse
Are you able to enter fastboot mode now?
Bobbi lim said:
Are you able to enter fastboot mode now?
Click to expand...
Click to collapse
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
ninjawulf98 said:
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
Click to expand...
Click to collapse
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Bobbi lim said:
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
ninjawulf98 said:
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
Click to expand...
Click to collapse
Which stock recovery is it? ColorOS? CM? Or OxygenOS?
I had a similar issue when I tried to unlock mine when I first got my OPO
Sent from my Nexus 7 using Tapatalk
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
ninjawulf98 said:
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
Click to expand...
Click to collapse
Maybe my previous post was a bit confusing but it is still locked, i meant that the previous owner locked it and then relocked it.
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
GirishSharma said:
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
Click to expand...
Click to collapse
I've got the following:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Windows\System32>
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
GirishSharma said:
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
Click to expand...
Click to collapse
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
And when i do the command: "fastboot oem device-info" again.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Program Files (x86)\Minimal ADB and Fastboot>
ninjawulf98 said:
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I don't know if this is an issue but i have both the adb and fastboot tools installed from here and the adb, fastboot and drivers here .
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
GirishSharma said:
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
Click to expand...
Click to collapse
I already founded that thread and did the solution that worked for him and another solution that a guy a few posts above him mentioned. Sadly enough without any results.
Anyway, thanks for the help and all the effort you did!
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
ninjawulf98 said:
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
Click to expand...
Click to collapse
Now actually i think that the partition bootloader doesn't exists but boot does (which I think containts the bootloader and the kernel).
After waiting very unpationtly -+ 24 hours I tried it.
Sadly enough again without success.
CMD copy:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot devices
866878f3 fastboot
C:\Windows\System32>fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.057s
C:\Windows\System32>
Fried emmc. Sell it for junk.
Sent from my SM-G920T
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
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 bootlo
ader
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
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Deep.G said:
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
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 bootlo
ader
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
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Click to expand...
Click to collapse
The command for unlocking the bootloader is "fastboot oem unlock" not "fastboot unlock oem".
Also sometimes when you type a commando that isn't recognised by the phone it can take forever.
So, I think that the commando "fastboot flashing unlock" doesn't exist.
Anyway I think I know now for sure that the previous owner erased and/or formatted the cache.
Hi I have been working all day trying to get my moto G up and running again.
The problem is that when I boot it shows the boot animations then boots to a blank screen with backlight on.
So far I have tried.
1. Going into the bootloader then into recovery by holding up for 10s then tapping power. From here I wiped back to factory settings. Then I tired to wipe cach partition. When I did this it said ERASING... then rebooted a second later.
It went back to the same black screen after I booted.
1. Flashing a new recovery. TWERP. The flashing process seemed to go ok ... .
target max-sparse-size: 256MB
sending 'recovery' (9488 KB)...
OKAY [ 0.318s]
writing 'recovery'...
OKAY [ 0.170s]
finished. total time: 0.488s
but when I checked I was still on stock recovery.
Then I went and used fastboot to erase recovery and tried flashing again and rebooted bootloader with fastboot reboot command. Still on stock recovery.
2. Then I tried sideloading falcon to this device it aborted.
3. I discovered the sideload boot recovery and when I was able to load TWERP into RAM and boot from there I thought I had it made.
I tried sideloading my ROM from here and got Error 7 I am on bootloader 4113 and I need to be on a newer on.
4. Flashed bootloader
First with getvar I was able to confirm I was on 13. I downloaded 41.19 and flashed that
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.099s]
but when I rebooted the bootloader with fastboot reboot, and did getvar again. I saw that I was still on 13.
This is only a short summary of the highlights of what I have tried with this phone today. Can anybody give me and idea how to proceed? I'm stuck fast here.
Then I tried simply booting into TWRP recovery with
And yes I unlocked the bootloader. I also tried flashing a stock ROM from here
I've seen similar reports like yours and no solution. It is supposed to be a hardware error. To confirm this, fastboot boot twrp.img and then run adb shell dmesg > dmesg.txt and post the file, maybe there are any clues in this kernel log.
_that said:
I've seen similar reports like yours and no solution. It is supposed to be a hardware error. To confirm this, fastboot boot twrp.img and then run adb shell dmesg > dmesg.txt and post the file, maybe there are any clues in this kernel log.
Click to expand...
Click to collapse
Sorry. I am not sure exactly how to do this. Would you be so nice as to post command here so that I can cut and paste into command line?
jonawald said:
Sorry. I am not sure exactly how to do this. Would you be so nice as to post command here so that I can cut and paste into command line?
Click to expand...
Click to collapse
You can literally cut and paste the commands from my post (if your twrp image is named "twrp.img"). Between fastboot and adb, wait for TWRP to start up.
_that said:
You can literally cut and paste the commands from my post (if your twrp image is named "twrp.img"). Between fastboot and adb, wait for TWRP to start up.
Click to expand...
Click to collapse
I tried this
adb-mac adb dmesg > dmesg.txt
and this
adb-mac adb shell dmesg > dmesg.txt
I am using a mac as you might guess from the -mac piece. When I try this I get
Android Debug Bridge version 1.0.32
Revision 760a64fe84b7-android
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
etc.
Hi Guys, I need some help.
I tried to flash TWRP 3.1 over a 3.0 using the official TWRP app from the store (With root access) The img file I downloaded using the app is the one specific for the TF700T.
Now my device got stuck in a TWRP bootloop. Initially I got the classic RCK/ANDROID/WHIPE DATA menu, but since I used whipe data it is only cycling through TWRP boot loops. (No more menu)
I can only stop the loop using the volume-up rocker during boot.
I'm trying the adb sideload but I am unable to flash the recovery partition.
adb devices does return the device ID followed by 'recovery' but when flashing the new img file the process only waits for a responding device.
> adb devices (output above)
> adb reboot bootloader
> adb devices (output above)
> fastboot -i 0x0B05 flash recovery twrp31.img (Here is where it fails, the device reboot by itself returning to the bootloop / TWRP is obviously not flashed)
Tx a lot for your help
JS:crying:
Geez - where to start?
You should never use Wipe Data from the bootloader menu if you have a custom recovery installed!
You cannot use fastboot commands while connected in adb.
Two different protocols or tools:
Use adb in recovery or Android, and fastboot when I the bootloader.
And that is where you want to be to fix this.
So you have to use bootit.ko to kick the tablet out of the loop and into the bootloader. Not literally please
Check out the guide below and ask if not clear before you completely brick it...
And then never use an app again to flash a recovery. Ever!
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my Nexus 5X using Tapatalk
Hi
Thanks for your comments on my post. I will have a good look at the info tonight and check if all is clear before I execute the next step.
Kindest regards
JS
PS: I'll be a good boy from now on and keep your advice in the back of my head at all times.
It's not the first time that I see a story like yours. These apps have to be designed for many, many different devices and identify the correct partition to the flash the recovery to for each device. So they either need a large data base of Android devices with the correct partition tables (not likely) or they need to read the partition table off the device - correctly... And that's the weak spot. If you're unlucky it could flash the recovery to the boot partition - good luck getting out of that one.
In your case it flashed it wrong but not super wrong and then you made it worse with that wipe data.
As long as you have adb in recovery this should be fixable. Good luck!
Sent from my Nexus 5X using Tapatalk
Made some progress
Here are the results of my attempt
adb push bootit.ko /
1136 KB/s (27690 bytes in 0.023s)
adb shell insmod /bootit.ko
(No return, so I asume its ok)
GOT OUT OF BOOTLOOP
fastboot devices
015d2bbce63fec14 fastboot
fastboot erase misc
erasing 'misc'...
OKAY [ 0.260s]
finished. total time: 0.261s
fastboot reboot
rebooting...
finished. total time: 0.020s
fastboot -i 0x0B05 flash recovery twrp31.img
< waiting for device >
sending 'recovery' (7218 KB)...
OKAY [ 2.863s]
writing 'recovery'...
OKAY [ 8.069s]
finished. total time: 10.933s
fastboot reboot
rebooting...
finished. total time: 0.021s
TWRP 3.1.0.0 is loaded, when I boot I get the splash screen, but there it loops again. Stop bootloop by using Volume down rocker.
I have used following commands with the new 3.1.0.0
fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.249s]
finished. total time: 1.249s
fastboot -w
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
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
erasing 'userdata'...
OKAY [ 64.078s]
sending 'userdata' (139133 KB)...
OKAY [ 25.092s]
writing 'userdata'...
OKAY [ 2.166s]
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 96.343s
fastboot -i 0x0B05 flash recovery filename.img
sending 'recovery' (7126 KB)...
OKAY [ 2.029s]
writing 'recovery'...
OKAY [ 7.546s]
finished. total time: 9.590s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
TWRP does start OK, I am able to flash a custom ROM
Thanks a lot for your incredible support. I hope to have your knowledge and understanding on this topic on day
Kindest regards
JS
It's just practice my friend, just practice. And making a lot of stupid mistakes. Like you did.
Glad you're up and running
Sent from my Nexus 5X using Tapatalk
Hi,
I had to erase/format the system and data partition to get access to TWRP. (fastboot -w)
Once that was done, it all went smooth and silky.
Tx again
JS :good:
berndblb said:
Geez - where to start?
You should never use Wipe Data from the bootloader menu if you have a custom recovery installed!
You cannot use fastboot commands while connected in adb.
Two different protocols or tools:
Use adb in recovery or Android, and fastboot when I the bootloader.
And that is where you want to be to fix this.
So you have to use bootit.ko to kick the tablet out of the loop and into the bootloader. Not literally please
Check out the guide below and ask if not clear before you completely brick it...
And then never use an app again to flash a recovery. Ever!
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
Click to expand...
Click to collapse
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
Click to expand...
Click to collapse
Hey @[email protected] - how about sharing the script? I'd like to add it to the guide.
[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
Click to expand...
Click to collapse
Hello can you share your batch file because I have the same problem as you had.