Hello, can anybody please upload the build.prop file along with the default.prop in root.
Would you also provide the permissions.
I am having problem because i cannot boot up my phone after having edited these files, and cannot use flashtool because flashtool needs to read these files in order to flash roms.
I have also tried CWM to install .zip but i receive status 7 error.
I only want to flash back to stock and cherish my pictures and videos, please help me. i want to cry and cry and cry.....
I only need the default.prop and build.prop and the permissions please
MeraVeer said:
Hello, can anybody please upload the build.prop file along with the default.prop in root.
Would you also provide the permissions.
I am having problem because i cannot boot up my phone after having edited these files, and cannot use flashtool because flashtool needs to read these files in order to flash roms.
I have also tried CWM to install .zip but i receive status 7 error.
I only want to flash back to stock and cherish my pictures and videos, please help me. i want to cry and cry and cry.....
I only need the default.prop and build.prop and the permissions please
Click to expand...
Click to collapse
Permissions are 644 or -rw-r--r-- see http://linuxcommand.org/lts0070.php
Owner root:root
MyroLM said:
Permissions are 644 or -rw-r--r-- see http://linuxcommand.org/lts0070.php
Owner root:root
Click to expand...
Click to collapse
Thank you very much for replying, the permissions are same for both files?
And for "644" permissions is same as "0644" right? Need confirmation for both of the files
And can you please also advise me what to do next also.
644 both of them. 0644 is the same as 644
MyroLM said:
644 both of them. 0644 is the same as 644
Click to expand...
Click to collapse
Okay i have done that, now what is the ownership i dont understand, what command do i need to enter for both files? kindly give me the code please
chown root:root default.prop
chown root:root /system/build.prop
MyroLM said:
chown root:root default.prop
chown root:root /system/build.prop
Click to expand...
Click to collapse
I tried that, but tools still do not identify my device shows as "Unknown - [date manufactured of software]"
Code:
Current device : Unknown: Apr 17 2013/13:56:34 - CB5123RGBE - Unknown: Apr 17 2013/13:56:34 - 1262-6309_9.1.A.1.141 - Unknown: Apr 17 2013/13:56:34
Which ROM are you using?
MyroLM said:
Which ROM are you using?
Click to expand...
Click to collapse
Stock 4.1.2 9.1.a.0.141, which may have been delelted as it showed no OS installed and system has 450 MB.
If you are able to flash recovery, flash CWM, boot info recovery, mount internal storage and SD card, recover your files and flash stock FTF file.
Related
I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?
top_bunk said:
I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?
Click to expand...
Click to collapse
You probably have SLCD screen. Then you have to use Amon_RA 1.8.0.1 recovery which is only one (as far as i know) intended for SLCD screens.
Ah okay. Is there an easy way for me to flash that? Not really comfortable with the SDK approach...
Thanks for the fast reply btw
If you don't have unlocked bootloader you have to use flash_image binary to flash new recovery because amon_ra 1.8.0.1 recovery don't show up in rom manager.
Download it from here http://cyanogen-files.carneeki.net/flash_image.zip. Put it in root of sdcard as well as 1.8.0.1 img file and in phone terminal type
1) cd /sdcard
2) flash_image recovery 1.8.0.1.img (replace with name of img file)
houmles said:
2) flash_image recovery 1.8.0.1.img (replace with name of img file)
Click to expand...
Click to collapse
I'm getting flash_image: not found
I've double checked the file name is correct
Did you unpack the zip file? There is only one file named exactly "flash_image" so you should not getting not found error if you have that file in root of sdcard and you are at /sdcard in terminal.
Send me output of "ls -la" command from /sdcard.
----rwxr-x system sdcard_rw 17638414 2010-09-10 20:20 gapps-hdpi-20100817-signed.zip
----rwxr-x system sdcard_rw 70864056 2010-09-10 20:22 update-cm-6.0.0-N1-signed.zip
----rwxr-x system sdcard_rw 11818685 2010-09-10 21:05 FRF50-radio-4_06_00_12_7.zip
----rwxr-x system sdcard_rw 4145152 2010-09-10 23:10 recovery.img
----rwxr-x system sdcard_rw 26172 2009-10-03 18:07 flash_image
Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>
Jack_R1 said:
Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>
Click to expand...
Click to collapse
./flash_image: permission denied
top_bunk said:
./flash_image: permission denied
Click to expand...
Click to collapse
Weird. Try:
1) su
2) cd /sdcard
3) chmod +x flash_image
4) ./flash_image recovery file.img
Well, that's because SD card isn't a good place to put flash_image. Permissions inherited from FAT32 are awkward and aren't changeable. But there's a way around it.
Do the following sequence: run Terminal, enter the following commands:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>
houmles said:
3) chmod +x flash_image
Click to expand...
Click to collapse
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
It didn't work...
Jack_R1 said:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>
Click to expand...
Click to collapse
cp: not found
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
I just thought of the same thing
Installing Astro now (it's a new phone no apps!)
Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
ah, didn't know that
Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
As Jack wrote, you can only copy the file manually with some file explorer.
houmles said:
As Jack wrote, you can only copy the file manually with some file explorer.
Click to expand...
Click to collapse
It won't let me copy it... I've tried Astro and ES.
Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.
If you have adb connection you can try this:
unpack zip I sent you and recovery.img to root of c:\ for example .. then:
1) adb push c:\flash_image /data/flash_image
2) adb push c:\recovery.img /data/recovery.img
3) adb shell
4) chmod 755 /data/flash_image
5) /data/flash_image recovery /data/recovery.img
Jack_R1 said:
Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.
Click to expand...
Click to collapse
Lots
...but it's done! Thanks a lot for the help guys
I've gotta be up in a few hours so I don't have time to install a ROM and faff about, but hopefully it will be all good from here on in.
Cheers again!!
First ....THANKS @letama, and last but not least thanks to @tRAcE3k for .ext4 build.
Official Stock Firmware v3.2.79 => ROOT, Update : Su binary v3.0.3.2, Superuser v3.0.7 and busybox v1.19.3, Add : enables vibrator and adjust volume !
(There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/ - only for .ext4)
This ROM is only for SDE enable ( recovery) ....you can use it as a daily ROM...
These are the files you need :
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/archive/6Y9sMqJ5/initramfscpio.html
- archos_3.2.79.squashfs => http://www.4shared.com/zip/-vo5gkRr/firmware_3279squashfs.html (...version without busybox and update!)
- archos_3.2.79.ext4 => http://www.4shared.com/zip/dmrcBtJM/3279_updat.html
How install this :
- connect device via USB cable
- adb push archos_3.2.79.squashfs data/media/ ........for read-only /system
- adb push archos_3.2.79.ext4 data/media/..............for read-write /system and other stuff
- reboot into recovery , Recovery System-> Developer Edition Menu -> Remove Kernel ( for boot only to SDE) -> I Understand -> Ok -> Developer Edition Menu -> Flash Kernel and Initramfs -> copy zImage and initramfs into new driver -> Ok ! that's all
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
letama said:
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
Click to expand...
Click to collapse
old firmware (3.2.77 etc) must be removed manually from device?
ext link is invalid "......". ciao ;-)
gegabit said:
old firmware (3.2.77 etc) must be removed manually from device?
Click to expand...
Click to collapse
When everything works, yes, you can remove the previous .ext4 from internal storage. That's the only thing you have to remove.
hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
now its upload to share.
- archos_3.2.79.ext4 => /.......future upload ..... it's 512Mb ext4...........
Click to expand...
Click to collapse
Hi Folks.
Thought I'd do my bit. Here are some more sources to download the ext4 firmware.zip
http://www.multiupload.com/0OTX0D54XW
Thanks to surdu_petru for the original image and tRAcE3k for the repacking instructions in this post.
Thanks
Trev
hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
[email protected] sure is right....on the ather hand, every new firmware ( ex. firmware_archos_it4.aos) has its own boot image ( boot.img = zImage + initramfs) -used to boot devices and has its own flash files / system files which are grouped in an archive ( contains - libraries, aplikations, and other stuff ) - used to run system android , and all these are closely linked ....I think you can now better understand how to use them, and why ......
hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
Ok...Now is valid link : http://www.4shared.com/zip/bp7XjWzY/archos_3279ext4.html....
Good luck!
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
droobey said:
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
Click to expand...
Click to collapse
Ok! Now just upload new update .....
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
revere521 said:
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
Click to expand...
Click to collapse
OK! Try >adb shell chmod 6755 system/bin/su
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
.....after install all....try to update Superuser into Market......
Update doesn't help :-(
surdu_petru said:
.....after install all....try to update Superuser into Market......
Click to expand...
Click to collapse
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
basd82 said:
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
Click to expand...
Click to collapse
OK I know.....just wait max 1 hour and I'll uploaded the new archos_3.2.79 files...with it everything works perfectly ( I have tested all , root_explorer, es file explorer, Root Check ....it's OK !!!!!).
basd82 said:
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
Click to expand...
Click to collapse
ok! but now problem was solved.....just redownload the new firmware_3.2.79 files , unpack and enjoy*
I have mis-deleted the Home.apk, and meet a black screen after unlocking the devices.
May I ask you for uploading the Home.apk in the stock 4.21?
Thanks a lot in advance.
How do you plan on installing it if you have no launcher? (its launcher.apk, not home.apk.)
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
AW: [HELP]Missing the Home.apk
UltimaClaud said:
I have mis-deleted the Home.apk, and meet a black screen after unlocking the devices.
May I ask you for uploading the Home.apk in the stock 4.21?
Thanks a lot in advance.
Click to expand...
Click to collapse
You could try to download nova launcher with the play store Web interface. If that won't work, open a stock rom and search for launcher2.apk or take it from a custom rom then install it with adb install.
Sent from my Nexus 7
As the above poster said, "Launcher2", not Home.
The type of things you are doing - altering things in /system - is exactly the sort of activity that you prepare for inevitable mistakes by making full Nandroid backup of your ROM ahead of time.
Didn't make a backup? Live and Learn; now you know why they are useful.
If you have a backup, save your current ROM to a full Nandroid backup, restore the good backup, and pull the launcher2 .apk and .odex files out of the /system partition from that. Then restore your borked ROM backup and put them in place into /system using ADB and the recovery, e.g.
C:\foo> adb shell
# mount /system
# mount /sdcard
# cp /sdcard/Launcher2.apk /system/app/Launcher2.apk
# cp /sdcard/Launcher2.odex /system/app/Launcher2.odex
# chmod 644 /system/app/Launcher2*
# chown root.root /system/app/Launcher2.*
# sync
# umount /system
# exit
C:\foo> adb reboot
FWIW (nakasi JOP40D 4.2.1 stock):
[email protected]:/mnt/foo/app# ls -l Launch*
-rw-r--r-- 1 root root 12190703 2012-11-19 16:55 Launcher2.apk
-rw-r--r-- 1 root root 549816 2012-11-19 16:55 Launcher2.odex
[email protected]:/mnt/foo/app# md5sum Launcher2.*
934eb033d26cd2c7aaabc4f0759e9fa7 Launcher2.apk
73c6281e2ec601bd1181d588a72070a5 Launcher2.odex
since its rooted, I assume you have a custom recovery flashed? if so, download your exact ROM as a flash able .zip to a computer and copy that to your tablet. reboot into recovery and dirty flash it.
or do a factory reset and a advanced restore of data only.
Or you could simply flash the stock system.img in fastboot.
Sent from my Nexus 7 using Tapatalk HD
I've been trying to flash a nandroid backup that I downloaded as a zip file via clockworkmod.
I've placed the nandroid zip in the clockworkmod/backup folder, but when I go to restore in clockworkmod it is not seen (only a backup I made earlier).
I pushed the .zip via adb into the /mnt/shell/emulated/clockworkmod/backup/ directory.
Any ideas how to get this to work? I need to return to stock for an insurance claim.
Thanks for any help!
can you do this using ADB ?
adb shell
cd /mnt/shell/emulated/clockworkmod/backup/
ls -la
what is your output?
If there is an error above, try cd /data/media/clockworkmod/backup/
or cd /data/media/0/clockworkmod/backup/
SaHiLzZ said:
can you do this using ADB ?
adb shell
cd /mnt/shell/emulated/clockworkmod/backup/
ls -la
what is your output?
If there is an error above, try cd /data/media/clockworkmod/backup/
or cd /data/media/0/clockworkmod/backup/
Click to expand...
Click to collapse
Output was:
Code:
drwxrwx--- root sdcard_r 2014-02-10 21:27 2014-02-10.21.23.00
drwxrwx--- root sdcard_r 2014-02-12 20:10 2014-02-12.20.04.30
-rw-rw---- root sdcard_r 1034657679 2014-02-11 00:22 ruu.zip
Still can't see the ruu.zip file that I want to restore when I'm in clockworkmod. Is it because it's a .zip or a permission error? I presume the others are folders.
1. Wrong folder location. Evident by no other folders.
2. You can NOT restore ruu.zip file. It need to be unzipped and the content pushed to a new folder
SaHiLzZ said:
1. Wrong folder location. Evident by no other folders.
2. You can NOT restore ruu.zip file. It need to be unzipped and the content pushed to a new folder
Click to expand...
Click to collapse
Thanks, I got it to show up.
Next problem however, is a MD5 mismatch. No knowledge on how to fix this, if possible. Are you aware?
Thanks again
Maybe an older cwm version. Sorry can't help. But there maybe an option to skip md5 check if you are certain you have right file
sent from my mobile device
SaHiLzZ said:
Maybe an older cwm version. Sorry can't help. But there maybe an option to skip md5 check if you are certain you have right file
sent from my mobile device
Click to expand...
Click to collapse
No worries, thanks though. Ended up flashing a different stock rom instead. Removed tampered, relocked and s-on. Finally.
Alright.. I wanted the Note 8 version of gallery and i went into system/app folder and deleted the SecGallery2_Galaxy.apk but before deleting i saw that its size was 0.00 kb lol ..
But when i tried tried to copy and pasted in the extsd it pasted and showed 13mb..
Now i deleted the file and copied the Note 8 Galley and pasted in the system/app folder only to get an error " Operation failed " and i realized only 7 mb free space is there in the partition by going into the android emulator!
Now i also found out that, full size SecGallery2_Galaxy.apk was in the preload partition and i instead of replacing that i deleted the file in system/app..
Now how do i get back that file in system/app?.. is that what they call deodexed file?.. Please help..
Thanks a lot in advance
Just copy it from other rom, that You can explore with winrar.
Sent from galaxy n7105
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
nokiamodeln91 said:
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
Click to expand...
Click to collapse
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
CustomRomAddicts said:
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
Click to expand...
Click to collapse
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
nokiamodeln91 said:
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
Click to expand...
Click to collapse
It says read only file system
I even changed the permission of the file in preload to 644 ( rw-r--r-- )
still the same message?.. any idea what it might be?.
Thanks in advance
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
nokiamodeln91 said:
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
Click to expand...
Click to collapse
Honestly i just now searched in google for adb shell and it says to run windows but when i download and double click the adb.exe it runs and exits!.. Please help..
Will mounting the preload and system in recovery and rebooting the device and running the script again in android emulator work?..
Keep in recovery and mount both.. Then run....
nokiamodeln91 said:
Keep in recovery and mount both.. Then run....
Click to expand...
Click to collapse
I tried in adb shell too.. but its not working
Do u guys have the symlink file?.. can u share with me?.. will it work?..
Thanks in advance
Oh Yeah! SOLVED IT!!
I installed Root explorer and created symlink via that and Voila it worked!
Although i dont know why when i open a photo in gallery i experience FC!