Related
A few days ago I got my Atrix HD and immediately rooted and subsequently unlocked the bootloader. Later I successfully flashed EcHoFiiVe's paranoidAndroid port... I didn't really like it because of the aspect ratio (too tiny) so I tried to flash back to a stock ROM. I lost and later accidentally deleted the backup I had made of the stock ROM that came on the device so that is now out of the question but for some reason, no matter what I do, I can't make changes to /system from the recovery or from the bootloader using fastboot commands. I've tried inputing
Code:
fastboot erase system -w
and it told me that I didn't have sufficient permissions and that the command failed. Therein lies my problem. Fortunately, I have a runnable backup (PA) I just really wish to try something different and the device is adamantly against the idea. According to the bootloader the device is unlocked with status code 3. Any help will be greatly appreciated!
read this
http://forum.xda-developers.com/showthread.php?t=2226527
frog1982 said:
read this
http://forum.xda-developers.com/showthread.php?t=2226527
Click to expand...
Click to collapse
I've read through that and I can now see a line that I missed that said that it was a common issue for that particular command to not work but I still don't know what to do about my inability to flash a different ROM. I have tried to mount /system before flashing and I've tried wiping /system using the recovery before flashing, all without avail. Do you have any advice on how to wipe the system partition?
you do not have to wipe it just fastboot flash Mex retail to overwrite it and you will be starting over.
frog1982 said:
you do not have to wipe it just fastboot flash Mex retail to overwrite it and you will be starting over.
Click to expand...
Click to collapse
to be clear, are you saying I can just do this:
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
Code:
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot reboot
sparkplugDev said:
to be clear, are you saying I can just do this:
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
Code:
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
yes but make sure you also have the snap-fastboot files in the folder you are working in or in your path
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).
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
My phone is 8937 and device state remains locked after stage 5. And "if not, do like U did this on old bootloader from fastboot" means we should use some other adb codes? Such as?
Woohooo, the display has been turned upside down. How do I fix this?
---------- Post added at 03:24 PM ---------- Previous post was at 03:17 PM ----------
What the ??? Stock recovery is upside down, but fastboot is the right way. Is this supposed to happen?
---------- Post added at 03:45 PM ---------- Previous post was at 03:24 PM ----------
Hmmm, I think I'll pass on this method. I appreciate the effort, but too much weirdness happening with my phone.
igerup said:
My phone is 8937 and device state remains locked after stage 5. And "if not, do like U did this on old bootloader from fastboot" means we should use some other adb codes? Such as?
Woohooo, the display has been turned upside down. How do I fix this?
---------- Post added at 03:24 PM ---------- Previous post was at 03:17 PM ----------
What the ??? Stock recovery is upside down, but fastboot is the right way. Is this supposed to happen?
Click to expand...
Click to collapse
worked thanks
Display rotates only few seconds when it boot
Dreamject said:
Display rotates only few seconds when it boot
Click to expand...
Click to collapse
It doesn't bother me at all ? it worked perfectly, thanks for your work
Dreamject said:
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
Click to expand...
Click to collapse
dont work for me, than i do this:
1. do what you told
2. use unlock bootloader from asus website
3. repeat what you told
4. walaaa... my device unlocked, than i flash twrp and magisk
5. done, i have rooted device
:laugh::laugh::laugh:
thank you guys...
no no no ..... not work for me, and upside down the title!!!!!
I have no choice but to fix it with: xxx youtube................. /watch?v=s592QY56VjM
than restore back to oreo 8.1..........
tfstk said:
no no no ..... not work for me, and upside down the title!!!!!
I have no choice but to fix it with: xxx youtube................. /watch?v=s592QY56VjM
than restore back to oreo 8.1..........
Click to expand...
Click to collapse
if you screen rotated on thethe boot, it means you have old bl. You just needneed toto flashflash twrp, or unlock bl with fastboot
Dreamject said:
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
Click to expand...
Click to collapse
I've problem that if I mounted System partition in Any App,it will freeze my Systemui and can't do anything
Since 7.1.1 to 8.1 still have these problem
tony8077616 said:
I've problem that if I mounted System partition in Any App,it will freeze my Systemui and can't do anything
Since 7.1.1 to 8.1 still have these problem
Click to expand...
Click to collapse
DonT know.... Try magiskmagisk, system less stuff, change launcher, disable bloatware
Dreamject said:
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
Click to expand...
Click to collapse
Hi, thank to you I have unlocked my phone in 8.1.
But when I tried to downgrade to nougat, home and fingerprint botton won't work. I had tried relocking bootloader and lock again using nougat method, but still home button won't work.
Do you have any idea to fix home button so I can use nougat firmware in this device?
komtek said:
Hi, thank to you I have unlocked my phone in 8.1.
But when I tried to downgrade to nougat, home and fingerprint botton won't work. I had tried relocking bootloader and lock again using nougat method, but still home button won't work.
Do you have any idea to fix home button so I can use nougat firmware in this device?
Click to expand...
Click to collapse
You should flash service nougat
Dreamject said:
You should flash service nougat
Click to expand...
Click to collapse
I'm sorry, can you tell me what service nougat is? Did you mean play service, or other service?
komtek said:
I'm sorry, can you tell me what service nougat is? Did you mean play service, or other service?
Click to expand...
Click to collapse
you can find service fw at least on 4pda. Service fw contained more data than usual fw
Dreamject said:
you can find service fw at least on 4pda. Service fw contained more data than usual fw
Click to expand...
Click to collapse
Thanks to @Dreamject I have managed broken fingerprint sensor when I tried to downgrade to 7.1
Here is quick guide to fix broken fp sensor in 7.1:
(Prerequisites: adb driver installed on computer)
1. Download service firmware nougat v.232-AFT https://yadi.sk/d/IzR3ITht2IlHxw (source 4pda)
2. Extract firmware to root C://
3. Open flashall_AFT.bat
4. Go to fastboot mode and connect the phone to computer. (NOTE: YOU MUST ON 8.1 FIRMWARE UNLESS FP SENSOR WON'T FIXED)
5. Wait ~10 minutes until finished.
Mother Russia)
By the way, be careful, coz it contains as o remember service Oreo too.
If file name 14.2016 it's nougat, if 15.2016 it's Oreo
link is gone, pls fix the link
Bootloader ReLocked Problem same as WW-15.2016.1812.505,So contiue used these step
Dreamject said:
As you know, on 8.1 we still have ununlockable bootloader. But it's quite simple to fix, just flash 'old' bootloader
It's unofficial method
1) Go to fastboot bode (keep + button on reboot/boot your phone)
2) Use service firmware or download this https://vk.com/doc275347426_479517439 , open command promp (start.bat)
3) VERY IMPORTANT
you should know your platfotm. As I know, 2 GB (my phone) have 8917 processor, 3gb/32 have 8937. You can get your platform with this
Code:
fastboot getvar platform
4) I have 8917, so I type
Code:
fastboot flash aboot 8917_emmc_appsboot.mbn
fastboot flash abootbak 8917_emmc_appsboot.mbn
On 8937 type
Code:
fastboot flash aboot 8937_emmc_appsboot.mbn
fastboot flash abootbak 8937_emmc_appsboot.mbn
5) Reboot your phone, you should get 'device state unlocked' , if not, do like U did this on old bootloader from fastboot
6)Flash twrp as usual. In archive I already include this, you can flash it with
Code:
fastboot flash recovery twrp.img
And install magisk/SSu
Attention: if you wanna get full access for /data partition from twrp, you should flash patch with prevent autoencrypt. I did not do this, system access is enought for me.
But before you root your device, U have to erase data partition, coz root patch boot partition too, patched boot can not load stocky encrypted data. After data format you can flash magisk. When you boot phone, it will encrypt data partition and you get installed Magisk and ecrypted data
Original system/boot images, restore them with twrp https://mega.nz/#!ziJxCCqA!C0lG5hUcOGwl2ER0Mp342lfx5_DOIzalAi7RExR6nro
Click to expand...
Click to collapse
I've make a flashable which can used with ZF4 Max update ROM(script and binary based on WW-15.2016.1812.505,file is from OP post)
-Just flash it after stock ROM update
[GUIDE][HOW TO] Flashing with care & Surviving soft bricks with fastboot [CMD] [TIPS]
Hello guys, some of us are new to the A/B partitions. Flashing on wrong partition may end up in soft bricks. This is not a rooting guide, here I'm explaining how to handle flashing A/B partitions properly and survive soft bricks using fastboot . Always backup your data before flashing anything.
Those who still don't know about the A/B partitions, please take a look at this thread https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Prerequisites:
OnePlus 6T with unlocked or locked bootloader
A computer for running fastboot commands
You :laugh:
Rebooting
Rebooting your device via adb and fastboot
Code:
adb reboot //normal reboot
adb reboot recovery //reboot to recovery
adb reboot bootloader //reboot to fastboot (bootloader)
Code:
fastboot reboot //normal reboot
fastboot reboot bootloader //reboot to fastboot (bootloader)
Unlocking the Bootloader
Bootloader can be unlocked via fastboot
Code:
fastboot oem unlock
WARNING THIS WILL WIPE YOUR DATA
Working with A/B Partitions
There are two boot partitions on this device, named boot_a and boot_b respectively, they are not the “traditional” boot partitions. Both of these partitions contain a kernel and ramdisk like you are probably used to. The difference is that there is no recovery partition and the boot partition is new recovery partition. The A/B partitioning scheme can be quite confusing to users. There are actually two copies of many of the partitions. There is only one data (userdata) partition.
Slots
The concept of ‘slots’ comes into play to determine whether you are booting ‘slot A’ or ‘slot B’. We can determine which slot is ‘active’ or marked for booting via adb and fastboot:
Code:
adb shell getprop ro.boot.slot_suffix
Code:
fastboot getvar current-slot
Switching Slots
We can switch between slots via fastboot:
Code:
fastboot set_active other //switch to inactive slot
Code:
fastboot set_active (a or b) //switch to specified slot
Flashing/Booting
We can flash/boot (temporary flash) recovery/kernel via fastboot. To boot (what we call temporary flash) a kernel/recovery there is no need to switch/select any slot. Keep in mind that when we run the flash command instead of boot, it will wipe the specified partiton (you may lose your root & custom kernel)
Code:
fastboot boot boot.img or twrp_recovery.img
To flash permanently, first switch/select any slot you want or it will automatically flashed to the active slot. This may cause boot loop, always proceed with caution.
Code:
fastboot flash boot boot.img or twrp_recovery.img
Code:
fastboot flash recovery twrp_recovery.img
If your testing something, always use the inactive slot. Eg: if you want to test a custom rom, first back up your data then switch to the inactive slot and flash the custom rom, this will save your time (no need restore full backup only data).
Surviving Soft Bricks
Some possible simple solution we can try rather than using MSMTool or flashing the full rom.
When causing boot loops, try these:
Flash Magisk via recovery
Switch to the other slot via fastboot
Wipe data partiton via fastboot -w
When causing Bootloader crash, try these:
Turn off the phone by holding the power button (release after power off)
Hold both volume buttons
Now press power button
Phone will boot to fastboot
Now switch the other slot via fastboot
To be continued....
Just in case
This is my first A/B device so forgive my ignorance, I was wondering if its possible to flash two different roms on to different slots...like oxygen on one partition and lineage on other?
Also why twrp has two buttons 'slot a' and 'slot b' in reboot section?
The phone doesn't have recovery partition, so what happens on typing 'Fastboot flash recovery' command?
Thanks again for this tutorials. That's really helpful in understanding of the new Android features.
What'd be your advice on instructions to get stock kernel back? I couldn't find an appropriate command on how to do it
patelparth120595 said:
This is my first A/B device so forgive my ignorance, I was wondering if its possible to flash two different roms on to different slots...like oxygen on one partition and lineage on other?
Also why twrp has two buttons 'slot a' and 'slot b' in reboot section?
The phone doesn't have recovery partition, so what happens on typing 'Fastboot flash recovery' command?
Click to expand...
Click to collapse
You can install any rom on both slot, there is no problem. There is only one userdata partiton. The two buttons are for switching between slots, if you press slot a button, the recovery will mark slot a as bootable or active partition. On next boot or reboot rom from slot a will boot, this same thing is applied for slot b too. There is no dedicated partition for recovery , files for recovery are stored in system_root.
geminium said:
Thanks again for this tutorials. That's really helpful in understanding of the new Android features.
What'd be your advice on instructions to get stock kernel back? I couldn't find an appropriate command on how to do it
Click to expand...
Click to collapse
Get stock boot.img file and flash using fastboot
Code:
fastboot flash boot boot.img
AnoopKumar said:
You can install any rom on both slot, there is no problem. There is only one userdata partiton. The two buttons are for switching between slots, if you press slot a button, the recovery will mark slot a as bootable or active partition. On next boot or reboot rom from slot a will boot, this same thing is applied for slot b too. There is no dedicated partition for recovery , files for recovery are stored in system_root.
Click to expand...
Click to collapse
Thanks for the reply. Cleared all my doubts.
So could we have two ROMs and switch back and forth between on one device in this case?
geminium said:
So could we have two ROMs and switch back and forth between on one device in this case?
Click to expand...
Click to collapse
Because of one userdata partition, there will be some issues. If wipe data when switching roms, no issues then.
Man i could use some help patched the file moved it to harddrive tried fastboot flash boot boot.img (the patched one) and all i get is
C:\Users\seang\OneDrive\Desktop\Moto G Stylus 2021>fastboot flash boot boot.img
error: cannot open 'boot.img' Could you please make a guide with some pics or at least a step by step cause nothing i have tried has gotten root yet. Thanks!
Thanks to the OP.
WARNING:
You need to backup your data before installing. I am not responsible for any damage or loss that might occur. Proceed at your own risk.
Tested with MIUI version 10.2.5.0 Global.
Bootloader must be unlocked (https://en.miui.com/unlock/)
1. Unpack Minimal ADB and Fastboot to C:\ drive of your PC
2. Rename patched boot to boot.img. Rename recovery file to recovery.img. Place boot.img, recovery.img, vbmeta.img in ADB folder.
3. Enable USB-debugging in developer options on your phone.
4. Connect phone with PC via USB. Reboot phone to fastboot mode (Volume-down + Power).
5. On your PC open command prompt and nagivate to ADB folder.
6. Enter the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash vbmeta vbmeta.img
Code:
fastboot flash recovery recovery.img
7. Reboot to recovery (Volume-Up + Power; release Power when phone turns on, keep holding Volume-Up until you see screen of TWRP). If TWRP asks for PIN, enter the PIN of your unlock screen.
8. Wipe Dalvik / ART cache, System, Data, Cache. Format Data > Yes
Do not wipe Internal Storage!
9. Unpack the downloaded GSI Rom and move it to your phone.
10. Flash the Rom (Install image).
11. Reboot to Recovery.
12. Move files Magisk, Permissiver, FM-Radio fix, GApps to your phone.
13. Flash Magisk (optional)
14. Flash Permissiver
15. Flash GApps (optional).
If you get 'insufficient space' error, first resize System partition.
16. Flash FM-Radio fix:
In TWRP, Mount System. Then flash fix.
17. Reboot system and enjoy.
-----------------------
Downloads:
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
GSI Rom:
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
You need to get a64_bvN version from folder lineage-17.x.
Patched boot img file:
http://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Check your MIUI version in System, so that you download the correct boot img file.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
vbmeta file
http://www.mediafire.com/file/bgpn9b87b4t8yye/vbmeta.img/file
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Permissiver
https://androidfilehost.com/?fid=6006931924117940902
GApps (choose 'ARM' & '10.0')
https://opengapps.org/
FM Radio fix:
https://androidfilehost.com/?fid=8889791610682885147
After installing Gsi
After installing Gsi, can I get the fast boot mode later
Ts40 said:
After installing Gsi, can I get the fast boot mode later
Click to expand...
Click to collapse
Yes, you can still get into fastboot mode.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
kra_ppo said:
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
Click to expand...
Click to collapse
i would recommend you to flash MIUI global first, because if somethings goes wrong you can't say whats the reason for the error.
and the encrypted folders can be deleted in twrp by format data -->yes
raijinlee said:
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Click to expand...
Click to collapse
thats the one i'm using and never had problems with this, so yes