A couple of weeks ago, I started to mess around with the build.prop file in my LG e430. Things turned bad once I change the api (or sdk) from 16 to 19. Nearly every single app became unresponsive, so I managed to change it back to 16 with es file explorer. I rebooted my phone, and things seemed to go back to normal. Strangely, I seemed to have lost root, so I try to root it again, first with Framaroot, then with other programs on a pc. Every single time it said that it was a success, but my phone did not get rooted. So I told myself, "Maybe the binary is installed but there is a problem with installing Super SU?". I installed super su, but it detected no binary. I tried with other superusers, but with no luck. I then decided to install it before performing the rooting process with framaroot and other programs. Same result as the last. What went wrong? Now I realize that some apps (like aptoide or clean master) derect that I have root, but then can't use it. What's weird is that the build.prop is back to its original state, like it came out of the factory. I can no longer view it or edit it, as I no longer have root. Can anyone help me with getting my phone back to a working root condition? Flashing the stock rom is the last thing I want to do. Thanks.
Devices:
-LG Optimus L3 II
-Lenovo IdeaTab A3000-F
Before you criticize a man, walk a mile in his shoes. That way, when he gets mad, he is a mile away and barefoot.
PJMOR said:
A couple of weeks ago, I started to mess around with the build.prop file in my LG e430. Things turned bad once I change the api (or sdk) from 16 to 19. Nearly every single app became unresponsive, so I managed to change it back to 16 with es file explorer. I rebooted my phone, and things seemed to go back to normal. Strangely, I seemed to have lost root, so I try to root it again, first with Framaroot, then with other programs on a pc. Every single time it said that it was a success, but my phone did not get rooted. So I told myself, "Maybe the binary is installed but there is a problem with installing Super SU?". I installed super su, but it detected no binary. I tried with other superusers, but with no luck. I then decided to install it before performing the rooting process with framaroot and other programs. Same result as the last. What went wrong? Now I realize that some apps (like aptoide or clean master) derect that I have root, but then can't use it. What's weird is that the build.prop is back to its original state, like it came out of the factory. I can no longer view it or edit it, as I no longer have root. Can anyone help me with getting my phone back to a working root condition? Flashing the stock rom is the last thing I want to do. Thanks.
Devices:
-LG Optimus L3 II
-Lenovo IdeaTab A3000-F
Before you criticize a man, walk a mile in his shoes. That way, when he gets mad, he is a mile away and barefoot.
Click to expand...
Click to collapse
see my thread
generally vroot will be your best bet
than u can replace apk later
Thanks for your help.
Devices:
-LG Optimus L3 II
-Lenovo IdeaTab A3000-F
-Hyundai Dual SP 4S
Before you criticize a man, walk a mile in his shoes. That way, when he gets mad, he is a mile away and barefoot.
Related
I rooted it using IOroot last night, factory reset this thing and now it says that. Anyone have any idea why?
htcdesirezgeorge said:
I rooted it using IOroot last night, factory reset this thing and now it says that. Anyone have any idea why?
Click to expand...
Click to collapse
If all you did was root the phone and factory reset then no idea. You didn't freeze anything or mod the phone in any way?
- Tapatalked from the G3
I actually froze a bunch of LG stuff because I didn't like them... Apparently I froze LGSetupWizard or uninstalled it and now I am sitting with a shiny new brick. Hopefully I can unbrick it when I get home; tried at work and the flash tool wouldnt see the device so I was stuck at the log in screen.
htcdesirezgeorge said:
I actually froze a bunch of LG stuff because I didn't like them... Apparently I froze LGSetupWizard or uninstalled it and now I am sitting with a shiny new brick. Hopefully I can unbrick it when I get home; tried at work and the flash tool wouldnt see the device so I was stuck at the log in screen.
Click to expand...
Click to collapse
Yea you will have to put the phone into download mode and use the LG Flash Tool to flash the .TOT. I had a similar problem after I tried to edit the build.prop (less than 24 hours with the phone and had just finished setting everything up...) and since the file is so large Root Explorer can't open the whole thing and saved an incomplete build.prop. Couldn't get through the setup wizard either after factory reset so had to flash the .TOT.
THEbigSWEEN said:
Yea you will have to put the phone into download mode and use the LG Flash Tool to flash the .TOT. I had a similar problem after I tried to edit the build.prop (less than 24 hours with the phone and had just finished setting everything up...) and since the file is so large Root Explorer can't open the whole thing and saved an incomplete build.prop. Couldn't get through the setup wizard either after factory reset so had to flash the .TOT.
Click to expand...
Click to collapse
can someone please help me i have an lg g3 d851 (tmobile). i just got this phone like 3 weeks ago and rooted it..i think i used lg one click root . about a week ago i started having problems with my wifi where some apps would connect and work fine but other apps would not connect. i decided to factory reset (since i didn't have anything on the phone anyway) and when it booted back up i went through the setup process and at the last screen it fails and says "Unfortunately LGsetupwizard has stopped working." and it takes me back to the first screen. I have no idea what to do should i take it to tmobile will they fix it or should i try one of the methods above? if so which method should i do? i dont reallty remember but i think i deleted t mobile my account and google play musi and google play books
Try over in the t- mobile lg g3 area: http://forum.xda-developers.com/tmobile-lg-g3
For Verizon we have options to flash a .tot or a .kdz file. Your phone likely has the same options, but you should look in the area with the right carrier- specific info.
Good luck, it's a great phone!
I need help rooting this tablet that I got for my birthday in march.
I've tried alot of places, towelroot, kingo, almost everything but no success.
It runs android 4.4.2 jellybean and the model (as i placed in tittle) is a DP7856K
Hello XDA. I've been a long time reader of these forums and would now like to learn how to root. I have a dp7856k tablet purchased from walmart and would like to start with this before trying to root my LG G Vista. I have not found anything regarding this tablet and I hope y'all can help. Thanks in advance!
Sent from my DP7856K using XDA Free mobile app
I was able to root my DP7856K with Kingo Root, although now every reboot results in a near factory reset, root remains intact, but data and apps are wiped, signing into google starts the download process. What I've read so far is that the location of busybox is/may be wrong.
ButtersCast said:
I need help rooting this tablet that I got for my birthday in march.
I've tried alot of places, towelroot, kingo, almost everything but no success.
It runs android 4.4.2 jellybean and the model (as i placed in tittle) is a DP7856K
Click to expand...
Click to collapse
Don't know if you're still having problems or not, but the Kingo apk worked for me, although proceed at your own risk, rooting my DP7856K resulted in a factory reset with every reboot, even after moving busy box to /system/bin from /system/xbin as suggested by this forum. I've been forced to keep it on and charged up, or reload everything if the battery gives out unexpectedly.
Hi everybody.. I've been viewing and reading the XDA forums for years, looking for help and tips with various phones.. I just registered today so I could share my recent experience with rooting the Note II (sch-i605 from Verizon) that I bought used.
I was doing my due diligence, researching different methods of rooting, several different websites, which I've concluded are a waste of time because they all link back to the best! Trying to decide if it was worth it with the locked bootloader.. After reading up on several different threads, I figured what the heck.. So I bit the bullet and dove in.. No easy task this, because I don't have internet access at home, other than on my wife's phone with unlimited data.. Downloading the files necessary, saferoot, safestrap, twrp, various versions of drivers, some programs.. All very time consuming over 4g! Lol..
Anyway, having rooted a Motorola Droid Razr, a Samsung Epic 4g, OG Droid, an LG G2, along others in the past, I'm not an expert, but not exactly a n00b at rooting either.. I Odin on my PC from when I did the Epic, and adb was there from multiple devices, so that saved a little time.. So over to the PC I go with my Note 2, wife's G2 and my trusty USB cable..
Saferoot worked beautifully! First time success! Installed jrummy root check to verify.. :good:
I let that be it for while since the bootloader is perma-locked.. But after a couple hours of reading more threads about ROMs, I started feeling the itch again.. So off to download twrp so I can play with some shiny new ROMs.. The twrp website has installation instructions for twrp manager from the play store, upgrading from inside an earlier version, fresh install with Odin, and using "su dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p9".. Since I was on the other side of the room, I decided to try the dd method.. Not having experience with this particular command, I figured some practice was in order.. Read up on what it does, played around with it using some worthless files.. Then I used it in reverse.. Finally I ran the did command for real.. That's when it all went downhill.. When I rebooted I ended up with the Dreaded Yellow Triangle of Doom! Unauthorized software and take the phone to Verizon.. Ask I had was download mode.. :crying:
Fought with the phone and the computer for a while until my wife made me give it up for the night. Studied up some more on the , and jumped right into things first thing this morning.. Downloaded a couple .IMG stock room files, one rooted one not, and a stock recovery .IMG to use with Odin.. Got them into the PC, Windows 7 Pro, hooked up the new brick and fired up Odin.. No joy.. Odin wouldn't see my phone! Time for a smoke break, just had to step back and think about things for a minute or two. After a Google search and some digging, i found a YouTube video describing exactly my problem(Odin or Kies won't recognise download mode). I tried it, and guess what, IT FREAKING WORKED! I don't understand it, but taking the battery out made Odin see my phone!
Now onward we go..Back to trusty old XDA! That's when I found the Android toolkit bySkipSoft.. Talk about a phone saver! Got my phone hooked up, in download mode, tried a few different things in the Unified Android Toolkit, couldn't download anything since the PC has no internet but I already had stock recovery and stock rom images, and the toolkit told me where to stick em! First I tried to use a few adb commands to try to get the data off the phone I wanted to save, but I finally gave up because adb couldn't see the phone since it couldn't see that USB debugging was active, even though I promised it was..
Before I tried flashing the stock rom I thought I'd flash the recovery since that was the beginning of the problem. About 4 mouse clicks, 30 seconds, and a reboot, my phone was alive again! :victory:
Still on the stock mj9 release, rooted with saferoot, and chugging along splendidly.. I may just let it sit this way for a while.. Lol!
TLDR: got a used Note 2, rooted it, b0rked it, and fixed it with the help of the awesome devs and members of XDA!
Unfortunately, I didn't keep track of all the threads, devs, and members I looked at and read that helped me solve my conundrum.. However, the main reason I finally registered was so that I could say a great big THANK YOU to the community here.. It's the best! And you came through for me in my hour of need..
Theude
P.s. as I have time over the next few days I'm going to try to find the posts I used for information, and add my thanks there too.. Also will try to post links, but they'll probably be in text not actual links lol..
Well, I just got this phone this week. It was actually a gift in fact since I broke my last phone a week before this.
As soon as I got used to the new phone. I started playing with it's guts. I rooted it with Kingroot, since it has never failed me before. Installed Xposed Framework, and flashed the 5.1.1 stuff for it to run. I had to flash TWRP to flash the Xposed Framework stuff (for some reason I couldn't get the sideload to work). Got a few modules for it. Got all my usual apps such as Facebook, ES FM, Instagram, etc. Got a few games. Spent some hours playing the games. You know, all the stuff you do when you get a new phone.
Then, I decided it was time to switch from Kingroot to SuperSU, as I do with every phone I root with Kingroot (and there were a few). I did it the same way as I have before, using w0lfdroid's method (I can't post links yet). The Kingroot app didn't automatically uninstall, but SuperSU was working. So, I uninstalled Kingroot manually with ES FM. That caused a lot of "unfortunately, com.kingroot.kinguser has stopped" dialogs that never stopped coming, and I decided a reboot might fix it.
I was wrong, the reboot did NOT fix it. It turns on, goes to the LG logo screen, goes to the Metro PCS screen, dims the background, [all of that within a minute and then] vibrates once, and then no sign of anything else. However, the phone does seem to be alive. When I plug it into USB the MTP starts working. It's also listed in adb's devices list. I can even use adb. I used adb to boot it into bootloader/fastboot, and it's even listed in fastboot's devices. It does still charge.
That damned Kingroot, I'll never use it again to shortcut through rooting. It has always worked, and I've been able to swap it with SuperSU everytime before this one. I just don't want to risk this happening again.
I'm lost on what I should do about this. What would you fella's do?
_____________________
I do have a warranty on it, but I've obviously voided that above. I could lock the bootloader back with fastboot (using "fastboot oem lock") so they don't see anything significant right away, but they could always dig in to see that I've done a lot of changing. Hell, all they would have to do is boot into recovery and see TWRP... xD
Well, I just locked it back ("fastboot oem lock" ) and I think my phone is actually coming back on, it's currently on the "Android is starting" screen optimizing app 12 of 151.
I'm just hoping the lock command doesn't reset my device like the unlock command obviously does... I guess I'll edit this with my results in like an hour when this is done (not literally an hour)!
EDIT 1: 10 minutes later, it seems to be stuck on "Starting apps." after it finished optimizing.
EDIT 2: 10 more minutes later, I'm pretty sure it was indeed frozen on "Starting apps.", so I took the battery out. I turned it back on only to see it still freezing on the Metro PCS screen... Well damn.
EDIT 3: Yet another 10 minutes later, still stuck on the Metro PCS screen...
EDIT 4: I no longer have USB debugging access, since I re locked the bootloader (which seems to have reset it, again). So now I also do not have access to fastboot. I think I screwed myself...
unbricking
@ goatitalone can help you unbrick your device. I still have the files if he is OK with it I can help you too or if he can write a tutorial on here that would be great. @ goatitalone?
I have same exact problem howisit fixed?
Magik1 said:
I have same exact problem howisit fixed?
Click to expand...
Click to collapse
do you still have adb? if you do i can send a twrp backup
its been listed kingroot will brick you, currently the oneclick is compatible with our devices. you should have done some searchign before tinkering with your device in my opinion, if youre smart enough to unlock your bootloader .. you should be smarter in researching root methods.
youll have to reflash your device, contact goitalone - as noone that he's helped will help you with getting those files.
as for it being an ms3302 device.. i havent seen that device under our series.
Use this to unbrick http://forum.xda-developers.com/android/development/stock-firmware-rom-unbrick-lg-k7-k330-t-t3432878
Hi xda,
i currently have an lg g 90 (pretty old model) that is rooted with either kingroot or super su, im not sure. I originally had kingroot but used super su me to try to switch to super su. It said it was completed but kingroot was still there. I then restarted my device and it got stuck on the load up screen with the t-mobile logo. I tried restarting it many times. I then found a tutorial to factory reset my phone but now in the setup, it wont let me go past wifi. It wont even let me type in a password. I'll click next and it will take me to a blank page and back to the wifi setup. Also once this problem is resolved, would it be able to install twerp and cm13 on it? Thank You!
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Check out the L90 forum here for everything you need to properly root and update your device.