Hello,
I've been working on rooting an LG K20 M255 (ATT) for a few days with little luck. It refuses to get in to the bootloader using the manual button press method or adb. I can get it in to SAFE mode, but that's it. When I try to get in to the bootloader it just reboots normally.
My google-fu has led me to believe that this phone is not ideal for rooting, but it's what I've got and I wanted to exhaust all my options before I started looking to replace it.
If anyone has helpful information on how to unlock and root this thing, it'd be appreciated. My goal is to root it, image it with a linux build and attach a wifi dongle via OTG cable.
Assuming that I decide I've banged my head on the wall enough with this phone, are there recommendations for an inexpensive android device that would be a better fit for what I'm trying to accomplish? I've got a few in mind, but I'd really appreciate input from those with more experience than I.
Thanks!
Related
Okay, So I've been looking since August for a rooting tutorial for this phone and I've had zero luck.
I've attempted nearly every simple method of rooting (Gingerbreak, Superoneclick, etc) and all to no avail.
My phone has been in debugging mode and I do have the drivers installed (courtesy of the Huawei's website) so I'm not sure where to go from here.
I've learned that holding down the Power Button and the Volume Up button boots the phone into Recovery mode but I'm not sure if that's helpful or what to do with it. I considered attempting to use Odin but I can't find out how to get my phone into Download Mode (if it even has it).
If anyone could guide me of where to go or what to try, that would be greatly appreciated. I'll answer any questions that you need.
It's running 2.3.6 gingerbread, and the cell provider is Cricket, if anyone needed to know.
Huawei doesn't have the phone listed in phones that need the bootloader unlocked.
I've also found one tutorial, but it doesn't work, I keep getting permission denied on "adb push root/flash_image /data/local/", and it also uses Z4 and from what I've read, Z4 doesn't work on devices past 2.2, I could be wrong though.
Please help me, I'm a tad desperate.
Did you figure this out? ....or somebody did? Thanks.
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
Hello I bought this product http://www.staples.com/Nobis-7-inch-8GB-Tablet/product_1052513
But I cant find anything to root it can anyone please help?
darkphate83 said:
Hello I bought this product http://www.staples.com/Nobis-7-inch-8GB-Tablet/product_1052513
But I cant find anything to root it can anyone please help?
Click to expand...
Click to collapse
As an alternative, is there a way to install CM-10 or CM-11 on it? (yeah, I expect if no developers have one here, it might be difficult to develop an image for it). For now I haven't needed to root it, as it's doing what I need for now, but if I want to start moving apps (or app data) off to a microSD card, I may need a root or CM1x version (and Google needs to be *smacked* for disabling SDcard functionality in later Android versions).
I have just purchased one of these NB7022S tablets from Staples as well. I have unsuccessfully been trying to root it for the last couple of days. Any help would be greatly appreciated
I have one of these Nobis NB7022s tablets as well, but the screen has been broken. So since the tablet isn't usable in it's current state, would it be of use to someone to do a teardown/analysis of the device in order to make a CyanogenMod port to it?
success
Just rooted the nb7022s using kingo root. First download the android software developer kit on your pc then open the sdk manager and download every possible update in order to have the correct drivers, not sure which one did the trick because i just downloaded everything. Then in your tablet go to settings-about tablet- then scroll down to build number and click 7 times to unlock developers options on the main settings screen. Go to developers options and turn it on and enable usb debugging. Plug tablet into your PC and install and run kingoroot. Should connect and root your tablet and automatically install superuser. Now I just need to figure out what version of clockworkmodrecovery to flash as recovery because this tabket does not have a supported cwmr, any help on that would be awesome because i dont want to brick my very first rooted device lol. Hopefully this info might help another newbie like myself.
thanks buzzdb666 for the tip on rooting. However, now every time I turn off the tablet and on, it always does a factory reset/wipe so I have to reinstall everything . Wondering if you've encountered the same thing?
Would be an interesting experiment to try, but again, the tablet has a broken screen, and I can't have a mouse *and* a connection to the computer at the same time. I had thought I could at least get the debug info from the tablet in case someone wants to develop an image for a non-broken unit. Once again, it's available if any XDA developers would like to use it for tear-down or testing, since I can't do much with it otherwise. Unless there's a way to extract what someone would need via a microSD card.
Mine is doing the same thing after using Kingo Root. Not sure what can be done since I can't go backwards now.
My Nexus 6 has presented me with an interesting challenge. During my attempts/process to root my phone, inevitably, one must reboot your phone. And as the reboot takes place the phone always goes into the "Charge" mode and not the "File Transfer" mode that the phone was in as it began the root process. I'm at a cross in the road because I cannot complete the root process. The only option that has presented itself to me is to restart the phone. And while my phone works properly, it halts the root process. I have just purchased another USB cable that charges and transfers data/syncs to cover that question. Any hints would be appreciated. I have had this phone unlocked using Chainfire's Nexus Root Toolkit a while back. It worked flawlessly. I've not really been interested in a custom ROM/Kernel etc. but in continuing to research this area. I'd like to try and unlock then root the phone again. Any hints would be appreciated
If your phone got the January update from Google, they patched a ton of the "exploits" that previously were/can be used to root Android devices. These were pushed out to the Nexus line by Google and made available for OTA by wireless vendors otherwise. This could be the issue you're running into now. If you haven't updated, then I think you just may need to find an alternative rooting method, as the one you tried may not be 100% compatible or is missing some sort of command to direct the device to go into file transfer/download mode.
wosumner said:
If your phone got the January update from Google, they patched a ton of the "exploits" that previously were/can be used to root Android devices. These were pushed out to the Nexus line by Google and made available for OTA by wireless vendors otherwise. This could be the issue you're running into now. If you haven't updated, then I think you just may need to find an alternative rooting method, as the one you tried may not be 100% compatible or is missing some sort of command to direct the device to go into file transfer/download mode.
Click to expand...
Click to collapse
I really appreciate your perspective. And without a doubt I'll look around and see where this goes. Just reading about all the work that has taken place since I purchased the phone, the landscape is a lot more enticing.
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
afireblood said:
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
Click to expand...
Click to collapse
Update: Now in search of the Moto G7 specific blankflash.zip
If anyone knows where I can find that I would really appreciate it!!
I am not familiar with the g7. (I own a G5+). I believe the G7 code name is "river". You can look at https://mirrors.lolinet.com/firmware/moto/river/ and they show a blank flash - but let me say something - a blank flash must be exact for your phone. Its basically the main disk partition with other partitions inside. My phone has 64GB/4GB, and 32GB/3GB-2GB models - so you see a problem. But if all the G7s are the same, then this blank flash should be OK.
Also you can download the phones original firmware at https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/ , if its a US model. If its not, back up 1 directory and you can find it by either carrier or country. You can fastboot the firmware - which I would do before a blankflash,
Hope that helps.