Hello,
My friend gave me his locked out phone AppTab Dual talk...( a company name unheard of) and asked me to unlock it for him. He doesn't know his account password. Now I tried booting into recovery or anything. I held power and vol down. Some stuff in Chinese came up. Image attached.
And language barrier apart, only vol down and up buttons work in that to scroll through the options . I've tried everything to try and select an option in that. But no luck!
If I hold down vol up and power buttons, something like a broken Android logo screen comes up which I believe is recovery mode for this device.
Then I plugged it on to my PC and installed the adb drivers for it.
adb devices --> I can see the device listed
Fastboot devices --> I can't see the device
adb reboot bootloader --> the stupid phone just reboots into actual rom instead of bootloader.
I tried to see if the bootloader is locked..now how do I unlock it? fastboot OEM unlock? Damn thing doesn't get recognised in fastboot.
I thought I'll enable USB debugging..which I believe isnt enabled.
So I searched online and came across this command.
adb pull /data/property/persist.sys.usb.config ~/
But the out put of this is either "error: no device" or "permission denied"
I don't know what to do. Here it doesn't go into bootloader. If I want to flash a custom recovery, fastboot commands ain't working, if fastboot shud work I shud enable USB debugging some how, and that too isn't working. If I hold down some random buttons also there is no bootloader mode or anything.
And the options which it gives and which I believe will have the factory reset option also doesn't work bcoz I can't select any option in that.
And yeah...I tried one more thing
adb shell recovery --wipe_data
Which also dint work
I tried
adb shell
Wipe /data
Wipe /system
Wipe /all
I also tried to side load one zip package which could disable the pattern lock
Bt that also dint work.
I tried adb USB and then adb side load <file>
Still no luck.
I might just recommend my friend to throw this phone into the water!
Thanks in advance
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Art Vanderlay said:
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Click to expand...
Click to collapse
Well, that still keeps me in the loop. I have to enable usb debugging & if i have to do that i have to root & so on.
Thanks for the reply. No luck with the thread you linked either.
Related
Hey guys, how are you?
Well, I wished to root my Moto G, so I (tryed?) to unlock the bootloader. Alright, done it, but then I ran into some trouble...
After the booting up, everything started forceclosing and since then, when I try to boot it, I get a black screen after the Motorola logo.
Now, I am really really worried about my phone. I got it a month ago. I'm so afraid I really f****d up my phone right now that my hands are shaking.
I'm new to Android, so sorry if the solution is pretty obvious. And if it's not, could explain it very carefully to me? I don't know what to do.
My best wishes to you, guys.
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
TomGlass1 said:
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
Click to expand...
Click to collapse
Yeah, that happenned when I was trying to unlcok bootloader.
And well, my computer now doesn't even recognizes my phone.
EDIT: It appears as "Fastboot falcon S" in the Device Manager. Tried installing some drivers I found in the Internet, but it didn't work.
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
hemanthmahesh said:
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
Click to expand...
Click to collapse
Alright, just after I unlocked, when I was booting, I got a message saying that "xxxx has stopped working/failed to initialize/something like that". And then, when I rebooted, I got the usual message of the "bootlocker has been unlocked". After that, the Motorola logo started animating, but then I just got a black screen. I can't turn it off and the battery just got depleted (I'm charging right now).
When I try to connect it in my computer, the PC recognizes it as "MTP Device" or "Fastboot falcon S" when fastbooted. I can't install any drivers and the Motorola Device Manager doesn't recognizes it either.
Well, if there is some missing information, just ask me. I tried to describe my problem the best I could. Anyway, sorry for my bad English and thanks in advance for any effort trying to discover what's wrong.
Motorola Device Manager isn't helpful in this state as it doesn't handle things in fastboot. You already have all the required drivers (fastboot falcon S is the right driver afaik, falcon being motog codename) for flashing your stock firmware.
1. First, you can try the "Factory" option in bootloader (the third one, use volume down to move selector, volume up to select), though this might not really work for major issues.
2. When in fastboot mode, use "fastboot getvar all" to get the firmware details if you already didn't know about it.
3. Otherwise if yours is a standard gsm (non dualsim/non cdma), just download Blur_Version.174.44.9.falcon_umts.Retail.en.GB (UK stock for gsm, 4.4.2)
Download the mfastboot files to use rather than fastboot for flashing. You might need to modify your commands a bit for various firmwares.
http://forum.xda-developers.com/showthread.php?p=47820707 (refer this thread for flashing your stock firmware)
All the firmwares are in either of the links below (all around 400mb):
http://sbf.droid-developers.org/phone.php?device=14
(or)
http://www.filefactory.com/folder/c6cdedc45a775d27
I still don't get why many ppl are getting these errors after unlocking, very bad unlock method of moto if so ( I didnt get any such issues though).
When I use the "fastboot getvar all" command, it says "waiting for device". The phone is already connected, but the Moto G doesn't recognizes it's connected either.
I'm getting more and more afraid I really hardbricked it.
http://www.mymotocast.com/download/MDM?platform=windows
Tried installing these drivers? Your fastboot doesn't seem to be setup properly. How did you unlock without a working fastboot driver? You are trying that command in bootloader mode right?
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
hemanthmahesh said:
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
Click to expand...
Click to collapse
OMG. I tried that "Factory" option before but it didn't work. Now I tried a second time and it worked. Thanks a lot! Really :laugh:
Anyway, now my phone is back again and rooted. Thanks for the help, guys!
Thaiane said:
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
Click to expand...
Click to collapse
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
help
forgotter said:
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
Click to expand...
Click to collapse
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
jidurrr said:
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
Click to expand...
Click to collapse
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
forgotter said:
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
Click to expand...
Click to collapse
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
jidurrr said:
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2704207
Go to the above forum.
Sorry for late reply was busy with studies.
I had flash stock firmware
through PC
I have search XDA, and the net as a whole, and I have found many people with this same problem, and a few that were able to fix it -- however none of the fixes have helped me.
The problem is that once the boot loader is unlocked, I am no longer prompted to allow a connection from ADB so the RSA key doesn't get installed. If I do an adb devices, it shows as unauthorized.
This isn't a huge issue since I can still use any terminal program and execute the same commands on the phone itself, however, that is not ideal. I would really like to be able to use adb and fastboot to pull images, dump files, etc to my PC. As it stands now, I have to use a wireless KB / mouse, execute the commands in a terminal, and then transfer the files to my laptop.
I have tried taking the key that gets generated in %appdata%\.android and copying it to /data/misc/adb/adb_keys, and /adb_keys and /data/adb/adb_keys. I have also tried setting the build.prob variable ro.adb.secure to 0 -- no luck.
If anyone has any other ideas, it would be greatly appreciated. Again, this only happens once I unlock the boot loader (which is needed to root MM). Stock MM gives the prompt on the phone, and I can communicate just fine with adb and fastboot (obviously, need fastboot to unlock the bootloader ).
EDIT: I have an MS631 -- not sure if H631 has this same problem.
-- Brian
So I had a brilliant idea during lunch just now (yea, that is a whole lot of sarcasm).
I figured I would just lock the boot loader back, use adb and then then unlock it. So I boot into fastboot mode, do an oem lock, and then it dawns on me that I kinda need that unlocked bootloader to boot back into the OS. Well, unfortunately my fingers were typing a little faster than my brain was thinking and a fastboot reboot had already happened... LMAO. So, Now I get to sit here and install the LP KDZ, and root / install twrp, then install MM, and root / install TWRP, then restore the backup (that luckily I made right before being a moron) *sigh*. Prime example of why finding a way to boot MM without unlocking the boot loader is so important ....
-- Brian
Hey,
Tried to root my phone and things got messy.
I'm at a point where when I try to access the bootloader I get the "No command" screen, which I can bypass with the Power+Up keys and reach the "Android Recovery" screen.
I used "Wipe Data/Factory Reset" which didn't help much.
I can't do much more than that because Windows doesn't recognize my device and so I can't apply anything through ADB.
I tried to install the drivers again, but still nothing. My phone doesn't appear on the Device Manager.
Windows does make a sound of connected USB when I enter bootloader, but soon as it hits the "No Command" screen I hear the sound of a disconnected USB device.
Any idea how to make Windows recognize the device again so I could try to install things back with ADB?
Thanks!
OK, managed to solve this part after some reboots.
I'm now failing to ADB the stock image.
The phone says on top of "Andoird Recovery" that it's 7.1.2/NZH54D.
That's the stock image I've downloaded and when I try to ADB it I get on the windows terminal
"cannot read 'sailfish-nzh54d-factory-127f0583.zip'".
How do I move on from this?
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
I would start over from scratch. This guide is really good, it's for Pixel XL, but should be interchangable for Pixel 1 (non-XL), just be careful of the model specific files (salefish vs. marlin)
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
Can't you acces bootloader with "adb reboot bootloader"?
Also make sure u switched on usb debugging in developer options.
Sent from my Google Pixel using XDA Labs
If you get to the screen where you can choose to enter recovery, that is the bootloader. The no command thing is something you always get when you choose to boot to recovery. When on the screen before the no command thing, plug it into your PC. If the PC recognizes it, use fastboot to access it. "Fastboot devices" will show your phone. Adb devices doesn't work there. Bottom line is, it sounds to me you're getting to the bootloader. Just not realizing it.
TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.
Milly7 said:
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.
Click to expand...
Click to collapse
Yup. I think I'm good now. Gave up on the ROM thing. Too much headache to maintain it. Sticking to stock. Imperfect, but less headaches.
I wanted to root my device mostly for Titanium backup.
The rest isn't that important to me.
Thanks for the help!
My Xiaomi Mi 9T just fell and the screen now just flashes black and green. I'm sure that the phone is working but not so sure about the touch screen (can't see anything).
I wanted to access the screen from PC and recover my data but adb devices shows "unauthorized", and obviously I can't see the dialog box on the phone asking for adb authorization.
I already tried rebooting in recovery mode but trying to adb push the key to the device gives an error, and adb shell outputs "error: closed".
Installing a custom recovery afaik requires unlocked bootloader and unlocking it means losing all the data so that's not an option.
Am I 100% screwed or is there anything I didn't think of that could help?
e-ew--w said:
My Xiaomi Mi 9T just fell and the screen now just flashes black and green. I'm sure that the phone is working but not so sure about the touch screen (can't see anything).
I wanted to access the screen from PC and recover my data but adb devices shows "unauthorized", and obviously I can't see the dialog box on the phone asking for adb authorization.
I already tried rebooting in recovery mode but trying to adb push the key to the device gives an error, and adb shell outputs "error: closed".
Installing a custom recovery afaik requires unlocked bootloader and unlocking it means losing all the data so that's not an option.
Am I 100% screwed or is there anything I didn't think of that could help?
Click to expand...
Click to collapse
Unless you unauthorize adb from operating sytem you can't access it from recovery, unless you do adb sideload. One thing is that the screen doesn't display, an other that doesn't react to touches. Anyway adb backup will not backup everything. I recommend you to buy a counterfeit screen for $15 and replace it at least to power on and recover your data.
...
Hello. I wont lie.... im very frustrated. Its hard to find straight forward instructions.
I'm using linux ububtu. Ive also tried FWUL and mAid
Sdk tools installed, tried androud and google sdk
I have enabled oem unlock from the developer settings menu, along with usb debugging. file transfer mode is recognized as mtp.
I tried exalab's non-root busybox for some functions. Superuser x from k shark apps. I get bad system call.
I can only adb sideload and adb shell from pc. i cannot access anything else!
The most annoying part? When the sideload fails, it takes me into recovery mode, but adb doesnt work there!!! I have options like erase cache, reboot to bootloader, and mount /system (which mounts) but useless because i cant adb pull the build.prop file to change ro.secure 1 , ro.adb.secure 1, and ro.flash.locked 1.
Through getprop, i found the oem key but fastboot doesnt recognize anything at all.
I inspected the init.rc file Just to try and understand.
Adb setprop doesnt work.
How do i allow adb in recovery mode, or modify these syrstem properties? yes, manually and the ultra hard way. Even though im annoyed about it i want and love to learn.
edit: power, vol + and - at boot brings up a white screen saying 'device information' with the imei and s/n #'s with barcodes.
power with vol - to reboot, then at logo: release power and hold again : brings up factory reset screen with yes/no option (not recovery screen).
I cant figure anything else out
I opened up 2 androids now and i notice some pins, maybe for a debug mode? Forced bootloader ?
oliverbell760 said:
Hello. I wont lie.... im very frustrated. Its hard to find straight forward instructions.
I'm using linux ububtu. Ive also tried FWUL and mAid
Sdk tools installed, tried androud and google sdk
I have enabled oem unlock from the developer settings menu, along with usb debugging. file transfer mode is recognized as mtp.
I tried exalab's non-root busybox for some functions. Superuser x from k shark apps. I get bad system call.
I can only adb sideload and adb shell from pc. i cannot access anything else!
The most annoying part? When the sideload fails, it takes me into recovery mode, but adb doesnt work there!!! I have options like erase cache, reboot to bootloader, and mount /system (which mounts) but useless because i cant adb pull the build.prop file to change ro.secure 1 , ro.adb.secure 1, and ro.flash.locked 1.
Through getprop, i found the oem key but fastboot doesnt recognize anything at all.
I inspected the init.rc file Just to try and understand.
Adb setprop doesnt work.
How do i allow adb in recovery mode, or modify these syrstem properties? yes, manually and the ultra hard way. Even though im annoyed about it i want and love to learn.
edit: power, vol + and - at boot brings up a white screen saying 'device information' with the imei and s/n #'s with barcodes.
power with vol - to reboot, then at logo: release power and hold again : brings up factory reset screen with yes/no option (not recovery screen).
I cant figure anything else out
I opened up 2 androids now and i notice some pins, maybe for a debug mode? Forced bootloader ?
Click to expand...
Click to collapse
Can you help me root my lg journey the same way you did pls ?
You can't fix it the LG L322L CAN NOT be unbootlocked or rooted especially StraightTalk, tracphone or t-moble phones. ANYONE WHO CLAIMS THEY CAN OR HAVE IS A BOLD FACE LIAR!
IF YOU visit lg's website the K30 LG L322L is NOT on the list of devices that can be unlocked they have been houndreds of people tried in the last 4 years and not one has successfully done so
It's sounds like you soft bricked it and their is not a fix for it.. sorry but best of luck!
MountainMan42 said:
You can't fix it the LG L322L CAN NOT be unbootlocked or rooted especially StraightTalk, tracphone or t-moble phones. ANYONE WHO CLAIMS THEY CAN OR HAVE IS A BOLD FACE LIAR!
IF YOU visit lg's website the K30 LG L322L is NOT on the list of devices that can be unlocked they have been houndreds of people tried in the last 4 years and not one has successfully done so
It's sounds like you soft bricked it and their is not a fix for it.. sorry but best of luck!
Click to expand...
Click to collapse
Ah, I see.
I didnt mean the phone doesnt work, actually, it works just fine....my bad. just the adb/fastboot/root attempts didnt work.
if only i could modify those system service variables somehow. .. or even access the /system after mount?
getting access to adb via recovery? i had thoughts that if adb isnt shown via recovery, it isnt implemented there but can be done...
i havent tried since, been playing with my solder tools xd.
oliverbell760 said:
Ah, I see.
I didnt mean the phone doesnt work, actually, it works just fine....my bad. just the adb/fastboot/root attempts didnt work.
if only i could modify those system service variables somehow. .. or even access the /system after mount?
getting access to adb via recovery? i had thoughts that if adb isnt shown via recovery, it isnt implemented there but can be done...
i havent tried since, been playing with my solder tools xd.
Click to expand...
Click to collapse
oliverbell760: Do you STILL have the LG Journey phone??
I just came across your post here , while investigating this secon-hand phone ,the lgl322dl . I picked it up right after my LAST economy LG phone lgl355dl ,2022 model running Android 10 slipped into a bootloop.
I have found some very interesting "root-like" methods of running Linux distros "natively" along side of Android.
Please get in touch with me if you care to
expand on your 19-month old concern.
Also reach me at [email protected]