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]
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.
I can boot up to use my phone and whatever. Only problem is that, i try booting in recovery, and it just stays on initial nexus x logo. I use 4ext touch recovery. I then flashed CWM. And still stay on initial nexus x logo. Please help.!! D; -
Leo,
time to learn fastboot--
although with cwm not flashing maybe you lost root--did you ever get partitioned for ics and have 4ext working or any recovery working?
either way you could try these ideas below--
did you buy paid version and do you have sdk on pc and where is fastboot.exe? Tools folder?
---------- Post added at 04:25 AM ---------- Previous post was at 04:00 AM ----------
if you paid, there is a dl link on 4ext OP page you can click on and it will dl you a .img you can fastboot to get recovery back.
one should also be saved on your sdcard
not sure whether it matters if paid or not
put in your tools or fastboot.exe folder, cd to that folder
have phone in fastboot mode
fastboot devices to check phone recognized
fastboot flash recovery recovery.img if recovery.img is exact name of img file
then fastboot reboot-bootloader
one time time I had to type fastboot erase system before i fastbooted the recovery to get it to work
good time to back up anything you can as in sdcard and phone stuff if you have a non root required bu program like MyBackUp Pro
i have lost recovery a couple times before with ics roms
i got to call it a night and will be on road all day tomorrow
if you don't get it someone else will offer help
ken
did the recovery stopped working right after installing blackrose?
is ur bootloader locked?
as ken suggested u need to fastboot recovery.img
Sent from my Nexus One using Tapatalk
rugmankc said:
Leo,
time to learn fastboot--
although with cwm not flashing maybe you lost root--did you ever get partitioned for ics and have 4ext working or any recovery working?
either way you could try these ideas below--
did you buy paid version and do you have sdk on pc and where is fastboot.exe? Tools folder?
---------- Post added at 04:25 AM ---------- Previous post was at 04:00 AM ----------
if you paid, there is a dl link on 4ext OP page you can click on and it will dl you a .img you can fastboot to get recovery back.
one should also be saved on your sdcard
not sure whether it matters if paid or not
put in your tools or fastboot.exe folder, cd to that folder
have phone in fastboot mode
fastboot devices to check phone recognized
fastboot flash recovery recovery.img if recovery.img is exact name of img file
then fastboot reboot-bootloader
one time time I had to type fastboot erase system before i fastbooted the recovery to get it to work
good time to back up anything you can as in sdcard and phone stuff if you have a non root required bu program like MyBackUp Pro
i have lost recovery a couple times before with ics roms
i got to call it a night and will be on road all day tomorrow
if you don't get it someone else will offer help
ken
Click to expand...
Click to collapse
Thanks Ken, I will go through your steps later on. And I wasn't able to be partitioned, my command gave me error: cannot find hboot_brcrust_210-8-218-ICS.nbo
HTCLeoSence3.X said:
hboot_brcrust_210-8-218-ICS.nbo
Click to expand...
Click to collapse
Just to make sure you did the right thing. Extension isn't nbo, it's nb0.
Sent from my Nexus One
HTCLeoSence3.X said:
Thanks Ken, I will go through your steps later on. And I wasn't able to be partitioned, my command gave me error: cannot find hboot_brcrust_210-8-218-ICS.nbo
Click to expand...
Click to collapse
It could be that you didn't specify correct path to the nb0 file.
so i have to put c:\USERNAME\program files\Android\android-sdk\platform-tools\hboot_brcrust_210-8-218-ICS.nb0
the nb0 is a zero not o nb(zero)0
put your android sdk on root of c drive not in programs
then open command window and after your user name type cd/
at the C:\> prompt type cd Android/android-sdk/platform-tools then hit enter and you should see-- (btw, not sure if command line is case sensitive as you have upper and lower case "android"
C:\ Android\android-sdk\platform-tools right after this line type fastboot devices do not hit enter first
you should see your phone ID# HT******* then you can type fastboot commands when you have phone in bootloader (fastboot) mode
assume your fastboot/adb stuff is in platform-tools. i have an older version of sdk and only use tools not platform tools. but you should have adb.exe and fastboot.exe and two adbWin dll's. an Api and UsbApi
btw if you have set up sdk correctly as you said you have exp with it--you need to have set your environmental path also
if you haven't review sdk setup in wiki, as you need to see your phone after you type fastboot devices before you can go further
also are your drivers installed and did you review the posts by efrant on adb and fastboot explanation--good info if you don't already know it
---------- Post added at 03:15 AM ---------- Previous post was at 03:02 AM ----------
a note
i guess with br installed you may not need sdk to run fastboot for br stuff. i don't do it that way so someone else may be able to offer advice. still need correct path to fastboot.exe folder drivers installed per br OP. but since you showed us the path to tools assume you are all setup with sdk and i prefer it that way myself.
Thanks man. Helped a LOT. Now running ICS. I swear thanks a million.
Sent from my Nexus One using xda premium
Welcome and enjoy------
Now that the bootloader is unlocked, everyone is asking "WTF do I do now?". Well, here's a bit of help to get you started. I'm assuming you already have adb and fastboot setup and working -- if not, quit reading and get that taken care of. Also, I only run Linux...so I'll try to be transparent and only list the fastboot commands.
I assume that you're not a complete moron and can Google what you don't understand.
Don't use the stock\SDK fastboot binary for flashing /system.
An updated fastboot binary for Lin\Win\Mac can be found here on the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory in your $PATH -- Ubuntu\Debian users can just add it to ~/bin (enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere handy...that's on you to decide.
ROOT\ADMINISTRATOR INFO
On Linux, you might have to run as root in order to run some of the fastboot commands. If your system uses sudo for root commands, typing "sudo -i" will bring up an interactive sudo shell so you don't have to type sudo over and over again. If your system uses su for root, well, you already know the command.
On Windows, you have to enable Administrator Privileges to be able to run some of the fastboot commands.
Linux Terminal Hints
~/ means your home directory -- example -- "gedit ~/Documents/file.txt" would open file.txt in gedit easier than /home/yourusername/Documents/file.txt
You can add a * to file names and directories to not type as much -- example -- "gedit ~/Doc*/file.txt" is the same as the command above, only shortened. If two files have similar names, like Documents and Downloads, then you have to type the name up until the firs different character then add *.
Use the command "../" to go up\back one directory. The command is stackable so "../../" would go back 2 directories and so forth and so on.
Use "cd" to change directories. Is an example really needed for this...
Proper Apps to Use
For zip file editing, use 7-zip on Windows and Archive Manager (file-roller) on Linux
For editing text files on Windows use Notepad++ or any text editor that has unix line breaks -- do not use default Notepad or Wordpad -- you've been warned. Use what ever you prefer on Linux. I prefer Gedit myself.
Basic Fastboot Command Syntax
fastboot flash "partition" "image" -- flashes partition image where partition is where to write to and image is the path to the image being written.
example -- fastboot flash system /path/to/system.img
fastboot -w -- does a factory reset; to expedite things, "-w" can be added to "fastboot flash system system.img -w"
fastboot continue -- continue with the boot process
fastboot devices -- list devices fastboot recoginzes
fastboot -s "device model number" -- set the device fastboot will write commands to; use "fastboot devices" to find model number
fastboot reboot bootloader -- reboot phone into fastboot mode (or restart fastboot mode while in fastboot); same as "adb reboot bootloader"
fastboot help -- list all of this & more
Command Info
Not all the fastboot commands work for us. Specifically, the "erase" commands. If a wipe command doesn't work, skip it. I'll mark them with a ! at the end if it might fail.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Install Stock Fastboots ICS
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img.ext4
fastboot erase cache !
fastboot -w
fastboot reboot
Install Alternate Radio
Reboot into fastboot
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
NON-HLOS.bin is found inside a fastboot zip.
Easy Kernel Install
Download kernel-flash.zip in the attachments[/URL]
Open the zip
Replace the zips current boot.img and device_tree.bin from the fastboot of your choice
Install the zip with CWM
By default, kernel-flash.zip comes with Mex Retail kernel and devtree
Easy CWM Install
Download recovery-flash.zip in the attachments[/URL]
Install the zip with CWM
Not sure if its SS compatible, but it is CWM compatible (for the lazy Photon Q users).
Obtain root after installing a Stock Firmware
There are two choices for obtaining root after a stock flash. the closed source SuperSu by Chainfire & and the open source Superuser by Koush.
Download SuperSu zip from Chainfire (Closed Source)
Download Superuser from Koush (Open Source)
Download the one of the root zips above.
Reboot into CWM/TWRP -- adb reboot recovery
Locate and flash the zip (see below for an alternative way)
Reboot, that's it. Nice not having to run exploits\hacks\Linux just for root
Install Rom/Zip file with ADB + CWM
CWM has the awesome ability to install zip files without having to manually copy them to the phone first. All's necessary is a PC with working adb.
Reboot into recovery
Select "install zip from sideload"
On PC, type "adb sideload /path/to/zip" and press enter
The zip will now be copied to the phone's cache & install
Once installed, do any requirements you'd normally do like wipe caches, etc
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Unless you're not rooted with an unlocked BL, there's really no reason why it shouldn't work?
Sent from my N4'd Atrix HD
I was rooted before unlocking... shouldn't it still be rooted?
Sent from my MB886 using Tapatalk 2
miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Did you uninstall safestrap?
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
miketravis said:
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
Click to expand...
Click to collapse
Still did not work for me
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
miketravis said:
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
tvd0405 said:
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
Click to expand...
Click to collapse
same here.
I have the same problem. I was able to flash cwm, uninstall the SS recovery, and uninstall the app. The first time I got the dead android symbol. I restored SS via Titanium Backup, reinstalled the SS recovery, and flashed cwm again. I tried rebooting into recovery and was able to get cwm working. As soon I uninstalled SS and rebooted, I got another dead android.
probably because were all on the XT926 if we were to revert back to XT925 then the recovery should work otherwise we will have to tweak the recovery to get it to work properly witht the XT926 software awesome thing is we can now free up the space that SS used for a rom slot however for noobs you might wana stick with SS once you hardbrick without anything to go back too it will be game over for your phone and then you have to con ATT for another
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
htchd2fix said:
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
Click to expand...
Click to collapse
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
skeevy420 said:
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
Click to expand...
Click to collapse
What's MR?
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Markyzz said:
What's MR?
Click to expand...
Click to collapse
Mexican Retail
Install instructions in OP
htchd2fix said:
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Click to expand...
Click to collapse
You won't lose root
And with an unlocked bootloader, all you gotta do is flash an updater zip with the su binary and app for Stock roms that don't have root
I'll link to a root zip in the op once I find one (or just make it; depends on how quick I find it in a search)
thanx again..
ahahahha...what a beautifullll day....
skeevy420 said:
Mexican Retail
Install instructions in OP
Click to expand...
Click to collapse
is there a point to flash a different firmware? is it required by any means?
I had SS and was backed up, I booted up the "stock ROM" and was successful in unlocking the BL and flashing CWM. I made a new backup of the stock ROM and restored it with success in CWM. In the video it show he has MR , but im confused as to why.
Also, I cant seem to get rid of safestrap....how in the hell do you uninstall it???
I feel like a dummy.
I ran fastboot flash boot openrcovery-twrp-2.8.0.1-ghost.img on my unlocked Moto X.
I can boot into TRWP and stock recovery, but not the bootloader or system. I haven't been able to get to anywhere that I can run fastboot to reflash the bootloader, but I'm not an expert.
How can I restore my stock bootloader? (I have the boot.img)
Update 1: I can access adb shell so I'm considering:
dd if=/sdcard/boot.img /dev/block/mmcblk0p33
I know this is the bootloader partition, but I don't want to make things even harder on myself, so I am being cautious.
Update 2: Fixed!
It worked. Triple checked the target partition. The best way to check is :
ls -al /dev/block/platform/msm_sdcc.1/by-name/
Looked at the contents of /dev/block/mmcblk0p33 and compared to twrp image file. Made sure it looked like boot.img would be good to flash straight into the partition. Then ran the dd, said a little prayer and rebooted.
Have you tried "fastboot flash boot boot.img" by using cmd?
Well, first, boot isn't the bootloader, it is the kernel. If you flashed the bootloader with recovery, you couldn't do anything. Next, if you have recovery access and adb access, why not do "adb reboot bootloader"? Or send the stock kernel to your phone in a flashable zip and flash it via recovery? My advice after you get it fixed would be to leave your phone alone, and ideally, flash it to stock. If you don't know how to fix it, and aren't sure what partition does what, that is a recipe for disaster. The partitions have been named the same thing since the Nexus S (possibly earlier), so this is something that is fairly fundamental to Android.
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