Related
I'm having hard time flash custom recovery. I installed ROM Manager, when I tried to go to recovery I got stuck at android logo with EXCLAMATORY POINT. I already followed this instructions http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638 (deleted these files /system/etc/install-recovery.sh and /system/recovery-from-boot.p)
Followed these instructions:
via fastboot
Code:
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
via terminal app
Code:
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)
Click to expand...
Click to collapse
I also installed 4Ext Touch Recovery, but I think it need a wifi to connect to server, but I can't access a wife connection as of now.
What am I missing? I'm about to flash a ROM, my problem is just the recovery.. Anyone can help me with this? :crying:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
demkantor said:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
Click to expand...
Click to collapse
I really dont know what is happening. Still I can't go to recovery. Btw, does locking/unlocking bootloader affects in flashing custom recovery. But I think I already unlock mine, how would I know if unlock or lock my bootloader?
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
demkantor said:
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*BlackRose - Made by Lecabel(dla5244) *
jb-260/10/166
NEXUSONE PVT ENG S-OFF
HBOOT-7.35.5017 (PB9911000)
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
Apr 21 2012, 04:53:16
HBOOT
VOL UP
VOL DOWN
TRACKBALL
FASTBOOT
RECOVERY - when I select this, I will be stuck at android logo with !
REBOOT
POWERDOWN
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
demkantor said:
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Finally.. Thank you so much.. I can now go to custom recovery.. Now I will backup and wipe then flash.. :good::good: Will press THANK button now, maybe a million times.. hehe
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Okay. I will try to read my left time for this day. Thanks a lot..
demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi, I have a follow up question regarding sd partition, I will just raise my question here than making another thread. I have 4GB SD card but I forgot how much ext partition I made before but my total space in my SD card is 3.21GB. I want to partition my sd card again and increase it maybe to 1gb. If I will increase my partition should I flash again my ROM (VJ CM10.1 | Jelly Bean 4.2.2 - v6.0) and execute a2sd command in terminal emulator? or it's okay to partition my sd card without flashing the ROM again?
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
demkantor said:
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I think a2sd is not working in my device. When I tried to install a2sd or reinstall it there was a line written in termenal emulator (/dev/block/mmcblkop2) I think that the reason why I easily having internal memory full, even I already partition my sd card, with 1024 ext partition using 4ext touch recovery. Check my screenshot in titanium backup showing my memory status..
Sent from my Nexus One using xda app-developers app
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
demkantor said:
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Im using VJ CM10.1 | JB 4.2.2 V 6.0. How to move data to ext partition? I will post screenshot in my internal storage too.
Sent from my Nexus One using xda app-developers app
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
demkantor said:
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
Click to expand...
Click to collapse
Thanks. Btw what rom are you using?
Sent from my Nexus One using xda app-developers app
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
demkantor said:
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Thanks, Btw, what if I wanted to change my ROM, what procedure should I follow? Should I go back to Stock ROM before flashing a new ROM?
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
demkantor said:
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply. So, you're saying that I should partition my system first and flash recovery just like what you taught me in our previous posts? Just to be sure and making all things clear to my self.
I have this big problem:
I have a N7000 that afrer an accident have a bricked screen and touch. Complete blank screen and non working touchscreen.
The main board still works.
I have to recover the contacts, not syncronized with google.
I am able to boot but ADB is switched off and I have no way to navigate in the phone to turn it on because non working touchscreen.
I am able to bootup in recovery mode but I have it stock.
I am able to bootup in Odin mode but I do not know wich recovery to flash in order to have an already switched on ADB.
Do you have any suggestion?
With adb on I can resolve, but I do not know how to turn it on without screen and touchscreen.
Kind regards.
Philz kernel has odin flashable files and has adb connectivity in recovery.
Sent from my GT-I9500 using xda premium
WOW!
nokiamodeln91 said:
Philz kernel has odin flashable files and has adb connectivity in recovery.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Great! I did it. With Philz kernel I have downloaded contacts2.db to my PC. That file and also all /data dir.!
Now I have problems in extracting contacts with sqlite3.exe. Seems that every phone have a slightly different database.
I want to extract to cvs google compatibile.
Seems so difficult because I have not database and/or scripting skills.
In any case the big problem is solved. I have recovered the database!
Thank you nokiamodeln91
Why not make a nandroid backup. I don't remember but I think I have used a tool to make nandroid using PC. Can't find it may be you will have better luck.
Or may be you can look for philz recovery steps for nandroid backup and blindly follow it using the vol and power buttons. Then pull the nandroid to PC.
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
Why not make a nandroid backup. I don't remember but I think I have used a tool to make nandroid using PC. Can't find it may be you will have better luck.
Or may be you can look for philz recovery steps for nandroid backup and blindly follow it using the vol and power buttons. Then pull the nandroid to PC.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
I do not need a nandroid backup, since I've already pulled the whole data partition directly by ADB shell.
I was able to do this by falshing Philz Kernel and booting up Philz Recovery, as suggested.
Now I have in my hands the file contacts2.db wich is a sql database. I can access to it with sqlite3.exe but I have no skills to create a proper query to extract the numbers, names, emails and so on in a format ready to be imported.
The standard query I've used is
Code:
sqlite3.exe contacts2.db
sqlite> .bail ON
sqlite> .headers ON
sqlite> .mode csv
sqlite> .output my_contacts_db.csv
sqlite> SELECT _id,package_id,mimetype_id,raw_contact_id,is_primary,is_super_primary,data_version,data1,data2,data3 FROM data;
sqlite> .output stdout
sqlite> .quit
and the results are in two lines and looks like that:
5406,,5,2335,0,0,0,[i've removed the number here for privacy].......,2,
5407,,6,2335,0,0,0,"federico agronomo",federico,agronomo
and Google compatible importing cvs looks like:
Agronomo F Rubegni,Agronomo,F,Rubegni,,,,,,,,,,,,,,,,,,,,,,,* My Contacts,,,Mobile,[i've removed the number here for privacy],,,,,,,,,,,,,
I would like to avoid to manually copy and paste something like 1000 contacts
so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Beta 1 zip is bad i am just goinmg to make a windows bat file that will do it lol
instructions.
if you want to keep your rom and data you will need and external sd card that is big nough to hold a backup of system and data.
okay i made a bat script that **SHOULD** work i havent been able to test one part of it so if youd like to test ill attach the zip to the bottom of the post
DISCLAIMER
i am not resposible if you brick your device doing this i can only confirm it will work on D415 if your onj a variant and want to know if itll work PM me the output put either from adb or a terminal emulator ls -l /dev/block/platform/msm_sdcc.1/by-num
now there are instructions on screen to follow so make sure you fread them or you could screw something uyp lol
demonslayer12349 said:
so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Click to expand...
Click to collapse
so how do u increased it.....???
using sd card ext partitions or shrinking of other partitions..???
kprsnt said:
so how do u increased it.....???
using sd card ext partitions or shrinking of other partitions..???
Click to expand...
Click to collapse
shrinking of others. my final shrinking puts the total at 5.65GB
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
sorabh.v6 said:
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
Update..???
This works (because i tried this kind of method in p500)..
But I didnt tested it because my device is new ..
If u wanna try PM him
sorabh.v6 said:
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
just posted the first beta
I'm going to try this then give feed back
Sent from my LG-D410 using Tapatalk
---------- Post added at 05:26 AM ---------- Previous post was at 05:25 AM ----------
Just curious if this will work with stock rom
Sent from my LG-D410 using Tapatalk
I got an error flashing the .zip on TWRP, something related to binary. My model is the 410hn. Thanks for the support to L90.
Using cwm, got and error 6 during flash. D410. Stock ROM
Sent from my LG-D410 using Tapatalk
goldfinv said:
Using cwm, got and error 6 during flash. D410. Stock ROM
Sent from my LG-D410 using Tapatalk
Click to expand...
Click to collapse
InfinitusDesigner said:
I got an error flashing the .zip on TWRP, something related to binary. My model is the 410hn. Thanks for the support to L90.
Click to expand...
Click to collapse
working on a windows script right now to do it or to restore it to defazult
demonslayer12349 said:
so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Beta 1 zip is bad i am just goinmg to make a windows bat file that will do it lol
instructions.
if you want to keep your rom and data you will need and external sd card that is big nough to hold a backup of system and data.
okay i made a bat script that **SHOULD** work i havent been able to test one part of it so if youd like to test ill attach the zip to the bottom of the post
DISCLAIMER
i am not resposible if you brick your device doing this i can only confirm it will work on D415 if your onj a variant and want to know if itll work PM me the output put either from adb or a terminal emulator ls -l /dev/block/platform/msm_sdcc.1/by-num
now there are instructions on screen to follow so make sure you fread them or you could screw something uyp lol
Click to expand...
Click to collapse
I tried using this and it at first didn't find adb. I moved the .bat into the tools folder, and it ran and booted to recovery. When it booted to recovery it sat there saying "waiting for device to enter recovery"
Sent from my LG-D415 using Tapatalk
blondgod said:
I tried using this and it at first didn't find adb. I moved the .bat into the tools folder, and it ran and booted to recovery. When it booted to recovery it sat there saying "waiting for device to enter recovery"
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
Okay. I need to refresh my bat scripting obviously XD and do you have twro installed? I should have mentioned that and if nothing else just unplug plug back in.
demonslayer12349 said:
Okay. I need to refresh my bat scripting obviously XD and do you have twro installed? I should have mentioned that and if nothing else just unplug plug back in.
Click to expand...
Click to collapse
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
blondgod said:
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
Click to expand...
Click to collapse
I've tried making a flashable zip but with no success. Right now twrp is the only way this works
blondgod said:
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
Click to expand...
Click to collapse
Sorry should have mentioned you needed twrp. I've tried flashable zips but can't seem to get a working one
demonslayer12349 said:
Sorry should have mentioned you needed twrp. I've tried flashable zips but can't seem to get a working one
Click to expand...
Click to collapse
Its no problem at all. I've got enough space for now. Thanks for the work!
Sent from my LG-D415 using Tapatalk
blondgod said:
Its no problem at all. I've got enough space for now. Thanks for the work!
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
No problem.
What about restoring original partition scheme? Is this possible via kdz tools (or what's called)? Is kdz reparitioning device?
Or it has to be done manually (then we have repart making it EXACTLY the same, every single byte?
@demonslayer12349, your script is a little strange.
Code:
@adb shell su -c "mount -o remopunt rw, /"
It should be:
Code:
@adb shell su -c "mount -o remount rw, /"
isn't it?
Then another thing. You delete 4 partitions and create only three.
For D410 partition 31 is "eksst". It is 0.5mb only. What is the reason to delete it?
Or the script is device-specific?
judas1977 said:
What about restoring original partition scheme? Is this possible via kdz tools (or what's called)? Is kdz reparitioning device?
Or it has to be done manually (then we have repart making it EXACTLY the same, every single byte?
Click to expand...
Click to collapse
As I know LG software doesn't recreate partitions, so you have to do it manually.
@up
Thx for the answer. Spoony bards they are
Hey guys, today I'm going to tell you how to backup & restore few things of your phone without using a pc. This guide is divided into two parts: 1st post contains a guide to backup things & 2nd post contains two methods two restore the backup. So let's get started without wasting any time...
Things you gonna need:
1) Busybox installed (Stericson is recommended)
3) A SD-Card inserted to your phone with some free space to backup things
2) Any terminal emulator
3) Patience & some common sense (not HTC Sense )
First I'll say you how to backup things & later I'll say how to restore them...
How To Backup:
• Boot.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p7 of=/sdcard/backups/boot.img
• Cache.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p15 of=/sdcard/backups/cache.img
• Logo.bin :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p11 of=/sdcard/backups/logo.bin
• Nvram.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p2 of=/sdcard/backups/nvram.img
• Recovery.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p8 of=/sdcard/backups/recovery.img
• System.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p14 of=/sdcard/backups/system.img
• Userdata.img :
In terminal emulator type the following:
dd if=/dev/block/mmcblk0p16 of=/sdcard/backups/userdata.img
Click to expand...
Click to collapse
If this post helped you then please hit thanks, & feel free to ask any doubts or questions...
Restoring in 2 methods
In this second post I'll tell you how to restore the backups in two different methods...
How To Restore in 1st Method:
• Boot.img* :
In terminal emulator type the following:
dd if=/sdcard/backups/boot.img of=/dev/block/mmcblk0p7
• Cache.img* :
In terminal emulator type the following:
dd if=/sdcard/backups/cache.img of=/dev/block/mmcblk0p15
• Logo.bin :
In terminal emulator type the following:
dd if=/sdcard/backups/logo.bin of=/dev/block/mmcblk0p11
• Nvram.img :
In terminal emulator type the following:
dd if=/sdcard/backups/nvram.img of=/dev/block/mmcblk0p2
• Recovery.img :
In terminal emulator type the following:
dd if=/sdcard/backups/recovery.img of=/dev/block/mmcblk0p8
• System.img* :
In terminal emulator type the following:
dd if=/sdcard/backups/system.img of=/dev/block/mmcblk0p14
• Userdata.img* :
In terminal emulator type the following:
dd if=/sdcard/backups/userdata.img of=/dev/block/mmcblk0p16
(* = Not recommended to restore while your phone is on, unless you know what you are doing)
Click to expand...
Click to collapse
How To Restore in 2nd Method(Recommended):
1) Download the attachment below, named 'Restore.zip'
2) Extract the contents of the zip somewhere on your SD card.
3) Replace the dummy files,which you find when you extract the zip, with the backups you made above.
4) Don't forget to delete the dummy files which you don't need to restore.
5) Again compress the contents.
6) Boot to recovery & flash the zip which you just compressed with the backups.
7) Your backup will be restored, enjoy... :good:
Click to expand...
Click to collapse
F.A.Qs
Frequently Asked Questions:
Q: Where does the backup gets stored?
A: It's in sdcard/backups/
Q: While backuping/restoring in terminal emulator I get Access Denied or something message like that.
A: Make sure your phone is rooted & don't forget to type "su" in terminal emulator before following any of the steps above.
Q: Why is second method of restoring recommended?
A: Because it restores the backup in recovery, so that you don't brick up your device while restoring system.img or few other backups while phone is on.
Q: Then why did you posted the first method?
A: First method of restoring is only for advanced users, who knows what they are doing.
Q: Can I use this method of backuping in my non-mtk device?
A: No, you can't, this guide is strictly only for MTK devices.
Q: I want to contribute/donate to you, where can I?
A: I'm still 14,& I don't need any money. Instead you can hit thanks. And if you liked my work that's enough for me.
Q: I have some "xxxx" question/doubt.
A: Feel free to comment below.
there is no way to backup without root or unlock the bootloader? even if it requires a pc its ok
austinpinto said:
there is no way to backup without root or unlock the bootloader? even if it requires a pc its ok
Click to expand...
Click to collapse
I'll make a new guide on that very soon, maybe this coming Sunday...
Taking a nandroid will cover all this right?
I am on cwm recovery, cm11-3. My sdcard path is '/storage/sdcard0' in stead of '/sdcard'. Replaced the correct path and took backup. Thanks for the nice post.
Sent from my A1 using XDA Free mobile app
miscos said:
I am on cwm recovery, cm11-3. My sdcard path is '/storage/sdcard0' in stead of '/sdcard'. Replaced the correct path and took backup. Thanks for the nice post.
Sent from my A1 using XDA Free mobile app
Click to expand...
Click to collapse
Welcome my friend...
akhil1999 said:
Taking a nandroid will cover all this right?
Click to expand...
Click to collapse
Yeah, it'll...
can you please make a guide to backup non rooted devices with bootloader locked? even if it requires a pc its ok
Download a custom recovery.
Boot into fastboot.
Code:
fastboot boot recovery.img
Then backup!
Sent from my A1 using XDA Free mobile app
akhil1999 said:
Download a custom recovery.
Boot into fastboot.
Code:
fastboot boot recovery.img
Then backup!
Sent from my A1 using XDA Free mobile app
Click to expand...
Click to collapse
i did this.
the backup finished properly.
i got 2 .img files 1 md5 file and some .tar files some .tar.a files and 1.tar.b file.
now i tried opening .tar file with 7zip i get error no trailing records 0 filled records found then i tried opening .tar.a files the files open properly but when i go to extract something it shows error unable to open output file when i open .tar.b files i get 7zip cannot open.tar.b as archive.
can some1 tell me what is the problem?
i did using touch recovery is this the best recovery to do backup? if no please give link for some other recovery
Why are you opening it?
If you have to restore then boot into recovery again and restore.
If you want apps, etc. there's an app that can extract apps from a nandroid
Sent from my A1 using XDA Free mobile app
akhil1999 said:
Why are you opening it?
If you have to restore then boot into recovery again and restore.
If you want apps, etc. there's an app that can extract apps from a nandroid
Sent from my A1 using XDA Free mobile app
Click to expand...
Click to collapse
Just to view the contents of the tar files I tried opening
Sent from my Spice Mi-498 using XDA Free mobile app
---------- Post added at 10:57 AM ---------- Previous post was at 10:50 AM ----------
Can u give link for that app that extract apps from the tar
Sent from my Spice Mi-498 using XDA Free mobile app
Its called "Nandroid Manager * Root"
Sent from my A1 using XDA Free mobile app
Great
Devam03 said:
Great
Click to expand...
Click to collapse
Thanks & if you liked please don't forget to hit thanks...
EDIT: It works with the 8GB versions of Android One.
I implemented this method using built in twrp's terminal. I did it without root my device.
nothinkinc said:
I implemented this method using built in twrp's terminal. I did it without root my device.
Click to expand...
Click to collapse
how did u do.
i want a way of backuping which i can later restore using fastboot
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