Hello,
I found a Nice Sprint Nexus S on craigslist. The seller said it was on Sprint. He says is has the fast bootloader, but no Android OS. Is there a way to get the original OS back on it, or even a ROM. Considering purchase, but wanted to verify it is recoverable first. Thanks in advance.
has no android os??
thats a gamble right there sir
Benny1234 said:
Hello,
I found a Nice Sprint Nexus S on craigslist. The seller said it was on Sprint. He says is has the fast bootloader, but no Android OS. Is there a way to get the original OS back on it, or even a ROM. Considering purchase, but wanted to verify it is recoverable first. Thanks in advance.
Click to expand...
Click to collapse
yes!
Sent from my Nexus S using xda premium
Borky_16 do you have a link or directions on how to do it?
Is the bootloader unlocked? If so does it have clockwoorkmod? If so have u tried flashing a rom
Sent from my MIUI powered Nexus S 4g using XDA Premium App
Also try this http://forum.xda-developers.com/showthread.php?t=1078213
Sent from my MIUI powered Nexus S 4g using XDA Premium App
From what I understand it only has a bootloader. Can clockwordmod be installed on a device without an OS? That would certainly make things easier. I have recovered galaxy s phones from ODIN, but this is new territory for me.
Benny1234 said:
From what I understand it only has a bootloader. Can clockwordmod be installed on a device without an OS? That would certainly make things easier. I have recovered galaxy s phones from ODIN, but this is new territory for me.
Click to expand...
Click to collapse
If you can get a bootloader, you can flash everything using fastboot still. Basically you follow everything at this:
http://forum.xda-developers.com/showthread.php?t=1078213
Doesn't matter if it's locked or not, that should still work as long as you have a bootloader functioning.
Thank you very much.. One last question. Does anyone know which builds and radios are specific to the Sprint model? I want to make sure I have the right one before trying this. Thanks!
Benny1234 said:
Thank you very much.. One last question. Does anyone know which builds and radios are specific to the Sprint model? I want to make sure I have the right one before trying this. Thanks!
Click to expand...
Click to collapse
The link I provided is for the ns4g so all I need is there.
Sent from my MIUI powered Nexus S 4g using XDA Premium App
Is the esn clean????? If not then it may not be worth purchasing.
Sent from my Nexus S using Tapatalk
Related
Hei guys!
I first got a U8800, but there was a voltage problem with the phone and I had to return it. The store's authorized service center sent me a U8800Pro in return. The phone is shipped with Build number: U8800PV100R001C00B042, and I've never seen a ROM from Huawei listet with B042.
The problem is that I can't upgrade from Android 2.2.2 to the offical ROMs from Huawei. It just says "update failed" and a yellow warning triangle appears on the screen.
The 2.2.2 doesn't really work with my phone. Wi-fi and general performance is laggy and slow. Well, wi-fi doesn't work at all (needs 10 mins to download a 600KB file :S, but 3G works well thought").
I've been in contact with the service center but they don't really know what to do. They sent me a guide to unlock the bootloader but fastboot on the PC won't recognize the phone when in pink screen or boot loader screen. There is no "power" option in the "Settings"-menu so can't disable the fastboot option there.
I've searched every forum possible and I've got the proper USB-drivers etc etc etc
Does anybody know what to do?
Cheers
Aleksander
Send it back in maby? If something doesn't work you should be able to get a new one again if they can't fix it.
Sent from my U8800 using Tapatalk 2
Hmm
theminikiller said:
Send it back in maby? If something doesn't work you should be able to get a new one again if they can't fix it.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
I had the same thought myself, but I don't think the phone is broken. Had to wait four months to get the U8800pro-replacement-phone so I'm postponing it for as long as I can.
Has anyone heard of the B042 ROM or at least how I can use fastboot to unlock it?
If you can't update it I'd say that's broken for me, especially if they don't know how to fix it either. And shouldn't you be able to complain on getting back another phone model than you sent in?
About the other stuff I have no idea, sorry.
Sent from my U8800 using Tapatalk 2
I don't now if this is your case but it is nesesery upgrade first to gingerbread official 2.3 and then to ics.
Can you sent me this guide stuff or upload here?
Sent from my U8800PRO using xda app-developers app
SOLVED
theminikiller said:
If you can't update it I'd say that's broken for me, especially if they don't know how to fix it either. And shouldn't you be able to complain on getting back another phone model than you sent in?
About the other stuff I have no idea, sorry.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I agree. I'll return it first thing on monday.
gyankamp1 said:
I don't now if this is your case but it is nesesery upgrade first to gingerbread official 2.3 and then to ics.
Can you sent me this guide stuff or upload here?
Sent from my U8800PRO using xda app-developers app
Click to expand...
Click to collapse
I know you have to upgrade to 2.3 before 4.0, but the phone won't allow me to upgrade to 2.3, or any other ROM for that sake. Thanks though
I was on a phone call suddenly phone turned off. Tried booting it it would go past the GOOGLE logo. I went into recovery but nothing is able to mount. Trying flashing stock img through TOOLKIT errors, I guess cause won't mount. Any solutions? I heard it might be the EMMC chip?
Try flashing the factory images manually
http://forum.xda-developers.com/showthread.php?t=2010312
Sent using xda-developers app
Chromium_ said:
Try flashing the factory images manually
http://forum.xda-developers.com/showthread.php?t=2010312
Sent using xda-developers app
Click to expand...
Click to collapse
No :crying: like nothing can be flash. Every time I try it ends up with "flash write failed"
theedon323 said:
No :crying: like nothing can be flash. Every time I try it ends up with "flash write failed"
Click to expand...
Click to collapse
Last resort: http://forum.xda-developers.com/showthread.php?t=2347060
Yeah looks like the telltale sign of a dead emmc, like the Samsung Galaxy S3, sorry.
xda app
Chromium_ said:
Last resort: http://forum.xda-developers.com/showthread.php?t=2347060
Click to expand...
Click to collapse
Tried it and nothing. It's just not able to write into the system, fails everytime. I appreciate your help. LG G2 is next I guess.
eksasol said:
Yeah looks like the telltale sign of a dead emmc, like the Samsung Galaxy S3, sorry.
xda app
Click to expand...
Click to collapse
I think so. Do you know the reason for it? Do you think it was because i had the XPOSED framework mod?
theedon323 said:
I think so. Do you know the reason for it? Do you think it was because i had the XPOSED framework mod?
Click to expand...
Click to collapse
I use Xposed framework, I don't see that being the issue and how it could cause a hardware failure. I have heard this issue before when tons of people had their S3 died suddenly, there is a big thread of it in its forum.
You'll probably want to wait for the Nexus 5.
sent from xda premium app
eksasol said:
I use Xposed framework, I don't see that being the issue and how it could cause a hardware failure. I have heard this issue before when tons of people had their S3 died suddenly, there is a big thread of it in its forum.
You'll probably want to wait for the Nexus 5.
sent from xda premium app
Click to expand...
Click to collapse
That was my plan but I can't go another day without a phone D; isn't the Nexus basically a LG G2 just little tweaks and Kit Kat
theedon323 said:
That was my plan but I can't go another day without a phone D; isn't the Nexus basically a LG G2 just little tweaks and Kit Kat
Click to expand...
Click to collapse
Well it would be better if you have a backup phone. It will be based on the LG G2 and gsmarena.com even post is specs, but until it's officially announced by Google it's all speculation.
You could use get the G2, but since it's not the nexus you won't get the same software experience and developer support, price is a big deal as well. Also rumor is the Nexus 5 will support all LTE bands, but that's to be seen.
sent from xda premium app
So this happened to my phone. Brought it to a repair shop and said the EMMC was dead.
Long story short, credit card company refunded the purchase price, I bought a Nexus 5, but I still kept the dead Nexus 4.
Is it possible to buy a replacement part/motherboard to replace this, or is it completely shot (fine with that)?
If it is dead, I was going to recycle it or offer it up for parts. With an EMMC brick, is there anyway to recover any of my personal information that was on the phone?
Thanks!
You'd have to get a new motherboard. Check eBay. No way to get your info off out that I know.
Out of curiosity, what were your symptoms of the phone?. Did you ever try to lock the bootloader and it wouldn't lock?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You'd have to get a new motherboard. Check eBay. No way to get your info off out that I know.
Out of curiosity, what were your symptoms of the phone?. Did you ever try to lock the bootloader and it wouldn't lock?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Motherboard ~$100. Might give it try. The teardown instructions dont' seem too daunting. Do I have to worry about this IMEI stuff?
As for symptoms. I was completely stock, and locked bootloader. I was doing something and then it froze on me.
Went to reboot, and it was stuck on the boot animation (merging dots).
Ended up trying a tool kit to flash the phone. It worked, got back into the system and as it was downloading apps, it froze again.
This time, when I went to reflash, it would error would error with a "failure to write to flash".
recovery.img flashing
your emmc is not corrupt. you want to flash single file of recovery.img.this file is in the firmware find by extract firmware by winrar and 7zip. first flash recovery.img than flash whole firmware by adb 100% it works . and also take help from nexus toolkit in future
owaisali said:
your emmc is not corrupt. you want to flash single file of recovery.img.this file is in the firmware find by extract firmware by winrar and 7zip. first flash recovery.img than flash whole firmware by adb 100% it works . and also take help from nexus toolkit in future
Click to expand...
Click to collapse
You realize this thread is two years old right ?
but i read it know
boltthrower56 said:
You realize this thread is two years old right ?
Click to expand...
Click to collapse
dear i don't know who is you but i read it know because of that i give the solution of these problem hehehe
owaisali said:
dear i don't know who is you but i read it know because of that i give the solution of these problem hehehe
Click to expand...
Click to collapse
It could help someone here, I'm facing the same issue, could you please detail your suggestion please?
Here is my request for help...
http://forum.xda-developers.com/nexus-4/help/nexus-4-stuck-animation-android-t3419997
Newbie here... :/
The Verizon Note 3 variant N900V has had it's bootloader bypassed by @Hashcode and custom recovery has now been achieved on that device. I talked to @bajasur who is running their bounty thread and he believes that the same safestrap method could possibly be used on the N900A (our version). If @Hashcode can get this to work on the N900A I am sure development will move quickly so get over to our bounty thread and make your bounty pledges now!!! http://forum.xda-developers.com/showthread.php?t=2493369
See @bajasur's N900V Bounty Thread here...
http://forum.xda-developers.com/showthread.php?t=2473918
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Awesome!
Sent from my SAMSUNG-SM-N900A using Tapatalk
slidesear said:
Awesome!
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Definitely great news!!!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I don't mean to be a downer, but I'm still on the fence whether I can get this working on the AT&T variant.
So let's hold off on any specific donations. :/
Fingers crossed! this would be great news!!!
Hashcode said:
I don't mean to be a downer, but I'm still on the fence whether I can get this working on the AT&T variant.
So let's hold off on any specific donations. :/
Click to expand...
Click to collapse
Pledges....meant pledges. Will update the OP...sorry @Hashcode.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
That would be pretty sweet
Sent from my SAMSUNG-SM-N900A using Tapatalk
Does this trip knox
Sent from my SM-N900W8 using Tapatalk
Canadoc said:
Does this trip knox
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
At this point we will just have to wait and see what happens. I would imagine it doesn't but since it is currently being worked on and not confirmed we will have to just be patient...which I clearly wasn't with this thread.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Isn't this the same thing that happened with the s4? Bootloader exploited on verizon variant, didnt know if it would work for anyone else and it did?
Sent from my VS980 4G using Tapatalk
MrPlNK said:
Isn't this the same thing that happened with the s4? Bootloader exploited on verizon variant, didnt know if it would work for anyone else and it did?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
The difference is ATT in addition to a locked bootloader made SELinux Enforcing. The VZW has permissive from what I've read.
mircury said:
The difference is ATT in addition to a locked bootloader made SELinux Enforcing. The VZW has permissive from what I've read.
Click to expand...
Click to collapse
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
kennonk said:
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
Click to expand...
Click to collapse
Normally it doesn't have anything to do with the bootloader but in this case since we can't crack or modify the bootloader we have to hijack the real /system into loading a recovery on a special partition along with a fake /system located on the internal sdcard. Whether or not SELinux enforcement policies prevent this or causes problems later if it does boot, we don't know yet. What it does do for sure is make it more difficult.
Same
kennonk said:
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
Click to expand...
Click to collapse
Same here. I hate that AT&T is doing this. It's crazy how the tables have turned, as it used to be (As with the S4) we would get a way to flash a recovery before the VZW variant, but now it seems that has changed. Is the Knox option only on our variant or is it on VZW too?
I got super excited when I first saw this but then depressed when I found out that it hasn't fully been achieved... what is the difference from the way that the s4 was cracked? It had knox too didn't it?
Sent from my SAMSUNG-SM-N900A using Tapatalk HD
I have verizon and no it doesn't trip knox
tropazr said:
The Verizon Note 3 variant N900V has had it's bootloader bypassed by @Hashcode and custom recovery has now been achieved on that device. I talked to @bajasur who is running their bounty thread and he believes that the same safestrap method could possibly be used on the N900A (our version). If @Hashcode can get this to work on the N900A I am sure development will move quickly so get over to our bounty thread and make your bounty pledges now!!! http://forum.xda-developers.com/showthread.php?t=2493369
See @bajasur's N900V Bounty Thread here...
http://forum.xda-developers.com/showthread.php?t=2473918
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
SunnyOK said:
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=48555170
We have Safestrap now. Read up on it!
Sent from my SAMSUNG-SM-N900A using Tapatalk
SunnyOK said:
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
Click to expand...
Click to collapse
Have you not looked in the development forums?
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Agent said:
Have you not looked in the development forums?
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately the bootloader is still locked and hasn't been bypassed. What safestrap does is hijack the boot process once it reaches the /system partition. That is after the bootloader. It then runs a modified recovery. This is why you can't run custom kernels on it yet. The /boot partition is still protected. Don't get me wrong though it's a huge step in the right direction.
Haven't spent much time researching but time is short before Monday' sale/
Why would I want the developer edition over a standard designed phone. I'm just not quite understanding what the advantage of the developer version is. I do want to root if that's a factor.
Thanks.
homemadehitshow said:
Haven't spent much time researching but time is short before Monday' sale/
Why would I want the developer edition over a standard designed phone. I'm just not quite understanding what the advantage of the developer version is. I do want to root if that's a factor.
Thanks.
Click to expand...
Click to collapse
Two things:
1. You get to keep your warranty if you unlock the bootloader
2. You don't have to worry about root exploits for FUTURE OTA releases; current software already has root.
Other than that, they are identical devices except that you can customize the regular version.
chaoslimits said:
Two things:
1. You get to keep your warranty if you unlock the bootloader
2. You don't have to worry about root exploits for FUTURE OTA releases; current software already has root.
Other than that, they are identical devices except that you can customize the regular version.
Click to expand...
Click to collapse
Developer edition has root by default out of the box?
d14gvn said:
Developer edition has root by default out of the box?
Click to expand...
Click to collapse
No you don't have root out of the box. With developer edition, you can unlock the bootloader, flash a new recovery, and install su (root) using fastboot. You can do it at any time.
For the regular version, you need to root using Jcase's exploit (in the Development forum) which is also relatively easy to do.
chaoslimits said:
No you don't have root out of the box. With developer edition, you can unlock the bootloader, flash a new recovery, and install su (root) using fastboot. You can do it at any time.
For the regular version, you need to root using Jcase's exploit (in the Development forum) which is also relatively easy to do.
Click to expand...
Click to collapse
But with regular version you can flash TWRP recovery too and get SU with that, I see no difference in there.
I think the difference is in when you unlock your bootloader, developer edition doesn't lost its warranty
d14gvn said:
But with regular version you can flash TWRP recovery too and get SU with that, I see no difference in there.
I think the difference is in when you unlock your bootloader, developer edition doesn't lost its warranty
Click to expand...
Click to collapse
For now yes. If we get another OTA and no one makes a root exploit, the regular version may be stuck without root. If you care that much about having root, the dev edition is most likely the better choice. If you're not too worried about not having root in future OTAs (who knows if we'll actually get another major OS bump) the I guess the custom versions are going to be more interesting to you.
chaoslimits said:
For now yes. If we get another OTA and no one makes a root exploit, the regular version may be stuck without root. If you care that much about having root, the dev edition is most likely the better choice. If you're not too worried about not having root in future OTAs (who knows if we'll actually get another major OS bump) the I guess the custom versions are going to be more interesting to you.
Click to expand...
Click to collapse
Thank you for that information. :good:
Dev edition is also more "figure proof" whereas after motorola stop supporting the phone you can still get android updayes so long as there are devs building them.
Thanks for the info guys. I'm really considering upgrading from my Nexus 4. I would have preferred a different color but I think I'd go with the developer edition. I'm getting ready to go through the forums but how do you guys feel the developer support is compared to the Nexus 4? I use CWM recovery and like CM and AOSPA a lot. Does performance take a hit on custom ROMs compared to stock which is from my understanding highly optimized?
Sent from my Nexus 4 using XDA Premium 4 mobile app
homemadehitshow said:
Haven't spent much time researching but time is short before Monday' sale/
Why would I want the developer edition over a standard designed phone. I'm just not quite understanding what the advantage of the developer version is. I do want to root if that's a factor.
Thanks.
Click to expand...
Click to collapse
If you don't know why you need the developer edition, then you don't need the developer edition.
Sent from my XT1060 using Tapatalk
Can anyone speak to the LTE bands for ATT on DE? It looks like it has 17 covered but ATT can also use 4(?) and I think Wikipedia says 29 in the future. I'd hate to get it and stop getting LTE in areas I'm getting it in now.
1ManWolfePack said:
If you don't know why you need the developer edition, then you don't need the developer edition.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Says the guy with the Tapatalk sig.
homemadehitshow said:
Says the guy with the Tapatalk sig.
Click to expand...
Click to collapse
Lol.
I do use tapatalk. And I don't put an obnoxious signature. I leave it default.
That was a HARD DISS YO
Sent from my XT1060 using Tapatalk
1ManWolfePack said:
Lol.
I do use tapatalk. And I don't put an obnoxious signature. I leave it default.
That was a HARD DISS YO
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I agree pretty harsh.....
Sent from my Nexus 7 using Tapatalk
mcsqwizzys98 said:
I agree pretty harsh.....
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
He just ripped on 87% of this community and doesn't even know it. Lol.
Anyways, for $400 - get the Dev. A true custom recovery and no root exploits needed.
SENT FROM MY TAPPED OUT CYAN PURPLE BUBBLE GUM TRANSPARENT WITH A CUSTOM KERNEL AND A CUSTOM ROM THAT I PAID FOR WITH MY OWN MONEY MOTOROLA MOBILITY MOTO X WITH SILVER HIGHLIGHTS AND NAVY BACK ON THE BIG RED NETWORK KNOWN AS VZW SENT FROM YOUR AUNTS HOUSE GO OBAMA
Sent from my XT1060 using Tapatalk
Oh I know it.
Sent from my electrical device.
Anyone know of any word on these two roms making a appearance here soon?
Sent from my SM-N900V using Tapatalk
There's like 8 of these threads already but long story short, no.
Sent from my SM-N900V using xda app-developers app
akellar said:
There's like 8 of these threads already but long story short, no.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Link me to the long story please
Sent from my Nexus 7 using Tapatalk 4
Jeremiah_1988 said:
Link me to the long story please
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Here's your long story short:
Until we get the bootloader unlocked, NONE of those ROMs will make it to this phone. Period.
carlz28 said:
Here's your long story short:
Until we get the bootloader unlocked, NONE of those ROMs will make it to this phone. Period.
Click to expand...
Click to collapse
Why do people keep saying this? I came from Droid Razr MAXX, locked bootloader. and officially supported by CM and AOKP.
If you dont believe me go here and select Razr Maxx and see. This is CM official download site. Not trying to argue, just sayin'. Dont be so sure we will not see that type of development.
http://wiki.cyanogenmod.org/index.php?title=Devices#vendor=;
willjohnson said:
Why do people keep saying this? I came from Droid Razr MAXX, locked bootloader. and officially supported by CM and AOKP.
If you dont believe me go here and select Razr Maxx and see. This is CM official download site. Not trying to argue, just sayin'. Dont be so sure we will not see that type of development.
http://wiki.cyanogenmod.org/index.php?title=Devices#vendor=;
Click to expand...
Click to collapse
Kind of what I thought, just going to try and wait patiently for more development
Sent from my Nexus 7 using Tapatalk 4
Again, they all use kexec or loki and neither will work on this device. Please read the other threads about this. They are all the same.
Sent from my SM-N900V using xda app-developers app
akellar said:
Again, they all use kexec or loki and neither will work on this device. Please read the other threads about this. They are all the same.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
This.
Safestrap (at least at the moment) doesn't support kexec or Loki for this device, which is the way those other devices manage to run custom kernels. Not saying its impossible, but likely improbable.
carlz28 said:
This.
Safestrap (at least at the moment) doesn't support kexec or Loki for this device, which is the way those other devices manage to run custom kernels. Not saying its impossible, but likely improbable.
Click to expand...
Click to collapse
All i was saying, is that our device is way to new to be saying what it will or wont have development on in the future. Thats just my opinion.
i have an unlocked developer edition where is my cm/aosp then haha
oneandroidnut said:
i have an unlocked developer edition where is my cm/aosp then haha
Click to expand...
Click to collapse
Apparently there are a lot of problems getting it working on this device. If you will notice, none of the note 3's have it, not even the international. I think part of it is knox, part of it is the bootloader, part of it is the hardware on the device. Samsung went above and beyond to keep this phone running their system.
shiftr182 said:
Apparently there are a lot of problems getting it working on this device. If you will notice, none of the note 3's have it, not even the international. I think part of it is knox, part of it is the bootloader, part of it is the hardware on the device. Samsung went above and beyond to keep this phone running their system.
Click to expand...
Click to collapse
i dont know what the issue could be. tmobile and dev editions are unlocked bootloaders and you dont have to run knox so idk unless knox is baked in somewhere where you cant get around it
oneandroidnut said:
i dont know what the issue could be. tmobile and dev editions are unlocked bootloaders and you dont have to run knox so idk unless knox is baked in somewhere where you cant get around it
Click to expand...
Click to collapse
Unlocked does not equal aosp, at least functioning. Ril is likely an issue.
Sent from my SM-N900V using xda app-developers app
Sbrissen said he'd make it happen if he were to obtain a device...... Dev Edition....
TechSavvy2 said:
Sbrissen said he'd make it happen if he were to obtain a device...... Dev Edition....
Click to expand...
Click to collapse
i have a friends bricked note 3 he can get haha