I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.
carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted
Related
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
tobdaryl said:
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Click to expand...
Click to collapse
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
flumpster said:
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
Click to expand...
Click to collapse
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Rojikku said:
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Click to expand...
Click to collapse
The twrp mentioned above can be found here.
tobdaryl said:
The twrp mentioned above can be found here.[/URL]
Click to expand...
Click to collapse
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Rojikku said:
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Click to expand...
Click to collapse
Wrong twrp! You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off stock 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Unless the rom you flash is also for 4.2 bootloader. Both are located at teamwin.
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock.
As far as flashing a new rom look at the op and determine if it is for the new stock 4.2 bootloader. If not do not flash over 4.2 but downgrade first. I have upgraded from 10.4.2.20 to stock 4.2 and downgraded from stock 4.2 to 10.4.2.20 several times without issue.
Stock 4.2 includes an assert to only allow upgrade from 10.4.2.20.
tobdaryl said:
Wrong twrp! [/URL]You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Both are located at teamwin.[/URL]
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock and hold a minute or you are going right back where you were or worse. You need slightly more info before going forward and I need to check my notes while you get the proper twrp flashed.
Click to expand...
Click to collapse
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Rojikku said:
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Click to expand...
Click to collapse
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
tobdaryl said:
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
Click to expand...
Click to collapse
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Rojikku said:
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Click to expand...
Click to collapse
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
tobdaryl said:
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
Click to expand...
Click to collapse
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
I decided to take the risk and reboot it. Everything fine. I flashed the tool, ran the reboot command(Which actually didn't work... >>; But I rebooted it manually and it seems fine...)
On that note, is it actually possible to destroy a device beyond repair accidentally? And the TWRP tool said it flashed fine but I still have the old version. Odd....
I do have the image you said currently installed, I checked the version against my download.
Rojikku said:
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
Click to expand...
Click to collapse
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
tobdaryl said:
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
Click to expand...
Click to collapse
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Rojikku said:
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Click to expand...
Click to collapse
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
tobdaryl said:
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
Click to expand...
Click to collapse
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Rojikku said:
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Click to expand...
Click to collapse
When it asks for the password hit cancel and just ignore the error.
tobdaryl said:
When it asks for the password hit cancel and just ignore the error.
Click to expand...
Click to collapse
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Rojikku said:
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Click to expand...
Click to collapse
Thanks for the link. I looked at the info provided for that rom. You don't want to flash that over an encrypted tablet which you now have. The only safe way I have found to go to or from stock 4.2 rom is with stock 10.4.2.20.
To do that you would flash 10.4.2.20 with twrp, boot into os, reboot back to the bootloader which will now be four icons, select usb, use fastboot to flash twrp again, and now flash your new rom.
This sounds long but removes encryption from your tablet and you should be able to flash the jb rom of choice that does not require stock 4.2 bootloader.
Good Evening,
AT&T LG G2 rooted, TWRP. Have installed a few different roms but mostly used PA. All of a sudden the phone started experiencing issues with cell Data. So I did a clean install of PA and then had issues with BT, did another clean install and had issues with Wifi.
So I decided ok maybe its time to go back to stock. Hook it up to a win7 computer... Device manager doesn't see it at all (doesn't show up AT ALL). Says charging and that is it, does not recognize that it is hooked up to a computer. Have tried several different computers now and several different USB cables. The only way I could try other roms was downloading via wifi. Tried a stock rom and still experiencing issues.
I think there is something wrong with the phone so I want to get it warrantied, but without hooking it up to a computer I can not figure out any way to remove the custom recovery or revert it to stock.No matter what I do no computer will even recognize the phone is connected, let alone trying to install drivers. Device manager just straight up does not see it.
Any help or suggestions is GREATLY appreciated. Any way to remove recovery/root without a PC connection?
UPDATE: Here was my solution
Took some work but I figured out a way to do it in case anyone else ever runs in to this:
(make sure you are stock rom or on a stock rooted rom before proceeding)
First download the stock recovery.img on the device.
http://downloads.codefi.re/autoprime...10B_Partitions
Then download/open Terminal Emulator and type:
su
Then
cd /sdcard/downloads
Then
dd if=/sdcard/downloads/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
That replaces TWRP/CWM with the stock recovery.
Then open supersu, go to settings, towards the bottom is full unroot.
Yay no more custom recovery or root on stock rom.
If you are planning on getting warranty you need to use download mode and the back to stock guide also that is the best way to flash to stock and get rid of problems
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
If you are planning on getting warranty you need to use download mode and the back to stock guide also that is the best way to flash to stock and get rid of problems
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Agreed, problem is the computer will not see the phone, so I can't use the program to flash it back to stock.
It's not just a driver or com issue, the computer does not see it AT ALL. Device manager doesn't see a new device when I plug it in (in OS, in Download mode, nothing).
crawlgsx said:
Agreed, problem is the computer will not see the phone, so I can't use the program to flash it back to stock.
It's not just a driver or com issue, the computer does not see it AT ALL. Device manager doesn't see a new device when I plug it in (in OS, in Download mode, nothing).
Click to expand...
Click to collapse
Have you tried different usb ports also very important are you using original cable that came with the phone in my case if I try many of the different cables I have, only the stock one works for download mode
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
Have you tried different usb ports also very important are you using original cable that came with the phone in my case if I try many of the different cables I have, only the stock one works for download mode
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Different usb ports, different computers, different cables (stock one included). No luck. Phone says download mode then goes to "firmware update" and says at the bottom B53 then "ROOTED" in red letters. Nothing appears in device manager.
In android regarless of rom if I plug it in it doesn't act like I plugged it in to a computer, just charging. Again nothing in device manager regardless of USB debugging or not.
currently have twrp 2.6.3.3, running D80210b 4.2.2, with baseband M8974A-AAAANAZM-1.0.190034
What I really need to know is if there is any way to restore stock recovery and remove root without using that method (ie using Terminal Commands or flashing a package, since I can download via wifi).
I am pretty sure this phone has a messed up USB port, but I don't really want to send it in with it rooted/twrp on it .
crawlgsx said:
What I really need to know is if there is any way to restore stock recovery and remove root without using that method (ie using Terminal Commands or flashing a package, since I can download via wifi).
I am pretty sure this phone has a messed up USB port, but I don't really want to send it in with it rooted/twrp on it .
Click to expand...
Click to collapse
Did you try restore & reset functionality on the phone? I had somewhat similar issue with the plug & pop feature (although my laptop recognized the phone under Devices & Printer but it didn't show it as a separate drive) when I flashed CM11 but then I did a full factory reset, everything goes back to normal. Also you might try uninstall LG driver and reinstall it. Hope this help.
paulthuong said:
Did you try restore & reset functionality on the phone? I had somewhat similar issue with the plug & pop feature (although my laptop recognized the phone under Devices & Printer but it didn't show it as a separate drive) when I flashed CM11 but then I did a full factory reset, everything goes back to normal. Also you might try uninstall LG driver and reinstall it. Hope this help.
Click to expand...
Click to collapse
Unfortunately it is not a driver issue, it doesn't show up in device manager at all, on several machines.
I have tried multiple different roms, factory rests, even tried ADB sideloading, no luck.
i remember there's this app called Auto Rec that has an option to unroot the device or something like that.
Took some work but I figured out a way to do it in case anyone else ever runs in to this:
First download the stock recovery.img on the device.
http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware/10B_Partitions
Then download/open Terminal Emulator and type:
su
Then
cd /sdcard/downloads
Then
dd if=/sdcard/downloads/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
That replaces TWRP/CWM with the stock recovery.
Then open supersu, go to settings, towards the bottom is full unroot.
Yay no more custom recovery or root on stock rom. (this was after flashing a rooted stock rom by downloading it on the device itself since I had no USB).
crawlgsx said:
Took some work but I figured out a way to do it in case anyone else ever runs in to this:
First download the stock recovery.img on the device.
http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware/10B_Partitions
Then download/open Terminal Emulator and type:
su
Then
cd /sdcard/downloads
Then
dd if=/sdcard/downloads/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
That replaces TWRP/CWM with the stock recovery.
Then open supersu, go to settings, towards the bottom is full unroot.
Yay no more custom recovery or root on stock rom. (this was after flashing a rooted stock rom by downloading it on the device itself since I had no USB).
Click to expand...
Click to collapse
So did this worked for you? And what about your warranty?
I have an issue with the vibration and I am thinking of going to stock and send my G2 to LG.
petran_7 said:
So did this worked for you? And what about your warranty?
I have an issue with the vibration and I am thinking of going to stock and send my G2 to LG.
Click to expand...
Click to collapse
It worked perfectly and I got the phone exchanged without any hassle, but if your USB is working there are plenty of better ways to return to stock. This was an option I had to use because of USB not functioning. I mean this would allow you to unroot without wiping/restoring but if your going to send the phone in anyway you might as well wipe it as well.
crawlgsx said:
It worked perfectly and I got the phone exchanged without any hassle, but if your USB is working there are plenty of better ways to return to stock. This was an option I had to use because of USB not functioning. I mean this would allow you to unroot without wiping/restoring but if your going to send the phone in anyway you might as well wipe it as well.
Click to expand...
Click to collapse
I understand and thank you for the reply.
I am a bit afraid of the other methods I saw and this one seems easier
I have a question if you can answer to me.
I restored the official rom from TWRP and did all the process you wrote. Is there any way to check if now I have the stock recovery?
And to see if I am now ready to send my phone to LG?
P.S. "I will hit the thanks button tomorrow because I have reached the limit of 8 thanks per day "
petran_7 said:
I understand and thank you for the reply.
I am a bit afraid of the other methods I saw and this one seems easier
I have a question if you can answer to me.
I restored the official rom from TWRP and did all the process you wrote. Is there any way to check if now I have the stock recovery?
And to see if I am now ready to send my phone to LG?
P.S. "I will hit the thanks button tomorrow because I have reached the limit of 8 thanks per day "
Click to expand...
Click to collapse
Just reboot to recovery, you should get the stock LG recovery instead of TWRP. If you unrooted as well, you are good go. Glad I could help! No worries on the thanks .
crawlgsx said:
Just reboot to recovery, you should get the stock LG recovery instead of TWRP. If you unrooted as well, you are good go. Glad I could help! No worries on the thanks .
Click to expand...
Click to collapse
When I am going to recovery, appears the Factory hard reset option.
I did it and it shows up again when I am trying to boot to recovery.
Again thank you for your replies and the time you spend. :highfive:
petran_7 said:
When I am going to recovery, appears the Factory hard reset option.
I did it and it shows up again when I am trying to boot to recovery.
Again thank you for your replies and the time you spend. :highfive:
Click to expand...
Click to collapse
Awesome sounds like you got it. :good:
So I have to congratulate and thank once more this man @crawlgsx for this great thread.
It worked on my D802 (international model) and got it repaired by the official service center of LG in Greece.
Great work, with no need of PC and difficult processes.
Noob question, but will this allow users to take OTA updates? Running stock rooted right now and really don't want revert to stock to get latest ota, but this seems pretty seamless. Thanks.
thestrangebrew said:
Noob question, but will this allow users to take OTA updates? Running stock rooted right now and really don't want revert to stock to get latest ota, but this seems pretty seamless. Thanks.
Click to expand...
Click to collapse
I believe that in order to take OTAs you must be on stock rom and stock recovery. Be rooted will not be a problem if you have these stock but when OTA installed you will lose root access.
If I am wrong, correct me someone.
Hi
Sorry to bump this thread but I need to unroot my AT&T G2 800 so get the warranty.. I had taken the stock backup using twrp.
Can I restore the restore it using twrp ? and do i need to install Terminal emulator on my restored stock rom and then do the commands ?
Are there any chances of bricking the phone ?
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.
EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central
CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.
tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.
I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.
Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.
Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?
Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.
The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.
Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.
Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!
I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.
Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.
I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.
Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol
I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...
treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...
You need to root to flash twrp?
EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.
amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.
oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing
oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?
Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...