Related
I know this tutorial is everywhere on this forum. But with HTC Legend, it's a little different.
Read the tutorial here : http://forum.xda-developers.com/showthread.php?t=695411
Now I'll make it simple, just do this :
Your Legend must be rooted!
Step 1 : Download host file from the attach at the end of the post and unzip it to get the hosts file
Step 2 : Copy hosts to ADB folder (in my case : C:/android/tools) download Android SDK here
Step 3 : reboot your Legend to recovery mode (Install Rom manager on Market, Flash recovery, than reboot into Recovery mode)
Step 4 : Open Command window (Start menu > Run > cmd (windows xp) / Start menu > cmd (windows 7))
Step 5 : point to your adb folder
In my case :
cd\
C:\cd android\tools
Click to expand...
Click to collapse
Step 6 :
C:\android\tools\adb shell mount /system (Enter)
C:\android\tools\adb push hosts /system/etc/hosts (Enter)
C:\android\tools\adb reboot (Enter)
Click to expand...
Click to collapse
Step 7 : Done.
Note : This hosts file was updated long time ago, so it might not work with new apps. But it will disable most of the apps.
Very nice!
Does this work? It did not work on my Legend. I just cant get into shell when in recovery.
Precisely, "adb shell" gives an error!
"an" error!
BTW the file hosts works for me, and not a single ad is shown on my cell
Isn't our recovery just pressing volume down + power then go to recovery and wait for the "!" ? cause if I try adb shell then, it tells me:
Code:
-exec '/system/bin/sh' failed: no such file or directory (2)-
am I in the wrong recovery?
it is saying I'm in recovery when asking for the "adb devices" command
EDIT: found what I was doing wrong, didn't know you needed to run the recovery-windows.bat file first
EDIT 2: still having adds (in astro)
Does this thing removes adds out of free aplications, that usually have them?
I updated the instruction, I hope it's easier for you to follow every steps.
Does this thing removes adds out of free aplications, that usually have them?
Click to expand...
Click to collapse
It blocks the apps from connecting to the ad server. And yes, it does remove every single ad from free applications.
@Jonas : please follow the new instruction.
If you would use this MOD, you would be able to write to system partition thus installing AdFree from market would be possible.
I get..
Code:
C:\Users\parker\Downloads\android-sdk_r06-windows\android-sdk-windows\tools>adb shell mount /system
- exec '/system/bin/sh' failed: No such file or directory (2) -
NVM read above posts; ran Windows-recovery.bat - pushes the host.txt to the phone, now rebooting to see if it removes ads.
edit II: removes ads out of Advanced Task Killer but it keeps trying to load the ads so would that mean that its still pinging a server because that could use up a lot of data couldn't it if it keeps running?
parker09 said:
...so would that mean that its still pinging a server because that could use up a lot of data couldn't it if it keeps running?
Click to expand...
Click to collapse
Nope. Did you even look what's inside of that hosts file? There are adresses of ad servers pointing to localhost (that's your phone itself)...
BlaY0 said:
Nope. Did you even look what's inside of that hosts file? There are adresses of ad servers pointing to localhost (that's your phone itself)...
Click to expand...
Click to collapse
Oh okay I see now, thanks for that.
awesome thanks
Updated a really big hosts file (blocks almost every ads)
when i press C:\android\tools\adb push hosts.txt /system/etc/hosts (Enter)
it tells me theres no hosts.txt
the file i downloaded is just host there is no .txt
so what do i do?
how would i know whether i have succeeded or not?
This is what i did:
C:\>cd\androidsdk\tools
C:\AndroidSDK\tools>adb shell mount /system
C:\AndroidSDK\tools>adb push hosts.txt /system/etc/hosts
cannot stat 'hosts.txt': No such file or directory
C:\AndroidSDK\tools>adb push hosts /system/etc/hosts
1246 KB/s (0 bytes in 1236506.000s)
C:\AndroidSDK\tools>adb reboot
"host.txt" did not work so i tried just "host"
is it correct?
knnhzx said:
This is what i did:
C:\>cd\androidsdk\tools
C:\AndroidSDK\tools>adb shell mount /system
C:\AndroidSDK\tools>adb push hosts.txt /system/etc/hosts
cannot stat 'hosts.txt': No such file or directory
C:\AndroidSDK\tools>adb push hosts /system/etc/hosts
1246 KB/s (0 bytes in 1236506.000s)
C:\AndroidSDK\tools>adb reboot
"host.txt" did not work so i tried just "host"
is it correct?
Click to expand...
Click to collapse
Yes, change hosts.txt to hosts. When I wrote this tutorial, the file was hosts.txt but then I changed a better one (block more ads) : hosts
how would i know whether i have succeeded or not?
Click to expand...
Click to collapse
Open the app with ads and see the difference...like Angry Birds or Advanced Task Manager,.etc...
The only working method is in my signature link. Replace mtdblock4 with mtdblock3.
chinmoykanjilal said:
The only working method is in my signature link. Replace mtdblock4 with mtdblock3.
Click to expand...
Click to collapse
This tutorial was being something about changing "mtdblock4" to "mtdblock3". But then I figured out we don't need that complicated command.
Just do
Code:
adb shell mount /system
is enough for our legend.
What's the benefit in having ads removed besides them not showing up and less net traffic (even if the traffic is not so high due to this)? The apps still have that space for ads even if they're not showing up, plus I got frequent restarts of the application. After one day trying this, I've deleted the hosts file, at least now the apps ARE working. And finally if one doesn't like ads there's allways the option for buying/donate...that is also supporting development
Hello,
I used the condi's flasher to get jelly bean a long time ago.
Now I wanted to have the last update from sony (R3 it seems) however the tablet says that there is no new updates (which is false). I have noticed that for my version number (or something like that, last info on the tablet ) I have "UNKNOWN (FR)".
Can you help me to update it?
Thanks
griotte said:
Hello,
I used the condi's flasher to get jelly bean a long time ago.
Now I wanted to have the last update from sony (R3 it seems) however the tablet says that there is no new updates (which is false). I have noticed that for my version number (or something like that, last info on the tablet ) I have "UNKNOWN (FR)".
Can you help me to update it?
Thanks
Click to expand...
Click to collapse
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"
Thanks for your help bg_man, I will try and update the post is everything is OK.
:good:
bg_man said:
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"
Click to expand...
Click to collapse
Hi,
In fact I have a strange situation :
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
I don't have this symlink. How can I create it?
Thanks
bg_man said:
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"
Click to expand...
Click to collapse
griotte said:
Hi,
In fact I have a strange situation :
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
I don't have this symlink. How can I create it?
Thanks
Click to expand...
Click to collapse
You have a directory or a symlink to other folder instead?
Delete it and create symlink to right folder. "FI" stands for Finland. Put a correct one for your location.
Symlinks are remover with "rm", dir with "rmdir". I'd rename if it's a directory, rather remove it.
bg_man said:
You have a directory or a symlink to other folder instead?
Delete it and create symlink to right folder. "FI" stands for Finland. Put a correct one for your location.
Symlinks are remover with "rm", dir with "rmdir". I'd rename if it's a directory, rather remove it.
Click to expand...
Click to collapse
Yes that the point. The symlink is on the OTHER partition.
Thank you for your help, can you help me for the instructions? Especially the symlink is in read-only mode.
griotte said:
Yes that the point. The symlink is on the OTHER partition.
Thank you for your help, can you help me for the instructions? Especially the symlink is in read-only mode.
Click to expand...
Click to collapse
You have to mount system R/W:
/data/local/tmp/busybox mount -o rw,remount /system
Hi,
i have the same problem than Griotte.
Isn't it possible to flash directly the last firmware (downloaded on the SD card ) by using the condy "all in one" ?
In fact i just want to update because i have the Sony sound dock SGP-SPK1, everything work except that the sound don't pass from the tablet to the dock... great Sony !
So i suppose that maybe if i update the tablet, the dock will work...
Sorry for my English and thanks for your help
Note: I'm just sharing the work of the XDA member.This guide was tested on Galaxy Y GT-S5360.Here's a little introduction:
scandiun said:
INFORMATION
This guide is intended to make a full backup of your android phone (the entire memory block with all partitions) or a single partition (including sdcards, etc) directly to your computer, in either
Block level (with dd): for single partitions or whole memory block (all partitions in one piece). The backup always has the same size which is the size of the partition.
File level (with tar): only for individual partitions. This only includes files and folders, so occupies much less space, depending on how much filled is the partition.
It can be done with the phone powered on or from ClockWorkMod Recovery (from both ADB works, while in Fastboot doesn't so won't apply). Unless specified the commands meant to be used from Windows. For Linux and Unix is similar.
REQUIREMENTS
Rooted Android Phone
Busybox installed on your phone
If you are using Linux / OS X you have native tools, for Windows download Cygwin, and install with it netcat, pv and util-linux. Get them from Cygwin's setup.exe
ADB installed.
Make sure adb.exe is in your windows' path. See here and here, or use Path Manager.
Android phone with USB Debugging enabled, and the proper drivers installed on Windows so the phone is recognized. Typing 'adb devices' on a terminal should show your device.
PARTITION IDENTIFICATION
You now have to identify the partition or block device that you want to backup. For a single partition you can use either tar or dd, while for the entire memory block you can only use dd.
For example, on Galaxy Nexus you have the list of partitions here and for Galaxy S2 here.
Usually on android, the entire block containing all partitions is located at /dev/block/mmcblk0 and the data partitions is a subpartition of it. You can push parted with GPT support to your device and see all information on a partition or block.
Whole phone memory -> /dev/block/mmcblk0 (may vary, in some phones this is the sdcard)
Subpartitions -> depends on each device. Usually at /dev/block/platform/dw_mmc/by-name/ there are listed by name linking to the real device.
Back up of the whole memory block (via adb)
Connect the phone in ADB mode and unlock the screen.
Open one Cygwin Terminal and enter (replace mmcblk0 if needed):
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
You will see the cursor blinking at the left. Now the phone is waiting to send the block over the network.
Open another Cygwin terminal and type:
Code:
adb forward tcp:5555 tcp:5555
cd /path/to/store/the/backup
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
You will see how the image size is growing until it finishes. Now you have the whole phone backed up in raw format. You can see the contents of the GPT partition with gptfdisk tool, available for windows, linux and such. See official website and sourceforge to get it. You can do it the same from ClockWorkMod Recovery but you have to mount first the /system partition since the busybox included with clockworkmod does not come with netcat and you have to use the one from the system partition.
With further linux tools you could edit or extract single partitions from the whole block.
You can use adb via wifi as well with applications like WiFi ADB.
Back up of the whole memory block (via wifi)
Original post: [Q] Nandroid directly to computer w/o sdcard
We need to install a FTP server on the computer or the other device, configure a user with a password if we want to, and set some port. It uses by default 21 but this example uses 40. We must set a home dir for the user with write permissions.
Usually is a good idea to put myfifo in /cache not in /data because we may overwrite sensitive data in case we want to use that raw image for data recovery.
Open one Cygwin terminal
Code:
adb shell
su
mkfifo /cache/myfifo
ftpput -v -u user -p pass -P 40 COMPUTER_IP block.raw /cache/myfifo
Open another Cygwin terminal
Code:
adb shell
su
dd if=/dev/block/mmcblk0p12 of=/cache/myfifo
Tips:
- Fifos only can be made on linux native filesystems, for example on a FAT partition is not possible.
- Reading from a partition does not modify it.
Now check on Filezilla Server the speed
Back up of the whole memory block (USB tethering, Wifi tethering)
To use tethering you have to disconnect the computer from all networks and connect it only to the phone with the type of connection you want.
Once you connect it, you can view the IP of the computer and the IP of the phone from connection properties. The ip is the computer ip and the gateway is the phone's ip.
Wifi Tethering: Computer Phone Internet
USB Tethering:
Computer Phone Internet
Conputer Phone Internet
This is exactly the same as via wifi, except that the transfer speed is much higher because the computer and the phone are directly connected, instead of using a router as a gateway. In this case, the gateway is the phone. USB tethering has the highest transfer rate.
Back up of a single partition (raw = every bit of the partition)
It is exactly the same as the the previous but replacing mmcblk0 by the corresponding partition. You can use in this particular case several software to read the partition from windows, depending on partition filesystem: DiskInternals Linux Reader, Ext2Read, Ext2 File System Driver for Windows, Ext4Explore, plugin for Total Commander and ImDisk Virtual Disk Driver. You can also use recovery software on individual partitions like Recuva in combination with VHD Tool or command line tools included with operating systems.
Back up of a single partition (tar = only files and folders)
In this case, you need the partition mounted. To see the list of mounted partitions type on Cygwin Terminal
Code:
adb shell mount
Now you need to know where is mounted the partition you want to backup, for example the firmware is mounted on /system, which is the ROM.
In this case you will have to open three terminals, because of android limitations:
Open one Cygwin terminal and create a fifo, in /cache, for example, and redirect the tar there
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/xbin/busybox mkfifo /cache/myfifo
/system/xbin/busybox tar -cvf /cache/myfifo /system
We have to do it this way because redirecting the tar to stdout (with - ) is broken on android and will corrupt the tar file.
Open a second Cygwin terminal and type:
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox cat /cache/myfifo
Open a third Cygwin terminal and type:
Code:
adb forward tcp:5555 tcp:5555
cd /path/to/store/the/backup
nc 127.0.0.1 5555 | pv -i 0.5 > system.tar
You can browse the tar file with Winrar, Total Commander, PeaZip and almost any compression tool. Note that you shouldn't extract files or edit it since the tar format saves the permission and owner data for each file, that is lost when extracted to FAT / NTFS partitions and you will mess things when restoring.
LINKS
[GUIDE] Internal Memory Data Recovery - Yes We Can!
How to Create and Attach a Virtual Hard Disk in Windows 7
[Guide] Types of Android backups
Click to expand...
Click to collapse
Original Thread : http://forum.xda-developers.com/showthread.php?t=1818321
And here is the guide to make nandroid backup through terminal app in android with switching off the phone in sdcard!!!
http://forum.xda-developers.com/showthread.php?t=1620255
Hello everyone this is going to be my second tutorial on XDA.
After rooting the coolpad dazen 1 lot of peoples devices were stuck in a bootloop when updated through OTAs and then Mr. Jaswant Singh came up with a solution which was to flash system.img file via fastboot to the bricked dazen1. But because there are not a lot of user of dazen1 that's why the link he posted to the system.img tends to get expire after sometime.
So, Here I am posting the method to create system.img file without the use of PC. Although I have posted this tut for dazen1 but it should work for other devices too.Let's move on to the procedure.
REQUIREMENTS
root
terminal emulator
busybox installed
B1 Archiver or any other software installed capable of decompressing .tar files
about 5 GB space in memory card
-Those who system folder shall move it to the root of external sdcard and follow step 3
-Those who have system.tar shall first extract it so that a system folder gets created which contain app, bin, etc, framework... etcetera and follow step 3
-Others follow all three STEPS
procedure
STEP-1
open terminal emulator and type following commands
Code:
su
tar -c /system/*>> /storage/sdcard1/system.tar
above will create a system.tar in external SD card
STEP-2
Now open B1 archiver and go to /storage/sdcard1/
there you will system.tar select it
choose "extract here"
when extraction gets completed then delete the system.tar file to free up the space
STEP-3
now again open terminal emulator and type following
Code:
make_ext4fs -s -l 2048M -a system /storage/sdcard1/system.img /storage/sdcard1/system
above will create the system. img (flashable via fastboot) in the external SD card
Now you can delete the system folder from the external SD card to free up the space
congrats
Now if your device ever gets in trouble use this system. img
Important threads for dazen1
[ROOT PROCEDURE] http://forum.xda-developers.com/android/software-hacking/dazen-1-proper-rootsolution-t3215902
[UNBRICK]Reviving Yulong Coolpad Dazen 1 http://forum.xda-developers.com/android/help/reviving-coolpad-dazen-1-8297l-i00-t3236337
[Discussion/Q&A kind of thread] http://forum.xda-developers.com/chef-central/android/root-extracting-boot-img-recovery-img-t3170809
good job . really helpful for the new users
Sent from my Coolpad 8297L-I00 using XDA Premium 4 mobile app
I need boot IMG can anyone provide me link
@ paramparmatma
Here you go
Download it from here http://www.multiup.org/en/mirror/04a6c6d222b361b777ad69d2da6cbd1f/boot.img.zip
or
here http://uppit.com/9j9di8qyfgoa
any way to make data & cache.img too?
myballgotkicked said:
any way to make data & cache.img too?
Click to expand...
Click to collapse
Yes it's possible but why would you want to make img of Cache and data
if you only want it for backup purpose you can use Titanium backup
BTW
you can use
Code:
su
dd if=/dev/block/mmcblk0p27 of=/storage/sdcard1/cache.img
To get the cache.img
Code:
dd if=/dev/block/mmcblk0p28 of=/storage/sdcard1/recovery.img
To get recovery.img
Code:
su
dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/boot.img
To get the boot.img
Code:
su
tar -c /data/*>> /storage/sdcard1/data.tar
for creating .tar of data partition and then follow the above posted procedure replacing word "system" with "data" for making a data.img, BTW depending on the number of installed apps your data.img may be too big and as far as I know , I think you can't flash images larger than 2gb and therefore you may not be able to flash boot.img via fastboot
Frank782 said:
Hello everyone this is going to be my second tutorial on XDA.
After rooting the coolpad dazen 1 lot of peoples devices were stuck in a bootloop when updated through OTAs and then Mr. Jaswant Singh came up with a solution which was to flash system.img file via fastboot to the bricked dazen1. But because there are not a lot of user of dazen1 that's why the link he posted to the system.img tends to get expire after sometime.
So, Here I am posting the method to create system.img file without the use of PC. Although I have posted this tut for dazen1 but it should work for other devices too.Let's move on to the procedure.
REQUIREMENTS
root
terminal emulator
busybox installed
B1 Archiver or any other software installed capable of decompressing .tar files
about 5 GB space in memory card
-Those who system folder shall move it to the root of external sdcard and follow step 3
-Those who have system.tar shall first extract it so that a system folder gets created which contain app, bin, etc, framework... etcetera and follow step 3
-Others follow all three STEPS
procedure
STEP-1
open terminal emulator and type following commands
Code:
su
tar -c /system/*>> /storage/sdcard1/system.tar
above will create a system.tar in external SD card
STEP-2
Now open B1 archiver and go to /storage/sdcard1/
there you will system.tar select it
choose "extract here"
when extraction gets completed then delete the system.tar file to free up the space
STEP-3
now again open terminal emulator and type following
Code:
make_ext4fs -s -l 2048M -a system /storage/sdcard1/system.img /storage/sdcard1/system
above will create the system. img (flashable via fastboot) in the external SD card
Now you can delete the system folder from the external SD card to free up the space
congrats
Now if your device ever gets in trouble use this system. img
Important threads for dazen1
[ROOT PROCEDURE] http://forum.xda-developers.com/android/software-hacking/dazen-1-proper-rootsolution-t3215902
[UNBRICK]Reviving Yulong Coolpad Dazen 1 http://forum.xda-developers.com/android/help/reviving-coolpad-dazen-1-8297l-i00-t3236337
[Discussion/Q&A kind of thread] http://forum.xda-developers.com/chef-central/android/root-extracting-boot-img-recovery-img-t3170809
Click to expand...
Click to collapse
I have coolpad dazen 1. But it is dead now (stucked at logo). Not starting evn not getting in bootloader not in fastboot too. But i installed emmc on my memory card with the help of which i am able to get in fastboot mode. But when i flash cpb file using ygdp tool then it stops at 11% of cell1 by giving error --
"12:52:11 CELL0: Downloading the 1 packet of system
12:52:33 CELL0: Fail to execute flash command!
12:52:33 CELL0: Res:flash write failure
12:52:33 CELL0: Fail to transmit system file data !
12:52:33 CELL0: Lock bootloader ...
12:52:33 CELL0: Download faile,please try again!!
12:52:33 CELL0: Total download time elapsed: 0 min : 23 sec
12:52:33 CELL0: Downloading all files: Failed!"
And when i try to flash recovery and system using adb then it says while writing Failed (remote: flash write failure).
Please help me. What should I do.
Disclosure: I'm intentionally editing build.prop to feel out the limits one can tweak it, I'm fully aware I can completely brick these devices doing this.
With that said, ive encountered an issue that replicates on different devices and have no clue as to how or why.
Target Devices:
Samsung S21 (USA-TMB)
Samsung S22 (USA-XAA)
LG V20 (USA-XAA)
LG Velvet (USA-TMB (MTK))
Google Pixel6 Pro
All devices above have been rooted and i have patched bootloader and VBmeta &/or Preloader.
On ALL of the above devices, when i edit the build prop, it simply edits into a blank build.prop. This was replicated using Root Explorer Pro, Rom ToolBox Pro & SmartPack Kernel Manager (F-Droid)
I also tried making a backup before edit, then restore. The system still Bricks upon reboot.
Even if i don't edit the build prop directly, but rather replace it, even with an identical one. The system refuses to read it next boot.
On Most of the listed devices - System is A/B - Also worth noting is the build.prop in /system references importing the build.prop and default.props from /Vendor and /Product. Could that have anything to do with it?
Trouble-Shooting steps taken:
Ensured /System is mounted
Tried Different methods for editing build.prop "on-device"
pull to pc, edit, push back.
Google - XDA Search (duh)
is this DM-Verity? TF am I missing?
So if I understand correctly:
You mount -o rw,remount /system
You adb pull some-text-file
You edit some-text-file
You adb push some-text-file
Did you subsequently adb pull some-text-file to make sure that it was actually changed?
This isn't a super (dynamic partition) with /system /vendor /product all together, is it?
Do:
Code:
dd if=/dev/block/by-name/system of=/sdcard/check skip=big-number
Big number = count of sectors in system partition - 8 // for eMMC
Big number = count of sectors in system partition - 1 // for UFS
You should end up with a file exactly 4096 bytes. If you don't play with the numbers.
Hexedit that file, does it start with fe cf ec fe? Then it has FEC.
Renate said:
So if I understand correctly:
You mount -o rw,remount /system
You adb pull some-text-file
You edit some-text-file
You adb push some-text-file
Did you subsequently adb pull some-text-file to make sure that it was actually changed?
This isn't a super (dynamic partition) with /system /vendor /product all together, is it?
Do:
Code:
dd if=/dev/block/by-name/system of=/sdcard/check skip=big-number
Big number = count of sectors in system partition - 8 // for eMMC
Big number = count of sectors in system partition - 1 // for UFS
You should end up with a file exactly 4096 bytes. If you don't play with the numbers.
Hexedit that file, does it start with fe cf ec fe? Then it has FEC.
Click to expand...
Click to collapse
Super - yes. is this same as system as root? (Sorry if it's an obvious question, I'm learning)
Yes , correct, i ever tried changing Owner and permissions (chmod 777)
Thats the weird part, when i did pull the file from the device it actually came out the other end on my pc intact with all the props - i then proceeded back to device and checked the file in /system and it was blank, as well as the build.bak.
At first thought it was the file explorer (Root Explorer Pro) but when tried manually, same result.
Don't know if its relevant or not to the issue, but i WAS able to use setprop on some props, but only select ones, and I'm not able to figure out the bias as to which one I can or can't.
Persisitent props are stored in /data, so those would work.
Do the dd and tell me if you have FEC. This is for me, your numbers will be different.
Code:
Poke3:/ # dd if=/dev/block/by-name/system of=/sdcard/check skip=6291448
8+0 records in
8+0 records out
4096 bytes (4.0 K) copied, 0.000839 s, 4.6 M/s
Numbers too high will say "Can't skip". Numbers too low will give you a file that's too big.
Do:
Code:
dd if=/dev/block/by-name/system of=/sdcard/check skip=big-number
Big number = count of sectors in system partition - 8 // for eMMC
Big number = count of sectors in system partition - 1 // for UFS
You should end up with a file exactly 4096 bytes. If you don't play with the numbers.
Hexedit that file, does it start with fe cf ec fe? Then it has FEC.
Click to expand...
Click to collapse
Came back weird, does this need to be run as root?
Code:
$ dd if=/dev/block/by-name/system of=/sdcard/check skip=big-number
dd: not integer: big-number
K0mraid3 said:
Came back weird, does this need to be run as root?
Code:
$ dd if=/dev/block/by-name/system of=/sdcard/check skip=big-number
dd: not integer: big-number
Click to expand...
Click to collapse
dumb question lol disregard. same result.
ill go check in /data now
/data is fine. Just check system partition. Using real numbers. Actually integers.
Bump...