Develop Bugs

Oneplus 3 Boot Issue

Well, Long story short, I flashed Freedom OS on my Oneplus 3 and things went poorly. I set up a passcode and when my device booted, the passcode was somehow changed to one other than what I had put. Not only that, I seem to have no recovery on my device either. Basically I can boot into my lockscreen where I'm basically screwed, and I can mess with fastboot but I'm unable to flash a rom, twrp wont flash either. Please help, will do anything.

bparisi15 said:
Well, Long story short, I flashed Freedom OS on my Oneplus 3 and things went poorly. I set up a passcode and when my device booted, the passcode was somehow changed to one other than what I had put. Not only that, I seem to have no recovery on my device either. Basically I can boot into my lockscreen where I'm basically screwed, and I can mess with fastboot but I'm unable to flash a rom, twrp wont flash either. Please help, will do anything.
Click to expand...
Click to collapse
Did you try the mega unbrick guide ? http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

bparisi15 said:
Well, Long story short, I flashed Freedom OS on my Oneplus 3 and things went poorly. I set up a passcode and when my device booted, the passcode was somehow changed to one other than what I had put. Not only that, I seem to have no recovery on my device either. Basically I can boot into my lockscreen where I'm basically screwed, and I can mess with fastboot but I'm unable to flash a rom, twrp wont flash either. Please help, will do anything.
Click to expand...
Click to collapse
Recovery:
I assume you are on FreedomOS CE, have you flash the recovery who's recommended for the CE version?
If no, read the op: http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-ce-1-7-t3470660
and use this command in fastboot:
Code:
fastboot flash recovery twrp-3.0.2-19-oneplus3.img
Lockscreen / data:
Because you have set a passcode at the booting time (not the basic lockscreen).
You can't restore all your data, because all the partition is now encrypted, the only way to access to that is to use the passcode.
The only way to fix that is to format your data partition in fastboot (not twrp).
Code:
fastboot format userdata

NevaX1 said:
Recovery:
I assume you are on FreedomOS CE, have you flash the recovery who's recommended for the CE version?
If no, read the op: http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-ce-1-7-t3470660
and use this command in fastboot:
Code:
fastboot flash recovery twrp-3.0.2-19-oneplus3.img
Lockscreen / data:
Because you have set a passcode at the booting time (not the basic lockscreen).
You can't restore all your data, because all the partition is now encrypted, the only way to access to that is to use the passcode.
The only way to fix that is to format your data partition in fastboot (not twrp).
Code:
fastboot format userdata
Click to expand...
Click to collapse
THANK YOU SO MUCH! The data format completely fixed it for me, thank you so much!

I have rooted my OP3 and manually updated to 3.2.6 O2 os,but unfortunately device get unrooted and no custom recovery is there.But now i want to root and install custom recovery but Facing problem with ADB Interface Device can't be detected in Fastboot mode????please help me out.

Relock bootloader on LOS microG

Hello all
I desperately try to relock my bootloader but failed many times and I am shortly before giving up. I was once on a locked bootloader on LOS but camera didn't work. (Couldn't reproduce)
Maybe you see something I missed out / didn't understand.
The main reason is, that some apps like ebanking check the state of the bootloader. And they also don't go through Securenet because of huawei.
So what I tried with this setup:
sign both boot.img and twrp.img with BootSignature.jar using own private key
Twrp Using: twrp-3.5.2_9-0-oneplus3
boot img from:
lineage-17.1-20210330-microG-oneplus3
lineage-18.1-20210403-microG-oneplus3
With firmware: oxygenos-9.0.6-firmware-3 from https://github.com/nvertigo/firmware-3t/tree/master/archive/op3
Mostly I got the ideas from https://forum.xda-developers.com/t/device-forum-rules-please-read-before-posting.3333345/
And what I do is this:
Using fastboot flash signed recovery
boot into recovery
whipe everything (is this needed every time?), data, factory reset, all partitions except internal & usb
reboot into recovery
sideload lineageos with signed boot.img inside
fastboot oem unlock => directly restarts after 'yes'
boot into LOS
fastboot oem unlock => directly restarts after 'yes' again
Do you see something I do wrong? Should I use other versions/files?
Hope to find a way
Edit: Also I can go back to stock where it gets locked again using the latest OnePlus3_16_A.86_191104_repack.

Problem Rebooting into Recovery

I am in the process of installing LineageOS 18.1 onto a Pixel 3 XL (I have done a Pixel 3 before with no issues). I am following the instructions from lineageos.org (https://wiki.lineageos.org/devices/crosshatch/install). It is specific instruction for the Pixel 3 XL. I have successfully completed the first number of steps but got stuck on the last one noted below:
Unlocking Bootloader (ALL COMPLETE)
enable OEM unlock
connect device to PC
adb reboot bootloader
fastboot devices
fastboot flashing unlock
reboot
re-enable usb debugging
Temporarily Booting a Custom Recovery
download a custom recover (lineage-18.1-20210803-recovery-crosshatch.img) - COMPLETE
connect device to PC - COMPLETE
adb reboot bootloader - COMPLETE
fastboot devices - COMPLETE
fastboot flash boot lineage-18.1-20210803-recover-crosshatch.img - COMPLETE (received msg that sending and writing to boot_a is okay)
reboot into recovery - INCOMPLETE
will not reboot into recovery, stays in fastboot mode
last line on fastboot mode screen says "no valid slot to boot" at one point it also said "error booting boot.img"
Any idea/suggestions on what would be the problem? I did try redoing the fastboot flash boot command an additional time and again it said it sent and wrote ok, however, still unable to reboot into recovery. I did not check the version of android on the phone before i flashed the lineage 18.1 recovery - could that be the problem? Might it be that the phone cannot run LIneage 18.1 because it is on android 10? (which I'm not sure how to check at this point). If this is the problem what would be the best solution - reflash with a lineage 17.1? Or, is there a way at this point to check and upgrade the android on the phone? Perhaps there is another problem entirely.

Fastbootd can't find "product" partition

I'm trying to install LineageOS via fastbootd, since TWRP can't mount the super partition. I can flash most images with a method similar to this post, but "fastboot flash product product.img" fails with "FAILED (remote: 'No such file or directory')". "fastboot erase product" gives a slightly more helpful "FAILED (remote: 'Partition doesn't exist')". The only solution I was able to find was apparently for 32bit Windows systems, neither applies to my computer.
How can I create this partition or, if it exists, make fastbootd see it? Or do I have to enter something other than "product"?

"adb sideload lineageos.zip" while in Los recovery

HueyT said:
"adb sideload lineageos.zip" while in Los recovery
Click to expand...
Click to collapse
Yeah, that was the first plan, it's also what the official instructions say. But neither the LOS recovery, nor TWRP can mount the super partition, so sideload, flash, wipe, file explorer etc. all fail. At this point I think that TWRP for the OnePlus 7T (with or without "Pro") might just be unfinished software and not usable for ROM installation, but if you think it can work, please help here, it's my older thread about trying to get that to work: https://forum.xda-developers.com/t/recovery-unable-to-mount-storage.4378801/

Fabian R�ling said:
Yeah, that was the first plan, it's also what the official instructions say. But neither the LOS recovery, nor TWRP can mount the super partition, so sideload, flash, wipe, file explorer etc. all fail. At this point I think that TWRP for the OnePlus 7T (with or without "Pro") might just be unfinished software and not usable for ROM installation, but if you think it can work, please help here, it's my older thread about trying to get that to work: https://forum.xda-developers.com/t/recovery-unable-to-mount-storage.4378801/
Click to expand...
Click to collapse
MSMtool to go to last oos10, ota to latest oos11, install Los recovery, sideload los18.1 zip

HueyT said:
MSMtool to go to last oos10, ota to latest oos11, install Los recovery, sideload los18.1 zip
Click to expand...
Click to collapse
I just found this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
That's a Windows tool. Wine can launch it, but I don't even know if it would work, because if I do "adb reboot edl", the phone just shows a black screen, almost as if it was off (but not really, because then it would show something when charged).
Can EDL mode break? Or this ADB command? How else would I enter that mode? I've also read to hold volume up and volume down, but I've done that for some time and nothing happened.

Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…
I did not do the bootloader-based installation with that, so I'm not sure if I should mark this thread as solved.

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