Database Users

ugent help

every flashing using adb or flashtools has failed
adb sideload fails with E:cant mount/cache
flashtool (oem partition)
and i think i messup with the oem partiton. i flash with the kitkat v.54
i am in lolipop non root
i can go to droidmode and recovery but wipe and factory reset always fails with E:cant mount........
i have tried every bit of available solutions . plz help
please tell me with something effective
fastboot flash recovery recovery.img
........................................
.....................................
.................................... don't work during sideload it fails

is the zenfone 5 section dead here on xda? there are too many queries left unanswered, this is still such a good phone though

adb sideload ?
u'll never success !
u just need to unlock bootloader
go study this thread http://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
and give it a try u can read thru from
page to page !
I'm a noob on this zenfone 5
after 4th day success unlock bootloader
and flash any rom o like !
but there will still have problem
with TWRP for flashing ROMs
zenfone 5 TWRP not universer !
u need to tackle by ur self !

done everything but failed to mount is the ans
failed to mount is the final result

gradd said:
is the zenfone 5 section dead here on xda? there are too many queries left unanswered, this is still such a good phone though
Click to expand...
Click to collapse
i don't know what else i can do sideload cant be done
E:failed to mount(invalid argument)
if you can help me please

akatsuki oinam said:
i don't know what else i can do sideload cant be done
E:failed to mount(invalid argument)
if you can help me please
Click to expand...
Click to collapse
it seems you lost root. are you using custom recovery? if not, you may try debricking thread, as a last resort. if its stock recovery. it looks lije its borked
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455

gradd said:
it seems you lost root. are you using custom recovery? if not, you may try debricking thread, as a last resort. if its stock recovery. it looks lije its borked
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
Click to expand...
Click to collapse
i try the method but sadly it gives the same command

akatsuki oinam said:
i try the method but sadly it gives the same command
Click to expand...
Click to collapse
consider yourself lucky coz you can get past droidboot, if you can sideload, there's an alternate method to flash stock .raw firmware thru xfstk. im still stuck at intel logo, no progress just yet since December 8 and no droidboot

gradd said:
consider yourself lucky coz you can get past droidboot, if you can sideload, there's an alternate method to flash stock .raw firmware thru xfstk. im still stuck at intel logo, no progress just yet since December 8 and no droidboot
Click to expand...
Click to collapse
xfstk.im how? can i check

akatsuki oinam said:
xfstk.im how? can i check
Click to expand...
Click to collapse
sure! i found it outside xda, its for both variants of zen5.
https://www.google.com/amp/s/andrewbenedictus.wordpress.com/2016/02/15/how-to-unbrick-asus-zenfone-5-stuck-on-intel-logo/amp/?client=ms-android-pantech

gradd said:
sure! i found it outside xda, its for both variants of zen5.
https://www.google.com/amp/s/andrewbenedictus.wordpress.com/2016/02/15/how-to-unbrick-asus-zenfone-5-stuck-on-intel-logo/amp/?client=ms-android-pantech
Click to expand...
Click to collapse
after using the flashtool
flash image failure(FAILURE(remote:unknown OEM command))
what can be done more:crying::crying::crying:

Hello! I'm new to you at xda
I am having this same problem on my asus zenfone 5 (a501cg), when I clear the partiques cache / data or facrore reset, it shows the following. "E: cant mount / cache / recovery / last_update-log".
I would like and help, but I have not found a solution yet:confuso:
-benzóico.

Huawei Nova Dload Bootlop

Hi, I recently tried to downgrade back to stock firmware from Lineage OS using the Dload method.
However now its on a bootloop, the versions of CAN-01 and CAN-11 all give me a bootloop, after waiting on it a while it will boot into recovery mode.
Usually this is a simple problem to fix however it reset my bootloader to locked as well as my twrp recovery, I'm not sure how I can recover from this other than sending to repairs.
Any suggested solutions!
It could just be I have the wrong update.zip but I want some more views on this.

Noctyk said:
Hi, I recently tried to downgrade back to stock firmware from Lineage OS using the Dload method.
However now its on a bootloop, the versions of CAN-01 and CAN-11 all give me a bootloop, after waiting on it a while it will boot into recovery mode.
Usually this is a simple problem to fix however it reset my bootloader to locked as well as my twrp recovery, I'm not sure how I can recover from this other than sending to repairs.
Any suggested solutions!
It could just be I have the wrong update.zip but I want some more views on this.
Click to expand...
Click to collapse
Hello!
Check this post.

#Henkate said:
Hello!
Check this post.
Click to expand...
Click to collapse
Hi! Thank you for the fast reply, I remember that I've tried method 1 already and since it reset my bootloader, it's no longer unlocked. The first thing I did when I realised it was a bootloop I tried to reflash my TWRP as I have a backup but it fails everytime I try to flash anything through fastboot as my bootloader is locked.
I was slightly naive and didn't think it would wipe my TWRP and bootloader back to locked.
What do you recommend I try?

Well, Unlock your Bootloader again.. ^^

Bad2hold said:
Well, Unlock your Bootloader again.. ^^
Click to expand...
Click to collapse
I've fixed the issue now thanks, I forgot to wipe the cache and extra bits after the Dload update thats why it was stuck on the bootloop :silly:
My problem before was I couldnt get the IDs needed for my bootloader unlock code since I couldn't actually check the IDs through settings.

can anyone help me root my samsung Tab A 10.1 with S Pen ?

I tried installing TWRP but always failed, the nearest TWRP build I can find is for gtanotexllte, but mine is gtanotexlltedx, so I tried flashing the non dx version (I haven't found the DX one) and It just bricked the tab, any help ?
Edit: My device is the S Pen version (SM-P585Y, Australian ROM, Android Oreo)

Jelly Hero said:
I tried installing TWRP but always failed, the nearest TWRP build I can find is for gtanotexllte, but mine is gtanotexlltedx, so I tried flashing the non dx version (I haven't found the DX one) and It just bricked the tab, any help ?
Edit: My device is the S Pen version (SM-P585Y, Australian ROM, Android Oreo)
Click to expand...
Click to collapse
You need a DEV to fix TWRP for your device because your TWRP you are using is for Android 6, it needs updating for working on android 8.1. Or if you want Twrp, you can downgrade to android 6 and flash it.

I tried downgrading but it says error bootloader binary 1...

raphael mark said:
I tried downgrading but it says error bootloader binary 1...
Click to expand...
Click to collapse
You can use Magisk Manager app to patch boot.img and flash using Odin to root the tablet

Thanks its works....and how can I Install a custom rom without twrp

Hi seniors, please guide me samsung bootloop SM-P585Y tab after trying to install twrp and then I flash the firmware to solve the problem failed to install twrp. after flashing the firmware successfully, I tried installing Twrp again and failed again. When I tried flashing the firmware it failed and "bootloader device 2, binary 1" appeared and finally the battery shutdown. please provide help for me

Guncloudes said:
Hi seniors, please guide me samsung bootloop SM-P585Y tab after trying to install twrp and then I flash the firmware to solve the problem failed to install twrp. after flashing the firmware successfully, I tried installing Twrp again and failed again. When I tried flashing the firmware it failed and "bootloader device 2, binary 1" appeared and finally the battery shutdown. please provide help for me
Click to expand...
Click to collapse
The Twrp is only for android 6 and need a developer to maintain it and fix error with android 8.1. If you want twrp, just downgrade your tablet to android 6 and flash twrp.

Tung Lam said:
The Twrp is only for android 6 and need a developer to maintain it and fix error with android 8.1. If you want twrp, just downgrade your tablet to android 6 and flash twrp.
Click to expand...
Click to collapse
Thanks for answer. i trying downgrade and just success. But always self reboot and stuck at logo samsung .
Mr Tunglam, what step to solve auto reboot?

Guncloudes said:
Thanks for answer. i trying downgrade and just success. But always self reboot and stuck at logo samsung .
Mr Tunglam, what step to solve auto reboot?
Click to expand...
Click to collapse
Make sure that u download right version of 4-file ROM of your tablet. Flash all 4 files with Odin.

Tung Lam said:
Make sure that u download right version of 4-file ROM of your tablet. Flash all 4 files with Odin.
Click to expand...
Click to collapse
Thanks for help.
Now my tab allready flash to android 7.
But after boot to system and phone screen lock ,all screen black just a black line white line.

Tung Lam said:
The Twrp is only for android 6 and need a developer to maintain it and fix error with android 8.1. If you want twrp, just downgrade your tablet to android 6 and flash twrp.
Click to expand...
Click to collapse
This step bring everythings fine. Thank you very much Mr Tung Lam

TWRP issues
Guncloudes said:
This step bring everythings fine. Thank you very much Mr Tung Lam
Click to expand...
Click to collapse
Commonly TWRP will not install if you're using a version incompatible with the device, check to make sure. You should always have the original stock frimware on hand in case anything goes wrong. If you do encounter difficulties such as bootloops you can basically start over by flashing in the stock firmware in download mode via Odin3. Sometimes after flashing it may take a while for the device to fully boot up, I've had some take hours.

Tung Lam said:
You can use Magisk Manager app to patch boot.img and flash using Odin to root the tablet
Click to expand...
Click to collapse
I get Odin fail with this. I'm using the Magisk 20.1 version. Do you have a solution?

Guncloudes said:
Thanks for answer. i trying downgrade and just success. But always self reboot and stuck at logo samsung .
Mr Tunglam, what step to solve auto reboot?
Click to expand...
Click to collapse
You have to wipe data after a downgrade.

twrp gets erased

Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you

Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.

As far as i remember there were 2 files. dm-verity and forced encryption. I never needed them but if you stay on stock you will have to flash those so that twrp doesn't get replaced by stock recovery everytime you reboot. Check the how to root forum you should find more information there about this.

Or you can just root it and twrp won't erase with stock recover.

naikxda18 said:
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Click to expand...
Click to collapse
Do this:
[email protected] said:
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
Click to expand...
Click to collapse
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw

Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?

Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
Thanks but i flashed RR pie soon after flashing twrp now its working fine

[email protected] said:
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Click to expand...
Click to collapse
I didn't either, as you wrote if you boot into TWRP before going to system it should stick or also if you flash magisk before booting the OS.
But there are some devices/ROMs that need the no verity flag to be disabled so flashing this file might help if TWRP won't stick (even when DM verity looks for a tampered system partition in the first case). There are also some terminal commands to do that but I forgot them at the moment.
I mainly used the zip to keep my /data partition decrypted after reformating it. When flashing Nougat magisk did the job for me but when I upgraded to Oreo /data was reencrypted again after flashing magisk and booting into system.
The above zip prevents /data from being encrypted again and may make sure that TWRP sticks.

ahhh, ok I see. Thanks for the explanation.

Phone won't boot?

Hello, I was trying to root my phone last night, I unlocked the boot loader that worked perfectly, easy. Nothing else went well, I was fighting with it TWRP for hours and then Magisk wouldn't install. I gave up on that and tried SuperSu... now the phone just stays on the loading screen instead of booting, It won't boot into recovery either just fastboot. Can it be fixed?

Your phone is soft bricked and can only boot to bootloader, correct?
The only solution is flashing the stock ROM of the device. You can get your device (Tissot) stock ROM from here.

I just got it to boot into TWRP, after it cycled a few times.

Well that may make it easier, you can try wiping dalvik cache then wiping data and see if that works. Needless to say wiping data is going to delete all your personal data, but since you're in TWRP recovery you can back it up.

Wiping it didn't work, I'm trying to use MiFlash I have downloaded "Tissot_9.0_V10.0.10.0.PDHMIXM_Fastboot" my phone is in fastboot. MiFlash detects it but when I try to flash I just get "can not found file flash_all_lock.bat"
How do you tell is MiFlash has successfully installed drivers, it gives me a window in Chinese?

If it's not working - I never thought it would anyway - then your only option is to flash stock ROM.
You can try using fastboot commands through cmd window, if it returns <waiting for device> or something similar then the driver isn't installed properly. Alternatively you can install the driver from here.

Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?

galaxymini1 said:
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
Click to expand...
Click to collapse
You can use any version as long as it is meant for your device. Flashing the latest version might be best option.
Happy to help.

I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.

galaxymini1 said:
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
Click to expand...
Click to collapse
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.

XDHx86 said:
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
Click to expand...
Click to collapse
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...

galaxymini1 said:
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
Click to expand...
Click to collapse
You can find that in an XDA revised article here.

I got TWRP and Magisk installed no problem. I don't know if I was just tired or it was the crap guides but nothing wanted to cooperate on my first attempt.
Thanks for all the help.