Hi, I'm on a Spring HTC One M7 and I accidentally (cuz im a noob) flashed the android 4.4 rom for GSM devices. Now my phone is softbricked and stuck on the boot screen. I am running TWRP 2.7.1.0. I have been trying to sideload and flash a different rom since I didn't make a back up. Now when I'm in my cmd and input the "adb usb" I get the error: closed message. I'm pretty sure I have the latest drivers and the version of SDK. Please help! I really don't want to do a factory reset because of all the stuff I have on my phone!
LameJae said:
Hi, I'm on a Spring HTC One M7 and I accidentally (cuz im a noob) flashed the android 4.4 rom for GSM devices. Now my phone is softbricked and stuck on the boot screen. I am running TWRP 2.7.1.0. I have been trying to sideload and flash a different rom since I didn't make a back up. Now when I'm in my cmd and input the "adb usb" I get the error: closed message. I'm pretty sure I have the latest drivers and the version of SDK. Please help! I really don't want to do a factory reset because of all the stuff I have on my phone!
Click to expand...
Click to collapse
if you are going to flash a different rom its going to delete all of your user data anyway, does the M7 have a SD card slot? put on in and flash CWM, from there you should be able to mount usb storage and take some of your data off the phone.
The M7 doesn't have a SD card slot
Related
Yepp. After attempting to root my Nexus, I screwed up somewhere along the line and have now made my phone useless. Every little thing I've tried has not been able to fix it
I got the bootloader unlocked, but whenever I try and boot my phone, it gets to the google logo with the little unlocked padlock beneath it, and no further. So I screw'd up along the line following some probably bogus POS guide.
Anyhoo, I'd like to know how to fix it. I can still get into the fastloader, but I have no idea what to do from there. I'd like to figure out how to do a complete factory reset. I can't access the phone a usb mass storage device at all, so I can't figure out how to load a recovery file into clockwork.
Any help would be greatly appreciated. Its on a Koodo carrier (I believe its a branch of Telus up here in Canada)
Install android ask correctly with correct drivers. Execute : fastboot devices
Make sure you are in the boot loader.
If your device id shows up flash a recovery for your phone.
This should work provided that you do it correctly. As far as I know there is no way to overwrite nexus s bootloader so bricking it is virtually impossible unless you physically do some damage.
Sent from my Nexus S 4G using XDA App
obsanity said:
Install android ask correctly with correct drivers. Execute : fastboot devices
Make sure you are in the boot loader.
If your device id shows up flash a recovery for your phone.
This should work provided that you do it correctly. As far as I know there is no way to overwrite nexus s bootloader so bricking it is virtually impossible unless you physically do some damage.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
ask correctly? You mean SDK?
I did get the Android SDK and instaled the Google drivers. Now what do I do with "execute :fastboot devices" ?
Put the cwm recovery image into the /tools folder inside your SDK folder, boot device into bootloader, open command prompt, type
fastboot devices (should return your device's id)
fastboot flash recovery <nameofrecovery>.img
go to recovery on the phone,
mount & storage > mount usb (if that doesn't work you are either missing more drivers or go back one step to mount & storage and mount /sdcard then repeat the step)
copy a ROM for YOUR device from the stickied topic in this very subforum onto your phone, a full rom, signed or unsigned doesn't matter.
unmount usb
go back to top menu in recovery, "install zip from sd card". choose the ROM you downloaded and run it, done
OP, we need to know, do you have Clockwork Recovery installed?
Yes. I have clockwork Recovery installed.
Clockwork Oranges said:
Yes. I have clockwork Recovery installed.
Click to expand...
Click to collapse
Ok did you flash a ROM after you rooted? You may have flashed a ROM that does not work for your device. Which model Nexus do you have and which ROM did you flash?
I didn't try flashing a Rom. I have an I9020A.
rentaric said:
Put the cwm recovery image into the /tools folder inside your SDK folder, boot device into bootloader, open command prompt, type
fastboot devices (should return your device's id)
fastboot flash recovery <nameofrecovery>.img
go to recovery on the phone,
mount & storage > mount usb (if that doesn't work you are either missing more drivers or go back one step to mount & storage and mount /sdcard then repeat the step)
copy a ROM for YOUR device from the stickied topic in this very subforum onto your phone, a full rom, signed or unsigned doesn't matter.
unmount usb
go back to top menu in recovery, "install zip from sd card". choose the ROM you downloaded and run it, done
Click to expand...
Click to collapse
I just tried one that was SUPPOSED to work with my phone, (I9020A) but it failed mid instalation and aborted. I tried re downloading and re installing it through clockwork and got the same error.
Clockwork Oranges said:
I just tried one that was SUPPOSED to work with my phone, (I9020A) but it failed mid instalation and aborted. I tried re downloading and re installing it through clockwork and got the same error.
Click to expand...
Click to collapse
Well if you have working Clockwork Recovery, then your solution is probably as simple as flashing another ROM. You can download another zip on your PC, then in CWM recovery go to Mounts and Storage and then Mount USB Storage. Then you can copy the zip over, then flash it.
I have done exactly the same thing OP! I am from Canada too, also Koodo. Let me guess you went here:
"a url that isnexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/..."
I don't know if that guy is the retard - or if I am the retard for not scrolling down the screen and seeing everyone screaming about their phone being bricked lol.
I get extra points too because I didn't backup any of my sdcard data first %^&* lol
oh boy.
Well I'll let you know how I make out with the ROM, and hopefully Google will sync back my paid apps (well one - TouchDown)
Back up and rooted to boot. Not screwed after all. This site is a great resource, thank you so much!
Clockwork Oranges said:
I just tried one that was SUPPOSED to work with my phone, (I9020A) but it failed mid instalation and aborted. I tried re downloading and re installing it through clockwork and got the same error.
Click to expand...
Click to collapse
Make sure you have the correct recovery and the correct ROM for your phone model. I suggest you re-flash CWM recovery from this thead , then flash OTA ROM from this thread (look for the one that says "Works on: I9020A")
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
First for the One XL it is suggested you use TWRP and not CWM
You can get it here from their website .
It tells you how to fastboot flash it.
If you did an OTA to 2.20 or your device came with 2.20 you probably need to flash the boot.img /kernel
So in your CM10 zip, extract the boot image.
and use fastboot to flash the boot img with the command
fastboot flash boot boot.img
and that should help you out.
I also suggest reflashing the rom with TWRP just in case. Hope this helps.
Can adb see the phone?
FrustratedAndConfused said:
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
Click to expand...
Click to collapse
This is the one xl correct, not the international on x?
If you can get anything on your screen, your phone isn't hard-bricked.
First, which phone do you have? ClockworkMod Touch Recovery does not work on the AT&T One X (One XL). If you tried flashing a ROM through it, it's not going to work and it's probably not booting up because the ROM is corrupted.
I would start with flashing a new recovery in adb. Use TWRP, because even the basic CWM is not supported for this phone and can cause issues.
Can you get into recovery? If so is the SD card mountable?
First time I flashed i had a similar issue where the SD couldn't mount. I ended up having to run the factory RUU after relocking the bootloader & then start again. I waited for a later nightly to come out. Also seems to go better if you flash a different rom first like viper.
NismoR31 said:
Can you get into recovery? If so is the SD card mountable?
Click to expand...
Click to collapse
Doesn't matter. He flashed the wrong recovery (not for our phone). There is not Touch CWM for our version.
i should really refresh pages before replying
After trying to install CM10 Via TWRP my phone hung on the CM10 splash page.
I have tried to reinstall CM10 and I keep having the same problem.
I'm able to access TWRP but for some odd reason I can't mount my sd card properly. I'm not able to click "Mount sd card" on the "mount" page in TWRP. That being said I can't backup my phone from a previous backup.. Any help would be greatly appreciated.
Now my phone won't even turn on.. HELP
undergrad said:
Now my phone won't even turn on.. HELP
Click to expand...
Click to collapse
Have you tried holding down the power and volume down button for longer then 10 seconds or longer? this should force restart your phone, get into TWRP and try an other Rom for now, also did you try an international rom? international roms will not work.
UPDATE: I'm guessing your also can't recover your last back up because your on HBOOT 1.14 S-ON? 1.14 will not recover boot.img's
If you manage to get it to mount to your computer (Check your drivers are installed also, EG htc sync usb drivers) then look for a "one click boot img flash" unless you know how to flash them using fastboot commands, whenever you are to flash a room, extract the boot.img from the zip file, flash that in fastboot, THEN go to recovery and flash a rom. same goes for backups. S-off is a hassle.
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
undergrad said:
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
Click to expand...
Click to collapse
when in twrp recovery.
1. delete cache, dav. cache, and system restore.
2. reinstall the gapp files and the CM10 zip file.
3. reboot
The issue is that I can't get into TWRP
what did you do to it? phones don't just die and cm10 didn't kill it. are you sure you flashed cm10 for the evita?
also try flashing this version of twrp openrecovery-twrp-2.3.3.1-evita.img
also run "fastboot erase cache" after flashing then try going into recovery and wiping cache,dalvik, and external
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
undergrad said:
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
Click to expand...
Click to collapse
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Lemagex said:
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Click to expand...
Click to collapse
I managed to relock my bootloader, but installing the stock RUU is still another story..
I can only get my computer to recognize that the phone is connected to my computer if I'm in Fastboot mode.
If you can't mount from recovery the sd got corrupted happened to me they have a fix if you do a few searchs. If you locked the bootoader and the computer only recognizes in fastboot that is good now run a RUU like 1.85
Sent from my HTC One X using xda premium
Dear XDA community,
I installed Clockwork recovery and the USB drivers. The device is unlocked and when in fastboot mode it is correctly identified by my PC as falcon XT1302 with an USB connection. When in recovery mode, the device appears as "Android" in the devices menu in Windows 7 and there is a yellow "!" next to it. Unfortunately after formatting system and deleting the cache as per instructions the device won't boot up. I'm stuck at the bootloader unlock warning screen. I can access fastboot mode and recovery mode but that's it.
I want to place the cyanogenmod zip inside the internal SD card of the Moto G but adb doesn't work. I get the device not found error when inputting a command. adb devices returns a blank. I don't know which drivers to install or what to do. I've tried various fixes on forums but none work. Maybe USB debugging is the problem although I distinctly remember switching it on. In any case, I can't boot so I can't change the settings.
All I want is a way to place the cyano .zip in the phone /sdcard so that I can install it. I'm all out of ideas. USB mounting doesn't seem to work. Neither does sideloader (or maybe I messed it up?) I am at wit's end.
I didn't have anything important on my phone so I did not make a backup. In hindsight, this was a stupid mistake. I've certainly learned a lot during the install attempt.
If possible please give step by step instructions. I am not a very technical person. Any help would be greatly appreciated. pls halp
kind regards
Dont worry too much if you can acces Fast Boot just download STOCK Firmware for your version I can't post links cuz im beginer searc under help "Restore STOCK Firmware" and flash it. :fingers-crossed:
Reply here i will tell you how if you not fixed it alredy
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
hechadnebiphyh said:
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
Click to expand...
Click to collapse
As above said flash stock boot up copy cm11 and gapps reboot boot loader flash cwm or twrp reboot recovery wipe data,cache,dalvik flash ROM gapps reboot all done
Sent from my Nexus 7 using Tapatalk
Thanks to the users who replied. I've managed to solve the problem. :laugh:
Would have been faster though to get your device recognized while in recovery. You can install the driver manually and it should work. Just search for seperate driver files and ignore the Windows message that it is probably 'not compatible etc.'.
Then your device is connected properly and you can get ADB sideload to work from your recovery.
Hello,
I got this HTC One X from AT&T (->evita) and tried to get CM 10.2.1 running on that.
The steps I made:
Boot into bootloader, go to fastboot, then get the identifier, get unlock token via htcdev and unlocked it with fastboot.
I then flashed CWM 6.0.4.6 for evita via "fastboot flash recovery *filename*". Now I booted into CWM (recovery) and wiped everything instead of first trying to copy the cm.zip onto the sdcard. (I also didnt do this when the stock ROM was still running...)
Now I can access the phone via fastboot in the bootloader but I can not use adb or the USB mount when in CWM. Whenever I plug the phone into my computer (or laptop, doesn't matter. Also tried switching between USB 2 and 3 ports!) Windows keeps making the "unplugged" sound every second.
Reinstalling the latest HTC drivers did not change anything.
Anyone here knows a way how I can stop that or get the zip file on the memory? I also tried flashing the boot.img on boot and tested if I can copy the file then through CWM but that did not work.
Hoping,
NyphoX
Not sure if it'll work but try using TWRP recovery instead:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Installed the most recent version.
I get into the recovry and when I plug it into a computer Windows will keep making the "unplugged"-noise.
I can see the sdcard-directory perfectly when I hit install in both, TWRP and CWM but when I want to mount it via USB it will not change anything and I cannot access it on my PC.
adb doesn't list any device either.
Also, TWRP and CWM keep telling me that my phone is not rooted, when I try to power off or restart. Is that normal?
My other HTC One X (non AT&T) just works fine with cwm 5.*.*.*
It's normal for the recovery to inform you that you're not rooted, it'll suggest that you install superuser but there's no point doing that in your case because you have no working OS installed. Did you at any point perform a factory reset from the bootloader? If so, you've corrupted the internal storage (known bug on modified Evitas) and will need to wipe it with TWRP.
Sent from my Evita
Saw that in your Q&A.
I wiped the internal_sd and tested it after but it still did not work. I also tried a factory reset through TWRP but that did not help either.
Both recovery programs keep telling me "E:Unable to mount '/cache'.
Still not working. Q_Q
Update: I got like the oldest laptop I ever owned and installed the most recent HTC drivers there and tried to mount it. It told me in device manager that the "evita" is not recognized. When I let Windows search automatically it installed the drivers and I am now able to access the memory.
I can only assume what the problem was but it seems like the HTC One X (endeavoru) driver and the evita don't like each other...
TL;DR trying to install now. Will edit.
//EDIT: Windows still screws when I plug the phone to the other computer/laptop, so I just have to use the old machine now. Still thanks for your help, timmaaa!
//EDIT: It does work when I booted CM and enable the USB storage at the other two machines.