Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a build of AICP for the Shield Tablet (WiFi Only) (wx_na_wf)
You need to have CWM recovery installed on your device See Here for instructions install CWM. Try this version of CWM when flashing
Or use PhilZ
Instructions on installing:
Make a backup of your current ROM (Optional but highly recommended)
Wipe --> Factory Reset (Data, Cache, and Dalvik Cache)
Flash ROM
Flash Gapps
Reboot
Downloads:
8/28/14 ROM
8/25/14 ROM
8/23/14 ROM
8/22/14 ROM
Gapps
Bugs
You tell me
Kernel Source
XDA:DevDB Information
AICP for Shield Tablet (WiFi Only), ROM for the Nvidia Shield Tablet
Contributors
joshuabg, Unjustified Dev For making the device tree compatible
ROM OS Version: 4.4.x KitKat
Based On: AOKP
Version Information
Status: Testing
Created 2014-08-22
Last Updated 2014-12-20
Reserved
Reserved
OK I done a full wipe factory reset/cache in the latest recovery then tryed flashing had an error saying
This package is wx_na_wf this device is shield tablet
Error status 7
I'm not much of a dev but will look through the build prop or meta data to see if its a simple name change?
MRobbo80 said:
OK I done a full wipe factory reset/cache in the latest recovery then tryed flashing had an error saying
This package is wx_na_wf this device is shield tablet
Error status 7
I'm not much of a dev but will look through the build prop or meta data to see if its a simple name change?
Click to expand...
Click to collapse
Just got to edit the META-INF/com/google/android/updater-script
proably have to change wx_na_wf to shieldtablet in line 2
I can do it and reupload the whole zip f you want
Edit: You could just erase that line
joshuabg said:
Just got to edit the META-INF/com/google/android/updater-script
proably have to change wx_na_wf to chield tablet in line 2
I can do it and reupload the whole zip f you want
Click to expand...
Click to collapse
That's OK I can do that give me 10 mins
MRobbo80 said:
That's OK I can do that give me 10 mins
Click to expand...
Click to collapse
OK, just edit the updater script, you should be able to just delete the second line without an issue.
Deleted second line and did not have any luck so this second line below just change
"wx_na_wf" to ,"shieldtablet "
").");
assert(getprop("ro.product.device") == "wx_na_wf" || getprop("ro.build.product") == "wx_na_wf" || abort("This package is for \"wx_na_wf\" devices; this is a \"" + getprop("ro.product.device") + "\".");
MRobbo80 said:
Deleted second line and did not have any luck so this second line below just change
"wx_na_wf" to ,"shieldtablet "
").");
assert(getprop("ro.product.device") == "wx_na_wf" || getprop("ro.build.product") == "wx_na_wf" || abort("This package is for \"wx_na_wf\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Click to expand...
Click to collapse
What happened when you deleted the second line? It might be easier if you join the IRC channel so I can walk you though everything.
Deleted second line and did not have any luck so this second line below just change
"wx_na_wf" to ,"shieldtablet "
").");
assert(getprop("ro.product.device") == "wx_na_wf" || getprop("ro.build.product") == "wx_na_wf" || abort("This package is for \"wx_na_wf\" devices; this is a \"" + getprop("ro.product.device") + "\".");
So it should look like this
").");
assert(getprop("ro.product.device") == "shieldtablet" || getprop("ro.build.product") == "shieldtablet" || abort("This package is for \"shieldtabley\" devices; this is a \"" + getprop("ro.product.device") + "\".");
MRobbo80 said:
Deleted second line and did not have any luck so this second line below just change
"wx_na_wf" to ,"shieldtablet "
").");
assert(getprop("ro.product.device") == "wx_na_wf" || getprop("ro.build.product") == "wx_na_wf" || abort("This package is for \"wx_na_wf\" devices; this is a \"" + getprop("ro.product.device") + "\".");
So it should look like this
").");
assert(getprop("ro.product.device") == "shieldtablet" || getprop("ro.build.product") == "shieldtablet" || abort("This package is for \"shieldtabley\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Click to expand...
Click to collapse
What happened when you flashed this?
Says
Installing
Installation aborted
MRobbo80 said:
Says
Installing
Installation aborted
Click to expand...
Click to collapse
Do you have zip signature verification checked?
No I did not, now I enabled that I tried flashing the original rom it seems to start of by going through the normal process of flashing, then stalls with the first error message to start with. When I change the second line (name change) in the update script to (shieldtablet) it the gives me an error saying the footer is in correct when trying to flash. Think it is a very simple fix to get this going but having a dipstick trying to help you is not much kop sorry m8
Hold on think I know what I done
@joshuabg You have to upload your recovery.img that compiled with it. I changed name because we shouldn't be using shieldtablet name in custom roms that's common to all versions.
Unjustified Dev said:
@joshuabg You have to upload your recovery.img that compiled with it. I changed name because we shouldn't be using shieldtablet name in custom roms that's common to all versions.
Click to expand...
Click to collapse
I'll upload that tommorow.
Unjustified Dev said:
@joshuabg You have to upload your recovery.img that compiled with it. I changed name because we shouldn't be using shieldtablet name in custom roms that's common to all versions.
Click to expand...
Click to collapse
My ROM is made for wx_na_wf. The bad thing about that is that aicp checks to see if the device is a wx_na_wf before it flashes. The stock os shows the device is a shieldtablet. So you have to remove that line in the updater-script.
sorry man got it sort of working got it to flash but stuck in a boot loop, now I can not enter recovery or so far get adb working
Here's my recovery.img that generated with AICP (wx_na_wf)
https://s.basketbuild.com/filedl/devs?dev=joshuabg&dl=joshuabg/wx_na_wf/recovery.img
Unjustified Dev said:
@joshuabg You have to upload your recovery.img that compiled with it. I changed name because we shouldn't be using shieldtablet name in custom roms that's common to all versions.
Click to expand...
Click to collapse
https://s.basketbuild.com/filedl/devs?dev=joshuabg&dl=joshuabg/wx_na_wf/recovery.img
Q&A for [ROM] [5.0] Samsung Galaxy S3 [d2usc][Nightly] LiquidSmooth Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.0] Samsung Galaxy S3 [d2usc][Nightly] LiquidSmooth Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
htrowpiks said:
First!... Androidfilehost says need to sign in and I don't have access to the folder....
Click to expand...
Click to collapse
Maybe they are working on a new nightly build.
liquidsmooth on d2mtr
@vuzedroid
I tried to answer your question in the liquidsmooth thread, but I get directed here because I have less than 10 posts. Anyways, I hope you see this...
I have this rom installed on my d2mtr. It works well, but I loose audio every once in a while and just have to reboot to get it back. Also install open camera if you need the camera.
Here's how to install it on the d2mtr. I recommend the 02/08 build since it has the cm theme engine instead of layers...
Unzip the package and open the "updater script" and change the "assert" line at the top from this...
Code:
assert(getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" || getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || abort("This package is for device: d2usc,d2lte; this device is " + getprop("ro.product.device") + "."););
To this...
Code:
assert(getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" || getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || getprop("ro.product.device") == "d2mtr" || getprop("ro.build.product") == "d2mtr" || abort("This package is for device: d2usc,d2lte,d2mtr; this device is " + getprop("ro.product.device") + "."););
Then zip it back up and wipe then flash the rom and gapps. I used the PA Pico gapps.
Before rebooting use the file manager in twrp recovery and go to "/system/priv-app" and delete "cmsetupwizard" then you can reboot. If you don't delete it then it will keep crashing during initial setup and not let you get to the home screen. That's it enjoy.
GameTheory. said:
@vuzedroid
I tried to answer your question in the liquidsmooth thread, but I get directed here because I have less than 10 posts. Anyways, I hope you see this...
I have this rom installed on my d2mtr. It works well, but I loose audio every once in a while and just have to reboot to get it back. Also install open camera if you need the camera.
Here's how to install it on the d2mtr. I recommend the 02/08 build since it has the cm theme engine instead of layers...
Unzip the package and open the "updater script" and change the "assert" line at the top from this...
Code:
assert(getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" || getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || abort("This package is for device: d2usc,d2lte; this device is " + getprop("ro.product.device") + "."););
To this...
Code:
assert(getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" || getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || getprop("ro.product.device") == "d2mtr" || getprop("ro.build.product") == "d2mtr" || abort("This package is for device: d2usc,d2lte,d2mtr; this device is " + getprop("ro.product.device") + "."););
Then zip it back up and wipe then flash the rom and gapps. I used the PA Pico gapps.
Before rebooting use the file manager in twrp recovery and go to "/system/priv-app" and delete "cmsetupwizard" then you can reboot. If you don't delete it then it will keep crashing during initial setup and not let you get to the home screen. That's it enjoy.
Click to expand...
Click to collapse
I just noticed this message, thanks a ton! I think I can do all this xD I'll let you know once I try :good:
Unable to start camera after resotring backup
Hi,
I have install your ROM and it's nice but have some bugs. specially volume. It does not reduce volume to lower level. In min. level it is too loud. So I decided to revert. I reverted my old OS backup, after that my primary camera is unable to start. I thought it might have some issue so tried different ROM, But camera won't work.
I tried Open Camera, it says
FAILED TO OPEN CAMERA.
CAMERA MAY BE IN USE
BY ANOTHER APPLICATION?
Front camera is working with Open Camera application. Standard camera application stops by saying "camera failed".
Is there any hardware damage.
Please help me out. I am stuck.
LiquidSmooth Lollipop GApps zip file
Hello and thank you for the Lollipop ROM for the US Cellular SGS3! I've been having fun playing with that today. One question, however: when I download the GApps zip file from the drdrvs website:
drdevs.com
devs
teamliquid
Gapps
lollipop
gapps-L-2-25-15.zip
(Sorry, new members can't post outside URLs...)
unzip claims that it's not a complete archive:
$ unzip -l gapps-L-2-25-15.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
I've attempted to download it several times, just to make sure my browser isn't truncating the file. The downloader page says it's 10.9MB, which jives with ls:
10887168 Apr 10 14:44 gapps-L-2-25-15.zip
Thought you might want to check it out on your end.
Grouchicarpo
Dark UI
How do I find and enable the dark ui? I am coming from SlimKat and loved that darkness it had.
I am on LS-LP-v4.1-2015-05-14-liquid_d2usc version of LiquidSmooth.
Also, Mobile network WORKS FINE, but it complains about not having an APN and won't send MMS messages....
LiquidSmooth d2usc
I too eagerly await an update for my GSIII on USCellular. This phone runs Lollipop really well. My only real complaint is the long boot time on LiquidSmooth and the resultant (unsettling) looping of the boot animation.
Thanks Orion116
I just wanted to say thanks and for all your hard work on the quickly dying d2usc or all usc variants. I currently have the "LS-LP-v4.1-2015-05-14-liquid_d2usc" from the liquidsmooth website. Is this the most recent update?
يريد ت
As you all know, flashing MIUI ROMs have become a bit tricky for Whyred users, due to the Anti-roll back issue. But fear not, @AL_IRAQI has found the solution, and I'll explain here how that goes, and I'll also link to the first Stable MIUI 10 in English by Xiaomi.eu. That ROM will not require this process, as pointed out by @dingdong3000 here.
► Why do you want this?
• Well, right now, the only Stable MIUI 10 for Whyred is Chinese. But Xiaomi.eu is based on the Chinese release, so their Stable ROM is basically the better Global version. Also, all of their ROMs pass the SafetyNet test without any issue, even if you directly modify parts of the system.
► How can you download?
• Download from official SourceForge link. DOWNLOAD
► How can you make the modification yourself?
• That's actually the prime purpose of this thread. There are basically 2 things to do when you want to make a MIUI ROM fw-less. Follow this procedure:
Download your desired ROM.
Open it with WinRAR (No need to extract).
Delete the folder title "firmware-update" from the list.
Go inside META-INF\com\google\android.
Double click on "updater-script".
Select "Notepad++" from the list. (IMPORTANT. Normal Notepad doesn't have a line count. Download it from here.)
We need to remove all the radio update tasks. To do that, remove the red colored lines from the code.
Code:
getprop("ro.product.device") == "whyred" || abort("E3004: This package is for \"whyred\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.19.0.OEIMIFA:user/release-keys");
show_progress(0.100000, 5);
show_progress(0.200000, 10);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
[COLOR="Red"]
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/mdtpsecapp.mbn", "/dev/block/bootdevice/by-name/mdtpsecapp");
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/abl.elf", "/dev/block/bootdevice/by-name/abl");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/abl.elf", "/dev/block/bootdevice/by-name/ablbak");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfgbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/dspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");[/COLOR]
show_progress(0.600000, 250);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.100000, 2);
set_progress(1.000000);
The final copy should look like this-
Code:
getprop("ro.product.device") == "whyred" || abort("E3004: This package is for \"whyred\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.19.0.OEIMIFA:user/release-keys");
show_progress(0.100000, 5);
show_progress(0.200000, 10);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.600000, 250);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.100000, 2);
set_progress(1.000000);
Notice the blank line at the end, don't remove it. Global ROM seems to have 14 lines of code with 1 blank line at the end after this process.
Save the file, WinRAR will ask if you want to update the archive, permit it.
Your ROM is now fw-less. Enjoy.
► You bricked your phone?
Sorry, I can't help you if you messed something up. That's the disclaimer here. You do this with all liability to yourself.
► Want to learn more?
• Everything About Anti Roll-back [Whyred]
• Redmi Note 5/Pro Miui ROMs without firmware [fw-less]
► Should you be careful?
• I don't exactly know how far behind you can go, do that research yourself and let me know so I can update it here. But I'd recommend not going too far behind. If you go too far, even after following this process, your phone might end up bricking. Some ROMs are just too old.
Isn't Xiaomi EU Firmware less itself ?
FroZine said:
Isn't Xiaomi EU Firmware less itself ?
Click to expand...
Click to collapse
As I already said, the version they released has the firmware update folder, which suggests that it isn't firmware less.
Thank you for this. Just to be on the same note, if I'm on latest 9.6.4 stable global I should be ok to flash this firmless ROM right? I just wanna make sure because I tried to flash MIUI pro 10 and bricked my device
NaeemBolchhi said:
As I already said, the version they released has the firmware update folder, which suggests that it isn't firmware less.
Click to expand...
Click to collapse
The firmware inside this xiaomi.eu 10 stable rom won't trigger ARB. It only updates BT, DSP, and modem not bootloader so ARB is safe.
dingdong3000 said:
The firmware inside this xiaomi.eu 10 stable rom won't trigger ARB. It only updates BT, DSP, and modem not bootloader so ARB is safe.
Click to expand...
Click to collapse
Yeah, just found out myself as well. So I guess I'll remove the download link and just keep the method.
coco1476 said:
Thank you for this. Just to be on the same note, if I'm on latest 9.6.4 stable global I should be ok to flash this firmless ROM right? I just wanna make sure because I tried to flash MIUI pro 10 and bricked my device
Click to expand...
Click to collapse
Use the official ROM, it'll work just fine. Skip mine.
NaeemBolchhi said:
Yeah, just found out myself as well. So I guess I'll remove the download link and just keep the method.
Use the official ROM, it'll work just fine. Skip mine.
Click to expand...
Click to collapse
OP I'm still complicated.. you have provided a link. Can you tell me if I flash that will it my ARB or not? Is it safe to flash?
1Ishara said:
OP I'm still complicated.. you have provided a link. Can you tell me if I flash that will it my ARB or not? Is it safe to flash?
Click to expand...
Click to collapse
My link leads to the SourceForge location, the rom works on both Ai and Pro Whyred devices. As someone mentioned above, it doesn't touch ARB, so no worries. I had previously added a different rom due to a misunderstanding. The current one is perfect.
Nice tutorial. Helped me a lot. Successfully installed latest global build. Keep up the good work. Thanks & please keep us updated
---------- Post added at 07:19 PM ---------- Previous post was at 07:03 PM ----------
@Naeem Will the system ota update stop completely by this method? I don't want ota updates.
NaeemBolchhi said:
My link leads to the SourceForge location, the rom works on both Ai and Pro Whyred devices. As someone mentioned above, it doesn't touch ARB, so no worries. I had previously added a different rom due to a misunderstanding. The current one is perfect.
Click to expand...
Click to collapse
Thank you very much. Off topic how about the battery life of xiaomi.eu stable? Im currently on masik i need to change the rom.
I tried your method exactly like you said with muipro 10 and bricked my device... again, but thanks to the new unbrick method I was able to unbrick it for free this time
In flash files long lists with the numbers of apps to be flashed are given. It would be highly useful if someone provides names of the corresponding apps that are associated with the numbers. I'm certain bloat can be minimised to some extent with this.
In terms of stability and performance it is better Xiaomi.eu or Miui Global?
coco1476 said:
I tried your method exactly like you said with muipro 10 and bricked my device... again, but thanks to the new unbrick method I was able to unbrick it for free this time
Click to expand...
Click to collapse
Which method that you used to unbrick the device, could you please share?
---------- Post added at 03:54 AM ---------- Previous post was at 03:46 AM ----------
NaeemBolchhi said:
As you all know, flashing MIUI ROMs have become a bit tricky for Whyred users, due to the Anti-roll back issue. But fear not, @AL_IRAQI has found the solution, and I'll explain here how that goes, and I'll also link to the first Stable MIUI 10 in English by Xiaomi.eu. That ROM will not require this process, as pointed out by @dingdong3000 here.
► Why do you want this?
• Well, right now, the only Stable MIUI 10 for Whyred is Chinese. But Xiaomi.eu is based on the Chinese release, so their Stable ROM is basically the better Global version. Also, all of their ROMs pass the SafetyNet test without any issue, even if you directly modify parts of the system.
► How can you download?
• Download from official SourceForge link. DOWNLOAD
► How can you make the modification yourself?
• That's actually the prime purpose of this thread. There are basically 2 things to do when you want to make a MIUI ROM fw-less. Follow this procedure:
Download your desired ROM.
Open it with WinRAR (No need to extract).
Delete the folder title "firmware-update" from the list.
Go inside META-INF\com\google\android.
Double click on "updater-script".
Select "Notepad++" from the list. (IMPORTANT. Normal Notepad doesn't have a line count. Download it from here.)
We need to remove all the radio update tasks. To do that, remove the red colored lines from the code.
Code:
getprop("ro.product.device") == "whyred" || abort("E3004: This package is for \"whyred\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.19.0.OEIMIFA:user/release-keys");
show_progress(0.100000, 5);
show_progress(0.200000, 10);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
[COLOR="Red"]
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/mdtpsecapp.mbn", "/dev/block/bootdevice/by-name/mdtpsecapp");
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/abl.elf", "/dev/block/bootdevice/by-name/abl");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/abl.elf", "/dev/block/bootdevice/by-name/ablbak");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfgbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/dspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");[/COLOR]
show_progress(0.600000, 250);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.100000, 2);
set_progress(1.000000);
The final copy should look like this-
Code:
getprop("ro.product.device") == "whyred" || abort("E3004: This package is for \"whyred\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.19.0.OEIMIFA:user/release-keys");
show_progress(0.100000, 5);
show_progress(0.200000, 10);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.600000, 250);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.100000, 2);
set_progress(1.000000);
Notice the blank line at the end, don't remove it. Global ROM seems to have 14 lines of code with 1 blank line at the end after this process.
Save the file, WinRAR will ask if you want to update the archive, permit it.
Your ROM is now fw-less. Enjoy.
► You bricked your phone?
Sorry, I can't help you if you messed something up. That's the disclaimer here. You do this with all liability to yourself.
► Want to learn more?
• Everything About Anti Roll-back [Whyred]
• Redmi Note 5/Pro Miui ROMs without firmware [fw-less]
► Should you be careful?
• I don't exactly know how far behind you can go, do that research yourself and let me know so I can update it here. But I'd recommend not going too far behind. If you go too far, even after following this process, your phone might end up bricking. Some ROMs are just too old.
Click to expand...
Click to collapse
My file has three extra lines at the end difference from yours should i removed it also?
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/cust", "0", "/cust");
package_extract_file("META-INF/com/xiaomieu/xiaomieu.sh", "/tmp/xiaomieu.sh");
run_program("/sbin/busybox", "sh", "/tmp/xiaomieu.sh", "dummy", "1", "/tmp/xiaomieu.sh");
pipo_nhoc said:
Which method that you used to unbrick the device, could you please share?
Click to expand...
Click to collapse
Sure it's this method
https://forum.xda-developers.com/re...nofficial-unbrick-harddricked-whyred-t3840687
The ROM linked in the OP is the official Xiaomi.eu MIUI 10.0.1 ROM, which contains the firmware-update folder, hence it's highly possible that it will trigger ARB4. OP, you'll save many users some time by either removing that link, or providing a link to a non-arb version of the ROM.
Does anyone know of a tool to check the ARB version in the ROM zip itself? Instead of flashing it on the device first and then checking via fastboot
Can I dirty flash the new MIUI 10 global stable over this rom?
Dr_TGP said:
Can I dirty flash the new MIUI 10 global stable over this rom?
Click to expand...
Click to collapse
No. Wipe clean.
pipo_nhoc said:
My file has three extra lines at the end difference from yours should i removed it also?
Click to expand...
Click to collapse
Don't do that. Also, verify if the rom isn't already fw-less, like Xiaomi.eu.
can you make fw-less for xiaomi eu weekly build?
i was looking for the exact same thread thank u
Hi.
I have a samsung A70 device
I want to make a simple zip can to delete bloatware and install some app after reflash rom.
So, i try many time with updater-script file but seemlike it not working.
There is code example:
ui_print(" Starting ... ");
mount("ext4", "EMMC", "/dev/block/platform/soc/1d84000.ufshc/by-name/system", "/system");
ui_print(" ");
delete("/system/app/ARCore/ARCore.apk");
ui_print(" ");
delete("/system/app/ARCore/ARCore.apk");
Click to expand...
Click to collapse
I Zip it on update.zip file and when i flash it still running nomarly but nothing got delete in /system/app/arcore/
TWRP so me
script susseded: result was [0]
Click to expand...
Click to collapse
i think system partion is not mounted yet. I don't know extracly vartion "/dev/block/platform/soc/1d84000.ufshc/by-name/system" is correct or not. Or i must set permission for that.
Can somebody help me write updater-script. Thank you!
May be studying this helps:
[TUTORIAL] The updater-script completely explained
Hi all XDA Members :) This is not at all an updater-script guide but an explanation Example of updater-script: assert(getprop("ro.product.device") == "janice" || getprop("ro.build.product") == "janice" || getprop("ro.product.device") ==...
forum.xda-developers.com
xXx yYy said:
May be studying this helps:
[TUTORIAL] The updater-script completely explained
Hi all XDA Members :) This is not at all an updater-script guide but an explanation Example of updater-script: assert(getprop("ro.product.device") == "janice" || getprop("ro.build.product") == "janice" || getprop("ro.product.device") ==...
forum.xda-developers.com
Click to expand...
Click to collapse
i already read this topic but it still not working bro. the systax is true but can't working
So you know the EDIFY-script is correct.
Then why ask here for verify / correct it?
BTW:
This forum is wrong place for your issue. Getting helped typically is requested here:
Android Q&A, Help & Troubleshooting
This forum is for all of your questions about Android Development and Hacking. If you need help troubleshooting a problem, please be as specific as possible by describing your software configuration, including the ROM, kernel, and any modifications you've done.
forum.xda-developers.com
You could have FEC (error correction) on this partition.
You could mod it until you're blue in the face and not see any change.
If you're rooted, do a dd then look at the last 4096 bytes of that partition.