I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
Not even ordering until I am sure that is all in place.
Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.
I'm waiting for a method of gaining root access to be achieved before placing my order. The phone I have now (Nexus 6) still works fine so I'm in no rush. Also, I am kind of interested in seeing what kind of reviews the XL gets anyways. Mainly regarding the volume of the speaker.
cmzizi said:
Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.
Click to expand...
Click to collapse
How do you plan on paying for it? I can bring it with me on my trip to Zimbabwe 10/17/16.
I can do payment via PayPal.
Sent from my SM-N930F using Tapatalk
You will almost certainly have root access on this device. The bootloader looks to be unlockable unless you get the Verizon branded version.
Remember, root doesn't mean supersu, or even the su binary. Root means the ability to run commands in the superuser context. You will have that at the very least. From there a new solution to give root access to normal android applications may need to be developed, but that is only a matter of time. As long as your bootloader is unlockable, you can build whatever you need into the kernel as a module, or run a service from init (like daemonsu).
grneyez said:
How do you plan on paying for it? I can bring it with me on my trip to Zimbabwe 10/17/16.
Click to expand...
Click to collapse
The phone doesnt come out until after this date. This is impossible
cmzizi said:
Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.
Click to expand...
Click to collapse
cmzizi said:
I can do payment via PayPal.
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
I'll PM you.
---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------
KnownDominance said:
The phone doesnt come out until after this date. This is impossible
Click to expand...
Click to collapse
For you yes that is correct, for me I get it sooner. Thanks
tigercranestyle said:
in the past only unlocking the bootloader erased data... not the actual rooting. why not just unlock the bootloader before setting it up, continue to use the device as you please, and then just wait until a root method is released?
Click to expand...
Click to collapse
That is what I normally do...... unlock the bootloader right out of the box (it wipes the phone then before you set it up) then you have the option to root later on if you like.
ill keep my s7. the phone looks smooth And fluid but i hate the design. its also way overpriced.
How could you wait? Buy it. If for some wild reason we couldn't get root. I'm sure it would still be returnable. If you wait, the phone will already have root and a custom ROM before one ever shows up on your doorstep.lol
Sent from my Nexus 6P using XDA-Developers mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
charlieb620 said:
Click to expand...
Click to collapse
I don't do that.... I usually buy Verizon and purposely get at least 3 phones and return them as defective when I dont have root to my own device. Just as a little F-U to them. Then I finally hack my own phone and go with it. But I'll return as many as I can as defective first until they wise up and stop sending them to me.
You simply should not have to pay extra when hardware and software shouldn't be tied together in the first place. Why would I pay extra for an unlocked device that is exactly the same hardware as the locked one.
That is definitely the most immature thing I've heard all week.
You don't like their policies so you are 'showing them'? Give me a break. My 11 year old grew out of that behavior 5 years ago...
Sent from my Nexus 6P using Tapatalk
AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
Dude its not hard to completely re set your phone quit being lazy I do it like 30 + times in 2 months, and install many themes apps widgets and configurations. I also use Nova launcher back up where you just have to install widget apps etc. But re setting a phone is nothing and do not expect root on this phone. Just google search root pixel phones. Many sources say its going to be impossible. Hope you didnt get it for root purposes. lol
AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
I even already wait 3rd year cause I skip ugliest nexus 6p and now pixel xl which has no unlocked bootloader and no root, and on top of that it has NOT wireless charging AGAIN !!!
I'm incredibly disappointed because Pixel XL seems good even it has HUGE, gigantic bezels on top and bottom.
For now Nexus 6 is the best and hope not the last google phone.
BaconSeeds said:
Dude its not hard to completely re set your phone quit being lazy I do it like 30 + times in 2 months, and install many themes apps widgets and configurations. I also use Nova launcher back up where you just have to install widget apps etc. But re setting a phone is nothing and do not expect root on this phone. Just google search root pixel phones. Many sources say its going to be impossible. Hope you didnt get it for root purposes. lol
Click to expand...
Click to collapse
Not one source says impossible...stop spreading false propaganda, phones will be rooted within days
I can assure you this thing will be rooted, I will see to it myself
DespairFactor said:
I can assure you this thing will be rooted, I will see to it myself
Click to expand...
Click to collapse
I hope so I want it to be rooted just the articles I've read made it seem doubtful. Especially b/c I pre ordered one.
Related
I just Rooted my Z1 Compact by this method http://forum.xda-developers.com/showthread.php?t=2642081 and now I have 4.3 firmware UK. Now I have some questions:
1. When I check on phone if unlocking bootloader is possible, it says no. I haven't read that article about unlocking fully, but is there still any way to unlock it? Because, once Stable official CM comes out, I could install it.
2. When I check for software update, it says already latest, and doesn't provide KitKat(Don't forget I'm on UK rooted 4.3). Why? Also do I loose root if I update by official software?
3. As I said, once CM, stable comes out I will install it. But until then, I'm gonna stay on official firmware + root. What is simplest way to update to latest firmwares but still having root(or if really required, first updating, then rooting that latest firmware)?
I tried to be as straight as possible with my questions, and it would really mean a lot to me, any useful answers because I don't have much time for reading all those posts. Note that before this phone I had already Samsung galaxy mini with many roms, but for this phone it's much more complicated, so that's why I'm asking this all. Thanks.
Smoller said:
I just Rooted my Z1 Compact by this method http://forum.xda-developers.com/showthread.php?t=2642081 and now I have 4.3 firmware UK. Now I have some questions:
1. When I check on phone if unlocking bootloader is possible, it says no. I haven't read that article about unlocking fully, but is there still any way to unlock it? Because, once Stable official CM comes out, I could install it.
2. When I check for software update, it says already latest, and doesn't provide KitKat(Don't forget I'm on UK rooted 4.3). Why? Also do I loose root if I update by official software?
3. As I said, once CM, stable comes out I will install it. But until then, I'm gonna stay on official firmware + root. What is simplest way to update to latest firmwares but still having root(or if really required, first updating, then rooting that latest firmware)?
I tried to be as straight as possible with my questions, and it would really mean a lot to me, any useful answers because I don't have much time for reading all those posts. Note that before this phone I had already Samsung galaxy mini with many roms, but for this phone it's much more complicated, so that's why I'm asking this all. Thanks.
Click to expand...
Click to collapse
1. If you got your Phone from a provider then you're probably out of luck.
2. Should have used this instead if you want KK - http://forum.xda-developers.com/showthread.php?t=2688933
3. Read the forums with each new release, unless you unlock the BL you'll have to wait for a method like above.
XperienceD said:
1. If you got your Phone from a provider then you're probably out of luck.
2. Should have used this instead if you want KK - http://forum.xda-developers.com/showthread.php?t=2688933
3. Read the forums with each new release, unless you unlock the BL you'll have to wait for a method like above.
Click to expand...
Click to collapse
Well, yeah it's from T-mobile, so there is no way to unlock bootloader? Thanks for link, but is there any way to update just using phone? I have problems with PC, whenever PC detects flash drive inserted(my phone in flash mode) it freezes at the end of installation, so I have to flash on another PC, which is frustrating as I can do that like every 2 weeks(I have only 1 PC)
Smoller said:
Well, yeah it's from T-mobile, so there is no way to unlock bootloader?
Click to expand...
Click to collapse
Unfortunately, no. I had my Z for about year living in hope but Sony have locked it down too much for the devs to crack, so I'll never get another Phone from a carrier again.
Smoller said:
Thanks for link, but is there any way to update just using phone?
Click to expand...
Click to collapse
Modding the Phone breaks the OTA update service which is why, once you decide to start modding you're better off just flashing an .ftf to update.
Smoller said:
Well, yeah it's from T-mobile, so there is no way to unlock bootloader? Thanks for link, but is there any way to update just using phone? I have problems with PC, whenever PC detects flash drive inserted(my phone in flash mode) it freezes at the end of installation, so I have to flash on another PC, which is frustrating as I can do that like every 2 weeks(I have only 1 PC)
Click to expand...
Click to collapse
Z1 compact from tmobile? or z1s? or you have a z1 compact on tmobiles network? If it says bootloader unlocked allowed: no, you cant unlock it and will not be able to install cm. Where did you get the phone from?
Correct me if I'm wrong but.... Xperia Z1 Compact is still not available in US much more on carriers like T-Mobile.
If I guess correctly, 'bootloader unlocked allowed: No' should be stored in the TA partition. Maybe it's not so hard to find, if you compare two TA backups (one disallowed and one allowed). Is there any research done already about that?
@Smoller do you have a backup of your TA partition (DRM keys)?
@zxz0O0
It's impossible by just comparing. I'm not sure if you still remember my reply on your bootloader unlocking thread but I posted there a comparison between 2 the same TA backup just between 2 reboots and the result was that they are very2 different from each other.
zxz0O0 said:
If I guess correctly, 'bootloader unlocked allowed: No' should be stored in the TA partition. Maybe it's not so hard to find, if you compare two TA backups (one disallowed and one allowed). Is there any research done already about that?
@Smoller do you have a backup of your TA partition (DRM keys)?
Click to expand...
Click to collapse
Riyal said:
@zxz0O0
It's impossible by just comparing. I'm not sure if you still remember my reply on your bootloader unlocking thread but I posted there a comparison between 2 the same TA backup just between 2 reboots and the result was that they are very2 different from each other.
Click to expand...
Click to collapse
What? You made a TA backup on your phone and after 2 reboots it was completetly different? No I've never seen a post like that, that sounds really weird.
I would really be interested to see this myself.
Yes it says exactly bootloader unlock allowed: No. And I'm from Croatia so most likely it is also available in other Europe countries, especially UK...From T-Mobile...really weird it's not still on US Tmobile because this phone is made in January. And I can make a DRM backup if needed, if there might be any way to unlock bootloader. Also, just to be sure, if I input unlock SIM code for other carriers, it has still everything same except possibility to put SIM cards and use other carriers, right?
Sent from my D5503 using xda app-developers app
zxz0O0 said:
What? You made a TA backup on your phone and after 2 reboots it was completetly different? No I've never seen a post like that, that sounds really weird.
I would really be interested to see this myself.
Click to expand...
Click to collapse
@zxz0O0
You did forget it... Anyways here it is... 2 working TA backups made from the same version of Backup TA. What I only did between the 2 backups was
1. Make the 1st backup
2. Reboot the phone
3. Make the 2nd backup
And here are the results.
Please do note that I tried both TA backups and both of them are perfectly fine when restored on my phone. Also I made a 3rd TA backup and it's also very different from the last 2 backups which is shown in the screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Riyal said:
@zxz0O0
You did forget it... Anyways here it is... 2 working TA backups made from the same version of Backup TA. What I only did between the 2 backups was
1. Make the 1st backup
2. Reboot the phone
3. Make the 2nd backup
And here are the results.
Please do note that I tried both TA backups and both of them are perfectly fine when restored on my phone. Also I made a 3rd TA backup and it's also very different from the last 2 backups which is shown in the screenshot.
Click to expand...
Click to collapse
Isn't it only the log that changed? And the padding at the end? If not then I guess the partition is randomly encrypted and the key is stored inside the partition.
zxz0O0 said:
Isn't it only the log that changed? And the padding at the end? If not then I guess the partition is randomly encrypted and the key is stored inside the partition.
Click to expand...
Click to collapse
Nope! The log there is only like 4 lines. While the difference between both files are hundreds or even thousands of lines You could see the grey and yellow markings on the left. That should graphically show you what & how big the difference are between the 2 files.
$20 to the dev who gets AOSP to work on Sprint's latest 1.80.651.30, WITHOUT using foreign firmware.
We're about a year into this device, and apparently we have no developers on the Sprint side working on this.
Not sure if that price is worth it to anyone, but I'm a man of my word.
mcwups1 said:
$20 to the dev who gets AOSP to work on Sprint's latest 1.80.651.30, WITHOUT using foreign firmware.
We're about a year into this device, and apparently we have no developers on the Sprint side working on this.
Not sure if that price is worth it to anyone, but I'm a man of my word.
Click to expand...
Click to collapse
You contacted me multiple times about editing the Verizon guide for Sprint.. I took my free time to respond.. and now you post this.. A bit of a slap in the face, no? :silly:
I would contact the Devs working on AOSP personally, however with N already here (and coming soon to the rest of the carriers), I personally don't see anyone taking their time on MM (just an opinion).
I do hope you get it working. :good:
andybones said:
You contacted me multiple times about editing the Verizon guide for Sprint.. I took my free time to respond.. and now you post this.. A bit of a slap in the face, no? :silly:
I would contact the Devs working on AOSP personally, however with N already here (and coming soon to the rest of the carriers), I personally don't see anyone taking their time on MM (just an opinion).
I do hope you get it working. :good:
Click to expand...
Click to collapse
No, you never got back with my question!
I have your zip, but haven't flashed it, because I'm not sure if it needs "modified" for Sprint.
Plus, I am looking for it to work with Sprint firmware first.
mcwups1 said:
No, you never got back with my question!
I have your zip, but haven't flashed it, because I'm not sure if it needs "modified" for Sprint.
Plus, I am looking for it to work with Sprint firmware first.
Click to expand...
Click to collapse
"No, you never got back with my question!"
I responded last night, and I quoted you so you'd get a notification to see it.
http://forum.xda-developers.com/showpost.php?p=70256059&postcount=15
The whole point of this method is to get back to stock Verizon/Sprint.
If you do my method you will be back on 100% Sprint (Since you are flashing the Sprint RUU AFTER the modified firmware) AND AOSP ROMs working. I don't know why, but it works. It's been confirmed on a number of Verizon users AND Sprint.
"Plus, I am looking for it to work with Sprint firmware first"
Then why did you contact me multiple times? I am not going to apologize for taking longer than you'd like to respond.. I wrote the guide for Verizon, so excuse me for not wanting to brick your device with rushed info..
Like I said, I hope you get it working.. I did respond in the thread, and as I said if you need help editing the android.info.txt, let me know. :good:
I didn't get it. Responded to the linked thread /post.
Thank you.
I understood your instructions for the firmware and RUU, but didn't think your zip would work with my Sprint device. Thank you so much for the deeper explanation.
Will report back here....
mcwups1 said:
I didn't get it. Responded to the linked thread /post.
Thank you.
I understood your instructions for the firmware and RUU, but didn't think your zip would work with my Sprint device. Thank you so much for the deeper explanation.
Will report back here....
Click to expand...
Click to collapse
You are very welcome my friend!
AOSP/CM ROMs are a great way to change up the device so I understand the want to use them, hence how this method was found.
andybones said:
You are very welcome my friend!
AOSP/CM ROMs are a great way to change up the device so I understand the want to use them, hence how this method was found.
Click to expand...
Click to collapse
@andybones
Just to make sure (on both threads, sorry), my CID is 11111111.
I don't use the Sprint CID, I change the android text to the Super CID number, right?
Okay.
Everything done and I didn't brick.
New problem.
I only have 3G, even after the RUU.
Something tells me I shouldn't have GSM options?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mcwups1 said:
Okay.
Everything done and I didn't brick.
New problem.
I only have 3G, even after the RUU.
Something tells me I shouldn't have GSM options?
Click to expand...
Click to collapse
In bootloader run these cmds
fastboot erase modemst1
fastboot erase modemst2
Okay. It appears I have LTE, but now I can't make calls.
Edit: Now, since I woke up this morning, I have no data. I can boot up, but I cannot make calls or message anyone.
Says my device is not activated, and I need to call customer service.
Or, you are not authorized to call this account (calling my wife), if you would like more services, contact customer service.
Showing all zeros for a phone number.
000-000-0000
@andybones
Check your Gmail.
mcwups1 said:
@andybones
Check your Gmail.
Click to expand...
Click to collapse
Thank you kindly my friend! Very much appreciated.
andybones said:
Thank you kindly my friend! Very much appreciated.
Click to expand...
Click to collapse
I can flash CM, but I can't use it.
I cannot make calls or message anyone.
If I restore my Sense backup, then I have no data. I have to erase modems again, just to get messaging back and to get my Sprint ID to return and give me my phone number again.
This has been a major headache, and I don't think this will actually work fully on my device.
Curious to know if you know why I had to input a PIN after flashing that modified firmware zip after reboot?
mcwups1 said:
I can flash CM, but I can't use it.
I cannot make calls or message anyone.
If I restore my Sense backup, then I have no data. I have to erase modems again, just to get messaging back and to get my Sprint ID to return and give me my phone number again.
This has been a major headache, and I don't think this will actually work fully on my device.
Curious to know if you know why I had to input a PIN after flashing that modified firmware zip after reboot?
Click to expand...
Click to collapse
Can't say about Sprint usage and AOSP ROMs or sprint anything really so can't comment on that.
After flashing the firmware it wiped my system so it had no ROM to boot to, so I had to hold volume buttons and power to get into bootloader and then ran the VZW RUU.
I have been using multirom personally since this method as well.
I still wish someone would find a way to get AOSP working on Sprint firmware.
After wiping modems, updating PRL and Profile, I have a working phone again on Sense.
I'm not sure what flashing that zip did, but I'm thinking it changes the internal partitions of firmware, and that Sprint either blocks partitions or doesn't have them, and the zip modded them, or added them.
But WTF do I know?
mcwups1 said:
I still wish someone would find a way to get AOSP working on Sprint firmware.
After wiping modems, updating PRL and Profile, I have a working phone again on Sense.
I'm not sure what flashing that zip did, but I'm thinking it changes the internal partitions of firmware, and that Sprint either blocks partitions or doesn't have them, and the zip modded them, or added them.
But WTF do I know?
Click to expand...
Click to collapse
As I. It seems once/if theres a fix for Sprint, it should also hopefully be the same for Verizon.
Your input is as good as the rest of us.
I've gotten CM/Lineage to work on my Sprint HTC 10. I did have to flash an international firmware zip to get it to get past the boot logo but now it's fine. Note though that I did delete the modems, radio, cache and recovery out of the firmware package before I flashed it. This is likely why you have issues with data now if you didn't do so.
That said, data is still iffy at times on AOSP without toggling some settings after rebooting so it might be worth it for some people to wait until that's fixed before proceeding.
ssmercurys said:
I've gotten CM/Lineage to work on my Sprint HTC 10. I did have to flash an international firmware zip to get it to get past the boot logo but now it's fine. Note though that I did delete the modems, radio, cache and recovery out of the firmware package before I flashed it. This is likely why you have issues with data now if you didn't do so.
That said, data is still iffy at times on AOSP without toggling some settings after rebooting so it might be worth it for some people to wait until that's fixed before proceeding.
Click to expand...
Click to collapse
You should do a write up on the Sprint forums for others.
Their are builds that are out now for sprint that doesn't require a custom firmware
trev23sks said:
Their are builds that are out now for sprint that doesn't require a custom firmware
Click to expand...
Click to collapse
How?
Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
andixxx81 said:
Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
Click to expand...
Click to collapse
That's a brick. Call Google with that one. They should replace that. Anytime I've seen the n/a for bootloader and baseband it's toast.
How did you brick with bootloader locked? Best bet is to RMA it for a replacement it's done unless there is a tool to save it but I doubt it
andixxx81 said:
Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
View attachment 4287902
Click to expand...
Click to collapse
Have you tried a newer RUU version from Google, or was it already on the newest?
toknitup420 said:
That's a brick. Call Google with that one. They should replace that. Anytime I've seen the n/a for bootloader and baseband it's toast.
Click to expand...
Click to collapse
Theres no other way to make this back normal?
liam_davenport said:
How did you brick with bootloader locked? Best bet is to RMA it for a replacement it's done unless there is a tool to save it but I doubt it
Click to expand...
Click to collapse
I just take picture and video,after that suddenly restarted and boot into this,i try to choose start,recovery mode,no luck..
Yes,i did twit google and they said must go to google store
michaelbsheldon said:
Have you tried a newer RUU version from Google, or was it already on the newest?
Click to expand...
Click to collapse
I dont know whats RUU version,i'm nubie about this sir:silly:
andixxx81 said:
I just take picture and video,after that suddenly restarted and boot into this,i try to choose start,recovery mode,no luck..
Yes,i did twit google and they said must go to google store
Click to expand...
Click to collapse
andixxx81 said:
I dont know whats RUU version,i'm nubie about this sir:silly:
Click to expand...
Click to collapse
Yeah RMA it then probably some hardware issue. He means Factory Image from here But I doubt you'll be able to flash one since locked and no fastboot
liam_davenport said:
Yeah RMA it then probably some hardware issue. He means Factory Image from here But I doubt you'll be able to flash one since locked and no fastboot
Click to expand...
Click to collapse
His only option is RMA. Locked bl so he can't do anything on his end. But this is clearly a hardware or software failure that is not his fault. Google will replace it.
Are there any News on this issue?
Got my Pixel Bootlooping with locked Bootloader, disabled OEM-Unlock Option.
Do i have any options other than RMA?
I had this problem too, except I could get into the recovery after many tries. I tried sideloading the ota with adb to fix it. But it didn't help. Any way to get replacement after this many years?
andixxx81 said:
Please help my pixel xl
cannot enter into recovery mode
Click to expand...
Click to collapse
You can get into recovery mode , by (in my case): leave the phone in Power Off mode for an hour or more - Start with power + volume down - recovery... and sometimes it works. But no, it does not help. I sideloaded the OTA multiple times, still no luck
ferydaboss said:
You can get into recovery mode , by (in my case): leave the phone in Power Off mode for an hour or more - Start with power + volume down - recovery... and sometimes it works. But no, it does not help. I sideloaded the OTA multiple times, still no luck
Click to expand...
Click to collapse
I confirm to that as I have the exact problem. I did manage to boot into system a few times after it started bootlooping but it always froze and restarted before I enabled oem unlocking.
iloveoreos said:
I confirm to that as I have the exact problem. I did manage to boot into system a few times after it started bootlooping but it always froze and restarted before I enabled oem unlocking.
Click to expand...
Click to collapse
exactly the same here i just talked to google support, hey redirected me to the UK google support, but i am from Romania, don't really know if they will RMA it or not.. but anyways i will have to pay shipping cost via DHL or something like that. maybe it's not worth it.
ferydaboss said:
exactly the same here i just talked to google support, hey redirected me to the UK google support, but i am from Romania, don't really know if they will RMA it or not.. but anyways i will have to pay shipping cost via DHL or something like that. maybe it's not worth it.
Click to expand...
Click to collapse
I read that replacing the battery sometimes fixes it. I might try that, but it sounds sketchy.
iloveoreos said:
I read that replacing the battery sometimes fixes it. I might try that, but it sounds sketchy.
Click to expand...
Click to collapse
I went to a local repair shop, they said the the "EEMC memory" is bad... meaning that i would have to replace the whole motherboard + there are no spare pieces in my country. Luckily i managed to talk to Google Support, and they will RMA it, i just need to clarify the details of shipping, packaging etc. we'll see HOw it works out. Also i just bought a used pixel 2 XL, so i'm good for the moment. Will sell the pixel XL they send me.
ferydaboss said:
I went to a local repair shop, they said the the "EEMC memory" is bad... meaning that i would have to replace the whole motherboard + there are no spare pieces in my country. Luckily i managed to talk to Google Support, and they will RMA it, i just need to clarify the details of shipping, packaging etc. we'll see HOw it works out. Also i just bought a used pixel 2 XL, so i'm good for the moment. Will sell the pixel XL they send me.
Click to expand...
Click to collapse
Was yours still on warranty?
iloveoreos said:
Was yours still on warranty?
Click to expand...
Click to collapse
It seems so, yes. I bought it last year, from someone, in my country who said it was bought from the UK. I contacted google for fun, and they said that based on the IMEI it is under warranty.
ferydaboss said:
It seems so, yes. I bought it last year, from someone, in my country who said it was bought from the UK. I contacted google for fun, and they said that based on the IMEI it is under warranty.
Click to expand...
Click to collapse
Ok, so I replaced the battery and it booted! Except I broke the screen taking it apart so I couldn't go on it.
hELLo,
All of a sudden this bootloop happens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it possible to fix this nexus 5x? 16gb
0. Bootlooping.
1- Bootloader locked.
2- Can not Get into phone.
3- Can get into fastboot
4. Can get into recovery
5. ADB SIDE LOAD FAILED, sometimes at 11%, sometimes at 48%,
Tried following:-
Anyone?
Administr4tor said:
Anyone?
Click to expand...
Click to collapse
If it's bootlooping then that's what ended up happening to all the devices up until this point. The bootloop issue does not load beyond the recovery partition. It's not a software issue, it's hardware related. You can contact LG and see what they say, but it may be the end of it.
mikeprius said:
If it's bootlooping then that's what ended up happening to all the devices up until this point. The bootloop issue does not load beyond the recovery partition. It's not a software issue, it's hardware related. You can contact LG and see what they say, but it may be the end of it.
Click to expand...
Click to collapse
Thanks for confirming that LG is piece of trash.
My phone was working fine today till evening, suddenly it restarted and this boot loop started. I was on PixelRom (Oreo 8.0)
I tried flashing Factory image of 8.1 final release via fastboot. Its still not booting. Keeps restarting.
Any help?
Administr4tor said:
Thanks for confirming that LG is piece of trash.
Click to expand...
Click to collapse
Danish Fayaz said:
My phone was working fine today till evening, suddenly it restarted and this boot loop started. I was on PixelRom (Oreo 8.0)
I tried flashing Factory image of 8.1 final release via fastboot. Its still not booting. Keeps restarting.
Any help?
Click to expand...
Click to collapse
Contact LG. They're fixing these even if they're out of warranty.
My Nexus 5x bootlooping also. I try to sideload the latest ota and make an Factory Reset but did not help. Bootloader is locked and oem Unlock is disabled. What can I do?
-Happy Feet- said:
My Nexus 5x bootlooping also. I try to sideload the latest ota and make an Factory Reset but did not help. Bootloader is locked and oem Unlock is disabled. What can I do?
Click to expand...
Click to collapse
Throw it in garbage and never buy LG phones.
the fact you can enter recovery, heck even adb/fastboot means you can 99% fix it (the 1% being hardware failure, which i really doubt, due to overheating, but thats fixable with the cooper plate mod), there's tons of guides in the q&a forum section, search it up.
LG replaced my MOBO and CPU for free, even though I had bought used on eBay. I just used the confirmation email from eBay and PayPal as proof of purchase.
Assuming you have called LG and confirmed your trashy assumption take matters into your own hands.
Did you try "fastboot flashing unlock" command from command prompt while n5x is on the bootloader?
Then proceed to https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926
To fix BLOD
derrickl1990 said:
LG replaced my MOBO and CPU for free, even though I had bought used on eBay. I just used the confirmation email from eBay and PayPal as proof of purchase.
Assuming you have called LG and confirmed your trashy assumption take matters into your own hands.
Did you try "fastboot flashing unlock" command from command prompt while n5x is on the bootloader?
Then proceed to https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926
To fix BLOD
Click to expand...
Click to collapse
As I said, BOOTLOADER IS LOCKED, OEM IS LOCKED, CAN NOT ENTER into PHONE, so there is NO POINT IN trying FASTBOOT FLASHING UNLOCK, it will not do anything good.
tHis is not first time i have had ISSUES WITH NEXUS LG TRASH CANS, check these posts too :
Nexus6p-how-to-flash-stock-factory-rom
How-to-flash-NEXUS6 rom
Thx
Administr4tor said:
As I said, BOOTLOADER IS LOCKED, OEM IS LOCKED, CAN NOT ENTER into PHONE, so there is NO POINT IN trying FASTBOOT FLASHING UNLOCK, it will not do anything good.
tHis is not first time i have had ISSUES WITH NEXUS LG TRASH CANS, check these posts too :
Nexus6p-how-to-flash-stock-factory-rom
How-to-flash-NEXUS6 rom
Thx
Click to expand...
Click to collapse
Got it. Check with LG
Administr4tor said:
Thanks for confirming that LG is piece of trash.
Click to expand...
Click to collapse
Do what everyone is telling you to do: contact LG.
My Nexus 5X was overheating a lot and I sent it back to LG telling them about the bootloop issue and they offered me a complete refund for the phone.
It's a hardware issue, so you can't do anything related to software (ADB, fastboot, etc. nothing will work).
two questions
Carball0 said:
Do what everyone is telling you to do: contact LG.
My Nexus 5X was overheating a lot and I sent it back to LG telling them about the bootloop issue and they offered me a complete refund for the phone.
It's a hardware issue, so you can't do anything related to software (ADB, fastboot, etc. nothing will work).
Click to expand...
Click to collapse
1. Is/Was your phone under warranty?
2. Did they do for free? how long did it take? Please share their contact information, how you initiated this all process.
Thanks
Administr4tor said:
1. Is/Was your phone under warranty?
2. Did they do for free? how long did it take? Please share their contact information, how you initiated this all process.
Thanks
Click to expand...
Click to collapse
I bought my Nexus on Amazon and they kindly offered me a complete refund of the phone (it was under warranty, it had three months left).
I just opened a chat with Amazon support and they offered me the refund (completely free, I returned the phone to Amazon and then I bought a Pixel XL
If your warranty period has ended, try contacting your seller and see if they offer you any solution. I've read that because of the bootloop problem the warranty period has been extended to 30 months:
https://www.reddit.com/r/ProjectFi/comments/86kuvq/lg_extends_bootlooping_nexus_5x_warranty_to_30/ but I don't know if it applies to every retailer.
Carball0 said:
I bought my Nexus on Amazon and they kindly offered me a complete refund of the phone (it was under warranty, it had three months left).
I just opened a chat with Amazon support and they offered me the refund (completely free, I returned the phone to Amazon and then I bought a Pixel XL
If your warranty period has ended, try contacting your seller and see if they offer you any solution. I've read that because of the bootloop problem the warranty period has been extended to 30 months:
https://www.reddit.com/r/ProjectFi/comments/86kuvq/lg_extends_bootlooping_nexus_5x_warranty_to_30/ but I don't know if it applies to every retailer.
Click to expand...
Click to collapse
So, its Amazon who were kind NOT LG because I have had hard time with LG replacing phones.
Thanks for all information
Administr4tor said:
So, its Amazon who were kind NOT LG because I have had hard time with LG replacing phones.
Thanks for all information
Click to expand...
Click to collapse
But have you tried requesting an RMA on LG's webpage? I once did and they fixed it in one week for free before my overheating/bootloop problems started.
Even so, some people on XDA claims to have their NX5X repaired out of warranty with LG service because of the bootloop: https://forum.xda-developers.com/nexus-5x/help/lg-usa-doing-warranty-repairs-5x-t3687497
I have a question. I went to oneclickroot.com to get the Pixel rooted.
Is it normal when i reboot or shut down the phone, that the phone keeps saying that the phone bootloader is unlocked then it says press power button to continue, is it normal for that to keep popping up, when u restart and power on the phone.
Dasin said:
I have a question. I went to oneclickroot.com to get the Pixel rooted.
Is it normal when i reboot or shut down the phone, that the phone keeps saying that the phone bootloader is unlocked then it says press power button to continue, is it normal for that to keep popping up, when u restart and power on the phone.
Click to expand...
Click to collapse
Did it actually root the phone? You may have corrupted your device with that root method. If it even worked
Badger50 said:
Did it actually root the phone? You may have corrupted your device with that root method. If it even worked
Click to expand...
Click to collapse
So your saying that it is not suppose to do that. agghhh i used the site oneclickroot.com and i had to pay them 99.99 dollars to root the phone, because the instructions is detailed enough there is always a small part that is missing. Is there a way i can wipe the phone and make it brand new so i can start from scratch because clearly as u stated they messed up my device with there corny root process.
Dasin said:
So your saying that it is not suppose to do that. agghhh i used the site oneclickroot.com and i had to pay them 99.99 dollars to root the phone, because the instructions is detailed enough there is always a small part that is missing. Is there a way i can wipe the phone and make it brand new so i can start from scratch because clearly as u stated they messed up my device with there corny root process.
Click to expand...
Click to collapse
Yeah, your phone shouldn't do that. Does it actually boot up to the OS outa curiosity? If your bootloader is unlocked, and you have OEM unlocking and USB debugging enabled, then you can fastboot the factory image and wipe your device to start over. There are great guides in these forums for that purpose :good:
Unlocking the bootloader will induce a warning every time the phone is rebooted. That would be normal. Without seeing exactly what the warning says, it's hard to say if what you are seeing is the same message or is normal.
That said, I would probably reflash the factory images and use a different root method. It's not terribly hard to do on your own so I would avoid any one click type solutions because it's just asking for trouble.
this is the normal bootloader unlocked screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes that screen is normal in a phone that had the bootloader unlocked on every boot
Badger50 said:
Yeah, your phone shouldn't do that. Does it actually boot up to the OS outa curiosity? If your bootloader is unlocked, and you have OEM unlocking and USB debugging enabled, then you can fastboot the factory image and wipe your device to start over. There are great guides in these forums for that purpose :good:
Click to expand...
Click to collapse
Yeah it goes into the OS.
fury683 said:
Unlocking the bootloader will induce a warning every time the phone is rebooted. That would be normal. Without seeing exactly what the warning says, it's hard to say if what you are seeing is the same message or is normal.
That said, I would probably reflash the factory images and use a different root method. It's not terribly hard to do on your own so I would avoid any one click type solutions because it's just asking for trouble.
Click to expand...
Click to collapse
When i reboot the phone it says this (Press power button to resume)
Right below that with a yellow triangle, it says.
The bootloader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers, Do not store any sensitive data on the device.
Visit this link on another device
then it shows an ID
Dasin said:
Yeah it goes into the OS.
When i reboot the phone it says this (Press power button to resume)
Right below that with a yellow triangle, it says.
The bootloader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers, Do not store any sensitive data on the device.
Visit this link on another device
then it shows an ID
Click to expand...
Click to collapse
The bootloader message is normal, you just shouldn't have to press to continue every time. Since your in the OS, have you checked if it's rooted?
Badger50 said:
The bootloader message is normal, you just shouldn't have to press to continue every time. Since your in the OS, have you checked if it's rooted?
Click to expand...
Click to collapse
No, i dont have to go to continue, when i boot up my phone that message pops up and it automatically boots into my OS unless i tap the power button, as it says in the message. I just wanted to know if thats normal because im getting conflicting information, like does it mean that the jailbreak method done was the wrong one or its not a proper root.
Also how do i check to see if it is rooted?
Dasin said:
No, i dont have to go to continue, when i boot up my phone that message pops up and it automatically boots into my OS unless i tap the power button, as it says in the message. I just wanted to know if thats normal because im getting conflicting information, like does it mean that the jailbreak method done was the wrong one or its not a proper root.
Also how do i check to see if it is rooted?
Click to expand...
Click to collapse
That message is normal for all of us with bootloader unlocked pixel devices. You can check root status with an app like this one :good:
https://play.google.com/store/apps/details?id=technarcs.rootchecker
And my question is you paid $100.00 to root when devs have root included with a rom? That's probably the more important issue lol
dipstik said:
this is the normal bootloader unlocked screen:
View attachment 4667879
Click to expand...
Click to collapse
Right ok thats what i see on my screen then higher up on the screen it says press power to pause, thats it, ok so if that normal that i think im good then if im not mistaken.
Ill make another forum on questions about root, and what can i do with it to make my phone better, as everyone says.
biggiesmalls657 said:
And my question is you paid $100.00 to root when devs have root included with a rom? That's probably the more important issue lol
Click to expand...
Click to collapse
I did not know, people put up tutorials and they seem detailed but small things are missing from it that you guys expect some people to know but they dont, im coming from iPhone so certain things, i dont get. i just got tired of trying and went to onclickroot.com
Dasin said:
I did not know, people put up tutorials and they seem detailed but small things are missing from it that you guys expect some people to know but they dont, im coming from iPhone so certain things, i dont get. i just got tired of trying and went to onclickroot.com
Click to expand...
Click to collapse
It's understandable but 100.00 dollars to me for something software related seems to good to be true unless it's a big name like Microsoft. Lol at least you know for next time
Badger50 said:
That message is normal for all of us with bootloader unlocked pixel devices. You can check root status with an app like this one :good:
https://play.google.com/store/apps/details?id=technarcs.rootchecker
Click to expand...
Click to collapse
Yeah i checked it, im rooted, so i guess everything is fine, thanks for the help with that i was beginning to worry.
biggiesmalls657 said:
It's understandable but 100.00 dollars to me for something software related seems to good to be true unless it's a big name like Microsoft. Lol at least you know for next time
Click to expand...
Click to collapse
I just wanted to root it and get it over with. Now i have to figure if there are root apps like IOS like backgrounder that leaves apps open in the background, or a rooted app that can tell me what tower im on and the band etc... I already posted a thread about my questions, i dont want to misguide this thread, thanks to you all.
Dasin said:
Yeah i checked it, im rooted, so i guess everything is fine, thanks for the help with that i was beginning to worry.
I just wanted to root it and get it over with. Now i have to figure if there are root apps like IOS like backgrounder that leaves apps open in the background, or a rooted app that can tell me what tower im on and the band etc... I already posted a thread about my questions, i dont want to misguide this thread, thanks to you all.
Click to expand...
Click to collapse
No worries man, you are gonna have fun! Pixels are way more fun than iPhone. Androids allow you to modify deep in the hardware, CPU speed, governor's, and kernels. Apple won't let you touch that stuff because it is closed source code. Google is obviously open source. Just don't Kang lol. I helped these forums for years until I made the mistake of buying a Verizon pixel 2 which was factory locked by Verizon. Greenify is a good root app. Macrodroid is another. If you do decide to modify, know that there are risks with all of these tweaks. You could potientally set your CPU or GPU on fire or your wife will tell at you! Lol Lots of experienced people including myself are here to help you at any point.
---------- Post added at 09:31 PM ---------- Previous post was at 09:31 PM ----------
Great app for cell towers is LTE Discovery as well
Dasin said:
Yeah i checked it, im rooted, so i guess everything is fine, thanks for the help with that i was beginning to worry.
I just wanted to root it and get it over with. Now i have to figure if there are root apps like IOS like backgrounder that leaves apps open in the background, or a rooted app that can tell me what tower im on and the band etc... I already posted a thread about my questions, i dont want to misguide this thread, thanks to you all.
Click to expand...
Click to collapse
Cool beans bruh. Now don't forget to hit that TANKS button to all those that help you on your way! :good
Dasin said:
I did not know, people put up tutorials and they seem detailed but small things are missing from it that you guys expect some people to know but they dont, im coming from iPhone so certain things, i dont get. i just got tired of trying and went to onclickroot.com
Click to expand...
Click to collapse
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + December 2018 Security Patch
Welcome to the family @Dasin. If you're willing to learn you'll have a lot more fun with andriod phone than you ever will work an iPhone. There's lots of good guides and better yet, lots of good people to help you. You've already met some of the best in this forum. Good luck and have fun.
Sent from my [device_name] using XDA-Developers Legacy app