I have the At&t HTC One and wanted to root,So i did steps as instructed in the all in one kit by hasoon,i unlocked bootloader,flash twrp
2.5 recovery, and then flash the same twrp kennel, the recovery appear on my phone, but then i cant push the SU into my phone, using perm
root,keep getting device not found although i have installed htc sync along with the driver, and i stuck at the recovery loop, cannot get out of it, so
then I enter bootloader again, and flash Superboot image, the phone appeared to be rooted as i can use titanium backup to delete apps but then
my wifi not working, and if i restart the phone i will stuck in the recovery loop no way to get out,please help
I was having major problems with my device not being recognized - issues with having BOTH the HTC Drivers AND HTC Sync Manager installed - kept saying the drivers needed to be reinstalled/updated, but if I did that, the device was never recognized - like the two installs compete.
I uninstalled both the drivers and the sync manager, rebooted my computer, installed sync manager, and ran it, IGNORING the request to update it.
The system FINALLY recognized my device when I plugged it in, and I was able to get superSU to load via TWRP.
Related
I'm new to rooting and all of this type of thing, i figured I would first start with my HTC Flyer. I successfully unlocked the bootloader, and installed SuperUser, upon installing greenify and i tried to install the Xposed Framework, and my device now is stuck in a boot loop.
When enter the bootloader and do a factory reset or try to enter factory it completely freezes, and when i try to connect it to my PC via fastboot the PC says that the USB device that is connected cannot be recognized and fastboot will not work. Did i completely fry this device? Also if you have time I couldnt figure out a proper way to flash a custom rom so if anyone has a guide for that I would appreciate a link to that as well.
Thank you so much!!
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
Hi!
I'm so stupid. I wanted to install cm12.1. So I rooted phone, unlocked BL. Then, I had first problem - when executing adb oem-unlock BL has unlocked and phone go to fastboot. But my comp couldn't recognize it (heard plugging in and out sound repeatedly). And here comes my "stupidity". I installed flashify and flashed CWM by it, got to CWM, installed cm12.1 zip. Of course wiped all data. Because I didn't flashed boot.img cm12.1 was freezing on fist setting up screen (nothing was working, just power button - pushing 10s turned off phone).
I wanted to flash boot.img by fastboot. But I still had problems with drivers(omap4boot didn't work). So I tried to recovery system by LG Mobile Support Tool. Everything got fine, but then phone stuck on the LG logo.
S/W Uprgade mode works of course, but I can't get to recovery now.
I'm using Windows 8.1
Any ideas?
Edit.
Ok, so I tried to install omap again. I did it, but the phone is still repeatedly conecting and disconnecting and in device manager I cought omap4430 driver whith waring mark for a while. Any ideas now?
Is it the non-animated LG logo?
This should work:
http://forum.xda-developers.com/showthread.php?t=2748384
The download links for the firmware are probably not up to date. Use this to download: http://forum.xda-developers.com/showthread.php?t=2287573
If your phone still goes beyond the non-animated logo, there might be easier solutions.
It was after animation.
Anyway, I have finally solved this problem by installing new system using Bride's solution with full wipe.
I have an answer to this. I had the problem, then I found the solution and now I'm sharing it:
Problem: I tried to put SuperSU on my M9 with CM-13 because I thought I needed root (you don't, under developer options there is the ability to turn on root essentially). So I flashed SuperSU from an apk and then it auto-updated itself then rebooted and got in a start up loop! Now I couldn't access the phone via adb, I'm not sure why. I think USB Debugging was off, but I'm not sure. AND I had not installed SuperSU from a zip so I didn't have that file laying around! So I went and got the latest SuperSU which I heard would work (it did) here: http://download.chainfire.eu/969/SuperSU/ THEN....how do I get it on my phone? I mean, who has a micro-SD reader laying around...not me today.
I DID have fastboot working but not adb. SO....I went into my phone and launched recovery mode then I chose this new thing called "adb sideload." That turns ON MTP so your phone comes up technically on your PC via USB but it doesn't show under my computer. But then I was able to go to my command prompt and type "adb-killserver" then "adb sideload NewSuperSU.zip" and it loaded!!! And I could then boot in!
Now I'm sure I shouldn't have SuperSU running but at least now I can put all the needed binarys (like CM and gApps to get started if I needed to from scratch) on !!!
So it works now.
I had TWRP installed and all was good. Then I tried an OTA update. Update failed and now I can't get into recovery or fastboot. When I try it stops at the 1+ logo with Fastboot Mode written under the logo. This happens if I try Volum Up + power button or adb reboot-bootloader. Device is listed with ADB but won't show up for fastboot.
How do I get back to stock recovery and get the update installed?
Thanks!
Is fastboot installed properly on your PC?
Drivers?
If not and you get it working, you can use fastboot to flash a new recovery. Otherwise read ahead.
Does your phone boot? Is it rooted?
If so, you can try to flash a new recovery via tools like FlashFire, Flashify, Rashr, etc.
If none of those work for you, you can try the un-bricking methods.
I've had my Oneplus 2 hardbrick 3 times on me so far. The solution was to put the phone into a Qualcomm QHUSB_BULK mode, installing unsigned drivers in Windows, and using Chinese software to push recovery files to your phone.
For my first two hard bricks (My phone wasn't responding to anything - it would just show up in the device manager when plugged into the PC). I was able to write the stock recovery and boot files onto my phone by using Method 1 from this OnePlus Forums thread: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/.
I was then able to boot to recovery and dirty flash my OS without any data loss this way.
The last hard brick was much worse and required me to completely reinstall everything on my phone via one of the other methods (I used this link: http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 and ended up with H2OS, which I then replaced with OOS 3.1.0) - if it comes to that I would recommend checking out the other methods in the OnePlus Forum link below to hopefully avoid going through H2OS - but if not, this one worked.
Also, for updates: You'll need to to reflash (dirty flash) your rom first (this is to unroot/undo any modifications you made to the system, otherwise the OTA will fail) and then flash the OTA. You should be able to use TWRP for this.
Thanks for the reply. Got fastboot working on a different computer.
Phone boots just fine. Not rooted. Just can't access recovery mode or install updates
I tried loading stock recovery (as per this thread) with no change. Thinking I'll have to treat it like it's bricked. Would rather not have to wipe phone though, but doesn't look like I have much choice .
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
CrazyArjun said:
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
Click to expand...
Click to collapse
can you share those drivers,,facing same issue actually