Related
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.
Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)
For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.
Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.
demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks
Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
zaft1 said:
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
Click to expand...
Click to collapse
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
mnb91 said:
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
Click to expand...
Click to collapse
Hey sorry, I haven't been on the site for a couple days.
I used the flashtool to go back to stock. Had to enter download mode and work from there. The big issue I was having was a driver issue. Uninstalled every driver related to android and then reinstalled after a restart and that did the trick. For some reason android phones are giving me a lot of driver issues on windows 8.1
follow these steps here but make sure you read a chunk of the thread as the steps in the main post are not complete
http://forum.xda-developers.com/showthread.php?t=2432476
see post 4
see post 4
see post 4
d802 int
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!
kye1987 said:
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!
Click to expand...
Click to collapse
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for
XxZombiePikachu said:
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for
Click to expand...
Click to collapse
Cheers I'll see if the supermarket has them at a half reasonable price, otherwise ebay has them for £1 delivered and I'll have to wait. Thanks for the reply and confirmation that would work though.
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