My Pixel 2XL has locked bootloader and from yesterday I'm having some issues with touchscreen not responding. I spill some coffee on display - just a few drops of cold coffee - but quickly wiped out. The phone was OK, but in the evening the touchscreen stopped working. My first impression was that's a beta issue and so I manually wiped device but it didn't help, the screen is still not reacting.
So before I tear device to see it's not a hardware issue I would like to try to downgrade to stable android 9. Because bootloader is locked my only option is to update/downgrade via ADB, but because official OTA for Android 9 is older ADB is not allowing me to downgrade.
From what I read, rolling back to stock involves sing-off from the beta program on Google's website and wait for another OTA to revert to stock, but because I wiped the device and can't even set the system up and running I won't get it.
Maybe someone can provide such OTA file? Or maybe I'm doing something wrong.
Please, guys, help me out.
Files are here https://developers.google.com/android/images
Droid_Nut said:
Files are here https://developers.google.com/android/images
Click to expand...
Click to collapse
Because my bootloader is locked I just can't flash system image and so far there's no method to unlock Verizon variant. Only OTA newer than Q beta4.
What happens when you try to wipe/format data from the recovery partition? Having a corrupt system/OS shouldn't have affected the recovery partition and/or the ability to format and wipe it to a stock state...
But, if anything, you might have some luck downloading the OTA system image (can still be found at the developers site of Google's), loading up the stock recovery (don't worry if you get a dead droid with an exclamation/triangle, it's supposed to show that, you just need to hold Power + Volume-Up at the same time), and running through the selection of "Apply update from update" and/or "Apply update from .zip" where you can now either point to the OTA .zip manually or "push" the file onto your device...
Using the stock recovery to either wipe/format the device or manually applying the OTA seems to be the only rescue method available to locked bootloader devices...
Good luck to you and I hope this helps...
Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770
Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.
Edmontonchef said:
Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.
Click to expand...
Click to collapse
My touchscreen doesn't work, so I can't pass the initial set-up.
I just hope Google will release DP5 within a couple of weeks. Or maybe the touchscreen is broken? I guess I have to wait.
BTW Now I'm rocking old Lumia 550 on WM10 and it's a real pain in the a.ss without google services.
lywyn said:
Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770
Click to expand...
Click to collapse
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Maybe someone could upload it's "un-roll" OTA. So I could try to flash it and find out is it software or hardware issue.
adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...
adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."
lywyn said:
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."
Click to expand...
Click to collapse
I know that, but IP rating doesn't mean that your phone is absolutely 100% safe, and maybe this time I got run out of luck.
I'm just patiently waiting for beta 5 to be announced and then we'll see.
simplepinoi177 said:
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...
Click to expand...
Click to collapse
It's exactly like You said. I'm able to flash Android Q beta DP4 OTA, but after rebooting I'm stuck at welcome screen and the touchscreen doesn't work.
But once, when I removed the SIM card and popped it right back, a popup window for SIM unlock appeared and I was able to input pin (after that screen got frozen), so I believe that's not a hardware issue. I just have to wait for DP5 and find out is it gonna help or not.
Use an external mouse via USB adapter to pass the welcome screen etc
siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
I didn't know that. Thanks for the tip.
siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
So I did. With the mouse, I was able to sign in Google account and unroll from the beta program. I immediately received OTA with android 9 form June, but after a downgrade, my touchscreen still doesn't work.
How the heck is it possible? The screen is connected to the motherboard with only one ribbon, so if that ribbon would be defective, the screen should not turn on or have some artifact.
So far it's working OK, except for some strange glitch with "day widget".
{
"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"
}
Any suggestions? Should remove the screen and see what's inside? I guess that's the only option left.
Probably your screen is broken and you need a new one. Warranty?
siggey said:
Probably your screen is broken and you need a new one. Warranty?
Click to expand...
Click to collapse
Nop, device bought in Best Buy i NY. So would have to bring it overseas from Europe, because in my country Google doesn't sell devices.
Related
!!Check out the Video on how it works!!!
http://www.youtube.com/watch?v=ZANt0vaiZYs
[Disclaimer]:
The method of rooting your Android device as described below is solely by your choice and your choice only!
IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA.
I, XDA, and other forum members claim no liability for any harm that may come to your device, including, but not limited to: bricked phones, voided manufacturer warranties, bootloops, loss of data, etc
While generally this software is safe, and does have fail safe and error checking, it does not mean that something can/shell/or will not go wrong. Please be prepared if it does.
[/Disclaimer]
[Information]:
Device Supported:
MZ600 VZW 3G/4G
Software Supported:
3.0 Build HRI39
3.0.1 Build HRI66
3.1 Build HMJ37
Method Used:
Fastboot oem unlock
Unsecured boot.img for device software.
Features:
Fast and easy 1 click root method for supported sw.
Error checking to prevent mistakes as much as possible.
Takes 5-8 Mins to Unlock/Root device.
Install's SU and Superuser.apk
Detects Software version to version selected, helps install correct files needed.
Other Information:
This will WIPE ALL USER DATA.
Tested with:
3.0 Build HRI39
3.0.1 Build HRI66
3.1 Build HMJ37
I have personally restored to all three version's of the software and tested root and unlock on all software version's. This should/will work as long as you follow instructions. Its really not hard, and its hard to mess up.
[/Information:]
I know there is just a WIFI Version and I will add support later. It will auto detect you're phone mode.
{
"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"
}
[DOWNLOAD LINK HERE]
Download Here DO NOT POST ON OTHER FORUMS IF ITS POSTED ON OTHER FORUMS I WILL REMOVE LINK AND STOP SUPPORT THIS IS FOR XDA ONLY!
Download Unroot_tools, please extract into the unroot_tools folder.
If you use this software please leave feedback.
Supported Devices:
US VZW 3G/4G on either 3.0/3.0.1/3.1
Support for other devices planed:
US VZW WIFI on either 3.0/3.0.1/3.1
EU Xoom's
Support to flash Clockwork Recovery is planned.
Support to install new framework for SMS/MMS/UAString on either 3.0/3.0.1/3.1
*I will not enable phone features untill a phone app can be used, i use another carrier other then VZW and I myself would like to be able to use the phone feature as well but can't untill a new phone.apk is compiled for honeycomb or one comes out that works with it*
Looking pretty smooth. Just took the plunge to root via adb though.
The unroot method will let you lock without getting any LNX errors,?
The LNX error from what I seen is because the device needs to be unlocked again in order to boot.
Ill have too check it out again, I restored mine last night and received this LNX error. The way to recover was to boot fastboot by shutting the device off first VOL UP + PWR let it stay off for a min then boot into fastboot by VOL UP + PWR this kicked me into fastboot and running the cmd fastboot oem unlock my device was able to boot properly without an issue.
I am assuming the device cannot be locked and boot because the img files are not signed files from Motorola? I ran into this problem recently while trying to revert back to stock and locked to give the video app a try. I had a terrible experience with LNX 0x0004. Pretty severe brickage. Kinda scurry thought I had a high dollar paper weight.
amoamare said:
The LNX error from what I seen is because the device needs to be unlocked again in order to boot.
Ill have too check it out again, I restored mine last night and received this LNX error. The way to recover was to boot fastboot by shutting the device off first VOL UP + PWR let it stay off for a min then boot into fastboot by VOL UP + PWR this kicked me into fastboot and running the cmd fastboot oem unlock my device was able to boot properly without an issue.
Click to expand...
Click to collapse
Yes, sorry still at work so short answers.
From what it seems is that you have to return completely to stock images, even then it might now work. From what it seems the application the removes the lock might also implement security in order to prevent from being locked again.
While the lock method works for some I think its all dependent on when people got their xoom. Mine is new and came loaded with latest software.
I think you hit it right on the nail. I think that even returning back to stock because the images and boot partitions have been modify the device will fail to boot. I have tried RSDLite to restore the SBF all the way from version 4.8 to 5.3.1 and it will not restore it fails each time. Only way to recover it was to re unlock the device and the device booted fine.
Tried to relock again and it failed to boot.
W00t just what we need...
It should be much more difficult for them to brick there device with this tool. As the user isnt using a 1 click method made for 1 version of the system.
The problem with the 1 click's out is currently they flash 1 boot.img for only 1 system either 3.0 or 3.01 this cause the device to hang at boot then people thinking something went wrong.
The program is designed with error checking in mind.
As seen in the video I show you this by purposely selecting the wrong software version, it notify's me that i'm trying to install the wrong boot.img for the a mismatched version of the os.
Also i was receiving the LNX errors before when trying to relock the device i figured out a good method and it will be implemented.
This is amazing if this works flawless, and I'm Super new to android, and I just bought a Xoom, I'm curious what does Rooting do for the device?, also why do people try to Un-Root for?
This is 3G only?
Yes 3G only, once the 3G is completly done ill focus on the WIFI version. I do not have a WIFI version myself so it will be based of whats posted.
Bad ass! Can't wait for wifi version! Great work
Azrael X 4.0
Can you tell me where the download link is?
Its comming as soon as i fix the MD5 Checks for the files and images.
Download Link Added.
Thanks op, I used this to unroot my xoom and it worked perfectly.
Thank you for the reply glad you liked it.
I'm eagerly awaiting the WIFI version! Woot!
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I dont have a WiFi version so I need someone with adb experience so that I can implement a wifi version.
I take it just need the right boot images as well for the wifi version as there seems to be some hardware differences. But i need someone who can adb the device and get me some getprop information so that i can implement the wifi version of the device. I have rooted and unrooted my device over 20 times with this tool. Its fast and easy to use. I actually just updated it again with a new help box when it gets to fastboot oem unlock. I will have to also add one for the fastboot oem lock feature as I think I forgot to add that one.
Anyway.
If you have used this software Please Please leave feedback so that other users can see the success to fail rate. *THERE SHOULDNT BE ANY FAIL RATE* but if it fails i need to know so i can fix what ever it didnt do.
Will u not being doing this for EU xooms?
As the title states, I'm looking for a working link to a *working* Gen2 stock 3.2 Honeycomb Rom. Not sure if there's one out there. I tried searching with all my resources (Google and the Search bar here on xda). I tried following a few guides that did provide supposed Gen2 roms, however I get this during restore attemps:
{
"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"
}
That stays up on the screen for about 2-3 minutes, then it restarts, and gets stuck on the android boot screen....forever(let it sit for over an hour and got nothing).
I could update back to any gen1 ics image, but I'd like to get back to Gen2 and see if I cant get ICS Gen2 (unless Acer still hasn't released it for real).
Thanks!
Edit: I should probably mention I was on the latest leaked version of ICS for Gen1 and before attempting to restore to 3.2 Gen2 I formatted my MicroSD and Factory Restored the tablet itself.
Hadriel18 said:
As the title states, I'm looking for a working link to a *working* Gen2 stock 3.2 Honeycomb Rom. Not sure if there's one out there. I tried searching with all my resources (Google and the Search bar here on xda). I tried following a few guides that did provide supposed Gen2 roms.
That stays up on the screen for about 2-3 minutes, then it restarts, and gets stuck on the android boot screen....forever(let it sit for over an hour and got nothing).
I could update back to any gen1 ics image, but I'd like to get back to Gen2 and see if I cant get ICS Gen2 (unless Acer still hasn't released it for realh).
Thanks!
Edit: I should probably mention I was on the latest leaked version of ICS for Gen1 and before attempting to restore to 3.2 Gen2 I formatted my MicroSD and Factory Restored the tablet itself.
Click to expand...
Click to collapse
You need to perform an hard reset before you can rollback from ICS (be it leaked or official) to HC.
Flash HC, then shut down the device. Place your rotation lock switch to the OFF position. Power up your device holding the POWER button and the VOLUME UP button. As soon as the device starts, release the POWER button and activate the rotation lock. Wait till the system is restored.
Just mind you that the VOLUME UP buttons varies from Landscape to Portrait mode.
EDIT - Just noticed you already tried this. Sorry.
.
Anyway, all ICS ROMS for A100/A101 I've seen so far were GEN1, so you might end up receiving a GEN1 ROM via OTA regardless.
Well I did some more internet-ing. Contacted Acer support and in the end they told me to try a Factory Data Reset:
Please follow the steps given below to perform a Factory Data Reset:
1. Place the rotation lock switch in the up position.
2. Press and hold the Volume down button, which is located farthest from the rotation lock.
3. With the Volume down button held, press and hold the Power button for 3 seconds then release it. Continue holding the Volume down button.
4. Once the tablet vibrates, switch the rotation lock on and off repeatedly while still holding the Volume down button.
5. Release the Volume down button and stop switching the rotation lock once the "Erasing Userdata..." message appears in the upper left corner of the screen.
6. Once the factory reset has been completed your tablet will load to the Welcome screen.
7. Your Factory Data Reset has completed now follow the onscreen steps to setup your tablet.
Click to expand...
Click to collapse
Worked like a charm and I was able to at least get the tablet working back on 3.2 Gen1. Using Vache's OTA checker I then checked the Android version that was on the tablet and changed that Gen1 part to Gen2 and have now downloaded what I believe to be 3.2.1 for Gen2 and some small update as well from the acer futuredial repository. Now I'm just running through all these small updates Acer has ( looks like 2 that are a little over 3mb and one 13mb update thus far.)
If I manage to get to Gen2 ICS I'll post here. Not sure if that is big news or not. Just reporting where I end up at this point and I hope this post can help anyone.
EDIT: After the 13.6(I think)mb download, Vache's Acer OTA Check tool no longer can find any further updates.
I'm on 3.2.1
Build Number: Acer_A100_2.013.02_COM_GEN2
and my tablet now gives me the option to update to: Acer_A100_041.202.01_COM_GEN2
It is 165.56mb and I'm assuming (hoping) it's ICS, but it says:
Acer Sync, Adobe Flash Player and Kobo are not included in this upgrade. You can download Adobe Flash Player and Kobo (when a new version is available) from the Android Market. Kobo books are still available on the Kobo servers.
Click to expand...
Click to collapse
I'll update this post further if anything else happens.
Okay so now my tablet is on 4.0.3
Kernel: 2.6.39.4+
Image Version: Acer_AV041_A100_RV02RC01_PA_CUS1
Build Number: Acer_AV041_A100_1.015.00_PA_CUS1
And it now shows no further updates. I have no clue what the PA_CUS1 thing is though...
Hadriel18 said:
Well I did some more internet-ing. Contacted Acer support and in the end they told me to try a Factory Data Reset:
1. Place the rotation lock switch in the up position.
[...]
4. Once the tablet vibrates, switch the rotation lock on and off repeatedly while still holding the Volume down button.
Click to expand...
Click to collapse
Always wondered why they suggest to place the rotation lock up, and then to switch it up and down repeatedly. Each time I had to hard-reset my device, it was enough for me to simply place the lock DOWN and then to switch it up (while holding VOLUME UP, as mentioned).
I believe there's really no need to move it repeatedly like they say. Anyway, glad it's solved now.
Hadriel18 said:
I have no clue what the PA_CUS1 thing is though...
Click to expand...
Click to collapse
As far as I understood Acer's cryptic nomenclature, the first portion of the code is an area code (most Euro/Middle East devices are COM1/2, for example, while North American and Canadian devices seem to be PA) which likely influences built-in language packages/default language, and the second part is used to define update batches (it's been observed that GEN1 are the first to get OTA updates, then comes GEN2 and then... anything else, I believe...?)
Take this with a grain of salt tough. This is mostly deduction as there's no official information available.
Hadriel18 said:
Okay so now my tablet is on 4.0.3
Kernel: 2.6.39.4+
Image Version: Acer_AV041_A100_RV02RC01_PA_CUS1
Build Number: Acer_AV041_A100_1.015.00_PA_CUS1
And it now shows no further updates. I have no clue what the PA_CUS1 thing is though...
Click to expand...
Click to collapse
Yeah, don't worry about what the suffix on the image and build #s is. It really doesn't matter. Give it a few days and you will probably get the latest update to .037. But its no biggie, I didn't see any noticeable change from any of the updates.
Hadriel18 said:
Well I did some more internet-ing. Contacted Acer support and in the end they told me to try a Factory Data Reset:
Worked like a charm and I was able to at least get the tablet working back on 3.2 Gen1. Using Vache's OTA checker I then checked the Android version that was on the tablet and changed that Gen1 part to Gen2 and have now downloaded what I believe to be 3.2.1 for Gen2 and some small update as well from the acer futuredial repository. Now I'm just running through all these small updates Acer has ( looks like 2 that are a little over 3mb and one 13mb update thus far.)
If I manage to get to Gen2 ICS I'll post here. Not sure if that is big news or not. Just reporting where I end up at this point and I hope this post can help anyone.
EDIT: After the 13.6(I think)mb download, Vache's Acer OTA Check tool no longer can find any further updates.
I'm on 3.2.1
Build Number: Acer_A100_2.013.02_COM_GEN2
and my tablet now gives me the option to update to: Acer_A100_041.202.01_COM_GEN2
It is 165.56mb and I'm assuming (hoping) it's ICS, but it says:
I'll update this post further if anything else happens.
Click to expand...
Click to collapse
Do you still have the 3.2 Gen1 rom? All of the links on XDA for 3.2 are dead and I cannot get this method of reverting to Gen2 to work with 3.2.1 Gen1 roms. Thanks in advance.
Hi, I was on my way to root my z5p Australian version, I repaired with PC companion that also updated to Android 6 I suppose. But after update, I wanted to use my old gmail ID that I use in my other phones; however, after putting id and password it was asking for the id I've created temporarily for z5p to put that was previously synced with z5p. Unfortunately, as it was temporarily created I can't recall anything. I tried google recovery option with no luck.... can't even remember with id I used for recovery....
I've also reset it with flash tool guided through this forum, no luck.... tried to unlock boot loader from sonymobile forum by installing Android sdk. But it's failing when I put the command with the unlock code...
Is there any way that I can root my z5p or at least I can get to the phone...? Thanks in advance.....
That doesn't make a great deal of sense - did you encrypt the storage before doing any of this? If you factory reset the phone then it should 'forget' all of the Google account association and be like an 'out of the box' phone again...?
NJ72 said:
That doesn't make a great deal of sense - did you encrypt the storage before doing any of this? If you factory reset the phone then it should 'forget' all of the Google account association and be like an 'out of the box' phone again...?
Click to expand...
Click to collapse
Hi,
What do you mean by storage encryption...? I didn't do anything just updated the to Android 6 with Xperia companion. Since than I couldn't access to it without gmail account that i forgot. I read in one blog that from google has made a new security feature from Android 5 (google support for Android-one site). In that case, I've bricked my Z5P....
If none of you are able to help me, I need to through it away. I'm also ready to donate/pay for the service, if necessary. Thanks in advance.....
Hi,
Just got an idea, if Android 5 and onwards have more robust security features; is it possible to downgrade to kitkat or less, then unlocking the bootloader for rooting....? How about that...?
You won't be able to downgrade below 5.0 as that's what the device shipped with (I also doubt any devs are working on KK builds for the Z5P )
If you connect the device to your PC does it show within PC Companion? If so then try and wipe the device from there.
Can you take a picture of the screen you are presented with on boot as that should help.
{
"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, it is showing on PC companion and Xperia companion. However, I don't know how to wipe off. Please let me know. Thanks
sazzadhasan said:
Hi, I was on my way to root my z5p Australian version, I repaired with PC companion that also updated to Android 6 I suppose. But after update, I wanted to use my old gmail ID that I use in my other phones; however, after putting id and password it was asking for the id I've created temporarily for z5p to put that was previously synced with z5p. Unfortunately, as it was temporarily created I can't recall anything. I tried google recovery option with no luck.... can't even remember with id I used for recovery....
I've also reset it with flash tool guided through this forum, no luck.... tried to unlock boot loader from sonymobile forum by installing Android sdk. But it's failing when I put the command with the unlock code...
Is there any way that I can root my z5p or at least I can get to the phone...? Thanks in advance.....
Click to expand...
Click to collapse
The only way to continue past this is to "remember" the Google email (and password)
Sent from my E6653 using Tapatalk
Hmm... the only wipe method using PC companion is the 'repair' option that will almost certainly still require the use of your credentials. Can you show me how far in to the system you can get? Do you have another device you can use to take a photo?
Edit: I imagine you have as you mention flashtool, but have you tried flashing a new FTF with all of the options along the right hand side ticked?
NJ72 said:
Hmm... the only wipe method using PC companion is the 'repair' option that will almost certainly still require the use of your credentials. Can you show me how far in to the system you can get? Do you have another device you can use to take a photo?
Edit: I imagine you have as you mention flashtool, but have you tried flashing a new FTF with all of the options along the right hand side ticked?
Click to expand...
Click to collapse
I'll do it again today.
Yes, I used flashtool and ticked those 4 wipe options and did it twice; till same result. Yes, I've iPhone 6s Plus and the pic I sent was taken with that....
Hi, just thinking how about formatting the phone drive a put the new rom again...! Any ideas...?
sazzadhasan said:
Hi, just thinking how about formatting the phone drive a put the new rom again...! Any ideas...?
Click to expand...
Click to collapse
I think it might be the my xperia theft protection. Google it for more information
kamalaggi said:
I think it might be the my xperia theft protection. Google it for more information
Click to expand...
Click to collapse
Yeah, it is. Google has introduced it from Android 5.0 and onwards. If it continues, some people like me has to chuck the android phones away....
Just thinking, if I use a Different stock ROM other than AU, what would happen..!! Anyone have idea...?
I don;t think moving to a different region ROM would change anything. I doubt it's the Xperia theft protection, more like Google's built in stuff.
Random-ass question, but have you actually contacted Sony support about it? I appreciate you're likely to get a faster answer out of us here at XDA, but so far our ideas haven't turned up much...
Likewise I wouldn't blatt the whole storage just to try and get in to the phone, if you can't install a ROM back on it you'll be more than buggered.
Is there any way to at least find the email address you used as your Google ID? Did you get an email confirmation to your other Google account which would at least tell you the email address?
EDIT: perhaps have a look at this page: Google Account Recovery
sazzadhasan said:
Yeah, it is. Google has introduced it from Android 5.0 and onwards. If it continues, some people like me has to chuck the android phones away....
Click to expand...
Click to collapse
If you don't mind losing data, download an Ftf for your phone and flash through flashtools. When that happens, I think you can wipe data. Thus making your phone look " out of the box"
Not sure if anyone has told this already, didn't read through the pages.
As per my knowledge, it should ask you if you want to create a new account or use an existing one, when the phone boots up.
Ashray_Vk said:
If you don't mind losing data, download an Ftf for your phone and flash through flashtools. When that happens, I think you can wipe data. Thus making your phone look " out of the box"
Not sure if anyone has told this already, didn't read through the pages.
As per my knowledge, it should ask you if you want to create a new account or use an existing one, when the phone boots up.
Click to expand...
Click to collapse
Hi, just a quick question, what is a 'ftf'..? Yes, I did flash through flashtool with 4 things checked on the top right corner. After booting it asked me to sign in and I've signed in with a new gmail ID, well new in a sense that I used it with my old Samsung S2 4G, Sony tablet and so. After putting it through I got the notification in my iPhone gmail that my ID is used to sign in to Sony Xperia z5 premium...blah...blah....On the other hand, on z5p another screen came over which was asking to put my old temporary ID that I was created at the beginning; however, I forgot the ID. I've posted that picture at the beginning if you wanna look at it. Thanks
NJ72 said:
I don;t think moving to a different region ROM would change anything. I doubt it's the Xperia theft protection, more like Google's built in stuff.
Random-ass question, but have you actually contacted Sony support about it? I appreciate you're likely to get a faster answer out of us here at XDA, but so far our ideas haven't turned up much...
Likewise I wouldn't blatt the whole storage just to try and get in to the phone, if you can't install a ROM back on it you'll be more than buggered.
Is there any way to at least find the email address you used as your Google ID? Did you get an email confirmation to your other Google account which would at least tell you the email address?
EDIT: perhaps have a look at this page: Google Account Recovery
Click to expand...
Click to collapse
Thank you so much for all those ideas, but nothing helped me. I think it is a good time to throw it away....
sazzadhasan said:
Hi, just a quick question, what is a 'ftf'..? Yes, I did flash through flashtool with 4 things checked on the top right corner. After booting it asked me to sign in and I've signed in with a new gmail ID, well new in a sense that I used it with my old Samsung S2 4G, Sony tablet and so. After putting it through I got the notification in my iPhone gmail that my ID is used to sign in to Sony Xperia z5 premium...blah...blah....On the other hand, on z5p another screen came over which was asking to put my old temporary ID that I was created at the beginning; however, I forgot the ID. I've posted that picture at the beginning if you wanna look at it. Thanks
Click to expand...
Click to collapse
I tried. But I am not able to see that image, like it's broken or something. Maybe it's just me. Could you please upload that image again?
https://mega.nz/#!c9lRjRpD!8JQWyaqzEUj9wU7d5ic3MEO_zrfpTBhekwKCTmlPy6I
Hello Everyone
So before I was unlocking and rooting the Amazon Fire TV Stick 4k by shorting the efuse, on which on the process is after patching the bootrom exploit w/TWRP is yeah it went great but when I executed the fastboot command which didnt work, like i checked errors for the command but theres really some bug idk even how matter I try (maybe because it was a partition problem on where did I put my exploit files)… so I restarted everything from start… but when I shorted and plugged everything from my laptop, and running the amonet exploit, it didn't detect my FS even how matter I change the plugs and the shorting. And there was no physical damages on the shorting area. And so I cannot run the fastboot command to Open and Execute files thru TWRP and ADB…
(I executed this during the 6.2.7xx vesion with the old UI)
But it seems that the FS is now unlocked and it has TWRP installed as a bootloader cause
After plugging it in TV and rebooted it to fastboot thru network adb, it rebooted instantly on TWRP and it prompts things like “Keep system Read only” well unfortunately I cannot access that before because I don't have OTG so cannot swipe it so I bought one then unfortunately I tried to plug it with high voltage charger and mouse peripherals but the mouse input doesn't show up no matter i change everything or wait to load up for couple of hours, maybe I received a faulty one... so I gave up for a long time and paused this due to budget restraints
Fast forward this time, and for dumb reasons that I never noticed that i constantly accept the updates that I updated it to stock 6.2.8.1 and lately found out that this version update burns efuse but I'm really curious what does this really mean? Does it mean on how many times you run the exploit and shorting it wont work and will not be detected thru pc? Or worst that the system partition cannot be modifed and you can't flash files no matter what even you installed TWRP? Can someone enlighten me? Will installing the prerooted roms like the 6.2.8.0/6.8.8.1 will work to root my systems? Cause I ordered 2packs of OTG again and they will be arriving in 10days hoping that the otg will work...
Can someone help me? Anyhelp regarding this issueis highly appreciated
Thanks
boss @Sus_i @Skel40 @tsynik @rbox any thoughts around this sirs?
yan2xme said:
Fast forward this time, and for dumb reasons that I never noticed that i constantly accept the updates that I updated it to stock 6.2.8.1 and lately found out that this version update burns efuse
Click to expand...
Click to collapse
TWRP skips flashing some images like TZ during an update, which means the efuse is safe, as long as you didn't update the TZ as well.
yan2xme said:
Does it mean on how many times you run the exploit and shorting it wont work and will not be detected thru pc?
Click to expand...
Click to collapse
The shorting thing gets permanently disabled, i.e. the SOC will refuse to boot with a short in place and there isn't a way to run the bootrom exploit again.
yan2xme said:
Will installing the prerooted roms like the 6.2.8.0/6.8.8.1 will work to root my systems?
Click to expand...
Click to collapse
Ofcourse they do.
Sus_i said:
TWRP skips flashing some images like TZ during an update, which means the efuse is safe, as long as you didn't update the TZ as well.
The shorting thing gets permanently disabled, i.e. the SOC will refuse to boot with a short in place and there isn't a way to run the bootrom exploit again.
Ofcourse they do.
Click to expand...
Click to collapse
sorry for dumb questions cause I want to make things for myself clearer (but first of all really thank you for replying fast)
so what's TZ again? is it abbreviated word?
and so is the bootrom exploit does only work once in a lifetime of a FS and will not work in other attempts even tho my FS is updated in a stock 6.2.8.1? should I try it again thru pc? or should wait just when my OTG arrives? and reboot it thru TWRP using mouse? Can I downgrade it too on the old 6.2.7xx versions where much of the kernels and patches here are suported on that version? Or for example can I use a kernel or GApps intendedly for 6.2.7xx on a prerooted 6.2.8.1 rom? Sorry for a topsy turvy kind of question but I hope you could really help me out... btw thank you sm
{
"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"
}
yan2xme said:
sorry for dumb questions cause I want to make things for myself clearer (but first of all really thank you for replying fast)
Click to expand...
Click to collapse
No problem.
yan2xme said:
so what's TZ again? is it abbreviated word?
Click to expand...
Click to collapse
TZ (trustzone) is an Image inside the OTA update package, which gets installed from the 'stock recovery' to a partition called TEE1. The efuse can't burn, because TWRP skips flashing the TZ.
yan2xme said:
and so is the bootrom exploit does only work once in a lifetime of a FS and will not work in other attempts even tho my FS is updated in a stock 6.2.8.1? should I try it again thru pc?
Click to expand...
Click to collapse
No, your Stick is fine, because you've TWRP installed...
yan2xme said:
Can I downgrade it too on the old 6.2.7xx versions where much of the kernels and patches here are suported on that version? Or for example can I use a kernel or GApps intendedly for 6.2.7xx on a prerooted 6.2.8.1 rom? Sorry for a topsy turvy kind of question but I hope you could really help me out... btw thank you sm
Click to expand...
Click to collapse
You can downgrade if you like, there shouldn't be a problem at all.
Edit: PS: You don't need to swipe in TWRP, you can also use TWRP commandline... via ADB over USB.
Sus_i said:
No problem.
TZ (trustzone) is an Image inside the OTA update package, which gets installed from the 'stock recovery' to a partition called TEE1. The efuse can't burn, because TWRP skips flashing the TZ.
No, your Stick is fine, because you've TWRP installed...
You can downgrade if you like, there shouldn't be a problem at all.
Click to expand...
Click to collapse
Ohh goodie I've been relieved after a long list of doubt...
So I should just wait till the OTG arrive so I can bring it on! And hopefully everything will be fine during flashing process and I can finally watch the Netflix TV without freezing and have a flawless running os
So I got my phone fixed by flashing some random files I got off a quick Google search and got my phone back up and everything.
Now I have a brand new issue and it's stressing me the hell out that I feel like throwing my phone at the wall because that's how much stress this piece of garbage called a phone is causing me. I have been at this for hours to no proper fix from countless google searches going through websites and other xda threads.
The issue I'm experincing is I'm patching the boot.img file with Magisk and I then flash the img file with adb fastboot. There's 4 things going on when I do this
1 - The phone boots up normally but my touchscreen doesn't work to where I can't click or navigate my entire phone.
2 - The phone ends up in a boot loop where I see the Motorola Logo and that's it it restarts over and over and over and never properly boots.
3 - The phone keeps booting into bootloader on it's own.
4 - When I am able to get through my phone normally after flashing a patched magisk boot file an android update ends up restarting my phone and completely removes my root and I'm back to square one...
All this because I got sick of being bugged by these (BEEP)ing Motorola update pop ups which I made a thread about it on here asking for a way to disable it but never got any responses so I've taken this into my own hands and have made it even MORE worse and it's stressing me out so much.
I need to know how to I extract the boot.img file from my phone myself? I'm finding so many tutorials telling me to just download some boot.img file off the internet but that's what's causing me these issues above because I'm patching something that's probably not even compatible with my phone to begin with so i want to know how do I get the boot.img file directly off my phone so I can patch that with magisk?
I'm at a breaking point with this phone...
jake7901 said:
So I got my phone fixed by flashing some random files I got off a quick Google search and got my phone back up and everything.
Now I have a brand new issue and it's stressing me the hell out that I feel like throwing my phone at the wall because that's how much stress this piece of garbage called a phone is causing me. I have been at this for hours to no proper fix from countless google searches going through websites and other xda threads.
The issue I'm experincing is I'm patching the boot.img file with Magisk and I then flash the img file with adb fastboot. There's 4 things going on when I do this
1 - The phone boots up normally but my touchscreen doesn't work to where I can't click or navigate my entire phone.
2 - The phone ends up in a boot loop where I see the Motorola Logo and that's it it restarts over and over and over and never properly boots.
3 - The phone keeps booting into bootloader on it's own.
4 - When I am able to get through my phone normally after flashing a patched magisk boot file an android update ends up restarting my phone and completely removes my root and I'm back to square one...
All this because I got sick of being bugged by these (BEEP)ing Motorola update pop ups which I made a thread about it on here asking for a way to disable it but never got any responses so I've taken this into my own hands and have made it even MORE worse and it's stressing me out so much.
I need to know how to I extract the boot.img file from my phone myself? I'm finding so many tutorials telling me to just download some boot.img file off the internet but that's what's causing me these issues above because I'm patching something that's probably not even compatible with my phone to begin with so i want to know how do I get the boot.img file directly off my phone so I can patch that with magisk?
I'm at a breaking point with this phone...
Click to expand...
Click to collapse
Most likely you have a mis-matched boot.img.
Use LMSA's flash rescue to reflash the firmware.
Then use that boot.img to patch with magisk.
Stop using random guides that offer no support.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
Most likely you have a mis-matched boot.img.
Use LMSA's flash rescue to reflash the firmware.
Then use that boot.img to patch with magisk.
Stop using random guides that offer no support.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to include LSMA is not working for me at all probably due to the firmware that I used several weeks ago when I first rooted the phone.
{
"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"
}
I had a similar issue to this several weeks ago but it was some other error that I forgot and thinking this was a long time ago I thought by now the program would finally work for me today but nope it never works.
App thinks I'm not in fastboot when I am right now.
So sadly I have to depend on these confusing builds from here and there and who knows where pretty much trial and error...
I wouldn't be in this position if it wasn't for those annoying (BEEP)ing Motorola update pop ups ruining my phone.
Maybe I should just throw the phone at the wall there's no hope.
jake7901 said:
Forgot to include LSMA is not working for me at all probably due to the firmware that I used several weeks ago when I first rooted the phone.
View attachment 5577727
View attachment 5577731
I had a similar issue to this several weeks ago but it was some other error that I forgot and thinking this was a long time ago I thought by now the program would finally work for me today but nope it never works.
App thinks I'm not in fastboot when I am right now.
So sadly I have to depend on these confusing builds from here and there and who knows where pretty much trial and error...
I wouldn't be in this position if it wasn't for those annoying (BEEP)ing Motorola update pop ups ruining my phone.
Maybe I should just throw the phone at the wall there's no hope.
Click to expand...
Click to collapse
Could also be a usb issue, Motos have had some issues like this for a while.
Try a different USB port, Cable or PC
I had the same problem. After patching the boot.img with Magisk and fastboot flashing it, I got no touchscreen.
The problem was the wrong boot.img.
I downloaded Stock ROMs from several sources, all saying that my phone uses a particular Stock ROM. They were all wrong!
I used the Lenovo Rescue and Smart Assistant v6.4.2.13. With genuine Motorola USB drivers.
It found my phone via the IMEI and I downloaded the stock ROM it suggested, it was a different one from all the other ones I had previously downloaded.
TIP, when downloading from the Rescue and Assistant program change where you want it to download to, as it's a pain to try and find it later when you need the boot.img!
After patching with Magisk and fastboot flashing, I'm now rooted and EVERYTHING works!