If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Just so others know, TWRP under the "Advanced" menu item has a "File Manager" which allows you to remove each of these files. That's important for those who can't get to a PC with a working adb to mount the shell. I used OTG external storage to access the OTA and Magisk zips for flashing and storage of my nandroid backup.
Personally I would need the File Manger as I have a fully functioning PC fastboot but for some reason can't see my OP5 using adb. Not a big deal but there is a user-friendly built right into TWRP which always has "root" privileges to "/data".
zdimension said:
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Click to expand...
Click to collapse
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Dchoi229 said:
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Click to expand...
Click to collapse
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
zdimension said:
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
Click to expand...
Click to collapse
Thanks for the response Z! I just tried it and my wifi isn't stable at all when trying to connect to wifi. It's my workplace wifi that I usually have to sign into to access. It'll connnect and disconnect constantly. Is there anything you'd advise me to do?
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
buzzfuzz1 said:
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
Click to expand...
Click to collapse
Nah, the command is supposed to be run when the phone is in TWRP.
First, you use adb shell to open a terminal from your PC (ignore this step if you want to use TWRP's integrated terminal directly on the phone).
Then, when you're in the shell, run the rm command.
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
buzzfuzz1 said:
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
Click to expand...
Click to collapse
The file the command deletes is basically the "Wi-Fi" settings file, which contain identification settings for the network card amongst other things. If you keep the Nougat one while you're on Oreo, you can't turn on Wi-Fi, or use anything related to the Wi-Fi antenna; Thus, we delete it. That solves the problem "Wi-Fi doesn't turn on". Here, you've got another problem: "Wi-Fi can't connect". I have no clue of what could be causing this, this issue never happened to me. I'm gonna search a bit and update here if I find anything.
Related
Hello all,
I have a problem. I looked all over and everybody is excited to get their Tab to hook up to Ad Hoc connection. But rarely anybody addresses the issue that follows... It kills regular Wifi!
I cannot connect to any regular wifi now, just my ad hoc connection via my Sprint CDMA Rhodium (touch pro2). I use wifi all the time and running wifi router on my phone all day is not a sensible thing to do.
I tried to put the original wpa file that I had backed up, but still the galaxy cannot connect to regular wifi.
All it says is "connecting" and then "disconnected" and keeps trying to connect to it but never to a point that it says "obtaining ip address"
Please help
Sent from my SPH-P100 using XDA App
try chmod new wpa_supplicant file to 777 had the same issue and solved it with this.
kromosto said:
try chmod new wpa_supplicant file to 777 had the same issue and solved it with this.
Click to expand...
Click to collapse
may sound like a stupid question... but what is chmod?
sorry im pretty good with winmo, but a total noob on android development.
Ok so I downloaded this app called chmod from the market. It's giving me a settings screen with an ability to change numbers and options like read, write, exec...
I feel like this is for the whole system... Not an individual file.
Please help. I really appreciate it! ! !
Thank you
Sent from my SPH-P100 using XDA App
i dont know the app but you can get and terminal app from the market go to the directory you copied the wpa file and write chmod 777 wpa_supplicant and it should be fine you may need su command to get super user access before this command
Did that.
#Su
#Chmod 777 system/bin/wpa_supplicant
Then the terminal registers and goes to next line.
I did reset term, app exited. Wifi doesn't work, ad hoc works
second time I backed out of the app. Still wifi- no, ad hoc-yes
Any clue?
Should I hard Reset?
Sent from my SPH-P100 using XDA App
so you problem is not same as mine. i can tell you what i did exactly maybe it helps.
i didnt use mount commands that wpa-supplicant thread i used androotfile program from the slideme market (normal android market doesnt have this or i couldnt find it) to backup the old one and use it to copy the new one. then got the same problem as you had so go back to old wpa file with again androotfile but still have the same problem. then tried chmod command with the old file and yes it worked (cant remember if i restarted the device) so again copy the new one and chmod it and all started to work.
Actually I just observed that my laptop didn't connect to the internet. So I reset the router and voila! The wifi on my pad works! ! !
All I needed to di was rest the router... stupid me! Didn't think to cover the basics...
And to think, I was soo close to painting a hard reset.. Haha
Thank you so much! ! ! I really appreciate it! !
You are the man!
Sent from my SPH-P100 using XDA App
Hy,
i did everything exactly as described here.
copied new wpa_supplicant to system/bin and thereafter
chmod 777
when i check the permissions with ls -l i can see
wpa_supplicant has following permissions: -rwxrwxrx root root
i can see AD-HOC and "normal" WIFI, but when i want to connect to adhoc, it says: receiving IP Adress, and thats it.
any thoughts?
(i try to connect to my HTC Touch diamond Wm 6.5)
Regards
R
Works like a charm
This fixed my problem getting disconnected from my AP all the time.
Thanks
@kromosto - dude.. THANK YOU! I created an acct on here just to say that. I thought I was in **** water cause my new wpa_supplicant would not work for the life of me, spend hours, and thought the tab was paper weight. Found your post, changed permissions to execute, and I no longer that that 'error' under the Wifi turn-on.
YOU ARE A LIFE SAVER..
armageddon!
Dear All,
I am in the same situation with wpa_supplicant on my brand new Samsung Galaxy S Wifi 5.0, running Froyo, firware: 2.2.2.
I did the following:
1. Download this file: wpa_supplicant
2. Start -> Accessories -> Command Prompt Run as Administrator
3. cd the directory
4. Connect your phone via USB to your computer, then execute the following command:
5. adb shell
6. su
7. mount -o remount,rw -t yaffs2 /dev/block/stl9 /system
8. cp /system/bin/wpa_supplicant /sdcard/wpa_supplicant_ORIGINAL
"/system" is now "rw" mode, original wpa_supplicant is saved.
9. Open another command prompt ( repeat step 2. and 3. ) Then execute the following commands:
10. adb push wpa_supplicant /sdcard/wpa_supplicant
( adb push localfile /remotedir/remotefile )
11. Get back to your other command prompt, and execute the following commands:
12. cp /sdcard/wpa_supplicant /system/bin/wpa_supplicant
13. sync
14. chown root.shell /system/bin/wpa_supplicant
15. chmod 755 /system/bin/wpa_supplicant
16. sync
17. exit
18. exit
So at the moment wifi does not work (ad hoc also, but i do not care) I have the original wpa_supplicant file, but I am too noob to restore it. If someone who already managed to get back wifi working could explain what to do it would be highly appreciated.
Thanks!!!!!!!
cusin
help
nubie said:
Did that.
#Su
#Chmod 777 system/bin/wpa_supplicant
Then the terminal registers and goes to next line.
I did reset term, app exited. Wifi doesn't work, ad hoc works
second time I backed out of the app. Still wifi- no, ad hoc-yes
Any clue?
Should I hard Reset?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Hello,
It's fantastic.. it's long time I'm looking for a way to connect via adhoc and now I see that you have already done and trying to get back to original.
Please let me know how you were able to activate this feature(adhoc) on android.
I'm really stopped!!
Still stuck
I actually didn´t backup my old wpa_supplicant :\\\
Still struggling with this!! Any help?
I´m on a galaxy tab 2 GT-P3110 on android 4.0.4.
Thanks!
So guys, here is a quick tutorial how to fix your nonworking wifi in certain countries. The problem for it not working is that motorolas wifi driver is missing some country codes ... i guess they still live 20-30 years back, if anyone has the will to do it, we might post on motos forums to change the driver int he upcoming updates/releases. Here is the link to working wifi drivers: http://www.megaupload.com/?d=V8TGAY0C
if anyone can host it on a better location, feel free to do so.
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE, YOU OR TO ANYTHING THATS IN RELATION WITH THE PHONE OR YOU.
this tutorial will be for use with adb shell (if anyone wants to make a script or a batch or even cwm flashable out of it, be my guest, i dont really have the time and my knowledge is a tad limited in doing those things )
Prerequisites:
1.the wifix.zip
2.adb on your computer with at least some adb/linux terminal knowledge
3.rooted ATT Atrix (i tested it on mine thats from ATT and several others did too, dont know if anyone tried with the bell or other atrix's but im sure it should work)
4.some common sense
5. i assume you have am external sdcard aswell (if not swap the sdcard-ext for sdcard only to use the internal card)
Code:
TURN OFF WIFI in the settings/wireless networks menu
1.connect phone to computer with us on usb mass storage mode and without adb debugging, create a folder called wififix on your external sdcard, unzip and copy the three .bin files to that folder
2.do the safely remove on windows/linux and than change connection to none, disconnect usb, enable adb debugging and reconnect your phone to the usb
3. run cmd/terminal
4. write as follows, after each line press enter:
adb shell
su (allow su on your phones display if its the first time you are using adb with su)
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
rm /system/etc/firmware/wifi/*.bin
cp /sdcard-ext/wififix/*.bin /system/etc/firmware/wifi/
chown root /system/etc/firmware/wifi/*.bin
chgrp root /system/etc/firmware/wifi/*.bin
chmod 755 /system/etc/firmware/wifi/*.bin
reboot
5. let your phone reboot, disconnect usb, unlock phone, enter pin, enable wifi and its working.
Feel free to comment in the thread and help eachother with problems and ideas
Updated link due to request and megaupload being down, fee free to host it if you want to: http://filesave.me/file/13333/wififix-zip.html
Where was this driver taken from?
lg optimus 2x /system dump
the driver itself is a tad older version as the one moto has, but everything works for me fine now, several other users reported the same. i wanted to use the driver from the UK atrix (from orange) but its identical with the one from the ATT atrix (even the nvram.txt has region US in and not UK ...), so for the time being this is the only way for a few of us to have a fully functional phone.
one more thing, everyone who uses the fix and it works for him please post on motorolas forum that you have the problem:
https://supportforums.motorola.com/thread/50598
i started the thread just add that its not working.
and I was thinking how can wi-fi be related to country/location?!
because I remember in the old thread that several users from the same country (Qatar) reported the same problem.
I just sent an e-mail about your thread to one of those users who was in contact with me via e-mail while trouble-shooting his problem.
Thanks and gold luck.
Ye, just post in the moto forums that he/you have the same problem.
Does not work
on the line: chmod -R 0755 /system/etc/firmware/wifi
I get: Bad Mode
then I use: chmod 755 /system/etc/firmware/wifi/*.bin
and after reboot the same problem... WiFi appears for few seconds and gets lost
crnkoj, since this is the case. do you think using the market enabler app to spoof the SIM carrier will make wifi work in non-supported countries?!
uhm, did you copy the files over properly? the thing is its working for me fine and several others have confirmed this to work. Honestly i dont know why it wouldnt work, did the method from akizakian work for you at least? with the modified and locked settings.db?
genatsvale said:
on the line: chmod -R 0755 /system/etc/firmware/wifi
I get: Bad Mode
then I use: chmod 755 /system/etc/firmware/wifi/*.bin
and after reboot the same problem... WiFi appears for few seconds and gets lost
Click to expand...
Click to collapse
Tried that, it wont help. Market enabler spoofs the mcc and mnc, which comes from the sim card itself. The problem here becomes once you have cellular signal and turn on wifi, at that point wifistatetracker request country code from the cellular network, sets it to the one in which country you are and than the driver doesnt reckognise the code and blocks wifi. If you would take lets say a german sim card and put it in in your country wifi still wouldnt work, if you would take your sim card go to germany, turn on wifi and it would work. im trying to get something solved int eh motorola forums but until now only one guy is responding (not sure if hes motorola staff or whatsoever).
CyberPunk7t9 said:
crnkoj, since this is the case. do you think using the market enabler app to spoof the SIM carrier will make wifi work in non-supported countries?!
Click to expand...
Click to collapse
Still doesnt work for me. I can see my wireless, and can connect to it. but if I try to go to the market, or anywhere using the browser.. nada
uhm, but your laptop can use the wifi? is it any special encryption maybe, maybe you have to do vpn or stuff?
did you try ping from a terminal emulator?
guys, motorola is gonna fix it with an update it seems
https://supportforums.motorola.com/thread/50598?start=15&tstart=0
I made an update.zip for CWM if you need it. THis way you just have to apply the update after SBF/root. It SHOULD work....I did not try it.
Thanks Dennis, i was too lazy to do it
crnkoj said:
So guys, here is a quick tutorial how to fix your nonworking wifi in certain countries. The problem for it not working is that motorolas wifi driver is missing some country codes ... i guess they still live 20-30 years back, if anyone has the will to do it, we might post on motos forums to change the driver int he upcoming updates/releases. Here is the link to working wifi drivers: http://www.megaupload.com/?d=V8TGAY0C
if anyone can host it on a better location, feel free to do so.
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE, YOU OR TO ANYTHING THATS IN RELATION WITH THE PHONE OR YOU.
this tutorial will be for use with adb shell (if anyone wants to make a script or a batch or even cwm flashable out of it, be my guest, i dont really have the time and my knowledge is a tad limited in doing those things )
Prerequisites:
1.the wifix.zip
2.adb on your computer with at least some adb/linux terminal knowledge
3.rooted ATT Atrix (i tested it on mine thats from ATT and several others did too, dont know if anyone tried with the bell or other atrix's but im sure it should work)
4.some common sense
5. i assume you have am external sdcard aswell (if not swap the sdcard-ext for sdcard only to use the internal card)
Code:
TURN OFF WIFI in the settings/wireless networks menu
1.connect phone to computer with us on usb mass storage mode and without adb debugging, create a folder called wififix on your external sdcard, unzip and copy the three .bin files to that folder
2.do the safely remove on windows/linux and than change connection to none, disconnect usb, enable adb debugging and reconnect your phone to the usb
3. run cmd/terminal
4. write as follows, after each line press enter:
adb shell
su (allow su on your phones display if its the first time you are using adb with su)
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
rm /system/etc/firmware/wifi/*.bin
cp /sdcard-ext/wififix/*.bin /system/etc/firmware/wifi/
chmod -R 0755 /system/etc/firmware/wifi (you can use chmod 755 /system/etc/firmware/wifi/*.bin )
reboot
5. let your phone reboot, disconnect usb, unlock phone, enter pin, enable wifi and its working.
Feel free to comment in the thread and help eachother with problems and ideas
Click to expand...
Click to collapse
_Dennis_ said:
I made an update.zip for CWM if you need it. THis way you just have to apply the update after SBF/root. It SHOULD work....I did not try it.
Click to expand...
Click to collapse
Contribute, collaborate, conquer!! Outstanding.
It just seems strange that the OS wouldn't let you choose your country, like most routers already do... or is that taboo? Is wifi on Android mobile/cellular dependent? If so... what think tank came up with that...? How does Windows (desktop) handle this? It's not like laptops don't go on airplanes and visit other countries!!! BTW I can't believe I had to specify 'desktop'... I was thinking/worried ... "What if someone thinks I mean Windows (phone)." Seriously... who has a Windows phone? Let me re-phase... Who would be reading this specific thread and have a windows phone?
genatsvale said:
on the line: chmod -R 0755 /system/etc/firmware/wifi
I get: Bad Mode
then I use: chmod 755 /system/etc/firmware/wifi/*.bin
and after reboot the same problem... WiFi appears for few seconds and gets lost
Click to expand...
Click to collapse
The fix for that is to switch the numbers and -R, chmod expects to the the numbers first.
Code:
chmod 0755 -R /system/etc/firmware/wifi
Guys, before applying this method to my Bell Atrix (using it in Qatar, WiFi not working), I need to know:
1) Given it's a Bell Atrix, is there anything different I need to do?
2) Which root method should I use?
3) Did Bell's update fix this? Will this conflict with Bell's update? I'm planning to update my software once I get WiFi working.
Thanks
Can I apply this fix AFTER deodexing?
NOT WORKING for me either.
Rooted using Gladroot.
Non-deodexed Bell Atrix.
Followed all instructions.
Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Cowmonaut said:
Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Click to expand...
Click to collapse
I can say a couple words to describe my reaction.. OH ****. Your phone seems to have too many problems to be software related. Try to flash back to stock 5.6.890 and get a new phone.
Sent from my DROID3 using XDA App
Hmm, I guess for the mean time I'll just have to keep trying to get the Marketplace ROM Manager to install and launch. Should be a way to install straight to the SDCard that doesn't have problems.
Thinking it over, my Internal Storage may just have a bad sector... Yeesh.
Have you tried formatting /system in mounts and storage in CWM? Then reinstalling a fresh rom on top?
Sent from my DROID3 using xda premium
Negative. I didn't have CWM installed (stock ROM just rooted for certain apps) and apps are usually crashing now.
I'll give that a shot though. Sometimes I can use an app so maybe if I'm persistent...
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Yea can't get any new apps to run. Interestingly, the camera app seems to crash the OS at the moment.
I think I'm going to have to try to RMA...
MrJudylicious said:
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Click to expand...
Click to collapse
Its running 5.6.890. Unless I'm mistaken its the xt862. I've only had it since September.
well as long as root isnt showing and the /system hasnt been changed from stock rom, it should work. i do find it bad that rsd didnt work. i wonder if you were trying to flash the .959 sbf on your .890 system? I would def try again to sbf and wipe data/cache through stock recovery after that using volume buttons (android!)
Well, that's kind of the problem. Changes don't survive a reboot so i haven't been able to unroot the phone. I double checked and the file was the .890 flashboot. Wiping data/cache literally does nothing.
Is there a way to format this offline, from a PC? Going to try some more Google searches...
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
MrJudylicious said:
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
Click to expand...
Click to collapse
1) How do you unroot with Pete's motorola tools? Is it a different version than the one click root? Cause that's how I rooted my phone in the first place but it doesn't seem to have an option to unroot...
2) The link for the flashboot file gives a 404 error. The attached .RAR only has the .XML file.
Any place else I can get that version?
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Edit: srry didnt read the full post
jellydroid13 said:
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Click to expand...
Click to collapse
If you read the original post, that doesn't work.
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
sh[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Cowmonaut said:
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Click to expand...
Click to collapse
Have you tried to root manually? Here are the original instructions vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
[edit] I guess I miss read that you are trying to unroot.
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
MrJudylicious said:
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
Click to expand...
Click to collapse
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Cowmonaut said:
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Click to expand...
Click to collapse
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
ChaoticWeaponry said:
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
Click to expand...
Click to collapse
Where do you get that idea?
When I do this manually:
1) I'm running the command prompt as Administrator
2)I'm launching into adb using the command "adb shell".
3) First thing I do is type in "su"
4) second thing I do is approve "unknown" in the superuser app on account of it never remembering I already did that.
5) I use the command "mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system"
6) I use the "ls" command on /system/app and find an .apk to uninstall (not all my apps seem to be installed in this location either...)
7) I use the "pm list packages" command to find the rest of the files for that .apk
8) I use "rm <filename>.apk" followed by "pm uninstall <whatever that developer chose to name things>" command to fully uninstall.
I should note on my phone at this point it disappear from the application list.
9) I use the command "mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system"
10) I use the "ls" command on /system/app to confirm and voila, the apk file is back!
The app doesn't show up in my app manager until I reboot the phone. Changes to /system and /data are not persisting and I have no idea why.
I can't seem to unmount them either so I can't format via ADB...
SOLVED
(No success for me personally, but I'd still like to explain how I realised there's no hope left - description is at the bottom of this post)
Hi, not a regular poster in the S3 mini section, but a friend of mine has had his entire screen smashed. Somehow though, the phone is still breathing and can be turned on/off.
The problem is: My friend has asked me to extract his photos and similar media from the device's memory.
The device isn't rooted and I'm not sure if there's a default recovery mode or something like that built in the device.
I've tried connecting the device to my PC and it gets recognized and the drivers install themselves, but the device is empty. Moreover, I've downloaded KIES which also recognized the device, but says that there's a lockscreen and he can't go any further.
Any advices? Most of the other xda answers are for rooted phones so they haven't been very helpful, unfortunately.
There's a picture of the device in the attachments below, and KIES interface aswell.
<<EDIT>>
I'm using this http://forum.xda-developers.com/showthread.php?t=2339530 Recovery operation but it keeps saying "adb.exe" not found. I've installed ADB via the 15sec install ( http://forum.xda-developers.com/showthread.php?t=2588979 ) and entered the path correctly, but it still can't detect it. Any tips? perhaps i'm using the wrong ADB - I don't have c:\android\platform-tools folder - it's simply c:\adb\adb.exe.
SOLVED PROBLEM:
After messing with this for 2-3 days, I've decided to go with the simplest method - find a way to list all directories on the device and then see if there's anything in "sdcard" or a similar folder. To do this, after ADB recognizes your device, type : adb shell ls -R
adb shell ls -R will list a zillion directories so you may want to save the data into a .txt file. to do this, type adb shell ls -R > output.txt (or any other name).
After that, open the output.txt file and then use ctrl-f to find the sdcard folders and check if there's any data left in them.
IMPORTANT:
I've read that, without root permission, one cannot access the data or sdcard directories. The device I was working on had USB debugging OFF so there was no way I could root the phone in order to access the data directories.
Silly question, but did you use option 2 in RecoverData to change the path of ADB to c:\adb\?
aumedina said:
Silly question, but did you use option 2 in RecoverData to change the path of ADB to c:\adb\?
Click to expand...
Click to collapse
Yup, but it still can't find it. That's why I think the ADB-15sec install might be flawed.
There's a screencap of the Recovery + TotalCMD in the background in the attachments.
<EDIT>
Alright so I've followed an ADB tutorial (http://forum.xda-developers.com/showthread.php?t=2266638), installed all the SDK packages just to be sure.
ADB now recognizes the device after I've booted it into recovery mode. I've tried doing adb pull /data and it says 0 files pulled, 0 files skipped. Does this mean the device's internal memory is blank? No it doesn't, only the folder "data" is blank, other system data is present.
<EDIT 2> Can anyone please tell me the path to the internal camera storage folder? I may have fixed the problem if only I knew the correct path. SOLVED: The correct path is one of 4 combinations, usually these: /mnt/sdcard0/ /mnt/sdcard/ /storage/sdcard0/ /storage/sdcard/
I am really stumped here. I have an Android 5.1.1 TV computer, rooted, SuperSU, shared mount namespaces, and generally working as expected. I have Tasker run a shell script, using root, to perform a nightly backup of my /sdcard to a file on a flash drive attached to one of the computer's USB ports. Seems like this should not be a problem. Indeed, at one time this worked but for some reason it started failing a few weeks back and I am trying to ascertain why and how to fix it.
In normal operations, I can access the drive at /storage/udisk0 with a file manager app or with a terminal app. I can read/write without troubles. I don't even require su to be run first.
However, when the backup script runs (confirmed as root using the whoami command), any write access to the flash drive fails reporting a read-only file system. Again, if I try the file manager or terminal apps to write immediately after the backup routine has failed, I have no problems.
I have gone so far as to place mount -o rw,remount /storage/udisk0 in the backup script (again running as root) prior to trying to access the flash drive. Still it fails. I cannot even echo hello > /storage/udisk0/test.txt from inside the script. Of course, this works fine outside of the script.
So I am stuck. I have no idea why this is occurring or how to fix things. I have tried using Chainfire's StickMount app which mounts the flash drive under /sdcard/usbStorage/sda1 and there seems to be no problem in accessing the drive that way. But that was just a test and I would really rather not go that route since things previously worked just fine without.
Any tips/hints/suggestions are appreciated. Thanks!
Edit - please ignore this as I discovered that I was somehow shooting myself in the foot. Seems that somehow a Tasker task was unmounting the usb flash drive in certain circumstances. Why this reported as a "read only" I am not sure. Cheers!