Can someone please give me a hand 😭😭i bricked my n100 - OnePlus Nord N100 Questions & Answers

Ok so i downloaded a module for lsxposed and we'll it prompted to reboot my phone and GG it was stuck in boot loop and well i tried factory reset cleared data etc etc so i have the original payload.bin but i need the actually img files so i can manually fasboot command each one since i rooted my device without PC and i don't have access to one ATM. If anyone has extracted the files from the payload.bin can u please let me know

How on earth did you root without a PC and how will you flash the images without one? Also we need to know your model (BE2012/BE2013/BE2014/BE2015) and your OOS version (10.0.1/11.0.1/11.0.7/etc/etc). Or you can attach the payload file you have so someone can extract it.
Alternatively you can try to switch slot in bootloader if you can execute fastboot commands. However if boot image is also patched on the other slot then this will probably not work.

I have to manually flash them one by one example fastboot flash vbmeta etc etc Haha yes i know it's actually quite difficult but with trial and error i managed to root it and have essentially full access all without a PC hehe trust me it took me 72plus hours and what is the command to switch from boot_a/boot_b and i will attach the payload.bin file hopefully someone can help

fastboot getvar current-slot will tell you your current slot. fastboot --set-active=[a or b] to switch.
I still don't understand how you are running the commands if you're not using a PC. Except if you're using adb on another phone.

Yeah i bricked it bad now lol i searched on Google found the same commands so i switched it to _a and we'll now it won't boot to recovery or even to the bootloader and i use bugjaeger app essentially use your phone as a pc but is limited

Related

[Q] How to restore back to factory settings after using towel root

I have rooted my device using towel root which doesn't unlock the boot loader. I then used the twrp manager to install custom recovery. I am wondering how to restore everything back to factory as all the tutorials I have seen so far require an unlocked boot loader. Any help will be appreciated, thank you.
Flash a stock r for your phone
swagg blasted from TMO LG G3
jailbreakkid23 said:
Flash a stock r for your phone
swagg blasted from TMO LG G3
Click to expand...
Click to collapse
If I download a stock image from google and flash it from my nexus 7 using twrp will everything be restored to factory settings?
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
fastboot
Jordydaman said:
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
Click to expand...
Click to collapse
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
@SidDev said:
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
Click to expand...
Click to collapse
Would you mind finding a link for me ? I have never encountered this before as I have always unlocked the bootloader to root but this time I used towel root which was different as explained above.
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
try this and press thanks
Jordydaman said:
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
Click to expand...
Click to collapse
nope,
Step 1: Download the ADB/Fastboot files and the
USB drivers for Windows based PC first. The the
latest factory image for your Nexus device can be
downloaded directly from Google’s website .
ADB/Fastboot – Mac , Windows
USB drivers for Windows
Extract the contents of the ADB/Fastboot ZIP file
inside a new folder called ‘google’ on your desktop.
Extract and transfer the contents of the factory
image inside this folder as well. The list of files will
include a ZIP file containing the codename of your
Android device, two files with “flash-all” names, and
a bootloader image file. All the extracted contents of
the factory image should be inside the same folder
as the ADB and Fastboot file, otherwise you will get
a file not found error.
Make sure to install the ADB drivers as well if you
are running a Windows based PC.
Step 2: Now, reboot your Nexus device in bootloader
mode. This is usually done by switching off the
device, and pressing the Volume down + Volume Up
+ Power button simultaneously. If that does not
work, try the Volume down + Power button
combination.
After the device has booted into bootloader mode,
connect it to your PC.
Step 3: Open a new Terminal or Command Prompt
window, and navigate to the ‘google’ folder that you
created in Step 1. Before we start flashing the
factory image, we need to make sure that your
Nexus device is being detected by the PC.
fastboot devices
If you are using a Mac, then you need to prefix a “./”
before every Fastboot command. So, the above
command will look something like this on a Mac -:
./fastboot devices
The above command should confirm if your device is
indeed being detected by your PC or not. If it is,
then proceed to the steps below. If not, repeat the
steps above again. Make sure that you have properly
installed the drivers and are inside the correct
folder.
If you are running Windows, copy-paste the following
command in the command prompt window -:
flash-all.bat
On a Mac, copy-paste the following command -:
./flash-all.sh
The script will then automatically flash the full
factory image on your Nexus device. Once the
factory image has been flashed, your device will
automatically reboot. Keep in mind that the first boot
might take some time so please be patient.
If the flash-all.sh script gives you a fastboot not
found error on your Mac, open up the file in Text Edit
and add a “./” before every fastboot command.
The flash-all script included in the factory image
might not work for all. It has always been pretty
unreliable and has only worked once for me in the
last 2 years. If you are in the same boat as me, you
will have to flash each partition manually on your
device. This is slightly cumbersome though.
The command to manually flash a partition via
fastboot is “fastboot flash partition filename.img”. In
the factory image that you extracted in Step 1, you
will notice there is another ZIP file. Extract the
contents of that ZIP file inside the ‘google’ folder.
Now, its time to manually flash the partitions to your
Nexus device. We will first begin with the bootloader.
fastboot flash bootloader filename.img
Then, we will flash all other partitions. They don’t
necessarily need to be in the same order as I have
listed them below. The names of the image files in
the factory image will clearly indicate the partition
they are intended for as well.
fastboot flash boot filename.img
fastboot flash radio filename.img
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img
Thank you very much I will try this today.
I couldn't flash all and when I flashed the bootloader it came up with failed bootloader is locked?
Enter this command to unlock the bootloader:
fastboot oem unlock
After unlocking, you can run flash-all.bat (or run manual fastboot commands to flash).

Possibly Bricked Pixel XL

Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
parakleet said:
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
Click to expand...
Click to collapse
No offence but i am lost by what you said, I am trying to get back to completely stock. Is part of my issue the fact that command prompt didn't detect my device? or no?
I'm not exactly sure what to do with the information you shared, sorry
I the tutorial i found it says to make sure the command prompt sees your device but doesnt say what to do when it doesnt see it.
Also, I downloaded the may factory image, i believe it was version O
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
jreink01 said:
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
Click to expand...
Click to collapse
If you did not get your phone from Verizon use this
7.1.2 (N2G47O, May 2017)
Download the zip
unpack all the zip files some are nested so unzipping one creates more keep unzipping until there are no more then gather the following img files
bootloader.img
radio.img
boot.img
system.img
system_other.img
vendor.img
modem.img
Some of those names are cut down as i hate typing long strings, jsut rename them as such.
Create a folder on root of c:\_PIXEL_XL_
put all the files there.
You will use way less files than you unpacked
once you have done that run the following commands
copy and paste
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
After last reboot just wait and you will be back at stock
if that doesnt work
Download latest version of TWRP place it in C:\_PIXEL_XL_
rename it twrp.img, again i hate typing long strings
from bootloader run
fastboot boot c:\_PIXEL_XL_\twrp.img
This will take you into twrp
you might need to wipe system and cache and data,
From memory the fourth entry at bottom is internal memory or user data, in any event if you do not check that your data stays on the phone.
Once you have wiped the other 3 rerun the fastboot commands and you will be back at stock
add the twrp and supersu commands from earlier to add root.
dont forget the signatureverify.img if you are doing that.
good luck.
you arent bricked
you just need to find the correct combination of steps to get your phone where you want it to be
Thanks for the response. I am having a hard time with this, the zip file i downloaded from the google website, when i open it, there are only 6 files, 1 of which is a zip file (marlin). When I open marlin it shows a bunch of files, none of which you mentioned. I am confused, was wondering if you would be nice enough to walk me through this over the phone, i would be really grateful.
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
jreink01 said:
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
Click to expand...
Click to collapse
Yes, i sent you a PM.
HALV0RS3N said:
Yes, i sent you a PM.
Click to expand...
Click to collapse
thanks, sent you my #
Okay so I had the exact problem yesterday. To to the Google developers site and download the official Google pixel or xl 7.1.2 nougut ota update. Once that's downloaded, go to your phone, I had all the exact same screens on my phone so it should work. Hold down the power button until it completely shuts down. Then hold the power and volume down to go to recovery mode, if it goes back to the ext 4 screen, try it again until it goes to recovery mode, then on command prompt type, fastboot boot twrp.img then once it's in twrp, go to advanced-then adb sideload and click both boxed and then swipe to enter sideload. Then on your computer, type adb sideload "file name for Google update" and hit enter. That should do the trick. Like I said, I had the exact same problem yesterday
---------- Post added at 06:56 PM ---------- Previous post was at 06:50 PM ----------
Also, I forgot to mention, download the twrp image file from the Internet. Shouldn't be hard to find just make sure it's the latest. Put that file in the adb file on your computer same with the Google update for your phone. Do not unzip either file. That's very important. DO NOT UNZIP THE UPDATE File. When you type in the twrp.img make sure you type img. And when you flash the update, make sure at the end of the file name you put
.zip ex( marlinpixelxl7.1.2.zip)
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
Looking at your screen shot you didn't let the file finish flashing. It sticks at the "does not contain" for a bit before it continues.
You were doing it right. You just didn't wait.
If it wasn't going to work it would eventually give you a failure and jump to the command prompt.
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
RedBlueGreen said:
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
Click to expand...
Click to collapse
OP was flashing to stock. Didn't let it finish though.

Mixed Nougat/Oreo partitions

My Honor 7x (BND-L21) is totally bricked for the moment. I think there is Nougat and Oreo partitions at the same time because of Huawei Multi-Tool. Now I can't boot into recovery/eRecovery and the device stucks in the splash screen (bootloader unlocked). I think I have to rewrite all the partitions but I don't know how to do it... If anybody has a solution it will be greatly appreciated, I tried for 1 week!
If your device has a locked bootloader or frp follow these steps
First of charge your device for 1 hour in whatever mode it is..
https://www.androidfilehost.com/?fid=11050483647474828964
Then download the service rom from the above link
Extract the contents of the downloaded file. Copy the dload folder from the extracted files to a sdcard.. (Directly to it not on any directory)
Insert the sd card..
Press all the buttons until the emui logo comes.
After the flashing reaches 100 percent.. Reboot the device unlock the oem in developer option..
Step-2 (Computer)
Download adb drivers and fastboot and install them.
Download complete ota package for your device (make sure you have the correct build number because service rom has a different build number ) (download size will be above 2gb)
Extract all downloaded zip files. Then using huawei firmware extractor extract all contents of the update. app files.. (one update. App file in each zip files)
Copy
kernel. Img
Ramdisk. Img
System. Img
Cust. Img
Version. Img
Vendor. Img
And version. Img to the folder having adb files. And version and vendor files to sd card
//Make sure that the complete ota package you downloaded matches the os before the software brick(noughat or oreo) //
Open the adb folder and do shift plus right click to open command window there and connect your device in fastboot mode to pc
Use the below commands one by one each after completion
Fastboot devices(show your device if its connected)
Fastboot oem unlock (code obtained from huawei unlock page)
#factory rest occur
After tha enter fastboot mode again
Step-3
Fastboot flash ramdisk ramdisk.img
Fastboot flash recovery_ramdisk recovery_ramdisk. Img
Fastboot flash system system. Img
Fastboot flash cust cust.img
Flash twrp using
Fastboot flash recovery_ramdisk twrp. img
Boot your device to recovery mode.( Volume up plus power)
Flash version. Img to version partition and vendor. Img to vendor partition
If you want stock recovery back
Boot into fastboot mode
Enter the command
fastboot flash recovery_ramdisk recovery_ramdisk. Img
And do a reboot
Relock bootloader upto your wish..
Better keep oem unlocked in developer options
If you have both unlocked bootloader and frp follow from step 2
I heard huawei discontinued the unlock page
In that case use dc unlocker to find the code
It will cost some money
All credits to @mrmazak
Thank you I will try this but the dload method didn't worked when I tried 4 days ago...
I can't go into dload update mode (when I hold all the physical buttons the phone restarts and this appears (picture 1) and got stuck on this screen).
Also I don't know why but the phone doesn't charge, when I unplug it after 1h of charge, it shows the critical battery screen (picture 2) and it goes off...
Any help is reaaly appreciated!
Any other ideas?
gabrce said:
Any other ideas?
Click to expand...
Click to collapse
Though situation, if not charging. Bit to verify, try different cable and charging brick to make sure.
I changed twice the cable and nothing change...
Is there a method to factory reset the device in fastboot mode?
Maybe I should try HWOTA8?
gabrce said:
Maybe I should try HWOTA8?
Click to expand...
Click to collapse
Will need to de able to boot twrp for hwota to work.
So what should I do? Is there a method to flash twrp without fail? Because I can't boot into it...
gabrce said:
So what should I do? Is there a method to flash twrp without fail? Because I can't boot into it...
Click to expand...
Click to collapse
If battery is not charging, then it will not take a flash.
You can maybe try remove back cover and unplug battery, then reconnect see if it will take a charge.
As for your question about resetting with fastboot. You can wipe data, and maybe format system also. But I don't think that will help you.
My friend is asking help. His situation is similar. The phone is honor 6x.
My opinion is that something wrong with boot partition. you can ask some body extract the boot image from another phone. Then run "fastboot flash boot_ramdisk boot.img".
Hope it helps
Thank you for your answer.
This command didn’t work.
My phone got stuck for one month now...I’m desesperate...
gabrce said:
Thank you for your answer.
This command didn’t work.
My phone got stuck for one month now...I’m desesperate...
Click to expand...
Click to collapse
I try to help again.
Describe problem please
As I recall it is as follows
** Phone working,
** Attempts some backup or restore using multi-tool
** This made phone no longer boot
**Possible that nougat images flashes to Oreo partition tanle (or visa- versa)
**Now no recovery or erecovery will even boot.
**Also phone shuts off with low battery as soon as cable unplugged.
If this is the case, I see no way forward. Because the battery needs to hold something in order for flashing to complete

Stuck on loading G screen

I see a lot of people have this same problem for different reasons and the solutions are seemingly all over the place if any
My phone recently lagged out and i had to restart it, which is when my issue happened.
I know my space was running low so im assuming that may have something to do with why it happened.
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else. I am new to this and have absolutely no idea what im doing. So ive googled as much as i could but some things arent making sense, id appreciate some help or a step by step
some info
my phone is 100% stock aside from my nova home launcher.
I dont not have custom bootloaders
my phone has a password, idk if that matters but just in case
my phone is not jailbroken (i think is the term?)
I did have USB debugging set already, and I BELIEVE i had developer mode enabled
thats about it for the phone info
In the bootloader main scree, it stats im in fastboot mode, secure boot yes, device state, locked
What ive tried
-I have tried the manual OTA install via the adb stuff
i got success 0 but upon restart, nothing changed and i was still stuck
-i tried the flash steps
but i get "flashing is not allowed in lock state pixel 2"
ive tried to use a pull command via adb, but it said some strings were incorrect? I just copy pasted a command from a similar post, it may not have been catered to my situation fully so i dont know about that
Is there any steps i can take to simply either recover my photos before i factory reset, or reset without wiping, or even maybe delete some files to make space via something somehow?? I just need my data, the phone itself i can replace
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Edmontonchef said:
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Click to expand...
Click to collapse
i turned that off initially but checked the site just in case, theyre not backed up ):
Sui77 said:
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Click to expand...
Click to collapse
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
buninthesun said:
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
Click to expand...
Click to collapse
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Edmontonchef said:
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Click to expand...
Click to collapse
the OTA sideload has a success of 0 but nothing happens beyond that, the phone still gets stuck at loading
does 0 mean it should have worked? Any idea why nothing changed?
Sorry for the problems.
My bootloader is unlocked, so that might be the reason.
buninthesun said:
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else.
Click to expand...
Click to collapse
Try the following.
1. Download the latest ADB and Fastboot binaries from the links at this page.
2. Extract the zip file you just downloaded to a directory on the root of a drive. For example, I have my copies of ADB and Fastboot stored at a directory I created, D:\ADB.
3. Open a command prompt, not a powershell window, and navigate to that directory using DOS commands.
4. Enter the bootloader on your device and connect your device to your PC.
5. Type "fastboot devices" to make sure the P2XL appears.
6. If it does, type the following commands:
fastboot getvar all
fastboot --set-active=a/b
fastboot reboot
The idea here is to get you into the device by using the second partition. To do this, you need to find out which slot you are currently using, A or B, and set the active slot to the OTHER partition. "fastboot getvar all" will tell you which slot is currently active. "fastboot --set-active=a/b" will change the active partition to the currently unused one. For example, if the active slot is currently a, you would issue the command "fastboot --set-active=b" to switch to the other partition, and then reboot.
Moral of the story here is unlock your bootloader and leave it that way.
So much easier getting out of trouble

Recovering data on a DEAD Redmi Note 8 PRO

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

Categories

Resources