Hi,
I am trying to flash a new ROM to my Samsung Galaxy S5830i, but unfortunately, I can't use either Recovey Mode, or Download Mode.
When I try to access Download Mode, it simply boots in as nothing happened. (I tried to access Download Mode by pressing Vol Up + Vol Down + Power)
When I try to access Recovery Mode, I can't move with the volume buttons, but the home button does work (and it reboots the phone). It says, "Applying Multi-CSC", but nothing happens, I tried to leave it there for 1 hour, but nothing changed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried the following soultions, but none of them solved the problem:
I rooted the phone, and tried using Terminal to flash CWM as recovery.IMG, as this tutorial suggests:
Launch terminal emulator
Change user as superuser, type
$su
the $ symbol wil change to #
Mount and change the permission
# mount -o remount rw /system
Concatenate flash_image files and set the permission.
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
Install the CWM recovery
# flash_image recovery /sdcard/recovery.img
set back the permission for /system and reboot
# mount -o remount ro /system
# reboot recovery
Click to expand...
Click to collapse
It got stuck on installing the CWM recovery:
I tried to access Download Mode with ADB using the "reboot download", but the phone rebooted normally, not in Download Mode.
Any suggestions, on how to access Download Mode or fix the Recovery Mode, so I can flash a new ROM to the phone?
Related
I'm on SGS 3 (I9300) with freshly installed I9300XXDLIH_I9300VFGDLJ1_VIP and rooted afterwards.
Since I upgraded my phone to Jelly Bean, I can't test/debug any development project on the phone.
The Eclipse APK build passes OK and this is what I get in the step afterwards -- when the APK is tried to be deployed on the phone:
Code:
Installation failed due to invalid APK file!
Please check logcat output for more details.
Launch canceled!
This is what I get when I try installing directly with ADB:
Code:
>adb install -r test.apk
3484 KB/s (1616779 bytes in 0.453s)
pkg: /data/local/tmp/test.apk
Failure [INSTALL_FAILED_INVALID_APK]
I've found some hints that the tmp folder may have invalid permissions, so I have done this:
Code:
chmod 777 /data /data/local /data/local/tmp
With the result:
Code:
[email protected]:/ # ls -ld data data/local data/local/tmp
ls -ld data data/local data/local/tmp
drwxrwxrwx system system 2012-10-23 15:40 data
drwxrwxrwx root root 2012-08-25 10:40 local
drwxrwxrwx shell shell 2012-10-23 16:36 tmp
Eclipse or ADB still refuse to install (any) APK.
If I copy the Eclipse-generated APK to the phone and initiate the install from there, it works OK.
What can I do to fix this? Please help.
FYI, I'm using 20.0.3 Android SDK (and Eclipse 4.2.1).
My system properties:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update:
Installed SiyahKernel S3-v1.6.8 and w/o any tampering with the settings (e.g. through ExTweak) the problem is solved.
Root cause seems to be UMASK.
- on stock kernel I had 0077
- now on SiyahKernel I have 0000
Still, as can be seen from numerous other threads on the same issue out there, it's very wrong for the stock kernel to cause that problem.
Moved to Android Q&A.
Hi everyone,
First of all, I would like to wish Merry Christmas to the Community Members...
Secondly, I am stuck on a very irritating problem: Read Only File System
I Rooted my phone, Flashed CWM 6.0.3.1 a month ago. Since then, I tried various ROMs here and I found this problem in all ROMs I've tried. Basically, I am not able to Change my System Files.
I tried ES File Explorer to overwrite but it says: Permission Denied!
I tried all File manager, but failed!
I tried mount -o remount,rw /system but neither it changed the permissions, nor it gave any error in Terminal.
I used Terminal and tried the chmod command, but it says Read Only file system
I tried to make a Flashable ZIP using this method, but even this doesn't change the files.(No, it does not show any error while flashing the zip through CWM)
Actually, I was trying to overwrite the boot animation, but the thing is that my whole system seems to be Read Only.
So, I would like to ask for help regarding this.
Thank You
Best Regards,
THAKUR
SCREENSHOTS BELOW
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
flashed roms. ..? ehh is your bootloader unlocked...?
second it looks like a root problem . try this method to gain root again (if you're already rooted ,then go to supersu and in settings do permanent unroot) ,it roots your phone in 28~35 seconds ,
http://forum.xda-developers.com/showthread.php?t=2511695
Ok. So the problem was solved on the same time as I posted this thread.
What worked for me:
When I tried mount -o remount,rw /system, I was still not able to Fix permissions through ES File Explorer. Then, When I tried mount -o remount,rw /system 2 times, and then I used the Default File manager(Cyanogen File Manager) to change permissions, it was working.
Ok. So the problem is solved now.
Thread can be marked as SOLVED :good:
Anuj, Thanks though
Dear all,
I've used device name EBEN T4 (e人e本 T4 - from china). I rooted device and deleted/modified system. So, now it can not boot, it stuck at manufacter logo. I wiped data/factory reset or wipe cache but not success. So it need to be reflashed device roms.
Device allowed me to enter recovery mode and select update rom from zip file on SDCard (internal memory). I saved zip file on SDCard. BUT SDcard have so many folders and files in root folder, and zip file names "update.zip" - it means that it is on near last of list, and recovery limited number of line to view, so i could not browse to update file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device has Vol +/-, home, left, right, back, menu and power button. (Home + Power will bring me to recovery mode)
Device use CPU Freescale i.MX535, android 2.3.4, origional recovery system.
Please suggest me how to fix that by anyway.
P/S: I found that Back + Power will bring me to fastboot interface?
Need help so much
That's why you should backup your system before rooting etc. Do you have a stock image of your device?
eagleeyetom said:
That's why you should backup your system before rooting etc. Do you have a stock image of your device?
Click to expand...
Click to collapse
Thank you for reply.
This is stock image: http://update.eben.cn/t4/update.zip
I found that my device could enter fastboot mode by press back + power button.
When connect usb, screen show:
[fastboot mode]
fastboot is in init......
fastboot transfer buffer: 0x0000000
flash <1 word i cant recoginze> is MMC: 1
USB Mini b cable Connected!
fastboot initialized
USB_SUSPEND
USB_RESET
USB_RESET
Windows device Manager (on WIndows 7 32bit) shows that device connect (ADB), i'm used to use many ADB universal driver (google, ClockworkMod). When i used "fastboot devices" command, it reponsed nothing.
Could i connect to fastboot to update file update.zip to device? If ok, how i connect?
Fastboot will give you nothing, mate. Try to set up the ADB and use adb sideload <path/to/zip> without "<>" or delete folders in recovery by going to adb shell and changing the dir by cd command and removing them by rm -r foldername.
Good luck.
RECOVERY 3e Recovery Modded w/ No Verification :highfive:
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Click to expand...
Click to collapse
Instructions
1)Download and extract the file here
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
Click to expand...
Click to collapse
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great thread. I've extracted 3e recovery from vivo xshot. Can you explain me how disable security check? This phone don't have recovery file in system/bin but I've found a way to open bootloader
Nice App....
The file link is broken.
Hi Jawad Twam,
Very useful. I am also trying the same on my samsung galaxy S5. However, I could not download your recovery file since the link is broken. Can you please upload the file in somewhere and share the link?.
Thanks in adv,
Prakash.
Hi I get a message "operation not permitted" in the terminal emulator after typing the line. How can I fix that?
All I want to achieve is to pull subfolders ( DCIM etc.pp ) of Android's /data/media folder what successfully got mounted as RW
To access /data partition you need root permission which is adb root
But most devices would refuse to run this command, in which case you need to install adb insecure mode. You can get that from here.
After installing the app switch to insecure mode. Then pull command should work.
Alternatively you can use adb shell to work around it:
Code:
adb shell
su
mkdir /sdcard/media
cp -R /data/media/* /sdcard/media
exit
exit
adb pull /sdcard/media
Notes:
The "*" in "/data/media/*" stands for all, which copies all files in current directory. If you want specific file just replace it with "filename.extension"
The option "-R" in "cp" command stands for recursive which copies directories, and will copy all files in respective directories as well.
Thanks for trying to help: Unfortunately your solutions don't work at all.
FYI:
I use /data/local/tmp for intermediate storage ( permissions: rwxrwxrwx )
I can successfully copy /data/media/<SUBFOLDER> to /data/local/tmp/<SUBFOLDER> ( permissions rw-rw-rw- )
All copied files have permission rw-rw-rw-
When applying ADB PULL on /data/local/tmp/<SUBFOLDER> I still get error "Access denied" even if having additionally set owner of all
files in /data/local/tmp/<SUBFOLDER> to shell.shell and/or root.shell and/or shell.root and/or root.root
It's working fine with me, but I used /sdcard as the copy folder.
Like I said you can only access /data partition with root. You can try the first method mentioned above.
As mentioned none of your suggestions solved the problem.
1, ADB Insecure obviously doesn't work on Android 8+ devices, hence useless
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Temporarily copying to /sdcard in my case is useless too, because /sdcard is merely a symlink to /data
So you can't even use pull command on /sdcard partition?
I only found this answer, that may be similar https://android.stackexchange.com/a/213172