I'm currently on a custom rom trying to install a stock rom to snag the 4.2.2 OTA or another custom rom with 4.2.2 already. I've installed plenty of custom roms before, however this time I can not get my phone to be detected by Hasoons tool kit, or Windycity's toolkit this time (Needed to flash boot image?). Both say the device isn't found (my computer detects it just fine). USB debugging is enabled and I've deleted all USB drivers related to my phone and the ADB drivers, followed by reinstalling the needed files again. Is there anything else I can do to get my phone to be detected to install 4.2.2? Any and all help is appreciated, thanks!
Related
Ugh, totally my fault for not thinking this through.
Had downloaded the Paranoid Android ROM, a newer version from what I had, as I had installed it incorrectly.
So I thought, no worries, I'll just reinstall the ROM.
Booted into recovery mode, did a full wipe and then tried to install the new rom, only I couldn't find it anywhere...
Thinking I'll restart the phone and figure it out from there, but of course it doesn't go past the loading screen.
I can boot into download mode, but on my PC if I boot Odin, it doesn't recognize the phone and I get no yellow colour.
Pretty sure my internal SD card still has one or two custom roms on it, but without booting into recovery mode, I can't do much.
Odin doesn't recognize my phone. I installed the drivers from the samsung website, but it is not reading the phone in download mode.
Now I am unsure if there's another driver I need to install, i.e. a USB driver, seeing as this is a brand new pc, but other than that, I'm stuck.
Any ideas are greatly appreciated!
Download galaxy s3 toolkit from original android development section,install it and agree when asked to install drivers , reboot Pc and cross fingers for your Pc to detect your phone in download mode then just flash stock ROM
Sent from the grey stuff inside my skull
If you have a custom recovery (CWM or TWRP), you can use an OTG cable to connect a USB stick to your phone (which will be discovered by CWM, haven't tried TWRP) and install a new ROM with gapps from it...
Of course if you want to install stock, you have to stick with Odin.
Hope it helps
Hi folks,
I previously managed to get Cyanagenmod installed on my HTC One X but since made a mess of it trying to get a stock ROM on there (to unlock my SIM). I have since given up on getting a stock ROM back on there and am now trying to get Cyanogenmod back on there, but I have hit some problems.
I have CWM on there and my PC can see the phone in Fastboot, but not via ADB (which I am trying to use to 'push' the ROM on there so I can install it). My PC (Win 8.1) is giving me a "device descriptor request failed" when connecting to USB when on the boot menu, and is showing up just as "One" in device manager when I load CWM. However neither of these situations are allowing my computer or ADB to recognise the SD card.
I have tried 'mounting' it in CWM, updating drivers through device manager, installing Sync (and uninstalling/reinstalling it), installing HTCDriver_4.10.0.001.msi all to no avail.
Does anyone have any advice to get my PC to recognise my phone or otherwise get a customer ROM installed (if there is another way.)
Thanks in advance all.
Hey, I am new here so sorry if I'm posting in wrong board.
I rooted my P70 a while ago and everything was fine. Now I decided that I want to flash 5.1.1 on it. I proceeded to flash TWRP.
I tried it with SP flash on pc, I checked that my scatter file and recovery.img was correct. I opened the scatter file in SP, connected my phone and clicked download, but nothing happened. Only the phone started charging, I have enabled USB Debugging and developer mode. The bootloader was still the stock one. Why?
Next thing I tried is to put the recovery.img on SD card and downloading Uncletools, I flashed it and it asked me if I want to reboot in bootloader, so I did, but it was still the stock bootloader.
What am I doing wrong? Thanks a lot for any response.
Anyone got any idea?
Click download and conecting usb cable to hh
Hey,
I have the same issue. The phone is rooted but the SP flash tool will not do anything. I've read that it's because the USB drivers are incorrect. However I am unable to install the drivers as the phone does not show up under other devices but rather under portable devices. I tried to install the android sdk and use those drivers or ones I found on the web but none of them will take. I found the ADB device signed driver under USB devices in the device manager.
I am honestly at a loss here. Would be grateful if anyone has ideas I could try!
Thanks
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Darrian said:
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Click to expand...
Click to collapse
There is none. The only safe way to root is to flash TWRP in fastboot. Right now, you can try to force update through update.app
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Darrian said:
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Click to expand...
Click to collapse
Oh. But like I said, there is none.
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Darrian said:
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Click to expand...
Click to collapse
Have you tried changing the drivers.?
Yes
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Darrian said:
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Click to expand...
Click to collapse
Glad you fixed it. :highfive:
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.