I can't work out what's going on.
My phone lost it's root a few days ago - I only noticed when Magisk said it had a new one. So here's the lowdown:
My TWRP is out of date.
Magisk is out of date.
I've downloaded both the magisk.zip file and an img file of the latest TWRP.
I put them on the deskop, in the adb folder (in C drive) and on the phone under "downloads".
Boot into recovery, but when I navigate to install a zip file, it can only see the system files, no "downloads" folder or pictures or anything. I can't seem to change that.
Use Powershell to try and sideload the TWRP zip and it says "waiting for device" - that seems good. However, when i then boot into fastboot mode, Powershell tells me "error: cannotload twrp... .img"
So I try and look at Magisk, but I can only download the zip (of which I've done and can't flash it via recovery), or patch boot file, of which I can't navigate to as I'm currently not rooted so it can't find the boot file anyway.
What do I type into Powershell to flash the latest Magisk (I guess I can then update TWRP after using the in-
built updater?)?
When in TWRP, I click on the three lines on the right, which say:
Could not muont /data and unable to find crypto footer.
Failed to mount '/data' (no such process)
Unable to recreate /data/media folder,.
Updating partition details
Failed to mount '/data' (no such process)
... done
Unable to mount storage
Failed to mount '/data' (no such process)
Full SELinux support is present
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (no such process)
Click to expand...
Click to collapse
What can be causing all of this?
Probably rip UFS chip, if
Code:
fastboot format userdata
won't help, then you should send your phone for repair
Hmm.
So the only fix is to format all the data?
What data gets deleted?
I don't really want to do that if I can help it but I guess it's the only way to fix it.
Strange how it's just done it by itself.
anotherxdauser said:
Hmm.
So the only fix is to format all the data?
What data gets deleted?
I don't really want to do that if I can help it but I guess it's the only way to fix it.
Strange how it's just done it by itself.
Click to expand...
Click to collapse
Is the system bootable? If yes, then you can make a backup, if not, then you can consider your data gone.
"format userdata" removes everything you have stored on the phone
Yeah, I can boot to my Resurrection Remix rom and see everything, all my files, it's fine.
I can connect to a PC and move files to and fro the device.
It's just TWRP doesn't seem to see the storage. When looking, it just says 0Mb :S
Does Userdata mean the apps and stuff as well?
I saw a video of someone formatting the userdata to ex2, then back to ex4 but if it means I'd have to reinstall RR then it's a lot of work for something that may happen again in the near future.
I have Titanium Backup but of course, it needs root, of which I can't gain :/
Sounds a lot like a failed decrypt of an encrypted userdata partition, this is common in this phone with TWRP and custom ROMs.
Skickat från min ONEPLUS A3003 via Tapatalk
pitrus- said:
Sounds a lot like a failed decrypt of an encrypted userdata partition, this is common in this phone with TWRP and custom ROMs.
Click to expand...
Click to collapse
Is there non-destructive way to fix?
Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img
Which TWRP version do you have exactly?
Sent from my ONEPLUS A3003 using Tapatalk
przemcio510 said:
Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
Yeah, try this first. Problably you have a twrp lower than 3.2.0? I think below that it cannot decrypt Oreo encrypted Partitions.
Second thing is. Probably you have to format Data (not Userdata) anyway. I think you probably tried to upgrade Magisk because you lost root. But Magisk hat a bug in 17.0. That corrupted the permission Database. I had the same problem and was not able to get root again until formatted data. You will loose every app and its setting when formatting it. But everything under sdcard/ will still be there. So the download folder should be fine and everything. So when you make a titanium backup of your most valuable apps. You can restore them after renewing your phone.
TLDR:
1. Make Titanium Backup if you have it and want to have your apps back as before.
2. Try przemcio510 suggestion to get new TWRP. (most important)
3. backup your partitions and copy them to your pc
4. backup everything importantto you on your "SDCard" Volume (Where Download is and everything)
5. format DATA, Cache, Dalvik/ART Cache, System
4. Reflash Full OxygenOS 5.0.5
(optional) 5. Flash Rom of your flavor (with/without Gapps)
(optional) 6. Flash magisk
7. boot up your device
przemcio510 said:
Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
Did this. ADB said it was "waiting for device" so I rebooted to fastboot but then the ADB window shows some options (see quote below), nothing to show it's done anything.
I put the img file on the sim card on the phone and in the directory of the adb.
Code:
PS C:\WINDOWS\system32> fastboot twrp-3.2.3-0-oneplus3.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\WINDOWS\system32>
RASTAVIPER said:
Which TWRP version do you have exactly?
Click to expand...
Click to collapse
3.1.1-0
S4RGE said:
TLDR:
1. Make Titanium Backup if you have it and want to have your apps back as before.
2. Try przemcio510 suggestion to get new TWRP. (most important)
3. backup your partitions and copy them to your pc
4. backup everything importantto you on your "SDCard" Volume (Where Download is and everything)
5. format DATA, Cache, Dalvik/ART Cache, System
4. Reflash Full OxygenOS 5.0.5
(optional) 5. Flash Rom of your flavor (with/without Gapps)
(optional) 6. Flash magisk
7. boot up your device
Click to expand...
Click to collapse
My Titanium Backup needs root to work :/
It might have been when I upgraded RR Rom to the Oreo release, but it's only been the past week when I mysteriously lost root access.
anotherxdauser said:
Did this. ADB said it was "waiting for device" so I rebooted to fastboot but then the ADB window shows some options
Click to expand...
Click to collapse
To be clear, I think you mean fastboot whenever "ADB" is mentioned above. adb and fastboot are related, but 2 different things, with different usages and requirements. So it's best to refer to them in correct and distinct terms.
adb: Needs debugging enabled. Will work only in OS or custom recovery. Will not work in bootloader (even in fastboot mode) - maybe this is why you have "waiting for device"?
fastboot: Does not need debugging enabled. Only works in bootloader-fastboot mode.
fastboot is what you want for booting/flashing TWRP. Not adb (at least for the commands/methods suggested here).
anotherxdauser said:
PS C:\WINDOWS\system32> fastboot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
When command prompt shows you the list of command, this almost always means your command syntax is incorrect.
In your case, you used typed "fastboot" and a file name, without telling it what to do with that file name. The suggested command was "fastboot boot filename" (no quotes) or another usage option is "fastboot flash filename".
A little confusing I know, "fastboot" in itself is not a full command/action. I has to be "fastboot boot". Think of fastboot as a "thing" instead of an action. Thus, you still need to tell fastboot to perform an action ("boot").
anotherxdauser said:
...
3.1.1-0
My Titanium Backup needs root to work :/
It might have been when I upgraded RR Rom to the Oreo release, but it's only been the past week when I mysteriously lost root access.
Click to expand...
Click to collapse
Ah right I forgot.
As redpoint73 mentioned you have to be in fastboot mode.
When you start up your phone and the unlock Warning ist triggered. Push the volume up or down button and go to fastboot.
When you are in there the fastboot command should work.
As redpoint73 pointed out it is very important that you type "fastboot boot (ImagePath)".
To make it easier for you, you should copy the image where fastboot is.
Then you have only to enter
fastboot boot twrp-3.2.3-0-oneplus3.img
This should do the trick. If you still need help. Don't hesitate to ask.
redpoint73 said:
To be clear, I think you mean fastboot whenever "ADB" is mentioned above. adb and fastboot are related, but 2 different things, with different usages and requirements. So it's best to refer to them in correct and distinct terms.
In your case, you used typed "fastboot" and a file name, without telling it what to do with that file name. The suggested command was "fastboot boot filename" (no quotes) or another usage option is "fastboot flash filename".
Click to expand...
Click to collapse
Sorry my explanation isn't that great.
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
At any rate, tried "fastboot boot twrp-3.2.3-0-oneplus3.img" and the command prompt window shows "waiting for device". My device is on, at the homescreen, doing nothing. The command prompt window stays like that until I boot into fastboot mode, where it then just shows the large list of commands quoted above.
HOWEVER, a development!
When in fastboot mode and using the "fastboot boot twrp-3.2.3-0-oneplus3.img" command, the window now says "cannot load 'twrp-3.2.3-0-oneplus3.img': No such file or directory". So I tried typing the exact file path (C:\adb\twrp... img), which has now allowed me to boot into the updated TWRP.
Does this mean it's just booted into it, but not updated to it?
I'm able to see the contents of my sdcard now. So flashed the latest 17.1 magisk zip and... success! I'm now on the latest magisk and have been able to flash the latest TWRP to recovery.
Just to say, I really appreciate the help with this.
I know I could factory reset but it's helping me learn more.
anotherxdauser said:
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
Click to expand...
Click to collapse
You confuse some terms. adb and fastboot are programs, command prompt is the interpreter of the commands you give to these programs.
And yes, the fastboot is that mode.
anotherxdauser said:
At any rate, tried "fastboot boot twrp-3.2.3-0-oneplus3.img" and the command prompt window shows "waiting for device". My device is on, at the homescreen, doing nothing. The command prompt window stays like that until I boot into fastboot mode, where it then just shows the large list of commands quoted above.
Click to expand...
Click to collapse
Fastboot mode is meant to be used while phone is booted into fastboot mode
anotherxdauser said:
When in fastboot mode and using the "fastboot boot twrp-3.2.3-0-oneplus3.img" command, the window now says "cannot load 'twrp-3.2.3-0-oneplus3.img': No such file or directory". So I tried typing the exact file path (C:\adb\twrp... img), which has now allowed me to boot into the updated TWRP.
Click to expand...
Click to collapse
"no such file" means that you could have not copied the img file to the same folder as the adb binary (this is not the case when adb and fastboot binaries are installed with %PATH% variable added, then you can use these commands all over the filesystem).
anotherxdauser said:
Does this mean it's just booted into it, but not updated to it?
Click to expand...
Click to collapse
Fastboot boot command, which I have provided earlier is used to boot temporarily, one time an image you tell it to.
anotherxdauser said:
Just to say, I really appreciate the help with this.
Click to expand...
Click to collapse
Just kindly informing that there is a button on the lower-right hand corner for this
anotherxdauser said:
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
Click to expand...
Click to collapse
Both adb and fastboot are command prompt functions. They are both "bridge" tools used to communicate from computer to the phone.
The phone menu screen you are referring to is bootloader. Fastboot is one of the choices on that (bootloader) menu. It puts the phone in fastboot mode, which is specifically intended for fastboot commands (only mode fastboot command will work). The response will always be "waiting for device" if you try fastboot commands, and not in fastboot mode.
If the command is "fastboot . . . " you are issuing fastboot commands (not adb).
If the command is "adb . . . " you are issuing adb commands.
Again, they are both related, but different. Different requirements and usages for adb versus fastboot. It is important to understand the distinction, so you don't waste more time trying command in the wrong mode (which will never work).
Related
just a quick tool i put together that unlocks bootloader, flashes a recovery image, installs root, s-off and writes superCID!
simply install the exe file and run it off your desktop(sorry windows only)
FULL FEATURES:
Free Me (Unlock Bootloader, Flashes Recovery, Roots Device, S-OFF, Writes SuperCID)
Show oem token code
Flash oem token
Flash recoveries
Flash recovery themes
My GraffStyleZ TWRP Theme Included
S-Off
Enable root permissions
Force Update
Flash any .zip file
Flash a rom
Create a logcat
Show CID
Write superCID
Backup device
Restore device
Relock bootloader
Flash custom radio
Fix sdcard errors
Fix low batter error
Reboot options
Advanced wipe Options
Pulls Files From Server
Wipe Data
Wipe Cache
Wipe System
Wipe Dalvik Cache
Wipe Android Secure
Wipe Recovery
Wipe Boot img
Wipe Data,Cache
Wipe Data,Cache,System,Dalvik
Automatically Kills adb Upon Completion Of Task
Unlock bootloader guide
Install custom recovery guide
Install recovery theme guide
Enable root permissions guide
Install roms or .zip files guide
Restore device to defaults guide
Click to expand...
Click to collapse
Download Here
REMEMBER! IF YOU LIKE MY TOOL HIT THE THANKS BUTTON OR EVEN BUY ME A KANGAROO!
Ehm..... Just wanted to add a reminder, only use fastboot when it is the only way out. Fastboot can be dangerous, but nice made.
Also here is my testresults:
i did use the function : INSTALL A DOWNLOADED ROM
but:
fastboot erase data -- should be userdata
fastboot erase dalvik -- does not exsist, dalvik-cache is either /cache/dalvik-cache or if i remeber correctly some cm roms uses /data partition to handle dalvik-cache.
and last:
fastboot flash zip --- does not allow you to flash a rom, it complains about it is not allowed to do it, and as i remeber it is our bootloader that are locked on that part.
i tried also with a kernel.zip
sendng "zip" (4029 KB)...
OKAY [ 2.571s]
writing "zip"...
FAILED (remote: not allowed) <----i am s-off and rooted and so on
Finished....
so try do it like a openrecovery scripts using recovery
and last:
the fix low battery error, can you explain how that works
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
ehm
anders3408 said:
Ehm..... Just wanted to add a reminder, only use fastboot when it is the only way out. Fastboot can be dangerous, but nice made.
Also here is my testresults:
i did use the function : INSTALL A DOWNLOADED ROM
but:
fastboot erase data -- should be userdata
fastboot erase dalvik -- does not exsist, dalvik-cache is either /cache/dalvik-cache or if i remeber correctly some cm roms uses /data partition to handle dalvik-cache.
and last:
fastboot flash zip --- does not allow you to flash a rom, it complains about it is not allowed to do it, and as i remeber it is our bootloader that are locked on that part.
i tried also with a kernel.zip
sendng "zip" (4029 KB)...
OKAY [ 2.571s]
writing "zip"...
FAILED (remote: not allowed) <----i am s-off and rooted and so on
Finished....
so try do it like a openrecovery scripts using recovery
and last:
the fix low battery error, can you explain how that works
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
ehm
Click to expand...
Click to collapse
i have flashed .zip files on other phones like nexus and desire hd, it was successful, but i have not tried it on sxl as do not have the device anymore but seeing as developers gave so much to me from this forum, i thought id give a little back before i move on to learning ios development, try manual adb and executing adb root then flashing your kernel or zip
i havent tested roms yet though
as of the flashing kernel.zip, i do not know why it did not flash, maybe also try the adb root command before flashing?
and on some devices your phone will not charge it bootloader or recovery and when you want to revert back to stock os, no root, no custom recovery etc. some peoples devices fail to restore after the phone wipes system, data and cache partitions while there battery is below i think 18 percent, and fastboot wont allow you to boot into recovery until battery is above that amount.
why dont they turn their phone off abd let it charge? because when they connect the charger the phone boot into bootloader
i found a guide on google the other week as a request of adding the feature and those commands worked
this is a beta, thanks for the bug reports, will update it and fix the bugs later tonight
our bootloader does not support flashing zip files, that part is locked even if s-off
anders3408 said:
our bootloader does not support flashing zip files, that part is locked even if s-off
Click to expand...
Click to collapse
well thanks for your advice great help, need more people who give great accurate feedback like you will fix most of these errors in the update!
ricky310711 said:
well thanks for your advice great help, need more people who give great accurate feedback like you will fix most of these errors in the update!
Click to expand...
Click to collapse
You can try something like this example:
make a OpenRecoveryScript called flash_rom
adb shell mkdir /cache/recovery/openrecoveryscript
adb push flash_rom /cache/recovery/openrecoveryscript
adb reboot bootloader
fastboot boot twrp-recovery.img
i dont know how to get it to start the script, perhaps it is enough to push the script to correct folder and then boot recovery up.
The reason for fastboot boot ..... is for all can use it also if they uses cwm or a outdated recovery
More info :
http://www.teamw.in/OpenRecoveryScript
https://github.com/JBirdVegas/andro...installer/OpenRecoveryScriptSupport.java#L265
and here is what i also found, that is being done via an app called tasker from android, but i guess it should give us an idear on how it works
1) Use the Secure Settings plugin to run the command as root:
date=`date +%Y.%m.%d-%H.%M`;echo -e "wipe cache\nwipe dalvik\nbackup SDBO $date" > /cache/recovery/openrecoveryscript
2) then choose task > wait and set it for 5 seconds (giving time for things to settle
3) Use Secure Settings plugin as root again to run the command:
echo 'boot-recovery' > /dev/block/mmcblk0p3; sync; reboot <--------mmcblk..... should ofc be changed so it fits runnymede.
i think that is the only way you can flash a rom automaticly on runnymede, but what you can do is, push the rom to zip and when done reboot to recovery and i guess people knows how to press a few buttons
anders3408 said:
You can try something like this example:
make a OpenRecoveryScript called flash_rom
adb shell mkdir /cache/recovery/openrecoveryscript
adb push flash_rom /cache/recovery/openrecoveryscript
adb reboot bootloader
fastboot boot twrp-recovery.img
i dont know how to get it to start the script, perhaps it is enough to push the script to correct folder and then boot recovery up.
The reason for fastboot boot ..... is for all can use it also if they uses cwm or a outdated recovery
More info :
http://www.teamw.in/OpenRecoveryScript
https://github.com/JBirdVegas/andro...installer/OpenRecoveryScriptSupport.java#L265
and here is what i also found, that is being done via an app called tasker from android, but i guess it should give us an idear on how it works
1) Use the Secure Settings plugin to run the command as root:
date=`date +%Y.%m.%d-%H.%M`;echo -e "wipe cache\nwipe dalvik\nbackup SDBO $date" > /cache/recovery/openrecoveryscript
2) then choose task > wait and set it for 5 seconds (giving time for things to settle
3) Use Secure Settings plugin as root again to run the command:
echo 'boot-recovery' > /dev/block/mmcblk0p3; sync; reboot <--------mmcblk..... should ofc be changed so it fits runnymede.
i think that is the only way you can flash a rom automaticly on runnymede, but what you can do is, push the rom to zip and when done reboot to recovery and i guess people knows how to press a few buttons
Click to expand...
Click to collapse
i will look into that, as im sure you know i have only just started development, im still learning from people like, but am gonna give back as much as i have took
So this tool basicly roots the sxl for ya am I right going to give it a try today if it does
Sent from my GT-N7105 using xda premium
Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!
Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.
Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.
If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard
Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.
Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.
Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else
Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.
Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.
dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.
This thread is intended to get a fully working twrp for our new device sooner than later by more of us participating.
This is a testing thread so YES ANYTHING CAN GO WRONG. But most likely will not go wrong..
All test builds compiled by me are from @mauronofrio source code
https://github.com/mauronofrio/android_device_oneplus_guacamole_TWRP
This guide was copied and pasted from @mauronofrio Twrp thread.
Install guide:
Actually seems "fastboot boot twrp.img" is not working so we need to use another guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Now you should check which slot are you using with this command "fastboot getvar current-slot"
5. Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
6. Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
7. Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
8. First thing go in reboot menu and restore the old active slot
9. Now you can flash the installer (Actually you can do it using sideload, start sideload server from twrp advanced menu and from pc use this command "adb sideload twrpinstaller.zip")
If you are already rooted, you can skip all and directly flash the installer like a magisk module. Always remember that after you flashed the installer you will be unrooted.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/one...e-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
I need the following logs in order to find issues.
start a terminal window and enter below commands to get the logs
When TWRP boots enter below commands in terminal:
Code:
adb shell "getprop" > getprop.txt
adb pull /tmp/recovery.log
adb shell "dmesg" > dmesg.log
adb logcat > logcat.txt
and post the files here.
Links will be in post #2
Links to test builds
Test-0.2 f2fs filesystem
Twrp.img https://www.androidfilehost.com/?fid=1395089523397969888
Twrp installer https://www.androidfilehost.com/?fid=1395089523397969887
Test-0. 3 ext4 filesystem
Twrp.img https://www.androidfilehost.com/?fid=1395089523397969903
Installer https://www.androidfilehost.com/?fid=1395089523397969902
Under 6. Should we be using "fastboot flash recovery xxx.xxx" or the one from the post?
I might be able to test evening today.
Sent from my GM1911 using Tapatalk
vickyjusme said:
Under 6. Should we be using "fastboot flash recovery xxx.xxx" or the one from the post?
I might be able to test evening today.
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
fastboot flash boot twrp-test.img
Tried this method, but TWRP does not load. Stuck on this (image attached)
Reboot sticks to this screen again. Cannot access fastboot from here, but I can see my device from adb devices. Help me?
https://imgur.com/1s6dejl
Edit: start by power on+volume down loads fastboot.. Phew...
vukis said:
Tried this method, but TWRP does not load. Stuck on this (image attached)
Reboot sticks to this screen again. Cannot access fastboot from here, but I can see my device from adb devices. Help me?
https://imgur.com/1s6dejl
Edit: start by power on+volume down loads fastboot.. Phew...
Click to expand...
Click to collapse
Where are the logs. Please don't test and not provide logs. But thanks for informing test 0.3 doesn't work.
Just wondering how long you waited.
miflash error: not catch checkpoint (\$fastboot -s .*lock), flash not done -> HELP?!
Hello,
I unlocked my Mi8 and successfully installed Lineage on it.
After trying to install Magisk, my phone only boots into fastboot (and mi recovery, but that's not very helpful).
fastboot boot twrp.img results in error :
FAILED (remote: Failed to load/authenticate boot image: 00000050)
I tried MIFLASH by
1) downloading, dezipping and starting newest miflash (2020.3.14.0)
2) installing drivers
3) downloading and dezipping MIUI-fastboot-ROM
4) entering path* into miflash, refresh and flash (already tried all options "clean all" to "clean all and lock")
*) path to the folder that includes among others flash_all.bat
all this results in error:
not catch checkpoint (\$fastboot -s .*lock), flash not done
Nothing changed with the phone, still the same error.
While wanting to review the logs, I clicked in miflash on log/flash log. The log did not say anything helpful, but the error code of fastboot boot twrp.img changed to command write failed (Unknown error). Nothing else changed.
UPDATE: changed back to previous error (remote: Failed to load/authenticate boot image: 00000050)
If you have any idea or need any more information, please tell me!
I need that phone and cannot afford to terminally brink it!!
I did not find much online, did no one else had this problem??
THANK YOU!
PS: Using lenovo-laptop with quite vanilla win10 (and not so vanilla kubuntu dualboot, but miflash only supports windows)
MIFLASH-log says:
Code:
[14:37:14]:lsusb path:"C:\Users\<>\Downloads\MiFlash20200314\MiFlash20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:GetScriptDevices
[14:37:15]:FlashingDevice.flashDeviceList.Remove ab6ee6a0
[14:37:15]:add device ab6ee6a0 index 1
[14:37:15]:Thread start,thread id 5,thread name ab6ee6a0
[14:37:15]:start process id 2524 name cmd
[14:37:15]:Thread stopped, thread id 5, thread name ab6ee6a0
UPDATE:
what would the world be without mysteries. Though I cannot really accept them in the IT sector, I cannot really explain, why "everything" works now.
The error of miflash still exists, but fastboot works.
I tried booting and flashing the lineage boot.img instead of twrp.img as well as miflash about every five minutes. I do not think it was the latter, though.
I am still curious on that matter, but having everything working is more important.
Thank you anyway.
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub.
There is no need to use miflash to flash the fastboot miui rom - you can do it from command line in both windows and linux. Once you decompress the fastboot tar.gz, you have .bat and .sh files in the folder - miflash runs those exact files. Just install adb and fastboot on kubuntu and run your choice of script (flash_all, flash_all_lock, etc.) this has the added benefit of not needing odd drivers in windows (last time i used miflash it complained about some .net stuff that i had to manually install).
Since normally you would install twrp i have to wonder if by any chance mi-recovery is not checking the boot image before flashing it ... not sure, or maybe it had something to do with the FBE of lineage since there was no recovery in place to decrypt the partitions, if i remember correctly, the boot image needs to be signed with the verity key. The log snippet you provided doesn't tell anything as it has no error messages or anything.
Either way, not sure how what you brutforced to get it working but glad it solved itself, however, if you still have mi-recovery instead of a custom one, i would suggest you backup the device, flash MIUI without locking the bootloader, installing twrp (not just booting it) and reinstalling lineage from there. (all this can be done from your kubuntu install so you avoid driver and other windows shenanigans)
to install adb and fastboot it's just a question of sudo apt install adb fastboot
either tar -xvzf the archive of the fastboot image or just extract it from the file manager
open a terminal in the extracted folder (where the bat and sh files are)
put the phone in fastboot mode, connect via usb and do a "fastboot devices" just to make sure the device shows up
./flash_all.sh (this does the exact same thing as the clean option in miflash - just open the script and take a look through it)
Once the flash is done and the phone reboots, skip through all the setup steps just so miui loads up then reboot to fastboot
get twrp from their website, open terminal where it is downloaded and "fastboot flash recovery <name_of_file>.img"
once the command finishes do a "fastboot boot <name_of_file>.img" and once you are in twrp, go yo wipe, do a factory reset, back, advanced wipe and select the caches, back, format data, type yes, back to the main menu of twrp and reboot recovery, this should boot you back into twrp but this time the one that is flashed on the device.
from here on install rom of choice and magisk as usual (use the install option in twrp tho, don't unpack the zip)
Had the phone for 2 years and i flashed different roms on it almost weekly since the wait time to unlock the bootloader expired and never had an issue with this workflow and it saves you from having to use windows. Even for unlocking the bootloader, in case you ever lock it back up, you can use https://xiaomitool.com/V2/download (worked like a charm on linux)
sorfat said:
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub....
Click to expand...
Click to collapse
Thank you for your detailed reply!
Of cause, in order to install lineage, I used TWRP. But I somehow did not install it, but used fastboot boot twrp.img in order to manually temporary boot twrp every time I need it. It was not intentionally at first (did do
"fastboot flash recovery <name_of_file>.img"
Click to expand...
Click to collapse
) but I learned to like the mi recovery for it's wiping and being able to use with the keys (not touch, since I managed to disable touch once before that). Mi recovery does not allow flashing at all, so no worries there^^
I have read the ryzen thread before posting, that's why I included my hardware. Not sure, if Lenovo has ryzen, mine does not.
Why I did not think of just running the script in kubuntu instead of hassling with windows, I do not know. Guess it does have something to do with the wood in front of all the trees.
I have the phone for about one and a half week and flashed it at least once a day :laugh:
But I hope to neither lock it again (twice is sweaty enough) nor have to flash it every week.
Thank you very much, if I ever lock myself out again or get another phone to set up, I will defintely reread this post!
btw: is there no way in xda to close a thread?
I'm trying to flash an image as system
But OrangeFox, PBRB and TWRP don't let me (it doesn't even show me the option)
Is there any other way to do that?
Hi @ax0 what do you mean? Flashing from recovery gives the zip access to all system files...
traman124 said:
Hi @ax0 what do you mean? Flashing from recovery gives the zip access to all system files...
Click to expand...
Click to collapse
Yeah but I wanna flash a GSI (.img) and when I select the IMG , on the flash menu there isnt no "System"
Should I try to rename the image to "system.img" and then zip it and perhaps flash that?
is there an "install image" at the bottom of the screen in the zip select screen? Are you on the latest TWRP?
Ig he is saying that there is no system partition to flash the GSI image to.
Redmi 9C device has system-as-root partition, meaning that it has Super partition (which is IIRC a combination of system, product and vendor) rather than System partition
noob_developerdfd said:
Redmi 9C device has system-as-root partition, meaning that it has Super partition (which is IIRC a combination of system, product and vendor) rather than System partition
Click to expand...
Click to collapse
All devices shipped with Android 9 must have a system-as-root (SAR) layout. But it's not the same as a super partition.
The SAR configuration merged the root file system into system.img and then mount system.img as the root file system (rootfs).
This was published in connection with "Project Treble" to optimize the update process for vendor related files. Those files are no longer part of /system and now stored on /vendor.
Super: Here the partitions /system, /vendor and /product are dynamic logical partitions within /super (block device) and are managed in userspace. Fastboot access is also handled in userspace (recovery) by the fastbootd mode (fastboot reboot fastboot).
ax0 said:
I'm trying to flash an image as system
But OrangeFox, PBRB and TWRP don't let me (it doesn't even show me the option)
Is there any other way to do that?
Click to expand...
Click to collapse
As mentioned before that's related to /super. Use
Code:
fastboot reboot fastboot
when in fastboot mode to switch into fastbootd mode.
Then you should be able to run
Code:
fastboot flash system <PATH TO IMAGE>
To switch back into bootloader mode use
Code:
fastboot reboot bootloader
Take care using a newer version of the Platform Tools for full support of fastbootd mode.
WoKoschekk said:
As mentioned before that's related to /super. Use
Code:
fastboot reboot fastboot
when in fastboot mode to switch into fastbootd mode.
Then you should be able to run
Code:
fastboot flash system <PATH TO IMAGE>
To switch back into bootloader mode use
Code:
fastboot reboot bootloader
Take care using a newer version of the Platform Tools for full support of fastbootd mode.
Click to expand...
Click to collapse
For some reason when I run fastboot reboot (partition) it always just shows me the usage menu!
No matter what the partition is!
can you try getting fastboot through nexustools? I've had tons of problems with 15-second ADB in the past
traman124 said:
can you try getting fastboot through nexustools? I've had tons of problems with 15-second ADB in the past
Click to expand...
Click to collapse
What is NexusTools?
oh nvm https://github.com/corbindavenport/nexus-tools
that... actually worked!
i can reboot to fastbootd!
and WoKoschekk's guide worked!
thanks yall!