This is for any other weary guy who ran into a problem similar to mine.
Flashed the MJ7 BTU firmware to my Hong Kong N9005 today.
It flashed the kernel and recovery but the moment it reached the system, it gave an error saying 'invalid ext4 image'.
Tried a couple of more BTU firmwares to no avail.
Installed a custom recovery (tripping knox) and then a prerooted MJ7 firmware through CWM. It ran into a bootloop.
Then a custom rom based on MK2. The rom had a lot of lag and calling didn't work at all.
Flashed another custom ROM to the same effect.
After flashing a lot more stock firmwares (none of which ever got across the 'invalid ext4 image' error), I finally tried flashing a pre-rooted ROM (MJ7 via Odin) from this thread:
Even it ran into the same error on trying to flash the system but before trying to flash system, it flashed everything else. This updated my baseband to MJ7 (was MI5 or MI7 before this. Don't remember).
After this, the custom roms work fine, though I still cannot find a way to flash stock roms to my note 3.
Press thanks if I helped.
It didn't help me as I want to fix this without tripping Knox if I can, but at least I can see it will work, maybe, if I am willing to just say eff it and root anyway.
F*ck Knox. Trip it. It smells better.
FeralFire said:
F*ck Knox. Trip it. It smells better.
Click to expand...
Click to collapse
Indeed DD
Hi,
I´m a neewbie to Samsung. My phone is a S6 SM-G920F, Baseband G920FXXU1AOCW
I came form an HTC and I´ve seen that flashing things are very different. So here are my questions:
1. I think, my bootloader is unlocked but I didin´t know for sure. So how can I check this?
(My HTV showed me this by using fastboot, didn´t know if there is fastboot with Samsung and how to start it - only know the download-mode and how to enter TWRP recovery)
2. Flashing firmware via Odin (i. e. from sammobile.com) means to loose my root again, right?
3. If I loose root, where do I get custom Firmwares and how do I flash them (if this is possible)?
4. If not, is it enough to flash bootloader and modem through Odin?
All answers are appreciated. Thanks in advanced.
Maybe someone can link me to an step to step instruction...
Fastboot is android doesn't matter who makes the phone.
If you flash a rom from sammobile then you will go to whichever stock you pick.
Other ROMs are available here. The phone is new. There aren't many yet. Cyanogen mod isn't available yet.
Root is available by flashing cfautoroot with Odin. You will need to get the specific one.
You can replace the recovery by flashing twrp team win recovery project with Odin.
You can flash boot loader and modem. Make sure you get the right region. The modem frequencies are different in different places.
You may find flashing a whole ROM even stock will fail. This is because the partitions are not the same size for all s6 stock ROMs. Don't ask me why. You can open the tar find which file stopped the flash delete it from the tar and flash again.
quatzar said:
Fastboot is android doesn't matter who makes the phone.
If you flash a rom from sammobile then you will go to whichever stock you pick.
Other ROMs are available here. The phone is new. There aren't many yet. Cyanogen mod isn't available yet.
Root is available by flashing cfautoroot with Odin. You will need to get the specific one.
You can replace the recovery by flashing twrp team win recovery project with Odin.
You can flash boot loader and modem. Make sure you get the right region. The modem frequencies are different in different places.
You may find flashing a whole ROM even stock will fail. This is because the partitions are not the same size for all s6 stock ROMs. Don't ask me why. You can open the tar find which file stopped the flash delete it from the tar and flash again.
Click to expand...
Click to collapse
Thanks for answering. My questions had an other intention, I think.
My S6 is already rooted and I have a custom recovery (TWRP) :good:
I would like to know if you have to flash a whole firmware or only bootloader/modem? Because I didn´t seen a post here for a full firmware yet.
I am not familiar with the differences between htc whole firmware and samsung bootloader/modem
Actually I am on Firmware G920FXXU1AOCW. But there are newer ones like XXU1AOE3 or XXU1AOE4.
In the days of my htc you couldn´t flash only bootloader or modem, you had to flash a whole firmware (like radio, drivers, bootloader, modem etc.)
Flashing only modem and bootloader will it update i. e. touchscreen drivers? If not, where do I get this ones? You know, because of root I don´t get OTA´s anymore...
The modem just controls how your phone hardware connects to carrier towers etc.
The boot loader is a tiny thing that tells the processor where and how to load the OS.
The software for pretty much everything is in /system.
Many of these releases are the same software, region specific. The dates are fairly unimportant for the same version number. They generally reference the time when they were uploaded by someone. Not that they have updates and fixes.
Just wanted to know can I change my phone logo MetroPCS to say T-mobile with all the T-mobile add on. I have a Samsung Galaxy s6 by MetroPCS
I got the Galaxy S6 yesterday and coming from Nexus 5, I wanted to remove the existing bloatware by flashing the XtrestoLite Deodexed ROM. This one here: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-xtrestolite-deodexed-mod-edition-1-3-t3119968
I'm haven't had much experience in rooting and it's my first time flashing a custom ROM. The phone was running on Android 5.1.1.
Apparently I failed. I started with CF-Root but I wasn't sure if it was done correctly. This was followed by TWRP 2.8.7.1 . Then I tried booting up the phone and the boot logo just loops. I tried to wipe the cache as well as the Delvik-cache through TWRP but it's still the same. Then I tried to flash the stock ROM that I found online but I got the error "Nand Write Start" followed by "Fail". I seem to have tried everything and now I just want to get the phone to work again. It shouldn't be so hard.
Someone help me please :crying:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Gallitho said:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Click to expand...
Click to collapse
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Edit: I managed to do it through initialization. I'll update when it's done.
Edit 2: It worked! Thanks so much!
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
1qazwsx4 said:
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
Click to expand...
Click to collapse
How could I transfer the flashable ROM to the phone when I can't have it boot up to connect to my computer?
Gallitho said:
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
Click to expand...
Click to collapse
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Can you guys help me check if this post has the correct steps or is it missing anything like bootloader and root?
reddit.com/r/GalaxyS6/comments/39wwf6/should_i_install_xtrestolite_rom/cs7b7yq
ztmj96 said:
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Click to expand...
Click to collapse
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Gallitho said:
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Click to expand...
Click to collapse
1. So what is the correct order?
2. Did you have to manually unlock bootloader?
3. And is it a must to install uniKernel in order to root the device?
I have no idea how to proceed now.
This requires a lot more effort than I thought :fingers-crossed:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Gallitho said:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Click to expand...
Click to collapse
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
ztmj96 said:
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
Click to expand...
Click to collapse
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Gallitho said:
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Click to expand...
Click to collapse
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
ztmj96 said:
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
Click to expand...
Click to collapse
Glad to read that, dude!
Yep, our situations are identical and also happened at the same time haha.
Now's time to enjoy! :good:
Hi all, I'm sorry if this is a stupid question but I just wanted to make sure I don't mess up my phone.
So I had flashed a Custom ROM (Resurrection Remix) on my Galaxy S7, but after a while I wanted to reflash it back to stock 8.0 Oreo which I have done successfully. Now of course the knox counter has been tripped, however the phone is unrooted and also no longer has TWRP as its recovery (just the standard android recovery now).
Now that I have flashed it back to stock, would it be safe to perform OTA updates on the phone? Someone had told me it would not be possible as I had flashed a custom ROM before and I just wanted to get some other opinions.
Thanks in advance!
OTA updates gonna work fine
Hey guys, I rootrd my phone about a week ago and installed Pie rom. However is it possible to get my previous original android and unroot my phone to be like I bought it?
Thanks!
Yes, if you download the stock firmware files from a firmware host (updato.com, sammobile.com) or from samfirmtool, then do a full flash with Odin, it will essentially be like it was factory new.
However the exception is the knox trigger, once tripped it can never be reversed.
Downgrading may require bootloader unlock and a custom version of Odin, otherwise you could flash an older firmware with TWRP to downgrade then reflash with Odin