Database Develop

[Q] Is there anybody who could Answer

I tried each and every thing to get full root but everytime I end up with that fu** partial root. Is there anybody who can guide me. I had tried following things till now :
1. Installed Factory kJ1 via pc odin.
2. Got full root access in KJ1 GB rom (tested by pasting a file in system folder)
3. Rebooted in recovery.
4. Installed Red pill Abyss kernel.
5. Did all the three wipes in red pill mode.
6. Installed Kingdroid Rom and s3 mod patch via red pill abyss.
7. Booted up in Rom and noticed a partial root.
8. Then flashed Chainfire 5.6 kernel via pc odin.
9. Used remove triangle apk ( succeded in removing triangle)
10. But still that partial root.
11. Then tried to flash cwm.zip via "update from sdcard" mode in CWM but failed to do so. It says no update file available.
12. Then installed the same file via "Select zip from sd card".
13. Did succeded in installing by this method then tried to install SU installer but CWM hangs at "unmounting system".
14. And guess what that fu**ing partial root.
I have tried many times the same methods but still no benefit.

I upgraded using Mobile Odin and I have full root.
When MO loads files, replace kernel with CF-Root 5.6 or any other safe kernel.
Hope it helps.
----
Edit
----
Read this post before you continue.
As CF said Beware: update.zip's can trigger the bug if they use "format" commands!
This kernel is safe to restore backups and to perform wipe data and factory reset but do not use it to flash custom roms.

Boy124 said:
I upgraded using Mobile Odin and I have full root.
When MO loads files, replace kernel with CF-Root 5.6 or any other safe kernel.
Hope it helps.
----
Edit
----
Read this post before you continue.
As CF said Beware: update.zip's can trigger the bug if they use "format" commands!
This kernel is safe to restore backups and to perform wipe data and factory reset but do not use it to flash custom roms.
Click to expand...
Click to collapse
didnt helped tried it earlier...cud u tell how u upgraded using odin

hardkaurr said:
didnt helped tried it earlier...cud u tell how u upgraded using odin
Click to expand...
Click to collapse
I flashed KKA ROM, rooted it.
Then flashed LPY with CF-Root 5.6 LPY kernel.
Tick preroot and inject SU.

Boy124 said:
I flashed KKA ROM, rooted it.
Then flashed LPY with CF-Root 5.6 LPY kernel.
Tick preroot and inject SU.
Click to expand...
Click to collapse
but I want kingdroid ehich can only be flashed via cwm not odin

hardkaurr said:
but I want kingdroid ehich can only be flashed via cwm not odin
Click to expand...
Click to collapse
Flash it with safe kernel.
And try this http://forum.xda-developers.com/showpost.php?p=27221642&postcount=2241

I flashed prerooted stock gb via PC Odin, then flashed cf root via PC Odin. The through cwm I flash abyss note 4.2, then I flash the rom I want and I have full root
Sent from my Galaxy Note running LiquidSmooth

carbonassassin said:
I flashed prerooted stock gb via PC Odin, then flashed cf root via PC Odin. The through cwm I flash abyss note 4.2, then I flash the rom I want and I have full root
Sent from my Galaxy Note running LiquidSmooth
Click to expand...
Click to collapse
even i did this but i never flashed cf root via pc odin earlier. let me give it a try will tell u. ...

Success
Finally succeded in rooting ICS thanks to robbie hood and his method given in Alliance rom forum.

I currently have android 4.4.4. should I Ota update then root and custom recovery

I currently have android 4.4.4. should I Ota update then root and custom recovery first?

mxl180 said:
I currently have android 4.4.4. should I Ota update then root and custom recovery first?
Click to expand...
Click to collapse
Yeah, cause if you root on 4.4.4...after you take the OTA...you lose root...so, might as well take the update first then root. If you are going to be using a custom ROM, you can just skip the root part and just go straight into getting a custom recovery...then just flash a custome ROM, which will of course already be rooted.

SiNJiN76 said:
Yeah, cause if you root on 4.4.4...after you take the OTA...you lose root...so, might as well take the update first then root. If you are going to be using a custom ROM, you can just skip the root part and just go straight into getting a custom recovery...then just flash a custome ROM, which will of course already be rooted.
Click to expand...
Click to collapse
I'm going to try PopRocks.. can you expand on the 2. Odin Flash Auto Root ? I want to make sure I don't mess up.
1. Odin Flash Cod6 Stock Rom Base
TMO Cod6 Base Mirror: thanks DuckSauce
https://www.androidfilehost.com/?fid=23991606952595535
2. Odin Flash Auto Root
3. Odin Flash Twrp 2.8.1.1 (link below)
https://mega.co.nz/#!7cQ0yb7a!hwHNPa...5qQwB0mmhJacBc

Yeah, that just means to use Odin to flash the Auto Root file (it roots the COD6 Stock ROM from step 1). It's the same process as flashing the COD6 file. Check out the first Stickied Post in the General section....by @TEKHD. A very easy to follow guide with links to all the files you need.

Help Needed. Softbrick after wipe

Hi All
I used safestrap to do a clean wipe of my phone. I selected data, cache, system in the advanced wipe options and wiped it thrice and then used the format data option as well. I wanted a clean phone for a custom rom install. After this I am only able to boot into stock recovery or download mode but not into safestrap and hence not able to flash any rom. It simply doesnt go into safestrap. I was on lollipop (Alliance rom). I am assuming wiping/formatting deleted some important files. I dont have any idea how to get it back to work using ODIN. Can someone please help me.
Thanks in advance

zain.quraishi said:
Hi All
I used safestrap to do a clean wipe of my phone. I selected data, cache, system in the advanced wipe options and wiped it thrice and then used the format data option as well. I wanted a clean phone for a custom rom install. After this I am only able to boot into stock recovery or download mode but not into safestrap and hence not able to flash any rom. It simply doesnt go into safestrap. I was on lollipop (Alliance rom). I am assuming wiping/formatting deleted some important files. I dont have any idea how to get it back to work using ODIN. Can someone please help me.
Thanks in advance
Click to expand...
Click to collapse
You can try to flash the NC2 Kernel https://www.androidfilehost.com/?fid=96042739161891885 using Odin in the AP Slot to see if you still have Safestrap, but I think when you did "format data option" you lost Safestrap. Seeing you wipe your phone clean, then you would have to Odin the NC2 files. BL https://www.androidfilehost.com/?fid=96042739161891602 AP https://www.androidfilehost.com/?fid=96042739161891890 CP https://www.androidfilehost.com/?fid=96042739161891603 and CSC https://www.androidfilehost.com/?fid=96042739161891604. Once you're up and running root it Towelroot https://www.androidfilehost.com/?fid=23991606952593961 Busybox https://play.google.com/store/apps/details?id=stericson.busybox&hl=en Supersu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en Safestrap https://www.androidfilehost.com/?fid=23991606952593962 Odin http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613

Rooted i747 said:
You can try to flash the NC2 Kernel https://www.androidfilehost.com/?fid=96042739161891885 using Odin in the AP Slot to see if you still have Safestrap, but I think when you did "format data option" you lost Safestrap. Seeing you wipe your phone clean, then you would have to Odin the NC2 files. BL https://www.androidfilehost.com/?fid=96042739161891602 AP https://www.androidfilehost.com/?fid=96042739161891890 CP https://www.androidfilehost.com/?fid=96042739161891603 and CSC https://www.androidfilehost.com/?fid=96042739161891604. Once you're up and running root it Towelroot https://www.androidfilehost.com/?fid=23991606952593961 Busybox https://play.google.com/store/apps/details?id=stericson.busybox&hl=en Supersu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en Safestrap https://www.androidfilehost.com/?fid=23991606952593962 Odin http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613
Click to expand...
Click to collapse
Thanks for the reply. Is there any particular order in which I need to flash these files using ODIN?

zain.quraishi said:
Thanks for the reply. Is there any particular order in which I need to flash these files using ODIN?
Click to expand...
Click to collapse
If you are useing the NC2 files then you need to use all four files at the same time, BL in the BL Slot AP in the AP Slot and CP in the CP Slot and CSC in the CSC Slot. If you are just trying to see if you have Safestrap then put the Kernel in the AP Slot only.

All four

Thanks
Rooted i747 said:
All four
Click to expand...
Click to collapse
This worked perfectly. Thanks for the help. Much appreciated

Factory Reset my S6 with Odin No Network!

I rooted with ping pong root, followed these guides to do my "OTA" updates:
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135
Then I used this file with Odin, to factory reset:
http://forum.xda-developers.com/att-galaxy-s6/general/odin-tar-files-sm-g920a-t3103835
Now it seems to have factory reset it but it says I have no IMEI, network unknown, etc....
I am suspecting that its something to do with those updates I did and flashing the Modem drivers, which maybe need to be downgraded now? or if i can update my software somehow with a legit version?
Any help is greatly appreciated.
Gavin

To my understanding, the downgrade to OE2 from OE3 or OF4 causes these issues with the imei and such.
Sent from my SAMSUNG-SM-G920A using Tapatalk

from what I have gathered... seems right.
so I am thinking now if I can upgrade to OE3, or OF4 in a legit way... then my modem will work again....
but If i use the upgrades mentioned on those 2 threads, those are pre rooted? so ill just be rooted again (but working modem)
correct?

My files are working fine. the problem is that you're trying to keep root and the modem you flashed is NOT compatible with the bootloader you current have.

Sunderwear, no problem with your files at all, I think the problem is with me.
I am trying to remove root.
How can I put a bootloader on my device that will be compatible with my modem?

I had the same issues. I ended up using Odin to go to OCE, then OE2 then I used PPR to root, and used FF to go to OF3 then OF4. Cause a BUNCH of problemt so I went to BBuy and had them force a flash of the full OF4.
You could always try doing the Odin OI2 files and see if that leaves you fully updated with everything working. You will lose root and will not be able to downgrade.

Well, depending on your desired outcome (rootless OF4, or 5.1.1), you'll have to do slightly different things, both will wipe your phone completely.
To move to rootless OF4, just download the Full OTA from the bottom of the first post at this link this is where things get different.
The next step is to reboot your device to recovery, not download mode (hold power home and vol up). You may see a updating android icon, but nothing should be happening yet.
You should now see the manual menu for the recovery, select the sideload update option
On your computer with ADB, sideload the OTA zip Do not unplug your phone
Your phone should reboot and you're now running OF4 while rootless
For 5.1.1
Flash the ODIN files with ODIN

Please note, you must be already rooted for this to work: I made the same mistake of upgrading to of4. Here's what I did, and my phone works just awesome and is still rooted with the Of4 base band.
1. Odin 3.10.6 OCE2
2. Reboot, at this point you'll have no carrier signal/data.
3. Ping pong root, install flash fire.
4. Install Rayman's ROM, Clean ROM, or Dennis ROM with flashfire (wipe first!).
5. Download the of4 root update here. forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135 ONTO YOUR PC. unrar. Flash via Odin the two files you unrar'd according to these instructions:
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Reboot, and you should be up and running with cell data and carrier signal.

dave812 said:
Please note, you must be already rooted for this to work: I made the same mistake of upgrading to of4. Here's what I did, and my phone works just awesome and is still rooted with the Of4 base band.
1. Odin 3.10.6 OCE2
2. Reboot, at this point you'll have no carrier signal/data.
3. Ping pong root, install flash fire.
4. Install Rayman's ROM, Clean ROM, or Dennis ROM with flashfire (wipe first!).
5. Download the of4 root update here. forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135 ONTO YOUR PC. unrar. Flash via Odin the two files you unrar'd according to these instructions:
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Reboot, and you should be up and running with cell data and carrier signal.
Click to expand...
Click to collapse
Worked like a charm thxs

[REQ-DEV HELP] Experienced user and flasher stuck on DOK2 mounting partitions problem

Hello XDA members and devs. I have stumbled upon an issue that seems to be close to un-fixable. I have the SM-N910T obviously. I am on DOK2, every rom Touch Wiz and Cyanogenmod flashed correctly a couple of months ago. Now the only things I can flash are DOK2 stock firmware via ODIN, and then I can successfully flash TWRP 2.8.7.0, the only ROM I can flash is Maximum Overdrive 4.0.1 +(all upper updates.) I got a hold of Max OD dev and he said it's because of the 3 mount lines he added to the top of his updater-script. So I added those lines to updater-scripts of other roms and none worked. Some other roms have many other mount points and important lines of code in the updater-script that should not be removed or edited. I want to go back to Cyanogenmod, and others either 12.1 nightlies, or the new CM Remix 13.0 which worked before all the others stopped working at the same time.
Yes I also tried this.
Quote:
Originally Posted by sudoBacon
I tried before. Doesnt work onlky DOK2 or maximum ods 4.0.1 + no other roms
After you flash D0K2 firmware - Use the stock Recovery and Factory Reset - That will get you out of the bootloop - Just remember that your internal storage will be wiped!
I also get the same issue after attempting to downgrade which always fails. Used to be able to downgrade and upgrade firmware's as well, now I cant. I got the dev of Max OD rom to pull a DOK2 pit file even flashing that does not fix my issue. I also posted on Reddit, so I will copy and paste this post.
Reddit Post.
I have a T-Mobile Note 4 was working fine for a long time flashed many ROM's multiple times over and over again never had a problem until I flashed DOK2 I assume. With ODIN. I did flash to stock from COD6 to DOK2 can't seem to downgrade back to COD6 with ODIN get error cant downgrade note 4 SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABOOT , that appears on Download mode. Then every time I install TWRP I try to install a ROM from OTG usb or ext sd and nothing flashes, rom files work used them before. I can only seem to install DOK2 and can't downgrade or flash other roms. I need help so I can flash other roms. Yes I tried flash stock DOK2 and boot stock recovery then clearing cache and factory reset, to downgrade to COD6 still failing and can't install other roms. every time i try to flash version lower then DOK2 using odin get this error ; SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABOOT
At one point I installed CWM trlltexx or something like that through TWRP, and did format and all of that. But after that went back to stock flashed TWRP 2.8.7.0 because couldn't flash roms with CWM because the roms thought I was on trltexx. Formatted all partitions with CWM. Anyways tried to get back to Cyanogenmod and or Tekxodus and other roms all fail. Minus Maximum Overdrives 4.0.1.
The first 3 lines that Overdrive mentioned that must make my roms flash able are.
HTML:
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/cache");
run_program("/sbin/busybox", "mount", "/data");
Anyways please contact me on Google+ Hangouts or respond here if you know how to fix my issue also have Skype but PM me for that info. Add Bacon Seeds first and last name to Google + Hangouts that G+ Hangouts email is [email protected] . I am experienced in compiling roms extracting, de compiling as well. Life on my Note 4 without some Cyanogenmod had been technologically heartbreaking. I like flashing multiple roms and swapping back and forth. Now I cant even test others stuck on Max OD which is a good and awesome rom but sometimes get tired of Touch Wiz.

I would install the ROM you can, then dirty flash an aosp ROM, then try to flash the ROM you want.

therealjwkware said:
I would install the ROM you can, then dirty flash an aosp ROM, then try to flash the ROM you want.
Click to expand...
Click to collapse
I'll give this a shot but I seriously doubt this will work if other methods didn't.

sudoBacon said:
I'll give this a shot but I seriously doubt this will work if other methods didn't.
Click to expand...
Click to collapse
Use Kies to recover your phone. It should be able to fit any issues with partitions etc.

Odd how using the PIT file does not fix this issue. It's literally setting up your phone's partition table all over again and it isn't working. Also, on DOK2's bootloader, it is impossible to rollback bootloader. I tried going from DOK2 -> ANIH (Kitkat original) and it didn't work. You can still run older ROMs, just not the older bootloader. That's why you're getting the 'Binary 2 > Fused 1' message.
-
By the way, you should be using ODIN3.10.7. It is the latest version. Load up the full stock DOK2 firmware (I suggest downloading using SamFirm -- make sure to check Binary Nature for a full firmware), follow this guide:
http://forum.xda-developers.com/showthread.php?t=2610757
They used a PIT and Stock to fully wipe, with the exception in this case being that this is 5.1.1 and not 4.4.4

ShrekOpher said:
Use Kies to recover your phone. It should be able to fit any issues with partitions etc.
Click to expand...
Click to collapse
I tried that and now after doing factory reset in the stock firmware I can not even flash Maximum OD only DOK2 via odin.

sudoBacon said:
I tried that and now after doing factory reset in the stock firmware I can not even flash Maximum OD only DOK2 via odin.
Click to expand...
Click to collapse
do you have a working DOK2 stock firmware running on your phone. Once you upgrade to DOK2 you can only flash ROMs based on 5.1.1 or ROMs that include a kernel. If you want to flash a ROM based on 5.0.1 you will need to flash either the Emotion Kernel or the Beast mode kernel as well before you reboot the device.
If you have Stock TW firmware running and you have TWRP installed your phone should be fixed. As long as you use compatible ROMs with it.

ShrekOpher said:
do you have a working DOK2 stock firmware running on your phone. Once you upgrade to DOK2 you can only flash ROMs based on 5.1.1 or ROMs that include a kernel. If you want to flash a ROM based on 5.0.1 you will need to flash either the Emotion Kernel or the Beast mode kernel as well before you reboot the device.
If you have Stock TW firmware running and you have TWRP installed your phone should be fixed. As long as you use compatible ROMs with it.
Click to expand...
Click to collapse
Still didn't work.
Edit : Now i cant seem to install any rom nor Max OD. only DOK2 via odin. TWRP log says
E:Mount: Unable to find partition for path /sdcard
E:UnMount: Unable to find partition for path /sdcard
E:Mount: Unable to find partition for path /sdcard

sudoBacon said:
Still didn't work.
Edit : Now i cant seem to install any rom nor Max OD. only DOK2 via odin. TWRP log says
E:Mount: Unable to find partition for path /sdcard
E:UnMount: Unable to find partition for path /sdcard
E:Mount: Unable to find partition for path /sdcard
Click to expand...
Click to collapse
Looks like you corrupted your partitions. You might need to flash the pit file to fix it. I think there is a thread related to that somewhere.

Request thread closed, resolved!
Steps taken not in any order.
Find a legit us TRLTE pit file. Message me for the TRLTE pit file or I'll make a separate thread for it.
Flash DOK2 stock firmware + proper pit file and have re-partition checked, along with flash BL and EFS clear.
Format ext SD card.
Downloaded the roms onto the formatted SD card.
Flash the latest TWRP recovery
Wipe all not including system x3 times.
Go to Wipe and then Format, check system format system type Yes
Go to install select your ROM.
Then select your GApps and custom kernel whatever else you want.
You might have to do the stock flashing and wiping and formatting several times before this works along with the re-partitioning.
Note a legit TRLTETMO pit file can be found : http://www.sammobile.com/forum/showthread.php?t=29568
The legit pit file name for TRLTETMO should be labeled: TRLTE_USA_TMO.pit

sudoBacon said:
Request thread closed, resolved!
Steps taken not in any order.
Find a legit us TRLTE pit file. Message me for the TRLTE pit file or I'll make a separate thread for it.
Flash DOK2 stock firmware + proper pit file and have re-partition checked, along with flash BL and EFS clear.
Format ext SD card.
Downloaded the roms onto the formatted SD card.
Flash the latest TWRP recovery
Wipe all not including system x3 times.
Go to Wipe and then Format, check system format system type Yes
Go to install select your ROM.
Then select your GApps and custom kernel whatever else you want.
You might have to do the stock flashing and wiping and formatting several times before this works along with the re-partitioning.
Note a legit TRLTETMO pit file can be found : http://www.sammobile.com/forum/showthread.php?t=29568
The legit pit file name for TRLTETMO should be labeled: TRLTE_USA_TMO.pit
Click to expand...
Click to collapse
Congrats!

Hey bacon. I'm glad you figured it out. But in was wondering if you think me doing the pit file would work for my situation. Currently my phone is on a loop every time I flash dok2. And twrp will not flash any huge files. I can get kernels too flash but not roms. Any insight would be greatly appreciated. I can't even get the firmware too boot up. Thanks in advance

Jamonguyen said:
Hey bacon. I'm glad you figured it out. But in was wondering if you think me doing the pit file would work for my situation. Currently my phone is on a loop every time I flash dok2. And twrp will not flash any huge files. I can get kernels too flash but not roms. Any insight would be greatly appreciated. I can't even get the firmware too boot up. Thanks in advance
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24369303960684492
Here's a pit for the N910T, grabbed from the latest DOK2.

eduardog131 said:
https://www.androidfilehost.com/?fid=24369303960684492
Here's a pit for the N910T, grabbed from the latest DOK2.
Click to expand...
Click to collapse
I'm trying to get stock to boot without success. I would really appreciate any help.

Longshark said:
I'm trying to get stock to boot without success. I would really appreciate any help.
Click to expand...
Click to collapse
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.

eduardog131 said:
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
Click to expand...
Click to collapse
So I'm flashing the full ODIN package. PDA for stock, PIT from the link you posted, Checked boxes are Auto Reboot. Re-Partition, F. Reset Time and NAND Erase All. This is with ODIN 3.07.
What do I do when it finishes?
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
eduardog131 said:
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
Click to expand...
Click to collapse
It's done but boot looping with RECOVERY BOOTING... screen. Do I flash TWRP now? I have 2.8.7. Is that sufficient?
Thanks

Longshark said:
So I'm flashing the full ODIN package. PDA for stock, PIT from the link you posted, Checked boxes are Auto Reboot. Re-Partition, F. Reset Time and NAND Erase All. This is with ODIN 3.07.
What do I do when it finishes?
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
It's done but boot looping with RECOVERY BOOTING... screen. Do I flash TWRP now? I have 2.8.7. Is that sufficient?
Thanks
Click to expand...
Click to collapse
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.

eduardog131 said:
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
Click to expand...
Click to collapse
Sorry I'm fairly new to this. So it did boot into custom recovery. I just want the phone back to stock without TWRP or any bells or whistles.
Its on the stock recovery interface. Should I wipe data/factory reset? Or reboot system now?

Longshark said:
Sorry I'm fairly new to this. So it did boot into custom recovery. I just want the phone back to stock without TWRP or any bells or whistles.
Its on the stock recovery interface. Should I wipe data/factory reset? Or reboot system now?
Click to expand...
Click to collapse
Once it's done with verification of CSC, just reboot system. It should take a few minutes to set itself up, then will throw you into the setup wizard. Once you're there you're good to go.

eduardog131 said:
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
Click to expand...
Click to collapse
Also does it matter the dm-verity verification failed is showing at the bottom?