Database Develop

plz help im stuck on TWRP lock screen [SOLVED]

hi im newbie here i dont know much about rooting but i successful unlocked the bootloader but during root i got this TWRP unrespond lock screen

adeel343 said:
hi im newbie here i dont know much about rooting but i successful unlocked the bootloader but during root i got this TWRP unrespond lock screen
Click to expand...
Click to collapse
outdated recovery, if you have an m7_u or m7_ul model: get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY

i did what u asked me to but it keep saying 'waiting for device' but htc was attached
check my attached image
can u plz help me via teamviwer software plz?

adeel343 said:
i did what u asked me to but it keep saying 'waiting for device' but htc was attached
check my attached image
can u plz help me via teamviwer software plz?
Click to expand...
Click to collapse
you are in recovery, you need to go to bootloader, so either:
adb reboot bootloader
or if that doesn't work
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)

thanks
thanks a lt bro a simple comand worked
thanks alot again

adeel343 said:
thanks a lt bro a simple comand worked
thanks alot again
Click to expand...
Click to collapse
sure, no problem, but please next time use the search function and read a few threads, this has been answered so many times.
and if you could also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks

plz help me with rooting
nkk71 said:
sure, no problem, but please next time use the search function and read a few threads, this has been answered so many times.
and if you could also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks
Click to expand...
Click to collapse
i follew is post http://forum.xda-developers.com/showpost.php?p=38933080&postcount=1&nocache=1&z=9537047115154564
and i succesfull unlocked the boot and i performed the rooting proceder as mentioned in the post but when i check via root checker app it says sorry this device does not have proper root access i tried CWM and TWRP recovery but stilll same message of root checker
plz help and sorry about my English
check attachment pic plz

adeel343 said:
i follew is post http://forum.xda-developers.com/showpost.php?p=38933080&postcount=1&nocache=1&z=9537047115154564
and i succesfull unlocked the boot and i performed the rooting proceder as mentioned in the post but when i check via root checker app it says sorry this device does not have proper root access i tried CWM and TWRP recovery but stilll same message of root checker
plz help and sorry about my English
check attachment pic plz
Click to expand...
Click to collapse
why did you switch back to CWM? I really (at the moment) recommend you stay with TWRP 2.6.3.3 or .4
and also flash SuperSU (by Chainfire) from here: http://download.chainfire.eu/supersu instead of superuser (by Koush) because some apps have problems with superuser on 4.4 ROMs.

plz help installing Xposed insataller framework
thanks flashing with SuperSU (by Chainfire
now plz could u help me installing Xposed insataller framework,error that im getting is in attachment pics

adeel343 said:
thanks flashing with SuperSU (by Chainfire
now plz could u help me installing Xposed insataller framework,error that im getting is in attachment pics
Click to expand...
Click to collapse
you do understand I'm not really helping you by giving you the answers? you should start searching, reading, and try to solve it by yourself... it's a great feeling when you can figure out something by yourself and get it working
Anyway, here you go: http://forum.xda-developers.com/showpost.php?p=50586287&postcount=70182
Note: if "classical" installation mode doesn't work, then select "recovery install" mode

nkk71 said:
you are in recovery, you need to go to bootloader, so either:
adb reboot bootloader
or if that doesn't work
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
Click to expand...
Click to collapse
hello am a new member, i have the same problem, my phone is stuck in in the TWRP lock screen, i tried the force reboot and the buttons start to blink but phone doesn't reboot.

P9 stuck with open bootloader, I need to relock

So I was on my coffee break @ work and I red about the possibility to try out the new nougat beta.
I couldn't sign up for beta program. I assumed that this was due to the fact that I had unlocked boot loader + twrp + root.
So... I kinda downloaded some 7.0 rom and installed that through twrp. It installed fine, but now nothing seems to work anymore.
I reseted the phone and I am stuck with bare bones 7.0 without any essential goodies like keyboard or such.
I tried to re-lock my boot loader with osx latest build.
Terminal i get the following:
./adb devices
List of devices attached
MW************** device
all fine and dandy I guess but in fastboot&Rescue mode:
./fastboot oem relock *mydevicesidentifyingnumber*
...
FAILED (remote: root type is risk)
finished. total time: 0.005s
What am I doing wrong?
Can I install clean 6.xx wit open bootloader. I am stuck at the moment with y360 huawei and compared to P9 it sucks big time.

Same problem please help guys

zakcena said:
Same problem please help guys
Click to expand...
Click to collapse
me too

Do you guys also have mac computers?

I tried with windows PC and the same hapens.

[GUIDE] Temporary unlock bootloader to flash partitions on Nougat

This guide won't work with OFFICIAL Oreo. I've also made a batch script for this so you don't have to type though
This is the new guide for TWRP without the need of OST. I'll cover the other thread later
What you need:
-Service bootloader which is in the attachment, just delete the .zip extension
-ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Nokia driver, available when you plug in the phone
Tutorial:
-Install Nokia driver and ADB first in which way you feel the most convenient
-Plug in your phone after allowing USB Debugging
-Type these commands, each one at a time
Boot your phone to download mode
adb reboot bootloader
Click to expand...
Click to collapse
Get the product ID
fastboot getvar productid
Click to expand...
Click to collapse
It will throw back a string begin with D1A. Copy that string and generate its MD5. I use this service https://md5.gromweb.com
Unlock the bootloader
fastboot oem dm-verity <your MD5 here>
Click to expand...
Click to collapse
When it says failed, your MD5 might be wrong
Flash the service bootloader
fastboot flash aboot <path to mbn file>
Click to expand...
Click to collapse
BE CAREFUL AS CORRUPTED ABOOT MIGHT BRICK YOUR PHONE
If it says OK, proceed to the flashing part, else dm-verity again
Reboot bootloader again
fastboot reboot-bootloader
Click to expand...
Click to collapse
Re-unlock your bootloader
fastboot oem dm-verity <your MD5 here>
Click to expand...
Click to collapse
Congrats! Now you can flash anything you want, shoutout to anyone who provided OST
Note
-Again, special thanks to @heineken78 and @the_laser for their discussion, and anyone involved with the great tool called OST
-The command is found within the file named AdbCmdDll.dll. You can just crack open it with IDA or whatever to find the command yourself
-After flashing, log is in C:\LogData\OUT or OST. Just find the txt file which is about 15KB in size, thanks @hikari_calyx

You mean if I use this option to OEM unlock the boot loader is still locked

Note, doesnt work after Oreo update

heineken78 said:
Note, doesnt work after Oreo update
Click to expand...
Click to collapse
Do you have IDA on your PC?

wolfyapl said:
Do you have IDA on your PC?
Click to expand...
Click to collapse
Yes I have.
Tools "must have":
Beyond Compare, IDA Pro, WinHex.

heineken78 said:
Yes I have.
Tools "must have":
Beyond Compare, IDA Pro, WinHex.
Click to expand...
Click to collapse
Hey, can you patch the exe of OST 6.0.4? Thanks!

wolfyapl said:
Hey, can you patch the exe of OST 6.0.4? Thanks!
Click to expand...
Click to collapse
look here https://forum.xda-developers.com/showpost.php?p=75486360&postcount=64

heineken78 said:
look here https://forum.xda-developers.com/showpost.php?p=75486360&postcount=64
Click to expand...
Click to collapse
Do you know the password of the mbn zip?

Does it work after oreo update... Is there is any way to root oreo

Birbal said:
Does it work after oreo update... Is there is any way to root oreo
Click to expand...
Click to collapse
If you're talking about official Oreo, I'm afraid not

wolfyapl said:
If you're talking about official Oreo, I'm afraid not
Click to expand...
Click to collapse
Thanks bro for the info i am running official oreo btw

I've accidentally tried to do this with the mbn file of Nokia 5 TWRP link of this tread:
https://forum.xda-developers.com/nokia-5/development/root-twrp-nokia-5-t3703423
When I tried to reboot the bootloader, the phone started acting like it's dead and Windows couldn't recognize it anymore. Do you know how I can fix this?

LInk doesn't work
Can someone upload the TWRP link as the above one doesn't work. Thank you!

pls help
after entering "fastboot oem dm-verity e9fcead1112f39bf19a83fc753b4bc1d" it says OK but nothing happens
here:
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
D1AGAD1781632534 fastboot
PS C:\adb> fastboot oem dm-verity e9fcead1112f39bf19a83fc753b4bc1d
...
OKAY [ 0.008s]
finished. total time: 0.010s
PS C:\adb> fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.031s

It shows "Waiting for device"
It shows "Waiting for device"
When i type 2nd command line.
My phone is in download mode after i typed first line.
Please help me , I need to change my imei . So i have to root. But i am not having any proccess. I googled a lot but cant unlock the bootloader.
Even when i tried flashing twrp ,that said the same thing waiting for device in adb command line. :crying:

black screen
my device is on screen deny and windows does not recognize it, nor does it enter download mode with buttons volume up and power

thankyou ... its work for TA-1053

Besides the effort you made to place this into the forum; I disregard having to make click in a Website in Chinese.
Perhaps you know Chinese. Well.. Imagine all the users clicking blindly... Is that safe? Even though you've tested it; it is still pretty uncertain that users will not end with malware.
Or end up with anti privacy on their devices or receiving millions of ads. I honestly find this thread offensive and unsafe to everyone.
If you are the author; a mirror would be nice. Some information regarding TWRP; indicating that the TWRP itself wont be in Chinese.
Therefore i disregard this thread.

wolfyapl said:
It will throw back a string begin with D1A. Copy that string and generate its MD5. I use this service
When it says failed, your MD5 might be wrong
Click to expand...
Click to collapse
Do we need to copy that string in capital or lowercase ?

after the command "fastboot getvar productid", i'm stuck at [waiting for device]... please help me solve this

Data recover from a dead ALE-L21 P8Lite

Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks

tcolaco said:
Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks
Click to expand...
Click to collapse
Hmm, if you have twrp dirty flash personas mod. If you don't, try t flash twrp, and after flash the mod. That won't delete your files, only make your phone to boot. Hopefully you had Android 6 already.

tcolaco said:
Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks
Click to expand...
Click to collapse
flash twrp, if your internal storage isnt encrypted then put a microsd card into your phone and copy your data.
Sent from my LG-K220 using XDA Labs

D1stRU3T0R said:
Hmm, if you have twrp dirty flash personas mod. If you don't, try t flash twrp, and after flash the mod. That won't delete your files, only make your phone to boot. Hopefully you had Android 6 already.
Click to expand...
Click to collapse
In the fastboot & rescue mode it the bottom it says in green "PHONE Locked". This might be a problem to flash ?
I run adb and my device is detected if I use "fastboot devices". When I try to run "fastboot flash recovery" it gives me the message below;
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26000 KB)...
OKAY [ 0.621s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s

tcolaco said:
In the fastboot & rescue mode it the bottom it says in green "PHONE Locked". This might be a problem to flash ?
I run adb and my device is detected if I use "fastboot devices". When I try to run "fastboot flash recovery" it gives me the message below;
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26000 KB)...
OKAY [ 0.621s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
Click to expand...
Click to collapse
Unlock your bootloader... Get the unlock code, unlock it, and than repeat.

D1stRU3T0R said:
Unlock your bootloader... Get the unlock code, unlock it, and than repeat.
Click to expand...
Click to collapse
How do I get the codes ?? can you please clarify me.
Thanks

tcolaco said:
How do I get the codes ?? can you please clarify me.
Thanks
Click to expand...
Click to collapse
Search in the megathread and you will find it

fastboot errors, Can't flash oem - FAILED (remote: 'unknown command') [Ubuntu Linux]

I've basically two questions: First my concrete problem and second "how can I debug problems with the horrible platformTools"? Maybe you can help me solve both.
1. fastboot fails with "unknown command"
I've sucessfully build AOSP Android 10 via the instructions from Sonys Open Devices. But I'm currently stuck at the last step - flashing the images on my phone. I've successfully put the device in fastboot mode (LED is glowing blue, and "fastboot devices" lists a connected device).
But sending the vendor image fails with an "unknown command"-error
Code:
./fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v3_yoshino.img
Sending 'oem' (211868 KB) FAILED (remote: 'unknown command')
I'm using the newest platformTools on Ubuntu Linux 18.04. My bootloader is unlocked and I've already installed other Android Versions in the past on the phone. Any idea whats going on here and how to fix it?
2. How to debug it myself?
And as a more general approach, as some problems with fastboot/adb appear to occure almost everytime I try to use it: Any tipps on how to find the cause of the problem myself? Any logs which I should check? Any known problems which I should be aware of?

AllesMeins said:
./fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v3_yoshino.img
Click to expand...
Click to collapse
EDIT: Does THIS help?

SXUsr said:
EDIT: Does THIS help?
Click to expand...
Click to collapse
Unfortunaly not - I already had a pretty recent version, but did an update to the newest nevertheless. Problem stays the same.
I'm thinking about trying to flash the other parts first but I'm still reluctant, because I'm afraid that I might end up without a way to go back, if fastboot doesn't work reliably.

AllesMeins said:
I'm thinking about trying to flash the other parts first but I'm still reluctant, because I'm afraid that I might end up without a way to go back, if fastboot doesn't work reliably.
Click to expand...
Click to collapse
Try it, you can always rely on EMMA to go back. I'll happily test if you want?

SXUsr said:
Try it, you can always rely on EMMA to go back. I'll happily test if you want?
Click to expand...
Click to collapse
No luck... Tried it for boot, system, vendor and everytime the same error. But it seems to be a Linux-Problem. I tried it with my flatmates Windows 10 PC and there everything worked. But of cause this is no solution for the future. Any ideas why the phone doesn't understand the commands, when coming from my system?

AllesMeins said:
Any ideas why the phone doesn't understand the commands, when coming from my system?
Click to expand...
Click to collapse
I don't, but I assume you've set up everything properly. Can the PC see the phone under the adb devices command?

SXUsr said:
I don't, but I assume you've set up everything properly. Can the PC see the phone under the adb devices command?
Click to expand...
Click to collapse
In normal mode: yes.
$ ./adb devices
List of devices attached
BH906VHH9E device
Click to expand...
Click to collapse
In fastboot mode no - but there it is listed under fastboot devices

I wish I could be of more help, I really want to see 10 on this phone.

I managed to flash it on Windows, but version is 5 , but got loopboot afte reinstalling PIxel Experience Plus.
https://forum.xda-developers.com/xperia-xz1-compact/help/pixel-experience-10-0-plus-how-to-t4077747