Related
I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.
I have been holding off from updating to 30O since it came out because of battery issues, however now that 33R is rolling out im trying to install 30O in preparation but am unable to do so. Whenever I hit the "Download Update" button through settings nothing happens, I have tried restarts and cache wipes with no luck. Everything on the phone is still stock.
Any suggestions?
Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.
teh roxxorz said:
Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
I am trying to update via ota not a custom recovery does that make a difference?
teh roxxorz said:
Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
I don't think that's possible; the OTAs are incremental.
Joe-Pk said:
I am trying to update via ota not a custom recovery does that make a difference?
Click to expand...
Click to collapse
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.
teh roxxorz said:
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.
Click to expand...
Click to collapse
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.
dr3amsINdigital said:
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.
Click to expand...
Click to collapse
Well yea. Sorry if my wording was a bit convoluted; but I just see it being a waste of time to overwrite the custom recovery. But also from my experience OTA just goes with stock recovery, so thank you for your input.
Joe-Pk said:
I have been holding off from updating to 30O since it came out because of battery issues, however now that 33R is rolling out im trying to install 30O in preparation but am unable to do so. Whenever I hit the "Download Update" button through settings nothing happens, I have tried restarts and cache wipes with no luck. Everything on the phone is still stock.
Any suggestions?
Click to expand...
Click to collapse
You can download the OTA updates from somewhere like Android Police and flash them manually.
teh roxxorz said:
Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
This is irrelevant.
Joe-Pk said:
I am trying to update via ota not a custom recovery does that make a difference?
Click to expand...
Click to collapse
It makes zero difference.
dr3amsINdigital said:
I don't think that's possible; the OTAs are incremental.
Click to expand...
Click to collapse
It is possible by using the fastboot images from the cyngn site.
teh roxxorz said:
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.
Click to expand...
Click to collapse
Not true.
dr3amsINdigital said:
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.
Click to expand...
Click to collapse
Exactly.
teh roxxorz said:
Well yea. Sorry if my wording was a bit convoluted; but I just see it being a waste of time to overwrite the custom recovery. But also from my experience OTA just goes with stock recovery, so thank you for your input.
Click to expand...
Click to collapse
An OTA can be flashed by stock recovery or TWRP on this device.
Transmitted via Bacon
I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.
Joe-Pk said:
I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.
Click to expand...
Click to collapse
You can manually flash updates while stock.
Joe-Pk said:
I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.
Click to expand...
Click to collapse
dr3amsINdigital said:
You can manually flash updates while stock.
Click to expand...
Click to collapse
Yes you can. Rename file to update.zip and flash through stock recovery. Please make sure you give out accurate information if you're going to answer questions.
Transmitted via Bacon
timmaaa said:
Yes you can. Rename file to update.zip and flash through stock recovery. Please make sure you give out accurate information if you're going to answer questions.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm not sure if you read my post wrong or not, but I said you can manually flash updates while stock. If you did read it correctly and are just complaining that I didn't give a detailed answer with instructions, I wasn't exactly sure of the process, so I left that to someone else. Some helpful information is better than none.
dr3amsINdigital said:
I'm not sure if you read my post wrong or not, but I said you can manually flash updates while stock. If you did read it correctly and are just complaining that I didn't give a detailed answer with instructions, I wasn't exactly sure of the process, so I left that to someone else. Some helpful information is better than none.
Click to expand...
Click to collapse
My sincerest apologies! I completely misread your post.
Transmitted via Bacon
I ended up just flashing manually using files from android police and stock recovery, however the download update button still didnt work even when i was trying to go to 33R. If I get some time ill get around to factory resetting and trying again because as far as i can tell there is no reason for it not to work.
You could always sideload a OTA if you have the zipfile.
Code:
adb reboot recovery
in recovery choose "ADB Sideload"
Code:
adb sideload update.zip
Hello guys,
I wasn't pretty active here for a year but when the latest preview came out it changed. I was wondering that people only mentioned TRWP Recovery to install but not CWM. Does this have a reason? Is CWM not compatible to the L stuff/did the dev stop developing the recovery?
I installed TRWP then but I really don't like it, it takes ages to start and I really just prefer using my volume keys and stuff to navigate through CWM without touch.
Did gave this one a short search but it was a mess finding something.
Thanks for answers.
S3cret said:
Hello guys,
I wasn't pretty active here for a year but when the latest preview came out it changed. I was wondering that people only mentioned TRWP Recovery to install but not CWM. Does this have a reason? Is CWM not compatible to the L stuff/did the dev stop developing the recovery?
I installed TRWP then but I really don't like it, it takes ages to start and I really just prefer using my volume keys and stuff to navigate through CWM without touch.
Did gave this one a short search but it was a mess finding something.
Thanks for answers.
Click to expand...
Click to collapse
Official CWM is antequated. It hasn't even been properly updated to Support Android Jellybean 4.2 (Which was HOW long ago???). The Dev pretty much abandoned it, leaving it to an unruly band of muppeteers to maintain, so I would suggest you avoid Official CWM at all costs
Oh damn, so there is only TRWP left, or is there some other I don't know about yet?
S3cret said:
Oh damn, so there is only TRWP left, or is there some other I don't know about yet?
Click to expand...
Click to collapse
It's *TWRP. And the other one is Philz Touch, based off CWM but not outdated.
Lethargy said:
It's *TWRP. And the other one is Philz Touch, based off CWM but not outdated.
Click to expand...
Click to collapse
The problem with Philz is that it is no longer maintained so although in my opinion, it is much better than TWRP and CWM, it won't support encryption, which L will enforce by default I believe so I would have to say use TWRP
rootSU said:
The problem with Philz is that it is no longer maintained so although in my opinion, it is much better than TWRP and CWM, it won't support encryption, which L will enforce by default I believe so I would have to say use TWRP
Click to expand...
Click to collapse
Confirmed by Phil or is it a feeling?
Primokorn said:
Confirmed by Phil or is it a feeling?
Click to expand...
Click to collapse
Which part?
rootSU said:
Which part?
Click to expand...
Click to collapse
PhilZ won't support encryption and it's no more maintained. TWRP will be the only up-to-date recovery? (don't know about Cannibal)
Primokorn said:
PhilZ won't support encryption and it's no more maintained. TWRP will be the only up-to-date recovery? (don't know about Cannibal)
Click to expand...
Click to collapse
Official support has ended.
http://forum.xda-developers.com/showthread.php?t=2201860
Primokorn said:
PhilZ won't support encryption and it's no more maintained. TWRP will be the only up-to-date recovery? (don't know about Cannibal)
Click to expand...
Click to collapse
Philz doesn't support encryption. Encrypt your phone and see
And as just mentioned above, no more support - so future functionality will not be added.
rootSU said:
Philz doesn't support encryption. Encrypt your phone and see
And as just mentioned above, no more support - so future functionality will not be added.
Click to expand...
Click to collapse
Unfortunate, but these things happen. Oh well.
Lethargy said:
Unfortunate, but these things happen. Oh well.
Click to expand...
Click to collapse
It is. Unless someone has the skills to take over the entire project, we're doomed.
That said, I think L encryption has possibly changed. Not sure TWRP world with latest L encryption yet.
Sent from my Nexus 5 using Tapatalk
So I lost twrp and root, Whats the easiest way to get root back or twrp as I cant get into twrp recovery to try and flash supersu.
SysAdmNj said:
So I lost twrp and root, Whats the easiest way to get root back or twrp as I cant get into twrp recovery to try and flash supersu.
Click to expand...
Click to collapse
You'll probably need to flash a custom recovery via fastboot/toolkit, you can root at the same time or flash a supersu zip once you have your custom recovery.
gsmyth said:
You'll probably need to flash a custom recovery via fastboot/toolkit, you can root at the same time or flash a supersu zip once you have your custom recovery.
Click to expand...
Click to collapse
Dammit, I should of asked first before updating lol. Thanks, I guess I'll have to go that route.
SysAdmNj said:
Dammit, I should of asked first before updating lol. Thanks, I guess I'll have to go that route.
Click to expand...
Click to collapse
Same thing happened to me, but at least its simple enough to sort. Doesn't help if you're not near a PC and can't wait though!
For future reference remember and untick update CM recovery in developer options
gsmyth said:
Same thing happened to me, but at least its simple enough to sort. Doesn't help if you're not near a PC and can't wait though!
Click to expand...
Click to collapse
Yup, gotta wait till this evening.
bombadier said:
For future reference remember and untick update CM recovery in developer options
Click to expand...
Click to collapse
Jeez, missed that as well. Thanks.
Re-Install TWRP through Play Store no PC needed
Cholerabob said:
Re-Install TWRP through Play Store no PC needed
Click to expand...
Click to collapse
But you need root to do that, no?
SysAdmNj said:
But you need root to do that, no?
Click to expand...
Click to collapse
That's right, the TWRP app is really unreliable anyway so don't bother with it. Why don't you just flash TWRP the normal way, with fastboot?
Transmitted via Bacon
Oneplus updated the OnePlus 6's Bootloader and you may ask yourself 'Can i still root?'
The answer is yes. It is easy.
1. At first, your bootloader has to be unlocked
2. Just download the Twrp.img and the Twrp installer from twrp.me, then the latest magisk installer
3. Put the magisk.zip and twrp installer zip into the root of your device and boot into bootloader
4. Now you have to open a new shell or cmd window in your adb folder, then type "Fastboot devices" there
5. If your phone is recognized, then do this command: " fastboot boot .\twrp-3.2.1-0-enchilada.img"
6. The op6 should boot into the TWRP, there type in your pincode, pattern, or what so ever you have. If you get a message because of system modification, click 'Keep read only'
7. Go to 'Install', then flash the TWRP installer zip, then magisk right after it
8. Just reboot and enjoy
The procedure is the same as always. I can confirm it's working because i rooted a few minutes ago
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
iElvis said:
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
Click to expand...
Click to collapse
Forgot the mention that, thanks!
Edit: Screenshots
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Sorry, I thought that would be helpful for people who are worried about root because of updated bootloader.
A Moderator can remove this thread then
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Based on how things have been going so far, people are going to be asking. Just saying.
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
So if I already have twrp and Magisk installed is the method still the same?
Will this update lock the bootloader back?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
joemossjr said:
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
Click to expand...
Click to collapse
Yes I know. I mean, you're right. Thought something like "new bootloader, new confusions". I justed wanted to help people if they're worried of a brick
dgunn said:
So if I already have twrp and Magisk installed is the method still the same?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
Click to expand...
Click to collapse
Don't worry. You can use TWRP and your phone itself as always
Sconny said:
Don't worry. You can use TWRP and your phone itself as always
Click to expand...
Click to collapse
So do I flash the update in twrp?
Must the bootloader be unlocked again?
dgunn said:
So do I flash the update in twrp?
Must the bootloader be unlocked again?
Click to expand...
Click to collapse
No you flash in system via local upgrade
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash with local upgrade, reboot to fastboot, run twrp.img, install twrp, flash Magisk and reboot? No unlocking bootloader again?
If not correct please tell me
Yup that's it
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
BossNexusS said:
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
What were the steps you followed if you don't mind?
Maybe someone will upload the full rom?
anyone tried hiding system updates inside magisk hide ?
it now shows only 224 update (canadian vpn), hence don't know what it will do when you take that route, anyone ?