No. All of the devices are quite different. Different processors, different radios, different in other hardware too... the screen controller may be different specifically between the US and Int'l vers
[BOOTLOADER] Locked bootloader research and news [Updated: 7/16/2012]
- Thread starter AdamLange
- Start date
No. All of the devices are quite different. Different processors, different radios, different in other hardware too... the screen controller may be different specifically between the US and Int'l vers
So yeah, you know that there is now an app in the play store that unlocks the bootloader for you right? Its called "Vzw gs3 Ez-unlock (Bootloader) " by a dev called mmmeff
And you don't even have to brick your computer to do It!
Sent from my GT-P7510 using xda premium
A joker, eh? If it means anything I had it fixed within an hour... XD
Sent from my SCH-I535 using xda app-developers app
I'm using TWRP 2.2. The only issue I've seen is it won't read my internal sd, so I've gotta put the .zip I'm flashing on the external sd.
Oh, and I'm unlocked via the one click method. And here I was worried that once they figured out the unlock I'd need to short a connection with a paperclip...
That was something I was prepared to do. Did it with my Google tv "sorta ".
sent from an UNlocked I535!!!
sent from an UNlocked I535!!!
I understand that with the international version. Being the hardware differences.. but even with the other US variants? That seems false. We were able to port on the HTC droid incredible 2 from the desire Incredible S (which is the international version of 2) from Runnymede and several other phones that still had different radios and hardware changes. Now I understand work must be put into it to get them to work on our phones, I wasnt asking the ability to just flash any variant at random. I was asking since now we are not KEXEC screwed anymore, is it possible to port from similar devices and now a lot more easier too.
Sent from my SCH-I535 using Tapatalk 2
What you are saying does make sense. At least as far as cdma to cdma and gsm to gsm. But (and someone correct me if I am wrong) Sammy hardware is just a whole different beast than the Quietly Brilliant phone maker. I had an og HTC Droid Incredible up until I got this phone a few weeks ago. My Dinc with s-off had Evo Rom/kernels ported to it. Hell coming from the Dinc with CM9 running on it,I was actually unimpressed with The GS3 when I first got it.
I'm starting to come around to loving this phone but it still got a long way to go to be as awesometastic as the original Incredible.
sent from an UNlocked I535!!!
I'm starting to come around to loving this phone but it still got a long way to go to be as awesometastic as the original Incredible.
sent from an UNlocked I535!!!
My Incredible still has jermaine151's In-Sensitive Minimalist ROM with GO EX Launcher and it can give an iPhone 4s a run for its money (actually, it has on several occasions with my relatives' phones), but a stock Galaxy S III generally runs circles around the Incredible (and, by extension, the iPhone 4s) without breaking a sweat.
I still adore the Incredible, but it had a h/w issue where reboots occur during web browsing or video recording at odd times and this turned out to be a not uncommon issue with that line. It fit perfectly in the palm of my hand and was perfect for stashing anywhere, even though I generally kept it in a holster. Mine is an early AMOLED version, which is of course terrific - my spouse's Incredible 2 was great all-around, but my smaller display beat it for clarity and richness quite markedly.
Nevertheless, my hand has adapted to the much larger Galaxy S III footprint in the past month and the larger display real estate has been a (previously unperceived) much-needed relief for these older eyes. Its everyday speed still amazes me - there's no way an Incredible could download 15 updates from Google Play in the background and not experience significant lag in foreground apps, but this Galaxy S III just whistles along.
I would defend the Incredible's historical strengths to extremes, but feel it's more than a stretch to say it remains competitive with my new Samsung - especially since a bootloader unlock method has been released.
- ooofest
Someone tell me if I'm right or wrong. To relock using the EZ method I have to Odin to stock first? Or how would I go about this?
Sent from my Verizon Samsung Galaxy S3 4G LTE
Sent from my Verizon Samsung Galaxy S3 4G LTE
The recommendation is stock, but the developer of EZ lock said any stock rom should work (I asked him the same question). Obviously no guaranties!
Agreed on everything you just said...
I can not wait to see quadrant scores on an aosp or cm10 with a stream lined kernel!
Sent from my GT-P7510 using xda premium
Thank you for that download. I am always looking to better my speaking and writing skills.
Or
I always look to better my skills in speaking and writing. Thank you for that download.
I am laughing out loud!
Or
LOL!
Sent from my SCH-I535 using xda app-developers app
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
New posts
-
[OFFICIAL] LineageOS 20.0 [z2_plus]
- Latest: rishabhs103
-
-
