first off if this is a wrong place than sorry but ....i wanted to know how to add device support to the kitchen?? my device is GT-S6012 galaxy music duos) rooted .......does it use yaffs file system..........if anybody could suggest me a method ...........i also want to know the procedure to port cm or any othe custom rom as i am using the stock rom right now .....any help would be appreciated !!!! :good:
omkar333 said:
WARNING: If your device is not listed in post #1 of this thread, and it does NOT use a 'YAFFS'-based filesystem (e.g. usually only low-end devices use YAFFS), do not attempt to flash a ROM that you built with this kitchen. Instead, you must do the following if your device is NOT listed:
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
NOTE: This method does not guarantee your device will work with your custom ROM, however. Some devices may require more steps than just the edify_defs file, but the procedure is outside the scope of this FAQ. Ask around in the XDA sub-forum for your device if you need further help.
Click to expand...
Click to collapse
You can find it in third post:@ here
THIS TOOL IS FOR TESTING PURPOSE ONLY.
THIS MAY WORK ON SOME DEVICES OR MAY NOT WORK AT ALL.
IF THIS TOOL MAKES THE ROM UNBOOTABLE PLEASE COMMENT BELOW.
NO BUG FIXING not until i get an oreo supported phone for me to test.
TREBLE ROMS ARE NOT SUPPORTED!
FEATURES:
CAN DETECT OREO BOOT.IMG (YOU CANT MESS UP THIS TOOL. HAHA!!)
CAN DETECT WHETHER THERES A BOOT.IMG INSIDE THE MAIN FOLDER
CONVERTS BINARY INTO PLAIN CONTEXTS (MAIN FEATURE)
DECOMPRESS .BR IMAGES INTO .DAT (COOL RIGHT?)
USAGE:
GRAB A BEER AND RELAX
WHILE ON YOUR WINDOWS COMPUTER, UNPACK THE ARCHIVE AND GRAB THE OREO BOOT.IMG INTO oreo_contexts_tool FOLDER
RUN OFC.EXE AS ADMIN (NO NEED ADMIN RIGHTS FOR V2.0.0.1 AND V2.0.0.2)
FOLLOW INSTRUCTIONS AFTERWARDS..
IF YOU NEED THE CONTEXTS CONVERTER FOR NOUGAT THEN USE MY TOOL HERE TO CONVERT PLAIN CONTEXTS INTO BINARY AND VICE VERSA.
tested only on x32bit windows 7 ultimate
ofc v2.0.0.1
ofc v2.0.0.2
!!VERY IMPORTANT TO READ NOTES!!
Code:
v2.0.0.1
can decompress .br image into .dat
can compress .dat image into .br
NO NEED to run the application with admin rights, just run normally.
I added x64 bit application but havent tested it yet on 64bit machine
(my laptop cant run x64 os :p) if it wont work pls use the other application.
v2.0.0.2
file contexts output is current directory
added reset tool if experiencing errors
added clean current directory
less popup of cmd (only when unpacking boot.img)
x64bit tool is not included yet.
note:
choosing "clean current directory" option will delete EVERYTHING
inside the current directory except for the tool. so i advise to run this tool
inside a folder/directory to avoid deleting all your important files on your pc.
e.g you run ofc.exe in drive C:\ (C:\OFC.EXE) ...then you chose
"clean current directory" option, this will delete EVERYTHING in
C: drive so BE CAREFUL!! I wont be responsible if this happens..
if your anti virus detects malware, trojan, etc just ignore.. my script is very simple and basic that any highschool student can laugh at it. :silly: :laugh:
AIK LINK
CREDITS
@osm0sis <-- also thank him
@munjeni <-- and him
DONT JUST SAY THANKS!! HIT THE BUTTON BELOW..
last update:
06/08/18
Thank You.oreo unpacked.
tool
Zipper31 said:
Thank You.oreo unpacked.
Click to expand...
Click to collapse
can you give oreo extract tool
new test update..
there is a trojan in the executable??
Friend, link is broken, please, upload again.
JamFlux said:
Friend, link is broken, please, upload again.
Click to expand...
Click to collapse
Yes! Update link please
greeshan said:
Yes! Update link please
Click to expand...
Click to collapse
I MANAGE MY OWN TOOL FOR THIS:
https://forum.xda-developers.com/ch...l-extract-repack-dat-img-android-5-8-t3670763
JamFlux said:
I MANAGE MY OWN TOOL FOR THIS:
https://forum.xda-developers.com/ch...l-extract-repack-dat-img-android-5-8-t3670763
Click to expand...
Click to collapse
Thanks, i'll try
link works on my slow internet..
reupload please?
0ther said:
reupload please?
Click to expand...
Click to collapse
link is working fine.. maybe use another browser?
Got 404, reupload please ?
DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.
C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.
Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk
I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.
Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...
Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.
@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...
Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.
Question is, for those of us with the Non Pro version, can this still be done.
@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?
OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:
struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img
The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.
I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost
Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod
AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101
Hey ! Wanna make the same thread as *Discussion* OREO but for Pie updates, a thread that is amazing by the way. Check it out here :
https://forum.xda-developers.com/galaxy-s8/how-to/discussion-oreo-final-t3746561
So ! Any Update.zip ? Post em here ! I got some for S8+ from this thread by @geri005 :
https://forum.xda-developers.com/galaxy-s8/how-to/s8-exynos-pie-oneui-beta-official-t3890376
G955F update.zip (CRL3 ---> ZSA5):
Google Drive:
https://drive.google.com/open?id=1Sz_r2vKXTs14E5todfZI1q14KE1s66Tz
Mega:
https://mega.nz/#!kV8mGSbQ!GbS3b3SJO_Z5yBanab35j93x1jd716_R4jXzgfUhVk8
G955F update.zip (CRL3 ---> ZSA5):
Google Drive:
https://drive.google.com/open?id=1lhQcAYgbkkYyyL7qiqp9G1b7065u8IE4
Will I be able to register in beta, when it's released in my country? Cause in Germany all beta builds for S9/N9 were available.
Members App show beta page, but tells my device is not registered :-/
Gesendet von meinem SM-G950F mit Tapatalk
Does someone know how to disable this?
yener90 said:
Does someone know how to disable this?
Click to expand...
Click to collapse
Think that's one handed mode, go into settings and disable
Is it possible to root pie ?
Fix error 7 in adb sideloading
Step 1. Copy the update zip file to a seperate folder and extract it using your favorite unzipping software. (i use WinRAR)
Step 2. Once unzipped, browse to the META-INF/com/google/android directory. You will find two files one of em called “updater-script”.
Step 3. Rename “updater-script” to “updater-script.txt” and open with NotePad.
Step 4. Get rid of the line containing the conflicting line “ro.secure” by making a search in the notepad and deleting from the semi-colon before it to next semi-colon ( ; ........ ro.secure ........ ; ).
Step 5. Save file.
Step 6. Rename “updater-script.txt” back to “updater-script”.
Step 7. Rezip all the files you’ve unzipped, in WinRAR just put the extension .zip and it will work. (change the name to Eupdate.zip or something like that juste in case).
Step 8. Now retry "adb sideload update.zip" and it will work
I just finished an update to my flashing script, now it will work with payload.bin and unpacked payload files.
Currently, only gsi_sdm660_64 models are available for this option.
And Windows only, too.
PLEASE ENSURE YOUR PHONE HAS UNLOCKED BOOTLOADER, OTHERWISE THIS GUIDE IS USELESS.
Let me introduce you how to use the new script:
DL: https://github.com/HikariCalyx/OSTRemote/releases
source: https://github.com/HikariCalyx/OSTR...Script/generic_flash_script_gsi_sdm660_64.bat
If you use unpacked nb0 extension stock firmware as before, please follow this guide:
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-workaround-flashing-sparse-t3906070
Click to expand...
Click to collapse
1. You must have Python 3 installed. It can be downloaded from https://www.python.org/downloads/
2. Extract the payload.bin from full OTA package (e.g. March 2019 update known as B2N-351F-0-00WW-B04)
3. Put the script file (and required files if you prefer original script source) and the payload.bin altogether
4. Download payload_dumper.py and update_metadata_pb2.py from the URL given by the script, and place them to the same directory of the script.
5. Type lowercase "yes" (without quotes) and press Enter, wait for the procedure complete.
6. The script will dump the payload.bin and process both system and vendor image to flashable sparse image.
7. After that, you should know what to do next.
If you already have dumped payload and converted system.img / vendor.img, the script will tell you if you want to flash the unpacked OTA packages, you can simply type "yes" and proceed.
You needn't to waste the time of processing payload.bin again, once you don't delete them.
I'm considering port this script to universal for almost every A/B Android devices, if it works great.
Nice job dude, this will be very useful to many people.
Very well Hikari, nice script
Very very much appreciated work!
Can't wait to try it out!
Thanks !
Mod edit - Translated by Google Translate:
Very supportive! !! !!
*********************
非常支持！！！
does this work for other Nokia models? Such as 3.2?