Related
I am not responsible if you damage your device in any way you are the one that has decided to modify your device.
Guide
1. Download the Beta 2.68 SuperSU zip
2. Make sure you have adb and fastboot and robin usb drivers installed there are tons of guides just google it if you need to install them.
3. In cmd line type the following after connecting robin to your computer (and accepting the computer on robin if first time)
Code:
adb devices
It should start adb and you should see a device listed if it properly connected with developer options enabled, if not go back and make sure you have the proper drivers installed and USB debugging is indeed enabled.
4. Next we are going to unlock the bootloader, if you already have then skip this step.
-It will wipe ALL you data if you are coming from a locked bootloader so back up your internal storage
- You will need to enable developer options in your settings, this is done by going Settings->About phone and tapping Build number 7 times or until you "become a developer". Then you will need to go back to Settings->Developer options and enable USB debugging
First you must reboot to bootloader use the following command to do that:
Code:
adb reboot bootloader
Then after the device has rebooted into the bootloader screen you need to type this command
Code:
fastboot oem unlock
6. Now that we are still in bootloader you can install twrp download the latest twrp img from here
https://twrp.me/devices/nextbitrobin.html
7. Run the following command to flash twrp:
Code:
fastboot flash recovery twrp-3.0.0-0-ether.img
8. Now the easiest way to root it with out having to time mashing the buttons to reboot to recovery again is to fastboot boot the recovery image and install your SuperSU zip then.
Code:
fastboot boot twrp-3.0.0-0-ether.img
9. MTP does work so if you forgot to move your SuperSU zip over you can do it in recovery. Now you just do the normal proccess to flash a zip.
Troubleshooting
1. Some fastboot binarys do not recognize the Robin's fastboot id so if your device is not showing up please add the following to your fastboot commands -i 0x2c3f so a command would look like this
Code:
fastboot -i 0x2c3f flash recovery twrp-3.0.0-0-ether.img
Mine just in case
WOWWWW!!! AWESOMEEEE!! THIS IS AMAZING!!!
Xposed will work right? Will unlocking bootloader reset device??
varun.gid said:
WOWWWW!!! AWESOMEEEE!! THIS IS AMAZING!!!
Xposed will work right? Will unlocking bootloader reset device??
Click to expand...
Click to collapse
Xposed works, unlocking the bootloader wipes all data on the device.
I keep having issues with adb. It connects when the phone is on and USB debugging. But when I go to fastboot, it doesn't connect for me to go forward.
Drivers are good and whatnot.
Use fastboot -i 0x2c3f
Sent from my Robin using Tapatalk
joeminati said:
I keep having issues with adb. It connects when the phone is on and USB debugging. But when I go to fastboot, it doesn't connect for me to go forward.
Drivers are good and whatnot.
Click to expand...
Click to collapse
Fastboot mode doesn't have ADB enabled genius. Fastboot is within the bootloader, while adb is a daemon started by the kernel's init.rc on first boot.
AMAZING THANK YOU SO MUCH! I had to use fastboot -i 0x2c3f
You think Nextbit will support flashing updates through TWRP?
deadman96385 said:
Mine just in case
Click to expand...
Click to collapse
I'm having a problem.. I unlocked bootloader.. flashed recovery... booted into it there was nothing.. Empty folder for internal storage.. Then i booted up the ROM, and then again booted to TWRP.. it asks for password to decrypt.. Please Help!
varun.gid said:
I'm having a problem.. I unlocked bootloader.. flashed recovery... booted into it there was nothing.. Empty folder for internal storage.. Then i booted up the ROM, and then again booted to TWRP.. it asks for password to decrypt.. Please Help!
Click to expand...
Click to collapse
You have to put in your encryption password, it is the one that you have to put in when you boot up the device normally.
deadman96385 said:
You have to put in your encryption password, it is the one that you have to put in when you boot up the device normally.
Click to expand...
Click to collapse
I tried that it didn't work! N then i did advanced wipe and in a hurry i checked system... Now I'm screwed i have No OS Lol!
varun.gid said:
I tried that it didn't work! N then i did advanced wipe and in a hurry i checked system... Now I'm screwed i have No OS Lol!
Click to expand...
Click to collapse
I will upload a full stock twrp backup later today so you and others can recover until factory images are released.
deadman96385 said:
I will upload a full stock twrp backup later today so you and others can recover until factory images are released.
Click to expand...
Click to collapse
Awesome! Please try n load rooted one if possible! Thanks once again life saver!!!
deadman96385 said:
I will upload a full stock twrp backup later today so you and others can recover until factory images are released.
Click to expand...
Click to collapse
I am in the same boat. Can't access internal files if password does not release them. So he can't flash without the TWRP password. Or am I missing something?
deadman96385 said:
I will upload a full stock twrp backup later today so you and others can recover until factory images are released.
Click to expand...
Click to collapse
Any luck in putting it up.. The stock rom?
@deadman96385
Sorry for pushing but please please can u upload stock TWRP /Backup..
Didn't work for me, not only the TWRP kept asking me for a password no matter what, but latter on when I decided to flash through adb sideload, got stock in the bootloader and wiping didn't solve the issue for me. So now I don´t now what to do, I guess I´m going to have to wait for the image as well...
Here is a rooted twrp backup:
http://forum.xda-developers.com/nex.../rom-rooted-twrp-backup-t3336828#post65843511
Does somebody have robin image?
I had wiped my robin system...
Does somebody have robin image ?
Or somebody can backup the image and upload for me ?
Thank a lot!!
---------- Post added at 05:52 AM ---------- Previous post was at 05:40 AM ----------
nelson0521 said:
I had wiped my robin system...
Does somebody have robin image ?
Or somebody can backup the image and upload for me ?
Thank a lot!!
Click to expand...
Click to collapse
I see the link, thanks everyone.
Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?
Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone
tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted
**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.
Hi all,
I have a T-Mobile Revvlry that I’ve been trying to flash lineage os to. It was unlocked and now after so many tries, it is oem locked
I went through all the unlock bootloader process before and was able to flash but always no os installed are you sure you want to proceed.
Slots a and b were confusing and so I changed the slot to a for flashing but this time the bootloader screen changed along with the serial number and now it is oem locked and can do nothing now .
I tried to boot twrp but no success. How can I oem unlock?? I tried the command fastboot oem unlock and fastboot flash etc but it is denied and that I need a code. Which I do have but don’t know how to use it now.
glossallalia said:
Hi all,
I have a T-Mobile Revvlry that I’ve been trying to flash lineage os to. It was unlocked and now after so many tries, it is oem locked
I went through all the unlock bootloader process before and was able to flash but always no os installed are you sure you want to proceed.
Slots a and b were confusing and so I changed the slot to a for flashing but this time the bootloader screen changed along with the serial number and now it is oem locked and can do nothing now .
I tried to boot twrp but no success. How can I oem unlock?? I tried the command fastboot oem unlock and fastboot flash etc but it is denied and that I need a code. Which I do have but don’t know how to use it now.
Click to expand...
Click to collapse
Did you follow the preinstall instruction and use copy-partitions-20210323_1922.zip?
if not that's what caused the problem.
You will need to use a blankflash to fix
Search for Channel blankflash there are some here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but you may need a newer one
The device will need to be in Emergence Download Mode (EDL Mode)
Use
Code:
fastboot oem blankflash
or
boot twrp (use full twrp file name)
Code:
fastboot boot twrp.img
and use
Code:
adb reboot edl
EDL Mode is just a black screen, and
Windows device manager will see it as a Qualcomm device (attached)
If it says ..._bulk... you need the Qualcomm drivers
Thank you! Yes I did follow the preinstall instruction and used copy-partitions-20210323_1922.zip several times. But obviously messed it up somehow.
I was missing some of the things you mentioned so I’ll work on that and thanks again!
sd_shadow said:
Did you follow the preinstall instruction and use copy-partitions-20210323_1922.zip?
if not that's what caused the problem.
You will need to use a blankflash to fix
Search for Channel blankflash there are some here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but you may need a newer one
The device will need to be in Emergence Download Mode (EDL Mode)
Use
Code:
fastboot oem blankflash
or
boot twrp (use full twrp file name)
Code:
fastboot boot twrp.img
and use
Code:
adb reboot edl
EDL Mode is just a black screen, and
Windows device manager will see it as a Qualcomm device (attached)
If it says ..._bulk... you need the Qualcomm drivers
Click to expand...
Click to collapse
Blankflash did work to blank the screen. But <adb reboot edl > came back with ‘no devices/emulators found’.
I do have the Qualcomm drivers
glossallalia said:
Blankflash did work to blank the screen. But <adb reboot edl > came back with ‘no devices/emulators found’.
I do have the Qualcomm drivers
Click to expand...
Click to collapse
No, you only use "adb reboot edl" if "fastboot oem blankflash" didn't work.
Now use the blankflash file.
sd_shadow said:
No, you only use "adb reboot edl" if "fastboot oem blankflash" didn't work.
Now use the blankflash file.
Click to expand...
Click to collapse
Ok, when I do the blankflash, there is the blank screen, however I can't communicate with the device after that and if I have lineage.zip or copy-partitions-etc...zip, how could I flash it or what is the next step? I'm new at this - I started this a year ago, after, gave up for a while.
Thanks!
glossallalia said:
Ok, when I do the blankflash, there is the blank screen, however I can't communicate with the device after that and if I have lineage.zip or copy-partitions-etc...zip, how could I flash it or what is the next step? I'm new at this - I started this a year ago, after, gave up for a while.
Thanks!
Click to expand...
Click to collapse
If you have run the blank-flash.bat and it worked the device will reboot to bootloader.
If the device remains in EDL Mode, the blankflash failed, you may need a newer version.
You may need to do some searching in the forums for a newer version.
sd_shadow said:
If you have run the blank-flash.bat and it worked the device will reboot to bootloader.
If the device remains in EDL Mode, the blankflash failed, you may need a newer version.
You may need to do some searching in the forums for a newer version.
Click to expand...
Click to collapse
thanks - blank-flash.bat worked and i'm back to flashing again - I sideload copy-partitions-etc.zip and the lineage.zip and there is 'no os installed...' this happens every time, and before as well. When I 'start' from the fastboot flash mode, it starts to draw the lineage symbol, then goes back to bootloader.
glossallalia said:
thanks - blank-flash.bat worked and i'm back to flashing again - I sideload copy-partitions-etc.zip and the lineage.zip and there is 'no os installed...' this happens every time, and before as well. When I 'start' from the fastboot flash mode, it starts to draw the lineage symbol, then goes back to bootloader.
Click to expand...
Click to collapse
what is the file name of lineage.zip?
sd_shadow said:
what is the file name of lineage.zip?
Click to expand...
Click to collapse
LineageOS17.1Modified.img.xz
I went to Motorola website and flashed the firmware to restore the phone to its original state. I'll try lineage again in future and thank you!
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