Related
I need some help unlocking my xoom wifi using adb.
My son got ahold of it last night and tried the pattern until it locked out, i had the wifi off to save battery so now i cant use the username and password to unlock it.
I believe there is a way to reenable the wifi through adb but cant find the information anywhere, i tried to edit the settings database but cant seem to get that to work, I dont have a current backup so would really like to avoid losing my data.
Can someone please help?
I was able to pull the settings.db to my pc, make the changes necessary, then push it back.
I just changed the permantly locked out variable to 0 instead of 1 and everything worked.
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.
Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie
First off, this is not my phone, but my dad's, so I'd really like to avoid a factory reset. Also, the phone isn't rooted.
He managed to install some Wifi Tools app, which is a quite an ugly virus. Even the reviews say what an absolute crap of an app this is. Its even messing with the phone's mobile network connectivity.
So, the issue is, I can't remove this app. I can go into Device admins, and select deactivate on the bottom right part of the screen , but I can't even select 'Deactivate' in the window that pops up afterwards. Even if I tap furiuosly on the screen, nothing happens. After that, the settings app is all messed up. It doesnt react to most inputs, like it's frozen, or I can only scroll, but can't enter any subsections. 'Curiously', I can't enter the Security subsection if I don't restart the Settings app, even if everything else works.
How the hell do I remove this hellspawn? I know I can't do it through ADB because it has Admin privileges. Admin privileges that can't be revoked.
Hello,
Your options are:
1)root the device and then you can get rid of the app.
2)use the factory reset option in system settings to reset the device.
3)boot to stock recovery and use the factory reset and wipe cache option in recovery.
4)the last option you won't need but you can restore the stock firmware via whatever flashtool the device uses.
If you are trying to avoid resetting the device to prevent losing data then try rooting the device and just use root access to remove the app. Depending on the rooting method you won't lose any saved data.
If you don't like either of those options, try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
Thanks for the answer, but I already solved it. I rooted the phone with Framaroot and then nuked it from the phone with Titanium Backup. Afterwards, I locked down root access/rights as best as I could. Better safe than sorry heh.
boki9999 said:
Thanks for the answer, but I already solved it. I rooted the phone with Framaroot and then nuked it from the phone with Titanium Backup. Afterwards, I locked down root access/rights as best as I could. Better safe than sorry heh.
Click to expand...
Click to collapse
You can remove root access if you think its too risky for your dad, if you think he may at some point make a big mistake because of root access I would recommend removing root to avoid getting the device in a situation that nay not be fixable. If you need root later you can re root it like you did this time, you may can even go a step further and install a custom recovery and use it to create a nandroid backup, then if at some point something goes wrong you can just restore the nan droid and be back to how everything was when the backup was created. You might even be able to make the backup then remove root and if you need root back you can restore the band to is and have root to do what needs to be done. Just a few options for you, whatever you think would work best.
So I have a lg l58bl. Its supposedly unrootable. But before I knew that I tried to use kingroot on it hoping that app could do it. (I had read it could work on a nearly identical phone model in terms of hardware/processor.)
But it didnt work. Well it seemed like it halfway did. I could access some stuff I couldnt before but still my profile was not seen as rooted. I think I changed a fuse setting file and bricked.
Did a factory reset. Then my brightness would auto adjust to 65% even after I set it to 0% 50 times. Did that a minute after booting.
Then I tried searching in directories and found a lot of kingroot files. Some that are documented. Some that are not. Like a "kr." File in some place like bin. It was a file written to run every boot to restructure the permission tree and give the newly added account of kr full root. Pretty simple solution.
So this phone was abanodoned out of fear of infection. I didnt know if itd be safe to connect to internet on it. So ive isolated it until I can know.
I worried my brightness was due to some kr malware stuff. Although I read that auto brightness was a feature lg phones had for sales room display until a sim was used. But even after inserting an old sim. It still auto adjusted with auto brightness OFF. So how I fixed it was wait until it booted, change to 0. Before it could auto adjust yank batterty out and then remove sim. (Sim doesnt have to be valid). Now it doesnt auto adjust. When I powered it off by button it took an extra bit like it was rewriting a configuration for brightness. That was a problem that took a while. Now
Can anyone give me a list of all kr related files so I can delete anything fishy? I found this but it doesnt help much.I worry this method would miss some of those files. https://forum.xda-developers.com/t/2020-replace-kingroot-v5-x-or-kingo-root-with-supersu.3904880/
Re-flash Stock ROM.
Unfortunately there is no firmware download for LG Rebel 2 LTE tracfone - all links are down or fake
aIecxs said:
Unfortunately there is no firmware download for LG Rebel 2 LTE tracfone - all links are down or fake
Click to expand...
Click to collapse
So alecxs, saw you in this topic https://forum.xda-developers.com/t/kingroot-malware-adware-root.3563090/page-3
You got any ideas in your wise experience?
On that kr txt file, files I saw in my phone are not listed there. 1 was an html5 file.
Whats worse, if I recall right I did not have permission to delete 1 of the files.
If I get the courage to try ill see if I can find those files again.
So as it stands, without fastboof or download mode (lol fastboof)
And no kdz. And kr mystery. The thing might as well be bricked?
I would like to use this phone on the net but I suppose that goose was cooked unless someone knows a way.
I had tried supersume pro I think but it failed.
If only there was a way to wipe partitions in factory reset mode but it just has a white background menu.
Anybody know if I could intentionally corrupt or delete the partition with the spy files? Probably not easy without root. But I did somehow edit 1 of the main config files and move it back to the main dir renamed old file and restarted to brick. But not sure if kr was given me halfroot or the facade of root.
Hmm. if im using this online wouldnt I risk infecting others through that? Like if kr is running a background daemon couldnt they inject things into files?
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
If only it was that easy lol. Thanks though
The best you can do is root that phone with kingroot, then use the kingroots official unroot/uninstall menu within the kingroot app.
Do not try to wipe system partition without having backup or stock rom.
Hmm. Looking more and more hopeless. Becausd I bricked after root attempt(which failed) but still kingroot managed to install stuff. Some in places I dont hVe permissions to do anything with.
I would guess it used like dirtycow or w/e to install through temp?
And now that its factory reset even ifi install kr again to uninstall wont there still be the instance of kr from before brick?
Crap.
Well unless I can figure out a way I guess this phones toast. I really dont feel comfortable using it with potentially malicious files hidden in it running on boot.
Not that huge of a loss but I would like to use it
AstralA said:
even ifi install kr again to uninstall wont there still be the instance of kr from before brick?
Click to expand...
Click to collapse
Kingroot has a very clean Uninstaller and will remove itself completely. If there is any (potential) malware left this is not caused by Kingroot, it's more likely you accidentally granted root access to that malware.
Kingroot was the only app installed after factory reset. So that file could only come from kingroot. It had kr in the file name anyway. Oh well. If I do anything with it ill lock all internet and use a linux installation. But probably wont even do that. Kingroot as good as ransomware because good luck cleaning up afterwards. sounds like kingroot used to not be so bad. But maybe it was that malicious and nobody suspected until it was too late.
Edit: of course kingroot is great if you have a firmware to reinstall and all else fails. Like pos devices stuck in read only from manufacturer.
But it sucks to not feel able to safely use a device that I payed money for. Which was the problem from the manufacturer as well.
I still didnt find the files in question because it would be a crap chore but I did recall kingroot failed to get root initially, then after trying again it bricked. But I could still get to factory reset holding vol up and pow. But even though kingroot failed to get root it did manage to install files in read only directories (ro without root). Presumably adding a new user with permissions that the main user lacks. But thats the problem. Theres not a way for me to access the directories where the files are. Because kr cant give the main original user those permissions I guess...
I heard of a similar tactic to root fire hd 3rd gens that auto updated to be fstabbed stuck in ro with no bootloader access.
Use kingroot to brick the fire then after bricking fastboot works.
But if I did that with the phone I still lack a dz or kdz/img. But I could try installing a different phones kdz that uses the same board/cpu. As far as I can tell theres a resistor on those pcbs to determine brand/service provider.
The k7 is identical for instance (in terms of hardware) but the last time I tried that it did flash but then the phone is bricked hard. Lgup cant recognize the model because the k7 firmware doesnt match whatever bits are used to sign what version it is (m151 or ls675) yet the cpu and ram matches.
But I might try that in my desperation.
Also words of wisdom. Dont cross flash firmware because it will usually end in brick.
I only entertain that thought because of the situation.
Although if someone knew where I could find the bits to set phone model in firmware? Thatd help. Anyway. Thanks and cheers.
I installed new soft to my phone and i lost some of photos, screenshot
If I rooted my phone, can I recover my data that was lost after the software update? Can I unroot it later without any effects or issues with banking apps and financial services?
Also, I hope there is a way to retrieve photos and files without rooting the phone because I have tried several methods on both the phone and PC, but they are not recognizing the device even though it appears on the Explorer.
Short answer:
1. A stable wired / wíreless ADB must be given
2. The partition that holds the data in question must be decrypted
3. The phone must be rooted
4. The partition in question must get dumped to PC
5. An external forensic software is needed to read the dumped partition / fles in question
shadyhoo said:
If I rooted my phone, can I recover my data that was lost after the software update?
Click to expand...
Click to collapse
To root your phone, you'll need to unlock the bootloader first.
If you unlock the bootloader, it will erase your internal storage and all files will be lost.
Is your bootloader unlocked as of now?
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
xXx yYy said:
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
Click to expand...
Click to collapse
What are the uses of temporary root?
This post says it is not possible in Android 6 and newer.
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
xXx yYy said:
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
Click to expand...
Click to collapse
Can you provide more information on this? Even links to existing posts would also do fine.
I'm interested to know if it can be used to debloat the system without tripping Knox or other disadvantages of an unlocked bootloader.
TheMystic said:
To root your phone, you'll need to unlock the bootloader first.
If you unlock the bootloader, it will erase your internal storage and all files will be lost.
Is your bootloader unlocked as of now?
Click to expand...
Click to collapse
I had some photos and I was done soft for the phone and lost my photos and screenshot
My phone is a Sony Xperia xz1 compact.. Do you mean to activate this option?
shadyhoo said:
I had some photos and I was done soft for the phone and lost my photos and screenshot
My phone is a Sony Xperia xz1 compact.. Do you mean to activate this option?
Click to expand...
Click to collapse
Activating that option is just the first step. There are other things to do to unlock the bootloader.
Since your bootloader is locked as I expected, rooting to recover files is out of question now. That's because if you follow steps to unlock the bootloader, it will wipe everything on your phone. The question of recovery won't arise.
xXx yYy said:
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
Click to expand...
Click to collapse
My phone is sony xperia xz1 compact
If you root the phone, will this cause a problem with banking financial applications?
is it possible to completely remove the root after that without any problem or I will need to make a new software?
As I can see you've no idea what rooting Android means: it's simply spoken adding SU binary to Android's
filesystem - preferredly put it into RW-mounted /data/local/tmp directory. My recommendation: Become familiar with this, e.g. look inside here.
xXx yYy said:
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
Click to expand...
Click to collapse
So why not just teach us ignorant noobs and grab the cash?
I didn't even exclude exploits (such as mtk-su) in my bounty, I just limited to a real android device phone or tablet
alecxs said:
get yourself a smartphone and learn the basics. I will pay $ 100 if you show any proof of your magic temporary root.
Click to expand...
Click to collapse
@shadyhoo if you factory resetted the device during update, your data is already lost.
You can root your phone after bootloader is unlocked. There might be a way to cheat bootloader and root with Magisk, but still the chances to recover any data is very low to zero. On flash memory the data is discarded right on deletion, recovery tools on file system level won't work because only the emmc flash memory controller (which runs it's own proprietary firmware) knows where the data is located. Only data that isn't discarded yet might be recoverable if it's not too long ago deleted.
It would be possible to get a dump of /dev/block/dm-0 and run extundelete if custom recovery were previously installed. Unfortunately the TWRP for Sony Xperia xz1 compact AFAIR requires custom kernel that supports FOTAKernel partition, boot image must include ramdisk extraction utility extract_elf_ramdisk for installing custom recovery. So this is a showstopper even on cheated bootloader lock.
you can however try to flash magisk patched boot image in EDL mode and see if that passes locked bootloader anyway, if the boot.img is properly AVB signed. if phone is rooted you can dump /dev/block/dm-0 during runtime.
But first clarify how the data was deleted. If a factory reset during the update occured it's absolutely pointless, because once the disk encryption key has changed the data is 100 % unrecoverable.
alecxs said:
So why not just teach us ignorant noobs and grab the cash?
I didn't even exclude exploits (such as mtk-su) in my bounty, I just limited to a real android device phone or tablet
@shadyhoo if you factory resetted the device during update, your data is already lost.
You can root your phone after bootloader is unlocked. There might be a way to cheat bootloader and root with Magisk, but still the chances to recover any data is very low to zero. On flash memory the data is discarded right on deletion, recovery tools on file system level won't work because only the emmc flash memory controller (which runs it's own proprietary firmware) knows where the data is located. Only data that isn't discarded yet might be recoverable if it's not too long ago deleted.
It would be possible to get a dump of /dev/block/dm-0 and run extundelete if custom recovery were previously installed. Unfortunately the TWRP for Sony Xperia xz1 compact AFAIR requires custom kernel that supports FOTAKernel partition, boot image must include ramdisk extraction utility extract_elf_ramdisk for installing custom recovery. So this is a showstopper even on cheated bootloader lock.
you can however try to flash magisk patched boot image in EDL mode and see if that passes locked bootloader anyway, if the boot.img is properly AVB signed. if phone is rooted you can dump /dev/block/dm-0 during runtime.
But first clarify how the data was deleted. If a factory reset during the update occured it's absolutely pointless, because once the disk encryption key has changed the data is 100 % unrecoverable.
Click to expand...
Click to collapse
That's what happened to me an error occurred and the phone froze and then rebooted continuously, it never works, I tried to turn it on for a whole day uselessly bootloop continuously ,
I connected the phone. With a pc using sony companion pc program to repair software, app tell me will erase every thing while installing a new software and erased everything, and the phone appeared as a completely new object
through Google backup downloaded applications, messages, etc.,
but personal photos and files do not exist, and this is what I'm looking for
Do I have any chance to get my photos back or is there no chance ?
shadyhoo said:
I connected the phone. With a pc using sony companion pc program to repair software, app tell me will erase every thing while installing a new software and erased everything, and the phone appeared as a completely new object
Click to expand...
Click to collapse
This counts as factory reset, therefore no chance sorry.
I'm sad to see so many people get into this position.
Backing up the data to MyMegaApp can be complicated because some of that is stored in /data/data/com.mymegaapp/...
Some of that is stored in /sdcard/Android/data/com.mymegaapp/...
Photos are generally stored in /sdcard/DCIM/Camera and that is trivial to backup.
Photos are probably the most valuable thing you have on your phone.
For Windows user, you can use my adbsync.exe in my sig.
Here is one line out of my "sync" script (actually a makefile):
Code:
adbsync /hscu /s C:\Handy\MotoG storage/emulated/0/DCIM/Camera
So at the same time I make sure that all my books and guitar transcriptions are on my device I also backup all the photos.
This probably happens multiple times a week.
And of course I backup my desktop too.
Renate said:
This probably happens multiple times a week.
And of course I backup my desktop too.
Click to expand...
Click to collapse
This. Or just do not care attitude. I still had that when the 1st mSD died. 2nd was bad, about half year of photos and such went. Still hoping to recover it somehow. Then 3rd one went not so long ago. Windows "fixed" it, but now it has some folder added, with files that I don't what they all are... less than a month of damage this time...
So, like Renate said, take backups and take them often.
Adbsync is really good indeed.
Although the usage instructions might need some more details/examples like above...
(Just like some of Renate's other progs - might... )
edit a typo
CXZa said:
Although the usage instructions might need some more details/examples like above...
(Just like some of Renate's other progs - might... )
Click to expand...
Click to collapse
Mmm, probably guilty. You can always ask though.
I always say that I wouldn't cry if a truck ran over my Android.
That is, as long as at the time the device wasn't in my pocket.
Renate said:
You can always ask though.
Click to expand...
Click to collapse
That's not how it works... people just don't realize the potential of your programs that way..
Probably i'm not any better in that though.. lol.
CXZa said:
That's not how it works... people just don't realize the potential of your programs that way..
Click to expand...
Click to collapse
Yeah, I probably should add some examples to some things.
Edit: I added some examples and stuff. Happy(er)?
http://www.temblast.com/adbsync.htm
I was looking in the previous days to recover data from the phone and found a lot of programs, most of which require root for mobile and are not free, meaning that if I want to restore some files, I have to root and also format the phone!! And you all say that it is almost impossible to return files after formatting, so what do all these programs that require rooting the phone do?! I do not understand the usefulness of such programs