Related
There are a lot of people joining xda on daily basis, and there are a lot of repetitive questions being asked which fill up Development threads. Point them here. Feel free to ask or answer questions. Idea of this thread is to get users to help other users with their problems/questions. Please do not spoon feed, but rather point in the direction where that user can find an answer and educate himself
First thing first. I strongly advise you to read THIS thread before posting ANYTHING on XDA.
Then, have a quick look at the names of threads in post no2, you might find what you need right away.
For ROM issues please do mention in your post about:
ROM name
ROM version and base
kernel version and its settings
any mods applied on top of it
flashing "style" aka dirty or clean
something like this
...and be sure you have asked before on the ROM thread unless you have less than 10 posts on XDA
Third. Even if you do get your question answered, please, do come back and read threads in post no2 (coming later as soon as we start getting the guides) to educate yourself. You'll be surprised how much time and frustration it will save you in the future.
ASK ANY QUESTION HERE,adb, drivers, superCID etc...... You will either get an answer or will get pointed in the right direction.
No abuse towards noobs tolerated here! No question is stupid in this thread.
***I feel that a little OT is healthy to the success of this type of thread. The people here who help the most will develop a comradery therefore OT is allowed within reason. Common sense will be applied ***
Credits to @xanthrax who made the original nexus 4 thread where i got inspired! :highfive:
Great idea!!! And well needed! :good::good:
Darth said:
Great idea!!! And well needed! :good::good:
Click to expand...
Click to collapse
Thanks i hope we can fill this up quickly! Just share it!
Enviado desde mi XT1060 mediante Tapatalk
Sorry I am a noob.
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
4yush said:
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
Click to expand...
Click to collapse
yes, you will get the update. but the installation fails
I have got tired of waiting for official update and have decided to root my moto x on 4.4.4.
This is what I understood.
1 . unlock bootloader
2. Install twrp
3. Install rom.
I would want to know if I can flash BlissPop directly after the above steps.
Also can kernels be flashed directly from recovery or they have to be flashed using pc like my xperia did
4yush said:
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
Click to expand...
Click to collapse
To root on 4.4.4 you need an unlocked (or unlockable) bootloader. An unlocked bootloader phone roots by flashing custom recovery.
If you try to take an OTA without stock recovery on your phone, you'll get stuck in a bootloop (fastboot earase cache will get you out of it), and can not apply an OTA. Further, if while rooted you modify /system, certain files, or other parts of the phone too much while rooted, the OTA could fail its pre-flash validation checks, thus preventing it from installing.
Then again, those who use SlapMyMoto/RockMyMoto/PwnMyMoto or other HACKS to root their phone with locked bootloader, could also run into issues with the OTA's pre-flash validation checks causing the OTA Update to fail too. However, those old processes don't work on 4.4.4 as the vulnerabilities they used are patched.
If you have an unlocked bootloader, root your phone by flashing TWRP (or CWM, etc) and installing SuperSU, then flash stock recovery back on, and run rooted with apps installed that use root, like RootExplorer, Wifi Tether for Root, Greenify, etc. You can take the OTA just fine.
Note: If you install something like Xposed, it will cause the Pre-flash vaildations to fail because it does modify things the pre-flash checks look for. You'd have to disable it, which involves having 3rd party recovery, and flashing the disable.zip (on your phone as /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip), then put stock recovery back on.
adity said:
I have got tired of waiting for official update and have decided to root my moto x on 4.4.4.
This is what I understood.
1 . unlock bootloader
2. Install twrp
3. Install rom.
I would want to know if I can flash BlissPop directly after the above steps.
Also can kernels be flashed directly from recovery or they have to be flashed using pc like my xperia did
Click to expand...
Click to collapse
If BlissPop is a custom ROM then yes after all of those steps you can flash it directly, I'll suggest to make a nandroid backup before. And then to get some gapps for that ROM. And kernels can be flashed directly on recovery too! Good luck!
Enviado desde mi XT1060 mediante Tapatalk
Should this have to be sticky?
Enviado desde mi XT1060 mediante Tapatalk
Using blisspop which is based on cm12 and mobile standby is using abnormal amounts of battery(75%)
{
"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"
}
adity said:
Using blisspop which is based on cm12 and mobile standby is using abnormal amounts of battery(75%)
Click to expand...
Click to collapse
I think battery life on custom ROM is very bad compared to stock, I'm back at it because of that and for moto features.
Enviado desde mi XT1060 mediante Tapatalk
Making a bump to everyone can see this post!
Enviado desde mi XT1060 mediante Tapatalk
Moto X - No Signal?
So I got the Verizon XT1060 a couple of days back, put my SIM in and everything was working fine for a couple of days. Made a few calls, texted a bunch. Everything was good.
Never really got a chance to check how data worked since I was always on WiFi but yesterday when I tried making the mobile internet work it just wouldn't . I have a 3G connection, so I thought might as well give it a shot and started putting in the APNs in according to what my provider said. I came across a post that said you can't select just 3G for the XT1060 and you'd have to install this app called PhoneInfo(Ad) to make 3G only work.
So I installed the app. Set it to WCDMA only. And restarted the phone. Ever since then my phone has been on no-signal. Can't make calls/texts. No bars. I can read stuff on the SIM card just fine though. Today I went and got a new SIM Card hoping it'll work. But nothing. Zilch. Factory reset multiple times. Just no signal at all. In About Phone, in status information, the network shows up as unknown.
I don't exactly know what the problem is here. I talked to my provider and they said everything was fine on their end and I should check if my model is compatible. Which it is. At least for EDGE, if not for 3G. If phone was receiving signals and all before, then that definitely means it was compatible, right?
Any way. I'm based in Islamabad, Pakistan. And the phone is a Verizon XT1060 16GB. This is the only phone I have right now and I REALLY need to get this phone working asap.
I'm going to try and flash the stock image onto it. The phone was running stock VZW 4.4.4 and is not the dev edition. So I can't root.
Any suggestions or ideas are welcome.
Thank You.
NadirChaudhry said:
So I got the Verizon XT1060 a couple of days back, put my SIM in and everything was working fine for a couple of days. Made a few calls, texted a bunch. Everything was good.
Never really got a chance to check how data worked since I was always on WiFi but yesterday when I tried making the mobile internet work it just wouldn't . I have a 3G connection, so I thought might as well give it a shot and started putting in the APNs in according to what my provider said. I came across a post that said you can't select just 3G for the XT1060 and you'd have to install this app called PhoneInfo(Ad) to make 3G only work.
So I installed the app. Set it to WCDMA only. And restarted the phone. Ever since then my phone has been on no-signal. Can't make calls/texts. No bars. I can read stuff on the SIM card just fine though. Today I went and got a new SIM Card hoping it'll work. But nothing. Zilch. Factory reset multiple times. Just no signal at all. In About Phone, in status information, the network shows up as unknown.
I don't exactly know what the problem is here. I talked to my provider and they said everything was fine on their end and I should check if my model is compatible. Which it is. At least for EDGE, if not for 3G. If phone was receiving signals and all before, then that definitely means it was compatible, right?
Any way. I'm based in Islamabad, Pakistan. And the phone is a Verizon XT1060 16GB. This is the only phone I have right now and I REALLY need to get this phone working asap.
I'm going to try and flash the stock image onto it. The phone was running stock VZW 4.4.4 and is not the dev edition. So I can't root.
Any suggestions or ideas are welcome.
Thank You.
Click to expand...
Click to collapse
Do you know which exactly are the bands your network uses? And I have stock ROM too and I get the 3G only option without the use of an external app. See here.
Enviado desde mi XT1060 mediante Tapatalk
Used Moto X What to look at.
Hello! (second post after saying hello on the corresponding post).
Please my native language is spanish so forgive my mistakes if any.
Going to the point and abusing the "ask ANY question" theme,
¿What to look in a Used Moto x?
In other words, here in Argentina phone are really expensive, and i have the chance to buy a Moto x really cheap.
Besides the obvious scraches, marks, screen details, and checking battery status and life. What else should i look? Any specific serial, date of production? any data?
Also i ad one more question.
As far as i understood with this post http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 if i have a 4.4.4 Phone all will be useless since there is no Rooting or bootunlock.
In any other cases there is some way to get root acess and also could get bootunlock (did i understood correctly?)
Also Unlocked boot would give me the chance to install a new operating system (Cyanogen mod or whatever)
Root would only give me the chance to uninstall app and so.
Thanks for all your answers!
Kind Regards!
cabe72000 said:
Besides the obvious scraches, marks, screen details, and checking battery status and life. What else should i look? Any specific serial, date of production? any data?
Click to expand...
Click to collapse
I've seen no evidence that any date range or serial number range is better than another.
One thing i would look for is... If you have the option to find out what ROM and bootloader is on the phone, that is helpful.
ROM: On the phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
Bootloader: check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
The android version and bootloader version should match, otherwise it means someone was experimenting when they were flashing, and if you buy that phone you definitely make sure you fully flash the correct SBF onto the phone to bring everything in line. (I would ask the owner to do it BEFORE you buy, so if something goes wrong while flashing, you aren't the one bricking the phone).
cabe72000 said:
As far as i understood with this post http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 if i have a 4.4.4 Phone all will be useless since there is no Rooting or bootunlock.
In any other cases there is some way to get root acess and also could get bootunlock (did i understood correctly?)
Also Unlocked boot would give me the chance to install a new operating system (Cyanogen mod or whatever)
Root would only give me the chance to uninstall app and so.
Click to expand...
Click to collapse
Read further in that thread... like what I posted -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
So when you get your X, try to get the unlock code from Moto's web site. Then.... If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
Moto gives the bootloader unlock code for most 2013 X's, its only a few carriers they don't give them for.
For Example: While Moto doesn't give out the Unlock Code for the ATT XT1058, they do give out the unlock code for the XT1058 from Rogers in Canada. So if you are buying a used Rogers XT1058 you can unlock the bootloader for free. The same holds true with nearly every XT1052, XT1053, and XT1056 I've seen (moto gives the bootloader unlock code on their web site).
Another thing to keep in mind, IF you get a model from a carrier that Moto doesn't give out the bootloader unlock code for, If the phone and its bootloader are still on 4.4.2/30.B4 or below, you can use Sunshine to unlock the bootloader.
Unlocking the bootloader will allow you to flash 3rd party or custom Recoveries, Roms, parts, etc. (so CM12, etc) With a locked bootloader, you can only flash ROMS/Parts which have been digitally signed by Moto and are for your particular Phone Model and Carrier combo. (The CID comes into play).
Rooting will allow you some access and control over /system and other files that are usually inaccessible to normal users. It doesn't allow you to flash 3rd party roms and pieces,etc. If you have a LOCKED bootloader, you basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It , if you want root. Right now, with 4.4.4 and a locked bootloader, there are no vulnerabilities which can gain root, that is why having an unlocked or unlockable bootloader is so important. For more see -> http://mark.cdmaforums.com/MotoX-Locked.html
KidJoe said:
I've seen no evidence that any date range or serial number range is better than another.
One thing i would look for is... If you have the option to find out what ROM and bootloader is on the phone, that is helpful.
ROM: On the phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
Bootloader: check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
The android version and bootloader version should match, otherwise it means someone was experimenting when they were flashing, and if you buy that phone you definitely make sure you fully flash the correct SBF onto the phone to bring everything in line. (I would ask the owner to do it BEFORE you buy, so if something goes wrong while flashing, you aren't the one bricking the phone).
Read further in that thread... like what I posted -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
So when you get your X, try to get the unlock code from Moto's web site. Then.... If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
Moto gives the bootloader unlock code for most 2013 X's, its only a few carriers they don't give them for.
For Example: While Moto doesn't give out the Unlock Code for the ATT XT1058, they do give out the unlock code for the XT1058 from Rogers in Canada. So if you are buying a used Rogers XT1058 you can unlock the bootloader for free. The same holds true with nearly every XT1052, XT1053, and XT1056 I've seen (moto gives the bootloader unlock code on their web site).
Another thing to keep in mind, IF you get a model from a carrier that Moto doesn't give out the bootloader unlock code for, If the phone and its bootloader are still on 4.4.2/30.B4 or below, you can use Sunshine to unlock the bootloader.
Unlocking the bootloader will allow you to flash 3rd party or custom Recoveries, Roms, parts, etc. (so CM12, etc) With a locked bootloader, you can only flash ROMS/Parts which have been digitally signed by Moto and are for your particular Phone Model and Carrier combo. (The CID comes into play).
Rooting will allow you some access and control over /system and other files that are usually inaccessible to normal users. It doesn't allow you to flash 3rd party roms and pieces,etc. If you have a LOCKED bootloader, you basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It , if you want root. Right now, with 4.4.4 and a locked bootloader, there are no vulnerabilities which can gain root, that is why having an unlocked or unlockable bootloader is so important. For more see -> http://mark.cdmaforums.com/MotoX-Locked.html
Click to expand...
Click to collapse
Thanks for your answer!!
Im sure that the actual owner knows nothing about Android, what im trying to say is that he didn't even know how to root or check software updates.
Besides that, what you answered to me is what i was looking for. On monday i have access to the phone so i will check everything you told me.
Tell you the news on Monday.
Muchas gracias!! (Thank you very much)
EDIT: Kidjoe Where do you work to have such a list of phones??? I work on Automotive industry and i drive maybe 5 o 6 cars but your's is incredibly long! hehe (sorry offtopic but i was amazed with the list )
cabe72000 said:
EDIT: Kidjoe Where do you work to have such a list of phones??? I work on Automotive industry and i drive maybe 5 o 6 cars but your's is incredibly long! hehe (sorry offtopic but i was amazed with the list )
Click to expand...
Click to collapse
I've been using cell phones since 1992... There was a period in there, for personal, that I was part of a Verizon Wireless customer "focus group" known as the VerizonWireless Customer Council, so many of my PERSONAL phones were acquired that way (for free).
Long story short... I worked for one global company for just a week shy of 20 yrs. While always a field employee needing mobility to do my job, for about the last 7 or 8 years, my focus was shifted to doing a lot of work in the mobility support space. The current company I'm working for (also global), I've been a part of the Tier 3/4 Mobility Support team, supporting our network, MDM solution, etc for our employees. We also take part in the design... so I have to have all, or as many as I can, of the devices we allow our employees to have. I often times joke that my job is being paid to play with my toys
KidJoe said:
I've been using cell phones since 1992... There was a period in there, for personal, that I was part of a Verizon Wireless customer "focus group" known as the VerizonWireless Customer Council, so many of my PERSONAL phones were acquired that way (for free).
Long story short... I worked for one global company for just a week shy of 20 yrs. While always a field employee needing mobility to do my job, for about the last 7 or 8 years, my focus was shifted to doing a lot of work in the mobility support space. The current company I'm working for (also global), I've been a part of the Tier 3/4 Mobility Support team, supporting our network, MDM solution, etc for our employees. We also take part in the design... so I have to have all, or as many as I can, of the devices we allow our employees to have. I often times joke that my job is being paid to play with my toys
Click to expand...
Click to collapse
My wife has forbid me to get another phone for a couple years.... Lol
Moto X, N5 and M8 in a year. Though, she's in love with the hand me down moto X... It finally got her off her iPhone 4s. So she benefited from my whims.
So I'm stuck for awhile. ?
I did find a solution to the battery problem.
Thing is google keeps data on even when wifi is connected for the handofff feature. So I make sure that I turn off data while at home.
Since then I have been having great battery life.. Even better than stock, more than 4 hours screen time
Hi!
Anyone who have heard anything about Googles thoughts on the forced encryption on the Nexus 6? Will they ever let us choose if we want it or not? I dont want to root and void the warranty on the phone but the performance is sluggish at times and most ppl say that is because of the encryption.
Br J
We can only guess but I suspect not.
Jaxione said:
Hi!
Anyone who have heard anything about Googles thoughts on the forced encryption on the Nexus 6? Will they ever let us choose if we want it or not? I dont want to root and void the warranty on the phone but the performance is sluggish at times and most ppl say that is because of the encryption.
Br J
Click to expand...
Click to collapse
Please don't take this as offense but why get a nexus device if u don't want to root? if your worried about voiding warranty all u have to do is return to stock/Unroot/Lock Bootloader back up and then you good.
Jaxione said:
Hi!
Anyone who have heard anything about Googles thoughts on the forced encryption on the Nexus 6? Will they ever let us choose if we want it or not? I dont want to root and void the warranty on the phone but the performance is sluggish at times and most ppl say that is because of the encryption.
Br J
Click to expand...
Click to collapse
No they've stated that they suggest all devices going forward are encrypted. Obviously OEM's can do what they want but that's not going to be an option on the Nexus side.
the_rooter said:
Please don't take this as offense but why get a nexus device if u don't want to root? if your worried about voiding warranty all u have to do is return to stock/Unroot/Lock Bootloader back up and then you good.
Click to expand...
Click to collapse
I have had some bad experiences with rooting and Im afraid to damage the device. Thats probably why Im afraid of the rooting process. No offense taken
Br J
Jaxione said:
I have had some bad experiences with rooting and Im afraid to damage the device. Thats probably why Im afraid of the rooting process. No offense taken
Br J
Click to expand...
Click to collapse
If you ever need a step my step on doing so there is a video that i followed on youtube. There are many that does wonders. I can also offer a helping hand in doing so. I know how to do fasboot/adb method also I tried the WUG Toolkit which many people blast tool kits, but i come to enjoy it. I have made mistakes in rooting/unlocking bootloaders but thats mainly because I didnt fully read before I started. If your concerned check out WUG Tool kit here, and also this youtube channel does wonders.
https://www.youtube.com/watch?v=XBIPQVDfAQ8
Rootjunky channel on youtube. The guy has awesome videos and he does step by step. If interested I can even offer some help and guidance. Pm me.
Jaxione said:
I have had some bad experiences with rooting and Im afraid to damage the device. Thats probably why Im afraid of the rooting process. No offense taken
Br J
Click to expand...
Click to collapse
You don't need to be rooted in order to remove encryption. But you do need to format all data.
Unlock in Fastboot (all data wiped automatically)
Flash TWRP 2.8.5.0 in Fastboot
Flash kernel in TWRP without encryption flag (LeanKernel or franco, to name a few)
In TWRP - Wipe -> Factory Reset, then Wipe -> Format Data -> (yes) to confirm format
Fastboot flash all but the boot.img from the latest factory image
NotATreoFan said:
You don't need to be rooted in order to remove encryption. But you do need to format all data.
Unlock in Fastboot (all data wiped automatically)
Flash TWRP 2.8.5.0 in Fastboot
Flash kernel in TWRP without encryption flag (LeanKernel or franco, to name a few)
In TWRP - Wipe -> Factory Reset, then Wipe -> Format Data -> (yes) to confirm format
Fastboot flash all but the boot.img from the latest factory image
Click to expand...
Click to collapse
Ok thanks. But how will this affect my warranty?
Br J
It doesn't with a Nexus device.
As long as you can flash back stock your warranty is intact.
I had TWRP recovery, custom kernel and some ROM tweaks first thing this morning. Then I flashed everything back to stock and sent it in for warranty repair today.
Jaxione said:
Ok thanks. But how will this affect my warranty?
Br J
Click to expand...
Click to collapse
Unlocking a Nexus device will not void the warranty. If your only desire is to remove encryption, you could even go back to stock recovery and relock the device afterward.
NotATreoFan said:
Unlocking a Nexus device will not void the warranty. If your only desire is to remove encryption, you could even go back to stock recovery and relock the device afterward.
Click to expand...
Click to collapse
Well hold on. I've no idea how moto handle warranty...
But on the nexus 5, if you bought from play store, Google handled warranty. Even if it was unlocked... Like the law in many places suggest.. However if you bought from somewhere else. LG handled the warranty but they would refuse it if it was unlocked or tamper flag tripped...
Now the 6 does t seem to have a tamper flag and I'm not sure how moto do things vs LG, but saying "Nexus device" insinuates all of them but that would not be accurate.
rootSU said:
Well hold on. I've no idea how moto handle warranty...
But on the nexus 5, if you bought from play store, Google handled warranty. Even if it was unlocked... Like the law in many places suggest.. However if you bought from somewhere else. LG handled the warranty but they would refuse it if it was unlocked or tamper flag tripped...
Now the 6 does t seem to have a tamper flag and I'm not sure how moto do things vs LG, but saying "Nexus device" insinuates all of them but that would not be accurate.
Click to expand...
Click to collapse
You may be correct. I am speaking from the Google side, as well as T-Mobile. I've spoken to their service reps and they will issue RMAs for unlocked Nexus devices.
NotATreoFan said:
You may be correct. I am speaking from the Google side, as well as T-Mobile. I've spoken to their service reps and they will issue RMAs for unlocked Nexus devices.
Click to expand...
Click to collapse
Yep Google are definitely good. That's why I bought from play this time. Moto may also be good - I don't know. But lg on the 5 I hope are not setting a trend
I didnt buy the Nexus 6 for the flashing, rooting and unlocking. I bought it because I wanted a clean Android experience and because I think the Nexus 6 is a handsome looking phone. Found this article: http://www.droid-life.com/2014/11/20/i-didnt-buy-a-nexus-to-flash-all-the-things/
Thats exactly how I see it even though I didnt write the article. But it makes me pissed that google is forcing encryption on us for no reason.
Br J
Jaxione said:
I didnt buy the Nexus 6 for the flashing, rooting and unlocking. I bought it because I wanted a clean Android experience and because I think the Nexus 6 is a handsome looking phone. Found this article: http://www.droid-life.com/2014/11/20/i-didnt-buy-a-nexus-to-flash-all-the-things/
Thats exactly how I see it even though I didnt write the article. But it makes me pissed that google is forcing encryption on us for no reason.
Br J
Click to expand...
Click to collapse
Its not for no reason. Its for security. Its to become a viable alternative to apple in the corporate world.
rootSU said:
Its not for no reason. Its for security. Its to become a viable alternative to apple in the corporate world.
Click to expand...
Click to collapse
Completely agree.... It was most certainly done for A REASON.
Just like Samsung's KNOX was done for A REASON...
Some people may not like the reason because it doesn't meet their particular needs, but that's another story...
JasonJoel said:
Completely agree.... It was most certainly done for A REASON.
Just like Samsung's KNOX was done for A REASON...
Some people may not like the reason because it doesn't meet their particular needs, but that's another story...
Click to expand...
Click to collapse
Indeed. I hate encryption but I also love rooting and flashing so I'm good..
Lets set one thing straight; the only DOWNSIDE to encryption, is the performance hit, and that is because they are using SOFTWARE CRYPTO. Qcom didn't have the code for hardware crypto published on time for the N6 ship date, but it is now, which means that there is a good potential for THAT to be added at some point. IMO, it is MUCH more likely that they will add hwcrypto than to fall back to allowing you to run unencrypted.
Just talked with Motorola. I was thinking about rooting the device but after the talk with Motorola Im not going to. They said I will void the warranty when rooting.
Br J
derp.. my mistake :angel:
Hi I have a DROID Turbo that currently has the MOFO Rooted ROM installed. I have to send my in for the screen replacement, but need to remove the Root as this voids the warranty. I have went to the SU app and clicked on the remove root, but am unsure if that is all I need to do besides wiping my cell.
raxhunter said:
Hi I have a DROID Turbo that currently has the MOFO Rooted ROM installed. I have to send my in for the screen replacement, but need to remove the Root as this voids the warranty. I have went to the SU app and clicked on the remove root, but am unsure if that is all I need to do besides wiping my cell.
Click to expand...
Click to collapse
I had to use the screen replacement last summer for my first Turbo, which was purchased from Verizon around Thanksgiving 2014. I never took an OTA update and got MOFO root as soon as it came out. I'm not sure if this works for everyone, but the only way I was able to have the "Modified" Software status on bootloader changed to Unmodified before I sent it back for replacement was to plug it into a windows computer with Verizon's Upgrade Assistant installed, wipe everything and reset to factory (backup anything you want to save first), and let it update. I couldn't read the screen but after letting the busted phone update, I do remember somewhere within the Verizon application it stated the software status was Unmodified (or what ever else it's supposed to say).
Not sure if it will work for you but it's something to try.
Thank you for the info... I'll give it a try
raxhunter said:
Thank you for the info... I'll give it a try
Click to expand...
Click to collapse
If that doesn't work, you might have to purchase moforoot or Sunshine in order to flash an unrooted image, and to get rid of the Modified line.
I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance
raxhunter said:
I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance
Click to expand...
Click to collapse
I'm not sure about this article's reliability, but it looked like it could help you.
Or you can download these files for the appropriate firmware version and flash them after unlocking with Sunshine.
Your best bet would be to flash the stock system image with mofo. Unfortunately, I was unable to find the flashable moforoot unrooted image.
I'm unsure if this would change the Modified line to Unmodified; if it doesn't than I have no idea.
Additionally, Motorola offers a repair service where you can send in a device to be repaired either for a small fee or for free. With the paid option, they don't inspect the actual device, and they send you a new phone. This could be used as a last resort.
I tried the article... The downgrade didn't work... I'll see if sunshine will work...
The sunshine one is the same one I tried earlier from rootjunky... The software line in the boot still sez modified, but the software in the about phone area sez official.. Dunno...
You might have to just use the Motorola service. Why do you want to get rid of the Modified line, again?
raxhunter said:
I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance
Click to expand...
Click to collapse
Factory reset, then use the Verizon update tool? Wait for it to actually finish? It probably takes a long time.
Sent from my XT1254 using Tapatalk
Latiken said:
You might have to just use the Motorola service. Why do you want to get rid of the Modified line, again?
Click to expand...
Click to collapse
The screen is cracked, VZW will replace the screen for free if phone is less then 1yr old, but in the return box there is a clause for modified software that won't cover the broken screen.
SpyderPride said:
Factory reset, then use the Verizon update tool? Wait for it to actually finish? It probably takes a long time.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
That's what I tried... It gets to about packet 17 of 20 then the screen sez lost communication... It's weird because onbthe cell is sez USB connected...
raxhunter said:
The screen is cracked, VZW will replace the screen for free if phone is less then 1yr old, but in the return box there is a clause for modified software that won't cover the broken screen.
Click to expand...
Click to collapse
You don't have to use Verizon's service. There's two options you can use, both from Motorola: a paid one and a free one. The link is in one of my previous posts.
Someone on the forum said that with the paid option, they send you a new (or very well refurbished) Turbo without looking at your current device (so they wouldn't penalize you for it being modded.)
The free option is a bit more iffy. The same someone said that they check the device, but Motorola didn't specify if they check the software, or just the hardware.
The paid option would be your best bet, but you can opt for the free option if you feel a bit risky.
newbie warning: don't re-lock bootloader, and beware flashing any custom ROM. &OTA...
only modify a phone you are willing to throw away.......
##
pre-note: TWRP 3.3.1-0 -> fastboot boot twrp.img (this is temporary)
before doing anything, backup some little partitions: EFS, fsg, Vendor. Maybe others. You will need these to get back to a working stock.
##
$$
DO AT YOUR OWN RISK - I TAKE NO RESPONSIBILITY.
note added 2-27-2020: it may be that some problems with returning to stock are due to not (in TWRP) advanced wiping data, system, dalvik ART cache before flashing. You can do temp "fastboot boot twrp-3.3.1-0-payton.img" w/o quotes, and do it there. -changed/edited. don't use TWRP to flash a stock zip!
$$
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
newbie warning: don't re-lock bootloader, and beware flashing ANY custom ROM.
On the X4, the bootloader changes drastically between 8 and 9 as it introduces a dual file system which is used by OTA updates to alternate the live system, and as a backup if failure. It is not a true Treble system, only partial. You must not depend on being able to flash back and forth between O and P. If you update to P, stay there. I expect this to be exacerbated by those phones which update to 10, if that in fact happens(probably One/fi only). There is also much confusion as to which file system/setup any custom ROM uses, and thus, how you would get back to stock, if that is even possible. Be very careful and assure yourself that you are fully willing to lose permanently your new phone before you do anything. Please read posts in these forums.
I've seen many posts of folks, mostly noobs, who have flashed ANY custom ROM Lineage and are unable to get back to a working stock. Sounds super simple but apparently it's not. Best to assume that if you try things, especially Lineage, that you will never be able to get back to a working stock. Read a bunch of posts here and you will realize that.
I've also seen a bunch of folks on this phone, and other phones who have run a bat file to flash their phone which contains the line
"fastboot oem lock" or similar.
Don't do it!!! - This will lock your phone and you will never be able to do anything with it again. It is totally unnecessary to lock your phone. Folks who should know better are leaving bat files lying around with this command. If you use one of those bat files to flash your phone, just check and remove that command line. Else you will have destroyed your phone. That's one of those things that "sounds good" until you do it.
EDIT: You can run stock on a bootloader unlocked phone - I do it all the time - plays PoGo just fine. I don't know about banking apps - I don't use them as I assume any 10-year-old can and will hack my phone.
EDIT: 6Feb2020: folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
EDIT: this was successfully fixed. see: https://forum.xda-developers.com/moto-x4/help/ota-update-endless-fail-loop-ppws29-69-t4045771 my guess is only works if you haven't changed bootloader or file system - NO custom ROM.
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
Please do a lot of reading here before you try to modify your phone, unless you are totally willing to render it useless. A word to the wise.
Ahah ))) I bought today X4 with relocked BL and I it seems it was relocked after flashing LOS or similar )) )
Now I trying to recover it ))
Сan we boot phone to QC9008 (EDL) mode without testpoiint?
St.Noigel said:
Ahah ))) I bought today X4 with relocked BL and I it seems it was relocked after flashing LOS or similar )) )
Now I trying to recover it ))
Сan we boot phone to QC9008 (EDL) mode without testpoiint?
Click to expand...
Click to collapse
afaik, you can't. Return the phone and get your money back. There will probably be a bunch of these worthless phones put up for sale. If you can't return it you could try the suggestions of sd_shadow in other threads here, but I don't believe they were successful on the X4.
KrisM22 said:
afaik, you can't. Return the phone and get your money back. There will probably be a bunch of these worthless phones put up for sale. If you can't return it you could try the suggestions of sd_shadow in other threads here, but I don't believe they were successful on the X4.
Click to expand...
Click to collapse
OK. But I unbrick it. Now I have fully loaded system, but without WiFi ot mobile network.. It`s problem - I can`t turn on OEM unlocking.. (
Goшng to try to find solution
UPD. Everything work well now. But it my device I have custom stock flashed. Not sure it`ll work with LOS onboard
its to late for me
llue45 said:
its to late for me
Click to expand...
Click to collapse
Yeah, I know. You're one reason I posted this.
modified OP
change: from "Lineage" to "any custom ROM"
hi im thinking about buy this phone for 100 bucks used how i can verify this relocked bootloader problem ? in Developer Options ? if i cant switch to Oem Unlocking its broken ? to make sure this dont happen to me the one who its selling it to me says that already its updated to PIE , i want stock and root it just that after unlock the bootloader but if cant be unlocked i better move on . so my question is what really im looking for , when i get my hands on the phone before drop my money to the thin air because is not a store . and maybe never see this guy again in my life , i Live In The Caribbean Dominican Republic
People here are not so trusty . so i will appreciate if i can have some tips to know if im going to do a good Buy. Thanks In Advance .
JavaShin said:
hi im thinking about buy this phone for 100 bucks used how i can verify this relocked bootloader problem ? in Developer Options ? if i cant switch to Oem Unlocking its broken ? to make sure this dont happen to me the one who its selling it to me says that already its updated to PIE , i want stock and root it just that after unlock the bootloader but if cant be unlocked i better move on . so my question is what really im looking for , when i get my hands on the phone before drop my money to the thin air because is not a store . and maybe never see this guy again in my life , i Live In The Caribbean Dominican Republic
People here are not so trusty . so i will appreciate if i can have some tips to know if im going to do a good Buy. Thanks In Advance .
Click to expand...
Click to collapse
Good to not be trusting!!!! With this (or any) phone, I recommend you get only from a place (like ebay) where you can easily return it and get your money back. ebay can force a reluctant seller to refund your money. Assure that the seller has a 99% + rating and says they will accept returns and pay for return shipment, usually for 30 days. I don't think you can easily tell if it has been unlocked and re-locked - only that it works perfectly, or doesn't. You can check the ID of the ROM in your phone against the latest for your area by checking lolinet.
When you get it, check all functions and assure IMEI is present. check wifi, BT, etc etc. Make calls. Check that the phone works with the towers in your area and with a local SIM. etc etc. read here and find the things that folks having problems where it won't do things and assure your phone will do it. Install Pokemon Go on it and play it briefly to assure your phone hasn't been modified. I have no idea if any of these phone will work with any banking or payment apps, and each app will have it's own specific checks that it performs against the phone. Test what you will use. Fully. ASSUME NOTHING!!!
As far as rooting it and/or unlocking it, I would strongly advise against it. For this particular phone X4 I would determine that it works perfectly and then NOT modify it. Unless, of course, you are willing to throw your phone away and buy a new one without a second thought(most of us don't have that kind of money!). Mine happened to have been unlocked when I got it from ebay but it was on a stock 8.1 and it was able to, and did OTA update to the latest Pie stock ROM. Thus I was easily able to assure if was okay. It being unlocked seems to have affected nothing. I have never tried to root it or do anything to it (recovery or otherwise) as I read far too many posts of folks here who had rendered their phones incapable of returning to a working stock, and only on a limited custom. Not what I wanted. I have not heard of anyone successfully getting one of these phones back to a FULLY WORKING stock state.
The days of getting a phone and easily modifying it and then returning it to stock may be gone. Get a phone you will enjoy, and use it! Unmodified!!! Welcome to pre-Treble part1a . Expect a few years of growing pains.
I like my phone and enjoy not having to worry about whether a custom ROM will work and constantly be chasing updates and fixes. I use a case - I believe it is this one
https://www.ebay.com/itm/For-Motoro...hash=item33d89fee5a:m:mU5XV7jSj1TfD_kr-L4VT9g
which, so far, has protected it from several minor falls. I would never use any phone w/o a case!!!
But i think if the phone gets unlocked the bootloader and flash twrp making a backup of the stock recovery before just booting the twrp custom recovery then flash magisk on twrp on top of Stock PIE , After Of Course Make A Full Backup Of all partitions reboot and then on Stock PIE have ROOT. and never flash custom roms and never lock the bootloader and stock can be reflashed without problems with a script on linux with fastboot on bootloader-fastboot mode this plan can work , NO ? i had a E4 sprint and never had problems doing that
I need root for A Lot Of Things like Xposed Drivedroid Youtube vanced Adway ETC.
Can Anyone who is reading this have done this just root pie on this phone with unlocked bootloader ? and able to restore stock flashing it back with the retail firmware just to remove root and clean the stock and recovery ? or try to put android one ? the phone which im going to buy its the XT1900-6 retail brazil i already have the retail stock official pie rom ready to flash and with the script on linux with no fastboot oem lock anywhere .
added to OP: EDIT: 2-6-2020 folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
OTA issues
KrisM22 said:
added to OP: EDIT: 2-6-2020 folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
Click to expand...
Click to collapse
I posted a new thread on these OTA issues with the X4 at https://forum.xda-developers.com/moto-x4/help/ota-update-endless-fail-loop-ppws29-69-t4045771. I was never presented with an "option" to install the latest OTA, it just automatically attempted to install (apparently a FORCED update) and is continuing to do so and failing ad infinitum. That phone works, just getting constant failure notifications. Question is, how to stop the attempted updates?
The second identical phone (updated per Magisk OTA tutorial instructions) is borked, with no phone connectivity. Can these be recovered by wiping/flashing stock rom PPWS29.60-39-6-2 and get them operating again as stock? I can forego the OTAs if there's a way to stop them from screwing up the device.
I never had other than stock recovery on either of these phones, I always boot TWRP via fastboot to do mods.
EDIT: XDA system is stalling and caused double post. Sorry. Mod please delete.
-deleted by me -
@redwoodie , please don't post to this thread. I read all your threads/posts but have no information.
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
As to whether "x" strategy will work, you are certainly free to explore that on your own, in your own thread.
No one here knows. I am certainly not going to experiment on my own phone and run the likelihood of having to buy a new one. Folks like yourself keep showing up and doing just that because they are SURE it will work. But it hasn't.
Read all the posts.
There are very few folks left here on this forum. Once they have destroyed their phone, and tried a bunch of things, they move on.
THERE IS NO SOLUTION.
This thread is only to warn newbies.
I personally know nothing about the phone other than what has been posted by others.
Read it.
If you discover a true solution that allows a phone to work perfectly ON STOCK, please post it and you will make lots of folks happy, assuming it is repeatable.
However, no known solution.
But, again, you are free to explore solutions - just not in this thread, please. Thanks.
added paragraph at top:
$$
DO AT YOUR OWN RISK - I TAKE NO RESPONSIBILITY.
note added 2-27-2020: it may be that some problems with returning to stock are due to not (in TWRP) advanced wiping data, system, dalvik-ART-cache before flashing. You can do temp "fastboot boot twrp-3.3.1-0-payton.img" w/o quotes, and do it there. -changed/edited. don't use TWRP to flash a stock zip!
This guy is full of crap
KrisM22 said:
only modify a phone you are willing to throw away.......
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
Please do a lot of reading here before you try to modify your phone, unless you are totally willing to render it useless. A word to the wise.
Click to expand...
Click to collapse
I've literally put so many different custom ROMs on this phone. I've bricked it, unbricked, hard bricked it and soft bricked it. Stop misinforming people bro. The Moto G6 I would say to be careful with but still I wouldn't make a post like this guy. The Moto x4 just requires a little prep to make it a full treble, GSI accepting, custom Rom beast. Plus there are a few official ROMs out there even Android 10 for the Moto x4 specifically. Don't be scared. Just research a lot and follow instructions
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
JavaShin said:
But i think if the phone gets unlocked the bootloader and flash twrp making a backup of the stock recovery before just booting the twrp custom recovery then flash magisk on twrp on top of Stock PIE , After Of Course Make A Full Backup Of all partitions reboot and then on Stock PIE have ROOT. and never flash custom roms and never lock the bootloader and stock can be reflashed without problems with a script on linux with fastboot on bootloader-fastboot mode this plan can work , NO ? i had a E4 sprint and never had problems doing that
I need root for A Lot Of Things like Xposed Drivedroid Youtube vanced Adway ETC.
Can Anyone who is reading this have done this just root pie on this phone with unlocked bootloader ? and able to restore stock flashing it back with the retail firmware just to remove root and clean the stock and recovery ? or try to put android one ? the phone which im going to buy its the XT1900-6 retail brazil i already have the retail stock official pie rom ready to flash and with the script on linux with no fastboot oem lock anywhere .
Click to expand...
Click to collapse
The op is a cracker Jack
Ims status not registered
Guys i flashed custom rom without taking backups of efs and all,so i ended up with ims status not registered because of that my volte is broken mine is retin.I tried to flash stock firmware but the imei is broken.Any way to fix this?
bumpsi since apparently folks are not reading this. mod a phone, likely lose it. relock a phone and def lose it.
Totally stock pixel 5. Tried to sideload 12, and due to crappy instructions on XDA, that failed to mention the need to do the OEM unlock step, I ended up with a ADB sideload flash that failed at 94% and resulted in a empty A partition and a phone that failed to boot, so it switched to the backup system partition.
I'm now booted on the B partition (Android 11).
How can I fix my phone, so it's got 2 good system partitions?
Enable OEM unlocking, unlock bootloader, then use the Android Flash Tool to flash 12 Beta 5. Wiping /data shouldn't be necessary; however, if this fails and you have to force flash all partitions, a /data wipe will be required.
I highly recommend you keep the bootloader unlocked while using beta firmware, because it makes it a LOT easier to downgrade back to production firmware.
If you intend to root, don't forget to disable dm-verity and vbmeta-verification.
Detailed instructions on using the Android Flash Tool
Tip: When you get to the step of selecting which build to flash to your device, click the pencil icon to change options. Make sure you leave Relock Bootloader unchecked,
V0latyle said:
Wiping /data shouldn't be necessary
Click to expand...
Click to collapse
But unlocking the bootloader will wipe the phone.....
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
xunholyx said:
But unlocking the bootloader will wipe the phone.....
Click to expand...
Click to collapse
Correct, but it's still necessary to install the beta (and downgrade)
xunholyx said:
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
Click to expand...
Click to collapse
There is indeed. It's actually quite comprehensive.
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Chr1stOnABike said:
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Click to expand...
Click to collapse
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work. Requires unlocked bootloader
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
V0latyle said:
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work.
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
Click to expand...
Click to collapse
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Chr1stOnABike said:
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
Click to expand...
Click to collapse
Ah. Well, you can fix this, but it will require unlocking the bootloader.
You can always relock it after you're done.
Chr1stOnABike said:
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Click to expand...
Click to collapse
Don't know. Given that you can't boot into recovery, you can't sideload the OTA to test this theory. I personally doubt it. You can either wait and see, or you can just bite the bullet and fix the issue.
Chr1stOnABike said:
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Click to expand...
Click to collapse
Link to the post? You may not be the only one, but the majority of folks (including myself, I was in the Marine Corps for 9 years so you can guess my mental acuity) have been able to use the instructions to our success.
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Chr1stOnABike said:
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
Click to expand...
Click to collapse
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
Chr1stOnABike said:
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Click to expand...
Click to collapse
I have updated my phone using both of these methods and can personally confirm the instructions are correct. The only difference I would point out is that I'm comfortable enough using adb and fastboot commands that I manually type them and don't use the batch file.
It is your responsibility to understand the instructions and follow them. You flash and modify your device at your own risk. If you do not fully understand the instructions, it is also your responsibility to either find the details you need, or ask for help.
This may seem rather condescending or apathetic, but the situation is this:
- You tried to run experimental beta firmware on your device despite your concerns for the warranty
- You did not ask questions before doing so, and if you did read any of the multiple threads on this issue, you would have been acutely aware of the recommendation to unlock your bootloader before you proceed
- You are now left with few options to fix your device because you decided to ignore experienced advice and do things your own way
As I stated previously, the responsibility for fixing things is yours and yours alone. If you were that concerned with your warranty, you should have kept your phone completely stock and avoided installing the beta.
I have one last recommendation for you:
Disenroll from the beta program and wait for the OTA to take you back to A11 public release. A data wipe will be required.
You have been told in detail what you can do to fix your device. What you do now is completely up to you.
V0latyle said:
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
I have updated my phone using both of these methods and can personally confirm the instructions are correct. .
Click to expand...
Click to collapse
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
Click to expand...
Click to collapse
Yes - I unlocked and rooted my phone the day I got it, and I bought it full price direct from Google. Your point?
Chr1stOnABike said:
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
Click to expand...
Click to collapse
Yes, it's always worked for me. I've been trying to work with you here and give you options that do not require OEM Unlock or unlocking the bootloader. The reason I thought the Android Flash Tool might work is because it's literally a tool provided by Google, and though it uses ADB, I figured they might have some sort of security to allow recovery of locked phones.
What exactly is it you don't think I understand? As I've pointed out, you decided to install beta software on your device despite your concerns for warranty. As I ALSO pointed out, if warranty was that much of a concern for you, you should have stayed on stock public release firmware and not messed with anything at all.
I will admit that the guide you linked does not mention needing an unlocked bootloader. I think it's generally been assumed among us in the community that modifying your device requires an unlocked bootloader. I will talk to the mods and see if we can get a note added to the post. However, you seemed to miss the big warning that advises against using the beta on your daily driver.
Chr1stOnABike said:
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
Again, how so? If you're going to call me ignorant, you had better explain how.
OEM Unlock simply sets a flag: "unlock-ability" to 1. It's an on/off switch that corresponds to the 1 or 0 set for the "unlock-ability" flag. It has no other function.
When someone attempts to unlock the bootloader, the device checks that flag. If it's 0, the bootloader cannot be unlocked. If it's 1, it can.
Unlocking the bootloader disables security features that prevent you from flashing partitions on your phone, or booting images sent via ADB. The reason why this is important when running custom or experimental firmware is because it allows the user to reflash corrupted partitions (like in your case). It allows a lot more freedom over what you can do with your phone.
I've been doing this for years - more than 10 years in fact. I would be careful about making accusations like "you don't understand the difference" or "you don't know what you're talking about'" to someone who is trying to help you. I understand you're frustrated, but you're going to have to swallow your pride here and admit, at least to yourself, that you screwed up. It seems pretty clear to me that you either did not fully understand the risk of trying to modify your device with a locked bootloader (yes, installing the beta counts as a modification), or you ignored the risk and tried to do it anyway. Yet you come here and impugn my credibility? As they say, "check yourself before you wreck yourself". You screwed up and got yourself into this mess. You alone are to blame. No one has to help you, and believe me, I've been quite tempted to tell you to pound sand. The least you can do is show a little gratitude for someone who's trying to help, and respect for experience and knowledge far beyond your own.
I have one more option for you: Rescue mode.
Reboot your phone into bootloader (hold power + volume down, release power but keep holding volume down when screen turns off)
Use volume buttons to select rescue mode on the right side, then press power to select
Google Pixel Repair Tool
This probably won't work because the repair tool only works if the firmware on your phone is older or equivalent to the firmware the repair tool has.
Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
I haven't had time to read much of this thread yet, but why insult the one person I see who's trying to help you?
I've seen this before and other users who may know what to do, usually just walk away as they don't want to help someone who may just insult them or are clearly unappreciative of the help given.
Everyone let's all keep it civilized.
If you have issue with a post, please hit report button and walk away.
Positive vibes, all.
--andybones
@Chr1stOnABike I am indeed trying to help you, as I understand your situation is frustrating. I also understand that it may be frustrating to be told to do what you didn't want to do in the first place, but the reason why I'm telling you to do it is because it'll be of the most help to you.
Losing your data sucks. I get it. But fortunately the Pixel 5 is great about backing everything up to your Google account. Just make sure your photos are backed up and you'll be fine. Setting it back up after a wipe is a pain in the ass, but again, I'm recommending the bootloader unlock because I believe it's your best chance at recovery.
As far as that goes, I'm still trying to be flexible and provide you with different options. Be aware that if these other options don't work, you have no other choice. I'm not saying that to be rude, that's just the reality of it.
And lastly, I would very much appreciate you making the distinction between thinking I'm wrong because you have evidence to the contrary, vs thinking I'm wrong simply because you don't like my recommendations. If you sincerely believe I'm incorrect and can demonstrate how, please feel free to do so.
My only objective here is to help people the best I can with the knowledge and experience I have.
For those who ever get stuck like I did. When I got stuck in a bootloop, I realized I could 'fastboot boot twrp.img' and was able to save my internal storage from being lost by backing up to PC with TWRP, then move it back onto internal after the factory reset. Did I lost app data in these cases, yes. But that's my own fault for not regularly backup app data up with something like Swift or AppDash.
@Chr1stOnABike just checking in to see if you were able to get your problem resolved?