The .629 update has been nothing but a headache. All I am trying to do is flash the new stable CM 7.2 mod on a D2G running a rooted version of .629. I constantly get stuck at the "M" boot logo then because of the locked bootloader, have no choice but to .sbf again and start the process all over. It's definitely becoming a hassle!
So I ask are any of these thing possible:
Flashing CM 7.2 from a rooted .629
Restoring a Nandroid backup from earlier (a CM 7.1 nightly that ran fine)
Not having to re-do the whole .sbf process EVERY TIME something goes wrong with the boot process.
I've searched up and down but I have just run out of patience. Any help is GREATLY appreciated.
Sincerely, exasperated.
If you're installing CM7 from the official Cyanogenmod site, that's exactly what you are doing wrong.
Repeating this for the 52nd time: official stable builds of Cyanogenmod 7 available from the official Cyanogenmod site are made for 2.4.x firmware and are incompatible with 4.5.x and its kernel.
You must be on 2.4.x to run official CM7.
Related
Howdy folks, it appears that I've run into a bit of a hurdle playing with my transformer.
-----------------------------------------
Problem:
Stuck Boot (static "ASUS" logo, with nvidia logo in bottom right and "unlocked" in top left)
-(rebooting into bootloader and recovery is possible)
-----------------------------------------
Background Steps:
1. device got the 4.2.2 OTA from ASUS and is running the 10.6 bootloader
2.performed 4.2 unlock as per ASUS instructions
3.loaded TWRP 2.5 (4.2 version)
4.did a full wipe within TWRP (except SD)
5.installed stable release 10.0.0 =
6. wiped cache and dalvik
7. rebooted
------------------------------------------
I figured this was a problem with the kernel (similar symptoms before on previous devices) so i went into fastboot and loaded the boot.blob from the cm zip. - It had no effect!
I then wiped and tried again with 10.1 (nightly), again updating kernel - It had no effect!
Getting nervous, i flashed a rom based on stock 4.2 (kernel flash was required) -It's working but not what I want to end up with.
-Can you folks help me out?
Any help is appreciated
As far as I know the this [OFFICIAL][4.2.2][TF300T][NIGHTLIES] CyanogenMod 10.1 for TF300T does not work with the 4.2 bootloaders, even though it's 4.2.2 it needs a 4.1 bootloader like 10.4.2.20.
There is an experimental build for the 4.2 bootloaders here [ROM][4.2.2][CyanogenMod 10.1 Unofficial][TF300T(G) with BL 4.2][2013-05-09], if your using twrp 2.5.0.0-4.2 you should have JB 10.6.1.15.3 bootloader as twrp 2.5.0.0-4.2 on JB 10.6.1.8 has a split-screen issue.
As far as I know, the official CM10 and CM10.1 (including nightlies) are still not compatible with the ASUS new 4.2 Boot loader. You have to wait a little while for the official CM10.1 maintainer to catch up.
However, there is an unofficial CM10.1 that can work with your current 4.2 bootloader, look here: http://forum.xda-developers.com/showthread.php?t=2252990
would you recommend downgrading to 4.1 to use the stable release, or should is it safer to just stay with what i got til they decide to make an official cm release that'll work with it?
n00b1c1d3 said:
would you recommend downgrading to 4.1 to use the stable release, or should is it safer to just stay with what i got til they decide to make an official cm release that'll work with it?
Click to expand...
Click to collapse
It is safer to stay. Messing with recovery, fastboot and bootloaders is risky business. Although, it may work, there is also a chance you might brick your tablet when done incorrectly. Not that I doubt your abilities. It's just that we are seeing an alarming rate of bricked TF300T being reported in the forum. Better wait for a much safer version of TWRP recovery.
EDIT: However, if you have NVFlash backup of your tablet, downgrading and bricking won't be much of a problem.
Roger, i'll stay with 4.2, maybe i'll try that experimental 4.2 one.
Hi,
this is my first post, but it's been a while that i'm playing with this phone and I looked for solutions but could't find.
I smoothly managed to flash PAC ROM 4.3 (stable version) following these instructions and used it for a while without any problem. Then I decided to take the next step to move on to some custom KitKat ROM. I did a nandroid backup and I tried to install the kitkat android 4.4 Cyanogenmod 11 but i'm always stuck at the cm logon screen.
I did flash the boot from ROM.zip as I am S-On.
My hboot is 3.01
What am I missing? This is where my knowledge ends. Is it about kernel? (as I am trying to go to a 3.4 kernel from a 3.0 kernel. Any help is appreciated. Thanks!
So I have been reading but still confused. I am running validus 5.2 on my maxx HD. I am assuming I have a jb bootlaoder. I have philz touch 6.48.xx on my phone. I have tried to install validus 6 on my phone but I keep getting a status 7 error on my phone and it will not flash. I am thinking maybe I need to go back to stock and update to kk. Maybe I am wrong, I don't know. I am confused a bit on what I should do to flash to the new kk update on the custom ROMs. Any input is appreciated!
Update, I have searched and tried other methods to get rid of the status 7 error. I have unzipped and deleted the assert, get prop lines. I was able to flash validus 6 but unfortunately, it just sits on boot image. Any other ideas I can try?
dolfns99 said:
Update, I have searched and tried other methods to get rid of the status 7 error. I have unzipped and deleted the assert, get prop lines. I was able to flash validus 6 but unfortunately, it just sits on boot image. Any other ideas I can try?
Click to expand...
Click to collapse
if you have a xt926 you can follow this link to guide you to KK and you can install new roms afterwards.
I appreciate the help. I so want to make sure I understand, I am already rooted and unlocked, running validus 5.2 on my phone. So I still need to flash back, reroot, reunlock and upgrade to KK before trying to flash a KK custom ROM? is: CM11, validus 6?
Well after reading the other post numerous times, I think I will just start from scratch!!! Happy flashing to me. Its been a good year since using rsd but I'm sure I can follow directions!
Hey guys, I Know this phone is old but please help me
I was using official 2.3.5 ROM and it was getting old so I thought to root and install an ICS Rom so i rooted and installed MIUi ICS ROM (http://forum.xda-developers.com/showthread.php?t=2029969) it was really nice and i thought to install Aurora Rom(http://forum.xda-developers.com/showthread.php?t=1492957) and it was Awsome! so i got into installing new ROMs and i was installing new ROMs almost every week and one day i saw CM 11 KitKat ROM for Huawei U8800 and I wanted to install it but before that i had to install Ble-Part Partition (http://forum.xda-developers.com/showthread.php?t=2615712) i flashed it succesfully and i installed the 2.2 version after that i flashed CWM 6.0.4.6 and i installed KitKat CM11 without any problems!
After some time using it for some time i thought to go back to Aurora as CM 11 was a little buggy and Aurora was the most stable ROM but as i was installing Aurora, i accidently formatted Boot instead of formatting System and without realizing it i flashe Aurora which flashed very quickly rather unexpectedely, and when i rebooted a blue screen appeared. I (surprised) installed official 2.3.5 ROM via dload and when it had installed the phone went into bootloop and i performed a factory data reset and it booted normally. But when i rebooted the phone again again it went to bootloop again. So i installed official 2.2 ROM and it installed succesfully and it never bootlooped in 2.2 ROM. But i wanted to install Aurora but it needs a .35 kernel and whenever i install 2.3.5 it keeps on bootlooping and i cant root it, though i can root 2.2 ROM easily and install .32 ROMs but they are quite old and I want to install ICS, JellyBean or KitKat Rom, which unfortunately i cant
Just in case you would be wondering i have tried many methods to go back to stock partition and none of them works and i have 1.8 GB storage! I have read that distorted partition can cause bootloops on 2.3.5 ROM so if anyone can help me to fix this problem, ill be very grateful as this is a very important phone to me!
And if you have any questions please ask!
Hello,
I keep trying to update to the latest nightly to get cyanogenmod 12 on XT1302. However they don't work. I get weird scan lines, even during the boot logo and animation. Everything is slow and unstable. During installation it always says root access possibly lost, fix, yes or no. Thankfully I have a working backup, but it's stuck on an old 2014 cm 11 snapshot and I want to upgrade
I suspect there is a problem with gapps since I get incessant "X app has stopped working error" messages and it's always a google service. However I do not know what the procedure is. I downloaded the cm12 gapps and flashed them after flashing the nightly as said in faq but it doesn't seem to work. Sometimes even Trebuchet stops working, making the phone totally unusable.
Any help would be greatly appreciated. :good:
Are you running with a lollipop bootloader? I think the latest CM12 requires it.
audit13 said:
Are you running with a lollipop bootloader? I think the latest CM12 requires it.
Click to expand...
Click to collapse
I've been googling this and I think you have correctly identified the issue. If I install the lollipop bootloader, will I be able to go back to my cm11 backup in case of an emergency?
Just to confirm, to update the bootloader, you have to flash the brazil lollipop rom and it should work?
If you unzip the stock ROM, the bootloader is the motoboot.img file.
I don't think you need to flash everything, just the bootloader file. If that doesn't allow you to use CM12, you may have to restore your CM11 nandroid and then flash CM12.