i am attempting an sdk port with mixed sucsess with defferent methods
i have today (1/5/11) tried the port using the .36 kernel but now get stuck with a black screen no abd or the slightest signs of life :blink:
if i use origional kernel i get adb working before boot loop but if i try and run a log cat to see whats going on i get
Code:
D:\Documents\android-sdk-windows\tools>adb logcat
- waiting for device -
- exec '/system/bin/sh' failed: Exec format error (8) -
18/4/11
Gets stuck on the boot image screen
doesnt make it to boot animation
doesnt reboot
adb works
but i cant run a logcat to find out whats up?
Code:
D:\Documents\android-sdk-windows\tools>adb devices
List of devices attached
1714404540bfb617 device
D:\Documents\android-sdk-windows\tools>adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
any ideas
19/4/11
Ok so i have deleted some unused apps in system such as phone so now the system image is small enough and copies correctly
It now gets stuck in boot loop after boot image and i now have no adb
Any help welcome
20/4/11
my files are here, i dont no what to do next so go on and have a dig around if you wish
19.4-2update.zip----------------get stuck in boot loop no adb
http://www.mediafire.com/?u403ooy0mijoy4y
18.4-3update.zip----------------no boot loop but adb
http://www.mediafire.com/?isdf8wpf7d5n8pt
20/4/11
ok im a little confused not. the updater-script is the thing im least sure about but i have found a problem with it.
however when i change a load if ui_prints and some file locations and re flash it has not changed anything all the ui prints are unchanged and the problem i encountered is still their
any one know whats going on?
Click to expand...
Click to collapse
I got this message today appling a zip file into CWM 3.
Never seen it before
add.thebad said:
when i try and flash my rom in clockwork i get an error status (0) what does this mean?
Click to expand...
Click to collapse
That can mean your using the incorrect or corrupt update binary
bob1369 said:
That can mean your using the incorrect or corrupt update binary
Click to expand...
Click to collapse
Thanks i thaught i may have something to do with the update binary or script. this is my first rom how can i get a cOrrect one
Try taking one from one of the various roms for the vega but don't take the update script
Did it work?
bob1369 said:
Did it work?
Click to expand...
Click to collapse
yeah i did thanks for the help
just now it get stuck at the boot logo
doesnt get to animation or reboot but adb will work
good to here it good luck boot logo's good progress often just a few bugs from there
bob1369 said:
good to here it good luck boot logo's good progress often just a few bugs from there
Click to expand...
Click to collapse
thats good to here, just a shame i dont know where to start. could it be a problem with the update script
possible always wipe data etc trying adb logcat can reveal problems bootloops and freezes can have many causes difficult to suggest a likely fix if you have real problems i'd suggest getting help from an experienced dev
bob1369 said:
possible always wipe data etc trying adb logcat can reveal problems bootloops and freezes can have many causes difficult to suggest a likely fix if you have real problems i'd suggest getting help from an experienced dev
Click to expand...
Click to collapse
i cant get logcat to work see first post so i dont no where to start
I have this problems sometimes.. it's a problem of space in /system. You only have 105Mb in system, so bigger images dont copy all the files. In your case dont copy sh, so no shell, so no logcat or anything
Corvus.
What bootscreen do you mean black or picture
Sent from my HTC Desire using XDA App
What the Corvus said makes a lot of sense
corvus said:
I have this problems sometimes.. it's a problem of space in /system. You only have 105Mb in system, so bigger images dont copy all the files. In your case dont copy sh, so no shell, so no logcat or anything
Corvus.
Click to expand...
Click to collapse
ok thanks, so i should unyaff the system.img and delete /sh
add.thebad said:
ok thanks, so i should unyaff the system.img and delete /sh
Click to expand...
Click to collapse
Yes and no. You need to delete files so all the files fit in the system partition. Usually you can remove a handful of apps without any impact on the system.
bob1369 said:
What bootscreen do you mean black or picture
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
the cyanogen logo beacause i used the cm7 boot.img and never changer the initlogo
HomerSp said:
Yes and no. You need to delete files so all the files fit in the system partition. Usually you can remove a handful of apps without any impact on the system.
Click to expand...
Click to collapse
ok thanks, have have deleted some of the phone and sms apps and have saveed enough space, down to 92mb now
this time round it took longer to flash so i think it is copying correctly
now i get boot loop after boot logo and now i have no adb so dont know whats going on
Ok cool might restart my attempts at a port had issues with freezing sound like a similar problem had a lot in system directory on my rom
Sent from my HTC Desire using XDA App
bob1369 said:
Ok cool might restart my attempts at a port had issues with freezing sound like a similar problem had a lot in system directory on my rom
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
That would be good if we can get some more peopple working on it. I just tried because i got fed up witg all the people winging about honeycomb. Ive never made a full rom b4 only tweaked so this is a big learning curve
Hopefully will see some sucsess for all my late nights reading stuff
If any one had any advice on how to fix my boot loop i would b very happy
Related
I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!
That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App
Wait. I have a normal reboot. Maybe mine is messed up?
Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.
Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer
jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse
I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...
Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App
Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.
I have created the vendor files for the advnet vega based apon the cyanogen ones for the Gtab, and compiled CM6 for the vega. This is not supported by cyanogen's team yet as the vega isnt officialy supported by them yet so please take that into mind (dont ask for support on the cyanonen irc ect u probably wont get it) but feel free to ask support on this thred.
Nither me or the CyanogenMod team take no responsability for any damage caused bu this rom. by flashing it means u understand this risks and accept the risks.
What doesnt work :-
- Camera
- Rotation can be funny (if it works at all)
[UPDATE]
- Black Screen Of death can occur when rebooting (looking into this ASAP) so be prepared to restore
What works :-
- Every thing else (i think)
[INSTALL]
1) get the .zip file from the bottion of the post
2) copy it to SD card
3) reboot into recovery
4) MAKE NANDROID BACKUP
5) flash zip from recovery (you will get a boot write error thats normal)
6) reboot
7) DONE
[DOWNLOAD]
http://db.tt/UmV1dYK
[CREDITS]
CyanogenMod Team for there src
Bekit for the Gtab vendor this is based on
Anyone else i have forgotten
[MY VENDOR]
If anyone else wants to try and improve on this please feel free.
https://github.com/BuzzBumbleBee/android_device_vega/tree/froyo
(Please note at the current time the boot.img that the compile creates will not work on the vega to u will have to make one by extracting the original ramdisk from the boot.img)
thanks mate been tring with cyanogenmod for gtablet..gonna try now. THis bad boy vega need some action
got error message:
assert failed: package_extract_file("boot.img" ,"/temp/boot.img")
E:Error in /sdcard/CM-6.2.0-Vega.zip
(status 7)
Installation aborted.
edit: fixed.
I successfully installed, I put the original boot.img from vega into the zip, taking it for a spin now. Thanks Apache14.
I sold my Vega because of the screen imo wasnt great and the wi-fi issue.
Would have loved to have tried this rom though.
Good work !!!
Thanks to apache14 and everyone involved
How do we get market onto the tab. thanks in advance
Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)
Apache14 said:
Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)
Click to expand...
Click to collapse
thx mate, misread the first post
Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.
arad85 said:
Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.
Click to expand...
Click to collapse
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Follow the instruction paul gave on modaco.
Download the Recovery image and flash utility and extract to desktop
open terminal
adb devices to make sure your device is connected
cd to the directory of file you just extract
then type
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 4755 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
thats done.
If you on mcr 6, the vega reboot recovery is already installed if not download from the market.
cheers
alphaola said:
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Click to expand...
Click to collapse
Yes, it's very straightforward. I've done it a few times too and followed the instructions. I still get the bsod as do a number of others. Without CM installed, no bsod...
Try power cycling your Vega back-to-back using the power button. I bet you'll get it to bsod reasonably quickly.
BSOD
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon
Apache14 said:
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
Brilliant - thanks
Apache14 said:
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
arad85 said:
Brilliant - thanks
Click to expand...
Click to collapse
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Note: Do not unzip the cyanogengenmod, just use winrar to open it and copy those files into it then close it
alphaola said:
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Click to expand...
Click to collapse
Sorry, being particularly thick today. How do I get hold of the three .img files?
arad85 said:
Sorry, being particularly thick today. How do I get hold of the three .img files?
Click to expand...
Click to collapse
download the advent vega system file from advent vega website,zip it using winrar.
alphaola said:
download the advent vega system file from advent vega website,zip it using winrar.
Click to expand...
Click to collapse
<facepalm>
arad85 said:
<facepalm>
Click to expand...
Click to collapse
no stress man. Its quite smooth and fast, love the animation as well
alphaola said:
no stress man. Its quite smooth and fast, love the animation as well
Click to expand...
Click to collapse
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!
To get the market and apps
Download http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-tegra-20101020-signed.zip, then flash using rom manager. then once you reboot you should get all your apps and market. enjoy
arad85 said:
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!
Click to expand...
Click to collapse
ahahha mate,it works.
Download button savior to make navigation easy
Hello all
Really looking forward to a stable version with an idiot proof install for folks like me.
Great work
Rgds
Lok
I have been trying to for over a week in the captivate forum to get ANYONE to try and help me and so far no one will. So i'm really hoping someone will take the time, i will PAY YOU UP FRONT over paypal to help me. I am DEAD SERIOUS.
Have a captivate, but this problem is not exclusive to this phone. This error has happened on just about any/every android phone there is.
Phone was working fine, have been putting any and all custom roms on that i wanted, but went to install a new custom rom (cog4), and it fails every single time at system/xbin/su. Now ANY rom i install (custom), gives me that same error. NO CUSTOM ROM WILL INSTALL. THEY ALL FAIL. I have flashed back to stock a million times, wiped, re-partitioned the sd card, master cleared, and done all of those in every combination possible. The ONLY rom i can put on here is the one i had RIGHT before this problem started (cog3.04). Only roms that can be flashed via odin will go on my phone now. All zip files fail.
I am not a noob and know my way around a computer. I promise if someone tries to help me i will be very prompt in my responses and will try ANYTHING that you ask me to. I have been googling for over a week hours a day, i am never gonna resolve this issue unless someone with the know-how helps me Every time this topic is brought up on any forum on the internet, the problem never gets solved and it fades away....there is no answers out there. Someone who knows this stuff is my only hope
I will pay you to help me even if your troubleshooting does not work
Just out of curiosity, did you open Rom Manager once you installed it to grant it superuser rights? Also, make sure you Click the top link in Rom Manger and choose your phone. "Flash ClockworkMod Recovery"
Yes tim i have done that.
I sent you a private message -- here is the same:
Have you tried adb root - and then from / rm -rf * and see if you can wipe all clean. Ofcourse if the issue is the partition, then this won't help. Also I have never tried this - as this has never been an issue for me.
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
JoelParke said:
I sent you a private message -- here is the same:
Have you tried adb root - and then from / rm -rf * and see if you can wipe all clean. Ofcourse if the issue is the partition, then this won't help. Also I have never tried this - as this has never been an issue for me.
Click to expand...
Click to collapse
I am definitely rooted and have su permissions, but it will not let me access SYSTEM from recovery or when the phone is on. Says access denied.
xsteven77x said:
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
Click to expand...
Click to collapse
I read that post but the update-script in Cog4 doesn't have those lines. You could in theory edit the script so that it just has those three lines but I'm not sure that would be sufficient to install Cog4. That may be a question for DG.
Do you have the root explorer app?
timbrendelaz said:
I read that post but the update-script in Cog4 doesn't have those lines. You could in theory edit the script so that it just has those three lines but I'm not sure that would be sufficient to install Cog4. That may be a question for DG.
Do you have the root explorer app?
Click to expand...
Click to collapse
Yes i do 10char
xsteven77x said:
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
Click to expand...
Click to collapse
Not sure as this looks like a patch and specifically asks for no wipe. Also my knowledge is limited as to what harm you can do that will make the phone unusable -- BUT you are already into that realm . Perhaps someone with deeper specific experience can answer this????
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
timbrendelaz said:
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
Click to expand...
Click to collapse
K will report back.
Also it looks like the update.zip file is long gone....
JoelParke said:
Also it looks like the update.zip file is long gone....
Click to expand...
Click to collapse
??? 10 chars
xsteven77x said:
I am definitely rooted and have su permissions, but it will not let me access SYSTEM from recovery or when the phone is on. Says access denied.
Click to expand...
Click to collapse
using adb remount will set the /system partition as read/write. This may help.
xsteven77x said:
??? 10 chars
Click to expand...
Click to collapse
I attempted to look at the original link your posted and tried to download the patch -update.zip - which was missing on the thread. Sorry this wasn't clear.
JoelParke said:
using adb remount will set the /system partition as read/write. This may help.
Click to expand...
Click to collapse
I have been doing that within sgs tools, not the same thing?
timbrendelaz said:
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
Click to expand...
Click to collapse
Having alot of trouble getting my root explorer installed. Keeps saying parsing error UGH COME THE **** ON!!!!
JoelParke said:
I attempted to look at the original link your posted and tried to download the patch -update.zip - which was missing on the thread. Sorry this wasn't clear.
Click to expand...
Click to collapse
Oh ok sorry i didnt understand. Ty for trying regardless though.
xsteven77x said:
Having alot of trouble getting my root explorer installed. Keeps saying parsing error UGH COME THE **** ON!!!!
Click to expand...
Click to collapse
LOL, of course......
If it doesn't install, try installing Terminal Emulator from the Market
Ok so inside of the system folder they both have the permissions set to what you wrote.... .
There is only a bin in the folder right before the system folder...should there be an xbin there too?
So, I updated to 2.3.4 today, and after a rebbot into recovery, CWM was gone.
No problem, I tought, and used fastboot to flash it back.
fastboot went OK, but when I tried to use CWM from recovery, I got stucked at the "stock" recovery (android with a exclamation mark). Is anyone else facing this?
Click to expand...
Click to collapse
NVM this first part, solved that.
Also, I can´t get adb to work, tried pushing some files and got permission denied; abd remount gave me a "remount failed: Operation not permitted" error.
Yeah, having the same problem here. The 'remount failed..' error is because the update patched our boot.img and now they are no longer 'insecure.' I think I might fix it so we all can have root again. I've also had better luck when running a shell script and physically moving apps, etc to the places i want them...then have to chmod, etc...freaking sucks.
If you need any help with some workarounds shoot me a message..also have some personal scripts that get everything going
du5t3r said:
Yeah, having the same problem here. The 'remount failed..' error is because the update patched our boot.img and now they are no longer 'insecure.' I think I might fix it so we all can have root again. I've also had better luck when running a shell script and physically moving apps, etc to the places i want them...then have to chmod, etc...freaking sucks.
If you need any help with some workarounds shoot me a message..also have some personal scripts that get everything going
Click to expand...
Click to collapse
Thanks, I spent a long time yesterday trying to solve this.
Finally, I gave up and installed Root Explorer. Let me know if you have any progress with this.
Use RootExplorer after flash to rename the recovery.sh to recovery-no.sh its found in the ETC folder.
Try choosing erase recovery in the rom managers settings then flash.
kaizxclusive said:
Use RootExplorer after flash to rename the recovery.sh to recovery-no.sh its found in the ETC folder.
Try choosing erase recovery in the rom managers settings then flash.
Click to expand...
Click to collapse
Hmm, I found a install-recovery.sh, is that one?
I am not using rom manager...
gasparzim said:
Hmm, I found a install-recovery.sh, is that one?
I am not using rom manager...
Click to expand...
Click to collapse
yes, just rename it to something like install-recovery.sh.old
Bajo76 said:
yes, just rename it to something like install-recovery.sh.old
Click to expand...
Click to collapse
Thanks, looks like it´s working now.
I installed a custom boot animation and now my phone won't boot up properly. The animation won't show during boot and basically after the galaxy sIII screen, nothing is shown. The phone seems to be started okay, I hear sounds and vibration when I press buttons, but the screen just is not showing anymore.
I'm trying to boot to recovery and use adp to either delete the bootanimation.zip or push a different version, but I get the device not found error.
PLEASE HELP!!!
ned4spd8874 said:
I installed a custom boot animation and now my phone won't boot up properly. The animation won't show during boot and basically after the galaxy sIII screen, nothing is shown. The phone seems to be started okay, I hear sounds and vibration when I press buttons, but the screen just is not showing anymore.
I'm trying to boot to recovery and use adp to either delete the bootanimation.zip or push a different version, but I get the device not found error.
PLEASE HELP!!!
Click to expand...
Click to collapse
How'd you install it? Do you have a link to what you flashed?
Sent from my SCH-I535 using xda app-developers app
ajrty33 said:
How'd you install it? Do you have a link to what you flashed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but I finally got it figured out. Scarred the crap out of me for a minute there though!
I was able to run "adb push bootanimation.zip /system/media" and it works after reboot. I couldn't get it working in recovery, but was able to with the phone started like "normal".
Not sure what was wrong with the other version of the bootanimation to totally killed the screen though. The only thing I can think of is there was zip compression on. But I would have thought that wouldn't kill the entire screen like that! Dunno.
I am have execet same issue please help
ned4spd8874 said:
Thanks, but I finally got it figured out. Scarred the crap out of me for a minute there though!
I was able to run "adb push bootanimation.zip /system/media" and it works after reboot. I couldn't get it working in recovery, but was able to with the phone started like "normal".
Not sure what was wrong with the other version of the bootanimation to totally killed the screen though. The only thing I can think of is there was zip compression on. But I would have thought that wouldn't kill the entire screen like that! Dunno.
Click to expand...
Click to collapse
So I am experiencing same issue I can please be little be more detailed how you pushed the bootanimation. except command. please i am panicking i know there is a solution but i just cant seem to make it work. You help would be much appreciated. thank you!
MyMymusicIsSoHard said:
So I am experiencing same issue I can please be little be more detailed how you pushed the bootanimation. except command. please i am panicking i know there is a solution but i just cant seem to make it work. You help would be much appreciated. thank you!
Click to expand...
Click to collapse
Sorry, it's been so long I can barely remember this! I think what I did was pretty much as I described. I booted the phone up, waited for a little bit to make sure it was all the way started since I couldn't see the screen. And then plugged in the cable and performed the push command. It was pretty straight forward as long as you can ignore the fact that the screen wasn't displaying anything.
Had to flash the fireware
ned4spd8874 said:
Sorry, it's been so long I can barely remember this! I think what I did was pretty much as I described. I booted the phone up, waited for a little bit to make sure it was all the way started since I couldn't see the screen. And then plugged in the cable and performed the push command. It was pretty straight forward as long as you can ignore the fact that the screen wasn't displaying anything.
Click to expand...
Click to collapse
So my Debugging mode was off so I could not use adb push command, I had to do a complete firmware flash, that got my phone to work but lost all my data on the phone. but still a happy camper.
Thank you for prompt response, all your help it's much appreciated.
I had the same problem but with an ASUS memo pad hd7. I downloaded a bootanimation.zip that was the wrong orientation, so I unzipped it, rotated all the pictures rezipped and placed it back in /system/media/. Mistake! After that the device would not boot! At least that's what I thought until a quick google search led me here, thanks for your help! My situation was a little different, i'll explain my journey below in case it helps others with similar situations.
Installed minimal ADB and Fastboot from here http://forum.xda-developers.com/showthread.php?p=42407269 . I already had the device drivers installed on my computer so I skipped that step. Luckily I had USB debugging selected, however, I had never used ADB and had not given it SU permissions on the tablet. I input the following code into adb:
adb shell
cd /system/media/
ls
This verified that the offending bootanimation.zip was in there. I then tried to remove the offending bootanimation.zip with this command
rm bootanimation.zip
It failed because system was mounted as Read Only and I could not change it because I did not have SU permissions so I hit the power button on my tablet to wake it up, blindly swiped to get through the lock screen, and typed this into ADB to request Super User permissions
su
I then blindly tapped near the middle of my screen. After a few tries I successfully hit the right spot at the right time and granted SU to ADB
Once that was done I remounted system as read write and deleted the offending file with this code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
rm bootanimation.zip
ls
After verifying that bootanimation.zip was gone, I rebooted the tablet and was greeted with success in the form of some generic Android boot animation.
Same thing with my Panasonic p11 and I have a password for SuperSU so I am stuck pls help
I would suggest flashing a backup from before the custom boot animation. Then taking more cautious steps the next time you try.
To avoid this kind of unpleasantness, whether for changing the boot animation or anything else, here's a few tips:
always root your phone
It's your phone, you should have access to everything, shouldn't you? That's like buying a new car and the dealer won't give you a key for the trunk.
always use a custom ROM
Stock ROMs are usually bloated with apps you don't need and can't uninstall. Also, stock ROMs often disable features and access either "for your own good" or to keep the interface simpler. Case in point, neither of the stock ROMs that came with my Galaxy S4 or my Atrtix HD allowed me to customize the LED notification light. Whatever defaults they picked, that's what I got. A flashing green light meant I received "something" (text or email). There are a variety of 3rd party ROMs out there ready to flash for a specific device, find one that you like.