{
"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"
}
4.3 Stock Firmware for Australian S34G (I9305T) users
WARNING !! DO NOT USE THIS ON ANY OTHER I9305 DEVICE, IT MAY CAUSE PROBLEMS !!
INFORMATION
The official 4.3 Firmware has now been released for the Australian S34G (I9305T).
Here's a safe way to update your phone and not be forced to install the KNOX (4.3) Bootloader.
The whole ROM has been taken apart so you can easily choose what you want to flash.
REQUIREMENTS
- Samsung S34G I9305T
- About 840mb - 1.5gb on your SDCard to copy the files
- Custom Recovery (CWM, Philz, TWRP, Mobile ODIN)
INSTALLATION INSTRUCTIONS
- Copy required zip files to your internal SD Card
- Reboot into recovery
- Perform a full wipe (Optional, but recommended)
- Install ROM
- Reboot and enjoy
If you wish to use addional files, the best order to flash them is this:
Kernel - Recovery - CSC - Odex - KNOX (make sure you used the Odexed KNOX version if you are using the Odex patch)
DOWNLOADS - DVUENC1
Main ROM: DOWNLOAD HERE - MD5: CC0EE566F8BA28FCEC909785898B3D48
- Boeffla 5.3 Beta 3 Custom Kernel *FIXED* (Built 2014-05-20)
- Deodexed, Zipaligned, SU, BusyBox, init.d
- No apps have been removed (except for KNOX protection)
- Extra CSC apps from TEL and XSA added
Odex Patch: DOWNLOAD HERE - MD5: 319A753F4FA8662A2201719BC2660008
- Turns the ROM into an Odexed ROM (like it originally comes stock)
KNOX: DOWNLOAD HERE - MD5: 0232AD5E46E2D812FE25DA851778D4B8
KNOX (Odexed): DOWNLOAD HERE - MD5: 913B85F228BF449A3B9668976ACB64F3
- Use this if you are one of the unfortunate ones with the 4.3 Bootloader
Stock Kernel: DOWNLOAD HERE - MD5: DE1EBF4A99FE6E763F3613B6EF191FA8
DOWNLOADS - DVUEMK4
Main ROM: DOWNLOAD HERE - MD5: 94FC96B7F9136049B3C245971CF3C431
- Boeffla 5.2 Custom Kernel (Built 2014-04-24)
- Deodexed, Zipaligned, SU, BusyBox, init.d
- No apps have been removed (except for KNOX protection)
- Extra CSC apps from TEL and XSA added
Odex Patch: DOWNLOAD HERE - MD5: 017AB49D9144D5581DBD7A55918EB0FB
- Turns the ROM into an Odexed ROM (like it originally comes stock)
KNOX: DOWNLOAD HERE - MD5: 4646030A29E68C8DF1163BC85099D581
KNOX (Odexed): DOWNLOAD HERE - MD5: D9FE90293427C774B5365D82CE9320D9
- Use this if you are one of the unfortunate ones with the 4.3 Bootloader
Stock Kernel: DOWNLOAD HERE - MD5: EA9AAEA3D20F6DD8A59E20A36742942D
DOWNLOADS - OTHER
SDCard Files: DOWNLOAD HERE - MD5: 8B67AFAC39C5D8A223B245898E1CDAC8
- Unpacked hidden.img installed to your SD Card
- Includes data for Navagon plus some sample music and video
Stock Recovery: DOWNLOAD HERE - MD5: 794C3C42C455E9D5C9AB63628A138028
- Just in case anyone needs them
CSC (TEL): DOWNLOAD HERE - MD5: 9C337956C923A9C614327449731278BC
CSC (XSA): DOWNLOAD HERE - MD5: 2D2C9A5DEE10B7F80F10E9C33681ED37
- The specific Australian CSCs. TEL is for Telstra CSC, and XSA is for the generic Australian CSC.
- With some recoveries, you may have to manually mount the /system partition as these original CSC files don't seem to do that automatically
Modem (DVUEML1): DOWNLOAD HERE - MD5: E6B263802912EF2B43759B31D336FED2
Modem (DVUEMK2): DOWNLOAD HERE - MD5: 561DFD09A7011566B63E406354526C8E
Modem (DVUENC1): DOWNLOAD HERE - MD5: DB088658B5025D679721EA66FB42E690
- DVUEML1 and DVUENC1 came with the TEL Firmware, and DVUEMK2 came with the XSA Firmware.
Reserved...
Cheers man!:good::laugh:
Added the OPS CSC
djb77 said:
[
ORIGINAL ODIN FILES
These should only be used for development purposes, or if you have already installed a previous 4.3 Firmware on your phone via ODIN
I9305TDVUEMK4-TEL - DOWNLOAD HERE
I9305TDVUEMK4-XSA - DOWNLOAD HERE
Click to expand...
Click to collapse
what's the difference with the 2 odin files?
Thanks heaps by the way
billyhoyle said:
what's the difference with the 2 odin files?
Thanks heaps by the way
Click to expand...
Click to collapse
Different CSC's in them.
djb77 said:
Different CSC's in them.
Click to expand...
Click to collapse
Sorry for the stupid questions -
CSCs?
Does it matter which I flash?
billyhoyle said:
Sorry for the stupid questions -
CSCs?
Does it matter which I flash?
Click to expand...
Click to collapse
Use the TEL CSC if you're a Telstra user, OPS for Optus, and XSA for Australian generic.
Like I said before, DONT flash the ODIN files unless you already have previously flashed a 4.3 FW via ODIN. Use the zips I made instead.
djb77 said:
Use the TEL CSC if you're a Telstra user, OPS for Optus, and XSA for Australian generic.
Like I said before, DONT flash the ODIN files unless you already have previously flashed a 4.3 FW via ODIN. Use the zips I made instead.
Click to expand...
Click to collapse
Thanks heaps.
Hadn't flashed 4.3 via ODIN (just Telstra update), trying to flash other rom, got stuck in recovery mode, flashing this via ODIN worked.
billyhoyle said:
Thanks heaps.
Hadn't flashed 4.3 via ODIN (just Telstra update), trying to flash other rom, got stuck in recovery mode, flashing this via ODIN worked.
Click to expand...
Click to collapse
And now you have the 4.3 bootloader flashed to you phone.
The whole point of this thread was to save people from doing that and installing KNOX on their phone (which is a new protection from Samsung).
It's too late now to go back to a 4.1.2 bootloader now too.
I updated with stock Optus 4.3 through Odin. Got the Knox apps but managed to disable it then froze it intitanium backup.
Perhaps silly question but what does the CSC mean and what does it do?
Sent from my GT-I9305 using Tapatalk
harlz said:
I updated with stock Optus 4.3 through Odin. Got the Knox apps but managed to disable it then froze it intitanium backup.
Perhaps silly question but what does the CSC mean and what does it do?
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
CSC is a sales code and its different for each country and some providers.
Do a google search and you'll find some more info
djb77 said:
And now you have the 4.3 bootloader flashed to you phone.
The whole point of this thread was to save people from doing that and installing KNOX on their phone (which is a new protection from Samsung).
It's too late now to go back to a 4.1.2 bootloader now too.
Click to expand...
Click to collapse
Ive just upadate from 4.1.2 to 4.3 does it mean I have the 4.3 bootloader? thanks
dbp said:
Ive just upadate from 4.1.2 to 4.3 does it mean I have the 4.3 bootloader? thanks
Click to expand...
Click to collapse
Depends on if you flashed the update with ODIN or not, if you did, you'd have the 4.3 bootloader
djb77 said:
Depends on if you flashed the update with ODIN or not, if you did, you'd have the 4.3 bootloader
Click to expand...
Click to collapse
I've have updated it from the device and there is KNOX app but haven't installed it yet and is there rooting for this version?
dbp said:
I've have updated it from the device and there is KNOX app but haven't installed it yet and is there rooting for this version?
Click to expand...
Click to collapse
Just for the fact there is a sign of KNOX isnt good. A custom kernel still might be able to save you and SuperSU for root.
djb77 said:
Just for the fact there is a sign of KNOX isnt good. A custom kernel still might be able to save you and SuperSU for root.
Click to expand...
Click to collapse
I must have a bad rooting last version because when I run SystemApp Remover it prompted my device is not rooted, don't know what to do, very much appreciated
dbp said:
I must have a bad rooting last version because when I run SystemApp Remover it prompted my device is not rooted, don't know what to do, very much appreciated
Click to expand...
Click to collapse
Try flashing the latest version of SuperSU
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
djb77 said:
Try flashing the latest version of SuperSU
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Click to expand...
Click to collapse
damn the security blocked the superSU
The way I rooted my stock 4.3 Optus (with Knox)
I used the cf root recovery that you flash through Odin. Once that's done and you reboot you so don't have root because of Knox. Go to app store and update SuperSu.
From there open SuperSu and it should now ask if you want to have Knox disabled. It worked for me. Then use titanium and delete or freeze all Knox related rubbish.
Sent from my GT-I9305 using Tapatalk
Related
Update: Mobile Odin Pro 4.0+ is fully working with KitKat too! So you can upgrade your 4.3 to 4.4.2 with no problem and flash custom KK ROMS too! Don't forget to upgrade your bootloader though, and be careful, after upgrading you'll have a secure bootloader that will trip Knox if you ever lose root and want to root back again.
ZeAuReLiEn said:
Installing from a rooted 4.3 with knox 0x0 the stock 4.4.2 rooted with Mobile Odin Pro + installing the BL through Odin PC + installing X-Note 8 through Mobile Odin Pro WITHOUT INSTALLING ANY KERNEL OR BOOTLOADER = X-Note 8 with knox 0x0 !
Thanks for the usefull tip !
Click to expand...
Click to collapse
How to do the same:
Mwyann said:
Tested on European phone, not tested on US branded:
Download N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5, N9005XXUENA6_BL-Only.tar.md5 and Odin 3.09. Place the first file in your phone's memory. Do some backups and when you're ready, fire up MOP, load the HOME.tar.md5 in it, enable EverRoot, choose After flashing and select Download mode. Start flashing. When in download mode, hook your phone to the computer, run Odin 3.09, load he BL-Only.tar.md5 in the BL section, check Phone Bootloader Update, uncheck Auto Reset and Start. When Odin says RESET!, turn off your phone, and then press VOL UP+HOME+POWER to run recovery. Wait... and here you go!
Click to expand...
Click to collapse
Hello guys,
I'm posting a new thread as this is an extension of both using Mobile Odin Pro 3.85+ to flash stock firmwares and installing a custom ROM without flashing a custom recovery (preventing tripping knox).
This guide will show you how to flash a custom ROM and keeping Knox at 0x0 (it will NOT revert a 0x1 though, still not possible).
MAKE SURE THE ZIP FILE YOU PLAN TO INSTALL WILL NOT FLASH ANY RECOVERY OR ANY NON-STOCK KERNEL !!!
For your information, I tripped my Knox by flashing a ROM with its "Stock Kernel", which in fact wasn't. So, just to be on the safe side, do NOT flash kernels unless you're 100% sure this is an official and signed kernel. If unsure, just skip kernel installation, and you should be fine!
soloilmeglio said:
sorry the stock kernel was modified in ramdisk to enable init.d .... it will trip knox...
Click to expand...
Click to collapse
Some Aroma installers let you choose before installing, but others just do it without a warning. If you flash a wrong recovery or wrong kernel, you'll be screwed! So be aware of that. If you can, just check what the installer script is doing and remove the offending flashing parts, or ask the ROM's OP.
Also some ROMs (like AOSP) rely on some kernel's functionnalities that are not present in the stock kernel, or use a different version of the kernel. You would need to flash their custom kernel, which will trip Knox. There's nothing you can do about that for now. Same thing if you want to use modified kernel like SElinux permissive or more UC/UV/governor options. Those need a custom kernel, and will trip knox too.
Chainfire said:
Update ZIPs
Support for this means you can flash complete custom ROMs, or simple updates (like SuperSU's distribution ZIP file). This doesn't automatically mean all Update ZIPs are compatible. The environment in Mobile ODIN's temporary recovery is slightly different from CWM or TWRP, this can cause problems in some cases.
Click to expand...
Click to collapse
I'm of course not responsible for what you do. I'm trying to make it clear enough for you to understand, but if you don't fully understand that flashing a wrong recovery/kernel will trip your Knox, then you'd better keep stock.
Also, all this process can be totally reverted simply by flashing a stock ROM, either with MOP or with Odin on your computer (but it will not revert Kn0x of course...).
Anyway, here is the thing...
You need to turn Reactivation Lock off for the whole rooting/flashing part (just to be on the safe side).
First you have to safely root your device, for example with Root De La Vega. There is enough tutorials and how-tos out there, just look by yourself
Then, purchase and install Mobile Odin Pro.
Let's say you want to install a ROM based on firmware version ML2, I recommend (but it's not mandatory) to flash the corresponding stock firmware first (after you've flashed the custom ROM, I think you won't have to do that again, you can always update modem with standalone zip updates). Personally, as no stock ML2 was out at the time of doing this, I just installed MK2 then X-Note ML2 (with stock ML2 kernel), and that was it
Download the ROM from sammobile (choose the right one for your country, if you mix CSC you can trip Knox), load it on the phone's memory or the sdcard, and set up MOP like this (don't pay attention to the warning saying that you will trip Knox by using MOP, it does not if you follow these instructions carefully) :
{
"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"
}
Load the .tar.md5 with the "Open file..." option, check EverRoot, SuperSU, MobileOdin and wipe dalvik cache, and start flashing.
After rebooting, download the custom ROM you wish (for example X-Note), load the zip into the phone's memory or the sdcard, run MOP and set it up like this:
Load the .zip file with "OTA / Update ZIP" this time, uncheck EverRoot (your ROM should be already rooted), uncheck wipe dalvik cache (already done by the ROM installer) and start flashing.
If the Zip is an Aroma installer or similar, you'll be presented to your ROM's installation menu. Here is the most important part, so listen carefully: When asked, choose not to install any recovery, and don't install any custom kernel either (you can still flash stock kernel). Finish the installation, let it reboot, and enjoy your ROM with Knox 0x0
Note: You can also flash any zip mods you want with that method (you just have to put the .zip into "OTA / Update ZIP", uncheck EverRoot and start flashing). Of course, I'll repeat once more, but you still cannot flash any custom recovery nor non-stock kernel (well you can, but then you'll trip Knox).
I'd be glad if we could also do nandroid backup/restores with MOP, that way we wouldn't have to flash a recovery at all
Hit Thanks if this helped you, and of course let us know how it went for you.
Yann
Great, you have made a thread. Thank you!
and2 said:
Great, you have made a thread. Thank you!
Click to expand...
Click to collapse
Time to udpate your signature I guess (and mine too btw).
Mwyann said:
Time to udpate your signature I guess (and mine too btw).
Click to expand...
Click to collapse
Ha, you are right ??
Gesendet von meinem SM-N9005 mit Tapatalk 4
"First you have to safely root your device, for example with Root De La Vega. There is enough tutorials and how-tos out there, just look by yourself "
I am on MJ7 no root. If i use RDLV Knox will become 0x1. What about Chainfire?
this is working in a SG4 i337M?
megatooth said:
"First you have to safely root your device, for example with Root De La Vega. There is enough tutorials and how-tos out there, just look by yourself "
I am on MJ7 no root. If i use RDLV Knox will become 0x1. What about Chainfire?
Click to expand...
Click to collapse
Good question.
AFAIK, Chainfire's auto root on MJ7 and MK2 turns your Knox into 0x1....
So take it easy. Cheers
?
Sent from my NOTE 3 monster
Latest firmware for my country is:
PDA: N9005XXUDMK2
CSC: N9005NEEDML2
MODEM: N9005XXUDMJ7
I want to install X-Note ML2 rom.
How should I do it? First install ML2 firmware without CSC and modem? Or is it even possible to flash only PDA with MOP?
Sent from my SM-N9005 using Tapatalk
piats said:
Latest firmware for my country is:
PDA: N9005XXUDMK2
CSC: N9005NEEDML2
MODEM: N9005XXUDMJ7
I want to install X-Note ML2 rom.
How should I do it? First install ML2 firmware without CSC and modem? Or is it even possible to flash only PDA with MOP?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
You can flash PDA only with MOP, but it will be totally erased when you'll install X-Note, so it's useless. You can upgrade Modem only (if needed) and then flash X-Note directly if you want. I told to flash latest firmware first to get latest official upgrades before going to custom ROM, but that's not mandatory, it depends on what you already flashed.
Mwyann said:
You can flash PDA only with MOP, but it will be totally erased when you'll install X-Note, so it's useless. You can upgrade Modem only (if needed) and then flash X-Note directly if you want. I told to flash latest firmware first to get latest official upgrades before going to custom ROM, but that's not mandatory, it depends on what you already flashed.
Click to expand...
Click to collapse
My point was that I want to install latest X-Note rom and keep my country csc and modem. So can I first flash X-Note ROM and after that flash csc and modem via MOP?
Thanks for your patience
Sent from my SM-N9005 using Tapatalk
piats said:
My point was that I want to install latest X-Note rom and keep my country csc and modem. So can I first flash X-Note ROM and after that flash csc and modem via MOP?
Thanks for your patience
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
X-Note doesn't update Modem anyway. If you want to reflash CSC you can, but I'm quite sure it doesn't change anything either. Not 100% sure but shouldn't be a problem to reflash CSC, nor not reflashing it at all too
Thanks a lot for your information! I was not sure what would change after flashing ROM which is different than your country's latest firmwares. Nor I wasn't sure what MOP could flash. I will test and report back soon when I have enough time
Sent from my SM-N9005 using Tapatalk
Just downloaded Singapore firmware and flashed on Australian Note 3, I cleared the Cache section on MOP and flashed it.It didn't trip Knox.
Installed X-Note and had to choose BTU CSC in aroma installer. Now I have wrong CSC for my region. I'm just wondering would it be possible to flash correct csc for my country via odin?
Sent from my SM-N9005 using Tapatalk
How did you guys get Mobile Odin to work? When I try to run it, it says device not supported.
Sent from my SM-N900T using Tapatalk
nyflyguy said:
How did you guys get Mobile Odin to work? When I try to run it, it says device not supported.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Install mobile odin and then reboot.
tobia996 said:
Install mobile odin and then reboot.
Click to expand...
Click to collapse
Tried but still can't get Odin to load up. Cdn note3
imsiin said:
Tried but still can't get Odin to load up. Cdn note3
Click to expand...
Click to collapse
You're rooted, right ? (And Odin has root priviledges). You have a genuine device, not a clone?
Mwyann said:
You're rooted, right ? (And Odin has root priviledges). You have a genuine device, not a clone?
Click to expand...
Click to collapse
I hope to God it's genuine lol I got it from best buy through Rogers.. Yes rooted and odin does have privileges. Thx
Sent from my SM-N900W8 using Tapatalk
imsiin said:
I hope to God it's genuine lol I got it from best buy through Rogers.. Yes rooted and odin does have privileges. Thx
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
nyflyguy said:
How did you guys get Mobile Odin to work? When I try to run it, it says device not supported.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Not sure it will work on SM-N900W8 or SM-N900T though, I only tested this on my SM-N9005. Check the compatibility between your device and MOP.
For future use
For future use
{
"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"
}
4.3 bootloader/No knox/no binary count/wi-fi working (Alternative) for Note 2
ONLY FOR THE GT-N7100 INTERNATIONAL MODEL(GSM)
This package is only for devices that still have old bootloaders or are using patched bootloader including wi-fi patches.
SEE POST 2 FOR MORE INFO
1. Download the package from the link.
2. Extract the package.
3. Boot your device into download mode.
4. Flash the final tar via odin PDA mode.
DEVICE WILL ENTER RECOVERY MODE,PRESS THE POWER BUTTON TO REBOOT.
5. Use triangle away to remove the binary if you have it.
This package will not fix already Knox triggered devices.
This will not help you if you already flashed the 4.3 official rom with Knox bootloader.
This package contains 4.3 bootloader, recovery, kernel and modem.
Package will add a new entry to download mode called warranty bit: 0
Package has been tested many times by me.
You will be able to downgrade with this package.
I will not be held responsible for any arising divorces due to you yelling at your device and spending too much time trying to fix it when flashing this package, do so at your own risk. Do not flash if you don't know what i'm on about.
How to use:
Flash this package before flashing any custom 4.3 rom.
Other uses:
Flash this package then a custom recovery, install all your zip update files. Once your done reflash the package and run triangle away to get rid of the binary count.
Now you can have a device with a 4.3 without random reboots, working wi-fi and no binary count.
Thanks to all the XDA users that made this possible.
Package with mj5 bootloader and mj9 modem [BTU] UK
************************************************************************************
Requested Packages with custom Modems
Package with mj5 bootloader and mj5modem
You can find a prior way of achieving the above in this thread by Robalm,Minus recovery and modems.
How to set SELinux from enforcing to permissive
How to set SELinux from enforcing to permissive.
YOUR DEVICE MUST BE ROOTED
First you need SuperSU from chainfire, xposed framework and wanam exposed module.
Download the xposed framework and follow the instructions on how to install it, then install the wanam xposed module and activate it within the xposed framework.
Open SuperSU, go to settings, tick enable SU during boot and tick trust system user.
Open the wanam xposed module and press the security hacks tab and then tick disable SEAndroid box.
Reboot your device.
Your SElinux will now be set to permissive.
http://selinuxproject.org/page/SEAndroid
FAQ:
Package is made simple so you can fix 4.3 bootloops, wifi problems and downgrade to 4.1 without any additional steps.
This is only applicable to devices that have never been flashed with the official 4.3 update.
How to downgrade to 4.1?
Flash the Package then flash the official 4.1 rom
Can i use this package to upgrade to a 4.3 custom rom?
Yes and its a must. Flash it before or after flashing custom rom.
Can i use this package to Set my device to OFFICIAL status?
yes, After flashing it use Triangle away to Fix your Status.
can i flash this if i have problems with wifi on 4.2?
Yes
Can i flash this to fix my boot-loops in 4.3 ?
Yes
Can i use this package with 4.1?
NO!
Can i use this package to revert Knox to X0?
NO.
Will this package Trigger my binary?
No.
Q. I have already flashed a 4.3 custommrom, can i still flash this?
Yes
Package can be also be flashed to any official rom as long you never had a Knox bootloader. (eg. a offical rom flashed by mobile odin.)
Package is not compatible with mobile odin so dont even try, it won’t work.
good news
Thx 4 this. Anyone tried it?
Sent from my GT-N7100 using Tapatalk 2
Doesn't work with mj5 bootloader....... Right?
Obviously with knox counter not active...
Inviato dal mio GT-N7100 utilizzando Tapatalk
Great News
Well done! Is it possible to post a version with only the bootloader?
crisgen said:
Doesn't work with mj5 bootloader....... Right?
Obviously with knox counter not active...
Inviato dal mio GT-N7100 utilizzando Tapatalk
Click to expand...
Click to collapse
the package contains an mj5 bootloader so i guess it will be fine.
TITAN-23 said:
Well done! Is it possible to post a version with only the bootloader?
Click to expand...
Click to collapse
Yes but i rather not post it here to avoid issues/problems (thinking of new users etc)give me a few minutes and i will pm you a link.
Edit.... in order to have reset the binaryi need to include the stock kernel,is this ok or you just want the boot loader?
Thanks so much. Just the bootloader please.
TITAN-23 said:
Thanks so much. Just the bootloader please.
Click to expand...
Click to collapse
Pm sent.
faria said:
Pm sent.
Click to expand...
Click to collapse
thanks for this. could i get the bootloader only as well? id like the fix but keep my current modem. no one seems to deal with the mj4 modem for my region (TPA) thanks.
KoKoMaster said:
thanks for this. could i get the bootloader only as well? id like the fix but keep my current modem. no one seems to deal with the mj4 modem for my region (TPA) thanks.
Click to expand...
Click to collapse
+1
tegben said:
+1
Click to expand...
Click to collapse
if you post your modem i will repackage for you,meanwhile i will send you the link to boot loader only.
Heres link to the mj4 modem I made
https://www.dropbox.com/s/kap2bde6bgv03i2/mj4 modem.zip
I followed the instruction from this link so I hope I did it right
http://forum.xda-developers.com/showthread.php?t=2044937
KoKoMaster said:
Heres link to the mj5 modem I made
https://www.dropbox.com/s/kap2bde6bgv03i2/mj4 modem.zip
I followed the instruction from this link so I hope I did it right
http://forum.xda-developers.com/showthread.php?t=2044937
Click to expand...
Click to collapse
that's fine, it 2 am here, I will do it tomorrow.
Seems will not work with MJ9 bootloader then why the screenshot having MJ9 bootloader?
lontu said:
Seems will not work with MJ9 bootloader then why the screenshot having MJ9 bootloader?
Click to expand...
Click to collapse
Mj5 bootloader mj9 modem.
Procedure for installing stock Samsung Lollipop firmwares with Knox 0x0. (I9505)
You can do the upgrade from your 4.4.2 KitKat, already rooted with Peppe130's method, as described here. You need Mobile Odin Pro and Odin 3.09 for Windows (this is the version that worked for me, I can't say whether different versions work equally well, they might). You also need the bootloader .tar for the version you are installing. The tar needs to include 6 .mbn files, aboot, rpm, tz, and sbl1-3. @ambassadii has included the bootloader .tar for the OB7 firmware in his post here. Then:
Download the firmware you want (e.g. OB7) and the latest SuperSU v.2.46 from @Chainfire's page, and copy both of them on your external SD card.
Factory reset your phone, and only install SuperSU and Mobile Odin Pro from the Play Store (you can obviously backup what you want beforehand with Titanium).
Run Mobile Odin Pro, accept the download of the required file, and then press OTA/Update ZIP and locate the UPDATE-SuperSU-v2.46.zip file you saved on your external SD.
Now press Open File... and choose the .tar.md5 firmware file you also saved a minute ago. Mobile Odin will automatically find and separate the different parts.
Tick only Enable EverRoot, leave the other options (inject odin etc.) unticked. Then press Flash firmware.
{
"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"
}
It will ask to check the md5 file, say yes. Mobile Odin will then do the job automatically, and will upgrade your firmware to lollipop 5.01, the phone will then enter recovery, and then it will upgrade all your applications (about 215 of them). All this will take about 5 minutes.
After reboot, turn the phone off and enter Download mode. Run Odin 3.09 on your PC and put the bootloader file in the BL field (see picture).
Connect the phone, press Start and wait for the Pass.
After reboot, do another factory reset, and redownload SuperSU from Play Store after you go through the initial setup.
That was all; you now have a clean stock Samsung Lollipop firmware which is rooted, and the Knox flag remains at 0x0.
Two things are remaining,
1) Disable the Knox apps, you can do this with Titanium Backup by freezing all the Knox-related things, or you can delete the files manually (e.g. with adb), the forum is full of Knox-removal instructions..
2)Using a root editor, edit the file /system/build.prop, and change the line ro.securestorage.support=false (it is normally set to =true). This solves various problems related to SELinux, also documented in the forum.
Enjoy your rooted Lollipop phone!
Great work man
can you show us your knox status?
I don't understand it. For using mobile odin pro we need to have root access.. right? Then how can I use mobile odin pro to root my phone when I already don't have root access? Do we need to be on kitkat to do this? Or can we do this on lollipop flashed via odin as well?
khsh97 said:
I don't understand it. For using mobile odin pro we need to have root access.. right? Then how can I use mobile odin pro to root my phone when I already don't have root access? Do we need to be on kitkat to do this? Or can we do this on lollipop flashed via odin as well?
Click to expand...
Click to collapse
Yes, if you read more carefully I say that you have to start from a rooted 4.4.2 (kitkat) phone.
c.ozzy said:
Great work man
can you show us your knox status?
Click to expand...
Click to collapse
Sure, attached
Dear Tyxerakias,
YOU SIR, ROCK!!!!!
After following the procedure, I started with my i9505 UK version at 4.4.2 with no root, KNOX 0x0, and now I have latest and greatest Lollipop with root, Titanium, Mobile ODIN, and KNOX 0x0.
System status Modified is the only giveaway, and as we all know that is easily fixed (mine is more than 1 year out of warranty so I don't give a monkey's arse either way).
But this is a very nicely done hack. Also great thanks, of course, to peppe130.
GREAT WORK!
// Descore
Descore said:
Dear Tyxerakias,
YOU SIR, ROCK!!!!!
After following the procedure, I started with my i9505 UK version at 4.4.2 with no root, KNOX 0x0, and now I have latest and greatest Lollipop with root, Titanium, Mobile ODIN, and KNOX 0x0.
System status Modified is the only giveaway, and as we all know that is easily fixed (mine is more than 1 year out of warranty so I don't give a monkey's arse either way).
But this is a very nicely done hack. Also great thanks, of course, to peppe130.
GREAT WORK!
// Descore
Click to expand...
Click to collapse
Thanks, enjoy it By the way, you should now uninstall Mobile Odin, as it doesn't yet work on Lollipop.
Tyxerakias said:
Procedure for installing stock Samsung Lollipop firmwares with Knox 0x0
You can do the upgrade from your 4.4.2 Jellybean, already rooted with Peppe130's method, as described here. You need Mobile Odin Pro and Odin 3.09 for Windows (this is the version that worked for me, I can't say whether different versions work equally well, they might). You also need the bootloader .tar for the version you are installing. The tar needs to include 6 .mbn files, aboot, rpm, tz, and sbl1-3. @ambassadii has included the bootloader .tar for the OB7 firmware in his post here. Then:
Download the firmware you want (e.g. OB7) and the latest SuperSU v.2.46 from @Chainfire's page, and copy both of them on your external SD card.
Factory reset your phone, and only install SuperSU and Mobile Odin Pro from the Play Store (you can obviously backup what you want beforehand with Titanium).
Run Mobile Odin Pro, accept the download of the required file, and then press OTA/Update ZIP and locate the UPDATE-SuperSU-v2.46.zip file you saved on your external SD.
Now press Open File... and choose the .tar.md5 firmware file you also saved a minute ago. Mobile Odin will automatically find and separate the different parts.
Tick only Enable EverRoot, leave the other options (inject odin etc.) unticked. Then press Flash firmware.
View attachment 3223407 View attachment 3223408 View attachment 3223942
It will ask to check the md5 file, say yes. Mobile Odin will then do the job automatically, and will upgrade your firmware to lollipop 5.01, the phone will then enter recovery, and then it will upgrade all your applications (about 215 of them). All this will take about 5 minutes.
After reboot, turn the phone off and enter Download mode. Run Odin 3.09 on your PC and put the bootloader file in the BL field (see picture).
Connect the phone, press Start and wait for the Pass.
View attachment 3223409
After reboot, do another factory reset, and redownload SuperSU from Play Store after you go through the initial setup.
That was all; you now have a clean stock Samsung Lollipop firmware which is rooted, and the Knox flag remains at 0x0.
Two things are remaining,
1) Disable the Knox apps, you can do this with Titanium Backup by freezing all the Knox-related things, or you can delete the files manually (e.g. with adb), the forum is full of Knox-removal instructions..
2)Using a root editor, edit the file /system/build.prop, and change the line ro.securestorage.support=false (it is normally set to =true). This solves various problems related to SELinux, also documented in the forum.
Enjoy your rooted Lollipop phone!
Click to expand...
Click to collapse
You forgot to specify in the title that this is only for i9505.
Enviado desde mi SM-T520 usando Tapatalk 2
Tyxerakias said:
Yes, if you read more carefully I say that you have to start from a rooted 4.4.2 (kitkat) phone.
Sure, attached
Click to expand...
Click to collapse
You have made typo mistake. In your post, it is written "4.4.2 jelly bean" instead of "4.4.2 kitkat".
Tyxerakias said:
Thanks, enjoy it By the way, you should now uninstall Mobile Odin, as it doesn't yet work on Lollipop.
Click to expand...
Click to collapse
Yeah, thanks for letting me know - I felt a bit stupid as I bought Mobile ODIN Pro yesterday just to do this upgrade with your guide, but then I looked in the Mobile ODIN thread and I can see that Chainfire is working on a new app as a replacement, and will give it FREE to all owners of Mobile ODIN Pro :good:
So I don't feel stupid after all :laugh: What a great community.
Hello, this procedure works with a model I9515 ?
I am on 4.4.2 I9505XXUFMB8 rooted with towelroot only and knox 0x0.
Can I follow this guide or do I have to root again with Peppe130's method ?
Thanks
Plumber_Gr said:
I am on 4.4.2 I9505XXUFMB8 rooted with towelroot only and knox 0x0.
Can I follow this guide or do I have to root again with Peppe130's method ?
Thanks
Click to expand...
Click to collapse
Same question here, i'm on I9505XXUGNF1 towelrooted, may i proceed or do i have to update and/or reroot?
update: if it can help you, i just factory resetted, rerooted and followed instructions, all went smooth and now i'm running lollipop.
i guess it won't be a problem if you have the latest 4.4.2 update (i was on GNF1, previous one)
Plumber_Gr said:
I am on 4.4.2 I9505XXUFMB8 rooted with towelroot only and knox 0x0.
Can I follow this guide or do I have to root again with Peppe130's method ?
Thanks
Click to expand...
Click to collapse
Er... Peppe's method IS towelroot... So no, you don't have to root again.
Sent from my GT-I9505 using Tapatalk
I did the root changing the kernel 4.4.2 for a kernel prior to June, the towelroot work in this kernel. After the root back the kernel of the newest room. It is possible to upgrade to lollipop, change the kernel by the kitkat, use towelroot to root, then return lollipop kernel?
n3n3 said:
I did the root changing the kernel 4.4.2 for a kernel prior to June, the towelroot work in this kernel. After the root back the kernel of the newest room. It is possible to upgrade to lollipop, change the kernel by the kitkat, use towelroot to root, then return lollipop kernel?
Click to expand...
Click to collapse
No it's not.
Sent from my GT-I9505 using Tapatalk
Well .. Whats the advantage of keeping the KNOX 0x0 & rooting ??
** A - R ** said:
Well .. Whats the advantage of keeping the KNOX 0x0 & rooting ??
Click to expand...
Click to collapse
Keeping your warrenty
XDAcube said:
Keeping your warrenty
Click to expand...
Click to collapse
Coz my knox is triggered .. and it every time bootloops for CM rom !! ..
.
currently i'am on danvdh's gpe rom ..
.
i eagerly need cm !!..
leonov said:
Hello, this procedure works with a model I9515 ?
Click to expand...
Click to collapse
can some1 explain, if its working with model i9515???
thanx. in advance.
suemer
** A - R ** said:
Well .. Whats the advantage of keeping the KNOX 0x0 & rooting ??
Click to expand...
Click to collapse
If KNOX is 0x0 you can always flash back to a fully non-rooted stock firmware and hand in to warranty repair. Once KNOX triggers, you can never get back to 0. If you don't care about warranty, or having a "clean" device, then you might as well use CF-Root, which is much easier and faster. But this method rocks as you can get your device back to "pristine" as-new condition, should you ever want to for some reason.
---------- Post added at 01:01 AM ---------- Previous post was at 12:54 AM ----------
suemer said:
can some1 explain, if its working with model i9515???
thanx. in advance.
suemer
Click to expand...
Click to collapse
All of the files used for this root are stock, so if you can find the similar ones for i9515 it should probably work. If you can get root using Towelroot, you can probably do the similar steps but with the firmware and bootloader tar's replaced with the appropriate ones for the i9515. There's no guarantee, but if you start with a rooted 4.4.2 my bet is that it would work.
☆★☆ [ROM|RADIO|FIRMWARE][6.0] Stock-Rooted Marshmallow | Sense 7 | m8vzw | 07-03-16
6.21.605.3
-Stock Rooted-
Android 6.0 Marshmallow
{
"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"
}
Firmware files moved to Post #2
ROMS:
Stock Rom Revamped/Final
6.21.605.3_M8_WL_M60_SENSE70_VZW_MR_AROMA-FINAL.zip
I've included a few Aroma options for your choosing:
- Stock System.img and Boot.img without root
- Stock System.img and Boot.img with Chainfire SuperSu root
- Stock System.img and Boot.img with Magisk + Phh Superuser root installed and enabled (will pass SafetyNet w/magisk Hide enabled)
- Encrypted/Decrypted - Choose whether to use Encryption or not
- Debloat - Removes excessive carrier bloat from Vzw and Amazon
- User App Removal - Allows you to choose which Google/Market apps you don't want installed
- Tether Unlock - Enables wireless tethering regardless of your Vzw account type
OLDER FULL STOCK VERSIONS:
Pure Stock Rooted
6.21.605.3_M8_WL_M60_SENSE70_VZW_MR_Full
Pure Stock Rooted
4.17.605.9_M8_WL_L50_SENSE60_MR_Full
Pure Stock
Rooted with Systemless SuperSu v2.67
BusyBox
Nothing else added or removed
___________________
OLDER DEBLOATED STOCK VERSIONS:
Stock Rooted and Debloated
NuSense_of_Stock_M8vzw_6.21.605.3_Debloated
NuSense of Stock Wifi Tether Patch: LINK
4.17.605.9_M8_WL_L50_SENSE60_MR_Debloated
Debloated of Vzw/and downloadable junk (35 apps in all + tutorial vids)
Rooted with SuperSu
BusyBox
System R/W (insecure kernel)
Updated ALL Market Apps in System incl: Sense Home w/themes
Stock m8 boot animation/splash (non-vzw)
Wifi Tether - enabled for all users
10 Unlock Fail device wipe - disabled
Full stagefright patch integrated (fixes remaining vulnerability left from stock OTA)
Replaced Sense 6 wallpapers with ones from Sense 7
Probably a few other minor enhancements...to improve the stock experience
XDA:DevDB Information
★ ☆ Stock-Rooted Marshmallow | Sense 7 | m8vzw ☆ ★, ROM for the Verizon HTC One (M8)
Contributors
santod040
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 6.21.605.3
Based On: Sense 7.0
Version Information
Status: Stable
Created 2015-09-09
Last Updated 2017-04-30
Firmware
FIRMWARE:
MARSHMALLOW:
Combined Marshmallow Firmware Zip
If coming from a previous Android version, you can use the following zip to get caught up on all previous firmwares in one shot.
This zip contains all firmware files from the first OTA through the latest, with the newest files replacing the older ones, while keeping the ones that did not get replaced in newer firmwares.
This will give you all needed firmware files for the current Marshmallow release, no matter what you had previously.
m8vzw_AllInOne_Firmware_6.21.605.3 (will NOT wipe the device)
Otherwise, you can just flash the incremental firmware update posted below:
6.21.605.3_NoBoot-TWRP3.0.0-1_firmware.zip
6.21.605.3_NoBoot-NoRecovery_firmware.zip
6.21.605.3_FULL_firmware.zip
LOLLIPOP:
Combined Lollipop Firmware Zip
If coming from a previous Android version, you can use the following zip to get caught up on all previous firmwares in one shot.
This zip contains all firmware files from the first OTA through the last, with the newest files replacing the older ones, while keeping the ones that did not get replaced in newer firmwares.
This will give you all needed firmware files for the last Lollipop release, no matter what you had previously.
m8vzw_AllInOne_Firmware_4.17.605.9 (will NOT wipe the device)
Otherwise, you can just flash the incremental firmware update posted below:
4.17.605.9 Modified Firmware - Removed stock boot.img and stock recovery and WILL NOT WIPE device
(suitable firmware update for most cases, especially if running custom rom and recovery)
4.17.605.9 Full Firmware - Includes stock boot.img and recovery and WILL WIPE device
No Red Text and Faux Locked Hboots - my m8 hboot thread
4.17.605.9 Stock Recovery
4.17.605.9 Stock Boot.img/Kernel
How to manually flash firmware zips:
(sd card method also works, but I recommend fastboot)
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip to make it simple/optional)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Click to expand...
Click to collapse
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
OTAPkg
For those that want to apply the OTA manually:
Old files:
LOLLIPOP:
4.17.605.9_OTAPkg.zip:
To be applied on stock device with stock recovery only
LOLLIPOP:
Stagefright Patch:
Recovery Flashable Patch
Fixes the one remaining vulnerability that the OTA didn't patch.
__________
Thanks, santod040! Nice to see you around in these parts again!
Awesome! But, what is it? Latest firmware appears to be 4.17.605.5. First guess was Stagefright fix, but that would be done in ROM, not firmware. Did our phone get an OTA today?
dragontology said:
Awesome! But, what is it? Latest firmware appears to be 4.17.605.5. First guess was Stagefright fix, but that would be done in ROM, not firmware. Did our phone get an OTA today?
Click to expand...
Click to collapse
Yeah our phone received a update today
Sent from my HTC6525LVW using Tapatalk
dragontology said:
Awesome! But, what is it? Latest firmware appears to be 4.17.605.5. First guess was Stagefright fix, but that would be done in ROM, not firmware. Did our phone get an OTA today?
Click to expand...
Click to collapse
Yes, there was an OTA to .9 with the stagefright patch/security update.
I'll be posting a full stock rooted rom in a bit...
Awesome thanks santod. Can't wait to get your latest nusense seven. And with this I'll be ready to flash..
Sent from my HTC6525LVW using XDA Free mobile app
I tried the non-wipe fastboot method. It updates through the console correctly, the software version shows the .9 in the boot loader, but when I go to settings and check the version, it still shows the .5 and I get the upgrade nag screen.
Edit: I think I fixed it, I had to go into recovery and wipe my cache and dalvik cache.
Edit2: Nvm, I thought it was fixed because I saw the updating apps window, but it's still .5 in Settings
liquidrezin said:
I tried the non-wipe fastboot method. It updates through the console correctly, the software version shows the .9 in the boot loader, but when I go to settings and check the version, it still shows the .5 and I get the upgrade nag screen.
Edit: I think I fixed it, I had to go into recovery and wipe my cache and dalvik cache.
Click to expand...
Click to collapse
Your updated firmware will show in fastboot mode only.
You will need to update/flash a rom based on the new OTA for Settings/Software info to change.
That is merely showing what rom base/software you are running, not firmware.
They are not one in the same thing.
Full rooted stock rom should be uploading shortly...
santod040 said:
Your updated firmware will show in fastboot mode only.
You will need to update/flash a rom based on the new OTA for Settings/Software info to change.
That is merely showing what rom base/software you are running, not firmware.
They are not one in the same thing.
Full rooted stock rom should be uploading shortly...
Click to expand...
Click to collapse
Ok, thanks for the clarification.
OP Updated
Full Stock Rooted is now live in the OP: - 4.17.605.9_M8_WL_L50_SENSE60_MR_Full
Debloated: - should be up before I have to head off to work. (3 hours until then...)
Debloated version is up!
Stock Rooted and Debloated is now live in the OP
4.17.605.9_M8_WL_L50_SENSE60_MR_Debloated
Debloated of Vzw/and downloadable junk (35 apps in all + tutorial vids)
Rooted with SuperSu
BusyBox
System R/W (insecure kernel)
Stock m8 boot animation/splash (non-vzw)
Updated ALL Market Apps in System incl: Sense Home w/themes
Wifi Tether - enabled for all users
10 Unlock Fail device wipe - disabled
Full stagefright patch integrated (fixes remaining vulnerability left from stock OTA)
Replaced Sense 6 wallpapers with ones from Sense 7
Probably a few other minor enhancements...to improve the stock experience
Hey Santo! Is the OTA that you posted the same one I posted or have you rooted that so we can just install that instead of the full version?
jrg67 said:
Hey Santo! Is the OTA that you posted the same one I posted or have you rooted that so we can just install that instead of the full version?
Click to expand...
Click to collapse
I posted the OTAPkg.zip that I downloaded from Vzw in it's stock patch form, for users that want to apply it manually with stock recovery.
That is in the third post.
I also made a complete full stock rooted rom from it, after applying it to the previous RUU/software version.
That is in the OP, and not only did I post the full stock rooted flashable rom, but I also posted a debloated version of the rom as well, with a few small goodies added.
The links in the OP are full Twrp flashable stock roms.
The files in the second post are firmware from the OTA.
The files in the 3rd post are the OTAPkg.zip which should only be applied if you have the previous stock rom running and stock recovery.
In other words, I posted full rooted Twrp flashable roms and fastboot flashable firmware, so that everyone doesn't have to worry about completely wiping their devices to take an OTA or getting stuck in the process.
Also, in the 3rd post, I posted a stagefright patch, to fix the remaining stagefright vulnerability that HTC/Vzw still left us with, after this OTA. (included in the debloated rom I posted as well)
santod040 said:
I posted the OTAPkg.zip that I downloaded from Vzw in it's stock patch form, for users that want to apply it manually with stock recovery.
That is in the third post.
I also made a complete full stock rooted rom from it, after applying it to the previous RUU/software version.
That is in the OP, and not only did I post the full stock rooted flashable rom, but I also posted a debloated version of the rom as well, with a few small goodies added.
The links in the OP are full Twrp flashable stock roms.
The files in the second post are firmware from the OTA.
The files in the 3rd post are the OTAPkg.zip which should only be applied if you have the previous stock rom running and stock recovery.
In other words, I posted full rooted Twrp flashable roms and fastboot flashable firmware, so that everyone doesn't have to worry about completely wiping their devices to take an OTA or getting stuck in the process.
Also, in the 3rd post, I posted a stagefright patch, to fix the remaining stagefright vulnerability that HTC/Vzw still left us with, after this OTA. (included in the debloated rom I posted as well)
Click to expand...
Click to collapse
Thank you again for all your hard work! Just a fast question about the firmware, can it be loaded via hboot by changing the file name to the 0P6..etc or can it only be loaded via fastboot/pc?
jrg67 said:
Thank you again for all your hard work! Just a fast question about the firmware, can it be loaded via hboot by changing the file name to the 0P6..etc or can it only be loaded via fastboot/pc?
Click to expand...
Click to collapse
No problem. You're quite welcome.
I believe I mentioned in the firmware post, that sd card method works as well. [emoji5]
Sent from my HTC6525LVW using Tapatalk
I must have missed that, you did say sd method works.. That's what I get for skimming quickly for the links and not reading the entire post!
Thanks again sir. Updated firmware and removed red text using SD card method. Worked fine, but just to be safe I ran the hboot install twice for the firmware.
Sent from my HTC6525LVW using Tapatalk
...so the ROM kernel isn't 3.10.X right? Seems to be 3.4.0 from the screenshot
Team Win Recovery Project 3.6.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"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash 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
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
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 it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904
Reserved
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.
costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!
costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data
Everything working!
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:
Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.
Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?
toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733
ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)
xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?
ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.