Related
My friend has the samsung intercept and I was going to help him root it. I have tried Z4root and gingerbreak but they didn't work.
Does anyone have a site on how to root? Or instructions?
I am a very experienced android user and I am very comfortable with ADB if it is needed.
Anybody know?
Let's try again. Does anyone here know?
S.D.X. Everything you need to know for the intercept
Yes I found that method as well. We tried that about twenty times along with another 1 click at xda, z4, and gingerbreak. Is there an Adb method? Also, would rageagainstthecage work?
Jmoney47 said:
Yes I found that method as well. We tried that about twenty times along with another 1 click at xda, z4, and gingerbreak. Is there an Adb method? Also, would rageagainstthecage work?
Click to expand...
Click to collapse
S.D.X. is a website S.D.X. developers They have several guides to rooting.I rooted mine with a programed called sw updater with my pc but now ther are easier ways.
Ok thank you I will check it out
You're going to need to run one (or several) of the root exploits (until they 'take') and then edit some files manually via adb to make it permanent. See the SDX Developers website as previously noted.
It won't let me post a link but Google this...
how-to-install-custom-kernelrom-on-your-intercept-using-cm01-recovery
I did it with SWUpgrade Tool, but...
1) Even though I could connect and swap files between my phone and my computer over USB, SWUpgrade for some reason would not recognize my USB connection on Windows XP SP 3. This page along with the Samsung driver link on the same page saved my ass...
Google this - Troubleshoot driver error June Fabrics android
2) With the SWUpgrade you have to be really quick and unplug the USB and take out the battery when he says to, or you will not get the custom recovery installed. It took me about 4 tries before I was able to get the custom recovery in my phone.
I previously did the rageagainstthecage method, and while it worked, at one point I stupidly took out the battery when it froze before I had put in a custom recovery and done a backup and I very nearly bricked my phone. It would not bootup after that no matter what. Fortunately I was able to boot into the Virgin Mobile recovery and start from scratch wiping and resetting my phone, but I had to re-download all my apps from the Market all over again which fortunately the Market kept a record of.
I used the first link for the kernel and I am very happy. Just take it slow, be careful, and follow the instructions exactly.
Rooting using ADB Tool Manual Method
Please see my post in the following thread:
http://forum.xda-developers.com/showthread.php?p=13849534#post13849534
Ok guys thanks for the advice however I have been having one problem:
I cannot seem to get the drivers installed successfully on my computer. It is windows vista x86. I have tried the easytether drivers and the samsung drivers but for some reason they don't work. Any ideas?
My Rom version is 4.2.2. And I have upgraded the toolkit to v4.3.9, the latest one.
I was able to unlock the bootloader. However, I couldn't root my Nexus 7.
Nexus 7 gets stuck at "booting the downloaded image", while the toolkit was showing "Waiting for adb Mode".
Luckily, the Nexus 7 wasn't bricked though. I was able to boot into the official image, by holding the power button for a long time.
I tried many times with different options in the Toolkit. Still got no luck. Many suggestions are welcome. Thanks.
Dont waste any more time with toolkits. take 5 minutes to learn how to do it manually
Pirateghost said:
Dont waste any more time with toolkits. take 5 minutes to learn how to do it manually
Click to expand...
Click to collapse
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.
ejj3 said:
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.
Click to expand...
Click to collapse
Now that your N7 is already unlocked, all you need is a recovery... Download this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-grouper.img
Also make sure that you have the android sdk installed. It's easy enough to find.
Open the platform-tools folder, hold shift and right click; then choose "open command window here"
Make sure that your N7 is rebooted into the bootloader and run the command "fastboot flash recovery recoveryname.img" replacing recoveryname with the name of the recovery.
After that, follow the instructions to flash any custom rom or supersu from recovery... I'm sure that there are more detailed instructions elsewhere, but that's all you really need at the moment...
ejj3 said:
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=2150661
And you DONT need windows to use fast boot or adb
Sent from my Galaxy Nexus
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
Nexus devices are hard to brick. Just to be on the safe side, just follow the videos, follow instructions and you'll be fine.
"Riddle me this, Riddle me that."
It's importanto to be sure that alla drivers are working correctly and if you are able root manually from the command line ( it's easy ).I'm going to root too,and I'm trying to understand if my drivers are working but with no results
Federico_96 said:
It's importanto to be sure that alla drivers are working correctly and if you are able root manually from the command line ( it's easy ).I'm going to root too,and I'm trying to understand if my drivers are working but with no results
Click to expand...
Click to collapse
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
I used wugfresh's toolkit for the n7 and the n4 with absolutely no trouble. Other than not letting the drivers install automatically drivers. Once I let them go on auto it worked like a charm windows xp.
Sent from my Nexus 4 using Tapatalk 4 Beta
Th3RiddL3r said:
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
Is there a way to check if adb has been installed correctly? I'm using wugfresh toolkit,i already made the drivers test and it went fine,but i don't know if adb has been included in this test too,and I noticed that even if the drivers test said that all is ok,in my device manager i still see a yellow exclamation mark near to the MTP device...another question,if i plug my device with usb debugging on, should i be able to transfer files in the memory? beacuse i can't see my device
With a command prompt i moved in the adb directory and typed adb devices,it said daemon not running,daemon started running successfully,and it showed a serial number and "offline", is this correct?
dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
download the 4.2.2 factory images and keep them handy for emergencies, setup and learn fastboot, and never flash anything for another device/not meant for the N4. if you do this, you will never brick it.
Federico_96 said:
Is there a way to check if adb has been installed correctly? I'm using wugfresh toolkit,i already made the drivers test and it went fine,but i don't know if adb has been included in this test too,and I noticed that even if the drivers test said that all is ok,in my device manager i still see a yellow exclamation mark near to the MTP device...another question,if i plug my device with usb debugging on, should i be able to transfer files in the memory? beacuse i can't see my device
With a command prompt i moved in the adb directory and typed adb devices,it said daemon not running,daemon started running successfully,and it showed a serial number and "offline", is this correct?
Click to expand...
Click to collapse
You need to update the adb driver if it's showing offline. Try searching the new updated adb driver in google. I think it's also here in the N4 forums, not quite sure where.
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Th3RiddL3r said:
You need to update the adb driver if it's showing offline. Try searching the new updated adb driver in google. I think it's also here in the N4 forums, not quite sure where.
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
OK so now typing adb devices i get a serial number and "device", i suppose that now adb is working,and now i installed mtp drivers using this guide
Th3RiddL3r said:
Just install the WUG's nexus root kit, all needed drivers are included there. Or if you want to do it manually, download the adb and fastboot drivers.
Or you can try this: http://forum.xda-developers.com/showthread.php?p=42878983
"Riddle me this, Riddle me that. Smash an iPhone with a baseball BAT!"
Click to expand...
Click to collapse
what's the difference between auto root and manual? which is better?
Questions: 1.Difference between manually rooting and auto-rooting
2. This thing say we can root without unlocking bootloader, is that really legit and if so will our stuff be wiped or no?
3.How to back up my phone? Which program to use?
4.Long does it take to root?
dreseansr said:
what's the difference between auto root and manual? which is better?
Click to expand...
Click to collapse
1) Download either Clockwordmod http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img or TWRP http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img recovery image and move the file to the folder that contains adb and fastboot.
2) Open a command prompt in the folder that contains adb and fastboot type fastboot oem unlock and install a custom recovery by typing fastboot flash recovery recovery-image-name.img.
3) Boot into recovery and install SuperSU.zip downloaded from http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip.
4) Reboot your phone, search the Play Store for BusyBox, and install BusyBox.
Now your Nexus 4 is fully rooted. If you intend to flash a custom ROM, superuser and busybox will be included in the ROM.
BobWalker said:
1) Download either Clockwordmod http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-mako.img or TWRP http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img recovery image and move the file to the folder that contains adb and fastboot.
2) Open a command prompt in the folder that contains adb and fastboot type fastboot oem unlock and install a custom recovery by typing fastboot flash recovery recovery-image-name.img.
3) Boot into recovery and install SuperSU.zip downloaded from http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip.
4) Reboot your phone, search the Play Store for BusyBox, and install BusyBox.
Now your Nexus 4 is fully rooted. If you intend to flash a custom ROM, superuser and busybox will be included in the ROM.
Click to expand...
Click to collapse
Wait I'm confused, Clockwordmod is to backup my stuff?
dreseansr said:
Wait I'm confused, Clockwordmod is to backup my stuff?
Click to expand...
Click to collapse
Clockworkmod and TWRP are recovery software. Either can be used to perform nandroid backups of all system files, applications and data, and boot image installed on the phone at the time of the backup. Recovery may also used to flash custom ROMs or kernels and to install some software directly from a zip file and to wipe cache, Dalvik cache, and system before flashing a new ROM.
At a minimum, you should perform a nandroid backup of your phone when you have it rooted and have all essential programs installed so you have an image of your phone in a working state as insurance in case you do something wrong and need to restore your phone to normal operation.
BobWalker said:
Clockworkmod and TWRP are recovery software. Either can be used to perform nandroid backups of all system files, applications and data, and boot image installed on the phone at the time of the backup. Recovery may also used to flash custom ROMs or kernels and to install some software directly from a zip file and to wipe cache, Dalvik cache, and system before flashing a new ROM.
At a minimum, you should perform a nandroid backup of your phone when you have it rooted and have all essential programs installed so you have an image of your phone in a working state as insurance in case you do something wrong and need to restore your phone to normal operation.
Click to expand...
Click to collapse
hm ok so is there any video showing the steps of how to back up my phone or using this programs?
You need to do more research on your own all this info u need is on this site and on YouTube please read for yourself
Sent from my Nexus 4 using Tapatalk 4 Beta
dreseansr said:
hm ok so is there any video showing the steps of how to back up my phone or using this programs?
Click to expand...
Click to collapse
You Tube videos for using TWRP to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=laBKgRCpMeI and at http://www.youtube.com/watch?v=bGgTkzLHzHo respectively.
You Tube videos for using Clockworkmod to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=36cihz4l-vk and at http://www.youtube.com/watch?v=Gvi0cbMz1V8 respectively.
dreseansr said:
Okay today I'm finally going to root my phone but I would like to know how people brick their phone so I don't make that mistake and do it.. I've read so many things and watched so many videos and I think I understand how to do it but before I take the chance I want to know how people brick their phone or mess it up so if someone could explain that to me, i'd be nice
Click to expand...
Click to collapse
Well I think there is an forum rule that says we're not supposed to discuss about things such as how to brick your phone. And the most, if not all, of the bricks on the Nexus 4 are recoverable anyways.
That being said, before you flash anything, especially kernel or bootloader, be absolutely sure the file is made for your device
Sent from my Nexus 4 using xda app-developers app
nelsonator1982 said:
You need to do more research on your own all this info u need is on this site and on YouTube please read for yourself
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If you have read the thread you will see that i've done that already but since he/she is informing me on a program that they used, i am simply asking for a video that showed them how to do it so i know everything is legit.
BobWalker said:
You Tube videos for using TWRP to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=laBKgRCpMeI and at http://www.youtube.com/watch?v=bGgTkzLHzHo respectively.
You Tube videos for using Clockworkmod to perform a nandroid backup and restore and flashing a custom ROM can be found at http://www.youtube.com/watch?v=36cihz4l-vk and at http://www.youtube.com/watch?v=Gvi0cbMz1V8 respectively.
Click to expand...
Click to collapse
Thank you
Does anyone know whether the GPE can be rooted yet? I got mine yesterday and would like to transfer my app data from the LGE to the GPE if possible. I'd also like to use some root only apps like Xposed so that I can force Immersive Mode for more apps (mostly games and book/magazine readers).
UPDATE: I thought I'd post instructions on how to do it here. Basically just follow the Nexus 5 guide posted here:
http://www.droid-life.com/2013/11/04...t-the-nexus-5/
but in step 6 (flashing an alternative recovery), use this TWRP recovery image:
http://forum.xda-developers.com/showthread.php?t=2565431
Hopefully that helps others who are wanting to root their G Pad GPEs!
SCWells72 said:
Does anyone know whether the GPE can be rooted yet? I got mine yesterday and would like to transfer my app data from the LGE to the GPE if possible. I'd also like to use some root only apps like Xposed so that I can force Immersive Mode for more apps (mostly games and book/magazine readers).
Click to expand...
Click to collapse
yes it can be, the bootloader unlock is the same as it's always been for nexus devices, there is a custom recovery for it already.
1. download recovery and superSU zip
2. unlock bootloader
3. flash the recovery
4. boot into recovery
5. flash the superSU.zip
6. profit
thoughtlesskyle said:
yes it can be, the bootloader unlock is the same as it's always been for nexus devices, there is a custom recovery for it already.
1. download recovery and superSU zip
2. unlock bootloader
3. flash the recovery
4. boot into recovery
5. flash the superSU.zip
6. profit
Click to expand...
Click to collapse
Thanks! I've never had a Nexus or GPE device before, so I'm more accustomed to the various non-standard ways to root devices and assumed the G Pad GPE might need something similar.
I assume this is the recovery you're referencing?
http://forum.xda-developers.com/showthread.php?p=48479203
I tried to use the minimal adb included with dalingrin's simple root for the LGE but it says "error: device not found". Can you provide a pointer to the correct drivers for adb so I can perform steps 2-3?
Thanks again!
SCWells72 said:
Thanks! I've never had a Nexus or GPE device before, so I'm more accustomed to the various non-standard ways to root devices and assumed the G Pad GPE might need something similar.
I assume this is the recovery you're referencing?
http://forum.xda-developers.com/showthread.php?p=48479203
I tried to use the minimal adb included with dalingrin's simple root for the LGE but it says "error: device not found". Can you provide a pointer to the correct drivers for adb so I can perform steps 2-3?
Thanks again!
Click to expand...
Click to collapse
i just downloaded the sdk ages ago and have been using that, you'll also need the fastboot drivers instead of just ADB
in fact if you watch a tutorial about how to root a nexus 5 it will be closer than any of the stuff posted right now
Sorry for being a bit dense here, but I'm still spinning my wheels a bit on this. I downloaded the latest ADK and had it install the Google USB Driver. I have USB Debugging enabled on the GPE tablet. Unfortunately neither "adb shell" nor "fastboot devices" recognize the device. Any tips on what important step I'm missing that will allow me to get past this first hurdle?
UPDATE (FIXED): Never mind. I had to update the device with the driver first as per this link: http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
SCWells72 said:
Sorry for being a bit dense here, but I'm still spinning my wheels a bit on this. I downloaded the latest ADK and had it install the Google USB Driver. I have USB Debugging enabled on the GPE tablet. Unfortunately neither "adb shell" nor "fastboot devices" recognize the device. Any tips on what important step I'm missing that will allow me to get past this first hurdle?
UPDATE (FIXED): Never mind. I had to update the device with the driver first as per this link: http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
Click to expand...
Click to collapse
I can seem to find the drivers for our tablet! I can't find the link to download them. Where did you find them?
Thanks!
joaquinla1 said:
I can seem to find the drivers for our tablet! I can't find the link to download them. Where did you find them?
Thanks!
Click to expand...
Click to collapse
Just install the Android Development Kit and then have it install the USB driver. Don't forget to use Windows Device Manager (if using Windows) to update the driver for the G Pad while it's plugged in.
SCWells72 said:
Just install the Android Development Kit and then have it install the USB driver. Don't forget to use Windows Device Manager (if using Windows) to update the driver for the G Pad while it's plugged in.
Click to expand...
Click to collapse
Thanks!
I tried using the WDM before, but it can't find the drivers online. Should i just install the google drivers from the adk?
Update: I installed the google usb drivers with the ADK and still no luck!
joaquinla1 said:
Thanks!
I tried using the WDM before, but it can't find the drivers online. Should i just install the google drivers from the adk?
Update: I installed the google usb drivers with the ADK and still no luck!
Click to expand...
Click to collapse
Yes, install "Google USB Driver" from the ADK, then open WDM and find your tablet which should say something like "Unknown Device" (can't remember the exact term), right-click and say "Update Driver...", and navigate to the driver that the ADK downloaded for you. Once that's updated, you'll be able to use adb and fastboot.
The links I've posted don't seem to be working properly, but if you Google "root nexus 5", go to the result on Droid Life called "How to: Root the Nexus 5" and follow the linked instructions on how to unlock the boot loader, then the instructions on that page on how to root the device. Like I said, the only difference is that you'll use the TWRP image for the G Tab GPE from this forum instead of the one referenced there.
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
ImjuzCY said:
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
Click to expand...
Click to collapse
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Zaphodspeaks said:
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Click to expand...
Click to collapse
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
ImjuzCY said:
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
Click to expand...
Click to collapse
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Zaphodspeaks said:
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Click to expand...
Click to collapse
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
ImjuzCY said:
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
Click to expand...
Click to collapse
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Zaphodspeaks said:
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Click to expand...
Click to collapse
Luckily i was using stock kernel. Ive disabled root beforehand and the problems i faced was all on the pc side. Evrything should be easy if my pc doesnt show so much problems. And i like to take challenges so i chose to sideload haha