Hey guys i just flashed the 3.28.401.6 firmware and in the process i relocked the phone. I flashed the firmware and everything works fine, but now i can't unlock it for some reason i'm S-OFF and my CID is 11111111. I tried the command to flash the token but no luck and have even tried getting a new token.
C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s
i've also tried this (http://forum.xda-developers.com/show....php?t=2708571) however i got this:
1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>
i also realized that my recovery is no longer working as well as superSU... please someone help me
My Phone is after booter responsive to the volume buttons, but the HTC Bootscreen keeps hanging... so cant do anyhting
No clue why your token didn't work, but it may be that you just need to request a new one. Perhaps they changed something in the OTA that invalidated older tokens? If so, ask for a new one. This is, by far, the safest choice.
However, if you just really want a challenge, you can try this. I haven't done this exact procedure myself, but it should work. The manual unlock is failing because you aren't in a root shell. If you have lost root, you will need to temp-root to recover.
Get Sunshine and let it temp-root your phone. Then, start up a local terminal and su into a root shell. You can't use ADB commands because Sunshine kills the ADB connection. Then, very carefully copy/paste the required dd command into it from the XDA forum thread. I use Mobile Firefox, but I know the built in "Internet" browser works too. Note - be very careful not to pick up any stray characters when you copy/paste. If you accidentally pick one up, the command will execute immediately.
That should do it.
Related
Hey guys i just flashed the 1.54 firmware and in the process i relocked the phone. I flashed the firmware and everything, but now i can't unlock it for some reason. I tried the command to flash the token but no luck it gives me:
C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s
please help!
***and on a side note, whenever i plug the phone into the computer it takes a good 2-3 minutes before it detects the phone and starts working. wtf?***
itzjonjon69 said:
Hey guys i just flashed the 1.54 firmware and in the process i relocked the phone. I flashed the firmware and everything, but now i can't unlock it for some reason. I tried the command to flash the token but no luck it gives me:
C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s
please help!
***and on a side note, whenever i plug the phone into the computer it takes a good 2-3 minutes before it detects the phone and starts working. wtf?***
Click to expand...
Click to collapse
Apply for a next token
Sent from my HTC One_M8 using Tapatalk
I did, same thing
i tried this (http://forum.xda-developers.com/showthread.php?t=2708571) however i got this:
1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>
i also realized that my recovery is no longer working as my super SU... please someone help me
I also did .
itzjonjon69 said:
i tried this (http://forum.xda-developers.com/showthread.php?t=2708571) however i got this:
1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>
i also realized that my recovery is no longer working as my super SU... please someone help me
Click to expand...
Click to collapse
I had about the same issue and did all the stuff your doing.
Check in your hboot if it says S-On.
If so then like me you may need to visit the guys in the #firewater IRC channel on freenode.
They ran me through a couple things that didn't work then we all came to the conclusion that my system was write protected.
Something set incorrectly in my mmcblk0p2 caused everything to act as if the phone is S-On.
Finally Beaups remoted into my laptop with the phone connected and ran through some stuff in adb that allowed him to write a fresh copy of mmcblk0p2 to my phone and everything went back to normal.
Sorry I don't know the specifics but it was a couple hours into it then Beaups just remoted in and did it, it was to fast for me to follow.
mc_365 said:
I had about the same issue and did all the stuff your doing.
Check in your hboot if it says S-On.
If so then like me you may need to visit the guys in the #firewater IRC channel on freenode.
They ran me through a couple things that didn't work then we all came to the conclusion that my system was write protected.
Something set incorrectly in my mmcblk0p2 caused everything to act as if the phone is S-On.
Finally Beaups remoted into my laptop with the phone connected and ran through some stuff in adb that allowed him to write a fresh copy of mmcblk0p2 to my phone and everything went back to normal.
Sorry I don't know the specifics but it was a couple hours into it then Beaups just remoted in and did it, it was to fast for me to follow.
Click to expand...
Click to collapse
oops i thought i updated the thread, but forum member russellvone SAVED my ass. So what he did was he had me download this file for my ATT M8
https://mega.co.nz/#!NUURzC5T!tCjG3n...c6zRAwOPZ8T2PI and told me to rename it 0P6BIMG.zip and place it in my adb fastboot folder
then he told me to run these commands:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
fastboot reboot
then once everything was done we ran the commands from this thread (http://forum.xda-developers.com/show....php?t=2708571) and voila! i'm once again unlocked! He explained to me that when i tried to run the unlock commands before it didn't work because i had the secure boot.img and what he had me flash was a file he created which made it unsecure so i could run the command. HUGE HUGE props to this guy.
good to hear
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
I'm on 2.18 and rooted. Problem is, I uninstalled or disabled a bunch of ASUS apps, will I have an issue if I use SuperSU to unroot and try to restore or upgrade my phone to 2.19?
Also, I have model number ASUS_Z00AD. Is this firmware OK to install on my phone?
cmendonc2 said:
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Fixed.
edit: nvm...
Both download links link to the same file. splashscreen.img
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
jpacleb85 said:
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
Click to expand...
Click to collapse
LOL... Gotta love the devs who tinker on here... Now we might actually get a recovery that will do nandroid backups in case of those "little" mistakes/problems that crop up from time to time...
MiCmAsTa said:
Both download links link to the same file. splashscreen.img
Click to expand...
Click to collapse
Fixed.
This is probably a silly question, but I have the ZE550ML and the latest update is 2.18, meaning that unlocking the bootloader it is still not possible can I install droidboot.img(fastboot img) from the 2.19 ZE551ML on my device? Or that will just hard brick my device?
Let me know your thoughts on this.
Continue the great work XDA crew =)
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
PsychoKilla666 said:
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
Click to expand...
Click to collapse
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
rafyvitto said:
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
Click to expand...
Click to collapse
Link please? and how to?
error
rafyvitto said:
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
Click to expand...
Click to collapse
I follow this method and received the following error on CMD
writing 'fastboot'....
FAILED (remote: falsh_cmds error!
Finished. total time: 0.830
im on 2.20 and it wont let me do anything.. i get the white boot screen instead of black but bootloader doesnt exist and it wont download twrp any suggestions?
Success
My phone's recovery stopped working, and the bootloader was locked, but I found this thread. I think I was able to get it working.
I extracted the droidboot.img from the file in the OP.
I copied the droidboot.img to my working directory, and tried to flash it.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.826s
Ok, I got the error. Maybe the "unlock" command will work.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.203s]
finished. total time: 0.204s
Same output as the last hundred times I tried to run it.
I rebooted the phone.
Code:
C:\myworkingdirectory>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
I put the phone into the bootloader mode. (For anyone reading, to get into the bootloader, turn the phone completely off. Hold the power button until it vibrates. Then hold the volume up key.)
I ran the unlock command twice.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.291s]
finished. total time: 0.326s
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.216s]
finished. total time: 0.216s
Then I tried to flash the image again.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.690s]
writing 'fastboot'...
OKAY [ 0.692s]
finished. total time: 1.384s
No error?! I have progress!
------
I believe my bootloader is unlocked. Let me try to flash the recovery. (My recovery was corrupted longggg before doing this.)
Code:
C:\myworkingdirectory>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11676 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.571s]
finished. total time: 1.153s
No permission error! (Before this, I would usually have gotten an error that says "FAILED (remote: Permission denied".)
---- Important Notes ----
NO WHITE BACKGROUND IN BOOTLOADER.
Many people have reported seeing an inverted background in the bootloader. I don't have that.
TRIPLE DOTS IN COMMAND PROMPT
The triple dots you see when I run the unlock command are actually there. They are not placeholders.
------------
Right now I'm booting into recovery mode to flash a ROM to the phone. I'll update if I get the phone working.
I've managed to unlock the bootloader on a friend's Zenfone 2 (Z00A); or, at least, I believe I have, because the boot splash screen has the inverted colors that most threads on BL unlocking mention. I used this method, inside a Windows XP VM.
The thing is, I can't flash TWRP. If I try, it tells me permission was denied.
Code:
[email protected]:~/dev/android/sdk/platform-tools$ sudo ./fastboot flash recovery /media/michael/2D66-7551/Zenfone\ 2\ ZE551ML/twrp-3.0.0-0-Z00A.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'recovery' (15674 KB)...
OKAY [ 0.967s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 1.123s
(The same thing happens if run from inside the XP VM.)
Could someone please steer me in the right direction?
Sorry i can't post any external link.
I had this kind of problem the first time, because you need to root the phone after you unlock the bootloader.
Follow this step : http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
then
Enter that in google : gurus wizard/2015/07/root-and-unlock-bootloader-on-asus-zenfone-2.html
Hi,
I was following the guide to install Rbox's boot menu from aftvnews. I had done it on my other aftv fine. The bootloader on the aftv was unlocked, but when I rebooted the aftv just sat at the white Amazon screen. The last few commands are below.
255|[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/syste
m/boot/boot.img
_sdcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.884 secs (11861719 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ # dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by
-name/boot
dev/block/platform/msm_sdcc.1/by-name/boot <
13164+0 records in
13164+0 records out
6739968 bytes transferred in 1.289 secs (5228834 bytes/sec)
[email protected]:/ # reboot
I tried hooking up a keyboard, but the alt i prtscn doesn't seem to work. I tried fastboot, but it doesn't look good. I haven't come across what tampered true, unlocked false means. As you can see from above though I had root, so that should have meant the bootloader was unlocked. Any help would be appreciated. I have done a fair bit of looking and it seems unless I want to take up soldering I am probably out of luck.
Thanks in advance!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
OKAY [ -0.000s]
finished. total time: -0.000s
Sox35 said:
Hi,
I was following the guide to install Rbox's boot menu from aftvnews. I had done it on my other aftv fine. The bootloader on the aftv was unlocked, but when I rebooted the aftv just sat at the white Amazon screen. The last few commands are below.
255|[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/syste
m/boot/boot.img
_sdcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.884 secs (11861719 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ # dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by
-name/boot
dev/block/platform/msm_sdcc.1/by-name/boot <
13164+0 records in
13164+0 records out
6739968 bytes transferred in 1.289 secs (5228834 bytes/sec)
[email protected]:/ # reboot
I tried hooking up a keyboard, but the alt i prtscn doesn't seem to work. I tried fastboot, but it doesn't look good. I haven't come across what tampered true, unlocked false means. As you can see from above though I had root, so that should have meant the bootloader was unlocked. Any help would be appreciated. I have done a fair bit of looking and it seems unless I want to take up soldering I am probably out of luck.
Thanks in advance!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse
Having root does not mean the bootloader is unlocked. Can you run:
Code:
fastboot boot recovery.img
rbox said:
Having root does not mean the bootloader is unlocked. Can you run:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Sorry, I was going by the guide of aftvnews that says if you have root it is unlocked. I ran the command, but I am guessing it is not good news.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
FAILED (remote: boot not allowed for locked hw)
finished. total time: 0.296s
Sox35 said:
Sorry, I was going by the guide of aftvnews that says if you have root it is unlocked. I ran the command, but I am guessing it is not good news.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
FAILED (remote: boot not allowed for locked hw)
finished. total time: 0.296s
Click to expand...
Click to collapse
You didn't follow all the instructions properly, and it is bricked now. I wrote instructions in a post somewhere on how to unlock with fastboot. I don't know where it is though. You could try searching my posts. @AFTVnews.com might know where it is.
rbox said:
You didn't follow all the instructions properly, and it is bricked now. I wrote instructions in a post somewhere on how to unlock with fastboot. I don't know where it is though. You could try searching my posts. @AFTVnews.com might know where it is.
Click to expand...
Click to collapse
Do I need to generate an unlock file using the output from the commands below? I am not able to find it again right now, but I believe you mentioned something about not using the 1949 part of the command. I don't have a Linux machine. Is there anyone that has the script installed already? If not I can hopefully find someone at work that has one. I just want to make sure I am using the correct commands. I am not sure if I can make the AFTV worse that it is now, but you never know!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem emmc-info
(bootloader) 0x154f04bad7
7090030242070BNB fastboot
//github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
connect the hdx to a linux box and do following command:
./fastboot -i 0x1949 devices
./fastboot -i 0x1949 flash unlock unlock.signed
./fastboot -i 0x1949 reboot
Sox35 said:
Do I need to generate an unlock file using the output from the commands below? I am not able to find it again right now, but I believe you mentioned something about not using the 1949 part of the command. I don't have a Linux machine. Is there anyone that has the script installed already? If not I can hopefully find someone at work that has one. I just want to make sure I am using the correct commands. I am not sure if I can make the AFTV worse that it is now, but you never know!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem emmc-info
(bootloader) 0x154f04bad7
7090030242070BNB fastboot
//github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
connect the hdx to a linux box and do following command:
./fastboot -i 0x1949 devices
./fastboot -i 0x1949 flash unlock unlock.signed
./fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Yeah, Cuber. That's it. And yes, you dont need the -i. http://forum.xda-developers.com/showpost.php?p=61812290&postcount=213 That has some instructions for doing it on Windows.
rbox said:
Yeah, Cuber. That's it. And yes, you dont need the -i. http://forum.xda-developers.com/showpost.php?p=61812290&postcount=213 That has some instructions for doing it on Windows.
Click to expand...
Click to collapse
Thank so much for the Windows link. The instructions on the couple different posts all mention the argument being 0xmmsssssss, but I am getting the following. I have to assume that isn't going to work without using the emmc-info.
C:\Python27>python.exe cuberHDX.py 0xd77090030242070BNB
Usage: cuberHDX.py [boot.img|serial]
Sox35 said:
Thank so much for the Windows link. The instructions on the couple different posts all mention the argument being 0xmmsssssss, but I am getting the following. I have to assume that isn't going to work without using the emmc-info.
C:\Python27>python.exe cuberHDX.py 0xd77090030242070BNB
Usage: cuberHDX.py [boot.img|serial]
Click to expand...
Click to collapse
Your ID is from the previous line:
(bootloader) 0x154f04bad7
Hello,
i have big problem wiht my D855. I'm trying to install recovery on my device via fastboot, because flashify method failed resulting in lack of recovery on my phone... When i enter "the place where recovery should be" boot certification error shows up and the only way to get rid of it is to re-insert the battery. Unfortunatelly fastboot is not working somehow. Command where it stuck while flashing says:
Code:
C:\adb\fastboot flash recovery reco.img
target reported max download size of 214743648 bytes
sending 'recovery' (15382 KB)...
OKAY [ 0.557s]
writing 'recovery'...
device:
Code:
[132740] fastboot: flash:recovery
Ive been already waiting about 40 minutes for this process to continue but of course nothing happened. After removing USB cable it says:
Code:
FAILED (status read failed (Too many links))
finished. total time: 649.362s
Other commands also do not work, they crash almost the same way but with sh.. i called "three dot bug"
Code:
C:\Users\Dom\Desktop\2>fastboot flashing unlock
...
It even dont reboot after typing:
Code:
C:\Users\Dom\Desktop\2>fastboot reboot-bootloader
rebooting into bootloader...
I have tried different cables, USB ports, different PC. I have lates LG drivers installed. What can I do. My OS is running but has many issues like not working wifi, crashing camera or random reboots (on new battery), so I cant use this phone anymore. It is impossible to revert it back to factory because recovery, which is used for this process is not working, so do fastboot...
Please help, I'm not android expert (and poor english user).
Cheers
Flash the latest TWRP onto it, it should let you boot. I had this problem a few days ago on a samsung tablet. I used odin on that. But you are going to have to match up the TWRP version and the android version you are running.
If you get TWRP working you wont have any problems, you can fix everything from there. Flash fulmics, unroot, what ever you want. Wipe the whole device ect. Make your goal trying to get TWRP on it.
Well, the problem is that I'm trying to flash TWRP now, it is the "reco.img" file, because I was trying to resolve the recovery instalation problem by changing name of file, which could be a problem somehow.
I found adb method to flash recovery:
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/yourrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Will it work? ADB is working fine, I already tried similar method when removing and reinstalling laf.