[Q] Can't get out of cwm recover - HTC One S

Hey guys I need some help. I'm usually able to find answers to all my problems because they've already been answered, but for once, I'm stumped.
I can't seem to get my One S out of CWM recovery. Every time I try to reboot, the screen will flash briefly a couple times, and will come right back to cwm. I can't access the bootloader screen, and cant mount my sd card (error given is: "Unable to open ums lunfile (No such file or directory"). I think I may have caused this by not first flashing boot.img via fastboot before flashing trickdroid. I followed all steps to root without a problem.
I'm not quite sure what else to try at this point. Since I can't access bootloader screen, I can't use fastboot. I can adb push files to my device, though.
Any help/suggestions you may be able to provide would be greatly appreciated. Thanks in advance.
UPDATE: After what seemed like the 100th time I tried to restart the device, it finally booted normally. Not sure what caused it, but the device works fine now.

Related

[Q] Virtually bricked s3, any suggestions?

First of all, thanks for reading my post. I'll try to make this as concise as possible.
My Sprint Galaxy S3, which is rooted with CWM v6.0.1.2 and running official Jelly Bean was doing great.
I was trying to lower the screen density as much as possible and accidentally set it too low, so now it wont load past the last Samsung logo screen.
Ive tried pulling the build.prop, and i edited it with no issues. but i had issues pushing it back in (apparently i cant give the adb proper root access.)
Ive tried reinstalling cwm.
Ive tried pushing the build.prop with the phone in recovery mode (in which case my pc cant find the drivers), download mode, on the samsung logo, and on a frozen "updating apps" screen that appears whenever i reinstall cwm, and each time i get no response when i attempt to give root access to the adb. (tried using command "adb command su" and just "su" and the cmd never responds)
I even tried a factory reset.
And nothing has worked so far.
Ive been at it for hours, searching these forums trying to learn everything i possibly can.
but now im at a loss, and i've come here for help.
I sincerely appreciate any reply. My last option on my list is to install a custom rom to see if it will overwrite the build.prop.
Please please please help me find a solution. Thanks in advance,
-Clay
---
EDIT:
ended up unrooting and installing stock rom and it fixed it.
So i guess my new question is, what are the proper methods to make sure i can push files through the adb?
thanks!
-clay

Bricked with no ADB, can't mount USB or SDcard, ODIN freezes

. The phone was running great for weeks, it had the USB fast charge hack, and the setup in my sig, when suddenly I woke up to a bootloop after going to bed with a perfectly good phone. Stupidly, I had no backup in recovery to flash. Trying to put an update.zip onto the internal memory is when I discovered that USB mount in recovery doesn't work. In CWM or TWRP I get nothing if I try. I also couldn't mount anything from /sdcard, /data, or /system, I would get "Error mounting /system!" if I tried. It also won't flash a zip from sideload in CWM, although it seems to push it over just fine as it takes a while and reads the file size of the zip. It seems as if anything I try to do to /system, /sdcard, or /data just won't take.
. I can get it to listen to fastboot commands, it will even list as one in Wug's toolkit, but it is not recognized as an ADB device in Wug's. Fastboot seems to work by itself, and in Wug's. In both cases, it seems to flash the radio, bootloader, and recovery just fine. When I (or the script in Wug's) gets to flashing the /system, /sdcard, and /data portion however, then it returns an error after seemingly writing everything. I've tried flashing with manual command line, Wug's Toolkit, and a batch file from someone here on XDA, none of it works.
ODIN hangs indefinitely within a few seconds of trying to flash. I can only get the COM:3 box in ODIN to go yellow, never green like I remember when I unlocked the bootloader. How can I get ODIN working? I feel like if I can get it going I should be able to fix this.
I'm at my wits end here. At this point I've tried fastboot, ODIN, and Wugs Toolkit. Nothing works I can flash recoveries. I have download mode. I have fastboot working. What can I do to get this damn thing working? Can this be a simple USB driver issue after all the drivers I've tried?
Anyone who helps me fix this will get thanked by me every time I see them for quite awhile, I've put too many hours into this already! Yes, I've moved on to a GS4, but I LOVED this phone and would like to get it going again. I'll still use it as a GrooveIP phone at home, or give it to my kid. Or even to have it as a backup would be great. Thanks for all the help guys!
http://forum.xda-developers.com/showthread.php?t=2500397
Have you tried going trough the same steps?
Oh yes, several times, with a GB, ICS, and the latest JB AOSP ROM, for the correct phone (sph-d720). I always use crespo4g images. It never works. It acts as if it writes, but has an error that says "can not automatically format" when it tries to flash the zip. When I reboot the phone there is no change. I can flash recoveries just fine.
Sent from my SPH-L720 using xda app-developers app
Nobody? I would love to get back on this phone... My favorite device of all time to this day
DizturbedOne said:
Nobody? I would love to get back on this phone... My favorite device of all time to this day
Click to expand...
Click to collapse
I have a hunch that your internal memory has gone bad. Any luck so Far by any other method?
Sent from my Nexus S using Tapatalk
No go from anything I've tried. It seems like it just won't be recognized as an ADB device. Pretty disappointed at this point.
Tapatalkin' from my SGS4

[Q] Locked Bootloader with TWRP, Won't unlock anymore

Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha
Tonymhoffman said:
Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha
Click to expand...
Click to collapse
Believe it or not, I have the same problem since yesterday. Its driving me mad since I'm no expert on rooting/unlocking
Phone gets detected by PC and by the toolbox but I can not unlock my phone again.
I am now stuck with TWRP and the only rom I can flash is Slimkat, all the others fail. If I hit unlock bootloader in the toolbox it goes through the process (fast) and it gives no error, boots back up to TWRP and thats it, but it is still locked
I just want it back locked and stocl CM11
Firstly, don't use toolkits. They are often the cause of issues.
Follow this thread to solve your problem: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
PewLaserBeam said:
Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.
Tonymhoffman said:
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.
Click to expand...
Click to collapse
I had this yesterday + I kept getting the message 'No OS installed'. Since it was already half 'broken', out of frustration I clicked everything and used all sorts of commands I could find (not the best idea I know :angel untill my PC detected the internal memory and then I downloaded 6-7 roms just to be sure. Slimkat was the only one without a fail.
How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.
Adb sideload did the fix for me after a while.
But it looks loke you have another problem.
Tonymhoffman said:
How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.
Click to expand...
Click to collapse
Instead of trying to sideload the unlocker zip have you tried using the adb push command?
Timma
Thanks for the reply. The solution for me was to mount the phone in TWRP. This allowed my SD card to be explored in Windows. However, it still would not allow me to copy files to the main directory and just out of frustration I quickly drag and dropped a PDF file that landed on a folder in the SD directory and it worked. Haha. So I then tried to copy the file inside another folder instead of the main directory. Success. What a headache and big ass mistake I'll never make again.
Note to self. Do not lock the bootloader with a custom recovery still installed. Ever.

[Q] Having problems when trying to ROOT Moto G LTE x1040

Hi, I'm relatively new to this forum and I've been trying almost all day to root my phone...
First, I had problems trying to get a working recovery (they just crashed to random colors/or loaded fine and then rebooted like nothing happened). Tried with CWM Recovery but it seems this model is not supported atm, tried with TWRP v2.8.3.0 and also crashes... ATM the only custom recovery that has started without going haywire is TWRP v2.8.0.0 (at least for my phone).
I prefered using 'fastboot boot recovery.img' before 'flash' since it's the first time I'm trying to root a phone. The recovery mode starts okay and I also placed the UPDATE-SuperSU-v2.46.zip in the internal storage before hand. I try to install the .zip file and all goes well, no errors and a blue 'Successful' message. This is where the 'root' procedure fails. Since you can reboot or go home to check other stuff I just tried rebooting the first time and it asked me that I had a SuperSU in the device and that if I wanted to install it to have root. I obviously swiped to install it and it displayed for a split of a second the window from before and just shut down and rebooted...
I tried several other methods to try and root my phone after this failure, but none worked. I checked again if trying this procedure would serve a purpose but I got the same thing always. But since I saw the process so many times I could see for a moment a red line saying something like 'E: failed to copy su binary to /system/bin (...)' but couldn't read more because it was a split of a second there xD. I googled this weird error and I found that my /system is in read only state and not writtable... But to change it to writtable I need root too it seems <_<)
So, any help? I'm sorry if this long text makes someone just look away but I don't really know how to explain my problem in more simple words xD. Any help will be appreciated .
EDIT: Forgot to say that my phone has its bootloader unlocked already and it has USB Debugging enabled.
Moto G LTE x1040
System version (as my phone says) 21.31.1.peregrine.retla.retla.en.01 entcl
Build: KXB21.14-L1.56-1
OS: KitKat 4.4.4
Please help
Bump.
Bump.

Help very much appreciated (boot loop nexus 5)

Hello Everyone,
I have searched this forum and followed many useful threads which seemed related to my issue, alas none have actually been able to fix my phone.
I am using a stock ROM which upgraded to marshmallow not too long ago. The other day my phone rebooted for no reason got it's self into a boot loop. Since them I have tried the following:
1) I have used recovery mode and cleared the cache/performed a factory reset. I just the get the can't mount/cache line pop up.
2) Tried to use ADB to boot an image over the USB but couldn't get much from this (so I may have missed something with this).
3) Tried to use fastboot to move flash back to a version of marshmallow downloaded. When I go to flash files in I get failed messages on command prompt. (Failed, remote flash write error).
additional info
1) the device was encrypted from the settings menu when functional.
Any advice or help would be good at this point. Let me know if additional information is needed.
Thanks!

Categories

Resources