Lessons You've Learned - General Topics

So I thought it would be fun to compile a list of lessons you've learned while working with your smartphones, as I just had a doozy last night.
Updated my radio last night and forgot to remove the zip from my SD card root.
Flashed a fancy new ROM, and see that it was stuck in a boot loop.
Realize that I can't boot into Recovery because it tries to auto-load the radio update.
Go buy a card reader to delete the radio zip.
Realize that I can't remember the generated password for my new Windows 8 PC installation (live.com linked account -- had been using a password manager on my phone). Email associated with the account is a gmail account with an authenticator, and the backups stored on the PC... so no way to reset the password from a different computer since the authenticator was on the phone I just screwed up.
Dug up an old-ish linux gparted live cd, loaded it up, deleted the radio zip, booted the phone into recovery and restored a good rom.
Tried to restart the computer into Win8, only to realize I'd somehow managed to hose the installation with the live cd (maybe locked partition, dunno, wouldn't boot)... gave up and reformatted the Win8 machine.
So lessons learned:
1. Delete the radio file as soon as you're done with it.
2. Don't use a web-linked password for your home desktop pc.

Related

Can't restore Lumia 710.....flashable ROM?

I forced 8107 onto my T-Mobile Lumia 710, and the light sensor doesn't seem to be working (screen doesn't brighten in direct sunlight), so I wanted to restore to my old point. The problem was, the only restore point I had was on my work machine. So I remoted in, downloaded DropBox to my work machine, made a zip of the backup from my work machine, and uploaded the zip to my DropBox account. When I moved the backup zip to my user/AppData/Microsoft/Local/... on my laptop Zune didn't recognize it as a backup and kept deleting it.
So I figured I would just wait and come to work to restore my backup and now my backup from WORK is deleted as well. I still have the file on my laptop at home, so at least I still have it.
My question is, is there a way I can use my restore point, or is there a flashable 7740 Stock ROM for the T-Mobile Lumia 710 I can use?
I believe the phone must have the primary sync relationship with the computer that you're trying to restore on. Sync the phone with the PC (and make it the primary PC) and then try copying in the restore point to the correct location (make sure it's the right location! You may need to close Zune before you can overwrite the folder that is automatically created when you sync the phone). Then, try restoring again. Ideally, you'd be able to Syn with Zune, copy over the restore point while Zune is running, and then go to Settings - Phone - Update and hit Restore.
For another way to restore the phone, try the following:
Disconnect from the PC and turn the phone off.
Press and hold the Camera button, then press Power. The phone should boot into the backup/update/recovery mode (mostly black and white).
On the PC, start Zune and copy the restore point. If you can't copy the restore point while Zune runs, close Zune, do the copy, and then start Zune again.
Connect the phone (still in recovery mode) to the PC (with Zune running) via USB.
Zune should prompt to restore the phone, tell it to do so.

Google nexus s unusable

Hi All
I have a Google Nexus S, bought last year and it was working fine till last week.
It came with Android Ginger Bread, and I rooted the phone and installed several custom ROMs including Cyanogenmod.
Recently I installed Android Jelly bean ROM, and it was working fine.
Last week, I wanted to try the Cyanogedmod 10 (on Jelly bean). I went to recovery mode for taking a backup.
But I saw a recent backup which was taken before 2 months. I thought that should be fine.
I cleared all cache and did a factory reset for getting ready for the new ROM.
Now something went wrong!
I tried to reboot the device, but I could only see the usual animated CROSS logo( with four colours) for ever.
I even left the phone for more than a hour. But it is not rebooting.
//SO CAN'T RELOAD THE PREVIOUSLY WORKING OS
I tried restoring from the previous backup.. It shows that "installation complete".
After that while rebooting the device just hangs in the same place.
//SO CAN'T RESTORE FROM MY PREVIOUS BACKUP
I thought of copying the new rom in the device. I could not succeed.
I tried adb command through my SDK.
ADB is not listing my device.
In all the forums it is mentioned that to enable the USB debugging from the phone.
I cannot do this, because I cannot go into the device OS other than recovery mode.
I even tried some GUI stuff like Android commander / QtADB but every thing needs USB Enable from the OS Menu.
Finally I tried mounting disk from recovery mode.
Whenever I mount the disk, Windows 7 is fixing the file system errors and bad sectors for a while
and shows "no problems were found" and it is ready to use.
Here something weird happens.
I can copy the files in windows explorer and can see the files in the device thru explorer,
BUT when I unmount and browse from the recovery mode the files are not there. (may be the files are copied in cache)
//SO I CAN'T COPY ANY FILE TO THE DEVICE.. ( May be here I am doing something silly. )
My phone is now unusable!
Any advice/tips is highly appreciated!
Cheers
Kum

[Q] Surface Pro 2 Clean install

I just installed the latest Firmware / Drivers MS has pushed through Windows Update,
and i would like to do a clean install so no older driver remnants are left behind and maybe create a separate partition to store data.
- First thing i did was create a bootable usb drive using Microsofts new 'Create Installation Media Tool', I selected 'Windows 8.1 Pro x64' in my native language which is Dutch.
- Then I copied my recovery image to a USB stick and deleted the recovery partition.
Before i continue i still have a few questions and i hope someone here can answer them.
-----
1. If i reinstall Windows can i still use the recovery usb and restore Windows in case something goes wrong during the (clean) installation or does the recovery only work
when the initial installation is untouched?
2. Will Windows automatically recognize the serial number, which i believe is stored in the BIOS / UEFI, and activate Windows?
3. If i do a clean install will Windows recognize and install the wifi adapter or do i need to manually download and install the latest drivers?
First off all: why do you want to re install? There will always be some remnants of old files, but windows does a relatively good job at deleting those (and they don't do any harm). Unless something doesn't work, i wouldn't re-install.
Oh, and you can create a secondary partition without re installing windows. Just re size your current windows partition.
But to answer your questions:
1. Yes, the recovery stick will still work. It even works when the SSD has been wiped.
2. It should activate automatically, but if you want to be sure, you can find your product key with the magical jellybean Keyfinder ( https://www.magicaljellybean.com/downloads/KeyFinderInstaller.exe )
3. Since Surface is a first party Microsoft product, i'd bet they automatically install the drivers.

Trouble installing TWRP on AOSP pixel 2

Hello! I have decided to turn in this pixel 2 I have to google finally but I'd really like to make a nandroid backup of it before I send it in as it has some very interesting apks on it (I made previous threads on this), pictures here https://photos.google.com/share/AF1...?key=dDc2UjVBQWpmUk5KUEpmNVJ6WWZYZ0RQUkprZm13 . Problem is that the phone isn't exactly running the stock pixel 2 os, it came directly from google running AOSP with android version 8.0.1. I'm not sure if the kernal and everything else are the same either, I do have a picture of the system information in the above album.
So I tried following this https://www.the***********.com/install-twrp-recovery-on-google-pixel-2-pixel-2-xl/ exactly to boot into twrp, but after following the steps to entering "fastboot boot twrp-3.2.1-2-walleye.img" in windows power shell, powershell says Downloading boot.img OKAY and booting OKAY, but the pixel 2 screen just goes black instead of loading TWRP. I am still able to get back to android and get back to the bootloader, but I can't seem to load or install TWRP.
^not sure why the url gets ***** out. the ***** out portion is "custom droid" with no space
I'm not sure of any other way to pull data off this phone without TWRP installed. The phone won't accept any sim card I've tried, and turning on wifi allows me to connect to my local wifi network, showing the correct IP, DNS, and default gateway, but still refuses to connect to the internet. Usb debugging is enabled, and adb lists the phones serial number when prompted with fastboot devices.
The phone itself shows 24gb/32gb all used by the system. When I plug it in to my PC and view the files, it shows as "AOSP on walleye" with 6.73gb free of 15.6gb rather than the 32gb the phone shows. The files shown on the pc are all most empty as well, I can't seem to find what files are taking up that 10gb or so that my PC does manage to see.
If anyone has any ideas, I'd be happy to hear them. It'd be a shame to let all these tools go. Otherwise this phone should be heading back to google soon.
ravensfan8448 said:
Hello! I have decided to turn in this pixel 2 I have to google finally but I'd really like to make a nandroid backup of it before I send it in as it has some very interesting apks on it (I made previous threads on this), pictures here https://photos.google.com/share/AF1...?key=dDc2UjVBQWpmUk5KUEpmNVJ6WWZYZ0RQUkprZm13 . Problem is that the phone isn't exactly running the stock pixel 2 os, it came directly from google running AOSP with android version 8.0.1. I'm not sure if the kernal and everything else are the same either, I do have a picture of the system information in the above album.
So I tried following this https://www.the***********.com/install-twrp-recovery-on-google-pixel-2-pixel-2-xl/ exactly to boot into twrp, but after following the steps to entering "fastboot boot twrp-3.2.1-2-walleye.img" in windows power shell, powershell says Downloading boot.img OKAY and booting OKAY, but the pixel 2 screen just goes black instead of loading TWRP. I am still able to get back to android and get back to the bootloader, but I can't seem to load or install TWRP.
^not sure why the url gets ***** out. the ***** out portion is "custom droid" with no space
I'm not sure of any other way to pull data off this phone without TWRP installed. The phone won't accept any sim card I've tried, and turning on wifi allows me to connect to my local wifi network, showing the correct IP, DNS, and default gateway, but still refuses to connect to the internet. Usb debugging is enabled, and adb lists the phones serial number when prompted with fastboot devices.
The phone itself shows 24gb/32gb all used by the system. When I plug it in to my PC and view the files, it shows as "AOSP on walleye" with 6.73gb free of 15.6gb rather than the 32gb the phone shows. The files shown on the pc are all most empty as well, I can't seem to find what files are taking up that 10gb or so that my PC does manage to see.
If anyone has any ideas, I'd be happy to hear them. It'd be a shame to let all these tools go. Otherwise this phone should be heading back to google soon.
Click to expand...
Click to collapse
So you're sending the phone back to Google....why? Because it came without the stock OS? It's hard to believe that the phone came with AOSP already installed...that's awesome if it did since AOSP is usually something that you have to load yourself.
So I'm sure you understand that your bootloader has to be unlocked in order to boot TWRP yes? Because typically when the bootloader is not unlocked the phone will reject the recover and shut down. So make sure your bootloader is unlocked in developer settings since you have a Google verison.
Sounds like your partitions are being weird when plugged in to the PC and its only seeing some of the partition. I would try to reinstall the driver and see where that gets you.
If you're concerned about your APKs, I would just use Titanium Backup and backup all the APKs to storage and then pull that from the phone using PC.
Hope this helps.

Easiest Way to Recover Deleted Files on Mac

Have you ever worked on something really important for the longest time only to find that you accidentally deleted it? Or the lights just went off and corrupted your hard disk? maybe the SD card just gave up? or you are attacked by a virus which made all your files non-accessible? I’m sure in this age of digital technology everyone might have faced this issue in one way or another. But don’t worry, today, we bring an end to all of these problems. Here’s our ultimate guide on how to recover the deleted files on Mac. If you have been looking for a way to do the same on an Android device or a Windows PC, read this tutorial.
Best Software to Recover deleted files on Mac
There is quite a few software in the market which offers the functionality to recover data on your machine but today we are going to talk about Recoverit by Wondershare. Wondershare has been popular for creating unique solutions in different verticles of Tech domain like Filmora for editing, Dr. Fone for anything and everything related to smartphones, PDFelement for documentation and Recoverit for data recovery. It is available on Windows as well as Mac. Today, we will help you with the guide on how you can recover deleted files on Mac.
How to Recover deleted files on Mac using Recoverit
Launch the Recoverit Mac App and select the source from where you want to recover files.
You can undo empty Trash on Mac, and recover files from a formatted disk, lost partition, an external device, etc. For this guide, we will help you with the steps to recover data you deleted from your trash on Mac but you can select the source from where you want to recover data as shown in the image below.
Once you select the source, Recoverit will start its scan and show you the files which are recoverable from your machine.
Mod Edit:- Links Removed & Thread Closed.

Categories

Resources