Related
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.
Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults
UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.
Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app
@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices
I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...
My problem:
My galaxy s3 takes a LONG time to connect to AT&T when it boots up (over 5 minutes), and then only has Edge:2 network service.
How I got here:
Had 4.1.2 installed from AT&T
I rooted my phone with the "no countering tripping method" as described here: http://forum.xda-developers.com/showthread.php?t=1739426 to 4.1.1 this downgrade apparently made something not work, I kept getting errors, something about acore process failures.
I re-installed the stock 4.1.2 from AT&T
Still getting process failures
Read that clearing the contacts sometimes works, it didn't
Read that factory reset helps, it did
I still wanted a rooted phone, so this time I used this method: http://forum.xda-developers.com/showthread.php?t=1746665
Again processes started crashing
Again had to reset to factory
Now I noticed my phone wasn't working at all
Found that my IMEI was set to 0
Fixed that by following these instructions: http://forum.xda-developers.com/showthread.php?t=1804117
Note: the link to the sgs3.nv.gen.zip was bad, I found another here: http://forum.xda-developers.com/showthread.php?t=2335951 but my virus checker freaked out on it. I ran it on my kids pc, and it worked, don't know if I infected them or not, but I got my IMEI data back
Decided all this was too much hassle, so I reset my flash count to zero with this: http://forum.xda-developers.com/showthread.php?t=1494114
Reverted to stock 4.1.2 from AT&T and reset to factory
Still stuck on Edge:2
Found this thread: http://forum.xda-developers.com/showthread.php?t=2036891 my phone won't let me change my band preference, also under *#197328640#>SIM>CHECK NV it say "Band perf: Unexpected value"
Question:
Where do I go from here?
Thanks!
thabin said:
My problem:
My galaxy s3 takes a LONG time to connect to AT&T when it boots up (over 5 minutes), and then only has Edge:2 network service.
How I got here:
Had 4.1.2 installed from AT&T
I rooted my phone with the "no countering tripping method" as described here: http://forum.xda-developers.com/showthread.php?t=1739426 to 4.1.1 this downgrade apparently made something not work, I kept getting errors, something about acore process failures.
I re-installed the stock 4.1.2 from AT&T
Still getting process failures
Read that clearing the contacts sometimes works, it didn't
Read that factory reset helps, it did
I still wanted a rooted phone, so this time I used this method: http://forum.xda-developers.com/showthread.php?t=1746665
Again processes started crashing
Again had to reset to factory
Now I noticed my phone wasn't working at all
Found that my IMEI was set to 0
Fixed that by following these instructions: http://forum.xda-developers.com/showthread.php?t=1804117
Note: the link to the sgs3.nv.gen.zip was bad, I found another here: http://forum.xda-developers.com/showthread.php?t=2335951 but my virus checker freaked out on it. I ran it on my kids pc, and it worked, don't know if I infected them or not, but I got my IMEI data back
Decided all this was too much hassle, so I reset my flash count to zero with this: http://forum.xda-developers.com/showthread.php?t=1494114
Reverted to stock 4.1.2 from AT&T and reset to factory
Still stuck on Edge:2
Found this thread: http://forum.xda-developers.com/showthread.php?t=2036891 my phone won't let me change my band preference, also under *#197328640#>SIM>CHECK NV it say "Band perf: Unexpected value"
Question:
Where do I go from here?
Thanks!
Click to expand...
Click to collapse
This just happened to me too. I backed up my IMEI but lost it and had to get a new phone. I used QPST tool to restore my IMEI , which is located behind your battery. I did not work. There is another tool called NV Generate or something like that and still it did not work. I did not like spending the money for a warranty replacement, of course, so looked and tried hard for a fix. Since nothing worked I am also thinking that its possible I had a hardware problem, but I can say that an IMEI issue can be as bad as hardbricking, so proceed with caution and follow to a T. Good luck bro. I hope you can fix it. Let me know if you have a chance.
Edit: I missed the part about you using NV tool. I spoke with a bunch of Att help and a Samsung guy as well. Nobody knew about it. Mine was 5 freaking days past warranty. Still sick from that. If you are under warranty. Take it back.
I'm also having these issues..
Anyone have a true fix? I would go back to Full Stock, but have already tried that and still had the data issues. Something is hosed that needs to be fixed..
Fixed!!
I bought a new phone from AT&T, copied the nv config using the instructions here:
http://forum.xda-developers.com/showthread.php?t=1804117
Changed the IMEI to my phone's IMEI, and EUREKA! It works!
I'm attaching the file I used (with the IMEI blanked out, so be sure to fill in our own IMEI or this won't work for you, it is section 550, see http://forum.xda-developers.com/showthread.php?t=1804117 for more details).
I hope this helps others, and they don't have to pay the $35 restocking fee.
thabin said:
I bought a new phone from AT&T, copied the nv config using the instructions here:
http://forum.xda-developers.com/showthread.php?t=1804117
Changed the IMEI to my phone's IMEI, and EUREKA! It works!
I'm attaching the file I used (with the IMEI blanked out, so be sure to fill in our own IMEI or this won't work for you, it is section 550, see http://forum.xda-developers.com/showthread.php?t=1804117 for more details).
I hope this helps others, and they don't have to pay the $35 restocking fee.
Click to expand...
Click to collapse
This is exactly what I need! Thank you! My usb is corroded so I cannot connect usb and will have to load this manually. Could you please tell me the exact process you used to add your EMEI # to the file? I have opened the text file and went to section 550, but I do not know if i'm properly changing the number.
bweyadn said:
This is exactly what I need! Thank you! My usb is corroded so I cannot connect usb and will have to load this manually. Could you please tell me the exact process you used to add your EMEI # to the file? I have opened the text file and went to section 550, but I do not know if i'm properly changing the number.
Click to expand...
Click to collapse
I fixed the IMEI using the following instructions:
http://forum.xda-developers.com/showthread.php?t=1804117
The link on that page for the utility to generate a new IMEI didn't work, but I found another copy here:
http://forum.xda-developers.com/showthread.php?t=2335951
*WARNING* my virus checker freaked out about this file. I ran in on my kids machine (not mine) and it seemed to work fine, but I want you to be warned about the royal freakout my virus checker gave me.
thabin said:
I fixed the IMEI using the following instructions:
http://forum.xda-developers.com/showthread.php?t=1804117
The link on that page for the utility to generate a new IMEI didn't work, but I found another copy here:
http://forum.xda-developers.com/showthread.php?t=2335951
*WARNING* my virus checker freaked out about this file. I ran in on my kids machine (not mine) and it seemed to work fine, but I want you to be warned about the royal freakout my virus checker gave me.
Click to expand...
Click to collapse
I got almost just the identical problem... However, I checked my phone and my IMEI number is still intact... yet im stuck on EDGE
story was that I brought my rooted S3 from ATT (but not unlocked) to China 2 weeks ago hoping to use the phone on China Mobile's network (though knowing that China Mobile doesnt support the same band for 3g/4g as the US).
It wasn't til after inserting the sim that I realized I havent unlocked the phone yet... and since ATT won't give me the unlock code, I ended up trying to use the *#197328640# method, which was unsuccessful because I was still on ICS and this method requires Jellybean.
So in a hurry I used odin to upgrade to a jellybean version that apparently wasn't compatible with my I747.
After taking to a local shop, the dude repairing my phone was able to get the OS running again but it was weird in that even with an ATT sim card the phone would ask for an unlock code.
So finally after doing the re-flash of the official ATT I747 Jellybean rom, I was able to get into the *#197328640# menu and unlock my phone using
the second method mentioned in here: http://www.wikihow.com/Unlock-Samsung-Galaxy-Siii-(S3)
I was happy to get it to work with China Mobile's sim even though I can only use EDGE over there, but I also realize the dreafully long wait time for the phone to get a signal from power on.
After coming back to the States today and inserting my original ATT sim card, I noticed that it still takes a long time for the phone to get a signal after power on and after it acquires the signal from ATT, Im only getting signal (feels almost like the phone is stuck in the international setting...)
I have tried to reflash to z999 rom with cwm, tried to reflash the modem firmware, nothing is working.
My IMEI is still showing up in the "status" under about this phone, and its the same number as it appears in the back of the phone...
but for some reason I feel like this might have something to do with the fiddling of the secret code menu during my unlock oversea... since I had to go into the UMTS menu (which I believe is for EDGE)...
Since my IMEI isnt lost... anyone have any ideas what could have been the problem? This is getting beyond frustrating... would really appreciate the help!
Hello. i have a few posts from a while back about rooting my g4.
It turned out i had some weird beta version of the bootloader on it but i was able to update and root it still.
Well, now just a few months later. My phone just starts restarting over and over and will not boot past the lg logo.
After some research i found that most g4 made before September of 2015 had this problem.
So i contact customer "support" and they cant find my imei in there system. After talking to 3 different people one of them finally said that it shows my phone is a beta phone made in 2011 so they cant honor a warranty.
They said that they wouldn't even have the parts to fix it if i were to pay.
They told me to contact lg Korea but couldn't give me any help in contacting them.
Anyways. I came across the fix https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
But it appears that my phone model h810 (att) is not supported.
Also im pretty sure i was on marshmallow (honestly cant remember).
Is there any known fix for the h810 that anybody knows of?
And if i try this and it does not work, will it prevent me from being able to recover my data if someone does make a port for it?
I downloaded the zip but i dont want to flash a tot for another phone on here yet.
Any help would be appreciated.
Thanks.
I doubt it is an 2011 year model. Look at serial number behind battery. The first three numbers are manufacture date - for example 505. First number means year (5 - 2015), other two are month (05 - May). Maybe you might have provided Serial Number rather than IMEI for them.
As you still have locked bootloader, contact the place where you bought it as you should still have guarantee. Either they will take it to fix it or they should give you contacts for authorized repair.
myphonesbetter said:
Hello. i have a few posts from a while back about rooting my g4.
It turned out i had some weird beta version of the bootloader on it but i was able to update and root it still.
Well, now just a few months later. My phone just starts restarting over and over and will not boot past the lg logo.
After some research i found that most g4 made before September of 2015 had this problem.
So i contact customer "support" and they cant find my imei in there system. After talking to 3 different people one of them finally said that it shows my phone is a beta phone made in 2011 so they cant honor a warranty.
They said that they wouldn't even have the parts to fix it if i were to pay.
They told me to contact lg Korea but couldn't give me any help in contacting them.
Anyways. I came across the fix https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
But it appears that my phone model h810 (att) is not supported.
Also im pretty sure i was on marshmallow (honestly cant remember).
Is there any known fix for the h810 that anybody knows of?
And if i try this and it does not work, will it prevent me from being able to recover my data if someone does make a port for it?
I downloaded the zip but i dont want to flash a tot for another phone on here yet.
Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
to make the modded KDZ work on your at&t you need to renamed with hex program phone model. the kdz is for h815.... read this page..
http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734/page72
well you need to be on LP if you were on MM.
i guess youll still need to downgrade anyways. to be safe..
raptorddd said:
to make the modded KDZ work on your at&t you need to renamed with hex program phone model. the kdz is for h815.... read this page..
http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734/page72
well you need to be on LP if you were on MM.
i guess youll still need to downgrade anyways. to be safe..
Click to expand...
Click to collapse
Thanks ill have to look more into this. I think its saying all i have to do is find where it says h815 and changed it to h810.
Ill read more when i get a chance of course.
cesedy said:
I doubt it is an 2011 year model. Look at serial number behind battery. The first three numbers are manufacture date - for example 505. First number means year (5 - 2015), other two are month (05 - May). Maybe you might have provided Serial Number rather than IMEI for them.
As you still have locked bootloader, contact the place where you bought it as you should still have guarantee. Either they will take it to fix it or they should give you contacts for authorized repair.
Click to expand...
Click to collapse
My serial starts with 503, when i first got it it had software vo9e but i updated since then.
Im not sure where they came up with 2011 but it would make sense . maybe 2013 as a beta test phone.
myphonesbetter said:
Thanks ill have to look more into this. I think its saying all i have to do is find where it says h815 and changed it to h810.
Ill read more when i get a chance of course.
My serial starts with 503, when i first got it it had software vo9e but i updated since then.
Im not sure where they came up with 2011 but it would make sense . maybe 2013 as a beta test phone.
Click to expand...
Click to collapse
yeah sort of .. thats whati understand... once you do please let us know. as i have h811 and would like to have this just in case.. kncok on wood
FAIL
Yup. Now its really a brick. Dont try that.
Cant even boot into upgrade mode now.
It will vibrate as if it was turning on. but wont even show the lg screen.
Should have just put it in the oven. That made more sense.
myphonesbetter said:
FAIL
Yup. Now its really a brick. Dont try that.
Cant even boot into upgrade mode now.
It will vibrate as if it was turning on. but wont even show the lg screen.
Should have just put it in the oven. That made more sense.
Click to expand...
Click to collapse
its really late
but no its not dead yet lol
Freeze it and keep holding the buttons to boot unto download, and every vibration take the battery out and back in
Try lg up may work
*** The issue is resolved!!! Thanks to xda, the solution is provided in the link in the comments.***
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for their help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys . :good:
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Will replacing the motherboard get my phone back? Any kind of suggestion will be very much appreciated.
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
what is your model H790 or H791
16 or 32 GB?
DC_Knight said:
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Click to expand...
Click to collapse
Well, I don't get bootloops, my phone is just stuck at the Google screen and I can enter recovery mode (lying Android with red exclamation mark), from there I can enter Android recovery mode, where ADB sideload is available.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
Like I mentioned in point 5, I did exactly that as mentioned in this link.
Duckscreen said:
what is your model H790 or H791
16 or 32 GB?
Click to expand...
Click to collapse
It's H791, 32 GB.
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
jadu45 said:
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
Click to expand...
Click to collapse
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
EeZeEpEe said:
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
jadu45 said:
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
Click to expand...
Click to collapse
Ah my bad. TL;DR on my end.
Sent from my Nexus 5X using Tapatalk
Please say something about replacing the motherboard. It's very very pricey, so I want to be sure -_-
sounds like its hardware problem, contact seller to replace it. if not going to happen, then buy a new phone from a company that does have a dealer in your country to warrant. aside of camera, the specs of other phones at this price range are better
That thought is also roaming around my head, still Nexus is Nexus!
What's the price going for the 5X over there? It's as low as $280 here in the US which is easy better then it's original.
Sent from my Nexus 5X using Tapatalk
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Thanks for this, it looks interesting and I definitely didn't try that. I'm at office right now, I'll let you know after trying this.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
jadu45 said:
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
Click to expand...
Click to collapse
Goodluck, and let us know the result.. :fingers-crossed:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
ShishkaBerry said:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
Click to expand...
Click to collapse
Well, there is no authorized dealer here; I had to buy it from a local shop. So, there is no warranty!
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Both of you provided me the link. I don't know who you are, but I if I find you you guys are going to have a treat for sure. I literally cried when I got my phone back. Thank you guys. Thanks xda!
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go
GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:
I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...