Fellas, this is kind of weird.
I installed CromiXenogenesis over stock 4.2.1, then downgrade to stock 4.1.1 and installed CM 10.1. Then upgrading again to stock 4.2.1 (wich by the way didn´t boot) and installing again CromiX.
Obviously, during those changes, I chaned also the twrp according to 4.2.1 or 4.1.1 as necesary.
The problem is this. After going back to cromix, I installed the twrp for 4.2.1 but the screen it´s split in two halfs horizontally! Yes, showing the same up and down and making almost impossible to navigate (wich I achieved very carefully).
So, the question is: somebody could help to fix this problem with showing the screen split on twrp 2.6.0 for bootloader 4.2.1?
Thanks in advanced. Maybe one of this days take a pic so you can see
Use twrp 2.5.0.0 -4.2!
Sent from my sensational HTC Desire C
noahvt said:
Use twrp 2.5.0.0 -4.2!
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Hey man, the problem has been since I was on twrp 2.5.0.0 for 4.2.1
Now I´m on twrp 2.6.0.0 for 4.2.1 and I´m going to flash 2.5.0.0 and see what happens.
Thanks for the advice :good:
Related
Ive been at it all day but ive yet to install a single custom rom on my tf300t, all of them get stuck at the Asus boot screen. I started of with a stock ics tf300, i installed nvflash then tried to install Cleanrom (first flashing the posted jellybean bootloader) but it didnt work, stuck at boot screen so i tried installing the latest 4.2.1 stock jellybean which installed fine (im using the latest twrp) which i was over the moon about, but then tried both official and unofficial cm10.1 roms both to the same result, stuck at asus boot screen:crying:
I know i must be doing something wrong here but ive tried so many combinations and guides im all out of ideas. Just wondering if anyone has had a similar experience.
JoinTheRealms said:
Ive been at it all day but ive yet to install a single custom rom on my tf300t, all of them get stuck at the Asus boot screen. I started of with a stock ics tf300, i installed nvflash then tried to install Cleanrom (first flashing the posted jellybean bootloader) but it didnt work, stuck at boot screen so i tried installing the latest 4.2.1 stock jellybean which installed fine (im using the latest twrp) which i was over the moon about, but then tried both official and unofficial cm10.1 roms both to the same result, stuck at asus boot screen:crying:
I know i must be doing something wrong here but ive tried so many combinations and guides im all out of ideas. Just wondering if anyone has had a similar experience.
Click to expand...
Click to collapse
I've got the same problem. I think it happened when I tried to flash the rootfs for Archlinux
huntb said:
I've got the same problem. I think it happened when I tried to flash the rootfs for Archlinux
Click to expand...
Click to collapse
the problem for me was the 4.2.1 bootloader, i flashed stock 4.1.1 with fastboot and it downgraded the bootloader from there i was able to install Cleanrom without any trouble, hope it helps:good:
JoinTheRealms said:
the problem for me was the 4.2.1 bootloader, i flashed stock 4.1.1 with fastboot and it downgraded the bootloader from there i was able to install Cleanrom without any trouble, hope it helps:good:
Click to expand...
Click to collapse
Do you have a link to the stock 4.1.1?
Put a pin in this thread.
Boot-freezing when coming from 4.2.1 is because the 4.1.1 bootloader is needed and needed to be reflashed before custom ROMs would work. I just spent 6 hours dicking around the answer was right here.
huntb said:
Do you have a link to the stock 4.1.1?
Click to expand...
Click to collapse
I think you can get it directly from the Asus website
Hi all,
a friend of mine has bought his HTC One S 3 days ago, but after using the all in one toolkit we aren't able to flash anything....Let me explain better:
1) we follwed everything step by step (unloocking and rooting) with success
2) we can mount the sd card from the recovery and copy any ROM
3) when flashing nothing happens, just errors messages (we tried with Viper and TrickDroid)
4) As far as I understood, the boot.img must be flashed AFTER flashing the ROM, not before, right?
The CID phone is vodap102. It was updated to the latest JB before messin'it up....so it has Hboot 2.15. The latest RUU for this Cid is unavailable so we can't back to stock...how can we solve this?? any idea???
Please help us, we're quite desperate :crying:
Thanks a million guys!
P.S. Just noticed that when rebooting from the recovery it say that SuperSU is not installed and can't be pushed to the sd .....if I install it manually says "successful", but that message, when rebooting, appears again...
Try with older version of twrp
Verstuurd van mijn One S met Tapatalk
Solved!
real187 said:
Try with older version of twrp
Verstuurd van mijn One S met Tapatalk
Click to expand...
Click to collapse
Great, after thousand of various recoveries we found the right one (TWRP 2.2.2.0) and we flashed Viper's ROM!
Thank you man!:good:
Where did you get that you have to flash the boot.img after the whole ROM?
Sent from my HTC One S using xda app-developers app
Before or after..doesn't matter
HTC_One_S | S-OFF | DeviantXone | Bubba_3.7b_SoftOV
TWRP v 2.2.2.1 I can't flash Jelly Bean 4.2.2 .zip on HTC one s (s3)
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
Hi, One HTC S (S3) there is no ROM 4.2.2. Did you use the wrong ROM (S4)
mikebryant2807 said:
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
Click to expand...
Click to collapse
As the poster above said, it's good that the 4.2.2 ROM wouldn't flash, or your device would have bricked by now with possibly no means to recover it. Flash a ROM from the S3 Development section.
Can’t Flash Anything on TWRP
Hello,
I’m using a Kindle Fire HD ( 1st Gen ). I rooted it and I’m running on CyanogenMod 9 ,Android version 4.0.4 . I also have TWRP installed,version 2.2.2.1 .I have decided to sell my Kindle Fire but I have to unroot it first. So I booted into TWRP 2.2.2.1 and tried to flash the Kindle Fire update bin file which is zipped. After flashing it, it says “ Error flashing zip ‘/sdcard/update-kindle-6.3.2_DO1E_4110520.BIN.ZIP’”.What should I do to unroot my kindle now? Please Help !!! :crying:
Greetings. Today I wanted to try a KitKat rom on my TF300T (currently on PacMan Rom 4.3), but as I've figured out, I needed a new version of recovery, since I was using TWRP 2.4.4.0.
So I flashed it (version for 4.2 Bootloader, of course), but even though I've tried nearly all versions higher than 2.4.4.0 (for ex. 2.5.0.0 or 2.6.1.0), I was still getting this weird screen (not my picture, but the same problem) and the only way, how to solve it, is to go back on my default TWRP version - 2.4.4.0.
Any help is much appreciated!
spenat said:
Greetings. Today I wanted to try a KitKat rom on my TF300T (currently on PacMan Rom 4.3), but as I've figured out, I needed a new version of recovery, since I was using TWRP 2.4.4.0.
So I flashed it (version for 4.2 Bootloader, of course), but even though I've tried nearly all versions higher than 2.4.4.0 (for ex. 2.5.0.0 or 2.6.1.0), I was still getting this weird screen (not my picture, but the same problem) and the only way, how to solve it, is to go back on my default TWRP version - 2.4.4.0.
Any help is much appreciated!
Click to expand...
Click to collapse
Which stock rom were you on, 10.x.x.x.x.x?
Hello and thanks for quick reply! My stock rom was 10.6.1.8.
Anyway, some really weird thing happened - I downloaded TWRP 2.6.1.0 (again, version 4.2BL), flashed it, went to recovery but whoa - It installed CWM 6.0.4.5...? How is that even possible? And yes, the blob was downloaded from the official TWRP site.
Anyway, with this new "TWRP" (aka. CWM ) I was able to install this KitKat rom, but still I would like to know the solution for the TWRP problem.
But still, truth is, that my stock rom is very old, going to update it then - Thanks!
EDIT: Ah, now I see it, my bad Just found this:
If current bootloader = 10.6.1.8 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.4.4.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device. Also flashing 2.5.0.0-tf300t-4.2 on the 10.6.1.8 bootloader results in a split-screen issue.
Click to expand...
Click to collapse
Yes, update to 10.6.1.27 to use the TWRP.
Sent from my TF300T using xda app-developers app
Hello xda-developers,
My TF300T was becoming very slow in the last few months so I decided to reset it to do a "fresh start". While doing so I would also like to upgrade my ROM. (Im currently running Android 4.1 with CleanRom 3.2).
I'm using the CWM Recovery 6.0.1.3 and would like to upgrade to CyanogenMod 10.2 (Stable - the *.zip file from the CM-website)
By reading several threads there seems to be some problems with current Android Versions and older bootloaders. My question is now:
Can I simply flash the new CM-zip with my recovery (After doing the factory reset) - or is there anything else I have to watch out for?
Thanks for your help in advance!
Nijin said:
Hello xda-developers,
My TF300T was becoming very slow in the last few months so I decided to reset it to do a "fresh start". While doing so I would also like to upgrade my ROM. (Im currently running Android 4.1 with CleanRom 3.2).
I'm using the CWM Recovery 6.0.1.3 and would like to upgrade to CyanogenMod 10.2 (Stable - the *.zip file from the CM-website)
By reading several threads there seems to be some problems with current Android Versions and older bootloaders. My question is now:
Can I simply flash the new CM-zip with my recovery (After doing the factory reset) - or is there anything else I have to watch out for?
Thanks for your help in advance!
Click to expand...
Click to collapse
If you are on a 4.1 ROM you probably need to upgrade your bootloader first.
The easiest way is to flash the latest ASUS stock ROM, then do a factory reset and after that flash recovery and your new ROM.
There are several ways to accomplish this, all covered in detail in several threads.
Sent from my TF300T using Tapatalk
Nijin said:
Hello xda-developers,
My TF300T was becoming very slow in the last few months so I decided to reset it to do a "fresh start". While doing so I would also like to upgrade my ROM. (Im currently running Android 4.1 with CleanRom 3.2).
I'm using the CWM Recovery 6.0.1.3 and would like to upgrade to CyanogenMod 10.2 (Stable - the *.zip file from the CM-website)
By reading several threads there seems to be some problems with current Android Versions and older bootloaders. My question is now:
Can I simply flash the new CM-zip with my recovery (After doing the factory reset) - or is there anything else I have to watch out for?
Thanks for your help in advance!
Click to expand...
Click to collapse
f69m said:
If you are on a 4.1 ROM you probably need to upgrade your bootloader first.
The easiest way is to flash the latest ASUS stock ROM, then do a factory reset and after that flash recovery and your new ROM.
There are several ways to accomplish this, all covered in detail in several threads.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
When you upgrade your bootloader, you will need to upgrade your recovery as well to a -42 TWRP if you are flashing CM10.2 or TWRP 2.6.3.1 for KitKat.
f69m said:
If you are on a 4.1 ROM you probably need to upgrade your bootloader first.
The easiest way is to flash the latest ASUS stock ROM, then do a factory reset and after that flash recovery and your new ROM.
There are several ways to accomplish this, all covered in detail in several threads.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
cmendonc2 said:
When you upgrade your bootloader, you will need to upgrade your recovery as well to a -42 TWRP if you are flashing CM10.2 or TWRP 2.6.3.1 for KitKat.
Click to expand...
Click to collapse
Alright, get Asus Stock from their website, install that, then reset and flash recovery (TWRP - what exactly does the "-42" mean?) After that I'm good to install CM.
Okay, I think I understood - thanks!
Nijin said:
Alright, get Asus Stock from their website, install that, then reset and flash recovery (TWRP - what exactly does the "-42" mean?) After that I'm good to install CM.
Click to expand...
Click to collapse
Oops, got the order wrong: first flash recovery, then do the factory reset using recovery. Don't use the wipe option on the bootloader screen.
There are several versions of TWRP, usually named -ics, -jb and -42.
Don't use the -ics or -jb versions with the new bootloader, but use a -42 version for flashing CM 10.
For flashing CM 11 you need yet another variant of TWRP that is not available from the official download site. Check the CM 11 thread for a download link.
Be careful, using the wrong recovery can result in an expensive brick.
Sent from my TF300T using Tapatalk
f69m said:
Oops, got the order wrong: first flash recovery, then do the factory reset using recovery. Don't use the wipe option on the bootloader screen.
There are several versions of TWRP, usually named -ics, -jb and -42.
Don't use the -ics or -jb versions with the new bootloader, but use a -42 version for flashing CM 10.
For flashing CM 11 you need yet another variant of TWRP that is not available from the official download site. Check the CM 11 thread for a download link.
Be careful, using the wrong recovery can result in an expensive brick.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Ah okay - but this leaves another question: Why exactly do I need the Asus ROM when I already have a 4.2 recovery? Shouldn't Cyanogenmod 10.2 take care of the bootloader then?
Thanks for your help!
Nijin said:
Ah okay - but this leaves another question: Why exactly do I need the Asus ROM when I already have a 4.2 recovery? Shouldn't Cyanogenmod 10.2 take care of the bootloader then?
Click to expand...
Click to collapse
No, CM does not include a bootloader. That is only included in the stock ROM.
That bootloader runs early before the CM Linux kernel is loaded.
The "4.2" recovery only means that it works with the updated bootloader ASUS introduced with the Android 4.2 update. Sorry, I know it is confusing. Thank ASUS for giving us all those incompatible bootloader versions.
Sent from my TF300T using Tapatalk
f69m said:
No, CM does not include a bootloader. That is only included in the stock ROM.
That bootloader runs early before the CM Linux kernel is loaded.
The "4.2" recovery only means that it works with the updated bootloader ASUS introduced with the Android 4.2 update. Sorry, I know it is confusing. Thank ASUS for giving us all those incompatible bootloader versions.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Okay, this makes sense (kind of). I think I know everything now - I'l try to update when I get a little free time. Thanks for your help!
Hi,
i'm using the official CM 11 on my XT925 and pretty much installed every new Nightly - never had any serious Problems, not even with Bluetooth (i get no Track in the Display, but at least it works ).
Since the 01.07.2014 Nightly i can't install the Nightlys anymore, because it wants a KK/ Kernel 3.4 compatible Bootloader. First, i flashed the new TWRP 2.7.1.0. Didn't work, very strange Problem (see below). So then i tried the new CWM 6.0.4.9. Also didn't work... same error message as with CWM 6.0.4.4 (which I used until now) - "no KitKat Compatible recovery detected". So I tried philz touch recovery. Also doesn't work.
Now i'm back with the 30.06.2014 Nightly.
Now the strange part: TWRP didn't recognize any touch inputs at all, I had to hard-reboot the phone. Also Philz touch recovery didn't recognize any touch inputs. CWM 6.0.4.4 hat the "Swipe-Touch" thingy, which I used, but it seems that CWM 6.0.4.9 also doesn't recognize any touch inputs! I can't swipe.
So the big questions are: What the hell have I done wrong, that no Recovery is not recognizing any touch inputs anymore?! Flashed it with fastboot, everything looked ok, only got an "ERROR: could not get pipe properties", but it flasehd it and it worked - apart from the touch.
It wouldn't even be such a big "bother" if the new CWM could install the new CM Nightly... Am I really stuck with 30.06.?
greetings,
David
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So, to install new nightlies we have to flash the KK OTA first, right?
TYG
pbosio said:
So, to install new nightlies we have to flash the KK OTA first, right?
Click to expand...
Click to collapse
Take a look HERE.
If I were you I'd wait for the official kk bootloader....if you read the previous post the method being used is risky for our model.
Sent from my RAZR HD using XDA Free mobile app