[SOLVED] help needed, replaced build.prop & phone won't start up

[Paul627g]

Re: help needed, replaced build.prop and phone won't start up now

No thanks needed here.... Seeing these two get their phones back up and going again will be all the thanks I need.

Thanks UL for providing the Nandroid... Great example of someone going out of their way to help another member

 

[Tkbredx]

It's official. I won't be rooting. I'm too scared lol. Chickening out. Lol. Goodluck to you heiro. And to those out there helping him, hats off to you my friends.

Sent from my SPH-L710 using Android Central Forums

 

[dmmarck]

It's official. I won't be rooting. I'm too scared lol. Chickening out. Lol. Goodluck to you heiro. And to those out there helping him, hats off to you my friends.

Sent from my SPH-L710 using Android Central Forums

Don't panic; with due diligence and an ounce of courage your phone can be turned into a device so powerful it will create anti matter.

Sent from my Galaxy Nexus using Android Central Forums

 

[Paul627g]

Re: help needed, replaced build.prop and phone won't start up now

It's official. I won't be rooting. I'm too scared lol. Chickening out. Lol. Goodluck to you heiro. And to those out there helping him, hats off to you my friends.

Sent from my SPH-L710 using Android Central Forums

Don't let this example here turn you away...

1. They both had an easy, successful root & installation of CWM (ClockWorkMod) recovery.

2. They both altered something in the file system which caused things to screw up. This is fine except....

2a. They didn't make Nandroid Backup's before they attempted any changes. This would of given them both a "Get out of jail free card" to return back to their original setup before they made any alterations to their devices after achieving successful root/CWM.

3. They also both did without the release of a "Restore or Return to Stock" option. This is a complete restore using Odin "same program you use to flash the custom recovery". The package will restore your device back to stock Android 4.0.4 & remove root & replace any custom recoveries with the stock OEM/Android recovery with no signs of being rooted.


Sorry I don't mean to make examples of these two but it shows how a simple mistake of not making a Nandroid Backup and waiting to attempt anything without a Restore option got them in trouble. This is also the same reasons you don't see any custom ROMs popping out yet, the ROM devs don't want to start fooling around and end up in a situation where they need the Restore option that we currently don't have.

 

[hiero]

Re: help needed, replaced build.prop and phone won't start up now

Don't panic; with due diligence and an ounce of courage your phone can be turned into a device so powerful it will create anti matter.

Sent from my Galaxy Nexus using Android Central Forums

so my phone will turn into Lord Nibbler?? sweet


and Paul627g, if someone can learn from my mistakes I'm all for it!

 

[dmmarck]

so my phone will turn into Lord Nibbler?? sweet


and Paul627g, if someone can learn from my mistakes I'm all for it!

Well played

Sent from my TARDIS

 

[cyberdalek]

Sent from my TARDIS

Love the new sig. All it took was half of the first season.


"There's always something to look at if you open your eyes."
-The Doctor

 

[hiero]

Re: help needed, replaced build.prop and phone won't start up now

OMG. It's done, I have recovered!!!!!

OK, the process was WAY more painful than it should have been, but again, my fault.

HUGE thank you to everyone on this thread who pitched in! With such a quick response too! AMAZINGLY responsive forum!

And A HUGE THANK YOU TO UNCLE LOUIE.

So I ended up figuring out that if you just turn the phone on normally and let it get past the 'Samsung Galaxy S III' screen to a blank screen, if you plug a USB cable in, it seems to actually connect to the computer. Unfortunately, it does NOT connect to the computer via normal windows USB connection and it does not show up as a drive.

Fortunately, I downloaded and installed ADB and installed the platform tools to get ADB functions enabled (I also installed the google USB drivers, but unsure if that helped or not). Once I had that, I thought I would just try to connect the phone and try a adb push of Uncle Louie's recover folder. Sure enough, IT WORKED.
Unfortunately, I uploaded it to the root instead of the proper /SDCARD/clockworkmod/backup folder! DOH. And yet again, unfortunately, I kept accidentally pushing the 'recover' button on the stupid CWM interface. What ended up happening? You can guess I hope, I RAN OUT OF SPACE. UGH.
So eventually I figured I'd just push to one of the existing backup folders and have it replace the files there. That worked and then the CWM recovery went through perfectly!

Now I'm back and setting up my phone again, but that's not so bad!
It's late and if I'm forgetting anything, I'll come back tomorrow and update. zharris24, I'm here if you need help with the process!

 

[dmmarck]

Love the new sig. All it took was half of the first season.


"There's always something to look at if you open your eyes."
-The Doctor

I presume you are on g+? It's been quite a day lol.

OMG. It's done, I have recovered!!!!!

OK, the process was WAY more painful than it should have been, but again, my fault.

HUGE thank you to everyone on this thread who pitched in! With such a quick response too! AMAZINGLY responsive forum!

And A HUGE THANK YOU TO UNCLE LOUIE.

So I ended up figuring out that if you just turn the phone on normally and let it get past the 'Samsung Galaxy S III' screen to a blank screen, if you plug a USB cable in, it seems to actually connect to the computer. Unfortunately, it does NOT connect to the computer via normal windows USB connection and it does not show up as a drive.

Fortunately, I downloaded and installed ADB and installed the platform tools to get ADB functions enabled (I also installed the google USB drivers, but unsure if that helped or not). Once I had that, I thought I would just try to connect the phone and try a adb push of Uncle Louie's recover folder. Sure enough, IT WORKED.
Unfortunately, I uploaded it to the root instead of the proper /SDCARD/clockworkmod/backup folder! DOH. And yet again, unfortunately, I kept accidentally pushing the 'recover' button on the stupid CWM interface. What ended up happening? You can guess I hope, I RAN OUT OF SPACE. UGH.
So eventually I figured I'd just push to one of the existing backup folders and have it replace the files there. That worked and then the CWM recovery went through perfectly!

Now I'm back and setting up my phone again, but that's not so bad!
It's late and if I'm forgetting anything, I'll come back tomorrow and update. zharris24, I'm here if you need help with the process!

The best news all night! Good job!

Sent from my TARDIS

 

[Uncle Louie]

Re: help needed, replaced build.prop and phone won't start up now

OMG. It's done, I have recovered!!!!!

OK, the process was WAY more painful than it should have been, but again, my fault.

HUGE thank you to everyone on this thread who pitched in! With such a quick response too! AMAZINGLY responsive forum!

And A HUGE THANK YOU TO UNCLE LOUIE.

So I ended up figuring out that if you just turn the phone on normally and let it get past the 'Samsung Galaxy S III' screen to a blank screen, if you plug a USB cable in, it seems to actually connect to the computer. Unfortunately, it does NOT connect to the computer via normal windows USB connection and it does not show up as a drive.

Fortunately, I downloaded and installed ADB and installed the platform tools to get ADB functions enabled (I also installed the google USB drivers, but unsure if that helped or not). Once I had that, I thought I would just try to connect the phone and try a adb push of Uncle Louie's recover folder. Sure enough, IT WORKED.
Unfortunately, I uploaded it to the root instead of the proper /SDCARD/clockworkmod/backup folder! DOH. And yet again, unfortunately, I kept accidentally pushing the 'recover' button on the stupid CWM interface. What ended up happening? You can guess I hope, I RAN OUT OF SPACE. UGH.
So eventually I figured I'd just push to one of the existing backup folders and have it replace the files there. That worked and then the CWM recovery went through perfectly!

Now I'm back and setting up my phone again, but that's not so bad!
It's late and if I'm forgetting anything, I'll come back tomorrow and update. zharris24, I'm here if you need help with the process!

YAY! Glad it worked out for you!

 

[Paul627g]

Awesome! One down, one to go :-D

Everyone involved did a great job.

Sent from my Nexus S 4G using Android Central Forums

 

[zharris24]

Re: help needed, replaced build.prop and phone won't start up now

OMG. It's done, I have recovered!!!!!

OK, the process was WAY more painful than it should have been, but again, my fault.

HUGE thank you to everyone on this thread who pitched in! With such a quick response too! AMAZINGLY responsive forum!

And A HUGE THANK YOU TO UNCLE LOUIE.

So I ended up figuring out that if you just turn the phone on normally and let it get past the 'Samsung Galaxy S III' screen to a blank screen, if you plug a USB cable in, it seems to actually connect to the computer. Unfortunately, it does NOT connect to the computer via normal windows USB connection and it does not show up as a drive.

Fortunately, I downloaded and installed ADB and installed the platform tools to get ADB functions enabled (I also installed the google USB drivers, but unsure if that helped or not). Once I had that, I thought I would just try to connect the phone and try a adb push of Uncle Louie's recover folder. Sure enough, IT WORKED.
Unfortunately, I uploaded it to the root instead of the proper /SDCARD/clockworkmod/backup folder! DOH. And yet again, unfortunately, I kept accidentally pushing the 'recover' button on the stupid CWM interface. What ended up happening? You can guess I hope, I RAN OUT OF SPACE. UGH.
So eventually I figured I'd just push to one of the existing backup folders and have it replace the files there. That worked and then the CWM recovery went through perfectly!

Now I'm back and setting up my phone again, but that's not so bad!
It's late and if I'm forgetting anything, I'll come back tomorrow and update. zharris24, I'm here if you need help with the process!

Downloading UL's file. Thanks again UL, if it worked for Hiero, I am hoping the same goes for me! I figured CWM wouldn't read the external SD card and was afraid that adb shell was needed.... Hopefully I can get my phone recognized on my computer so I can get adb shell going... I have a feeling it's going to be a long day. In any manner, thanks to everyone for the help. UL I can't give you enough thanks!

 

[Uncle Louie]

Downloading UL's file. Thanks again UL, if it worked for Hiero, I am hoping the same goes for me! I figured CWM wouldn't read the external SD card and was afraid that adb shell was needed.... Hopefully I can get my phone recognized on my computer so I can get adb shell going... I have a feeling it's going to be a long day. In any manner, thanks to everyone for the help. UL I can't give you enough thanks!

Glad I could help out... Let us know how it goes!

Sent from my SPH-L710 using Android Central Forums

 

[hiero]

Re: help needed, replaced build.prop and phone won't start up now

Glad I could help out... Let us know how it goes!

Sent from my SPH-L710 using Android Central Forums

Yes! Please do!

 

[zharris24]

Re: help needed, replaced build.prop and phone won't start up now

Yes! Please do!

So as of right now, I can't get CWM to read the backup file off of the external SD. So it looks like I am going to have to go the ADB route however, my phone freezes at the "Samsung Galaxy SIII" screen and doesn't ever to go a blank screen where ADB can connect to it. Any thoughts? I have all Samsung drivers installed as well as Google's USB drivers, but still can't get adb shell to connect. I'll keep digging but any thoughts would be helpful.

 

[hiero]

Re: help needed, replaced build.prop and phone won't start up now

So as of right now, I can't get CWM to read the backup file off of the external SD. So it looks like I am going to have to go the ADB route however, my phone freezes at the "Samsung Galaxy SIII" screen and doesn't ever to go a blank screen where ADB can connect to it. Any thoughts? I have all Samsung drivers installed as well as Google's USB drivers, but still can't get adb shell to connect. I'll keep digging but any thoughts would be helpful.

Have you tried doing a 'wipe drive/factory reset'? that may get you past the frozen screen to a blank one

 

[Tkbredx]

Congrats on getting it done. After all this I am considering rooting again. Lol. And I hope all's well for you too Zharris.

Sent from my SPH-L710 using Android Central Forums

 

[zharris24]

Re: help needed, replaced build.prop and phone won't start up now

Have you tried doing a 'wipe drive/factory reset'? that may get you past the frozen screen to a blank one

Yep and still no adb connection or blank screen...

 

[hiero]

Re: help needed, replaced build.prop and phone won't start up now

Yep and still no adb connection or blank screen...

how about formatting the system folder under mounts and storage? *I don't know if this will make things worse or not, someone smarter have an opinion?

 

[zharris24]

Re: help needed, replaced build.prop and phone won't start up now

how about formatting the system folder under mounts and storage? *I don't know if this will make things worse or not, someone smarter have an opinion?

Nothing.... If I only could get a recovery system that has ADB capabilities or can read from the external storage this would be a piece of cake...