Is anyone aware of a ROM, or even a basic mod/patch that enables an insecure boot? I'd like 'adb remount' back
You have to install a rom that has it edited/enabled.
Right
Yes, I understand that -- Though strictly speaking no, you can just replace the right bits yourself to allow it. Regardless, that's why I asked - I am not seeing a ROM with it, but there aren't exactly a ton of ROMs for this one just yet...
That's a surprise since most of the roms in the dev section are created using dsixdas kitchen and part of the rooting process in the kitchen involves editing the boot.img for exactly what you are asking for.
Regardless, it's better to have the rom have the boot unsecure then to replace the bits. At least with the edited boot it will always be unsecure even after a reboot.
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
Hi,
Is it possible to root without an exploit? I am trying to use fastboot but fastboot devices shows empty. Even the command oem unlock shows "Waiting for device". Heimdahl is not supported for my device i.e. GT-S6312. All the custom ROM installation in the forum shows using a exploit to root the device. Any information on this is much appreciated.
Thanks.
Re
mindentropy said:
Hi,
Is it possible to root without an exploit? I am trying to use fastboot but fastboot devices shows empty. Even the command oem unlock shows "Waiting for device". Heimdahl is not supported for my device i.e. GT-S6312. All the custom ROM installation in the forum shows using a exploit to root the device. Any information on this is much appreciated.
Thanks.
Click to expand...
Click to collapse
Hello, my friend. Wolcome to the forums. You got the things wrong you are mixing up some informations. Basically you involved 2 concepts here rooting and unlocking the bootloader (oem unlock). I have an Lg phone and i am not familiar with Samsung devices.
Rooting means by finding a security hole (like an exploit or a way to mess with permission) to let you get root and system files access (super user). This is like being on an Administrator account on Windows.
Unlocking the bootloader (the command you said oem unlock from what i know is used on Lg devices but i might be wrong; this command works just for some devices, not all) means to modify the bootloader so it will alow modified operating systems or modified code to be runned. A locked bootloader (most of the devices have this, some can be unlocked some not) means that you cannot load anything that is not signed by your phone company.
To flash a custom rom you need to be rooted, have an unlocked bootloader (so you can flash a custom recovery like TWRP, CWM etc.) and then to flash a custom rom (like Cyanogen Mod, Miui etc) and in some cases a custom kernel (boot.img).
I searched around and found how to root your device and install CWM and found some custom roms. Please next time use the Search function.
Root+CWM: http://forum.xda-developers.com/showthread.php?t=2330644
1 Custom ROM i found (use Search button maybe you can find more): http://forum.xda-developers.com/showthread.php?p=51520354
ALWAYS flash only roms for your device and closely follow the instructions on those pages!
Hope i helped you. If so hit the THANKS button!
Have a nice day
christi9503 said:
I searched around and found how to root your device and install CWM and found some custom roms. Please next time use the Search function.
Root+CWM: http://forum.xda-developers.com/showthread.php?t=2330644
1 Custom ROM i found (use Search button maybe you can find more): http://forum.xda-developers.com/showthread.php?p=51520354
ALWAYS flash only roms for your device and closely follow the instructions on those pages!
Hope i helped you. If so hit the THANKS button!
Have a nice day
Click to expand...
Click to collapse
I do not want to use Framaroot.apk as I don't have the source for it and don't know if there are exploits for rooting the device. Is there any other method for this?
mindentropy said:
I do not want to use Framaroot.apk as I don't have the source for it and don't know if there are exploits for rooting the device. Is there any other method for this?
Click to expand...
Click to collapse
Rooting includes exploits that is how root is obtained man. With normal things you can't get root. You exploit a security hole to get the super user acces. This can be made by flashing a root file, by an insecure kernel and some kind of exploit in CPU i think (not sure but this is what Framaroot uses i think). Framaroot is not a defenitive root you can unroot it. Every method for root needs an exploit (depends what kind). Framaroot is safe go with that. A lot of people using that. Good luck.
I see a few threads on root and unlocking the boot loader. which one is the most accepted and still current?
I didnt find any that have been updated recently but my searching probably wasnt the best.
And i see that cm installer works on this phone. Will that install recovery and a new rom and root? if so is there any limitations to changing the rom off of a cm?
Anything?
I don't know of any recent updated methods likely because most devs have obviously moved on to the newer devices (I used what you found on XDA - it's solid). However, there's been a couple of updated universal rooting apps such as VRoot (I haven't used it but I sent it to my novice BIL and he rooted an LG without a problem.) I think those are pretty much your choices.
This device is very ez to root, I think I know that the bootloader is not locked. There's even instructions on how to carrier unlock it if you need that.
Once I got CM 6.0.4 on there I haven't messed with it again. The more I have read about recoveries the more I want to minimize my messings with it. So I have been lazy or too comfy with my current setup so I haven't tried cm installer. I have jumped about 10+ roms and versions this year, I just find it ez to use my current setup. I guess it allows me the freedom to test roms other than cm.
Both of the rooting methods that are stickied dont work anymore. the .tar file is gone from the one that increases the flash counter and the other is a gingerbread kernel.
do you have a link to a root method that is intact?
oscar the grouch said:
Both of the rooting methods that are stickied dont work anymore. the .tar file is gone from the one that increases the flash counter and the other is a gingerbread kernel.
do you have a link to a root method that is intact?
Click to expand...
Click to collapse
Read here and here and watch this video
https://www.youtube.com/watch?v=vjbiF0Ohpe4
http://forum.xda-developers.com/showthread.php?t=1581185&highlight=ics+root
Final step - If you need to reset the flash counter flash this zip (even though this doesn't really matter if the phone is not warrantied[/URL]
Hello,
Anybody know of any good resources that can help me compile the kernel from my phone with a Linux base ROM/IMG like LineageOS or KaliNethunter? I can do the leg work, If I can find some solid documentation. The phone is rooted, bootloader unlocked, and carrier unlocked. I imagine you can compile the image, by using the Kernel from the stock image, and somehow using ADB to decompile and recompile the images?
I am new to this terminology, but not to jail breaking and rooting. The main thing is compiling systems with kernels, I've done it in Linux before, but the concept is still foreign. I'll understand more about it by the time I read a reply.
Thank you for any help or suggestions on where to start.
Edit:
Also, so long as I'm flashing images with fastboot, do I still run the risk of bricking the phone? I know there is always a risk, but it's safer than microsd updates, yes? Just keep a stock IMG file, and flash it if the kernel doesn't compile correctly?
Found this after posting https://forum.xda-developers.com/t/reference-how-to-compile-an-android-kernel.3627297/ . Going to add resources here. Multiple people have requested this, would like to get it working for everyone.