[Guide] Honor 8 Oreo stock EMUI upgrdade. - Honor 8 Guides, News, & Discussion

I guess this is a bit late for a proper upgrade thread with a proper guide, but better late than never. I have an FRD-L02 and I'm using 8.0.0.513(C675) without any major problems. Without further ado, here's how I did it. Make a full backup before you start.
Perquisites
1. Unlocked bootloader. Huawei doesn't provide the codes now but you can still get them using DC Unlocker.
2. TWRP. Use this link - http://https://mega.nz/#!8xcyWTyT!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
3. Firmware files - Use Firmware Finder from TeamMT. I downloaded them on PC. Makes life easier. You'll need to download three files -
i.update.zip
ii.update_full.zip (this can vary)
iii.public.zip
The links vary for different models so I'm just giving you a rough idea. If you are on PC you can just check in the common base for your device.
4. HuRU updater - Use version 0.4 http://https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
5. Stock EMUI recovery - Extract the update.zip and use HuaweiUpdateExtractor to extract recovery.img from update.app. Make sure verify header checksum is unchecked.
6. SD card or USB-otg to load the files.
7. A PC :laugh:
The guide :
USB or SD card prep
1. Rename the following files -
i. update.zip remains same
ii. update_full_FRD-L02_channel_in.zip becomes update_all_hw.zip
iii. update_data_full_public.zip becomes update_data_public.zip
2. Make sure all the following files are in one folder -
i. HuRUpdater_0.4
ii. recovery.img (this is stock EMUI recovery)
iii. update.zip
iv. update_all_hw.zip
v. update_data_public.zip
Flashing firmware
1. Reboot to bootloader and ensure that you have at least 80% battery along with Phone and FRP unlocked.
2. Enter the following commands -
fastboot erase userdata
fastboot erase system
fastboot flash recovery_ramdisk twrp.img or fastboot flash recovery twrp.img (depends on current android version)
fastboot reboot
3. Immediately press and hold volume up so that you boot into TWRP.
4. In TWRP, you'll probably get errors if you try and wipe straight away. Do a factory reset and reboot directly back into TWRP.
5. Do the necessary wipes - Dalvik, cache, system, data, internal storage. I was able to avoid many errors when I did a complete wipe.
6. Go the folder we prepped earlier and run HuRUpdater_0.4.zip. You'll have to press volume down to start flashing.
7. It'll take a while and after it's done boot into the system.
8. This method removes TWRP once you boot into the system and we are now on stock recovery. You will most likely encounter a bootloop on first boot. Don't worry, simply press and hold the power button to
power off and immediately press and hold the volume up button once the screen goes off to enter recovery.
9. Perform a factory reset by following the steps on the screen. Reboot!
10. You're done. Voila. Enjoy.

Related

[GUIDE] Upgrade to jelly bean super easy way (works for US varients, might for other)

Hello,
my tablet has a unlocked bootloader and was on 4.0.3 stock rooted when i did this and thought i would share how i did it, its really fast and easy.
Disclaimer: i am in no way responsible for a bricked or damaged devices, world endings, zombie attacks from using this guide. use at your own risk
Requirements: rooted with a custom recovery and unlocked bootloader. (i used CWM) a tf300t tablet
Recommended: doing the file transfers from pc to device as you go along
Step 1: get all the files you need download
****Version V9.4.3.30 make sure us download the file for US SKU
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
****Version V10.4.2.9 make sure to download the version for US SKU
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Step 2: get the first file ready by unzipping (US_epaduser9_4_3_30UpdateLauncher) so it extracts a zip file called (US_epad-user-9.4.3.30)
-place (US_epad-user-9.4.3.30) on the internal storage of your device.
Step 3: boot into recovery and wipe data/factory reset, wipe dalvik cache
-then flash the file US_epad-user-9.4.3.30.zip in recovery
-reboot device
Step 4: one device is rebooted and past the set up screen delete US_epad-user-9.4.3.30.zip off your internal storage (DO NOT INSTALL A CUSTOM RECOVERY AT THIS POINT)
Step 5 getting jelly bean ready: unzip (US_epaduser_10_4_2_9_UpdateLauncher) so it extracts a file called (US_epad-user-10.4.2.9)
- at that point a triangle with a exclamation point in the middle should appear saying system update file detected
(that same icon and message might pop up while the (US_epad-user-9.4.3.30) is on the internal storage ignore it then, this is why we delete said file before we put the (US_epad-user-10.4.2.9) file on the device)
Step 6: click on the triangle icon on your device and accept the update, your device will reboot and install jelly bean (should take 10 to 15 minutes be patient)
---Once the device reboots it will upgrade and you will be on jelly bean yay
To obtain root follow part 3 of this thread ( http://forum.xda-developers.com/showthread.php?t=1845377) i will put the intructions here below for those to lazy to click the link
all thanks for rooting instructions go to krabappel2548 thanks man.
rooting and custom recovery
files needed for this process
fastboot and recovery http://www.mediafire.com/?1u44b0w3k1qoy4r
root files: http://www.mediafire.com/?cr209hb5e2fr910
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files: Root Files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
hope this helps everyone
I Just followed this method with WW-files, works like a charm
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Thanks a lot, so happy I could help someone
Sent from my Galaxy Nexus using xda app-developers app
Deleted

Return to stock Bell

Hey xda! I was having trouble restoring my M7_UL to Bell Mobility stock OS, but with the help of the amazing people here on XDA, I have figured it out. here are the steps I took to restore from insertcoin back to stock:
1. download this TWRP backup: https://onedrive.live.com/redir?resid=61A88C96DFA8F691!624&authkey=!AC-6BqgL8HcbwjU&ithint=file,zip
2. download the matching firmware: https://onedrive.live.com/redir?resid=61A88C96DFA8F691!623&authkey=!ALE6X9YofxVQr8A&ithint=file,zip
3. download lastest TWRP: http://teamw.in/project/twrp2/164
4. reboot to bootloader, select fastboot, flash TWRP (fastboot flash recovery TWRP.img)
5. Boot into TWRP and backup just the boot, this way it will create the folder on your sd card with the correct name, otherwise backup won't show up
6. reboot into android. copy contents of TWRP backup to the folder created on your sd card
7. reboot back into TWRP. hit restore and wait for it to finish
8. reboot back into bootloader. select fastboot and boot into RUU mode (fastboot oem rebootRUU)
9. flash the firmware (fastboot flash zip 3.23.666.1.zip)
10. firmware flash will stop part way. this is normal. run the exact same command again and it will finish properly this time.
11. reboot back to bootloader (fastboot reboot-bootloader)
12. verify firmware has been flashed correctly (fastboot getvar all)
13. reboot, and take the OTA updates if you wish
14. this is where my instructions end. to finish restoring to 100% stock, follow this guide here, starting from removing the tampered flag: http://forum.xda-developers.com/showthread.php?t=2358738
I hope this helps!

[Guide] Procedure with Video to Return from Oreo Beta to Nougat step by step

Hello everyone, I leave here step by step how to return from Oreo Beta to Nougat along with a video that I made with the process step by step, greetings.
NOTE: THIS PROCESS WAS TESTED AND WORKS, IT MUST BE CLEARED THAT THIS PROCESS IS UNDER YOUR RESPONSIBILITY, IF YOU FOLLOW THE STEPS YOU WILL NOT HAVE ANY PROBLEM, ONLY YOU ARE RESPONSIBLE FOR BRICK.
COMMUNICATION GIVEN BY THE COMPI @kacarot, "ONLY YOU ARE RESPONSIBLE FOR YOUR TELEPHONE"
Look to read by xda and in androi hilfe who are warning that this system is dangerous and that there is a step where you can produce the brick .... I have only read a case of brick (recovered with fh) but several cooks insist on warning the risks ..... From what I read the failure can be given to clean data from twrp and copy the new oeminfo ... There may fail ....
Perhaps it would be prudent to notice well that in the mentioned forums they are withdrawing the instructions ...
COPIO flashdance user post very advanced
It is not advisable for any fan to do it! The trick with dd if =
is that you have to delete the data before in the TWRP to obtain a "normal file structure". You can verify that in the installation. Only if there are no numbers / combinations of letters can you be in Advanced in the TWRP with cp .... and dd if = make and wait until you have finished exchanging the message. Only then can you turn it off and then with VOL + / VOL- and Power of the SD starts the update and waits until it finishes. Then the HWOTA arrives at Zug. Yes, that's just with this rom and the dload folder in the root directory of the SD.
TELEPHONE PREPARATION
1. Activate OEM unlocking
2. Enable USB debugging
3. Have installed the Minibus ADB Fastboot 1.4.2 link download: https://drive.google.com/file/d/0B5MSGGCOoMjiTFE5RHlaOWFvOVE/view?usp=drivesdk
4. Copy to the folder where the Minimal ADB FASTBOOT was installed the TWRP OREO link download: https://drive.google.com/file/d/0B5MSGGCOoMjial94VHVzVnNVSGc/view?usp=drivesdk
5. download the rom MHA-AL00C00, unzip it and the dload folder that we have left to save it in the root of the SD link rom card: https://mega.nz/#!lYIhhDqY!I8lrCig3x2MMTHINZOvwVmhYDX2vz9QWb6V9epA6JI4
6. Download the file MHA-AL00C00.bin and save it in the root of the SD link card oeminfo: https://drive.google.com/file/d/0B5MSGGCOoMjiSUdZQmJQdzNIRUU/view?usp=drivesdk
DOWNGRADE PROCESS
1. Unlock the bootloader.
2. Enter the folder where you have installed the ADB Fastboot Minimal, press the shift key + right click and choose to open the command window here.
3. While in the command window we proceed to install the OREO TWRP with the following command: fastboot flash recovery_ramdisk twrp-oreo.img
4. Once the OREO TWRP is installed, we enter it with the button (volume up + power), the Huawei logo comes out and we release the power button.
5. Being in the TWRP we go to the option ADVANCE and in this we select the option TERMINAL where it opens a window to place the following commands which install the oeminfo saved in the SD the MHA-AL00C00.bin
cp /external_sd/MHA-AL00C00.bin /tmp/oeminfo.bin and they give the blue button of the keyboard to confirm it.
dd if = / tmp / oeminfo.bin of = / dev / block / sdd5 bs = 1048576 and they give you the blue button on the keyboard to confirm it.
After entering the two commands, we go back to the TWRP and look for the option to turn off.
7. With the phone completely turned off we proceed to install the ROM MHA-AL00C00 which is in the dload folder, press the three buttons at the same time (volume up + volume down + power) until the installation of this one.
If everything was done to the letter the phone should restart and turn on normally with the ROM MHA-AL00C00 installed, and after performing this process, you can re-perform the model and rom you want.
TIP: When doing the rebrand again for the change of ROM, perform the procedure twice selecting REBRAND so that the change of ROM can remain because once it is compiled in TEST KEYS NRD-900M, this I say as experience from someone who has already performed this procedure twice.
Link Video: https://www.youtube.com/watch?v=TtRD8g5n2_U#action=share
http://www.htcmania.com/showthread.php?t=1362900
Thanks to the creators of this method since without them this would not have been possible.
This procedure really helped when i was stuck while upgrading to Oreo. Especially the part where u need to load TWRP for oreo and then you are able to flash the oeminfo.bin file..
Thanks a million
ernest2728 said:
Hello everyone, I leave here step by step how to return from Oreo Beta to Nougat along with a video that I made with the process step by step, greetings.
NOTE: THIS PROCESS WAS TESTED AND WORKS, IT MUST BE CLEARED THAT THIS PROCESS IS UNDER YOUR RESPONSIBILITY, IF YOU FOLLOW THE STEPS YOU WILL NOT HAVE ANY PROBLEM, ONLY YOU ARE RESPONSIBLE FOR BRICK.
COMMUNICATION GIVEN BY THE COMPI @kacarot, "ONLY YOU ARE RESPONSIBLE FOR YOUR TELEPHONE"
Look to read by xda and in androi hilfe who are warning that this system is dangerous and that there is a step where you can produce the brick .... I have only read a case of brick (recovered with fh) but several cooks insist on warning the risks ..... From what I read the failure can be given to clean data from twrp and copy the new oeminfo ... There may fail ....
Perhaps it would be prudent to notice well that in the mentioned forums they are withdrawing the instructions ...
COPIO flashdance user post very advanced
It is not advisable for any fan to do it! The trick with dd if =
is that you have to delete the data before in the TWRP to obtain a "normal file structure". You can verify that in the installation. Only if there are no numbers / combinations of letters can you be in Advanced in the TWRP with cp .... and dd if = make and wait until you have finished exchanging the message. Only then can you turn it off and then with VOL + / VOL- and Power of the SD starts the update and waits until it finishes. Then the HWOTA arrives at Zug. Yes, that's just with this rom and the dload folder in the root directory of the SD.
TELEPHONE PREPARATION
1. Activate OEM unlocking
2. Enable USB debugging
3. Have installed the Minibus ADB Fastboot 1.4.2 link download: https://drive.google.com/file/d/0B5MSGGCOoMjiTFE5RHlaOWFvOVE/view?usp=drivesdk
4. Copy to the folder where the Minimal ADB FASTBOOT was installed the TWRP OREO link download: https://drive.google.com/file/d/0B5MSGGCOoMjial94VHVzVnNVSGc/view?usp=drivesdk
5. download the rom MHA-AL00C00, unzip it and the dload folder that we have left to save it in the root of the SD link rom card: https://mega.nz/#!lYIhhDqY!I8lrCig3x2MMTHINZOvwVmhYDX2vz9QWb6V9epA6JI4
6. Download the file MHA-AL00C00.bin and save it in the root of the SD link card oeminfo: https://drive.google.com/file/d/0B5MSGGCOoMjiSUdZQmJQdzNIRUU/view?usp=drivesdk
DOWNGRADE PROCESS
1. Unlock the bootloader.
2. Enter the folder where you have installed the ADB Fastboot Minimal, press the shift key + right click and choose to open the command window here.
3. While in the command window we proceed to install the OREO TWRP with the following command: fastboot flash recovery_ramdisk twrp-oreo.img
4. Once the OREO TWRP is installed, we enter it with the button (volume up + power), the Huawei logo comes out and we release the power button.
5. Being in the TWRP we go to the option ADVANCE and in this we select the option TERMINAL where it opens a window to place the following commands which install the oeminfo saved in the SD the MHA-AL00C00.bin
cp /external_sd/MHA-AL00C00.bin /tmp/oeminfo.bin and they give the blue button of the keyboard to confirm it.
dd if = / tmp / oeminfo.bin of = / dev / block / sdd5 bs = 1048576 and they give you the blue button on the keyboard to confirm it.
After entering the two commands, we go back to the TWRP and look for the option to turn off.
7. With the phone completely turned off we proceed to install the ROM MHA-AL00C00 which is in the dload folder, press the three buttons at the same time (volume up + volume down + power) until the installation of this one.
If everything was done to the letter the phone should restart and turn on normally with the ROM MHA-AL00C00 installed, and after performing this process, you can re-perform the model and rom you want.
TIP: When doing the rebrand again for the change of ROM, perform the procedure twice selecting REBRAND so that the change of ROM can remain because once it is compiled in TEST KEYS NRD-900M, this I say as experience from someone who has already performed this procedure twice.
Link Video: https://www.youtube.com/watch?v=TtRD8g5n2_U#action=share
http://www.htcmania.com/showthread.php?t=1362900
Thanks to the creators of this method since without them this would not have been possible.
Click to expand...
Click to collapse
What if we don't have SD card support. Mate 9 Pro with dual SIM. Is it possible to modify command as external OTG?
Metallica&Manowar

5S/5G Roms and Root Mega thread [Updated November 2022]

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

At my wits end

So I'm trying to get Magisk installed on my bootloader/OEM Unlocked S10+ (SM-G975F beyond2lte) device.
I can do that fine by downloading the latest official firmware for my device, installing that (BL/AP/CP/CSC) through Odin v3.14.
That installs fine.
Then I sideload Magisk v23.0, and the AP file I just flashed via Odin over adb via push.
I install Magisk, recovery-patch the AP file, usd adb to pull the file back over onto my desktop. I restart the phone in download mode and once again populate Odin with the BL/AP/CP/CSC files, but this time the AP file is the one I got from Magisk.
Start that, let Odin restart my phone whilst I'm holding Bixby/Power-Up/Power, I release those three once the bootloader warning message comes up.
I set the phone up like normal, but there's the issue - my 128GB device only reads as having 32GB - I can setup Magisk fine, it asks me to download an extra bit, then auto-restarts the phone after 5 seconds.
Yay, I have root! Boo, I'm missing 96GB of free space...
I've read that installing TWRP can help fix this, fair enough, I try to install TWRP (I've tried through both the "dd" method via adb shell, and patching the twrp 3.5.2_9-3 via Magisk, and installing with vbmeta over Odin), but that then eliminates Magisk.
I've been trying this now for days, literally days, reading through different forum posts, detailing my steps to myself in notepad++ step-by-step so I can see what it is I'm doing.
I'm left with zero clue what to do now except reach out and hope for some help from this forum.
Should have known... Now that I've posted on XDA it's fixed... In-case anybody else is having trouble here are the steps I've written down for myself.
Phone is S10+ SM-G975F (beyond2lte) - Bootloader / OEM Unlock is already unlocked.
******************************************************************
FLASHING STOCK ROM (ALWAYS GOOD PLACE TO START):
******************************************************************
1. Phone into Download mode (Vol Down + Bixby button, insert USB (Don't use power button))
2. Odin, AP in AP, BL in BL, CP in CP, CSC in CSC (NOT the HOME one). USERDATA stays EMPTY!
3. Phone may restart/erase several times, in the end inbuilt recovery will turn up. Use this to factory reset.
4. Wait for it to continue like normal after factory reset.
5. Setup INCLUDING with WiFi. WiFi REQUIRED. No need to add your account
6. Make sure OEM Unlock is still checked.
*************************************************************************************************
ROOT INSTRUCTIONS: https://www.thecustomdroid.com/samsung-galaxy-s10-root-guide/
*************************************************************************************************
1. Use adb push to shunt over Magisk Manager (download latest one), and the "AP" file
2. Install Magisk Manager
3. Open, select install, make sure "Recovery" is ticked, next, select "Select and Patch a File"
4. Select the AP file, then click "Let's Go"
5. Use adb pull, as the MTP file transfer ****s up the large patched files Thanks Microsoft!
6. (adb reboot bootloader) Restart phone in Download mode
7. Open Odin, & flash the patched Magisk AP file in AP, BL in BL, CP in CP, CSC (NOT the HOME one) in CSC.
8. Let device reboot while holding POWER, BIXBY, and VOL UP, and release all 3 buttons on bootloader warning screen.
a. NOTE: If you end up with a bootloop, hold POWER, BIXBY, VOL UP until you enter the built-in recovery menu, and do a factory reset.​
9. Set device up like normal, remember to enable the WiFi
a. Check device internal storage, should be XXX out of 128GB (Or whatever you have)​
10. Search installed apps for the Magisk one, it won't have a proper icon to begin with
11. Open it, and continue the setup as it instructs. It’ll reboot the phone.
12. Device is now rooted.
********************************************************************************************
TWRP INSTRUCTIONS: https://www.thecustomdroid.com/samsung-galaxy-s10-twrp-magisk-root-guide/
********************************************************************************************
Phone must be rooted for this to work!
1. Copy the un-magisked file "twrp-3.5.2_9-3-beyond2lte.img" onto phone
2. Open Magisk, select install, make sure "Recovery" is ticked, next, select "Select and Patch a File"
3. Patch the "twrp-3.5.2_9-3-beyond2lte.img" file
4. Copy that patched file onto your PC, and rename it magisk_patched.img
5. Open powershell in same folder, and type
a. mv magisk_patched.img recovery.img​b. tar cf twrp-beyond2lte.img.tar recovery.img​
6. Enter into Bootloader mode
7. Load up Odin, untick auto-reboot, and put the magisk-patched TWRP.tar file in AP
8. Press PWR and VOL-DOWN to exit Download Mode, as soon as screen goes black, switch to PWR, BXBE, VOL-UP, release PWR & BXBE when you see bootloader warning, keep VOL UP
9. In TWRP, swipe to allow modifications
10. Flash multidisabler-samsung.zip
11. Go to wipe - format data - yes, after go back to TWRP home screen
12. Click Reboot > Recovery (NOT SYSTEM), you now have a TWRP enabled device.
13. Reinstall Magisk, and check root status, it should ask you to do the whole re-download/5 second reboot thing because you did the wipe > yes thing in TWRP.
UPDATE: After restarting my phone I lost root (Magisk was still installed, but it didn't have an "installed" version listed). To get past this I...
*************************************************************************************************************************
Magisk reinstallation via TWRP:
[ROM][Signature Spoofing]LineageOS 18.1 for S10E/S10/S10+ Exynos
oHello my friends, please someone could make a video to activate root? I can't even do it with the key combinations... Please help me I can't get into the bank apps :(
forum.xda-developers.com
*************************************************************************************************************************
1. Copy the "beyond2lte-boot-magisk.img" onto phone (see URL above)
2. Run Magisk, patch the "beyond2lte-boot-magisk.img" file, then copy it over onto your MicroSD (I just find it easier)
3. Boot into TWRP > Install > Install Image button (Bottom Right)
a. If TWRP has vanished, follow steps above to get it back​
4. Flash the patched file to "Boot"
5. Go to TWRP Home screen > Reboot into Recovery (not into System)
6. Check Magisk Manager should have Root again (Don't update Magisk via app though, or you’ll bollocks the whole thing up, and have to start all over from the start.)

Categories

Resources