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)' *"..
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!
Hi everyone,
So today I came home from a trip as my HTC One S, that for like.. 2 months was on CyanogenMOD 12, was working all perfectly fine, showed up that there's an update available (usual stuff, these updates come often). After it finished downloading the update, it restarted and installed it.. after that the only thing that was showing up was the loading screen from CM (pulsing logo). I waited for more than 1 hour and still nothing happened. So then I decided to open the recovery and install the update again. As I did that, I restarted the phone but still it stopped at the loading screen and nothing happened. After that I decided to Factory Reset everything and download the update from the official CM website.. I tried to apply it from the fastboot through the
Code:
./fastboot flash zip *file*
but it showed me an error: FAILED (remote: not allowed) After reading countless threads and forums about why this might happen and stuff like that I figured out that it might be caused by the adb and because my device is S-ON, and I can't make it S-OFF because adb doesn't see my phone connected to the computer (using a mac). And so I'm stuck in a situation I can't find answer to. I have to make the adb work because I can't do anything through the fastboot, it just doesn't want to copy the zip.
Also, yes:
I did unlocked the bootloader through the HTC's website
I have TWRP installed (v.2.8.1.1)
I tried to delete the cache/dalvik. Advanced wipe through the TWRP
It says "tempered" in the bootloader
I tried to switch the cable (as I read that that might work)
I tried to stop/restart the adb server – still nothing
Edit: I managed to make the adb work through recovery. I sideloaded CMod again and Gapps. I went all back to the original problem – booting animation. I still can't figure out how to make it work.
I didn't find a thread for the Volt, model LS740 on Virgin Mobile. Rooted by the original owner. So I'm posting it here. I'm using adb on Ubuntu.
So I'm trying to repair a broken system by reflashing the stock ROM. I suspect the previous owner(who rooted) may have removed multiple important system apps. Upon doing a factory reset it has no home launcher or keyboard. As soon as the screen turns off it loops a com.android.systemui has stopped. Every boot you need to do a factory reset to get it to work: booting once, then again will loop the systemui crash, requiring a factory reset to work.
The android recovery works, I can get to it, but it offers install update from cache, adb, or sd card. The phone will not recognize sd card while it is in recovery, and adb doesn't work in recovery, only while booted. Copying recovery image to cache fails at 71%, I suspect the phone does not have enough RAM to move 1.17 GB from A to B. The phone may also not have spare storage space. I'm working on finding an sd card so I can try copying from there.
"adb reboot bootloader" reboots the phone normally. If there's a bootloader it skips it entirely. I found threads that say uncheck fast boot in power/battery options, but I have no such check box.
Right now, I have adb, images/zips for twrp recovery and stock rom, and I can push apks for a launcher and keyboard. But I apparently can't access bootloader or install rom via recovery. I don't have an sd card to try and copy the rom to cache, which I will try as soon as I get a card.
Adb cannot run as root, I get "adbd cannot run as root on production builds. So I can't directly push the rom to /cache/backup using adb.
Any help? I tried to get it all out there so that you guys could help better. Thanks for reading all that.
Fixed it by finding an LG recovery reflash utility and reflashing a factory version.
I unlocked the bootloader on an old HTC One S through the directions on the HTC Developer website. I then loaded the CWM recovery and did the rooting and installed the Rom manager app. The SuperSU update had to be added with the abd sideloader and the rootcheck said it had root access. Both of those programs seemed to be working fine. Then I send the Zip file of a ROM (idk which one because I renamed it so it would be easier to enter) and from the ROM manager I select the one I just sent and go to install it.
Then the phone turns off and a long string of code ends with "transfer successful" or something to that effect but stays there. I rebooted and tried again and the same thing. Tried again and did a factory reset from the recovery but nothing would get the phone to boot past the HTC screen. I tried Wiping the davlik cache and the regular wipe and hard reset and adding the recovery again but NOW MY PHONE DOESNT SHOW UP WITH ADB DEVICES CMD.
I am already in over my head but I have been enjoying learning from this and other websites about how android works. However I think I have exhausted my research options and I am at dead end...
How can I get the adb commands to work again?
bmckeeoneill said:
I unlocked the bootloader on an old HTC One S through the directions on the HTC Developer website. I then loaded the CWM recovery and did the rooting and installed the Rom manager app. The SuperSU update had to be added with the abd sideloader and the rootcheck said it had root access. Both of those programs seemed to be working fine. Then I send the Zip file of a ROM (idk which one because I renamed it so it would be easier to enter) and from the ROM manager I select the one I just sent and go to install it.
Then the phone turns off and a long string of code ends with "transfer successful" or something to that effect but stays there. I rebooted and tried again and the same thing. Tried again and did a factory reset from the recovery but nothing would get the phone to boot past the HTC screen. I tried Wiping the davlik cache and the regular wipe and hard reset and adding the recovery again but NOW MY PHONE DOESNT SHOW UP WITH ADB DEVICES CMD.
I am already in over my head but I have been enjoying learning from this and other websites about how android works. However I think I have exhausted my research options and I am at dead end...
How can I get the adb commands to work again?
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Probably an encryption issue. As twrp doesn't support encryption in A11. I don't know what's causing the black screen. The best way out is using msmdownload tool, I believe.
CodeRida said:
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Click to expand...
Click to collapse
in that case reflash twrp,root and the os you were using(in the order you did it the first time and, when you get your next ota update
extract it and edit to remove code which makes it look for stock recovery
select all the decompressed files and compress to ota zip file again
then in update area choose local update and use the file you just edited