Related
Hey
So I tried to root my SGN using Chainfires' thread, my phone got unlocked but I couldn't boot it so I got stuck with a black screen with the Google logo and an unlocked lock-logo. Now I have unrooted it and reset it back to stock using droid-life.coms' "How to", but when I try to boot now I only get the balck screen with Google-logo, and no lock-logo.
Do anyone know how I can fix this? Thanks for the help!
When I try to unroot, re-lock and set to factory state I get an error, probably because my driver isn't working, the 'SAMSUNG Mobile MTP Device'..
I tried the PDANet drivers, Samsungs' drivers and yeah.. I also downloaded the "Naked drivers" wich I found on another thread on XDA.
I really need help
How far into rooting it did you get? A link to the instructions you followed, and a detailed account of what happened and what you saw will help someone else help you.
as far as drivers go, if you installed a bunch drivers from different sources, uninstall them all, reboot, install the drivers from Samsung. Also remember that when you plug your phone in and the drivers start to autoinstall, that process can take awhile and you have to be sure it completed before trying to continue. It should show a status you can open in the system tray
Galaxy Nexus Bugless Beast 4.0.3 cdma
Also, be sure to scour all the sticky posts in these galaxy nexus forums, and also all the replies in the thread you were following. Chances are someone has explained an 'all else has failed blow it away' recovery step by step. Follow it closely!
Galaxy Nexus Bugless Beast 4.0.3 cdma
eovi said:
When I try to unroot, re-lock and set to factory state I get an error, probably because my driver isn't working, the 'SAMSUNG Mobile MTP Device'..
I tried the PDANet drivers, Samsungs' drivers and yeah.. I also downloaded the "Naked drivers" wich I found on another thread on XDA.
I really need help
Click to expand...
Click to collapse
Have you tried downloading the Google USB Driver package from Android SDK? Its under Extras. If my memory serves me right, our phones actually require two drivers (one for adb and fastboot modes, and one for normal operation). Also, when you are restoring your phone are you sure its the right version? Like you're not installing an LTE ROM on a GSM device?
Sent from my Galaxy Nexus using xda premium
@cancerouspete
I got the rooting all done until the phone was going to boot, then I got stuck at the black screen with the Google-logo. Unfortunately I can't post links, but I used Chainfires' ODIN method.
I can try to uninstall the drivers and only try Samsung drivers.
@nbeebe24
Yes, I downloaded the Android SDK drivers before I started the rooting. I am not 100% sure that it is the right version. I got the GSM, do you have a nice guide or 'How To' for restoring GSM?
Thanks for the help so far!
Let's take it form the beginning. First I followed the steps in Chainfires' thread about CF-Root for SGN (Galaxy Nexus). I used the ODIN-way to flash my phone. I followed the instructions to the letter and when I tried to boot the phone I only got a black screen with a white Google-logo in the middle and an unlocked lock-logo. Nothing else happens than this. My phone is GSM-version and is bought in Norway. One of the issues is that I'm not 100% sure of what build-number my phone is.. anyone know how I can find this out?
When I tried to fix this problem myself I tried to unroot, lock and reset the phone, and then unlock/root again with another version, the same happend (with the black screen and google logo + lock-logo). It doesn't work to unroot, lock and reset, if I do this I only get a balck screen with google-logo, but no lock-logo
I really hope someone can help me with this problem! All help and tips is appreciated!
Fixed!
I've finally fixed this problem. Can tell you how I fixed it if someone else need help.
I uninstalled the PDANet drivers, Samsung drivers and uninstalled the SDK-drivers. Then I reinnstalled the SDK driver and followed this to restore the phone to stock:
http://forum.xda-developers.com/showthread.php?t=1366806
So I guess the problem was that I used the wrong version or for another build when I CF-Rooted. I have ITL41D build.
Thanks for the help and I hope this can help other with the same issue!
Love my GNex, it's a beast! Upgraded from a SGS, this was a beast when it first came out but the electronic power are growing fast! Go Samsung and Google! Love ICS
Hello.
This is what I am dealing with.I am enabling USB debugging through Settings/Developer Options and:
The bean face appears instantly in the notification bar but doesn't remain there.
When I go again inside the developer options the USB debugging is unticked as if it was disabled by itself.
As a result of this no ADB mode is available through GN toolkit.For your interest I remember this was working fine till maybe yesterday.
Only major change to the phone was installing some apps like Avast mobile security, pocketcloud, titanium backup and clockwork mod recovery (through GN toolkit).
The phone is GN GSM version, unlocked, rooted and on 4.1.1 stock for over a month now wit the help of Galaxy Nexus Toolkit v.7.8.0.
Flasboot mode works fine.
ADB driver loads fine in windows (7 x64) and the device is recognized in device manager when it is plugged in.
Tried different USB ports, other computer, no difference.
Any help on getting USB debugging back would be greatly appreciated.
Thank you in advance.
Anyone having an idea?
ok, i get it, you used a toolkit.
that said, uninstall those apps, reinstall one by one till you find the culprit?
sent from my i9250
bk201doesntexist said:
ok, i get it, you used a toolkit.
that said, uninstall those apps, reinstall one by one till you find the culprit?
sent from my i9250
Click to expand...
Click to collapse
Hello bk201doesntexist.
I already uninstalled all those apps but that didn't help (checked after reboot).
I forgot to mention one more thing from "yesterday's messing around with my GN" and that is that through the toolkit I installed the CWM Recovery Touch.Then I got into Android ran Flash CWM Recovery from ROM Manager, in the hope any update was avail.I then reboot to test the "new" CWM recovery only to find out the touch interaction was gone.
One more strange thing happening is that 3G data connection opens automatically on boot despite being set to OFF.That wasn't happening as well.
Any ideas or possible causes? Do you think there is anything else I can do?
Thank you very much for stopping by.
PS - Is it bad I used a toolkit?
Ok in my case it was Avast Antitheft module the deny USB debugging setting causing the issue.Now USB debugging is back.
Hope someone else finds this helpful.
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
Hi all. I'm posting here because after countless (2) hours of searching online I haven't been able to find a proper solution for a problem. I'm hoping that you all can help me with this one.
I've been using the LG g3 for the past year and everything has been great. But since my screen got smashed I've had to replace it with a newer one. I got this last Thursday.
I've been sticking with stock because I'm quite fond of the stock marshmallow. But since I'm a tinkerer I can't help myself. So after I updated (yesterday) I was going to attempt to root and flash a shiny new rom. Unfortunately, I haven't been able to get that far, as my phone can no longer be recognized by my computer.
I will put it in, and it will pop up with "USB Device not recognized". Under device managers it merely shows up as "unknown usb device". So I uninstalled my LG drivers (which are normally installed once you plug in the phone, but I digress. It did all of this before the 6.0 update) and it will attempt to install usb drivers but fail almost immediately and say it experienced an "unknown error", very helpfully reminding me to try and unplug/plug the device or factory reset.
Factory reset is very difficult for me right now as I have just finally gotten the phone tweaked to my liking. I really don't want to have to re-download everything. I have tried almost every workarounds I could find on the Internet but I keep running in circles. I've downloaded several different drivers for my phone and none of them work. I'm really at a loss.
I'm assuming that it must be the marshmallow update, as I haven't rooted or installed cfw as of yet. And I can plug someone else's phone in and it will install the drivers in a heartbeat. I can charge my phone but it won't give me options for MTP/PTP/Charge mode at all.
Anyways that's about all I can ask at the moment. I just hope someone here has experienced this and knows what to do.
Okay, I have now tried factory resetting my phone and it still won't work. It's the 6.0 update that's causing this. I'm at a loss, either I have to wait for google to hopefully patch this or I have to take back my new phone and exchange it for a new one.
You should be aware that the correct model number for a Canadian G3 from Koodo is D852, not D820 as you mentioned.
Before taking back your phone, try to see if your phone is recognized with a different USB cable (OEM one preferred), plugged in a different USB port of your computer, or, if possible on a friend's Windows 10 or Windows 8 computer, just in case different drivers might recognize your phone.
Your suspicion (that the OTA update to MM caused this) is not well supported by the reality: the OTA update was quite uneventful for thousands of other Canadian G3 phones; we should have heard more complaints if the OTA update were botched by Koodo or Telus.
I've been trying to figure this out for a while, and I have made some headway but I think I need to make custom build. If anyone could point me in a direction, it would be super helpful. I have a few ELO ESY15i1 android computers. They are EOL now, and only supported up to kitkat. ELO does not release their kernel source, but I do have their peripherals.
This is how far I have got with this thing, and what I was able to do/determine.
After a bunch of digging, I'm pretty sure that this thing is just a modified S4 i9505. Hardware specs seem to match, outside of the CPU only being 1.7 instead of 1.9ghz. I'm *assuming* that they have down clocked it maybe? The first unit I was working with, apparently had a bricked recovery (had bough it 2nd hand). I was able to boot it into TWRP using the jfltexx image, but I would get no picture. I know it was booted because I could access TWRP via cmd, and it was giving me responses back.
I was able to root it in a very round about way. Since I do not have any volume buttons, I'm limited to adb etc. I was able to root it with iRoot, convert that to supersu, and eventually get flashfire to install. I could finally access almost everything I needed. At some point, I got it stuck in a mode where "QHUSB_DLOAD" was shown to me, with a folder called "image" which I took a copy of. Any google results with that, was just people who had bricked their device, I was able to boot in and out of this, so I'm not sure what was going on or broken.
Here is what the device props listed out: hXXps://pastebin.XXX/FtgQ0DUE
This is the mobilodin report: hXXps://pastebin.XXX/BZrDAFg4
Finally, the "image" I copied: hXXps://anonfiles.XXX/lcQ7RfJ8o0/ESY15i1-image_rar
(sorry can't post links)
The first unit I was working on, I gave to a buddy to mess around with. The 2nd one I have, I have now bricked and it is officially stuck in the "QHUSB_DLOAD" mode. I made a poor choice, and modified the i9505 "updater-script" in lineage-17.1-20200723-nightly-jfltexx-signed to include my "msm8960" device. I flashed it via FlashFire which did go through, just bricked me in the process.
I had a samsung download jig, but I can't find it anywhere, so I have a new one on order. I'm too lazy to cut up a micro usb plug and make one. I have yet to get odin to recognize it at all, or get it into download mode. When I try over adb, it will reboot, try to go in some mode, then reboot again back to the rom.
Any input / help would be greatly appreciated. These machines are super cheap on ebay, the only problem is being stuck on kitkat. I can think of loads of things to use these for, doesn't look like anyone has tried to do anything with them. From all my searching I just found one guy who was trying to root one, and that was about it.
Hi,
I have one 22 inch unit, which I'd like to use with monitoring system and some else, but I need android version with multi windows support, so I'd like to ask you if you succeed with installing new ROM ?
Thanks in advance for reply
Maciek
Well, I've been dinking around with it again, I think I have the HW figured out. I'm pretty sure it's an LG Optimus G, LGE970 is what I'm trying.
I was able to take the stock "ATT-Stock-E97020j" non KDZ zip, pull the boot.img off of it, and flash that.
Now when I connect to my computer, I'm getting LGE Androidnet for Diagnostics, and LGE Androidnet USB serial, as 2 devices.
Just keeps hanging right away when I try and flash the KDZ.