Database Users

Can't install ADB, TWRP, or OS

Guys, I think I messed up big league. I set a pin on startup and I'm guessing that encrypted my "system" partition. After trying and failing to decrypt that with the PIN I had set to use on startup I tried wiping "dalvik", "cache", "system", and "data". Then I flashed DrakenFX's B15 stock ROM, but it's still asking for PIN on startup. When I rebooted, I was faced with the stock recovery. ADB won't install on my computer, so I don't know how to flash recovery back onto the device. (Do I need the device powered on and in an OS for ADB to recognize the device and install the correct drivers?) TWRP says there is no OS installed. So, I guess my question is this: How do I decrypt my device and get back into an OS.
Thanks a million for your help in advance.

TheWoerbler said:
Guys, I think I messed up big league. I set a pin on startup and I'm guessing that encrypted my "system" partition. After trying and failing to decrypt that with the PIN I had set to use on startup I tried wiping "dalvik", "cache", "system", and "data". Then I flashed DrakenFX's B15 stock ROM, but it's still asking for PIN on startup. When I rebooted, I was faced with the stock recovery. ADB won't install on my computer, so I don't know how to flash recovery back onto the device. (Do I need the device powered on and in an OS for ADB to recognize the device and install the correct drivers?) TWRP says there is no OS installed. So, I guess my question is this: How do I decrypt my device and get back into an OS.
Thanks a million for your help in advance.
Click to expand...
Click to collapse
The only way to really decrypt your phone is by formating it, as for twrp try fastboot instead of adb is going to be easier and then download the OS of your choice if u need further help pm me ill help u through teamviewer

J0nhy said:
The only way to really decrypt your phone is by formating it, as for twrp try fastboot instead of adb is going to be easier and then download the OS of your choice if u need further help pm me ill help u through teamviewer
Click to expand...
Click to collapse
*EDIT* So the ADB installer ver. 1.4.3 wasn't playing nice with Windows 10. I installed the 1.3.0 installer and it worked right away.
Thanks! I'm back into DrakenFX's B15 ROM, now I need to figure out how to get ADB and fastboot drivers to install correctly. Every time I run the ADB+Fastboot installer, I go through the process and it says "0 Files Copied." Any help there?

TheWoerbler said:
*EDIT* So the ADB installer ver. 1.4.3 wasn't playing nice with Windows 10. I installed the 1.3.0 installer and it worked right away.
Thanks! I'm back into DrakenFX's B15 ROM, now I need to figure out how to get ADB and fastboot drivers to install correctly. Every time I run the ADB+Fastboot installer, I go through the process and it says "0 Files Copied." Any help there?
Click to expand...
Click to collapse
This is the adb and fastboot i use:
https://mega.nz/#!FdARiCIJ!QM_sfJ_JNBNv5HvjyNycVVZCSN6fUP5gVZdXKpUOAbo
To use it simply unzip the files then shift and left click and then click "open command window here" if you want to use adb type abd then whatever same thing with fastboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[FIX] Asus Zenfone 2 Laser ZE550KL Marshmallow update problem, failed to mount /asdf

I have good experience with other phones but this is my first time working with ZE550KL.
So I took my uncle's phone and he asked me to update his phone to the latest firmware to get the VoLTE feature.
He is was on ZE550KL_WW_21.40.1220.1708 which is Marshmallow of the ZEN UI.
I have downloaded the latest firmware from the ASUS website but I couldn't update it because the recovery which came with the marshmallow update is broken.
These are the errors I got
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what I did, and hope this works for everyone.
Hoping that you already went and searched about the problem over the internet.
These are the things you need to download :
ADB and fastboot
https://drive.google.com/file/d/0B0aDjdU4gTwZZW1HUHhqWnEteXM/view
Recovery image file
https://drive.google.com/open?id=0B0aDjdU4gTwZa1MyUmVPN3BhQjQ
Latest firmware:
https://www.asus.com/in/support/Download/39/1/0/22/ZROQURlyupei1ZQz/32/
1. Download the adb and fastboot drivers. Download the latest firmware and copy it onto your internal storage.
2. Boot into the bootloader.
3. Download the recovery image and paste it into the adb folder.
4. Now type the following command.
Code:
fastboot flash recovery recovery.img
5. This step is very important.
Now, all you have to do is hold the power button and the volume down button to boot into the installed recovery.
Remember that if you restart your phone after step 4, your old recovery(which does not work) will still be there.
6. Now select update from sdcard and select the zip file of the latest firmware you downloaded.
7. It will take at least 10 minutes to install, don't panic if you think the screen froze.
I hope this solves the issues many users are facing.
Feel free to ask questions, I will be very happy to answer.
The recovery we installed is the recovery of Android Lollipop version of the Zen UI ROM.

Thanks. It worked. The only difference is that after flashing the old recovery, my SD card was showing blank. So i selected the adb sideload option and flashed the new build.. Thanks for your guide.

Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?

hellbraker said:
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
Click to expand...
Click to collapse
Before I tried any of this... First thing I did was boot TWRP and install the lastest firmware.
But I couldn't do so because TWRP doesn't let you flash .img files.
And for the best result it is always better for you to use the official recovery to flash an official firmware.
Because ASUS f***ed up, I needed to install the previous version of the recovery to flash the firmware.
And I'm very happy that my guide worked for you.
Don't forget to give thanks. :laugh:

I haven't tried it yet. So you didn't tamper with boot.img at all. Right?
Also as previously asked what's the build number from which you extracted the recovery.img? Is it from .1503?
My current build is .1708 same as what you worked on. And will data get erased during this process?

How can I boot into the bootloader? is it by unlocking it? or is there any other non-invasive way?
Update: I installed as per your instructions. Device shows "Optimizing app 5 of 51".
Thank you.

Thank you
Thank you sir, this helped me a lot.

recovery link is asking need access plzz help

My Asus Zenfone doesn't boot anymore and doesn't even allow me to factory reset it from the bootloader. How to force reset it??

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""
I'm handling a bricked Zenfone 3 ZE552KL WW model, but I am unable to flash the stock rom back into the device.
For context, this device has never been unlocked, rooted, and always worked under its original factory Android. As told by the owner, he received an OTA update notification last week and confirmed all prompts to initiate the update. As instructed, he plugged the device to its original charger, left the update running and went by with his day doing other stuff. When he returned, the device was completely OFF with 0% battery. We figured the charging cable disconnected due to a bad connector endpoint, and the phone ran out of juice while the update was running!
The result is a bricked Zenfone unable to boot beyond the ASUS logo. It keeps crashing and gets into a boot loop.
I have tried most of the basic tech support I can give him.
I have downloaded a fresh copy of the official ZE522KL firmware from the ASUS website.
I can boot the phone into recovery, which is still the original ASUS recovery. But as I try to flash the firmware, I get this lovely error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ERROR: This package is for "WW_Phone" device. This is a "".
I know for a fact this is a WW_Phone device because when I try to flash the JP firmware, the error message is different.
ERROR: This package is for "JP_Phone" device. This is a "WW_Phone".
Already tried "Wipe data/factory reset" and "Wipe cache partition" from the recovery menu, but that didn't help.
Already tried pushing the firmware via "adb sideload" and placing it in a SD card. Those didn't help either.
I am also willing to flash a community ROM, like LineageOS or Mokee, but I first need to unlock the bootloader. I'm running adb and fastboot from Linux, and I can't find a descent tool to unlock using Linux is proving to be a real pain. Every tool seems to be made for Windows only.
So, I'm resorting to anyone here, hoping anyone could give me a light before we send this phone directly to ASUS tech support, not available in our region (we'll need to ship it to another city).
Anything I can try before that? I'm running out of ideas.
Best regards and thanks in advance for any help.

Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg

Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.

wang1chung said:
Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.
Click to expand...
Click to collapse
Since his phone is locked, he can't flash anything except RAW firmware.
---------- Post added at 11:52 AM ---------- Previous post was at 11:41 AM ----------
juliohm said:
Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg
Click to expand...
Click to collapse
Hey juliohm,
Just follow these steps & your device will operate normally
1) Download and install ASUS Flash Tool :
2) Download Latest Oreo RAW
ZE520KL:
ZE552KL:
3) Enter Fastboot Mode (Power + Volume Up)
4) Open ASUS Flash Tool
5) Select device & select firmware (select YES on wipe data tab too)
6) Connect phone to PC
7) Hit Start and wait 10-15 minutes (ignore the error 5 [FRP])
MOD EDIT: PAY-PER-CLICK LINKS REMOVED

Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?

juliohm said:
Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?
Click to expand...
Click to collapse
Check PM

Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.

GrenadeofTacos said:
Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.
Click to expand...
Click to collapse
No need. Flash RAW firmware is enough.

Just a quick follow up.
The owner decided to take it a local assist shop. I don't know what method they used, but they managed to reflash the stock firmware back into the device, and it's working fine again.
Thank you all for the tips. If this was my own device, I would be tinkering a lot more. But the owner decided to play safe and pay for repair in some authorized assistence shop.
Best regards all!

lg g6 - Stuck on firmware update with no OS

Hello,
I have a problem with my G6, i tried to install a custom rom this morning. At first i could get into twrp (melina one) and then wipe internal, system, cache etc. All went fine, then i tried to flash the custom rom, I got the cannot mount /system error. I've got that before so I went to the wipe menu, clicked format system and formatted it as something else to then format it back to ext4. But twrp got stuck on formatting it was looping, i then decided after 10 minutes to reboot the phone with a hard reset and then get back into twrp, but now i wouldnt get into twrp because it was just hanging on the splash screen of twrp. Ok no panic, i was in the twrp looping stage now, i then decided to format erase partition recovery and reflash recovery from melina again. That was successfull so i tried entering twrp: same thing happening the splash image hanging. I decided to flash the stock rom again and downloaded the correct KDZ file: H87020c_00_OPEN_EU_OP_0817.kdz i extracted this one from the lg bridge updater. The LG bridge software update failed 2 times after eachother because it could not "upgrade my phone". Ok so now i tried doing the LG Flash Tool:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
didn't work after numerous tries.
and then the almighty flashtool which i got this error, no matter what .dll file:
So I can't reach fastboot anymoreI can access fastboot now( ive formatted system partition when i still got the chance so that should be ok now) and no recovery, but the computer detects the phone as the com port and firmare update screen.
When i plugin my cable to the wall it goes directly to the firmware update screen, when i power the phone off with the firmware hidden menu update and holding volume down or up while booting goes directly to firmware update screen. I dont know what to do at this point.

Ok so i got it further by downgrading lg flashtool. But it errors out everytime at system, i guess something is wrong with that partition?
And I can access fastboot mode now luckely.

Yo dude.
Don't panic....help is here.
Download this version of LGUP
Pick the Oreo .KDZ of your choice.
Attach your phone
In LGUP tool, select your .kdz that you want to flash
Then select "PARTITION DL" "Upgrade" NOT "Refurbish"
Then click "select all"
Then click start and the magic will happen
Matt

matthew33 said:
Yo dude.
Don't panic....help is here.
Download this version of LGUP
Pick the Oreo .KDZ of your choice.
Attach your phone
In LGUP tool, select your .kdz that you want to flash
Then select "PARTITION DL" "Upgrade" NOT "Refurbish"
Then click "select all"
Then click start and the magic will happen
Matt
Click to expand...
Click to collapse
Thanks, but I've tried that before on the first screenshot I believe. I tried it anyway and when i run uppercut with your exe i get this messsage:
View attachment 4622981
I don't have a .msi dll package for the LGH870

Ok got the lgup working but i still get error 0x2BC with your version.
View attachment 4623053
maybe i need the right DLL from you.
And i got the LG LOGO back after erasing and flashing system.img manually. But I cant get to recovery, when i answer yes to both questions i just get the firmware update screen.
I really don't get why such a simple procedure should go so bad and wrong...

Nobody can help? I need the phone urgent.

Did you select partion then select all?
Sent from my LG-H870 using Tapatalk

matthew33 said:
Did you select partion then select all?
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
yes I did select all. Then the error came as usual.
Heres a video. Why doesn't it just continue...
https://www.youtube.com/watch?v=acytlLGHQ0c

It just sticks on 12% even after a few mins?
Sent from my LG-H870 using Tapatalk

matthew33 said:
It just sticks on 12% even after a few mins?
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
No it gives an error 0x2bc i can't show it on video cause of the OBS Software. I will try it on another pc today maybe that will work.

I'm hoping somebody with more ecpertise will come along for you,
COME ON XDA MEMBERS!! - HELP THIS GUY OUT!!
Matt

Which recovery have you tried?

jimbomodder said:
Which recovery have you tried?
Click to expand...
Click to collapse
Melina twrp 3.2.1. it just boots to download mode.