Database Info

Guide to get URDLV (Root De La Vegas) working

A lot of people were having issues with designgear's instructions on rooted their official roms.
Please read this guide (link below) first if you have no experience with this URDLV rooting method (a root method that avoids triggering KNOX counter).
http://www.theandroidsoul.com/universal-root-de-la-vega-script/
Here's a set of steps that worked
------------------------------------------------------------------
To URDLV your offical ROM (worked on MF4)
Some Assumptions:
1.) Snapdragon Processor
2.) Current Bootloader on your phone, MJ1 or lower. If higher, you'll likely trip KNOX
3.) Reactivation Lock = Disabled
Procedure:
Applying URDLV to Official ROM:
- Install Cygwin (64bit or 32 bit depending on your OS)
- Started the Cygwin terminal
- cd'ed to proper drive and URDLV folder
-----ie: cd urdl
- chmod +x URDLV.bat
- ./URDLV.bat full c:/URDLV/blahblah....tar.md5 (drag-n-dropped the path to the file)
-----this will take a while on regular HD
The following steps are folked into two alternate methods.
Method 1 can work for MF4, because it seems to work with the MF1 files, so not uploading the accompanying files from the official MF4 rom neglected by URDLV's process can work.
Method 2 is more complete, and includes the uploading of all files EXCEPT the bootloader, this should minimize any mismatches of files causing issues.
Method 1: Upload only System and Cache First, other files individually
-Use ODIN to send the file over to Phone (follow designgear's OP instructions)(or PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/ )
-Put the root files on the phone
Extra Reading (optional):
- follow designgear's OP instructions
- PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/
-----extract root_de_la_vega_sdcard.zip
-------- root_de_la_vega.sh (file)
-------- root_files (folder)
-----put into the directory: \sdcard
-Reboot
-Delete the Root files
-Reboot
-Extract the Modem.bin and NON-HLOS.bin file from the Official ROM (optional for MF4) (some later roms REQUIRE matching NON-HLOS.bin and MODEM.bin files)
-----these files were excluded by URDLV's output ROM (for reasons unknown with other ROM version, but the NON-HLOS.bin and modem files from MF4 seem to integrate fine)
-Use ODIN to send Modem.bin and NON-HLOS.bin to the phone via CP slot
If for some reason your WiFi passwords keep getting forgotten:
http://forum.xda-developers.com/showthread.php?t=2522629
-Done
Method 2 (which includes all files except the bootloader):
1.) Extract the System.img and Cache file FROM the URDLV tar.md5 TO [Folder]
--------You could use 7Zip
2.) Extract all files EXCEPT ABOOT and Cache file FROM the Official ROM TO [Folder]
3.) Now [Folder] should contain 10 files
4.) Tar up those files in [Folder].
----In Cygwin:
Change directory to the [Folder]
Enter the following commands to tar up your files into a TAR.MD5 file:
tar -H ustar -c *.* > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
How your TAR.MD5 should look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.) Send your your_odin_package.tar.md5 package via ODIN (AP Slot) to your phone
6.) -Put the root files on the phone (follow designgear's OP instructions) (or PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/ )
-----the directory: \sdcard
-Reboot
-Delete the Root files
-Reboot
If for some reason your WiFi passwords keep getting forgotten:
http://forum.xda-developers.com/showthread.php?t=2522629
-Done
------------------------------------------------------------------------------
For future rom updates (applicable to rooted users):
Reports claim that Mobile Odin works: http://forum.xda-developers.com/showthread.php?t=2522729
-------------------------------------------------------------------------------
Download Links in case if needed:
Working link:
https://mega.co.nz/#!co1jRKYY!p94iENAmHkqd9wD3c0T1qC_dz03o7n8xmmkuIiVxCLQ
OLD DELETED:
Universal RDLV script (v0.2)
https://mega.co.nz/#!ugJFUTCL!NrME135Mia6-x4e0E-21uQXmh8wMbhrksHG0HjTtg4g
Root de la Vega sdcard files
https://mega.co.nz/#!qoQnmAQD!U_dQMRsZ7UFMpEicnnGIFAtvn7V6Ti_gbyPDt9TDmmY
Odin v3.09
http://filecloud.io/cp43ua5j
Sammobile Firmwares
http://www.sammobile.com/firmwares/

Good guide m8 if I may tell you something to put in top of everything and This is that URDLV works only in mj1 bootloader and below, if with any way you have updated with OTA/KIES/SERVICECENTER or bought with mj3 and above you cannot use any of Vega ways.
Sent from my SM-N9005 using Tapatalk

You should write that old bootloader is needed and you should modify the process : boot, hidden and recovery images should be added to the tar

geek78 said:
You should write that old bootloader is needed and you should modify the process : boot, hidden and recovery images should be added to the tar
Click to expand...
Click to collapse
Are there any risks to triggering KNOX by integrating those files ?
I thought we don't want the boot file beyond mf1 since it makes it impossible to root without triggering KNOX later?
Figure there are reasons why designgears neglected to include those files.....

klau1 said:
Are there any risks to triggering KNOX by integrating those files ?
I thought we don't want the boot file beyond mf1 since it makes it impossible to root without triggering KNOX later?
Figure there are reasons why designgears neglected to include those files.....
Click to expand...
Click to collapse
No it won't as those are not the bootloader. I made a URDLV system image of MJ7 and added all the other files from the original rom (MINUS aboot --> bootloader) and flashed with odin. Got root and knox counter not tripped. :good:

Nice, I dont feel like uploading the system image again (and reroot), just to get the other files in.
Can I just tar.md5 up the left over files and Odin them in?
If so, which Odin slot?

klau1 said:
Nice, I dont feel like uploading the system image again (and reroot), just to get the other files in.
Can I just tar.md5 up the left over files and Odin them in?
If so, which Odin slot?
Click to expand...
Click to collapse
Yes you can just tar.md5 the rest and flash it. Not really sure where to place it but you can try ap or wait for others to reply.

Yes, I tar.md5 them up and ODIN them up from the AP slot.
It works

Was this thread moved over the General?
If not, could a MOD please move it over to Original Development where the URDLV thread also resides?
Thanks,

klau1 said:
Was this thread moved over the General?
If not, could a MOD please move it over to Original Development where the URDLV thread also resides?
Thanks,
Click to expand...
Click to collapse
Guides don't go in Development threads.

@klau1
Can you remove the download links please and link to the thread. I am going to be updating soon and don't want you to have dead links or links to older versions up. Thanks.

This guide will NOT work and brick your camera and wifi (did for me)
Real solution: http://forum.xda-developers.com/showthread.php?p=47390175
@klau1 u are allowed to copy my guide if you put my name on the op
My guide is 100% working for me 0x0 root camera wifi dmj7
Sent from my SM-N9005 using XDA Premium 4 mobile app

It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
In the case of mj7, the other files designgears urdlv neglected to include are required.
@designgears Let me know once you've updated your guide so I can update and reflect the changes here thanks.

Hi all!
I own SGN 3 with exynos octa processor.
Versions of installed firmware:
AP: N900XXUBMJ1
CP: N900XXUMI2
CSC: N900OJVBMI5
Can I root this device with URDLV method without any problem with KNOX and warranty?
Can I update firmware in the future with KNOX trigger = 0x0 and so on?
Thanks.

No, UDRLV only works with Snap Dragon version.

klau1 said:
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
I thought it didn't work on any bootloader under MJ1?
If it does work on MJ4, I'm on N900W8OYABMJ4 (Rogers Canada), which method would work best for rooting it.
Thanks! Sorry for being a noob:crying:
Click to expand...
Click to collapse

SimerToor said:
klau1 said:
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
Click to expand...
Click to collapse
I thought it didn't work on any bootloader under MJ1?
If it does work on MJ4, I'm on N900W8OYABMJ4 (Rogers Canada), which method would work best for rooting it.
Thanks! Sorry for being a noob:crying:
Click to expand...
Click to collapse
If the phone is ALREADY on MJ4 it's impossible to root with the current URDLV.
This method requires you to START OFF with MJ1 ROM because once your phone already has been upgraded beyond MJ1, the newer bootloader can detect changes in the URDLV rom and trigger KNOX.
Whereas the bootloader in MJ1 can be exploited.
You can't factory reset the bootloader back to MJ1 after you've upgraded AFAIK.

efs safe?
Hi,
Is the efs partition safe when flashing all those files ?
Could it be overwritten ?
Thx.

Masterz said:
Hi,
Is the efs partition safe when flashing all those files ?
Could it be overwritten ?
Thx.
Click to expand...
Click to collapse
100% safe
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app

Frickin amazing. Worked perfectly on my T-Mobile Note 3. No flag tripped, have root, will party. Had to use Cygwin to do it BTW.

Firmware Huawei Honor 9 STF-L09 - Stock service full rom

Update Instructions:
Normal update dload/update.app [Main firmware file]
Copy required vendor pack Example : [/dload/venrod/update_****_hw_eu.app] after rename the file in update.app
Update dload/update.app [Required vendor file]
Manually reset
Retry Normal update dload/update.app [Main firmware file]
Enjoy
Service repair firmware [ Скачать / Download ]
File: STF-L09 C185B140 Saudi Arabia Iran Iraq United Arab Emirates Android 7.0 EMUI 5.1
Model: STF-L09
Build Number: C185B140
Vendor: [ hw/meafnaf ]
Country: [ Saudi Arabia Iran Iraq United Arab Emirates ]
Service repair firmware [ Скачать / Download ]
File: STF-L09 C10B130 Russian Federation Android 7.0 EMUI 5.1
Model: STF-L09
Build Number: C10B130
Vendor: [ hw/ru ]
Country: [ Russian Federation ]
Service repair firmware [ Скачать / Download ]
File: STF-L09 C432B130 Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary Android 7.0 EMUI 5.1
Model: STF-L09
Build Number: C432B130
Vendor: [ hw/eu ]
Country: [ Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary ]

5261979 said:
Update Instructions:
Normal update dload/update.app [Main firmware file]
Copy required vendor pack Example : [/dload/venrod/update_****_hw_eu.app] after rename the file in update.app
Update dload/update.app [Required vendor file]
Manually reset
Retry Normal update dload/update.app [Main firmware file]
Enjoy
Click to expand...
Click to collapse
Hi! It all seems very interesting... But could you explain what you use that for please? Tyvm.

rom europe can not be installed by twrp? thank you

HI
Copy required vendor pack Example : [/dload/venrod/update_****_hw_eu.app] after rename the file in update.app
I DONT UNDERSTAND THIS HELP

Model: STF-L09
Build Number: C432B130
its out B150

Thanks, I was able to fix the bootloop!
A few notes: the firmwares can be copied into a sdcard (at least 8gb big), as long the "dload" folder is present in the sdcard root.
Also, what the author meant with
"Copy required vendor pack Example : [/dload/venrod/update_****_hw_eu.app] after rename the file in update.app"
is that you first have to install the big UPDATE.APP, then the smaller one by renaming it UPDATE.APP and placing it inside the "dload" folder (you should rename the big UPDATE.APP into something else, to avoid overwriting it).
Then you must factory reset and install again the big UPDATE.APP.
Only then the phone will work properly.
Hope this helps.

How do you install it. Do I have to hold 3 fingers when rebooting?
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Sephiroth1311 said:
Thanks, I was able to fix the bootloop!
A few notes: the firmwares can be copied into a sdcard (at least 8gb big), as long the "dload" folder is present in the sdcard root.
Also, what the author meant with
"Copy required vendor pack Example : [/dload/venrod/update_****_hw_eu.app] after rename the file in update.app"
is that you first have to install the big UPDATE.APP, then the smaller one by renaming it UPDATE.APP and placing it inside the "dload" folder (you should rename the big UPDATE.APP into something else, to avoid overwriting it).
Then you must factory reset and install again the big UPDATE.APP.
Only then the phone will work properly.
Hope this helps.
Click to expand...
Click to collapse
How do you "install"? 3 finger hold reboot?

Lukalion said:
How do you install it. Do I have to hold 3 fingers when rebooting?
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
How do you "install"? 3 finger hold reboot?
Click to expand...
Click to collapse
Exactly. You copy the UPDATE.APP file inside the "dload" folder on your SD and then use the Vol+, Vol- and Power reboot.

Well i did this for the b180 version and it says it failed

Lukalion said:
Well i did this for the b180 version and it says it failed
Click to expand...
Click to collapse
Edit: With Huawei firmware finder i managed to reinstall it.

Can I put this on external SD card or I must put it on intern SD?

4r44444 said:
Can I put this on external SD card or I must put it on intern SD?
Click to expand...
Click to collapse
I used the external SD Card without problems.

Hello guys,
I can't put the big UPDATE.app in my SD card by drag and and drop, how can I put the file in my SD card ? (I make a dload folder)
Thank you.

Must format your SDcard to exFAT.
Wysłane z mojego STF-L09 przy użyciu Tapatalka

and maybe use an external cardreader, not via phone, that was the solution for me

Lukalion said:
Edit: With Huawei firmware finder i managed to reinstall it.
Click to expand...
Click to collapse
How did you do that?

Xethere said:
How did you do that?
Click to expand...
Click to collapse
1. Download Firmware Finder for Huawei in the google playstore.
2. Select your phone model in the app
3. Choose yout desired firmware you want
4. Follow the instructions in the app or follow any Video guide
:good:

can i use this method with unlocked bootloader?

Sure but you'll have to be on nougat.
---------- Post added at 22:58 ---------- Previous post was at 22:57 ----------
And the sdcard MUST be EXFAT formated.

[GUIDE]: How to flash CRB7 using Odin - S8

UPDATE (27TH FEB 2018): We now have Odin v3.13.1 which is compatible with the new .lz4 compressed files referred to below in the tutorial. All the steps below are only required now if you are using a version of Odin older than 3.13.1. It is recommended that you use this new version to save yourself the hassle.
Odin v3.13.1 - XDA Link
S8 G950F / G950FD (F ROMs work on the FD variants, there are no FD specific ROMs):
Mirror Link 1 (MEGA NZ) (WIPE) - Thanks @ciccio80
Mirror Link 2 (MEGA NZ) (NO WIPE) - Thanks @ciccio80
Mirror Link 3 (Google Drive) - Uploaded by me
Let me start of by saying, Samsung changed some things around with Oreo. I downloaded 'XXU1CRAP' using SamFirm today, tried with both TUR and DBT CSCs, to make sure it wasn't a bad download or anything, but Odin just wouldn't accept the file. It froze on the first step, sboot.bin.lz4.
I had never seen the .lz4 extension before, so I asked a couple of helpful lads in the Samsung Oreo Telegram group who were very helpful throughout this process.
For those of you who want to join:
http://t.me/sammyoreoclub
Samsung is using a new compression method for the Oreo ROMs, so all files within BL, AP, CP and CSC have the .lz4 extension which Odin has trouble reading, and so the flash will never go past the first step.
Note: THIS DOESN'T TRIP KNOX.
Pre-requisites:
-SamFirm to get the CRAP ROM - https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
-Windows PC
-This modded version of 7Zip which can open .lz4 files. Link - Github
-The ability to read the instructions below.
-Prince Comsy's modified Odin - Google Drive Link
-A Galaxy S8/S8+ (G950F / G950FD / G955F / G955FD) - I tested this on my own G955FD and it worked just fine.
-The XXU1CRB7 Oreo ROM for your device
-A decent amount of storage space on your PC
-Preferably some experience with flashing using Odin
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
IF YOUR INTERNAL STORAGE SHOWS AS '16 GB' AFTER FLASHING, DO A FACTORY RESET AND IT'LL RETURN TO NORMAL.
Steps below:
1. Extract the zip file for the 3.7 GB firmware file you just downloaded. Should contain 5 files, AP, BL, CP, CSC_OXM and HOME_CSC_OXM.
In the tutorial below, I will be using CSC_OXM, however that does wipe internal storage.
If you are coming from ZRA5 or just don't want to wipe your data, use HOME_CSC_OXM instead.
2. All the files will have ".tar.md5" extensions. Remove the .md5 part so they can be opened in either WinRAR or 7Zip.
AP will contain a folder called 'meta-data', userdata.img.lz4, system.img.lz4, recovery.img, boot.img.lz4
Extract all these files from AP into a new folder. Right click on each one, select the '7Zip Standard' menu and hit 'Extract Here'.
This will extract all the files within, without .lz4 extensions. So you'll have userdata, system, recovery and boot as plain IMG files.
Note: Repeat this for CP, BL and CSC_OXM.
3. Grab the original file names for the files you extracted earlier, copy paste them into notepad.
They should be in this format, make sure .md5 isn't added at the end of any filenames. Do keep in mind that the filenames for the S8 (G950F) will obviously be slightly different.
Code:
AP_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship_meta.tar
BL_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar
CP_G955FXXU1CRAP_CP8821296_CL12993656_QB16754780_REV00_user_low_ship.tar
CSC_OXM_G955FOXM1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar
4. Select all the files you extracted for AP (including the meta-data folder), right click, scroll down to the '7Zip Standard' menu again and this time hit 'Add to Archive'. Copy-paste the filename for whichever file you're creating an archive for, AP, BL, CP or CSC, make sure archive format is set to .tar and leave everything else default and hit 'OK' at the bottom of the window.
Note: This too will be have to be done for CP, CSC and BL as well.
5. Once this is done, you should have 4 .tar files ready to be flashed. Open up Prince Comsy's Odin, add each file to it's respective field in Odin.
6. Connect your device in Download Mode, press Start, and wait for the flash to be completed and for Odin to show 'PASS' at the top of the window.
Your device will reboot automatically.
ALTERNATIVELY, you can watch this very crappy screen recording I made for a better idea on how to do it.
YouTube link: https://youtu.be/eyIh3_p8WBQ
Credits go to:
@FatalONEM8 and @me2151 for helping out.
Tino Reichardt (mcmilk) for the modified 7Zip
Prince Comsy for the modified Odin.
Samsung for making flashing more and more difficult every year.
----------------------------
For Linux/Ubuntu, @kernel.killer has created a script to unpack the .lz4 compressed firmwares without having to do all of the above manually.
See this post - Link

Delete this please, im a moron
also, worked like a charm for me

Odin stuck File Analysis

Worked like a charm. Thanks a lot dude

s
It works perfectly!, finally I have Oreo from a clean installation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I uploaded the files with the extraction process done (.lz4) in Google Drive but I can not publish it because I'm new, If someone wants it, you can ask for it through PM.

Works! Thank you so much!

WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!

Currently CRAP file is one and the same for the Nordic Countries, Spain, France, Germany, Turkey, Poland found on Sammobile.com ?
Tnx.
Trimis de pe al meu SM-G950F folosind Tapatalk

Thanks!! Finally my S8 is running Android Oreo.

Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Pavezi80 said:
Works! Thank you so much!
Click to expand...
Click to collapse
brenopapito said:
Thanks!! Finally my S8 is running Android Oreo.
Click to expand...
Click to collapse
Any of you guys try with Home_CSC?
Thanks!

geiti94 said:
WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!
Click to expand...
Click to collapse
can I use this guide to install CRAB when I have Renovate r44 (Oreo beta6) ?

Lucas_Skyline said:
Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Any of you guys try with Home_CSC?
Thanks!
Click to expand...
Click to collapse
I just tried with CSC_OXM file.

tomaasz said:
can I use this guide to install CRAB when I have Renovate r44 (Oreo beta6) ?
Click to expand...
Click to collapse
only when you dont let phone boot after flash in system and then you flash directly twrp and boot directly in twrp for mod build.prop so that vaultkeeper is set to 0 and flash magisk

Lucas_Skyline said:
Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Any of you guys try with Home_CSC?
Thanks!
Click to expand...
Click to collapse
You can use the normal CSC to format the S8. When installing, it will be ZTO / ZTO / ZTO because the Rom is multi-CSC (I downloaded the NEE)

It works! thanks!

Pavezi80 said:
You can use the normal CSC to format the S8. When installing, it will be ZTO / ZTO / ZTO because the Rom is multi-CSC (I downloaded the NEE)
Click to expand...
Click to collapse
That's the point, I'm going to travel tomorrow and I don't want to format at this moment
Just wondering if anyone tried with home_CSC from Nougat to Oreo directly to see if they found any issue.
Thanks!

worked here with HOME_CSC... will see if i will need to do it clean or if it will be ok with nowipe. i was on zre5, unoficial betatester

geiti94 said:
WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!
Click to expand...
Click to collapse
How to recover from this?

I made everything like in instruction but it stops at File analysis.... . What should i do ?

lumenit said:
I made everything like in instruction but it stops at File analysis.... . What should i do ?
Click to expand...
Click to collapse
Install with Prince Comsy's modified Odin

[GUIDE] Manual Update P20 PRO with HuRUpdater and TWRP

If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk
-Reboot to system and restore the security lock in developer options
- Restore your fingerprints and pins
- Enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.

Reserved

Working adb sideload?

If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
mangusZen said:
If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
- remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
-If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
- It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk 16.4
-Reboot to system and restore the security lock in developer options
- restore your fingerprints and pins
- enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.
Click to expand...
Click to collapse

ekremxx said:
Working adb sideload?
Click to expand...
Click to collapse
I have not tried that, it depends on the TWRP recovery, let us know if you try

sarichter said:
If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
Click to expand...
Click to collapse
I really don't know, and I don't think it will work.
As far as I know this is the only manual update method for now.
I just updated to unapproved .150 for my c636 and all seems fine

If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.

sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
eRecovery is not replaced.
To enter there try other volume button or with a cable plugged

Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff

sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
when booting there is a screen prompting to whether you want to go to eRecovery by pressing up or just boot into system and something ike that
---------- Post added at 04:23 PM ---------- Previous post was at 04:23 PM ----------
ekremxx said:
Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff
Click to expand...
Click to collapse
why you want to do sideload ? guide clearly explained to install it using TWRP.
if you dont have TWRP, then install it first

I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip

ekremxx said:
I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
The guide never said that you need sdcard
it said, that u need to put all those three files in same folder with the HuruUpdater.zip , and of course you can put it in your internal storage
i wont explain anything here. you better re-read the whole main post, as it already very clear
- put all files in one folder
- reboot to twrp
- flash huruupdater.zip
- boot to system
- reboot to twrp
- flash magisk to reroot
which step exactly that not understandable ? :silly:

I can install that's style orjinal filmware ty so much

Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto

moghetto said:
Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto
Click to expand...
Click to collapse
You should check and ask at P20 and HURupdater threads.
I don't know about P20.

Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?

can I downgrade firmware safely with this method? im on 150 and want to go back to 130

Ferezesal19 said:
Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?
Click to expand...
Click to collapse
You should not have problem, unless you are trying to rebrand.

Allesa said:
can I downgrade firmware safely with this method? im on 150 and want to go back to 130
Click to expand...
Click to collapse
I don't know about downgrading and I would not raccomend it

mangusZen said:
You should not have problem, unless you are trying to rebrand.
Click to expand...
Click to collapse
Thanks you. Only i want to Update... What firm you recommend That improves the duration of the battery?

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 10 (Exynos)

Team Win Recovery Project 3.3.1​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
Download: Note 10(Exynos variants - N970/971/975/976/N/F/B)
Download
Sources:
TWRP Tree and kernel source
Changelog:
15.12.2019
- Updated TWRP for Android 10.0
- From now on no more Magisk Prepatched images (if you need it patch it byself or flash my kernel where patched recovery is not needed)
22.09.2019
-Reverted MTP Changes from last build since for some mtp dont worked in system
21.09.2019
- Fixed the bug that mtp dont worked any more on TWRP when usb cable got disconnected and reconnected
- Modded Kernel for have MTP in TWRP, Samsung Roms and GSI roms (for GSI Roms flash GSI_MTP_ENABLER.zip)
- Reverted FFS MTP changes since new way is more stable
14.09.2019
- Fixed MTP using FFS_MTP in recovery (Thx to @bigbiff for add FFS MTP support on TWRP 3.3.0. FFS_MTP dont corrupts large files like the mtp used by samsung in the roms)
- Removed File Based backups because the phone refuses to boot from filebased backups since they breaks the rootfs
27.08.2019
-Initial Release
Bugs:
-No one
Telegram Group
https://t.me/twrp_n10
XDA:DevDB Information
[RECOVERY] TWRP for Galaxy Note 10 (Exynos), Kernel for the Samsung Galaxy Note 10+
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2019-08-27
Created 2019-08-27
Last Updated 2019-12-15

Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with power + vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field (if you want to patch twrp byself patch the downloaded tar in magisk manager. patched tar is in downloads folder after patch)
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp
flash the disabler that is on TWRP download link
flash my kernel avaiable here
press reboot to system in twrp.

so all builds are uploaded unpatched. for magisk you can patch it byself with magisk manager

Beware of multidisabler 1.3 at this moment, it has some bug

oggi21 said:
Beware of multidisabler 1.3 at this moment, it has some bug
Click to expand...
Click to collapse
then ian needs to fix it. i saw only he added note 10 support.

geiti94 said:
so all builds are uploaded unpatched. for magisk you can patch it byself with magisk manager
Click to expand...
Click to collapse
so you do the patch with magisk and ap rom flash via odin route still?
its old school jsut just fllash twrp via odin

Deezy88 said:
so you do the patch with magisk and ap rom flash via odin route still?
its old school jsut just fllash twrp via odin
Click to expand...
Click to collapse
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone

geiti94 said:
then ian needs to fix it. i saw only he added note 10 support.
Click to expand...
Click to collapse
Yeah, he said he gonna fix it today

so i added in download folder byself a n10 disabler because i saw that ians one will never ever work because my twrp use busybox and not toolbox (i like it easyers for dev thats why busybox is added)
that zip disables encrpytion, fix secure storage, removed 2 libs for not let the phone fall under prenormal state etc

geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow?

Deezy88 said:
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow?
Click to expand...
Click to collapse
yes you can

so since i am not all the time here on xda here is a telegram group link. use it for report bugs etc since i dont read all the time the complete thread here https://t.me/twrp_n10

thank you that was fast!

so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself

geiti94 said:
so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself
Click to expand...
Click to collapse
V2 worked like a charm! :good:

geiti94 said:
so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself
Click to expand...
Click to collapse
Great job geiti. Just waiting for rom release.:good::good:

geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
So, clear me if I have something miss-understand:
1. If flash rom cook: unlock OEM, flash twrp and then flash rom cook
2. If using stock root: unlock OEM, flash twrp and then patch AP with magisk and flash as Dr Ketan guide to flash Magisk?

namfat said:
So, clear me if I have something miss-understand:
1. If flash rom cook: unlock OEM, flash twrp and then flash rom cook
2. If using stock root: unlock OEM, flash twrp and then patch AP with magisk and flash as Dr Ketan guide to flash Magisk?
Click to expand...
Click to collapse
I think you're wrong for the number 2. If you wanted stock root with twrp. AFAIK you need to. Patch the AP from stock rom. Patch the twrp recovery.img . Then replace the stock patched recovery from AP patched with the patched twrp. Then you can follow dr.ketan's guide but use this new patched AP with the patched twrp inside

great now i have to spend 1000 bux to get this.

white7561 said:
I think you're wrong for the number 2. If you wanted stock root with twrp. AFAIK you need to. Patch the AP from stock rom. Patch the twrp recovery.img . Then replace the stock patched recovery from AP patched with the patched twrp. Then you can follow dr.ketan's guide but use this new patched AP with the patched twrp inside
Click to expand...
Click to collapse
Many thanks, got it.[emoji8][emoji8]
Sent from my SM-N975F using Tapatalk