Roms yes, kernels yes via kexec, radios we don't know yet.
Sent from my SCH-I535 using XDA App
[BOOTLOADER] Locked bootloader research and news [Updated: 7/16/2012]
- Thread starter AdamLange
- Start date
Roms yes, kernels yes via kexec, radios we don't know yet.
Sent from my SCH-I535 using XDA App
Correct. And there are workarounds in place for flashing custom kernels which have been working fine. Unlocking bootloader would just make things easier. Not sure about radios.
Thanks for the quick replies. Radios are my biggest concern especially since I'm coming from a thunderbolt
don't let that keep you from activating. This is a great device!
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
believe me i want to activate it, but i also paid full price so getting the developer one is no big deal i just don't want to wait. Im just worried it'll end up like my thunderbolt and have ril issues which stop development down the road
Yup, but since i have no idea when the developer phone will come out id rather just use this one, but for development and long term sake i dont want anymore radio problems, thats the biggest thing i had about the thunderbolt. Im fine with using kexec for kernels and all that.
I think we can. I could be wrong but I thought some of the guys with the newer phones with the updated stickers were flashing our current release stock image and it was downgrading their baseband. Not 100% though, as it was posted in General section. Maybe someone with an "updated" phone can answer this for us?
ok so i just bought the s3 at VZW and it has the updated sticker. i wat to root it and install a recovery. where can i find how to root and if i can even root it < cause it has been updated for me me>. any help would be cool. i have looked AT The root post but it says dont use this if you have the update. thanks for the help
Been on cm9 for close to 24 hours. One camera force close that was fixed with a reboot. Totally happy with it.
Yes it does . it has the same as yours. Now if you can point me to the right way to root my s3......lol
Question my sIII info is different, than what's posted in screenshot above. Is this what most of us have or will it be of any use to helping with bootloader work?
I'm stock unrooted, no updates that I know of haven't touched root or anything yet.
Thanks to all the dev's.
bbolton_98
Sent from my SCH-I535 using Tapatalk
I'm stock unrooted, no updates that I know of haven't touched root or anything yet.
Thanks to all the dev's.
bbolton_98
Sent from my SCH-I535 using Tapatalk
Attachments
Just out of curiosity, why is your baseband verison I535VRLG1 while mine is I535VRLF2?
My Kernel Version is also different:
You have 3.0.8-743127
I have 3.0.8-618049
Holy god has this turned into a junk thread...
Sent from my DROID RAZR MAXX using xda premium
Sent from my DROID RAZR MAXX using xda premium
Not in the BOOTLOADER THREAD! This thread is useless now. Are there any mods around? Wtf?
I agree aren't there another threads about "random thoughts" or the specific topics being posted here? I check this for relevant updates and for the last couple of days all I read about is how Johnny can't find the camera or Daisy doesn't like the white s3 and would rather have a pink one.......
Sent from my SCH-I535 using xda premium
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
67
thats not 100% accurate
i flashed a modified boot.img to our recovery partition (/dev/block/mmcblk0p18)
then rebooted into recovery
it booted up into android using this modified boot.img
i don't plan for this to be of any real use to us though. proof of concept really
we need our access to /dev/block/mmcblk0p7 (where our stock boot.img actually resided)
thing is, we can flash to mmcblk0p7 just fine, but it wont boot (wont do anything actually other than let you get back into odin mode, where you can re-flash the stock boot image, or it gives you this when you try to boot android or recovery: http://i.imgur.com/Ci0gY.png )
rest assured. this is being worked on...39Since this is a news thread...
It was reported in IRC within the past hour or so that supposedly BOTH kexec is likely working and noobnl (whom many of you may know from his work with AOSP ROMs) has stated that the RIL has been cracked
To those who don't know what that means, kexec chainloads kernels (in simplest terms, the custom kernel loads on top of the stock kernel AFTER the bootloader checks to make sure the stock kernel has been unmodified). This was necessary if one wanted to run a non-Touchwiz ROM (such as CM, AOKP, etc) or if they just wanted to run an overclocked, undervolted kernel.
The RIL is essentially the radio. It was also needed to run a non-Touchwiz ROM and now opens the door to Jelly Bean ROMs.
There is still working/testing to be done, and there are no ETAs, so don't bug the devs. They're actively working on it so let them do their thing.
What a roller coaster of a weekend36Since locked Verizon SGS3 is now the main problem, i'v decided to split my kernel thread to separate one that focus directly on unlocking bootloader and progress in that matter.
Summary of the problem
Verizon model is protected from flashing unsigned/modified boot.img and recovery.img. Which means there is no known root method as for now for SCH-I535.
And that is where our adventure starts ....
Rooted stock boot.img issue:
CWM Recovery.img flash issue:
Research status: 50%
+ 20% - Some devs stated that RIL is hacked and there is also sucessfull Kexec implentation in works - http://xdaforums.com/showpost.php?p=28484191&postcount=262 Stay tuned for more news. Kexec proof-of-concept thread: http://xdaforums.com/showthread.php?t=1760678
+ 20% - phone can boot from unsigned boot.img flashed to recovery partition, this will leave you without recovery and requires to boot-trough-recovery every time u rebooting phone! (thanx invisiblek)
Links: http://xdaforums.com/showpost.php?p=28420589&postcount=47 , http://pastebin.com/eARk7r48
+ 10% - phone rooted trough system.img tricks -> http://xdaforums.com/showthread.php?t=1756885 (by invisiblek)
ROM analysys:
boot.img -> signed
recovery.img -> signed
system.img -> not signed
cache.img -> not signed
Update [7/7/2012]
News about locked Verizon model is spreading over the websites and main tech-related portals. Hopefully we will get some detailed info soon.
Update [7/7/2012]
It looks like it has been rooted by using system.img trick (system.img is not signed)
http://xdaforums.com/showthread.php?t=1756885
Enjoy! and thanx to invisiblek good job!
Update [07/15/2012] VZN insider confirmed this is not a true info
One of thread members chatted with verizon reps over mail & chat and got info that there may be possible unlocker released for bootloader at vzn locked phones. Here's the screenshots of chat: http://i.imgur.com/0lX3o.png , http://i.imgur.com/ULA4X.png
At this is not confirmed yet officialy, it may be interesting finding.
Update [07/15/2012]
Adam Outler posted he's own research info in separated thread, read it. It may help a bit -> http://xdaforums.com/showthread.php?t=1769411
Update [07/16/2012]
Galaxy S III Verizon Developer edition shows up on Samsung Website! -> http://www.samsung.com/us/mobile/cell-phones/SCH-I535MBCVZW
Thanks!29Developing right now:
JackpotClavin and Invisiblek have successfully loaded a custom kernel using a modified recovery ramdisk. It's still very early but this is excellent news for us. As it stands, this method wipes ClockworkMod and requires the recovery key combination on every boot, but those issues can probably both be overcome with custom scripts.
Stay tuned guys...and mash those two guys' Thanks buttons!24
And your post also.
On a good note while i was digging around last night through the source code I did notice something really nice about the SGSIII that should make you all very happy. As the guys at epic have noted, the kexec flag is marked, meaning that kexec can crash the existing kernel with one of its own. Now what does that mean you may ask. I'm glad you asked.
For those of you that do not know there are 5 primary partitions that are contained on most phones and android devices:
- X-Loader
This partition is usually the partition with the most basic hardware inits such as base gpio (buttons) and power toggles - bootloader
This is the partition that contains what most of us as dev's hate the most, the dreaded boot signature, and boot instructions. When a bootloader is locked down it can be because of either a hardware lock, see OMAP4 processors Sec_On Pin, or a software lock, HTC's S-Off. When a bootloader is said to be locked, it can have two reasons for this, a signed header or an encryption algorithm on the entire partition. - recovery
This partition is the one every one loves to see Clockwork Mod on. When not signed the partition can be flashed and used. ONE THING TO NOTE HERE IS THAT WHEN YOU USE THIS THREAD, YOU ARE SHOWING THAT THIS IS NOT SIGNED, Or the signature is not checked!!! This is intersting because it its self may show a security hole. The recovery might be what checks the CWM recovery flash images signature. - boot
Perhaps one of the most interesting partitions on android devices. The boot partitions contains the binary for the kernel, and the inframs for the initilization of the os. This partition in this case has said to be signed, with a signature check in the bootloader that checks the validity of a boot partition, meaning there is no changing this. - system
Contains most of the information on the OS. At this point all the framework and android settings get loaded. This partition is not signed, meaning we can modify to our will - userdata
Contains the userdata, such as games and such
Now one thing to note is that there are two initialzation points, the first of which occurs in the boot parition and the second of which is in the system's /etc/init files. One thing that i would be interested in seeing is if you were to use this place to load in a new partition or an SD OS. for example:
system1 partition init:
system2 partition can then have an init that mounts a block partition from the sdcard onto the system partition.Code:kexec -l /sdcard/kernel --reuse-cmdline --ramdisk=/sdcard/ramdisk
Code:mount /dev/block/mmc1... /system
Now what does it all mean? This current method means that we can reload a compleatly new os onto a devices kernel and all. AKA Jelly Bean.
For those dev which hope to find a way to make it work i point you to the following posts:
2nd-init can be used for a second init after the first one to allow for kexec to be run (might not need this)
kexec for ARM I might have to modify some kernel memory allocation issues but it should work none the less with the flag. - X-Loader
