Related
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
don't use windows..
Ditto
dstenc said:
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
Click to expand...
Click to collapse
glen4cindy said:
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Click to expand...
Click to collapse
I was able to gain root back using the toolkit. I flashed stock rom image I believe the ROM from the factory then flashed back stock recovery. Went back in after I updated and re-rooted to flash the triangle away. Now I need to unroot and after speaking with Sprint Rep on phone and trying a few things they advised me to take it to store to let them try it. I believe ALL of my problems started when I tried to use Mobile Odin Pro to flash the latest update to LJC (should I have been on stock recovery?). It started to flash then stopped and went into CWM recovery which is the recovery that the toolkit flashed. I for some strange reason was going to flash the update from there except I didn't have it in the right place on my sd card (couldn't access it GOD I'm a Dumbass!). God help me cause I'm too stupid to even understand what side loading is let alone how to do it. If some kind soul would take pity on me and pm me I could get a handle on the differences between HTC and Samsung. Anyway need to unroot now. Oh I keep seeing in the flash counter saying 1 but I'm on stock rom with stock kernel and stock recovery how do I get it to zero. Using triangle away. Anyway to check counter with stock recovery?
OH yeah does anyone keep getting "Internal Error Code 1500" in addition to the hardware id is missing?
Thanks to everyone that takes time to help idiots like me. I promise I CAN learn.
Charles
chrisc627 said:
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
Click to expand...
Click to collapse
Thank you...Unlike user: dstenc, the above procedure fixed my issue. As has been the case many times, XDA helpful users to the rescue!
:laugh: :good:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Could you walk me through your fix?
dstenc said:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Click to expand...
Click to collapse
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Could you walk me through your fix?
Mods please delete double post sorry
ceabbott2 said:
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Click to expand...
Click to collapse
I don't remember link. I googled so you might try that way.
Just FYI, even with older drivers I have sporadic Hardware ID Missing error, but far too less than with the latest version.
I'm posting this to keep it to the top of this board.
This is my second Note 2 in 2 weeks. I returned the first one because it stated Hardware ID missing, so within my first 2 weeks Sprint gave me a new one thinking that it was my phone. While at the Sprint store, and not yet rooted, we installed the unit and removed the unit 15 times to see if we could get it to have the Missing Hardware ID to pop up, it DIDN'T pop up once, so I thought I was good to go.
I came home and did the common root method that uses Galaxy Note 2 Toolbox. I IMMEDIATELY started getting the Missing Hardware ID again.
So now that we have it localized, what could be missing or creating a problem from the root procedure from the Galaxy Note Toolbox 2???
What I find really strange is that many are not experiencing this problem or they are just living with it.
I even tried the USB Switcher that appeared to install and does switch between Mass Storage and MTP, but although my PC makes the upward noise that sounds like it is installing and recognizing the USB Mass Storage, it doesn't end up recognizing it. It was ZATTA's build but he said it didn't work for his Galaxy 3 or Note 2 either.
Will anyone find a cure????
This will be no fun to have to deal with for the next 2 years.
Chime in PLEASE!!!!!! Even if it's only to insult me, I don't care if you have a cure.
Regards
Dave
if you do Google search, it's a known issue. From what I read, it's a driver issue. Some have had luck using the older Samsung USB drivers. You have downloand them, and install, and have your PC completely disconnected from the internet before plugging in your GN2 after the install. Appaarently the drivers on Microsoft's servers are bad; may be the wrong device.
I've done this, and still have the issue. I just find I don't have plug and unplug the USB cable as much.
What I have seen, the PC does connect to the GN2. It just doesn't recognize it as a storage device. It wants to use it as a modem, probably from the tethering capabilities with a USB OTG cable.
It may not be so much that it's not wide spread, but more that not everyone uses the GN2 as storage device or connects it their PC.
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
knightfox said:
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
Click to expand...
Click to collapse
Yep I think you may be on to something. Because when I rooted I tried both TWRP and CWM and then I had to go back to stock to get to apply the LJC update. Ever since I have had the chameleon error and Handsfree activation issues. Oh my counter always says 1 and I can't remove it with triangle away. I think it says custom binary yes and the counter says 1. I am using a laptop with Windows 7 and it now recognizes the device just can't stop the errors on start up.
Charles
Sent from my SPH-L900 using xda premium
Samsungs older drivers: uploaded.net/file/hdh0f1xd
Q&A for [ROM][5.1] Candy 5 - Hercules [ALPHA]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1] Candy 5 - Hercules [ALPHA]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
hello there,
Has anyone tried to take a picture with flash on?
i'm using candy 5.0 and anh my phone will reboot immediately when ever i take picture with flash on...
chjcken12 said:
hello there,
Has anyone tried to take a picture with flash on?
i'm using candy 5.0 and anh my phone will reboot immediately when ever i take picture with flash on...
Click to expand...
Click to collapse
You are the first to report this issue.
The latest is Candy5 v2.1.0 in Post #2 (Android 5.1.1). Try the latest and clean flash. If it still does this, I need logcat logs showing the problem if I'm going to have any chance at fixing it. Paste a log on Pastebin.com and link it back here.
OK, I installed the last version (5.1.1 from 20150422) and everything seems to be working, at first boot I had no signal at all so I restarted my phone... and no signal.
Rebooted to recovery and installed Zero Gapps from slim, reboot system, no signal
The I attempted to add my google account and after conecting my phone to the wifi it got signal, went to APN config and my companies APN is there, Data seems to work OK, phone and messages works as well
Connect my phone to wifi seems to solve the problem
Thanks Dan!
NoSpamDan said:
You are the first to report this issue.
The latest is Candy5 v2.1.0 in Post #2 (Android 5.1.1). Try the latest and clean flash. If it still does this, I need logcat logs showing the problem if I'm going to have any chance at fixing it. Paste a log on Pastebin.com and link it back here.
Click to expand...
Click to collapse
thanks for always support your user
i tried a third-party camera app, and that camera app work fine with flash on, while stock camera still has that problem,
now i will try to update to candy 5.1
data not working.
I like the rom but data not stable. I did a clean install. If wifi turned off I lose mobile. but am looking forward to this rom i love my s2
same here dont have wifi
same here dont have wifi
hillinsf said:
I like the rom but data not stable. I did a clean install. If wifi turned off I lose mobile. but am looking forward to this rom i love my s2
Click to expand...
Click to collapse
mickeymichael said:
same here dont have wifi
Click to expand...
Click to collapse
This is an issue affecting many devices on LP5.1. I believe it is upstream and will get fixed in due time...
hello NoSpam Dan
i connect my phone to PC and choose Mass storage but only my 2GB SD card showed up in My computer window, neither internal storage!
Can you guide me to make the internal storage connect to my PC?
sorry for my bad english, hope you understand what i say
USB ?
I did clean install with new build , the data is much better but... when i try to enable usb it wont give me a menu when i enable it in developer then go to storage and press the settings it shows usb connection and i click it and no menu , the rom is great but really need the usb to work for daily driver , almost there
chjcken12 said:
hello NoSpam Dan
i connect my phone to PC and choose Mass storage but only my 2GB SD card showed up in My computer window, neither internal storage!
Can you guide me to make the internal storage connect to my PC?
sorry for my bad english, hope you understand what i say
Click to expand...
Click to collapse
Can you mount storage in recovery mode?
Check your Device Manager carefully for Nexus or ADB devices (if you're on Windows). If you find something like this, try to change it to a USB Storage Device.
NoSpamDan said:
Can you mount storage in recovery mode?
Check your Device Manager carefully for Nexus or ADB devices (if you're on Windows). If you find something like this, try to change it to a USB Storage Device.
Click to expand...
Click to collapse
i cant find anything like you said, it just an Android CompositeADB Interface i installed recently for android app debugging..
can you tell me more detail about this issue
chjcken12 said:
i cant find anything like you said, it just an Android CompositeADB Interface i installed recently for android app debugging..
can you tell me more detail about this issue
Click to expand...
Click to collapse
Sometimes you can right click that ADB interface and choose "Update driver". Then select manual and choose USB Mass Storage Device.
Depends on the drivers you are using. I haven't changed the connection methods, but that doesn't mean they haven't changed somewhere in the upstream code...
Nice rom but vibrating and does not turn on after restart
I installed in on cwm 6.0.2 and worked eith bugless and smooth i inserted sim it asked to restart and i restart and then it turn on at samsung and then vibrates every second then reboots every time.I don't think that at time of restart my battery was only 10% at the time of restart.Help me for any answer but tried to enter cwm but failed power on key gets automatically pressed
Zubair66 said:
I installed in on cwm 6.0.2 and worked eith bugless and smooth i inserted sim it asked to restart and i restart and then it turn on at samsung and then vibrates every second then reboots every time.I don't think that at time of restart my battery was only 10% at the time of restart.Help me for any answer but tried to enter cwm but failed power on key gets automatically pressed
Click to expand...
Click to collapse
You seem to have a stuck power button. @vincom has a 1-Stop sticky thread that is linked in my signature. Although that's for the Skyrocket, you might find some of it useful for the Hercules as well.
Does not turn on on vibrates and auto restart
Rom successfully installed and eorks later i put sim and restart and phone .It turn on automatically and after samsung logo it starts vibrating continously then restart but when i tries to enter recovery mode it automatically restarts
Zubair66 said:
Rom successfully installed and eorks later i put sim and restart and phone .It turn on automatically and after samsung logo it starts vibrating continously then restart but when i tries to enter recovery mode it automatically restarts
Click to expand...
Click to collapse
You need to give more details please.
- What recovery are you using?
- What GApps package?
- Did you repartition your device?
Full wipe, and try flashing only the ROM, without restoring any backup data, and see how it goes.
Or as I said, stuck power button.
how to root galaxy s2 t mobile version running on candy 5.1 lollipop
i lost my root access after i installed lollipop 5.1 custom rom. pls how do i reroot it
desmond4life said:
i lost my root access after i installed lollipop 5.1 custom rom. pls how do i reroot it
Click to expand...
Click to collapse
This ROM? Root is built in.
Try a full wipe and reflashing.
MY galaxy s2 t mobile version not charging after flashing candy 5 rom
i was running android 4.0.4ics stock and it was charging fine, but recently i flashed candy5 custom rom and my galaxy s2 is now on android 5.1 lollipop, but i noticed that my phone is no longer charging. once i plug in my charger, it will display charging for some few seconds and then it will stop and remain that way. even when i switch off, and then plug the charger, the battery icon will be counting without actualy charging. but if i restore my android 4.0 stock backup, it will be charging fine. pls i need help.
Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.
I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.
Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.
Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone
Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.
If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?
famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.