Related
A few weeks ago my SD card went bad on me. I have been using Gingershedbread as my ROM and see there are some updates, however, since I don't have an SD card, the "normal" method of loading the zip onto the SD card obviously won't work for me.
My question is: Is there a way to flash a ROM zip from a pc (windows) to my phone without an SD card? I know you can put the zip on the data partition, then use "recovery --update_package=DATA:rom.zip" (through adb), however, when trying to copy the rom I get a message saying that there is no space left.
As of now, the only thing I know of is to do a full wipe and factory reset, then push the ROM zip to my phone, but I don't necessarily want to do this every time.
I have also tried fastboot and using mkyaffs2image to create a system.img from the ROM's system folder in the zip file, but I am not doing something right.
I run "mkyaffs2image c:\rom\system\ c:\system.img"
then with my phone in fastboot, I "fastboot flash system c:\system.img"
and "fastboot flash boot c:\rom\boot.img".
I restart the phone in recovery mode, load gapps and xtrCache, but then it reboots, sits on black screen for a few seconds, then reboots into recovery.
I have tried erasing system and boot first, but that didn't seem to help.
I first tried just flashing system.img, but that didn't work.
Not sure what I am doing wrong. Is there a way to take a ROM zip and create a system.img and boot.img that can be flashed through fastboot without an SD card? OR, is it possible to flash a ROM zip without transferring the file to my phone first? Any help would be appreciated.
I don't think that there is an answer to your question which is both complete and also short.
So, here goes with the long answer.
First, a yaffs2 image file (e.g. system.img) is not compressed, so it is quite large - for things like the HTC factory/stock ROMs, it can be bigger than the cache partition. I don't know if the cache partition is actually used when you push things with fastboot, but experimentally, I have run into the problem that when attempting to do a
Code:
fastboot flash system my-yaffs2-system.img
fastboot gives you get an error about being out of room.
Second, and more importantly, the file modes (permissions) and user:group ownership of files in the /system mount point are extremely critical to proper operation of Android. If you have files sitting on a Windoze machine filesystem (either FAT32 or NTFS), all this information will be lost even before you create your "yaffs2" image file. (Not only that, but all symbolic links will be missing, too). This is why you observe that ROM files have instructions in their "update-script" (or "updater-script") command files for setting file & directory ownership, file permission modes, creating symlinks, et cetera.
Third - even if you use a linux OS to unpack yaffs2 images, and run as root when you are doing so, a lot of the "unyaffs" programs that are lying around do not even bother to extract things like user:group ownership or file modes - so you are basically screwed as soon as you unpack a yaffs2 image file on a PC, no matter whether it is Windows or Linux/Unix/OS-X.
Fourth, I am not sure that it is even a good idea in the first place to be "flashing" yaffs2 images. The "fastboot flash" command merely writes whatever you pass to it as a long linear blob of bytes, and there is no evidence to suggest that the yaffs formatting used in the archive is the same formatting used by the kernel. When "Nandroid" runs to restore a system.img or data.img file onto the phone, it does not write the image as a linear blob of bytes: it actually mounts the filesystem in question, cleans it up with a "rm -rf *" command, and then manually unpacks the yaffs2 image file into the mounted file system, one file at a time. (Fortunately in this case, it actually restores things like symlinks, file permissions, and file/directory user:group ownership information). This insures that the low-level yaffs2 formatting is *identical* to what the kernel expects, because it is the kernel that creates it.
There is a solution, but it is tedious enough that you really ought to ask the question, "Why don't I go out and buy a replacement SD card for 10 bucks instead of wasting a huge amount of time?"
Here's the solution:
You mount /system, clean it up manually, use adb to push the files recursively from wherever you have them stored on your PC, and then afterwards you run a custom (signed) installer .zip file which has been modified so that it only contains the "symlink" and permission-setting commands - you delete the "format" and "extract" commands from that command file, since you have manually put all the files into /system. Either that or you manually adjust the permissions and user:group ownership information by hand.
Obviously, since you don't have an /sdcard any longer, you will need to put this flashable, custom .zip file in /cache, and then create a one-line command file at /cache/recovery/command that points at the flashable .zip file in /cache. (This is the way the the OTAs work, and also how ROM Manager is able to customize the recovery when it boots).
Is this a lot of work? Yeah, you betcha.
It seems like running down to wally world to get a cheap SD card might be a little more fun.
Thanks for the info. I figured getting a new SD would be the best solution.
I knew about the symlink and file permission stuff and was trying to flash a system img then run a zip to ser that info., but couldn't get it to work. Sounds like using fastboot might be a bad idea.
For now I think I will just have to find a rom and stick with it for a while.
I am nearing an upgrade for a new phone and looking at the Thunderbolt, which comes with an SD so I don't want to buy one just yet.
Thanks for your help.
Sent from my ERIS GSBv2.1 using XDA App
kgunnIT said:
then run a zip to ser that info., but couldn't get it to work.
Click to expand...
Click to collapse
If you know how to sign ROMs, it's really not a hard hack to launch an installer of the type you mention.
And, now that I've just said that, I think I have another, simpler, idea.
But first:
[SIZE=+2]How To Launch a (smallish) .zip-based Flash That's Not On the SD Card.[/SIZE]
All of the recoveries - both the stock and custom recoveries - look for a "command" file when they first start up.
It literally is named "command", i.e.: /cache/recovery/command
... and it is a simple text file with as few as one line(s) in it.
Here is an example from the most recent OTA of the contents of /cache/recovery/command:
Code:
--update_package=CACHE:8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
basically, it's just a single line with the following format:
--update_package=CACHE:filename.zip
So, if you are trying to get an installer to run without an SD card, you would:
1) Boot to Amon_RA
2) Wipe the cache if necessary (wipe -> wipe data/factory reset also clears /cache)
3) Push your zip file to cache:
Code:
adb push mycustominstall.zip /cache/
4) Create a command file (say, named "command.txt") with the contents:
Code:
--update_package=CACHE:mycustominstall.zip
5) Push it to the phone:
Code:
adb push command.txt /cache/recovery/command
6) reboot directly back into recovery with
Code:
adb shell reboot recovery
When the recovery boots up again, it will immediately start unpacking your "mycustominstall.zip" file.
After I thought this all the way through, I realized, though: a lot of the ROM files are only about 100 MB, and cache is about 128 Mb, so
.... wait for it .....
... wait for it ....
it might be a worthwhile experiment to just push an untouched ROM file right to cache and then use that ROM file's name in your "command" file.
So long as /sbin/recovery does not unpack files to /cache (I can't remember if it does this or not!), you could use original ROM files -- just what you wanted originally. If it unpacks things to cache, though, it will only get part way through the install and fail.
It's worth a shot; if it fails, you'll have a mess that is no worse to clean up than what you've presently got. (If it fails, to be on the safe side it might be wise to go in using adb and clean things up in /cache a little bit so that the next recovery boot has some wiggle room in /cache - e.g. "adb shell rm -rf /cache/*" )
bftb0
bftb0 said:
If you know how to sign ROMs, it's really not a hard hack to launch an installer of the type you mention.
And, now that I've just said that, I think I have another, simpler, idea.
But first:
[SIZE=+2]How To Launch a (smallish) .zip-based Flash That's Not On the SD Card.[/SIZE]
All of the recoveries - both the stock and custom recoveries - look for a "command" file when they first start up.
It literally is named "command", i.e.: /cache/recovery/command
... and it is a simple text file with as few as one line(s) in it.
Here is an example from the most recent OTA of the contents of /cache/recovery/command:
Code:
--update_package=CACHE:8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
basically, it's just a single line with the following format:
--update_package=CACHE:filename.zip
So, if you are trying to get an installer to run without an SD card, you would:
1) Boot to Amon_RA
2) Wipe the cache if necessary (wipe -> wipe data/factory reset also clears /cache)
3) Push your zip file to cache:
Code:
adb push mycustominstall.zip /cache/
4) Create a command file (say, named "command.txt") with the contents:
Code:
--update_package=CACHE:mycustominstall.zip
5) Push it to the phone:
Code:
adb push command.txt /cache/recovery/command
6) reboot directly back into recovery with
Code:
adb shell reboot recovery
When the recovery boots up again, it will immediately start unpacking your "mycustominstall.zip" file.
After I thought this all the way through, I realized, though: a lot of the ROM files are only about 100 MB, and cache is about 128 Mb, so
.... wait for it .....
... wait for it ....
it might be a worthwhile experiment to just push an untouched ROM file right to cache and then use that ROM file's name in your "command" file.
So long as /sbin/recovery does not unpack files to /cache (I can't remember if it does this or not!), you could use original ROM files -- just what you wanted originally. If it unpacks things to cache, though, it will only get part way through the install and fail.
It's worth a shot; if it fails, you'll have a mess that is no worse to clean up than what you've presently got. (If it fails, to be on the safe side it might be wise to go in using adb and clean things up in /cache a little bit so that the next recovery boot has some wiggle room in /cache - e.g. "adb shell rm -rf /cache/*" )
bftb0
Click to expand...
Click to collapse
You always find the one thousand and ONETH way to skin a cat. Hehehehe...
Thankyou so much for this this alowed me to flash a rom on my phone which can't detect any sd cards and i stupidly wiped it before relising the sd card wasnt being detected!
sum_guy55 said:
Thankyou so much for this this alowed me to flash a rom on my phone which can't detect any sd cards and i stupidly wiped it before relising the sd card wasnt being detected!
Click to expand...
Click to collapse
very good, sum_guy55!
At least all that typing wasn' t in vain.
Out of curiosity, how big was the ROM file you used?
bftb0
Been meaning to post this:
Thanks for your posts roirraW "edor" ehT and bftb0 for posting this. I also was able to clear the cache and push the ROM and update.
However, I have xtrCMCache2cache on my phone, so the dalvik-cache was moved from /data/ to /cache/. After doing a wipe of dalvik-cache from Amon recovery, the folder in /cache/ was not emptied out. I went ahead and cleaned it manually, which freed up enough space to push the ROM.
Is this behavior expected using cache2cache and wiping dalvik-cache from recovery? I guess it would be since the dalvik-cache was moved.
Anyway, after clearing the dalvik folder, I was able to push GSBv2.4 to my phone, as well as gapps and xtrCMCache2cache, a total of almost 80 MB. Rebooted and all was well.
Thanks again for your help.
kgunnIT said:
Been meaning to post this:
Thanks for your posts roirraW "edor" ehT and bftb0 for posting this. I also was able to clear the cache and push the ROM and update.
However, I have xtrCMCache2cache on my phone, so the dalvik-cache was moved from /data/ to /cache/. After doing a wipe of dalvik-cache from Amon recovery, the folder in /cache/ was not emptied out. I went ahead and cleaned it manually, which freed up enough space to push the ROM.
Is this behavior expected using cache2cache and wiping dalvik-cache from recovery? I guess it would be since the dalvik-cache was moved.
Anyway, after clearing the dalvik folder, I was able to push GSBv2.4 to my phone, as well as gapps and xtrCMCache2cache, a total of almost 80 MB. Rebooted and all was well.
Thanks again for your help.
Click to expand...
Click to collapse
It was all bftb0. Interesting, I had once asked if cache was definitely wiped from Amon after it was moved. The consensus was that it should. I shall be anticipating some light shed on this.
Sent from my Gingerbread Eris via Tapatalk
Well, Amon_RA has no idea whether you are using cache2cache; I suppose we would need to look at the code to figure out how it behaves.
If it mounts /data and then does something like
rm -rf /data/dalvik-cache
there is a chance that the symbolic link is not followed, which would explain what kgunnIT observed.
Normally, if you are flashing a new ROM in a full-wipe fashion, the " wipe data/factory reset" menu option clears both /data and /cache, so in that case it is irrelevant that the "wipe dalvik-cache" is a no-op.
If you are overflashing, it's not obvious that you need to wipe the dalvik-cache... at least for the market apps normally stored in /data/app, although it seems like it would be a good idea to do so, as the system apps could be changing.
Note that even when cache2cache is not in use, the Amon_RA menu item "wipe dalvik-cache" never works as intended for froyo & gingerbread ROMs - the system apps have their dalvik-cache stored in /cache, and this never gets touched by Amon_RA with that menu operation.
BTW... for what it's worth, the ClockworkMod recoveryhas a menu entry for wiping only the cache.
bftb0
bftb0 said:
BTW... for what it's worth, the ClockworkMod recoveryhas a menu entry for wiping only the cache.
bftb0
Click to expand...
Click to collapse
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
kgunnIT said:
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
Click to expand...
Click to collapse
There is a version of Amon_RA (the trackball-optional version) that also allows you to format cache. You can find out more about it here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
That said, if you have ROM Manager, you can have Clockwork Recovery start as a stub within Amon_RA just from ROM Manager (the first option copies a file called update.zip to the root of your SD card, and the second, "Reboot into Recovery", starts Amon_RA with a script to flash update.zip, which starts Clockwork.) In fact, once update.zip is on the SD card, you can start Amon_RA as you always do, go to the Flash a zip from SD card menu, choose update .zip, and it will start Clockwork, if you want to do it that way. However, the drawback to this is that you can't go back to Amon_RA without shutting down the phone and then restarting in Recovery again, so I just find it easier to use the trackball-optional version of Amon_RA.
I think every person who has bricked their Eris while running Clockwork was running Clockwork Recovery as their main recovery image, and not in the way that I described in the last paragraph. (Though don't hold me to that ...)
kgunnIT said:
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
Click to expand...
Click to collapse
I've been using it through ROM Manager since last August or so, I use it all the time.
I was on a hunt to make this work without losing any data and I've figured out a way that works quite nice, and all it involves is a TWRP backup, ADB, and a bit of commandline.
Thanks to TrevE for his ever evolving tweaks to Android and for making them readily available to the community at the cost of one thanks per post, and maybe a beer or two (how many people really buy beer with donations?!)
Required:
TWRP backup
ADB
The EXT4 tweaks for /data
The EXT4 tweaks for /system
(If your ROM doesn't already have them, I will be providing the zips for them courtesy of Synergy.)
Step 1:
Connect your phone to your PC and like all things of this nature, BACKUP! Use TWRP to create a nandroid of your entire phone. We will need this backup to restore data and system via commandline. TWRP is the only tested method that works, since it creates backups that are actually TAR files (God, I love TWRP for this). Stay in recovery after completing backup.
Step 2:
While still in recovery, enable USB storage mode and download the two EXT4 files below (or applicable if your ROM already has one of the partitions optimized) onto the root of your microSD card. To make things easier, you can temporarily move your data.win and system.win files to the root of your microSD card. They are located in the TWRP folder on your microSD card. Afterward, disable USB storage mode.
Next, there are TWO ways to accomplish this. Choose which way you want to go before continuing.
Method 1: Reflash your ROM(NOT RIGHT NOW, later on in the guide--depending on ROM, this may format your /system and/or data partitions, rendering the tweaks useless.)
Method 2: Use commandline to restore your ROM from TWRP backup.
Step 3:
From recovery, wipe dalvik and cache and format data and and depending on method, your system partitions as well. NOTE: formatting the partitions can be done from TWRP in the advanced menu.
Step 4:
Flash the applicable EXT4 file.
Step 5:
Mount /data, /system, (if applicable), and /sdcard with TWRP and launch an ADB shell by typing "adb shell" then press enter while in your ADB folder from command prompt/terminal.
Step 6:
Type "cd /sdcard" and press enter. To make sure you're in your sdcard, type "ls" then press enter to verify that it's listing your microSD card contents.
Step 7:
Type "cd /data" and press enter. To make sure you're in /data, type "ls" then press enter to verify that it's empty. It will probably contain a lost+found folder, if so then that's fine.
Step 8:
If you moved your data.win and system.win backups to the root of your microSD card to make this easier, simply type "tar xvpf /sdcard/data.win" then press enter and it will begin extracting the backup file onto the /data partition. Otherwise, you will have to type "tar xvpf /sdcard/TWRP/nameofHTCfolder/nameofdatefolder/data.win" then press enter. This will take a few minutes to complete.
NOTE: MAKE SURE YOU ARE IN THE /DATA PARTITION BEFORE TYPING THAT COMMAND, OTHERWISE THINGS WILL GO WRONG.
Step 9:
Either reflash your current ROM (checking to make sure it doesn't format /system before installing) OR type "cd /system" then press enter. To make sure you're in /system type "ls" then press enter to verify that it's empty. It may contain another folder, if so that's fine. It should however be empty of ROM related files.
Step 10:
If you moved your data.win and system.win backups to the root of your microSD card to make this easier, simply type "tar xvpf /sdcard/system.win" then press enter and it will begin extracting the backup file onto the /system partition. Otherwise, you will have to type "tar xvpf /sdcard/TWRP/nameofHTCfolder/nameofdatefolder/system.win" then press enter. This will take a few minutes to complete.
NOTE: MAKE SURE YOU ARE IN THE /SYSTEM PARTITION BEFORE TYPING THAT COMMAND, OTHERWISE THINGS WILL GO WRONG.
Step 11:
Once this is all complete, exit ADB shell by typing "exit" then pressing enter. Next, unmount /system, /data, and /sdcard from TWRP and head on over to the fix_permissions option in TWRP and let it run. It will take a few minutes to complete.
Step 12:
Go ahead and wipe dalvik and cache again just to make sure, then reboot.
It will take a while to boot back into android, but if all goes well, you should have your data intact with fully optimized EXT4 partitions thanks to TrevE/Synergy.
NOTE: This worked for me, and if you follow the guide precisely, it should work for you too.
NOTE2: I did not try this method with /system, ONLY data, and it worked fine. I assume the same for /system as well.
Awesome! I as many others are appreciative of Team Xposed and how you explain mods to everyone. Most of the time we get a .zip with no explanation on how the .zip is doing what it does. We just know flash this and this happens, lol. With these breakdowns we all get a better understanding on how things work in our devices
Perhaps a sticky with all Team Xposed mods/tweaks, that would be
I believe this is what i used the last time i flashed synergy. If so, then it works great.
Wow the step by step was GREAT!! Man I did this in like 5 minutes....Granted it took me about 30 minutes to download all the tools I needed. Thanks for this one!!
Edit: So how do you know it truly worked?? How do I check if I am ext4 or not?
wow. I had EXT4 on my samsung phones and I LOVED it compared to this! I will definitely try this and make a video on my success or failure! lol
so what if i didnt care to lose data could i flash this with another rom.
Ok. So just trying to gain a better understanding here. So say if the rom were running already includes the /system tweaks but not the /data tweaks and the rom doesn't erase on flash can I just flash both of the files and flash the rom?? Also if I wanted to apply the tweaks to and existing nand can I just flash both the files and do a nand restore??? Or is restoring the data from the command line needed in order for the tweaks to work effectively???
Locked & Loaded
" Shooter on Deck "
Great write up, thanks for that!
Not to be a party pooper, but isn't there a tweaked version of the EXT4 optimized zip that backs up data to sd card, formats /data with ext4, then auto restores /data for you? I found it somewhere in the Synergy thread.
Correct me if im wrong if this does something more/different.
here is a link to it:
Synergy_Format_Data_EXT4_Optimized_apps_autorestored.zip
http://forum.xda-developers.com/attachment.php?attachmentid=708982&d=1315062399
I used it to go from Warm2.3 to Steel2.3 without any issues what so ever, except having to restore XDA app, wifi/bt networks and some widgets. It kept all my screens and settings just the way i like it. YMMV! i take no credit, and assume no responsibility if it rips your phone a new one.
Our phones are already ext4, the optimization just turns on some more features for ext4.
And the tool linked before me doesn't backup everything in /data... It should probably work, but if it misses anything this method will catch it
I just took the opportunity to wipe clean and reset some things.
Sent from my PG86100 using XDA App
youngpro83 said:
Wow the step by step was GREAT!! Man I did this in like 5 minutes....Granted it took me about 30 minutes to download all the tools I needed. Thanks for this one!!
Edit: So how do you know it truly worked?? How do I check if I am ext4 or not?
Click to expand...
Click to collapse
Good question. I suppose you could run a few Quadrant benches to ease your mind. You should get much better scores than you would normally. I suppose the only real way to know for sure is if someone created an EXT4 tweak checker of some sort lol. But the Quadrant benchmark should be enough, that is if you remember what kind of scores you were getting before hand.
digitalcrash said:
so what if i didnt care to lose data could i flash this with another rom.
Click to expand...
Click to collapse
Glad you asked! If you don't care about losing data, just go ahead and format your system and data partitions with TWRP or whatever recovery you use, then apply the tweaks zips and go ahead and flash the ROM of your choice. You should double check the updater-script of your ROM to make sure it doesn't reformat the /system partition or it will render the /system tweak useless.
laie1472 said:
Ok. So just trying to gain a better understanding here. So say if the rom were running already includes the /system tweaks but not the /data tweaks and the rom doesn't erase on flash can I just flash both of the files and flash the rom?? Also if I wanted to apply the tweaks to and existing nand can I just flash both the files and do a nand restore??? Or is restoring the data from the command line needed in order for the tweaks to work effectively???
Locked & Loaded
" Shooter on Deck "
Click to expand...
Click to collapse
Well, if the ROM you're running already contains the /system tweaks then you're half-way there. You still want a backup though, because each of these zips will format its respective partitions. You only want the zip that applies. In your case, you'd only need the data tweaks, but you'd still have to follow the guide that pertains to restoring your data partition after tweaking.
MFD00M said:
Great write up, thanks for that!
Not to be a party pooper, but isn't there a tweaked version of the EXT4 optimized zip that backs up data to sd card, formats /data with ext4, then auto restores /data for you? I found it somewhere in the Synergy thread.
Correct me if im wrong if this does something more/different.
here is a link to it:
Synergy_Format_Data_EXT4_Optimized_apps_autorestored.zip
http://forum.xda-developers.com/attachment.php?attachmentid=708982&d=1315062399
Click to expand...
Click to collapse
Glad you linked that. I actually looked over this yesterday, and while it does do something similar to this guide, It actually only restores part of your data partition, which is why it's said that you will need to repair your bluetooth devices and reenter your WiFi network settings. IIRC, it doesn't restore the entire data partition, just most of the important folders. If it were to do the entire partition, well, this guide would be much shorter.
freeza said:
Glad you linked that. I actually looked over this yesterday, and while it does do something similar to this guide, It actually only restores part of your data partition, which is why it's said that you will need to repair your bluetooth devices and reenter your WiFi network settings. IIRC, it doesn't restore the entire data partition, just most of the important folders. If it were to do the entire partition, well, this guide would be much shorter.
Click to expand...
Click to collapse
Thanks for clearing that up, i will try your method as well. I need more ADB exposure to help me learn.
so my next question is if the rom does format system on boot then i would install with adb as your guide says?
digitalcrash said:
so my next question is if the rom does format system on boot then i would install with adb as your guide says?
Click to expand...
Click to collapse
Yup...pretty much.
Thank you for this. I was able to apply this without any issues.
freeza said:
Yup...pretty much.
Click to expand...
Click to collapse
What would be the process if I didn't care about losing data? Would I just flash, and resign into my Google account and go through that process again?
LiquidSolstice said:
What would be the process if I didn't care about losing data? Would I just flash, and resign into my Google account and go through that process again?
Click to expand...
Click to collapse
If you don't care about losing data, you'd format/wipe the data and system partition from recovery, apply both ext4 zips... wipe dalvik+cache, reflash your ROM, and reboot
Keep in mind that this is pretty much the same process as factory reset, so you might as well just perform one of those lol
freeza said:
If you don't care about losing data, you'd format/wipe the data and system partition from recovery, apply both ext4 zips... wipe dalvik+cache, reflash your ROM, and reboot
Keep in mind that this is pretty much the same process as factory reset, so you might as well just perform one of those lol
Click to expand...
Click to collapse
So just to be clear, all that I need to do is before I flash a ROM, Superwipe/XRON wipe like I always do, flash the ROM, flash the EX4 zips, and then clear dalvik/cache and boot?
LiquidSolstice said:
So just to be clear, all that I need to do is before I flash a ROM, Superwipe/XRON wipe like I always do, flash the ROM, flash the EX4 zips, and then clear dalvik/cache and boot?
Click to expand...
Click to collapse
You wanna flash the zips before flashing ROM, as they format the partitions with the tweaks. You also want to double check the updater-script of your ROM to make sure it doesn't format the /system partition before installing, as it would remove the tweaks.
Soo..
Superwipe/XRON
EXT4 tweaks
ROM
No need to wipe anything as Superwipe/XRON already does this.
freeza said:
You wanna flash the zips before flashing ROM, as they format the partitions with the tweaks. You also want to double check the updater-script of your ROM to make sure it doesn't format the /system partition before installing, as it would remove the tweaks.
Soo..
Superwipe/XRON
EXT4 tweaks
ROM
No need to wipe anything as Superwipe/XRON already does this.
Click to expand...
Click to collapse
EXT4 before ROM?
Bear with me, I'm still a bit confused :X. Wouldn't flashing a ROM after the EXT4 data/system zips negate the zips' function?
LiquidSolstice said:
EXT4 before ROM?
Bear with me, I'm still a bit confused :X. Wouldn't flashing a ROM after the EXT4 data/system zips negate the zips' function?
Click to expand...
Click to collapse
lol no problem.......Well, what the tweaks does is format the system and data partitions a certain way as to improve io functions and other stuff. It's like formatting a drive in Windows with cluster switches etc. It's still empty once you flash the tweaks. The ROM simply puts all the information on the newly formatted filesystem. If you were to apply the tweaks after flashing the ROM, it would format the partitions and erase all data, which is why you do it first. The updater-script in ROMs also have the ability to format partitions, which is why in Synergy ROMs, simply flashing their ROM also applies the tweak and which is why you should check your updater-script beforehand to make sure it doesn't have a format command in it, as it would negate the tweaks.
Im trying to install cm 10.1 on galaxy player 5,0 international. But i get error 7 in cwm,so i edited updater-script.i deleted asserts..and now im getting error 6. This can be fixed by installing cm9 or some ics rom before jb? or i need to edit updater-script in notepad++ because unix codes.?? it would be easier for me just to flash cm9 first.
momirsarac said:
Im trying to install cm 10.1 on galaxy player 5,0 international. But i get error 7 in cwm,so i edited updater-script.i deleted asserts..and now im getting error 6. This can be fixed by installing cm9 or some ics rom before jb? or i need to edit updater-script in notepad++ because unix codes.?? it would be easier for me just to flash cm9 first.
Click to expand...
Click to collapse
Just flash this first, without loading the ROM. Enter again on CWM, wipe all but your SD/Internal memory (/cache, dalvik, /data, /datadata or something, /system, /system_app, but not emmc or sd_card) and flash CM10.1. Next flash the INTL kernel if you are not using an US version and flash GAPPS. Reboot and you are done.
A simple personal hint to get a better experience: After you get into CM, set the screen DPI on 160. If you don't like this kind of "tablet mode" set it on 161 or 162
zardak said:
Just flash this first, without loading the ROM. Enter again on CWM, wipe all but your SD/Internal memory (/cache, dalvik, /data, /datadata or something, /system, /system_app, but not emmc or sd_card) and flash CM10.1. Next flash the INTL kernel if you are not using an US version and flash GAPPS. Reboot and you are done.
A simple personal hint to get a better experience: After you get into CM, set the screen DPI on 160. If you don't like this kind of "tablet mode" set it on 161 or 162
Click to expand...
Click to collapse
i already flashed cm9 and then jb.. its working.. but now i tried to change dpi to 160 and it seems like we're talking about different versions or something because now i stuck and boot logo.. not animation. can i somehow change dpi withoud reflashing rom or something so i dont lose all my apps and data installed.
momirsarac said:
i already flashed cm9 and then jb.. its working.. but now i tried to change dpi to 160 and it seems like we're talking about different versions or something because now i stuck and boot logo.. not animation. can i somehow change dpi withoud reflashing rom or something so i dont lose all my apps and data installed.
Click to expand...
Click to collapse
No different version.
You clearly put some garbage on build.prop file OR used a incompatible 3rd party app.
I'd suggest to do it manually even because is not so hard.
Be carefull when trying to modify this file, even a single character (eg. blank space) can mess the device. Just delete the 3 characters ("240") and replace with "160".
The easiest way to get back the device is to reflash the ROM but if your data are too important do the followings:
1) Boot into CWM and connect the device to PC.
2) On "mounts and storage" mount /system.
3) Install ADB drivers on windows if you don't have them.
4) Check if ADB is working by typing "adb devices" without quotes on windows command prompt. You must see something like c501025b1278a9f recovery. If you get an error from that command you don't have adb installed correctly OR you are not in the adb.exe folder OR you didn't set up correctly the environment variable.
5) Get a clean copy of build.prop, you can extract it from the ROM.zip/system
6) Type "adb push PATH_OF_CLEAN_BUILD.PROP_ON_WINDOWS /system" without quotes, this will replace the bad build.prop with the clean one. For example, if you have build.prop on C:\ the command is: adb push C:\build.prop /system
7) Fix Permissions.
8) Done.
momirsarac said:
i already flashed cm9 and then jb.. its working.. but now i tried to change dpi to 160 and it seems like we're talking about different versions or something because now i stuck and boot logo.. not animation. can i somehow change dpi withoud reflashing rom or something so i dont lose all my apps and data installed.
Click to expand...
Click to collapse
alternatively, you could wipe /system and reinstall then wipe cache and dalvik and you should be fine
also, please refrain from creating threads with questions that should be posted in the Q&A
thanks
zardak said:
No different version.
You clearly put some garbage on build.prop file OR used a incompatible 3rd party app.
I'd suggest to do it manually even because is not so hard.
Be carefull when trying to modify this file, even a single character (eg. blank space) can mess the device. Just delete the 3 characters ("240") and replace with "160".
The easiest way to get back the device is to reflash the ROM but if your data are too important do the followings:
1) Boot into CWM and connect the device to PC.
2) On "mounts and storage" mount /system.
3) Install ADB drivers on windows if you don't have them.
4) Check if ADB is working by typing "adb devices" without quotes on windows command prompt. You must see something like c501025b1278a9f recovery. If you get an error from that command you don't have adb installed correctly OR you are not in the adb.exe folder OR you didn't set up correctly the environment variable.
5) Get a clean copy of build.prop, you can extract it from the ROM.zip/system
6) Type "adb push PATH_OF_CLEAN_BUILD.PROP_ON_WINDOWS /system" without quotes, this will replace the bad build.prop with the clean one. For example, if you have build.prop on C:\ the command is: adb push C:\build.prop /system
7) Fix Permissions.
8) Done.
Click to expand...
Click to collapse
Well then its because i used some dpi changing app from play store. Btw i restored everything by formating /system and flashing rom again without wiping cache,dalvik or data. and now its ok. so if set it to 160 i get tablet mode? Real tablet mode or what? Thanks btw for help.really.thanks.
momirsarac said:
Well then its because i used some dpi changing app from play store. Btw i restored everything by formating /system and flashing rom again without wiping cache,dalvik or data. and now its ok. so if set it to 160 i get tablet mode? Real tablet mode or what? Thanks btw for help.really.thanks.
Click to expand...
Click to collapse
I don't know if is the "real tablet mode" you think, but is kinda different than on >160 dpi.
For example, when you install an app, the window is not full screen; the same happens on google play store;
Some in-app buttons like "refresh" or "menu" are labeled (eg. Battery menu).
I use this dpi settting only because everything is smaller and there is more room, i don't care so much about this sort of tablet mode.
As I said is a personal opinion, you can reset at anytime. Just do it manually by opening /system/build.prop with ES File Explorer; scroll untill you find "ro.sf.lcd_density=240", delete 240 and replace with 160; save and reboot.
Another advice: when you aren't 100% sure on what you are doing do always a nandroid backup on CWM, if something goes wrong restoring this backup can save you a LOT of time.
Hello, i think i made a big mistake, on my phone with root explorer i was unable to mount / and then i tried to mount /system into read only, i remember that i ticked "owner" "group" and "other" but only on read, and my phone just freezed and now the screen is on but it is black and the navigation buttons are on too, please help me
skip
Go to twrp, mount system, go-to inbuilt file manager and chmod 755 the system folder and reboot, or Dirty flash the firmware will do the job.
Next time, do nand-backup before perform sny changes to system. or would be better don't messed up with root partition.
R324D said:
Go to twrp, mount system, go-to inbuilt file manager and chmod 755 the system folder and reboot, or Dirty flash the firmware will do the job.
Next time, do nand-backup before perform sny changes to system. or would be better don't messed up with root partition.
Click to expand...
Click to collapse
You are sure it is going to work ?
Yakia said:
You are sure it is going to work ?
Click to expand...
Click to collapse
Lol
I don't know man, you could try. I'm not a magician...
Soooo little info you provided, I don't know what device you mentioned above? Rooted/unrooted? Custom rom/stock rom? Twrp installed/uninstalled? Almost zero info :laugh:
But basically, yes it'll work. Just do it..
R324D said:
Lol
I don't know man, you could try. I'm not a magician...
Soooo little info you provided, I don't know what device you mentioned above? Rooted/unrooted? Custom rom/stock rom? Twrp installed/uninstalled? Almost zero info :laugh:
But basically, yes it'll work. Just do it..
Click to expand...
Click to collapse
I actually have twrp installed and fully functionnal, but the phone won't boot on os, when i try to boot, it always shows me recovery, and i precise that in /system there is no file, its empty, i don't know why but when i go to storage info i see that the system partition takes 4gb why ? If in file explorer /system is empty, why system takes 4gb ? Maybe it's not really empty ? Anyway i just need help please
Yakia said:
I actually have twrp installed and fully functionnal, but the phone won't boot on os, when i try to boot, it always shows me recovery, and i precise that in /system there is no file, its empty, i don't know why but when i go to storage info i see that the system partition takes 4gb why ? If in file explorer /system is empty, why system takes 4gb ? Maybe it's not really empty ? Anyway i just need help please
Click to expand...
Click to collapse
I tried to help you here, but clearly you didn't read my previous comment.
Boot into TWRP (you said you have it installed), and you have to MOUNT SYSTEM first, or it'll just show you an empty folder without file.
R324D said:
I tried to help you here, but clearly you didn't read my previous comment.
Boot into TWRP (you said you have it installed), and you have to MOUNT SYSTEM first, or it'll just show you an empty folder without file.
Click to expand...
Click to collapse
Where do i mount system ? Sorry if i'm maybe annoying i just want to be sure that i will not fail
Yakia said:
Where do i mount system ? Sorry if i'm maybe annoying i just want to be sure that i will not fail
Click to expand...
Click to collapse
Just boot into twrp, you'll see mount menu as soon as you enter the twrp recovery. Enter mount and check system.
R324D said:
Just boot into twrp, you'll see mount menu as soon as you enter the twrp recovery. Enter mount and check system.
Click to expand...
Click to collapse
When i tick system, i have no "mount" button, i only have a "disable mtp" button, why ? I can give you screens if you want
Hello.
I've installed viper4android on my mido. Everything is ok, but there is a background static sound when music is being played. According to the viper FAQ I need to delete /system/lib/soundfx/libbundlewrapper.so. What did I do:
1. Mount system as rw
adb shell
su
mount -o rw,remount,rw /system
2. try to rename that file
cd /system/lib/soundfx
mv libbundlewrapper.so libbudnlewrapper-2.so.bak
3. No success. Trying to create backup in a file manager and than trying to delete it. Still no luck. Changed system to ro and I'll wait for suggestions.
The file is there like I haven't done anything. The uncharted territory of the system partition still awaits for me. What I can do next to get the thing to work?
Rust3dCor3 said:
Hello.
I've installed viper4android on my mido. Everything is ok, but there is a background static sound when music is being played. According to the viper FAQ I need to delete /system/lib/soundfx/libbundlewrapper.so. What did I do:
1. Mount system as rw
adb shell
su
mount -o rw,remount,rw /system
2. try to rename that file
cd /system/lib/soundfx
mv libbundlewrapper.so libbudnlewrapper-2.so.bak
3. No success. Trying to create backup in a file manager and than trying to delete it. Still no luck. Changed system to ro and I'll wait for suggestions.
The file is there like I haven't done anything. The uncharted territory of the system partition still awaits for me. What I can do next to get the thing to work?
Click to expand...
Click to collapse
What rom do you use? Miui or los/aosp? Also do you use, magisk or super su? Plus, please tell how did u Install viper, that is through recovery or by using magisk?.
MyNameIsRage said:
What rom do you use? Miui or los/aosp? Also do you use, magisk or super su? Plus, please tell how did u Install viper, that is through recovery or by using magisk?.
Click to expand...
Click to collapse
I use Official and final RR
The phone uses magisk and viper was flashed by magisk (should I remove the module and flash as non-system app?)
Rust3dCor3 said:
I use Official and final RR
The phone uses magisk and viper was flashed by magisk (should I remove the module and flash as non-system app?)
Click to expand...
Click to collapse
Why don't you use es file manager? I just tried i was able to do it with es.
MyNameIsRage said:
Why don't you use es file manager? I just tried i was able to do it with es.
Click to expand...
Click to collapse
Still does not work. I have no idea what to do. Again.
Renaming the file does not go despite a Toast is visible "Rename Successful" and while deleting there is "Device or resource busy"
Rust3dCor3 said:
Still does not work. I have no idea what to do. Again.
Renaming the file does not go despite a Toast is visible "Rename Successful" and while deleting there is "Device or resource busy"
Click to expand...
Click to collapse
Why don't you try deleting it from twrp.
MyNameIsRage said:
Why don't you try deleting it from twrp.
Click to expand...
Click to collapse
I tried. The funny part is that I can only see /system/usr. No other folder is in /system. Thats why I've posted this topic. I'm just lost.
Rust3dCor3 said:
I tried. The funny part is that I can only see /system/usr. No other folder is in /system. Thats why I've posted this topic. I'm just lost.
Click to expand...
Click to collapse
Nope, you haven't mounted system in twrp, that's the reason you are only seeing /usr
So do this
From main menu, select "mount" and there select System, also make sure that the "system" box is checked and the box saying "mount system partition as read only" is unchecked(I've attached a screenshot for reference). Now you can easily go to /system and it should list the files and folders., And you can delete the file you want. Quote me if you need more help
MyNameIsRage said:
Nope, you haven't mounted system in twrp, that's the reason you are only seeing /usr
So do this
From main menu, select "mount" and there select System, also make sure that the "system" box is checked and the box saying "mount system partition as read only" is unchecked(I've attached a screenshot for reference). Now you can easily go to /system and it should list the files and folders., And you can delete the file you want. Quote me if you need more help
Click to expand...
Click to collapse
I can't believe how stupid I am. Thank You for Your advice.