Ok so my m8 from Verizon which has an unlocked bootloader, s-off, and is rooted with TWRP flashed and working but is unable to flash roms. I first tired to flash ViperONE but it said it failed with a status reason 7, ok thats fine lets reboot to the system, oh wait it's stuck on the white background green htc text logo. so I'm able to RUU back to stock and try to install cleanrom 1.0, failed, ok lets reboot back to system, oh wait stuck again, had to RRU back and now I don't know what the hell is going on with my phone. root checker verified root, when i boot into bootloader it says its unlocked and s-off, why can't i flash roms?
I did the weaksauce temproot and firewater exploit to get s-off.
Did you perm root?
Bellypock said:
Did you perm root?
Click to expand...
Click to collapse
Yea I did, so I uninstalled just to be safe and now when I try to reflash supersu.zip through recovery it flashes ok, but then when I boot back into the OS superuser is not installed.
ok im posting back becuase the issue has been resolved. I guess I had a corrupted copy of twrp because I flashed Philz touch recovery and everything flashed perfectly.
nfrederick said:
ok im posting back becuase the issue has been resolved. I guess I had a corrupted copy of twrp because I flashed Philz touch recovery and everything flashed perfectly.
Click to expand...
Click to collapse
I am still having the same issue. I can't flash any ROM. I get the Status 7 issue when flashing ViperOne. I have tried TWRP, CWM, and Philz, and I can't flash a ROM with any of them. How are you flashing your Recovery? I am wondering if flashing Recovery using Flashify is part of my problem. I this point, I am searching for any answer to this problem. I have been trying to flash a ROM since April 26th. Let me know. Thanks.
Rob
Related
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
hrrsncrawford14 said:
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
Click to expand...
Click to collapse
Had that happen to me. But just had to flash a kernel for it to boot properly. Everything fine after that.
Sent from my HTC One X using Tapatalk 2
THANKS!!! I have it working now thanks to the suggestions! :laugh::laugh:
DvineLord said:
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
Click to expand...
Click to collapse
glad u got it working again. i would recommend doing s-off so you don't have to flash boot.img separately anymore.
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
utdps said:
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
Click to expand...
Click to collapse
Did you flash boot boot.img?
Crypto66 said:
Did you flash boot boot.img?
Click to expand...
Click to collapse
I've narrowed down the issue to the install of CleanROM failing. This may be to twrp 2.5.0.0 but as I've said, earlier versions such as 2.3.3.0 aren't responding to touch for some reason. I don't think 2.5.0.0 is my problem though. I can see it if it didn't wipe properly, but the install is failing due to I/O errors.
But yes, I have tried flashing boot.img. twrp tells me I don't have an os when I try to reboot though, so that's the issue.
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Crypto66 said:
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Click to expand...
Click to collapse
Fix permissions won't work without a rom installed. It fails. And from what I understand anyways, fixing permissions is mostly for apps anyways.
Problem solved. Everyone make sure to use TWRP 2.3.3.1 and only that exact version. Older has touchscreen problems and newer has install issues. Man, this stuff can be frustrating at times.
That's not exactly true. Older versions work just fine, I'm using version 2.2 and it has never failed me.
Older versions aren't working for you because you have a newer touchscreen firmware, you would need to downgrade your touchscreen firmware in order to have touch response. For the same reason, you would not be able to run aosp roms until downgrading. Just thought I'd clear that up.
Sent from my One XL using XDA Premium
Hi
At the weekend I tried to update my TF300T from CM10.1 to CM10.2. That didn't work as I ended up in a boot loop. Then I thought, maybe I need to flash the latest system blob.
So I did that, only to find that I then couldn't install anything from zip or sd card as the recovery would not mount anything at all. Still got fastboot, so I've tried TWRP 2.6. TWRP 2.5, TWRP 2.4 and CWM, none of them will mount anything at all.
So I find myself with stock ROM, but no way of rooting or installing any custom ROMs.
I'm sure I've made a bloop somewhere, so all suggestions to resolve welcome!
Thanks
Rob
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
aarsyl said:
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
Click to expand...
Click to collapse
That was the tip I needed - I knew I had the right bootloader but I had downloaded the wrong TWRP (I had flashed the JB version instead of the 4.3 version). Doh!
Now flashed CM10.2 and is running Android 4.3. CPU-Z tells me I'm rooted though at the moment I can't get any root apps to work with SuperSU. I'll leave that for another day!
Rob
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
qabi said:
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
Click to expand...
Click to collapse
Do you have Ville (S4) or Ville C2 (S3) model?
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville/philz_touch_6.19.3-ville.zip
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
PLS check if you have S3 or S4
LS.xD said:
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
Click to expand...
Click to collapse
Thanks for your suggestion.
Actually I don't know. I think only one HTC One S was ever in my market (Denmark).
In the meantime I succeeded installing the TwistedKat ROM and have it running now.
Does anybody know of a tutorial for resetting to stock ROM? (Just in case I want to revert).
-qabi
Unable to enter clockwork recovery?
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
qabi said:
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
Click to expand...
Click to collapse
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
Which recovery do you use? Are you S-OFF // SuperCID // HBOOT 2.15??
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Rapier said:
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Click to expand...
Click to collapse
Rapier, can you explain this? A while back I loaded TWRP (S-ON) then loaded one of the CM series (either 11 or 10, can't remember). Then after I flashed boot.img, I was stuck in boot loop with HTC/red letters.
The reason I was asking what he did was I never did get to stop the boot loop myself. I paid to get it fixed, but I would like to know what I should have done to fix the boot loop after flashing the boot.img and having the problem. Seems like a lot of people get this so, so would be nice to know.
I was basically following everything listed on a web page and everything was working. Unlocked boot loader, SuperSU, TWRP etc... the last thing I did was flash the boot.img and then the problems occurred.
As far as the double try for CWM, I am S-OFF, 2.15 and I noticed it happens every now and then. I don't have this issue with TWRP at all.
It is hard to say why, apparently you did all right. What I can think off is a bad download or a bad flash or you could have used a wrong TWRP version. Also that ROM you have tried could have issues. It is very hard to know why without some logs that shows what went wrong
Sent from nowhere over the air...
LS.xD said:
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery -->
Click to expand...
Click to collapse
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
qabi said:
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
Click to expand...
Click to collapse
I think so. I am running the latest CWM and never had problems before this.
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
JustinBieber said:
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
Click to expand...
Click to collapse
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
robbham78 said:
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
Click to expand...
Click to collapse
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
charesa39 said:
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
Click to expand...
Click to collapse
Thanks guys, I didn't know everything had to be stock! plus I found out that xposed will also break the ota
There's an OTA help desk sticky thread in general that tells you everything you need to know
Sent from my Nexus 5 using Tapatalk