Related
Hi everyone. I've just rooted my galaxy s 2, running on gingerbread XWKE8. I'm planning to install a new rom.have heard about various rom available.
1. Is villain 2.0 rom okay? The main purpose for installing a custom rom for me is to save battery as I'm outdoor most of the time. as of now my gingerbread is working well except for this battery issue. Is it worth changing the rom?
2.Was reading about titanium backup
I've done back up of my custom apps + system data on phone' s external sd card. I don't have paid version of titanium. Can't buy it either. (no credit card).anyway, shall i be get nandroid backup too, just in case? when i install new rom n use TB for restore, since it*
Has system data as well, won't it overwrite the old data on the new rom? it sounds un believable coz it thwarts the whole purpose of installing a new rom. So will there be an option of ticking individual files to restore as per my choice? (no pro version of . titanium). If so, how do i know which one to be restored?
3. If clockworkmode has a back up option why do we need a titanium backup? cos it gives a nandroid type backup?
4. Can clockworkmode be used to upgrade to a new firmware (custom our stock) or odin should be used as in rooting with a little modification (depending on if firmware has one file or 3 files)?
Please enlighten.
Thank you very much
Sent from my GT-I9100 using XDA App
1) See for yourself if it's worth it.
2) Yes do a nandroid and check this before changing rom.
3) Nandroid is a exact copy of your current set-up, restoring it would undo the custom rom flash.Titanium backs up your apps so you can restore them after changing rom.
4) Depends on how the files are provided. Both should be possible.
For a credit card alternative I use this.
Hi.thanks a lot for replying. How do I get nandroid backup? Do I've to use rom manager in order to do nandroid backup? Cos when I search for nandroid in market, it doesn't return any nandroid app as such.
Sent from my GT-I9100 using XDA App
No boot in to recovery, go to backup and restore and backup.
TheGhost1233 said:
3) Nandroid is a exact copy of your current set-up, restoring it would undo the custom rom flash.Titanium backs up your apps so you can restore them after changing rom.
Click to expand...
Click to collapse
So if I happen to dislike or have problems with a custom rom, I just restore the backup of my rooted stock rom and all is back to the way it was (all, data/boot/apps/settings ...)? I think it will be, but I just want to be sure.
Hi.thanks again. I've read that recovery mode back up or titanium backup doesn't backup efs folder . One needs adb our terminal emulater or root explorer to do so.is there any link that explains efs folder backup using terminal emulater step by step?
Regards
Sent from my GT-I9100 using XDA App
dav pahwa said:
Hi.thanks again. I've read that recovery mode back up or titanium backup doesn't backup efs folder . One needs adb our terminal emulater or root explorer to do so.is there any link that explains efs folder backup using terminal emulater step by step?
Regards
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
EFS post in Dev section probably .
jje
I already linked to the right thread, in the thread there are different commands. All you have to do is pick a method, create the efs folder, copy the command to the terminal emulator and hit enter.
Sent from my Transformer TF101 using XDA Premium App
VillianRom is nice I've been using VR since release and tried many roms en route and keep coming back to VR for some reason!
Best to do a nandroid via CWM Recovery so if any of your new installs have problems you can always wipe and go back to a working config.
I only use TB to backup app data, I don't like backing up system data as when moving from one rom to another if you restore you may encounter issues so always best to start from scratch to save any hassles.
Default [REF] Backup /efs folder. IMPORTANT.
This guide is based on a guide by Candanga on the i9000 forums, and some commands from supercurio
Please hit thanks on their posts and show them some love for the write up.
-----------------------------------------------------------------------------------------------------------------------
I’ve compiled a quick guide to instruct how to make a copy of the /efs folder. I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone.
This guide ASUMES you have read this Excellent Guide by Darkstrikerfirst:
H E R E <-- Make sure to read the ADB Guide.
I recommend doing this with a Mobile just taken out of the box or with any Official ROM of its Service Provider. If you have already Flashed your phone with another ROM but its working fine, then you can use that /efs also.
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centres.
***WARNING: I take no responsibility to any damage caused by the methods cited and/or written here. Their sole purpose is to back-up data and not to alter in any way the integrity of the original files of the mobile***
What you will need:
* Rooted SGS II to get permissions as a SU (Super User) and perform the backup
* I would suggest learning a little about the terminal commands used (in case you are not familiar with them), as it’s better to know what you are doing rather than typing strings like a little chimp without knowing what they are; if you are a little lazy, then you have a good chance bricking your mobile. <- Busybox Commands(or Google them)
* Terminal Emulator by Jack Palevich (available from the market) <-Terminal Emulator or use ADB which is included in the SDK Development Tools
The standard prompt of terminal (adb) is a $ sign. Once you enter “SU” it will become a # Sign.
***NOTE: Make sure to keep an eye on the screen of your SGS II during this process, because it may request SU permissions [currently doesn't on CF-root]; else, you will get an error (just if it’s the first time). In Terminal Emulator you will need to reset the app after granting permissions cause it usually freezes***
*Remember: to use ADB you need to enable USB DEBUGGING under Applications/Development in your SGS II.
Here are 3 methods, I recommend that you do both Clean and RAW.
Basic, unix permissions lost :
Code:
su
busybox cp -a /efs /sdcard/efs/
Clean :
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
After this, you will end up with the file efs-backup.tar.gz in your INTERNAL SDCARD in sdcard/efs/, which is a “tarball” or a ZIP of the /efs folder. That file is your backup. You can expand it with Winrar.
You can also back up the mmcblk0p1 (where /efs is stored) under /dev/block which can greatly support in recovering your IMEI in case of a screw-up:
RAW :
Code:
su
cat /dev/block/mmcblk0p1 > /sdcard/efs/efs_dev-block-mmcblk0p1.img
Same thing, the target is the INTERNAL SDCARD in sdcard/efs/, so go ahead and copy the file.
Hi theghost & thanks for replying. Yes, i had read that link . But being a starter in androids, i had some doubts n thought if someone else knows a more simplified thread. Eventually i followed the same thread only.
As the author said, there r two methods - clean & raw n he advises to use both. when u used raw , in the end comes- no such file directory exists. When i checked my files->sdcard , i could see efs folder n some files inside it (which wasn`t happening even with astro file manger) I copied the efs folder N pasted it into Externalsd folder (default Ext. sd card folder ?)
R my efs folder files safe now ?
Is there any other precaution to be taken , any files to be saved before i embark on installing New villain rom 2.0 as per instructions given here http://forum.xda-developers.com/showthread.php?t=1081368 .
Strangely efs folder saving point isn`t mentioned here , even though its so important. (But then may be its very basic) Is there any other basic that i should know ?
Thanks a lot again.
with regards.
Create the efs folder with astro, then use the raw method and copy the .img to your pc.
Sent from my Transformer TF101 using XDA Premium App
How n where to create ef folder using astro? When i click on app
The home page shows
(folder icon)/mnt
(Home icon)(search icon) etc.
Folder-ifs
Asec
Obb
Sdcard
Secure
Usb
On this home page I should crate folder-efs ?
Sent from my GT-I9100 using XDA App
No in sdcard
Sent from my GT-I9100 using XDA Premium App
But sdcard already has efs folder with some files in it . This was created when I used the emulator. But the RAW step had failed as I told u earlier.
Sent from my GT-I9100 using XDA App
nikzDHD said:
VillianRom is nice I've been using VR since release and tried many roms en route and keep coming back to VR for some reason!
Best to do a nandroid via CWM Recovery so if any of your new installs have problems you can always wipe and go back to a working config.
I only use TB to backup app data, I don't like backing up system data as when moving from one rom to another if you restore you may encounter issues so always best to start from scratch to save any hassles.
Click to expand...
Click to collapse
Thanks mate. I'm backing up only custom apps, not custom apps.
Sent from my GT-I9100 using XDA App
Mist that you already had the efs folder. If you already have something there your probably good. If you still want the raw method to work make sure you type su first and hit enter and than exactly copy the cat command (ChromeToPhone is great for this) it should work.
Didn't work out mate .
Sent from my GT-I9100 using XDA App
I'm comfortable with it. Thanks for yo support mate
Sent from my GT-I9100 using XDA App
I had downloaded a version of this file from a post embedded deep inside one of the threads over here (sorry can't find it right now), but upon examination of its contents, I discovered some issues:
1. The checksums on the files in contained in the the original zip file showed that B&N had at least two versions of 1.3.0 update you can download from them, and the zip I got contained an older version so I put in the latest files in there.
2. There were unnecessary files included inside the original zip file, I deleted those, and only included what was needed.
3. There were errors in the script syntax, which I corrected, so that the proper commands are run during the update, and the proper sed substitutions are made during the editing of the unpacked init.rc inside the ramdisk.
What this zip will do is replace any older version of a B&N ROM on the alternate eMMC partitions of a dual booting configurations to the latest versions. This will prevent B&N from pushing the 1.3.0 update to you OTA, and messing up your dual boot setup. Just put the zip on your sdcard, boot into CWM recovery, and apply the zip. I apologize in advance for not giving credit to the original creators of the scripts here.
Note: There have been two different protocols for a dual booting u-boot.bin, with an older one relying on the files u-boot.altimg, and u-boot.altram to specify the names of the secondary boot ramdisk and kernel, and a newer one assuming that they are named uAltRam, and uAltImg respectively. This update conforms to the new u-boot.bin protocol. If you are still using the old one, you will have to get root access to /boot and edit the two files to point to uAltRam and uAltImg.
So if you want try it out, here it is:
http://www.mediafire.com/?gcrpzzc0kdoxcjx
MD5 Sum: 51e24c1e5eff11ba5ea481a63f7404eb
Update
I have now uploaded files for B&N Update 1.4.1.
The first file (MD5 Sum: 4ff1d9764663278c3f51e2e2c9d841a6) is meant to update a pre 1.4.1 Stock B&N ROM on secondary /system through CWM:
https://rapidshare.com/files/52135913/secondary_update_NC_stock_1_4_1.zip
The second file (MD5 Sum: c1506816fbfb8c419fbbc4afe1b12887) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM without messing with recovery;
https://rapidshare.com/files/869435270/primary_update_NC_stock_1_4_1_keep_CWM.zip
The third file (MD5 Sum: ab1307c55a2c35c91d339c8037ce9a78) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM, replacing recovery and all:
https://rapidshare.com/files/2059644016/primary_update_NC_stock_1_4_1.zip
None of these files will wipe user apps and data, so if you wish to do that, boot into recovery and wipe from there. [This will work on primary /data partition only]
Please note: If the B&N Stock ROM is rooted, you will lose root upon updating.
Thanks!
This worked beautifully! I flashed it from my sdcard after booting into CWM on my primary partition on emmc.
I'm betting you got the original from jasoraso in this dual boot thread: http://forum.xda-developers.com/showpost.php?p=17122342&postcount=142
What I would love is a straight CWM-flashable 1.3 ROM, to include in my up-to-date (for now) guide for setting up the dual boot, rather than having to set up and move 1.2, then update to 1.3.
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Sent from my SAMSUNG-SGH-I897 using XDA App
rajendra82 said:
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
Click to expand...
Click to collapse
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
rajendra82 said:
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Click to expand...
Click to collapse
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Taosaur said:
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
Click to expand...
Click to collapse
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Taosaur said:
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Click to expand...
Click to collapse
No way to get around having to register the primary partition image first. Once that is done it could be moved to secondary and then updated straight to 1.3 instead of going 1.2 first.
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
yelloguy said:
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
Click to expand...
Click to collapse
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
rajendra82 said:
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Click to expand...
Click to collapse
I wouldn't know what to change and what to leave alone, myself, but I think you're making this more complicated than it needs to be. I'm talking about installing 1.3 using CWM, regardless of how the device is partitioned or what was on the primary partition previously. Like the files in this thread, but 1.3: http://forum.xda-developers.com/showthread.php?t=1050520.
I understand that you were just cleaning up jaso's update-dualboot-to-1.3 file. I used the original and it worked fine, but it would have saved me a couple steps (and would be more useful in a guide for setting up dualboot) to simply install 1.3 rather than 1.2 to the primary partition when setting up. The reason I started with 1.2 is because it is the most current stock ROM available for CWM. What I would like is to avoid a historical re-enactment of stock OS development altogether. A general-purpose, CWM-flashable 1.3 ROM would be broadly useful, but is so far lacking as far as I've seen.
1. Do you envision this to be an uprooted stock 1.3 update ROM (either as primary or the only boot option) ? I just don't see the need for this to be CWM flashable. It is very easy to get there by resetting the device to stock, and then updating the device to 1.3.0 using the B&N file, and restoring dual boot as need be. If one has any older stock ROM running on primary, the B&N update will get them to 1.3 while losing root. There is no need to apply 1.2 update first.
2. Do you envision this to be for already rooted single or primary booting 1.1/1.2 users? There is once again no need to create any file for this. One can simply apply the B&N update, and then rerun manual nooter, and restore dual booting to the secondary.
3. The only users with no clear upgrade path are those who have already moved the B&N ROM to secondary. That's why I fixed up the zip file, and shared it. I am glad the original file worked for you despite the script errors. I can see other setups where it would have failed though.
I am not trying to make this more complicated than it needs to be. The Nook Color is just capable of being set up in so many ways, there isn't simply going to be a single update method that will work in all scenarios.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Taosaur said:
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Click to expand...
Click to collapse
Then the best bet is two step process:
1. Wipe device and restore to factory stock.
2. Download B&N 1.3 update file from website and place it on the root of SD card. Let the device recognize it, and apply it.
Once the 1.3 update gets applied, you are free to reroot, install CWM, set up dual booting, or whatever the next step may be.
It is the only method that will work in all circumstance as it involves starting from scratch regardless of setup. If want to preserve any of your current setup, no one step file will work for all circumstances. Some people have the stock firmware rooted, others do not. Some have the stock as the only internal boot, others have it as primary option of a dual booting configuration, while others have it as a secondary option. Some have stock recovery and run CWM off the sdcard when needed and want to update their recovery to the latest stock version, others want to keep the CWM recovery, and not update the recovery. There simply is no way file to cope with all these options.
rajendra82 said:
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
Click to expand...
Click to collapse
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
rajendra82 said:
1. Wipe device and restore to factory stock.
Click to expand...
Click to collapse
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
---------- Post added at 02:15 PM ---------- Previous post was at 01:58 PM ----------
yelloguy said:
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
Click to expand...
Click to collapse
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Taosaur said:
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Click to expand...
Click to collapse
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
Click to expand...
Click to collapse
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
Click to expand...
Click to collapse
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0p1 at the temporary location you created using the command:
mount /dev/block/mmcblk0p1 <full path to the directory you created>
4. Now use Astro to go over to the directory you created and mounted mmcblk0p1 into. You should see:
u-boot.bin which is the bootloader
u-boot.bin.stock which is the backup of the old stock bootloader
uImage and uRamdisk which are your primary kernel and ramdisk
uFImg and uFRam which are your secondary kernel and ramdisk (and whose names are mismatching the CM7 bootloader protocol)
u-boot.altimg and u-boot.altram, which are text files per the old bootloader method containing names of uFImg and uFRam
5. Rename uFImg to uAltImg, uFRam to uAltRam. And edit the contents of u-boot.altimg and u-boot.altram to match the new file names.
6. Reboot as usual into primary or secondary.
Now if an CM7 update ever replaces your u-boot.bin, you will not lose dual boot, as you have it set up as uAltImg and uAltRam per the new protocol.
Sent from my SAMSUNG-SGH-I897 using XDA App
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
Taosaur said:
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
Click to expand...
Click to collapse
I am sorry if you think I am rationalizing, but that was not my intention. I just wanted to point out that the files you linked to do not meet your own criteria.
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible IMO, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------
Taosaur said:
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
Click to expand...
Click to collapse
It would work. If you apply my zip, there will be a uAltImg and uAltRam in /boot (in addition to uFImg and uFRam). If you apply another update that pushes the CM7 bootloader, it will then look for these files with trying to do an alternate boot, and would boot into a unrooted stock 1.3.
rajendra82 said:
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0 at the temporary location you created using the command:
mount /dev/block/mmcblk0 <full path to the directory you created>
Click to expand...
Click to collapse
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
yelloguy said:
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
Click to expand...
Click to collapse
I see a typo in my command (stupid Swiftkey X). It should be:
mount /dev/block/mmcblk0p1 <some directory>
Also try typing just mount in terminal to see if /dev/block/mmcblk0p1 is already mounted somewhere else.
rajendra82 said:
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter will lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
Click to expand...
Click to collapse
Riiiiight... it would install stock 1.3 to the device. That's the intended behavior. The point is to avoid the unnecessary step of updating in any process that includes flashing stock to the sole or primary partition. One example of such a process would be a fresh dual boot setup. That it does not update or otherwise rely upon an existing install is the point.
Granted, such a file would not repartition the device, but it would install up-to-date stock in one step regardless of how a device is partitioned (1/5, 2/5, 5/1 or dual boot).
This is not a question about how to root the Atrix. I've already done that.
My question is about what actually is changed in the phone by following the root procedure. (I searched the forum but didn't find elsewhere the answers I look for).
Why do I ask?
1) Because I'd like to have a better understanding of the android OS.
2) Because I'd like to understand and know what do I need to do in case I want to unroot and return to plain stock.
My case:
(I've just rooted my Atrix. I didn't unlock it)
I've followed the "manual" procedure proposed by BriefMobile.
I can essentially understand (more or less) the commands listed (mount, remount, cp, install, chmod 6755, flash...)
What I'd like to understand better is what changes does the command
Code:
fastboot flash preinstall root.img
Does it just copy new files? Or does it copy (and replace) files on the phone?
(In the second case I'm afraid I made a mistake in not backing them up before running that command...)
Thanks in advance for your help.
Putting it in Windows terms (because Android is Linux), root is like having administrator privileges on your computer. It allows you to modify any system files that would normally be kept locked down. It also allows you to run applications, such as SetCPU, which can directly control hardware (in this case CPU frequency/speed and voltage) and low-level system files. Root in Android is comprised of two main files: the "su" binary (which is the command that applications use to invoke a request to do something with root privileges) and the SuperUser.apk (SuperUser app that's in the app drawer). The SuperUser app exists to prompt you whenever an application asks for root permission. So if you go into the terminal and type a low-level command, you'll see something like, "You do not have permission to do this". But if you type "su" before the command, it will run if you hit "Allow" on the SuperUser request.
Get it?
Product F(RED) said:
....
Get it?
Click to expand...
Click to collapse
Thanks Product F(RED) .
Yes I got it.
I already knew what rooting means in general terms.
What I really asked (sorry if I wasn't clear enough) is what does the root "physically" change on the phone.
According to your answer I assume it just adds the "su" binary and the "SuperUser" app (apart from changing some permission on some system folders) and that it doesn't replace any "stock" system file.
I also assume that these new files are extracted from the "root.img" (or "preinstall.img") files flashed by the fastboot command.
Is it so?
I was a little confused because I saw in some other forum a reference to some "stock" files wiped out in the /preinstall/app/ folder by the root process, mining the reversibility of the procedure (in case of no previous full system backup).
sphere314 said:
Thanks Product F(RED) .
Yes I got it.
I already knew what rooting means in general terms.
What I really asked (sorry if I wasn't clear enough) is what does the root "physically" change on the phone.
According to your answer I assume it just adds the "su" binary and the "SuperUser" app (apart from changing some permission on some system folders) and that it doesn't replace any "stock" system file.
I also assume that these new files are extracted from the "root.img" (or "preinstall.img") files flashed by the fastboot command.
Is it so?
I was a little confused because I saw in some other forum a reference to some "stock" files wiped out in the /preinstall/app/ folder by the root process.
Click to expand...
Click to collapse
Pretty much, yes, you're adding those two files (as well as another called BusyBox that allows other files to run, but this you can install after you root). The scenario I'm describing is that you're on a stock ROM and you just rooted your phone for the first time.
Though fastboot is present on every phone, using it to flash those two files seems to be unique to your phone because rooting methods vary from phone to phone. But basically the two most common methods are:
1. You flash a custom recovery from your computer if your phone's bootloader is not locked, and then you can flash the root files (su/SuperUser.apk) to the ROM from there or just flash a custom ROM that includes them.
or
2. You use fastboot/adb/some third-party method to root the stock ROM on your phone from your computer, then you install a custom recovery, and then you can flash custom ROMs/kernels/etc.
That /preinstall/app folder seems to be unique to your phone, but if I had to guess, it has something to do with deleting preloaded bloatware that comes with the phone. Because out of the box you can't, but once you have root permissions, you can go to that folder with a file manager to delete the APKs or use something like Titanium Backup to do it.
Product F(RED) said:
Pretty much, yes, you're adding those two files (as well as another called BusyBox that allows other files to run, but this you can install after you root). The scenario I'm describing is that you're on a stock ROM and you just rooted your phone for the first time.
Though fastboot is present on every phone, using it to flash those two files seems to be unique to your phone because rooting methods vary from phone to phone. But basically the two most common methods are:
1. You flash a custom recovery from your computer if your phone's bootloader is not locked, and then you can flash the root files (su/SuperUser.apk) to the ROM from there or just flash a custom ROM that includes them.
or
2. You use fastboot/adb/some third-party method to root the stock ROM on your phone from your computer, then you install a custom recovery, and then you can flash custom ROMs/kernels/etc.
That /preinstall/app folder seems to be unique to your phone, but if I had to guess, it has something to do with deleting preloaded bloatware that comes with the phone. Because out of the box you can't, but once you have root permissions, you can go to that folder with a file manager to delete the APKs or use something like Titanium Backup to do it.
Click to expand...
Click to collapse
Thanks again Product F(RED).
Things are clearer now.
I wasn't aware of the installation of "BusyBox" (I found it in my phone in the folder /osh/bin/)
I think the root method I used (BriefMobile) is the type 2. I didn't install a custom recovery as I'm not interested yet in flashing custom ROMs/kernels/etc.
So, to summarize...
The basic root methods (no unlock) consists in
1) install the "su" binary
2) install the "busybox" binary
3) install the "superuser.apk" app
4) change some r-w permissions
In my case (probably) the root method also wiped out some preloaded bloatware file in the /preinstall/app folder but that's not essential (unless Moto makes a check for the presence of those files before an OTA update).
They usually do check (and will fail) because OTA's are like patches; not really replacements for the whole /system/ partition. Never take an OTA when you're rooted, especially because they can do things like update and lock your bootloader, among other things. It's safer to wait until rooted versions pop up in the development section for your phone.
My HTC Desire VC (T328d) was rooted and running Android OS 4.0.3 (ics).
In recovery mode, I accidentally formatted /system folder (from internal phone memory).
This is because the recovery mode is all in chinese language and I did a huge mistake.
The phone cannot boot showing HTC logo screen and no boot sound.
I've downloaded the kernel for this device at htcdev.com and I don't know how to use it and what it is for.
Fortunately, I can enter recovery mode. My friend has the same device and his is not rooted yet. Maybe I can get some files from him.
Any solution, please?
Learn Chinese?
Flash a rom?
You should ask in a Desire forum tho
zeppelinrox said:
Learn Chinese?
Flash a rom?
You should ask in a Desire forum tho
Click to expand...
Click to collapse
I can't find the rom ... can u please help me?
There is no forum for my device. Only for Desire, Desire HD, Desire V ,.........
Looks like your best shot is to root your friends phone, do a nandroid backup, restore it to yours, then reset to factory defaults.
Don't forget to use V6 SuperCharger afterwards... lol
please tell me
zeppelinrox said:
Looks like your best shot is to root your friends phone, do a nandroid backup, restore it to yours, then reset to factory defaults.
Don't forget to use V6 SuperCharger afterwards... lol
Click to expand...
Click to collapse
Thanks for your advice. But, I don't know how to do nandroid backup. The instructions say that it is apk app. I can't even boot my phone and how can I use apk ? In addition, now I installed a recovery from china site (for Desire VC specifically) and it contains backup and restore function. Is it the same with Nandroid Backup or CWM ?
Can you instruct me in some steps, please ?
erizchen said:
Thanks for your advice. But, I don't know how to do nandroid backup. The instructions say that it is apk app. I can't even boot my phone and how can I use apk ? In addition, now I installed a recovery from china site (for Desire VC specifically) and it contains backup and restore function. Is it the same with Nandroid Backup or CWM ?
Can you instruct me in some steps, please ?
Click to expand...
Click to collapse
Yes, the backup option you see in recovery is Nandroid backup. Please be carefull in formatting system, it would wipe your ROM. Always take nandroid backup before you playing with other Rom.
Here you go,
1. Take nandroid backup of your friends ROM
2. Place the backup into your sd card( backup available in clockwork folder in ur friends mobile. Just copy the entire clockwork folder and paste in ur sd card. Now mount the sdcard in ur mobile)
3. Reboot in recovery.
4. Wipe cache and dalvik
5. Restore from nandroid.
Let me know this helps..
Cyb0rgz said:
Yes, the backup option you see in recovery is Nandroid backup. Please be carefull in formatting system, it would wipe your ROM. Always take nandroid backup before you playing with other Rom.
Here you go,
1. Take nandroid backup of your friends ROM
2. Place the backup into your sd card( backup available in clockwork folder in ur friends mobile. Just copy the entire clockwork folder and paste in ur sd card. Now mount the sdcard in ur mobile)
3. Reboot in recovery.
4. Wipe cache and dalvik
5. Restore from nandroid.
Let me know this helps..
Click to expand...
Click to collapse
What does "dalvik" mean ?
I've never heard of it. Can u explain me a little?
erizchen said:
What does "dalvik" mean ?
I've never heard of it. Can u explain me a little?
Click to expand...
Click to collapse
Dalvik is virtual machine that runs Android Apps on Android. Dalvik-cache is the cache area for Dalvik VM, it is created when the Dalvik VM optimizes your app for running.
Dalvik is the virtual machine that is used by Android. It is generally thought of as a java virtual machine, although this is not precisely correct. It uses an object model that is identical to java, and it's memory model is also nearly equivalent. But the
Accordingly, it uses a completely different bytecode than java. However, the Android SDK includes the dex tool to translate java bytecode to dalvik bytecode, which is why you are able to write Android applications in java.
When you install an application on Android, it performs some modifications and optimizations on that application's dex file (the file that contains all the dalvik bytecode for the application). It then caches the resulting odex (optimized dex) file in the /data/dalvik-cache folder, so that it doesn't have to perform the optimization process every time it loads an application.
Cyb0rgz said:
Dalvik is virtual machine that runs Android Apps on Android. Dalvik-cache is the cache area for Dalvik VM, it is created when the Dalvik VM optimizes your app for running.
Dalvik is the virtual machine that is used by Android. It is generally thought of as a java virtual machine, although this is not precisely correct. It uses an object model that is identical to java, and it's memory model is also nearly equivalent. But the
Accordingly, it uses a completely different bytecode than java. However, the Android SDK includes the dex tool to translate java bytecode to dalvik bytecode, which is why you are able to write Android applications in java.
When you install an application on Android, it performs some modifications and optimizations on that application's dex file (the file that contains all the dalvik bytecode for the application). It then caches the resulting odex (optimized dex) file in the /data/dalvik-cache folder, so that it doesn't have to perform the optimization process every time it loads an application.
Click to expand...
Click to collapse
Thanks alot for your explanation.
But, I don't have any setting to clear dalvik. Anyway to do so?
These are in my list of recovery menu:
1 - Reboot the system
2 - Select Update
3 - Restore the factory
4 - Empty the cache
5 - Backup and recovery
6- Mount storage
7 - Advance
- Empty the battery status
- Reporting errors
- Keys test
- Card partition
- Permissions repair
8 - Shutdown
I wish to succeed with nandroid backup and restore method.
erizchen said:
Thanks alot for your explanation.
But, I don't have any setting to clear dalvik. Anyway to do so?
These are in my list of recovery menu:
1 - Reboot the system
2 - Select Update
3 - Restore the factory
4 - Empty the cache
5 - Backup and recovery
6- Mount storage
7 - Advance
- Empty the battery status
- Reporting errors
- Keys test
- Card partition
- Permissions repair
8 - Shutdown
I wish to succeed with nandroid backup and restore method.
Click to expand...
Click to collapse
Your recovery is not CWM recovery.
You must flash CWM recovery first. With CWM recovery, you can find "wipe delvik cache"
under Advance menu.
erizchen said:
I wish to succeed with nandroid backup and restore method.
Click to expand...
Click to collapse
It's easy. Just try to do all steps with patience. If you have any doubts, please do clear it. Don't assume anything just few mins of Googling will solve major issues..
I will help as much as I can to get things works well in your desire cheers
Cyb0rgz said:
It's easy. Just try to do all steps with patience. If you have any doubts, please do clear it. Don't assume anything just few mins of Googling will solve major issues..
I will help as much as I can to get things works well in your desire cheers
Click to expand...
Click to collapse
Millions of Thanks to you all ... I can do it successfully :victory:
I just backup my friend's ROM (which was updated by him).
And I restored all of his ROM.
My device is being well now ..... but still problem there are errors for wifi and bluetooth
I can't switch on wifi and bluetooth.
Below the "wifi" text, it shows "error".
:angel: :angel:
I've tried the ways from here and there , but it didn't work
Please help me with this again.
Am I a problem maker ?
erizchen said:
Millions of Thanks to you all ... I can do it successfully :victory:
I just backup my friend's ROM (which was updated by him).
And I restored all of his ROM.
My device is being well now ..... but still problem there are errors for wifi and bluetooth
I can't switch on wifi and bluetooth.
Below the "wifi" text, it shows "error".
:angel: :angel:
I've tried the ways from here and there , but it didn't work
Please help me with this again.
Am I a problem maker ?
Click to expand...
Click to collapse
Try all basic things, like clearing RAM, Booting your phone etc. If its not solved, try to flash the kernel via recovery. Please ensure that you are s-off for this. Even after flashing the kernel that issue persists, please check your radio (baseband) is latest. Else update the radio. I guess, flashing kernel will solve the issue.
Please let me know whether you are s-off and rooted.
Tips: its my personal advice to be s-off (your warranty voids)
Edit:
If you are HTC.dev unlocked and s-on then follow below steps to flash the kernel.
http://forum.xda-developers.com/showthread.php?t=1752270
Cyb0rgz said:
Try all basic things, like clearing RAM, Booting your phone etc. If its not solved, try to flash the kernel via recovery. Please ensure that you are s-off for this. Even after flashing the kernel that issue persists, please check your radio (baseband) is latest. Else update the radio. I guess, flashing kernel will solve the issue.
Please let me know whether you are s-off and rooted.
Tips: its my personal advice to be s-off (your warranty voids)
Edit:
If you are HTC.dev unlocked and s-on then follow below steps to flash the kernel.
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
My device is not s-off yet. I've just unlocked with htcdev. I searched s-off for this device but i can't find and don't know how to.
I have kernel downloaded from htc official web. Can i flash it with s-on ?
PRE REQUISITES:
1. ROOTED/UNLOCKED Phone.
2. HTC Sync Drivers (Install HTC Sync, it will install necessary drivers; Make sure HTC sync is not active; Just Exit from HTC Sync if its running)
3. Android SDK/Fast boot and Adb installed.
4. ES or ROOT Explorer (Available in google play)
*
<<PLEASE TAKE NANDROID BACKUP>>
1.* Follows Steps 1 to 5 from This thread, http://forum.xda-developers.com/showthread.php?t=1752270
2.* Extract the bcm4329.ko from the your kernel.zip
*
[ with Root Exploror or ES Explorer ]
1. touch Mount R/W
2. copy bcm4329.ko to /system/lib/modules
3. long press on the bcm4329.ko and select Permissions then check read, write for owner, read for group and read for others, click ok
4. long press again on the bcm4329.ko and select Change Owner, then pick 0-root for owner and pick 0-root for group, click ok
*
-----I am not responsible for any problems caused to your mobile-----
Cyb0rgz said:
PRE REQUISITES:
1. ROOTED/UNLOCKED Phone.
2. HTC Sync Drivers (Install HTC Sync, it will install necessary drivers; Make sure HTC sync is not active; Just Exit from HTC Sync if its running)
3. Android SDK/Fast boot and Adb installed.
4. ES or ROOT Explorer (Available in google play)
*
<<PLEASE TAKE NANDROID BACKUP>>
1.* Follows Steps 1 to 5 from This thread, http://forum.xda-developers.com/showthread.php?t=1752270
2.* Extract the bcm4329.ko from the your kernel.zip
*
[ with Root Exploror or ES Explorer ]
1. touch Mount R/W
2. copy bcm4329.ko to /system/lib/modules
3. long press on the bcm4329.ko and select Permissions then check read, write for owner, read for group and read for others, click ok
4. long press again on the bcm4329.ko and select Change Owner, then pick 0-root for owner and pick 0-root for group, click ok
*
-----I am not responsible for any problems caused to your mobile-----
Click to expand...
Click to collapse
From where do I have to find "boot.img" ?
I have only back up folder (ROM) from my friend's phone. And I just restored it (including boot.img) with CWM nandroid backup.
Is that the same with your instruction from step 1 to 5 ?
I can selectively restore "boot.img" with CWM nandroid recovery. Is that the same ?
In addition, the version of Kernel I downloaded is the same with my phone currently. I downloaded it from http://htcdev.com/devcenter/downloads
I got primodd-ics-crc-3.0.16-ead8920.zip file. When I extract it, I just found "bcm4329" folder under "primodd-ics-crc-3.0.16-ead8920/drivers/net/wireless" path. I can't find "bcm4329.ko"
Do you mean the driver in my system is not compatible with my phone after restore ?
erizchen said:
From where do I have to find "boot.img" ?
I have only back up folder (ROM) from my friend's phone. And I just restored it (including boot.img) with CWM nandroid backup.
Is that the same with your instruction from step 1 to 5 ?
I can selectively restore "boot.img" with CWM nandroid recovery. Is that the same ?
Click to expand...
Click to collapse
Boot.IMG is consists of kernel and ramdisk. They both necessary to start up the device, initializing the hardware, phone etc.
Since you are s-on, while placing the boot.img from nandroid, its not well placed. S-0N means, security on that doesn't allows to flash boot.img from nandroid.
I guess, every time you flash the via recovery boot.img is not placed in correct partition.
So, you have alternative method which allows to place the boot.img in correct path.That's why asked to do it via fastboot mode. Hope you understand.
In addition, the version of Kernel I downloaded is the same with my phone currently. I downloaded it from http://htcdev.com/devcenter/downloads
I got primodd-ics-crc-3.0.16-ead8920.zip file. When I extract it, I just found "bcm4329" folder under "primodd-ics-crc-3.0.16-ead8920/drivers/net/wireless" path. I can't find "bcm4329.ko"
Do you mean the driver in my system is not compatible with my phone after restore ?
Click to expand...
Click to collapse
Since you have problem only with WiFi and Bluetooth. You can skip fastboot method. bcm4329.ko is same as what you found in the kernel that you downloaded from HTC dev. (Just right click and check the file extension from your pc)
Your friends WiFi and Bluetooth are working fine. bcm4329.ko is responsible for WiFi and Bluetooth. Since you used recovery to restore nandroid, the bcm4329.ko is not placed in the system/lib/modules path. So manually you are placing it
To make it easier do the following
1. From your friends mobile, goto system/lib/modules copy bcm4329.ko file into your pc (use root file explorer)
2. Place that file in your sd card.
3. Then use root explorer and follow the steps mentioned in previous post.( 4 steps under root explorer)
Please let me know if this works.
PS: take nandroid before performing. No warranty for any tips provided. Please do search on google regarding kernel, android partition, bcm4329.ko etc.
Since I don't have pc, I can't help you more with respective links to other sites. Yes, It took much time to compose in my android touch screen.
Any shine on your WiFi / Bluetooth? Just curious to know about it..
Trying
Cyb0rgz said:
Any shine on your WiFi / Bluetooth? Just curious to know about it..
Click to expand...
Click to collapse
What does "shine" mean ?
My friend can't find "bcm4329.ko" such a file under /system/lib/modules
So, I'm trying to take matching the files under /system/lib/modules to know the missing files.
Any idea ?
My friend told me he has same files as mine in /system/lib/modules
These are the file list
bluetooth.ko
bnep.ko
btwilink.ko
cfg80211.ko
compat.ko
fm_drv.ko
hidp.ko
kineto_gan.ko
mac80211.ko
rfcomm.ko
wl12xx.ko
wl12xx_sdio.ko
He has only those files (not include "bcm4329.ko")
What should I do now ?
Recently I was studying android recovery mode, and I have some questions. Anyone knows the answer? Thanks very much.
1. Can recovery flash bootloader?
From this link====>http://forum.xda-developers.com/showthread.php?t=2321310, I think it can do that. But I'm not sure.
2. Can recovery flash recovery partition itself?
I think it can not do this. Not confirm that.
3. We know in update.zip, boot.img is corresponding boot partition, but why system is a folder, not system.img? There is a system partition also.
4. While OTA upgrade system, why the update package downloaded under /cache path? Can we change it to sdcard?
5. Most important, what exactly update-script do things under recovery mode? How the command executed?
BTW, there are other questions, but not related to Recovery Mode.
1. How can I see the flash partitions? I know to use the command cat /proc/mtd, but as Samsung, it use emmc flash, while I type that command, no results printed. How to see?
2. About userdata partition, we know that when first run android OS, system will copy files from /system to /data, but does it do it every time that we turn on the phone or just do it once after the first booting after we update our system?
Hello,
I can answer some questions, and I hope someone else can fill the blanks.
1. Can recovery flash bootloader?
=> Yes, you have to modify your boot image, but it still possible, just include the modified boot image in the update file, and give good command in update.zip
2. Can recovery flash recovery partition itself?
=> I am not sure, but I think its possible, I saw code of recovery in Android code, so if you modify it, and include the good image in update.zip, I think you will see the modification. Never tried for now.
3. We know in update.zip, boot.img is corresponding boot partition, but why system is a folder, not system.img? There is a system partition also.
=> In fact is depend witch compilation system you use. For Cyanogen, yes in fact its a folder, but for AOSP its System.img
The difference comes from the command file in update, theire not the same. But finally the result in the same. We have a system partition.
4. While OTA upgrade system, why the update package downloaded under /cache path? Can we change it to sdcard?
=> Reasons I can see :
--> In past, sdcard was not mounted by default in recovery mode, so can't see the update.zip file
--> sdcard can be removed at any time, its dangerous, when do the update to loose the file
--> To be sure have right to remove the update.zip when installation done
--> Old phone didn't have all a sdcard, cache is sure to exists
=>Yes we can change it, but we have to be sure the sdcard is mounted on recovery mode. And be sure of the path of sdcard on recovery mode. For exemple in Nexus one it is /sdcard, in Samsung Galaxy S2 is /emmc/, in Samsung S4 mini its /sdcard/0/ ... So it could be a reason why its not in sdcard, because the path is not generic.
5. Most important, what exactly update-script do things under recovery mode? How the command executed?
=>It does lot of stufs, like mount partitions, copy system files, ...
The update-script is in elf script. Generally, an elf interpreter is given just next to the update-script.
I hope it helped you,
JHelp
1 yes, but flashing firmware from recovery can be dangerous and all though unlikely I have seen many brick there phone doing so
2. Yes, rather easily so long as the .zip is put together properly. But like bootloader, it is safest so flash through fastboot or download mode but a very unlikely brick so mostly safe
3. This is how a ROM gets built from source but it needs not be in this setup. At the same note I can't see a better way to flash through recovery than like it is. Using flash_raw_image would work but due to size a system.img shouldn't be flashed in recovery rather through fastboot, bootloader or download mode
4 mostly because you couldn't have an oem ota update without an SD card which isn't a prerequisite for using a phone. Also I believe there is some added safety flashing directly from nand, but in truth this is all speculation. Yes with a rooted phone this could be changed but most often it isn't wise to flash an oem ota on a rooted device
5 lots of things, take a look at my threads for a guide I made explaining this
1 cat /proc/partitions
mount
ls -l /dev/block/
And then keep searching until you get /by-name which many phones have, but this isn't always the same path so if you need further help ask and I'll walk you through it
2 I think this depends on a lot of things, but I don't have a good answer so rather than speculating I'll choose not to answer
Feel free to ask other questions
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
1 yes, but flashing firmware from recovery can be dangerous and all though unlikely I have seen many brick there phone doing so
2. Yes, rather easily so long as the .zip is put together properly. But like bootloader, it is safest so flash through fastboot or download mode but a very unlikely brick so mostly safe
3. This is how a ROM gets built from source but it needs not be in this setup. At the same note I can't see a better way to flash through recovery than like it is. Using flash_raw_image would work but due to size a system.img shouldn't be flashed in recovery rather through fastboot, bootloader or download mode
4 mostly because you couldn't have an oem ota update without an SD card which isn't a prerequisite for using a phone. Also I believe there is some added safety flashing directly from nand, but in truth this is all speculation. Yes with a rooted phone this could be changed but most often it isn't wise to flash an oem ota on a rooted device
5 lots of things, take a look at my threads for a guide I made explaining this
1 cat /proc/partitions
mount
ls -l /dev/block/
And then keep searching until you get /by-name which many phones have, but this isn't always the same path so if you need further help ask and I'll walk you through it
2 I think this depends on a lot of things, but I don't have a good answer so rather than speculating I'll choose not to answer
Feel free to ask other questions
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've got /by-num, but no /by-name, device is Sansumg GT-9288
not sure what a Sansumg GT-9288 is, gsmarena and google dont give me results
what happens with
cat /proc/partitions
or just
mount
?
demkantor said:
not sure what a Sansumg GT-9288 is, gsmarena and google dont give me results
what happens with
cat /proc/partitions
or just
mount
?
Click to expand...
Click to collapse
Sorry, type wrong, should be GT-9228, it's a customer made smartphone only for CMCC.
I can get the partition info by GT-9220, so I think it's because of the customer made that I can not get the by-name folder.
Thanks again.