For those of you looking to root your N3, @Chainfire has updated his one-click app for N3 variants. No official support for the Verizon variant yet, but it's something to keep an eye on. No word on the bootloader as it's not anyone's hands yet.
http://forum.xda-developers.com/showthread.php?t=2466423
That's good to know. Thx.
Sent from my SCH-I545 using Tapatalk 4
unlocked BL NEEDED.
Indeed. This method will not work with a locked bootloader. We have to wait for an exploit in order to root.
suzook said:
unlocked BL NEEDED.
Click to expand...
Click to collapse
I was not aware that this method needed an unlocked bootloader. I should have read more.
Banggugyangu said:
Indeed. This method will not work with a locked bootloader. We have to wait for an exploit in order to root.
Click to expand...
Click to collapse
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
This is great to hear!!1
It sounds as if within days of release we are likely to haveca method for rooting. I would be grateful for unlocking but expect to use Safestrap
docnok63 said:
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Read what I said again.... And you're wrong. You can't write to the recovery image on a locked bootloader phone. That means no custom recovery. What you CAN do.... is bootstrap a recovery. Different process, different results.
If you had read my post more closely, I said that we are going to have to wait on an exploit for root capabilities. Once we have root, I'm sure a bootstrap will follow. Hopefully, exploitative rooting won't trip knox. If it doesn't, then a bootstrap recovery also shouldn't. At that point, a custom ROM (especially if hashcode creates a safestrap) should bypass the software side of knox preventing tripping from that as well.
Banggugyangu said:
Read what I said again.... And you're wrong. You can't write to the recovery image on a locked bootloader phone. That means no custom recovery. What you CAN do.... is bootstrap a recovery. Different process, different results.
If you had read my post more closely, I said that we are going to have to wait on an exploit for root capabilities. Once we have root, I'm sure a bootstrap will follow. Hopefully, exploitative rooting won't trip knox. If it doesn't, then a bootstrap recovery also shouldn't. At that point, a custom ROM (especially if hashcode creates a safestrap) should bypass the software side of knox preventing tripping from that as well.
Click to expand...
Click to collapse
Since you want to argue sematics and I'm just in that kind of mood, my post never stated that SafeStrap involved writing to the recovery partition; simply that it was possible to have a custom recovery run on a device with a locked bootloader.
Neither the ME7 root method nor SafeStrap triggers Knox on the S4 and I don't expect them to for the N3. Of course, all this will be unnecessary if we get the bootloader. We only have a few days to wait for the devices and then a few days more to know for sure.
docnok63 said:
Since you want to argue sematics and I'm just in that kind of mood, my post never stated that SafeStrap involved writing to the recovery partition; simply that it was possible to have a custom recovery run on a device with a locked bootloader.
Neither the ME7 root method nor SafeStrap triggers Knox on the S4 and I don't expect them to for the N3. Of course, all this will be unnecessary if we get the bootloader. We only have a few days to wait for the devices and then a few days more to know for sure.
Click to expand...
Click to collapse
You also never stated anything about a bootstrapped recovery. You posted about chainfire's root method, then argued (wrongly) against those that stated that method wasn't possible due to locked bootloader. Not one person in this thread said anything about not being able to root because of a locked bootloader, just that this particular method wasn't going to work. FFS admit that you were wrong and move on...
Banggugyangu said:
You also never stated anything about a bootstrapped recovery. You posted about chainfire's root method, then argued (wrongly) against those that stated that method wasn't possible due to locked bootloader. Not one person in this thread said anything about not being able to root because of a locked bootloader, just that this particular method wasn't going to work. FFS admit that you were wrong and move on...
Click to expand...
Click to collapse
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Silly rabbit. I did admit I was wrong and I my link was for the SafeStrap recovery for the S4. It's time YOU moved on. There's more important issues in life. I'm done with you.
Realistic chance?
I've got an unlocked Droid Bionic. I was chicken and waited till it was out of warranty though. I wanted root so I could do full backups, something I believe was not possibly without it. Like you, I'm waiting for my VzW N3 to come in. I"m not sure how to restore some of my apps, or actually some of the data saved with that. TBpro wont help unless there is root. I've purchase the Asurian extended protection, not to much fine print info on it.. people say manufacturer warranty is voided with root. what about standard extended warranties like Asurian?
Bottom line.. just a guess, and I'll not hold anyone to it. What the odds that the guru's here will unlock our Vzw N3 without tripping knox, or somehow else voiding warrranty.
I'm probably sticking with stock rom for now..but without root, not sure how to get all my app data back. Someone said EZ file could make an apk but didnt see how. Someone else suggested helium makes good app backups without root, but that doesnt work on Motorola..so it wont work for my Droid bionic
Please familiarize yourself with the Forum Rules at the top of every Forum. This is a discussion thread and not a Development thread. It has no place in the Development Forum. I have moved this to the General Section where it should have been all along.
I look forward to your future attention and cooperation.
EFM
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Docnoc we all appreciate this post and are confident the people working on this will find something for us. Fingers crossed and donations ready!
edfunkycold said:
Please familiarize yourself with the Forum Rules at the top of every Forum. This is a discussion thread and not a Development thread. It has no place in the Development Forum. I have moved this to the General Section where it should have been all along.
I look forward to your future attention and cooperation.
EFM
Click to expand...
Click to collapse
When I read your post I hear Nucky's voice from seeing your avatar and sig plus your words is how we would talk lol
Apparently Chainfire's method helped designgears root the AT&T version. This took about 3 days. Good news!
http://forum.xda-developers.com/showthread.php?t=2472760
Does this work for the Verizon Note 3 ? Thanks guys.
Ok so a couple of things to note here.
First off it is about a 2% chance that you can just flash a custom recovery. There was a phone recently where the recovery partition had no verification check. With that being said it would be a big over sight. The next thing is that with Hashcode already working on a qualcomm kexec and SS I would be very supprised to see it not work, or there not be a strap method. As for root, if I'm not mistaken, and i could be, but Chainfire relies on you having an unlocked bootloader, as his image just has an init script in the recovery to boot, change ro.secure to false and then flashback the old recovery. With this being said THIS WILL NOT WORK WITH LOCKED DEVICES. If the bootloader allows for a unsigned kernel recovery to boot you can do it, or if it allows for stacksmashing you can do it, but those are two very iffy things. As for a root on this device, its more then likely going to have to come from a security tag that has been created in the linux kernel, that allows unverified code to run.
Second off I think there's something important to point out here, and I'm going to post it back to the days where there was no android. As of right now we have achieved a semi unlocked state (see loki and SS) however this is much like Musclenerd and geohotz grabbing the source code and finding injection points, the big difference was when geohotz found the holygrail, an architecture level exploit. What this translates into our world is much harder since the iPhone has one chip and we have... well Qualcomm, TI, and Samsung to name some. With this being said, and I know its easier said then done, but I think we are going to need a Qualcomm level exploit to really unlock all of these phones. We have seen in the recent couple of days that there are interrupts early on in the boot chain, see rumrunner, are not impossible. The reality is that our holy grail lies in one of two places, a leek, which in reality is more likely to happen since the other option is not always possible, or a base level exploit. The thing to keep in mind is that it too geohotz 2 years to discover the A4 hole, and he was just one man. While a community is much bigger, I urge everyone looking for exploits on new phones to realize that YOU SHOULD NEVER BUY A PHONE THAT YOU DON'T LIKE STOCK.
Hope you all are enjoying your GN3. They really are a great device with or without an unlock!!!
On a side note:
docnok63 said:
Apparently Chainfire's method helped designgears root the AT&T version. This took about 3 days. Good news!
http://forum.xda-developers.com/showthread.php?t=2472760
Click to expand...
Click to collapse
The reason for this is it seems there is a leek there that is allowing him to run a script that flashes over files to the FS. Look at:
designgears said:
As usual, a big shout out to my anonymous source for the file hook-ups!
Click to expand...
Click to collapse
This means that he most likely has some sort of System dump that is signed and has RO.secure disabled. If you look there's actually a full 2.2 GB image that you have to download and flash, meaning that it most likely has something that allows for root, and not actually an exploit.
Related
I've just seen a video on Youtube where a user has rooted his SGS II using Gingerbreak available here at XDA.
Am wondering if anyone has been brave enough to try it with their retail unit??
Sent from my X10i using XDA Premium App
+1
... Seeing as this is the make or break in my decision to buy.
Didn't work for me, sadly :-(
Given the latest attempts to secure root by Samsung, it may prove to be a task. The Indulge required that su be recompiled, and Superuser.apk be modified.
The above changes did not work on the ED12 leak of Gingerbread for the Samsung Epic4G.
This is probably going to be quite annoying.
Also note that the adb exploit we have been using has been patched in GB, so rageagainstthecage is not going to work at all.
I thought the bootloader was unlocked in the SGS2?
Gingerbreak 1.2 did not work on my retail unit. It sat at the "this may take a few minutes" screen indefinitely.
QuboidRC said:
I thought the bootloader was unlocked in the SGS2?
Gingerbreak 1.2 did not work on my retail unit. It sat at the "this may take a few minutes" screen indefinitely.
Click to expand...
Click to collapse
Bootloader being unlocked/locked has nothing to do with running an exploit to obtain root within the actual system...
But yeah, Gingerbreak does not work either on my SGS2... Neither the apk or the manual version via adb...
My comment was in reply to Dameon87 saying "Given the latest attempts to secure root by Samsung, it may prove to be a task." - is this not referring to the bootloader being locked? I'm a bit hazy on the technical side of this so perhaps I'm way off.
QuboidRC said:
My comment was in reply to Dameon87 saying "Given the latest attempts to secure root by Samsung, it may prove to be a task." - is this not referring to the bootloader being locked? I'm a bit hazy on the technical side of this so perhaps I'm way off.
Click to expand...
Click to collapse
No, all reports say the bootloader is unlocked. Samsung also confirmed they would not lock bootloaders unless it was requested by google.
QuboidRC said:
My comment was in reply to Dameon87 saying "Given the latest attempts to secure root by Samsung, it may prove to be a task." - is this not referring to the bootloader being locked? I'm a bit hazy on the technical side of this so perhaps I'm way off.
Click to expand...
Click to collapse
Root is the equivalent of "Administrator" privileges in windows. Android uses Linux, in linux one of the first things you learn in the terminal is how to gain root priviliges. You either temporarily use root with "sudo [command]" or you permanently take root through "su --".
Once we gain root, we can do anything on the phone since the bootloader is unlocked.
I know what root is but I don't know what a boot loader is and the significance of it being locked. Is it like BIOS?
Look, I don't have an SGS2 yet, nor do I have a flashable firmware in hand.
If I (or another hacker) can get my grubby little hands on an original flashable zImage from a retail device (sooner or later), AND I can figure out how to dump and fix the contents (I did it for SGS and SGT, so I hope I will again have success), it is possible to patch the zImage to include su and Superuser.apk. This will then be flashable with ODIN.
This is exactly why and how CF-Root on both SGS and SGT works. If the bootloaders are indeed unlocked, this shouldn't be all that difficult to do. I will hopefully be able to do it, I don't doubt Supercurio will be able to, and probably at least 50 others here on XDA know at least the basics for how to do this.
I'm betting (I ordered 2 SGS2's, but I won't get them 'til end of May) on this to be true and work. You'll just have to be patient a little until some of us devs get our hands on the device and some flashable firmwares.
I would be _really_really_ surprised if this isn't rooted within the next 4 weeks, using this or another method.
EDIT: Note that rooting has little to do with the bootloaders. The bootloaders generally decide if you can flash a custom kernel (the above method - cannot be done on protected bootloaders). NAND-lock or S-ON means that the /system is protected and cannot be modified. Root means you gain superuser priviliges, which can be accomplished in various ways, either with or without a locked bootloaders. It's damned difficult to do with NAND-lock though
QuboidRC said:
I know what root is but I don't know what a boot loader is and the significance of it being locked. Is it like BIOS?
Click to expand...
Click to collapse
Boot loader is code that is executed before any operating system starts to run. It reads data stored in ROM and starts to load it into RAM so that your CPU can execute the code.
By having the boot loader unlocked, we can change what is executed at boot.
Thanks.
S-On is a *****, I had that on my HTC Desire. I installed Cyanogen Mod with it still on, it was only when I tried to do things like change the host file that I ran into problems. I eventually had boot my PC from a boot CD and run some special software, goodness knows why it needed a boot CD! I got there in the end.
?
http://www.youtube.com/watch?v=9lVft5HoKP8
sun-drop said:
?
http://www.youtube.com/watch?v=9lVft5HoKP8
Click to expand...
Click to collapse
Patched.
Paul O'Brien (Modaco) has already tweeted he has pre ordered a SGS2 from Amazon and expects delivery next week.
Given his track record, I say he'll have it rooted in 48hours lol! Just need to pull him off the LG O2X first!!
Regards.
Chainfire just rooted a SGSII. So yes, it's possible. No, boot loader isn't locked.
Your wallets going to be sad ;-)
bilboa1 said:
Chainfire just rooted a SGSII. So yes, it's possible. No, boot loader isn't locked.
Your wallets going to be sad ;-)
Click to expand...
Click to collapse
Link? Screenshot? Tweet?
Anything?
Regards.
It's not rooted yet (but with luck in 10 minutes or so it will be). We did flash an unsigned kernel, and THAT worked, which confirms UNLOCKED bootloaders.
woops i though i read root too :s
well uve 5min. get to work.
Hi all. Please excuse if this has been asked (and answered), but I just spent two days with this phone and have just about torn my hair out.
I have a Verizon S4 (SCH-I545). I got it second-hand, so I don't know if the previous owner took any OTA updates. I wanted to put CM12 on it. However, in that thread, it's made very clear that it won't work without being on the MDK bootloader.
Well, when I execute the command "getprop ro.bootloader" from within Safestrap, I get "I545VRUFNC5".
Obviously, this is not MDK. Is this a bootloader that came after MDK as part of an OTA update? Either way, am I no longer able to Odin flash the MDK bootloader?
Thanks in advance.
Yes..This Bootloader is newer, and locked and cannot be reverted using ODIN. You would need to find a manual copy/change method to revert the Bootloader.
Sent from my SCH-I545 using Tapatalk
Hi KaosMaster. Thanks for your quick reply. So, does a manual copy/change method exist? You can probably surmise that I tried Odin'ing several stock ROMs with MDK packaged in and each one failed for various reasons. Can I do this copy/change action or would Verizon themselves have to do it? If the latter, would they do it without charging me a small fortune?
While I'm on the subject, are there any other gotchas you know of regarding this I545VRUFNC5 bootloader? What other ROMs won't work with it?
Thanks again!
Odin Won't work.
JTAG won't work(tested, phone bricks)
nc5 has root and safestap + limited ROMs with a touchwiz base
Some ROMs:
Hyperdrive
Echoe
Super6 Port
KitPop
Eclipse
Hi XxD34THxX. When you say the phone bricks using JTAG, do you mean it brick bricks? As in, turning the phone into a doorstop?
Do you know if Verizon would revert it back if you made such a request? If so, would it cost anything?
Well... with JTAG, I am pretty sure it turns into a soft brick. I can't confirm.
BWAHAHAHAHAHAHAH
Verizon will just laugh in your face if you asked them that.
XxD34THxX said:
Well... with JTAG, I am pretty sure it turns into a soft brick. I can't confirm.
BWAHAHAHAHAHAHAH
Verizon will just laugh in your face if you asked them that.
Click to expand...
Click to collapse
Arggh! Locked bootloaders are a complete and utter PITA.
What I don't understand is why CM12 requires a specific bootloader to function. To me, that sounds like Windows needing a specific BIOS or bootstrap to work.
Does CM10 have this requirement as well?
BTW, thanks for the rom list. I'll definitely check 'em out.
Yes, it needs an unlocked bootloader(any CM). It DOES need a specific bootstrap to work...
fleggett1 said:
Arggh! Locked bootloaders are a complete and utter PITA.
What I don't understand is why CM12 requires a specific bootloader to function. To me, that sounds like Windows needing a specific BIOS or bootstrap to work.
Does CM10 have this requirement as well?
BTW, thanks for the rom list. I'll definitely check 'em out.
Click to expand...
Click to collapse
Unfortunately you are stuck as no one has successfully downgraded the bootloader. Many developers have tried without success.
CyanogenMod will only work on an MDK device because the kernel is replaced during the flash process. This can only be accomplished with a custom recovery or unlocked bootloader.
FWIW, the MDK bootloader is technically not unlocked. There is a process called "loki" that took advantage of an exploit that was present on MDK which allowed the installation of a custom recovery. It did not unlock or overwrite the MDK recovery.
All bootloader versions past MDK have had this exploit closed.
OK I have question for developing if possible or someone more qualified than myself it's about the bootloader on verizon s4 I know it's locked down but I wondering if there is a way to go back to a previous version and unlock the bootloader
OK so here is what I did I tried unlocking bootloader with ez unlock for the s3 by the way this was my s4 i545 I tried this on .OK so I installed gave superuser permissions it said wasn't sure if my bootloader was unlocked but had a button to unlock it so I pressed it and it did something not sure what then it said it was successful. OK I then backed out and all my apps still worked phone still working until I powered down to try and get into download mode then phone bricked and yes hard bricked I know I can probably use jtag service for phone but my question is. If somehow it did unlock my bootloader can we use this and flashfire to maybe flash an older firmware like say the one that has an unlock able bootloader maybe
brandon79 said:
OK so here is what I did I tried unlocking bootloader with ez unlock for the s3 by the way this was my s4 i545 I tried this on .OK so I installed gave superuser permissions it said wasn't sure if my bootloader was unlocked but had a button to unlock it so I pressed it and it did something not sure what then it said it was successful. OK I then backed out and all my apps still worked phone still working until I powered down to try and get into download mode then phone bricked and yes hard bricked I know I can probably use jtag service for phone but my question is. If somehow it did unlock my bootloader can we use this and flashfire to maybe flash an older firmware like say the one that has an unlock able bootloader maybe
Click to expand...
Click to collapse
so your phone is bricked. is there anyway to get back the phone to usual or just throw it into the ocean? i think i have the same problem as you and my phone is "bricked". does it fixable?
Booboobanget said:
so your phone is bricked. is there anyway to get back the phone to usual or just throw it into the ocean? i think i have the same problem as you and my phone is "bricked". does it fixable?
Click to expand...
Click to collapse
If you are unable to get into dl mode, JTAG is required. Stop messing with the bootloader when you have no clue how it works
Matthew M. said:
If you are unable to get into dl mode, JTAG is required. Stop messing with the bootloader when you have no clue how it works
Click to expand...
Click to collapse
no by all means let him mess with it all he wants one less noob in this sub
Legitsu said:
no by all means let him mess with it all he wants one less noob in this sub
Click to expand...
Click to collapse
That's the stupidest thing i've seen on this board yet. But i haven't been here long. Samsung is a team full of selfish bastards for boobytrapping these things and trying to pawn them off as Look-see this here is android it's customizeable all you want, then they screw you into taking their lollipop crapware, and then they screw you into not being able to flash your way out of it.l And here you are saying crap like this. This place i thought was here for people to learn, but i've seen quite a few pricks here already in my short time. A lot of really smart helpful people. Two types that should be kicked off this place- idiots like you and people who talk too much like me.
Legitsu said:
no by all means let him mess with it all he wants one less noob in this sub
Click to expand...
Click to collapse
I always love coming here and reading your opinions. It gives me the greatest joy in life.
OK I have question for developing if possible or someone more qualified than myself it's about the bootloader on verizon s4 I know it's locked down but I wondering if there is a way to go back to a previous version and unlock the bootloader
Short answer: no, probably not.
Longer answer: if you want an unlocked bootloader, get a Nexus. I know that sucks, but I'm tired of messing with all this locked down.... stuff. I'll get my Nexus 6 in the mail tomorrow.
Long answer: sometimes, but it's a long, dangerous trip. (Not noob friendly at all-trust me, I've been there over and over)
If you remain undaunted, figure out what exactly which bootloader you have, and do some googling.
Matthew M. said:
If you are unable to get into dl mode, JTAG is required. Stop messing with the bootloader when you have no clue how it works
Click to expand...
Click to collapse
fortunately for everyone reading this, youre wrong. this brick is fixable with the boot.img file for the bootloader you were on when ya bricked it mounted to a sd card of equal size to the internal (if the phone came with a 16 but there was a 32 option, you can also use a 32). The hardware will look for the bootloader on the internal, and if it fails, it moved to internal sd, and if THAT fails, it looks finally on usb. There are many threads about this, and i personally fixed an sch-i535 in the EXACT same way.
also, not nice to chastise people when youre as wrong as they are...... so be nice......
---------- Post added at 02:31 PM ---------- Previous post was at 02:19 PM ----------
Airsoftjunky said:
Short answer: no, probably not.
Longer answer: if you want an unlocked bootloader, get a Nexus. I know that sucks, but I'm tired of messing with all this locked down.... stuff. I'll get my Nexus 6 in the mail tomorrow.
Long answer: sometimes, but it's a long, dangerous trip. (Not noob friendly at all-trust me, I've been there over and over)
If you remain undaunted, figure out what exactly which bootloader you have, and do some googling.
Click to expand...
Click to collapse
now this guy is on the right path. If you have a locked bootloader, the only ways to unlock it is if the carrier decides that its ok for samsung to issue a tar.md5 that can do it, a dev figures out a way around the security or if you were to connect the motherboard to a JTAG to force a previous firmware onto it that already has an unlocked bootloader. So if yours is locked, youll need to wait for an unlock or be clever enough to dink around with the coding and get it done yourself. That last option is not likely, not that im doubting your knowledge, its just that its nearly impossible to do so.
youdoofus said:
fortunately for everyone reading this, youre wrong. this brick is fixable with the boot.img file for the bootloader you were on when ya bricked it mounted to a sd card of equal size to the internal (if the phone came with a 16 but there was a 32 option, you can also use a 32). The hardware will look for the bootloader on the internal, and if it fails, it moved to internal sd, and if THAT fails, it looks finally on usb. There are many threads about this, and i personally fixed an sch-i535 in the EXACT same way.
also, not nice to chastise people when youre as wrong as they are...... so be nice......
---------- Post added at 02:31 PM ---------- Previous post was at 02:19 PM ----------
now this guy is on the right path. If you have a locked bootloader, the only ways to unlock it is if the carrier decides that its ok for samsung to issue a tar.md5 that can do it, a dev figures out a way around the security or if you were to connect the motherboard to a JTAG to force a previous firmware onto it that already has an unlocked bootloader. So if yours is locked, youll need to wait for an unlock or be clever enough to dink around with the coding and get it done yourself. That last option is not likely, not that im doubting your knowledge, its just that its nearly impossible to do so.
Click to expand...
Click to collapse
might wanna fact check before you got calling others out the sd recovery boot.img has not worked on the i545 since *NC5 it was removed for whatever reason (likeky to hamper attempts at unlocking it)
this has been confirmed by multipl devs
vzw s4 bootloader unlocking is completely dead stop giving false hope
btw good thread necro bro
Legitsu said:
might wanna fact check before you got calling others out the sd recovery boot.img has not worked on the i545 since *NC5 it was removed for whatever reason (likeky to hamper attempts at unlocking it)
this has been confirmed by multipl devs
vzw s4 bootloader unlocking is completely dead stop giving false hope
btw good thread necro bro
Click to expand...
Click to collapse
this is fact "bro". Ive walked a few people thru this process and helped them revive their "hardbricked" phones. Is it guaranteed to work on every baseband? No, there arent any guarantees in any of this stuff. And there wasnt any mention as to what baseband he was on.....
I never said that its unlockable, i was suggesting how one could go about unbricking their phone as opposed to throwing in the ocean.
and for your trolling, get a day job... youre terrible at it "bro"....
youdoofus said:
this is fact "bro". Ive walked a few people thru this process and helped them revive their "hardbricked" phones. Is it guaranteed to work on every baseband? No, there arent any guarantees in any of this stuff. And there wasnt any mention as to what baseband he was on.....
I never said that its unlockable, i was suggesting how one could go about unbricking their phone as opposed to throwing in the ocean.
and for your trolling, get a day job... youre terrible at it "bro"....
Click to expand...
Click to collapse
verizon section version phone verizon problems ONLY
bro
check your ignorance at the door please I don't need to be nice to wrong.ppl especially when they walk around acting like they know stuff and don't have a clue
Legitsu said:
verizon section version phone verizon problems ONLY
bro
check your ignorance at the door please I don't need to be nice to wrong.ppl especially when they walk around acting like they know stuff and don't have a clue
Click to expand...
Click to collapse
youre kidding right? i said BASEBAND!!! as in VERIZON BASEBANDS for the VERIZON S4....
bro....
im not gonna go thru my PMs to find the messages that i have from people who have had success fixing their phones with boot.imgs... even if i did, youre likely the type to say im faking it anyways... so just keep up the troll attitude, dont offer any help to anyone with your wrong info and just offer dead ends and "youre screwed" answers when there is an alternative...
bro... gawd, do you think this is jersey shore? who says bro anymore to people they dont know? is your chest all stuck out too? pffft...
Hello everyone,
Right now I have another thread for the root over ADB with DirtySanta, I've that far. I have a potential method but I need more information on it from somebody else so I am waiting on a response from him, once i have that I'll work on it. If you guys have any other potential ideas that'd be great.
Thanks,
Abine45
This is my link to the root on ADB. I will be updating it tonight or tomorrow for the convenience of others. Thanks for waiting.
http://forum.xda-developers.com/verizon-lg-v10/general/temporary-root-adb-t3523538
NEW INFORMATION FOUND! I GOT SIGNIFICANT ROOT ACCESS WITH DIRTYSANTA!!!
SO i used the DirtySanta fearing for my life I wouldn't ruin my device, well the v10 failed it. rebooted and it didn't do anything but reboot back into the normal bootloader and stuff. But what i found is that he go the dirty cow to just work under root, so maybe from there we could do something, anybody have any ideas?
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Haxcid said:
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Click to expand...
Click to collapse
How did Tungkick manage to repackage it then? The dirty cow exploit can exchange recovery though on an unlocked bootloader so shouldn't I be able to replace the boot image if done correctly wouldn't it work? I could possibly unpack everything and modify it all and test it but the issue comes back to repacking and flashing?
Ask him, but if you attempt to do this on a locked and encrypted boot loader then you will brick the phone. I mean think about it, if it was really just that simple every phone would be rooted and rom'd. Most phones running 6 or above have had the security vastly increased to make the phone secure so they can be used by government employees. Hence the introduction to SELINUX polices into the kernel which is why getting root is so unbelievably difficult. The locked boot loader resets everything at boot so getting root and maintaining is so hard combined with SELINUX does not allow standard root to perm. write anything to the system partition and then good old hboot kills anything you did mange to write on reboot... you can start to see how difficult this really is.
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
LG are just not popular devices for hacking due to they make if extremely difficult. LG is a Corp. friendly company it is why Verizon loves them where companies like HTC are a bit more user sympathetic.
Funny you say that
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
Funny you say that! Tungick said to me, and i quote "[email protected]#$g you" and blocked me from Facebook. He also told me that he wouldn't tell me because it's a secret. He didn't speak very great English, that's why there is an ing at the end of the F-bomb. I asked Jcase through XDA and he said he wouldn't and so i put it better explanation of help through an email and he said I was harassing him... In which case before hand he said he doesn't develop for LG because he says basically we are A-holes sadly and that we don't live up to our donation pledges.
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
beavis5706 said:
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
Click to expand...
Click to collapse
True, that's why I'm going to try to do it. If you know anything and want to help could use it.
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
qujuanmiller said:
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
Click to expand...
Click to collapse
For sure, message me on xda.
beavis5706 said:
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
Click to expand...
Click to collapse
Anybody can help! Do some research and send it and whatever you would like to do. Try different things, Try to modify bits of code and see what you can do! Always gotta start somewhere!
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
beavis5706 said:
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
Click to expand...
Click to collapse
The thing with that is the fact that even if I know how systemless root works, I still have no way to install it, so first I need to find a way to get in the system.
Think I might have a way though
From what I understand systemless root will modify the boot image to attain root. Super SU will decide how to flash based on firmware version. Will automatically root normal with Lollipop and down, will automatically modify boot image on Marshmallow and up. How you will be able to modify the boot image on a VS990 without bricking it I don't know.
In order to do system less root we need a unlocked bootloader... It says that everywhere I'm reading
Hi abine45,
Please read this post completely, the guys here are close to obtain the perma root on android 6, using dirty cow.
https://github.com/timwr/CVE-2016-5195/issues/9
Sent from my E2006 using Tapatalk
I looked at this thread... a bit more technical than I am able to do... did it end up working? Looks like no, but I might have missed something.
Thanks!
Is there still no way to unlock the bootloader and get a custom recovery onto an AT&T SGH-i527 Mega 6.3 over six years later? These phones are still popular despite having frequent hardware failures.
I found a site claiming to have instructions for flashing LineageOS 17.1 to the AT&T i527, but I'm pretty sure it's just a bot-written ad site with articles that appear to make sense at first glance, while nevertheless being completely useless and existing solely to harvest traffic for ad views by appearing to have real-looking content.
Note that in the URL below, I replaced ".com/" with ".c/", just to avoid having Google see this post and raise that URL's ranking because it found a link to it from here.
https://tweakdroid.c/lineage/samsung-galaxy-mega-6-3-samsung-sgh-i527-meliuslteatt/
On one hand, it seems to superficially make sense... until you you get to steps 2 and 3...
Next, you need, unlock the bootloader. You can’t do this if you have a locked bootloader. If you haven’t heard about this, you can look at the guide of unlock bootloaders.
As you have done these, next install TWRP recovery in your phone. You can use our guide for the installation of the TWRP recovery process.
... then head over to XDA, and ultimately lose several hours of your life that you'll never be able to get back before discovering that as far as anyone here can tell, unlocking the i527's bootloader is literally impossible (at least, without paying more than the phone is actually worth to have someone do it with a JTAG... and based on a 28-page thread I spent 2 hours reading, it looks like that didn't even work when someone tried paying someone to do it).
For what it's worth, I actually have two of these phones:
One has 4.2.2 (I527UCUAMH1)
One has 4.4.2 (I527UCSBNJ4)
As far as I know, the second one is doomed to be a useless paperweight forever, because nobody has ever even manged to root 4.4.2, let alone unlock its bootloader.
I haven't completely given up hope that the first one might eventually be useful for something, but as far as I can tell after plowing through old and dead threads here, 4.2.2 is rootable, but not even it can be unlocked for reflashing... and TWRP has never been successfully made to work with it. I'd love to be wrong... but I'm not feeling very hopeful right now.