Related
I decided to go to Android 5.0.1 from CM10.2 on my Nexus 4. I guess I did not think it though that well and relied on some crappy guides too much.
I have CWM Recovery 6.4.3 installed, so I thought I just place the factory image on the phone and install it via CWM. So:
1) Copied occam-....tgz on the phone;
2) Rebooted into CWM recovery;
3) Did wipe cache/format system/wipe dalvik;
4) Went to install .zip menu... and figured out that the file is no longer on my phone.
I thought OK, I do it via ADB and cable, so installed ADB, drivers etc. and connected my phone to my computer. However, adb does not see it most of the time (when at logo, bootloader, recovery) and only once adb managed to see it (*some number* device unauthorized) while the phone was at Google logo. And I realized I forgot to set up the USB debug option. What are my options now? I can go into CWM recovery, but ADB does not see the device, as I forgot to set up recovery before flashing. Help, please?
The computer sees the phone as MLP, but I still cannot see its storage in Explorer, so I cannot copy the .zip file.
Update
I managed to make adb recognize the phone, but consistently says that it is not authorized, which makes sense. And there is not way I can mount it as an external storage .
first of all, you have a serious lack of knowledge. not activating USB debugging in android settings has no effect whatsoever on ADB usage ability when you are in recovery mode. Secondly, installing factory images is not done through recovery (the downloaded factory image zip is not even flashable so it would work not in recovery), as factory images also contain RADIO and BOOTLOADER images that are flashable through fastboot (not the recovery). The only thing from factory image that you could flash via recovery is a zip file named - in case of 5.0.1 factory image - image-occam-lrx22c.zip (you can find it if you unpack the downloaded factory image on your PC). And this zip file is a classic ROM (system,userdata,boot,cache,recovery partitions). However, even if you were to flash the correct zip (rather than the zip containing entire factory image complete with ROM, RADIO and BOOTLOADER) Android 5.0 (or 5.0.1) comes with updated RADIO (maybe bootloader aswell, i did not check), so you are supposed to update that aswell prior to switching to 5.0/5.0.1
now here is what you should do:
1. download 5.0.1 factory image from gooogle
2. make sure you have ADB and drivers for Nexus4 correctly set up (in order to check wheter it works go see point 3 of this instruction set)
3. boot to fastboot mode (vol down+power) and check if 'fastboot devices' gives you back device id (you should open command prompt in platform-tools folder, where both adb.exe and fastboot.exe are present)
4. proceed with this instruction, start at step 8 http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ (in step 11, name of zip file is the one that is INSIDE downloaded factiory image file (image-occam-lrx22c.zip) and you either do the single zip flash or flashing each of .img files separately (system,boot,userdata,cache,recovery)
ps. 1st android 5.0.1 boot after flashing will take up to 15 minutes. (it took 10 in my case)
Update 2
Thanks dzumagos! Sure, I do not claim to be a specialist by any means. I managed to successfully install Cyanogenmod many times, so thought I would give this one a go as well.
I read your post after I fixed the issue. Basically I did exactly what you suggested, but following another guide and it worked fine, also took it around 15 minutes to load the first time. I noticed I do miss a few tricks from Cyanogenmod
Hello. Sorry for my english. I want flash my phone via rootjoy to Arcatarc's MIUmIZERO and i only can see miui logo. next i want back to stock rom from needrom via sp flash tool, i followed instructions and i stop, when red status back not change for 20 minutes. and i can't charge my phone, can't conected to pc, can't turn on, looks like dead. How unbrick my phone? please help
problem solved
how did you solve it? please let me know as i am in the same boat
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
it is dead . the phone wont turn on . the pc wont recognise it anymore , it was fine ... untill i tried to flash stock through sp flash tool .
i was running antarcts emui,.... tried flashing using the method on umi digi forum : http://umidigi.com/forums/topic/how-to-restore-rom-version-3-03-2/ ... preloader was unticked, and when i tried firmware uopgrade option...nothing happened, and the phone was dead after that.
thepopos said:
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
Click to expand...
Click to collapse
I managed to make it boot.
The problem is I have twrp and some chinese recovery . And I cant go back to stock.
Fastboot cant flash recovery for some reason ... so I can go back to rootjoy.
use adb side load an try to flash a working rom, the original one from umi website or emui.
can you get in recovery mode? volume (+ or - try both) and power button for some seconds
if yes go adb side load, (check google) and transfer an original rom, then flash it again in the recovery
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Pospa420 said:
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Click to expand...
Click to collapse
If the system is unstable with popups etc or with damaged partitions you can get past that with TWRP.
Boot into recovery Wipe/Advanced Wipe. Then after that is completed, without rebooting, Format Data. That should sort out your partitions.
Then Install ROM from the recovery. It will need to be on the device. If your new ROM is not already there plug in a USB lead and transfer the zip file from your pc.
If you want to re-install your backup, do that instead.
If that doesn't work Backup in TWRP, even though there is no system. Then copy your Nandroid backup (must have been made via TWRP) and paste into the same folder as the Backup you just made, overwriting if asked.
I have had to do all this myself!
Good luck
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
It looks like memory become write-protected...
YrP said:
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
Click to expand...
Click to collapse
Hi
Did you Advance Wipe and Format Data?
I found that worked.
Alternatively, you could use Rootjoy to put just about any ROM on. CM 12.1 works ok.
Once you have a stable installation, install a custom recovery like TWRP 2.8.7 from Needrom. I used Mobileuncle, an app from the Playstore. However, I looked just now and it doesn't seem to be available.
I have tried Rashr, but couldn't get it to work.
Once you have it all stable you can flash the ROM you really want via TWRP.
Good luck
Advance Wipe and Format Data or flashing new stable ROM via TWRP did not work for me. The same result- unable to mount /system.
Rootjoy and Mobileuncle could be used if phone is working. My phone works in recovery mode only.
I tried to flash different recoveries but did not find the way to do this. As I wrote, Sp Flash Tool, Fastboot and Adb Sideload did not make any changes to my recovery. I think, flash new recovery will help if I found the way)
Or if I discover the method to test and\or repair /system partition from PC
But thank you for answer)
@YrP
Rootjoy works from your pc
Yes, Rootjoy- works)
But for establish connection phone must work too.
And not in recovery mode.
@YrP
I have already done all this with my daughter's Zero.
However, it's in bits at the moment while we wait for a part from China. So I can't go through the process with you live, step by step.
I am in the UK.
If you send the phone to me I will try and fix it for you.
PM me if you want to go ahead and I will let you have my address.
I am in Ukraine, it is too far from UK)
I will keep trying to find the way to fix it by myself.
But thank you very much for your attention and advices.
@YrP
I have got my daughter's phone back together and fixed (mostly).
Did you manage to get your Zero going?
Sent from my Nexus 4 using XDA-Developers mobile app
@goldbear
My UMI is still bricked(
It is flash memory problem, I think.
I am trying to find the tool to remap internal memory, to move SYSTEM part to other physical place. But did not find it yet.
What was your way?
Zero stutters, processes crash or the phone will not boot into System
Have you already tried a Factory Reset or re-installed the ROM?
What can you do?
You could try the following. However, if your phone blows up, orders a takeaway or elopes with your girl-friend, please don’t blame me.
1. Provided you already have TWRP custom recovery installed and your phone is powered down boot into Recovery: hold the volume down and power buttons until the Zero logo appears then let go
2. Select Wipe/Advanced and select Dalvik Cache, System, Cache and Data. Slide to execute
3. Select Format Data/ type yes and slide to execute
4. Reboot into Recovery without installing a new ROM
5. Select Backup, choose SD card rather than internal storage and give the file a memorable title like Blank Backup and date. Select Boot, Logo, Recovery and Uboot. Slide to execute
6. The next step requires you to have a Nandroid backup made via TWRP already made of a stable ROM. If it isn’t stable or you don’t have one I have attached a clean backup below. It’s derived from Cyanogen Mod 12.1. This is based on Lollipop 5.1, with Gapps and rooted. I have found this to work. As the title of the file suggests, it’s a factory reset, ie no personal data included. Download it to your pc unzip and save it.
7. Connect your phone to your pc via USB cable and open Windows Explorer
8. Find your stable backup or the one below and drill down until you see the folder with 15 files, starting with data.info and ending with uboot.emmc.win. Select all and Copy.
9. Open another window and find the TWRP folder on the SC card of your phone. Drill down to the same folder containing similar files as to step 8 above. Click in folder and Paste. When prompted select Copy and Replace, all and Ok
10. If your pc doesn’t show your phone and the SD card, in recovery select Mount and USB storage.
11. In Recovery select Restore and the Blank Backup (or whatever file name you gave it, now populated with usable ‘data’). Slide to execute
12. Give it time to load and boot up
13. You should be good to go!
If you don’t like CM 12.1 installing a new Launcher from the Playstore, like Cheetah will make it run smoother. Everything after that is down to you.
Of course, you could flash another ROM via TWRP
The backup below was made via TWRP 2.8.6. This is also attached below. You can install this via a previous version of TWRP as an image. Unzip it first.
Assuming this doesn’t wreck your phone and you like the guide please click Thanks below.
https://drive.google.com/file/d/0ByoLjFrSKxLwc01UUWZBZEQtbWs/view?usp=sharing
https://drive.google.com/file/d/0ByoLjFrSKxLweGhqNGJuVGV1a0U/view?usp=sharing
[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required
Simplified procedures with LMY47M / LYZ28E now available as a factory image.
Hopefully this isn't blatantly obvious to everyone, it is a little different than the normal sideload procedure. Thought it might be useful to some who want to load 5.1.1 (and get Wifi calling with T-Mobile!) and not be forced to encrypt.
Requirements:
1. I'm assuming you have adb/fastboot working on your computer / connecting to your device and you understand a little bit about using adb / fastboot with an android phone.
2. Your phone cannot be encrypted, if you're encrypted already - this will not un-encrypt your data - you need to turn off forced encryption and format the "userdata" partition to disable the encryption.
3. You need to have an unlocked bootloader for this to work of course.
How to follow this procedure:
1. If you're on LMY47M (T-Mobile) and unencrypted, you can follow option 2, starting with Step 3 - only a small ~150MB download required.
2. If you're on anything other than LMY47M, you should use option 1 unless you have a desire to flash LMY47M and sideload LYZ28E.
I didn't do much here - except spent a bunch of time writing the procedure.
All Credit for tools / ideas goes to:
- efrant for his explanation of how to get OTA updates to work with TWRP ( http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919/page4 )
- hlxanthus for the NO FORCE ENCRYPT mod ( http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788 )
- Q9Nap and mhous33 for the LMY47M factory image ( http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 )
- bbedward and others for the original disable forced encryption boot.img ( http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715 )
- TeamWin - the TWRP Developer ( https://twrp.me/ )
——————————————————————————————————
OPTION 1 - Easy Method - Flash the LYZ28E factory image directly:
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Download LYZ28E for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lyz28e-factory-b542b88a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img (OPTIONAL - If you have TWRP or another alternative recovery you can skip this step)
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Restart the Bootloader, and flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the Bootloader again and then go to Recovery (TWRP). Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!
———————————————————————————————————————————————————
OPTION 2 - SIDELOAD Method (Makes sense if you’re already on LMY47M):
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Follow the normal procedure, if you're already on LMY47M you can skip to step 3. Download LMY47M for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lmy47m-factory-5228e84a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Now flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the bootloader, and enter recovery mode (TWRP). Once in TWRP, go to Advanced -> ADB Sideload. You may need to unplug/plug in the USB cable to your computer again.
Download my version of LYZ28E from here: https://www.androidfilehost.com/?fid=23991606952609905
Note: I modified this version to work with TWRP, it will not work with the stock recovery (because I modified it, the signature on the file is now invalid). The only thing I changed was I edited the updater-script to remove the release keys check which seems to fail on the stock recovery and doesn't work right with TWRP).
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
5. After it finishes, do not reboot yet. Go back and I recommend rebooting to recovery again. Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!
why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.
simms22 said:
why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.
Click to expand...
Click to collapse
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.
liqice said:
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.
Click to expand...
Click to collapse
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.
simms22 said:
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.
Click to expand...
Click to collapse
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?
Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.
cam30era said:
Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.
Click to expand...
Click to collapse
Thanks, updated the original post.
liqice said:
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?
Click to expand...
Click to collapse
easier/harder isnt an option here, since any way takes seconds. im just saying there are several options for this, thats all
liqice said:
Code:
fastboot flash f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
Click to expand...
Click to collapse
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?
So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?
Chahk said:
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?
Click to expand...
Click to collapse
Oops, you're right. Thanks!
Gage_Hero said:
So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?
Click to expand...
Click to collapse
This is where I was, LMY47E, rooted, unencrypted and with TWRP. I followed the entire procedure - went back to LRX22C using fastboot, then sideloaded LMY47M (T-Mobile version) - then flashed the no force encrypt boot.img - booted, after it finished booting, rebooted to the bootloader and so on ...
When you go to LRX22C you flash back to the stock recovery. So you need to boot into the stock recovery, pick "apply update from adb" and then run the adb sideload command from the PC.
Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?
With the factory images being posted, I just did the following:
Flashed the factory images
While still in bootloader, flashed TWRP
Rebooted into TWRP
Pushed SuperSU and the No_Force_encrypt to the /sdcard/ partition
Installed via TWRP
Profit.
lamenting said:
Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?
Click to expand...
Click to collapse
For LMY47D you need to get to LMY47M first, so you would follow the entire procedure, downgrade to LRX22C and then sideload LMY47M and so on.
Heavily updated the procedure since LMY47M and LYZ28E factory images are now available directly from Google.
Should be a lot easier and more straight forward now!
I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?
Boot loader and radio only...
So if I understand the instructions correctly, if you are still encrypted but rooted, from any Lollipop installation, fast boot flash the factory images... then flash TWRP ... root and done right? Then I have another question... the kernel I am running EX 1.07 along with Flar's app is running perfect for me.... any dangers in just flashing the boot loader and radio? I would like to wait on the system part until the kernel has been updated.....
Also, if I needed to do a restore, if I only flash the boot loader and radio have I pooched being able to go backwards to a nand backup?
FYI, step 3 in option one should read:
fastboot flash recovery twrp-2.8.6.0-shamu.img
vs
fastboot flash twrp-2.8.6.0-shamu.img
frater said:
I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?
Click to expand...
Click to collapse
Starting with Android Lollipop (5.0) and newer - at least on the Nexus 6 - encryption is turned on by default for the userdata partition.
You would - if you wanted to - backup all of the data on your userdata partition (e.g. Any pictures you've taken with the phone, etc - all of the data basically that shows up when you plug your phone into your computer).
Then you need to be running an OS that doesn't force encryption (for example if you follow my instructions) - this would also get you running 5.1.1.
After that you need to format your userdata - it wouldn't be encrypted at that point, and then copy your data back if you want to.
If you don't care about encryption, you can simply flash the factory 5.1.1 image following my instructions and skip the TWRP parts.
Help me guys. I deleted my Oneplus 6T SystemUI.apk. Bootloop. Please teach me how to fix it.
Maybe this thread could be useful
https://forum.xda-developers.com/showthread.php?t=1637847
Is your bootloader unlocked? If so, you can just boot TWRP via fastboot (boot the img, not installing the zip) and dirty flash the latest OTA.
If nothing works, boot into EDL mode and use msmdownloadtool as last resort, but you will lose ALL your data in the process. Don't mess with the cable when msmdownloadtool is working or your phone is going to be permanently bricked. You should only use msmdownloadtool if you've tried everything and nothing is working, or you entered Qualcomm crash dump mode and fastboot/recovery isn't working.
I don't understand
komodo_1 said:
Maybe this thread could be useful
https://forum.xda-developers.com/showthread.php?t=1637847
Click to expand...
Click to collapse
I don't understand this
Then
adb shell
su
rm system/app/SystemUI.apk
exit
basedtobeh said:
Is your bootloader unlocked? If so, you can just boot TWRP via fastboot (boot the img, not installing the zip) and dirty flash the latest OTA.
If nothing works, boot into EDL mode and use msmdownloadtool as last resort, but you will lose ALL your data in the process. Don't mess with the cable when msmdownloadtool is working or your phone is going to be permanently bricked. You should only use msmdownloadtool if you've tried everything and nothing is working, or you entered Qualcomm crash dump mode and fastboot/recovery isn't working.
Click to expand...
Click to collapse
My 6t bootloader unlocked and i don't have boot img
undrahbayar said:
My 6t bootloader unlocked and i don't have boot img
Click to expand...
Click to collapse
Since you uninstalled SystemUI.apk, I'm going to assume you have Magisk and adb/fastboot installed on your PC.
Do you have TWRP installed? If so, just boot into it and dirty flash the latest OTA.
If not, download twrp-3.2.3-2-fajita.img here https://dl.twrp.me/fajita/ and boot into it via fastboot.
On your PC, download the latest OxygenOS from OnePlus website. move the .img you downloaded earlier to your fastboot folder, hold Vol Up + Power until you enter fastboot, back to PC - type into the search bar "cmd" then press enter, type fastboot boot "twrp-3.2.3-2-fajita.img" and press enter. Your phone should boot into TWRP, now copy the OTA file into your phone and install it into both slots (just to be sure).
You're going to lose Magisk if you do this, but you can just reinstall it and it's much better than having a $600 paperweight
Remember that you need to have a working adb and fastboot on your PC to do this.
Some tip: You can backup your data while you're in TWRP via USB mass storage, it's a good idea to do it now just in case your phone is bricked even worse than before.
basedtobeh said:
Since you uninstalled SystemUI.apk, I'm going to assume you have Magisk and adb/fastboot installed on your PC.
Do you have TWRP installed? If so, just boot into it and dirty flash the latest OTA.
If not, download twrp-3.2.3-2-fajita.img here https://dl.twrp.me/fajita/ and boot into it via fastboot.
On your PC, download the latest OxygenOS from OnePlus website. move the .img you downloaded earlier to your fastboot folder, hold Vol Up + Power until you enter fastboot, back to PC - type into the search bar "cmd" then press enter, type fastboot boot "twrp-3.2.3-2-fajita.img" and press enter. Your phone should boot into TWRP, now copy the OTA file into your phone and install it into both slots (just to be sure).
You're going to lose Magisk if you do this, but you can just reinstall it and it's much better than having a $600 paperweight
Remember that you need to have a working adb and fastboot on your PC to do this.
Some tip: You can backup your data while you're in TWRP via USB mass storage, it's a good idea to do it now just in case your phone is bricked even worse than before.
Click to expand...
Click to collapse
i don't want lost my data. my phone twrp installed. https://l.facebook.com/l.php?u=http...v2tKWpgjtH1uNa9qGkEpux3yPIjNDUTQIEPCPb_dVJD7U i don't understand it
He had to delete the wrong systemui apk first, with the commands you quoted
then comes those for apk installation
Code:
adb push SystemUI.apk system/app/SystemUI.apk
reboot
i never tried something like that so I dunno if it would work on all devices, or just on rooted or on no one @ all.
undrahbayar said:
I don't understand this
Then
adb shell
su
rm system/app/SystemUI.apk
exit
Click to expand...
Click to collapse
undrahbayar said:
i don't want lost my data. my phone twrp installed. https://l.facebook.com/l.php?u=http...v2tKWpgjtH1uNa9qGkEpux3yPIjNDUTQIEPCPb_dVJD7U i don't understand it
Click to expand...
Click to collapse
Dirty flashing doesn't wipe your data, but you should definitely back up your data in case something goes wrong.
If you have TWRP installed, just do what I typed on my previous reply. To make it clearer:
1. Download the latest OxygenOS for OnePlus 6T here https://www.oneplus.com/support/softwareupgrade/details?code=9
2. Boot into TWRP (Vol Up + power/Vol down + power, I don't remember which one is for recovery). If it asks for password, enter your PIN number
3. USB mass storage should now be available, you can copy/move files from your phone to PC while in this mode. It's a good idea to backup your data now if you haven't.
4. Copy the OTA file you downloaded into your phone
5. Press Install on TWRP, and select the file you downloaded earlier. It's going to take a while, don't panic.
6. When it has finished, DON'T reboot into system. Instead, go back to TWRP.
7. Press Reboot and choose the other slot (opposite of current slot, so if your current slot is B, press A. if it's A, press B)
8. Install the OTA again (This flashes stock OOS into both slot)
9. Again, DON'T reboot into system, go back to TWRP.
10. Press Reboot in TWRP and choose your previous slot.
11. Boot into system
You're not going to lose data if you do this correctly. But, you're going to lose Magisk if you do this (or maybe TWRP too). Just install Magisk again.
Don't permanently install TWRP on OP 6T because it's going to conflict with Magisk. If you need TWRP, just boot into TWRP.img via fastboot instead of permanently installing it.
I don't exactly know how to flash ROMs on A/B partition devices, but this is what I do and it works everytime. Some steps might be unnecessary, though.
basedtobeh said:
Dirty flashing doesn't wipe your data, but you should definitely back up your data in case something goes wrong.
If you have TWRP installed, just do what I typed on my previous reply. To make it clearer:
1. Download the latest OxygenOS for OnePlus 6T here https://www.oneplus.com/support/softwareupgrade/details?code=9
2. Boot into TWRP (Vol Up + power/Vol down + power, I don't remember which one is for recovery). If it asks for password, enter your PIN number
3. USB mass storage should now be available, you can copy/move files from your phone to PC while in this mode. It's a good idea to backup your data now if you haven't.
4. Copy the OTA file you downloaded into your phone
5. Press Install on TWRP, and select the file you downloaded earlier. It's going to take a while, don't panic.
6. When it has finished, DON'T reboot into system. Instead, go back to TWRP.
7. Press Reboot and choose the other slot (opposite of current slot, so if your current slot is B, press A. if it's A, press B)
8. Install the OTA again (This flashes stock OOS into both slot)
9. Again, DON'T reboot into system, go back to TWRP.
10. Press Reboot in TWRP and choose your previous slot.
11. Boot into system
You're not going to lose data if you do this correctly. But, you're going to lose Magisk if you do this (or maybe TWRP too). Just install Magisk again.
Don't permanently install TWRP on OP 6T because it's going to conflict with Magisk. If you need TWRP, just boot into TWRP.img via fastboot instead of permanently installing it.
I don't exactly know how to flash ROMs on A/B partition devices, but this is what I do and it works everytime. Some steps might be unnecessary, though.
Click to expand...
Click to collapse
i don't fix it. don't work it.
Nubia Red Magic 5G and 5S Roms and Root support Thread
Second post for TWRP and Magisk installation. Mirror for all roms and tools at end of post
Latest Official Rom updates
Android 11
US/Asia - V8.70 Nubia Link MD%: will update soon
EU - V7.70 Nubia Link MD5: will update soon
China - V9.50 Nubia Link MD5: 361AC13CA52AB83C239783FBAB088CEA
Android 10
US/Asia - V8.12 Nubia Link MD5: 6e930fc2431b3daeae2d94145926a6c1
EU - V7.15 Nubia Link MD5: bb9e3153716851e87f196ae6b4f44a2e
China - V6.23 Nubia Link MD5: BD447840ACA4D48F9443B94D2EAD890F
Change Log - 8.70 / 7.70 Android 11
- Security Patch October 2022
- Game Space enhancements
- Game space Gyro sensitivity menu
- game space touch sample rate improvement
- Fixed: corner of screen non-touchable in some cases
- Fixed: issue where game would fail to close
- Fixed: location of caller display
-Fixed: screen tearing when using 144hz
-
Bugs -
in Testing
- Always on display notification not showing
- memory leak in nubia launcher (requires forced close often to stop phone from lagging)
- small window mode for telegram and discord have wrong zoom/ aspect levels.
_____________________________________________________________________________________________________________
UNBRICK TOOL for 5S - Courtesy of @johnny886
Use this tool, with directions on the thread to restore your device to USA/Asia 8.07
you can then install TWRP and after flash any region rom after creating a somewhat universal unbrick tool for those in different regions.
Follow directions on the thread. but here is a link to the Thread. A Mirror for the tool is in my Personal Mirror at the bottom of this thread post.
Link to Thread
Confirmed working with 5G devices - but its recommended to update as soon as you unbrick.
_____________________________________________________________________________________________________________
For unlocked bootloader
Fix your fingerprint sensor.
here Link
--------------------------------
Update Instructions.
Note
for Android 11 do not flash through TWRP you will softbrick.
____________________________________________________________________
For Stock devices without root
- disable security. No pin, no face unlock, no finger print, no pattern. remove all security.
-download zip file
-go to system update tap three dots and select local update
-Navigate to update.zip and select.
-your phone will reboot and install new rom
- you phone will reboot once more and you will be greeted with your lock screen
- setup Phone with security options as before flash.
For devices with "LOCKED bootloader" Root / TWRP (not tested on A11)
- take backup of vbmeta and recovery partitions in TWRP
- change the name of both files to vbmeta.img and recovery.img
(VBmeta is often 64kb big and Recovery is often 90+mb big.)
- copy and paste these new img files into the update zip.
- flash through TWRP
- go back to main menu, select advanced, then select option
"disable replace TWRP" to keep TWRP as your recovery.
for devices with "Unlocked bootloader" (not tested on A11)
-make full backup
-download zip
-install zip through TWRP
-reboot
__________________________________________________________________________________
Custom Roms and Kernels
Kernel
Mattofthedead's Redmagic 5S kernel for LOS and Stock roms LINK
Roms
Rom Builder Ra's Custom Roms - Please post any bugs or issues in the related threads.
Pixel Experience Plus
Ressurection Remix
NOTE : to boot any Custom rom on the 5S device. Flash the Rom following the directions. then flash Matts LOS kernel Version 3
__________________________________________________________________________________
------------------------------
Old roms
Android 11
V8.65 Nubia Link MD5: 3d52e18c66366d3d23744184425d3926
V8.64 Nubia Link MD5: a7e61f5e2f7c377a6850cf6ac3a62aa7
V7.65 Nubia Link MD5: 746dad5b6145dfba1108355095a6ad46
V7.64 Nubia Link MD5: 55371ee8e5728aee2bc7df5b3a7d6585
V9.42 Nubia Link MD5: D492B92DD83B366508CDD74DE7D152A3
V9.40 Nubia Link MD5: D28F26289A9B75F771EF4F623F0BB367
V8.57 Nubia Link MD5: 266819d4b09c2c52aadb39e948dc84bc
V8.59 Nubia Link MD5: d7e32b7a3e833adc57fcf734aa47f5a3
V7.57 Nubia Link MD5: 81ee71869f660a28b631d871ffb59524
V7.60 Nubia Link MD5:
V9.26 Nubia Link MD5: 8997375CD97D8F7F261F21121FC8EFAA
Android 10
v6.18 Link MD5: 9AC5EA5F64835C1995E4A81D4973FB71
V6.13 Link MD5: F38ED2D7CB58252D308B29D1D4517DB9
V7.07 Link MD5: ffc3fdaf4afc522aa3a084d9275f2cb6
V7.14 Link MD5: 0f879160fbf8b556de5303207b93d0d1
V8.07 Link MD5: b30dab221be73292c5da7884afc0363f
V8.11 Link MD5: 85d9366a3017112cb68d66041e725ce6
________________________________________________________
Personal Mirror - Located in Eastern Canada
________________________________________________________
TWRP and root guide for 5S and 5G on Android 10 only - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked during and after process is complete.
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put an installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file found at the end of this post
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted. (CD = Change Directory)
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable replace TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Reboot to system for the first time and complete the initial setup. this is to create the user space partitions data/media ( preferably do not make a pin or pattern at this stage)
13. once in the rom, connect to PC and copy over the Magisk zip to the internal memory. then reboot holding Volume up
14. once back into TWRP (if you created a pin during setup TWRP will ask you for your pin to access data) go into install and flash the Magisk.zip you moved in step 13 then reboot. once back into the rom, you will see a Magisk app, tap it and allow to update, the APK will install latest version of the manager.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have an update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini - zip updated with Magisk 21.4 zip
MD5 for ADBfastbootmini.zip: 0ad97a9ae1539b26ef78c849b169e807
I'm working on a process that will update to Android 11, through TWRP and root, without losing data. Much like a stock update.
I will update the thread once my tests are complete.
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
josehdx said:
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
Click to expand...
Click to collapse
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Patrick Morgan said:
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Click to expand...
Click to collapse
Thanks
Working fine after full data partition wipe.
I have an additioal question regarding further updates, and i would not want to open a new topic. so, after flashing the zip, i "lost" TWRP but i already have root access. I wonder if is possible to flash upcoming updates with the default recovery built in on the phone, if not, i would assume i need to install TWRP again.in any case, will side loading update make any problem with the current system? i hope my question and context is clear
As these are official ROMs, they will replace the recovery and remove root from the phone.
If you do not have root, flashing these zips from the system menu local update should work. But if you have root or TWRP it's better to flash through TWRP.
You could just flash TWRP again after flash, but I personally modify the zip and add the recovery to it to save me going into fastboot after each update.
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Darkvenum79 said:
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Click to expand...
Click to collapse
I've spoken with another EU rom user, that has the same issue before. it seems it was an error in the stock rom.
reinstalling 7.07 from the links above should fix your problem.
both 7.07 (the EU rom) and 8.07 (the US rom) are exactly the same. the only difference is the languages from what I can tell.
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
No it wont.
There is a specific step by step that is required to get it functioning again. And it only survives until your next full wipe, which i assume you will do more often flashing non official roms.
I can grab the steps and edit this post for you.
Edit -
Prep.
have a black / very dark brown leather. (belt, wallet, etc)
a soft gel plaster / Bandaid
(something skin textured and in a pink / light beige colour) texture and colour are important.
First step is clear data in the infingerprint app in app info and remove permissionfor data memory - (you need to show system apps to find it)
- digit in call phone code:
*#9959#
(android 11 use Activity launcher (playstore) to enter fingerprint menu)
- uncheck performance checkbox , check only calibration checkbox
Steps -
1. Press start then wait.
2.Press next and with plaster / bandaid press on circle
3.Press next and use wallet / belt ( the display becomes black for black calibration)
4.Press next and use gel plaster / bandaid again but pinch it in so only the part with your finger touches the circle.
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access to data memory then reboot device.
Enjoy your Finger Print once more!
P.S. = do this procedure in a very dark room to improve the chances of it succeeding.
Thanks to qtr1st (Salem) and mikekrunk (Mike) for the steps and information.
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Patrick Morgan said:
TWRP and root guide for 5S - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked after process is complete.
Pretty short step by step to get twrp and Magisk if you want, on your phone. (Red Magic 5S)
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put a installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file attached or mirrored
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted.
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have a update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
where is the link of twrp.img
sansha1211 said:
where is the link of twrp.img
Click to expand...
Click to collapse
Patrick Morgan said:
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
that file called Link ADBmini has all you need
Is it ok to flash Eu rom to my NA/asia rom?
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
reboot to bootloader by... power off device -> press and hold volume down and power button until you see the logo -> connect device to your computer then do the steps 7 to 12
also once you are in TWRP make sure you ... this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
if you have not removed your pin before flashing any of the roms. it asks you for YOUR own pin that you made when you setup the phone. so use your own pin.
the process of rooting your device, clears a security partition. (the VBmeta partiton)
this deletes the encryption you had on your phone. so the devices partitions are unaccessable and need to be wiped before you can boot to system.
you need to clear data. all data. then check in TWRP file browser if your data partition is clear. .. if you see folders with random letters its not been formatted correctly.
so, in the wipe menu on TWRP you should go into advanced and change the partition type to ext4 then back to f2fs to clear the partition of data.
once your phone is clear you should be able to wipe cache and davik then reboot to system for it to start like a factory reset.
sansha1211 said:
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
where is the link of twrp.img
Click to expand...
Click to collapse
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing lock
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
via cmd -- fastboot flashing lock
After i reboot in TWRP and disable replace TWRP, i install magisk from a USB otg, and then i wipe all data, then i reboot system but it keeps opening TWRP in every reboot, i had to install Stock Rom to have my phone back but without root, what im doing wrong?? thanks
Edit: now it worked, tried a few times and worked don't know what failed