Related
I've spent 4-6 hours researching and trying things and have become quite familiar with rooting, fastboot, adb, sideload, and various other tools and have many installed & working, so if I make a noob comment or mistake, go easy on me. I did my best to do my own due diligence.
Here's the situation:
Nexus S 4G - stock from Sprint
Android 4.1 as pushed from Sprint
Not Rooted
Debugging Mode not enabled
Launcher, UI, Settings, Apps, etc fail ("has stopped") if they use the UI
Things not requiring UI do start and run
Android boots up normally to the lock screen (I have pattern lock). Apps start up in background fine (Locale, Alarm Clock Extreme, etc). Upon unlocking, I get "Unfortunately, Launcher has stopped." Repeatedly. It won't let me click any apps. I can, however, bring down the notification window. Selecting anything in the notification window fails, with "____ has stopped," including Settings, Messaging, Google Play, etc. When I plug in USB, I see the green Android with the "Turn on USB storage" button, but I can't click it before "System UI has stopped."
Unfortunately, most solutions warn "this will wipe all user data," and I don't have backups of a hundred or more photos and videos of my daughter's first year. So wiping data will be my LAST resort...and even then I may try forensic recovery from a dd image (I work in Computing Security, so have a fairly good technical background).
What I've tried, and result:
Reboot into recovery - I get dead Android with red exclamation
Wipe cache & reboot - no improvement (tried 5-10 times)
Reboot into Safe Mode - no improvement
Push 3rd party launcher - installs, but upon unlocking and selecting Launcher / Go Launcher (.e.g), I get "Go Launcher has stopped."
Fastboot - I get device listed/connected, but most commands cause wipe, so I haven't ventured much further
Calling Sprint and having Jellybean re-pushed to my device - it appeared to push (I saw update status message), but when I rebooted, no apparent difference (maybe it didn't push?)
Add/Remove apps via Play Store - works fine. I can remove apps (and have removed nearly all) and add apps, and they uninstall or install successfully (notification window confirms). But I can't access any newly installed apps due to the "stopped working" window.
Suggestions I can't try:
adb backup/shell/pull etc - my debugging mode is not on and I can't turn it on.
USB backup - can't enable USB Mode, and I don't have an automount capability
fastboot oem unlock - wipes phone
I want to try adb sideload <image>, but I haven't been able to confirm whether this truly wipes the user partition or not. If anyone can confirm, let me know. My phone enters sideload mode via:
1) boot to fastboot (power + vol up from OFF)
2) select recovery
3) at dead android with red exclamation, again press power + vol up and release. Menu appears only after you release.
4) 2nd option is "Apply update from ADB" which puts phone into special adb mode where the ONLY command accepted from your PC is "adb sideload."
Any suggestions on how I may be able to retrieve my photos and videos given this completely borked OS?
Thanks.
You could try this. It's Beta and buggy but might work.
http://forum.xda-developers.com/showthread.php?p=36499906
jayjay3333 said:
You could try this. It's Beta and buggy but might work.
http://forum.xda-developers.com/showthread.php?p=36499906
Click to expand...
Click to collapse
Thanks for the suggestion, but that requires Debugging Mode enabled. It's essentially a GUI for "adb backup." Unfortunately, I can't get debugging mode enabled in any way known to me yet.
Is anyone out there familiar with the adb sideload command? I'm really curious if sideloading an image into user partition in any way wipes data.
SOLVED - how I saved the baby photos
I thought I'd give a quick post on how I actually was able to recover my baby's photos. I was at my last resort and decided I'd just try to do a dd image of the card after I did a "wipe and factory reset." My hope was that a "wipe" did not actually write 0s over the entire internal SD card, but just erased the FAT. In that case, I figured, if I took a dd image, I could use a tool like Forensic Toolkit or similar file carving tool to carve out .MP4, .3GP and .JPG files.
So I selected the wipe and factory reset, but had my Linux system ready to do the dd IMMEDIATELY upon reboot. I had ALREADY plugged my USB connector into the Linux system. When the factory reset completed, the system booted directly to the "Enable USB Mode?" prompt. I enabled it, and performed a ~14 GB dump. I know this only catches the user partition, but I didn't care about the system partition, and hoped it would be re-allocated in roughly same location as previously (not stomping on my user data). After the dd was complete (about 3 hrs or so), I bit the bullet and just signed into my Google account and had Google Backup "restore settings."
Later, I was using ES File Explorer and noticed all JPGs were still in my DCIM folder. When I browsed with Gallery ALL PHOTOS AND MOVIES were still present! :victory:
I did not have any backup/recovery software installed to the best of my knowledge, except for Google's "settings backup." So my best explanation is that the wipe & factory reset DID NOT wipe my user data. This may be a fluke, or due to me having USB connected during the wipe & reset. Not sure.
Just to be sure we're all talking about the same "Factory Reset," on my stock Nexus S 4G running Android 4.1.1:
- power off phone
- press Vol Up and Power at same time -- you'll get the Bootloader
- select Recovery -- you'll get dead android with red exclamation after a few seconds
- press Vol Up and Power at same time again -- you'll get a secondary menu
- select "wipe data/factory reset"
- select "Yes" from a long list of "No" with one randomly-placed "Yes"
Hope this helps someone down the road...
I also wanted to note about the "ADB sideload" command. It can only be used to push incremental updates to the device--not full images needed to recover from a corrupted OS. I successfully sideloaded the 4.1.1 update (re-applied the 4.1.1 that I was currently running), which included "launcher2.apk" and a couple other launcher components that gave me hope. But when the 4.1.1 sideload completed successfully and I rebooted, launcher was still hosed. The 4.1.2 incremental update hasn't been released by Sprint yet.
That was hell of a read. The Samsung toolbox program you can do a temp boot and mount your SD card. But I'm too late to tell you now sorry.
Sent from my Nexus S using xda app-developers app
A few minutes googling would have told you that adb is set in the build.prop
Code:
persist.sys.usb.config=adb
OR adb with mount external
persist.sys.usb.config=mass_storage,adb
OR adb with mtp, but you need a kernel
persist.sys.usb.config=mtp,adb
Hi Can you tell us the dd command that you have used to dump the data?
My Case was little different. My friend had tried unlocking screen pattern and it got locked.
Wifi was not on neither was it rooted nor usb debugging mode enabled.
Solution:
I did a factory reset with my phone connected to PC.
once this is done during reboot a prompt came up asking whether to enable USB debugging need to be enabled.
I enabled it and I could see all my data from my PC.
I copied everything and continued with booting.
Hope this will help someone
Pavankumarvijapur said:
My Case was little different. My friend had tried unlocking screen pattern and it got locked.
Wifi was not on neither was it rooted nor usb debugging mode enabled.
Solution:
I did a factory reset with my phone connected to PC.
once this is done during reboot a prompt came up asking whether to enable USB debugging need to be enabled.
I enabled it and I could see all my data from my PC.
I copied everything and continued with booting.
Hope this will help someone
Click to expand...
Click to collapse
I wonder if this will work with a Nexus 7 on 4.3-4.4 ota soft brick
This is why rooting unlocking and a custom recovery is so important.
Sent from my XT897 using XDA Premium 4 mobile app
I installed the OTA update last night and it's just looping through the "alcatel one touch" and "smart move" screens. It's been like that for hours.
I need assistance in getting into recovery mode, and hopefully getting my files off the device.
I have downloaded android-studio and am about to install it to get adb and fastboot, and have downloaded the drivers for the idol 3. At this point when it's plugged in, my computer doesn't recognize the device.
If you did not have usb debugging enabled BEFORE the boot loop installing adb and fastboot now won't do you any good. Are you still able to get into recovery and is it twrp or the factory recovery? Without a direct way to get the phone into bootloader regretfully the only solution is to send it in for warranty repair (or replacement via your credit card if you paid that way under purchase protection)
Are you trying to remove the data to prevent access by others or because you need the data? Did you make any backups to external sd or copied to the pc?
I as well am stuck in bootloop. Was able to get into factory recovery and reset phone several times. Still no luck. I have a TWRP backup, but how to I do a temporary boot into it? Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there. Phoned Alcatel and they have referred me back to Amazon. Amazon only wants to refund me, won't exchange! Of course I bought at the pre-order price. Any help would be greatly appreciated.
wrench588 said:
I as well am stuck in bootloop. Was able to get into factory recovery and reset phone several times. Still no luck. I have a TWRP backup, but how to I do a temporary boot into it? Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there. Phoned Alcatel and they have referred me back to Amazon. Amazon only wants to refund me, won't exchange! Of course I bought at the pre-order price. Any help would be greatly appreciated.
Click to expand...
Click to collapse
The factory reset killed you....if you had usb debugging enabled prior and had not done a factory reset (which kills /data) you could have possibly gotten to an adb shell long enough to do an adb reboot bootloader. The problem is there's no way now to get you into bootloader....you can't get to it from recovery (factory).
If you purchased it by credit card you might see if their purchase protection (typically 60-90 days) allows a claim submission for a replacement....in this case they would cut you a check for the cost of a replacement after mailing in your old one. That's the only solution I see to remain at the $199 price.
You could also see if amazon will issue a $50 credit to your account in addition to return to allow for repurchase. Unlikely but possible.
Ok thanks for the input and advice. As a last ditch effort, is there a way to create or modify the twrp file as a "signed" zip file so that I could boot into it via stock recovery. This was how I rooted my old Galaxy S2, although it was a CWM recovery.
wrench588 said:
Ok thanks for the input and advice. As a last ditch effort, is there a way to create or modify the twrp file as a "signed" zip file so that I could boot into it via stock recovery. This was how I rooted my old Galaxy S2, although it was a CWM recovery.
Click to expand...
Click to collapse
Nothing so far has worked in that regard...in fact I created a update.zip using "zipme" to replace the build.prop that another user says the factory recovery refused to process.
Without a full factory rom to pull needed info in or the source code to compile one we can't do some of the things which would "save" the device.
wrench588 said:
...Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there.
Click to expand...
Click to collapse
Strange ... the stock recovery of 6039y has an option for reboot to the bootloader.
petrov.0 said:
Strange ... the stock recovery of 6039y has an option for reboot to the bootloader.
Click to expand...
Click to collapse
Can you post a screenshot where the option is? I'm not doubting your word but perhaps he's looking in the wrong place? I'm back on TWRP so can't look in the stock recovery myself.
famewolf said:
Can you post a screenshot where the option is? I'm not doubting your word but perhaps he's looking in the wrong place? I'm back on TWRP so can't look in the stock recovery myself.
Click to expand...
Click to collapse
There is no option for screenshot while the phone is in the stock recovery. I need a camera to take a picture of the menu. I can do this later. The menu however looks like this:
Code:
reboot system now
apply update from ADB
apply update from sdcard
apply update from phone storage
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery log
petrov.0 said:
There is no option for screenshot while the phone is in the stock recovery. I need a camera to take a picture of the menu. I can do this later. The menu however looks like this:
Code:
reboot system now
apply update from ADB
apply update from sdcard
apply update from phone storage
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery log
Click to expand...
Click to collapse
If it's right off the main page like that then I can confirm it's not on the 6045. It's been one of the main issues with folks bricking their devices...if their rom gets messed up and they have factory recovery they have no way to get into bootloader to do anything to repair the device. Seems alcatel needs to add the reboot to bootloader to our recovery. I wonder where we could report that.
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
famewolf said:
If it's right off the main page like that then I can confirm it's not on the 6045. It's been one of the main issues with folks bricking their devices...if their rom gets messed up and they have factory recovery they have no way to get into bootloader to do anything to repair the device. Seems alcatel needs to add the reboot to bootloader to our recovery. I wonder where we could report that.
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
Click to expand...
Click to collapse
This is a snapshot from the recovery menu of 6039y.
The short answer of your question regarding the "lock" is ... no. If a longer explanation is needed ... this is from the update file, a link to which was provided by you:
Code:
if ! applypatch -c EMMC:/dev/block/bootdevice/by-name/recovery:18393344:f9062580503eb61b315a5d12c5c6b3bb133aa4b2; then
....etc.
what it does is to check the sha1 sum of the recovery partition and if the sha1 sum doesn't match to f9062580503eb61b315a5d12c5c6b3bb133aa4b2 will continue with an overwriting of the recovery partition and then will apply a patch. It can't be changed because the whole update will fail.
yep no bootloader
I've got reboot to boatloader on main page from stock recovery on my 6045k
Sent from hell
famewolf said:
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
Click to expand...
Click to collapse
Back to the "lock" question. Probably it is possible the OTA update to be slightly modified and then to be flashed through the TWRP recovery (there is an option in TWRP to skip the signature verification ... the verification will fail if the zip file is modified). But I prefer to wait for the OTA update of the 6039y, as I want to perform some tests with the upgrade.
ractar28 said:
I installed the OTA update last night and it's just looping through the "alcatel one touch" and "smart move" screens. It's been like that for hours.
I need assistance in getting into recovery mode, and hopefully getting my files off the device.
I have downloaded android-studio and am about to install it to get adb and fastboot, and have downloaded the drivers for the idol 3. At this point when it's plugged in, my computer doesn't recognize the device.
Click to expand...
Click to collapse
I am in the same boat as OP re the state my Idol 3 (6045i) is currently in. I also unchecked superuser but did not unroot completely before installing the update. I have not yet done a data wipe through recovery though. Unfortunately, back when I rooted the phone I did NOT check the box telling the phone to remember the computer/RSA key for future use. As a result, now when the phone is stuck at the white/animated Alcatel boot logo I can see the phone under adb devices, but it shows as unauthorized.
One thing that did seem odd, was browsing through stock recovery when trying to browse to apply an update from either phone storage or the SD card, no files are showing up at all. All it is showing is the folder root ( /.. ) in both instances and nothing else. Even after I attempted loading several system update and twrp images (in .zip and .img formats) on the SD card from my computer, once loaded in the phone none of the files show up through stock recovery. Is this SD card not compatible/formatted wrong or is something else going on?
Is there any current method to gaining access to the phone via adb manupulating the adbkey files in the $User$/Home/.android folder? I do currently have the adbkey files on my Mac from connecting the phone previously. I'm assuming these files are uniquely generated hashes?
That is ridiculous if the 6045k has bootloader access from recovery and 6045i does not. What would be the reasoning for this?
Nikola Jovanovic said:
I've got reboot to boatloader on main page from stock recovery on my 6045k
Sent from hell
Click to expand...
Click to collapse
Does the sha1 sum of your recovery happen to match f9062580503eb61b315a5d12c5c6b3bb133aa4b2 ? If so it could solve some issues but why do I suddenly think all 3 models have their own recovery?
---------- Post added at 08:47 AM ---------- Previous post was at 08:43 AM ----------
n3tnut said:
I am in the same boat as OP re the state my Idol 3 (6045i) is currently in. I also unchecked superuser but did not unroot completely before installing the update. I have not yet done a data wipe through recovery though. Unfortunately, back when I rooted the phone I did NOT check the box telling the phone to remember the computer/RSA key for future use. As a result, now when the phone is stuck at the white/animated Alcatel boot logo I can see the phone under adb devices, but it shows as unauthorized.
One thing that did seem odd, was browsing through stock recovery when trying to browse to apply an update from either phone storage or the SD card, no files are showing up at all. All it is showing is the folder root ( /.. ) in both instances and nothing else. Even after I attempted loading several system update and twrp images (in .zip and .img formats) on the SD card from my computer, once loaded in the phone none of the files show up through stock recovery. Is this SD card not compatible/formatted wrong or is something else going on?
Is there any current method to gaining access to the phone via adb manupulating the adbkey files in the $User$/Home/.android folder? I do currently have the adbkey files on my Mac from connecting the phone previously. I'm assuming these files are uniquely generated hashes?
That is ridiculous if the 6045k has bootloader access from recovery and 6045i does not. What would be the reasoning for this?
Click to expand...
Click to collapse
adb reboot bootloader won't work even with it showing unauthorized? If you can get into bootloader you can fix /system without messing up your /data (don't wipe data or you lose adb entirely...you may figure out how to add the correct hash if we can find how it's generated)
Here's some info on the hashes you might find useful taken from: http://nelenkov.blogspot.com/2013/02/secure-usb-debugging-in-android-422.html
Secure ADB implementation
The ADB host authentication functionality is enabled by default when the ro.adb.secure system property is set to 1, and there is no way to disable it via the system settings interface (which is a good thing). The device is initially in the OFFLINE state and only goes into the ONLINE state once the host has authenticated. As you may already know, hosts use RSA keys in order to authenticate to the ADB daemon on the device. Authentication is typically a three step process:
After a host tries to connect, the device sends and AUTH message of type TOKEN that includes a 20 byte random value (read from /dev/urandom).
The host responds with a SIGNATURE packet that includes a SHA1withRSA signature of the random token with one of its private keys.
The device tries to verify the received signature, and if signature verification succeeds, it responds with a CONNECT message and goes into the ONLINE state. If verification fails, either because the signature value doesn't match or because there is no corresponding public key to verify with, the device sends another AUTH TOKEN with a new random value, so that the host can try authenticating again (slowing down if the number of failures goes over a certain threshold).
Signature verification typically fails the first time you connect the device to a new host because it doesn't yet have the host key. In that case the host sends its public key in an AUTH RSAPUBLICKEY message. The device takes the MD5 hash of that key and displays it in the 'Allow USB debugging' confirmation dialog. Since adbd is a native daemon, the key needs to be passed to the main Android OS. This is accomplished by simply writing the key to a local socket (aptly named, 'adbd'). When you enable ADB debugging from the developer settings screen, a thread that listens to the 'adbd' socket is started. When it receives a message starting with "PK" it treats it as a public key, parses it, calculates the MD5 hash and displays the confirmation dialog (an activity actually, part of the SystemUI package). If you tap 'OK', it sends a simple simple "OK" response and adbd uses the key to verify the authentication message (otherwise it just stays offline). In case you check the 'Always allow from this computer' checkbox, the public key is written to disk and automatically used for signature verification the next time you connect to the same host. The allow/deny debugging functionality, along with starting/stopping the adbd daemon, is exposed as public methods of the UsbDeviceManager system service.
We've described the ADB authentication protocol in some detail, but haven't said much about the actual keys used in the process. Those are 2048-bit RSA keys and are generated by the local ADB server. They are typically stored in $HOME/.android as adbkey and adbkey.pub. On Windows that usually translates to %USERPOFILE%\.android, but keys might end up in C:\Windows\System32\config\systemprofile\.android in some cases (see issue 49465). The default key directory can be overridden by setting the ANDROID_SDK_HOME environment variable. If the ADB_VENDOR_KEYS environment variable is set, the directory it points to is also searched for keys. If no keys are found in any of the above locations, a new key pair is generated and saved. On the device, keys are stored in the /data/misc/adb/adb_keys file, and new authorized keys are appended to the same file as you accept them. Read-only 'vendor keys' are stored in the /adb_keys file, but it doesn't seem to exist on current Nexus devices. The private key is in standard OpenSSL PEM format, while the public one consists of the Base 64 encoded key followed by a `[email protected]` user identifier, separated by space. The user identifier doesn't seem to be used at the moment and is only meaningful on Unix-based OS'es, on Windows it is always '[email protected]'.
While the USB debugging confirmation dialog helpfully displays a key fingerprint to let you verify you are connected to the expected host, the adb client doesn't have a handy command to print the fingerprint of the host key. You might think that there is little room for confusion: after all there is only one cable plugged to a single machine, but if you are running a couple of VMs, thing can get a little fuzzy. Here's one of way of displaying the host key's fingerprint in the same format the confirmation dialog uses (run in $HOME/.android or specify the full path to the public key file):
awk '{print $1}' < adbkey.pub|openssl base64 -A -d -a \
|openssl md5 -c|awk '{print $2}'|tr '[:lower:]' '[:upper:]'
We've reviewed how secure ADB debugging is implemented and have shown why it is needed, but just to show that all of this solves a real problem, we'll finish off with a screenshot of what a failed ADB attack against an 4.2.2 device from another Android device looks like:
famewolf said:
adb reboot bootloader won't work even with it showing unauthorized? If you can get into bootloader you can fix /system without messing up your /data (don't wipe data or you lose adb entirely...you may figure out how to add the correct hash if we can find how it's generated)
Click to expand...
Click to collapse
Just tested using adb reboot bootloader again and this is the result: error: device unauthorized. Please check the confirmation dialog on your device.
Something else I tried was running fastboot commands in the narrow window that the phone initially boots (black screen with Android logo) but that didn't seem to work either. I tried:
fastboot reboot-bootloader
fastboot -i 0x1bbb reboot-bootloader
fastboot -i 0x1bbb devices
I noticed if you plug the phone into the computer via USB while the phone is off, it will briefly power on to the Android logo/black screen before flashing the battery status once and turning off. Is this an opportunity to send fastboot or adb commands to the phone?
I'll try messing with the adbkey stuff later when I have time to dig into it.
There is a tool from Alcatel (TCL) which can perform upgrades of the device from a Windows PC. You can try it if nothing else helps. There are two COM ports available under Windows when the device is powered off and the USB cable is connected to the phone. This tool use them to perform some checks on the device and probably will continue with an upgrade (it says that all of your data will be wiped after the upgrade etc. so there is a possibility to overwrite everything with a stock image) ... there are instructions how to work with it. The link is from the French support section of Alcatel. Despite that the program has support for 6039 and 6045 is not clear for which of their versions.
petrov.0 said:
There is a tool from Alcatel (TCL) which can perform upgrades of the device from a Windows PC. You can try it if nothing else helps. There are two COM ports available under Windows when the device is powered off and the USB cable is connected to the phone. This tool use them to perform some checks on the device and probably will continue with an upgrade (it says that all of your data will be wiped after the upgrade etc. so there is a possibility to overwrite everything with a stock image) ... there are instructions how to work with it. The link is from the French support section of Alcatel. Despite that the program has support for 6039 and 6045 is not clear for which of their versions.
Click to expand...
Click to collapse
The problem is we currently have no stock images in the format it requires to flash to restore the device. I would think those have to be available first?
---------- Post added at 02:56 AM ---------- Previous post was at 02:55 AM ----------
n3tnut said:
Just tested using adb reboot bootloader again and this is the result: error: device unauthorized. Please check the confirmation dialog on your device.
Something else I tried was running fastboot commands in the narrow window that the phone initially boots (black screen with Android logo) but that didn't seem to work either. I tried:
fastboot reboot-bootloader
fastboot -i 0x1bbb reboot-bootloader
fastboot -i 0x1bbb devices
I noticed if you plug the phone into the computer via USB while the phone is off, it will briefly power on to the Android logo/black screen before flashing the battery status once and turning off. Is this an opportunity to send fastboot or adb commands to the phone?
I'll try messing with the adbkey stuff later when I have time to dig into it.
Click to expand...
Click to collapse
You can't do fastboot commands until the phone is IN bootloader....so you'd have to do adb reboot bootloader
adb devices
etc....
famewolf said:
The problem is we currently have no stock images in the format it requires to flash to restore the device. I would think those have to be available first?
Click to expand...
Click to collapse
It is possible the program to download these images from a server.
I found another interesting thing. The device has a download mode. It is activated when the phone is powered off and connected to a PC. You must wait the display to turn off after the charging battery symbol and then to press and hold both volume keys, after which to press and hold the power button (without releasing these for the volume). But still don't know what to do in this mode. No device is detected on my Linux box when the phone is in this state. Probably I should try in Windows.
Also when the Alcatel upgrade tool was trying to detect the phone I'm almost sure that one of the COM ports was
Qualcomm HS-USB Diagnostics 9006
there is a lot information for other devices how this can be used to unbrick your phone, so this is a some start. The images which the people flash through it are in raw format.
My Moto G (1st Gen XT1033) began to have issues 3 months back, I havent been able to fix it yet.
The phone boots up fine (usually), displays "Android is Upgrading" message each time, then shows the lock screen which still functions fine.
Once unlocked, the phone does not display the Home screen, nor am I able to open the Apps Drawer, I can access Settings though.
It shows the same missed call notification each time, even if I dismiss the notification and force restart the phone, it will still show up again.
I can see that my files are still around by navigating from the Storage section under settings.
If I try to take a screenshot using Power+VolDown keys, it will say screenshot captured in the notification bar, but I dont think that it is able to actually save the screenshot, since the count of files in Screenshot folder from the Storage section remains same.
Unable to open any apps since I can only access settings. Modifying any setting here has no effect and is lost again on reboot.
When connected to PC, it does not mount properly even though I have the drivers installed.
ADB pull also does not work, even though I had enabled USB debugging long before it stopped functioning properly. I no longer get the authorize dialog.
I repeatedly get "xxxx stopped/stopped working" error dialog.
While I am able to mount an OTG usb drive, I am unable to use it since I can only open it from Total Command and it seems to be unable to open it in Read-Write mode. I am unable to open it from ES Explorer since I cant open any of the apps..
I tried to go to recovery mode and clear cache, but it has issues booting into recovery. Earlier post here.
Here's a recording of how the phone behaves after rebooting.
Unfortunately I had not setup a backup process and now I need to badly recover my data from the UserData partition.
How do I go about recovering my data from the UserData partition?
Another Noob Question: Can I safely run "fastboot erase cache" or "mfastboot erase cache" command from bootloader(fastboot mode) without having to unlock the bootloader?
assuming you have a locked bootloader, there is nothing you can do (like salvaging userdata, which require root privileges)
unlocking the bootloader will reset the phone, and you will lose all you user data/apps.
So I may be doing something totally idiotic, but I seem to be stuck at the most simple part of unlocking my bootloader.
I follow this to step 2:
https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
when it says "Set up ADB" I follow the link to this:
https://www.xda-developers.com/install-adb-windows-macos-linux/
until I get to step 7. When I enter the command 'adb devices' I never get a serial number nor a prompt to allow or deny USB Debugging access. I never get see my device’s serial number in the command prompt.
So doing a bit of digging I have looked into ensuring my ADB and One Plus driver was installed correctly, and I even purchased a new data transfer cable to make sure that wasn't the issue.
I check my device drivers and see get an error in my ADB Interface driver, but after following a few tutorials I'm still lost as to whether its updated or if I'm doing so incorrectly, or if that's even the problem.
Any direction would be appreciated.
I am running Windows 8.1 and my device is Android 10, model GM1915.
NephilimHoss said:
So I may be doing something totally idiotic, but I seem to be stuck at the most simple part of unlocking my bootloader.
I check my device drivers and see get an error in my ADB Interface driver, but after following a few tutorials I'm still lost as to whether its updated or if I'm doing so incorrectly, or if that's even the problem.
Click to expand...
Click to collapse
Hallelujah!!
Finally found a way to manually install the correct driver from a tutorial on visualgbd{dot}com, so now my device is recognised.
I had to find where my drivers were being default downloaded since they weren't in the place the tutorial indicated, but that was the only hitch.
SO. On to the actual unlock. :fingers-crossed:
So I need help.
I followed an XDA video tutorial which was a bit difficult for a newbie, but I think I did everything correctly up to installing TWRP.
I got to the point of flashing my ROM and jumped to the Eelo website instructions:
- Go to main menu, then tap Wipe.
- Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.
- Return to the previous menu and tap Advanced Wipe.
- Select the Cache and System partitions to be wiped and then Swipe to Wipe.
- Sideload the /e/ .zip package:
- On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
- On the host machine, sideload the package using: 'adb sideload filename.zip'
I followed this and while the package did not sideload, I beleive my recovery partition was wiped I seem to be stuck.
I'm at the point where I feel I need to Flash OEM Stock and start over, but I am getting a bootloader loop.
Really need help. I feel at this point I'm going to start making things worse as I look at various tutorials and whatnot.
In case additional information is helpful:
My device does not show up in my device list, but it is detected with "fastboot devices".
I attempted to flash TWRP with "fastboot flash boot <TWRP.img> and it writes to 'boot-a'. But when I then try to boot into recovery mode, instead of booting into TWRP I enter the fastboot screen.
I tried using mauronofrio's Tool All In One to flash stock ROM and possibly fix the partition, if thats what the problem is, but I cant tell it did anything.
I have a very old Wikipad tablet, which these days tends to only get used for playing old video games. I hadn't used it for a few months, but now whenever I switch it on I get an error:
"Unfortunately, System UI has stopped"
No matter how many times I tap OK, the error just keeps popping up, with the occasional "unfortunately, Launcher has stopped" thrown in as well.
There are plenty of suggestions online for how to fix these errors (remove apps, empty cache, etc.), but those all rely on you actually being able to access the UI and settings. I can never get past these errors on top of a blank screen.
If I enter the Power/Volume-Down boot menu, I get the options of "normal boot", "fastboot protocol", "recovery kernal" and "forced recovery". Selecting "Recovery Kernel" shows the image of the android lying down with an exclamation mark above it. However, I'm not sure where to go from there. No commands appear on screen and various power/volume button combinations don't seem to do anything.
Does anyone know the correct commands to do a factory reset on a Wikipad (or have any other suggestions as to how to resolve the errors)? I'm not bothered about losing all of the data on it.
Thanks!
OK, after weeks of scratching my head on this one for a few weeks and deciding to post the question on this forum, I figured it out myself a couple of days later
I downloaded Fastboot and Android USB drivers from the links posted here:
Fastboot.zip, ADB, & Android USB Drivers | HighOnAndroid.com
highonandroid.com
I installed Android USB drivers (by ClockworkMod). I plugged the Wikipad in to my laptop (Windows 10), powered it off and booted it holding the power and volume down keys. I selected the "fastboot protocol" option. An unknown "fastboot" device then appeared in Device Manager. I had to manually select the ClockworkMod generic Android driver before it was recognised.
Running "fastboot devices" then listed a device. Running "fastboot -w" then deleted all user data (there's no confirmation prompt, it just runs). It also threw an error:
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I ignored the error and rebooted the Wikipad. It then booted in to the first time start-up wizard and the System UI errors are gone. All of the data I had on it is gone too, but that's no big deal.