Related
Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Rephosix said:
Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Click to expand...
Click to collapse
WAIT THE PHONE ACTUALLY REBOOTS the problem is that i don't see the screen but i can tap on it and i hear that beep when i unlock the screen i just need aboot.bin because the adb after all still recognize the device, please someone can give me aboot.bin pleaseee!
Rephosix said:
WAIT THE PHONE ACTUALLY REBOOTS the problem is that i don't see the screen but i can tap on it and i hear that beep when i unlock the screen i just need aboot.bin because the adb after all still recognize the device, please someone can give me aboot.bin pleaseee!
Click to expand...
Click to collapse
Okay this is getting weirder, it booted....and guess what i see the screen rotated 180 but the buttons are working as they weren't been rotated, plus that the resolution is lower, i mean i can see the pixels for some reason.
Rephosix said:
Okay this is getting weirder, it booted....and guess what i see the screen rotated 180 but the buttons are working as they weren't been rotated, plus that the resolution is lower, i mean i can see the pixels for some reason.
Click to expand...
Click to collapse
Okay, i was so desperate that i didn't pay attention there was already a aboot.bin on the forums but the problem is that everytime i try:
-dd if=/sdcard/aboot.bin of=/dev/block/mmcblk0p6 through the ADB it says /sdcard/aboot.bin : cannot open file : aboot.bin doesn't exist.
Any solutions?
Hi Reposix,
if you would tell us the ADB commands you used before we might be able to help.
Did you put the about.bin on external SD? /storage/external_SD/about.bin
Did you push it with adb?
Did you adb shell?
Did you su?
Zaaap
Zaaap72 said:
Hi Reposix,
if you would tell us the ADB commands you used before we might be able to help.
Did you put the about.bin on external SD? /storage/external_SD/about.bin
Did you push it with adb?
Did you adb shell?
Did you su?
Zaaap
Click to expand...
Click to collapse
about.bin was put on the SD with the usb, i used this adb command to patch it : dd if=/sdcard/aboot.bin of=/dev/block/mmcblk0p6
The last two questions are invalid since without i wouldn't have been able to use the previous command.BTW, i fixed by replacing destroyed mmcblk0p6 with the stock one, i asked a guy on the forums to give me one, anyways i appreciate your conscientiousness :good: .
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.:thumbup:
Sent from my Nexus 7 using XDA Free mobile app
Zaaap72 said:
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.[emoji106]
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
/sdcard/ is a symlink to /storage/emulated/0/
So, he probably put it at the internal SD.
Sent from my D620R [Stock 4.4.2]
Zaaap72 said:
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.:thumbup:
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Right..i forgot...i used adb shell just like this :
-adb shell
-su
-dd if=/sdcard/%imagename%.img of=/dev/block/mmcblk0p17
-reboot
And it's aboot.BIN not .IMG(i'm writing with caps so you can notice no offense )
And Vagelis is right, i put it on the internal SD not the external.
Thank you for clarifying this. :thumbup:
May help others with a similar problem.
Zaaap
can you help me too
Rephosix said:
Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Click to expand...
Click to collapse
HI my pone is bricked, it's dead
i was trying too root my phone and put twrp on it than it got me in recovery mode but i got frustrated because i didn't know how to select the options so i took my battery out with the hope that my phone would just reboot like normal but it didn"t. now i tried the buttons : home and volume down or volume up and connect with usb it just won't work, can you pleas help me... it does connect to my pc but nothing else
@Teamsvg
Don't you think one thread is enough for your issue?
Teamsvg said:
...it does connect to my pc but nothing else
Click to expand...
Click to collapse
And it connects in which mode? ADB? Recovery? Download? Media?
Have you tried the method I recommended in your thread?
http://forum.xda-developers.com/showthread.php?p=54325341
And if you don't answer questions no one can help!
Zaaap
Zaaap72 said:
@Teamsvg
Don't you think one thread is enough for your issue?
And it connects in which mode? ADB? Recovery? Download? Media?
Have you tried the method I recommended in your thread?
http://forum.xda-developers.com/showthread.php?p=54325341
And if you don't answer questions no one can help!
Zaaap
Click to expand...
Click to collapse
I've got the same problem ; phone is not response to ADB , Download, USB , nothing , when i connect to my pc , nothing happens, the only time i see anything is when i pull the battery and plug in USB the sign of no battery is visible
Any things i can try ?
Tried:
Pulling battery and restart
Starting with volume up + power
Starting LG soft and holding volume up while plugging in usb
Al these things diden't help , still screen stays black and no response from usb on pc...
HELP !!
:crying:
please help i have the same promblem.. i copied wrong aboot.img how did you fix it???
Rephosix said:
Right..i forgot...i used adb shell just like this :
-adb shell
-su
-dd if=/sdcard/%imagename%.img of=/dev/block/mmcblk0p17
-reboot
And it's aboot.BIN not .IMG(i'm writing with caps so you can notice no offense )
And Vagelis is right, i put it on the internal SD not the external.
Click to expand...
Click to collapse
please help i have the same problem.. i copied wrong aboot.img how did you fix it???
thanks in advance
please email to me your solution.. if you have time thanks.
[email protected]
tengskie said:
please help i have the same problem.. i copied wrong aboot.img how did you fix it???
thanks in advance
please email to me your solution.. if you have time thanks.
[email protected]
Click to expand...
Click to collapse
http://forum.xda-developers.com/g2-mini/help/bricked-phone-help-t3192435/page2?nocache=1
Hello,
today i tried to root my phone who runs on kitkat 44.2 and i v'e made a big mistake
i wanted to make my phone look like the g3
now its rooted but while it got in recovery i didnt know how to select the options so what i did was
i took my battery out and now i tried to get it on again and it won't
it doensn't want to get in recovery nothing
when i connect it with my phone it shows that its connected
i don't know what to do can someone help me pleasss i want it back like the beginning without the root pleas (((((
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
hi
Zaaap72 said:
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
Click to expand...
Click to collapse
hi, thnks for replying
this is what i tried
https://www.youtube.com/watch?v=KINp9v_GN3o
i didn't enable usb debugging ...
zaap
Zaaap72 said:
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
Click to expand...
Click to collapse
My phone is like this: you the screen is black, i forgot to enable usb debugging because i tried to root it in my phone so i ddin't need my computer, i can't get in download mode or recovery nothing ! i tried the buttns( and no my buttons works fine) how can i fix this? the link you've send me ask me to put my phone in download mode : "if your device is bricked and can't boot you'll have to enter the Download Mode, to do that just keep holding the Vol. Up button while inserting the USB cable in the phone( The USB cable must be already plugged into the PC while doing that), and you keep it until you go into the Download Mode."
but it can't ...
Teamsvg said:
My phone is like this: you the screen is black, i forgot to enable usb debugging because i tried to root it in my phone so i ddin't need my computer, i can't get in download mode or recovery nothing ! i tried the buttns( and no my buttons works fine) how can i fix this? the link you've send me ask me to put my phone in download mode : "if your device is bricked and can't boot you'll have to enter the Download Mode, to do that just keep holding the Vol. Up button while inserting the USB cable in the phone( The USB cable must be already plugged into the PC while doing that), and you keep it until you go into the Download Mode."
but it can't ...
Click to expand...
Click to collapse
autoirec is onyl for g2.. not mini. becouse we have locked bootloaders custom recoverys doesnt work. something similiar happened to my phone. i can tell you by confedens that first of all it doesnt sound that you are familiar with custom recoverys and stuff and that you have hard bricked your phone. i had to send mine in after 2 days of trying to make it start again. it is broken. and if you take it to service i wouldnt tell them what you did or that you rooted it.
Try this. If you phone is detected under sdb or sdc you have a chance to unbrick your phone.
I attached the files needed to unbrick G2 mini:
sbl1.img
aboot.img
rpm.img
tz.img
recovery.img - download from here.
Be very careful. The order of partitions for our phone is different from the LG G2. So then you use "gdisk -l /dev/sdb" command, find the partitions numbers of each file attached, and use that number in dd command.
I do not know why on tutorial for G2 there is a warning not to flash original recovery.img on recovery partition. So my advice is to flash all partition except recovery.img and see if your phone enter download mode. If not, flash recovery.img, you have nothing to lose.
If the phone enter download mode flash kdz.
powermetza said:
Try this. If you phone is detected under sdb or sdc you have a chance to unbrick your phone.
I attached the files needed to unbrick G2 mini:
sbl1.img
aboot.img
rpm.img
tz.img
recovery.img - download from here.
Be very careful. The order of partitions for our phone is different from the LG G2. So then you use "gdisk -l /dev/sdb" command, find the partitions numbers of each file attached, and use that number in dd command.
I do not know why on tutorial for G2 there is a warning not to flash original recovery.img on recovery partition. So my advice is to flash all partition except recovery.img and see if your phone enter download mode. If not, flash recovery.img, you have nothing to lose.
If the phone enter download mode flash kdz.
Click to expand...
Click to collapse
Can i use this files on G2 Mini D618?
Thanks!
No you can´t.
Sent from my LG-D620 using XDA Free mobile app
could anyone help with a seemingly bricked tab speed 6, attempted to root using kingoroot and it failed causing connection issues to google so i was unable to add a account, after hard reset and booting in to recovery i have wiped the cache and reset to factory, however now the tablet is stuck on checking connection and doesn't go any further with or without sim card.
after searching and searching i have come up with nothing apart from this threadhttp://forum.xda-developers.com/general/xda-assist/stock-rom-vodafone-speed-tab-6-vf-1397-t3329343
it looks as though he is having the same problem.
assuming kingoroot has corrupted the rom and i need to reflash to repair it,
i don't know if it is a generic tablet it appears to be made by alcatel but im unsure.
i also do not know if i could use a firmware from another device or even custom rom, anything will do as long as it doesn't end up in the bin
i also have another which hasnt been messed with and was wondering if it would be possible to back up the rom from it and reflash it to the bricked one, if so could anyone steer me in the right direction
could anyone help me locate as rom and flashing tool that will help
thanks in advance, apologies if this is posted in the wrong place.
You said you had a second one, you don't have to root it, just follow this tutorial and hopefully you should be good to go.
no bootloader
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
inexperience
thanks for the help I am quiet inexperienced but determined so any help pointing me in the right direction would help thanks
facerolla said:
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
Click to expand...
Click to collapse
What command do you do to tell adb to reboot to download? What command to you give fastboot to flash the recovery?
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
I don't know if download mode is accessed differently I've found this post that seems to Suggest hold volume up and down then connect until battery charging appears http://forum.gsmhosting.com/vbb/f272/vf-1397-a-2047715/ this is for unlocking it seems, but don't seam to be able to get it to work, earlier I removed root with kingoroot from kingoroot app, also to no avail and rooted again both root removal and rooting were successful but still tablet stays on the checking connection screen when rebooted, I was hoping the removal may of fixed the issue but no...., I was thinking if I could get back custom recovery on it I could do the same to the working one I have begrudgingly so I could back up the working ones rom and use it to flash the bricked one, but I don't really want to risk bricking that one either, but was considering finding another rom from another model the same chipset and flash it with that but obviously no download mode means I can't do it..
if it's any help The recovery mode states android system recovery <3e>
LMY47V release keys
reboot system now
wipe data/factory reset
wipe cache partition
power down
enable adb
they are the only options,
again thanks for all your time and effort
facerolla said:
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
Click to expand...
Click to collapse
You can't always unlock the bootloader via that command and you'll need to have the bootloader unlocked to flash a custom recovery, if you can find stock images on the web you can flash them via fastboot.
---------- Post added at 12:44 PM ---------- Previous post was at 12:36 PM ----------
Also to restore an adb backup you do "adb restore filename".
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
facerolla said:
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
Click to expand...
Click to collapse
Hello! Remember this?
Also to restore an adb backup you do "adb restore filename".
Click to expand...
Click to collapse
Did it work? I see you left a "thanks" so I assume something happened.
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
facerolla said:
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
Click to expand...
Click to collapse
I have a couple tricks up my sleeve and that is, you know how you said when you ran adb reboot bootloader? Run adb shell instead and it should give you a command explorer, from there, type "su" and report results, you should see either a root request on the device or a hash sign in the coommand shell.
Just a quick question
Did you ever manage to get it working if so how did you go about doing it as i attempted to install a custom boot animation and it appears to be stuck in a constant boot loop as such i'm not really sure what to do with it or if it is savable. Any response would be helpful. Thanks.
How to make oppo a57 be fastboot mode.
I want to install twrp and will be in root.
I've tried to hold volume + power button but become booting to window screen again..
what is oppo a57 no feature fastboot mode?
And what version twrp for oppo a57?
Please help me
thanks
"volume+" and "power" mostly running recovery/twrp mode.
Try "volume-" and "power" for fastboot mode.
Developer option is running? OEM unlock?
Load TWRP please. I wanna try too. Thanks.
volume - and power to recovery mode default oppo..
volume + and power oppo loggo appears and than booted to start again..
i have done it all before..
butstill can not get into fastboot mode..
i have not instaled twrp..
i want to fastboot mode to install twrp..
the problem is oppo a57 can not get into fastboot mode..
unlike oppo f1 i already successfully install twrp and root..
please help me
thanx for the answer
How about ADB?
USB-debagging, OEM unlock on phone, then use terminal.
"ADB reboot bootloader" - isn't work?
I'll try some things too, then return to home after work.
i have done and nothing happened,when running adb command "adb reboot bootloader" phone restart and returne to home screen not to fastboot mode.
i try to do this repeatedly until finally i ask to this forum..
help me
thanx for the answer
can someone help me?
Hello Dear, I have been trying the same with My Oppo A57, but still nothing works, I hope, we find out a way to enter fasboot mode. Thanks
Oppo A57 makes me dizzy:crying:
Fastboot access has been disabled on Oppo A57
Hey guys,
I've been looking into this situation and as far as I can tell, fastboot is disabled/unavailable on new Oppo devices unless we can find a workaround.
Fastboot was disabled by Oppo to help secure ColorOS but was previously available by flashing 'project spectrum'. Based on this report by Ausdroid it appears that they have either cancelled or temporarily suspended development of project spectrum now as well: http://ausdroid.net/2017/03/16/oppo-project-spectrum-killed-off-hiatus-notice/
A potential option I have found was a flashable zip file (magictricks.zip) that was created to enable fastboot on the Oppo F1 but I have not yet attempted to flash it as it wasn't made specifically for the A57 so it could possibly brick it.
https://forum.xda-developers.com/oppo-f1/development/boot-loader-unlock-twrp-related-t3397013/page1
I have emailed the creator of magictricks.zip asking if there's potential that it could work but I have yet to receive a response.
If someone has an A57 and is feeling brave, flashing it might possibly work as the F1 had fastboot disabled for the same reason. I am not responsible for your bricked device if you attempt this though.
Here's hoping some senior devs start helping us out with this because this phone has the potential to be an awesome well spec'd budget device with a custom rom installed.
Here's hoping.
I am waiting for news from the maker of magictrick.zip..:good:
thank
I tried .
Magictricks get rejected by A57 recovery.
As any other not genuine oppo firmware.
I tried adb reboot edl command and it works.
Blank screen phone is recognized as COM port in Windows.
That could be way to upload custom boot image.
martinr1 said:
I tried .
Magictricks get rejected by A57 recovery.
As any other not genuine oppo firmware.
I tried adb reboot edl command and it works.
Blank screen phone is recognized as COM port in Windows.
That could be way to upload custom boot image.
Click to expand...
Click to collapse
Interestingly I only found this out the other day as well.
Turns out if you put: *#801# in the dialer it gives you access to a diagnostics menu which let's you activate a bunch of Qualcomm diag ports.
Problem is I'm a rookie when it comes to QPST. I was able to use one of the included programs to backup a copy of my non-volatile memory but I'm not sure if I did it correctly or if that information is even useful? It's only 917KB.
Now would be a great time for an experienced developer to chime in. If you know ways to use QPST to back up I can do it and send you the files you need.
You need to modify emmc_appsboot.mbn to enable fastboot, then flash to phone with built in recovery or harder way with QPST tool.
Magictrics contains also emmc_appsboot.mbn but for different phone.
Original firmware is available on oppo website. It is 1.7GB size, quite a bloat. It contains emmc_appsboot.mbn
If you look inside that file with text editor you can see fastboot commands etc.
It is implemented but disabled.
martinr1 said:
You need to modify emmc_appsboot.mbn to enable fastboot, then flash to phone with built in recovery or harder way with QPST tool.
Magictrics contains also emmc_appsboot.mbn but for different phone.
Original firmware is available on oppo website. It is 1.7GB size, quite a bloat. It contains emmc_appsboot.mbn
If you look inside that file with text editor you can see fastboot commands etc.
It is implemented but disabled.
Click to expand...
Click to collapse
Thanks for the info, now I'm headed in the right direction. You sound like you know your stuff a lot more than me tbh.
See the potential problem I could see with the stock recovery is that I'm assuming it would have some kind of signature verification to ensure that the update.zip is legitimate.
I'm in the process of fixing my computer atm so I can't use it to look at the file right now.
When I open emmc_appsboot.mbn with a generic editor it's gibberish. Do I need to use notepad++ or is it just encrypted or a compressed format?
I reckon I could work out how to decrypt the emmc_appsboot.mbn but repackaging it into a working flashable file makes me nervous..
I hate this phone in its current state though so I guess I've got nothing to lose if I brick it haha. Wish me luck.
So I've done some digging and realised it's a binary file. Looks like I've got a steep learning curve ahead of me trying to wrap my head around editing these binary files. ?
This should be fun.
Good continue waiting then
Yes, it is binary file, but with text editor you can find understandable text inside gibberish.
Better results can be seen with dissassembler.
More info:
newandroidbook.
com
/Articles/aboot.html
So what next?
is there a solution?
I hope to find the best solution ..
thanks
It seems there might be a solution in China.
bbs.7to.cn/thread-315780-1-1.html
I got my A57 to custom recovery and root.
http://bbs.7to.cn/thread-315939-1-1.html
Hi to everybody,
my MI 9T Pro has black/broken screen so I need to access it and/or replicate the screen by using the ADB facility.
It has the USB Debug enabled, but I cannot authorize the access from my laptop due to the black screen and broken touch, there is any possibility to bypass the authorization process?
I have already tried to connect a mini-docking station in order to replicate the screen via the USB-C to HDMI feature, but nothing appears on the external display.
Any suggestion?
Many thanks
Roberto
P.S.: the phone works, it receives call, it is connected to the wifi network and, if it is connected via USB to the laptop, the "adb devices" command returns its serial number followed by a sad unauthorized status...
Tamagnun said:
Any suggestion?
Click to expand...
Click to collapse
Hello and good afternoon, Roberto.
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Thank you Oswald, sorry for my wrong posting, I chose that thread because it was referred to ADB.
Kind Regards
Roberto
Don't know if it'll help, but the unauthorized message means a mismatch between pc and phone.
You can do this:
Go to C:/Users/<your username>/.android and delete a file called "adb key"
It's a hidden folder so activate that in folder options.
However, this will only trigger a new authorization message on the phone again.
The Android usb debugging notification gives you the option to switch the connection to be controlled from the phone to the PC side but it won't help if you can't see it.
IamTheBRAVE said:
Go to C:/Users/<your username>/.android and delete a file called "adb key"
Click to expand...
Click to collapse
Thank you very much for the useful tip!!
In this folder I found two files with the same timestamp:
- adbkey (without extension)
- adbkey.pub
Do you think it's better to delete both, isn't it?
Any idea to connect to the smartphone the USB-C data cable AND an external keyboard at the same time, using an OTG adaptor?
I need to use the data cable for ABD because I'm afraid I didn't activate the wireless debug option on the phone AND the keyboard in order to try to grant the authorization when the popup "appears" (ehm... it cannot, but if it should be possible it woold appear!! )
Anyway, many many thanks for this first step!!
Tamagnun said:
Thank you very much for the useful tip, in that directory I found two files,with the same timestamp:
- adbkey (without extension)
- adbkey.pub
Do you think it's better to delete both, isn't it?
Click to expand...
Click to collapse
Both is ok.
Any idea to connect to the smartphone the USB-C data cable AND an external keyboard, via OTG adaptor?
I need to use the data cable for ABD because on the phone I'm afraid I didn't activate the wireless debug option AND the keyboard in order to try to grant the authorization when the popup "appears" (ehm... it cannot, but if possible it wuold appear!! )
Click to expand...
Click to collapse
I don't know, maybe a wireless keyboard ? Or an usb hub like this:
https://www.amazon.com/TargetGo-Splitter-Extender-Ultra-Slim-Microphone/dp/B0957JKBHZ
So you can plug both the keyboard and the phone cable. Not sure if it would work...
Good luck
Hi Iam,
I'm performing some tests with an old phone (Note 4) in order to check your suggestion: unfortunately it's not possible to connect a keyboard (using an OTG cable, the phone is the "host" and devices are "clients") and to use ADBat the same time, because the standard data cable sets the phone like "client" and the PC like "host".
In fact in the OTG cable the pin 4 in the micro-USB connector is closed to GND, in standard data/charge cable the PIN 4 is not connected.
The idea to use a wireless keyboard is good, but with the black screen I cannot control BT connection or other.
In addition, I verified that the grant popup appears only if the phone is unlocked and also this is very hard with the black (and dead) screen.
I read in another thread (that I'm not able to find now...) that by copying the adbkey file from the PC .android folder to an internal android directory on th phone (something similiar to /data/adb/keys, but I don't remember well...) the smartphone authorizes the PC to connect via adb, do you now if this method could be a way to bypass the manual grant operation ?
Do you know a method to copy a file from PC to the phone by starting it in recovery mode?
Fastboot can help in this operation?
Thank you
Transferring files can only be done with adb push command.
I am not aware of a directory in the phone with the adbkey in it. So can't help you there...
Edit: found this
Storage location of "adb_keys"
I have a Galaxy s3 (I9300) that has a broken touch screen (display is fine). I therefore can not click the authorization dialog that pops up when I try to access the device via adb on any ROMs above
android.stackexchange.com
Hope it helps a little.
Hi Iam, thank you for your help!
On GitHub I found the cmd to copy RSA key from the PC to the smartphone, it is:
adb push %userprofile%/.android/adbkey.pub /data/misc/adb/adb_keys
but the author wrote that it works only with rooted phones... and my broken one is not!!
Anyway I'll try and I'll write here the result of the test in order to share my experience.
Nothing to do, it doesn't work...
The phone is switched on because if I connect it to the data cable on the PC I get this result:
C:\Users\rober>adb devices
List of devices attached
598261c1 unauthorized
and it is in RECOVERY MODE because I cannot find its IP address on the wifi router, but I cannot push the adbkey file:
C:\Users\rober>adb push C:\Users\rober\.android\adbkey.pub /data/misc/adb/adb_keys
adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I don't have any idea to bypass the unauthorized state, due the host/client state it isn't possible to connect an external keyboard and the data cable at the same time, wireless keyboard cannot be paired without accessing the display so I dont' know how to proceed... sigh...
If someone has a suggestion I'll really appreciate it!
Found this. Can you try it?
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
What do you have for a screen lock? Swipe? Pattern? Numbers?
You need to tap and swipe the screen to get things done.
A plugged in mouse could do that if you only knew what you were doing.
If you have a digitizer (Wacom tablet) you can use that to do anything the screen can do.
Also, are you quite sure that the screen isn't responsive? It could be black but responsive.
I did a project to swipe patterns using a separate, rooted Android.
It works like a charm, but it's kind of a pain to set up.
See: https://forum.xda-developers.com/t/accessing-my-phone-with-a-dead-screen.4542763/post-88013171
Hmm, it's actually more complicated.
I plug in a device and the authorization popup appears.
But, if I pull the plug, the popup disappears after a second.
You won't be able to get a USB digitizer working.
You'd need a Bluetooth digitizer, but that would have to be enabled too.
So you'd need the USB digitizer to enable the BT digitizer.
(By "digitizer" I mean any absolute pointing device.)
If there is an internal UART (hardware console) you might be able to simply type in the adb_keys.
this script claims to by-pass the adb authorization by patching stock boot.img and resign with google test keys. it might work on locked bootloader (untested)
https://github.com/bkerler/android_universal
I don't know how it works, but you can hopefully write/flash partitions in EDL mode with this loader (untested)
https://forum.xda-developers.com/t/...r-qualcomm-based-phones.4368989/post-88041131
there is also a linux executeable to reboot into EDL mode from fastboot
https://github.com/bkerler/edl
Code:
$ fastboot devices
$ ./fastpwn oem edl
to install the loader
Code:
$ python3 edlclient/Tools/fhloaderparse path/to/FHLoaderDir Loaders
if you don't have linux you can try the re_livedvdV4.iso from pendrive.
there is also executeable for windows to reboot EDL and another EDL tool for windows (credits: @Renate)
the downside of this, once you rebooted phone you cannot get back to its currently (AFU) unlocked state, which means all your files are no longer decrypted (BFU). you can install apps remotely only as long as the phone is decrypted and online, so maybe there is a better way (vysor?)
alecxs said:
there is also a linux executeable to reboot into EDL mode from fastboot
Click to expand...
Click to collapse
I see that the "fastpwn" is 12 MB. Seems a bit large. No idea what's in there.
Some abl's may support fastboot commands for getting to EDL.
I've never seen it clearly listed which do have that.
The standard fastboot filters all commands except for "oem".
Code:
fastboot tickle me elmo // will not even be sent because "tickle" is not on the command list
fastboot oem ridiculous command // will be sent since oem commands get a free pass
So if your device uses an oem command to get to edl it will work with the stock fastboot.
If it uses a special "first tier" command you will have to use a modified, lenient fastboot.
IamTheBRAVE said:
Found this. Can you try it?
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
Hi Iam, I found a similar page on GitHub and I tried to input the adb pull command (see my previous msg), but because the PC is not authorized there is no way to write anything on the phone by using abd.
Many thank for your tentative to help me.
Renate said:
What do you have for a screen lock? Swipe? Pattern? Numbers?
You need to tap and swipe the screen to get things done.
A plugged in mouse could do that if you only knew what you were doing.
If you have a digitizer (Wacom tablet) you can use that to do anything the screen can do.
Also, are you quite sure that the screen isn't responsive? It could be black but responsive.
I did a project to swipe patterns using a separate, rooted Android.
It works like a charm, but it's kind of a pain to set up.
See: https://forum.xda-developers.com/t/accessing-my-phone-with-a-dead-screen.4542763/post-88013171
Hmm, it's actually more complicated.
I plug in a device and the authorization popup appears.
But, if I pull the plug, the popup disappears after a second.
You won't be able to get a USB digitizer working.
You'd need a Bluetooth digitizer, but that would have to be enabled too.
So you'd need the USB digitizer to enable the BT digitizer.
(By "digitizer" I mean any absolute pointing device.)
Click to expand...
Click to collapse
Hi Renate,
it is not possible to connect at the same time a USB keyboard (phone is the server by using an OTG cable) and a data cable (phone is the client in this situation) and as you have verified, when the data cable is disconnected, the grant message disappears...
I have a BT keyboard, but it is not possible to pair it to the smartphone working on a black screen, even if it was responsive.
Finally, I thing there isn't a way to bypass the grant message and authorize the phone "regularly", I think.
Renate said:
If there is an internal UART (hardware console) you might be able to simply type in the adb_keys.
Click to expand...
Click to collapse
Where the UART should be present? Inside the phone? Uhhmmmm.... Even if I found it your idea would be to wire it by soldering directly on the mainboard? Too much difficult for my poor experience, sorry!
Many thanks for your answer.
Before to start with replies, dear Alexc and Renate please let's apologize me because I'm absolutely newbie about these new devices, in order to clarify to you my (un)knowledge condition, let's consider that my last fw update was performed using the Odin tool on very old Samsung devices!
Thanks to your suggestions, now I know what is the fastboot and EDL (I read something on XDA and other sites), but I haven't understood if it is possible to read the userdata from one of these two boot states... anyway, I try to reply you, if you would want to continue to help me I'll be very grateful for this!
alecxs said:
this script claims to by-pass the adb authorization by patching stock boot.img and resign with google test keys. it might work on locked bootloader (untested)
https://github.com/bkerler/android_universal
Click to expand...
Click to collapse
It is written that it is tested only up to Android 10, so I prefer to avoid to test this method on a smartphone that hasm't a working screen, it isn't possible to understand what happens on it.
https://github.com/bkerler/android_universal
alecxs said:
I don't know how it works, but you can hopefully write/flash partitions in EDL mode with this loader (untested)
https://forum.xda-developers.com/t/...r-qualcomm-based-phones.4368989/post-88041131
Click to expand...
Click to collapse
I downloaded the firehose file for the chipset 855 but I'm not interested to flash a new firmware or similar...
alecxs said:
there is also a linux executeable to reboot into EDL mode from fastboot
https://github.com/bkerler/edl
Code:
$ fastboot devices
$ ./fastpwn oem edl
Click to expand...
Click to collapse
OK, the previous is clear for me: now the smartphone is booted in fastboot mode and the utility can access it:
Code:
C:\Users\rober>fastboot --version
fastboot version 34.0.0-9570255
Installed as C:\Android-Recovery\platform-tools\fastboot.exe
C:\Users\rober>fastboot devices
598261c1 fastboot
Is the fastboot utility version the right one to operate on my smartphone?
Please let's explain me: if I'll reboot the phone to EDL (using fastpwn utility, fastboot oem command or another utility or method) I risk to lose my userdata ?
alecxs said:
to install the loader
Code:
$ python3 edlclient/Tools/fhloaderparse path/to/FHLoaderDir Loaders
Click to expand...
Click to collapse
Sorry for the stupid question, but why I have to install a loader on the phone?
alecxs said:
if you don't have linux you can try the re_livedvdV4.iso from pendrive.
Click to expand...
Click to collapse
My Surface has Win10 and Ubuntu (I never use it but I have prepared a dual boot for any needs...).
alecxs said:
there is also executeable for windows to reboot EDL and another EDL tool for windows (credits: @Renate)
Click to expand...
Click to collapse
I would prefer to use Windows utilities, but it is not mandatory...
Before to try to switch to EDL I need to understand if this operation will destroy my data or not, and what I can do from this EDL boot mode, I know it is posisble to flash the phone from scratch, but is it possible to read data by mounting phone partitions or similar?
For example, I listed the fastboot options and I found the possibility to FETCH a partition from the phone and copy it to the PC, this can help to access my data?
Maybe they are encrypted?
Do you have a schema or a list of all available partitions inside a MIUI 13 device? (I need to learn something before to proceed...)
alecxs said:
the downside of this, once you rebooted phone you cannot get back to its currently (AFU) unlocked state, which means all your files are no longer decrypted (BFU). you can install apps remotely only as long as the phone is decrypted and online, so maybe there is a better way (vysor?)
Click to expand...
Click to collapse
So, the previous message is the reason I'm very carefull before to switch to EDL boot mode: is it enough to switch the phone to EDL in order to lock all data because they'll become definitively encrypted ??
Please let's try to clarify me your suggestions and how to proceed...
Many many thanks for your patience
Update: with the cmd fastboot getvar all I obtained the entire partions list, I tried to fetch one of this and the result is:
Code:
C:\Users\rober>fastboot fetch limits cache.ext4
fastboot: error: Unable to get max-fetch-size. Device does not support fetch command.
Not good, but at least I have answered to a couple of questions by myself... sigh...
@alexc: two years and seven months ago you helped someone to retrieve userdata from a bricked MI 4C by suggesting the followiing process, can i do something similar on my MI 9T PRO?
1 Obtain a programmer
To successfully acquire all of the data from EDL you need programmer.
For Mi 4c it is prog_emmc_firehose_8992_ddr.mbn that can be obtained in (first?) official image of OS. I got it from file Xiaomi_Mi_4C_V8.1.3.0.LXKCNDI_20161213_China_5.1_XFT.zip on some random site. You can find it in the archive under folder Firmware/images/.
The full path in archive would be Firmware/images/prog_emmc_firehose_8992_ddr.mbn.
2 Get working FirehorseI have got mine from repository: https://github.com/bkerler/edl.
Proceed with all instructions mentioned in the repository. (I personally used Ubuntu 20.04 as all of the stuff is easier to make work.)
3 Connect to EDLBoot phone to fastboot. In case of Mi 4c that is my case it is pushing volume down during boot.
When you enter fastboot and you can see your device with fastboot:
fastboot devices
In case of Mi 4c you can directly boot to EDL with command:
fastboot oem edl
4 Acquire data through EDLWhen device enters EDL state you can test connection with programmer (in my case prog_emmc_firehose_8992_ddr.mbn). In loader parameter you are entering path to this file.
./edl.py --loader=prog_emmc_firehose_8992_ddr.mbn printgpt
When it outputs all of the partition then you are golden!
On my phone there is one partition named userdata:
userdata: Offset 0x00000000c4000000, Length 0x0000000683bfbe00, Flags 0x00000000, UUID 07c2b899-1574-564c-2f46-e26a6378bdd8, Type 0x1b81e7e6
To acquire the partition use command:
./edl.py --loader=examples/prog_emmc_firehose_8992_ddr.mbn r userdata userdata.bin
The copy of user data just needs to be read.
5 Reading user data (userdata.bin)Luckily for the phone Mi 4c you can directly mount the dump in Linux. For some other phones the process might not be so straightforward and you might need simg2img. But I am not 100% sure.
sudo mkdir /media/userdata
sudo mount -t ext4 -o loop userdata.bin /media/userdata/
To read the data you will need to get root rights as the data belong to non-existing or different existing users and you won't get access with your user.
sudo mkdir userdata
sudo cp -r /media/userdata/media/0/* userdata/
The path to the your data might be different so take your time to look around.
Done! All the data are now completely accessible.
Click to expand...
Click to collapse
What is the "programmer"?
As I wrote before, I downloaded the file prog_ufs_firehose_sdm855_ddr.elf but it is the firehose, not the programmer, isn't it ?
Many thanks, I spent all the night to try to acquire some knowledge, but I have too many dubts again...
When your Android boots it goes PBL (in ROM) -> xbl -> abl -> Android.
A Firehose loader is a custom replacement for xbl that it can load live.
Instead of loading all the rest of the stuff it just sits on USB and awaits commands.
Firehose, programmer, loader, .bin, .elf, .mbn can all be the same things.
Using EDL will not hurt your system or data (unlike fastboot unlock).
If you read back your userdata it will still be encrypted (if it was).
One thing that you can do is read back your entire image.
Then you will in any case be able to restore your device to exactly how it is right now.