How can I make a NANDroid backup of an unofficial, unsupported prototype device? (Nvidia Shield Portable 2) - Android Q&A, Help & Troubleshooting

Hello! I've recently come to own an Nvidia Shield portable prototype, and am interested in tinkering with it as part of a long-term project. Before I mess with any of that, I wanted to make a NANDroid backup of the device to make sure I could recover it if I were to mess anything up. However, I'm not really sure how to install TWRP - and, by extension, make a NANDroid backup - onto an unsupported device. There is no official firmware available for this, the only thing I have is the device itself and everything on it.
The device is in complete working condition without any issues, it's just stuck on Android 4.4.2 without any updates available (because it was never officially released). If any further information about the device is needed, please let me know. I am new to these forums, so if there's a more appropriate place to post this let me know and I can post there.
Any help would be appreciated. Thank you!

Nandroid backups are usually performed in Android's recovery mode - option: backup and restore.

jwoegerbauer said:
Nandroid backups are usually performed in Android's recovery mode - option: backup and restore.
Click to expand...
Click to collapse
Yeah I did manage to access the recovery mode, but it only has stock recovery - no option to backup/restore. I'd need to flash on a custom recovery like TWRP so I can make a NANDroid backup, which brings me back to the problem of not being able to install TWRP on this unsupported prototype.

To do a full backup by means of ADB's inbuilt backup routine isn't possible. That's fact. Professional apps as Titanium Backup or Online Nandroid Backup requires Android is rooted. Root-free apps as Helium Backup only allows to backup all the videos, pictures, emails, notes, etc. on your Android device.
Possible workaround - NOT TESTED BY ME:
If device's Android supports Linux command tar then you easily can backup device by means of it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If tar not present then install BusyBox-NoRoot, obtain path to BusyBox
Example:
Code:
adb devices
adb shell stop
adb shell "<PATH-TO-BUSYBOX> tar -cvf %TEMP%\system.tar /system"
adb shell "<PATH-TO-BUSYBOX> tar -cvf %TEMP%\data.tar /data"
adb shell start

jwoegerbauer said:
To do a full backup by means of ADB's inbuilt backup routine isn't possible. That's fact. Professional apps as Titanium Backup or Online Nandroid Backup requires Android is rooted. Root-free apps as Helium Backup only allows to backup all the videos, pictures, emails, notes, etc. on your Android device.
Click to expand...
Click to collapse
The device IS rooted but I can't install any of the 'professional' backup apps since they seem to require device-specific configurations.
My question is "how can I do a complete backup of an unofficial, unsupported device?"
The device is rooted and I can access the bootloader, I just don't know how to go about backing it up since it's unsupported

My understanding of peforming a successful Nandroid backup is that this is completely independent of the hardware / configuration of the device, that it doesn't matter what is the brand / model of the device, that it's totally irrelevant whether OEM/vendor supports the device or not, that it''s only important that device's Android preferredly is rooted so that all partitions / directories can be mounted as RW, that there is enough storage space available ( dozens of GB ) to hold the backup - preferredly on external SD-card. But I may err, as always ...

Related

[SHARE]Online Nandroid Backup / Nandroid Backup without re-booting by ameer1234567890

Sorry if repost and i just copy/paste from original thread.
Nandroid backups are usually performed in recovery mode. This means you would have to turn off your phone and reboot in recovery mode, which wastes a whole lot of time rebooting and a lot more time offline. For me, this has been a killer as I do regular nandroid backups. Having to reboot in recovery and finding missed calls, sms from my wife and friends is totally not accepatable for me. So, I set to develop an online nandroid backup tool which can do nandroid backups without switching off my phone.
Today, I am releasing it to public, as it may serve good for some others too. This tool is specifically for Xperia phones, but should work with any model of android phones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This tool backups /system , /data , /cache & .android_secure partiotions to /sdcard/clockworkmod/backup directory. The date format used for folder name is the same used by CWM itself and nandroid backups created with this tool can safely be restored using CWM. If you would want to have a custom name for backup folder, pass an argument with the name to the script and it will use the name.
Feedback (especially ideas to improve) are most welcome.
Requirements
1. Rooted android phone
2. A terminal emulator installed on phone
3. Busybox
4. A working CWM based recovery installed
5. Some patience
Installation
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
Usage
1. Open terminal emulator
2. Type su to obtain root
3. Type onandroid
4. Wait and watch
Custom Backup Name
* Example:
Code:
onandroid custom_name
* Please be careful not to include characters not allowed in filenames.
Timezone modifier
* Example: Use home/phone timezone for backup file name
Code:
onandroid -h
* Example: Use UTC (default) for backup file name
Code:
onandroid -u
* Note: UTC is used as default (if no timezone modifier is passed). This is to comply with CWM nandroid backups.
Download:
onandroidv3.0.zip
Tested and working in NeoThanks to ameer1234567890
Original thread:- http://forum.xda-developers.com/showthread.php?t=1620255
I will be testing this when i get home back to my wifi!!!!
Excellent work.

Root Z2 without loss?

Is it possible to root a Sony Z2 without losing data or something? I have a Sony Z2 which needs to be rooted, but the owner does not want to lose his apps and other data. Is that possible?
Not that i know of
There are options that are somewhat odd as the apps used send a lot of private data.
What version of Android? Should be easy if you don't have to downgrade. What data don't you want to lose? If it's sms and call logs, they can be backed up without root. User apps should also be able to be backed up without root and then restored later.
Have you looked at the backup and restore app?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google is a wonderful thing
http://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-howtos.html
1. How to make your first backup WITHOUT root:
Before beginning, you need to setup your ADB and have your device detected. You must also running Android version 4.0 and above. Also, make sure you have a file manager installed. Our favorite is the ES File Explorer.
Connect your device and make sure its listed with the following command:
adb devices
Run a FULL backup with the following command:
adb backup -f FullBackup.ab -apk -all
This will create a “package” called “FullBackup.ab” on the current location in your command prompt. This is your backup package.
Now you can root your phone.
Once finished rooting, insert the “FullBackup.ab” package on your sdcard
Hit the menu button and look for “Extract from ADB backup” option. This will prompt you to search for the file. Use the file manager that you installed earlier and navigate to the directory and select the FullBackup.ab file.
Now restore like as if the backup was made with Titanium Backup. Don’t forget to make a fresh copy of the backup using Titanium Backup. You’re Done!
Sent from my D6503 using Tapatalk

MeLE A200 Internal Storage not mounted

I've MeLE A200 HTPC (single core A10S SoC, FW Android 4.0.4 v1.2b rooted, Board HMC-G41A03WL). Recently after installing a small app, something went wrong, the box Internal Storage changed from 10% full to 0.0B, meaning its not mounted anymore on device reboot. I've no access to previously installed packages, and can't install any new package that requires access to Internal Storage ( Data partition) or root access. I tried soft recovery from Settings and Hard recovery by pressing the device button, but they didn't fix the issue.
I earlier installed CWM ROM Manager, but was unable to find Recovery image for this device. Wanted to re-install original firmware, but official links are dead. Mele Support never answers any emails, and they block registration emails on the company forum, so no way to ask a question on the forum. They posted an updated firmware v1.3 for "A200 upgraded version" device on the forum, but that device hardware has 1GB RAM, and mine only 512MB, and there may be other differences. So I'm not sure, it will boot, and if it doesn't I'll get a brick.
I installed Terminal package, and can access the box partitions from PC using ADB via Wi-Fi, since USB Recovery option is not showing in the device Settings, and Mele provides no USB Windows driver. I can see that Data, Cache, and probably some other partitions are not mounted. I mounted them OK manually, but lost Wi-Fi access after that, probably because the device lost access to Data folder on root it was using instead of Data partition on NAND.
This picture has proper links, since I can't post them here so far:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My questions are:
1. Can anyone point to a link to A200/A210 original firmware? I need:
A200_Mele_HTPC_20130117_V1.3.1
A200 Mele_HTPC_ Home _20121220_V1.2
2. What are my chances to get a brick, if I flash the above mentioned v1.3 for "A200 upgraded version" device? Can I unpack & modify that firmware to fit my device - how?
A200升级版_A10_SDK1.6_V1.3_20140715.img
3. If I flash that FW to the device, will it erase original Recovery partition? If Yes, and the device can't boot after flash, could I recover it by pressing Hard Recovery button? Does it mean, Hard Recovery partition is stored separately in NAND, and never erased when a new FW is flashed from SD Card?
4. May be I can change some automount rules via ADB? So far, I found that /etc/vold.fstab has no automount rules for any system partitions, only for SD Card and USB partitions. So what file contains automount rules for Data and Cache?
5. What else can lead to Data not being mounted, what else can I check or do to fix the device? I can post some debug and dmesg logs saved by the system if needed. How I can fully backup or recover the device from full backup in this situation?
Update: the only resolution I found was reinstalling factory firmware procured from Mele upon request.
Does your device have a custom recover? Flash a new rom

Soft brick, stock recovery, no downloadable ROM; use files from another mobiie?

Dear XDA Developers Users,
I have two STK Hero X mobiles. One of them is rooted and working (1), the second one is soft-bricked (2). I´m looking for a way how to unbrick the second one, maybe using the first one.
Both mobiles: No official or custom ROM available, no custom recovery available, rooted using KingRoot, Android 5.1, MTK6735P chipset.
The working one (1): Can use ADB, Fastboot, Dev options, stock recovery
The bricked one (2): Can only get to recovery, fastboot. Bootloader locked. Freezes at the STK logo during booting. I had removed a few system apps using System App Remover: AVG antivirus or Chrome. In recovery, there is a root integrity check. A few files are modified (2; because of root, I suppose, including /system/bin/app_process64), missing (7; antivirus), and new (13 of them). It´s the Android System Recovery <3e> which looks like that (not a my photo):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What I´ve tried (2)
- Factory reset using recovery (/data, /cache). Still feezes at the logo during booting (two hours).
- Create a ZIPme recovery from the working one (1) with system apps. In the recovery (2), the ZIP is loaded via SD card and suddenly interrupted with no reason. (Battery charged.) Tried with two different ZIPme recoveries.
- Create a FlashFire ROM brackup (1). Can´t because of the KingRoot. Supersume Pro didn´t help. Source: https://www.xda-developers.com/chainfires-flashfire-can-now-create-fastboot-flashable-backups/
- Create a complete ADB backup (1), and restore it (2). Well, wasn´t possible because the ADB in recovery (2) doesn´t support adb restore. Source: https://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351¨
- Unlock the bootloader (1). I can´t boot the OS and allow OEM via Dev tools. Unlocking with Fastboot fails. Source: http://www.theandroidsoul.com/unlock-bootloader-via-fastboot-android/
- Port a TWRP recovery and then simply use a recovery from (1). Well, I can´t unlock the bootloader. Source: http://forum.xda-developers.com/showthread.php?t=2798257
- Create a complete nandroid backup (1). I can´t restore it using the stock recovery. Source: https://www.informationlord.com/create-nandroid-backup-without-cwmcustom-recovery/
I will be grateful for any idea how to make my mobile (2) boot into Android. Maybe using the files from the working one (1), restoring the partitions? In the recovery (2), there is a backup user data option. The mobile has a 16GB storage, and after a factory reset, the backup user data needs around 12GB of free space on SD card. Since there is no user data, is it possible it includes the system files somehow?

Development OrangeFox Recovery UNOFFICIAL for Realme narzo 30A

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OrangeFox Recovery UNOFFICIAL
By @iamshubh69
Fw: Realme UI 2.0
Download: Click here
Changelog:
- build for Realme ui 2.0
Bugs:
- For working of OTG, plug it before booting to recovery
- Decryption in a12
Notes:
Only for Realme UI 2.0 Firmware
Guide to flash:
1. Unlock bootloader using the Realme UI 2.0 Deeptest tool
2. Enable usb debugging
3. adb reboot bootloader
4.fastboot --disable-verification flash vbmeta vbmeta.img (vbmeta 4KB)
5. fastboot flash recovery recovery.img
Credits:
Thanks to @sarthakroy2002 for trees and help
What do you mean by "Decryption in a12"? Like the OS fails to read an encrypted partition, resulting in a brick if we encrypt our drive? Or rather it refuse to decrypt the drive in case you don't want to be encrypted anymore? Or something else? Wasn't it already denied widely to unencrypt an Android installation from when it has been done?
The phone would not the able to perform any OTG anymore if we don't plug it to the computer before the booting preceding the installation of this recovery? Or an OTG function into this recovery will not work for the session if not plugged before booting? Or something else?
Can you add a part who warn about potential data loss? And redirect to tutorials about how to backup the most possible of the phone (app data and settings, android data and settings, kernel, RAM/ROM, phone personal identification files, anything that could help in case of brick and that could help restoring as most as possible thing like before any manipulation)?
dd
pingopower said:
What do you mean by "Decryption in a12"? Like the OS fails to read an encrypted partition, resulting in a brick if we encrypt our drive? Or rather it refuse to decrypt the drive in case you don't want to be encrypted anymore? Or something else? Wasn't it already denied widely to unencrypt an Android installation from when it has been done?
The phone would not the able to perform any OTG anymore if we don't plug it to the computer before the booting preceding the installation of this recovery? Or an OTG function into this recovery will not work for the session if not plugged before booting? Or something else?
Can you add a part who warn about potential data loss? And redirect to tutorials about how to backup the most possible of the phone (app data and settings, android data and settings, kernel, RAM/ROM, phone personal identification files, anything that could help in case of brick and that could help restoring as most as possible thing like before any manipulation)?
Click to expand...
Click to collapse
dude can you just email me on [email protected] I am tired of reading this long threads
iamshubh69 said:
dd
dude can you just email me on [email protected] I am tired of reading this long threads
Click to expand...
Click to collapse
Sure thing, but I think people maybe have those questions too. I don't ask them just for me
Bro link not working

Categories

Resources