Related
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
Your boot image is missing...
When your phone boots in bootloadermode, it should (now, anyway) say: boot.img missing. Or something of that nature. Check this, flash it via fastboot, then everything should be back to normal...
EDIT:
It works with both: CDMA & GSM
luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
do you know how to use fastboot and adb?
Excuse my lack of knowledge, but how exactly do I flash something over fastboot? Thanks in advance again.
Edit: And I do know how to use adb, however it does not connect. I do not know how to use fastboot
After some playing around with fastboot, I now have a basic understanding. However, I am not sure where I should be flashing that file you have linked.
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
luminuss3 said:
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
Click to expand...
Click to collapse
I'd seriously try to go back to stock first. I'm not a Windows user but if you have adb, fastboot, and your drivers setup, it should be easy. Mark is a great help in this thread and you can use his script I guess:
http://forum.xda-developers.com/showthread.php?t=1400871
You need to also realize that if you have wiped everything to install a new rom, you have nothing to boot to. Also there is install-recovery.sh file that keeps re-writing your recovery to stock erasing custom recovery (CWR) until you rename or erase that file. So going back to stock would be the safest and then you can try again.
You can use adb in recovery and fastboot in bootloader. If you have everything setup correctly (sdk, adb, fastboot, drivers for windows) either of these commands should recognize your phone:
In Bootloader (the first screen you see with big arrow on top):
Code:
fastboot devices
In recovery:
Code:
adb devices
If you don't have a recovery, then use the first one. If you see your phone's serial number like this
Code:
List of devices attached
HT12HS005115 device
you can now use it to flash things onto your phone. As I said I am not a windows user so I can't be specific, sorry. But adb and fastboot, once you are at their prompt, should work the same.
In general, when fastboot is recognizing your phone in the bootloader, you can use:
Code:
fastboot flash zip YOURFILENAME.zip
changing yourfilename of course. This zip file could be a stock imaqe or a custom recovery. Again, you need someone with windows to give you exact steps, this is just general stuff.
if your phone is yakju build then you can get the stock images from google.
download and unzip the files to your fastboot folder and use these commands, the file names in these commands are for the Android 4.0.1 (ITL41F) build so you will have to change the filenames if you use a different build.
Code:
fastboot devices (to make sure your phone is connect to fastboot)
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
Hello, I have sent my phone to warranty and after that I received a phone with NO RPMB and after many frustrations I found (with help of many users and forums) how to workaround this..
To start:
Download boot image from here
Download twrp from the official website
Change the name to boot.img and twrp.img and put it in the platform-tools folder
Open the terminal there
Download your favourite rom
Enter fastboot mode on your phone
!!!!After this you will loose all of your data!!!!
Paste this to the terminal
fastboot oem unlock
(select yes on your phone)
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot format userdata
fastboot format cache
Reboot to recovery (if it doesn't enter at the first time enter download mode again and restart to recovery)
After that you have twrp and can flash every rom.. yay!!!
Wipe everything.
Copy the rom zip to your phone using MTP
Install your fancy new rom
If you want to install magisk:
Install the magisk manager.
On the app select install and select patch image file. (it will create a new boot image already patched)
After that install the new image (patched_boot.img) using twrp
Do a clean instalation of your ROM (recomended) or a Factory Reset first
Reboot to twrp
Select install
Click in install image
Select patched_boot.img
Select install to boot partition
Reboot.
Install magisk manager and do the sugested setup.
You now have magisk working
Thanks to all the users that helped me!!
I had real trouble getting twrp to work the last time I tried this a few months ago. Followed the steps here and am now on pixel experience with magisk. Thanks!
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
sigibian said:
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
Click to expand...
Click to collapse
My bootloader is still unlocked after following this guide
For Magisk:
-Install your custom ROM and boot it up (without root)
-Then extract the boot.img from the ROM zip file and save it on your phone storage.
-Install the Magisk manager apk
-In Magisk manager, select install Magisk> choose the patch boot image option and -Select the boot.img you previously saved.
Once it's done, reboot into twrp and flash the patched boot.img. When you reboot Magisk will be working.
I've had no issues with my bootloader, even after an ota update for pixel experience.
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
sigibian said:
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
Click to expand...
Click to collapse
The official twrp works for fine for me, haven't tried the 4 core version but it can't hurt to try if you need it.
Power off your phone then press and hold volume - and power to enter bootloader, then connect to your pc and follow the steps in the OP
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
sigibian said:
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
baddesthad said:
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
Click to expand...
Click to collapse
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
sigibian said:
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
Click to expand...
Click to collapse
You need to use vol- and power to go into fastboot mode then connect to the pc. As for userdata and cache, if you don't clean them when coming from stock you will have issues (your data will be encrypted if you're on stock?). As I said this guide worked for me. The op was talking about fastboot mode in the 6th option (also there is much more information in the thread I linked above)
sorry for the confusing i wanted to say fastboot mode..
i knew the thread that you are saying but most people doesn't want to search so I made a little thread only with the needed parts..
I use it myself so I have a place to remember all the steps when I need to change the rom to a new one or when I make experiments and brick my phone XD
If anyone know anything else that should be in here just say, I really want to improve the post
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
fhartane said:
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
Click to expand...
Click to collapse
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
PedroM.CostaAndrade said:
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
Click to expand...
Click to collapse
Thanks for the answer. You mean that now I have twrp, I can flash custom Roms with my bootloader locked without any issue?
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yes if you have TWRP you can install custom ROMs, custom Kernel's, magisk, super su, etc..
the locked bootloader only prevents you from using fastboot commands like the one needed for installing custom recovery
Now that you have TWRP you can use it for everything
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Fabiojoker said:
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Click to expand...
Click to collapse
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Hello, thank you for your information, since I haven't done modding on phones for a long time, I didn't remember exactly the procedure with fastboot and therefore I didn't understand where I had to put the files, but in the end I did it.
Thank you
PedroM.CostaAndrade said:
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Click to expand...
Click to collapse
Why is a custom boot image needed? I don't want to root.
Hello, on any custom roms we see recovery as img, so whats the ultimate good process to actually flash it?
img to tar bootloop
any other recovery bootloop
only one thats working is "twrp-z3s-3.5.0_10-A11_6+vbmeta_DUB5" BUT i have x1s, so pain to flash some rom.
Im currently on beyond rom 3.1, because i cant flash anything else.
Any help here?
Try flashing vbmeta.img after flashing recovery
like download mode -> recovery, then download mode again and only vbmeta?
didnt try that, ill try it right away
edit:
1) download mode -> AP EXYNOS-G98X-LINEAGE-RECOVERY-20200709
2) booted up rom
3) turned off -> download mode -> USERDATA vbmeta.tar from beyond rom
4) bootloop, up button and power same thing
i dont know if i should try stock and then go for root again or what exactly do.. i dont want to lose any data now. It got really complicated, since i go from root apk clockworkmod era.
maybe magisk is the issue? since i have it installed
Go to fastboot
Flash recovery
Flash vbmeta
Reboot
If fastboot doesn't like extensions of your images, change them to .img
how can i get to that? on TWRP if i do reboot -> fastboot, im still in TWRP and "fastboot devices" shows completely nothing (not even list of devices or whatever)
when i go to bootloader mode from magisk i just see "entering fastboot mode.." and thats about it, no fastboot commands work
b30wu1f said:
how can i get to that? on TWRP if i do reboot -> fastboot, im still in TWRP and "fastboot devices" shows completely nothing (not even list of devices or whatever)
when i go to bootloader mode from magisk i just see "entering fastboot mode.." and thats about it, no fastboot commands work
Click to expand...
Click to collapse
Move vbmeta.img to your phone and go to Install section. Install it and reboot.
Also, TWRP offers an option to reboot to bootloader. You can try it too
well, i flashed lineage recovery img and then vbmeta, phone booted up, but got probably original recovery. its really frustrating. Do you have any valid and working "tutorial" to get the recovery working ?
i just need recovery thats x1s, so it should be probably lineage recovery, but cant install it. Im starting to hate these new phones.
I'm sorry, I don't have any specific tutorial, but in general:
adb reboot-fastboot
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot-recovery
If this doesn't work, search for your specific device on XDA. You shouldn't hate new phones, you should hate people who sell them, because they make everything hard so you won't switch from their software, which spies on you.
tried TWRP that works, installed as img lineage-18.1-20210224-recovery-x1s.img and now it suddenly worked. Thank you for help, after 6 hours =)
On an older phone I used TWRP recovery. That has a brilliant option to create system backups.
How to do that in the LineageOs recovery?
I want to clone one phone to another identical phone. I hope that can be done by creating a backup on phone 1 and install it from recovery on the other. Hopefully including the OS (with all the setting that take hours of fiddling about), apps and data.
Just use twrp..?
PhotonIce said:
Just use twrp..?
Click to expand...
Click to collapse
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp
carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Use twrp backup and select all the partitions. It'll back up everything.
Apps and settings are located in the data partition and other files/data is located in the internal storage partition. boot is the kernel, recovery is the recovery and system in the system image.
If you know what you're doing you could even install a fresh copy of lineage onto another phone and just restore the data and internal storage partitions, and still receive an exact copy of the phone you backup up from while using less space in the backup.
... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?
Paul_Neocube said:
... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?
Click to expand...
Click to collapse
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.
PhotonIce said:
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.
Click to expand...
Click to collapse
On my device there are two slots... A and B. Like two separate partitions that van have software installed to. When I installed my rom I first installed twrp to slot a and then my Tom to slot b which is what runs now when I power on my device. I can't install twrp to the slot my os is on as I would have issues with the os recovery that is on that slot.
Skorpion96 said:
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp
Click to expand...
Click to collapse
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.
zogoibi said:
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.
Click to expand...
Click to collapse
It's not. He keeps LineageOS recovery on the phone, and when he wants to use TWRP, he connects the phone to his computer via USB and runs fastboot boot twrp.img from the command line. This reboots the phone and loads TWRP into memory without flashing it to the phone.
@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?
zogoibi said:
@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?
Click to expand...
Click to collapse
actually i done the reverse, i have twrp installed and when i want to run lineage recovery i boot it with fastboot boot "recovery.img"
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
You ever flashed TWRP via cmd (adb) on a pc? It's the same thing but you use fastboot flash rather than fastboot boot. When you flash twrp on phone, you put the recovery.img file in your adb folder, if I'm not mistaken. The same thing goes for booting an .img file (it goes in the adb directory/folder in your pc).
zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
The alternate recovery should remain on the computer. It can be in the same folder as adb and fastboot for easy access (it doesn't need to be there, it's just easier that way). That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.
MJPollard said:
That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.
Click to expand...
Click to collapse
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.
zogoibi said:
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.
Click to expand...
Click to collapse
Try fastboot boot recovery twrp.img. I don't normally do this so I might have misremembered it. If it works, I'll edit my post so that others don't get confused.
Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!
zogoibi said:
Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!
Click to expand...
Click to collapse
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.
agamemnonn said:
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.
Click to expand...
Click to collapse
I found out that it's not possible. LOS Recovery's fastboot mode has that command disabled.
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5