I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Android Cowboy said:
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
johnnydowngrief said:
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
Click to expand...
Click to collapse
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Android Cowboy said:
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Click to expand...
Click to collapse
Then maybe this. http://forum.xda-developers.com/showthread.php?t=1379875 But I'm just guessing here. I dont want to spam this thread. Maybe someone more experienced can help you.
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I will try that. If I could just push a new build.prop to overwrite the old one I put probably be okay. How did restore system files using ADB.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That didn't work for me, I've also trying factory resetting again multiple times through recovery, but no dice.
I got my fastboot cable working, and was able to get the device recognized as "Qualcomm USB modem converter"
I opened a thread about it, any help is appreciated!
Android Cowboy said:
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
Click to expand...
Click to collapse
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
GSLEON3 said:
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
Click to expand...
Click to collapse
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Android Cowboy said:
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Click to expand...
Click to collapse
Did you try either of these drivers:
http://www.4shared.com/rar/kRIFBtGe/qualcomm_hsusb_device_drivers.html
http://drivers.softpedia.com/progDo...dows-7-x64-Windows-8-x64-Download-179130.html
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Since you didn't factory reset, does it show up on adb devices at all while it's trying to boot ?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
So currently its not showing up on adb while its booting, but that's probably because I haven't updated adb in a while. I'm going to update when I get home from work and report back.
EDIT: So I update ADB, which isn't recognizing it, but oddly enough, my computer can see it even after the screen shuts off as an android device. My only guess then is I'm missing a driver or something. Any suggestions?
Android Cowboy said:
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
S_transform said:
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
Click to expand...
Click to collapse
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Android Cowboy said:
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Click to expand...
Click to collapse
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
S_transform said:
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
Click to expand...
Click to collapse
When you ADB shell, are you seeing a "#" which means you are rooted. I'm not the world's expert on ADB but this should help. Once you are shell and rooted you can just chmod 644 or 777 on /system and see if that works. http://gizbeat.com/2103/how-to-change-file-permissions-through-adb/
Related
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Sounds to me like a permissions issue. I had that after I fiddled with the contacts database to unrestrict pictures from third party apps. I would double check any files you modified and make sure they got chmod'ed back to what they should be.
You will have to somehow access the Settings to re-enable adb. When you did a factory reset, you disabled USB Development (aka adb).
For now the only known way to recover is through adb. No fastboot or signed update.zip for now.
navalynt said:
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Click to expand...
Click to collapse
When I lost ADB access because of a hard reset (I think), this is what I did to fix my issue: http://forum.xda-developers.com/showthread.php?t=974824
I never lost root after a hard reset so I went to the market and bought root explorer and sqlite editor and copied the adbd to the /sbin folder to fix adb. I then bought sqlite editor and followed this: http://forum.xda-developers.com/showthread.php?t=972760 to re-enable side loading of apps. To install apps that I had the apk's for.
I still lose adb after a reset, but I can copy the adbd file to the /sbin folder and adb works again until I reset the phone.
I made a post about losing adb access on the motorola support forums: https://supportforums.motorola.com/message/332307#332307 to see if there were any solutions, but Mark said he would get back to me after trying to reproduce my problem.
I hope this helps.
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
No problem. That sucks, I'm not sure what you can do. Hopefully motorola or someone here will get a sbf soon so we can mess with our phones and have a way to fully recover. I hope you get it working again. Good luck!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
shadowscreation said:
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Requires USB Debugging to be enabled, but I have no access to enabled it due to Settings force closing and no ADB access in pre-boot.
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
adlx.xda said:
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
Click to expand...
Click to collapse
It won't let me install a downloaded APK because of the security restriction.
If you have an SD card, try booting into recovery with an update.zip on the file.
I can get into the recovery, but the update.zip file needs to be signed. I created one that will push the original copies of the framework files I was working with but it won't install because it's signed with test keys. The stock recovery 3e needs update.zip files signed with the manufacturer release-keys which only Motorola has.
https://supportforums.motorola.com/thread/46051?tstart=30
I started a thread on the official Motorola Owner's Forum in hopes I can find a full factory restore method for the OS. It's unfortunate that unlike HTC and other manufacturers who release full wipe RUU files Motorola has chosen to keep their restore files internally.
http://www.4shared.com/file/7YXo_gmO/update.html
That's the link to the update.zip file I was trying to use that fails because it's only signed with test-keys.
Retracteddd
i am rooted and unlocked and ran a rom well in twrp i accidentally wipe everything internal now i have to way to get zips back to flash them my backup and all is gone and i have zips on ext card but twrp wont mount it please help
I pretty much just need a way to get my zips back to internal storage
Sent from my SCH-I605 using xda app-developers app
trinitystudio said:
i am rooted and unlocked and ran a rom well in twrp i accidentally wipe everything internal now i have to way to get zips back to flash them my backup and all is gone and i have zips on ext card but twrp wont mount it please help
Click to expand...
Click to collapse
while in recovery, you can use ADB to transfer files to prime from PC via data cable. look for ADB PUSH here on forums
qery said:
while in recovery, you can use ADB to transfer files to prime from PC via data cable. look for ADB PUSH here on forums
Click to expand...
Click to collapse
thanks ill give it a try and get back with you
ok i found and did what it says it sees my prime but im getting this error now failed to write data 'protocal fault <no status>' *3%
now this
i am runnung this command - adb push pac_tf201_4.3.Build-1_20131003.zip /sdcard/ ..all i get is a protocol failure not sure what that means but i need help bad wiped internal and stuck in twrp recovery
trinitystudio said:
i am runnung this command - adb push pac_tf201_4.3.Build-1_20131003.zip /sdcard/ ..all i get is a protocol failure not sure what that means but i need help bad wiped internal and stuck in twrp recovery
Click to expand...
Click to collapse
You need to make sure sure you have all the Android files installed on your PC which I am sure you do. Also, you need to specify where the pac_tf201 build is located. This is what I did to push the version onto my TF201 in Recovery:
adb push c:/pac_tf201_4.3.Build-1_20131003.zip /sdcard/
I did the same with gapps but I made sure that both zip files (rom and gapps) were directly on my C drive and not anywhere else. Let me know if you need anymore help as I just barely did this a few days ago. Took me hours to get it but I have learned quite a bit from it. :good:
Edit: Make sure your directory is pointed to your sdk platform-tools folder as well in CMD.
alias4ever said:
You need to make sure sure you have all the Android files installed on your PC which I am sure you do. Also, you need to specify where the pac_tf201 build is located. This is what I did to push the version onto my TF201 in Recovery:
adb push c:/pac_tf201_4.3.Build-1_20131003.zip /sdcard/
I did the same with gapps but I made sure that both zip files (rom and gapps) were directly on my C drive and not anywhere else. Let me know if you need anymore help as I just barely did this a few days ago. Took me hours to get it but I have learned quite a bit from it. :good:
Edit: Make sure your directory is pointed to your sdk platform-tools folder as well in CMD.
Click to expand...
Click to collapse
i have done that all but putting it on the c:\ drive ....yes im pointed to that folder ill try c and get back to you thanks
edit: try c drive thing still a no go still getting protocol failure
Hardbricked!!!!!!!!!!!!!!
Well im hardbricked now asus wants $324 to fix so NOT!!!!!! Guess its time to go shopping lol
trinitystudio said:
Well im hardbricked now asus wants $324 to fix so NOT!!!!!! Guess its time to go shopping lol
Click to expand...
Click to collapse
Can you boot into fast boot at all? Or are you stuck at the Asus screen?
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
alias4ever said:
Can you boot into fast boot at all? Or are you stuck at the Asus screen?
Click to expand...
Click to collapse
What would you plan on doing or what does anyone do with a hardbricked Prime as I am curious? Sorry to hear it.
It happens I have done roms for years from droid one to note2 never had a issue till now it was my own mistake so... I guess nothing to do but trash it prob going today to get Samsung note 8 or 10.1
Sent from my SCH-I605 using xda app-developers app
Do you by any chance have Asus sync running on your pc? It seems that this can interfere with adb.
Try killing all asus related programs on your pc through task manager and then try adb push again.
Sent from my SO-04E using xda app-developers app
This is what I'm curious about too. If there were photos on this SD card before you put it in the device, they will remain intact after a security wipe.
This is unclear to me based on the OP: You got the Bold as a graduation gift and would like to start using it i assume. (I also got this bold a couple days ago after my HTC One S died, bringing me to Blackberry after years of faithful service on Android. The 9900 is a great phone)
When you tried to use the phone, you were prompted to input your BBID credentials, which subsequently failed repeatedly. The phone has since been security wiped due to too many failed attempts. Upon opening the phone, the microSD that you had in there is gone.
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.
Long story short... I have a non-rooted SGH-M919 (Samsung Galaxy S4) with a completely broken screen. USB to PC transfer doesn't work, it's set to charge only, Kies doesn't see it...etc.
I have found that it's still on my wifi and on my google play account so I can install apps from the website. Does anybody know any apps I can install that will instantly let me access my files (and transfer them) without needing to do anything on the phone's side? Remote access would be great but I'd settle for file sharing even if only on the local network.
Any other ideas would be great! I need to recover pictures and contacts that aren't on google, or the SD card. New phone doesn't take the SIM.
You're probably not going to like this answer, but I recommend you simply have the screen fixed. If MTP isn't enabled and you can't enable it, and it's not rooted... There's just not much you can do.
NetworkAuditor said:
You're probably not going to like this answer, but I recommend you simply have the screen fixed. If MTP isn't enabled and you can't enable it, and it's not rooted... There's just not much you can do.
Click to expand...
Click to collapse
That's not too helpful... I found a (paid) app that attempts to recover files from the phone's download mode, which I think I could get to. There's gotta be other (free) options out there if download mode has access to files. Also as I said, I'm sure there's some app out there that shares files on the local network. I just need a name if anybody has one.
Thanks for answering still... but I know there's options.
UnknownCloakedMan said:
That's not too helpful... I found a (paid) app that attempts to recover files from the phone's download mode, which I think I could get to. There's gotta be other (free) options out there if download mode has access to files. Also as I said, I'm sure there's some app out there that shares files on the local network. I just need a name if anybody has one.
Thanks for answering still... but I know there's options.
Click to expand...
Click to collapse
Oh! Well if you can get to recovery, you may be able to pull the files off the device or back it up entirely.
Search "adb from recovery" and see if that gets you anywhere. If you *can* use adb, you might be able use adb's "backup" command to back up whatever you have on there.
NetworkAuditor said:
Oh! Well if you can get to recovery, you may be able to pull the files off the device or back it up entirely.
Search "adb from recovery" and see if that gets you anywhere. If you *can* use adb, you might be able use adb's "backup" command to back up whatever you have on there.
Click to expand...
Click to collapse
No custom recovery and no root access so I don't think adb will work for me... will it? I've confirmed USB debugging is off.
UnknownCloakedMan said:
No custom recovery and no root access so I don't think adb will work for me... will it? I've confirmed USB debugging is off.
Click to expand...
Click to collapse
Well, I've never used adb from recovery before, but a quick search makes me think it could be possible. If you're desperate to recover the data, I' m assuming anything is worth a try.
Now most of the time, stock recovery doesn't have adb access, but if you can manage to unlock your phone, you would be able to install CWM recovery and boot to it.
However, this is unlikely, as IMO, the SGS4 is one of the most painful phones to try to unlock, especially when you don't have access to the screen.
soo.. I am trying adb right now. I did...
adb shell
cd /sdcard/DCIM/Camera
ls
and all my pictures are listed! I tried doing a pull at that point and it says device not found... which it clearly is since it's reading the info. Any idea what my next step is? mounting or something? I feel like I'm so close!
EDIT:
BOOM! got it! I read one post online that said "stay out of shell for pull" I reopened my adb window and just did "adb pull /sdcard/DCIM/Camera" and all is recovered now. Thanks and I hope this post helps somebody in the future!
UnknownCloakedMan said:
soo.. I am trying adb right now. I did...
adb shell
cd /sdcard/DCIM/Camera
ls
and all my pictures are listed! I tried doing a pull at that point and it says device not found... which it clearly is since it's reading the info. Any idea what my next step is? mounting or something? I feel like I'm so close!
EDIT:
BOOM! got it! I read one post online that said "stay out of shell for pull" I reopened my adb window and just did "adb pull /sdcard/DCIM/Camera" and all is recovered now. Thanks and I hope this post helps somebody in the future!
Click to expand...
Click to collapse
Glad you got everything resolved! Now for my own curiosity, how did you manage to get adb working?
NetworkAuditor said:
Glad you got everything resolved! Now for my own curiosity, how did you manage to get adb working?
Click to expand...
Click to collapse
Nothing special at all. It only required:
> Phone in download mode, wired to PC with USB cable
> ADB installed on PC
> Samsung USB Drivers
> Open adb command prompt, and run the pull command (after finding the exact directory using adb shell)
So i got the new G8X and have been trying desperatey to just access the system files to remove some bloatware.
Problem is it only gives me access from \User\0 and on. I tried to delete them through adb on windows but everytime i try and run adb shell the phone automatically disconnects.
I know i have all the updated drivers cause it recognizes the phone through windows and adb when i type adb devices
but as soon as i execute adb shell it disconnects. Does anyone have a solution for this?
Any sort of feedback would be greatly appreciated. i Have a 30 day return policy in effect if i cant gain access to any of that i plan on returning the phone.
Thanks for reading
Edit: Im dumb switching ports and usb cable resolved issue.
If anyone hears anything about root access please advise. Thanks all
I have had my phone on ADB and sending and reading data from it two nights in a row, I have not seen this problem at all. I can run adb shell no problem. Sorry! I know it's a stupid suggestion, but can you try a different USB cable/port on your PC?
SirataXero said:
I have had my phone on ADB and sending and reading data from it two nights in a row, I have not seen this problem at all. I can run adb shell no problem. Sorry! I know it's a stupid suggestion, but can you try a different USB cable/port on your PC?
Click to expand...
Click to collapse
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
abraham3991 said:
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
Click to expand...
Click to collapse
The problem might be that if you run from power shell command, first type cmd and press enter.
abraham3991 said:
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
Click to expand...
Click to collapse
I bought unlocked but i'm using it with T-Mobile and its getting WiFi calling and HD Voice and everything. Works really well and am getting good service/signal with it on T-Mobile.
Yeah, as suggested, I also used it in CMD and not in powershell…
SirataXero said:
I bought unlocked but i'm using it with T-Mobile and its getting WiFi calling and HD Voice and everything. Works really well and am getting good service/signal with it on T-Mobile.
Yeah, as suggested, I also used it in CMD and not in powershell…
Click to expand...
Click to collapse
As simple as your suggestion was it lets me command it through cmd now., switching the cable worked.
Still through the phone itself i cant access system directories. and its not like i cant change things it just flat out wont let me view them at all.
The end goal is to get root/custom recoveries so i can install magisk and xposed, if you hear anything let me know.And thanks again!
abraham3991 said:
As simple as your suggestion was it lets me command it through cmd now., switching the cable worked.
Still through the phone itself i cant access system directories. and its not like i cant change things it just flat out wont let me view them at all.
The end goal is to get root/custom recoveries so i can install magisk and xposed, if you hear anything let me know.And thanks again!
Click to expand...
Click to collapse
No problem! Glad that worked.
I can view system directories, and I read them as well. However, I definitely can't change anything and don't have write access either.
Will be open to suggestions/attempts in the future!
SirataXero said:
No problem! Glad that worked.
I can view system directories, and I read them as well. However, I definitely can't change anything and don't have write access either.
Will be open to suggestions/attempts in the future!
Click to expand...
Click to collapse
Sorry or the constant questions I downloaded a file explorer and im able to see more than before but i still have some files telling me i lack access.
What file explorer are you using?
abraham3991 said:
Sorry or the constant questions I downloaded a file explorer and im able to see more than before but i still have some files telling me i lack access.
What file explorer are you using?
Click to expand...
Click to collapse
I use Solid Explorer. So, some of the files you can physically see in the explorer, but if you try to open it, the text is garbled. It was only after I started doing adb pull that I could actually see/read the files themselves.