Database Info

[Q] ROM Problem : Stuck on boot logo

This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?

confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth

CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.

confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102

I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.

k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop

confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.

k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.

Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?

k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout

CWM & CM10/10.1 problem (hung on "The device is unlocked")

Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!

cyaneo said:
Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!
Click to expand...
Click to collapse
What is your bootloader version? Si it fresh enough?

Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!

cyaneo said:
Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!
Click to expand...
Click to collapse
Yeap,.. Bloody bootloader
No problem

Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?

cyaneo said:
Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?
Click to expand...
Click to collapse
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1

szulco said:
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1
Click to expand...
Click to collapse
- now I formatted data and system and also wiped all possible parts
- flashing cwm 6.0.2.3 and installing asus stock ROM (ww_epad-user-10.4.2.20), reboot
- cannot access cwm recovery, so I reeflash it with fastboot method
- access cwm recovery and install latest 10.1 nightly, reboot, done.
Thank you so much!

I'm having the same issue.
I bought my TF300T when if first came out. I finally decided to play around with it.
I unlocked it with the Google Play app.
Used fastboot to push the latest ASUS JB4.2 firmware (US_V10.6.1.8)
My bootloader says: (1.00 e) released by "US_epad-10.6.1.8-20130225" A03
I rooted and installed TWRP v2.4.4.0
Everything is working fine for me and I have taken a solid backup, so I'm able to restore back to that when things fail.
I loved using CM7 on my phone, so I wanted to try CM10 on my tablet.
I have tried installing the stable CM 10.0, and I've tried all of the CM 10.1 Nightlies.
Every single time, the install goes perfectly fine, but when I reboot I just get the plain white Asus screen and then it freezes.
I have tried installing with and without installing the gapps.
Every time I install I do a Factory Reset, wipe the Cache, Dalvik Cache, and System. The only thing I didn't do is wipe Data as I'd prefer not to lose my files. (is that the problem, is the data-wipe required?)
Is there something obvious that I'm missing or a step I left out?
Any help would be greatly appreciated.

I tried doing it again with wiping all my data too...that didn't make a difference either. Still freezes on the white asus screen.

Hi, I just registered to reply, as seems noone did. And Ive been there myself, also with the 10.6.1.8 bootloader. Thats the issue. Cyanogenmod isnt compatible yet with the newest bootloader 10.6.1.8.
I hope it will in the future, Im awaiting it too. Until then I just rooted the stock rom, and using it that way. You could try the CROMI-X rom, but its also stock based, I havent tried it yet, maybe ill give the newest update a try (4.3) which will be available in a couple of days, as I really love their newest boot animation(wich I believe isnt included in the 4.2 version)
Till then, no Cyanogenmod for us with the newest bootloader.....also downgrading is not worth the risk if you ask me,,, even if its possible. So Ill wait for the Cyanogenmod team to update their version to ours.
Advice: dont mess with the bootloader nor the recovery img files. Always read carefully if you wanna change recovery if its compatible with your bootloader. If its not, and you flash it...tada....youre the owner of a cool and expensive brick. Dont wipe data in the bootloader, cuz as I understood reading posts here at xda, it will wipe your entire device, including bootloader...then your kinda screwed. So stick to what you have and let the devs do their work to update their roms for the 10.6.1.8 bootloader...MOST importantly, DONT store your device with the keyboard dock closed...(like a laptop)...your screen will crack eventually.I gathered this info on youtube as well as here, and Ive a friend, who was using the device with the dock till last month like that, had it from last august...result, screen cracked 3 weeks ago...its a design flaw in the transformers, the screen is under heavy pressure while in the keydock..I just got my dock last week,, Im storing it separately, and I never close it, only use it for typing, battery and usb.
im writing all this as I think I wont find this post again to reply if you read it.

[Q] upgarde snaufu...

was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.

What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.

first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off

No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?

I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.

iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.

i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.

i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.

well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.

[Q] Can't Get Rom to Boot

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

[Q]Unable to flash latest cyanogenmod nightly

I am running cm12 nightly of 3rd April and I am using cyandelta to update so that I
Don't have to download 200mb everyday. It was working great until today .
I am unable to flash the latest nightly and it shows error . I even update twrp and tired
Everything please guys help.

CyanDelta is unofficial.
Maybe try flashing the regular zip, it'll probably work.

Elluel said:
CyanDelta is unofficial.
Maybe try flashing the regular zip, it'll probably work.
Click to expand...
Click to collapse
solved it . i just copied the update script from older version of nightly and placed it in the downloaded one

I have had a few issues with latest versions of CM.
First was errors received during the flash process. Was able to get past this a number of ways.
Change bootloader version in update script.
removed bootloader version check line altogether from the script .
Edit line in source for my current bootloader and compiling myself.
This was all find and dandy but with every one of the above mentioned changes to either flash an official nightly or one compiled myself after flashing has gone through without error I am stuck on the "Google" logo after rebooting into system. Have done a quick search and have seen a number of posts like the one mentioned above that after getting past flash errors by modifying update script or in the above case had probably worked because older script was from an update.zip created before the bootloader check had been added by CM after the flash was successful no additional issues had been experienced.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on SD card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "Google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0_r3 for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "Google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "Google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on sd card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0_r3 for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.

chairshot215 said:
I have had a few issues with latest versions of CM.
First was errors received during the flash process. Was able to get past this a number of ways.
Change bootloader version in update script.
removed bootloader version check line altogether from the script .
Edit line in source for my current bootloader and compiling myself.
This was all find and dandy but with every one of the above mentioned changes to either flash an official nightly or one compiled myself after flashing has gone through without error I am stuck on the "Google" logo after rebooting into system. Have done a quick search and have seen a number of posts like the one mentioned above that after getting past flash errors by modifying update script or in the above case had probably worked because older script was from an update.zip created before the bootloader check had been added by CM after the flash was successful no additional issues had been experienced.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on SD card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "Google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0_r3 for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "Google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "Google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on sd card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0_r3 for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=59913506&postcount=3

beekay201 said:
http://forum.xda-developers.com/showpost.php?p=59913506&postcount=3
Click to expand...
Click to collapse
Thanks but the thread is the issue with the bootloader version in the updater script like the op had experienced I am not having an issue at this point but after rebooting into system. At first I thought maybe Kernel as am using my own kernel but same with Stock CM Kernel. Also Nandroids restore and boot without issue so have been using my Nandroid backed up just before installing 5.1 and have flashed test versions of my Kernel just fine. Its just weird that the issue is when booting after a fresh Rom install. Can flash a new boot.img without causing the issue and have done a diff between update scripts just in case something else funny in my update script other than the bootloader version line ans they come back the same.