Please help - flashing incomplete - Google Pixel 3 Questions & Answers

So I was trying to just do a clean install. This phone had no mods installed.
I have done this many times and all went well. I am hoping that someone can help me understand what went wrong.
So working on linux, latest fastboot/adb (29.0.6-6198805) and the March image for blueline.
flashing radio and bootloader went fine. When I got to flashing the kernel it stopped after writing slot_a and rebooting into fastboot. I got the message "waiting for any device"
The phone displayed a warming (see pics) that the bootloader is unlocked and phone vulnerable and gave me an option to pause. after a few seconds it went into a "fastbootd" screen that I never saw before (see pic attached) which gave me options to restart or go back to bootloader. Either option breaks the flashing sequence which ends with error.
Re-flashing produces the same result.
Any suggestions what causes this?
Of course the phone does not boot anymore. But I can get to bootloader again using key sequence. Bootloader is unlocked.
Thank you!

Fastbootd happens part way through a flash-all beginning with Android 10. I assume you are using the flash-all script and now doing each command individually. If not, edit the flash-all to get rid of the -w to dirty flash and keep apps and user data. My guess though is that your path is referring to an older version of fastboot. If you have ever installed the apt version of fastboot, it becomes the first to load in your path. Instead, drop the March files into your updated platform-tools folder and ./ the flash-all command in terminal directly from that folder. In a pinch, you can also sideload the ota zip (which you will need to download separately of course) from fastbootd by entering recovery from there and sideloading. Fastbootd gets you into user space, so you should have adb sideload ability.

there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?

sliding_billy said:
Fastbootd happens part way through a flash-all beginning with Android 10.
Click to expand...
Click to collapse
I did not know that.
What is the "normal" sequence of events? In our case it got to fastbootd and the laptop seemed stuck into "waiting for any device" Am i supposed to press anything or it resumes on its own?
We tried choosing bootloader once and reboot another time but in both cases the process broke down. Are we supposed to wait longer or what?

metricusa said:
there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?
Click to expand...
Click to collapse
metricusa said:
I did not know that.
What is the "normal" sequence of events? In our case it got to fastbootd and the laptop seemed stuck into "waiting for any device" Am i supposed to press anything or it resumes on its own?
We tried choosing bootloader once and reboot another time but in both cases the process broke down. Are we supposed to wait longer or what?
Click to expand...
Click to collapse
I've never ran ChromeOS, but the reboot into fastbootd not retaining the connection would definitely be a problem. The sideload does no reboots until install is complete, so that would be a better way for sure. In reality the phone did at least one reboot into fastbootd. You'd need to try a flash-all with -w in place to see if it could pull off a clean install with the factory image and not lose track of the connection. No doubt it will lose track with individual commands . The normal sequence for factory flash now is just that... run the flash-all .sh it will go into fastbootd during install while terminal will continue to work. There are definitely some spots where nothing appears to be happening on the phone or terminal until reboot. Given the remote nature of your install, I do think a sideload (follow the directions on the pixel ota developers page where you DL the file) is the best option for you.

metricusa said:
there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?
Click to expand...
Click to collapse
I had the same problem with my PixelBook. My conclusion was ChromeOS does not forward the USB connection to the Linux container before the phone times out, but your theory about loosing USB permission may be correct. If you have developer mode enabled on the ChromeBook, try booting into Linux from a USB stick instead of running the Linux container. Unfortunately, I have no other solution.

dcarvil said:
If you have developer mode enabled on the ChromeBook, try booting into Linux from a USB stick instead of running the Linux container. Unfortunately, I have no other solution.
Click to expand...
Click to collapse
I agree but with my daughter abroad she can't do the USB stick thingy.
I'll explore the sideload. I'll have to test everything on my Pixel 3. I was trying to avoid that. I have both a Linux machine and a Chromebook here.
And yes, the permission is lost quite fast during a phone reboot. I tested it. I do however find it amazing that a Chromebook is capable of doing such advanced tasks.
I'll try again tomorrow and report back.

metricusa said:
I agree but with my daughter abroad she can't do the USB stick thingy.
I'll explore the sideload. I'll have to test everything on my Pixel 3. I was trying to avoid that. I have both a Linux machine and a Chromebook here.
And yes, the permission is lost quite fast during a phone reboot. I tested it. I do however find it amazing that a Chromebook is capable of doing such advanced tasks.
I'll try again tomorrow and report back.
Click to expand...
Click to collapse
What if you get phone into fastbootd, then plug in so the phone is recognized, then "fastboot update image-blueline-qq2a.200305.002.zip"
Or just unplug it once it gets to fastbootd and plug it back in...if it becomes unrecognized, unplug and plug it back in again when needed?

wangdaning said:
What if you get phone into fastbootd, then plug in so the phone is recognized, then "fastboot update image-blueline-qq2a.200305.002.zip"
Or just unplug it once it gets to fastbootd and plug it back in...if it becomes unrecognized, unplug and plug it back in again when needed?
Click to expand...
Click to collapse
I'll try that.
Unplugging opens another can of worms:
The reason we are doing this is bc the phone suddenly has a problem charging. Opening the battery setting shows a red battery with the message "can't charge now". Also if plugged in while turned off the little battery shows a question mark.
Google offered to exchange it but shipping it back and forth from Europe is 140$ each way and I got a new phone for less. On top of this I risk having to pay import taxes on it.
So in short, if unplugged the phone dies.
The intent of doing this burn was to see if this issue is software related. As I said it happened suddenly after a simple restart. Battey was fine and after restart was not.
I have a feeling it's not the software though.

Wow, that is really high for shipping. I mean, I ship from China to the US for like 20 USD, beside the point though really. She knows no one with an ordinary PC to test? Or a local cell phone service center in her area that could evaluate it? I mean the battery could be dead, or it could have, ehehe, been dropped and a connection loose or something. Not trying to imply anything there, just saying there are many variables at play. I would say if getting to fastbootd and trying the update does not work, then she should really look for a repair shop. Depending on where she is it should be fairly cheap or even free for them to look at it.

wangdaning said:
Wow, that is really high for shipping. I mean, I ship from China to the US for like 20 USD, beside the point though really. She knows no one with an ordinary PC to test? Or a local cell phone service center in her area that could evaluate it? I mean the battery could be dead, or it could have, ehehe, been dropped and a connection loose or something. Not trying to imply anything there, just saying there are many variables at play. I would say if getting to fastbootd and trying the update does not work, then she should really look for a repair shop. Depending on where she is it should be fairly cheap or even free for them to look at it.
Click to expand...
Click to collapse
Well the option is through fedex/ups. Shipping USPS has resulted many times in the package being stuck in customs for weeks. And the price is not necessarily much lower.
Yes we looked into having it seen by a repair shop but normally we should have been able to do flash it ourselves. Plus it's a good experience for her to be exposed to some linux and the basics of hacking a phone.
Another reason is that this has a high chance of being hardware related so whatever we spend on repair shop is wasted money.
I got her a Samsung A51 and she is out of trouble for now. I have had several bad experiences with pixels so this time I am officially done with spending a fortune on them.
Update as of this morning: It is clear that the USB permission is lost while fastboot performs a reboot during flashing. We tried to quickly re-allow the permission but while the terminal waits for a device patiently it looks that the loss of link is long enough for the phone to decide that something went wrong and goes into fastbootd.
We also tried to flash just the boot.img in both slots . that went well apparently but did not change anything and the phone is still unbootable. Tried recovery but it went back into bootloader with the error that it cannot boot boot.img.
So next step is sideload. i have to figure how that works

fastboot reboot fastboot, select recovery, apply update from ADB, adb sideload whatever.zip
Seems if there is no way to keep the phone on without it plugged in that is a problem. What about a cheap wifi charger, will that keep it on? I mean the phone will technically reboot going from bootloader to fastboot (fastbootd) and the permission will be lost. At least a repair shop could use a proper computer to test it.

wangdaning said:
Seems if there is no way to keep the phone on without it plugged in that is a problem. What about a cheap wifi charger, will that keep it on?
Click to expand...
Click to collapse
The phone stays on while it is connected to usb. Never died in this process. The connection loss is because of permissions not power.

Latest update: adb sideload worked just perfectly phone is back in running condition.
The bad news, which was expected, is that we did not solve the battery problem so it's hardware related. See attached pic.
In any case: A million thanks for the help. You guys rock!
At least we found out that a Chromebook can do some of these tasks but cannot do the flashing.
I placed a question on Chromebook community about a possible way to give Linux permanent permission to USB. If I find out any good news I'll report back.
Thank you and stay safe!

metricusa said:
Latest update: adb sideload worked just perfectly phone is back in running condition.
The bad news, which was expected, is that we did not solve the battery problem so it's hardware related. See attached pic.
In any case: A million thanks for the help. You guys rock!
At least we found out that a Chromebook can do some of these tasks but cannot do the flashing.
I placed a question on Chromebook community about a possible way to give Linux permanent permission to USB. If I find out any good news I'll report back.
Thank you and stay safe!
Click to expand...
Click to collapse
Glad you got the device up. As for the charging issue, have you tried a different wired charger or a wireless charger? I assume you are converting power somehow in Europe.

sliding_billy said:
have you tried a different wired charger or a wireless charger?
Click to expand...
Click to collapse
Yes. Tried different charger and a battery pack and also charging through USB from laptop. Did not try wireless. Before I bought the new phone she was using the phone connected to a battery pack.
As you can see in the pic the battery is red and it says "can't charge" while confirming that it does receive power.
I Googled the issue and there are several reports about same behavior. I also did talk to a repair shop over the phone and they said that the power module goes bad and it is a known problem with pixel 2 and 3. He also mentioned that there is a class action lawsuit but I cannot confirm the info.
It doesn't really matter at this point.
My aim was to eliminate the remote possibility this problem was due to some software issue. We solved this and from now on it's a google issue. As I mentioned Google offered to exchange the phone. But with COVID we had to postpone some flights when we could have made the exchange.
I will contact Google and ask for some workaround the COVID crisis. I hope they will be cooperative. I don't see why not.
Thank you all for your help!

Related

[Q] Tablet stuck in password screen + recovery mode doesn't work

Hello,
I'm sorry to bother you with an apparently repetitive thread, but I assure it is not.
I've been dealing with this problem for over a year now. Of course there were times that I simply gave up, but every now and then I searched all over the internet (seriously; very resilient, I am) and tried everything. Nothing seems to work.
The issue is: one day I was reading something on Google Reader and the tablet restarted. When it came back, it was in this password screen.
[AS A NEW USER I COULDN'T POST THE IMAGE - please see attachment ending in 41]
Detail: I had never, EVER set any kind of password. I don't do this with any of my devices unless I'm obliged to (as in Windows 8, this big piece of shiite).
So the thing is: I did not set a password, I did not choose to ask for a password in any situation and there isn't a single combination that I haven't tried. The thing doesn't even ask me to stop -- like 'hey, you've tried your 30k input, I think you should stop now'.
Now, for you not to start cursing me, I tried EVERYTHING that is basic and post-basic to fix it. I did wipe the data, I tried flashing another ROM, I did cold boot, factory reset, EasyFlashed, nvflashtf and whatnot. I swear to GoogleGods that I, as a non-expert-but-very-keen-on-technology, could.
Another thing that happens is when I try to enter the recovery mode, after using the nvflash, it doesn't work. The image that appears to me is this one:
[SAME THING -- attachment ending in 38]
Again: I'm not a complete noob. I know how to get into things; all I need is a simple guidance. I'm really sorry if this has been posted before and only I couldn't find it, but I won't be so if someone helps me to get it and solve my problem. I can't stand this anymore -- now it's just a matter of pride.
Thank you all.
This happened to me on my SL101 after I flashed a ROM of some sort. I used ADB commands to push the stock ROM back to it and to push another Recovery to it. Mine was in worse shape, Recovery loop, and then I finally got it to where yours currently is. My physical nor on screen keyboard would even work. Look up some ADB commands, perhaps you already know them, and attempt to either push the stock ROM or a new Recovery blob back to it.
D
DatDude123 said:
Look up some ADB commands, perhaps you already know them, and attempt to either push the stock ROM or a new Recovery blob back to it.
D
Click to expand...
Click to collapse
Yeah, well, y'know, I'm not at this level yet, but I'll dig into ADB and stuff.
I tried to use this sometime in the past, but my computer was so bad back then that I had to give up to keep my sanity. Now I've got a fairly good one (very good, considering the few things I use it for), however much less time.
Tonight is the night, though. I'll study as much as I can and I'll fix this ****. Any tip you may remember now would be useful.
Thanks.
I'm struggling with something even before I start: there's no way I can get access to the system and turn the USB Debugging on.
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
maycondimas said:
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
Click to expand...
Click to collapse
For some reason i thought you were on th sl101(slider) so i didnt comment. So heres the deal, any fix is going to be data destructive(nothing you can do at this point as even if you manage to pull data from the tablet, it will be encripted) You need Easyflasher(dev section) follow the instructios there (basically donwloading stock firmware from asus and by using nvflash in apx mode it will re-partition storage, and upload the stock firmware to the tf101)
If you hit any problems, post them here and ill help you further
Edit: just read you post more, if you tried easyflaher and it didnt work, please post the details of what you tried within easyflasher.
Its a strange issue, if it happend to me and id tried the things you already have, this is what id try:
-Flashing ubuntu from the dev section(i known very little about how nvflash works but it maybe only re-partitioning certain partitions, ubuntu i would imagine would require a full re-partitioning)
-alternativly (or on top of the previous idea) use one of the ubuntu installers(OLiFE on ubuntu worked the best for me, but franks tools/ newer software based on franks tools should work fine) and flash the Prime! rom on its own.
If these dont work, your last resort is asus - but thats a long shot lol
maycondimas said:
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
Click to expand...
Click to collapse
If you can't get into anything, but you can enter APX Mode, but NVFlash doesn't work, then I'm not sure anything will as NVFlash completey deletes and recreates all the partitions on the drive
So unless you have been unlucky and downloaded a bad version of an NVFlash ROM....
I know you say you have used NVFlash but I`ll stick this here anyway
The way I restore is:
Connect tablet to PC and make sure the tablet is turned off (Make sure it is the only USB device connected other than keyboard/mouse)
Hold Volume Up + Power for a few seconds until you hear the USB connect sound on the PC, release the buttons, you are in APX mode
Install APX drivers if you have not already
Now extract this
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
And run "download.bat"
I think you should see some text appear on the tablet screen, and progress will be shown in the command prompt window on the PC
Wait for it to complete 100%
Its been a while so I can't remember if the tablet will reboot on its own or if you need to hold power for 30 seconds to get out of APX mode
Either way, make sure it is completely finished and reboot the tablet
Only thing I can remember going wrong with NVFlash was the first time I rebooted after a sucessful boot, it would hang on a black screen
Just hold power for 30 seconds and then power on normally, done, if it has worked you have your tablet back, if not, I think its a hardware issue > see asus
Im very keen to get this fixed/ find the issue as uptil now I thought the tf101 was virtually software invincible, you need to pay attention to what the nvflash process says, the one thing I can think of as to why nvflash didn't work is it can't write over encrypted partitions although that would make no sense why it wouldn't.
Just a suggestion... make sure you're not docked. Some people report issues when nvflashing while docked (I can't replicate those issues except with the Tubuntu tool).
Is there a solution?
I also have an error! see picture

Stock TF700 boot loop, can't turn off device.

Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Wow - you're in a difficult situation...
You being on stock I can only imagine the bootloop is caused by something you installed.
So if you can access settings and are able to uninstall apps, just keep doing it until you are back to the original stock setup.
Are you sure the files you are trying to save are still on the SD card? Don't know how you flashed 10.6.1.14.8, but flashing a complete firmware package ususally erases /data - although your persisiting bootloop indicates it didn't...... if the bootloop is caused by an app. And I can't imagine what else would cause it.
You could try to do a factory reset in Backup&Restore but you will loose the contents of your /data partition...
You can flash the 10.6.1.14.10 firmware file, but most likely you will also loose your data.
The only way I can think of to replace your bootloader and firmware without data loss is if you try to find a copy of the 10.6.1.14.10 dlpkgfile. That is the OTA update file Asus pushes out to users. It's a patch file, meaning it only replaces/updates new files and leaves everything else alone.
If you find the dlpkgfile on some forum you would have to place it into your /cache directory and reboot - and I don't know if you can copy it to your tablet before it bootloops again.
Unfortunately the reason for your bootloop is probably an app on the same partiton with the data you don't want to loose. Unless you manage to uninstall the culprit I don't see much hope....
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
_that6042401 said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
He's bootlooping..... How does he go into settings and turn on USB debugging?
I think the best option maybe to flash a stock Asus ROM from their site but that will wipe all data including those photos......
zanadoo22 said:
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Click to expand...
Click to collapse
I have not use this method but you could try.
You need a boot OS tool on your external sd and run it from your external sd so you can access to your internal sd to copy files from there. You can search on the internet and you should find more information on how to use them depending on what boot os you are using.. Good luck.
zanadoo22 said:
and I only have about 10 seconds before it freezes and restarts.
Click to expand...
Click to collapse
sbdags said:
He's bootlooping..... How does he go into settings and turn on USB debugging?
Click to expand...
Click to collapse
Preferably FAST.
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
LetMeKnow said:
You need a boot OS tool on your external sd
Click to expand...
Click to collapse
What is a boot OS tool?
_that said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
zanadoo22 said:
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
Click to expand...
Click to collapse
What Windows version do you have on your PC?
You can check your drivers in Device Manager. Open it, look for your tablet under Portable Devices and check if the driver has a yellow exclamation mark next to it. You should be able to update/install/uninstall the driver from here.
Try to find out if there is a setting in your Windows version to only allow Microsoft signed drivers and disable it.
Sent from my DROID4 using Tapatalk 2

New Verizon Ellipsis 10 Tablet

I purchased the new Verizon Ellipsis 10 in late November. I believe the tablet was released for sale in mid November. My question is can it be rooted? I see the Ellipsis 7 and 8 can rooted. Wondering if anyone would be working on this or because it from Verizon no one cares. I can't find the tablet mentioned on any search that I do. I Have been checking daily to see if the device will have development on it. Thanks in advance for any information.
In the same boat. Need some help you smart tech guys out there. How can I root my Ellipsis 10?
I have the same tablet, and I do not think it could be rooted, at least not in the near future. The tablet comes encrypted (which I am not too happy about....I just noticed it) and cannot be decrypted, even if you do a factory reset. It runs fine as it is, but would be greatly enhanced if it could be decrypted. I also think there are very few devs on this forum that really care a lot about this tablet, so you may not see too much work being done on it.
Same here, just picked one up. Really hoping that there will be a root for this at some point soon. Someone please help us all out!
wish I would have saved the 50$ now, and got the Samsung tablet for free... it's OK, the biggest problem for me is the audio output being too quiet. all the "volume booster's" on the play store have been jenky, to say the least. if anyone has suggestions of a "good, volume booster", or work around, please let me know. thank you for you time.
Oh, No! Sadness!
mikekoz said:
I have the same tablet, and I do not think it could be rooted, at least not in the near future. The tablet comes encrypted (which I am not too happy about....I just noticed it) and cannot be decrypted, even if you do a factory reset. It runs fine as it is, but would be greatly enhanced if it could be decrypted. I also think there are very few devs on this forum that really care a lot about this tablet, so you may not see too much work being done on it.
Click to expand...
Click to collapse
Please, influence some senior devs to help you with this issue!
qtair7 firmware files
https: / / " www dropbox com " /s/f8ye7yw24mjqiva/IR7-20C59.7z?dl=0
just fix the text when u enter in address bar (-""'s,+.'s)
so i downloaded the IR7-20C59..7z package from the software upgrade/repair tool from verizon... I extracted the files and sent the boot.img to my tablet (qtair7) and used magisk manager to patch the boot.img then I used ubuntu to adb pull the magisk-patched-boot.img and modded it using abootimg and changed a few things from default.prop.. ro.secure=0 ro.debuggable=1 and drm.service.enabled=false .. (just saying im an amateur android enthusiast with little experience. ive played with image kitchens and compiled a kernel and ported a rom for the samsung on5 indie variant to have sound on my smg550t1. worked but all google services and apps crash constantly.. but anyways) i dont really know what im doing just saying this is what i did. repacked magisk-patched-boot-new.img then i sent the adb reboot fastboot command to my tablet and it fastboot flashing unlock , fastboot flashing unlock boot, fastboot flash boot magisk-patched-boot-new.img. fastboot continue, fastboot reboot.. the tablet boots and is rooted with magisk.. now i installed busybox to sbin. i have done this 2 times. im not sure if its the busybox or the magisk, but when i reboot following the above steps i get the verizon splash screen and in the bottom righthand corner of the screen it says modified. then boots to recovery. and now can only boot to recovery. now i have the upgrade/repair tool .iso on usb flashdrive that i use to repair my device from this state. which sometimes is a pita.. i have to continually attempt to repair sometimes it takes 2 days.. before it finally works.. i dont know why.. but it boots from fastboot the first time fine. and would like to know how to stop the soft bricking of my device or how i can obtain a twrp.img for this device QTAIR7.. please help ive been working on rooting my tablet for over a year. and feel that i am very close . thanx
Anyone interested in the system.img or any other partitions.. the Dropbox file is only the recovery flash files. I think. I know I couldn't edit system.img from the file with any kitchen but the system.img I dd'd from my device can be edited with kitchen. It's is 3.7gb so in not going to post unless someone can do something with them
Please share some info on the file you posted,..
jonthn41 said:
qtair7 firmware files
https: / / " www dropbox com " /s/f8ye7yw24mjqiva/IR7-20C59.7z?dl=0
just fix the text when u enter in address bar (-""'s,+.'s)
Click to expand...
Click to collapse
Hello, THANK YOU!! This is the most progress I have made in months! I don't know what it is, what it offers, or what to do with it yet, but it is a step!
Could you maybe say what it is, what it will do (how it helps..) and what to do with it?
My Verizon Ellipsis 10 (qtair7), even after wiping the cache, even after doing a factory reset, (even after 'disabling' all but FEW APPS!) JUST SPONTANEOUSLY REBOOTS every time i try to do anything, I try to watch a video it is fine for 5 minutes or an hour then I push volume up or touch the screen and suddenly it reboots, totally random, Clearing the cache gets it to works for a while but it always does it again it has NEVER been usable really,.. It pops up some screen often like"Google Play Services have stopped' something like that,.. Will this help with any of that? Make it more,. stable?
I wish I could just do ANYThING simple to make it better I just use it for video playback,.
THANK YOU!
I have the same tab with the same issues. Rebooting, random cut out and full on reboot. Just before it became target practice I decided to take it apart, just because that's what I do when I'm bored and my ADHD is taking over. I looked up the tab on youtube to see if there was any vids of how to get it apart and found a guy that said he fixed the with the tablet that no one could figure out. Meh I was like ok I'll give him a couple seconds checked it out. He found that all connections, screws holding boards down, and power were all loose. Once he went through all of that it had fixed the issues. So I tried it and damn, everything from screws holding boards down to power feeds were all loose, really bad loose. Got mine working good now. Haven't had issues since. Now if I can get it rooted I'll be good. And I suspect the loose connections would also potentially cause the battery to go bad from excessive amperage draw and charge in short time, over time.

Updated Mate 9 via firmware finder now bricked - screen won't initialise

Hi folks.
I updated my mate 9 last night using firmware finder, phone rebooted, did the update thingy and then switched off. It didn't boot back up so tried turning on - nothing. Plugged in the charging cable, no light came on to indicate it was charging.
I have tried connecting to my computer using the USB 3 port and the computer does seem to recognise it as it makes that jungle sounds when connected (computer) and again when disconnected. I have tried doing the power vol down and that seems to create the PC to make the sounds again but there is nothing displaying on the phone itself. If you looked it at you'd think it was off.
So I guess it's a positive that the PC is getting some kind of response, and the phone must be working.
Can anybody suggest as to how I can get things back up and running? Remember the screen doesn't work on the phone since the update. I am on C636 converted from AL00 early last year.
Have tried HiSuite just in case but phone isn't recognised.
Thanks.
DT.
adb commands
Shooting from memory here...but have you tried any of the adb commands to see if the computer is seeing the phone?
adb kill-server
adb start-server
adb devices
If you get something from the devices command, then you should be able to
adb reboot
Also, if you are able, find another computer and install ADB as well has HiSuite software/drivers.
dwcasey said:
Shooting from memory here...but have you tried any of the adb commands to see if the computer is seeing the phone?
adb kill-server
adb start-server
adb devices
If you get something from the devices command, then you should be able to
adb reboot
Also, if you are able, find another computer and install ADB as well has HiSuite software/drivers.
Click to expand...
Click to collapse
Thanks for the reply.
Nope - doesn't seem to work. No idea what's happend but it appears to be kaput. Other than my PC recognising that I am connecting something when I plug it in to a USB socket, there is no other way of knowing if the device is even on. I've left it on charge over night, tried the power up/down (even though I can't see the screen) and have tried the appove. It did list a port that was open but no devices appeared as listed.
Will continue having a look to see if there are any other methods. Appreciate your help dwcasey.
DT
Totally at a loss as to what's happend. If I leave it plugged in to my PC it seems every 5 minutes the PC disconnects and reconnects to the phone (notifaction sounds). When plugged in, if I press the power button it gives the same notification sound to indicated disconnected and reconnected. Have tried updating drivers. Device is not listed under ADB when I type the command. It's a Chinese AL00 6/128gb so can't get it reparied locally (UK). Debating whether to bin it as I fear the worst. Will opening up and removing the battery do anything? A bit like removing the cmos battery from a motherboard and it resets?
Cheers for any help.
I've come to the conclusion that the phone is dead and that I have a few options.
1 hope for a repair but it'll cost a fair bit given it's a Chinese model and I'm in the UK.
2 sell it on fleabay, but it contains personal data.
3 stick it in a drawer and console myself with my Note 4, that's it originally replaced.
Phone is definitely toast. When I connect to a PC it loads as USB SER. It still makes some sort of connection but it's impossible to access the phone Absolutely no response from ADB/Fastboot.
Clearly an issue with the update using FF given It was this that caused things to go tits up.
Back to my Note 4. First time I've ever had this happen. Fingers burned, dammit.
btblue said:
3 stick it in a drawer and console myself with my Note 4, that's it originally replaced.
Click to expand...
Click to collapse
If you leave it long enough for the battery to go down (no idea how long that might be) then from a 'drained' phone state to plugging in, you might see a 'powered off charging' screen which would be nice. At least you might have a starting place once again.
Happened to me if you have no warranty ,then it will cost about 200-300 dollars to replace your motherboard.
btblue said:
Totally at a loss as to what's happend. If I leave it plugged in to my PC it seems every 5 minutes the PC disconnects and reconnects to the phone (notifaction sounds). When plugged in, if I press the power button it gives the same notification sound to indicated disconnected and reconnected. Have tried updating drivers. Device is not listed under ADB when I type the command. It's a Chinese AL00 6/128gb so can't get it reparied locally (UK). Debating whether to bin it as I fear the worst. Will opening up and removing the battery do anything? A bit like removing the cmos battery from a motherboard and it resets?
Cheers for any help.
Click to expand...
Click to collapse
Instead of binning it I suggest you disassemble your phone completely with the help of video guides and some fine screw drivers and replace the motherboard yourself. They shouldn't be too expensive on AliExpress. The phone and its components are quite easy to wrap ones head around. Just be wary of the glue they use to stick the battery to the case. It can be a bit of a bastard to get off, but it's worth trying for sure! I've opened it up for screen and camera replacement myself. And I don't count myself as a "phone repair geek" Best of luck on this endeavor!

Unlock Screen through PC??

My wife dropped her Pixel 4a yesterday and completely broke the screen. You can't see anything except done bright green splotches and lines and it doesn't respond to touch. I bought her a new phone and synced her account, but because her Drive storage was full, the last months photos are not synced. I upgraded her to the 100gb plan and let the broken phone sit hoping it would automatically upload the missing photos but it did not.
So at this point my only options are to somehow connect it to my computer and get them, or replace the screen. I'd rather not pay $140 to replace the screen JUST to get a month's worth of photos.
My question is, can I connect the phone to the PC and remotely enter her PIN and then access the files?
I searched online but the two softwares I found say they will wipe data.
x_orange90_x said:
My wife dropped her Pixel 4a yesterday and completely broke the screen. You can't see anything except done bright green splotches and lines and it doesn't respond to touch. I bought her a new phone and synced her account, but because her Drive storage was full, the last months photos are not synced. I upgraded her to the 100gb plan and let the broken phone sit hoping it would automatically upload the missing photos but it did not.
So at this point my only options are to somehow connect it to my computer and get them, or replace the screen. I'd rather not pay $140 to replace the screen JUST to get a month's worth of photos.
My question is, can I connect the phone to the PC and remotely enter her PIN and then access the files?
I searched online but the two softwares I found say they will wipe data.
Click to expand...
Click to collapse
You MIGHT be able to get the phone to show up on Windows by mirroring it (either over USB or over Wi-Fi).
My phone isn't broken, but I can easily mirror the phone and unlock the lock screen and view it and control it using free software on Windows.
You can also mount the entire phone onto Windows as a drive letter over Wi-Fi if you have a webdav server on it.
Here are some screenshots of what I do, and I have some tutorials here on how to set that up if you need them.
if you didn't enable usb debugging before the accident, nothing can be done now
Nfury00701 said:
if you didn't enable usb debugging before the accident, nothing can be done now
Click to expand...
Click to collapse
Good point!
I assumed the op had already enabled USB debugging.
In fact, most people I know (including me) enable Developer Options the instant we get a new phone, and then we enable Mock Location and USB Debugging the second instant, so every Android device I've ever touched has had those two options set as the first things done.
But the user we're both trying to help might not have done that.
If he has any server (FTP, WebDav, SMB, etc.) set up to run at boot time, then he still has a chance (as most people set up one of those also, as far as I know).
If not, this is a lesson to the rest of us to have a failsafe plan if the screen won't work (my personal favorites are Vysor & WebDav).
I'm pretty certain I didn't enable the USB Debugging. Maybe I'll order a cheap screen from eBay just to get it working. Obviously it would be very low quality compared to OEM, but it's a fraction of the price and should get the job done.
Thanks for the replies!
Edit:
Well scratch that idea. Can't get a screen for under $130 now. The repair shop quoted me $140 I think and it's an OEM replacement. Still though, not gonna do it, at least not right now.
x_orange90_x said:
I'm pretty certain I didn't enable the USB Debugging.
Click to expand...
Click to collapse
Drat.
I am racking my brain trying to figure out a way you can access the phone from your PC (over Wi-Fi or over USB) without interacting with the screen, which I do all day, every day, but I'm already connected over a variety of servers that are either on the phone (e.g., WebDAV) or on Windows via adb (e.g., Vysor, Scrcpy).
I guess the lesson for anyone reading this is set up a wireless server now, as they're free, and they need ZERO software on Android.
x_orange90_x said:
I'm pretty certain I didn't enable the USB Debugging. Maybe I'll order a cheap screen from eBay just to get it working. Obviously it would be very low quality compared to OEM, but it's a fraction of the price and should get the job done.
Thanks for the replies!
Edit:
Well scratch that idea. Can't get a screen for under $130 now. The repair shop quoted me $140 I think and it's an OEM replacement. Still though, not gonna do it, at least not right now.
Click to expand...
Click to collapse
I dont know if this will work, and if you need the bootloader unlocked (for the TWRP stuff), but I would try the following.
Try to access the phone in recovery through adb. i think you would of had to have previously authorised adb from your PC to the device, for this to work.
NB: You can run TWRP, without flashing it.
Run adb through TWRP, and try accessing the photos/data. I would guess you wil need to unencrypt the phone first.
Run TWRP, unencrypt the phone and do a backup, and try viewing the contents through 7Zip on your PC
DiamondJohn said:
I dont know if this will work, and if you need the bootloader unlocked (for the TWRP stuff), but I would try the following.
Try to access the phone in recovery through adb. i think you would of had to have previously authorised adb from your PC to the device, for this to work.
NB: You can run TWRP, without flashing it.
Run adb through TWRP, and try accessing the photos/data. I would guess you wil need to unencrypt the phone first.
Run TWRP, unencrypt the phone and do a backup, and try viewing the contents through 7Zip on your PC
Click to expand...
Click to collapse
Sounds plausible, but I'm no expert on this topic. Remote-running TWRP sounds very promising. I'm willing to give it a shot if you can instruct me or provide me instructions to do so.
x_orange90_x said:
Sounds plausible, but I'm no expert on this topic. Remote-running TWRP sounds very promising. I'm willing to give it a shot if you can instruct me or provide me instructions to do so.
Click to expand...
Click to collapse
Its not what I would call "remote running". Its running it without flashing it.
The following is a log of my script. I copy the TWRP img file to g:\recovery and then run the following in a command prompt on windows.
Code:
>g:
>cd \recover
>PATH=%PATH%;"%SYSTEMROOT%\System32";"C:\Java\x86\Android\android-sdk\platform-tools";
>fastboot devices
08721KEC209540 fastboot
>fastboot boot sunfish_twrp201017-test5.img
Its probably an outdated TWRP, and I changed the return from fastboot devices for privacy
I defer to the extraordinary knowledge of DiamondJohn where all I want to add is that I searched EVERY similar thread on XDA and referenced over two hundred of them, sorted in LIFO order, over here:
What is the best XDA solution to control Android on the PC & recover data over Wi-Fi when the user suddenly has an unresponsive broken screen?
The OP "might" profit from reading some of them, particularly:
Tutorial : How to turn on USB debugging on device with broken screen, by MiroBiala, on Jun 28, 2017
[Tool][Windows] Control a device with a broken screen. Now with touchscreen support!!, by k.janku1 on Jun 17, 2014
[TOOL] ADB Data Recovery (recover data from a phone with broken screen), by FuzzyMeep Two, on Jun 26, 2013
Bear in mind that adb can remotely push buttons from the PC to Android over Wi-Fi if you happen to know the pixel location of those buttons on the Android device (but, of course, adb has to work first).
Good luck. You're in good hands with DiamondJohn (who knows far more than I ever will about this topic).

Categories

Resources