Ok I recieved the above device from a coworker. They had gotten the device for their kid for Christmas, non 3G version. Anyway their kid enabled airplane mode, and took the tablet to school. They had airplane mode on to save battery. They had a lock screen on the tablet. Well as luck would have it he left it on his desk, and the other students locked the tablet so the Gmail account had to be entered. Well with airplane mode enabled there was no way to authenticate with Gmail for recovery. Upon massive Google searches, I discovered this tablet had no hard key press recovery. Essentially it was a bricked device, even the company Sungale had no info on recovery. Well after working at it I discovered a fix. ADB is on by default for this device. Boot into ADB then issue the command
adb shell
wipe data
adb reboot
Now setup your tablet just as you did the first time you opened it.
Hope this helps guys!
Pntblltrc4
Root Access
One other tip, this device is rooted out of the box via the shell. So realistically it should be very simple to port clockwork to this tablet.
pntblltrc4
pntblltrc4 said:
One other tip, this device is rooted out of the box via the shell. So realistically it should be very simple to port clockwork to this tablet.
pntblltrc4
Click to expand...
Click to collapse
Out of curiosity, were you able to find out anything more about upgrading the device? I own an ID707WTA as well, and I've been searching for an unofficial ROM but nobody has seemed to have tried to make one yet.
device not found error
I keep getting a device not found error.... What do you think is the cause or how can you get around it?
Related
Hello all,
I have a friend's above mentioned phone. He has not modified the phone in any way. He said that a couple days ago, it just stopped functioning properly (no drop, water damage, etc.) When powered on, it just hangs at the HTC screen. I can get to the bootloader. My goal is to recover photos from the device (he has all of his baby's pics on it, no backups).
I have adb and fastboot installed on my computer and they work with my own devices. My computer can see the One via fastboot ("./fastboot devices" outputs the phone ID), but my computer can't see this HTC One via "./adb devices". I suspect that this phone isn't in USB debug mode.
I've read that unlocking the bootloader will erase all his data... where should I start in my adventure to rescue his baby pictures and insure that he will name his next child after me?
ayhindot said:
Hello all,
I have a friend's above mentioned phone. He has not modified the phone in any way. He said that a couple days ago, it just stopped functioning properly (no drop, water damage, etc.) When powered on, it just hangs at the HTC screen. I can get to the bootloader. My goal is to recover photos from the device (he has all of his baby's pics on it, no backups).
I have adb and fastboot installed on my computer and they work with my own devices. My computer can see the One via fastboot ("./fastboot devices" outputs the phone ID), but my computer can't see this HTC One via "./adb devices". I suspect that this phone isn't in USB debug mode.
I've read that unlocking the bootloader will erase all his data... where should I start in my adventure to rescue his baby pictures and insure that he will name his next child after me?
Click to expand...
Click to collapse
HTC offered a free 25gb Dropbox account with the One M7... If your friend did not take advantage of this offer and set the phone to auto update photos and videos their is probably nothing you can do now to save them.
adb only works in custom recovery and when the phone is booting up with usb debugging enabled... so any adb commands will fail. fastboot will work in the bootloader but is very limited in the functions it can do .. flash rom/ruu/firmware , unlock/lock bootloader , erase cache , reboot ..etc nothing really useful to you. A factory reset from recovery will also destroy all the photos on the device. This is one of the main reasons I unlock and flash a custom recovery on my phone the first few days i get it. you just have so many more options when the custom recovery is installed.
Hello, back again with a similar issue on a different phone.
I was unable to recover data from my friend's phone, but I was able to get it running again! I get it back to him and he informs me that the gremlins from his device must have somehow gotten into his wife's phone...
She has the same device, an AT&T One X (M7). Her device presents in the same as his (bootloops to the white HTC screen), but she has no data she wishes to recover. She'd just like it to work again.
I run through the same steps as I did with his first device, but things don't play out as I expected. I get it unlocked and get TWRP 2.7.1.2 installed without incident. However, the phone still bootloops into the white HTC screen.
What is my next move?
Thanks!
Did you clear the cache?
Hey guys,
So my LG G3 finally took a dump on me and I decided I'm done spending 600+ dollars USD on cell phones , so I picked up this Alcatel One-Touch Allura for around 120$.
There doesn't seem to really be any information about the device online, or even any reviews. I've been trying to root it on my own but am having no luck.
None of the "one-click-roots" work that I tried (surprise surprise). ADB doesn't run as root. For some reason ADB only works while the phone is on, and not in recovery, for the most part... I've installed the USB drivers that you can find on the phone under the CD USB option, I've tried universal Android USB drivers, I've tried updating my Intel USB drivers, but still nothing. ADB will not work while in recovery. The phone goes --start adb-- and then nothing, it just sits there. I AM able to use ADB when I hit "apply update from ADB" so I can kind of get ADB to work in recovery, just not where it says --start adb--, that still doesn't work even after I come out of the adb update menu. I tried to load a few things through sideloading but they all fail because of failing signature verifications.
Anyway, I can get it into recovery but I can't get into the bootloader, and the "allow oem unlock" option doesn't seem to really do much from what I can tell, since I can't even get into fastboot. This seems like a pretty solid device and I like the specs/aesthetics, but I would really love it rooted. I've never really done much with android before so please excuse any terms I may have used incorrectly.
Of course I will be more than happy to try any suggestions/answer any questions I can about the device. I would post a pic of the recovery screen but I need to boost my post count first..
Turns out kingo root works.
Meepbob said:
Hey guys,
So my LG G3 finally took a dump on me and I decided I'm done spending 600+ dollars USD on cell phones , so I picked up this Alcatel One-Touch Allura for around 120$.
There doesn't seem to really be any information about the device online, or even any reviews. I've been trying to root it on my own but am having no luck.
None of the "one-click-roots" work that I tried (surprise surprise). ADB doesn't run as root. For some reason ADB only works while the phone is on, and not in recovery, for the most part... I've installed the USB drivers that you can find on the phone under the CD USB option, I've tried universal Android USB drivers, I've tried updating my Intel USB drivers, but still nothing. ADB will not work while in recovery. The phone goes --start adb-- and then nothing, it just sits there. I AM able to use ADB when I hit "apply update from ADB" so I can kind of get ADB to work in recovery, just not where it says --start adb--, that still doesn't work even after I come out of the adb update menu. I tried to load a few things through sideloading but they all fail because of failing signature verifications.
Anyway, I can get it into recovery but I can't get into the bootloader, and the "allow oem unlock" option doesn't seem to really do much from what I can tell, since I can't even get into fastboot. This seems like a pretty solid device and I like the specs/aesthetics, but I would really love it rooted. I've never really done much with android before so please excuse any terms I may have used incorrectly.
Of course I will be more than happy to try any suggestions/answer any questions I can about the device. I would post a pic of the recovery screen but I need to boost my post count first..
Click to expand...
Click to collapse
Meepbob said:
Turns out kingo root works.
Click to expand...
Click to collapse
Have you been able to find a working recovery for this phone? I picked up one tonight for $89 after shattering the screen on my Nexus. I'd appreciate your input.
Yes Kingo Root works, and I used supersume to use supersu instead of kingos superuser. Now does anyone know if there is a custom recovery or custom rom for Marshmallow?
Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this
If powered on, and plugged in to PC, is it 'seen' at all?
robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it
If it is seen, there is a chance you can get data off it.
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe
Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli
Hi everyone,
This is my first thread here eventhough i m following these forums whenever I'm doing stuff with Android. I am also a programmer, not particularly an Android expert, but whenever I need to I use Android tools too. Anyways, today I realized my phone's touchscreen is broken somehow. And I have pattern lock. Normally my developer mode is enabled but darn when I connect my phone to PC I cant just tap to activate Usb connection. I searched through web, spent at least 6-7 hours looking for solutions. Here are what I got:
- I can't use Adb because my phone is not rooted and for most commands I got "closed" error.
- I tried various tools and methods, mostly from here but all end up not being able to confirm because of touchscreen malfunction.
- Tried to root it through Adb didnt work
- Can't seem to use fastboot, fastboot dont seem to see my device eventhough Adb can (I couldnt see any fastboot options in factory or recovery mode. Actually Factory Mode was only tests, and recovery mode has update from adb,update from sd card, update from cache, wipe, backup and restore options.)
Other than that I tried all I can except actually disassembly of my phone. So, at this point I wonder "If" there's a way of connecting my phone to my pc. Soon I ll buy a new display and replace it for sure. But I see this as a reason to dig into Android and dont want to miss the chance by being too lazy.
Thanks in advance.
Hi, when the Nexus 7 2. Gen came out in 2013, I bought it and used for 3 years until 2016. Unfortunately, I remember I dropped the device and the display cracked and made it impossible to use, and because a new one was 50 Euros back then, I thought it wouldn't be worth repairing it.
Now in 2020 I plugged in a OTG mouse, charged it and tried to find some funny stuff I could have stored like pictures from 4 years ago. However, there's a lock screen with password I have to prompt in which I can't remember anymore. The device is running Android 5.*, but I don't know which one for sure, there is no "Emergency call" to try this lock screen camera bypass bug.
The device has its bootloader unlocked (an unlocked lock is shown when I power on the device), and I rooted it 4/5 years ago so I could use my PS3 controller via OTG (This needed root permissions for some reason). I have also noticed that the tablet is still connected to my home WLAN connection.
Is there any chance to bypass the lock screen and/or recover data from it?
Edit: I managed to enter recovery mode but I can only wipe the whole device here, no backup. My android version is 6.0.1.
If you can establish an USB-connection between phone and PC
Code:
adb devices
then you can retain the data that you want to have by means of ADB, too.
Example:
Code:
adb pull /storage/emulated/0/DCIM C:\DCIM
jwoegerbauer said:
If you can establish an USB-connection between phone and PC
Code:
adb devices
then you can retain the data that you want to have by means of ADB, too.
Example:
Code:
adb pull /storage/emulated/0/DCIM C:\DCIM
Click to expand...
Click to collapse
the problem is that it's not recognized, I probably have to unlock it and then accept that I want to use the phone in ADB.
Norbix1977 said:
Hi, when the Nexus 7 2. Gen came out in 2013, I bought it and used for 3 years until 2016. Unfortunately, I remember I dropped the device and the display cracked and made it impossible to use, and because a new one was 50 Euros back then, I thought it wouldn't be worth repairing it.
Now in 2020 I plugged in a OTG mouse, charged it and tried to find some funny stuff I could have stored like pictures from 4 years ago. However, there's a lock screen with password I have to prompt in which I can't remember anymore. The device is running Android 5.*, but I don't know which one for sure, there is no "Emergency call" to try this lock screen camera bypass bug.
The device has its bootloader unlocked (an unlocked lock is shown when I power on the device), and I rooted it 4/5 years ago so I could use my PS3 controller via OTG (This needed root permissions for some reason). I have also noticed that the tablet is still connected to my home WLAN connection.
Is there any chance to bypass the lock screen and/or recover data from it?
Edit: I managed to enter recovery mode but I can only wipe the whole device here, no backup. My android version is 6.0.1.
Click to expand...
Click to collapse
Hi, maybe you could try to flash an custom recovery to it, since the bootloader is unlocked. After that it'll be a lot easier to delete the lockscreen-password and as well backup the data from it.
Fatal_Scythe said:
Hi, maybe you could try to flash an custom recovery to it, since the bootloader is unlocked. After that it'll be a lot easier to delete the lockscreen-password and as well backup the data from it.
Click to expand...
Click to collapse
This sounds good, you mean something like TWM? Is there anything to consider, do I just sideload this thing via adb?
EDIT: Thanks man, I did it, removed the password file and just got access. Feels like going 4 years back in time.
Norbix1977 said:
This sounds good, you mean something like TWM? Is there anything to consider, do I just sideload this thing via adb?
EDIT: Thanks man, I did it, removed the password file and just got access. Feels like going 4 years back in time.
Click to expand...
Click to collapse
Nice to hear that everything went well.