[Q] Creating a "phone dump"? - Nexus One Q&A, Help & Troubleshooting

There's lot of threads about flashing recovery images that you download from somewhere, and how to customize your roms, etc. but i couldn't find any about dumping my current phone image to restore later if so I desire.
Is it possible?
I want to start using Cyanogen, but I also would appreciate the idea of being able to restore 100% of my previous phone software. I have an unlocked N1.
There's no info on how to actually generate your own image on the restore thread http://forum.xda-developers.com/showthread.php?t=614057
neither over the wiki http://forum.xda-developers.com/wiki/index.php?title=Nexus_One

I run the following script (AT YOUR RISK!):
1. Boot into recovery (don't worry nothing flashed):
Code:
adb wait-for-device
adb reboot bootloader
fastboot boot recovery-RA-passion-v2.2.1.img
echo ... Waiting for recovery image load
while [ -z adb shell pwd 2> /dev/null` ]
do
sleep 1
done
2a. To backup:
Code:
adb shell nandroid-mobile.sh --backup --defaultinput --norecovery
2b. To recover use the menus

gcbxda said:
There's lot of threads about flashing recovery images that you download from somewhere, and how to customize your roms, etc. but i couldn't find any about dumping my current phone image to restore later if so I desire.
Is it possible?
I want to start using Cyanogen, but I also would appreciate the idea of being able to restore 100% of my previous phone software. I have an unlocked N1.
There's no info on how to actually generate your own image on the restore thread http://forum.xda-developers.com/showthread.php?t=614057
neither over the wiki http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
Click to expand...
Click to collapse
The quickest way is to create a nandroid backup. Basically this will backup either selected or all partitions on the phone and can be restored easily. You can access this via either Amon_RA or Clockworkmod recovery. You'll need to use one of these to flash CM7 anyhow. Depending on whether you are on 2.3.3 or 2.3.4 the method to flash the recovery image differs. Either post back here with your rom version or have a good read on the Nexus one wiki Also, to understand nandroid have a read here. The process to creating a backup is a little different but the principle behind it is the same.

Install a recovery like Amon_RA's that supports Nandroid. Dead simple.
This is in the wiki.

thanks everyone.
just explaning why at the time i thought it wasn't in the wiki: it mentions the phone will be erased. i assumed it would erase the Whole nand when i installed amon_ra (so, what's the point of having a backup dump of a already erased phone?) but aparently it will only wipe out your data when enabling fastboot oem unlock.

Related

Will a Nandroid restore undo my ROM upgrade?

I wouldn't think so, but I'm really clueless about what's going on...
I have Cyanogen 3.9.8
I want 4.0.2
When I use the CM Updater, I get the dreaded acore Force Close.
So I try the manual approach, putting the 4.0.2 zip file on my SD card's root, then I reboot into recovery, and I perform a Nandroid backup (I run Linux on my computer, and don't use ADB).
Then I do a wipe, before I install the 4.0.2 zip.
Finally, I do I Nandroid restore.
Rebooting takes a long time, which tells me something has been done in the ROM department.
But when I have it up and running, everything seems just as they were before the operation, and when I start CM Updater it says "Running version: CyanogenMod-3.9.8"
I tried again, this time I booted the phone before I did the Nandroid restore, was met with the "factory fresh" Google account login screen (so it looked wiped to me...), then did a reboot to recovery and a Nandroid restore, reboot, checked CM Updater: "Running version: CyanogenMod-3.9.8".
Maybe I need to tweak my ROM updating routines..?
I have 3 partion SD card, so apps2sd is running.
Any help is highly appreciated.
Thanks,
Christopher
I'm kinda confused here, it's Monday morning. Since your trying to upgrade why do you keep doing a nandroid restore? You only want to restore nandroid if you want to go back to that previous point when you made the restore point. If you are just upgrading, just upgrade without restoring nandroid.
do exactly what you did without doing the nandroid restore at the end
Nandroid Restore is pretty simple.
Say you have ROM1 installed and there is an experimental ROM2beta out. So you want to try it.
Do a nandroid backup and it saves it to your sdcard.
The files that are saved are:
recovery.img
data.img
system.img
cache.img
misc.img
boot.img
This is almost every part of your phone except the spl and radio.
When you do a ROM upgrade MOST of the time it only updates the system and boot (some ROMs like Hero wipe/update the system, data, cache and boot.) But if your going from Cyan1 to Cyan2 then the only things being changed are system.img and boot.img. Unless you wipe, everything else should remain the same.
With all that said... you flash from ROM1 to ROM2beta and then do a restore from the ROM1 backup. So what does that mean for your phone? Is it possible to have ROM2beta ROM with the ROM1 system.img and boot.img? No. Since system.img is restoring the key elements for the ROM1 over your newly flashed ROM2beta. Bottom line. You'd be right back to where you started.
Binary100100 said:
With all that said... you flash from ROM1 to ROM2beta and then do a restore from the ROM1 backup. So what does that mean for your phone? Is it possible to have ROM2beta ROM with the ROM1 system.img and boot.img? No. Since system.img is restoring the key elements for the ROM1 over your newly flashed ROM2beta. Bottom line. You'd be right back to where you started.
Click to expand...
Click to collapse
Which explains what I am experiencing.
Thanks, 36!
That means I have misunderstood what Nandroid does.
I thought it would just take a backup of "user changed" files, like application data, configurations, call logs, that sort of things - like MyBackup Pro, more or less.
Guess I will get back to using MyBackup Pro before I upgrade my ROM.
Thanks, this really clarified things - I'm sorry I had to post such a n00b question, but I haven't found any other Nandroid postings telling me in such details what Nandroid backs up (and restores) - but then again I probably haven't looked hard enough! ;-)
~Christopher
Seems I had the same misconception and it seems that Nandroid is not nearly as useful as I had been led to believe by all the posts harping on about it. What I want is a backup of all my user data which I can restore to the updated ROM. Luckily I suspected Nandroid wasn't going to do this and used MyBackup Pro too
MikLSP said:
Seems I had the same misconception and it seems that Nandroid is not nearly as useful as I had been led to believe by all the posts harping on about it. What I want is a backup of all my user data which I can restore to the updated ROM. Luckily I suspected Nandroid wasn't going to do this and used MyBackup Pro too
Click to expand...
Click to collapse
nandroid can do this you just have to do a backup flash youre rom then push youre data.img
I understand you push the data.img but.....
how...
please
Perform a nandroid backup
Locate the backup on your sdcard under the foler "Nandroid"
Navigate to the last folder (this should be your latest)
Copy all or at least the folder that you want to push back (in this case just data.img to a directory say c:\nandroidbackup)
Open the cmd prompt and make sure that you have your fastboot.exe file in your pc's system32 directory.
If your phone is already on type "adb shell reboot recovery" in the cmd prompt to get to the bootloader and ready for FASTBOOT and then type "exit" to quit the adb shell.
If not then power on your phone while holding the camera button to get to the bootloader and then press the back button on your handset to get to FASTBOOT mode.
On your cmd prompt type "cd" along with the location of the data.img file (example cd c:\nandroidbackup) to move the command prompt to the backup location.
On the cmd prompt type fastboot flash userdata data.img and hit enter.
You should see "sending" followed by "writing" once complete type fastboot reboot and hit enter.
That should do it.
Now mind you that pushing your data across different builds may not work. If you are trying to restore your data on Hero that was previously saved from Cupcake then you're wasting your time. And vice versa. Always store a backup or two on your pc for quick and easy access in case something doesn't work.
In the event that it does not work simply wipe and follow the above directions to restore.
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
Thanks great thanks mate!!
On the cmd prompt type fastboot flash userdata data.img and hit enter.
Click to expand...
Click to collapse
This step fails for me during the "verifying signature" phase. I believe this is todo with my spl.
Is it possible to use adb to do this? or will the spl still prevent it?

[GUIDE] Back Up and Restore your ROM (manual method)

For these steps to work, ensure that your Milestone currently contains an unprotected recovery image (eg. Brazilian 2.0.1 SPF or the vulnerable recovery SPF for 2.1 Milestones).
Also ensure that you have installed the Android SDK so that you can access your phone with ADB.
These instructions are mostly based on user poseiden's guide at alldroid.org, before the site went down and was cleaned up.
How to make a Nandroid backup
Download the ADBRecovery files from here.
Unzip the archive onto the base of your SD card, so that you have a /recovery folder and an update.zip (NOTE: if you had an earlier update.zip, it will be overwritten with the ADBRecovery update.zip, so back up or rename the original update.zip.)
Reboot your phone into recovery menu:
Turn off phone
Press Camera button, then press Power. Hold them both till you see recovery screen.
Press Volume Up and Camera button at the same time till you see the recovery menu.
Run the update.zip.
Connect via ADB and execute:
If you want everything backed up:
Code:
nandroid-mobile.sh --backup
If you don't want your installed apps + data backed up:
Code:
nandroid-mobile.sh --backup --nodata --nocache --nomisc
How to do a Nandroid restore
Ensure the Nandroid backup content is found under your phone's /sdcard/nandroid/console=ttyS2,115200n8 folder.
Ensure the /recovery folder and ADBRecovery update.zip is at the base of your SD card.
Reboot your phone into recovery menu:
Turn off phone
Press Camera button, then press Power. Hold them both till you see recovery screen.
Press Volume Up and Camera button at the same time till you see the recovery menu.
Run the update.zip.
Connect via ADB and execute:
Code:
nandroid-mobile.sh --restore
Type the name of the backup you want to restore.
Telus 2.0.1 unrooted backup
Here's a clean Telus Milestone 2.0.1 Nandroid backup. I found this one on the web, and then I removed the "su" and "Superuser.apk" files so that it's no longer rooted. Sorry, the original source is uncredited as I forgot where I got it from.
As far as I know, there is no shipped SPF of the 2.0.1 Telus firmware, so this is your only option to go back to stock.
http://www.multiupload.com/TA8V2QPJEO
I used this to restore back to stock Telus Milestone ROM so that I could return the device. The only thing different from the original purchased state was the recovery SPF, but that would be really hard to tell or to find out (just a version number difference).
There's a step missing from the backup process. You need to 'flash' the update.zip from the recovery menu before you can connect over adb.
slightly said:
There's a step missing from the backup process. You need to 'flash' the update.zip from the recovery menu before you can connect over adb.
Click to expand...
Click to collapse
Oops! Fixed now. Thanks!
no need for a computer to do this anymore custome recovery does all that from the phone now .
DAGr8 said:
no need for a computer to do this anymore custome recovery does all that from the phone now .
Click to expand...
Click to collapse
Wicked, thanks for letting us know. Do you have instructions or a link to one?
EDIT: You mean this?
http://www.motorolafans.com/forums/...m-update-recovery-package-updated-v1-12d.html
I see it also does root!
dsixda said:
Here's a clean Telus Milestone 2.0.1 Nandroid backup. I found this one on the web, and then I removed the "su" and "Superuser.apk" files so that it's no longer rooted. Sorry, the original source is uncredited as I forgot where I got it from.
As far as I know, there is no shipped SPF of the 2.0.1 Telus firmware, so this is your only option to go back to stock.
http://www.multiupload.com/TA8V2QPJEO
I used this to restore back to stock Telus Milestone ROM so that I could return the device. The only thing different from the original purchased state was the recovery SPF, but that would be really hard to tell or to find out (just a version number difference).
Click to expand...
Click to collapse
You just saved my Milestone. Thank you x10!
(using xperia x10)
I've made a lot of modifications to my stock rom, and would like to share it.... so is system.img a valid way to share my *own* rom or mod ? (valid as in technically feasible? means ppl can d/l it n flash using recovery n use it?)
my main concerns are... will it boot on someone else's device? (i tried it myself... total wipe + clean stock instal, followed by flashing only my backed up system.img, *didn't flash data.img, only system* it took an eternity to boot first time but it ran)
second concern... system.img doesn't have any personal data right? logs, msgs etc are in data partition i guess??
Sent from my X10i using XDA App
Sent from my X10i using XDA App

[q] neeeeeeeed help please!!!! Urgent!!!!!

Ok so I am in a serious situation here... I have been using my nexus one (STOCK) for few months now and i love the phone right..I am new to the android interface but I reaallly am tempted on getting my phone rooted...btw its running on froyo 2.2, FRF91, Mod 6.0.0-N1-RC3.
Here is the problem... the more I research into it the more I'm getting confused for some reason...
Is there any one who can just go thru the steps I need to get it all done please.
for example: what should i be doing first, root, bootloader unlock, nandroid backup, rom install, mod install.....and so on? just need a little overview on everything once...
also as i have the mod 6.0.0, does it need to be upgraded to some other version or does it need to be flashed?!
please help me on this as I will seriously pray for your long life !
AK
There are loads of guides on here already:
http://forum.xda-developers.com/showthread.php?t=705460
Or even googling nexus one root steps gave plenty of guides:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
- First step : Root...
If root is the only thing you want, then you're finished.
If you want to flash alternate ROM's, then:
- Flash alternate recovery(Amon_RA or Clockwork)
- Do a nandroid backup(is just a backup from your current ROM, so you can go back if the next step fails)
- Flash a ROM.
You don't have to unlock the bootloader.
Guides for the above you can find in the Nexus Forums.
How do I get those crazy animations at the startup? don't I need to unlock the boot loader for that??
How do i get those crazy animations at the startup, would i need to unlock the bootloader for that ??
Just curious, but can you type the full mod version again, because that looks extremely like a Cyanogen mod...?
Sent from my Nexus One using XDA App
YoMarK said:
- First step : Root...
If root is the only thing you want, then you're finished.
If you want to flash alternate ROM's, then:
- Flash alternate recovery(Amon_RA or Clockwork)
- Do a nandroid backup(is just a backup from your current ROM, so you can go back if the next step fails)
- Flash a ROM.
You don't have to unlock the bootloader.
Guides for the above you can find in the Nexus Forums.
Click to expand...
Click to collapse
You have made me extremely curious with your statement:
You don't have to unlock the bootloader.
I am contemplating partitioning my SD card so that I can take advantage of "Apps2SD". My phone is rooted w/ Froyo 2.2.1 FRG83D, but I haven't proceeded with flashing the Cyanogen recovery image because I was under the impression that unlocking bootloader is a requirement.
If it is possible to flash a recovery image and/or a custom ROM without unlocking bootloader, why bother unlocking bootloader?
Yes I'll admit, I'm a NEWBIE.
Master N1 said:
You have made me extremely curious with your statement:
You don't have to unlock the bootloader.
I am contemplating partitioning my SD card so that I can take advantage of "Apps2SD". My phone is rooted w/ Froyo 2.2.1 FRG83D, but I haven't proceeded with flashing the Cyanogen recovery image because I was under the impression that unlocking bootloader is a requirement.
If it is possible to flash a recovery image and/or a custom ROM without unlocking bootloader, why bother unlocking bootloader?
Yes I'll admit, I'm a NEWBIE.
Click to expand...
Click to collapse
Unlocking a bootloader makes it a lot easier to flash stuff. And some people had their bootloader unlocked because there were no ways to actually flash without unlocking before...now, new techniques appeared and you can do it without.
gravufo said:
Unlocking a bootloader makes it a lot easier to flash stuff. And some people had their bootloader unlocked because there were no ways to actually flash without unlocking before...now, new techniques appeared and you can do it without.
Click to expand...
Click to collapse
Would utilizing ROM Manager (Flash ClockworkMOD Recovery) be one of those new techniques?
I'd like to partition my SD card just in case I decide to take advantage of "Apps2SD (or similar)" in the future. In doing so a recovery image is required, but would like to avoid unlocking bootloader at this stage.
BTW, would you happen to know if the suggested SD partitions are still the same?
32 MB linux-swap partition
512 MB ext2 partition and
remaining free space as a fat32 partition
Master N1 said:
Would utilizing ROM Manager (Flash ClockworkMOD Recovery) be one of those new techniques?
I'd like to partition my SD card just in case I decide to take advantage of "Apps2SD (or similar)" in the future. In doing so a recovery image is required, but would like to avoid unlocking bootloader at this stage.
BTW, would you happen to know if the suggested SD partitions are still the same?
32 MB linux-swap partition
512 MB ext2 partition and
remaining free space as a fat32 partition
Click to expand...
Click to collapse
First, a custom recovery (such as ClockworkMod and Amon_Ra) are the result of either unlocking the bootloader or using adb.
Basically, with ADB, you need to be rooted and then download a custom recovery of your choice as well as flash_image onto the root of your sdcard (i.e. in no folders) and run the following commands:
NOTE: These commands will assume that you renamed the recovery image to recovery.img instead of whatever name was there before. It will also assume you have the android SDK w/ adb + usb drivers installed as well as checked the USB Debugging setting under Settings > Applications > Development in your Nexus
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
As for your a2sd, the values look correct to me but I am no expert in partitioning optimally, wait for some linux guru to help you in there
gravufo said:
First, a custom recovery (such as ClockworkMod and Amon_Ra) are the result of either unlocking the bootloader or using adb.
Basically, with ADB, you need to be rooted and then download a custom recovery of your choice as well as flash_image onto the root of your sdcard (i.e. in no folders) and run the following commands:
NOTE: These commands will assume that you renamed the recovery image to recovery.img instead of whatever name was there before. It will also assume you have the android SDK w/ adb + usb drivers installed as well as checked the USB Debugging setting under Settings > Applications > Development in your Nexus
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
As for your a2sd, the values look correct to me but I am no expert in partitioning optimally, wait for some linux guru to help you in there
Click to expand...
Click to collapse
Thanks so much for your feedback.
To answer your earlier question.
Yes - you can also install a custom recovery via ROM Manager.
Sent from my Nexus One using XDA App

[Q] How to properly make a total backup of your current ROM

I have a very decent working ROM at the moment (4.4.4 rooted xposed gravitybox etc.) and I'm not sure I can live with Lollipop without al those tweaks. So before upgrading to Lollipop (whenever that may be), I want to make a decent backup of my current ROM.
Normally I would do this with TWRP, but the backup doesn't seem to work at the moment. And there doesn't seem to be a properly working version of TWRP.
So how do I make a proper backup of my ROM?
Adb?
A confirmed working version of TWRP?
CWM?
Another?
Jeltel said:
I have a very decent working ROM at the moment (4.4.4 rooted xposed gravitybox etc.) and I'm not sure I can live with Lollipop without al those tweaks. So before upgrading to Lollipop (whenever that may be), I want to make a decent backup of my current ROM.
Normally I would do this with TWRP, but the backup doesn't seem to work at the moment. And there doesn't seem to be a properly working version of TWRP.
So how do I make a proper backup of my ROM?
Adb?
A confirmed working version of TWRP?
CWM?
Another?
Click to expand...
Click to collapse
You can use standard tools installed on the phone to dump your partitions. See here for a rundown. I'd recommend backing up /boot, /recovery, /system, /pds, /modem and /fsg.
Ah yes, that's what I was looking for. Thanks
When I restore the mentioned items, will I get back my old installation? Or should I backup more? i.e. userdata for example?
And how to restore all these items? (I know to flash the boot, recovery and system.img via adb).
Yeah, you'd need to backup the data partition too, if you want to keep settings and user data. Remember, dd produces a 1:1 copy of the partition... I prefer to backup personal data selectively. The quick way to do it is by using a backup app: Most use Titanium Backup, but I find Chainfire's Helium does the job well, too. The other way is to use the built-in 'backup' command directly to select a range of files to save (i.e. 'adb backup')...
The partition images can be restored from adb using the reverse version of the command you used to make to the backup, i.e. use dd but with the 'if' and 'of' parameters switched:
Code:
dd if=/path/to/source.img of=/path/to/block/device
Be careful though; if you write the wrong image to the wrong partition, you can damage -- or even hose -- your software environment.
In the case of most partitions, restoring images should be done whilst booted into recovery for safety reasons, rather than overwriting a filesystem whilst it is mounted and in use. If you have the stock recovery installed, you can temporarily boot into TWRP or CWM recovery from a recovery image stored on your computer (i.e. 'adb boot /path/to/recovery.img') and then enable adb from within the custom recovery environment. Then you just use 'adb shell', followed by the 'su' command to switch to the root user account.
For the same reason, you should write the recovery partition backup back to disk from adb within the normal android environment. Again, you must do this after switching to the root user account by issuing the 'su' comand.
Alternatively, you should be able to write all the images from fastboot mode (i.e. 'adb reboot lootloader'). For example:
Code:
adb fastboot flash recovery recovery.img
AFAIK, fastboot will accept standard images created with dd, but I have never tried it on a Moto G, so YMMV... Maybe someone else would care to comment on this?

zenfone 2 (z00d) not booting

Hello, a few days ago my zenfone started acting up (again), with built in applications crashing randomly and failing to boot half of the times. I always managed to fix it downloading the firmware from Asus' website and re-upgrate it, but this time it didn't worked out quite well. It now refuses to boot (sometimes gets stucked at boot, simetimes I manage to have asus screen). Booting into recovery prints `E:mount fail, change path to mount /dev/block/mmcblk1`, then errors about cache partiton not being found.
I've tried pretty much anything that would not result in data loss:
Wiping cache doesn't report errors, but doesn't help either,
Flashing stock boot.img and droidboot.img don't report error, but doesn't help either,
Flashing TWRP to recovery reports success, but I still get stock recovery,
Sideload fails coz it doesn't find expected mounts
Adb shell doesn't work as it can't find `/system/bin/whatever`
`adb pull /proc/partitions` returns what looks like a legit partitions list for mmcblk0 to me
Does anyone know what else I can try to rescue the data on the phone?
WobLight said:
Hello, a few days ago my zenfone started acting up (again), with built in applications crashing randomly and failing to boot half of the times. I always managed to fix it downloading the firmware from Asus' website and re-upgrate it, but this time it didn't worked out quite well. It now refuses to boot (sometimes gets stucked at boot, simetimes I manage to have asus screen). Booting into recovery prints `E:mount fail, change path to mount /dev/block/mmcblk1`, then errors about cache partiton not being found.
I've tried pretty much anything that would not result in data loss:
Wiping cache doesn't report errors, but doesn't help either,
Flashing stock boot.img and droidboot.img don't report error, but doesn't help either,
Flashing TWRP to recovery reports success, but I still get stock recovery,
Sideload fails coz it doesn't find expected mounts
Adb shell doesn't work as it can't find `/system/bin/whatever`
`adb pull /proc/partitions` returns what looks like a legit partitions list for mmcblk0 to me
Does anyone know what else I can try to rescue the data on the phone?
Click to expand...
Click to collapse
When you flash TWRP and try to boot into recovery, have you tried using adb with "adb reboot" command?
Have you tried the "fastboot boot twrp.img" command"(with the TWRP file renamed to "twrp.img")? If you can get that to work, you can temporarily boot a TWRP session and then use it to make a nandroid backup.
Have you tried creating an adb backup, as described in the link below?
https://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
If you have corrupted partitions, you might not retrive anything, you might have no choice but to use an option that wipes, repartitions and flashes the device.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When you flash TWRP and try to boot into recovery, have you tried using adb with "adb reboot" command?
Have you tried the "fastboot boot twrp.img" command"(with the TWRP file renamed to "twrp.img")? If you can get that to work, you can temporarily boot a TWRP session and then use it to make a nandroid backup.
Have you tried creating an adb backup, as described in the link below?
https://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
If you have corrupted partitions, you might not retrive anything, you might have no choice but to use an option that wipes, repartitions and flashes the device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thanks for suggestions,
adb backup doesn't work. It complains about /system/bin/sh not found (looks like either the partition isn't mounted or the failed update erased it).
fastboot boot doesn't work. I was messing with boot.img before, and I found out that intel's boot.img (my zenfone is x86) is not standard format. fastboot logs `creating boot image...`, I suspect it doesn't work at all for intel's. It reports 'booting OK' but the phone doesn't reboot at all.
fastboot flash recovery twrp.img returns OK but still stock recovery...
WobLight said:
thanks for suggestions,
adb backup doesn't work. It complains about /system/bin/sh not found (looks like either the partition isn't mounted or the failed update erased it).
fastboot boot doesn't work. I was messing with boot.img before, and I found out that intel's boot.img (my zenfone is x86) is not standard format. fastboot logs `creating boot image...`, I suspect it doesn't work at all for intel's. It reports 'booting OK' but the phone doesn't reboot at all.
fastboot flash recovery twrp.img returns OK but still stock recovery...
Click to expand...
Click to collapse
I have an intel atom tablet that I used this tool to boot TWRP then root and create nandroid backups with.
https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
There may be similar tools for your intel tablet, or maybe you can modify this tool or work out something similar.
There is another similar tool that I used on an intel based RCA Viking III tablet.
Sent from my LGL84VL using Tapatalk
Droidriven said:
I have an intel atom tablet that I used this tool to boot TWRP then root and create nandroid backups with.
https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
There may be similar tools for your intel tablet, or maybe you can modify this tool or work out something similar.
There is another similar tool that I used on an intel based RCA Viking III tablet.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
It worked!!! :victory:
Thank you so much for helping me out with this, I spent over a week trying to fix/backup data, I was going to give up.
After backing up things properly I'll play with it, see if I can have it booting again (maybe not stock system ).
WobLight said:
It worked!!! :victory:
Thank you so much for helping me out with this, I spent over a week trying to fix/backup data, I was going to give up.
After backing up things properly I'll play with it, see if I can have it booting again (maybe not stock system ).
Click to expand...
Click to collapse
Be careful, this tool is built to work on a lot of different devices with different hardware and different partitioning, the differences in partitions means that it cannot create or restore nandroid backups on all devices that the tool can boot on. Some intel devices that this tool works on can create and restore nandroid backups, some can't, it just depends on how the device is partitioned. It can also be used to flash ROMs on some devices but not on others.
This tool can boot a temporary recovery session on a lot of devices but not all of them can use all of the features in the recovery that it boots.
This difference in partitioning means that trying to restore a backup or flash a ROM can break some devices because the partitioning isn't right. So just be warned, you will be exposing your device to a certain amount of risk if you try using all of the features in the temporary recovery session.
Also, this tool was designed to boot a temporary recovery session on intel devices that have a locked bootloader, this recovery session can not flash ROMs on intel devices that have a locked bootloader, it can only be used to flash devices that have an unlocked bootloader. If your bootloader is locked, you'll brick your device if you attempt flashing a ROM on your device using this recovery session.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Be careful, this tool is built to work on a lot of different devices with different hardware and different partitioning, the differences in partitions means that it cannot create or restore nandroid backups on all devices that the tool can boot on. Some intel devices that this tool works on can create and restore nandroid backups, some can't, it just depends on how the device is partitioned. It can also be used to flash ROMs on some devices but not on others.
This tool can boot a temporary recovery session on a lot of devices but not all of them can use all of the features in the recovery that it boots.
This difference in partitioning means that trying to restore a backup or flash a ROM can break some devices because the partitioning isn't right. So just be warned, you will be exposing your device to a certain amount of risk if you try using all of the features in the temporary recovery session.
Also, this tool was designed to boot a temporary recovery session on intel devices that have a locked bootloader, this recovery session can not flash ROMs on intel devices that have a locked bootloader, it can only be used to flash devices that have an unlocked bootloader. If your bootloader is locked, you'll brick your device if you attempt flashing a ROM on your device using this recovery session.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank for your concern, I've backed up contents of the sdcard and data partition (other partitions fails to mount) to an external SD. Ofc sdcard contents are just copy/pasted, as for data partition I've checked and looks like I can open the twrp archives from linux. I'm gonna try to clone the whole mmcblk0 before trying anything weird tho .
WobLight said:
Thank for your concern, I've backed up contents of the sdcard and data partition (other partitions fails to mount) to an external SD. Ofc sdcard contents are just copy/pasted, as for data partition I've checked and looks like I can open the twrp archives from linux. I'm gonna try to clone the whole mmcblk0 before trying anything weird tho .
Click to expand...
Click to collapse
You might can modify the tool itself or the TWRP .img that is built into the tool to modify it to work with the way that your device is partitioned, that way it mounts, reads and writes those partitions correctly.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You might can modify the tool itself or the TWRP .img that is built into the tool to modify it to work with the way that your device is partitioned, that way it mounts, reads and writes those partitions correctly.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I've tried to use the twrp for z00d I have previously downloaded, I have to do some tweaking to make it boot. Even tho it looks like a newer version, console is crashing and partitions won't work anyway. Since stock recovery fails to mount cache I guess there's corruption somewhere on the device. I might have found the stock partitions.tbl, but if I manage to clone mmcblk0 to an external sd, I can perhaps mess with the image with linux and confirm whether is there's corruption.
WobLight said:
I've tried to use the twrp for z00d I have previously downloaded, I have to do some tweaking to make it boot. Even tho it looks like a newer version, console is crashing and partitions won't work anyway. Since stock recovery fails to mount cache I guess there's corruption somewhere on the device. I might have found the stock partitions.tbl, but if I manage to clone mmcblk0 to an external sd, I can perhaps mess with the image with linux and confirm whether is there's corruption.
Click to expand...
Click to collapse
Here is another tool that I used on an intel based RCA tablet, it might can be adapted to be used on your device if you know or can find out where the tool can be modified to work on your device.
https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Sent from my LGL84VL using Tapatalk
Droidriven said:
Here is another tool that I used on an intel based RCA tablet, it might can be adapted to be used on your device if you know or can find out where the tool can be modified to work on your device.
https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello, I've tried a few more stuff today, by the looks of it, the device silently fails to write anything.
I've tried to use adb push to flash a fixed image to /dev/block/mmcblk0, tried fastboot flash, tried dd from the recovery, even tho it reports ok, nothing is actually written on the device. I've tried to rename a file in data (which does mount), but after unmounting/remounting the partition the file still have the old name.
Maybe I can try loading a system on the external sd instead, but that's it.
Thanks again for your help, I was able to recover the data which was actually my priority.
EDIT: partition command also fails

Categories

Resources