Related
how do i connect my phone to my pc to search all my files and pull them out, im not tlking about sd mount eighter i need to pull out internal files
Try downloading a file manager on your phone.
Evo SHIFT
I need to connect my phones internal files to my pc, so i can access everything in my phone, root explorer or other apps won't allow that.
thizzlemania91 said:
I need to connect my phones internal files to my pc, so i can access everything in my phone, root explorer or other apps won't allow that.
Click to expand...
Click to collapse
Root explorer allow you to delete system files.. you just have to change permission for it to work... thrust me I dint know how to do it at the beginning but it works.
You can use root explorer to copy/paste the files you want to your SD card. Or simply adb pull. Either way will work.
Just use adb wireless. You have full access wirelessly that way.
Sent from my PG86100 using Tapatalk
You can always use Droid Explorer.
thizzlemania91 said:
how do i connect my phone to my pc to search all my files and pull them out, im not tlking about sd mount eighter i need to pull out internal files
Click to expand...
Click to collapse
personally I prefer using the tools google has released for developers all included in the android-sdk package. the main tool for command line access to the device is adb (android debug bridge).
i wrote a quick/simple guide on the basic commands for using adb - [TUTORIAL/HOW TO] Basics of ADB
hope that helps!
Thanks ppl ill give your suggestions a go
Joey your tutorial is noob friendly +1thank you brother.
does anybody know if there's a way to block an app fr detecting that your phone is rooted, i was trying to redeem my code for my digital copy to download fast five on my phone using pocket BLU, once it gets ready to download it let's me knw that it detected that my phone was rooted n doesn't let me download, i also had the same problem with blockbuster before I was rooted I purchased some movies but after I was rooted tried to go back to my movies n. same thing, detected my device was rooted... I was wondering if there's a way or hack that we can do to not make it detectable as being rooted, thanx
Sent from my PG86100 using XDA App
do you have the Superuser app auto allow root requests or do you have to manually allow each time?
ozkaya said:
do you have the Superuser app auto allow root requests or do you have to manually allow each time?
Click to expand...
Click to collapse
everytime u get an app that request root user permission I have to allow, it doesn't allow automatically but once I have aloud an app I don't have to do it again
You have to delete the root detection in some smali files to remove it.
私のEVO 3Dから送信される
Flip35 said:
does anybody know if there's a way to block an app fr detecting that your phone is rooted, i was trying to redeem my code for my digital copy to download fast five on my phone using pocket BLU, once it gets ready to download it let's me knw that it detected that my phone was rooted n doesn't let me download, i also had the same problem with blockbuster before I was rooted I purchased some movies but after I was rooted tried to go back to my movies n. same thing, detected my device was rooted... I was wondering if there's a way or hack that we can do to not make it detectable as being rooted, thanx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
a temporary fix:
1) rename /system/bin/su to anything else, example: /system/bin/jk. i prefer to use adb shell for the renaming.
2) run the application which looks for root
3) when done running the application which has root detection, rename /system/bin/jk back to /system/bin/su.
this should work because the root detection method most applications use is to only check if a file named /system/bin/su is present. if that file is present, they consider the phone rooted. they usually don't even attempt to open the /system/bin/su which would trigger the superuser apk, they usually only look to see if the /system/bin/su file *exists*.
hope that helps!
joeykrim said:
a temporary fix:
1) rename /system/bin/su to anything else, example: /system/bin/jk. i prefer to use adb shell for the renaming.
2) run the application which looks for root
3) when done running the application which has root detection, rename /system/bin/jk back to /system/bin/su.
this should work because the root detection method most applications use is to only check if a file named /system/bin/su is present. if that file is present, they consider the phone rooted. they usually don't even attempt to open the /system/bin/su which would trigger the superuser apk, they usually only look to see if the /system/bin/su file *exists*.
hope that helps!
Click to expand...
Click to collapse
after doing this is not gonna mess anything up with me been rooted, i'm still gonna b able to flash roms n all that?
joeykrim said:
a temporary fix:
1) rename /system/bin/su to anything else, example: /system/bin/jk. i prefer to use adb shell for the renaming.
2) run the application which looks for root
3) when done running the application which has root detection, rename /system/bin/jk back to /system/bin/su.
this should work because the root detection method most applications use is to only check if a file named /system/bin/su is present. if that file is present, they consider the phone rooted. they usually don't even attempt to open the /system/bin/su which would trigger the superuser apk, they usually only look to see if the /system/bin/su file *exists*.
hope that helps!
Click to expand...
Click to collapse
joey good **** man, u da man, got it downloading my movie now so it worked
Flip35 said:
does anybody know if there's a way to block an app fr detecting that your phone is rooted, i was trying to redeem my code for my digital copy to download fast five on my phone using pocket BLU, once it gets ready to download it let's me knw that it detected that my phone was rooted n doesn't let me download, i also had the same problem with blockbuster before I was rooted I purchased some movies but after I was rooted tried to go back to my movies n. same thing, detected my device was rooted... I was wondering if there's a way or hack that we can do to not make it detectable as being rooted, thanx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
There's an app on the market "temp root remover" this works great for me..is much easier...
Sent From My HTC EVO 3D ROOTED
luisrod03 said:
There's an app on the market "temp root remover" this works great for me..
Sent From My HTC EVO 3D ROOTED
Click to expand...
Click to collapse
so we can go unroot n root pretty easy?
Flip35 said:
so we can go unroot n root pretty easy?
Click to expand...
Click to collapse
Yes....on one click
Sent From My HTC EVO 3D ROOTED
luisrod03 said:
Yes....on one click
Sent From My HTC EVO 3D ROOTED
Click to expand...
Click to collapse
iight thanx ill give itt a shot
After you rename the file you lose root. How do you regain root privilege to rename the file? Do you chmod? How do you mount rw?
larsdennert said:
After you rename the file you lose root. How do you regain root privilege to rename the file? Do you chmod? How do you mount rw?
Click to expand...
Click to collapse
Try the app I put on the previous post that's going to give root access again...
Sent From My HTC EVO 3D ROOTED
larsdennert said:
After you rename the file you lose root. How do you regain root privilege to rename the file? Do you chmod? How do you mount rw?
Click to expand...
Click to collapse
yes try the app that luis posted it works flawless, i went in blockbuster and pocket BLU and downloaded all my movies without any issues got don't when to temp unroot remover one click n. back to normal, that app is definitely a life saver, thanx luis
Flip35 said:
yes try the app that luis posted it works flawless, i went in blockbuster and pocket BLU and downloaded all my movies without any issues got don't when to temp unroot remover one click n. back to normal, that app is definitely a life saver, thanx luis
Click to expand...
Click to collapse
you welcome.....
Ok tried to watch fast five from the market, got video playback not supported on rooted devices error 49. Tried to find "temp root remover" in market... No results... Tried renaming system/bin/su still wont work... Ideas?
Ok got the temp root remover but is not working... Help?
Edit... Found a fix. Must be a synergy thing cause got the app to work in viperROM... guess synergys just heavyhanded with the tweaks.
Sent from 3D A.W.E.S.O.M-O
motoelliot said:
Ok tried to watch fast five from the market, got video playback not supported on rooted devices error 49. Tried to find "temp root remover" in market... No results... Tried renaming system/bin/su still wont work... Ideas?
Ok got the temp root remover but is not working... Help?
Edit... Found a fix. Must be a synergy thing cause got the app to work in viperROM... guess synergys just heavyhanded with the tweaks.
Sent from 3D A.W.E.S.O.M-O
Click to expand...
Click to collapse
Yeah synergy is cool rom but the bad thing is that when trying to change system files is not going to let u....
Sent From My HTC EVO 3D ROOTED
Flip35 said:
after doing this is not gonna mess anything up with me been rooted, i'm still gonna b able to flash roms n all that?
Click to expand...
Click to collapse
as you found out, the temporary fix won't "mess" with anything as long as you restore the su binary back to its default name.
larsdennert said:
After you rename the file you lose root. How do you regain root privilege to rename the file? Do you chmod? How do you mount rw?
Click to expand...
Click to collapse
you don't lose root by renaming the su binary. by renaming the su binary, you're ONLY changing the name of the su binary. the su binary does not require itself to be named "su" to execute properly. of course, make sure not to run chmod and remove the setuid bit on the file.
command: mv /system/bin/su /system/bin/jk
now, instead of having to type "su" for root, you'll type "jk" or whatever the new name of the su binary is.
also, you can configure adb shell to always drop to root access by toggling the ro.secure value, either 0 or 1, in the default.prop file which is stored inside the ramdisk of the boot.img kernel file. many custom kernels toggle this setting so adb shell always drops to root, even if no "su" binary exists on the system.
worse case, if for some reason you make a mistake, you can always boot into the custom recovery which provides root access via adb shell (ro.secure is toggle as such in the ramdisk of the recovery custom kernel) and setup root access again from there.
hope the additional information and technical details help!
Temp Root Remover
After using this app or manually renaming in Terminal Emu. Root is still detected by Pocket Blu. Any suggestions?
senjam1 said:
After using this app or manually renaming in Terminal Emu. Root is still detected by Pocket Blu. Any suggestions?
Click to expand...
Click to collapse
Really??? I've been using the app fr the market temp unroot remover n it works
my sister bought a samsung galaxy ace(gingerbread 2.3.4) I rooted it with upd_1.zip I install openvpn and followed every tutorial i saw how to get it work but i failed to get it work I'm so pissed of i deleted the bb folder in system/xbin/ using root explorer I first change its attribute then I delete it. And then to my surprised when i open the busybox it said the phone is not rooted...i unroot it to delete the super user using unroot.zip folder and again try to root it using upd_1.zip it only install super user but the phone is not rooted what is that mean? I tried to use super one click but i can't beacause it cannot detect the .netframework4...help me guys i want to again root my phone.
fusty07 said:
my sister bought a samsung galaxy ace(gingerbread 2.3.4) I rooted it with upd_1.zip I install openvpn and followed every tutorial i saw how to get it work but i failed to get it work I'm so pissed of i deleted the bb folder in system/xbin/ using root explorer I first change its attribute then I delete it. And then to my surprised when i open the busybox it said the phone is not rooted...i unroot it to delete the super user using unroot.zip folder and again try to root it using upd_1.zip it only install super user but the phone is not rooted what is that mean? I tried to use super one click but i can't beacause it cannot detect the .netframework4...help me guys i want to again root my phone.
Click to expand...
Click to collapse
bb ? File or folder ?
sir i deleted the bb folder on system/xbin including its content ipconfig and route,help me root my phone again sir.
but i am still guessing why would someone remove folder without any reason and that too in the system folders
i decided to delete that and make new bb folder and follow again the tutorial on configuring the openvpn not knowing that this will happen
Why don't you reflash with Odin to stock firmware and re-root?
@valexi reflash = upgrade firmware? And what is stock room sorry guys i admit i'm a noob when it comes to android...
fusty07 said:
upgrade firmware? And what is stock room sorry guys i admit i'm a noob when it comes to android...
Click to expand...
Click to collapse
THIS is perfect place for you then to start off
is it safe to flash my phone even though i delete some system files and my rom is gingerbread 2.3.4 is it ok if i flash it to gingerbread 2.3.4 also?
Yes, you can.
You will lose data though. Messages, contacts and apps. Backup those if you need to.
So I spoke with T-Mobile yesterday and they agreed to send me a new phone for exchange because of a faulty pin on my connector. I can charge my device but it will not detect a USB storage device when plugged in. I even took it to a mobile repair store and they told me the pin is beyond saving and the board would have to be replaced for around $75 bucks.
It just occured to me that I cannot ODIN to stock! Is there a method that does not involve a Phone to PC connection which will allow me to make this thing appear to be stock? (I am on custom rom and recovery obviously).
If not, what will happen to me if I just send in my current phone with the rom/recovery it is on? Do they actually check? My damage/issue is physical and not software related at all so would my warranty still be voided?
Any input would be immensely helpful! Thanks folks
When rooted warranty void
Sent from my SGH-T959 using Tapatalk 2
Search mobile odin
Sent from my SGH-T959 using xda premium
Find the latest stock rom and flash it. I think Moped_Ryder might have it. Ill give you the terminal commands to get rid of Root later on when I get to my PC.
Woodrube said:
Find the latest stock rom and flash it. I think Moped_Ryder might have it. Ill give you the terminal commands to get rid of Root later on when I get to my PC.
Click to expand...
Click to collapse
How would I get rid of CWM? Or do they not even care about that? Damn my new phone already came!
explodingboy70 said:
Search mobile odin
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I just found out about it actually. Looks like my device is not on the list of supported devices though :/
If I CWM flash a stock rom and stock kernel, is there a way to remove SU and return to stock recovery once again without connecting to the PC (ODIN). I have an SD card converter so I can freely move files to my external SD
Lo N Slo said:
How would I get rid of CWM? Or do they not even care about that? Damn my new phone already came!
Click to expand...
Click to collapse
Should be able to just uninstall it same as any other app, if you installed through ROM Mgr. If you use the update.zip method then it wont matter at all.
Here is the code to remove Root. Just download any terminal from the market and run this.
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot
Code will still work to remove Root on any device. I've done it on my tablet before just for kicks to make sure it works. It does, so it should work on SGSII also. You are on your own for the stock ROM though.
Woodrube said:
Should be able to just uninstall it same as any other app, if you installed through ROM Mgr. If you use the update.zip method then it wont matter at all.
Here is the code to remove Root. Just download any terminal from the market and run this.
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot
Code will still work to remove Root on any device. I've done it on my tablet before just for kicks to make sure it works. It does, so it should work on SGSII also. You are on your own for the stock ROM though.
Click to expand...
Click to collapse
Awesome! Will run after I flash the Stock rom link I posted above. I am assuming that removing CWM is just impossible without connection to PC?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Lo N Slo said:
Awesome! Will run after I flash the Stock rom link I posted above. I am assuming that removing CWM is just impossible without connection to PC?
Click to expand...
Click to collapse
If you are returning to complete stock it should automatically revert to stock recovery also
Sent from my SGH-T959 using XDA Premium App
Running ICS Passion
Hi folks
I hope I am not breaking any rules. I tried my best to read up on the problem and see if it's already been fixed. So far I haven't encountered anything which is specific to my needs, but I learned enough to pose a well-formed question.
Phone: Samsung Galaxy SIII International (GT-I9300)
ROM: Stock Samsung, version 4.1.2, the update with Multi-window. Do not have the exact build number unfortunately.
Root status: Rooted
Recovery: Stock recovery. (I JUST rooted the phone, nothing else.)
So the problem is:
1. I used ES File Explorer in root mode, mounted /system as writable, and made an edit to build.prop (added "qemu.hw.mainkeys=0" to the end of the file to enable navbar) and saved the file. I rebooted the phone and now it is stuck with a looping Samsung logo.
2. I have made a backup of build.prop and placed it in /sdcard/ but unfortunately I haven't made a copy on my PC. Also note that I don't have an external SD card, I am using the 16GB space that came with the phone. So the build.prop backup is on the phone.
3. I do not have a USB cable (I have one that has a loose connection somewhere and my phone is not detected 99% of the times I've used that cable)
What I have found after 2 hours of searching online:
1. Factory Reset through recovery (I am able to boot into stock recovery by doing Vol Up + Home + Power) will not restore /system partition so that won't fix this.
2. ES File Explorer might have messed up the file permissions of the build.prop file.
3. I can use PC ODIN to flash the stock firmware (I might lose data but at least the phone would be back to normal).
4. I can use adb to push a good build.prop file and set the correct permissions (my most fav. set of instructions are from here: http://forum.xda-developers.com/showthread.php?t=1660596 Of course I got the idea from several other threads)
5. I can sideload a good build.prop file that someone might be generous to provide me using adb.
I don't have a data cable, so you can see how that Might be a problem. What I DO have is a USB OTG cable and a pen drive. Now, in the stock recovery, I noticed an option "apply update from external storage". Assuming I have an update.zip with the proper build.prop in it, can I load the update.zip into a usb pen drive (formatted to fat32)? Does "apply update" here work for such zip files or is it only meant to be used for full firmware images? If so, can I just download the latest stock firmware and apply it from here without wiping the /data partition?
If I can get this resolved tonight I can get my phone up and running before tomorrow's work week. I will buy an USB cable ASAP (it's 12 AM here so going out to get it is not an option now). But even if I do, I still have 5 months worth warranty left and I'd like to stick with the stock recovery and avoid incrementing the flash counter altogether, despite Triangle Away.
Thank you very much for the help in advance.
Adb pull your backup» then push it back?
slaphead20 said:
Adb pull your backup» then push it back?
Click to expand...
Click to collapse
I don't have a working data cable, so I cannot connect to the PC. That was my first idea, though, thanks! I am currently reading about making an Update.zip. It's very unfortunate that I didn't note my firmware details after the OTA...
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work.
LenAsh said:
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work. If not try 777 for giggles.
Click to expand...
Click to collapse
I am unable to boot into the phone, it is stuck in a bootloop
I don't have a USB cable to use ADB. I don't even have a custom recovery. All I have is the stock recovery and the option to "apply update from external storage". I now remembered that I also have an SD card on which I can put an update.zip or the stock firmware. Unfortunately I didn't note down the firmware details after the last OTA from 4.1.1 to 4.1.2, so I don't know which one to download.
Can I use the option "apply update from external storage" to flash an update.zip or is that only meant for full firmwares? Thanks!
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
LenAsh said:
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
Click to expand...
Click to collapse
Fix permission option on the stock recovery? I don't think so, haven't been able to find it. Here are the options I have:
reboot system now
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Interestingly, when I selected the last option, it had these 3 folders:
fota/
lost+found/
recovery/
I was hoping fota/ had the files from my last OTA update but nope.
I guess you are not sure whether I can flash an update.zip through stock recovery... so I just have to wait till I get my USB cable and try out some adb magic?
EDIT: I'm retiring for the day. Thanks for the suggestions @LenAsh and @slaphead20. I'm gonna buy a cable next week and try to set the permission to 644 (RW-R-R) using this thread as my reference (http://forum.xda-developers.com/showthread.php?t=1660596). Thanks for your suggestions, I will post back when this is all resolved.
In the meanwhile, please keep the ideas coming
PS: Oh wait, I am still curious. What is the worst thing that could happen if I try to flash an update.zip through stock recovery? I am very curious to see if it will work.
You could flash a later custom recovery (this one works well http://forum.xda-developers.com/showthread.php?t=2002953) via Odin and then fix permissions that way. Even if that doesn't work, you could then flash anything you like without having issues that the stock recovery presents.
EDit: still need a cable though...
Trouble is he hasn't got a cable, I had same thinking, that he could use the aroma file manager in philz but he's stuffed without a cable!
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
LenAsh said:
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
Click to expand...
Click to collapse
Just edited my post
Sent from my GT-I9300 using xda premium
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
ficti0n851 said:
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
gautham_y said:
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
Click to expand...
Click to collapse
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
black_hawk1990 said:
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
Click to expand...
Click to collapse
Hey, are you still having problems or did you solve it yourself? Anyway... If you still don't know what to do, describe best what you did to end up in a bootloop. As far as I understand what your problem is, you should use your recovery to move the backup of the original build.prop file to the system folder.
I changed my phones build.prop and when rebooted it does not started and ended up in bootloop and when I searched for how to fix this problem it showed that clear all the data from the phone but nothing happened and when I tried to install custom ROM in my phone my pc is not detecteing my phone .so what should i do ?
@Rajsh90: pull out battery for some minutes, put it in, reboot into downloadmode. Connect with PC, start Odin and hope that a COM-flag colours. Flash latest firmware.