I flashed a CWM, and did a backup. I then wiped the data partition in preparation to flash Cyanogen. At some point my computer lost the connection to the device so I could not push the file. So I ran restore from CWM, the restore completed, but when I go to reboot device, it just reboots back into recovery. Am I missing something? Please help, my phone is completely unusable.
I tried rebooting into fastbook from CWM, and it did, and my PC see's the phone, but when I boot into recovery, my PC stops seeing it so I cannot push CWM.
I reflashed a different recovery clockworkmodrecovery.6051.falcon, and it still drops the USB connection when you go into recovery, so adb push does not work. I tired restoring again, the phone just reboots into CWM. Is my phone completely dead? It seems no matter what I do I cannot get my PC to see the phone when CWM is running. In fastboot, it sees it fine, as soon as you go into recovery, it drops the USB connection and you cannot push files.
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
Hey,
i've got a few problems with my HTC One S, running Cyanogenmod 11 (4.4.4) with TWRP as recovery.
Since a few days nearly every app crashes, ca. 3 minutes after I start the phone. In these minutes everything is working. After that there are only messages that "android.process.acore", "com.google.process.gapps" and nearly every other app has been closed. When I press OK, the message appears again.
So I tried to flash another ROM, which isn't possible because I first can't copy anything to the phone, the copying process stops after the half. I also couldn't download a ROM directly to the phone. Then I tried to flash again my actual ROM which is still on the phone, I selected the .zip in TWRP, but then the phone is restarting and nothing happened.
There are also other problems:
1. I tried a soft reset in the settings, isn't possible because nothing happens when i press the "Confirm" button
2. Clear storage and Factory reset in the boot loader isn't possible, when I select one of that the phone only starts into the recovery, without anything has been resetted
3. Pushing a zip with ADB doesn't work, it says I don't have permissions to copy anything on the storage
4. The ADB sideload mode doesn't start in TWRP
5. I tried to flash CWM as recovery, it says "successful", but when I start into recovery there is still TWRP..
6. Relocking the bootloader doesn't work, it also says "successful" but in the bootloader appears "*** unlocked ***" After that I tried to turn back to stock ROM with the RUU exe by HTC, but when the process starts, the phone just turns off.
Does anyone have a idea? Do I maybe have a virus? Sometimes it appears to me that there are problems with the storage or anything like that..
I really tried to do everything, and also searched in this forum and in other but I didn't find anyone with the same problem..
Thank you!
Give the Mount option a try in TRWP and see if you can copy a ROM over to the phone.
Okay I had to install the right driver for adb..
Then adb push worked, I could select the .zip in the Install option in TWRP, but the phone again just restarts without installing the rom..
ADB Sideload also worked with the driver, but after I tried to ADB sideload the ROM it said "* failed to write data 'protocol fault (no status)' *"..
HI,
ads started appearing on my a850, then massive apps started appearing, I had no option but to restart.
When I did my phone is stuck at those who do logo.
I did reset to factory many times but still the same, I then went to flash but I am running XP and no matter what I try, I cannot get the usb drivers to appear, so I have no usb connect.
Is it possible to run an update.zip from my sdcard to reload the system, I guess my phone would have to be rooted first.
So is there a zip which roots the phone, then loads the recovery system, from the sdcard zip file?
I am sure I cannot connect my phone via usb
Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.
Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?
This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?