Related
Hi,
So I tried the [MOD] Reboot Options in Power Menu in http://forum.xda-developers.com/showthread.php?t=836942 and now my phone won't boot it gets stuck on the Sony Ericsson Logo. I backed up the original three files, but I am not able to push them back to the phone via ADB, as it refuses to mount the File system in write mode.
It has been suggested to reflash system.sin using Bin4ry's flash tool. I'm downloading the X10i_2_0_A_0_504_NORDIC which is what my phone had already. Do I just remove all the files from the firmware folder except system.sin ?
Alternatively any way I can mount the filesystem as write and push files to /system ?
Cheers
don't worry I fixed it.
mookie3three said:
don't worry I fixed it.
Click to expand...
Click to collapse
Would you mind telling us how you did it???
I am messing with my framework a lot, and a solution like this could come in handy, just in case!
Also, did you lose any of your data and apps?
My_Immortal said:
Would you mind telling us how you did it???
I am messing with my framework a lot, and a solution like this could come in handy, just in case!
Also, did you lose any of your data and apps?
Click to expand...
Click to collapse
In the "old" flash, non-gui, there is an option to "not erase user data"
It may work for what you want.
I uninstalled the Protips.apk without doing a backup first and now need to restore it so the OTA update completes. I have the file from another Photon but how do I go about getting it installed? I moved it to /system/app/ with Root Explorer but it won't install.
Do I need to push it with adb? If it somehow needs to be re-signed I'm not sure how to sign w/system signatures.
What steps can I use to complete this?
Thanks.
download the cm5 from yays thread in the dev section and then using 7zip (providing you are using windows) take everything out except protips app and flash it through recovery
If it will flash via recovery and work then would there be a reason why I can't push it via adb? The file that was sent to me should still have the original signature attached correct?
I was trying to avoid unlocking the bootloader and having to install custom recovery.
CCallahan said:
If it will flash via recovery and work then would there be a reason why I can't push it via adb? The file that was sent to me should still have the original signature attached correct?
I was trying to avoid unlocking the bootloader and having to install custom recovery.
Click to expand...
Click to collapse
I THINK that you can flash the via bootstrap recovery. If not try pushing with adb and before you reboot typing
Code:
sync
reboot
[email protected] said:
I THINK that you can flash the via bootstrap recovery. If not try pushing with adb and before you reboot typing
Code:
sync
reboot
Click to expand...
Click to collapse
I pushed it but not sure about the sync command. Do I need to use "adb sync /system/app/"? It is asking me for a directory but don't know what I am supposed to be syncing.
**EDIT...NM. I need to know the exact syntax for the adb sync command I need to use. Nothing is working. Also, I do not have permission to run the remount command. Does this mean the system may still be read only?
Thanks.
CCallahan said:
I pushed it but not sure about the sync command. Do I need to use "adb sync /system/app/"? It is asking me for a directory but don't know what I am supposed to be syncing.
**EDIT...NM. I need to know the exact syntax for the adb sync command I need to use. Nothing is working. Also, I do not have permission to run the remount command. Does this mean the system may still be read only?
Thanks.
Click to expand...
Click to collapse
Okay try this.
1st put the protips.apk on your sd card then
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /sdcard/protips.apk /system/app
sync
reboot
this should work
You know do don't actually install the apk. Just drop it in the system/app folder in reboot.
Perhaps I misunderstood your problem.
ptfdmedic said:
You know do don't actually install the apk. Just drop it in the system/app folder in reboot.
Perhaps I misunderstood your problem.
Click to expand...
Click to collapse
Yes. However it seems the Protips.apk I have might not be signed properly because it never installs upon reboot. So I was trying to find a way to make this work.
ptfdmedic said:
You know do don't actually install the apk. Just drop it in the system/app folder in reboot.
Perhaps I misunderstood your problem.
Click to expand...
Click to collapse
won't work because we don't have remount available now.
CCallahan said:
Yes. However it seems the Protips.apk I have might not be signed properly because it never installs upon reboot. So I was trying to find a way to make this work.
Click to expand...
Click to collapse
Did you try what i had suggested above (cp from sdcard mount file system sync reboot)???
[email protected] said:
won't work because we don't have remount available now.
Did you try what i had suggested above (cp from sdcard mount file system sync reboot)???
Click to expand...
Click to collapse
Not yet...had to make some dinner. Going to try it here in a sec.
Thanks.
[email protected] said:
Did you try what i had suggested above (cp from sdcard mount file system sync reboot)???
Click to expand...
Click to collapse
Tried it. All commands went through without issue. After reboot I tried doing the update but when it scans for existing files it still stops at 30%. It is still either not finding Protips.apk or there is something wrong with the file I have. A friend of mine emailed to me in an attachment. Don't know of any other way to get it without knowing how to properly extract an sbf file. Maybe if someone has a TB backup of it and could send to me? Then I could try restoring it. Not sure if something like that would be worth a try.
CCallahan said:
Tried it. All commands went through without issue. After reboot I tried doing the update but when it scans for existing files it still stops at 30%. It is still either not finding Protips.apk or there is something wrong with the file I have. A friend of mine emailed to me in an attachment. Don't know of any other way to get it without knowing how to properly extract an sbf file. Maybe if someone has a TB backup of it and could send to me? Then I could try restoring it. Not sure if something like that would be worth a try.
Click to expand...
Click to collapse
protips is the only thing that you don't have?
I am not sure. this thread has the ota as an sbf. I saw in another thread you were worried about having to reactivate again. The phone will program over the air you won't have an issue at all. I wish I could help you get protips installed correctly but I am still finding my way around moto. I guess that the mount command we used could be wrong. Not sure :/
[email protected] said:
protips is the only thing that you don't have?
I am not sure. this thread has the ota as an sbf. I saw in another thread you were worried about having to reactivate again. The phone will program over the air you won't have an issue at all. I wish I could help you get protips installed correctly but I am still finding my way around moto. I guess that the mount command we used could be wrong. Not sure :/
Click to expand...
Click to collapse
Yes. I deleted Protips.apk after rooting and didn't make a backup. The update errors every time because of that file not being installed it seems. Do you think that leaked OTA would restore the missing apk?
CCallahan said:
Yes. I deleted Protips.apk after rooting and didn't make a backup. The update errors every time because of that file not being installed it seems. Do you think that leaked OTA would restore the missing apk?
Click to expand...
Click to collapse
This leak is the same as the OTA. The only difference between installing this and downloading the OTA is having to reset everything up.
[email protected] said:
This leak is the same as the OTA. The only difference between installing this and downloading the OTA is having to reset everything up.
Click to expand...
Click to collapse
I'm gonna go ahead and try to figure out how to do the leaked one. I pulled the Protips.apk from Juggs file and still doesn't work. Weird that I can't go to it in Root Explorer and just install it.
Anyways, phone has been factory reset anyways so I'm not worried about having to set it all back up.
Thanks for your help.
Did you set the proper permissions for it?
CCallahan said:
Tried it. All commands went through without issue. After reboot I tried doing the update but when it scans for existing files it still stops at 30%. It is still either not finding Protips.apk or there is something wrong with the file I have. A friend of mine emailed to me in an attachment. Don't know of any other way to get it without knowing how to properly extract an sbf file. Maybe if someone has a TB backup of it and could send to me? Then I could try restoring it. Not sure if something like that would be worth a try.
Click to expand...
Click to collapse
Beach_Head said:
Did you set the proper permissions for it?
Click to expand...
Click to collapse
Yes. Still wouldn't work. Only thing I didn't try is modifying the update.zip and flashing just to restore the missing apk.
Did you also return the Protips.odex file?
That's the only other reason why the update wouldn't work...
CCallahan said:
Yes. Still wouldn't work. Only thing I didn't try is modifying the update.zip and flashing just to restore the missing apk.
Click to expand...
Click to collapse
Beach_Head said:
Did you also return the Protips.odex file?
That's the only other reason why the update wouldn't work...
Click to expand...
Click to collapse
I can't believe I didn't think of that
Sent from my MB855 using xda premium
No...I didn't.
Oh well. Too late now.
Thanks for the tip.
Hello there. As you will notice, I am new to this forum. I own the Xperia U (ST25i) handset, and currently run the .564 firmware. Unfortunately for me and multiple others, my bootloader is locked, and my phone is also SIM locked to Three UK. Now, I am aware that for users with an Xperia S, there is a method to obtain root access through downgrading to Gingerbread, then running a script of some sort and updating to ICS. But, as there is not an ICS update for the Xperia U as of yet, this method does not work. But I'm thinking; surely if the exploit RUNS in gingerbread, it could get access to system files and such, without the need of ICS? My understanding is slim, granted. But I'm familiar with rooting, ADB commands and the Android file structure.
I would like for anybody with knowledge to help in this, as it could potentially be a breakthrough in rooting all NXT Xperia devices without losing warranty.
Many thanks,
-Pokoby
UPDATE
Having modified the .bat files and testing both the original and the modified versions of them, I can confirm they do not work. The problem lies in gaining root shell access. ADB shell always comes up with a $, rather than a #. This means there is no access to any of the files in /system/, /data/ or any derivatives. Unfortunately, that is where all of the files used to root are kept. I would love to work at a way around, and will help in any way I can.
-Pokoby
I have a xperia U with LB also. I´m not a developer but it would be great if someone could help with this idea.
gengi said:
I have a xperia U with LB also. I´m not a developer but it would be great if someone could help with this idea.
Click to expand...
Click to collapse
Well, it'd be a tonne of help if you'd test my work with me
I've managed to get shell root, but for some reason it still will not let me push files to /system/ or to the /data/ partitions. Finding out a workaround. Although, I've noticed a "recovery" folder created in /mnt/sdcard/ by default (after I factory restored my ST25i). Wondering if the phone crashes, it'd load a .sin or .img file from it?
If anyone can help, do all NXT line devices have this folder in their /mnt/sdcard?
-Pokoby
Never noticed that. I´m upgrading my software and i you´l see if i have one named recovery.
Edit: I also have that folder. Any idea?
gengi said:
Never noticed that. I´m upgrading my software and i you´l see if i have one named recovery.
Edit: I also have that folder. Any idea?
Click to expand...
Click to collapse
Kind of. On one of my friends' crappy Chinese android phones had one, and it booted either a .elf or recovery.img file from it if the system crashed in some way (as in total lock up, not just an app force closing). I may have to test this, but Sony aren't stupid, so I reckon it'll have something to do with engineering.
This is a folder created by system because i deleted and made a hard reset and the foder was there again. What is the purpose of that folder? How can we use it?
gengi said:
This is a folder created by system because i deleted and made a hard reset and the foder was there again. What is the purpose of that folder? How can we use it?
Click to expand...
Click to collapse
So far, I put the file for ClockworkMod Recovery in there. I made a batch file which essentially sends a couple hundred bizarre requests through ADB, which crashed the phone. Phone froze, did a reboot but no luck. I don't think there's any prime reason for it.
it´s not possible to put a rooted image file in there and use it somehow?
nope
nickholtus said:
nope
Click to expand...
Click to collapse
Can´t you lie??? looool...
---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------
More serious now.
Why does exist that folder?
Well good luck.
Realising that the recovery folder was relatively pointless from a rooting standpoint, I have managed to compile a bunch of .bat files which can and have successfully rooted my Xperia U. I believe I'll need to get permission from whoever made zergRush to distribute this, unless somebody tells me otherwise. Nevertheless, it is a modified version of zergRush. If you want technical details, PM me about it and I'll be happy to talk. But all it does is gain shell root access and push files, in a very similar way to that of the Xperia S rooting method.
I'll hopefully have an upload later today, but in preparation:
Use Flastool to flash the stock .564 firmware
Wipe EVERYTHING in Flashtool
Reflash the .564 firmware without wiping /data/ and such (Not too sure if necessary, but is required in the process)
Make sure you have the correct drivers installed for ADB and such (A no brainer)
Pokoby said:
Realising that the recovery folder was relatively pointless from a rooting standpoint, I have managed to compile a bunch of .bat files which can and have successfully rooted my Xperia U. I believe I'll need to get permission from whoever made zergRush to distribute this, unless somebody tells me otherwise. Nevertheless, it is a modified version of zergRush. If you want technical details, PM me about it and I'll be happy to talk. But all it does is gain shell root access and push files, in a very similar way to that of the Xperia S rooting method.
I'll hopefully have an upload later today, but in preparation:
Use Flastool to flash the stock .564 firmware
Wipe EVERYTHING in Flashtool
Reflash the .564 firmware without wiping /data/ and such (Not too sure if necessary, but is required in the process)
Make sure you have the correct drivers installed for ADB and such (A no brainer)
Click to expand...
Click to collapse
will there ever be a way to root without wiping data etc? i've only recently upgraded to ics, and my phone is set up exactly as i want it now, except battery life is awesome, so i want to root so that i can use setcpu or similar to underclock.
Gloris said:
will there ever be a way to root without wiping data etc? i've only recently upgraded to ics, and my phone is set up exactly as i want it now, except battery life is awesome, so i want to root so that i can use setcpu or similar to underclock.
Click to expand...
Click to collapse
Which phone are you using? There isn't an ICS ROM for the Xperia U. If you have the Xperia S, there's a seperate rooting guide available on these forums
Did you realy found way to root Xperia U,cant wait you upload files.
Hope it will work because I just need root,custom kernel is pointless.
Sent from my ST25i using Tapatalk 2
XperianPro said:
Did you realy found way to root Xperia U,cant wait you upload files.
Hope it will work because I just need root,custom kernel is pointless.
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
I shall upload screenshots shortly, hang on.
EDIT
Root access from the terminal emulator, here y'ar
Nice.
Sent from my ST25i using Tapatalk 2
XperianPro said:
Nice.
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
Gonna have a go at some ADB pushing and pulling. Might do some little tweaks in build.prop, as a test. Will keep you all updated, and will hopefully release soon!
If you got it you are my idol !! looool...
Pokoby said:
Gonna have a go at some ADB pushing and pulling. Might do some little tweaks in build.prop, as a test. Will keep you all updated, and will hopefully release soon!
Click to expand...
Click to collapse
Use script that will just add lines to build.prop instead of replacing it whole if possible.
Sent from my ST25i using Tapatalk 2
Hi!
I have the following (cosmetic, i know...) issue: after formatting data for a clean install, i still have a folder which won't go away (see attachment). it contains files with corrupt names, and I could not delete it in any way (format, using CWM, deleting from phone or PC)
I think a PIT fash would do the trick, but I am afaid its not worth it for being too risky.
Does anyone have any tips or tricks to get rid of these files?
Coirpre said:
Hi!
I have the following (cosmetic, i know...) issue: after formatting data for a clean install, i still have a folder which won't go away (see attachment). it contains files with corrupt names, and I could not delete it in any way (format, using CWM, deleting from phone or PC)
I think a PIT fash would do the trick, but I am afaid its not worth it for being too risky.
Does anyone have any tips or tricks to get rid of these files?
Click to expand...
Click to collapse
Mango? you have a fruit folder?
don't go pitting now. Root explorer wouldn't delete that?
gastonw said:
Mango? you have a fruit folder?
don't go pitting now. Root explorer wouldn't delete that?
Click to expand...
Click to collapse
looks like its re-generating.. maybe that directory is part of your rom
bytes2000 said:
looks like its re-generating.. maybe that directory is part of your rom
Click to expand...
Click to collapse
gastonw said:
Mango? you have a fruit folder?
don't go pitting now. Root explorer wouldn't delete that?
Click to expand...
Click to collapse
I tried deleting from PC and with solid explorer (with root) which was unsuccesful. The folder is the library of a comic reader app, thus not system relevant. Depending of the program I use to try to delete it, I get: "File or folder not found (CM File Manager), "unable to delete file /.../ö°Ñ5 π.∞..." (Solid Explorer), and on the PC, I can see a few files with names such as └éQ┬¾╠/Ú.┼, which can not be deleted, because they "can not be found."
does this help?
http://forum.xda-developers.com/showthread.php?t=2083682
Have sent that other guy a pm...
MistahBungle said:
http://forum.xda-developers.com/showthread.php?t=2083682
Click to expand...
Click to collapse
911-Future_Maker said:
Hi mate. Have you tried flashing with Odin? This way I fixed formattiing my sdext2 partition which was unaccessible at all.
You may try to flash some other CWM recovery like Philz and then delete those files.
Click to expand...
Click to collapse
I can't quite understand this. not enough information, I have almost no knowledge whatsoever about filesystems. Should I flash with odin? a rom? or a new CWM?
Why ? You've got the fix
Reminder: "don't mess with mangos"
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.