Hi Sifus,
I owned a SM-N9005 Note 3, with Stock MJ1 Rom, rooted with CF-Auto and installed with TWRP (hlte) 4.3.
So I understood that once upgrading to KK, there's currently no way to downgrade back to JB thus taking this pre-caution to ask for advices. (correct me if I'm wrong)
I am intended to upgrade my Note 3 to a custom KK ROM (eg: XRom, Omega Rom, etc...) however, I am not too sure what's the next step I need to take?
(A) Since I'm rooted with TWRP, go ahead and download the ROM from developer and follow instructions to flash?:victory:
(B) Since I'm still with JB, I need to flash to Stock KK before flashing any custom KK ROM?
(C) Other better ways?
Regards,
SiLvErBoLd17
Some advises please? Anyone?
re: upgrade firmware.
silverbold17 said:
Hi Sifus,
I owned a SM-N9005 Note 3, with Stock MJ1 Rom, rooted with CF-Auto and installed with TWRP (hlte) 4.3.
So I understood that once upgrading to KK, there's currently no way to downgrade back to JB thus taking this pre-caution to ask for advices. (correct me if I'm wrong)
I am intended to upgrade my Note 3 to a custom KK ROM (eg: XRom, Omega Rom, etc...) however, I am not too sure what's the next step I need to take?
(A) Since I'm rooted with TWRP, go ahead and download the ROM from developer and follow instructions to flash?:victory:
(B) Since I'm still with JB, I need to flash to Stock KK before flashing any custom KK ROM?
(C) Other better ways?
Regards,
SiLvErBoLd17
Click to expand...
Click to collapse
#1: Goto http://SamMobile.com and download the latest official stock
KK 4.4.2 firmware for your phone's model Note 3 (N9005).
#2: Download cf-autoroot from: http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
#3: Unzip cf-autoroot into an empty folder on your computer's desktop
and copy the new odin flash kk firmware and twrp into the same folder.
#4: The cf-autoroot zip file comes with Odin which is needed to flash
the stock official firmware, cf-autoroot and twrp recovery.
#5: Download TWRP from here: http://goo.im/devs/OpenRecovery/hlte/openrecovery-twrp-2.7.0.3-hlte-4.4.img.tar
#6: Perform a full wipe including Wipe Data, System, Cache, Dalvik and
last but not least a factory reset in twrp recovery.
#7: Odin flash the stock official firmware which you have downloaded.
#8: Odin flash cf-autoroot.
#9: Odin flash twrp recovery.
Once you have done the above you will be able to flash any of the zip
file custom roms which are designed for the Note 3 N9005 phone.
Good luck!
Related
Guys i was looking for some installation guide but im not sure, if i found the right one. http://forum.xda-developers.com/gala...-roms-t2852310
I have stock 4.4.4 (firmware GNJ8). Is there someone who will not be ofended by noob question and show me some right guide how to flash this GPE rom ? I mean what do i need ? Root (which one?), recovery (which TWRP or CWM (throw CMW manager?)) and something else ? We do not use any knox features in our work, so that should not be a problem.
Thank you for any tips.
Firstly, the provided link does not work. 404 Page not found.
GNJ8..what s4 version is that?
I used CF-Auto-Root to root my s4. But this method does not work on all s4 versions so make sure you read carefully. The third post says on what model of the s4 it works. The thread can be found here.
I use TWRP. CWM just wouldn't flash on my device. Or, if it flashed, it didn't boot into CWM recovery. Kept booting into stock recovery. So I tried flashing TWRP and this one worked so I stick with it.
Make sure that it's the latest firmware for your device. And note that if you're on lollipop, you can't downgrade to kitkat anymore. So you will be stuck on the limited selection of lollipop roms for now.
http://forum.xda-developers.com/galaxy-s4/general/guide-how-to-install-custom-roms-t2852310
sorry for the link.
GNJ8 - European snapdragon version (GT i9505) bought in O2.
CF Auto Root is good idea.
"Make sure that it's the latest firmware for your device." means what exactly ? I have the latest 4.4.4 official stock firmware...
You realize that going from stock to GPE will trip knox, right? Any custom rom or bootloader will trip the knox flag
1. Flash TWRP or Philz recovery true Odin.
2. Wipe data (prepare for new rom) in the recovery.
3. Flash the rom you want with the recovery.
It's as simple as that. You don't need root to do it.
Yep, i know about knox. I dont think i need it.
TWRP which version ? Wipe data/cache (no format /system or similar?) and flash custom rom ? not hard. In fact it sounds so easy that i cant believe What about some post about firmware that with some firmwares you have to do that and sometimes this...
skejpa said:
Yep, i know about knox. I dont think i need it.
TWRP which version ? Wipe data/cache (no format /system or similar?) and flash custom rom ? not hard. In fact it sounds so easy that i cant believe What about some post about firmware that with some firmwares you have to do that and sometimes this...
Click to expand...
Click to collapse
Format system/data wipe of course before flashing a new rom. Pick the version for your phone from TWRP.
Ignore those posts about firmwares.
Just as the title asks, is there any custom recovery available for Verizon S5 running latest rooted, stock ROM? I have been unable to find a straight answer. I know NCG build works with Safestrap, but is there any custom recovery out there for BOC4 build? If not, how have people been installing mods and other zips that require flashing?
MWFD said:
Just as the title asks, is there any custom recovery available for Verizon S5 running latest rooted, stock ROM? I have been unable to find a straight answer. I know NCG build works with Safestrap, but is there any custom recovery out there for BOC4 build? If not, how have people been installing mods and other zips that require flashing?
Click to expand...
Click to collapse
No custom recovery yet. Unless you want to venture into this post.
http://forum.xda-developers.com/verizon-galaxy-s5/help/qa-multisystem-android-t3101203
Flashfire will flash zips and firmware. And do backups. You can get it at the top of this post.
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
You can use flashfire, which is a very easy ways to install ROMs, or, when you want to install a ROM, just flash a Kitkat kernel in Odin and safestrap will work if you have it installed.
mrjiggywiggy said:
You can use flashfire, which is a very easy ways to install ROMs, or, when you want to install a ROM, just flash a Kitkat kernel in Odin and safestrap will work if you have it installed.
Click to expand...
Click to collapse
Can I flash any kit Kat kernel over lollipop BOC4? Or do I have to flash a stock KitKat image too?
MWFD said:
Can I flash any kit Kat kernel over lollipop BOC4? Or do I have to flash a stock KitKat image too?
Click to expand...
Click to collapse
If you had safestrap installed you flash a KitKat kernel right over your OC4 to get safestrap to boot up. Before your phone boots all the way up, go into recovery, and flash your ROM. Boot into download mode via safestrap, Odin the corresponding firmware.
I have used flashfire quite a bit to go up and down. The only problem I had is when I was on NGC. Flashfire wouldn't work for me. I'm no expert but this is how I've done it with flashfire.
1. Hit the plus, select firmware, only check boot and recovery.
2. Hit plus, select zip-ota and your ROM ( don't check auto mount)
3. Hit plus, select firmware again, check boot, recovery, modem, firmware. Flashfire will ask if you want them in separate zips, say yes.
4. Hit plus and wipe. Wipe all but SD card).
Arrange like this
1. Wipe
2. Firmware- boot+recovery
3. ROM
4. Firmware- modem+firmware
5. Firmware-boot+recovery
6. EverRoot - inject SuperSU
7. Reboot
I've gone to OA8, OC4, NI2, and NK2 with no problems. I'm getting ready to test NE9 but like I said I had trouble coming from NGC. Try at your own risk.
Edit: Just went from NI2 to NE9 Alliance ROM with no problems
I made these odin flashable firmwares for those who need them. This is only the stock firmware for Lollipop 5.01 build OB7. (NO system or data partitions) If you need to flash the stock OB7 firmwares then this will do that for you. This will not wipe your system or data.
Once you flash the "OB7-FW.tar.md5" you must reroot and flash a custom recovery if you want to flash custom roms etc. Simply odin flash cf-auto-root and the latest recovery by TWRP and you'll be back in business.
The OB7-modem.tar.md5 requires no extra steps... it's just the modem.
I have tested these packages on my Note 4 running OB7 firmware. Note: If you are on OE1 firmware, you will NOT be able to flash this OB7 firmware successfully due to new security measures in the OE1 bootloader.
OB7-FW.tar.md5 This tar package includes all of the stock OB7 firmware including kernel,modem, recovery, bootloader, etc. Please flash this in odin on your PC ONLY!
OB7-modem.tar.md5 This tar package includes only the modem and HLOS patch. Can be flashed with odin on your pc and also mobile odin.
Gonna try
tx_dbs_tx said:
I made these odin flashable firmwares for those who need them. They are the stock firmware for Lollipop 5.01 build OB7. If you need to go back to the OB7 firmwares then give this a try. This will not wipe your system or data.
Once you flash the "OB7-FW.tar.md5" you must reroot and flash a custom recovery if you want to flash custom roms etc. Simply odin flash cf-auto-root and the latest recovery by TWRP and you'll be back in business. The OB7-modem.tar.md5 requires no extra steps... it's just the modem.
I have tested these packages on my Note 4 running OB7 firmware. OE1 bootloader/recovery may not allow flashing back to older firmware. (I haven't tested with OE1 firmware) Please report your success or failure when flashing this over your OE1 firmware.
OB7-FW.tar.md5 This tar package includes all of the stock OB7 firmware including kernel,modem, recovery, bootloader, etc. Please flash this in odin on your PC ONLY!
OB7-modem.tar.md5 This tar package includes only the modem and HLOS patch. Can be flashed with odin on your pc and also mobile odin.
Click to expand...
Click to collapse
I just tried this and I got the following error:
UDC START
SW RED CHECK FAIL : [tz]Fused 2 > Binary 1
I am using Odin 3.07, running Windows 7.
tx_dbs_tx said:
I made these odin flashable firmwares for those who need them. They are the stock firmware for Lollipop 5.01 build OB7. If you need to go back to the OB7 firmwares then give this a try. This will not wipe your system or data.
Once you flash the "OB7-FW.tar.md5" you must reroot and flash a custom recovery if you want to flash custom roms etc. Simply odin flash cf-auto-root and the latest recovery by TWRP and you'll be back in business. The OB7-modem.tar.md5 requires no extra steps... it's just the modem.
I have tested these packages on my Note 4 running OB7 firmware. OE1 bootloader/recovery may not allow flashing back to older firmware. (I haven't tested with OE1 firmware) Please report your success or failure when flashing this over your OE1 firmware.
OB7-FW.tar.md5 This tar package includes all of the stock OB7 firmware including kernel,modem, recovery, bootloader, etc. Please flash this in odin on your PC ONLY!
OB7-modem.tar.md5 This tar package includes only the modem and HLOS patch. Can be flashed with odin on your pc and also mobile odin.
Click to expand...
Click to collapse
ive been searching but can you help me put stock 0e1 recovery back on my phone i forgot to factory data reset after i updated to 0e1 and rerooted and now my phone is super buggy and i think its because i didnt wipe on stock recovery which usually fixes my problems. thanks if you can help or not. ive wiped on twrp of course but my stock rooted 0e1 rom just isnt right idk but like i said the stock recovery to me really wipes evrything. ive tried aosp roms but there even more buggy can you please help thanks
No one has it yet
Right. There is no official tar ball available for OE1 firmware. OTA is the only way right now and nobody has pulled and uploaded the update zip for OE1. Im afraid you're gonna have to try the OB7 official rom tar or else you're stuck until a tar pops up somewhere. And that may not happen for OE1.
PeteSeiler2010 said:
I just tried this and I got the following error:
UDC START
SW RED CHECK FAIL : [tz]Fused 2 > Binary 1
I am using Odin 3.07, running Windows 7.
Click to expand...
Click to collapse
Thanks for the report. Which software version are you currently on? Extension OB7 or OE1 ??? You must be on OE1 because it flashed successfully on my OB7 software. I will upload another version for you to test.
Yes, I am on OE1, I will gladly test for you. Just keep me posted.
So just to clarify, if I am on KK, I can ODIN this then cf auto root then TWRP? And don't take the update to OE1 because it's not worth it?
Sent from my SM-N910P using XDA Free mobile app
beezar said:
So just to clarify, if I am on KK, I can ODIN this then cf auto root then TWRP? And don't take the update to OE1 because it's not worth it?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Ok, don't mess with this, it's for a different purpose. Read the OP in @tx_dbs_tx 's hybrid X 2.2 rom thread here:
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully as there is a VERY specific procedure (it's easy) you MUST follow to move up to lollipop.
Stock tar in the OP here:
http://forum.xda-developers.com/showthread.php?t=3056478
If you'd rather have a stock rom instead of hybrid x download the stock tar and follow tx's instructions to the T in his Hybrid-X OP before flashing it or any lollipop based rom.
Remember, you MUST flash the stock OB7 tar BEFORE flashing any lollipop rom.
EDIT: If you decide to go stock, do not take the ota. Once you cf-auto-root & odin twrp you won't have to worry about it anymore. The same with Hybrid-X. Once you flash that no more OTA worries.
Did u find the hidden image ??
I'm not going to pursue the OE1 secured bootloader thing. We will have to wait for an official tar ball and rebuild roms from it. Until then I'm staying on my OB7 rom.
I dont quit but thanks for your efforts
pbedard said:
I dont quit but thanks for your efforts
Click to expand...
Click to collapse
Have at it... Keep us posted.
Meh sourcecode is out
Hi all,
I want to install ROM by _alexndr on a new G900F. I want to keep KNOX 0x0, so I need root to flash this ROM using flashfire.
However, the device came with android 5 when I bought it, so towelroot does not work. If I understood correctly, I have to flash stock 4.4.2 firmware (where do I get it? which tool to use for flashing? Just flash, or other things to take care of?), then I can use towelroot and flash ROM by _alexndr with flashfire. Did I miss anything important?
Get the ROM and ODIN the flashing tool from sammobile .com firmware section
Instructions under the download (Free account might be needed to download the ROM)
Can I just flash the old 4.4.2 firmware over the current 5.0 firmware, or do I have to consider something else?
I've flashed KK over LP before, and first boot didn't boot, flashed it again the same way, and it booted fine
Might need to factory reset before/after flashing if you have problems
Okay, here is the deal. I was trying to install a costum rom on my att galaxy s4. What I did was I rooted it using king root and tried to flash a rom through rom toolbox, but I believe it was just going to take me to my recovery. After that the screen got stuck on the costum screen with the padlock, and only seems to turn on with a charger plugged into it. I am on 5.0.1 lollipop and have managed to flash the original recovery, but any stock rom I try to flash using Odin fails by saying complete thread failed or something like that, and says on my phone binary 1 or something like that. I really need help on where to start.
Thanks
What is the exact Odin error?
AT&T never released a full firmware for flashing via Odin beyond 4.1.2. Look here for a possible solution: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Once the phone is running a 4.3 or higher bootloader, the bootloader is locked and custom ROMs can't be installed unless the custom ROM is based on a stock ROM.
There's an ODIN flashable Android 4.2.2 MDL bootloader tar file out there somewhere too.
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
audit13 said:
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
Click to expand...
Click to collapse
Are there any other options, or should I just give up on it?
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2
audit13 said:
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2
Click to expand...
Click to collapse
I finally fixed it. I had downloaded that rom before, but it hadn't worked. I decided to try it again and used a different USB port and it worked! Thanks for the help!