hi guys
i have galaxy nexus 16 GB it was good until i did "factory data reset", then the phone says "SIM network unlock PIN"
-all the last android phones those i was dealing with didn't that before!!!
-what's going on "did i make some wrong"
by the way i'm using "Djezzy" -Algeria
{
"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"
}
Try taking out your sim, I'm assuming its a GSM model, and if that works set everything up on wifi and put it back in. I've seen locked sim cards before. You might have to get another one from your provider
Sent from my Galaxy Nexus using xda premium
the phone was working great until i did factory data reset???
Do you have a DoCoMo branded nexus? There are some known issues with DoCoMo nexus devices reverting to a locked state when factory reset.
Sent from my Galaxy Nexus using xda app-developers app
thos25 said:
Do you have a DoCoMo branded nexus? There are some known issues with DoCoMo nexus devices reverting to a locked state when factory reset.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
how can i know?
by the way it's written " fabrique en corée par Samsung" which it mean does "made in Korea by Samsung"
in the battery i found that date "2011.11.09"
samhawk said:
how can i know?
by the way it's written " fabrique en corée par Samsung" which it mean does "made in Korea by Samsung"
Click to expand...
Click to collapse
Check the back. Does it look like this one?
Wait. It says that in French? You probably have a non-NTT DoCoMo GSM model.
Sent from my Galaxy Nexus using Tapatalk 2
rmcsc said:
Check the back. Does it look like this one?
Wait. It says that in French? You probably have a non-NTT DoCoMo GSM model.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks --
no it's like that:
samhawk said:
thanks --
no it's like that:
Click to expand...
Click to collapse
Plain old GSM model.
Did you try booting it without the SIM inserted as suggested?
Sent from my Galaxy Nexus using Tapatalk 2
Just download the toolkit and do an oem unlock, and reflash the stock image.
rmcsc said:
Plain old GSM model.
Did you try booting it without the SIM inserted as suggested?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I did the booting with sim inserted
Sinfamy said:
Just download the toolkit and do an oem unlock, and reflash the stock image.
Click to expand...
Click to collapse
Thanks but I the phone is new I mean without root or something like that
And I did not get it "how to do"
did I lost my phone
Sent from my galaxy nexus
samhawk said:
hi guys
i have galaxy nexus 16 GB it was good until i did "factory data reset", then the phone says "SIM network unlock PIN"
-all the last android phones those i was dealing with didn't that before!!!
-what's going on "did i make some wrong"
by the way i'm using "Djezzy" -Algeria
Click to expand...
Click to collapse
The device you bought was SIM-locked to a carrier. Where did you buy it from? If they said it was unlocked, then they need to provide you the code. Otherwise, you can get around it by using this or this.
efrant said:
The device you bought was SIM-locked to a carrier. Where did you buy it from? If they said it was unlocked, then they need to provide you the code. Otherwise, you can get around it by using this or this.
Click to expand...
Click to collapse
So if my phone was unlocked then will i just enter the pin code ?
is that was normal in the galaxy nexus?
samhawk said:
So if my phone was unlocked then will i just enter the pin code ?
is that was normal in the galaxy nexus?
Click to expand...
Click to collapse
Most Galaxy Nexus devices are sold SIM-unlocked. However, there are some, like yours, that are sold SIM-locked. If they are sold SIM-locked, you need a code to allow it to work on carriers OTHER than the one the device was locked to (which someone already entered in your phone before you bought it). Once the code is entered, it will work exactly like a SIM-unlocked device until such time when you either do a factory reset or flash a different ROM. When that happens, you will need to re-enter the code OR use one of the methods I linked to above.
samhawk said:
Thanks but I the phone is new I mean without root or something like that
And I did not get it "how to do"
Click to expand...
Click to collapse
You don't need root or anything for the toolkit. Also, if you don't ask it to root your phone, it won't. It's. Pretty straightforward process. Just pick the one that combines the download stock image from Google to flash it and whatnot.
Sent from my Galaxy Nexus using Tapatalk 2
rmcsc said:
You don't need root or anything for the toolkit. Also, if you don't ask it to root your phone, it won't. It's. Pretty straightforward process. Just pick the one that combines the download stock image from Google to flash it and whatnot.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The OP's issue is that he has a SIM lock, and he needs it unlocked. A toolkit is not going to help him with that. The links I posted will.
And I never recommend using toolkits for anything -- you may end up having issues.
hi guy than thanks
i have unlocked the phone by using efrant's solution
thanks again
-i have made "root", did i lost the Google officially support?
-and if i make a "factory data reset" or install new ROM (official or Cooked), will the phone lock again?
thanks again!!!
samhawk said:
[snip]
-i have made "root", did i lost the Google officially support?
Click to expand...
Click to collapse
No, you will still get updates, assuming you didn't change files on the system partition.
samhawk said:
-and if i make a "factory data reset" or install new ROM (official or Cooked), will the phone lock again?
Click to expand...
Click to collapse
Yes, but just use the same procedure to unlock.
thanks
Related
Alright, I updated my GS3 to the T999UVLH2 and I had google wallet installed before and I didn't wipe it or anything/ reset google wallet either, now it is just stuck at "Adding card" and I wanna know if I lost my secure element can anyone help me? And if I did Is there anyway to fix it?
Marshall2017 said:
Alright, I updated my GS3 to the T999UVLH2 and I had google wallet installed before and I didn't wipe it or anything/ reset google wallet either, now it is just stuck at "Adding card" and I wanna know if I lost my secure element can anyone help me? And if I did Is there anyway to fix it?
Click to expand...
Click to collapse
Mm when secure element brakes it will tell you right away, try unistalling the app or clearing cache and set it up again
Sent from my SGH-T999 using Tapatalk 2
My wallet won't scan after the update. It works and I can add cards and stuff but it won't pay for anything. NFC works otherwise though.
I guess I'm saying your problems may not be over once you solve this one.
So what your saying it will probably be better to just wait for isis?
Sent from my SGH-T999 using xda premium
Are you rooted? On a custom rom? And if so which one? I recently flashed the updated radio (T999UVLH3) and my wallet is working just fine. I'm rooted and on a custom Rom though (WICKED_IR[v1]). You may also want to take a look at the link and follow directions step by step. Hope I was of help.
http://forum.xda-developers.com/showthread.php?t=1769083
I also am having a problem with Google Wallet. I am rooted running Stock rom. I added prepaid card for $10 just fine (I followed the directions in the link listed above). I just can't spend it nor use any other card. I tried at 2 different stores. I really want to stay on the stock rom. If anyone can help I would greatly appreciate it.
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue ROOTED running Stock ROM
Try uninstalling the app, change build.prop, reboot to recovery and flash the two files for Google wallet.
Sent from my SGH-T999 using xda app-developers app
tiisai44 said:
I also am having a problem with Google Wallet. I am rooted running Stock rom. I added prepaid card for $10 just fine (I followed the directions in the link listed above). I just can't spend it nor use any other card. I tried at 2 different stores. I really want to stay on the stock rom. If anyone can help I would greatly appreciate it.
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue ROOTED running Stock ROM
Click to expand...
Click to collapse
Try using wallet at a mcdonalds or cvs. Those worked perfect for me. I also flashed a new version of the rom im on and its still working fine. If youre still lost, pm me and ill see if i can walk u through it some more
Sent From The Best Phone Ever Made
It's known that payment won't work on the latest OTA update, there's no workaround at this time.
Sent from the current Heavy Weight Champ GALAXY SIII
Google Play says that Google Wallet is not compatible with my current phone? How are you guys installing Google Wallet?
Bigsmooth843 said:
Are you rooted? On a custom rom? And if so which one? I recently flashed the updated radio (T999UVLH3) and my wallet is working just fine. I'm rooted and on a custom Rom though (WICKED_IR[v1]). You may also want to take a look at the link and follow directions step by step. Hope I was of help.
http://forum.xda-developers.com/showthread.php?t=1769083
Click to expand...
Click to collapse
What he said: http://forum.xda-developers.com/showthread.php?t=1769083
Sent from my SGH-T999
ingenious247 said:
It's known that payment won't work on the latest OTA update, there's no workaround at this time.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
I have a "newer older version" with the white background that is working fine for me, i can link the apk to my dropbox if you'll need it
Sent From The Best Phone Ever Made
So I broke my secure element by updating to the new ota leak..... Probably no way fix it is there?
{
"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"
}
Marshall2017 said:
So I broke my secure element by updating to the new ota leak..... Probably no way fix it is there?
Click to expand...
Click to collapse
You can fix it. There are a couple ways. First did you just install google wallet or did you flash a rom? If you flashed a rom then go to the apps page there are instructions, http://forum.xda-developers.com/showthread.php?t=1872161
There is another way as well follow these instructions: http://forum.xda-developers.com/showthread.php?t=1794727
If you just did an update and you are getting the error you can definately fix it, its'just a bad install of google wallet.
Gluck and let us know how things turn out. I got out of insecure element several times now so don't give up.
deathpulse said:
Google Play says that Google Wallet is not compatible with my current phone? How are you guys installing Google Wallet?
Click to expand...
Click to collapse
I have the same question here. How did you guys install it? I am rooted and on Stock.
http://forum.xda-developers.com/showthread.php?p=28679456
Sent from my SGH-T999 using xda premium
Possible fix to add other cards.
tiisai44 said:
I also am having a problem with Google Wallet. I am rooted running Stock rom. I added prepaid card for $10 just fine (I followed the directions in the link listed above). I just can't spend it nor use any other card. I tried at 2 different stores. I really want to stay on the stock rom. If anyone can help I would greatly appreciate it.
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue ROOTED running Stock ROM
Click to expand...
Click to collapse
If you followed the guide to add Google Wallet when you had to change the build prop you can try what I did. I changed my build prop back to the changes I had to make to originally install and activate wallet. I ran wallet for awhile but got tired of transferring money onto the Google prepaid card and wanted to add my debit. Here's what I did:
1) I changed the build prop back to the Galaxy Nexus stuff.
2) Rebooted into recovery.
3) Clicked Reboot
4) Went to wallet
5) Added my debit card; it took awhile to activate.
6) Changed build prop stuff back to the t-mobile samsung stuff
7) Card was saved in wallet.
8) Tried to use it at McDonalds first and NFC didn't start
9) Rebooted phone
10) It worked about 6 hours later at Sheetz gas station. Seems good to go!
Hope this helps.
I have a LG Nitro HD, which I unbricked, rooted, etc, and upgraded to Cyanogenmod 10.1. Worked great, I ended up giving it to my friend. He gave it back to me the other day because his brother accidentally did a factory reset and it "DOESNT WORK" as he put it. So i tried doing setup manager and stuff and whenever i clicked a button, it froze and rebooted. I reflashed CM10.1, same thing. Flashed to PARANOIDANDROID, same thing. On the lockscreen, everything is fine. I can touch the screen and pull down notification center without any issue, but as soon as i unlock it and touch the screen, it locks up and reboots. It seems like it's allergic to my touch....any help would be greatly appreciated as he wants to sell it.
Thanks!
drsn0w
Maybe going through the unbrick process again will fix the problem.
audit13 said:
Maybe going through the unbrick process again will fix the problem.
Click to expand...
Click to collapse
Don't I have to go back to stock to do that? Because I've tried, and the LG Support Software won't see the phone.
drsn0w said:
Don't I have to go back to stock to do that? Because I've tried, and the LG Support Software won't see the phone.
Click to expand...
Click to collapse
Did you put the phone in download mode 1st? Start with the phone powered off. Plug the lg supplied USB cable into the computer. Then hold down vol up and plug the USB cable into the phone. As long as the lg drivers are installed the lg support software will see it
Sent from my LG-P930 using xda app-developers app
Oh I completely forgot about download mode. I'll try that once the house wakes up (my computer is about as loud as a foghorn)
Sent from my SPH-L710 using xda app-developers app
Okay so it's connected (after installing USB drivers 7 times...) but it's connected, and it says it's running the latest software. So what am i supposed to do now...?
{
"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"
}
Never mind....I found this: https://forum.xda-developers.com/showthread.php?t=1597488
drsn0w said:
Never mind....I found this: https://forum.xda-developers.com/showthread.php?t=1597488
Click to expand...
Click to collapse
We're you able to get through the unbricking process?
If not, you can try and emergency restore by clicking on the Help button and changing your region or recovery mode.
audit13 said:
We're you able to get through the unbricking process?
If not, you can try and emergency restore by clicking on the Help button and changing your region or recovery mode.
Click to expand...
Click to collapse
Yes, I was, thank you. I got through unbricking, rooted it, installed TWRP 2.6.x, flashed CM10.1.2, and have just ordered my unlock code
audit13 said:
We're you able to get through the unbricking process?
If not, you can try and emergency restore by clicking on the Help button and changing your region or recovery mode.
Click to expand...
Click to collapse
Haha well turns out I jumped the gun and flashed CM10.1 too soon...apparently I have to have the stock ROM to SIM unlock it....reunbricking...
drsn0w said:
Yes, I was, thank you. I got through unbricking, rooted it, installed TWRP 2.6.x, flashed CM10.1.2, and have just ordered my unlock code
Click to expand...
Click to collapse
Good stuff. I'm not sure where you ordered your code but I have used this place before and it was cheap: http://www.cell-1st.com/lgcodes.htm
---------- Post added at 10:26 AM ---------- Previous post was at 10:24 AM ----------
drsn0w said:
Haha well turns out I jumped the gun and flashed CM10.1 too soon...apparently I have to have the stock ROM to SIM unlock it....reunbricking...
Click to expand...
Click to collapse
This may work with a custom rom: http://sim-unlock.net/simlock/LG/Nitro_P930/
audit13 said:
Good stuff. I'm not sure where you ordered your code but I have used this place before and it was cheap: http://www.cell-1st.com/lgcodes.htm
Click to expand...
Click to collapse
I used an eBay unlocker that I've had previous success with. Thank you though! Now to put stock back...again...lol...
Also yeah I tried the 2945 code but it doesn't work in Cyanogenmod10, and after some digging, I found that it's best to unlock on the stock ROM anyways.
drsn0w said:
Haha well turns out I jumped the gun and flashed CM10.1 too soon...apparently I have to have the stock ROM to SIM unlock it....reunbricking...
Click to expand...
Click to collapse
You don't have to unbrick again just flash one of the stock ROMs available.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
You don't have to unbrick again just flash one of the stock ROMs available.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
too late haha. Okay but now I can't seem to unlock it. Got my unlock code but when i go and click Network Lock, it comes up with "Your phone is not personalized."
I read that this mean's it's already unlocked, but i don't recall unlocking this before
drsn0w said:
too late haha. Okay but now I can't seem to unlock it. Got my unlock code but when i go and click Network Lock, it comes up with "Your phone is not personalized."
I read that this mean's it's already unlocked, but i don't recall unlocking this before
Click to expand...
Click to collapse
As long as it doesn't say sim locked and you have data access you should be good to go.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
As long as it doesn't say sim locked and you have data access you should be good to go.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately i don't have my TMo sim with me right now, or an AT&T one, for that matter. I'll be getting it later today, I'll let you know how it goes
Swetnes said:
As long as it doesn't say sim locked and you have data access you should be good to go.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Worked perfectly! Voice, SMS, HSPA+, even LTE!!!!
learn it, Useful experience
It's finally here. Downloading from NYC. 695mb
{
"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"
}
Sent from my SM-P600 using Tapatalk
Enjoy.....g
wilsonhuang said:
It's finally here. Downloading from NYC. 695mb
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Can we get a screen shot of your "About device page... expecially the baseband and kernel versions... build also if possible.
Can someone let us know if the update fixes the stupid screen rotation bug when you turn off auto-brightness. Also, if there is a noticeable change in overall snapiness. Thanks!
jfkerekes said:
Can we get a screen shot of your "About device page... expecially the baseband and kernel versions... build also if possible.
Click to expand...
Click to collapse
It's up sir!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
General noob question:
How would I go about rooting 4.3 for AT&T? Can someone point me to the thread of it exists? Yes I've tried the search function and no nothing exact came up. I don't want to mess up and then be "that guy" on here crying about making a noob mistake.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Jspex said:
General noob question:
How would I go about rooting 4.3 for AT&T? Can someone point me to the thread of it exists? Yes I've tried the search function and no nothing exact came up. I don't want to mess up and then be "that guy" on here crying about making a noob mistake.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
See Dr. Ketan and his thread regarding the bootloader on 4.3.....g
Will you be able to go back to 4.1.2 if you take this update?
gregsarg said:
See Dr. Ketan and his thread regarding the bootloader on 4.3.....g
Click to expand...
Click to collapse
But that's a thread specifically for 7100-based (non-LTE) variants, right? Whereas we have n7105-based LTE Versions...if I'm missing something please let me know. TIA.
Keeping root after 4.3 update
Jspex said:
General noob question:
How would I go about rooting 4.3 for AT&T? Can someone point me to the thread of it exists? Yes I've tried the search function and no nothing exact came up. I don't want to mess up and then be "that guy" on here crying about making a noob mistake.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I rooted using this method while still on 4.1.2 and it worked flawlessly.
I then paid for and installed SuperSU Pro and activated "Survival Mode"
Lastly, after the OTA update was COMPLETELY finished, I followed this simple procedure to get root back again.
SuperSU disables Knox for you on 4.3 which is also nice. I should have qualified here that I am COMPLETELY stock other than root. I have not "frozen" any apps., deleted any Samsung provided files, etc. and I have stock bootloader and stock recovery. This will likely NOT work if you have done any of those things.
Is there a flashable version of this? If not, can somebody make one? Thanks.
I'm running a custom rom and rollouts/updates from vendors freak me out because I don't trust not one of them. Knowing AT&T they have thrown in some bit of encryption that locks the bootloader. I understand this might not be the case this time but I do know none of them can be trusted.
Now if you excuse me, I'm 1/2 done with 1984 the book and my tin foil hat is making me itch.
Guys I need help I am stuck, I am using unlock att with tmobile, I check software update but it days interrupted, and I even tried with kies but it's not connecting at all, I tried 2 pcs.... Any help... What to do to update it... Please
Sent from my SAMSUNG-SGH-I317 using Tapatalk
rsalan said:
Is there a flashable version of this? If not, can somebody make one? Thanks.
Click to expand...
Click to collapse
The update has only been out for a few hours and we are asking for .zip files already ??
Sheesh...
Give the devs some time to pull it apart and clean it up...unless you would like Knox and a bootloader lock ??
gregsarg said:
the update has only been out for a few hours and we are asking for .zip files already ??
Sheesh...
Give the devs some time to pull it apart and clean it up...unless you would like knox and a bootloader lock ??
Click to expand...
Click to collapse
amen! Preach it my brethren
sent from my sgh-i317 using sky blue tapatalk
marckusdavis said:
I rooted using this method while still on 4.1.2 and it worked flawlessly.
I then paid for and installed SuperSU Pro and activated "Survival Mode"
Lastly, after the OTA update was COMPLETELY finished, I followed this simple procedure to get root back again.
SuperSU disables Knox for you on 4.3 which is also nice.
Click to expand...
Click to collapse
I have a few questions for you and/or those more in the know:
If I were to do this same thing, would I be able to flash a custom recovery (like TWRP) and/or flash custom ROM's/Kernels like I can already do now? One of my main concerns is that the stock kernel doesn't support Boeffla Sound, and that really makes for better audio on this device...might as well take full advantage of that Wolfson DAC...
I have to admit, it would be nice to be able to use pure AT&T stock, but rooted, as a base...this is why I loved the old CleanROM AT&T SE so much...
TIA for any guidance you can give on this.
Side note: after ODIN'ing back to 4.1.2 MA4, it says I have a 741MB update I can take....I'm sure that's this 4.3 update...Culpeper, VA here.
marckusdavis said:
I rooted using this method while still on 4.1.2 and it worked flawlessly.
I then paid for and installed SuperSU Pro and activated "Survival Mode"
Lastly, after the OTA update was COMPLETELY finished, I followed this simple procedure to get root back again.
SuperSU disables Knox for you on 4.3 which is also nice.
Click to expand...
Click to collapse
I did the same as marchusdavis but it resulted in a total disaster. After I downloaded the OTA update from AT&T I restarted my phone and it installed through CWM-Touch. At the end it asked if I wanted to ensure root was maintained and of course I said "yes" there (as well as through my SuperSU Pro Survival Mode). When it booted, my WiFi no longer works AND I lost root.
If anyway has any advice on how to get to a stock 4.3 from here please let me know!
Ugh, having trouble updating atm.
Goes up to 30%, then my phone reboots and says
"The update was interrupted" or something like that
On stock 4.1.2 rooted with stock recovery if anyone can help.
chris.l.naish said:
I have a few questions for you and/or those more in the know:
If I were to do this same thing, would I be able to flash a custom recovery (like TWRP) and/or flash custom ROM's/Kernels like I can already do now? One of my main concerns is that the stock kernel doesn't support Boeffla Sound, and that really makes for better audio on this device...might as well take full advantage of that Wolfson DAC...
I have to admit, it would be nice to be able to use pure AT&T stock, but rooted, as a base...this is why I loved the old CleanROM AT&T SE so much...
TIA for any guidance you can give on this.
Side note: after ODIN'ing back to 4.1.2 MA4, it says I have a 741MB update I can take....I'm sure that's this 4.3 update...Culpeper, VA here.
Click to expand...
Click to collapse
I don't believe so, as I am completely stock, bootloader and all. If you want to install other ROMs, you'd need to use a different method I believe. Likely downloading this update either via Kies or something else, and use ODIN to do everything. If you search around a bit on XDA, you'll probably find someone who has done it successfully and posted how. While I like custom ROMs, I have not had a need to use one yet on this device. However, if Samsung doesn't eventually give us Air Command, that might be enough to make me try it!
Is it possible to get the official update from the leak or do I have to downgrade to 4.1.2? I tried updating from the leak but it said it's the latest version.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Kitkat debrick images, created by me and @thenexusgeneration
Downloads
thenexusgeneration's image: https://mega.co.nz/#!8wlz0DKI!eavB0PVQAUbh7AGysI1gTlYiy3JFxuxqmeyuqZCdr18
My image: http://www.androidfilehost.com/?fid=23329332407591176
And mirrors for both are available here: http://cnexus.co/downloads/?device=DEBRICK&folder=ND8
Click to expand...
Click to collapse
These are for use in conjunction with this guide: http://forum.xda-developers.com/showthread.php?t=2369125
What exactly is a debrick image? Sorry, the only time I ever bricked a phone was on purpose si I've never used one.
Sent from my SPH-L710 using Tapatalk
Cnexus - any idea why yours is much smaller?
80mb vs 128mb
The 80mb file is about the same size as pre 4.3 images.
I just used a difference size when dumping it.
bigwillyg said:
What exactly is a debrick image? Sorry, the only time I ever bricked a phone was on purpose si I've never used one.
Click to expand...
Click to collapse
If the bootloader gets corrupted on the Galaxy SIII, you can flash the image file to an SD card and get the phone to boot from a fully bricked state (phone will not power on at all). The image file must match the current bootloader that is installed. There are other threads here for previous builds with the matching image files.
(If I got something a little wrong in terminology or concept, I'm sure someone will pop in and fix anything I got mixed up on explaining. )
You are all over this update man, I can't keep up lol.
{
"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"
}
bilgerryan said:
You are all over this update man, I can't keep up lol.
Click to expand...
Click to collapse
Him or me?
Unfortunately, my phone hard bricked during some testing of ND8 and now it's a paperweight as I haven't been able to get it back. I'm sure we'll see more of this going forward. I bet there were a few when 4.3 came along as well but we weren't around for that release here.
Looks like Jtag for this phone and I haven't decided what to do in the meantime to replace it; temporarily or permanently.
tdunham said:
Him or me?
Unfortunately, my phone hard bricked during some testing of ND8 and now it's a paperweight as I haven't been able to get it back. I'm sure we'll see more of this going forward. I bet there were a few when 4.3 came along as well but we weren't around for that release here.
Looks like Jtag for this phone and I haven't decided what to do in the meantime to replace it; temporarily or permanently.
Click to expand...
Click to collapse
I was talking about Boy Wonder, but that sucks dude (get another S3 if you can't fix it)
bilgerryan said:
I was talking about Boy Wonder, but that sucks dude (get another S3 if you can't fix it)
Click to expand...
Click to collapse
Ha. He hasn't put on his cape yet. It will be exciting around here once he does.
bilgerryan said:
I was talking about Boy Wonder, but that sucks dude (get another S3 if you can't fix it)
Click to expand...
Click to collapse
(TD drags thread offcourse LOL)
Heading out to buy a burner android phone while I wait.
Boost and Virgin are both coming out the with the S5 this month, it's tempting.
tdunham said:
(TD drags thread offcourse LOL)
Heading out to buy a burner android phone while I wait.
Boost and Virgin are both coming out the with the S5 this month, it's tempting.
Click to expand...
Click to collapse
I personally think I'm done with Sammy after this phone. Knox is too much of a pain in the arse and if they keep adding to it it's gonna eventually be locked down. I'm looking at the OnePlus or the LG G3 or the new M8, but not til Christmas or Tax Time.
bilgerryan said:
I personally think I'm done with Sammy after this phone. Knox is too much of a pain in the arse and if they keep adding to it it's gonna eventually be locked down. I'm looking at the OnePlus or the LG G3 or the new M8, but not til Christmas or Tax Time.
Click to expand...
Click to collapse
My thoughts exactly. The G3 or the Nexus 6 are on my radar. Will be looking at switching to T-Mobile as well.
enzoevo said:
My thoughts exactly. The G3 or the Nexus 6 are on my radar. Will be looking at switching to T-Mobile as well.
Click to expand...
Click to collapse
Yeah, I just wish I knew what their service was like in my area... I know they sucked like 5 years ago but nobody I know is on TMo anymore.
TD get the nexus 5 its a great phone and not to expensive. It would be great to have you over on it.
Destro warlock on WOW burnall
5FOOTER said:
TD get the nexus 5 its a great phone and not to expensive. It would be great to have you over on it.
Click to expand...
Click to collapse
Hey man, it's been a while.
I'm still weighing options and not sure if I want to change carriers yet too.
tdunham said:
Hey man, it's been a while.
I'm still weighing options and not sure if I want to change carriers yet too.
Click to expand...
Click to collapse
The good thing about the n5 it works with all carriers but Verizon.
Destro warlock on WOW burnall
tdunham said:
If the bootloader gets corrupted on the Galaxy SIII, you can flash the image file to an SD card and get the phone to boot from a fully bricked state (phone will not power on at all). The image file must match the current bootloader that is installed. There are other threads here for previous builds with the matching image files.
(If I got something a little wrong in terminology or concept, I'm sure someone will pop in and fix anything I got mixed up on explaining. )
Click to expand...
Click to collapse
I hard bricked my phone. How can I find out which bootloader was installed when it bricked? I have tried about every debrick image I can find with no success?
SniperDroid said:
I hard bricked my phone. How can I find out which bootloader was installed when it bricked? I have tried about every debrick image I can find with no success?
Click to expand...
Click to collapse
Tell me more, I just went through this. How did you do it and what is the phone doing/not doing now?
tdunham said:
Tell me more, I just went through this. How did you do it and what is the phone doing/not doing now?
Click to expand...
Click to collapse
Edit: Additionally, I had issues getting this image to flash in Windows. I had to flash it to SD in Ubuntu. If you can still read the SD in Windows, it didn't take the flash. If the card is unreadable in Windows then maybe it flashed ok but still no guarantees it will work if the bootloader partitions are corrupted like mine were.
tdunham said:
Tell me more, I just went through this. How did you do it and what is the phone doing/not doing now?
Click to expand...
Click to collapse
I was having connectivity issues so I flashed a new modem. Then, for some weird reason, I lost audio and had ZERO signal except wifi. I was advised to flash a TW rom to try and update PRL and activate the phone. I flashed Wicked Sensations, still no luck. So at that point, I was trying to flash back to non rooted using >>http://forum.xda-developers.com/showthread.php?t=1904099. Thats when it bricked. I don't blame anyone but myself. I didn't read the ENTIRE thread before flashing and it hard bricked. Won't power on, no recovery/download mode. Light comes on with battery pulled and plugged in to USB.
I have tried all the threads and has no luck. I bought a 16g class 10 sd card. Tried many different debrick files. Tried writing with win23 and Cygwin, nothing. I am thinking I may need a different image based on my bootloader, I just have no idea which it was at the time.
So, I'm on XDA what did you expect , I unlocked my bootloader and Android pay 'can't verify the software on my device'...
So I can't add my card.
No biggy, but has anyone else experienced the same?
Or am I just super unlucky? ????
nexusmaniac said:
So, I'm on XDA what did you expect , I unlocked my bootloader and Android pay 'can't verify the software on my device'...
So I can't add my card.
No biggy, but has anyone else experienced the same?
Or am I just super unlucky? ????
Click to expand...
Click to collapse
Yes, same with the 6P. Bootloader unlock breaks Android Pay.
B3501 said:
Yes, same with the 6P. Bootloader unlock breaks Android Pay.
Click to expand...
Click to collapse
Nah, my 6P is fine with an unlocked bootloader and a custom kernel and Android pay still works on that
nexusmaniac said:
Nah, my 6P is fine with an unlocked bootloader and a custom kernel and Android pay still works on that
Click to expand...
Click to collapse
On 7.1.1?!?!
Everyone else is reporting (including me) It doesn't.
B3501 said:
On 7.1.1?!?!
Click to expand...
Click to collapse
Ahhh... Nope, only on 7.0 - sorry I didn't realise you meant 7.1 haha
nexusmaniac said:
Nah, my 6P is fine with an unlocked bootloader and a custom kernel and Android pay still works on that
Click to expand...
Click to collapse
Are you using latest update of the app ,it got updated a few days ago and that definitely broke it I have a unlocked BL but have never rooted and get this
{
"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"
}
Sent from my Nexus 6P using XDA-Developers mobile app
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's nothing to do with 7.0 or 7.1 it's the update to the app that's done it,15/10/16 working fine in 7.0 unlocked BL no root,app updated on 18/10/16 no longer works in 7.0,or 7.1
Sent from my Nexus 6P using XDA-Developers mobile app
combat goofwing said:
Are you using latest update if the app ,it got updated a few days ago and that definitely broke it I have a unlocked BL but have never rooted and get this
Sent from my Nexus 6P using XDA-Developers mobile app
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's nothing to do with 7.0 or 7.1 it's the update to the app that's done it,15/19/16 working fine in 7.0 unlocked BL no root,app updated on 18/10/16 no longer works in 7.0,or 7.1
Click to expand...
Click to collapse
It must be based on Android version. My 6P has the same version of Pay as my XL but v the 6P still works and I can add cards to it.
It's a mixture of Bootloader and 7.1
Which sucks...
nexusmaniac said:
It must be based on Android version. My 6P has the same version of Pay as my XL but v the 6P still works and I can add cards to it.
It's a mixture of Bootloader and 7.1
Which sucks...
Click to expand...
Click to collapse
My 6P is unlocked but no root. Doesn't work. They definitely changed SafetyNet policies. It's not Android 7.1 the issue.
Sent from my Pixel XL using Tapatalk
sherlock5545 said:
My 6P is unlocked but no root. Doesn't work. They definitely changed SafetyNet policies. It's not Android 7.1 the issue.
Click to expand...
Click to collapse
Weird that it's not working for you but is for me on the 6P
Some sort of staged roll out perhaps?
nexusmaniac said:
Weird that it's not working for you but is for me on the 6P
Some sort of staged roll out perhaps?
Click to expand...
Click to collapse
It's probably a change that's still not rolled out to everyone. Unfortunately even my bank app relies on SafetyNET and disables some features. I guess no more custom kernels for me on the Pixel
Sent from my Pixel XL using Tapatalk
sherlock5545 said:
It's probably a change that's still not rolled out to everyone. Unfortunately even my bank app relies on SafetyNET and disables some features. I guess no more custom kernels for me on the Pixel
Click to expand...
Click to collapse
Yeah same here... I can't miss out on custom kernels though haha! ???? I'll just have to go back to the old fashioned way of contactless cards lol
nexusmaniac said:
Yeah same here... I can't miss out on custom kernels though haha! ???? I'll just have to go back to the old fashioned way of contactless cards lol
Click to expand...
Click to collapse
Does re-locking the bootloader get it working agian?
Relocking the bootloader will solve the AP issue.
chazall1 said:
Relocking the bootloader will solve the AP issue.
Click to expand...
Click to collapse
But, as I'm sure you know, if you have any custom software on your phone, I would not relock the bootloader until it is all back to stock.
chazall1 said:
Relocking the bootloader will solve the AP issue.
Click to expand...
Click to collapse
dbroer91884 said:
But, as I'm sure you know, if you have any custom software on your phone, I would not relock the bootloader until it is all back to stock.
Click to expand...
Click to collapse
Truthfully, I think I'll just wait for everyone else on the internet to complain, have Google revert the change and then carry on as normal haha
I'm sure there's some security risk involved. But that's for me to deal with, I can't blame Google because I unlocked my bootloader, that's just wrong.
nexusmaniac said:
Truthfully, I think I'll just wait for everyone else on the internet to complain, have Google revert the change and then carry on as normal haha
I'm sure there's some security risk involved. But that's for me to deal with, I can't blame Google because I unlocked my bootloader, that's just wrong.
Click to expand...
Click to collapse
It's more of a bank requirement than a Google requirement. I don't see that one getting rolled back. If they want more banks on board they need to comply to their security measures and show that the device data can't be compromised. The dev community, while vocal, is small. They want the system available to the masses.
Sent from my Pixel XL using Tapatalk
arcanexvi said:
It's more of a bank requirement than a Google requirement. I don't see that one getting rolled back. If they want more banks on board they need to comply to their security measures and show that the device data can't be compromised. The dev community, while vocal, is small. They want the system available to the masses.
Click to expand...
Click to collapse
It's funny that you mention that???? because my android pay (version 1.8) is now WORKING with my unlocked bootloader on the Pixel XL.
However, the rest of the internet is having very mixed results. Many not working, only a handful are. And even then, it seems like it might be a temporary glitch
So I am going to have to lock my bootloader, subsequently wiping my phone to use android pay again? D:
ZEnergy said:
So I am going to have to lock my bootloader, subsequently wiping my phone to use android pay again? D:
Click to expand...
Click to collapse
I don't think locking your boot loader wipes your phone. Only unlocking.
anyone find any fix/round about this problem?