Related
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.
Hi I have an LG Optimus 2x SU660 and I am having a problem on upgrading it.
It don't have a adb boot-loader so I can flash IMG files to it.
Is there a guide so I can flash IMG files using nvflash? Or some one who know how to do it.
Thanks.
It is possible to use fastboot, but it's more awkward than other phones.
The thing with NVFlash is you need to be sure of your partition layout, NVFlash uses a number to identify which partition to write the .img too, if you don't know what the numbers are, you'll have some difficulty.
Thank you. I am also unable to access the fastboot.
I think its because I used LG-P993 rom that is compatible with SU660.
Never heard of the P993 before, but looked it up and it appears to be another variant of the Optimus 2X. Great, that'll confuse people.
To use fastboot you have to wipe your boot partition, if you have to ask, then I don't recommend it.
What might be best is if you can get someone to make a NAND backup of a stock SU660 and then you restore it.
Can you still get into (custom) recovery? If so then I don't see why you couldn't DD the image files, you can get the partition layout from /etc/recovery.fstab
I am now stuck again on fastboot. any fix can you recommend?
Oh bloody hell, what have you gone and done?
If (as I'm assuming) you've got into fastboot, then the best thing you can do is get a recovery.img and use: fastboot boot recovery.img, at which point you can flash something.
Did fastboot flash recovery c:/recovery.img but still it won't boot.
Don't worry because I can return it to its original state by flashing the old nvflash rom.
Of course it wont boot, you've wiped your boot partition remember
You will now have to tell it to boot from something, so as above, try: fastboot boot c:\recovery.img and you should be in recovery. Now from there you can flash a .zip (which will replace your missing boot partition) or restore a backup.
OR
If you have the right bootimage handy, you can use fastboot boot c:\boot.img and the phone will fire up, after that you need to use DD to permantly install the boot image you booted.
That you do from ADB shell or the terminal: dd if=/sdcard/boot.img of=/dev/block/mmcblk0pX (where X is the boot partition)
what is dd?
---------- Post added at 06:43 PM ---------- Previous post was at 06:42 PM ----------
Sir may i requrest for your YM id?
If I knew what a YM ID was I'd tell you lol
dd is basically a *nix copy command, did you not use it to wipe the boot partition?
Yahoo Messenger Id.
No sir.
Oooh there's something I've not used in a while!
[email protected]
I have my wife's LG Revolution running Broken Out rom. I am getting to read to send int to big read for a replacement. They made me state that I had made not hardware or software modifications. So I need to return this to stock. I have successively used LGNPST in the past. But now the USB port does not work in data mode. A computer will charge the phone, but the phone does not prompt for USB Mode when plugin to a computer. I have tried 2 computers and 2 different cables. All of which work for my LG revolution with out a problem.
Is there any way to remove Clock Work mode and switch it to the factory recovery, and return the rom to Stock without a working USB port?
I have a way of copying files to the SD card if needed.
Thanks.
I like this this guys thoroughness, though, not totally relevant for you. The following steps would pertain best in your situation.
1) wipe data, cache, davlik cache from CWM
2) When the phone initial setup begins, bypass it with this method. Touch top left, top right, bottom right, then lastly bottom left.
3) OPTIONAL - Erase external SD card from settings menu (if you thnk it's necessary... you may not be sending that back in)
4) format internal memory from settings menu
5) LGNPST flash stock V9. Get the V9 TOT here and unzip it first.
Flashing the TOT just took me 20 minutes.
Really, though, just flashing the TOT will suffice.
That's very neet, thank you. But can I use LGNPST without a usb cable? My usb port will only charge, no data.
Sent using Tapatalk 2
Whoops. Missed that part. I was on a roll doing a TOT via USB myself. Maybe, if someone could wrangle you up a stock boot.img to flash in CWM after you unroot?
Sent from my VS910 4G using Tapatalk 2
If someone who is running a stock rooted rom, v9 or later, wants to put up a backup I can rip the rom out of it and make a flashable zip. Just when making the backup, go into the backup settings of cwm and change it to tar.gz. Not the blob crap.
Mine phone is now rooted, stock and running ZVb. This one could be backed up and installed on my. Wife's phone with the bad usb port?
I should install cwm on mine to take a backup?
Sent from my VS910 4G using Tapatalk 2
thesavo said:
Mine phone is now rooted, stock and running ZVb. This one could be backed up and installed on my. Wife's phone with the bad usb port?
I should install cwm on mine to take a backup?
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
That would be awesome! To have at least the android part of the new update is better than nothing.
He still needs to find a way to remove cwm with out a pc?
I don't have clockwork on my stock + rooted Revolution. Can I use any rooted backup tool from the market/play store?
IF i have to use Clockwork mod recovery, can I just do a nandroid backup from the good phone the other phone? I have to take in to big red tomorrow.
Does anything need to be stripped out of the nandroid back?
I was just trying to think of another way to get you going. ADB Wireless sounded good up until the point that the SU part has to be removed. Then ADB Wireless would fail I'm sure.
My best guess for you is to use the Easy V8 - V9 All in One by Mark Once Again as a basis for commands to execute from terminal. I'm not sure if losing root during terminal will affect the operation however. Looking at the batch file adb shell commands, it looks fairly straightforward to manually do. I am just not 100% sure it will work. Someone else with more experience could chime in about that.
Below is what I copied out of the batch file, the UNROOTSTOCK portion.
The ALL CAPS portions are comments I have added in. The usual warnings apply. Use at your own risk.
Code:
rm /data/bootlogo/bootlogopid
ln -s /data /data/bootlogo/bootlogopid
REBOOT
echo 'ro.kernel.qemu=1' > /data/local.prop
REBOOT
UNROOTING TIME
rm /system/bin/su
rm /system/xbin/su
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/bin/busybox
rm /data/local/tmp/* 2>/dev/null
USE A ROOT FILE EXPLORER APP TO COPY THIS Files\stockrecovery.img FROM THE EASY V8 - V9 ZIP. . .
TO HERE ON YOUR PHONE /data/local/tmp/stockrecovery.img
TIME TO PUSH THE STOCK RECOVERY
dd if=/data/local/tmp/stockrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
CLEAN-UP TIME
rm /data/bootlogo/bootlogopid
rm /data/local.prop
REBOOT AND YOU'RE DONE!
Hope that helps, or that it spurs the help you need.
EDIT: To make it stock, all the superuser and busybox files need to be removed, and the stock boot image needs to replace the one that has CWM. Otherwise, CWM is still there. So, no. A nandroid from the other phone wouldn't help you.
But would a restored nandroird backup (from my phone) work enough to get me 1/2 way there? Would the nandroid restore leave me with
Rooted Verizon rom
Clockwork mod recovery.
If so. I could DD the stock recovery over clockwork mod recovery.
Then unroot it with a terminal app.
By the looks of your pseudo-code script, It does do all of that, in a different order.
It's possible to capture a stock, unmolested nandroid, but that would be from a bone stock phone with CWM I think. A dev did that for us on the Nabi 2, making a stock image before the rooting business. Then it's just getting the stock boot image back, if you catch my drift.
I could have done it a couple days ago having just reTOT'ed...
Edit: The Nabi is a tablet and I think some have shared their images, but I don't know if there are any implications sharing a phone nandroid.
Sent from my VS910 4G using Tapatalk 2
I have two of these VS910s. I just cleared out my internal SDCard on my VS910. It's rooted running the newest verizon rom. It doesn't have CWM right now, but is that required for nandroid backup? To restore to my wife's with the busted USB port? I'll run the backup to my sdcard then place it in her phone to run the restore.
Needing CWM. . . no. I was going to say yes, but there is a way to make a nandroid with your phone on. Using Online Nandroid, or an app developed based on it, Orange Backup, you can make an image with your phone on, no need for CWM. It will need a patch file installed, but I already got that going with the dev. It looks like it will work for the Revolution. One caveat. While I tested that it successfully backed up my phone, I didn't actually restore the nandroid created.
Looking into the Nabi's stock backup during rooting and recovery, the dev used TWRP instead of CWM. TWRP supports Open Recovery Scripts which he used to do a stock backup. No go for us with CWM, at least not how he did it. No matter because your phone is rooted.
OK, so I installed CWM recovery on my working phone. No big deal. I took two backups for good measure on the bad phone. I also restored one of the backups, it seamed to work.
I am taking a backup of my rooted stock phone. I will then attempt to restore it to the bad phone. Any thoughts to using DD in a terminal app on the phone? I should then dd the recovery.img file over CWM,
To unroot, i think i shuld be able to do as you suggested to delete SU.apk and busybox.
Good luck. Dinner is served now so I'll be missing for a while.
Bait-Fish said:
Good luck. Dinner is served now so I'll be missing for a while.
Click to expand...
Click to collapse
We have stupid verizon 4G LTE boot video on the bad phone. That's a good sign.
Edit: Its running a VZW rom now!
home stretch
Ok, so after restoring a Nandroid backup of verizon's VZB to the bad phone. Now I need to un-root it. and I should be good. Also, Settings -> about says its version VZ9 not VZB. Odd.
Plan.
Add my google account to get to play store.
Add a terminal app.
Use terminal to delete any nandroid backups.
Run DD from terminal to overwrite CWM with recovery,img
delete rooted files.
Run factory wipe. from settings menu or PWR + Vol Down.
Then I should be done
Any thoughts.?
Seems about right. The version won't tick up from VZ9 unless you do the actual OTA I understand. Something about the baseband.
Sent from my VS910 4G using Tapatalk 2
Hi,
Seeing if anyone has stock images (system & boot) for the Urbane. I have hours of searching in online and came up empty. I flashed a system file that didn't belong and am now stuck on the splash screen. Does anyone have or has anyone seen the stock images??
Thanks in advance.
You sound like you know more about this stuff than me, but can you use the OTA update and recovery in the development forum? Would a factory reset overwrite system changes?
I was able to find a TWRP backup that was submitted on the forum for a LGWR development that worked perfectly. I will say I put my self through a lot of trouble as the rom I flashed messed with partitions and write permissions. I ended up doing a wipe in TWRP followed by individually wiping each partition. Then I was able to load the backup through adb and restore.
Thanks!
rwade434 said:
Hi,
Seeing if anyone has stock images (system & boot) for the Urbane. I have hours of searching in online and came up empty. I flashed a system file that didn't belong and am now stuck on the splash screen. Does anyone have or has anyone seen the stock images??
Thanks in advance.
Click to expand...
Click to collapse
Hi @rwade434,
Were you able to find a way to recover? I have got myself (stupid me!) into trouble by flashing the wrong ROM (damn!) and now I am stuck into fastboot menu!
Any idea how and where to get the original LJZ13E or LDZ22D image back to our Urbane?
Thanks a lot.
Ok, I have got myself out of misery by following the nice thread at http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005. There was the TWRP recovery and the 5.1.1. image backup. Thanks for the tips.
It certainly wasn't easy for me to find, it doesn't seem the the Urbane is really owned by anyone out there.
Were you able to find any ROMS for the Urbane?
This works to get the watch back to the last firmware version, but it seems that the system remains modified and unable to take the newest 1.3 firmware (Status 7 error). If anyone has the true, factory images (non-TWRP), I sure would appreciate them being posted (as I am sure others would too). Worst case scenario, a TWRP backup of the latest 1.3 image would work, too. Thanks!
meatlocker said:
This works to get the watch back to the last firmware version, but it seems that the system remains modified and unable to take the newest 1.3 firmware (Status 7 error). If anyone has the true, factory images (non-TWRP), I sure would appreciate them being posted (as I am sure others would too). Worst case scenario, a TWRP backup of the latest 1.3 image would work, too. Thanks!
Click to expand...
Click to collapse
Follow the step (copy from www reddit com/r/AndroidWear/comments/3hsmkq/ota_downloads/), it can fix the problem.
-----------------------------------------
The first thing that I did was relocked my bootloader, then unlocked it again, which wipes everything (again). Next, I used the adb shell command, and typed "su" to gain Super User. Then, I mounted the file system to r/w, using the following command: mount -o remount,rw /system Next, I cd'd to system/bin. In system/bin, I used the mv command to rename the app_process32_original file to app_process32. That looks like: mv app_process32_original app_process32. Then, I renamed the install-recovery_original.sh file to install-recovery.sh (using the same mv command as above).
-----------------------------------------
And then reboot into recovery mode and sideload the new ota.
Hahaha, that's a first for me. You quoted my own comment from Reddit. I hope my solution helps someone else. Have a 'thanks' for offering to help someone, Alex.
@rwade
rwade434 said:
I was able to find a TWRP backup that was submitted on the forum for a LGWR development that worked perfectly. I will say I put my self through a lot of trouble as the rom I flashed messed with partitions and write permissions. I ended up doing a wipe in TWRP followed by individually wiping each partition. Then I was able to load the backup through adb and restore.
Thanks!
Click to expand...
Click to collapse
Could you tell me what folder did you use to store the backup.zip? I've been trying to bring my Urbane back to life. It's driving me crazy.
mseck said:
Could you tell me what folder did you use to store the backup.zip? I've been trying to bring my Urbane back to life. It's driving me crazy.
Click to expand...
Click to collapse
https://mega.nz/#!0N0SiCrK!NEHqeolukz7jkuazn3V3eHSzVMC2hcEDbk4P3-cU7mY
Copy the folder of the zip into TWRP/BACKUP/505KPZK0107693/ and restore backup
potaturrias said:
https://mega.nz/#!0N0SiCrK!NEHqeolukz7jkuazn3V3eHSzVMC2hcEDbk4P3-cU7mY
Copy the folder of the zip into TWRP/BACKUP/505KPZK0107693/ and restore backup
Click to expand...
Click to collapse
Do i live the file as RAR or change it to ZIP? or unzip and move the folder itself?
@rwade434
Thank you for the TRWP back up, I had a couple issue creating directories so i created them manual. and Copy/paste each file.
I've been without my watch for 4 Days. Thank you much!
Factory reset, like new
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