I'm in a constant loop at the loading screen. I have CWM installed and I can get to that but I can't seem to get the Windows drivers working for my device. They worked fine with the phone fully booted up. Unfortunately, I don't have a ROM on the internal drive of the phone (no external SD). I can also get to Fastboot mode with drivers on Windows, but will I be able to flash a ROM using that? Or can I at least push a file to the internal drive to flash in CWM?
Never mind. I flashed a system.img file directly using fastboot from one rom and it's booted. Thanks for looking.
Related
I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.
Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...
I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.
Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2
Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!
Hello friends,
So I wanted to switch my TF101 to Cyanogenmod this weekend. I've been using Revolver, but with other devices on CM, I wanted some consistency in the experience among my devices.
I started by updating my Clockworkmod Recovery version. Flashing the latest 6.0.1.3 version caused problems with Install Zip from Sdcard, for some reason. So I downgraded to the 5.8.3.4 Touch version. Now Recovery works, but I cannot utilize adb reboot-recovery (it reboots system), Reboot System Now from CWM (it reboots recovery), or manually power off to reboot system (it reboots recovery). I can manually reboot back to system by Power+Vol Down and letting it cold boot, but this is less than ideal.
Here's my big problem. I went ahead with trying to flash CM anyways. I booted into the recovery, with the CM zip on my sdcard partition. I wiped cache and data, flashed the sdcard, and then tricked my tablet into cold booting (sigh). Then I waited. CM's logo spun around, and around, and around...and did this for the better part of an hour.
So I tried flashing it again. Same problem. I would have tried flashing back to Revolver, but apparently the new CWM looks for my internal partition rather than my microSD card, and that's where Revolver is stored. Bad luck there.
I went hunting for some unbricking tools. I got the tablet into APX mode once, and got my computer to recognize that something was there. But by the time I'd installed the drivers, Windows wouldn't recognize that anything was connected. So I can't use any APX tools.
tl;dr: Here's my problem:
Bootlooping ROM
Recovery Access (CWM Touch 5.8.3.4)
No ADB access
No APX access
jordanjay29 said:
Hello friends,
So I wanted to switch my TF101 to Cyanogenmod this weekend. I've been using Revolver, but with other devices on CM, I wanted some consistency in the experience among my devices.
I started by updating my Clockworkmod Recovery version. Flashing the latest 6.0.1.3 version caused problems with Install Zip from Sdcard, for some reason. So I downgraded to the 5.8.3.4 Touch version. Now Recovery works, but I cannot utilize adb reboot-recovery (it reboots system), Reboot System Now from CWM (it reboots recovery), or manually power off to reboot system (it reboots recovery). I can manually reboot back to system by Power+Vol Down and letting it cold boot, but this is less than ideal.
Here's my big problem. I went ahead with trying to flash CM anyways. I booted into the recovery, with the CM zip on my sdcard partition. I wiped cache and data, flashed the sdcard, and then tricked my tablet into cold booting (sigh). Then I waited. CM's logo spun around, and around, and around...and did this for the better part of an hour.
So I tried flashing it again. Same problem. I would have tried flashing back to Revolver, but apparently the new CWM looks for my internal partition rather than my microSD card, and that's where Revolver is stored. Bad luck there.
I went hunting for some unbricking tools. I got the tablet into APX mode once, and got my computer to recognize that something was there. But by the time I'd installed the drivers, Windows wouldn't recognize that anything was connected. So I can't use any APX tools.
tl;dr: Here's my problem:
Bootlooping ROM
Recovery Access (CWM Touch 5.8.3.4)
No ADB access
No APX access
Click to expand...
Click to collapse
Reconnect tablet into APX mode, if u have installed all drivers laptop should recognize your tablet in APX mode... once in apex, use easy flash
Sent from my Transformer using xda app-developers app
You didn't read, clearly.
No worries, I got this unbricked by following this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
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.
Quick note: I'm very new to all this so I don't really know entirely what's going on.
Alright, basically I'm trying to install the Paranoid Android ROM and I've run into a bit of an issue. I've unlocked the bootloader and flashed the ClockworkMod Recovery. The problem I've ran into is that when I go into the CWM recovery and attempt to do anything with ADB it comes up with "error: device not found"
What am I doing wrong?
Sidenote: ADB can find my phone if it's booted up normally, it's only when I boot to the CWM custom recovery that it can't find it...
I think you are doing it wrong way buddy..
Boot in to Bootloader mode not in CWM Recovery, then try with fastboot and check again..
I did boot into bootloader, then went to CWM and tried to push the ROM using ADB but it wasn't recognising my phone.
Doesn't matter now anyway. I got around it by literally just drag and dropping the zip files onto my phone's internal memory when it was booted up normally and connected to my PC. Then I rebooted into the bootloader, flashed CWM and installed from ZIP. That method was far easier than messing around with ADB etc.
Hello,
I received a used Vega Sky a800s (IM-A800s LTE) Korean device which had stock jb 4.1.2. It had issues like battery draining fast and getting damn hot while using network (3g, WiFi). I thought a lightweight custom ROM would solve these problems. So I rooted it using frama root application and flashed a downloaded compatible CWM.img 6.x with Rashr-flash tool application. All went smoothly and I got root access and could boot to CWM. I made a back up of my device, booted to android and copied the backup to my SD card. Then I again booted to CWM, erased everything and flashed a MiUi JB ROM I have downloaded. The ROM has been made for a800s which is my device. Flashing had no problem everything went smoothly no error message. But then the phone is not booting it shows error Messene "Kernal Panic" in a blue background. I can't boot to CWM but only fastboot mode can be activated. I tried all possible solutions but still my device is bricked.
1) I tried to flash backed up boot.IMG through fastboot. It gave error "remote error (unknown reason).
2) I downloaded the latest stock firmware in .bnix format to tried flashing with their IE flash method. It gives an error message with some symbols but I can't understand it.
3) I tried various other things but failed.
I think the problem is in boot partition which I can't access or flash.
Please help me to get my device back to life?
Thank you in advance.
Solved by myself
Finally I found a way HURRAY... My VEGA SKY is back to life..
Here I'll post what I did so someone in the same boat may be helped.
? If you accidentally bricked your phone by some error of flashing or whatever, you can get the brick back to life by this method. But you should have the followings to do that.
01. Your device must support fastboot and it should be able to boot to fastboot.
02. You have the drivers installed in your PC and be able to connect your device.
03. You should have the backup of your phone copied to PC. (Else you should have a backup in phone storage and the particular recovery (CWM in my case) in .IMG format saved in your PC.
OK. This is what I did.
01. Connect the device to PC in fastboot mode.
02. Run this command to check whether itbis connected properly.
fastboot devices
It will show your device as 'a number' and mode as 'fastboot'
03. Copy recovery.img (from backup or elsewhere) to the same folder as your fastboot folder.
04. Run this command.
fastboot boot recovery.IMG
(recovery.img should be the name of your recovery)
This will send the recovery to devices RAM and farce it to boot using this recovery.
Device will boot into recovery (CWM in my case)
Now you can restore through your device as usual.
That's it.?
Glad you got it solved. I'll close this thread.