[Q] HTC One X wont boot into recovery - HTC One X

Friend's father recently obtained a HTC One X runing on VIRIGIN network.
We've unlocked the boot-loader, and as soon as we flash clockwork's recovery image, the phone went onto a boot loop.
Once we turned off the phone, we were able to fully boot it onto the stock image.
We've tried..
1. Clearing Fastboot's cache
2. Flashing different recovery images (including the stock one)
3. Factory resting the phone (We were unable to because im guessing it needs its default recovery (It just restarted and didnt reset))
^ All had lead to either a boot loop or just failed and booted normally.
The phone isn't rooted (Im guessing you need a recovery image to flash supersu in the first place)
All help would be appreciated. Thank you for reading this,

Try this
Download the latest TWRP from here (or 2.4.1.0 if you can find it, best version IMO)
http://forum.xda-developers.com/showthread.php?p=25393156
Then put your phone in fastboot and connect usb make sure it says 'fastboot usb'
Then rename TWRP to 'recovery' (no quotes) and copy to your fastboot folder on your PC
Open CMD and type 'fastboot flash recovery recovery.img' (no quotes)
Then type 'fastboot erase cache' (no quotes)
Do it exactly like that then use the volume + power buttons to go to hboot --> recovery and hopefully it should work
Btw these kinds of questions should go in Q&A

Thank you so much ! What a relief.
Should i delete this thread since its in the wrong section?

Mozziliac said:
Thank you so much ! What a relief.
Should i delete this thread since its in the wrong section?
Click to expand...
Click to collapse
Did it work?
If so contact a mod and then they'll close the thread for you

Hi PLease Help!
Hi i have a HTC ONE X iv had it rooted and CWM was installed fin untill! A update came out i put my phone back to stock and it still didnt update.. So i unlocked the bootloader again tried to install CWM it said succsessfull then when i try to boot into recovery the only thing i say it HTC QUITLEY BRILLIANT! and it continues to do that untill i turn it off. it boots fine again and can do everything but go into recovery... Some-One with bigger knowledge PLEASE HELP (cant live without ROOT!) Im 13 BTW

Fastboot erase cache
Enter it after that command......

Quote:
Hi PLease Help!
Hi i have a HTC ONE X iv had it rooted and CWM was installed fin untill! A update came out i put my phone back to stock and it still didnt update.. So i unlocked the bootloader again tried to install CWM it said succsessfull then when i try to boot into recovery the only thing i say it HTC QUITLEY BRILLIANT! and it continues to do that untill i turn it off. it boots fine again and can do everything but go into recovery... Some-One with bigger knowledge PLEASE HELP (cant live without ROOT!)
hi, i have the same problem right now. did u solved it?

Related

HELP PLEASE - EVO 3D Stuck in Bootloop!

Hello All,
I recently rooted my EVO3D using the HTCDEV method because the bootloader was version 1.5.
Here are the steps I followed to root (sorry for the copy and past but I want to be as detailed as possible)
Files Used
su 2.3.6.3
TWRP Recovery
Steps Taken:
1)Take both the su.zip and recovery.img files and put them in your sdk tools folder.
2)Now do the following in ur command prompt, hitting enter after each command.
3)Code:adb push recovery.img /sdcard/And,
4)Code:adb push su-2.3.6.3.zip /sdcard/Then,
5)Code:adb reboot bootloaderUr phone will go to fastboot and should look like the after picture above. Now you can flash the twrp recovery, so do,
6)Code:fastboot flash recovery recovery.imgIt will ouput something like this,
7)Code:sending 'recovery' <5068 KB>... OKAY////writing 'recovery'... OKAY///finished. total time: 11.355sNow you have twrp recovery, so you can navigate to it. On ur phone, use the power button to pick bootloader, then scroll down to recovery and pick that. You will then be booted into recovery.
8)Here you can pick "install zip" and then pick the "su-2.3.6.3.zip"
It will flash, the you can pick "back to main menu", then "reboot system now"
9)You will boot back up and have working Superuser. I have had no trouble with Titanium Backup, Root Explorer, Quick Boot or any other app that requires root. Before you do too much, it would be good to go back to recovery and do a Nandroid backup. Always best to get one ready before you start modding anything.
All of this worked fine, and the phone was "unlocked."
Then, I flashed the most recent version of CleanRom (2.7)
Again, the phone worked fine, battery life was a little crappy.
I decided to flash Ziggy's kernel.I flashed the kernel simply by putting on the SD card, and then rebooting into recovery. This worked fine as well, but I noticed some of the buttons for example the menu popups displayed volume where it should have said more, or bluetooth options where it should have said preferences. so this is where the trouble started, I downloaded kernel manager, and flashed silverneedle through that program. Now, I am stuck at the White HTC Splash screen bootloop. The phone turns on and after 15 seconds reboots, and reboots, and reboots.
What Ive attempted:
I have done countless wipes and clears of the dalvik cache and cache
ive formatted the system and the date sections (advanced menu in twrp)
ive reflashed the rom after wiping countless times
ive tried flashing different kernels in recovery to no avail
factory reset and wipe havent helped
im not concerned losing the contents of the SD card
I need help because I already had two phone claims in the past 11 months, and if I claim another lost phone I will lose insurance for life with Asurion (sprint)
anytips or help would be greatly appreciated
i can provide any additional info
Similar situation, Not sure if you've already solved the problem but I'm going to copy paste my solution from another thread...
Hi, I'm not sure if this is the right place to ask but this is a preety derp question. I've gone across the internet and tried a lot of reflashing to repair my sort of "bricked" evo. What happened, was that I had a evo 3d s-on htc bootloader unlocked, with custom recovery -clockwork..anyways I had flashed the leedroid 3d 4.0 rom and It worked the only problem was my wifi, so i attempted to flash another kernel onto it, but I had accidently flashed "Rcmix" kernel which I later found out was cdma =.=. so now my phone keeps rebooting at the htc screen, it would just load up with the green htc letters, then after 10 seconds or so it'd reboot, and then begin the process again. I can boot into bootloader and recovery but whatever I flash doesn't seem to work including restoring my backups...and then the battery died so i couldn't even charge it or go in. But i managed to work out I could load into bootloader from the CMD and the furthest i've gotten to is to have the bootloader show FASTBOOT USB. SO I must be getting somewhere...? I did read that i had to load from the cmd and not just from power+vol down..but I'd appreciate any help towards restoring my phone to the way it is or at least before i flashed the rcmix.
Just a note tho I've tried factory resetting but all i get is that it loads into recovery at the bootloader options i dont get "clear storage" as an option and "restore to factory settings" and what not just boots me into recovery agian.
EDIT:
I Managed to fix the phoneeee!!!..just for future preferences and anyone else who has this problem...
I followed bits and piece of IL DUCE's advice to izzy spun, the important part was booting the recovery from cmd. I wasn't able to "erase recovery" But I tried just booting it,
First I would remove the battery,
Put it back in,
Plug the usb cable in
1. Type command, from your Adb/fasboot folder, "adb reboot-bootloader"
2. After that I made sure my bootloader said "Fastboot USB", and then I issued the command, "fastboot boot cwm-4.0.1.4-shooteru.img" or with whatever recovery you had..
3. From there I restored from my backups my original rom. Rebooting, and fixed.
--- and It worked. At the time I was on clock work recovery, i only had the Revolutionary recovery img. Cwm-4.0.14.-shooteru.img to be exact,
after going in there I just cleared the cache and davlik and then, proceeded to restore my backups (I'm not sure if it would've worked if I had re-flashed the leedroid or a custom rom)
and then I simply rebooted the phone, and it got back into my phones original state before leedroid (as I had Only backedup before then)....
Apologies for the lengthly post, but I guess reading does help, but I've been going nuts before I managed to fix this. Just thought I'd leave this post incase someone were to need this.
Same problem
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(
awsomepanda20 said:
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(
Click to expand...
Click to collapse
What your going to have to do is flash the original kernel you started with. thats why your in a bootloop
Similar problem
Hi everyone!
I have a kind of similar problem, so I won't post it in a new thread.
Yesterday I rooted my phone following this guide: androidforums.com/evo-3d-all-things-root/494212-complete-newbies-guide-rooting-flashing-evo-3d-roms-kernels-using-fastboot . html (i am not allowed to post links to prevent spam).
I unlocked it with htcdev and installed a custom ROM without getting any errors. After restarting the phone, it got into a boot loop; it showed the starting animations of htc and the ROM and then shut down again.
Here some more information:
-Evo 3d Europe gsm
-hboot 1.5
-s-on
-image version 3.28.401
-installed ROMs using clockworkrecoverymod (as proposed in guide)
I have tried these ROMs (all leading to boot loop):
ICS NonSense
Cyanogen Mod 10 – DisarmedToaster (v. 1.4 and 1.5)
Jelly Bean 3d (by Ubuntuz)
SAD 2.1 DEsenseX
I installed the ROMs by doing:
Connect device via usb > flash boot.img via fastboot (from pc) > clear Cashe/UserData/DalvikVM > install rom.zip from sdcard > reboot
I really don't know what to try
Any ideas how I could install a running Android OS are highly appreciated.
Thx for any help
Problem solved!
Ok, I solved the problem by simply relocking the phone and installing the stock ROM with the RUU.exe
RUU.exe
I'm glad someone else mentioned Relocking before running the RUU. I've read several posts be others that have actually stated that Relocking wasn't necessary but in order for the RUU to take you have to Relock. IF you get a chance check out CoolICS Rom and MeanRom both are pretty good.
Thanks all for the help, had to revisit this issue today.

[Q] Flash failed and now stuck with "waiting for device" in cmd

Hi guys,
I just bought my One X today. Since it is my first android i am quite noob in all the issues regarding flashing/rooting.
I already unlocked the bootloader, install the clock recovery and then when I try to flash the new rom, i forgot not to extract the zip file so things start to mess up.
Now I am stuck at the HTC boot up screen. I have tried all the methods at:
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
Click to expand...
Click to collapse
but it doesn't work.
The problem is that when i type a command into cmd it keep showing waiting for device
So I don't know what to do now. I really appreciate your help if you could provide step by step.
Thank you so much
OK so as a noob you thought you'd try too root your 1st android phone after having it just one day??? oops! Lesson learned, next time read up loads first and maybe get used to the phone first before trying too root it. Anyway. . .
After installing Clockworkmod did you (as instructed in all the manuals I have read!) do a backup? If so just remove the usb, turn your phone off and go to the cwm boot menu and select restore. Fixed
recovery?
i see you have flashed recovery..
can you get to it??
Press POWER + VOL DOWN until it reboots and keep holding until u get to HBOOT..
from there select recovery and see if that shows up..
if you can get to Recovery, then you can either flash a CUSTOM ROM, or go back to STOCK recovery and then run RUU (a program provided by HTC that will restore you phone to stock) but you also have to relock the boot loader..
based on your choice more info may be required to help you
My best guess is that you have a messed up kernel...

Bad flashing caused big problems

Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
When you flash a new kernel, all you have to do is place modules zip in phone storage, put phone in bootloader, connect to computer, flash boot.img, go into recovery and flash modules. If you don't flash boot.img, the phone won't boot. Try going into bootloader by pressing volume down and power at the same time and holding it, flash viper boot.img via fastboot kit, full wipe and reflash rom. I've messed up a few times but this has always worked for me.
Beyazid said:
Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
Click to expand...
Click to collapse
there are infinite posts about how to fix this and tutorials too if you use the search button, anyways
1- why using faux 7m when there is already 10m ?
2- hold power+vol dwn
3- go to recovery (hboot not fastboot)
4- go to mounts and storage, mount storage usb
5- copy to your sd all the files excluding the boot.img from faux
6- flash rom then modules then type in cmd "adb reboot-bootloader" (without quotes),
7- choose fastboot in bootloader then flash boot.img and erase cache
@VCek: I flashed this before the Versions 10 and 11 came out
Thanks for the infos. I´ll use them the next time. But now I can´t reach the bootloader anymore because I locked the phone with "fastboot oem lock" and because of that I can´t do anything but go to the fastboot mode. The recovery is locked or in other words: I can´t use the CWM Recovery anymore.
If I click the recovery mode this happens: vvvvvv(dot)vidup(dot)de/v/l1vVH/ (make a dot instead of the word "dot" and change the V´s to W´s, I´m not allowed to post outside links right now)
The next step should be the unlocking I guess. Right? But how can I do that?
Edit: I was able to unlock the phone again so it should be easier from now on but your steps didn´t work for me. I reflashed the Viper X Rom and reflahed the Kernel without the boot.img in it. But I didn´t get the point which boot.img I should flash. Both of them or just the Rom boot.img?
Edit2: After a long day I was able to solve the Problem with the right RUU. After all it was easier than I thought and I should have done that at the beginning

Possibly bricked One X - need assistance!

Hey, everyone!
So within the past week or two my stock standard HTC One X started playing up, which I'm pretty sure was a result of a recent system update (to 4.2.2, from memory). My 'twilight' app (similar to f.lux but for phones) started randomly turning on and off for no reason, the screen became very rapidly unresponsive unless a great deal of force was applied or the phone was repeatedly locked and unlocked, it began to heat up (even more so than normal), etc, etc. Yesterday the unthinkable happened: it got stuck in a bootloop.
So here's how I wound up where I am right now.
I came to terms with the fact that I was going to lose all of my data (at least Google has automatically backed up my images and videos every few days), and anyone important enough to me that I need their phone number I also have on facebook/google plus or see frequently enough in person that when the issue is resolved I can add their numbers again. So I performed a factory reset hoping that would fix the problem. It didn't. Today, at the behest of a friend of mine, I decided to flash a custom ROM on my phone in an effort to salvage what was increasingly likely looking to be a $600 paperweight. I've never done this before, so I followed the instructions in the following video exactly as shown, and downloaded the latest stable version of Cyanogen mod for the One X. The video can be found by googling, "HTC One X - How To Root (in-depth)". It's the first result.
Everything went... well, not smoothly. But I got there in the end. Eventually the phone rebooted, and the blue (or cyan, I suppose) Cyanogen mod logo came up with the circular loading symbol tracing around it. It stayed this way for some 30 minutes or so. I decided to reboot the phone. Same issue again. I performed a factory reset, cleared the cache, cleared the Dalvik cache, and rebooted again. Still wouldn't pass the booting process. I cleared everything a second time and even reinstalled the update.zip (which for some reason appeared as update.zip.zip in ClockworkMod Recovery v5.8.2.7... I'm wondering if that caused some issue). Still no progress. Eventually, out of frustration, I began playing around with random settings within Clockwork Mod Recovery and tried backtracking a few steps computer-side in terms of the installation process, and somewhere along the way I've really F'd things up.
And here's the current situation.
Now, whenever the phone restarts the white HTC splash comes up, followed very quickly by a black screen which flickers momentarily, and then immediately jumps to ClockworkMod Recovery (v5.8.2.7).
Whereas earlier today both fastboot and adb recognised my device, now only fastboot will. I can't get anything to appear in the adb device list anymore. I'd prefer it if people didn't immediately scream, "DRIVER ISSUE!" considering adb worked for half of the day so it seems relatively unlikely to me that that's the problem.
My computer itself won't recognise that my phone is plugged in (probably because there's no OS anymore by the seems of things). I've tried two USB cables to no avail (the first worked earlier on this afternoon, so that shouldn't be an issue).
Within the 'choose zip from sdcard' section of ClockworkMod Recovery I can choose from (other than all of the files that were already in there):
CWN-SuperSU-v0.87.zip
update.zip.zip (the double file extension really bugs me)
'mount USB storage' within ClockworkMod Recovery gives me an erroy reading, E: Unable to open ums lunfile (No such file or di...) (runs off the screen, although presumably it just says no such file or directory exists).
I can't think of anything else that's relevant or would help troubleshoot this issue. If you need anymore info please just let me know and I'll do my best to supply it (you may have to lead me through the data acquisition process, however). I'm really hoping the phone isn't completely bricked because I don't exactly have the money right now to buy a new phone - I'm a uni student who only works part time and I just bought a car a few weeks ago. Bye bye, savings.
Regards,
Scott.
man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?
Want a working phone for now, follow this :
Download this recovery and flash it :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.
Husky34 said:
man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?
Click to expand...
Click to collapse
I flashed SOME .img file, but not one called 'boot.img'. Can't remember when, unfortunately. If you find the youtube video I mentioned I followed that exactly.
No recovery unfortunately. I saw no point given that the phone was almost unusable in any form prior to me getting Cyanogen installed (it was constantly and randomly rebooting). Probably a mistake in retrospect.
Version 10.2, by the way.
Mr Hofs said:
Want a working phone for now, follow this :
Download this recovery and flash it :
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.
Click to expand...
Click to collapse
Can you walk me through it step-by-step. Again, I'm a total noob to this and I DON'T want to stuff this up again. Is the fact that adb (or my PC in general) isn't recognising my phone going to make this difficult? I mean how am I meant to copy anything to the SD card if I can't access it through windows explorer or via adb push?!
You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps
Mr Hofs said:
You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps
Click to expand...
Click to collapse
This seems to work at first - instead of jumping into ClockworkMod Recovery, after flashing the image file you gave me, it jumps into a new recovery mode. But after rebooting and going into recovery mode again it's back to ClockworkMod Recovery (I made sure to clear the cache).
You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !
Mr Hofs said:
You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !
Click to expand...
Click to collapse
Oh. Well it looks different the first time I boot into recovery versus the second time (PhilZ Touch 5 with a distinct purple background the first time, but the second time it goes back to a black background with blue text).
Not really sure how to proceed from here. Battery is dropping fast (9%) despite being plugged in, so I'm worried if I don't fix this ASAP it'll be forever FUBAR.
The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
If you use Fastboot flash recovery command the old one is gone.....can't come back like that !
Mr Hofs said:
The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
Click to expand...
Click to collapse
Mr Hofs, you sir are a gentlemen and a scholar! I have managed to get back to the initial bootscreen for Cyanogen mod. AND SUCCESS! IT JUST PASSED THAT SCREEN AS I WAS TYPING!
I am indebted to you, you glorious man! Thank you so very much I'll keep you guys posted (for better or worse)!
Hope it will be fine. I will keep an eye out here
Mr Hofs said:
Hope it will be fine. I will keep an eye out here
Click to expand...
Click to collapse
So I tried updating the camera (?) as a suggested update after getting back into my phone, and it's already stuffed up again. It rebooted and said that root access has possibly been lost. What's happening now?
Doesn't appear to be a big issue for now, actually. Reset, not caused any problems since then! Managed to get google apps working, and downloaded a bunch of the apps I need All's well!
Thanks one again!
Alright ! Hope i don't see you here again
Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?
darule_2011 said:
Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?
Click to expand...
Click to collapse
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA
Mr Hofs said:
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA
Click to expand...
Click to collapse
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
Radio-0-19as.32.09.11_2
As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....
Mr Hofs said:
As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....
Click to expand...
Click to collapse
uh oh, that doesn't sound good for me...I don't have the XL version, just the one X. Will that matter? Did I flash this baby using files for the XL when I should have used something else?
No you don't read well. You have the HTC one XL (EVITA) and this forum is for the ENDEAVORU HTC one X international version.
We here have the quad core and you there have the dual core phone !

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk

Categories

Resources