Hello all. this all started when i was editing build.prop to download an app in the store that was incompatible with my device.
I was editing my build.prop file on my note 2 (tmobile) and i was smart enough to make a copy before doing that, i just copied it to a random place the "downloads" folder, seemed like an easy place to remember.
After failing at editing the build.prop and getting the app i wanted, i decided to put the original build.prop back in the system folder and just give up.
Well im not sure what happened here, i think i deleted the edited one and tried to paste the original one, when i rebooted my phone, it wont boot up, screen wont come on when it boots up, etc.
now i know there is a good copy of build.prop in the downloads folder so for the past hour ive been trying to get that and place it in the system folder, im a complete noob to adb, which is what im using to try and poke around in there, but im horrible with the commands, and cant LOCATE the "downloads" folder, where i was planning on pulling the build.prop file, and then pushing it to the system folder.
I cant find online what the folder structure is like, and i cant view it because my phone wont start.
Can someone PLEASE help me getting to the downloads folder in adb, the command to pull the build.prop file, and then getting to the system folder (i have root access and everything) and pushing the build.prop file into there.
I think that should solve my problem, id even give 5 bucks on paypal or something if someone can give me an easy list of commands i need to do in adb.
THanks in advance everyone. I hope this is in the right subforum.
Jay
i dont know if its in /data/downloads or /sdcard/downlads or what, its so hard without being able to see what folders are where. none of them seem to work.
If i cant get to that file and copy it into its home, i suppose i can always reflash.
Hey may be i can help. U wipl have to get to the fastboot mode or that is called odin mode in samsung phones.u can reach to odin screen pressing vol+ + vol- + homebutton +the power button at the same time.now connect ur phone with the computer.remember that u will have to donwload the odin software for ur windows.in odin software in windows u can flash recoveries,boot images and much more.now download a suitable philz touch recovery or a twrp recovery.U can now connect ur phone to computer under recovery mode and u will have to mount the storage also the sd card will be shown to ur computer.may be this helps...
Sent from my A0001 using XDA Free mobile app
I have CWM recovery, and i have odin installed on my computer, I dont have an external sd card, only the "internal" one if that makes sense.
I just need to get to the downloads folder in adb. my phone isnt showing up in mycomputer when i am in recovery mode or odin mode it seems.
Bro u will have to flash a advanced touch recobery like philz.falsh it using odin.
Heres the detailed procedure.
Download these files
1) Unzip Odin3-v1.85.zip
2) Open the 'Odin3 v1.85.exe' file
3) Install samsung drivers
4) Put phone in download mode by powering off and holding volume up + volume down while plugging the phone into the computer
5) You should now see the first square in Odin turn yellow and say "Ready"
6) Click on the pda tab in Odin and select the recovery.tar.md5 you downloaded
7) Click start and wait for your phone to reboot
8) Done!
Sent from my A0001 using XDA Free mobile app
and what will that allow me to do, browse all the folders on my phone with root access in windows explorer?
No u will not have root access but u can explore all ur internal storage.
Sent from my A0001 using XDA Free mobile app
I cant seem to download the version for my phone, i think the hosting ran out...
http://forum.xda-developers.com/showthread.php?t=2552673
yeah i was reading about it, this seems like it would help, if i could find the right file to download.
I cant send links here...
But i have private messaged u..
What is ur phone model lte? Or simple tell me
Sent from my A0001 using XDA Free mobile app
im not sure to be honest. checking PM now
Check i have sent the pink for the philz in the end of pm
Sent from my A0001 using XDA Free mobile app
If you're using a custom ROM, the easiest thing to do would be to do a "dirty" flash of your ROM (no system wipe via recovery, only your cache). You won't lose any user data but things like the build.prop would be restored.
It also helps to have a backup so that you can simply restore it via recovery when trouble arises.
Related
umm so when i press back after the se logo appears nothing happens and it boots normally. im trying to go into recovery any suggestions?
You must press it lots,
Also when you install xrecovety your rom must be read write and not read only. Use a root explorer and set it to read write then try install the xrecovery apk u must get ticks for the last 3 otherwise your system is not read write. I used supermanager then file explorer then options mount system as rw then without closing super manager (just pressed home key) went to apps and installed xrecovery.
Then when you restart just keep tapping back at se logo screen.
Hope that helps
Sent from my X10i. Rooted jit enabled xrecovery loaded 2.1 asop lite using XDA App
Thanks will try again when wife gets home she wanted 2.1 tryed last night and it just wouldn't work.
Sent from my SAMSUNG-SGH-I897 using XDA App
Oh by the way I dropped the rom in on her sd card as stated and left it as a zip file I don't know if that means it's read write. And I used root explorer and put the three files of the apk where they said put it. And the only way I could copy it to its destination was if it was read write. So I believe I did everything correctly i just couldnt go into recovery. But you say press back more than twice so thats what must be the problem.
So I keep pressing back until xrecovery shows up? ... just too clarify
Sent from my SAMSUNG-SGH-I897 using XDA App
Tchem said:
Oh by the way I dropped the rom in on her sd card as stated and left it as a zip file I don't know if that means it's read write. And I used root explorer and put the three files of the apk where they said put it. And the only way I could copy it to its destination was if it was read write. So I believe I did everything correctly i just couldnt go into recovery. But you say press back more than twice so thats what must be the problem.
So I keep pressing back until xrecovery shows up? ... just too clarify
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
first, u need to get xrecovery works...
try this link..
reads carefully...
http://forum.xda-developers.com/showthread.php?t=859571
*in root explorer, there are grey button at the top right side...
mount r/w...hit the button whenever u want to paste the file..
thats mean read write...
then, u need to install the rom...
try this link...
http://forum.xda-developers.com/showthread.php?t=876548
for sure, press back button until u enter recovery menu...
multiple press...not long press...
if ur phone boot normally to rom, then your xrecovery is not working cause by false install..
I have an S-OFF HTC Incredible S 4G running 2.3.3 trying to get it rooted, I am trying to keep up but so use to stupid iPhone modding/themeing so just lost on how to send or use my SD card for ROMS? Can I just use the old word (shsh) files over to my phone while its plugged in its the Fdisk and do I put the files into 'root', I have installed Superuser app/ROM Manager app onto my phone also have Gingerbreak.v.120apk on my desktop plus Superuser.apk am I lost or what and anyone willing to help but go easy on me?
Thanks, TheCrow
Do you have ClockworkMod Recovery installed?
I have ROM Manager installed off the Market but my question is probably the one that I'm can't get the answer for which is, how do I transfer things onto my SD card cuz I have played a lot with my old iPhone 4 with mods/themes and so on but never had to write to my SD card atleast I don't think I did thats why I ask if its as easy as dragging and dropping files over to my phone while its plugged into my computer as 'use as driver'? I can't even get the CWM to work properly because it says something about 'special privillages', I have S-OFF but just want to get rooted so I can move on to the fun . Do I need something set on my phone or installed to get going, I also put Superuser & Astro on my phone from the Market so can if you have the time just give me a few dumby steps to point me in the right direction and I am over at the Android Newzealand site which is awesome but they get most files from here and only one guy is trying to help
Thanks, TheCrow
@Crow1372
I am all about trying to get things done in the easiest way possible to help the people that are new to Android.
This method has worked for me but there is no guarentee that it will work for you and I am no way responsible for anything that happens to your device.
DO THE ROOTING PROCESS AT YOUR OWN RISK
Procedure to Root HTC Incredible S
1. Install the ADB on your computer, but before that you will have to turn on the USB debugging in your incredible S which can be turned ON by pressing the “Menu” key first then “Settings” > “Applications” > “Development”. Now here you will find an option of “USB debugging”, select the option and just accept the warning which it will pop up. It’s very important to put the device in the USB debugging and also important to go through the ADB setup process without which it’s not advised to proceed.
2. Now you will have to download the Rooting package which you will have to unzip the same and need to place in the location path c:\adb after which you will have to connect the phone to the computer.
3. Now, open the command prompt and key in the “cmd” and then you will have to make use of the change directory command so that the directory in which you have placed the rooting file can be accessed.
4. Next type in the “pushroot” and enter the same, basically this will push in the pushroot.bat file.
After this type in adb shell /data/local/tmp/getroot and after that type in adb shell and press enter.
After typing in the above commands, you will now be prompted as # after which you will have to type in /data/local/tmp/pushroot.
That’s it you have now successfully rooted the HTC Incredible S
TheCrow1372 said:
I have ROM Manager installed off the Market but my question is probably the one that I'm can't get the answer for which is, how do I transfer things onto my SD card cuz I have played a lot with my old iPhone 4 with mods/themes and so on but never had to write to my SD card atleast I don't think I did thats why I ask if its as easy as dragging and dropping files over to my phone while its plugged into my computer as 'use as driver'? I can't even get the CWM to work properly because it says something about 'special privillages', I have S-OFF but just want to get rooted so I can move on to the fun . Do I need something set on my phone or installed to get going, I also put Superuser & Astro on my phone from the Market so can if you have the time just give me a few dumby steps to point me in the right direction and I am over at the Android Newzealand site which is awesome but they get most files from here and only one guy is trying to help
Thanks, TheCrow
@Crow1372
Click to expand...
Click to collapse
Try reflashing CWM Recovery. Since you have S-OFF, it should work. If you get it to work, then flash (install zip from SD in CWM) the attached file and you should be rooted.
Theonew said:
Try reflashing CWM Recovery. Since you have S-OFF, it should work. If you get it to work, then flash (install zip from SD in CWM) the attached file and you should be rooted.
Click to expand...
Click to collapse
I appreciate the one above yours and kinda understand it but waaay too indepth maybe, I also tried yours but when I go to HBoot menu and Recovery to look for the .zip file it is no where and I plugged my device into computer and 'debugging Enabled' also set my connection as 'disk drive' to load the file to my SD card but still can't find it?? I can't believe it is this hard cuz I see many others rooted and flying away on their Incredible S 4G, I was able to get the Gingerbreak.v.1.20apk on my device but it just keeps loading and saying that it will reboot once successful but after 20-30mins I figured it was not going to work also I have ROM Manager installed already but as you know no Superuser previlliages yet so can't load CWM
TheCrow1372 said:
but as you know no Superuser previlliages yet so can't load CWM
Click to expand...
Click to collapse
Have you tried searching for the zip when your device is NOT connected to your pc? And just so you know, you do NOT need superuser privileges (root) to be able to use ClockworkMod especially since you already have S-OFF. Have you tried flashing a different version of ClockworkMod? You could try using this: http://forum.xda-developers.com/showthread.php?t=794638 to flash it from your PC.
Theonew said:
Have you tried searching for the zip when your device is NOT connected to your pc? And just so you know, you do NOT need superuser privileges (root) to be able to use ClockworkMod especially since you already have S-OFF. Have you tried flashing a different version of ClockworkMod? You could try using this: http://forum.xda-developers.com/showthread.php?t=794638 to flash it from your PC.
Click to expand...
Click to collapse
I'll try finding it without being plugged in to pc, I put Gingerbreak.v.1.20apk on my SD card no issues so I shouldn't have an issue putting the CWM on but do you have a newer version (sorry) also do you think one of my issues is that I have a CWM on my 'Astro' file finder but the files say they don't exist so should I delete it and start over with a newer one that you may have and should I take of ROM Manager until I finish putting these files in cuz it should not be this hard others are rooted on their Incredible S 4G 2.3.3.
TheCrow1372 said:
so I shouldn't have an issue putting the CWM on
Click to expand...
Click to collapse
Please explain this. Here's the image: http://downloads.unrevoked.com/recoveries/cwm-4.0.1.4-vivo.img .
I can't open that image, my Winrar is acting up can you explain the image please (sorry)?
Also when I go to my 'Programs' on my computer 'Uninstall' it shows the SDK Tools with an 'X' beside it like it did not fully install, I don't know if I really need the ADB & SDK tools but I'll keep trying that later but I want to try your methods as well cuz as I mentioned it should not be this hard to root my phone right but I have to go to Doctors so I will check in later and keep trying
TheCrow1372 said:
I can't open that image, my Winrar is acting up can you explain the image please (sorry)?
Click to expand...
Click to collapse
You are not supposed to open the image. Download Android Flasher, connect your device to your pc, run Android Flasher, select recovery (at the side), find the image file you downloaded, select it, click ok (and again if necessary), and it'll do the rest.
Question, I drag and drop files over to my phone while plugged in to my SD card but everyone says to the root folder I just don't have a 'root' folder so one guy said to drop the files into the very first one and that is what I did with Gingerbreak.v1.20apk but it just says its rooting and will reboot device when done? After 3 attempts each at 15-25mins the wheel is still spinning so am I putting it in the right spot, Gingerbreak does show up in my apps drawer but the unzipped versions of CWM or Superuser never show up on my device even when I go to 'recovery' through Revolutionary to unzip it?
TheCrow1372 said:
Question, I drag and drop files over to my phone while plugged in to my SD card but everyone says to the root folder I just don't have a 'root' folder so one guy said to drop the files into the very first one and that is what I did with Gingerbreak.v1.20apk but it just says its rooting and will reboot device when done? After 3 attempts each at 15-25mins the wheel is still spinning so am I putting it in the right spot, Gingerbreak does show up in my apps drawer but the unzipped versions of CWM or Superuser never show up on my device even when I go to 'recovery' through Revolutionary to unzip it?
Click to expand...
Click to collapse
Did you read/understand my previous post?
Kinda but how does that have anything to do with rooting my Incredible S (sorry) its just that I'm new to HTC devices and I've been told that I have to be rooted to put ROM themes on my device and I have S-OFF, thats not enough is it? I tried the guy above yous method of ADB but my computer does not 'recognize that path', I did exactly what his video says but again is either of these methods going to get me 'rooted cuz all I want to do is start enjoying my phone plus your saying I don't have to have 'Superuser Permissions' to use CWM?? Sorry bro if I'm being difficult but I just want to be rooted already and have you heard of this angermod or what ever its called, like Gingerbreak or something?
HELP PLEASE lol, thanks
Forget about Gingerbreak. The tool (and instructions) is to flash the custom recovery (ClockworkMod) to your device. I said this before, and I'll say it again, using ClockworkMod recovery DOES NOT require root. You are going to root your device by using Clockwork to flash the file attached in post #5. After flashing that file, your device will be rooted.
When I go to extract it they ask for a gehroot password, I copied what looks like a password under my Incredible S/Vivo but that one did not work for the CWM download
I will try this tomorrow 4 sure and thanks for your patients, fill you in when I'm rooted (hopefully) Also is there a special password to download the CWM for my Incredible S/Vivo, sorry again?
One more question (sorry) the one I did download the other day was supposed to be CWM but it has all kinds of other files with it like 13 files including 'SuperOneClick' also suv1/v2/v3 plus 'busybox' but don't see cwm anywhere so anyway do I use the 'Android Flasher' and flash all of them like the whole folder or each one individually?
In the CWM image file, there are like 13 files that came with it like suv1/v2/v3 plus busybox and SuperOneClick so which or all of these files do I flash with Android Flasher?
I'm having an issue flashing a ROM via the sdcard zip file option.
I have (afaik) successfully installed CWM. Had an issue at first with it rebooting every 30 secs but reflashed the kernel and now it seems to work ok. However, when I try to flash a rom and go to the sdcard zip file option, it'll list several folders but not the ROM I want to flash. I have put the ROM on the sdcard in no folders (root folder) and am really at a loss.
I apologize in advance for any n00bish ways. I went through 2 cycles on iOS devices and decide to forgo the jailbreak cat and mouse chase and go android. I haven't regretted it yet. But I could really you some advice on this problem. Really looking forward to getting my phone rooted.
Much Love in Advance
Flu
All I know to say is if you put a .zip file on the sdcard you should be able to see it from cwm recovery. When you boot the phone normally can you see the file in file manager?
Which ROM are you trying?
And are you putting the file on the phones internal sdcard or an external sdcard?
Sent from my SAMSUNG-SGH-I777 using XDA App
I was trying the unnamed ROM -- I just have it on the sdcard in the phone. I see it fine when I plug it in and look at it through windows. What file manager are you referring to?
I have to go to work but later on tonight I'll probably try reflashing CWM and see if that helps.
fludiddy said:
I was trying the unnamed ROM -- I just have it on the sdcard in the phone. I see it fine when I plug it in and look at it through windows. What file manager are you referring to?
I have to go to work but later on tonight I'll probably try reflashing CWM and see if that helps.
Click to expand...
Click to collapse
Any file manager will do, there its one app named "My Files" that came with the phone. If you can see the file from that file manager you should be able to see it in cwm recovery.
Sent from my SAMSUNG-SGH-I777 using XDA App
I found it. Apparently, what appears to be the main folder in windows is actually the /externalsd folder. Found it in the stock file manager and was able to copy over the file and get it rooted. Thanks for your help!
Flu
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
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.