Hi all! I have a slight issue.. So my sisters phone is rooted and on offical kit-kat NAB.
I tried to install @kevinrocksman's hypnotoad boot animation, flashable through twrp. http://forum.xda-developers.com/showthread.php?t=2467543
It didnt work and after the Note 3 screen it stays black till it boots up. I figure it is because the phones only on stock rooted, and that uses a bunch of weird .qmg files. I cant restore the nandroid for several reasons so thats not an option. So I tried the following troubleshooting steps to either get the hypnotoad to work or restore the default sprint sound and animation.
1. I manually pushed the hypnotoad bootanimation.zip into system/media and changed permissions. no go
2. Then in hypnotoad aroma installer I installed it again. Still no go
3. In aroma I tried restore default feature, the sounds back but no yellow sprint animation
4.I deleted the bootanimation.zip in system/media. no go
.5.On the thread @shabbypenguin commented. Posting an enable bootanimation.zip to have the phone look for .zips instead of .qmg. I flashed it. (http://www.mediafire.com/download/xlbsop29q44vlco/Enable-Bootanimation.zip)
6. Then I tried twrping the hypnotoad aroma boot ani again, hoping shabbypenguins enable bootani will make it work. Nada
7. I tried restoring default again through aroma, still boots with sound but no yellow sprint animation.
So if anyone has an idea to either get the hypntoad to work or get back the defualt boot animation, that would be GREATLY appreciated.
I know it was probably dumb to try on stock rooted sorry, but my sister is stuck with no bootanimation, and she does not want to flash a new rom
So thanks
what thread was this??
shabbypenguin said:
what thread was this??
Click to expand...
Click to collapse
All was found on @kevinrocksman s thread. Your comment was at the bottom of the page
Thread: http://forum.xda-developers.com/showthread.php?t=2467543
I hope you have a fix mr. shabbypenguin sir! :fingers-crossed:
Do you know of any fixes @kevinrocksman??
I would think there would be a flashable. Zip laying around but i couldn't find any
if you read to the second page, you would have seen that zip doesnt work
shabbypenguin said:
if you read to the second page, you would have seen that zip doesnt work
Click to expand...
Click to collapse
Ive read the whole thread, and the comments. I believed it would work because I have been on several stock Samsung based roms, and all of either the flashable.zips or manually pushing to /system/media have worked fine. Im even currently on AOSP and pushing the monster attack bootanimation.zip to system/media worked perfectly. So I believe my error lies in possibly two things. Either..
A.these bootanimaton.zips are not NAB compatible; which would seem odd because as far as I know bootanimation.zips are fairly universal. It worked on AOSP just fine
B. Or since this is stock STOCK rooted, the system files have not been configured by a dev to allow changing bootanimation.zips.
If it is scenario B, which i think is more likely, then a solution would be to flash a custom built Nab rom, right? I would think if I flashed Freezas stockISH rom it would be too stock and the boot ani system files would be the same situation. Which is why im thinking @sac23 s kit-kats v1 nab rom would allow me to change bootanimation.zip. Do you think this would be accurate?
I did some further digging and I believe I may have found a way to be able to push bootanimation.zips and have them work even on stock stock roms.
What do you think of this? http://forum.xda-developers.com/showthread.php?p=50218786
I gather if I push the bootanimation.bin in OP and replace it with the current one in /system/bin it will enable me to change bootanimations just like normal. You probably would have a better idea then me, do you think this is an accurate conclusion?
Thanks :good:
kevinrocksman said:
samsung has been using qmg files since before the SGS1, this http://www.mediafire.com/download/xl...tanimation.zip should enable it. it swaps out the bootanimation binary for one looking for .zip's. it may not work if they are still using samsungani
Click to expand...
Click to collapse
this is what it does in adb when u execute bootanimation
CANNOT LINK EXECUTABLE: cannot locate symbol "_ZN7android21SurfaceComposerClient
14getDisplayInfoEiPNS_11DisplayInfoE" referenced by "bootanimation"...
Click to expand...
Click to collapse
as for all the other zips idk, but mine doesnt. as for figureing it out etc, youll have to ask someone who is up to date on samsung software and/or owns a note 3.
shabbypenguin said:
as for all the other zips idk, but mine doesnt. as for figureing it out etc idk, youll have to ask someone who is up to date on samsung software and/or owns a note 3.
Click to expand...
Click to collapse
okay thanks anyway, I happen to have an extra replacement note 3 for a little bit so ill run some tests!
thanks
Related
Girlfriend got a Fascinate yesterday and deemed me worthy enough to root it so she can kill all the bloatware (yay for me!). I've got root on the phone, and I understand that if I don't flash a custom kernel for the phone, it'll just break the recovery (using "cwm-recovery-all.tar") as soon as the phone boots up. She likes the overall touchwiz experience and all that, so I'm not sure of any rom's that are pretty stock cept for bloat, and any kernels I should use so recovery doesn't break.
I'm just concerned about getting recovery to stick so that I can perform a backup in case anything should happen.
I have a OG Droid, so all this bending over backwards for root and recovery is new to me and threads seem either too full of info or not enough for me, so here's me asking for help!
Either way, thanks!
Dustin
seraph_harim said:
Girlfriend got a Fascinate yesterday and deemed me worthy enough to root it so she can kill all the bloatware (yay for me!). I've got root on the phone, and I understand that if I don't flash a custom kernel for the phone, it'll just break the recovery (using "cwm-recovery-all.tar") as soon as the phone boots up. She likes the overall touchwiz experience and all that, so I'm not sure of any rom's that are pretty stock cept for bloat, and any kernels I should use so recovery doesn't break.
I'm just concerned about getting recovery to stick so that I can perform a backup in case anything should happen.
I have a OG Droid, so all this bending over backwards for root and recovery is new to me and threads seem either too full of info or not enough for me, so here's me asking for help!
Either way, thanks!
Dustin
Click to expand...
Click to collapse
You're just a few steps away.
First download this stock ed01 debloated/debinged stock ROM from link below and place in root directory of SD card:
http://www.multiupload.com/BKHF5DKJ18
also, choose a kernel and place on sd card. I recommend imnuts' PB&J variety-you might want to stick with stock voltage or -50uv for now. Be mindful to get non-voodoo if you aren't planning on getting into this. found here (try the 3rd or 5th option):
https://sites.google.com/a/imnuts.net/android/kernels
Next, use Odin to install your CWM again. When you boot up this time, boot directly into CWM by turning phone off, and holding volume down, volume up, and power (all 3) until CWM appears. flash your rom, and kernel. If you don't boot into cwm directly by this method, the stock kernel will overwrite CWM, which is what was happening to you, i believe.
after rom/kernel is installed, choose reboot system now from cwm.
Yeah, I just wasn't sure about what kernel would be good for her phone, so I just was kinda "stuck" at that point. ^^;;
But I will give it a go and she how it works out! thanks much!
Everything was a success, and there was much rejoicing!
They only thing I noticed was after the Samsung bootloop animation, it goes to the default "android" one instead of Verizon's... I'm sure there's a way to get that back, but its not in the system dump I have. I'm currently searching for it on the net ^^;;
Thanks again!
Edit: I was able to find a boot animation that had the first part of the Galaxy S bit without the Verizon part. When it booted it just repeated the "Galaxy S" animation. I thought by adding, renaming, and reversing the shutdown animation would at least give that back, but now I just get a black screen for that segment...Still working on it....I think it has to do with the txt file inside, but i'm not sure.
The PowerOn.wav is still present on the phone, but it doesn't play either.... >_<
Are you certain you put poweron.wav in /system/etc folder?
Yup, its there and plays fine in the media player, but I just noticed that there's also a PowerOn.snd file right above. Could that be interfering?
Make a backup elsewhere of that file, then delete it and see if that works.
Sent from mah Fascinate using XDA Premium App
The sound won't work with most kernels that are not stock because the boot sounds aren't actually turned on in the kernel
Swyped from my CM7 fascinate
Oh okay, any chance to get the default boot animation from any of you guys? She doesn't mind the sound "missing," but she would like the boot animation at least.
Eitiher way, thanks much for the info!
since it seems like you're using a stock Rom just debloated and rooted, you may want to think about just using the stock Kernel with the recovery wipe removed, it has two options one that sticks with the stock boot animation and may still have sound and one that allows custom boot animations. This kernel was created by imnuts and can be found here:
http://forum.xda-developers.com/showthread.php?t=1060457
Awesome, thanks! I'll give that a try and see how it turns out!
And it worked! Thanks again!
Hello.
I couldn't find any good information on how to safely test SystemUI.apk and framework-res.apk to minimize chances brick the phone?
For instance I've soft bricked my phone by misspelling a word in layouts/status_bar.xml
Is there a safe way test it before push it to the phone?
Thank you.
U can't possibly brick your phone because of wrongly modded framework_Res.apk or systemui.apk.
Ok, maybe not exactly brick, but boot loop with lost of root - yes I can. I've done it twice already, first time when copied recourses.arcs from freshly compiled resources-res.apk to original file (because apktools doesn't support .apk from LG Nitro HD, or ICS, it creates new folder and removes others making different file tree structure from original) and second time messing up systemui file, with the later boot loop the re-root that worked the first time didn't work I had to manually root the phone to brink it back.
Just backup working one, copy modded to it's directory and if not work change it with working one via adb during boot.
Ok, that's what I've been doing, but this phone is wierd, when boot loop happens it looses root access (I still can adb shell, but su would return segment fault error), so I have to re-root. Then when all fixed and done, after first boot it forgets my google account...
It's rather time consuming to go through all this on each failure, so I hoped there is a way do it more safely...
If that's the only way, so be it, if I brick my phone I'll blame it on BHuvan goyal
j/k
CWM full backup, flash new systemui and framework-res, bootloop? then CWM advanced restore /system only, should still have root. This is what usually works for me when flashing these .apks
Good idea. Unfortunately we still waiting for CWM on LG Nitro, we got root in no time, but can't get CWM to work just yet. There are quiet a few weird issues with this phone...
I'm getting weird results. Right now I'm using modified SystemUI.apk and framework-res.apk on stock rom. When I flash this same stock rom and replace these two files thrle phone gets into boot loop. How can I trace what causing it?
Thanks.
[email protected] said:
I'm getting weird results. Right now I'm using modified SystemUI.apk and framework-res.apk on stock rom. When I flash this same stock rom and replace these two files thrle phone gets into boot loop. How can I trace what causing it?
Thanks.
Click to expand...
Click to collapse
Rom deodexed?
Sent from my SCH-I400 using xda premium
No, it's a stock rom, not deodexed.
It's just the same method I used to push these files that do work now, don't work anymore when I try it on a "fresh" same rom...I don't recall doing anything else or different...
[email protected] said:
No, it's a stock rom, not deodexed.
It's just the same method I used to push these files that do work now, don't work anymore when I try it on a "fresh" same rom...I don't recall doing anything else or different...
Click to expand...
Click to collapse
To my knowledge rom needs to be deodexed to mod
Sent from my SCH-I400 using xda premium
Yes, but somehow I managed make it work on this rom several times, now for some reason it doesn't work anymore..can't wrap my head around it, very strange.
just place your current untouched systemui and framework apks in a themers update.zip if all goes wrong just boot into recovery and flash the zip to return to working APKS
I rooted my S3, changed one file, and am now stuck in the startup screen. I've looked on the forums but I'd like to confirm what my recovery options are.
(1) Since I have no backup*, can I recover from a factory recovery for my model and still keep some of my data, apps and customizations?
It's a N American SIII (Rogers Wireless Samsung SGH-I747M). I can boot successfully into both Odin and CWM Recovery (Clockwork 5.5). BusyBox installed.
*I only did one thing:
renamed framework-res.apk to framework-res.apk2 to test permissions. Errors and crash ensued, then I restarted and here I am.
That apk file is part of a fix which is circulating that corrects a bug in the North American models' battery reporting, which requires replacing the apk with a slightly modified version. I thought trying a file rename was a safe small test, prior to backing up. The name "framework" should have tipped me off probably.
(2) Is factory recovery my best option? I would love to get in and just name the file back. But I can't get in.
(3) Was some automatic backup made that I overlooked? Rooting and the learning curve took so many steps I can't remember myself.
(4) Can I just restore the /system directory perhaps? Or some other advanced or custom restore?
Yep, relative noob here. Hope my question is placed correctly and I haven't missed another post with the answers I need, if not pls advise.
CWM Recovery Flash Zip - Not able to find zip on SD
Some progress here...
Since I think the problem is that I renamed framework-res.apk to framework-res.apk2, and since I had a backup of the original, I found and applied the following:
[GUIDE] How to make a cwm recovery flashable zip
Specifically:
Stuck my saved framework-res.apk into the archive in the correct folder (system/framework)
Renamed from sample.zip to update.zip
Copied update.zip to the root of my micro SD (went to buy one since I didn't have a working one)
Since the Guide didn't specify, I assume that flashing requires booting into CWM Recovery (in my case Clockwork 5.5) and using one of the "install zip from sdcard" options there. But it couldn't find the file. Here are my attempt outcomes:
- apply /sdcard/update.zip:
E: Can't open /sdcard/update.zip
(no such file or directory)
Click to expand...
Click to collapse
- choose zip from sdcard:
This just shows me the directory structure inside my phone
So how can I flash from a zip on the (external) SD card? I can't connect via USB except maybe with Odin, so I don't think I can put anything on my device.
No luck
Well, attempted the stock restore from Epic and still have a soft bricked phone.
According to the thread, everyone else is reporting success with Epic's version 4, but it's not working for me. Maybe I'm tired after 48 hours of this and I've missed something or am trying something that cannot work. No idea what's wrong.
I even resigned to losing everything (no backup) and starting over. Didn't think I'd have a permanent brick though.
Here is what everybody is raving about. CWM Recovery on all SGS3 LTE Variants
Will try again, just in case.
Any Luck?
I have done something similar...
I've been trying to find the stock boot from Rogers for the last 5 hours.
I can get into recovery mode and the download screen, but that's as far as I can get.
If you figure it out PLEASE let me know!
same boat
i just bricked my Rogers S3 with apparently a wrong ROM.
can't even get into recovery, totally bricked!
Were you able to find any solution?
Gave up and swapped hardware
I wasn't able to fix it. I was stuck between three useless boot options:
Regular boot - splash screen only and a vibration every few minutes
ODIN - showing that I had flashed the ROM 3 times
CWM - Clockworkmod's custom flash install, replacing the stock one
(Search the forums for the key combinations to get into these.)
I took it back to the store and they kindly replaced it. Glad they didn't know the key combinations. When they told me they needed an hour "to look at it" I thought I'd come back to a finger wag and a flat denial. That was a tough hour.
Make a backup, people; actually, I'm completely sure that a backup is enough. I'm still green at this.
snoops609 said:
I've been trying to find the stock boot from Rogers for the last 5 hours.
Click to expand...
Click to collapse
I understand that the Rogers Galaxy SIII stock recovery isn't out anywhere. If someone is aware of one, please post a link.
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Details pls
snoops609 said:
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Click to expand...
Click to collapse
Snoops, do you have a Rogers phone? Just trying to understand what you mean by "att boot img". Lol on the Odin count, I got up to 3 and thought I was badass.
Yes, I'd be interested in the files for future use, especially if you're on Rogers and have the LTE version of the Galaxy S3. Model SGH-I747M.
snoops609 said:
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Click to expand...
Click to collapse
plese bro help me out...im stuck in the same hole..i just installed some font changer software and m:y phone just rebooted ....
Been looking around for lockscreen mods after running Rootbox a few weeks ago. Really liked what was available. But on other roms I was stuck with the plain old lock. Now on JB for a few days and really miss this kind of mod. I came across this in the Nexus forum(I KNOW, not an SGS2). http://forum.xda-developers.com/showthread.php?t=1704727&highlight=faithcry+lockscreen
Is this compatible with our phones and specifically running JB? If so, anyone know how to use this zipthemer and apply this mod?
The original OP list the galaxy s2 as being compatible. I've tried zipthemer. Had to edify before building. It built a zip but when flashed it didn't change anything.
Woohoo! It works! Finally figured it out!
knightsh said:
Woohoo! It works! Finally figured it out!
Click to expand...
Click to collapse
How did you get it to work? When I try to use lockscreen mods, I use ziptheme, configure the edify with my current rom zip, then flash the update zip and nothing happens. Am I doing something wrong?
It took me several tries to get right. There is a good write-up in the thread posted. But yeah. Basically click update edify, browse and find your current ROM and after it will show "success" at bottom of your screen. Then back to "theme", click back arrow and find the zip file of the icon you want to use. It should then show up on screen under "theme". Click "build it". It will create the "update.zip" file. Reboot into recovery, clear cache and dalvik, flash the "update.zip" file you created, then reboot. The op talks about boot looping and pulling battery out. I have never had to. Once it boot looped after changing jb ROMs and I just went back to recovery and reflashed ROM, booted and updated edify, then went and flashed again. Currently running Fusions jb and have never had to update edify after first time. It works with each nightly update.
You've probably heard this song and dance before, but my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
siren_shadows said:
my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Click to expand...
Click to collapse
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
siren_shadows said:
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
Click to expand...
Click to collapse
What happens if you just type in a URL, without going through Google search results?
redpoint73 said:
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
What happens if you just type in a URL, without going through Google search results?
Click to expand...
Click to collapse
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
siren_shadows said:
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
Click to expand...
Click to collapse
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
redpoint73 said:
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
Click to expand...
Click to collapse
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
siren_shadows said:
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
Click to expand...
Click to collapse
Did you modify build.prop?
redpoint73 said:
Did you modify build.prop?
Click to expand...
Click to collapse
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
siren_shadows said:
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
Click to expand...
Click to collapse
WNC just posted the 4.28.502 version of his ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I assume the build.prop is stock; and kernel is insecure.
unfortunately, I am s-on.
siren_shadows said:
unfortunately, I am s-on.
Click to expand...
Click to collapse
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
redpoint73 said:
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
Click to expand...
Click to collapse
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
siren_shadows said:
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
Click to expand...
Click to collapse
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
redpoint73 said:
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
Click to expand...
Click to collapse
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
siren_shadows said:
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
Click to expand...
Click to collapse
Can you still get into bootloader?
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
redpoint73 said:
Do you mean you can't get into bootloader?
If so, that doesn't actually make any sense, bootloader is write protected with s-on. So there is no way this can be corrupted or over-written.
This seems scary. But just take a breath, as I don't think this is as bad as it looks.
What happened after you copied the file?
Does the screen come on at all?
Click to expand...
Click to collapse
i got a black screen after a reboot. but holding power and volume up did the hard reset and i had to really quickly press volume down. like a split second window
siren_shadows said:
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
Click to expand...
Click to collapse
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
redpoint73 said:
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
Click to expand...
Click to collapse
I was a genius and decided I would save space by moving onto my computer. However, I am restoring now. That'll fix my black screen issue, right?
siren_shadows said:
I am restoring now. That'll fix my black screen issue, right?
Click to expand...
Click to collapse
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
redpoint73 said:
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
Click to expand...
Click to collapse
who knows. My issue isn't fixed regarding mobile data, either. At least I have a usable phone tho!