KNox and recovery

androidfine16 · Apr 13, 2014

Hello guys please help me ive searched through alot of forums and redaings a total of 4 hours and nothing usefull has come up.

So i have a galaxy s3 tmobile and it has Android 4.3 with knox and all of that other security crap on it. I tried to root it using this method
http://xdaforums.com/showthread.php?t=2563955 however i cant seem to flash arecovery no matter what or which i try. The odin flash says it flashed sucefully but when i go to recovery its still stock 3e recovery. I tried multiple flashing methods and nothing.
I even tried to flash a knox free rom http://xdaforums.com/showthread.php?t=2521742 but i cant being that i have no recovery.
CAN ANYONE PLEASE HELP ME?

>>>>>>>>>>>THANKS IN ADVANCE>>>>>>>>>

DocHoliday77 · Apr 14, 2014

Delete or rename two files

/system/recovery-from-boot
/system/etc/install-recovrry.sh

(Or similar to those...may have the path/name a little wrong. Now flash recovery and it should stick.

---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------

Or odin flash root66 firmware, then flash recovery.

androidfine16 · Apr 15, 2014

DocHoliday77 said:
Delete or rename two files

/system/recovery-from-boot
/system/etc/install-recovrry.sh

(Or similar to those...may have the path/name a little wrong. Now flash recovery and it should stick.

---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------

Or odin flash root66 firmware, then flash recovery.

I dont have root to delet those two files. And could you expand on the root66 and oding thing?

DocHoliday77 · Apr 15, 2014

Root66 firmware is in my thread in development section, link in my sig. Youll find instructions for Odin there and all over the place with a quick search and from the sticky threads. Not being rude, just don't like redoing what's already out there. If you have any specific questions about the process, ill be happy to answer them.

---------- Post added at 12:40 PM ---------- Previous post was at 12:39 PM ----------

Click the root66 heading to go to the thread if you want more info about it.

androidfine16 · Apr 16, 2014

DocHoliday77 said:
Delete or rename two files

/system/recovery-from-boot
/system/etc/install-recovrry.sh

(Or similar to those...may have the path/name a little wrong. Now flash recovery and it should stick.

---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------

Or odin flash root66 firmware, then flash recovery.

So i i flash the 4.3 over my current stock firmware with root66 version of 4.3 ill, have root?

serio22 · Apr 16, 2014

androidfine16 said:
So i i flash the 4.3 over my current stock firmware with root66 version of 4.3 ill, have root?

Yes

Sent from my SGH-M919 using Tapatalk

androidfine16 · Apr 16, 2014

serio22 said:
Yes

Sent from my SGH-M919 using Tapatalk

Ok i did it and i have superuser . If i follow this http://xdaforums.com/showthread.php?t=1766552 method to flash a recovery without tripping the counter can i flash roms afterwards and kernels without damaging the modem or flash counter trips?

androidfine16 · Apr 16, 2014

serio22 said:
Yes

Sent from my SGH-M919 using Tapatalk

androidfine16 said:
Ok i did it and i have superuser . If i follow this http://xdaforums.com/showthread.php?t=1766552 method to flash a recovery without tripping the counter can i flash roms afterwards and kernels without damaging the modem or flash counter trips?

Ok so i have root and installed twrp recovery the latest one and it worked. I have root and a recovery

. So can i go ahaed and flash a rom and kernel now without any repercussions?

DocHoliday77 · Apr 16, 2014

Flashing any recovery or kernel trips the warranty bit. No way around that and no way to reset it I'm sorry to say. Since you've flashed recovery its likely tripped already so flashing kernels and roms won't make any difference anymore. The binary counter doesn't matter as its easily reset. But if you have a custom kernel or recovery it'll retrip to 1 every time you boot.

androidfine16 · Apr 16, 2014

DocHoliday77 said:
Flashing any recovery or kernel trips the warranty bit. No way around that and no way to reset it I'm sorry to say. Since you've flashed recovery its likely tripped already so flashing kernels and roms won't make any difference anymore. The binary counter doesn't matter as its easily reset. But if you have a custom kernel or recovery it'll retrip to 1 every time you boot.

I dont care for warranty or counter trip than. So i guess my final question is can i flash any roms including 4.2 and kitkat and above without bricking my phone?

Perseus · Apr 16, 2014

You can flash Any of these roms via Custom Recovery TWRP and you will do fine.

Do note, some people have mentioned that with a 4.2.x or 4.1.x Roms, sometimes their IMEI goes missing. So take a Nandroid and EFS Backup before hand.

androidfine16 · Apr 16, 2014

Perseus71 said:
You can flash Any of these roms via Custom Recovery TWRP and you will do fine.

Do note, some people have mentioned that with a 4.2.x or 4.1.x Roms, sometimes their IMEI goes missing. So take a Nandroid and EFS Backup before hand.

alright i made a nandroid backup of my whole stock rom. so now i downloaded the resurrection remix rom and im about to flash it.

THANKS FOR ALL YOUR HELP. COUDLNT HAVE DONE IT WITHOUT IT=.)

androidfine16 · Apr 16, 2014

androidfine16 said:
alright i made a nandroid backup of my whole stock rom. so now i downloaded the resurrection remix rom and im about to flash it.

THANKS FOR ALL YOUR HELP. COUDLNT HAVE DONE IT WITHOUT IT=.)

IT WORKED!!!!!!!!!!!!!!!! just dont know how to remove these soft keys i dont like them NVM GOT IT

DocHoliday77 · Apr 16, 2014

Perseus mentioned the nv (efs) backup before. Easiest way to protect yourself is open a terminal emulator and enter this.

su
reboot nvbackup

Device will reboot and create an internal, hidden backup of your nv data. I highly suggest doing this.

androidfine16 · Apr 16, 2014

DocHoliday77 said:
Perseus mentioned the nv (efs) backup before. Easiest way to protect yourself is open a terminal emulator and enter this.

su
reboot nvbackup

Device will reboot and create an internal, hidden backup of your nv data. I highly suggest doing this.

I backed it up in .IMG format.

DocHoliday77 · Apr 17, 2014

androidfine16 said:
I backed it up in .IMG format.

How did you do that??

---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------

If you mean you made a nandroid backup, that is completely different and does not include any of the NV data. The backup I mentioned is intended to protect you from ever losing your imei in the first place.

androidfine16 · Apr 17, 2014

androidfine16 said:
I backed it up in .IMG format.

http://xdaforums.com/galaxy-s3/general/galaxy-s-iii-partition-layout-basic-efs-t1689623

I used this method.

DocHoliday77 · Apr 17, 2014

Ok , first, never use anything you find in the international models forum for any US model. They are very, very different devices. If you made an image from mmcblk0p3 as stated in that thread, you actually made a copy of sbl2 I'm pretty sure.
Also, the imei, (the important thing here) is not actually stored on the efs partition as it is in some other devices.
Run the command I posted before for the best solution. If NV corruption is ever detected, it should auto restore from this backup during boot up.

And again, stay away from the international forums. Most of the info there will not apply to our devices here and many, many people have bricked due to that mistake.
And delete the backup you made. If you were to try and restore it to your device after updating it at some point, it would most likely cause a brick.

androidfine16 · Apr 17, 2014

OK thanks I'll get on that . I flashed a remix ROM and everything seems good right now. I'll try to back it up today.

Sent from my SAMSUNG NOTE III using xda app-developers app

fdecker · Apr 18, 2014

Kit Kat

androidfine16 said:
I dont care for warranty or counter trip than. So i guess my final question is can i flash any roms including 4.2 and kitkat and above without bricking my phone?

Read up on Kit Kat, you might not want to upgrade. You will lose write access to the SDCard. There are ways to then fix it, but you could lose function in some of your apps. Samsung finally adopted the Android specs for write access.

KNox and recovery

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Retired Senior Moderator / Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts