So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
How many times per day does this thread need to be made?
You're either going to have to flash just the update via fastboot on your own, or unroot and accept the OTA normally.
Well I appreciate the answer, sorry to be a bother...
Anyway, is this the way it's always going to be since I'm rooted and unlocked? Where will I be able to download the OTA updates so I can flash manually with fastboot?
It won't work if you have ClockworkMod's recovery, you need the stock recovery.
Sent from my Galaxy Nexus using XDA App
105437 said:
So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
Click to expand...
Click to collapse
Dowload from http://code.google.com/android/nexus/images.html. It needs 7Zip to uncompress the file. Once decompressed it has a file with no extension, decrompress that again and you will have the several file.
The just power the phone off and power back on with the volume up and down pressed. Same as when you rooted it.
Then run these commands:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
sleep 5
fastboot update image-yakju-icl53f.zip
This will not wipe your phone!
You will need to root it again.
This is what I just did and works prefectly!
Root and unlocked bootloader shouldn't prevent you from installing if you still have stock recovery. If you have ClockworkMod recovery instead, you can use that to flash it manually. If your phone downloaded the update zip, it should be located in /cache.
You'll probably have to re-root after applying the update, regardless of how you install it.
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
105437 said:
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
Click to expand...
Click to collapse
I believe that in rom manager you should be able to set the recovery back to the default.
Bad Liar said:
I believe that in rom manager you should be able to set the recovery back to the default.
Click to expand...
Click to collapse
ROM Manager only has the option to flash ClockworkMod, not stock recovery. But the stock recovery can be extracted from the Google factory images and flashed with fastboot.
I have same problem like yours, how can i solved it? my device is SE WT19i
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
ceribaen said:
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Click to expand...
Click to collapse
Each if those warnings that you are getting is because something is not stock. You will need to download the appropriate stock file for each of those warnings. I have already posted the stock build.prop and boot image in the main IMM76I update thread. If you need others, instructions can be found in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
philipdeane said:
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
Click to expand...
Click to collapse
bingefister said:
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
Click to expand...
Click to collapse
toxaris said:
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
Click to expand...
Click to collapse
All of you guys recommending using a toolkit: do you even understand the OP's issue? I don't think so, otherwise you would know that a toolkit won't do what he needs done.
My opinion:
On an unrelated note: you need to figure out how to do things manually before you start using toolkits, otherwise you will never learn anything. There is a reason they teach you long division in school before letting you use a calculator...
Sent from my Galaxy Nexus using Tapatalk 2
Related
I am putting together a quick guide on how to update your Stock ROM, Rooted, custom recovery T-Mo GSIII without having to wipe your phone.
You will need:
- Kies (If your phone has not prompted you to install the OTA yet, Kies will download and attempt to install it for you) (http://org.downloadcenter.samsung.c.../20120809103126135/Kies_2.3.2.12074_13_13.exe)
- ODIN 3.7 (http://forum.xda-developers.com/attachment.php?attachmentid=1270006&stc=1&d=1345396888)
- STOCK T-Mo GSIII recovery.img (I extracted this from the stock ODIN image for T-Mo) (http://forum.xda-developers.com/attachment.php?attachmentid=1269983&stc=1&d=1345396186)
- TWRP or CWM ODIN Flash-able recovery (CWM - http://forum.xda-developers.com/attachment.php?attachmentid=1269979&stc=1&d=1345396186 , TWRP - http://forum.xda-developers.com/attachment.php?attachmentid=1269980&stc=1&d=1345396186)
- Recovery flashable SuperSU root package (http://forum.xda-developers.com/attachment.php?attachmentid=1269984&stc=1&d=1345396186)
SO, place your phone in download mode (Vol Down + Home + Power), and via ODIN, flash the "Stock-Recovery-Image(Working T-Mobile T999).tar" image. ( This is putting the stock recovery back on your phone so the update can install).
When it reboots, either select yes to allow the OTA update to install (if your phone is already aware there is an update) on your phone, OR plug you phone into your PC and allow Kies to prompt you to update your firmware. Select yes and allow the OTA to install.
Once completed, your phone is updated without having to wipe, but you have lost root and customer recovery, so.....
Again, in Download mode, Flash either of the provided ODIN flash-able custom recoveries (TWRP, or CWM) I prefer TWRP
Once that is complete, you can reboot your phone into the new recovery (Vol UP + Home + Power)
Once in recovery, flash the SuperSU.zip package and Voila, all done, Triangle away and you in cool runnings.
Let me know if I need to clarify anything here. It makes sense to me, but then again, I fumbled through it to figure it out and extract the right recoveries and set permissions etc.....
Please hit the thanks button if this helped you in any way
Hans
Nice instructions, but I'm going to wait a few days. I'm want to see if the dev that did the flash and root without tripping the flash counter will do the same for the new firmware. I'm still not too keen on custom recoveries yet even though I backed up my IMEI, so I just want to be rooted. If not, I'll use your guide.:good:
Wildchld already released it.
http://forum.xda-developers.com/showthread.php?t=1838101
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Wildchld already released it.
http://forum.xda-developers.com/showthread.php?t=1838101
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
But with Wildchild's it's a complete ROM (650-700MB), correct? Are you not wiping when you flash his?
Actually I'm not 100% that you need to do a full wipe, but I'm guessing you probably should. Depends on what's different. You can always nabdroid and give it a shot. I will later if I have time.
Anyway, I was more responding to the post above mine about stock with root than to the op. Sorry if shoulda been a little more clear on that.
Sent from my SGH-T999 using xda app-developers app
i might wait. finally got google now and google wallet working and i dont want to mess it up lol
RotaryXperiment7 said:
i might wait. finally got google now and google wallet working and i dont want to mess it up lol
Click to expand...
Click to collapse
What did you have to modify to get them working? Like I said before, I made this little method so you did not have to wipe your phone to get the OTA installed.
The only thing I could see that would cause the OTA to break wallet, or Google now would be that if you have to modify pieces in the /system/ directory that would be overwritten. The only thing I had to do after updating was re-flash my little installer for international boot image, re-remove Carrier IQ as it was added back, and revert the googlesearch.apk to the earlier backed up version (functioning unified search) with titanium. Outside of that I run a pretty tight ship as far as system modifications go outside of root and root privileged programs.
had to edit build pro for wallet
Thanks op, this worked great for me! Updated and rooted again...
Sent from my rooted T-Mo SGS3
I tried several times but couldent unroot my phone. I even tried through the root kit by mskip. I think the problem may be that I got my phone unlocked, not using an unlock code but some other method (all I know about this method is that my phone says"restricted access" for a few seconds upon restarting.)
Any suggestions on how to unroot? Also, if I unroot, will I loose the unlock?
pappuhathi said:
I tried several times but couldent unroot my phone. I even tried through the root kit by mskip. I think the problem may be that I got my phone unlocked, not using an unlock code but some other method (all I know about this method is that my phone says"restricted access" for a few seconds upon restarting.)
Any suggestions on how to unroot? Also, if I unroot, will I loose the unlock?
Click to expand...
Click to collapse
I think the best method to unroot your phone will be to ODIN it back to the stock T-Mobile image. (Overwrites EVERYTHING, probably your unlock as well).
http://forum.xda-developers.com/showthread.php?t=1737855
Above is the link to the stock image.
Apologies, in general, but I feel you may have the wrong thread if your looking to unroot your phone. That is off topic on what is being discussed here.
has anyone tried this and kept google wallet and google now working? Any troubles?
I'm wanting to update but I'm rooted withthose two apps finally up and running.
arts711 said:
has anyone tried this and kept google wallet and google now working? Any troubles?
I'm wanting to update but I'm rooted withthose two apps finally up and running.
Click to expand...
Click to collapse
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
cybrnook said:
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
Click to expand...
Click to collapse
So (in case this all doesn't work out) to restore via nandroid, just root and apply right?
cybrnook said:
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
Click to expand...
Click to collapse
You are correct about build.prop being overwritten.
Sent from my rooted T-Mo SGS3.
If I've helped you, be sure to use the thanks button!
arts711 said:
So (in case this all doesn't work out) to restore via nandroid, just root and apply right?
Click to expand...
Click to collapse
Well if it doesn't work (Which I think it won't), you don't need to worry about restoring root. You just need to flash a custom recovery to revert your nandroid backup. Your root and customization will come back with that.
But with some of the added features that come with the update, I would say don't look back. Upgrade to the latest, then reapply your customization to get wallet and all working again.
IF you have to revert your nandroid back, make sure to do a factory wipe before you revert to your backup.
thanks! i'll give it a shot this weekend once i get more time.
I've used two different versions of Odin and two different T-Mobile stock recoveries (other one is here), and I can't get stock recovery to replace CWM on my GS3. Odin reports that the flash is successful, but when it reboots, ROM Manager still shows me as having latest CWM Touch, and the T-Mo update fails. I'm attempting the update via Kies right now, but I anticipate failure due to CWM still being installed as recovery.
-- I have Cerberus anti-theft installed, but I don't see anything about protecting recovery.
-- I have Busybox installed, but that shouldn't affect recovery.
Any ideas?
EDIT: Interestingly enough, where the OTA update failed, the Kies update went smooth as silk. Now to re-root and remove bloatware!
RaymondPJR said:
Nice instructions, but I'm going to wait a few days. I'm want to see if the dev that did the flash and root without tripping the flash counter will do the same for the new firmware. I'm still not too keen on custom recoveries yet even though I backed up my IMEI, so I just want to be rooted. If not, I'll use your guide.:good:
Click to expand...
Click to collapse
Are you referring to MrRobinson's rooting method? I'm waiting for it too.
Sent from my SGH-T999 using XDA Premium App
Im unable to update. I used Odin to flash the stock recovery, then downloaded the update via settings-> about device-> software update. Installing reboots the phone but then fails and reverts to current state. I can't update through kies also bc it just says "connecting", no errors. I tried uninstalling/reinstalling drivers but kies never completes connecting. Any help?
Sent from my SGH-T999 using xda app-developers app
EDIT: I uninstalled all my samsung drivers and Kies from "Programs and Features" in win7, deleted Samsung folders from HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. Reinstalled Kies and connected my phone to install the drivers. Kies was stuck in the connecting loop still, so I unmounted my sd card, turned on USB debugging and Kies finally connected and asked to upgrade. Upgrading at this moment.
I have an unlocked I9250 Galaxy Nexus that was rooted. I recently upgraded to 4.1.2 using the automatic update. I had Voodoo OTA Rootkeeper installed which worked for the last upgrade, so I didn't even think about it. But I lost my root. Is there a way to re-root without losing any settings or data? When I boot into recovery I see the android with a red exclamation point. I assume My custom recovery was removed with the upgrade. Thanks!
I know this isn't answering your question, but I wanted to mention that I, too, had Voodoo OTA RootKeeper installed when I updated to 4.1.2 and it worked perfectly. I was on stock 4.1.1.
Sent from my rooted GSM Galaxy Nexus
Was I supposed to run the rootkeeper app prior to upgrading? I did not do that. Although I would think that it would have saved the superuser file from the previous run. I'm not sure how it works. either way, I definitely am not rooted anymore and not sure what to do. I'm not even sure if there are tools to root 4.1.2, or if the old toolkit works the same with this upgrade.
CatThief said:
I know this isn't answering your question, but I wanted to mention that I, too, had Voodoo OTA RootKeeper installed when I updated to 4.1.2 and it worked perfectly. I was on stock 4.1.1.
Sent from my rooted GSM Galaxy Nexus
Click to expand...
Click to collapse
Hmm good question. All I did was open it prior to the update to verify that all of the checkboxes under "Status" were filled in and su was protected.
After the update downloaded, rebooting took me into ClockworkMod Recovery where I had to give the ok to install the new file.
The only thing I needed to do after updating was flash ClockworkMod Recovery again. Everything else was fine.
As for rooting your new stock 4.1.2, here's a good place to start. You shouldn't loose your data assuming the bootloader is still unlocked.
http://forum.xda-developers.com/showthread.php?t=1529058
Sent from my rooted GSM Galaxy Nexus
download the superuser or supersu zip
download cwm or twrp recovery image
boot into fastboot mode
fastboot boot cwmortwrp.img
flash the superuser or supersu.zip
done.
Zepius said:
download the superuser or supersu zip
download cwm or twrp recovery image
boot into fastboot mode
fastboot boot cwmortwrp.img
flash the superuser or supersu.zip
done.
Click to expand...
Click to collapse
This.
Sent from my Galaxy Nexus using xda premium
Thanks everyone. Will doing this require a factory reset or any internal data loss? Or does that only occur when unlocking the phone?
prattleon said:
Thanks everyone. Will doing this require a factory reset or any internal data loss? Or does that only occur when unlocking the phone?
Click to expand...
Click to collapse
only when unlocking the phone, flashing userdata.img in fastboot, or using fastboot erase userdata
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
You're rooted, which means you edited the system, which means the OTA probably won't install. Always better to go back to 100% stock and re-root
ftrack said:
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
Click to expand...
Click to collapse
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
Huh.. I've received JDQ39 ota, I forgot to remove TWRP before hand, but it still went through anyway. It installed fine, surprised the hell out of me actually. TWRP 2.4.1.0. Didn't have any other mods though. Not even rooted.
Sent from my Nexus
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
you can definitely install the OTA with a custom recovery. it however will not install if you modified any /system files, bootloader or radio do not match.
Oh really? That surprises me honestly. Although I never tried it, I always assumed every partition needed to have unmodified stock files (adding extra files does not matter). Apparently the recovery partition is an exception.
Petrovski80 said:
Oh really? That surprises me honestly. Although I never tried it
Click to expand...
Click to collapse
+1
I was really surprised, in a good way! xD
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Sent from my Nexus 7 using xda app-developers app
datallboy said:
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Click to expand...
Click to collapse
There are many ways to accomplish the same end goal.
You can actually install the OTA while rooted. Just need to run the small fix in this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
Rerooting on this device is super simple.
There are also other options like flashing the factory images or one of the pre-rooted odexed/deodexed repackaged mostly stock ROMs. You can find them described here:
http://forum.xda-developers.com/showthread.php?t=2415497
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Sent from my Nexus 7 using xda app-developers app
datallboy said:
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Click to expand...
Click to collapse
You need to run the fix I mentioned above OR unroot BEFORE installing the OTA or the OTA will fail near the end.
You can find the OTA here:
http://forum.xda-developers.com/showthread.php?t=2415497
Don't quite understand the post, so better to just hold off on an attempt.. Would using the unroot option in SuperSU, allowing the OTA update to go through, then rerooting work fine without deleting data?
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Sent from my Nexus 7 using xda app-developers app
Super-Su unroot never help you if you delete something in the /system directory
1)you must flash fix after root
2)do not flash permanent custom recovery and relock bootloader (if your bricked you devices you can send to Warranty Service)
3)replace backup of /system directory before update
and after update clean Dalvik Cache before flash Root again (if superuser privilegies still anavalable for you)
Understand the fix now. Noticed the update went through, but got an error when it finished. Flash ota update in temporary recovery. Correct?
Sent from my Nexus 7 using xda app-developers app
I just downloaded the OTA to the device, unrooted, installed the OTA in TWRP, and then the latest superSU zip (still in recovery). Reboot and voila.
datallboy said:
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Click to expand...
Click to collapse
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
The fix worked, and I'm still rooted. with all data. Temporarily booted into TWRP, flashed the fix and forced OTA update. Thank you!
ripelli part
Don't fear the ota update. There were no negative effects on my rom or kernel.
-cleanROM1.3
- 3.4.0 ElementalX1.1+
sfreemanoh said:
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
Click to expand...
Click to collapse
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
sambistt said:
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
Click to expand...
Click to collapse
I'm not sure what you're saying in reference to my earlier comment...are you saying something I said was incorrect?
ok, I got stock 4.4.4 but with root, bootloader is locked..
I wanna be able to receive the OTA update what do I need to do in order to be able to receive that?
or do I need to unlock the bootloader, install a recovery and flash lollipop threw that?
If you have stock system, kernel, and recovery, (no altered system files, either) being rooted won't keep you from getting the OTA. Locked/unlocked bootloader doesn't matter. If you rooted with SuperSu, just use its settings to uninstall root (you'll lose it anyway). However, I think you have to unlock bootloader to reroot, which, of course, will wipe your device. The OTA zip is now available for adb sideload if you're interested.
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Cobra11Murderer said:
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Click to expand...
Click to collapse
OTA won't wipe regardless of how you get it--over the air or sideloaded. Wug's will wipe unless you tell it not to (Options>Flash Stock>Enable no wipe). He also has the LRX21P build available. IMO, one way isn't better than another.
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
You probably already did all this, but you have to specifically send command to lock boot loader. I don't get how your device wasn't recognized through stock recovery but is on NRT, but it doesn't matter. Just use the kit which is what you probably did.
What you should do is back up what you need and want, then unlock the bootloader. You're not gonna get root without it on Android L since it requires a custom kernel.
Cobra11Murderer said:
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
Click to expand...
Click to collapse
Based on this, I assumed you unlocked your bootloader since first posting. NRT recognizes the device, right? Have you gotten it all sorted out yet.
idk why adb sideloading would kick the connection out, then the pc would say nexus 7 but wrong driver?, anyways i just went ahead and flashed the factory image using flash stock + unroot since I had it all backed up anyways, and that went great now I got lollipop on it, and should be able to root no probs now
thanks everyone, I hope i dont have a issue with adb again, im not sure if it was the samsung cord or what but it kept disconnecting at that part asking for a driver.. funny thing everything from bootloader, fastboot and all worked great with the driver that I installed using the steps in the toolkit..
Glad it's all good. Root with the toolkit. Just for the heck of it, you may want to try running CMD from wug's ADB folder. I've experienced just the opposite with older versions of the kit. NRT wouldn't recognize device. I'd go to CMD and device recognized. Return to NRT, all good again.
alrighty will do!, thanks for all your help