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.
Related
first off, i have a cdma hero and i am running cm 6.1rc now, with classicalgas's theme.
i have weird permission problems going on. it seems like i have halfway lost my root. i can run superuser and all the apps that require root, but i cant modify or change anything in my system folders. typefresh gives me an error that says it cant remount. when i use adb to mount the sd, it says i dont have permission. i get the # but it still says no.
ive also noticed a problem with my nandroids. it worked the other night, but now, twice, it will let me make a backup but it will not restore it. it says there was an error and to do it thru adb.
so, basically, i guess i messed something up somewhere. did i lose some of my root functions? can i re-root, or do i have to go stock and do it all over again? any suggestions? you guys are all amazing for the knowledge on here, so i know someone will help me out.
thanks in advance!
tl;dr-- lost some root functions. do i need to start all over again?
anybody got any ideas ?
First off, I've been reading all around here, and this doesn't seem like an uncommon problem.
I'm trying to edit my build.prop file to be able to unlock APN access on my Verizon phone as I need to use it for T-Mobile.
My problem is that nothing in system files that I edit, including build.prop, will stick. I have used Root Explorer Pro, buildprop editor, adb cmd promps. My phone is rooted through weaksauce 2.
Once I edit file, I save it, set chmod to 644 and restart. The build.prop isn't being editted back to the default, it's just being replaced completely-- it will be right back to the default build.prop file that was originally there, with the same original create date and everything.
I've tried everything I know, and I absolutely cannot get anything to stay editted because no matter what I do, the phone will just replace my phones as soon as I boot.
My phone does not have a different ROM installed, and it is still S-ON, but I've tried to stay away from getting that far into it for something that I thought should be pretty simple to fix. Any advice?
storyquest101 said:
First off, I've been reading all around here, and this doesn't seem like an uncommon problem.
I'm trying to edit my build.prop file to be able to unlock APN access on my Verizon phone as I need to use it for T-Mobile.
My problem is that nothing in system files that I edit, including build.prop, will stick. I have used Root Explorer Pro, buildprop editor, adb cmd promps. My phone is rooted through weaksauce 2.
Once I edit file, I save it, set chmod to 644 and restart. The build.prop isn't being editted back to the default, it's just being replaced completely-- it will be right back to the default build.prop file that was originally there, with the same original create date and everything.
I've tried everything I know, and I absolutely cannot get anything to stay editted because no matter what I do, the phone will just replace my phones as soon as I boot.
My phone does not have a different ROM installed, and it is still S-ON, but I've tried to stay away from getting that far into it for something that I thought should be pretty simple to fix. Any advice?
Click to expand...
Click to collapse
I'm pretty sure it comes down to you still being stock & s-on. There's some sort of wp (write protection) which must be turned off in order for you to be able to make changes to the system partition that won't be referred upon reboot. I think wp-off is a feature of all kernels but it may be something from the rom. Maybe it's tied to a locked/unlocked bootloader, he'll I dunno. Either way, whatever exactly it is, wp is your problem. The moment you unlock & s-off your device you'll be able to flash what you want and make such changes.
cntryby429 said:
I'm pretty sure it comes down to you still being stock & s-on. There's some sort of wp (write protection) which must be turned off in order for you to be able to make changes to the system partition that won't be referred upon reboot. I think wp-off is a feature of all kernels but it may be something from the rom. Maybe it's tied to a locked/unlocked bootloader, he'll I dunno. Either way, whatever exactly it is, wp is your problem. The moment you unlock & s-off your device you'll be able to flash what you want and make such changes.
Click to expand...
Click to collapse
Correct. User must s-off since its vzw.
Op- I hate to tell you think but the vzw m8 is a terrible choice for T-Mobile. You might have better luck selling that one on swappa and getting a T-Mobile one off swappa.
Hey all, I'm having a problems to which i've been pulling my hair out and not sure what to do. Essentially, I had my phone rooted, although later decided I wanted to unroot. To unroot I used an app called "simply unroot" however it did not fully unroot my device, just made it worse, my phone does not pass the safety net, however "root checker apps" suggest my phone is not rooted, although some apps recognise my phone as being rooted. My phone bootloader is unlocked, but the OEM toggle in the developer options is not set as enabled, and is NOW greyed out so i cant click it, meaning i do not have access to any fastboot commands and thus cannot flash a recovery.img. Although, believe after having trying to unroot it had automatically disable OEM. I have tried to lock the bootloader in the hopes that OEM toggle would no longer be greyed out, but cannot do this as i dont have access to fastboot commands. Even with TWRP i cannot flash anything just promps me with Error 9. I have tried storing the UPDATE.app within the dload folder, but that doesnt work either. I have no idea how i can recover this device. Fell like i've tried everything. Please help.
rustymole said:
Hey all, I'm having a problems to which i've been pulling my hair out and not sure what to do. Essentially, I had my phone rooted, although later decided I wanted to unroot. To unroot I used an app called "simply unroot" however it did not fully unroot my device, just made it worse, my phone does not pass the safety net, however "root checker apps" suggest my phone is not rooted, although some apps recognise my phone as being rooted. My phone bootloader is unlocked, but the OEM toggle in the developer options is not set as enabled, and is NOW greyed out so i cant click it, meaning i do not have access to any fastboot commands and thus cannot flash a recovery.img. Although, believe after having trying to unroot it had automatically disable OEM. I have tried to lock the bootloader in the hopes that OEM toggle would no longer be greyed out, but cannot do this as i dont have access to fastboot commands. Even with TWRP i cannot flash anything just promps me with Error 9. I have tried storing the UPDATE.app within the dload folder, but that doesnt work either. I have no idea how i can recover this device. Fell like i've tried everything. Please help.
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3702235
https://forum.xda-developers.com/showthread.php?t=3600211
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
does anyone happen to know where frp data is stored on the phone? i bought a used one and the previous owner didnt reset properly so im trying to get rid of this idiotic stupidity before i give up and refund it. he didnt relock it when he sold it so i was able to install twrp and have basically full control of the phone, i just need to know where everything is stored so i can get rid of it. id like to just clear it out rather than doing that 50 step convoluted bypass because i dont want any problems in the future.
Probably should have put a question mark on the title to keep it from looking like a solution. Whoops lol.
Either way I've found a bypass, literally just deleting the setup apk. I've been using my new phone all day rebooting and flashing and installing, and I haven't had one single problem. Of course this requires root or twrp or some other method of rw /system access, but if you can somehow get into settings during setup to enable oem unlocking so you can unlock the bootloader and flash twrp, then you're golden. When I get home I'm going to investigate if this is temporary or permanent (as in do you need to remove setup.apk every reset or does adding your account overwrite ownership).
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.