WARNING: This method has been tested exclusively on the Verizon SCH-I545 on build number LRX22C.I545VRSGPL1. Any attempts to do this on another ROM/build/phone are not recommended unless you feel like taking a risk.
By now it's presumably old news that GPL1 has been rooted with KingRoot. However, I've seen people actually using KingRoot as their superuser app, which is really bad for those who want to accept OTAs and have a legitimate SU management app. So, I made this guide for those people. Enjoy!
1) ROOTING
1. Download KingRoot 4.5 from here.
2. Enable unknown sources and install.
3. Press the button and wait for the root. The phone may reboot, don't be worried. Once root has been obtained and KingRoot says "waiting for root request", turn off auto-update in KingRoot settings and proceed immediately to step 2.
2) Transfer to SuperSU
1. Download Super-Sume from the Play Store: Link
NOTE: If you don't feel like paying for the app you can download it from the dark places on the interwebs... BUT I don't endorse that so here is a free script that you can use :good:
For those who used Super-Sume
1. Install SuperSU from the Play Store: Link
Note: DO NOT OPEN SUPERSU!!!
2. Open Super-Sume and press the big blue button with the bugdroid on it! Wait until the process is complete. If SuperSU does not open automatically, ensure the process is complete and open the app yourself.
3. Update SU binary with normal, reboot, and PROFIT! Now rooted with SuperSU.
For those who used the script
Follow this guide: Link
I plan on adding more useful tips to this guide, such as debloat lists. In the meantime, leave a thanks and enjoy your properly rooted phone!!!
I just want to be sure: will this method allow me to flash TWRP via Odin, and a custom ROM?
Brasscat82 said:
I just want to be sure: will this method allow me to flash TWRP via Odin, and a custom ROM?
Click to expand...
Click to collapse
No. You can only use Flashfire to flash ROMs. SuperSU is required for Flashfire, hence the need for this guide.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Brasscat82 said:
I just want to be sure: will this method allow me to flash TWRP via Odin, and a custom ROM?
Click to expand...
Click to collapse
bilgerryan said:
No. You can only use Flashfire to flash ROMs. SuperSU is required for Flashfire, hence the need for this guide.
Click to expand...
Click to collapse
And even if you manage to flash a ROM with Flashfire, if your bootloader is locked, your phone will be unable to boot. Been there, done that with CyanogenMod 12
Jrhotrod said:
And even if you manage to flash a ROM with Flashfire, if your bootloader is locked, your phone will be unable to boot. Been there, done that with CyanogenMod 12
Click to expand...
Click to collapse
Custom TouchWiz ROMs boot just fine.
bilgerryan said:
Custom TouchWiz ROMs boot just fine.
Click to expand...
Click to collapse
Well, right. Hence why I said CM12. It's the change in kernel that triggers Verizon's locking.
I am sooOOoOoo happy this worked. Rooted with LRX22C.I545VRSGPL1. PL1 boot loader! Love it! :good:
Just purchased a new S4 Verizon to replace a getting flaky S3 and was really wondering if it could be done. I am currently using a S3 with a ton of custom software. Also a ton of root required apps. Needed root badly to use them.
Thanks to @Jrhotrod for all the work. Now off to finding a custom rom to get rid of the Verizon BS.
Have a great day folks!
JohnieJ said:
I am sooOOoOoo happy this worked. Rooted with LRX22C.I545VRSGPL1. PL1 boot loader! Love it! :good:
Just purchased a new S4 Verizon to replace a getting flaky S3 and was really wondering if it could be done. I am currently using a S3 with a ton of custom software. Also a ton of root required apps. Needed root badly to use them.
Thanks to @Jrhotrod for all the work. Now off to finding a custom rom to get rid of the Verizon BS.
Have a great day folks!
Click to expand...
Click to collapse
Thank you!
Regarding a custom ROM, you will unfortunately be unable to use it. Assuming you're using FlashFire (virtually the only flash tool on the latest software), the flash will succeed. But due to Verizon's restrictions, their watchdog in the bootloader will detect a change in kernel and you'll be unable to boot. Trust me, I've tried to flash CM12 and it gave me a screen telling me that it was insecure software or some crap like that.
You may have made the wrong decision upgrading to a Verizon S4. Depending on your budget (and how much you bought the Verizon one for) I would recommend getting the unlocked one (GT-19505) for slightly more money. It is easy to get TWRP and flash CM/Lineage.
@Jrhotrod
Jrhotrod said:
Thank you!
Regarding a custom ROM, you will unfortunately be unable to use it. Assuming you're using FlashFire (virtually the only flash tool on the latest software), the flash will succeed. But due to Verizon's restrictions, their watchdog in the bootloader will detect a change in kernel and you'll be unable to boot. Trust me, I've tried to flash CM12 and it gave me a screen telling me that it was insecure software or some crap like that.
You may have made the wrong decision upgrading to a Verizon S4. Depending on your budget (and how much you bought the Verizon one for) I would recommend getting the unlocked one (GT-19505) for slightly more money. It is easy to get TWRP and flash CM/Lineage.
Click to expand...
Click to collapse
Well FUDGE (Polite Talk!) I just looked and I can find white ones, but no black. However, beggars cannot be choosy! I know that my SIM from my S3 will swap to the S4 Verizon. Will my S3 SIM plop into this GT, or will I have to do something strange. If it will work, I'll go ahead and buy the White one. I'll be more comfortable with TWRP & Nano Backups! They WORK :good:
Thanks in advance for your assistance! :good:
JohnieJ said:
@Jrhotrod
Well FUDGE (Polite Talk!) I just looked and I can find white ones, but no black. However, beggars cannot be choosy! I know that my SIM from my S3 will swap to the S4 Verizon. Will my S3 SIM plop into this GT, or will I have to do something strange. If it will work, I'll go ahead and buy the White one. I'll be more comfortable with TWRP & Nano Backups! They WORK :good:
Thanks in advance for your assistance! :good:
Click to expand...
Click to collapse
As long as your sim card fits the Verizon S4, it will fit in the GT as well. The hardware in the Verizon variant is literally no different than the i9505.
If you want a slightly more powerful Exynos processor, go for the GT-19500. However, I don't believe that the developers at LineageOS support that variant, so choose carefully. Powerful processors are more battery-hungry.
And do keep in mind that when it concerns old phones, there are many cases where beggars can be choosers. Make sure to look on Swappa, eBay, and Craigslist before deciding that the white one is the only one available.
JohnieJ said:
@Jrhotrod
Well FUDGE (Polite Talk!) I just looked and I can find white ones, but no black. However, beggars cannot be choosy! I know that my SIM from my S3 will swap to the S4 Verizon. Will my S3 SIM plop into this GT, or will I have to do something strange. If it will work, I'll go ahead and buy the White one. I'll be more comfortable with TWRP & Nano Backups! They WORK :good:
Thanks in advance for your assistance! :good:
Click to expand...
Click to collapse
I recently swapped a sim card from the Verizon Galaxy S3 to the S4 it was painless. It took right away, there was no need to even contact them. Hope this helps.
My black S4 cost me $90-on eBay.
Sent from my SM-T800 using Tapatalk
Canarsie said:
I recently swapped a sim card from the Verizon Galaxy S3 to the S4 it was painless. It took right away, there was no need to even contact them. Hope this helps.
My black S4 cost me $90-on eBay.
Click to expand...
Click to collapse
$90 for the i9505? Or the Verizon variant? @JohnieJ is seeking the i9505 as a replacement for his Verizon one.
Canarsie said:
I recently swapped a sim card from the Verizon Galaxy S3 to the S4 it was painless. It took right away, there was no need to even contact them. Hope this helps.
My black S4 cost me $90-on eBay.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
@Canarsie
Thank you.
Did you get a used phone or a new one for that? There is a new white one (160.00) and a few recon there for 99.00. Also found a black one on Amazon for $299. I'll probably spring for the Amazon one.
BTW, are you folks sure that works on Verizon? It says not. Don't wanna make a mistake.
Jrhotrod said:
$90 for the i9505? Or the Verizon variant? @JohnieJ is seeking the i9505 as a replacement for his Verizon one.
Click to expand...
Click to collapse
My bad, it's the Verizon model.
Sent from my SM-T800 using Tapatalk
JohnieJ said:
@Canarsie
Thank you.
Did you get a used phone or a new one for that? There is a new white one (160.00) and a few recon there for 99.00. Also found a black one on Amazon for $299. I'll probably spring for the Amazon one.
BTW, are you folks sure that works on Verizon? It says not. Don't wanna make a mistake.
Click to expand...
Click to collapse
If you're willing to drop $300 I HIGHLY recommend the Moto G5 Plus. Look up the specs and reviews and I think you will be convinced. It works on Verizon (I have it on Verizon) and it is AMAZING!
It was reconditioned. I was amazed when my bill came that they knew the model number and color. This may sound crazy, but you can call and record the associates response if the sim card is compatible. I made sure to get the associates name when she told me there won't be a problem. She was spot on, if
there was a problem contact would have been made with management quickly. I'm an old man, there's a good chance I am Verizon's longest customer. They bend over backwards for me when they see how long I've been been with them.
Sent from my SM-T800 using Tapatalk
Canarsie said:
It was reconditioned. I was amazed when my bill came that they knew the model number and color. This may sound crazy, but you can call and record the associates response if the sim card is compatible. I made sure to get the associates name when she told me there won't be a problem. She was spot on, if
there was a problem contact would have been made with management quickly. I'm an old man, there's a good chance I am Verizon's longest customer. They bend over backwards for me when they see how long I've been been with them.
Click to expand...
Click to collapse
Verizon bending over backwards for a customer? Wow, thought that was a joke for a second. Especially a customer asking if an unlocked phone would work with their network. I could only see that happening if they were bending over backwards to get me to buy one of their carrier-branded devices.
You raise a good point but how many customer reps would know if a certain phone was unlocked? There's a good chance ten out of ten of my friends wouldn't know that. With Verizon I have had that nonsensical $35 activation fee waived for at least fifteen years among other perks when I caught them making false claims. Your knowledge of an unlocked phone is far greater than mine, but does making a five minute call that burdensome? If they get tripped up, your home free. If not, I'm the idiot who suggested it.
Sent from my SM-T800 using Tapatalk
Canarsie said:
You raise a good point but how many customer reps would know if a certain phone was unlocked? There's a good chance ten out of ten of my friends wouldn't know that. With Verizon I have had that nonsensical $35 activation fee waived for at least fifteen years among other perks when I caught them making false claims. Your knowledge of an unlocked phone is far greater than mine, but does making a five minute call that burdensome? If they get tripped up, your home free. If not, I'm the idiot who suggested it.
Click to expand...
Click to collapse
You don't even need to call them in the first place. If the phone is unlocked and compatible with Verizon, popping in the SIM will work fine. That's what I did with my Moto G.
At any rate, we're clogging the thread with irrelevant topics now. Let's take the conversation to PM.
I did it step by step. I lost root access but kingroot still there. Can't install any application. Phone lagging too much. Please help. How I get my root access back?
Related
Just days after my team Unlocked the IROM, Samsung is selling a "Developer Edition". This developer edition will be more secure than the exploit unlock my team provides.
http://www.samsung.com/us/mobile/cell-phones/SCH-I605MSAVZW
I find this really funny. I will also call those who pay for this device a sucker.
heck yea
Why would anyone in their right mind fork that kind of money over, when Adam Outler has opened this bad device up for you, you are right, they are a sucker if they fall for this.
Need to hire you Adam. Samsung will make major inprovements. I call for a petition.
Sent from my rooted Verizon Galaxy Note 2. FU Verizon and all tour BS you throw around.
I can think of several reasons to buy it. First, and most important, if Samsung gets high demand for this, it gives them data to send back to Verizon on subsequent models saying "look, there is a market for unlocked phones". This is especially true if Samsung sells significantly more of them on another carrier, and there is high demand for the unlocked version.
Another reason would be, if this is shipping unlocked in a manner that would allow you to flash the kernel and recovery, you are getting an unlocked phone that still has its warranty. Technically, you can restore your current phone to the factory state and get warranty coverage, but you broke the warranty. That would be less of an issue on the Developer edition.
Next, you'll never have to worry about an OTA update breaking the unlocked state of your device. It is possible that checks will be introduced to require a specific bootloader version to work with updated radios or kernels, or other proprietary libraries. We may be able to hack around it, but this isn't something you'd need to worry about here.
Finally, lets say you want to buy the device at full retail to keep your unlimited data. Why go and buy it at Verizon and let them make money off of a locked phone? This goes back to the first point too. Spend the same amount with Samsung, let them get the profits for producing an unlocked device.
imnuts said:
I can think of several reasons to buy it. First, and most important, if Samsung gets high demand for this, it gives them data to send back to Verizon on subsequent models saying "look, there is a market for unlocked phones". This is especially true if Samsung sells significantly more of them on another carrier, and there is high demand for the unlocked version.
Another reason would be, if this is shipping unlocked in a manner that would allow you to flash the kernel and recovery, you are getting an unlocked phone that still has its warranty. Technically, you can restore your current phone to the factory state and get warranty coverage, but you broke the warranty. That would be less of an issue on the Developer edition.
Next, you'll never have to worry about an OTA update breaking the unlocked state of your device. It is possible that checks will be introduced to require a specific bootloader version to work with updated radios or kernels, or other proprietary libraries. We may be able to hack around it, but this isn't something you'd need to worry about here.
Finally, lets say you want to buy the device at full retail to keep your unlimited data. Why go and buy it at Verizon and let them make money off of a locked phone? This goes back to the first point too. Spend the same amount with Samsung, let them get the profits for producing an unlocked device.
Click to expand...
Click to collapse
none of those are valid reasons. They are all possible on your device already. If they wanted to collect data they could.
AdamOutler said:
none of those are valid reasons. They are all possible on your device already. If they wanted to collect data they could.
Click to expand...
Click to collapse
They can collect unlocked data, but they can't say "these people wanted an unlocked device only". By purchasing the phone directly from them, they have hard numbers to provide. Also, how is the possibility of an OTA limiting future radios, etc. based on bootloader version not valid? Are they likely to do it? No, but it is still a possibility. And why would not buying it from Verizon be an invalid reason? You seem to hate them for locking it, so why would you buy it directly from them to help support them further in locking the device? I'd rather have whatever profits there are go only to Samsung.
imnuts said:
Next, you'll never have to worry about an OTA update breaking the unlocked state of your device.
Click to expand...
Click to collapse
I was under the impression(probably mistaken) that if we have a custom recovery installed that we wouldn't have to worry about an OTA installing itself? Am I incorrect in assuming this?
Thanks!
The way I see it, Samsung wants the phone unlocked from the start. They know that they can appeal to a greater Android crowd by letting it be easily unlocked, as it is on virtually all other flavors of the phone. When it comes to Verizon however, they have no say in the matter initially. It must be locked. This is the same for pretty much all other phone OEM's on Verizon as well. Hell, my old Droid X STILL doesn't have an unlocked bootloader.
By selling a "developer edition" that works on Verizon, it's kinda like they're sticking the finger back at Verizon while simultaneously making direct profit. Since they are the ones who made this beautiful device, I have no problem with this. They definitely deserve it. And they could opt to just not sell us these unlocked devices anyway, leaving us in the dust to deal with waiting on OTA's and never being able to truly update our device with custom firmware.
Either way if it weren't for you Adam and your team, this would be our only option. It's amazing to me that you guys were able to break Verizon's grasp on our devices and really stick it to them. As someone who has endured the annoying locked bootloader for a long time with my Droid X, it makes me grin ear to ear seeing their attempts to control our devices be foiled in just a couple of weeks after release.
Muchos gracias friend. And a big OORAH to you.
Old MuckenMire said:
I was under the impression(probably mistaken) that if we have a custom recovery installed that we wouldn't have to worry about an OTA installing itself? Am I incorrect in assuming this?
Thanks!
Click to expand...
Click to collapse
The OTA won't install itself, but, there could be checks in place that require everything to be a specific version before they would work. Obviously we're not on a stock bootloader, which has it's own version and checksum info. They could put something in that keeps let say, the cell radio from working if the bootloader isn't the proper version, thereby forcing you to unlock and update, or be stuck on old software. I doubt that this will happen, but it is a possiblity.
ihavenewnike said:
Need to hire you Adam. Samsung will make major inprovements. I call for a petition.
Sent from my rooted Verizon Galaxy Note 2. FU Verizon and all tour BS you throw around.
Click to expand...
Click to collapse
the problem is not samsung its verizon...samsung does not encrypt bootloaders. verizon requests the device to be locked and samsung must comply in order to manufacture devices for that network.
imnuts said:
The OTA won't install itself, but, there could be checks in place that require everything to be a specific version before they would work. Obviously we're not on a stock bootloader, which has it's own version and checksum info. They could put something in that keeps let say, the cell radio from working if the bootloader isn't the proper version, thereby forcing you to unlock and update, or be stuck on old software. I doubt that this will happen, but it is a possiblity.
Click to expand...
Click to collapse
I'm running deodexed stock, is there anything I or a developer can do that would block any OTA, and block the notification and nagging that would happen?
Thanks again man!
delete
droidstyle said:
delete
Click to expand...
Click to collapse
OK I found that under application manager>all>SDM
The option to disable is greyed out so I guess I will need to freeze via TiBu
Thank you for this info I sure hope it works I hate the idea that Verizon can still bork my device.
Oops I see you deleted your last post, does that mean I need to hold off doing the procedure you posted?
These unlocked, developer's edition would make sense if they were available the day the locked version came out. Even if Adam and his team hadn't unlocked the bootloader, any metrics collected from sales or interest in this late developer's edition is would already be skewed because the next big thing like the s4 is now even closer making this device close to being dated before it even ships.
phind123 said:
These unlocked, developer's edition would make sense if they were available the day the locked version came out. Even if Adam and his team hadn't unlocked the bootloader, any metrics collected from sales or interest in this late developer's edition is would already be skewed because the next big thing like the s4 is now even closer making this device close to being dated before it even ships.
Click to expand...
Click to collapse
nah... the download counters speak for themselves.
1500 so far.
Maybe a source code would be available on the dev edition that would help the devs with the locked editions
Sent from my SCH-I605 using xda app-developers app
crazydad said:
Maybe a source code would be available on the dev edition that would help the devs with the locked editions
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
The required source release will be the same for both.
Old MuckenMire said:
OK I found that under application manager>all>SDM
The option to disable is greyed out so I guess I will need to freeze via TiBu
Thank you for this info I sure hope it works I hate the idea that Verizon can still bork my device.
Oops I see you deleted your last post, does that mean I need to hold off doing the procedure you posted?
Click to expand...
Click to collapse
If you see sdm 1.0 in your apps then yes freeze it! I believe on beans rom its already removed. I could not remember if it had it stock, that's why I deleted my post...however I do know it was there on the GS3 stock.
One thing nobody has mentioned is the fact that there is a 32GB version not just 16
Sent from my SCH-I605 using xda app-developers app
Killer Turtle said:
One thing nobody has mentioned is the fact that there is a 32GB version not just 16
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
It doesn't say that anywhere in the specs...
I think it's high time that I present myself. I'm not as noob as I can be in the forums. Yes, I don't know Android, since electronics isn't my field of working anymore. I have studied electronics and went for a master in Engineering Physics so I'm not a newbie when it comes to hardware.
Just that I got this (stupid?) 30-year crisis and went for an MD instead.
My foremost field of working has been Unix, but I'm schooled in lower levels and had done both VHDL/Erlang projects and have been really fluent in asm. But that was a LONG time ago when Motorola 68xxx was the ruler (oh, the ****ing best cpu ever made code-wise).
The aversion and stop for asm-coding came with Inter and that was around the 486-time when you had to fiddle with the memory and stuff.
I have kept parts on my knowledge. Did a SOC for a big company with a linux that I pressed in on 128 kb of Rom but I'm not up to date with arm-asm and I can say that the last time I ever coded something was around 1996 since I started with design/capacity planning of hardware and management.
So the time has flown by. I'm a C-coder. Never coded a line of Java in my line. I'm also from Sweden and I don't know where you are from but if you are from USA we have quite some different rules here, especially when it comes to consumer law that can be used for us.
Ok. Enough **** about me.
I called Samsung today and this is a summary of the conversation I had.
I asked them about why the consumers had to use the Knox and how to pass it as a developer.
He could not answer it.
I asked if I trip the flag, why does it forbid me to sideload my own developed applications?
He could not answer it.
I asked how to remove it since as a consumer I had no use for it and this is something that I have not signed up for.
He said that I could send in my phone and have it reflashed to a lower version of the firmware.
I asked for specifications about it and said that knew it's a SE-linux containter (because it is).
That he could confirm.
I asked him what for specifications for the boot loader since it hinders me in my work.
He said that the only thing he could provide was a downgraded one (see above)
I said that I don't want a downgraded one since all use 4.3 and that is the future.
He could not provide that.
I said that maybe this is a deal that Samsung has done with NSA to provide them with information since I don't know what the phone sends out since I'm locked out of the kernel.
He said that he understood that he would feel the same sentiment.
I asked him if consider us who are developing on a low lever as valuable people the brings the phone forward.
He agreed.
I told him that I don't consider tripping the Know-flag to invalidate my warranty since it could be tripped in Kies (as reported here).
He agreed on that and told me that I could then contact the service for a reflash.
I told him that the option left then would be to crack the boot-loader as with the rooting.
He said yes.
Note that this is in Sweden. But the info in any case is interesting since he very well knew about this.
So the info I got. Yes. It's a Se-linux container and it is reflashable. Since it's reflashable we now know that it's not an e-Fuse and can leave that question. Since it's software it's crackable.
Seems high time for me to start to update myself on arm-asm. I got lazy with VHDL/Erlang
Also, this has not been the field of my quite messy life. Going from electronics to computers and Unix towards medicine.
I don't have a J-TAG. What do you guys use? What have you found so far?
Do we have access to the very beginning of the boot strapping?
With that I mean the first asm-lines that the phone do as a start. Is that hardware or is that software?
In this case. Could someone please provide me with that. As I said. I don't know Arm-asm yet, but I'll try to freshen myself. Asm is asm and the last thing I did with Arm was working with a Xlinix that had 2 cores in the die and then a VHDL-part. Really nifty. But that was 10 years ago.
My other problem is time, like you all, since I'm guessing you work full time.
But can someone update me or give me links to white-papers etc on how the phone starts? I guess there is quite little about it. It's not the glorious days where you could get papers on the clock-penalties and how revolutionary it was when you could do an instruction on both the edges of the clock-wave.
Sorry. I type a lot, but I really hate this and yes, people can say what they want. When Ericsson still made phones I had a special firmware that showed a LOT more then what a normal user would get and how chatty the phones are without us knowing. So the option of spreading the "Samsung has made a deal with NSA" WILL scare people whatever you think. I have done "activist" things before and you just have to present it as a theory and get to the point where the rumor will get viral.
I was truly amazed when my complaint against RIIA went viral and the "Govermental institution for internet privacy" got over 5000 complaints in one day. Don't know how that works in other countries but every document that you send here is official and need to be filed. We also have the reverse policy that seems to be a bit unique. Everything is open until it's classified as not public. Not otherwise as it seems in most countries.
Ok, off topic. You have to live with that if you want my help that I'm offering here.
Where are you know in the dissaembly of the boot-loader? SE-linux CAN be cracked but if t's scrabled with hardware it makes it a bit harder.
Ok, enough from me. Want me to start to dig with the Cortex-chip? I know that Qualcom are more then happy to provide white-papers on their chip. Just a matter of cost.
/Paul
Download the open source kernel and build it from source. Use ida for analysis and the qualcomm and Samsung boot procedure documents are around you have to search though.
Sent from my DROID RAZR using XDA Premium 4 mobile app
Surge1223 said:
Download the open source kernel and build it from source. Use ida for analysis and the qualcomm and Samsung boot procedure documents are around you have to search though.
Sent from my DROID RAZR using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, I've seen that some use a modded build-chain for it. Is that just modded for speed or what is modded and where can you get it?
/Paul
Btw, got a i9506 today. Will be interesting. Also got An Note 3 and that has 4.3. Both are "pre-knoxed". Need a good burn-in software before i start to root them. Know any?
I have not noticed this behavior before but although they are connected to a Wifi they still search every 15 s or so for others. I don't recall if my old one did that? My HTC doesn't.
But anyone now how the phone boots-strap? It's too late after having a kernel.
Since it makes it before it loads it, it's not a real SE-kernel because then the custom ones would work without even touching Know, would they. And they trip the flag.
So the check must be done earlier? Besides, are the kernel sources enforcing MAC? I have not set up a build env yet so that's all the questions.
And any good J-Tag that you recommend?
Double post. Don't know how to remove...
You might send it in, if yours is qfused like the ATT model they will have to resign the MDL bootloader with a certificate that has not been invalidated by the qfuse.
If they do that, you can extract it and we will atleast be able to flash back the i9505.
Sent from my i337 MF3 using tapatalk.
TheEgonSpengler said:
You might send it in, if yours is qfused like the ATT model they will have to resign the MDL bootloader with a certificate that has not been invalidated by the qfuse.
If they do that, you can extract it and we will atleast be able to flash back the i9505.
Sent from my i337 MF3 using tapatalk.
Click to expand...
Click to collapse
Do you still think it's actually an e-fuse? If they can "reflash" it as I got the info yesterday that means that the e-fuse is in the prom because how else could they just change it?
I'm still not sure about the fuse thing? Do we have that black on white that it's the case?
Because I think that they have just a small SE-Linux in the bootloader and then they can enforce all the rules they want. Your phone will behave
basically like a jailed Unix-account and the only success in cracking it is to prevent it to load. There is no other way.
I just sent a long and nice mail to Samsung. Will see if they contact me tomorrow.
I basically asked them why it's enforced on us private citizens and if we should start to openly question the motives on Samsung in different
mobile user forums. Because I will. Would be happy if someone would follow suit and help out.
Bad publicity is something that is hard to get rid off. Also, we never got an opt-in/out.
And if they start to get it it WILL scare them. I've done that before but not on this scale.
If need be I will drag them through our Consumer department. They are not so fun if they bite on the case and it just cost me time to write a letter of complaint to them.
"Freedom loving" Sweden will not accept spy-ware on their phones. That is one of the strong thing here. Consumer power and the equivalent for governmental issues.
Well, I'll report tomorrow. Btw, I got my new phone yesterday and it was a I9506.
They don't sell the I9505 anymore and the prel result with plain kernel is that it's about the same speed as Note 3.
absolon_se said:
Do you still think it's actually an e-fuse? If they can "reflash" it as I got the info yesterday that means that the e-fuse is in the prom because how else could they just change it?
I'm still not sure about the fuse thing? Do we have that black on white that it's the case?
Because I think that they have just a small SE-Linux in the bootloader and then they can enforce all the rules they want. Your phone will behave
basically like a jailed Unix-account and the only success in cracking it is to prevent it to load. There is no other way.
I just sent a long and nice mail to Samsung. Will see if they contact me tomorrow.
I basically asked them why it's enforced on us private citizens and if we should start to openly question the motives on Samsung in different
mobile user forums. Because I will. Would be happy if someone would follow suit and help out.
Bad publicity is something that is hard to get rid off. Also, we never got an opt-in/out.
And if they start to get it it WILL scare them. I've done that before but not on this scale.
If need be I will drag them through our Consumer department. They are not so fun if they bite on the case and it just cost me time to write a letter of complaint to them.
"Freedom loving" Sweden will not accept spy-ware on their phones. That is one of the strong thing here. Consumer power and the equivalent for governmental issues.
Well, I'll report tomorrow. Btw, I got my new phone yesterday and it was a I9506.
They don't sell the I9505 anymore and the prel result with plain kernel is that it's about the same speed as Note 3.
Click to expand...
Click to collapse
This link should shed some light on the qfuse situation.
http://forum.xda-developers.com/showthread.php?p=30781353
I believe this is specifically for the i9506 as the qualcomm chip in yours is a different prefix (though they are very similar in construction to my novice eye, the boot process is still a bit magical to me though so grain of salt all that.)
Sent from my i337 MF3 using tapatalk.
TheEgonSpengler said:
This link should shed some light on the qfuse situation.
http://forum.xda-developers.com/showthread.php?p=30781353
I believe this is specifically for the i9506 as the qualcomm chip in yours is a different prefix (though they are very similar in construction to my novice eye, the boot process is still a bit magical to me though so grain of salt all that.)
Sent from my i337 MF3 using tapatalk.
Click to expand...
Click to collapse
Actually they hotted up the phone quite much: http://www.gsmarena.com/compare.php3?idPhone1=5542&idPhone2=5371
Snapdragon 800, Adreno 330, Krait 400 @ 2,3 Mhz. Antutu places it next to Note 3 so it whops quite much.
Hi everyone!
I just want to share with you guys that I rooted my SGS i9505 with CF root and knox flag was tripped to 0x1.
I flashed the custom rom and i got bootloops and i tired of fixing that issiu. I went to Samsung service center in Dubai and they reflashed the MJ5 stock firmware.
Later when I checked in Download mode Knox flag it was 0x0. I guess I am lucky because I have my warranty back. Sorry for my bad English.
Bishkek said:
Hi everyone!
I just want to share with you guys that I rooted my SGS i9505 with CF root and knox flag was tripped to 0x1.
I flashed the custom rom and i got bootloops and i tired of fixing that issiu. I went to Samsung service center in Dubai and they reflashed the MJ5 stock firmware.
Later when I checked in Download mode Knox flag it was 0x0. I guess I am lucky because I have my warranty back. Sorry for my bad English.
Click to expand...
Click to collapse
That is interesting that they reflashed the stock firmware without negating your warrenty coverage for the tripped knox flag.
The question is were they supposed to do that or did they just screw up?
Thanks for sharing that!
Please follow the next thrilling episode in the Samsung-Zone... --> http://forum.xda-developers.com/showpost.php?p=48077682&postcount=1350
And about the reflash. They have offered that to me too if I "happen" to trip the Knox. So e-fuse, no e-fuse. Duck. I don't know what to think anymore.
As someone who's mother accepted the update to MI1 a few days ago, would contacting Samsung be a way to possibly downgrade the baseband?
Where in Samsung would I contact for this?
Sent from my SCH-I545 using XDA Premium 4 mobile app
kalestew said:
As someone who's mother accepted the update to MI1 a few days ago, would contacting Samsung be a way to possibly downgrade the baseband?
Where in Samsung would I contact for this?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Goodluck! US Samsung told me to kick rocks. (hence why I am posting from a HTC one now.)
Sent from my One using Tapatalk
Bishkek said:
Hi everyone!
I just want to share with you guys that I rooted my SGS i9505 with CF root and knox flag was tripped to 0x1.
I flashed the custom rom and i got bootloops and i tired of fixing that issiu. I went to Samsung service center in Dubai and they reflashed the MJ5 stock firmware.
Later when I checked in Download mode Knox flag it was 0x0. I guess I am lucky because I have my warranty back. Sorry for my bad English.
Click to expand...
Click to collapse
just a few quesitons to you sir.
did you wait for some minutes or did it take some hour?
was it repaired or motherboard simply replaced?
if they reflash the firmware it looks to me they have a "restoreable" that will be reversible if you flash it, just to ask why didn't you ask him what he did
I had 2 kindles lost in shipping. Called Amazon and they are sending 2 replacements. The originals arrived and I have the new ones. I called Amazon about returning the old ones and they said don't worry about it because they will be disabled anyway. My question is can the old ones be rooted so as to prevent the remote disable or is this connected to the serial number somehow to prevent anyway of saving these?
If you keep the two originals off and off of wifi until a bootloader exploit is found, then yes, you will be able to keep them for as long as you want.
Sent from my iPod touch using Tapatalk
Nice, thanks
gbrewha said:
I had 2 kindles lost in shipping. Called Amazon and they are sending 2 replacements. The originals arrived and I have the new ones. I called Amazon about returning the old ones and they said don't worry about it because they will be disabled anyway. My question is can the old ones be rooted so as to prevent the remote disable or is this connected to the serial number somehow to prevent anyway of saving these?
Click to expand...
Click to collapse
Do the world a favor and lure a great dev over to the kindle side with a donation . I would assume they would be fine as long as they never went online before a custom Rom is put on them.
conan1600 said:
Do the world a favor and lure a great dev over to the kindle side with a donation . I would assume they would be fine as long as they never went online before a custom Rom is put on them.
Click to expand...
Click to collapse
That is what I was thinking!
Who would be the best dev to donate this kindle to as far as cracking the bootloader and has the time to commit to it?
gbrewha said:
Who would be thst dev to donate this kindle to as far as cracking the bootloader and has the time to commit to it?
Click to expand...
Click to collapse
Well if your serious ask @Hashcode his opinion. He probably has some idea of the best kindle devs. Click the link and email him or one of the other devs currently working on this device. Or you could put up a post in general section asking this very question, I'm sure there will be some names dropped.
I'd be willing to donate to the cause to get some dev work on the HDX...specifically to help the guys working on getting the play store functional.
tegan_ca said:
I'd be willing to donate to the cause to get some dev work on the HDX...specifically to help the guys working on getting the play store functional.
Click to expand...
Click to collapse
Hashcode has a 7", which he picked up for his daughter.
If you want, I can talk to a few of the guys I know, to see if they have the time. Stericson (Kindle Free & Busybox Pro) would be great, however, I would say to wait. Don't give it to a good dev, what we really need right now is a low level guy that has connections & a good understanding of Qualcomm's msm9615. There are a lot of low level things hanging up any other work right now, even custom roms, or true recovery. A bootloader guy with msm knowledge would be even better, but there really are only a couple that have been reversing BL & msm hardware for any real lengthy period of time.
I'll talk to a few of the old timers & see if I can come up with a name.
GSLEON3 said:
Hashcode has a 7", which he picked up for his daughter.
If you want, I can talk to a few of the guys I know, to see if they have the time. Stericson (Kindle Free & Busybox Pro) would be great, however, I would say to wait. Don't give it to a good dev, what we really need right now is a low level guy that has connections & a good understanding of Qualcomm's msm9615. There are a lot of low level things hanging up any other work right now, even custom roms, or true recovery. A bootloader guy with msm knowledge would be even better, but there really are only a couple that have been reversing BL & msm hardware for any real lengthy period of time.
I'll talk to a few of the old timers & see if I can come up with a name.
Click to expand...
Click to collapse
Cool, thank you. I know the hardware side of it but come up against a pretty hard wall when it comes to FW. Just never got interested enough to dive in. But if anyone needs a rework or replace an IC I can help.
Edit: I have 2x7" that I picked up for my kids, have to follow what hashcode is doing with kids specific. Can't futz with the kids stuff!
I could use one
I'll take one if you wouldn't mind I'm pretty new to much of this but I can't get better without something to test on and I don't have the money right now to buy one on my own. Plus, I would like to help any devs I can by testing their software and other ideas.
Give one to meteorrock
Sent from my Galaxy Nexus using Tapatalk
Essentially, it seems the warranty cover hasn't changed. Unlocking the bootloader doesn't invalidate the warranty.
I didn't ask about QFuse. That seemed like a rabbit hole I didn't want to enter.
I didn't ask about modifications (though my Google rep did answer that anyway).
I haven't seen a 6P warranty document so can't comment on that either.
I removed details, including details of the rep as I don't want to get anyone in trouble. Just in case.
So I'm still hopeful.
(I hope the image below works. I shows the chat I had.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, so image didn't work. Here's the text:
Hi! Thanks for getting in touch with Google. My name is [Google rep - name redacted]. Please allow me a few minutes to review your case/ issue.
________________________________________
me
(Time stamp removed)
Hi. I currently don't have a case. This is a new question.
________________________________________
Google rep - name redacted
(Time stamp removed)
[my name], thank you for allowing me a moment to review your case. I would be happy to help you with this.
Was the device purchased from the Google Store.
________________________________________
me
(Time stamp removed)
It is a pre-order. The Nexus 6P has not shipped yet.
________________________________________
Google rep - name redacted
(Time stamp removed)
I see.
How can I help?
________________________________________
me
(Time stamp removed)
I would like to know what the warranty information is on the 6P regarding unlocking the bootloader. Does unlocking the bootloader invalidate the warranty of the device? I have had the last 3 Nexus devices and this was not the case so I am wondering if anything has changed for this device.
________________________________________
Google rep - name redacted
(Time stamp removed)
I can answer that now.
________________________________________
Google rep - name redacted
(Time stamp removed)
If you purchase a device from the Google Store, you are welcome to root or modify the software as you wish. In the event that you contact us for technical support, we will just direct you to reset the device to factory images.
Basically, you are reinstalling the original operating system back onto the device to attempt troubleshooting for the issue you would have reached out about. At this point, we can look at warranty options if the issue persists despite completing troubleshooting on the original operating system.
________________________________________
me
(Time stamp removed)
So to clarify, if I have unlocked the bootloader on the 6P and I develop a hardware fault, will I still be covered by the warranty?
________________________________________
Google rep - name redacted
(Time stamp removed)
Well, the limited warranty does not cover user induced damage like broken devices or water damage.
________________________________________
me
(Time stamp removed)
Naturally, that's fine. I mean a fault that is not the result of the owner's negligence.
________________________________________
Google rep - name redacted
(Time stamp removed)
Correct.
If there is an issue that would normally be covered under warranty, your warranty would be voided by having the operating system rooted or modified.
________________________________________
me
(Time stamp removed)
Ok. Here I just want to check with the bootloader. I have no plans to modify the OS.
________________________________________
Google rep - name redacted
(Time stamp removed)
In case you do, it doesn't void your warranty.
________________________________________
me
(Time stamp removed)
Ok thank you for that.
________________________________________
Google rep - name redacted
(Time stamp removed)
Right on [my name].
Is there anything else I can help you with today?
________________________________________
me
(Time stamp removed)
Nope. You've been very helpful.
________________________________________
Google rep - name redacted
(Time stamp removed)
Thanks for contacting Google! There’s a short survey coming up, so if you have a minute, we’d love to hear your feedback about our interaction today. Have a great day!
Thanks man! Good to know:good:
Soulfulgrey said:
Google rep - name redacted
(Time stamp removed)
Correct.
If there is an issue that would normally be covered under warranty, your warranty would be voided by having the operating system rooted or modified.
________________________________________
me
(Time stamp removed)
Ok. Here I just want to check with the bootloader. I have no plans to modify the OS.
________________________________________
Google rep - name redacted
(Time stamp removed)
In case you do, it doesn't void your warranty.
Click to expand...
Click to collapse
Hmmm I'm assuming thats a typo but its a very important one...
WoodroweBones said:
Hmmm I'm assuming thats a typo but its a very important one...
Click to expand...
Click to collapse
Yeah I saw that, too.
WoodroweBones said:
Hmmm I'm assuming thats a typo but its a very important one...
Click to expand...
Click to collapse
adamd1169 said:
Yeah I saw that, too.
Click to expand...
Click to collapse
It seems to directly contradict what was said before.
Won't be druv said:
It seems to directly contradict what was said before.
Click to expand...
Click to collapse
So unroot and flash stock before sending it on for warranty? Seems simple enough. I always do that anyways.
frigidazzi said:
So unroot and flash stock before sending it on for warranty? Seems simple enough. I always do that anyways.
Click to expand...
Click to collapse
That's how I read it too. By going back to stock, your system is no longer rooted or modified
Sent from my SM-G900V using Tapatalk
I don't think it does. They originally stated it's ok to unlock your bootloader and root the phone. Both of which can still be done while in operation of the stock ROM. But if you decide to flash a different ROM that isn't the stock OS and I'm assuming for some reason aren't able to flash back to stock then they won't help you because the warranty didn't cover user fault while running a version of Android that isn't stock.
heleos said:
That's how I read it too. By going back to stock, your system is no longer rooted or modified
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I never understood the whole thing in the first place. If factory images are published and customer support is going to ask you to flash them for troubleshooting, it makes no sense for a bootloader unlock to void the warranty.
Either way though thats good news :good:
That is exactly the response I got when I contacted them, so I am happy with that. I did ask their technical support if rooting the phone would break fingerprint support, they didnt know.
Certainly on my One Plus Two I can be fully rooted and still use fingerprint scanner. There was issues on some AOSP CM based roms, as the blobs for the fingerprint scanner were not available, but on factory images it was fine.
like is being said before, a factory images restores your device to out of the box state...
but part of the factory image reflash process requires to unlock the bootloader in order for it to work. i mean, its part of the flash-all.bat!!!!
so unlocking the actual bootloader cant void the warranty.
It would be very un-google of them to break anything that chould't be fixed by reloading factory image and re-locking.
Stephen said:
That is exactly the response I got when I contacted them, so I am happy with that. I did ask their technical support if rooting the phone would break fingerprint support, they didnt know.
Certainly on my One Plus Two I can be fully rooted and still use fingerprint scanner. There was issues on some AOSP CM based roms, as the blobs for the fingerprint scanner were not available, but on factory images it was fine.
Click to expand...
Click to collapse
The only worrying thing about rooting and fingerprint support is that of breaking Android Pay, one of the things I've been looking forward to since the Nexus S!
kboya said:
The only worrying thing about rooting and fingerprint support is that of breaking Android Pay, one of the things I've been looking forward to since the Nexus S!
Click to expand...
Click to collapse
I think we can forget about AP working if you root. Fingerprint unlock should be fine but it won't matter if it's AP you want. I think the only way you'll be able to get root and Pay working is if multirom comes to the device and you can flash M as a secondary rom unrooted like I have now on the N5. Kind of a pain to reboot to a stock M and then reboot into my rooted rom but it works and only takes about a minute.
You're probably right. Certainly this post (http://www.xda-developers.com/googl...-with-root-and-android-pay-in-the-xda-forums/ )suggests we should give up on Android Pay with root. Then again, and I dont know this site or its veracity, but this looks promising: http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
We shall see, although Android Pay in the UK may still be some way off.
kboya said:
You're probably right. Certainly this post (http://www.xda-developers.com/googl...-with-root-and-android-pay-in-the-xda-forums/ )suggests we should give up on Android Pay with root. Then again, and I dont know this site or its veracity, but this looks promising: http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
We shall see, although Android Pay in the UK may still be some way off.
Click to expand...
Click to collapse
Those methods don't work. At least not reliably. I'm not sure what the triggers are but I have an unlocked bootloader and I have AP working on a non rooted stock M build, so it's not the bootloader. Every other rooted build would not let me use AP whether or not it was the internal/primary rom or a secondary.
Now I'm not sure if that's a good thing or a bad thing. With all the cc problems and vulnerabilities rooted roms can bring to a device for the uninitiated, in order to secure the payment process I do believe unrooted is the only way to go.
Is there a case where you'd have to flash the stock images on a phone that has never been unlocked? The partitions couldn't have been modified anyway. A factory reset should be enough to return to stock.
Sent from my Nexus 6 using Tapatalk
Cheater912 said:
Is there a case where you'd have to flash the stock images on a phone that has never been unlocked? The partitions couldn't have been modified anyway. A factory reset should be enough to return to stock.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes potentially. The case I recall in particular I believe was with a Nexus 7 tablet. The user was having all sorts of issues with it so Google tech support walked him through unlocking the bootloader and reflashing the factory image. In the end I believe it was determined his storage was bad IIRC
So if unlocking the boot loader does not void the warranty and is even necessary for flashing a stock image, then why did they do this Qfuse thing? I mean, you can see if a phone has an unlocked bootloader just by booting to the bootloader. I don't get it. Why this need for absolute knowledge as to whether a phone has ever had an unlocked bootloader or not? It just seems designed to make people worry they did some horrible irrevocable thing.
Probably to placate banks lol
I have got Obi Worldphone Sf1 which is running android 5.0.1 . I tried every method i could and found on google and xda. But couldnt manage to root? I did all steps as noob but now i really want learn every depth of rooting and all. I thought to build android development env that i found on xda-university to build custom recovery like cwm or twrp. So my question is what are basics of rooting? I know what root is. I have experience of linux. I am not completely noob. So can anybody tell me which way to go to be a good android developer?? (like chainfire )
xactor said:
I have got Obi Worldphone Sf1 which is running android 5.0.1 . I tried every method i could and found on google and xda. But couldnt manage to root? I did all steps as noob but now i really want learn every depth of rooting and all. I thought to build android development env that i found on xda-university to build custom recovery like cwm or twrp. So my question is what are basics of rooting? I know what root is. I have experience of linux. I am not completely noob. So can anybody tell me which way to go to be a good android developer?? (like chainfire )
Click to expand...
Click to collapse
great so you are like me. The first step is to get the root working. Still no dev has managed to make this thing to work. Well for the most of the part our's is a great device, but at the same time because of unavaliability of kernel resources it is not listed in xda too. Until some experience dev comes out and do some force method to root this phone, there is no hope of ray. First to mess with phone you need a recovery so if anything go haywire then you can revert back to the safe backup.....
sachoosaini said:
great so you are like me. The first step is to get the root working. Still no dev has managed to make this thing to work. Well for the most of the part our's is a great device, but at the same time because of unavaliability of kernel resources it is not listed in xda too. Until some experience dev comes out and do some force method to root this phone, there is no hope of ray. First to mess with phone you need a recovery so if anything go haywire then you can revert back to the safe backup.....
Click to expand...
Click to collapse
Yes, I even talked with service representative of Obi Worldphone. He said that they dont have policy of sharing kernal source etc.
xactor said:
Yes, I even talked with service representative of Obi Worldphone. He said that they dont have policy of sharing kernal source etc.
Click to expand...
Click to collapse
what does that mean... Every company has to abide my GPL no matter what they are what they do. Well its shame that when indian companies like MICROMAX are releasing their kernel resources they are not going for it. @zelendel (can you shed some light here brother) http://www.obiworldphone.com/global/
See in ss..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sachoosaini said:
what does that mean... Every company has to abide my GPL no matter what they are what they do. Well its shame that when indian companies like MICROMAX are releasing their kernel resources they are not going for it. @zelendel (can you shed some light here brother) http://www.obiworldphone.com/global/
Click to expand...
Click to collapse
I am looking into it. The fact that they state every device is designed in the states might be useful. Hold tight while I get in contact with them.
zelendel said:
I am looking into it. The fact that they state every device is designed in the states might be useful. Hold tight while I get in contact with them.
Click to expand...
Click to collapse
Well Thank you very much brother. Nice to hear from you.. We hope something going to happen soon.
Well any news ?? @zelendel
sachoosaini said:
Well Thank you very much brother. Nice to hear from you.. We hope something going to happen soon.
Well any news ?? @zelendel
Click to expand...
Click to collapse
I have tried contacting them but heard nothing back in reply so far. This is nothing uncommon. Seems that they are just another device OEM from China as OEM from there dont have to respect the GPL.
zelendel said:
I have tried contacting them but heard nothing back in reply so far. This is nothing uncommon. Seems that they are just another device OEM from China as OEM from there dont have to respect the GPL.
Click to expand...
Click to collapse
Well as usual. So lets wait if they voluntary put their kernel resources online .
sachoosaini said:
Well as usual. So lets wait if they voluntary put their kernel resources online .
Click to expand...
Click to collapse
I dont wait. I will be getting a hold of them again.
If you just wait on them then they will not do it. Mainly as they are not required to due to where they are.
zelendel said:
I dont wait. I will be getting a hold of them again.
If you just wait on them then they will not do it. Mainly as they are not required to due to where they are.
Click to expand...
Click to collapse
One of their owner XApple CEO and other is Indian. And here in India I don't think except few does not give a heck about GPL.... Well most of companies just let it go approach... i also mailed them regarding as per GPL they need to put up their kernel resources online but no reply... Well just emailing i don't think going to have any effect on them.
sachoosaini said:
One of their owner XApple CEO and other is Indian. And here in India I don't think except few does not give a heck about GPL.... Well most of companies just let it go approach... i also mailed them regarding as per GPL they need to put up their kernel resources online but no reply... Well just emailing i don't think going to have any effect on them.
Click to expand...
Click to collapse
I have dealt with a few India based companies and it always comes down to the fact that they just rebrand China devices. Micromax being one of them.
Soon India will have to worry about things like this as it is along the copy right issues that they are trying not to fall into.
Emailing them is a good start, I would also contact who ever you can in the government. While I understand that Gov are different so you could use what ever might work. If it was me I would use the fact that it doesnt make them look good to openly support copyright infringement.
zelendel said:
I have dealt with a few India based companies and it always comes down to the fact that they just rebrand China devices. Micromax being one of them.
Soon India will have to worry about things like this as it is along the copy right issues that they are trying not to fall into.
Emailing them is a good start, I would also contact who ever you can in the government. While I understand that Gov are different so you could use what ever might work. If it was me I would use the fact that it doesnt make them look good to openly support copyright infringement.
Click to expand...
Click to collapse
well as per India there is no specific clause on rooting your phone. Companies just says that if you root your warranty is void. There was never any or whatsoever debate anywhere in Parliament or any public forum. And its better if this kind of thing don't come to INdia i mean rooting debate coz certain companies may force govt to make root illegal. So sometime we can see bigger picture in small loophole
sachoosaini said:
well as per India there is no specific clause on rooting your phone. Companies just says that if you root your warranty is void. There was never any or whatsoever debate anywhere in Parliament or any public forum. And its better if this kind of thing don't come to INdia i mean rooting debate coz certain companies may force govt to make root illegal. So sometime we can see bigger picture in small loophole
Click to expand...
Click to collapse
Rooting I really isn't the focus of it. Yes you would be able to have root if the bootloader could be unlocked. (totally different topic and nothing you really can do about that ) it's the kernel source that is the topic. Which by the GPL licence that all android kernels are based on require that the source code for the kernel on said device be made public upon request.
Rooting already pretty much voids warranties. This is why devs put red disclaimers in the OP of their threads. As for illegal, I am not versed in how the laws work there but the worst thing you would be doing is voiding your license you use the software that is on your phone. Nothing punishable by fines, jail or anything like that.
Website signature
zelendel said:
Rooting I really isn't the focus of it. Yes you would be able to have root if the bootloader could be unlocked. (totally different topic and nothing you really can do about that ) it's the kernel source that is the topic. Which by the GPL licence that all android kernels are based on require that the source code for the kernel on said device be made public upon request.
Rooting already pretty much voids warranties. This is why devs put red disclaimers in the OP of their threads. As for illegal, I am not versed in how the laws work there but the worst thing you would be doing is voiding your license you use the software that is on your phone. Nothing punishable by fines, jail or anything like that.
Website signature
Click to expand...
Click to collapse
Yeah I guess i gone away from the topic. But whenever the topic comes of following GPL companies dodge the question. And most of INdian companies just "nvm" thinking. And for rooting there is nothing like jail here... Things are changing here as people are getting conscious about what are laws and what companies main motive behind hiding like GPL. Well like in america people and devs community slams the companies for not putting sources online.
I have an interest in the Worldphone, but due to limits in my particular region, buying one would be like buying an iPod Touch. Can't get it online.
While bootloader unlock and the like should be possible, I think for now, it'll have to wait.
In the mean time, is there a possible file dump of things like the APKs that Obi Worldphone uses? No one else has access to the Obi Lifespeed UI except Worldphone users right now. If it's possible, can you grab the APKs with software like ES File Explorer, and ZIP it to a cloud?
UltimaXtreme said:
I have an interest in the Worldphone, but due to limits in my particular region, buying one would be like buying an iPod Touch. Can't get it online.
While bootloader unlock and the like should be possible, I think for now, it'll have to wait.
In the mean time, is there a possible file dump of things like the APKs that Obi Worldphone uses? No one else has access to the Obi Lifespeed UI except Worldphone users right now. If it's possible, can you grab the APKs with software like ES File Explorer, and ZIP it to a cloud?
Click to expand...
Click to collapse
As a onetime worldphone user i can tell you not to bother with it
The ui and every other app on it lags as af
Atleast in my case.
RebelO7 said:
As a onetime worldphone user i can tell you not to bother with it
The ui and every other app on it lags as af
Atleast in my case.
Click to expand...
Click to collapse
Performance ties very directly into device specifications.
Even if it lags, that's only the case known for the Obi Worldphone. There are several other phones in the world, with better processors than the SD615. An 800 may very well knock it out of the park compared to an SF1, and would no doubt topple the MV1, with its meager 212.
It's a simple request. The APKs to the exclusive applications. Even if it's the Lifespeed UI at most.
UltimaXtreme said:
Performance ties very directly into device specifications.
Even if it lags, that's only the case known for the Obi Worldphone. There are several other phones in the world, with better processors than the SD615. An 800 may very well knock it out of the park compared to an SF1, and would no doubt topple the MV1, with its meager 212.
It's a simple request. The APKs to the exclusive applications. Even if it's the Lifespeed UI at most.
Click to expand...
Click to collapse
It is simple enough but the UI in itself isnt all that good
I mean what do you like about it?
Its not like Lenovo's vibe UI or oneplus Oxygen OS
Its simply an icon pack and a different lockscreen
Dolby Atmos being the only somewhat redeeming feature of this phone.
RebelO7 said:
It is simple enough but the UI in itself isnt all that good
I mean what do you like about it?
Its not like Lenovo's vibe UI or oneplus Oxygen OS
Its simply an icon pack and a different lockscreen
Dolby Atmos being the only somewhat redeeming feature of this phone.
Click to expand...
Click to collapse
It's really that simple? Just a slightly colorful version of the stock lockscreen?
So beyond that, it's basically just AOSP versions of the other apps, I assume.
Pretty disappointing now that you bring that up. Seemed like it would be more intriguing than that.