I have superuser and artas CWM. I am running P769BK. I want to install a new ROM but want to avoid a security error again. Any tips?
I searched here and Google and found nothing. If I need to go to another thread I will.
Sent from my LG-P769 using Tapatalk 4 Beta
thchipmunk said:
I have superuser and artas CWM. I am running P769BK. I want to install a new ROM but want to avoid a security error again. Any tips?
I searched here and Google and found nothing. If I need to go to another thread I will.
Sent from my LG-P769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same here man i had unlocked the bootloader a while back before the JB upgrade was gonna try a Rom so decide to flash recovery and got the Sec error did all reflashed KDZ back on JB rooted and with artas recovery they say once you unlock the bootlader it stays that way, anyways did all the steps again to unlock, but boot normal and i have no way of checking... How can we know or check that the bootloader is unlocked??
Anyone????
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
elpuertorro said:
Same here man i had unlocked the bootloader a while back before the JB upgrade was gonna try a Rom so decide to flash recovery and got the Sec error did all reflashed KDZ back on JB rooted and with artas recovery they say once you unlock the bootlader it stays that way, anyways did all the steps again to unlock, but boot normal and i have no way of checking... How can we know or check that the bootloader is unlocked??
Anyone????
Click to expand...
Click to collapse
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Thanks! This are my unfortunate results.
I did not see the menu. I did the offline flash of V20_00
Nothing about unlocked bootloader
Yeah... I don't feel confident enough to try this again. Not yet.
Oh well. I'll wait longer until I feel better about what I am trying.
I have the P769BKGO GSM unlocked using Net10. So I think I won't be able to do the adb reboot oem-unlock trick. Other thoughts? Is flashing a different KDZ the only other route?
kuma82 said:
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Click to expand...
Click to collapse
kuma82 said:
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Click to expand...
Click to collapse
Thanks kuma the thing is i did this when i got the phone back in Jan so as you can see by now what ever i did is a bit of a blur, (short time mem loss you know lol) but i did recall doing it and have my folder set up for my phone, but to try to remember what or how and what tut i followed is the problem...but it's cool because i was looking for
V20b and since i could find one yesterday talking to carloswii for a copy asked if V20c would work as he didn't know figured i will try it and report back for the benefit of all....so that's next today
ps Kuma that's great advice but hey @thchipmunk don't be scared man is scary reading all but once you do it like 2 times it's all smooth plus with th KDZ offline method this cel comes back to life in no time so far as they have said you can't brick this phone even if you tried lol. to the rest stick with kuma's advice lol.
I am mostly just scared because it took me forever to get the KDZ to flash again. I kept getting that the USB was not connected to the phone so I wasn't able to ever complete the flash.
I do wonder though, if I would be able to unlock the bootloader. I see the directions say you need to wait 30+ minutes once connected, I assume this is some restriction in place on the actual phone with the SIM. However, I have an ATT SIM that I am using through NET10. Will that matter?
elpuertorro said:
Thanks kuma the thing is i did this when i got the phone back in Jan so as you can see by now what ever i did is a bit of a blur, (short time mem loss you know lol) but i did recall doing it and have my folder set up for my phone, but to try to remember what or how and what tut i followed is the problem...but it's cool because i was looking for
V20b and since i could find one yesterday talking to carloswii for a copy asked if V20c would work as he didn't know figured i will try it and report back for the benefit of all....so that's next today
ps Kuma that's great advice but hey @thchipmunk don't be scared man is scary reading all but once you do it like 2 times it's all smooth plus with th KDZ offline method this cel comes back to life in no time so far as they have said you can't brick this phone even if you tried lol. to the rest stick with kuma's advice lol.
Click to expand...
Click to collapse
thchipmunk said:
I am mostly just scared because it took me forever to get the KDZ to flash again. I kept getting that the USB was not connected to the phone so I wasn't able to ever complete the flash.
I do wonder though, if I would be able to unlock the bootloader. I see the directions say you need to wait 30+ minutes once connected, I assume this is some restriction in place on the actual phone with the SIM. However, I have an ATT SIM that I am using through NET10. Will that matter?
Click to expand...
Click to collapse
Been there , done that lol
By anychance when that happened to you
1 you were connecting the phone on lg software mode? that's what it should be and i'm sure you was
2 if you did, was it giving you errors about installing drivers failed?? that happens to me sometimes so i just restart the pc and then the phone get's recognized.
just remember sometimes we have to hit that skip that pops up when it's searching for drivers on the phone.... worse comes to worse reinstall the drivers for the phone hope this helps you out man.
Related
We can no longer unlock your bootloader with codes. Please do not ask me or ash for bootloader unlock codes. We can not help you.
This thread is now here for historical purposes representing times when people were free to do what they wanted with their devices. Fsck yourself with a rake, Verizon.
The bootloader has been unlocked. Let's get our freaking root on.
Disclaimer: Read through these instructions in their entirety. If these don't make sense to you, you do not need to be rooting your phone. Nobody here has the time required to teach you how to use cmd in Windows. We will not baby step you through how to use ClockworkMod Recovery. Root is not a mythical land with fairies and unicorns where nothing ever goes bad. If you don't know how to properly install a driver in Windows, you probably don't need an Android device to begin with, let alone a rooted one.
These instructions are intentionally left vague. Do your research on these terms. Understand what you are doing before you do it.
tldr: if you fsck your phone up, it's on you and only you.
Easy Way (YRMV!)
This is by far the easiest method. You will have to read between the lines here. I will not detail all the steps. Please record your experiences in this thread and let me know how it all goes! We're all still learning. This is basically copied from Bin4ry's CWMR Thread so thanks go to him! The easy steps below assume a lot of basic knowledge steps. Like unlocking the bootloader. If you're unsure of what to do, you probably shouldn't be doing it.
Download the CWM recovery from multiupload
Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
Copy this to your memory card and flash it with the booted recovery
Reboot and test root
Second Method: Advanced User Instructions
Unlock your bootloader. Check out Ash's thread: thread
Download Doom's all in one kernel from here
Use fastboot to "hot boot" the kernel: fastboot boot boot.img
Your phone may or may not boot. It doesn't matter. Let it be for a while, then power it off.
Doom's kernel will have rooted your stock system.
If You're On A Mac...
Or maybe just need some general help with some more detailed insturctions than are labeled here, check out the awesome post that Cubsfan3493 made for everyone. He's even got a downloadable PDF with pictures. Go give him some thanks at his post!
Is the R800x running 2.3.2 or 2.3.3. There's reports that Gingerbreak and alternatives are no longer working in 2.3.3.
It's running 2.3.2 right now. OTA updates say its up to date. I'm trying to figure out if I'm just having a generic issue with the breaks (like memory cards for example) or if Verizon maybe patched the exploit in their 2.3.2 build.
I have tried pretty much everything as well, I really hope some dev's start to pop their noises in here as I am a bit sad about the activity so far
I've been trying to root mine as well. The discussion I've been having is in this thread
http://forum.xda-developers.com/showthread.php?t=1097856
I'll keep an eye on both threads, but I have had no luck so far.
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
Yes i think verizon fixed the exploit gingerbreak uses before releasing the handset in the usa. When i was on build number 3.0.A.2.184 (uk xplay R800i) it rooted in like 30 seconds.
But in the new update 3.0.1.A.0.145 the exploit has been fixed. So all devices around the world have been left unrootable (for now ) the devs will figure away out.
I think the uk version 2.3.3 build 3.0.1.A.0.145 has been rooted (for unlocked bootladers) http://forum.xda-developers.com/showthread.php?t=1098736 So if your bootloader is unlocked soon it maybe possible. If its locked your stuck waiting with the rest of us for a rooting method on locked devices.
I saw you updated from another post, did you lose root access after the update?
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
build number - 3.0.E.2.89
A shame they didn't let us all have unlocked bootloaders.
axiomjunglist said:
I saw you updated from another post, did you lose root access after the update?
Click to expand...
Click to collapse
Yes i did. But the fixes added in the update are worth loosing root, for the time being . Being unable to root only applies to people with a locked bootloader. But im guessing devs from the arc and play forum are possibly looking for ways to root with a locked bootloader
Yeah I have the option to unlock my bootloader but don't want to just yet. I'll hold off on the update until a new version of gingerbreak arrives
Sent from my R800a using XDA App
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Mills00013 said:
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Click to expand...
Click to collapse
Wonder if you pop a pre-paid SIM in the slot (or try a friend's AT&T/T-Mobile SIM) and disabled the CDMA radio if you could get an IMEI to pop up on the keypad using *#06#. Might work? I have no clue... and you'd still have to send it to SE and hope they clear it.
I have a few SIMs here that I could try. Ill see what I come up with in a little bit. My gut is telling me that Verizon probably has the SIM slot firmware disabled. Thats only because they havn't officially mentioned it anywhere. In fact, the slot itself is actually hidden by a piece of plastic that you have to remove. One wouldnt have any idea it was there unless you were looking for it and even then you feel like you're breaking your phone to access it.
I also considered hooking it up to QPST to see if it would grab some serial numbers out of the device. Can anyone confirm if this is a qualcomm chip inside the phone?
I just tried a T-mo and an AT&T SIM, neither give me any sort of insertion notification or acknowledgement that they are present. So I'd say the slot is firmware disabled. But it should still have an IMEI, right? That would be programmed by Qualcomm out of the factory before Ericsson would have even installed it. Or am I taking crazy pills?
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
b00sted said:
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
Click to expand...
Click to collapse
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
ace518 said:
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
Click to expand...
Click to collapse
ya I just tried too and fail :/ #sadpanda
Neither the adb devices nor the fastboot devices codes have anything to do with the IMEI number.
Enviado desde mi R800i usando Tapatalk
I am willing to donate towards the first person that can get root and CWM on this!
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
tsouza said:
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I can wait for the release, but are they unlocking it with it. For sure?
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
tsouza said:
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
True. Very true.
magicriggs said:
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Click to expand...
Click to collapse
I think you might have returned the first 2 prematurely.
1st one probably could have factory reset or flashed a new sbf
2nd one was probably a fixable soft brick.
So I'd say you're safe, but up to you as there's always a risk.
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
magicriggs said:
I can wait for the release, but are they unlocking it with it. For sure?
Click to expand...
Click to collapse
not sure. i got a leaked 4.5.91 build, it's not unlocked (although early beta does). you still have to flash the pudding img yourself.
delect this post
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
magicriggs said:
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
Click to expand...
Click to collapse
hmm you are very unlucky then. You're the only one to hard brick from pudding. Probably advise you not to do anything with your phone.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
Click to expand...
Click to collapse
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
magicriggs said:
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
Click to expand...
Click to collapse
4.1.83 is a great point to unlock the bootloader. DO NOT install the 4.5.91 OTA udpate, too risky to hard brick if you flashed an sbf. Of course, you don't have to sbf back anymore, but I would steer way clear of that when there are perfectly good options available. Only use customized ones like Kenneth's or the CherryBlur ROM. More will start flowing soon.
So what your advising is not to even unlock it. All I really want is volume wake.
magicriggs said:
So what your advising is not to even unlock it. All I really want is volume wake.
Click to expand...
Click to collapse
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
OSNPA said:
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
Click to expand...
Click to collapse
Oh gotcha. Thanks for the info.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
i used update.zip ..did not flash back to 1.83...update.zip (blur 1.83 etc etc) was from leaked moto servers...i have new bootloader cause my andriod recovery is different...of course BL is locked....can i still unlock??
Hello i have just purchased this phone and i want to unlock the bootloader and install CWM and then Cyanogenmod but im finding it is very difficult to do so.. I have a few questions.. i have found some info on here but it says from tmobile 10g..which i am not.http://forum.xda-developers.com/showthread.php?t=2277639. Why is it so hard to do this and why after so much time has an easy fast method not been posted anywhere.It pisses me off they lock this thing up with all this built in bloat and make this so hard for users.. we are paying for the phones-therefore we should have 100 percent control over how they are used..
1. Is there any easier less risky way to unlock my bootloader and install cwm/cyanogenmod than this clusterfack way
(http://forum.xda-developers.com/showthread.php?t=2277639) for noobs ha
2. I rooted and flashed Cwm but i cannot get into it either with key combo or adb reboot recovery(brings me to android with open stomach screen, thats it..and i assume if i try to flash a zip like cyanogenmod IF I DID GET IN WITH A LOCKED bootloader it wouldnt work or id get security error)
i have busybox installed and phone is fully rooted..I need to avoid bricking and security errors at all costs
3.i need detailed step by step instructions for lg l9 p769 21d (locked bootloader) willing to offer a bit of cash to anyone who can help me successfully Unlock my Bootloader without any device brickage or security errors.
Update: Itried installing the artas test version on cwm with his installer and I now can get into cwm..the stable one wasn'tworking..
So now Ihave recovery just bbootloader locked preventing me from flashing any new ROMs...sighh
Update..I used cwm recovery installer by artas and I now can get into cwm
Device info
lg l9 p769 21d (android 4.1.2)
build number JZO54K
1.) Flash to 10G. T-Mobile doesn't matter, it still works with Wind. I've used Wind ROMs on my T-Mobile.
2.) That is the only way to unlock it, I'm sorry. Some conspiratist was trying to unlock it using a different method, but he rage quit when someone made fun of his website (lol).
3.) Really, it just takes luck. I haven't got it yet. But I try daily and it takes about 20 mins of work and 30-40 mins of waiting, so it's worth it. About to give up though lol.
LOL, I just realized you used numbers too. My numbers here don't correspond to your questions in that order. What a coincidence!
Sent from my LG-P769 using XDA Premium 4 mobile app
OK flash from 21d wind too T-Mobile 10g... Then I need to flash to Europe open 20b for 760...unlock the boot loader with mirrored image and messed up touch screen..then gain root..install cwm and fix the touch screen..
ARE YOU SURE I CANT GO FROM 21d to EUROPE 20b? Unlock bootloader and root and then Be done with it?And if so , Why not?
Anyone here unlocked boot loader of 769? BTW there is no working link to Europe open 20b kdz..I've been looking everywhere for an hour all links and downloads are broken/not working..anyone have the Europe open 20b for this process?
edit think i found the europe 20b
People say there's problems with it lol.. I haven't unlocked yet sadly. It's an annoying process and I feel that some devices can't be unlocked no matter what
Sent from my LG-P769 using XDA Premium 4 mobile app
Well it can be unlocked..but its a pain..day 1 and lg support tool will not install w admin priv/compatibility mode for xp sp 2/3.I'm on win 7
I take it this is why it won't flash the kdz and crashes the kdz installer..also shows phone not found in emergency mode but it is found in diag mode..what's with that?
Lol.. I'll try again tomorrow.. But I think I need to on a diff PC cause I've tried everything and it just gets stuck(lg support tool) at like 10 percent install..
What is the reason for going from 10g to 20b Europe and then back to 10g
Why not just stay on 20b fix the touchscreen etc and leave it..?
What issues if any would arise from flashing 20b Europe from 21d wind?
The unlock boot loader for.noobs 769 has files for SD including radio.zip..
Does the radio not work after flashing 20b Europe open? And if so how can I flash a zip on Europe 20b and unlock the boot loader without first installing radio.zip through a cwm?
The unlock boot loader for.noobs 769 has files for SD including radio.zip..
Does the radio not work after flashing 20b Europe open? And if so how can I flash a zip on Europe 20b and unlock the boot loader without first installing radio.zip through a cwm
I'd like to know what issues if any would arise from flashing to 20b from wind 21d?
What's the point of flashing from T-Mobile 10g to Europe 20b unlocking then flashing back to T-Mobile 10g?
Why not just leave it at 20b? Root 20b and be done?
matthewstice said:
The unlock boot loader for.noobs 769 has files for SD including radio.zip..
Does the radio not work after flashing 20b Europe open? And if so how can I flash a zip on Europe 20b and unlock the boot loader without first installing radio.zip through a cwm
I'd like to know what issues if any would arise from flashing to 20b from wind 21d?
What's the point of flashing from T-Mobile 10g to Europe 20b unlocking then flashing back to T-Mobile 10g?
Why not just leave it at 20b? Root 20b and be done?
Click to expand...
Click to collapse
Long story short, it won't work. Just do it lol.
Where are u in can?
Sent from my unlocked LG Optimus L9 running CM 10.1
isitbricked... I'm in Toronto...I read your posts today how u messed up then fixed your touch screen..and I also noticed your wind and u have ul your boot loader..was it from 20d as well ..? earlier version..?I wanna get this done
Ilxaot.
so do u have link to T-Mobile 10g..I'll flash to that then 20b then up..then flash back to 10g ?? or straight to cyanogemod..I just want cm in the en
d
matthewstice said:
Ilxaot.
so do u have link to T-Mobile 10g..I'll flash to that then 20b then up..then flash back to 10g ?? or straight to cyanogemod..I just want cm in the en
d
Click to expand...
Click to collapse
Go to the General section, and find the sticky (at the top) of the thread with the stock KDZ's by cmahendra. Find the ICS KDZ for P769, and download it.
matthewstice said:
Ilxaot.
so do u have link to T-Mobile 10g..I'll flash to that then 20b then up..then flash back to 10g ?? or straight to cyanogemod..I just want cm in the en
d
Click to expand...
Click to collapse
Get your T-Mobile STOCK here.
Get the V20B Euro Open here.
Good Luck and be patient.
do I have to flash back to 10g??? or I can go straight to cm 10.2..
what's the reason in the post everyone using this pattern
tmob10g-europe20b-tmob10g
why not flash to stock jb after Europe open? or cm 10.2 etc?
matthewstice said:
do I have to flash back to 10g??? or I can go straight to cm 10.2..
what's the reason in the post everyone using this pattern
tmob10g-europe20b-tmob10g
why not flash to stock jb after Europe open? or cm 10.2 etc?
Click to expand...
Click to collapse
You don't have to go to v10G after unlocking it... I don't know where you heard that lol.
please help
ive followed everything in the guide slowly and accurate to flash kdz with offline method..im flashing to 10g
it crashes every time after unpacking kdz ........dunno what to do..ive done exactly how it has said in guide step by step
windows 7.. http small server running... run as admin (sp3 mode) drivers installed(universal driver package) uninstalled /restart/reinstalled..
still program is crashing before it flashes kdz.. I included a screenshot of the logs
restart your pc and check yout host file and try a diffrent port...thats wat i did and its weird but it works
matthewstice said:
isitbricked... I'm in Toronto...I read your posts today how u messed up then fixed your touch screen..and I also noticed your wind and u have ul your boot loader..was it from 20d as well ..? earlier version..?I wanna get this done
Click to expand...
Click to collapse
20f is what I started with
Sent from my unlocked LG Optimus L9 running CM 10.1
I received phone as 10e (can anyone explain if this interferes with unlocking bootloada). I haven't tried unlocking yet but I think the time is upon me lol. ..I've been lurking these threads for months now. Are you t-mobile lg logo left side of phone?
Sent from my LG-P769 using xda app-developers app
Ilxaot said:
1.) Flash to 10G. T-Mobile doesn't matter, it still works with Wind. I've used Wind ROMs on my T-Mobile.
2.) That is the only way to unlock it, I'm sorry. Some conspiratist was trying to unlock it using a different method, but he rage quit when someone made fun of his website (lol).
3.) Really, it just takes luck. I haven't got it yet. But I try daily and it takes about 20 mins of work and 30-40 mins of waiting, so it's worth it. About to give up though lol.
LOL, I just realized you used numbers too. My numbers here don't correspond to your questions in that order. What a coincidence!
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have none either ....
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
matthewstice said:
The unlock boot loader for.noobs 769 has files for SD including radio.zip..
Does the radio not work after flashing 20b Europe open? And if so how can I flash a zip on Europe 20b and unlock the boot loader without first installing radio.zip through a cwm
I'd like to know what issues if any would arise from flashing to 20b from wind 21d?
What's the point of flashing from T-Mobile 10g to Europe 20b unlocking then flashing back to T-Mobile 10g?
Why not just leave it at 20b? Root 20b and be done?
Click to expand...
Click to collapse
You know i thought about this .... im gonna try it ...
Isitbricked...
After flashing to 10g then 20b did you then have a working signal for calls and data,,,or did.u only enabke wifi for the waiting.period,,,then unlock?
My issue.is that after flashing 20b i have no signal or data connection ...i also tried flashing the radio zip from putinsd card folder from.unlock.bootloader for.noobs p769 after flashing 20b...still no dice...
Hello everyone.
I had posted this in the Z forum, not realizing there was a Z Ultra forum. So I will just quote my previous post and add some info at the end:
Hello guys. New guy here with an Xperia Z Ultra phone.
I'm trying to load the Paranoid Android custom ROM.
Had a couple of questions:
1. I went thru Sony's instructions to unlock the bootloader. When I ran the fastboot -i 0x0fce oem unlock (e-mail code), the first error message I got was "FAILED - Remote - Command did not succeed". So I tried the exact command again, and then I got "FAILED - Remote: The device is already rooted".
I have searched high and low, and cannot seem to find any way to verify that the bootloader is now in fact unlocked.
2. Reading the instruction on how to install CWM/TWRP recovery menus, Every single list of instructions includes the following "This tutorial is only for Sony Xperia Z Ultra with 510 and 493 LTE firmware. Do not use it for any other carriers or variants"
Again, I have searched high and low to find a way to confirm what firmware version I have. All I know is I have the C6806 model, with the build number: 14.2.A.0.290
So can someone please help out a very confused guy here? I don't want to brick my phone by accident
So far it's still working ok
Click to expand...
Click to collapse
So far, after doing some major searching, I seem to have found that I currently have "290" Firmware, and that this Firmware is currently NOT able to be rooted. Is this correct?
Also, I still have not found a way to verify wether the boot loader actually did unlock or not. From what I have been able to read, it seems that if a proper boot loader was in fact, unlocked, it would have wiped all the data on my phone along with the SD card data.
So far, it seems everything on my phone is intact. So does this mean the boot loader unlock command failed for me? If so, why did I get the reply "this device is already rooted?"
I can't believe how difficult it is to root a damn Android phone! Jailbreaking an Apple device is 10 times easier!
First of all, it's usually pretty easy to root Android devices. In most cases it's only a simple click, but sony has done a good(?) job at fixing exploits, so it does it much harder for us.
Second, you can check if your bootloader is locked or unlocked by opening the dialer and insert *#*#7378423#*#*, go to "Service Info" and then "Configuration". If your bootloader is unlocked, it should say "Rooting status: Bootloader unlocked: Yes". It's easier to use Flashtool to unlock the bootloader if you're having issues using a terminal.
You'll find the rest here (including bootloader unlocking). If you need some help, ask in that thread.
If you aren't boot loader unlocked then "BACKUP TA PARTITION" from My Lord's guide @LordManhattan
Just incase you need to re-lock it for service
LordManhattan said:
First of all, it's usually pretty easy to root Android devices. In most cases it's only a simple click, but sony has done a good(?) job at fixing exploits, so it does it much harder for us.
Second, you can check if your bootloader is locked or unlocked by opening the dialer and insert *#*#7378423#*#*, go to "Service Info" and then "Configuration". If your bootloader is unlocked, it should say "Rooting status: Bootloader unlocked: Yes". It's easier to use Flashtool to unlock the bootloader if you're having issues using a terminal.
You'll find the rest here (including bootloader unlocking). If you need some help, ask in that thread.
Click to expand...
Click to collapse
First of all it' pretty damn complicated and unrewarding to root a Sony device. Not all android but Sony definately. We checked, bootloader is unlockable. We unlocked and relocked bootloader prevoiusly because there is no robust, easy-to-install ROM for ZU. But time to time we try to root it.
Now, the question is the same: what should we do to re-unlock the bootloader if anything is OK, but flashtool says "Command did not succeed" for the first time and "Device is already rooted" for subsequent times at unlocking?
Please write some advice about the question, not about TA backup and your success. Thx!
Champdor said:
First of all it' pretty damn complicated and unrewarding to root a Sony device. Not all android but Sony definately. We checked, bootloader is unlockable. We unlocked and relocked bootloader prevoiusly because there is no robust, easy-to-install ROM for ZU. But time to time we try to root it.
Now, the question is the same: what should we do to re-unlock the bootloader if anything is OK, but flashtool says "Command did not succeed" for the first time and "Device is already rooted" for subsequent times at unlocking?
Please write some advice about the question, not about TA backup and your success. Thx!
Click to expand...
Click to collapse
Oh, are we demanding help now?
Bootloader unlocking is a straight forward process. I've had a couple of strange errors in Flashtool while trying to unlock the bootloader, but just close Flashtool and try again. Also be sure to be on the latest version of Flashtool.
LordManhattan said:
Oh, are we demanding help now?
Bootloader unlocking is a straight forward process. I've had a couple of strange errors in Flashtool while trying to unlock the bootloader, but just close Flashtool and try again. Also be sure to be on the latest version of Flashtool.
Click to expand...
Click to collapse
No sir, not at all. I wrote please, no demanding. Well yes, I'm a bit picky because there were no answer and I usually find some on XDA. Besides I used custom roms on Samsung devices for years (SGS2, SGN, SGN2) and I was disapponted when I bought my XZU that there are very few roms and I couldn't use them (I managed with very hard work to go back to stock in 9 hours after unsuccesful flashing).
So there is some basic problem every time. Like trying to root but cannot re-unlock because of some mysterious errors with no solutions.
Enough of my problems, your answer is much appreciated, will try to re-unlock some time. Thx!
Champdor
Champdor said:
No sir, not at all. I wrote please, no demanding. Well yes, I'm a bit picky because there were no answer and I usually find some on XDA. Besides I used custom roms on Samsung devices for years (SGS2, SGN, SGN2) and I was disapponted when I bought my XZU that there are very few roms and I couldn't use them (I managed with very hard work to go back to stock in 9 hours after unsuccesful flashing).
So there is some basic problem every time. Like trying to root but cannot re-unlock because of some mysterious errors with no solutions.
Enough of my problems, your answer is much appreciated, will try to re-unlock some time. Thx!
Champdor
Click to expand...
Click to collapse
Oh, i get that. I came from Samsung myself, and this is my first Sony device ever, so I've had some issues myself. I've gotten the same error message(s) as you before, and i think i restarted Flashtool and rebooted my Ultra and it was back to normal again - i think, but it "fixed itself" after trying a couple of times, so don't give up. It's also important to always be on the latest version of Flashtool.
It would also help us if you could tell us what you're trying to achieve, so you don't end up spending 9 hours on something that takes 5 minutes
@Champdor
From what I can make out you have never managed root your phone or back up the TA. If the latter is true then there is very little point in relocking the bootloader.
Yes the process is a little harder than Samsung, but the last device I rooted was a ZTE, and that was even harder to root and flash from what I can remember (yes this is my first Sony device as well, and I will buy another...)
Take you time and read the stickies that we have written and all should go well. Don't be afraid to ask (intelligent) questions if you get stuck, and read some more
HELP!
i am in same situation as OP
in past, i unlocked the bootloader then i relocked.
now I like to re-unlock. but I get same errors (i.e. 'command did not suceed' or 'device is already rooted')
i check service menu and it says 'bootloader unlock allowed: yes' meaning its not unlocked yet.
i use latest flashtool and try to unlock but i get error
can any expert help!?
thanks for your help
corrado85 said:
HELP!
i am in same situation as OP
in past, i unlocked the bootloader then i relocked.
now I like to re-unlock. but I get same errors (i.e. 'command did not suceed' or 'device is already rooted')
i check service menu and it says 'bootloader unlock allowed: yes' meaning its not unlocked yet.
i use latest flashtool and try to unlock but i get error
can any expert help!?
thanks for your help
Click to expand...
Click to collapse
I have not had this error so have not tested this, but what happens if you flash a full FTF and wipe everything then try to unlock the BL?
And remember that you can take a backup of the unlocked BL (re member to name it as such) and just flash that to unlock again. Doing it this way you don't get the format that happens when using the unlock code.
I followed this post to downgrade, root, i use Backup TA v9.10 to backup DRM Keys, use Flashtool 0.9.14.0 to unlock Bootloader, then to flash other Rom's (stock and customs), came back to Stock Rom .681, relock the Bootloader with Flastool 0.9.15.0 flashed the last .757 and unlock the Bootloader again with no kind of problems using Flashtool 0.9.15.0....
blueether said:
I have not had this error so have not tested this, but what happens if you flash a full FTF and wipe everything then try to unlock the BL?
And remember that you can take a backup of the unlocked BL (re member to name it as such) and just flash that to unlock again. Doing it this way you don't get the format that happens when using the unlock code.
Click to expand...
Click to collapse
I just flashed C6802 .757 FW using flashtool, and i get same issue
is there a tutorial about backup of the unlocked BL? assuming you meant I have to have own device backup..
this is so confusing at the end :crying:
corrado85 said:
I just flashed C6802 .757 FW using flashtool, and i get same issue
Click to expand...
Click to collapse
I dont know what else to suggest other than rebooting every thing and reinstalling all the drivers
is there a tutorial about backup of the unlocked BL? assuming you meant I have to have own device backup..
this is so confusing at the end :crying:
Click to expand...
Click to collapse
You just back it up as you would for a locked BL. Just remember to make sure you name them well so you know which is the locked one and the unlocked one.
NEVER use a TA backup from another phone, you WILL HARD BRICK IT
Lc1975 said:
I followed this post to downgrade, root, i use Backup TA v9.10 to backup DRM Keys, use Flashtool 0.9.14.0 to unlock Bootloader, then to flash other Rom's (stock and customs), came back to Stock Rom .681, relock the Bootloader with Flastool 0.9.15.0 flashed the last .757 and unlock the Bootloader again with no kind of problems using Flashtool 0.9.15.0....
Click to expand...
Click to collapse
problem is i get message 'device already rooted' when i enter my bootloader key using flashtool as well
---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------
blueether said:
I dont know what else to suggest other than rebooting every thing and reinstalling all the drivers
You just back it up as you would for a locked BL. Just remember to make sure you name them well so you know which is the locked one and the unlocked one.
NEVER use a TA backup from another phone, you WILL HARD BRICK IT
Click to expand...
Click to collapse
ahh ok, in that case, i do not have a backed up unlocked bootloader rom
corrado85 said:
problem is i get message 'device already rooted' when i enter my bootloader key using flashtool as well
---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------
ahh ok, in that case, i do not have a backed up unlocked bootloader rom
Click to expand...
Click to collapse
Did you tried:
*#*#SERVICE#*#*
and confirm that the Bootloader is unlock?
Lc1975 said:
Did you tried:
*#*#SERVICE#*#*
and confirm that the Bootloader is unlock?
Click to expand...
Click to collapse
It states
Rooting status
Bootloader unlocked allowed:Yes
corrado85 said:
It states
Rooting status
Bootloader unlocked allowed:Yes
Click to expand...
Click to collapse
When you try to unlock the Bootloader.. What button or icon do you click?
The one who has the padlock or BLU?
Lc1975 said:
When you try to unlock the Bootloader.. What button or icon do you click?
The one who has the padlock or BLU?
Click to expand...
Click to collapse
I choose which states 'BLU'
actually I do get the option to click on padlock but i dont know what to do there
corrado85 said:
I choose which states 'BLU'
actually I do get the option to click on padlock but i dont know what to do there
Click to expand...
Click to collapse
The padlock is to root the device..
Sorry but i can't help you much more then this... I don't have much knowledge to go foward...
Try to start from scratch..
Downgrade...
Root...
Try to unlock the Bootloader
And update to the latest...
root didnt work
Hello , i want to root my phone z ultra 6833 .757 i watch this video youtube . com/watch?v=uFSeSe8gQOY
i unlock bootloader after this install 757.img by flashtool so i can open recovery but after this i didnt find the same file he run i try run supersu.zip but the phone havent rooted plz what the problem
Made a bit of a boob here. I was upgrading my firmware version 10v to the new January firmware using LGUP. Unfortunately i forgot to click Upgrade, and so by accident ran the refurbish command.
The 'upgrade' ran through OK, and it boots, but I lost root/twrp (im on H930).
When I tried to bung TWRP back on, I cant get the fastboot boot twrp.img command to work (sorry if syntax is wrong while typijg this message) - that command just reboots the phone but it sits of the LG v30 loading screen.
Ive noticed that the fastboot screen tells me to make sure I flip the OEM Unlock switch in Dev options (a blue message). However, that setting is greyed out. Running the getvar command says I am unlocked though, as does re-running the unlock command.
So im confused. Im guessing i cant install TWRP as fastboot mode thinks im locked?
Any ideas??
Sent from my LG-H930 using Tapatalk
It may say you are unlocked, but you are not. Once you are rooted, you should never flash a KDZ -- especially if you are unlocked via the unlock.bin method. If you want to upgrade, flash the firmware via TWRP.
But you are in this situation now.... so, have you tried flashing unlock.bin again?
-- Brian
runningnak3d said:
It may say you are unlocked, but you are not. Once you are rooted, you should never flash a KDZ -- especially if you are unlocked via the unlock.bin method. If you want to upgrade, flash the firmware via TWRP.
But you are in this situation now.... so, have you tried flashing unlock.bin again?
-- Brian
Click to expand...
Click to collapse
Hi Brian
Yeah, if i try flash the unlock.bin file again i get an error telling me im already unlocked (or words to that affect...im away from my PC so can't see the exact message)
Sent from my LG-H930 using Tapatalk
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
runningnak3d said:
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
Click to expand...
Click to collapse
Awesome Brian, thanks loads for the help. I'll PM you the Zip as soon as ive done it
Sent from my LG-H930 using Tapatalk
runningnak3d said:
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
Click to expand...
Click to collapse
Brian, quick question. Would i need to be rooted to create the dumps....?
Sent from my LG-H930 using Tapatalk
Nope.
-- Brian
thenoble06 said:
Any ideas??
Click to expand...
Click to collapse
Since you flashed a fully stock rom, can you try to do 'fastboot oem lock' and then check developer settings if OEM unlocking became active so you can flip it to ON again?
padmanek said:
Since you flashed a fully stock rom, can you try to do 'fastboot oem lock' and then check developer settings if OEM unlocking became active so you can flip it to ON again?
Click to expand...
Click to collapse
Ahhh cool, that did it. Re-locked, flashed latest KDZ with LG UP and then relocked, installed Recovery and re-rooted.
Jobs a good un!
I'll stay away from KDZ files now and just update/upgrade via TWRP (that's right yeah)?
Thanks both for your help!!
Sent from my LG-H930 using Tapatalk