Oneplus Bricklooping, Never ending Audio FX FC error, No IMEI/Baseband unknown, Corrupt EFS
READ THIS!!!
I cannot guarantee that this will work for everyone. However It has proven to be a solution for almost everyone that have used it. So if it does not work I ask that you be respectful in posting as such. Keep in mind that I myself am not having this issue. I was however compelled to try to help you guys, my fellow user. My hope is that I have given you a second chance. If it does work please be more careful!!!
Ok guys so I've read a lot of posts that say some of you guys are experiencing the above problems, and have tried what seems like everything to fix your baby. I've read the "flash color os" fix which seems to work for some but not all.
So I myself do not have this issue but a buddy of mine did so I was really wanted to not only help him fix his baby, but also anyone out here who is experiencing this issue.
Please note that if you have twrp installed you can skip down to "part 2" and simply run the command in terminal command via twrp
I am making a package for you to download which contains all files needed to make this happen.
Please note the methods here are not for fixing issues resulting from flashing various zips associated with any lollipop Roms or mods, nor is this thread a support thread for such problems
So inside it you will have a few files:
persist.img
reserve4.img (update: this file is not needed so ignore it!)
cm-11.0-XNPH30O-bacon-signed-fastboot_64GB.zip
adb-setup- 1.3.exe
please note that any commands run in fastboot mode require you to have an unlocked boot loader. If you are not sure if you are unlocked then that means you aren't! So to do so put the device in fastboot mode and type: "fastboot oem unlock"
Update: you don't need to worry about the reserve4.img or the 30O zip. if you have no O.S. then you can flash the 30O but we now know all that is needed is to flash the persist.img
INSTRUCTIONS:
EXTRACT ZIP
IF YOU HAVEN'T INSTALLED ADB/FASTBOOT DRIVERS RUN THE adb-setup- 1.3.exe FILE TO INSTALL ADB SYSTEM WIDE
IF YOU ALREADY HAVE ADB INSTALLED SKIP THAT STEP
OPEN A CMD WINDOW WHEREVER YOU HAVE THESE FILES EXTRACTED
TYPE THE FOLLOWING COMMANDS IN YOUR CMD WINDOW WITH DEVICE IN FASTBOOT MODE:
fastboot erase persist
fastboot flash persist persist.img
now reboot and check if all is working. If you have no O.S. installed then you will need to flash something to get back up in running: see below
Note that this will wipe your device 100% so if anything is on your phone back it up to your PC!
This next part (in green text) is only if you have no os installed and not necessary for most people:
[*]WE ARE NOW GOING TO FLASH 30O AND THEN ALL SHOULD BE FORGIVEN
[*]SO EXTRACT THE cm-11.0-XNPH30O-bacon-signed-fastboot_64GB.zip
[*]RUN THE flash-all.bat FILE FROM FASTBOOT AND YOU SHOULD BE CURED!!!
[*] Please note that some users may get an error from running the flash-all.bat/.sh
If so simply extract the .zip and flash all manually and you will get the desired result.
Part 2
If for some reason you have relocked your bootloader and still have twrp ( you'll know if its locked if you flash these images and it says "failed, device not unlocked"
So in this case reboot to twrp and run a terminal command with the following exactly as written
make_ext4fs /dev/block/mmcblk0p15
Then reboot and you should be all set!
Below are two different files for you to use. the first one contains the persist.img . I am uploading it seperate for those of you who already have a copy of 30O. I see no need in making you wait longer to dl this if you already have 30O.
I am uploading the full package which contains everything for those who need it all
If you found this helpful all I ask is you hit the thanks button!
Downloads ↓
NEVER SETTLE!
Full Package
If you are unable to use fastboot for whatever reason check this post for a flashable zip via custom recovery http://forum.xda-developers.com/showthread.php?p=55981898
Big shout out to my buddy AddisG for testing and confirming this works! We've been working on this for a long time and it's finally paid off
Also thanks to @Vonnegut for helping me maintain this thread and providing valuable information
Now once you are up and running again it's a good idea to not only backup your efs, but also copy that backup to your pc/cloud.
To do so is very easy. You'll need the app "terminal emulator" or alternatively you can do this on your Linux box too!
Issue the following commands to back them up:
open terminal
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
That will create two efs backups on your sd card. Make sure you copy them somewhere. DO NOT FORGET!!!
Now to restore your efs simply enter fastboot mode and flash the two efs files you backed up.
the commands are:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
If you've tried all of the above and still have no baseband you can try this:
fastboot erase modemst1
fastboot erase modemst2
Please report if this works for you!!!
I sure hope it does!!!
Thanks bro Mark for all the time you spent helping me on this!!
PEOPLE PLEASE SMASH HIS THANKS BUTTON!!!
Are the persist and reserve partitions not unique to devices?
dmo580 said:
Are the persist and reserve partitions not unique to devices?
Click to expand...
Click to collapse
No, If you're having those nasty AudioFX FC when you turn on your phone use those two files or If not then follow the other instructions. I was going through the same but this fixed my problem.
AddisG said:
No, If you're having those nasty AudioFX FC when you turn on your phone use those two files or If not then follow the other instructions. I was going through the same but this fixed my problem.
Click to expand...
Click to collapse
Flashing 33R (not 30O) factory image did not fix my issues earlier. Sure I can try the 30O suggested here, but not too sure it'll do anything. But you're saying the persist and reserve files are not related to corrupt EFS/IMEI?
dmo580 said:
Flashing 33R (not 30O) factory image did not fix my issues earlier. Sure I can try the 30O suggested here, but not too sure it'll do anything. But you're saying the persist and reserve files are not related to corrupt EFS/IMEI?
Click to expand...
Click to collapse
I can tell you exactly what i had done.. i was having AudioFX FC because of that i couldn't do anything on my phone.. so i flashed the persist and reserve files in fastboot.. that got rid of my AudioFX issues and fixed the WIFI issue also.. i was on R33.. no luck with data or network.. and had no IMEI.. so i flashed 30O then i got Data/Network back. Try Persist and reserve first.. on R33, if they don't work then flash 30O and see if it does it.
P.S once you get data and everything else working you can update to the latest version of CM11 (which i already done)
dmo580 said:
Flashing 33R (not 30O) factory image did not fix my issues earlier. Sure I can try the 30O suggested here, but not too sure it'll do anything. But you're saying the persist and reserve files are not related to corrupt EFS/IMEI?
Click to expand...
Click to collapse
Just try it and let us know if it works for you.
markbencze said:
Just try it and let us know if it works for you.
Click to expand...
Click to collapse
I followed your steps and no go. no cellular. Oddly Bluetooth works now. No Wifi, No cell.
dmo580 said:
I followed your steps and no go. no cellular. Oddly Bluetooth works now. No Wifi, No cell.
Click to expand...
Click to collapse
Is your SIM inserted? And are you on 30O?
dmo580 said:
I followed your steps and no go. no cellular. Oddly Bluetooth works now. No Wifi, No cell.
Click to expand...
Click to collapse
Try again.
Did you flash 30O also?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
markbencze said:
Try again.
Did you flash 30O also?
Click to expand...
Click to collapse
I flashed 33R like 2 days ago. Today I flashed 30O per your instructions. Got the 64GB version from this thread.
Yes SIM inserted.
Ok.. try this.. If you have ColorOS Rom try flashing that in recovery then flash 30O afterwards (must factory reset first).
dmo580 said:
I flashed 33R like 2 days ago. Today I flashed 30O per your instructions. Got the 64GB version from this thread.
Click to expand...
Click to collapse
I made no mention of 33R
Tell me step by step what you just tried. Being vague helps no one
markbencze said:
I made no mention of 33R
Tell me step by step what you just tried. Being vague helps no one
Click to expand...
Click to collapse
I flashed 33R as a part of my own debugging 2 days ago to try to recover the IMEI/EFS using the factory image. It is not part of what I tried today.
This morning I found that Nandroid restoring my CM11 Nightly backup made with TWRP 2.8.0.1 would give me WiFi and BT on boot.
Upon rebooting though no connectivity again. Cellular was never available, and IMEI was always unknown
I stumbled upon this thread, followed the steps in the OP regarding wiping and flashing both persist and reserve4 partitions
I then proceeded to use the flash-all.bat script for 30O
Booted up, and nothing connects. No WiFi, no BT, no cellular.
Upon rebooting (for the hell of it) it seems Bluetooth works now. Nothing more though. Further reboots show BT sticks.
Upon further inspection BT may not work. Somehow it shows as in the Settings menu and the toggle is switched on but it cannot see my Nexus 5. Further toggling off and on fails to turn BT back on. I suspect its a bug or something.
Edit: Forget the BT. No MAC address in Settings > Status. I bet the toggle is just faulty and switches on even if BT radio is messed up.
I have the AudioFix no SD issue. Going to try this when I get home. Will report.
joshyy_rey said:
I have the AudioFix no SD issue. Going to try this when I get home. Will report.
Click to expand...
Click to collapse
I can assure you that this will fix those issues.. for the AudioFX problem grab the two files from the OP "persist.img" and "reserve4.img" flash them in fastboot using the following commands:
fastboot erase persist
fastboot flash persist persist.img
fastboot erase reserve4
fastboot flash reserve4 reserve4.img
Hope this helps.
AddisG said:
I can assure you that this will fix those issues.. for the AudioFX problem grab the two files from the OP "persist.img" and "reserve4.img" flash them in fastboot using the following commands:
fastboot erase persist
fastboot flash persist persist.img
fastboot erase reserve4
fastboot flash reserve4 reserve4.img
Hope this helps.
Click to expand...
Click to collapse
WHOA IT WORKED....omg....thank you.
only have 12GB now of available storage... I need to see what went wrong... i only flashed the fix files
joshyy_rey said:
only have 12GB now of available storage... I need to see what went wrong... i only flashed the fix files
Click to expand...
Click to collapse
flash userdata 64GB img. find it via google or xda.
joshyy_rey said:
only have 12GB now of available storage... I need to see what went wrong... i only flashed the fix files
Click to expand...
Click to collapse
I have linked the 64 g factory image in the op. Try that
Related
Hey there. I hate to bother everyone, i really do, but after searching countless forums, and trying infinite solutions, i'm at a loss of what to do. I want to flash to stock rom, I'm on paranoid android at the moment. Now normally this wouldn't be an issue- but somehow, someway, my bootloader is locked, and i cannot get it to unlock again at all. i've tried doing it with the OPO tool, tried through cmd, nothing. all that happens upon running fastboot oem unlock is my device boots into recovery (philz). i have no idea what to do, but it's really bumming me out. My model is the 64gb one.
also as a side problem, i originally tried flashing THIS ROM, and ever since then my fastboot is in the chinese version. I couldn't flash to stock before hand because it kept telling me my fastboot was outdated. how can i fix this as well?
i really, really, REALLY appreciate any help i can get. i always surf for hours on forums trying to resolve the problem myself before making a new thread, but i have no other options now.
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Try reading through this thread, it may help (read all of it before you attempt anything)
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
sahil04 said:
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Click to expand...
Click to collapse
my sincerest apologies. i haven't actually used XDA in a while. give me a little bit though, upon trying again, apparently my abd isn't working right and isn't recognized as an internal command.
update: those threads always result in telling me to do this which is what i'm trying to do right now, though i've tried before and still tend to get a straight boot into recovery.
Sounds like you are not in the correct directory to run adb.
Try this:
cd (location of adb.exe)
example:
cd C:\android\platform-tools\
Then try to run this command with your device plugged in:
adb.exe devices
sahil04 said:
Sounds like you are not in the correct directory to run adb.
Try this:
cd (location of adb.exe)
example:
cd C:\android\platform-tools\
Then try to run this command with your device plugged in:
adb.exe devices
Click to expand...
Click to collapse
i'm in the right directory. i'm following this guide and i'm at the part where it tells me to type "fastboot oem unlock" it then tells me to do a fastboot reboot after that script finishes running which is where the problem comes in. the phone reboots into recovery IMMEDIATELY after inputting the oem unlock command, not giving me the chance to do anything else.
dokibot said:
i'm in the right directory. i'm following this guide and i'm at the part where it tells me to type "fastboot oem unlock" it then tells me to do a fastboot reboot after that script finishes running which is where the problem comes in. the phone reboots into recovery IMMEDIATELY after inputting the oem unlock command, not giving me the chance to do anything else.
Click to expand...
Click to collapse
try sideloading... Adb sideload "name of rom".zip
Sent from my A0001 using XDA Premium 4 mobile app
sahil04 said:
You did mess up pretty bad (by posting in the wrong section).
Does the command prompt give you any error when you try to unlock the bootloader?
Try reading through this thread, it may help (read all of it before you attempt anything)
http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
Click to expand...
Click to collapse
this is what the cmd shows when i run oem unlock. then the phone just boots into recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setting.Out said:
try sideloading... Adb sideload "name of rom".zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i've never side loaded before? i can't find anything specific for the opo
edit: all i can find is how to flash roms with it, when i really wanna get my bootloader unlocked
dokibot said:
i've never side loaded before? i can't find anything specific for the opo
edit: all i can find is how to flash roms with it, when i really wanna get my bootloader unlocked
Click to expand...
Click to collapse
Try the following links:
Link1
Link2
KDurantula said:
Try the following links:
Link1
Link2
Click to expand...
Click to collapse
surely there's something other than using a ubuntu virtual box? i don't have a lot of disk space right now, and i'd much rather have some other solution. anything else.
dokibot said:
surely there's something other than using a ubuntu virtual box? i don't have a lot of disk space right now, and i'd much rather have some other solution. anything else.
Click to expand...
Click to collapse
I was kind of in the same situation as you, nothing else would work for me lol. If all else fails, give it a shot!
Go back to stock and start over, please see this guide to go back to stock:
Download the official CM11S from cyanogen website http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip and follow this guide:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, everything will be lost! This is really a factory reset.
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the link above
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
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
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip (file used to extract the files above)
This will make you device go back to stock, check if it works now.
Hope this helps.
i can't flash anything. my bootloader isn't unlocked. this is my problem.
dokibot said:
i can't flash anything. my bootloader isn't unlocked. this is my problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If you do, your bootloader is unlocked.
Just sideload a XNPH38R.zip, Calkulin's one, or the official. Then try to use fastboot once more.
My guess is that this fixes your problem and that fastboot will work again.
P.S. Even if you haven't been on XDA for a while how in God's name would you post in "Original Android Development"...?
TiVON said:
Do you have a custom recovery? If you do, your bootloader is unlocked.
Just sideload a XNPH38R.zip, Calkulin's one, or the official. Then try to use fastboot once more.
My guess is that this fixes your problem and that fastboot will work again.
P.S. Even if you haven't been on XDA for a while how in God's name would you post in "Original Android Development"...?
Click to expand...
Click to collapse
**** i didn't even realize i was in original. my bad wow. Yeah i have philz right now. do i need to wipe everything to do this. i'm scared of wiping because if i do, since i can't flash anything, i'll be stuck without a rom at all. i'm downloading the official zip, and i'm about to try sideloading it.
edit: sideload failed. might be because i didn't wipe. error in /tmp/update.zip (status 7). it suggested i do a factory reset, tried that, still same error.
dokibot said:
**** i didn't even realize i was in original. my bad wow. Yeah i have philz right now. do i need to wipe everything to do this. i'm scared of wiping because if i do, since i can't flash anything, i'll be stuck without a rom at all. i'm downloading the official zip, and i'm about to try sideloading it.
edit: sideload failed. might be because i didn't wipe. error in /tmp/update.zip (status 7). it suggested i do a factory reset, tried that, still same error.
Click to expand...
Click to collapse
Have you tried flashing the stock rom with the stock recovery through the custom recovery and then trying to re-unlock the bootloader?
sahil04 said:
Have you tried flashing the stock rom with the stock recovery through the custom recovery and then trying to re-unlock the bootloader?
Click to expand...
Click to collapse
i can't flash stock. it tells me the bootloader is locked, and stops the process.
hugoprh said:
Go back to stock and start over, please see this guide to go back to stock:
Download the official CM11S from cyanogen website http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip and follow this guide:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, everything will be lost! This is really a factory reset.
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the link above
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
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
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip (file used to extract the files above)
This will make you device go back to stock, check if it works now.
Hope this helps.
Click to expand...
Click to collapse
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
dokibot said:
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
Click to expand...
Click to collapse
Try this:
cd C:\Users\(username)\Desktop\SDK\platform-tools\
Also, did you extract the files out of the zip file?
dokibot said:
none of this works. cant even get it to open NON-HLOS.bin everytime i try it just gives me "error: cannot open "NON-HLOS.bin'" i have my path set to
cd desktop/sdk/platform-tools/(folder i named with all the zip files)
is that right?
Click to expand...
Click to collapse
Install this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
So you can get the adb and fastboot from anywhere on the command line, then open the command prompt and navigate to that folder and copy line by line from the above tutorial.
The last line will require the original ZIP file to be in the same folder has the extracted files.
Hope this helps.
SOLVED: Performing a Factory Reset solved the issue. System only takes about 8GB now.
I keep getting notifications that my storage is almost full even though I barely have any stored photos/videos/music. I went in and looked to discover that "System" is utilizing 109GB of storage for some reason.
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sn0warmy said:
I keep getting notifications that my storage is almost full even though I barely have any stored photos/videos/music. I went in and looked to discover that "System" is utilizing 109GB of storage for some reason.
Any ideas?
Click to expand...
Click to collapse
Should be around 5 to 10GB. Something went awry. Can you start all over, clean system?
bobby janow said:
Should be around 5 to 10GB. Something went awry. Can you start all over, clean system?
Click to expand...
Click to collapse
Yeah, I have been meaning to flash the NMF26Q OTA anyway so I can just flash the entire factory Image, instead.
Maybe my flashing method is the issue. I know it's different with the Pixel compared to previous Nexus devices and I've been trying to pinpoint the correct way. Here are the steps I took when flashing NMF26O. Does anything look incorrect?
Keep in mind my phone defaults to slot B when flashing.
fastboot flash bootloader bootloader-xxx-xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-xx-xx-xx.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash system_a system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot flash userdata userdata.img
fastboot reboot
Follow method 2 here and if your storage is still like that after, then boot into recovery and perform a factory reset - restart your phone and check your storage. It should be about 5gb after following these steps:
http://www.theandroidsoul.com/flash-firmware-factory-image-google-pixel/
iainaaldrich said:
Follow method 2 here and if your storage is still like that after, then boot into recovery and perform a factory reset - restart your phone and check your storage. It should be about 5gb after following these steps:
http://www.theandroidsoul.com/flash-firmware-factory-image-google-pixel/
Click to expand...
Click to collapse
Sounds good. The only thing that doesn't make sense is the factory images for the Pixel don't include the cache.img or recovery.img files. I just downloaded the NMF26Q factory image and extracted it. It's missing the cache.img and recovery.img files as well. Am I missing something here?
sn0warmy said:
Sounds good. The only thing that doesn't make sense is the factory images for the Pixel don't include the cache.img or recovery.img files. I just downloaded the NMF26Q factory image and extracted it. It's missing the cache.img and recovery.img files as well. Am I missing something here?
Click to expand...
Click to collapse
Skip these two, don't worry about putting these in. You'll be fine without them.
iainaaldrich said:
Skip these two, don't worry about putting these in. You'll be fine without them.
Click to expand...
Click to collapse
I did a fresh install of NMF26Q and the issue remained. So I went into Settings and performance a "Factory Reset". Afterwards "System" now takes up just 8GB, as it should. So it looks like the Factory Reset was the solution after all.
Thanks for the help!
sn0warmy said:
I did a fresh install of NMF26Q and the issue remained. So I went into Settings and performance a "Factory Reset". Afterwards "System" now takes up just 8GB, as it should. So it looks like the Factory Reset was the solution after all.
Thanks for the help!
Click to expand...
Click to collapse
So you did need that full reset and wipe it seems. Weird about not having recovery.img in the image download though. What if you change your recovery and want to go back to stock? We need the definitive @Heisenberg thread here. Well not for me actually, I'm bootloader locked for the duration of the Pixel experience. (Verizon model) But so many are having issues flashing factory images here and in the XL forums.
Glad you got it working. Factory reset is our friend.
bobby janow said:
So you did need that full reset and wipe it seems. Weird about not having recovery.img in the image download though. What if you change your recovery and want to go back to stock? We need the definitive @Heisenberg thread here. Well not for me actually, I'm bootloader locked for the duration of the Pixel experience. (Verizon model) But so many are having issues flashing factory images here and in the XL forums.
Glad you got it working. Factory reset is our friend.
Click to expand...
Click to collapse
I'm fairly certain that if I simply performed a Factory Reset, without flashing he new factory images, it would have solved the problem. I wish I would have tried that first, to confirm. But in the end that was the solution. So I don't see why it wouldn't have worked without flashing the new factory images.
I've now installed 2 different factory images on my Pixel since I received it and each factory image I've downloaded is missing the cache.img and the recovery.img files. I never experienced this with my previous Nexus devices. Download and extract one of the Pixel factory images and see if you get the same result. From what I understand, the boot.img file for the Pixel contains the stock recovery. But I'm not sure about the cache.img file.
I think the reason why so many are having issues flashing factory images on the pixel devices is due to the flashing method being slightly changed as well as now having a "Slot A" and "Slot B". Some Pixel and Pixel XL's default to "Slot A" while others (like mine) default to "Slot B".
Depending on which one your Pixel/Pixel XL defaults to determines which partition you have to flash "system_other.img" to. For instance, since my Pixel defaults to "Slot B" I need to specify by doing the following:
fastboot flash system system.img
fastboot flash system_a system_other.img
For those whose phones default to Slot A, they need to do the following:
fastboot flash system system.img
fastboot flash system_b system_other.img
With my phone defaulting to Slot B, when I do the following, my phone goes into a bootloop:
fastboot flash system system.img
fastboot flash system_b system_other.img
sn0warmy said:
I'm fairly certain that if I simply performed a Factory Reset, without flashing he new factory images, it would have solved the problem. I wish I would have tried that first, to confirm. But in the end that was the solution. So I don't see why it wouldn't have worked without flashing the new factory images.
Click to expand...
Click to collapse
Wow you said a mouthful. If there is no recovery.img or cache.img in the image file then I suppose you're right that it's contained somewhere else. Which is why we really need a definitive post with different scenarios along with the different slot explanations. It's kind of all over the map now with different instructions on various posts as we can see from some above links. I'm going to root around Chainfire's threads to see if there is a full dissertation on the new slots and flashing root. As you said, this is way, way different from my past 2 Nexus devices, the 5 and the 5x. That was child's play compared to this.
bobby janow said:
Wow you said a mouthful. If there is no recovery.img or cache.img in the image file then I suppose you're right that it's contained somewhere else. Which is why we really need a definitive post with different scenarios along with the different slot explanations. It's kind of all over the map now with different instructions on various posts as we can see from some above links. I'm going to root around Chainfire's threads to see if there is a full dissertation on the new slots and flashing root. As you said, this is way, way different from my past 2 Nexus devices, the 5 and the 5x. That was child's play compared to this.
Click to expand...
Click to collapse
Recovery is contained within the boot.img. I've read someone saying something along the lines that cache doesn't exist (or work?) like it did in past phones. That's why they're not in the image file. Nothing's wrong.
bobby janow said:
...As you said, this is way, way different from my past 2 Nexus devices, the 5 and the 5x. That was child's play compared to this.
Click to expand...
Click to collapse
Agreed. But now that I have the factory image flashing figured out it's really not that bad. You can see what Boot Slot your phone defaults to simply by booting into Bootloader. It tells you, plain as day. Then...
fastboot flash bootloader bootloader-xxx-xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-xx-xx-xx.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash system_? system_other.img (Replace "system_?" with "system_a" if your phone's Boot Slot is B and replace it with "system_b" if your phone's Boot Slot is A)
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot flash userdata userdata.img
After first boot up, go into settings and perform a factory reset
If you follow those exact steps your factory image flash will go flawlessly.
I believe the simplest way for inexperienced users to follow is this. Boot into boot locker, notice the slot you're in, flash-all that slot. Fastboot TWRP, switch slot, flash-all the 2nd slot. Done. From there, you can flash root or kernel to which ever slot you want. This straight forward method has never failed anyone I helped.
Edit: NVM.
sn0warmy said:
This is assuming everyone uses Windows, which is not the case. Sticking with manually flashing each image as outlined above is the most surefire way to get the job done on both Windows and OS X/Mac OS.
Click to expand...
Click to collapse
In 2016, 93% use Windows, 4.5% use Mac OS, 2% use Linux, 0.5% use something else. I have a pretty good odds. However, your justification is certainly appreciated by me.
quangtran1 said:
In 2016, 93% use Windows, 4.5% use Mac OS, 2% use Linux, 0.5% use something else. I have a pretty good odds. However, your justification is certainly appreciated by me.
Click to expand...
Click to collapse
Fair enough. And I was actually wrong. It turns out that the flash-all.bat works with Windows while flash-all.sh accomplishes the same thing on OSX. So your method would work either way. I've personally never tried using the flash-all scripts.
sn0warmy said:
Fair enough. And I was actually wrong. It turns out that the flash-all.bat works with Windows while flash-all.sh accomplishes the same thing on OSX. So your method would work either way. I've personally never tried using the flash-all scripts.
Click to expand...
Click to collapse
I didn't doubt you one bit. I knew you were accurate. I normally don't deal with phones from my MBP, but I did look at the .sh file. The commands are identical to the .bat Windows counterpart.
Also, I really dislike helping people by spoon-feeding these instructions. They need to know when to adb, when to fastboot, what to do with zip, what to do with img, what sequence to flash, what would break what. Take this flash-all script, dissect it, know what each command does. When we don't understand, and just blindly attempt every suggestion given here, we end up more confused and frustrated.
quangtran1 said:
I didn't doubt you one bit. I knew you were accurate. I normally don't deal with phones from my MBP, but I did look at the .sh file. The commands are identical to the .bat Windows counterpart.
Also, I really dislike helping people by spoon-feeding these instructions. They need to know when to adb, when to fastboot, what to do with zip, what to do with img, what sequence to flash, what would break what. Take this flash-all script, dissect it, know what each command does. When we don't understand, and just blindly attempt every suggestion given here, we end up more confused and frustrated.
Click to expand...
Click to collapse
I'm not sure what you mean by spoon-feeding. You have no idea how often I went to the Heisenberg thread to step by step flashing images. I consider that prudent and responsible. I think these instructions should be verified, catalogued, and stickied. That's really the only way to teach people how to do it correctly. I for one appreciate it.
Sent from my Google Pixel using XDA Labs
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
nipun1110 said:
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
Click to expand...
Click to collapse
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Gr8man001 said:
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Click to expand...
Click to collapse
Hello, thanks a lot for your prompt response. But it is showing this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nipun1110 said:
Hello, thanks a lot for your prompt response. But it is showing this error.
Click to expand...
Click to collapse
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
maigre said:
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
Click to expand...
Click to collapse
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
That wasn't me. It was Gr8man001 that gave you the advice that worked.
nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
maigre said:
That wasn't me. It was Gr8man001 that gave you the advice that worked.
Click to expand...
Click to collapse
true command : '''' fastboot --set-active=a '''' is it?
For me not work... please help.
https://i.hizliresim.com/pbOkpJ.png
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
zulu657 said:
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
szybki_ben said:
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
Click to expand...
Click to collapse
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
zulu657 said:
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
Click to expand...
Click to collapse
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
szybki_ben said:
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
Click to expand...
Click to collapse
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
zulu657 said:
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
Click to expand...
Click to collapse
If you can boot into recovery then booting a fresh img is a good idea, good luck!
szybki_ben said:
If you can boot into recovery then booting a fresh img is a good idea, good luck!
Click to expand...
Click to collapse
Just tried that one -- No Cigar!!! I followed the instructions for installing recovery on a new install. It said to use the text: fastboot boot recoveryimgrecovery.img I had renamed the Blu-spark img to recovery.img. The result was: no file or directory with this name. I was in the folder with adb, fastboot, recovery.img and all the rest of the files for OP6.
There used to be a way to install twrp with adb if I recall, but I can't find it. I know it was for an earlier phone. I have had OnePlus phones from the first one.
Very frustrating!!! I hate to wipe the phone because this should be a simple thing. Of course those are the ones that really get you....
Hmmmm, evidently the command fastboot set active=a is not a command in adb v1.0.32. When I tried it, I got a list of the commands and that one isn't in it.
Trying to find a later version of adb without success.
There has to be a way to change the active partition without formatting the phone. The phone had the original OS and I upgraded to Experience when I got it and have been using it ever since. Experience should be on another partition, so if I can change partitions, I should be on the original OS.
Would that not be correct???
Dear community,
I have a doogee S96 pro, I'm from Italy, and I installed TWRP from the unofficaltwrp guide.
Now I'm no more able to boot, the phones goes directly to the recovery.
Probably magisk was no able to patch the system and to disable the tm verity (avb). I have a super partition, and from what I saw the fstab is inside the vendor partition inside super.
Doogee does not provide stock roms, so I cannot restore the phone as factory settings, that's why I open this thread.
Is someone available to help me booting into Android or available to give me the stock boot/recovery img? It's a fast and safe procedure, I can give more details on how to do.
Thank you!
Dear @giubenez I had a similar problem. But after I got in touch with doogee support they sent me the firmware. I want to share it with you and with any other person that wants to ROOT THE DOOGEE S96 PRO
The following link is the firmware and upgrade tool. Please open and download.
Please note that if your computer system is French you need to change the name of the downloaded file.
Spoiler: Link
ZN129（S96）
Folder
1drv.ms
When upgrading the firmware, please do not select the 'Format All+Download' option
When flashing the phone, please set up the software first, turn off the phone, and then connect the phone to the computer.
Best wishes
Wow! thank you!!!
You saved... us!
Why doogee does not respond to me? why they not post the firmware on the forum? WTF
@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
Google introduced vbmeta which is also a verity check. An option to bypass this check is to flash an empty vbmeta.img before attempting to flash TWRP recovery.
Click to expand...
Click to collapse
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"
Ankiseth said:
@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"
Click to expand...
Click to collapse
GOD BLESS YOU, Ankiseth!
YOU SAVE MY PHONE! SPFLASH AND EVERYTHING WORKS!
Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
Good day, I would like to ask you to help us. Please use the following link: https://1drv.ms/u/s!AvX9KABcpSV1kTOgCMsUkLyXY-we?e=nMchxl Download the previous version of the S96pro firmware and follow the tutorial to return the phone to OTA The previous version (ver3.02) was upgraded. The tutorial has been included in the firmware compression package. Please test the night vision camera after flashing the camera and let me know if it can be used normally. Thank you very much.
Click to expand...
Click to collapse
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth :
Please note that if your computer system is French you need to change the name of the downloaded file.
Click to expand...
Click to collapse
which file ?
berzerking said:
Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
There Is Hope Brother... I Just Downloaded The Files And Used The SCATTER-LOADING FILE From 3.02 on SP-FlashTools 5.2 Switched It To Download Only And Hit Download .. Plugged In My Phone To USB While OFF And aftyer the loading was complete .. Phone Reboot As If NEW. ( HARD RESET) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!! Now i Just Have To ReLoad All Apps And Accounts .. And Wait For The oukitel WP7 i ordered out of frustration. Will Be Doing A Review Comparison On Both Cameras !!!!! You Can Follow Me Here If Interested https://www.youtube.com/channel/UCYOpd4yooYgKS-0xe63jnCw
Hi all. Thanks for the information. I was in touch with doogee and they say to me that there is an update during this WE (S9S88A7.DGE.DOOGEE.EEA.HB.HJAYYDVFAZ.0128.V3.03820210313-2312.
Nothing change IR camera don't work
I will flash my S96pro during the week with S9S88A7.DGE.DOOGEE.EEA.HB.HJ.AYYDVFAZ.1130.V3.02.zip and I'll post here what happened
HouseOwl said:
) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!!
Click to expand...
Click to collapse
Yes !!!!! it s alive !!!!
Thank you dude ! my ir works again !!!!!
btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you
berzerking said:
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
Can you write a tutorial? Have you used SP flash tool?
Thank you!
giubenez said:
btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you
Click to expand...
Click to collapse
I solved in this way:
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(with the empty vbmeta
>fastboot.exe flash recovery recovery.img
(with the stock recovery)
>fastboot reboot
after that the update attempted to start and failed, the phone then boot to android.
The updates always failes after that, so I disabled them.
this is why the update fails..is it because I used the the Russian super img?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#edit: it was because I flashed the wrong recovery. With the correct one, i still have issues with the update: md5 chechsum controll is not passed and the update aborts.
I don't care, I prefer a rooted phone without the updates.
your device has not passed the test and may not work properly - Here is a message on the screen . Constantly overloaded is not included in the recovery. The firmware doesn't help.
Could someone repost the S96Pro stock firmware... I can't find it anywhere online, thanks in advance
I'm uploading them.
https://bit.ly/3en9EZY
Thanks giubenez ,u saved me but now I have the watermark from formatting Google Key State : Fail, I don't see a factory mode file to freeze, tried ADB and couldn't find the build prop values, has anyone else ran into this with a fix?
I can't get what problem are you facing. I unlocked and rooted my s96 pro.
If you describe your issue i can help you solving it.
However, i found very risky to root the phone, if you plan to do the ota updates avoid TWRP since it'll make you bootloop at the moment you try to install the update.
The only way to solve it is to flash the stock recovery through adb.
So.. yeah.
I have recently procured this device and want to install twrp, and stock and/or test a gsi and in what capacity the phone works with one of those.
Enabled both developer mode & the usb debug mode and adb devices lists the device.
N.B; the supplied s96pro cable does not seem to carry data, "presumably" because doogee is cheapskates on cables, as well in the support department. I had to use my sony headphone cable. Go figure, its consequential at least, so there's that.
In any case, read this thread and have downloaded all files, including the apparently new stock rom that is listed since yesterday in the evidently wholesome user Ankiseth's link above.
Questions:
In the 4pda link there are some instructions, specifically the adb command with the boot.img, however.. the links seems to be dead. What to do?
A) Can I first do the vbmeta command and then use our lord and savior Ankiseth's twrp recovery file and follow a generic "Case II: Devices with A/B partition scheme" mentioned in this xda twrp guide?
B) Hope that some other wholesome user share the boot.img file?
(Or, can I use the one in the zip file 'S9S88A7.DGE.DOOGEE.HB.HJ.AYYDVFAZ.1203.V3.04' ?)
-
After twrp is accessible can I use twrp/adb and install either the mentioned shared rom and any gsi for that matter?
I use linux and sure there is spflash, but the adb & twrp combo "subjectively feels" as a more stable way of doing things.
Update 2. Got both twrp and magisk going. Now to figure out if I can install a gsi.
Update, got spflashtool working and used the latest stock rom mentioned in my previous post.
However.
I patched the boot.img from said stock rom in magisk and also flashed twrp-recovery with fastboot.
No luck. Magisk seems not to be installed and the usual twrp gui does not show, seems to be the stock recovery. Got a orange state though.
[SOLVED] Please read through, hopefully this helps someone!
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
I think you have the wrong drivers, try these and check in windows update if your Qualcomm drivers are up to date in the optional updates. Also if fastboot is working and the bootloader is unlocked, you can download the latest full oos 12 and flash it all.
LaviLev said:
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
Click to expand...
Click to collapse
If you need the latest oos I can link it here.
Nimiskiv said:
If you need the latest oos I can link it here.
Click to expand...
Click to collapse
Please do! currently DLing the drivers posted Thank you!
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
LaviLev said:
Please do! currently DLing the drivers posted Thank you!
Click to expand...
Click to collapse
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Nimiskiv said:
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Click to expand...
Click to collapse
Anything with "kebab" in the beginning is OOS 12
Nimiskiv said:
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Click to expand...
Click to collapse
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
LaviLev said:
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
Click to expand...
Click to collapse
Use the MSM tool first
Nimiskiv said:
Use the MSM tool first
Click to expand...
Click to collapse
can not get phone to edl stuck in fastboot only. tried all the commands and physical button configs and still only get fastboot. Any workarounds?
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LaviLev said:
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
View attachment 5683905
Click to expand...
Click to collapse
That's a stock OOS recovery you're seeing.
BillGoss said:
That's a stock OOS recovery you're seeing.
Click to expand...
Click to collapse
Any advice or known methods to get me running from here?
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Run the MSM tool in edl, since now it should work fine. Also did the drivers work? If not you need to uninstall them in windows device manager, then reinstall them
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
BillGoss said:
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
Click to expand...
Click to collapse
I just reread my initial post, damn I started typing mid thought.. my bad!
I tried msmtool, but it doesn't load up a com port. All the listed methods with holding both vol buttons after already hitting start then plugging in did not work as I don't think it sees it at all.
Haven't found a thread with fastboot instructions that didn't require something I couldn't get to, to restore the phone. other methods fail writing to numerous areas when flashing.
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
LaviLev said:
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
LaviLev said:
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
Click to expand...
Click to collapse
check if EDL is working now, its very important for edl to work, because if something happens in the future, you need edl to reset.