Related
Ok, so I walked by my Xoom (while docked) the other day and I noticed it was in a boot animation (4.0.3 ICS, stock). I thought that odd since I didn't reboot it. I noticed it was like this 1 hour later so I thought I should give it a reboot. Did the power+Vol-up and it rebooted. Still in an endless boot animation. The volume buttons don't do anything once the messages below appear (normally it would scroll through selections).
Reboot + Volume down produces: "Starting Fastboot Protocol Support" and it's frozen there.
Reboot + Volume up: "Starting RSD Protocol Support 0"
"One Wire: Charger is connected"
"Battery Charge Level: 98%"
(frozen at this point)
Reboot + Both volume buttons: "Cold Booting Linux"
"Reading ODM fuse: 1"
(starts to boot, but endless boot still)
Not sure what else I can do. I work in IT and tech support, so I am very savy. I have rooted many other devices, funnily enough, I was happy enough with my stock Xoom, so I never rooted or hacked it in any way (wish I had now!). I simply enjoyed the Moto updates as they came.
I did a live chat with their (useless) support and they wanted me to depot this unit in for $150, which is insane considering how cheap Xoom's are going for. Considering I have a spare AC brick, Dock, portfolio, etc and i'm not super impressed with any other Android tablets as of today, I don't really want to pick up a better unit even (not yet anyways).
I did search the forums, but didn't find anything specific to my problem.
any help appreciated !!
Thanks
DDD-
I don't mean to come off as rude, but have you tried not using the dock? Perhaps the dock is the issue..
But assuming you tried that:
If you don't mind wiping everything out and starting back over in honeycomb, you could do that reboot + volume down and enter fastboot mode. Its supposed to stay frozen because it is actually waiting for fastboot commands from a computer.
With fastboot, you can flash images on to your xoom.
If you don't mind losing data (you may not have much of a choice) or some risk:
1. Go to http://developer.motorola.com/products/software/
2. Download the images for your device (it will be in a zip) (you may need to create an account.)
3. Extract that zip
4. If you haven't already, set up ADB and fastboot
5. Follow the fastboot instructions on the page given above. (It's under "INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:" ... I wouldn't follow the directions for the Razr...)
6. reboot
If I were you though, I would quickly google "how to restore xoom to stock" I may have left some things out. Use my mini-guide as inspiration. And I am not sure if you would need to unlock your bootloader first before flashing these images.
No worries, not a rude question at all since I mentioned it. It just sits on the dock and charges. I haven't done any of this testing on the dock.
I finally got some justice with Moto-India, they are going to have me ship it in and repair it for free. I did order a Moto Factory USB cable off ebay for $10 just in case Moto wouldn't hook me up on the repair. Thanks for replying though and I will keep this thread in mind if this happens again.
I am glad I could help.
You are very welcome.
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.
Little bit of background first...
Finally got my parents (senior citizens) into the smartphone era after StraightTalk starting doing BYOP and I'd had good service so far, but rather than use his old HTC phone which badly needed replacing, he opted to buy the Huawei Sensa (H710VL) branded by TRACFONE and with service via StraightTalk. Fast forward several months, and the old man has discovered a deal for senior citizens from T-Mobile that he likes better, and has opted to switch carriers. Well, he tried to do BYOP with TMOUS and just continue using the H710VL which he likes, but was informed that they wouldn't unlock the phone for another month because they won't do so until you've had it for a year. So therein came my opportunity to promise something I apparently cannot deliver (I told him I'd take the phone home and unlock it for him)!) He (wisely) decided not to wait for me, and went ahead and bought a new phone from TMOUS so he could initiate his new service with them without delay. But I still want to unlock this phone for him, if at all possible!
Fast-forward a few more days--well, I've been screwing around with this phone in the evenings for the past three days, trying to get the bootloader unlocked, and I'm at an impasse. First I had to tangle with the Google account verification, which wouldn't let me even sign into the phone after boot and get to the home screen because I had done a hard reset of the phone first, and didn't have the old man's Google account and password with which to sign back in. Fortunately, intrepid folks who came before me already found a way around that first hurdle. I took the following steps:
1. Went thru HWStartupGuide process until I was able to connect to my home WiFi network. So, internet connection is established.
2. Backed out of there to get to the first setup screen after the TRACFONE splash screen on boot, and used the "emergency calls only" escape hatch to navigate to the stock dialer app.
3. In stock dialer app, entered (without the quotation marks) "*#*#6130#*#*" which took me to the SIM Card Settings screen. Tapped three-dot menu, tapped, "Add SIM Contact," which took me to the native Huawei Contacts app. In Contacts app for the SIM card, tapped "Add Contact," made dummy contact called "Test" with a ph# of 1234. From list of contacts, tapped the "message" bubble icon next to the new "Test" contact, which opened the stock Messages app.
4. In stock Messages app, typed and sent message with the text "www.youtube.com." For obvious reasons the message doesn't send, but it does appear in the messages window, which renders the draft text's content into a hyperlink to YouTube. Bingo! Tapped link and opened up the YouTube app.
5. From the YouTube app, tapped the three-dot menu again, and tapped Privacy Policy from there. Now I'm into Chrome! Opened Chrome without signing in, and navigated to Google.com.
6. From Google.com, searched and then downloaded apk for Test DPC app. Installed Test DPC and set myself up as the new device owner.
7. Now that I'm the device owner, you'd think it would bypass the Google account verification requirement in HWStartupGuide, but no dice. So, rebooted, took same steps to get back into Chrome. From Chrome, I was able to get to the stock Google device search and navigate to the Settings app.
8. From device Settings app, changed settings to allow installations from unknown sources, then I set the option to allow USB debugging, and opened up the dev options to select "Allow OEM Unlock" in preparation for unlocking the locked bootloader, using the unlock code previously sourced from the official Huawei EMUI unlock code site.
So, to sum up, I've got access to the device in general, can use the web and all the apps on the device, and was thus finally able to disable HWStartupGuide to prevent the previous headache from cropping up again. Here's where the impasse starts.
I have Android SDK and everything I need on my laptop (to the best of my knowledge) to facilitate unlocking, flashing, and all the other fun stuff we love to do with our phones.
I was able to confirm the USB and Android drivers are correct and working fine, as I got both fastboot and adb to recognize and list the device when connected via USB cable to the laptop, and it worked both in command prompt and in PowerShell. Fastboot and ADB commands appear to work when facilitated and entered correctly. That is...UNTIL I tried to use the "fastboot oem unlock <unlock code here>" command. It just says "FAILED" with no error code. I tried this from my stock boot options screen (the screen you get when you boot or restart with power and vol-down pressed), and from the stock recovery screen, both to no avail.
This is where I'm all twisted up. There either doesn't appear to be a true bootloader screen to navigate to, or it's purposefully inaccessible, and I don't know how to get to it. If you do a "adb reboot bootloader" command, it just reboots the phone to Android home screen. The only options from the boot options screen are "Power (turn phone off), "Start" (boot to Android home screen), "bar codes" (screen that shows bar codes for the phone's IMEI, Serial #, etc), and "reboot recovery" (stock EMUI recovery screen), where the only options are 'Wipe/Factory Data Reset," "Wipe Cache," and "Reboot."
I feel like if I could get to a true bootloader screen that allows me to enter adb or fastboot command strings in such fashion that you can enter it and then see the process play out on your device screen, then the unlock code from Huawei would probably work and the bootloader would be unlocked, thereby allowing me to root and flash a better ROM, or at least eliminate bloatware and optimize the device for performance. But for whatever reason, and I assume it's purposeful on the part of TRACFONE/StraightTalk, tbh, there isn't a fastboot-capable bootloader screen like my years of using HTC phones taught me to take for granted.
So there I be...stuck, even WITH the unlock code from Huawei! What a crock! I know TMOUS will apparently unlock it in a month or so, but to me, that's not the point. I should be able to accomplish it on my own with the unlock code I got from Huawei. And that's why I'm throwing my hands up and begging for help.
Is there anything else I can try? Is there any other devious way to perhaps flash a different bootloader interface onto the phone that would allow me to use fastboot commands properly? Is it possible to mount the SD card from bootloader and push an apk to it that would install some kind of generic bootloader screen? I'm now a little out of my league, but I am willing to try just about anything that anyone thinks might work. Any advice or suggestions warmly welcomed...not worried about bricking the phone or anything, as it's not much better than a paperweight in its current form anyway.
Thanks!!
smb282
Hey there forums.
I've been an active browser of XDA but never really created an account but I've done so to have assistance with a particular situation with my device.
So the other week, i had spent 150 dollars on a Sony Xperia XA F3115 from Vodafone, Australia and it turns out that the bootloader was locked because of Vodafone and i wasn't going to pay 50 dollars to unlock it. I alternated and browsed the internet (Mostly XDA but other sources aswell) to figure out if there were any methods of bypassing this, whether it be easy or not - I was willing to try anything that seemed like it had a chance to work, without a 100% failure rate. Reading responses to particular methods, i was drawn into one method of just reflashing the stock firmware onto the device and then rooting, flashing and doing everything from there (as the device was no longer locked by Vodafone at that point).
I have completed this task as of this morning, and the device booted successfully. As soon as i unlocked my device, i had received the general android setup window but half way through, i got spammed with "Name has stopped responding" countless times to the point where the phone was literally unusable, it would just pop up again right after closing it - So i decided to restart the device. This was probably a big mistake, it booted fine but it said "Android is updating" and had the whole "Applications updating 100 out of 255" stuff happening. Then it booted to the lock screen, which i had previously setup before i flashed the device which didn't really surprise me too much.
Then it rebooted. Now every single time i boot the device, it reboots to the "Optimizing apps blah out of blah" and then will reboot upon the notification bar popping up, but no lock screen. I decided that my best cause of action was to download another firmware and try that one instead, but I'm unable to boot my device into bootloader mode as it's impossible to happen. I turn off my device, plug it in and hold the volume down button but it refuses to work anymore.
Now that the situation has been explained, I'd really like your help to see if i can have this resolved. I'm baffled as to why Vodafone even locked it to begin with, since the phone was prepaid and had nothing to do with any sort of plans - nor was it even available as a plan. I don't have the money to buy a new phone, and they have already denied me a refund. I need this phone for work and the mistakes i made were stupid - Please, i need assistance. You're all hopefully more tech savvy than i am in the field of mobile phones.
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).