Related
Hi there,
I'm a newbie to android. Just got my i9000 (international version of Galaxy S) for two weeks which I like it very much and flashed it to the official Froyo 2.2 (Build ZSJPD, which to my understanding is based on the European JPO) straight away. But only recently that I find out that it can neither boot into the recovery nor the download mode via the 3 button method, which makes flashing via the Odin impossible for me. I tried to download the Rom Manager to install the Clockwork Recovery Mod but I faced the same problem as the top message of this thread, i.e. it cannot get into the unsigned CWM recovery as it is running the stock 3e recovery.
Nonetheless, thanks to the "Quick Boot App", I was able to go into the stock recovery mode by clicking the dedicated button. So my question is:
Is there any way I could flash the stock kernel back to 2e recovery, given the above condition, so that I could run the CWM recovery?
Is there any apps, which would actual install a different kernel so that I could bypass the stock kernel?
Hope big guys out there could give me some hint and show me the way! Otherwise, I would miss a lot fun and can't even apply the Universal lagfix.
Alex
I am curious too. I am running ZSJPE (Asian Build) but it doesn't seem to have 2e recovery as I am unable to boot into CWM, even with ROM Manager installed.
Any help would be greatly appreciated.
aywchiu said:
Hi there,
I'm a newbie to android. Just got my i9000 (international version of Galaxy S) for two weeks which I like it very much and flashed it to the official Froyo 2.2 (Build ZSJPD, which to my understanding is based on the European JPO) straight away. But only recently that I find out that it can neither boot into the recovery nor the download mode via the 3 button method, which makes flashing via the Odin impossible for me. I tried to download the Rom Manager to install the Clockwork Recovery Mod but I faced the same problem as the top message of this thread, i.e. it cannot get into the unsigned CWM recovery as it is running the stock 3e recovery.
Nonetheless, thanks to the "Quick Boot App", I was able to go into the stock recovery mode by clicking the dedicated button. So my question is:
Is there any way I could flash the stock kernel back to 2e recovery, given the above condition, so that I could run the CWM recovery?
Is there any apps, which would actual install a different kernel so that I could bypass the stock kernel?
Hope big guys out there could give me some hint and show me the way! Otherwise, I would miss a lot fun and can't even apply the Universal lagfix.
Alex
Click to expand...
Click to collapse
It amazes me the amount of people flashing roms without 3br. Why dont you install the 3br fix? then you can do whatever you like to your phone
http://forum.xda-developers.com/showthread.php?t=785201 odin
http://forum.xda-developers.com/showthread.php?t=821698 update.zip
Try either of these before you brick your phone! it doesnt matter how carefully you follow instructions it takes just one bad flash and your history...
tragusman said:
It amazes me the amount of people flashing roms without 3br. Why dont you install the 3br fix? then you can do whatever you like to your phone
http://forum.xda-developers.com/showthread.php?t=785201 odin
http://forum.xda-developers.com/showthread.php?t=821698 update.zip
Try either of these before you brick your phone! it doesnt matter how carefully you follow instructions it takes just one bad flash and your history...
Click to expand...
Click to collapse
I've been directed to one of these links to fix the 3BR bug on my I9000, but after reading some replies I'm a little hesitant as several people have reported their phone being bricked thanks to it...
If by any chance my phone does get bricked because of this, is there any other way to re-flash or something of the sort?
EDIT: Sorry to bump an old post...
Hello everyone
I just got a I9505, and I'm coming from the first Note. Before I had rooted my Note only once, I dont remember how I got Custom Recovery (CWM) into the phone, but I used it for every rom flash, I have never used Odin before.
So far What I have seen here is that the guide for flashing appears to not include Custom Recovery (CWM I guess, there appears to be one other variation now), but in every ROM thread all I see are download links to flash with odin, looks like nobody is using CWM to flash roms anymore.
The main advantage of CWM is that for me it appeared to be safer (My friend who likes to use Odin he has difficulties flashing most of the time), and it does not increase the counter.
Also, I'm not sure if to obtain ROOT I can just flash a pre-rooted rom from Odin while not being rooted. Does it work?
Thanks in advance
sniperbr0 said:
Hello everyone
I just got a I9505, and I'm coming from the first Note. Before I had rooted my Note only once, I dont remember how I got Custom Recovery (CWM) into the phone, but I used it for every rom flash, I have never used Odin before.
So far What I have seen here is that the guide for flashing appears to not include Custom Recovery (CWM I guess, there appears to be one other variation now), but in every ROM thread all I see are download links to flash with odin, looks like nobody is using CWM to flash roms anymore.
The main advantage of CWM is that for me it appeared to be safer (My friend who likes to use Odin he has difficulties flashing most of the time), and it does not increase the counter.
Also, I'm not sure if to obtain ROOT I can just flash a pre-rooted rom from Odin while not being rooted. Does it work?
Thanks in advance
Click to expand...
Click to collapse
We use CWM to Flash only Custom ROMs/Kernels.
We use ODIN to flash Stock ROMs/Kernels.
The easiest way to have Root and CWM is HERE
Or you can Flash a Pre-rooted Stock ROM
Good luck
I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!
Did you try and reflash recovery ? Does the phone boot up once you restore via Odin ?
Have you tried flashing twrp via Odin?
I have not tried flashing TWRP with Odin... is there a Odin version of TWRP?
It did not boot after flashing stock. I'd like to Odin TWRP if it's available.
I found an Odin TWRP.tar for SGS3, but nothing for S4, yet. Need a little more help.
Did you try rooting and flashing twrp via goomanager? I had something similar happen to me on my skyrocket and that's how I fixed it.
Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium
TheAxman said:
Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
This version of CWM claims to work with Aroma on the S4...
http://forum.xda-developers.com/showthread.php?t=2322682
scott14719 said:
This version of CWM claims to work with Aroma on the S4...
well lets take a look see...shall we. thanks
Click to expand...
Click to collapse
came across this thread: http://forum.xda-developers.com/showthread.php?t=2281287
it converts an img to an odin-flashable tar.
i went ahead and converted the latest twrp img for the at&t S4 and have attached it. i have not tested it as i am not near my device at the moment. if you decide to try it, unzip the tar.md5 and flash at your own risk as i have not tested this method by @cabloomi.
False aroma works fine with twrp on a gs4.
Sent from my SGH-I337 using Tapatalk 4 Beta
This happened to me. Use odin to put TWRP back on. You'll be fine.
Sent from my SGH-I337 using Tapatalk 2
Yeah I had this a couple different times trying to get rid of the custom/lock icon boot up. Flash fresh stock rom, root it and install recovery with "Root and Recovery for ATT-TMO GS4-CASUAL-R527b" --> http://forum.xda-developers.com/showthread.php?t=2297900 then flash the recovery you want etc, and restore Nandroid of backed up rom. Worked for me!
Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you
JJ5150 said:
I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!
Click to expand...
Click to collapse
I had a similar issue. When you hold the key combination to boot into recovery, do it for more than one cycle. Sometime for some reason it doesn't take the first time so keep holding the buttons. After getting into android recovery, clear cache and reset the phone.
JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you
Click to expand...
Click to collapse
When I had the problem is sounds like your having I Odined the Stock image back to the phone and then cleared the dalvik and cache with the stock recovery menu, then I was able to boot, I then rooted and used the debloater program found here on the forums and then just downloaded goomanager and installed TWRP, the one it pushes is LOKIed for you.
This is also the only .img file I can find for the our version of TWRP. IIRC you can use Odin to flash it
EDIT: Like trublu said, you may have to do it several times (clearing the caches in the stock recovery after ODIN)
JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing.
Click to expand...
Click to collapse
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
JJ5150 said:
I have yet to find a Odin version of TWRP that's loki'd for the S4.
Click to expand...
Click to collapse
i believe that all s4 recoveries are "loki'd", if you will.
xBeerdroiDx said:
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
i believe that all s4 recoveries are "loki'd", if you will.
Click to expand...
Click to collapse
The Tmo and Sprint variants do not require Loki'd recoveries, as their bootloaders are not locked.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
They do great work..used them 2 years ago. With a mytouch..ouch..
Sent from my SAMSUNG-SGH-I337 using xda premium
JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
It's called Jtag repair. And the guys you mentioned have saved many a ass with it. I've seen several good results. Unless something else is found, it is the only way I know of to fix a truly bricked phone. Some people (those who flash a lot and Dev a lot) have their own Jtag boxes.
BTW, which tool / method did you use to convert the .img to a TAR? I've seen a couple of methods and a tool or two but I was wondering if you used something I don't know about? TIA.
Hey guys, been looking through the forum all morning at different ROM's. I considered the KK upgrade, however can't find a working link to a DL, my telco still have not released the KK update.
I have N9005 model, on 4.3 rooted using Chainfire, have CWM. I DL a 4.3 ROM, but can't figure out how to get it on my phone from PC (I sent the zip file over, but it does not show up on CWM), I found a few KK ROMS that interest me, but can't find a working link to a DL of 4.4.2 it for me to flash. I would post in the respective thread, but I cn't post in the developer forums yet.
As I understand to do most roms on here now, I need to flash 4.4.2, Root it, install new version of CWM, then install the rom.
However if I have used CWM to do a nandroid backup, is it possible to flash it back to that, or is any chance of 4.3 gone once I flash 4.4
I know this is very noob, but we all gotta learn some day.
Any help, even a link to 4.4.2 DL would be awesome.
Spudz30 said:
Hey guys, been looking through the forum all morning at different ROM's. I considered the KK upgrade, however can't find a working link to a DL, my telco still have not released the KK update.
I have N9005 model, on 4.3 rooted using Chainfire, have CWM. I DL a 4.3 ROM, but can't figure out how to get it on my phone from PC (I sent the zip file over, but it does not show up on CWM), I found a few KK ROMS that interest me, but can't find a working link to a DL of 4.4.2 it for me to flash. I would post in the respective thread, but I cn't post in the developer forums yet.
As I understand to do most roms on here now, I need to flash 4.4.2, Root it, install new version of CWM, then install the rom.
However if I have used CWM to do a nandroid backup, is it possible to flash it back to that, or is any chance of 4.3 gone once I flash 4.4
I know this is very noob, but we all gotta learn some day.
Any help, even a link to 4.4.2 DL would be awesome.
Click to expand...
Click to collapse
First thing, if you go to KK you can't come back. Nobody has yet found a way to reset Knox or to revert the bootloader from KK. Go to it and you're stuck with it. May not matter depending on how you use your phone but there's a thread on here where the poster actually got his phone replaced because KK update meant he could no longer use it as he wanted and as he had it set up under 4.3.
(see http://forum.xda-developers.com/showthread.php?t=2709623 )
You've already tripped Knox using Chainfire's autoroot so you're free to do pretty much whatever you wish. I have stayed with 4.3, using Alliance ROM, Philz recovery and Lean kernel because the phone is awesome using them and KK seems to be generating lots of problems even now and doesn't appear to offer anything really worth having to make up for the troubles... IMO.
If you can't see the zip in CWM the most likely reason is you're looking at the wrong 'card' - in Philz recovery for example, the external SD card is SDCard1, not SDCard. At a guess you have copied the zip to the external card and CWM is looking on the internal memory.Not sure what the options are for plain CWM but look for another card option or move the zip from where you have it. Given the best flash is to wipe everything on the internal memory, the external card is the best location - it won't be wiped.
Another way to do it is to use Odin - extract the zip till you get the MD5 file and flash that via Odin to the phone - you need to put the phone in Download mode to do it. (hold Menu + Vol Down + Power to get to DL mode) There are threads on here with instructions on how to use Odin.
Journyman16 said:
First thing, if you go to KK you can't come back. Nobody has yet found a way to reset Knox or to revert the bootloader from KK. Go to it and you're stuck with it. May not matter depending on how you use your phone but there's a thread on here where the poster actually got his phone replaced because KK update meant he could no longer use it as he wanted and as he had it set up under 4.3.
(see http://forum.xda-developers.com/showthread.php?t=2709623 )
You've already tripped Knox using Chainfire's autoroot so you're free to do pretty much whatever you wish. I have stayed with 4.3, using Alliance ROM, Philz recovery and Lean kernel because the phone is awesome using them and KK seems to be generating lots of problems even now and doesn't appear to offer anything really worth having to make up for the troubles... IMO.
If you can't see the zip in CWM the most likely reason is you're looking at the wrong 'card' - in Philz recovery for example, the external SD card is SDCard1, not SDCard. At a guess you have copied the zip to the external card and CWM is looking on the internal memory.Not sure what the options are for plain CWM but look for another card option or move the zip from where you have it. Given the best flash is to wipe everything on the internal memory, the external card is the best location - it won't be wiped.
Another way to do it is to use Odin - extract the zip till you get the MD5 file and flash that via Odin to the phone - you need to put the phone in Download mode to do it. (hold Menu + Vol Down + Power to get to DL mode) There are threads on here with instructions on how to use Odin.
Click to expand...
Click to collapse
I will stick with JB for now as I like my setup anyway. I know how odin works and CWM was definitely looking at my External SD as my backup was on it. This is the ROM I was trying http://forum.xda-developers.com/showthread.php?t=2541304 I DL, extracted to a folder on my PC, put onto my micro SD, but alas, nothing to choose from to flash.
Found the Alliance one for N9005, looks real nice, so will give it a shot.
Deleted
Urghhhh why is it after hours of trawling and googling I can't find my answer. I did the alliance ROM (and now know how my first rom stuffed up) how do I get rid of the icon in the top left which shows download rate? Can't find the option anywhere on phone
Edited: Found it myself.
Final bit of noob from me for now. I tried to restore my CWM backup after installing Alliance, alliance overwrote CWM with TWRP, I did a factory reset, but could not restore from backup. It noted my CWM backup, but I could not restore it. Anything I did wrong here?
Edited: Once again from learning I fixed my own issue. Reflashed CWM, restored from todays backup, phone has gone from factory reset to how it was earlier today. Love the nandroid backup.
Oh boy, I really screwed this one up...
I purchased a used Note 3 from eBay, hoping to be able to root it after it arrived. Much to my surprise, it arrived rooted with Safestrap, Hyperdrive ROM in Stock slot, and a different Hyperdrive ROM in Slot1. I was also impressed that KNOX had not been tripped. (It said Custom, but the KNOX flag showed 0x00)
Sweet looking phone in hand, I was thrilled! I wasn't going to have to cut my teeth on rooting the device myself prior to having an opportunity to explore a rooted Android and a custom ROM. The very first thing I did was to use Safestrap to backup both the Stock slot and Slot1. After the backups, I booted the stock slot first, to see how a factory Note 3 should look. Surprise again, the stock slot booted a Hyperdrive ROM. I was a bit nervous that I didn't have a truly stock ROM, but wasn't too worried about it because I had no plans to resell or seek repairs under warranty.
I then spent a couple of days tinkering with the device. Unfortunately, half asleep during the wee hours of the morning, I was tinkering around with SuperSU -- setting grant/deny/prompt flags for different apps. Somewhere in the midst of that, SuperSU informed me that I had lost root. I checked with RootChecker, and sure enough NO Root.
Things got worse from there, as I'm sure you can imagine. RootChecker had a button to relaunch SuperSU, so I tapped it. This time, SuperSU wanted to re-install itself. Being the ignorant noob that I am, I told SuperSU to proceed, and crossed my fingers. After a few seconds of thrashing around, SuperSU wanted to reboot, so I said okay...
Now the device attempts to go into recovery, reboots itself, attempts recovery, reboots, again, and again... boot loop... and no way to charge the battery... I believe I am around 55% to 60% charged at the moment.
So I read great things about Odin and downloaded a copy -- not yet sure exactly what I was going to do with it. I have been trying to wrap my head around this for a couple of days now, but I have several questions that I hope somebody can shed some light on.
Does the rooting take place in the boot image, or in the ROM image? I am assuming it has to be in the boot image, but then I've heard you can have rooted and unrooted ROMs in different slots.
If I use Odin to flash fresh firmware, will this firmware will have a functional recovery tool bundled with it?
Since the phone is no longer rooted, the recovery will not be able to re-flash a ROM onto the device?
If an Odin installed recovery can't re-flash a ROM due to being unrooted, am I faced with JTAG options only?
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
If I can't use Odin to flash the firmware linked in the previous paragraph, and get Safestrap to restore my backups, can I use the firmware, ROMs, and PIT file linked here: http://forum.xda-developers.com/showthread.php?t=2576104 to restore the phone to factory conditions and re-root from there?
Finally, is there any way for me to avoid tripping KNOX at this point? I'm not really sure I care if it gets tripped, but if I can avoid it then I probably should. Am I likely to need KNOX container support on a private device in the near future? Is there any other reason to be spooked about losing KNOX? I really don't care much about the warranty.
Any help with this mess will be **greatly** appreciated!
lintex said:
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
Click to expand...
Click to collapse
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
lintex said:
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
Click to expand...
Click to collapse
Using any other slot other then stock is going to be problematic. So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap. Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot. Setup phone like normal. Make a backup with your now freshly setup rom. Rinse and repeat for new roms. Label your backups if you want to rom jump. Always use stock slot. Odin the nc2 kernel if you have a blackscreen on first boot of a new rom.
RomsWell said:
Using any other slot other then stock is going to be problematic.
Click to expand...
Click to collapse
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
RomsWell said:
So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap.
Click to expand...
Click to collapse
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
RomsWell said:
Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot.
Click to expand...
Click to collapse
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
lintex said:
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
Click to expand...
Click to collapse
As long as you stick to the known exploits like safestrap and towelroot then theres no worrys about knoxs. And no real way to perma brick the device. Make sure you stick to offical firmware when using odin and abuse your device like you would any other.