Related
WARNING: DO NOT FLASH ANY OTHER GALAXY S VARIANT'S ODIN FILES. YOU WILL BRICK YOUR PHONE!
WARNING: DO NOT FLASH ANY OTHER GALAXY S VARIANT'S ODIN FILES. YOU WILL BRICK YOUR PHONE!
WARNING: DO NOT FLASH ANY OTHER GALAXY S VARIANT'S ODIN FILES. YOU WILL BRICK YOUR PHONE!
If you have installed voodoo before, please follow the instructions here: http://forum.xda-developers.com/showthread.php?t=804784 before attempting to restore back to stock odin files
ONLY FLASH ONE OF THESE AT A TIME. START WITH THE /SYSTEM ODIN AND WORK YOUR WAY DOWN THE LIST IF NEEDED.
Hey guys, after some reading and bricking one device beyond my repair, i have created a file to restore /system back to stock, with su, superuser and busybox already installed.
THIS SHOULD ONLY BE USED TO RESTORE TO STOCK AFTER A COMPLETE FUBAR! I AM NOT RESPONSIBLE FOR WHAT YOU FLASH TO YOUR PHONE!
You need the samsung drivers for windows for this to work. Those can be found on this thread: http://forum.xda-developers.com/showthread.php?t=779238
This has been tested and verified. I signed with md5 and odin reads the md5 signature as it should.
Steps:
1. Pull battery from device
2. Open odin on desktop
3. Hold volume down button and plug device into computer
-This will place the device into download mode
4. Verify device shows up in odin
5. Click "PDA" button in odin
6. Select "Stock-i500-VZW-System.tar.md5" from where you downloaded it
7. Click "Start"
8. Enjoy your fixed /system partition!
Download:
Odin: http://dl.dropbox.com/u/458252/Odin Files/Odin3 v1.3.exe
Odin Restore file for /system: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-System.tar.md5
Odin Restore file for kernel: http://dl.dropbox.com/u/458252/Odin%20Files/Stock-i500-VZW-Kernel.tar.md5
Odin Restore file for recovery: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Recovery.tar.md5
PIT file for use in Odin Restores: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-pit.pit
Big thanks to lilinser / dkcldark; koush; humancyborg, namebrandon, geeknik, and many others that were testing and constantly flashing their phones!
And without ludeboy, well, i wouldnt even be able to get into download mode to fix my phone in the first place
Changelog:
9/17/2010- Updated links, fixed md5 errors on files
9/15/2010: Added an odin restore file for the kernel and recovery now that sources are out. This should be used to restore the kernel if you try flashing another one. To those having problems, reboot into recovery (power off device, hold both volume buttons and power until samsung logo, release power button, recovery should boot) and wipe data and cache.
Tried these steps to a T and get "FAIL" in Odin on three separate attempts.
Imagiohio said:
Tried these steps to a T and get "FAIL" in Odin on three separate attempts.
Click to expand...
Click to collapse
what is the message that you get?
MD5 hash value is invalid
Imagiohio said:
MD5 hash value is invalid
Click to expand...
Click to collapse
Edit: BLAH
That did the trick. Thanks very much for the files and the help!
Thanks angel! Was afraid to start experimenting with the Fascinate until an Odin restore was available.
Has any one got this to work, Every time I try odin finishes and passes and then I replace the battery and phone hangs at verizon for a few minutes and then screen goes black and no longer responds. I thought it might be part of the process so i let is sit for 30 min and nothing.
I got this working last night after I screwed up my phone editing the browser.apk file. The whole process took about 2 minutes to complete, however I don't see superuser and it doesn't appear that I have root
pduboise said:
Thanks angel! Was afraid to start experimenting with the Fascinate until an Odin restore was available.
Click to expand...
Click to collapse
Did the same thing with Email.apk on day two with the phone trying to get multiple Exchange accounts like just about every other android device (Thanks TW!!! ). I was able to get it replaced but have been afraid to do anything beyond rooting and adding WiFi Tether until I had a way to un-brick.
Thanks angel!!!
For those that say they don't have root, can you please run 'ls /system/xbin' from adb shell and post your results here?
Sent from my SCH-I500 using XDA App
Thanks so much! Saved my butt, again.
Note to Everyone: Do not attempt to take the Contacts.apk file from another carrier's Galaxy S phone. It will prevent your phone from booting.
Another Note to Everyone: The Fascinate and the Vibrant, for whatever reason, lack the ability to add a unique ringtone to a given contact. The Epic 4G, however, has this option in Edit Contact. Not sure why...
We need to get a mirror up for that. 8k/s... I downloaded it last night at home, and it was a decent speed, but it's dragging here at work.
theicemonkey said:
Thanks so much! Saved my butt, again.
Note to Everyone: Do not attempt to take the Contacts.apk file from another carrier's Galaxy S phone. It will prevent your phone from booting.
Click to expand...
Click to collapse
Add Browser.apk to that list. I'm on device #2, since the ROM wasn't out when I bricked mine.
theicemonkey said:
Note to Everyone: Do not attempt to take the Contacts.apk file from another carrier's Galaxy S phone. It will prevent your phone from booting.
Click to expand...
Click to collapse
I'm new to Odin (coming from the Sprint Hero). With Odin, you'd still be able to recover even if your phone became unbootable such as the situation you describe, right?
Or maybe a better question: given Odin, are there things you could do to your phone that would NOT be recoverable?
The folder had su and budybox in it. I checked. The superuser.apk was not in the app drawer. I rerooted using adb rage.bin and everything is well again
After running the restore phone would boot past the verizon logo but would not respond and had a black screen. It showed up in adb and the softkeys responded to touch. I did adb reboot recovery and wiped data / factory restore and it rebooted like new. This may be a possible fix for someone experiencing similar issues with this. I am not an expert but it worked for me.
disclaimer: if you try this it is at your own risk what fixed my phone may brick yours, you have been warned
avhokie said:
I'm new to Odin (coming from the Sprint Hero). With Odin, you'd still be able to recover even if your phone became unbootable such as the situation you describe, right?
Or maybe a better question: given Odin, are there things you could do to your phone that would NOT be recoverable?
Click to expand...
Click to collapse
I can tell you that without this my phone would have been unrecoverable and I would have had to go back to Verizon. This restores your /system folder (which includes system apps, boot procedure, animations, etc.) back to stock. Therefore, if the problem preventing your phone from booting was due to a problem in the /system folder, this will fix it.
theicemonkey said:
Thanks so much! Saved my butt, again.
Note to Everyone: Do not attempt to take the Contacts.apk file from another carrier's Galaxy S phone. It will prevent your phone from booting.
Another Note to Everyone: The Fascinate and the Vibrant, for whatever reason, lack the ability to add a unique ringtone to a given contact. The Epic 4G, however, has this option in Edit Contact. Not sure why...
Click to expand...
Click to collapse
Hmm, interesting. I just checked this out, and at first, believed you were right (much to my dismay, as I have a distinctive ring on the number for my employer, for when I'm on-call). However, after playing around a bit, I discovered that contacts that are local to the phone can have the option for selecting a ringtone when being edited. So, for any contacts you need a custom ringtone on, do the following:
1. Create a duplicate contact stored on the phone (orange icon)
2. Link the new contact to the other existing contact
3. Edit the linked contact, and choose the Phone tab at the top
4. Scroll down to see the Ringtone option
erasmogjr said:
After running the restore phone would boot past the verizon logo but would not respond and had a black screen. It showed up in adb and the softkeys responded to touch. I did adb reboot recovery and wiped data / factory restore and it rebooted like new. This may be a possible fix for someone experiencing similar issues with this. I am not an expert but it worked for me.
disclaimer: if you try this it is at your own risk what fixed my phone may brick yours, you have been warned
Click to expand...
Click to collapse
this saved my life thanks man
Hi all. i'm having trouble finding a specific thread to help me solve my problem. (I'm not too good with rooting, and should have not messed with it in the first place!)
Anyways let's get to my problems:
So I needed to take my phone to the Verizon Store, and without thinking went straight to the Factory Reset thing. Now everytime I try booting up my phone it gets stuck on the custom bootup screen and freezes during part of the animation and just stays there.
I have read things that say try going into hboot and doing recovery, but all's it asks me to do is update, then has me reboot. It doesn't update anything as it still does the same exact thing.
My question is, can someone please help guide me through the process of returning my Thunderbolt back to STOCK. I really am unsure of what I need to download, and where I need to put things, and what I need to name them etc: Clearly I need to think twice before rooting my phone again.
Also when I go to plug my Thunderbolt into my computer via USB my computer cannot recognize the device, any suggestions why?
Thanks so much! Really really need help!
First off all it sounds like you have a pg05img.zip file on the root of the sdcard. Only way to remove it now is pulling the sdcard out and putting it in a conputer and deleting that file. Then you should be able to boot and/or get into recovery.
If that's not the case then i don't know what's preventing you from getting into recovery. Although, just a factory reset should not have caused this anyway.
Sent from my ADR6400L using Tapatalk
mini2215 said:
Hi all. i'm having trouble finding a specific thread to help me solve my problem. (I'm not too good with rooting, and should have not messed with it in the first place!)
Anyways let's get to my problems:
So I needed to take my phone to the Verizon Store, and without thinking went straight to the Factory Reset thing. Now everytime I try booting up my phone it gets stuck on the custom bootup screen and freezes during part of the animation and just stays there.
I have read things that say try going into hboot and doing recovery, but all's it asks me to do is update, then has me reboot. It doesn't update anything as it still does the same exact thing.
My question is, can someone please help guide me through the process of returning my Thunderbolt back to STOCK. I really am unsure of what I need to download, and where I need to put things, and what I need to name them etc: Clearly I need to think twice before rooting my phone again.
Also when I go to plug my Thunderbolt into my computer via USB my computer cannot recognize the device, any suggestions why?
Thanks so much! Really really need help!
Click to expand...
Click to collapse
How did you initially Root your device? I assume revo since so many have now. Like mentioned above make sure you check your sdcard and ensure there is no PG05IMG.zip on it. After you have checked your sdcard for that file and deleted it, or maybe it is not there try to get into recovery.
Pull your battery out and then hold Volume down + power. Where does that get you? Hopefully you made a nandroid of your device after you rooted. If you followed a guide that was most definitely recommended. If this takes you to recovery just do a restore.
If you get restored there are some very good guides that Google will lead you to on how to unroot and return to stock.
1Sorry for the super late response, I'm going to try everyone's advice now, thanks so much for the help!
a factory reset will not unroot the phone. If your going back to stock, you have to unroot it. If you bring it to verizon rooted, they may deny you service...
as stated above, just search google or here for instructions how to return to full stock
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 phone and was wanting to do tethering. So when I changed my services.jar and services.odex files, I did a reboot and now it gets stuck on the sprint start up screen. I did do a back up with titanium. But im not worried about losing everything just need to get it working.
hotrod624 said:
I rooted my phone and was wanting to do tethering. So when I changed my services.jar and services.odex files, I did a reboot and now it gets stuck on the sprint start up screen. I did do a back up with titanium. But im not worried about losing everything just need to get it working.
Click to expand...
Click to collapse
Do you have custom recovery?
A sd card?
Any roms saved on your sd card?
A pc and access to Odin?
You might need to just wipe the phone clean and start over.
You stated that you made a back up with T.B.
IMO you shouldn't mod anything without a backing up with custom recovery first. But thats
just me.
So give me the run down of what you have to work it in the way of android tools.
I have access to any pc tools, i currently have odin and kies, Something happened and my recovery is gone... I have loaded a stock firmware onto it and it is still doing the samething.
I fixed it, I reloaded the stock firmware on it and let it sit a few minutes on the sprint screen and that fixed. I guess it was loading system data and it just took a minute lol.
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!