Database Info

[GUIDE] Unroot / Unbrick, Flash official stock firmware on Galaxy SII Plus GT-I9105/P

Here is a full guide on how to unroot and back to official stock firmware for Galaxy SII Plus GT-I9105/P. It is useful also if you soft brick your phone​
!!!BE SURE THAT YOU ARE FLASHING THE RIGHT FIRMWARE FOR YOUR VARIANT!!!​Do it on your own responsibility! if you follow this guide properly u will be on the safe side ​
{
"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"
}
Before we proceed, make sure:
1-You have installed your Samsung Galaxy SII Plus GT-I9105/P USB drivers on your PC (the easiest way is to install Kies).
2-You need to enable USB debugging mode (Settings>Developer options) which is deactivated by default.
3-Your SII Plus GT-I9105/P should have 70-80% charge remaining.
4-Your SII Plus GT-I9105/P should be factory unlocked.
5-Backup your important data like Call logs, SMS and other data stored in phone memory in case if anything goes wrong, your data is not hurt.
6-Make sure that kies program is not running & disable antivirus.
This guide is only for Galaxy SII Plus GT-I9105/P. So don’t bother to try it on other devices.
How to do it:
Step 1) Turn OFF your mobile and go to Download Mode by pressing and holding the Volume Down + Home Buttons together for few seconds followed by Power button then proceed with volume up. (For some phones, when you see the construction Android robot and a triangle, press Power again to confirm to enter into Download Mode).
Step 2) Now open ODIN on your PC and connect your Galaxy SII Plus GT-I9105/P to your computer.
Step 3) Once your phone is successfully connected to your PC, the ID:COM box on ODIN will turn blue and will show the COM port number.
Step 4) unzip the downlowded file, u will get a Home.tar file.
Step 5) click on pda in odin (if odin 3.09 choose AP) and choose the file "xxxx.tar.md5"
Step 6) check "Auto Reboot" and "F. Reset Time" options and make sure that "Re-Partition" is unchecked
!!!!DO NOT CHECK "Nand Erase All" IN ANY WAY!!!!
Step 7) Click on Start button in ODIN window to start the installation process. The process will take few minutes to complete.
DO NOT UNPLUG USB CABLE WHILE EXECUTING THE PROCESS, YOU MAY BRICK YOUR PHONE!
Step 8) When the installation is completed, you read a "Pass". your phone will restart (first boot will take a longer time so don't panic) :good:
It is recommended to make hard reset after flashing to have a fresh official firmware ​
NOTE: I prefer to perform data and cache wipe before and after flashing stock firmware.
NOTE 1: If you have a corrupted partition table, (Odin says: "there is no pit partition" or "Re-Partition operation failed"), flash pit file for your device (attached) (put it in pit window) with your firmware, in this case "Re-Partition" must be marked.
NOTE 2: If it happen, and your new csc doesnt stick (the product code), usually a hard reset can solve this issue, or root it again and use third party application like "csc changer".
NOTE 3: For warranty reason, and if you have rooted your SII plus, you must reset the binary counter. Some users report that "Triangle away" application works on SII plus, do it when you still rooted and you have stock kernel and recovery.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Try another computer.
Download Links:​Odin
For Latest firmwares see second post​​
Don't forget to press THANKS & RATING buttons!

Firmwares links:
I9105 samsung-update.com
I9105P samsung-update.com

Reserved

Thanks for the Contribution brother

Step 5) click on pda in odin (if odin 3.09 choose AP) and choose the file "Home.tar"
Click to expand...
Click to collapse
Instruction is pretty clear, except step 5. I downloaded the correct rom, bit the zip-file doesn't contain a Home.tar at all?
Did I miss something here?

Bart-NL said:
Instruction is pretty clear, except step 5. I downloaded the correct rom, bit the zip-file doesn't contain a Home.tar at all?
Did I miss something here?
Click to expand...
Click to collapse
choose the xxxxxxxx_xxxxxxxx.tar.md5 file

Bart-NL said:
Instruction is pretty clear, except step 5. I downloaded the correct rom, bit the zip-file doesn't contain a Home.tar at all?
Did I miss something here?
Click to expand...
Click to collapse
Just extract the whole zip file and you will get what u need and what it means
Sent from my GT-I9105P using XDA Premium 4 mobile app

thanks but....
why 912 MB?
does it contain stock rom?or another rom?
if it's same stock rom lots of people already have it please give us only home.tar file. it takes me 12 houers to download and host won't let resume downloads and my pc can't maintain that much (but thanks anyway that's my problem)
-please someone tell what that 912MB file in third post contains?
another question about unrooting: i flashed CWM recovery via odin and then two files flashed with recovery(volume up+home+power) to root how can i restore them?(i don't care about triangle or warranty)
another issue:according to this post >> [GUIDE] [4.1] How to root and install CWM by panda00 if someone doesn't care about binary counter unrooting is just about flashing stock frimware with odin, what about that?
what's my problem?:i rooted my phone to use more storage space by deleting unnecessary system apps and moving my apps to system app folder instead(which i failed) but main problem is after rooting and wiping everything 249MB is mising
"sorry for long noob question and bad english and thanks"

vahid8910 said:
why 912 MB?
does it contain stock rom?or another rom?
if it's same stock rom lots of people already have it please give us only home.tar file. it takes me 12 houers to download and host won't let resume downloads and my pc can't maintain that much (but thanks anyway that's my problem)
-please someone tell what that 912MB file in third post contains?
another question about unrooting: i flashed CWM recovery via odin and then two files flashed with recovery(volume up+home+power) to root how can i restore them?(i don't care about triangle or warranty)
another issue:according to this post >> [GUIDE] [4.1] How to root and install CWM by panda00 if someone doesn't care about binary counter unrooting is just about flashing stock frimware with odin, what about that?
what's my problem?:i rooted my phone to use more storage space by deleting unnecessary system apps and moving my apps to system app folder instead(which i failed) but main problem is after rooting and wiping everything 249MB is mising
"sorry for long noob question and bad english and thanks"
Click to expand...
Click to collapse
the 4.2.2 zip is 912 MB, the firmware is arround 1.3 GB (after unzipping, the tar.md5 file)
yes it is a pure stock official rom, it contains, sboot, system, recovery, kernel, cache, param, radio........
you can unroot back to stock by flashing the stock firmware posted in third post!
for other issues, post in rooting thread :good:

Go back to the stock !!
hey there I have I9105XXUBMH4_I9105OXEBMH3_SER.zip file it just contains the pda file so I wanna reflash the stock rom (cuz i'm already running 4.2.2 by flashing this pda) can I just reflash the rom bly flashing this pda file ??
plz answer me as fast as possible.
thx

Bilal.Android said:
hey there I have I9105XXUBMH4_I9105OXEBMH3_SER.zip file it just contains the pda file so I wanna reflash the stock rom (cuz i'm already running 4.2.2 by flashing this pda) can I just reflash the rom bly flashing this pda file ??
plz answer me as fast as possible.
thx
Click to expand...
Click to collapse
Sure you can, but why don't you factory reset?

Raven_Yen said:
Sure you can, but why don't you factory reset?
Click to expand...
Click to collapse
My phone is now slow btw my phone is rooted is it work ??
Sent from my GT-I9105 using XDA Premium 4 mobile app

Bilal.Android said:
My phone is now slow btw my phone is rooted is it work ??
Sent from my GT-I9105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you want to go to clean stock without root, you need to flash through Odin. I am not aware of any unroot method for i9105(P) without using Odin yet.
Or you can factory reset if you still want a rooted status (I think the root still stays if you factory reset, correct me if I'm wrong)
Make sure you backup important datas, files, pictures in your internal storage before factory reset / re-flash firmware.

Raven_Yen said:
If you want to go to clean stock without root, you need to flash through Odin. I am not aware of any unroot method for i9105(P) without using Odin yet.
Or you can factory reset if you still want a rooted status (I think the root still stays if you factory reset, correct me if I'm wrong)
Make sure you backup important datas, files, pictures in your internal storage before factory reset / re-flash firmware.
Click to expand...
Click to collapse
Yes you are right the root even stays if you factory reset the device. Well after formatting everything ,stock rom has to be flashed by using odin after that you will find the binary counter increased. It will be cleared by sing TRIANGLE AWAY app. By this you can easily bring the binary counter to 0. By doing all this you will get the status stock

android.zealot.fervor said:
Yes you are right the root even stays if you factory reset the device. Well after formatting everything ,stock rom has to be flashed by using odin after that you will find the binary counter increased. It will be cleared by sing TRIANGLE AWAY app. By this you can easily bring the binary counter to 0. By doing all this you will get the status stock
Click to expand...
Click to collapse
I never remove binary counter in stock (rooted) ROM before.
Should we Triangle Away first in rooted stock, then flash clean stock ROM using Odin and get official+zero binary after that?
(Or pre-rooted stock ROM )

android.zealot.fervor said:
Yes you are right the root even stays if you factory reset the device. Well after formatting everything ,stock rom has to be flashed by using odin after that you will find the binary counter increased. It will be cleared by sing TRIANGLE AWAY app. By this you can easily bring the binary counter to 0. By doing all this you will get the status stock
Click to expand...
Click to collapse
But the thing is, wouldn't you need to re-root again to use triangle away? Hence, considering you want to return to stock, you would have to flash a stock firmware via odin to unroot. But then again, it would increase the binary counter?

Raven_Yen said:
I never remove binary counter in stock (rooted) ROM before.
Should we Triangle Away first in rooted stock, then flash clean stock ROM using Odin and get official+zero binary after that?
(Or pre-rooted stock ROM )
Click to expand...
Click to collapse
You need root to use triangle away. After using, just flash stock directly. Don't go into cwm or it will trigger the counter again
Sent from my GT-I9105P using XDA Premium 4 mobile app

Brian_SGW_CM9 said:
You need root to use triangle away. After using, just flash stock directly. Don't go into cwm or it will trigger the counter again
Sent from my GT-I9105P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ah, that's my guess and you confirmed for me.
I ended up having binary counter at 5 after upgrading CM11 from stock 4.2.2.
Does the previous binary counter (before re-flashing stock 4.2.2) counted inside?
I don't recall entering recovery mode that much in CM11.

wipe everything and factory reset via recovery
flash stock rom via odin
thats my way without triangle away..

Not sure if my phone is unlocked,,,how can I tell? The *# thing in dialer doesnt work

[SOLVED] Stuck in DOWNLOAD mode after failed ODIN frimware update [SOLVED]

For those in need I have just received another confirmation that my solution works. Here are the details!
Sooo... let me explain before you begin recovery (and it will work, believe me!). 1) worry not!) 2).... the whole wrong comes from Odin. No matter what version of Odin you're using (and I used 3.10.6) and what firmware are you trying to flash (original, not so original, with MD5 or without) Odin will **** up your phone and get you stuck to the bloody "Downloading" screen. For me it happened after having a custom ROM installed and trying to revert to Vodafone UK original rom (namely "G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5"). DITTO! On some S6s ODIN will ruin your life and you can check that there are other similar horror stories around.
HOW DO I FIX THIS?
Well... pretty simple! Thank God! The idea is that once you reboot you phone and it shows as stuck in "Download" screen you have to flash the "recovery.img" that is actually inside the ".TAR" or ".TAR.MD5" file you have just flashed.
To do so you have to actually put the "recovery.img" you have just extracted from the ".TAR.MD5" (or just ".TAR) into a flashable file that ODIN understands. Yes, your'e right, in a blah-blah.tar.md5 or blah-blah.tar file.
To do so I have downloaded and installed 7Zip (since it's able to mangle .tar files as opposed to WinRAR) and also downloaded a "pristine" .tar file like the TWRP recovery (e.g. twrp-2.8.6.2-zeroflte.img.tar). The TWRP fil actually contains in it a modified "recovery.img" file.
Further on I have created a copy of the TWRP recovery file and named it "my-recovery.img.tar" (or call it whatever it fits you), opened it up in 7Zip and just dragged the "recovery.img" (you have extracted previously from the exact firmware ODIN has ruined at flashing last time) over the existing one in the archive. Click OK when 7Zip will prompt you that you are going to overwrite the existing "recovery.img" and you are done.
Now simply flash the "my-recovery.img.tar" via ODIN to you S6 and once done you'll have a functional phone with the latest firmware!
DON'T FORGET to go into the newly created recovery and factory reset! For your own safety the CSC has to be aligned from one old firmware to the new one.
Here is the recovery image for Italy (Vodafone) 5.0.2 G920FXXU1AODG to get you out of the trouble with the latest firmware (get it here):
my-recovery.img.tar
ATTENTION
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
The solution is, once you go through the procedure I have described, to open up Samsung Smart Switch (the new "KIES" for S6 and S6 Edge), go to "MORE" --> "Emergency software recovery and initialization" and perform that task! I will actually re-write the latest firmware you have flashed to your phone BUT will also solve the ODIN issues. On my phone, after doing so, I was able to flash this latest Vodafone Italy I have uploaded here.
The "Emergency software recovery and initialization" procedure has to be completed BEFORE you finish the setup procedure of your S6, you know the "WiFi" / Accounts / blah, blah (after flashing the firmware) and not afterwards. It least so I discover it to work.
Please let me know how this tutorial worked for you.

Will this prosedure trip KNOX?

It will not trip KNOX because it is a signed firmware that you're flashing with Odin.

Everything worked fine but not the Smart switch part. My device doesn't show up here in the list. How do I proceed?

Here.
{
"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"
}

h3llboy911 said:
Here. View attachment 3321069
Click to expand...
Click to collapse
Select the right tab and fill in there your phone's model after it confirms fill in your s/n number (phone's)... youll find the details on phonr box

This is what it says when I select the right tab. Looks like my device i snot supported. Any alternatives? I want to able to flash roms again.

Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!

AskinSavascisi said:
Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!
Click to expand...
Click to collapse
Why are we facing this flash fail error first of all? Is it because I had reactivation lock tuned on?

If u have it on, u wont be able to use odin... i had the same issue thats why i went with smart switch but it seems u have a problem with your device Model (not supported)... smart switch doesnt care if your reactivation lock is off or on

AskinSavascisi said:
If u have it on, u wont be able to use odin... i had the same issue thats why i went with smart switch but it seems u have a problem with your device Model (not supported)... smart switch doesnt care if your reactivation lock is off or on
Click to expand...
Click to collapse
I don't remember turning reactivation lock on before flashing with odin. I googled about the issue and it seems like it's a partition issue and we need to flash the correct .pit file to fix the issue. Till then every firmware that is flashed is going to fail at hidden.img.
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
and as the OP has stated, Smart Switch fixes this partition issue but sadly my device is not supported by it.
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
This what the OP has stated.
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
Click to expand...
Click to collapse

AskinSavascisi said:
Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!
Click to expand...
Click to collapse
Just to confirm, does flashing rom from sammobile using Odin will wipe phone? I know it will not trip knox, but is there any chance to flash official rom without wiping it?

Ollve said:
Just to confirm, does flashing rom from sammobile using Odin will wipe phone? I know it will not trip knox, but is there any chance to flash official rom without wiping it?
Click to expand...
Click to collapse
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.

h3llboy911 said:
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.
Click to expand...
Click to collapse
The point is I'm still on OCV rom (not branded) and I'd like to flash at least OE2-4 with ram fixes and possibly root right after update. Then wipe when we get official 5.1.1.
Waiting for OTA is so pointless in this case...

h3llboy911 said:
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.
Click to expand...
Click to collapse
If its the same pda not really needed

AskinSavascisi said:
If its the same pda not really needed
Click to expand...
Click to collapse
Different, from OCV to OE3/OE4. So probably worth to try without wipe and in case I get FC/bootloops - wipe.

ollve said:
different, from ocv to oe3/oe4. So probably worth to try without wipe and in case i get fc/bootloops - wipe.
Click to expand...
Click to collapse
???

Well, thanks for this

I was trying to install TWRP and my phone got soft bricked. I tried flashing the Trinidad and Tobago firmware that I had and got this "hidden.img fail!" error.The solution to recover the phone is well-explained by the OP and it works like charm.
A lot of people had faced the same issue over the S6 and S6 edge forums
-Some people told that the phones partitions are messed up and I needed to flash the correct PIT file to be able to flash any FW again. Otherwise it will fail every time.
-Some people told that I had "Reactivation lock"(Find my Samsung's feature) enabled and that's why I am facing the error. (In that case, we get a different error while flashing via ODIN or factory reseting, not hidden.img failed error.
The error is because of the FIRMWARE you are flashing is not supported. Yes! I recovered my phone by flashing the latest Indian firmware and it worked like charm. So the lesson here is, EVEN WHEN THE DEVICE MODEL IS SAME(925I), THE FIRMWARES FROM DIFFERENT COUNTRIES ARE NOT COMPATIBLE WHEN FLASHED VIA ODIN. (At least in my case and a few other who confirmed)
PS: The same firmware works if done by FLASHFIRE but ODIN fails.

dehnhaide said:
For those in need I have just received another confirmation that my solution works. Here are the details!
Sooo... let me explain before you begin recovery (and it will work, believe me!). 1) worry not!) 2).... the whole wrong comes from Odin. No matter what version of Odin you're using (and I used 3.10.6) and what firmware are you trying to flash (original, not so original, with MD5 or without) Odin will **** up your phone and get you stuck to the bloody "Downloading" screen. For me it happened after having a custom ROM installed and trying to revert to Vodafone UK original rom (namely "G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5"). DITTO! On some S6s ODIN will ruin your life and you can check that there are other similar horror stories around.
HOW DO I FIX THIS?
Well... pretty simple! Thank God! The idea is that once you reboot you phone and it shows as stuck in "Download" screen you have to flash the "recovery.img" that is actually inside the ".TAR" or ".TAR.MD5" file you have just flashed.
To do so you have to actually put the "recovery.img" you have just extracted from the ".TAR.MD5" (or just ".TAR) into a flashable file that ODIN understands. Yes, your'e right, in a blah-blah.tar.md5 or blah-blah.tar file.
To do so I have downloaded and installed 7Zip (since it's able to mangle .tar files as opposed to WinRAR) and also downloaded a "pristine" .tar file like the TWRP recovery (e.g. twrp-2.8.6.2-zeroflte.img.tar). The TWRP fil actually contains in it a modified "recovery.img" file.
Further on I have created a copy of the TWRP recovery file and named it "my-recovery.img.tar" (or call it whatever it fits you), opened it up in 7Zip and just dragged the "recovery.img" (you have extracted previously from the exact firmware ODIN has ruined at flashing last time) over the existing one in the archive. Click OK when 7Zip will prompt you that you are going to overwrite the existing "recovery.img" and you are done.
Now simply flash the "my-recovery.img.tar" via ODIN to you S6 and once done you'll have a functional phone with the latest firmware!
DON'T FORGET to go into the newly created recovery and factory reset! For your own safety the CSC has to be aligned from one old firmware to the new one.
Here is the recovery image for Italy (Vodafone) 5.0.2 G920FXXU1AODG to get you out of the trouble with the latest firmware (get it here):
my-recovery.img.tar
ATTENTION
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
The solution is, once you go through the procedure I have described, to open up Samsung Smart Switch (the new "KIES" for S6 and S6 Edge), go to "MORE" --> "Emergency software recovery and initialization" and perform that task! I will actually re-write the latest firmware you have flashed to your phone BUT will also solve the ODIN issues. On my phone, after doing so, I was able to flash this latest Vodafone Italy I have uploaded here.
The "Emergency software recovery and initialization" procedure has to be completed BEFORE you finish the setup procedure of your S6, you know the "WiFi" / Accounts / blah, blah (after flashing the firmware) and not afterwards. It least so I discover it to work.
Please let me know how this tutorial worked for you.
Click to expand...
Click to collapse
i simply cant work out this line.. after extracting the firmware file, i only get 1 xxxxxx.tar.md5
how do i actually change the recovery thing?

Help rooting Tmobiles sm-n920t 6.0.1

Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)

jaycuzhommie said:
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
Click to expand...
Click to collapse
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Sent from my SM-N920T using Tapatalk

jaycuzhommie said:
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
Click to expand...
Click to collapse
to the be a novice as i, him agrees read well and and follow the instructions of post # 2 here
http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270
as already have the last firmware not have that install still the instructions since the step # 7 as in the image.
{
"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"
}
already the firmware the have for future if you wish render it to stock and clean

javierduran said:
to the be a novice as i, him agrees read well and and follow the instructions of post # 2 here
http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270
as already have the last firmware not have that install still the instructions since the step # 7 as in the image. View attachment 3848895
already the firmware the have for future if you wish render it to stock and clean
Click to expand...
Click to collapse
This is a much better guide for his model
http://forum.xda-developers.com/showthread.php?t=3361990
Sent from my SM-N920T using Tapatalk

You only have to do is flash TWPR in odin (don't forget to uncheck F. Reset time and auto-reboot) before you flash the recovery, download the flashable Super SU and place it on SD , memory, otg or wathever. Just flash recovery, when odin ends, then boot directly into recovery and flash the super su and you are done. if you no want to install custom recovery, you must look for other options

clsA said:
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Click to expand...
Click to collapse
I've read through a lot of the rooting threads here. From what I can see, the older stuff (2015) required flashing a new kernel as well. Is that just not the case anymore? Did I misread?

The Apostle said:
I've read through a lot of the rooting threads here. From what I can see, the older stuff (2015) required flashing a new kernel as well. Is that just not the case anymore? Did I misread?
Click to expand...
Click to collapse
That's correct the new SuperSU modifies the kernel for you
Sent from my SM-N930F using Tapatalk

clsA said:
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I have attempted this twice and both times no luck. First attempt I flashed via odin the twrp .tar file and it was blocked by FRP. Had no clue what that was because there is no mention of it in the guide posted. Second attempt I turned on Oem unlocking in settings menu thinking that would work and flashed that successfully but the phone wouldnt boot or go into recovery. I ended up flashing the stock DPG1 firmware to fix the no boot issue and now im back at square one.
Am I missing something? Been rooting and Roming my phones forever but need a little help with this 1 thanks.

wrecless said:
I have attempted this twice and both times no luck. First attempt I flashed via odin the twrp .tar file and it was blocked by FRP. Had no clue what that was because there is no mention of it in the guide posted. Second attempt I turned on Oem unlocking in settings menu thinking that would work and flashed that successfully but the phone wouldnt boot or go into recovery. I ended up flashing the stock DPG1 firmware to fix the no boot issue and now im back at square one.
Am I missing something? Been rooting and Roming my phones forever but need a little help with this 1 thanks.
Click to expand...
Click to collapse
It works. I did it again last night after taking the PG1 update. All you need to do is... 1) boot into DL mode. 2) flash the TWRP tar file in the AP slot via Odin. 3) flash SU in recovery. That's it... you're done.

The Apostle said:
It works. I did it again last night after taking the PG1 update. All you need to do is... 1) boot into DL mode. 2) flash the TWRP tar file in the AP slot via Odin. 3) flash SU in recovery. That's it... you're done.
Click to expand...
Click to collapse
Strange because thats exactly what I did. After flashing TWRP with oem unlock off in Odin all the phone would to is either show the T-mobile logo forever or boot to download mode. I saw something about removing google account. Did you also do that first?

wrecless said:
Strange because thats exactly what I did. After flashing TWRP with oem unlock off in Odin all the phone would to is either show the T-mobile logo forever or boot to download mode. I saw something about removing google account. Did you also do that first?
Click to expand...
Click to collapse
I've did not remove my Google account. I've read that too but believe the circumstances were different.
You said you have OEM unlock ticked off? Should tick it on (so it shows blue)
You may want to dload the official PG1 FW from Sammobile.com and flash from scratch.

No OS Found \ SW Check Fail [aboot]: fused 3/Binary 2 Error

If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.

Rawbert.Watkins said:
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Click to expand...
Click to collapse
CFW?
You need a revision 3 firmware.

Rawbert.Watkins said:
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Click to expand...
Click to collapse
Did you do your NANDROID backup to the phone? If so, wiping it would of course wipe out your backup. If you chose a complete wipe, it would even wipe the sd card.
Doh!
I'm not laughing, I did this not long ago myself, and I've rooted dozens of devices.
I'll search for a solution to this, no promises.

ashyx said:
CFW?
You need a revision 3 firmware.
Click to expand...
Click to collapse
CFW=Custom FirmWare
Sent from my Samsung Galaxy Trend Plus using XDA Labs

I'm getting the same error. I was fortunate enough to have another device available and pulled a backup from that device. But I need to use Odin to flash a different modem to get WiFi working again. It currently won't turn on and stays greyed out. It's been a couple weeks since this topic was posted. Any luck getting Odin to work?
Sent from my SM-G950U using Tapatalk

equitube said:
Did you do your NANDROID backup to the phone? If so, wiping it would of course wipe out your backup. If you chose a complete wipe, it would even wipe the sd card.
Doh!
I'm not laughing, I did this not long ago myself, and I've rooted dozens of devices.
I'll search for a solution to this, no promises.
Click to expand...
Click to collapse
Any word by chance?
Sent from my SM-G950U using Tapatalk

lancemulvihill85 said:
Any word by chance?
Click to expand...
Click to collapse
You need a matching NON-HLOS.bin flashed to the APNHLOS partition. You can flash this with TWRP.
However if you'd have paid attention to my previous post all you need to do is flash the correct firmware with odin.

ashyx said:
You need a matching NON-HLOS.bin flashed to the APNHLOS partition. You can flash this with TWRP.
However if you'd have paid attention to my previous post all you need to do is flash the correct firmware with odin.
Click to expand...
Click to collapse
I can't figure out how to flash to that partition with twrp. Just zipping the .bin to .tar and flash just doesn't fly. I apologize for my ignorance in the matter. However I was paying attention, and read the few previous posts. My situation is a little different. The last 3 letters of the current firmware end in QL3. And I can't seem to find that build ANYWHERE. When using the sammobile app to figure out what it's currently running, the CSC partition is empty. I have no CSC. When googling how to flash a CSC with twrp, I run into dead ends about using Odin (which will not work for my build). I'll post screenshots in a lil bit if anyone would help. I'm at a loss right now
Sent from my SM-G950U using Tapatalk
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
Basically, I have a working build, but WiFi is broken. It won't turn on. That's all I need. And I've been googling for about 2 weeks trying to figure this out
Sent from my SM-G950U using Tapatalk

lancemulvihill85 said:
I can't figure out how to flash to that partition with twrp. Just zipping the .bin to .tar and flash just doesn't fly. I apologize for my ignorance in the matter. However I was paying attention, and read the few previous posts. My situation is a little different. The last 3 letters of the current firmware end in QL3. And I can't seem to find that build ANYWHERE. When using the sammobile app to figure out what it's currently running, the CSC partition is empty. I have no CSC. When googling how to flash a CSC with twrp, I run into dead ends about using Odin (which will not work for my build). I'll post screenshots in a lil bit if anyone would help. I'm at a loss right now
Sent from my SM-G950U using Tapatalk
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
Basically, I have a working build, but WiFi is broken. It won't turn on. That's all I need. And I've been googling for about 2 weeks trying to figure this out
Click to expand...
Click to collapse
You don't need to flash the same build, you just need the right revision and version of Odin.
What is the error on the device when flashing the firmware?

Question Serious brick? Help please!

I'm on a T Mobile OP9 and had removed Root today via Magisk. Then deleted Magisk. All was fine. I restored the boot.img for the 11.2.2.2 and rebooted again, all good. I then went to 'fastboot flash oem lock' and it wanted my unlock token, I uploaded it to adb and retried, adb said finished and I looked at my phone and immediately saw in red "your device is corrupt it cant be trusted and will not boot". So yea. Im sitting here not sure what I can do. Its a TMobile OP9 and I just wanted to get it back to stock.

Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!

toyanucci said:
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
Click to expand...
Click to collapse
Well looks like I can go into the bootloader but if I choose recovery mode it just goes back to the "Device is corrupt screen".

toyanucci said:
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
Click to expand...
Click to collapse
Well I rebooted into bootloader but when I select Recovery mode, it just reboots back to the "Corrupt device" message. Not sure what ROM to use here as I don't have a backup of the tmobile rom :/ I think we ned the modem files from the tmobile version, which would be on my phone yet if I could acess them? The last time I did anything with a phone was the OP6 I'm out of my depth...

hiryupd said:
Well I rebooted into bootloader but when I select Recovery mode, it just reboots back to the "Corrupt device" message. Not sure what ROM to use here as I dont have a backup of the tmobile rom :/ The last time I did anything with a phone was the OP6 Im out of my depth...
Click to expand...
Click to collapse
The instructions in the link I sent will work but I'm not sure if there's a t-mobile rom that's available and I'm not 100% sure you can just flash the global rom

toyanucci said:
The instructions in the link I sent will work but I'm not sure if there's a t-mobile rom that's available and I'm not 100% sure you can just flash the global rom
Click to expand...
Click to collapse
I'm really not sure what to do atm, I don't want to make worse issues but It looks like its not a total brick at least? It should be fixable if the tools are around. I've read that we cant just flash global because the modem wont work with our phones? If i could access my files I could back those up I'm guessing? But messing around was what got me here. I just want to get stock back now. :/

hiryupd said:
I'm really not sure what to do atm, I don't want to make worse issues but It looks like its not a total brick at least? It should be fixable if the tools are around. I've read that we cant just flash global because the modem wont work with our phones? If i could access my files I could back those up I'm guessing? But messing around was what got me here. I just want to get stock back now. :/
Click to expand...
Click to collapse
People use the word brick a lot but I've never actually had a completely unfixable issue with an android phone. It can be fixed for sure with the right rom.
Oh, you can also try unlocking the bootloader. Since that was the only change you made it might boot. I'm remembering I had tried that too and it may be what got my phone to boot back up but I can't remember

toyanucci said:
People use the word brick a lot but I've never actually had a completely unfixable issue with an android phone. It can be fixed for sure with the right rom.
Oh, you can also try unlocking the bootloader. Since that was the only change you made it might boot. I'm remembering I had tried that too and it may be what got my phone to boot back up but I can't remember
Click to expand...
Click to collapse
Yea that occurred to me as well. I tried it and it worked! So at least I'm operable. But its just kicking the can down the road. Id really love to just be able to get back to stock and be done. But Im guessing that the boot.img from the oneplus site was the culprit. I don't have the original tmobile rom payload dumped. So I'm just going to site here with an unlocked phone I cant update... I dunno. Appreciate your help bud or i'd still be flipping out....

hiryupd said:
Yea that occurred to me as well. I tried it and it worked! So at least I'm operable. But its just kicking the can down the road. Id really love to just be able to get back to stock and be done. But Im guessing that the boot.img from the oneplus site was the culprit. I don't have the original tmobile rom payload dumped. So I'm just going to site here with an unlocked phone I cant update... I dunno. Appreciate your help bud or i'd still be flipping out....
Click to expand...
Click to collapse
I got it done with the 7T so it can be done and if you had restored the stock boot image with magisk before you uninstalled it then you are stock, just with an unlocked bootloader.
Re updates, again if you have the stock boot.img restored you'll get Ota updates just fine.

hiryupd said:
I'm on a T Mobile OP9 and had removed Root today via Magisk. Then deleted Magisk. All was fine. I restored the boot.img for the 11.2.2.2 and rebooted again, all good. I then went to 'fastboot flash oem lock' and it wanted my unlock token, I uploaded it to adb and retried, adb said finished and I looked at my phone and immediately saw in red "your device is corrupt it cant be trusted and will not boot". So yea. Im sitting here not sure what I can do. Its a TMobile OP9 and I just wanted to get it back to stock.
Click to expand...
Click to collapse
Do you have a backup T-Mobile stock oneplus 9 regular boot.img image? I can try a few things on my end if you want me to help you test. I forgot to take a backup of the boot.img. If you can share that I can try to help. I plan to return to stock too.

inspron said:
Do you have a backup T-Mobile stock oneplus 9 regular boot.img image? I can try a few things on my end if you want me to help you test. I forgot to take a backup of the boot.img. If you can share that I can try to help. I plan to return to stock too.
Click to expand...
Click to collapse
Thats the thing I used a tutorial from early on when the phone released, so I downloaded the 11.2.2.2.LE25AA and I used payload extractor to get the boot.img and rooted with magisk. So that was my backup. I assume this is why locking it now makes it corrupt? Im currently unlocked but also unrooted. There is no boot.img for the Tmobile variant floating about?

hiryupd said:
Thats the thing I used a tutorial from early on when the phone released, so I downloaded the 11.2.2.2.LE25AA and I used payload extractor to get the boot.img and rooted with magisk. So that was my backup. I assume this is why locking it now makes it corrupt? Im currently unlocked but also unrooted. There is no boot.img for the Tmobile variant floating about?
Click to expand...
Click to collapse
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image

toyanucci said:
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
Click to expand...
Click to collapse
Right and thats what i did. So what would cause my relocking it to be corrupt? I followed the procedure i wrote above. My rom is stock t-mobile except for the boot.img from the OP rom. So im sitting here on unrooted but also unlocked, unable to do anything in the way of relocking the loader. Im assuming at this point I just need to wait for an MSM tool for the non pro tmobile version.

hiryupd said:
Right and thats what i did. So what would cause my relocking it to be corrupt? I followed the procedure i wrote above. My rom is stock t-mobile except for the boot.img from the OP rom. So im sitting here on unrooted but also unlocked, unable to do anything in the way of relocking the loader. Im assuming at this point I just need to wait for an MSM tool for the non pro tmobile version.
Click to expand...
Click to collapse
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.

toyanucci said:
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
Click to expand...
Click to collapse
Well system update always comes back saying it has a problem and cant update. Also yea after I relocked It has a dialogue asking if im sure because it will do a full wipe, just like when I unlocked it. But instead of doing the full wipe it booted into that red text about being corrupt. So right back here again

toyanucci said:
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
Click to expand...
Click to collapse
I wish I had seen this part prior. I flashed img about 3 weeks ago prior to this method was known to me.

toyanucci said:
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
Click to expand...
Click to collapse
Thank you. Hopefully someone can share the stock boot.img for the T-Mobile variant.

inspron said:
Thank you. Hopefully someone can share the stock boot.img for the T-Mobile variant.
Click to expand...
Click to collapse
I exported them a while ago on a thread, we just moved our company so i dont have those systems and drives set up for me to get on server. We unbrick and all that fun stuff. If you have a telegram send me the info. & ill add you to try to resolve your issue.

Well i see now in the developer options that my OEM unlocking "Bootloader is already unlocked" and I cannot change this as it is greyed out? I dont if that means anythig for any of my issues...

oh
hiryupd said:
Well i see now in the developer options that my OEM unlocking "Bootloader is already unlocked" and I cannot change this as it is greyed out? I dont if that means anythig for any of my issues...
Click to expand...
Click to collapse
if that's the case you can flash with official build, and then you can add the t-mobile bloatware if you want.. Which i take it off most phones by request.
Official Build (Direct DWLOAD)
(Stock - Boot.img (Direct DownL)) Instead if easier...
If you really want the bloatware back that makes T-Mobile T-Mobile then.. here ya go..
pm install -k --user 0 com.mobitv.client.tmobiletvhd
pm install -k --user 0 us.com.dt.iq.appsource.tmobile
I want T-Mobile Boot Up Animation! I Want People to know im using T-Mobile!!
Here ya go, "https://www.hongkiat.com/blog/change-android-boot-animation/" - Add Sound even
{
"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"
}
I Hope this helps ya mate ..
You can also use these files I built to follow this post too if you need more help.
BACK TO STOCK 1+9