Database Info

[Q] Rooting without downgrade if you have Jelly Bean

Hi!
I hope some someone can explain me:
Why is it obviously so difficult (or not possible?) to root the XT925 Razr HD without downgrade to ICS if you are already on JellyBean? I read a lot of things and there everytime the poeple wrote about the VoodooKeeper thing and the downgrade.

wemsinho said:
Hi!
I hope some someone can explain me:
Why is it obviously so difficult (or not possible?) to root the XT925 Razr HD without downgrade to ICS if you are already on JellyBean? I read a lot of things and there everytime the poeple wrote about the VoodooKeeper thing and the downgrade.
Click to expand...
Click to collapse
I am also quite interested in this this! In particular, as going back ICS will require that i unlock the bootlock and loose the warranty (at least that is my understanding). I do not wish to sacrafice warranty "just" to get root, something that was very easily done on my old xperia (with or without locked bootlock)
I still love my razr hd (xt925) for lots of other reasons though!

You don't have to unlock or loose warranty to go back to ICS. You do however have to root.
IMO, their is not JB exploit so far because it is so easy to roll back to ICS root.... then use root keeper to hold root thru the update. So no real reason for anyone to work on a root exploit yet. Takes maybe 10-15 minutes if that.

clintonroche said:
You don't have to unlock or loose warranty to go back to ICS. You do however have to root.
IMO, their is not JB exploit so far because it is so easy to roll back to ICS root.... then use root keeper to hold root thru the update. So no real reason for anyone to work on a root exploit yet. Takes maybe 10-15 minutes if that.
Click to expand...
Click to collapse
I just got a XT295 from germany just to fix the damned ril issues ive been having in my root call management apps. But it was running 4.1.2 out of the box, with a locked boot.
Am i right in assuming theres a way to root it with that RSDLite tool? I have never owned a moto device, so know nothing about this tool or how it works with a locked bootloader.

clintonroche said:
You don't have to unlock or loose warranty to go back to ICS. You do however have to root.
IMO, their is not JB exploit so far because it is so easy to roll back to ICS root.... then use root keeper to hold root thru the update. So no real reason for anyone to work on a root exploit yet. Takes maybe 10-15 minutes if that.
Click to expand...
Click to collapse
In don't really understand your statement. If you're unrooted on JB, in order to root you definitely have to rollback to ICS... and this requires an unlocked bootloader.
So if you're unrooted, with a locked bootloader, on JB, there is no way you can rollback to ICS if you don't wish to void your warranty by unlocking the bootloader ?? (once you're on ICS, root/voodo/ota upgrade is good to go)
Or maybe I have missed something and there is a way to downgrade to ICS with a locked bootloader ??? If so, i'd be *very* interested...

There is a way to downgrade with locked bootloader. Use Matt's tool.
Enviado de meu DROID RAZR HD usando o Tapatalk 2

I've tried already, but it doesn't work. T my understanding (and after reading a bit the thread dedicated to Matt's tool) I'd say you must have an unlocked BL to downgrade...

CoinCoin88 said:
I've tried already, but it doesn't work. T my understanding (and after reading a bit the thread dedicated to Matt's tool) I'd say you must have an unlocked BL to downgrade...
Click to expand...
Click to collapse
It is definitely not necessary on the 926 Consumer Edition as of course it is not currently possible to unlock the BL at this time. It may be different on the 925, but u doubt it.
Sent from my DROID RAZR HD using Tapatalk 2

Regardless of what you do your gonna void your warranty no matter what,if its a simple root or flash anything your voiding it,and you don't need to have an unlocked bootloader to downgrade back to ics

rickt1152 said:
It is definitely not necessary on the 926 Consumer Edition as of course it is not currently possible to unlock the BL at this time. It may be different on the 925, but u doubt it.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Ok, so p-maybe the problem is not the locked BL... but the fact that probably many people here aren't using the Verizon 925 but the "international" XT-925 model (which is disclamed as "not supported" in Matt's tool's thread).
I'd definitely be willing to give it a try again to downgrade it, but IIRC the last time I tried, option 1 started well then ended up with some errors (can't actually remember what was written). Took like 5 minutes, a bunch of errors here and there on prompt, rebooted the phone, and was still on 4.1.1.
So either this is the "international XT-925 not supported thing", or there's somethign I did wrong (like, extracting a bug report with the key combination or i-don't-now-what-else). Just to be sure we're on the same page, are we all talking about the international XT-925 ? Or is this where we are misunderstanding ??

I'm using xt926 maxx and downgrade many time with no trouble,
Hope my information is helpful ^^
Sent from my DROID RAZR HD using xda app-developers app

unlocked or rooted?
HELP!
I have gone around with a motorola RAZR M only to be told by motorola that it couldn't be rooted. I have several posts in the general discussions area of the RAZR M. Motorola told me that I HAD to have a developer edition phone to unlock the bootloader. I did that. They told me that with the bootloader unlocked it would be considered rooted. That isn't true. I think I was misled or maybe uninformed. The phone that I got from them is a XT926dev. I voided the warranty, unlocked the bootloader and nothing has really changed. All the root dependent apps say it isn't rooted.
What am I not doing that completes the root? I have root checker and it's sole requirement for root appears to be whether or not superuser and su.binary are installed in the root sectors. Can anybody lead me into the light? I'm scared of the dark.
JAB©

jabeth407 said:
HELP!
I have gone around with a motorola RAZR M only to be told by motorola that it couldn't be rooted. I have several posts in the general discussions area of the RAZR M. Motorola told me that I HAD to have a developer edition phone to unlock the bootloader. I did that. They told me that with the bootloader unlocked it would be considered rooted. That isn't true. I think I was misled or maybe uninformed. The phone that I got from them is a XT926dev. I voided the warranty, unlocked the bootloader and nothing has really changed. All the root dependent apps say it isn't rooted.
What am I not doing that completes the root? I have root checker and it's sole requirement for root appears to be whether or not superuser and su.binary are installed in the root sectors. Can anybody lead me into the light? I'm scared of the dark.
JAB©
Click to expand...
Click to collapse
You maybe have unlocked the Bootloader, but that does not necessary means, you are rooted.
First think on which Firmware is you XT926, is it on 4.0.4 or is it on 4.1.2
If you are on 4.0.4, read this Thread.
http://forum.xda-developers.com/showthread.php?t=1943851
If you are on 4.1.2 and your bootloader really is unlocked, read this:
http://forum.xda-developers.com/showthread.php?t=2118483
If you are on 4.1.2 and your phone is VERIZON xt926 and your bootloader is locked:
Try Matts Tool to downgrade. Then do the first step i mentioned
Next time please inform yourself about the things you want to do. This should be the first thing. If you dont know the difference between an unlocked bootloader and root access, you should propably not try to mess with these kind of things.
Maybe Motorola Service Workers aren't the right people to ask about stuff like that...
But well hope i helped you out of the dark, greetz Esok

If you have the XT925 RAZR HD and don't want to downgrade, for now you have to unlock your BL, flash CWM and flash SuperSU through CWM (you can find the flashable zip on the chainfire.eu). Or you could wait for an exploit to come.
Sent from my XT925

saloums7 said:
If you have the XT925 RAZR HD and don't want to downgrade, for now you have to unlock your BL, flash CWM and flash SuperSU through CWM (you can find the flashable zip on the chainfire.eu). Or you could wait for an exploit to come.
Sent from my XT925
Click to expand...
Click to collapse
And we're back to this: is it actually possible to downgrade a XT925 with Matt's tool ?????

I downgraded straight with RSD... but my BL is unlocked don't know if it makes a difference
Sent from my XT925

CoinCoin88 said:
And we're back to this: is it actually possible to downgrade a XT925 with Matt's tool ?????
Click to expand...
Click to collapse
No. Matt's tool is intended for the XT926 only.
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2

esok44 said:
You maybe have unlocked the Bootloader, but that does not necessary means, you are rooted.
First think on which Firmware is you XT926, is it on 4.0.4 or is it on 4.1.2
If you are on 4.0.4, read this Thread.
http://forum.xda-developers.com/showthread.php?t=1943851
If you are on 4.1.2 and your bootloader really is unlocked, read this:
http://forum.xda-developers.com/showthread.php?t=2118483
If you are on 4.1.2 and your phone is VERIZON xt926 and your bootloader is locked:
Try Matts Tool to downgrade. Then do the first step i mentioned
Next time please inform yourself about the things you want to do. This should be the first thing. If you dont know the difference between an unlocked bootloader and root access, you should propably not try to mess with these kind of things.
Maybe Motorola Service Workers aren't the right people to ask about stuff like that...
But well hope i helped you out of the dark, greetz Esok
Click to expand...
Click to collapse
Thanks for the links, I'll try it. I tried to get information about what I'm doing from the manufacturer. You can see where that has gotten me. I have tried others too. It is a simple thing to share & part with knowledge. I still haven't gotten anybody to set me straight on any differences between unlocked boot & root. So, this is my attempt at informing myself.
---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------
esok44 said:
First think on which Firmware is you XT926, is it on 4.0.4 or is it on 4.1.2
But well hope i helped you out of the dark, greetz Esok
Click to expand...
Click to collapse
Mine is 4.1.1, as usual I have fallen between the cracks!

jabeth407 said:
Thanks for the links, I'll try it. I tried to get information about what I'm doing from the manufacturer. You can see where that has gotten me. I have tried others too. It is a simple thing to share & part with knowledge. I still haven't gotten anybody to set me straight on any differences between unlocked boot & root. So, this is my attempt at informing myself.
---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------
Mine is 4.1.1, as usual I have fallen between the cracks!
Click to expand...
Click to collapse
Well, then try the method, using matts tool to downgrade and then using the normal 4.0.4 method to root
Should be the easiest method
before downgrading, make sure that you save all relevant things, like pictures, etc on your external sd-card, they will get lost with the downgrade, i think
Good luck Esok

esok44 said:
You maybe have unlocked the Bootloader, but that does not necessary means, you are rooted.
Next time please inform yourself about the things you want to do. This should be the first thing. If you dont know the difference between an unlocked bootloader and root access, you should propably not try to mess with these kind of things.
Maybe Motorola Service Workers aren't the right people to ask about stuff like that...
But well hope i helped you out of the dark, greetz Esok
Click to expand...
Click to collapse
Hey man, I'm not totally useless. I know the bootloader is unlocked. I did manage to get that far. Give me a break, I'm used to my tandy 1000, cassette tape deck, b&w tv. Nice simple basic languages. Ha, ha, ha.

[Q] phone wont boot after 4.4 update PLEASE HELP

This morning i finally relented and installed the 4.4 update (kitkat?) on my droid razr maxx hd. now im stuck at the red M motorola splash screen thing. is there any way i can fix this? I went to verizon and they wouldent do anything for me. I need my phone for work every day so help is greatly appreciated. i also tried the power volume down to restore factory settings or whatever but it just goes to the M screen forever. the only thing that DOES come up from those menus is ap fast boot. not sure if thats helpful or not. PS im new to this stuff so noob friendly responses please!

Were you rooted at all? Did you modify your system in any way (froze or uninstalled stock apps)? If so, that's why.
Go here to get yourself back in shape:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/

f
i used a one click root method and always used voodoo ota rootkeeper other than that i havent changed anything else.
i will try this link and post back in a couple hours i have to go take care of a few things. thank you for the quick response.

KiraTheSavior said:
i used a one click root method and always used voodoo ota rootkeeper other than that i havent changed anything else
Click to expand...
Click to collapse
That's your issue. You can't do an OTA after you've rooted since the OTA does a verification to ensure the system isn't modified in any way.
Go to the link I posted in my previous reply to you to get yourself updated to Kit Kat and then unlock you bootloader if you haven't since the KK update put the bootloader exploit back in.

ok
iBolski said:
That's your issue. You can't do an OTA after you've rooted since the OTA does a verification to ensure the system isn't modified in any way.
Go to the link I posted in my previous reply to you to get yourself updated to Kit Kat and then unlock you bootloader if you haven't since the KK update put the bootloader exploit back in.
Click to expand...
Click to collapse
attempting it now. will post results.

it worked!
KiraTheSavior said:
attempting it now. will post results.
Click to expand...
Click to collapse
it worked im on kitkat and everythings great! thank you so much for the help! it was really easy with the step by step you linked. now i think ill try rooting and unlocking, if i mess it up i can always flash it like i just did and fix it right?
could you link me to the root/unlock tutorial for my phone? sorry im noob XD

Just to be sure, you didn't update to the latest soak that just came out, correct? You are on the previous Kit Kat OTA right?
If you haven't applied the latest soak (183.46.10.XT926), then you are golden and can unlock. ONLY apply the soak update AFTER you've unlocked your bootloader.

no
iBolski said:
Just to be sure, you didn't update to the latest soak that just came out, correct? You are on the previous Kit Kat OTA right?
If you haven't applied the latest soak (183.46.10.XT926), then you are golden and can unlock. ONLY apply the soak update AFTER you've unlocked your bootloader.
Click to expand...
Click to collapse
no my system information says 183.46.10 i dont know what a soak update is i just clicked install on that annoying install 4.4 update message ive had for weeks (which broke my phone) other than that i havent done anything. is my phone rootable?

KiraTheSavior said:
no my system information says 183.46.10 i dont know what a soak update is i just clicked install on that annoying install 4.4 update message ive had for weeks (which broke my phone) other than that i havent done anything. is my phone rootable?
Click to expand...
Click to collapse
You should have just ignored the update until after you unlocked the phone. The link I sent you to was meant to get you updated to KK before the 183.46.10 update. The previous KK update allowed you to unlock your bootloader. Now, that is no longer possible. There is no way to downgrade to a previous version. Once the ability to unlock has been patched, you cannot go back and try to unlock it.
You can still root the phone, though. Search for towelroot and you can install that and run it to root your device.
One thing you could try is once you've rooted, try running Motopocalypse to see if it will unlock your bootloader. Either it will or it won't. It won't hurt your phone in any way or brick it.

lame...
iBolski said:
It's rootable but it's not unlockable anymore. You have lost the ability to unlock the bootloader. There is no way to downgrade to a previous version. Once the ability to unlock has been patched, you cannot go back and try to unlock it.
Search for towelroot and you can install that and run it to root your device.
Click to expand...
Click to collapse
figures. thats me always a day late and a dollar short.

KiraTheSavior said:
figures. thats me always a day late and a dollar short.
Click to expand...
Click to collapse
WHOA! WHOA! WHOA! My bad. You should be okay to unlock!
Please go here and attempt it -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
Get Towelroot and run it. This should root your phone -> http://www.towelroot.com/
Next, get the motopocalypse apk from here -> http://forum.xda-developers.com/showpost.php?p=53428225&postcount=22
Install and run that on your phone. That should then unlock your bootloader.
So, you are fine. I completely brain farted that the soak test hasn't been sent to everyone. It is available to download and install, but don't do it yet.
PLEASE go and unlock your phone. I'm so sorry for the confusion.
Let me know how it goes!

hotspot
KiraTheSavior said:
figures. thats me always a day late and a dollar short.
Click to expand...
Click to collapse
is there a working exploit to make the mobile hotspot app work again? i always used the sqlite exploit to turn off subscription check but its still set to 0 on mine and the hotspot still wont work. im rooted by the way

?
KiraTheSavior said:
is there a working exploit to make the mobile hotspot app work again? i always used the sqlite exploit to turn off subscription check but its still set to 0 on mine and the hotspot still wont work. im rooted by the way
Click to expand...
Click to collapse
my system version says 183.46.10xt926 that link says its not unlockable. when i used the link in your original post to get my phone working again I automatically had this version. so i cant unlock right? ?_?

KiraTheSavior said:
my system version says 183.46.10xt926 that link says its not unlockable. when i used the link in your original post to get my phone working again I automatically had this version. so i cant unlock right? ?_?
Click to expand...
Click to collapse
No, that is the version you CAN unlock. At first, it was believed it couldn't happen, but someone discovered that Moto had accidentally added the bootloader unlock exploit back in with the KK release. It's the version after that, which hasn't been released yet but will be soon, that patches the exploit back up to no allow it. The zip file for it is available outside of the soak test so it hasn't been sent to you. What you took was the OTA you do want which does allow unlocking.
Please, go unlock your phone now before the OTA is released and then you'll be forever locked.
Go here to unlock it -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
Do it now before you do anything else. Do NOT apply the soak test OTA (which is available via a media fire link from SamuriHL) until you've unlocked your phone.

done
Rooted and unlocked. Very happy about it. But now what? What can I get with bootloader unlocked besides revert to jb?
I still need to get my WiFi tether app to work. I'm grandfathered into unlimited data so my phone is basically my internet. Are there any cool ROMs where the WiFi just works with no tricks or work a rounds?

Complete Guide for Xperia E1 (rooting, recovery, flashing, bootloader)

This thread has been moved to http://forum.xda-developers.com/xperia-e1/general/xperia-e1-rooting-flashing-recovery-t3051225
Xperia E1 has his own Subforum now, Thank you XDA!
If any moderator sees this, please close this thread!

Hello there!
First of all really thank you for making this topic, it will really help people who wants to customize their Xperia E1.
I really appreciate your action.
Secondly, I wanted to ask more help with the bootloader unlock.
I do exactly what you do but it always comes the following result;
First, when I click on unlock it gives me Failed error.
When I click on unlock for second time, it gives me Okay, meaning that successfully unlocked.
After, I'm booting into system but it stack at the boot animation.
Some people called this bootloop but I don't know what to do to fix it.
Flashing again a stock firmware fixes this but no unlocked bootloader at all.
Repeating this will give the same results.
I would like some help on it, I remember somehow I had successfully unlock the bootloader without stack at boot animation.
At service menu was saying boot loader unlock: Yes
Instead of bootloader unlock allowed: Yes
I'm able to give any information about my phone so we can fix the problems, I'm not going to buy another phone anyways
Sent from my D2005 using XDA Free mobile app

Kizoky said:
Now hold the following buttons on the phone: POWER+VOLUME DOWN
Do this until the LED turns GREEN.
Great, the phone is now in Flashmode!
Click to expand...
Click to collapse
You are supposed to VOLUME DOWN + CONNECT USING USB and you should NOT hold the power button.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
GiorgosGRN said:
Hello there!
First of all really thank you for making this topic, it will really help people who wants to customize their Xperia E1.
I really appreciate your action.
Secondly, I wanted to ask more help with the bootloader unlock.
I do exactly what you do but it always comes the following result;
First, when I click on unlock it gives me Failed error.
When I click on unlock for second time, it gives me Okay, meaning that successfully unlocked.
After, I'm booting into system but it stack at the boot animation.
Some people called this bootloop but I don't know what to do to fix it.
Flashing again a stock firmware fixes this but no unlocked bootloader at all.
Repeating this will give the same results.
I would like some help on it, I remember somehow I had successfully unlock the bootloader without stack at boot animation.
At service menu was saying boot loader unlock: Yes
Instead of bootloader unlock allowed: Yes
I'm able to give any information about my phone so we can fix the problems, I'm not going to buy another phone anyways
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
I have the same problem. Your career force-locked the phone, meaning that you cannot unlock it normally, only temporarily (that means when you do it the second time it says OKAY but when you reboot the device its gonna be locked again)
I got an email from my career, and they say the reason why I cannot unlock it is because of the firmware. I'm starting to think they don't know a thing about bootloaders.

God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app

GiorgosGRN said:
God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
Some careers (like mine, Orange) trick the user, they say Unlock Allowed: Yes. It's actually kinda true, because you can temporarily unlock it, but thinking about it our situation is the same as if that message would say No. If there would be test points on the E1 maybe we could unlock it like the older devices, but I'm not sure as it's quite old. Maybe if someone can make a hack to set the flag of locking to unlocked or make a 2ndinit ability to load a second kernel on the bootup process.
I think it would be possible, but it would require a lot of work and a large knowledge of our device (in a deeper meaning)

My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.

mire777 said:
My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.
Click to expand...
Click to collapse
You need to reflash the firmware. Kizoky will sure add that later on.

mire777 said:
My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.
Click to expand...
Click to collapse
If you brick your phone, you can always reflash the Firmware, or use the backup method which is found in PhilZ recovery.
I'll do a tutorial on this too soon

So..uhm.. Any chance I can root my phone without bricking it with this bootloader stuff ?
Was rooted using Kingo, latest update (20.A.1.2.14) removed root, prevents kingo and all other apps from rooting again.

GiorgosGRN said:
God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
As far as I know if it's says Allowed: Yes, as long as you obtain to code to unlock, along with using xperia flasher or fastboot tools to correctly unlock then it's should stay unlocked. An unlock allowed: No should not allow a request for unlock code via sony developer world site.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Kizoky said:
If you brick your phone, you can always reflash the Firmware, or use the backup method which is found in PhilZ recovery.
I'll do a tutorial on this too soon
Click to expand...
Click to collapse
I made a backup zip, that way if you use fastboot tools to flash the boot.img, then the kernel has the philz recovery 6 that can install the clone rom.zip file.

image45 said:
As far as I know if it's says Allowed: Yes, as long as you obtain to code to unlock, along with using xperia flasher or fastboot tools to correctly unlock then it's should stay unlocked. An unlock allowed: No should not allow a request for unlock code via sony developer world site
Click to expand...
Click to collapse
Some careers like Orange in Slovakia trick the user(or use a different force method) that the bootloader can be unlocked by saying Yes in the service menu, but cannot unlock with the Sony Bootloader Unlock code, due to Command did not succeed error. I think they either have a custom code, or as they said in the email I sent to them: we have something Orange(or other career-related) firmware on our device that blocks unlocking. Or maybe it's just a 0-1 flag. (like ForceLockUnlock=1)

How unhelpful of them, that's why I started obtaining off network handsets from 2010 on wards. SIM UNLOCKED ? and fully bootloader unlockable.

image45 said:
How unhelpful of them, that's why I started obtaining off network handsets from 2010 on wards. SIM UNLOCKED and fully bootloader unlockable.
Click to expand...
Click to collapse
I hate companies who force-lock their phones. I can understand why they block other SIM cards, but come on, let the bootloader unlocked for geeks/devs

Kizoky said:
I hate companies who force-lock their phones. I can understand why they block other SIM cards, but come on, let the bootloader unlocked for geeks/devs
Click to expand...
Click to collapse
I think there's some kind of a 'flag' or something in the TA that blocks us. Or maybe it's something /dev related. If the test point unlocking would work, I would be very happy. Though I don't think it would work with newer phones and it's old.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Also @Kizoky how are you planning to add more tutorials? Are you going to edit the first post or add a new post each time?

xezrunner said:
I think there's some kind of a 'flag' or something in the TA that blocks us. Or maybe it's something /dev related. If the test point unlocking would work, I would be very happy. Though I don't think it would work with newer phones and it's old.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Also @Kizoky how are you planning to add more tutorials? Are you going to edit the first post or add a new post each time?
Click to expand...
Click to collapse
I'm gonna do It tomorrow

Kizoky said:
I hate companies who force-lock their phones. I can understand why they block other SIM cards, but come on, let the bootloader unlocked for geeks/devs
Click to expand...
Click to collapse
Well I have three xperia E1's that I obtained off network along with this E3 that are all sim unlocked and fully bootloader unlockable. All the E1's are rooted with jelly bean or kit kat flashed via xperia flasher, with bootloader unlock: Yes. I find the 4.3 jb build to be the most responsive for D2005 handsets.

image45 said:
Well I have three xperia E1's that I obtained off network along with this E3 that are all sim unlocked and fully bootloader unlockable. All the E1's are rooted with jelly bean or kit kat flashed via xperia flasher, with bootloader unlock: Yes. I find the 4.3 jb build to be the most responsive for D2005 handsets.
Click to expand...
Click to collapse
Jelly Bean for the Xperia E1 (the official Sony one) is way too much unstable. KitKat is more stable. I've had random reboot issues and freezing issues (especially when playing games) on JB, while everything is much better on KitKat (there are still some lags and it takes some time to boot up but everything else is fine.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.

xezrunner said:
Jelly Bean for the Xperia E1 (the official Sony one) is way too much unstable. KitKat is more stable. I've had random reboot issues and freezing issues (especially when playing games) on JB, while everything is much better on KitKat (there are still some lags and it takes some time to boot up but everything else is fine.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.
Click to expand...
Click to collapse
You can decrease the boot time, If you delete the unnecessary apps (Google+, Google Books, etc..) And the apps you can't delete, or you are afraid, you can just disable them.

xezrunner said:
Jelly Bean for the Xperia E1 (the official Sony one) is way too much unstable. KitKat is more stable. I've had random reboot issues and freezing issues (especially when playing games) on JB
Click to expand...
Click to collapse
Well I rarely play games on any of my devices, however you are correct in that Jb does reboot more than kitkat does. When trying to control the kernel better for jelly bean, I did encounter freezing, however once I got the correct configuration it was fine.
xezrunner said:
everything is much better on KitKat (there are still some lags and it takes some time to boot up but everything else is fine.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.
Click to expand...
Click to collapse
I would love to say everything is better, however rooting is more of a challenge for some of the kitkat builds and installation of supersu was more tricky/ time consuming. Have to delete apks to speed up kitkat too.
Hope we do get a stable lollipop ROM for the E1.

image45 said:
Well I rarely play games on any of my devices, however you are correct in that Jb does reboot more than kitkat does. When trying to control the kernel better for jelly bean, I did encounter freezing, however once I got the correct configuration it was fine.
I would love to say everything is better, however rooting is more of a challenge for some of the kitkat builds and installation of supersu was more tricky/ time consuming. Have to delete apks to speed up kitkat too.
Hope we do get a stable lollipop ROM for the E1.
Click to expand...
Click to collapse
I hope too. But we'll not get an Official Lollipop provided by Sony
We'll have to wait for experienced Devs.

USCC V20 (US996) Bootloader Unlock/Root Discussion

Just a thread for the few USCC people here - I've tried to UL the bootloader using TMO instructions - no go. It will reboot into the bootloader but it asks for the unlock.bin key (fastboot oem unlock returns an unknown command error). So at least theirs that much
Phone will also boot into recovery, and I get the associated normal options there (clear, mount /system, wide device/cache, load update via ADB, load update via SD, view recovery logs, etc). Interesting thing happens when I select "run graphics test" from the recovery menu - it gives an error, then the "no command" icon, then multicolor circles rotating - but it says "erasing" then "installing system update" then goes back to the recovery menu. Not sure if it's normal, but it's interesting.
I'm not a dev or a software guy really, but would like to hear some thoughts on the USCC version...would love to have root like the TMO - especially since it will get into the fastboot menu. Wish I knew more so I could be more help.

Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.

Killah1994 said:
Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.
Click to expand...
Click to collapse
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...

elliwigy said:
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...
Click to expand...
Click to collapse
There you go, knew I was getting something mixed up.

us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Sent from my LG-US996 using Tapatalk

jayochs said:
us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Click to expand...
Click to collapse
if u read my previous post u can see i said the uscc BL is locked lol like everyone else

I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?

Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.

Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
does he have a copy of the debug kernel? you can pm me a link if possible thatd be great so we can take a look at it.. if it is an eng kernel, it could potentially help to root other variants with locked BLs
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out
---------- Post added at 02:41 AM ---------- Previous post was at 02:41 AM ----------
Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out

@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.

Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
hopefully you are able to as it shouldnt really take any time at all lol.. it would really help a lot of ppl out if it is in fact a debug kernel..
the root we have is a temp tcp root shell using a context we cant really do anything we need to do at all so it was pretty much a dead end so far

Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
I will pay you for the debug files

I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.

Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
you wont b doing anything to the phone.. if u have an adb root shell would just be copying a few files from the phone.. we can even tell you exactly what commands to use to make it easy.. we can invite you to a google hangout even so we can explain each step

Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
Whay are you asking for the phone?

I was looking to get what I spent for it, around $800

elliwigy said:
if u read my previous post u can see i said the uscc BL is locked lol like everyone else
Click to expand...
Click to collapse
yeah, the US cellular us996. it's different from the American unlocked us996. according to LG anyway, it lists it as two different phones.
I'm not on a US cellular one. I'm in an unlocked one with Verizon. the post above you said unlocked had unlocked bootloader. mines as unlocked as you get, and it doesn't have an unlocked bootloader.
Sent from my LG V20 US996

http://developer.lge.com/community/...nuId=38&contsTypeCode=QUE&prodTypeCode=MOBILE
Make yourselves heard. Let LG know we want the bootloader to be unlockable on the US996. I've talked to their live chat and they claim that they "didn't know people would want to unlock their bootloader". Show them we do.

Abumarf said:
I was looking to get what I spent for it, around $800
Click to expand...
Click to collapse
Ok if you download terminal emulator and type in get prop and send me the screen shots so i can verify it is indeed a debug kernel i will buy it from you but i would like to have proof of debug kernel

Sure, here it is: https://drive.google.com/file/d/0BwI6DTQJV37Ob1BwRkRab0xPRkk/view?usp=drivesdk
Also the phone is already up on Swappa
---------- Post added at 08:45 PM ---------- Previous post was at 08:36 PM ----------
@rickberg forgot to tag you

use Verizon locked international

Can you use a Verizon bootloader locked Pixel 2 international? With another simcard?
And is it possible to flash an ota file from Google on it and not the Verizon version? Or is that not needed?
Thanks

I'm pretty sure all phones manufactured after a certain year(think it was 2014) were made so they can be used anywhere. As long as it has the necessary bands. You will not be able to flash other firmware, unless the bootloader gets unlocked and root becomes available...
Sent from my Pixel 2 XL using Tapatalk

The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.

mikeyinid said:
The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.
Click to expand...
Click to collapse
It's not quite the same. It is unlocked, but the bootloader cannot be unlocked.

Erik1805 said:
Can you use a Verizon bootloader locked Pixel 2 international? With another simcard?
And is it possible to flash an ota file from Google on it and not the Verizon version? Or is that not needed?
Thanks
Click to expand...
Click to collapse
Yes, you can use the Verizon version withe the locked bootloader, internationally. I have one in the EU, running on Vodafone. Runs without issues.
Verizon prevents you from getting over the air updates unless you have an activated Verizon sim and the phone comes with a deactivated Verizon sim pre-installed. When I got mine it was two versions behind and on the September security patch. I tried all sorts of tricks to get it to update with my Vodafone sim, with the Verizon sim, but the best I could get it to do was say there was an update available before it bailed out one me. However, using adb and the Google images for OTA's they provide I was able to flash each update no problem using a USB cable.
Hope this helps!
Lenny
---------- Post added at 01:04 PM ---------- Previous post was at 01:00 PM ----------
mikeyinid said:
The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.
Click to expand...
Click to collapse
Just an FYI, they are slightly different. The phone itself is carrier unlocked. Any carrier can use the Verizon version just like a non-Verizon version. The difference is the Verizon bootloader is locked down, can't unlock that (unless you got one way early, on 7.1 or something like that). You also only get OTA updates for the Verizon version if you have an active Verizon sim in the phone. Manually updating using the OTA files from Googles website works with ADB, so not a big deal, but makes it a little more manual and technical than it would be otherwise. You'll notice there are different OTA's and different versions used for Verizon's files - keeping them slightly different.

IDroidThere4Iam said:
Yes, you can use the Verizon version withe the locked bootloader, internationally. I have one in the EU, running on Vodafone. Runs without issues.
Verizon prevents you from getting over the air updates unless you have an activated Verizon sim and the phone comes with a deactivated Verizon sim pre-installed. When I got mine it was two versions behind and on the September security patch. I tried all sorts of tricks to get it to update with my Vodafone sim, with the Verizon sim, but the best I could get it to do was say there was an update available before it bailed out one me. However, using adb and the Google images for OTA's they provide I was able to flash each update no problem using a USB cable.
Hope this helps!
Lenny
---------- Post added at 01:04 PM ---------- Previous post was at 01:00 PM ----------
Just an FYI, they are slightly different. The phone itself is carrier unlocked. Any carrier can use the Verizon version just like a non-Verizon version. The difference is the Verizon bootloader is locked down, can't unlock that (unless you got one way early, on 7.1 or something like that). You also only get OTA updates for the Verizon version if you have an active Verizon sim in the phone. Manually updating using the OTA files from Googles website works with ADB, so not a big deal, but makes it a little more manual and technical than it would be otherwise. You'll notice there are different OTA's and different versions used for Verizon's files - keeping them slightly different.
Click to expand...
Click to collapse
You can't flash images on the Verizon version. The bootloader needs to be unlocked, and that obviously isn't happening. I don't think it matters which sim you have in the Verizon version, you'll get OTA updates no matter what. The phones aren't as different as you guys think. The only reason there are different factory images for the Verizon version is they install Verizon bloat on first boot.

mikeyinid said:
You can't flash images on the Verizon version. The bootloader needs to be unlocked, and that obviously isn't happening. I don't think it matters which sim you have in the Verizon version, you'll get OTA updates no matter what. The phones aren't as different as you guys think. The only reason there are different factory images for the Verizon version is they install Verizon bloat on first boot.
Click to expand...
Click to collapse
You can ADB sideload. Did the same this week. No problems. You just cannot flash a another room.

Erik1805 said:
You can ADB sideload. Did the same this week. No problems. You just cannot flash a another room.
Click to expand...
Click to collapse
How do you adb sideload with a locked bootloader?

mikeyinid said:
How do you adb sideload with a locked bootloader?
Click to expand...
Click to collapse
Used this. Went great.
https://developers.google.com/android/ota

Erik1805 said:
Used this. Went great.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Yea, we're talking about two different things.

mikeyinid said:
Yea, we're talking about two different things.
Click to expand...
Click to collapse
Yes thought so. No custom rom flashing for me, thats what you ment

Erik1805 said:
Yes thought so. No custom rom flashing for me, thats what you ment
Click to expand...
Click to collapse
But, I just learned something because I had no idea Google posted the OTA files like that

Erik1805 said:
Used this. Went great.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
this is an old post but im trying to see if anyone can help me with this adb sidload. I get an error that footer is wrong and cant get the android P beta to flash. any thoughts?