Related
Anybody heard anything about when the ruu might be released? i rooted my phone and removed some of the sprint apps which i guess removed my stock 4g splash screen when the device boots.
Wow, the EXACT SAME THING happened to my phone. The only thing is, I didn't remove my stock boot splash screen animation. It just disappeared after I did the permanent root method. All I hear is the stock boot splash screen animation sound but see nothing but a black screen. I also removed some programs thinking that a factory reset would bring them back but that didn't happen. They are permanently gone. Hopefully, someone can post an RUU factory image file for the epic.
i didn't remove my stock splash screen either it just went away after i rooted and removed some sprint apps. Mine does the exact same thing you describe.
Yup, I was thinking of returning the phone to sprint for an exchange but in my opinion, that's not reason enough to return it. I'll just wait till someone hopefully releases a factory rom/image for the phone.
If you used the joeykrim root method or the one click root it moved the logo file and replaced it with a script that is keeping your phone rooted.
Sent from my SPH-D700 using Tapatalk
ahh thanks
I tried the instructions to reverse the root process to make the phone the way it was before root but I still do not get the animation screen back. Does it permanently delete the file.
Samsung phones dont use RUU. the stock tar or tarball has been released. the sprint logo goes away because playlogo turns into a script like someone else said. if you dont want/need root anymore you can pull the playlogo file from stock system dump and replace the script with the original using the adb explot.
Sent from my SPH-D700 using Tapatalk
Thanks for the helpful info. Do you know where I can find the stock system dump or the tar file?
edit:nvm, got it. Thanks again.
Sorry for noob question but how would one get back to a completely stock phone by using the stock tar? do you load it through the recovery manager? thanks in advance
i do not think what you guys are saying about root is true. I rooted using Joeykrims method, and i still have the Sprint 4G splash screen, even after deleting some stock sprint apps. Maybe you guys are doing something extra that is not neccessary...
There's a thread that has a tar file containing the epics firmware, my question is how do we flash it
ImSoHungry said:
i do not think what you guys are saying about root is true. I rooted using Joeykrims method, and i still have the Sprint 4G splash screen, even after deleting some stock sprint apps. Maybe you guys are doing something extra that is not necessary...
Click to expand...
Click to collapse
I'm not sure what I'm doing wrong but evidently, I'm not the only one since others are reporting the same thing. I followed his thread step by step. I copied and pasted all the commands as he had them. All I know is that my animated splash screen is gone but the sound is still there. The splash screen is there, however, when I power the phone off.
http://forum.sdx-developers.com/epic-development/successful-odin-v3-flash!!!/
here is how to return to full stock, who says we need recovery
2.0t03speed said:
Anybody heard anything about when the ruu might be released? i rooted my phone and removed some of the sprint apps which i guess removed my stock 4g splash screen when the device boots.
Click to expand...
Click to collapse
Alright OP, I solved the issue. I now have permanent root with my start up animation. Here's where I believe we went wrong. The file called playlogo is what's used to trigger the exploit which should be 114 bytes in size. What joeykrim's root method does is it renames the original playlogo (14.09kb in size) file in the system\bin to playlogo-orig. Then makes the os read the playlogo-orig for the animation instead of the playlogo. What I think we did was we ran the root method 2 or more times and by doing that, it took the 114 byte playlogo file that joeykrim included and renamed it to playlogo-orig so we had playlogo and playlogo-orig as identical files in the system\bin (both were 114 bytes)so there was no boot animation. What I did was I pulled the original playlogo file from the system dump and pushed it to the system\bin location, then ran the root again and now I have a playlogo file that is 114 bytes and a playlogo-orig that is 14.09kb. Look in your system\bin folder, I bet you that both the playlogo-orig and playlogo files are the same size.. 114 bytes. If you need the original playlogo file, I attached it here.
rose1 said:
Alright OP, I solved the issue. I now have permanent root with my start up animation. Here's where I believe we went wrong. The file called playlogo is what's used to trigger the exploit which should be 114 bytes in size. What joeykrim's root method does is it renames the original playlogo (14.09kb in size) file in the system\bin to playlogo-orig. Then makes the os read the playlogo-orig for the animation instead of the playlogo. What I think we did was we ran the root method 2 or more times and by doing that, it took the 114 byte playlogo file that joeykrim included and renamed it to playlogo-orig so we had playlogo and playlogo-orig as identical files in the system\bin (both were 114 bytes)so there was no boot animation. What I did was I pulled the original playlogo file from the system dump and pushed it to the system\bin location, then ran the root again and now I have a playlogo file that is 114 bytes and a playlogo-orig that is 14.09kb. Look in your system\bin folder, I bet you that both the playlogo-orig and playlogo files are the same size.. 114 bytes. If you need the original playlogo file, I attached it here.
Click to expand...
Click to collapse
Woot i got it fixed all i did was take the file you posted rename it to paylogo-orig put it on my sd card and then move it over and replace it with root explorer. Thanks again!
rose1 said:
Yup, I was thinking of returning the phone to sprint for an exchange but in my opinion, that's not reason enough to return it. I'll just wait till someone hopefully releases a factory rom/image for the phone.
Click to expand...
Click to collapse
Good luck trying to return a phone with "voided warranty" by rooting the phone. "Root=Voided Warranty." I'm a Sprint tech and I have had many people call and ask if rooting any of the Android phones would void the warranty, answer is yes so be careful.
Oni,
with enough careful measures it is very easy to remove all traces of ever having rooted in the first place. That is like custom roms on windows mobile, I sent in so many WM devices for advanced exchanges some even with the hacked SPL on them and sprint couldn't have cared less.
I don't know because I haven't tried it yet but what about a full factory reset? It's under settings privacy. Another idea I haven't tried yet is getting into one of the programming screens (I forgot the ##numbers# + msl) and do a FULL phone reset. I don't know if the same programming numbers work on different model and manufacturer's phones but there was something that said how to do this in the evo section. It was posts about people trying to trick the phone and tower to give the 1.40 PRI. I was lucky when I bought my epic, the girl gave it to me no problem (my msl).
I can say that all factory reset does is erase all data. If you want to flash back to stock the directions in the link to sdx posted above will work. I used it earlier myself.
Sent by an Epic 4g through the cosmos
So I have a Samsung Galaxy Europa I5500L (Running 2.2 android)
Im wanting to remove my carrier name from the pulldown bar and the lock screen.
I have successfully pulled framework-res.apk using adb into my pc.
I then edited it, and changed a few things to do with eri.xml (carrier name), and saved it.
However, I cant get adb to 'push' the framework back into the phone, even with su permissions, even with usb debugging on, and yes its rooted, and yes the adb connection works fine normally
SO I came to the conclusion that I could use root explorer to put the framework file back into my phones system.
This is way Im going to do it is this.. copy the modified framework-res.apk it to my SD card, then inside my phone copy the file across to the phones system area using the root explorer app (making sure that the system is R/W). Im thinking this will obviously replace the existing framework-res.apk
However, Is this safe? Ive read about people doing it before but it doesn't seem right to replace a system file whilst the phone is up and running
Can I have some clarification whether or not this will be fine or not?
Thanks...
bump
any response would be welcomed , im really stuck here!
Your phone might not boot afterwards, so unless you have a custom recovery dont do that.
Sent from my T-Mobile myTouch 3G using XDA App
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted!
I copied the modified 3e recovery into the correct place and rebooted. I than downloaded rom mngr and installed i9000.
I get that error message when I boot into clockworkmod.
what am i doing wrong? Thanks.
I have samsung infuse 4g ATT.
You're skipping ahead. Go back to 3E, drop the modded 3E recovery in the right location, reboot into recovery, install packages (twice, if necessary), and then you can work on getting CWM.
Thankfully I got it to work.! Thanks.
I am having the same issue. When I dropped the modified 3e into the phone and tried to copy and paste it in it replaced my old recovery even though I renamed it. I am thinking this was a mistake? Other then that I when I am in recovery I re-install packages and get the verification error.
jnwhatle said:
I am having the same issue. When I dropped the modified 3e into the phone and tried to copy and paste it in it replaced my old recovery even though I renamed it. I am thinking this was a mistake? Other then that I when I am in recovery I re-install packages and get the verification error.
Click to expand...
Click to collapse
Did you have the system directory mounted to allowed R/W? If you don't allow that, it won't change anything. I would suggest renaming the old recovery file and then pasting in the modified one. Don't just paste it over the other one. This way you know the process completes properly.
Remember to set the read/write privileges though or it won't work.
Depending on what your plans are, you could always use Odin to go back to stock with the modified recovery preinstalled if you use h8rift's Odin files that are available in Development.(Mind you this method will wipe all of your system files though and put you back to stock. So, if you are wanting to keep what you have, but just modify the recovery, I would suggest the other route.)
I am fairly confident that I am mounted as read/write. As far as what you are saying as not just copying and pasting it, that is one thing that confuses me. I have tried various methods to get the verified recovery onto the phone. The most recent was using drop box. I used root explorer>copied recovery from dropbox>went to system/bin> renamed old recovery recovery.orig> and pressed paste. In various youtube videos I watched it would just paste next to the old recovery.orig, but mine would then proceed to ask if I wanted to overwrite the old one, and I said yes. I am hoping I did not mess things up.
jnwhatle said:
I am fairly confident that I am mounted as read/write. As far as what you are saying as not just copying and pasting it, that is one thing that confuses me. I have tried various methods to get the verified recovery onto the phone. The most recent was using drop box. I used root explorer>copied recovery from dropbox>went to system/bin> renamed old recovery recovery.orig> and pressed paste. In various youtube videos I watched it would just paste next to the old recovery.orig, but mine would then proceed to ask if I wanted to overwrite the old one, and I said yes. I am hoping I did not mess things up.
Click to expand...
Click to collapse
Use this instead easy peezy
http://forum.xda-developers.com/showthread.php?p=14053463
infuse.....infused.......infusion.......
That will root ya and install 3e
Fyi I would download rom you want and then.do that method once ur in cwm install rom boom
infuse.....infused.......infusion.......
I just applied Daoist's CWM stock ROM update (should still be rooted, right?). It came up first time.
Then, I modded my build prop (set dpi to 120 because I like it that way). But maybe I screwed up the file name in Root explorer, because now I'm in a boot loop and if I try ADB PULL /system/build.prop it says "file not found."
I can't get SU through adb, so can't push build.prop to /system. ADB remount returns an error. permission denied. Transformer won't boot, so I can't do anything from it.
I CAN get to cwm, and have been trying to create an update.zip that will just copy build.prop to /system, but everything I have tried quits with "install aborted" message.
What can I do?
restore a nand and dont try and **** with it again, lol. no but really, restore a nand and then copy your build. prop and make a flashable zip and place on your sd card in case it happens again, so you can just flash it in cwm.
Resolved..
Well, why go back when you can go forward?
I went ahead and installed the Prime ROM. Looks like it is eating all my currently installed apps.
Y'all should know, though, that if your system can't find a build.prop it won't start. You can ADB to it and have a rudimentary set of commands, but your ability to significantly alter anything in your file system will be prohibited.
Lesson learned.
glg
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
mrevankyle said:
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
Click to expand...
Click to collapse
That is true. I had backups. But without a build.prop, the virtual machine won't start. There is no way to do a file operation to replace the backup. At least none that I found. I had to flash the whole system.
glg
I just installed jelly bean on my Samsun GS3 SCH-R530U, and now whenever I Odin CWM, it will boot only one time when I boot to it, after that I get a fallen over robot icon from samsung, and their old boot menu. This means I have to flash it every time I want to backup or restore a nandroid backup. Is there some way I can get past this? Do I need a newer CWM? Has Samsung found a way to disable CWM?
try this
as a nexus s owner got this issue in past, seems to be caused cause from GB on in /system/etc there is a install-recovery.sh wich overwrite all the recovery you have installed every time your phone boot up, just solved checking for this file and deleted or renamed (as you want) so in booting the CWM won't be deleted and overwrited by the original one (wich is called install-recovery.sh)
To be clear using root explorer os similar point to this file in /system/etc, then delete or rename, if it tells you can't do cause is read only file system switch from R/W to R/O
Not entirely sure but I think flashing recovery.IMG file on Mobile Odin solved the issue for me.
International S III 16GB / Dualboot 4.1.2 Stock & Cyanogenmod 10.1 / Gokhan's SK
Worthy path to pursue
stremax said:
as a nexus s owner got this issue in past, seems to be caused cause from GB on in /system/etc there is a install-recovery.sh wich overwrite all the recovery you have installed every time your phone boot up, just solved checking for this file and deleted or renamed (as you want) so in booting the CWM won't be deleted and overwrited by the original one (wich is called install-recovery.sh)
To be clear using root explorer os similar point to this file in /system/etc, then delete or rename, if it tells you can't do cause is read only file system switch from R/W to R/O
Click to expand...
Click to collapse
This sounds like a good path to pursue, but I can't find any "install-recovery.sh" anywhere in the system. Could it be named something else, but have the same function?
Accidentally found a workaround -PROBLEM SOLVED 4 me
I found that after using clockworkmod recover, if I remove battery, re-insert battery and then boot phone in normal way, instead of using CWM menu to reboot, it doesn't get over-written. I put in my Title that my problem was solved. Some forums have some other way to indicate this, but I couldn't figure out how on this forum.