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.
Related
Hey everybody,
I apologize in advance if this post is a duplicate but I have tried searching for a solution and still lost. Here is what I did: I used the Odin to restore stock rom, then re-rooted using the one click method, then downloaded a rom from theunlockr.com, then used rommanger to install it. My rom has gave me no problems but now when I try to reboot into recovery to install something else(Like the 2.3 keyboard or a lagfix) i get this error:
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
Can someone please help me? Thank you, BTW I have a Samsung Vibrant running axura-froyo-rom
I had the same problem too.
When I put update.zip at the root directory of internal memory... once I restart the phone (not get into the recovery mode), this file is missing / dissapear. So... I always got this message too :
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
anybody can help us pleaseeeeee
I got my phone to factory settings using odin then i rerooted my phone and flashed the same custom rom back on and it worked. Try reflashing your phone, backup first, might work.
CarlosCruz15 said:
I got my phone to factory settings using odin then i rerooted my phone and flashed the same custom rom back on and it worked. Try reflashing your phone, backup first, might work.
Click to expand...
Click to collapse
thanks for reply.
how to use factory setting using odin ? tick the "re-partition" box ?
can you explain to us step by step please ?
I'm so frustated
Did you guys delete the update.zip after rooting?
If you do not see
sdcard/update.zip using a file manager, download the update.zip from my noob guide, move it to internal memory and then try to flash CWR.
Also, look in the bottom of the noob guide (last few posts) for a solution to a RECENT issue with CWR... I assume whatever Koush did in the last update is causing this problem? BUT, there is a fix posted by another XDA user... just a matte of downloading the file and putting it in the right place.
mikomikos said:
thanks for reply.
how to use factory setting using odin ? tick the "re-partition" box ?
can you explain to us step by step please ?
I'm so frustated
Click to expand...
Click to collapse
check out this link...its what i used
http://forum.xda-developers.com/showthread.php?t=734475
listen to s15's post....he knows what he is talking about. i followed his noob guide in his sticky and everythign worked perfectly! his vids are also very helpful. one thing i have found that works a lot as well is if you download ROM Manager from the market and then click on "fix permissions"... don't know if this would help in this situation but i have had that fix weird stuff.
s15274n said:
Did you guys delete the update.zip after rooting?
If you do not see
sdcard/update.zip using a file manager, download the update.zip from my noob guide, move it to internal memory and then try to flash CWR.
Also, look in the bottom of the noob guide (last few posts) for a solution to a RECENT issue with CWR... I assume whatever Koush did in the last update is causing this problem? BUT, there is a fix posted by another XDA user... just a matte of downloading the file and putting it in the right place.
Click to expand...
Click to collapse
yeah this, the update.zip is ESSENTIAL for your phone to run the clockwork recovery, it stores all the things needed, and when you click "reinstall packages" your system goes in update.zip and looks for what to boot up and finds CWR and boots that so you see that screen.
Don't delete it if you did.
i have tried numerous times to root,but cant seem to get update.zip file in right place,can anyone help? thanks. challenged noob!!
Rayn1328 said:
i have tried numerous times to root,but cant seem to get update.zip file in right place,can anyone help? thanks. challenged noob!!
Click to expand...
Click to collapse
When you usb into your phone it needs to be in the initial area of your sdcard.
You might have a bad update.zip file. Two things, verify the md5(if possible) from where you got it and check the properties and make sure it's not names update.zip.zip. The later is very common.
Try this method too btw, when I Odin back to stock I always use this one to root again. Follow the 'Automated Method' area.
http://forum.xda-developers.com/showthread.php?t=786877
you will need these drivers AND set your phone to debugging mode (settings/applications/development check USB debugging).
http://forum.xda-developers.com/showthread.php?t=728929
hey all,
Newbie here trying to flash a ROM, i am running into this same error, i have tried everything here and i have one question (might be a stupid question) but my root sd folder is called SD/, not SDCard/ ...is this a path error?
Please note it file must be in the internal card, not the SD card.
This step drove me nuts.
"2. Copy the update.zip (and the ROM) to the INTERNAL SD (not the external SD Card). sdcard/ " (http://forum.xda-developers.com/showthread.php?t=732458)
i ran into the same problem...how do i get from 3e to CWR?
here's what's shown in my vibrant directory: Android, DCIM, external_sd, LOST.DIR
i dont have an internal sd (the card) so it's not shown?
the path i got error on: /mnt/internal_sd/update.zip
1. when i tried to "reinstall packages" i keep getting the error that the update.zip file cant be found. should i create a folder for it or something? i think it's a matter of pathing but i cant find out the right place to put the file...(to get from 3e to CWR)
2. i see people suggesting boot with odin or sth like that...does that solve my problem and how do i do that?
janthe6th said:
i ran into the same problem...how do i get from 3e to CWR?
here's what's shown in my vibrant directory: Android, DCIM, external_sd, LOST.DIR
i dont have an internal sd (the card) so it's not shown?
the path i got error on: /mnt/internal_sd/update.zip
1. when i tried to "reinstall packages" i keep getting the error that the update.zip file cant be found. should i create a folder for it or something? i think it's a matter of pathing but i cant find out the right place to put the file...(to get from 3e to CWR)
2. i see people suggesting boot with odin or sth like that...does that solve my problem and how do i do that?
Click to expand...
Click to collapse
You definitely have an internal sd card. Use Astro file manager or something similar and put update.zip on the root of internal sd card, meaning not in a folder. It should look like sdcard/update.zip. If you are having the 3e mismatch recovery issue read this http://forum.xda-developers.com/showthread.php?t=833423
Sent from my SGH-T959 using Tapatalk 2
i go to the link that you linked and ran the script. then i download the update.zip file at the noob guide with a slimbean 4.2.2 rom and addons. this time i would just put it in the root folder (technically not in any folder). when i try to reinstall packages, the screen shows that it is "replacing stock recovery with clock work recovery"... but then it would go back to the 3e.
so...i guess putting the files in the root folder is correct. but someone it still wont let me get tot CWR...
janthe6th said:
i go to the link that you linked and ran the script. then i download the update.zip file at the noob guide with a slimbean 4.2.2 rom and addons. this time i would just put it in the root folder (technically not in any folder). when i try to reinstall packages, the screen shows that it is "replacing stock recovery with clock work recovery"... but then it would go back to the 3e.
so...i guess putting the files in the root folder is correct. but someone it still wont let me get tot CWR...
Click to expand...
Click to collapse
You have to reinstall packages twice for it to work properly. It is normal to not work the first time, just reinstall packages again and you should be good to go. If you keep having issues you should just flash back to stock 2.1 with Odin and go from there.
Sent from my SGH-T959 using Tapatalk 2
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?
Greetings everyone!
New *registered* user here! I've been frantically sifting through post after post on the forums all night hoping to get some help with an issue I am having on my Vibrant.
Goal:
Remove some bloatware ONLY, not looking to install any ROMs or modify the phone too much...just clean some annoying apps and icons off.
Phone Information:
Model SGH-T959
Firmware 2.2
Baseband T959UVKB5
Kernel 2.6.32.9
Build FROYO.UVKB5
I currently have the latest version of Java, Android SDK, and SuperOneClick installed.
Install directory of AndroidSDK:
C:\AndroidSDK
My method of failure:
Open SuperOneClick, Click "Root"
Start, Run, "CMD"
cd c:\AndroidSDK\tools
adb shell
mount -o rw,remount /dev/block/st19/system
This is where it fails and I run into an endless loop of it telling me the proper usage of the "mount" command. I thought I had it at one point but when I typed: rm /system/AmazonMp3.apk all it did was tell me that it was a read-only file and that it couldn't be deleted.
Can someone help lead me in the right direction of what I am doing wrong? I rooted and removed all bloatware about a year ago but I just did an upgrade through MiniKies to the latest version of firmware and I can't seem to remember the process I went through that long ago to get it done right.
I apologize for possibly asking a question that has been asked numerous times but I just couldn't seem to get the wording right to get any helpful results in the search of the forums. Thank you so much for the time in reading this and the future help if any can be provided. Have a great night!!!
It looks like you are in the wrong directory. Open a command prompt in
C:\AndroidSDK\platform-tools
Open the platform tools folder. Click on a blank space > hold down the shift key > hit right click > select open command window here. Then enter the commands:
adb devices "to check if your device is connected. also make sure usb debugging is enabled on your phone.
adb remount
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
If you want a list of all your /system/apps enter this command
cd /system/app
ls *.apk
This is much easier if you download rom toolbox from the market. All you do is go to /system/app and delete whatever bloatware you dont want.
BUT BE EXTREMELY CAREFUL WHEN DELETING SYSTEM APPS. ONLY DELETE WHAT YOU KNOW IS BLOATWARE OTHERWISE YOU WILL GET FC'S
good luck
Would I still need to follow the steps prior to that and use SuperOneClick to root the device or do I just skip that process and go straight to the cmd prompt?
Also, I followed a tutorial I found for installing the Android SDK that informed me to copy all the files from android-tools to the tools directory and use that instead but I don't know what the use in that is except for maybe a smaller directory name?
EDIT: I tried what you said with and with using SuperOneClick prior to the procedure and the cmd prompt displayed the following text:
*opened cmd promt in C:\AndroidSDK\tools (no files in platform-tools anymore)*
adb devices (it found my device connected)
adb remount (adb remount: no such file or directory exists)
The adb shell and su commands works fine BUT I still hit the endless loop of it trying to explain to me the "usage" of the mount command.
I will look into Rom toolbox as I'm trying to figure this out as well. Thank you.
I strongly recommend you download root explorer or some similar root browser app. Of course though your phone must be rooted. Just try rom toolbox. It has its own root browser within the app along with other useful features. This is probably the easiest way to uninstall the bloatware in your case since you are having issues with adb.
Sent from my Galaxy Nexus using XDA
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
CScrivener said:
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
Click to expand...
Click to collapse
You can try rooting your phone using this toolbox.
http://forum.xda-developers.com/showthread.php?t=954509
If that does not work for you i will try and find the link to the "one click root program" i use all the time.
Here is an excellent guide to root.
http://forum.xda-developers.com/showthread.php?t=849028
Sent from my Galaxy Nexus using XDA
Here is the program i use. Just remember to have usb debugging enabled on your phone. It really cant get any easier than this.
http://forum.xda-developers.com/showthread.php?t=739300
Sent from my Galaxy Nexus using XDA
So I downloaded the one click program you suggested and the program itself seems to bee pretty straight forward.
I connected phone to computer with debugging on. Opened program and hit one click root. It started doing it's thing...phone rebooted and went into recovery. I started to follow instructions up until I got to where it said install packages. When I clicked it, the phone said installation failed no such file our directory exists.
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Thank you so much for all the help so far, I feel like I'm so close but just not there yet. You have been an incredible help!
Sent from my SGH-T959 using XDA
CScrivener said:
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Click to expand...
Click to collapse
The way (Stock) Recovery works is if you are not "Install from SD" then it will look for the file labeled Update.zip. So you can rename only the Root.zip to Update.zip and make sure that is the only thing on your internal SD labeled that or with .zip Put the unroot.zip in a folder for now. Then try again.
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
CScrivener said:
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
There is no need to rename anything. The program does it all for you. Play close attention to the first screen (green one) if it says update.zip copied successfully it will then reboot your phone to stock recovery. Once you are in stock recovery all you do is click reinstall packages. Keep clicking reinstall packages even if it reboots the first time. To prove my point mount your phone to your pc and check to see if the update.zip is copied onto the root of your into storage. If not well copy the update.zip from the last guide i suggested from above.
Also check to see if the superuser app is installed on your phone. The program also installs that along with the update.zip. If you have superuser then go to the market download rom manager so you could download CWM.
Sent from my Galaxy Nexus using XDA
Alright, so I tried it again once I got home. Didn't work BUT I did see that update.zip was installed into my phone. The sig verification failed, which means I need to change recovery versions to the one that skips sig verification correct?
I'll go search the forums for that since I remember seeing that a little while ago but that is the correct path I need to take at this point in time am I right?
Thank you so much! Big big help!
You can pull the CWR from my signature. Same as before. Put it on your internal labeled update.zip, boot into recovery and and scroll down to Reinstall Packages. Hit it. It will cycle and probably come back to stock recovery. Hit Reinstall Packages again and the stock recovery will go from blue to green (CWR).
Side note, probably from there you will be able to install the Superuser update.zip. Just go to Install from SD card and find it and hit it. The reboot. Might not but the CWR instructions above shoudl work for you.
Well I changed the recovery version using the file from http://forum.xda-developers.com/showthread.php?t=833423 and then used the OneClickRoot and was able to get the update installed (I think). The phone booted up normally, I noticed that SU Permissions was installed so I figure I am rooted correct? WRONG. Rom toolbox says I am not. Is there another way to verify? Should I reinstall Rom toolbox incase it's just bugging out on me?
So I tried using Rom Manager too. Looks as tho SU is not installed correctly, will have to try again I guess.
Cannot install CWR, tried and the recovery text stays blue even after 14 times of reinstalling packages...
This phone will be sent flying across the room sometime tonight I'm guessing. About to erase the entire thing and try starting from scratch again. (Start from Eclair and work my way up maybe)
If you are willing to start from Eclair it would be soooo much easier that all this stuff.
Odin to stock, flash CWR from my signature, go from blue to green and then flash Fishman's Bionix and you are good to go. Simple and way easier than all this mess. Just download Fish's and put it on you SD card somewhere you'll remember. Once in green recovery just scroll to that ROM and flash it per OP.
We've just been trying to Root you since on your OP you said you didn't want to flash a custom ROM.
Well...I'm still trying to avoid flashing Roms (I've upgraded through MiniKies and that's it).
I've only been trying to root just to clean bloatware off but it seems that I must be lacking the technical skills to follow instrcutions properly....nothing is cooperating and even after following all steps nothing wants to work like it should.
Grrrr! One last try to get CWR working before I lose my mind and need to take a break/walk away for a bit.
Ok, so I'm currently back to stock Eclair (ew!!) and about to boot to recovery to install CWR. Wish me luck on that one....
Wooo, CWR up and running! Now I just have to work on a flash maybe or whatever steps were suggested next...I might try the ROM you suggested.
The ROM gets placed on external sdcard and installed from within CWR correct?
Do most ROMs remove bloatware and useless apps?
Yes and are pre-Rooted. Put the ROM.zip on either card. I have a folder that I use. Boot into recovery and get green recovery back. Go to install from SD, find the ROM and flash it per the OP instructions.
Bloat free, pre-Rooted and usually has Voodoo so you can get Voodoo Sound from the market and have a sonic ear-gasm.
Just wanted to say thanks for all the help! I installed the suggested ROM last night and I am very happy with the results thus far. It was alot easier than I thought it would be. Flashing a ROM was MUCH more simpler than the root only decision. Thank you again!
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,
I'm running the last cyanogenmod 12.1 ROM on my S2. There is no custom kernel or recovery. The only thing I did was a repartition to 1GB system. This setup ran since 2016 feb. without problems. Tuesday morning got a notification from the play store, that there are updates to some of my apps, so I set my phone to update them all and left it there. I came back after 20min and then came the problem:
The phone is bootlooping. The booting animation finishes, then it starts optimizing my apps, every time different amount of apps. After it finishes it starts booting again... rinse and repeat. I tried to leave it there for a very long time, with no success. The phone is very hot in the CPU area and the battery gets hot too when it's bootlooping.
I am able to go in recovery and download mode. My recovery is the stock cyanogen recovery unfortunately. I tried putting it in download mode and since I have Android Studio installed on my pc, I tried to establish an adb shell (with adb shell command) with the adb tool that came it. Unfortunately it does not find my device (neither with adb devices). I might do it wrong though. Fortunately Odin 3.04 seems to recognize my phone, so I might be able the flash something, but I'm afraid that my internal memory is starting to fail and that is causing all these issues, so the flash would fail. First I'd like to try to save data without flashing if possible.
I have most of my user data on my sd card, so the most important thing would be to save is my contacts, messages and call history. No, I don't sync it with google, yes I know it's stupid. It used to mess up my contact list so I dropped using it.
Any help and advice would be appreciated, thanks in advance!
N7Gabe said:
Hi,
I'm running the last cyanogenmod 12.1 ROM on my S2. There is no custom kernel or recovery. The only thing I did was a repartition to 1GB system. This setup ran since 2016 feb. without problems. Tuesday morning got a notification from the play store, that there are updates to some of my apps, so I set my phone to update them all and left it there. I came back after 20min and then came the problem:
The phone is bootlooping. The booting animation finishes, then it starts optimizing my apps, every time different amount of apps. After it finishes it starts booting again... rinse and repeat. I tried to leave it there for a very long time, with no success. The phone is very hot in the CPU area and the battery gets hot too when it's bootlooping.
I am able to go in recovery and download mode. My recovery is the stock cyanogen recovery unfortunately. I tried putting it in download mode and since I have Android Studio installed on my pc, I tried to establish an adb shell (with adb shell command) with the adb tool that came it. Unfortunately it does not find my device (neither with adb devices). I might do it wrong though. Fortunately Odin 3.04 seems to recognize my phone, so I might be able the flash something, but I'm afraid that my internal memory is starting to fail and that is causing all these issues, so the flash would fail. First I'd like to try to save data without flashing if possible.
I have most of my user data on my sd card, so the most important thing would be to save is my contacts, messages and call history. No, I don't sync it with google, yes I know it's stupid. It used to mess up my contact list so I dropped using it.
Any help and advice would be appreciated, thanks in advance!
Click to expand...
Click to collapse
Ok, did you try dirty flashing the ROM using CyanogenMod recovery?
And then wiping cache and dalvik cache?
MigoMujahid said:
Ok, did you try dirty flashing the ROM using CyanogenMod recovery?
And then wiping cache and dalvik cache?
Click to expand...
Click to collapse
First of all, thanks for the advice, I didn't think of that. I assume this means there is probably no solution without flashing. Do I need to flash gapps too?
N7Gabe said:
First of all, thanks for the advice, I didn't think of that. I assume this means there is probably no solution without flashing. Do I need to flash gapps too?
Click to expand...
Click to collapse
No, no need for that, just the ROM, and it won't delete anything.
MigoMujahid said:
No, no need for that, just the ROM, and it won't delete anything.
Click to expand...
Click to collapse
So, I went to recovery, pressed apply update, searched for the cm12.1-20160203-nightly rom (same I had installed), flashed it without error messages, then I pressed wipe cache partition, then reboot system now. Now the phone starts to boot, the boot animation is playing for a few minutes, then the phone turns off. Tried it multiple times, with and without charging. I can still get into recovery.
N7Gabe said:
So, I went to recovery, pressed apply update, searched for the cm12.1-20160203-nightly rom (same I had installed), flashed it without error messages, then I pressed wipe cache partition, then reboot system now. Now the phone starts to boot, the boot animation is playing for a few minutes, then the phone turns off. Tried it multiple times, with and without charging. I can still get into recovery.
Click to expand...
Click to collapse
Ok, we will try another thing, can your phone be recognized using adb in recovery?
If so you can pull the data(contacts, sms) using adb pull command.
The data usually is stored there:
/data/data/com.android.providers.telephony/databases/mmssms.db
And there:
/data/data/com.android.providers.contacts/databases/contacts.db
If you were able to do it then fine, if not, there is luckily another solution!!
You have the latest cm12.1 build which is Feb 3rd build, so your build support iso-rec TWRP recovery, so you can flash TWRP recovery zip provided by the.gangster using CM recovery and reboot recovery so it will replace the CM recovery with TWRP, in TWRP you can mount system and data using "mount", and using the file manager there you can access the above mentioned directories and copy the files manually in the external sdcard(or the internal sdcard), then you can clean flash and copy them again after that.
That would be the ultimate solution
MigoMujahid said:
Ok, we will try another thing, can your phone be recognized using adb in recovery?
If so you can pull the data(contacts, sms) using adb pull command.
The data usually is stored there:
/data/data/com.android.providers.telephony/databases/mmssms.db
And there:
/data/data/com.android.providers.contacts/databases/contacts.db
If you were able to do it then fine, if not, there is luckily another solution!!
You have the latest cm12.1 build which is Feb 3rd build, so your build support iso-rec TWRP recovery, so you can flash TWRP recovery zip provided by the.gangster using CM recovery and reboot recovery so it will replace the CM recovery with TWRP, in TWRP you can mount system and data using "mount", and using the file manager there you can access the above mentioned directories and copy the files manually in the external sdcard(or the internal sdcard), then you can clean flash and copy them again after that.
That would be the ultimate solution
Click to expand...
Click to collapse
In recovery I can see my device with adb, but every command runs into a device unauthorized error.
Code:
D:\Android\sdk\platform-tools>adb devices
List of devices attached
0009bd0863c43f unauthorized
Code:
D:\Android\sdk\platform-tools>adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
etc.
So I assume I flash TWRP with odin. Is it possible to save data to a PC through USB connection with TWRP? I'm asking, because I'd still prefer a full backup if possible (I don't have the space for it on my external sd). Second question, if I'm able to save mmssms.db and contacts.db, how do I extract the data from it, or maybe reimport it (even to a different phone/ROM)? I don't entirely understand isorec, but let's say I manage to flash TWRP and save my data. Can I flash the latest LOS 14.1 and keep the isorec TWRP? Or after the LOS flash, I need to flash TWRP again? As I mentioned I already have the 1GB system partition, so that shouldn't be an issue. It would be a nice two birds with one stone, saving my data and updating my obsolete ROM to a isorec TWRP+LOS 14.1 combo.
Lastly, this is the recovery you mentioned, right?: recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip
N7Gabe said:
In recovery I can see my device with adb, but every command runs into a device unauthorized error.
etc.
So I assume I flash TWRP with odin. Is it possible to save data to a PC through USB connection with TWRP? I'm asking, because I'd still prefer a full backup if possible (I don't have the space for it on my external sd). Second question, if I'm able to save mmssms.db and contacts.db, how do I extract the data from it, or maybe reimport it (even to a different phone/ROM)? I don't entirely understand isorec, but let's say I manage to flash TWRP and save my data. Can I flash the latest LOS 14.1 and keep the isorec TWRP? Or after the LOS flash, I need to flash TWRP again? As I mentioned I already have the 1GB system partition, so that shouldn't be an issue. It would be a nice two birds with one stone, saving my data and updating my obsolete ROM to a isorec TWRP+LOS 14.1 combo.
Lastly, this is the recovery you mentioned, right?: recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip
Click to expand...
Click to collapse
First, TWRP won't be flashed with Odin, it will be flashed with CM recovery that you already have, and yes i meant the one you mentioned.
Second, the contacts.db and mmssms.db won't take that much space, and anyway it's OK to copy them to internal sdcard, not obligated to external, and no need to access them, after you flash another ROM like LOS 14.1, you can re copy them back to their directories.
Third, if you flash the latest LOS 14.1, you can keep the iso-rec TWRP it won't be removed.
MigoMujahid said:
First, TWRP won't be flashed with Odin, it will be flashed with CM recovery that you already have, and yes i meant the one you mentioned.
Second, the contacts.db and mmssms.db won't take that much space, and anyway it's OK to copy them to internal sdcard, not obligated to external, and no need to access them, after you flash another ROM like LOS 14.1, you can re copy them back to their directories.
Third, if you flash the latest LOS 14.1, you can keep the iso-rec TWRP it won't be removed.
Click to expand...
Click to collapse
Okay, so I need to find an SD card reader then, to put the recovery on it. Or is there another way to get it on the phone?
By the way, thank you for taking your time and helping me, I'm really grateful!
N7Gabe said:
Okay, so I need to find an SD card reader then, to put the recovery on it. Or is there another way to get it on the phone?
By the way, thank you for taking your time and helping me, I'm really grateful!
Click to expand...
Click to collapse
No pb bro, you're welcome.
Yes, you will need to get the recovery in the phone somehow, or you can put your memory card in another phone and use the phone to put the recovery in the sdcard, then place it in your phone again.
That would be an alternative if you don't have a sdcard reader.
MigoMujahid said:
No pb bro, you're welcome.
Yes, you will need to get the recovery in the phone somehow, or you can put your memory card in another phone and use the phone to put the recovery in the sdcard, then place it in your phone again.
That would be an alternative if you don't have a sdcard reader.
Click to expand...
Click to collapse
I managed to get it on the phone and flashed it. The phone was plugged in to my pc, and I could acces my internal SD so I managed to back that up. But here's the thing, TWRP file manager showed my /data to be empty, and not long after, the phone just shut down. My battery is only a few months old, so that should not be the issue, and the phone was also charging from the PC.
After this shutdown, I had a very hard time to get into recovery, because the phone thinks the battery is dead. I couldn't start booting normally either. Only download mode was available, but it only said, it can't get into download mode, because the battery is low. (when I plug in the charger the phone shows 100% battery) I changed my battery to my old weak one, I managed to get into recovery with it, after multiple tries. (I think it had nothing to do with the battery but was lucky) Now I check my /data through adb and it shows empty aswell:
Code:
D:\Android\sdk\platform-tools>adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
adb: error: remote object '/data/data/com.android.providers.telephony/databases/mmssms.db' does not exist
D:\Android\sdk\platform-tools>adb shell
~ # [6n
~ # [6nls
and-sec init.recovery.service.rc selinux_version
boot init.recovery.smdk4210.rc sepolicy
boot.txt init.recovery.usb.rc service_contexts
cache license sideload
charger mnt supersu
data proc sys
default.prop property_contexts system
dev recovery tmp
etc res twres
file_contexts sbin ueventd.rc
fstab.smdk4210 sdcard0 ueventd.smdk4210.rc
init sdcard1 usbotg
init.rc seapp_contexts
~ # [6ncd data
/data # [6nls
/data # [6n
Do I have to mount it somehow maybe? (Oh and twrp always ask at start to mount sys in read-only or R/W. I always mounted it in R/W.) I'm afraid if I start moving in TWRP the phone will shut down as it always did. If I use adb or windows explorer to acces the phone it does not shut down.
N7Gabe said:
I managed to get it on the phone and flashed it. The phone was plugged in to my pc, and I could acces my internal SD so I managed to back that up. But here's the thing, TWRP file manager showed my /data to be empty, and not long after, the phone just shut down. My battery is only a few months old, so that should not be the issue, and the phone was also charging from the PC.
After this shutdown, I had a very hard time to get into recovery, because the phone thinks the battery is dead. I couldn't start booting normally either. Only download mode was available, but it only said, it can't get into download mode, because the battery is low. (when I plug in the charger the phone shows 100% battery) I changed my battery to my old weak one, I managed to get into recovery with it, after multiple tries. (I think it had nothing to do with the battery but was lucky) Now I check my /data through adb and it shows empty aswell:
Do I have to mount it somehow maybe? (Oh and twrp always ask at start to mount sys in read-only or R/W. I always mounted it in R/W.) I'm afraid if I start moving in TWRP the phone will shut down as it always did. If I use adb or windows explorer to acces the phone it does not shut down.
Click to expand...
Click to collapse
You should go to "mount" in TWRP, and tick "data" and "system", i said that already earlier.
MigoMujahid said:
You should go to "mount" in TWRP, and tick "data" and "system", i said that already earlier.
Click to expand...
Click to collapse
After I sent the message and before I read yours just now, I managed to mount, save and even make LOS run. So I was wrong, the battery is probably dead. I guess the lot of heat it produced while bootlooping killed the battery. I switched back to my old original wore out battery which is humpy and everything, but I managed to do everything with the phone. Now my problem is after I put back the .db files in their place, when the phone start it constantly crashes android.process.acore, the messaging app and the caller app. I think it might be a permission issue, but I have no idea how to fix it.
N7Gabe said:
After I sent the message and before I read yours just now, I managed to mount, save and even make LOS run. So I was wrong, the battery is probably dead. I guess the lot of heat it produced while bootlooping killed the battery. I switched back to my old original wore out battery which is humpy and everything, but I managed to do everything with the phone. Now my problem is after I put back the .db files in their place, when the phone start it constantly crashes android.process.acore, the messaging app and the caller app. I think it might be a permission issue, but I have no idea how to fix it.
Click to expand...
Click to collapse
Download ES file explorer from play store and grant root access for root explorer and set permissions to the 2 files as (rw- rw- ---) as described in screenshot, then reboot.
MigoMujahid said:
Download ES file explorer from play store and grant root access for root explorer and set permissions to the 2 files as (rw- rw- ---) as described in screenshot, then reboot.
Click to expand...
Click to collapse
This method worked with the contacts db, but not with the messages db. Actually I did not find any databases when I first copied it there, even made the databases folder. Thanks though, I'm almost done!
N7Gabe said:
This method worked with the contacts db, but not with the messages db. Actually I did not find any databases when I first copied it there, even made the databases folder. Thanks though, I'm almost done!
Click to expand...
Click to collapse
Ok, i seem to know the problem here, i looked at my own mmssms.db file and found it in this path:
/data/data/com.android.providers.telephony/databases/mmssms.db
(not the same path for the contacts.db file)
So you should move it there and add the same permissions that you added to the other file, that will do the job for you
MigoMujahid said:
Ok, i seem to know the problem here, i looked at my own mmssms.db file and found it in this path:
/data/data/com.android.providers.telephony/databases/mmssms.db
So you should move it there and add the same permissions that you added to the other file, that will do the job for you
Click to expand...
Click to collapse
This is the path you told me the first time, and this is where it doesn't work. That databases folder was not even there, until I made it. I don't even have any other files in the folder but the mmssms.db that I copied there.
N7Gabe said:
This is the path you told me the first time, and this is where it doesn't work. That databases folder was not even there, until I made it. I don't even have any other files in the folder but the mmssms.db that I copied there.
Click to expand...
Click to collapse
I don't know what is the problem...I've ran out of ideas here
At least you got your contacts back :silly:
MigoMujahid said:
I don't know what is the problem...I've ran out of ideas here
At least you got your contacts back :silly:
Click to expand...
Click to collapse
No problem, I got lucky, run a search in the data partition for mmssms.db and it appears that now it is located in /data/user_de/0/com.android.providers.telephony/databases. I backed it up, then overwrote it, fixed the permission, rebooted and now it seems to work, so all is well.
In the end I managed to not only save my data, but to fix my phone and even upgrade it to the latest LineageOS, thanks to you! I wish you a good life!
N7Gabe said:
No problem, I got lucky, run a search in the data partition for mmssms.db and it appears that now it is located in /data/user_de/0/com.android.providers.telephony/databases. I backed it up, then overwrote it, fixed the permission, rebooted and now it seems to work, so all is well.
In the end I managed to not only save my data, but to fix my phone and even upgrade it to the latest LineageOS, thanks to you! I wish you a good life!
Click to expand...
Click to collapse
Thanks for the tip, i have a marshmallow ROM right now, it seems that the location was changed in Nogut, I'll keep that in mind.
Have a good life too.