Related
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!
elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.
Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.
I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp lets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?
taurius1 said:
I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp ets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?
Click to expand...
Click to collapse
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it
a box of kittens said:
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it
Click to expand...
Click to collapse
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.
taurius1 said:
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.
Click to expand...
Click to collapse
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
I've done that. But just to be sure, I'm gonna try a fresh download once more. ^_^ Brb 10 minutes.
Curious what happened, as I think I may be having this same issue.
a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
OOh that worked. Thanks a ton! ^_^
Probably was a bad download all three times I tried to download it before. :/ (I should probably buy a lottery ticket now :/ )
Now, Let me try installing my rooted stock rom. :3
Almost Same Problem
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?
lucasjohnsond said:
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?
Click to expand...
Click to collapse
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.
taurius1 said:
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.
Click to expand...
Click to collapse
Actually, I just remembered. If you're on the new hboot, you should be flashing the boot img through fastboot, and then installing the zip. Since you've been doing all that anyway, perhaps its time to just wipe everything and start over, step by step.
> download cm 10.0
> check md5 to make sure it's proper
> extract boot.img and flash it via fastboot
> reboot into recovery.
> wipe system, cache, dalvik cache, and factory reset
> transfer the rom and flash it via recovery
:/ I'm no expert here, but that's what I'd be doing now.
I've been updating Cyanogenmod with the Nightlies. Since the March updates, I've not been able to install gapps, even with the newest version. I've Googled on this, and I've tried everything I could find. I've made sure I had the latest version of gapps, I've wiped the cache and the Dalvik cache, and I've mounted the system partition before installing the zip. I've even done a factory reset. At one point, I was so far gone with all the different things I was trying that I had to revert back to a stock setup.
When I install the gapps zip file in Clockworkmod, everything looks fine. No errors or anything. It goes through the install process, and it completes, but when I reboot, I have no Google Apps installed.
I have a 4g Xoom (Verizon).
The different CWM versions I've had this issue with have been:
cm-10.1-20130309-NIGHTLY-stingray.zip
cm-10.1-20130311-NIGHTLY-stingray.zip
cm-10.1-20130315-NIGHTLY-stingray.zip
The latest gapps version I've been trying to install is:
gapps-jb-20130301-signed.zip
Thank you.
I have xoom wifi. the version of gapps I have is:
gapps-unified-jb-20130220-signed.zip
it should be somewhere in the portal as that's where I downloaded from. see it may work for you too.
hadji369 said:
I've been updating Cyanogenmod with the Nightlies. Since the March updates, I've not been able to install gapps, even with the newest version. I've Googled on this, and I've tried everything I could find. I've made sure I had the latest version of gapps, I've wiped the cache and the Dalvik cache, and I've mounted the system partition before installing the zip. I've even done a factory reset. At one point, I was so far gone with all the different things I was trying that I had to revert back to a stock setup.
When I install the gapps zip file in Clockworkmod, everything looks fine. No errors or anything. It goes through the install process, and it completes, but when I reboot, I have no Google Apps installed.
I have a 4g Xoom (Verizon).
The different CWM versions I've had this issue with have been:
cm-10.1-20130309-NIGHTLY-stingray.zip
cm-10.1-20130311-NIGHTLY-stingray.zip
cm-10.1-20130315-NIGHTLY-stingray.zip
The latest gapps version I've been trying to install is:
gapps-jb-20130301-signed.zip
Thank you.
Click to expand...
Click to collapse
hadji369 said:
I've been updating Cyanogenmod with the Nightlies. Since the March updates, I've not been able to install gapps, even with the newest version. I've Googled on this, and I've tried everything I could find. I've made sure I had the latest version of gapps, I've wiped the cache and the Dalvik cache, and I've mounted the system partition before installing the zip. I've even done a factory reset. At one point, I was so far gone with all the different things I was trying that I had to revert back to a stock setup.
When I install the gapps zip file in Clockworkmod, everything looks fine. No errors or anything. It goes through the install process, and it completes, but when I reboot, I have no Google Apps installed.
I have a 4g Xoom (Verizon).
The different CWM versions I've had this issue with have been:
cm-10.1-20130309-NIGHTLY-stingray.zip
cm-10.1-20130311-NIGHTLY-stingray.zip
cm-10.1-20130315-NIGHTLY-stingray.zip
The latest gapps version I've been trying to install is:
gapps-jb-20130301-signed.zip
Thank you.
Click to expand...
Click to collapse
Not sure if this is an option for you, but have you tried running gapps-jb-20130105-EOS-XOOM-ONLY.zip?
atloops said:
Not sure if this is an option for you, but have you tried running gapps-jb-20130105-EOS-XOOM-ONLY.zip?
Click to expand...
Click to collapse
I did try this, just for the sake of trying something as I am having the same issues as the OP.
I flashed the latest nightly cm-10.1-20130330-NIGHTLY-stingray.zip on my Xoom and then tried the EOS version of GApps. It just bootlooped numerous times. I flashed the ROM, then flashed GApps. I cleared cache/data/dalvik with no luck, it just brought me back to recovery.
Any ideas? I know it is a nightly, so I am not too worried about it. I am just playing around.
You should try the new unified gapps for Cm, the link is listed in the OP of the cm 10.1 thread. Also, if you are using cwm recovery, try twrp. Your recovery could be causing issues
Sent from my Xoom using xda premium
Thanks! I will give that a try when I get home. Went straight to the CyanogenMod site to get GApps so I missed that.
Well, I made a very simple mistake. I only read the directions partially, assuming everything would work like flashing my phone or Nexus 7. I wiped data, wiped dalvik, installed the ROM and then installed GApps. I booted my Xoom and of coarse, even with the unified version of GApps, it still did not work.
I repeated the process but did not install GApps. I let the device boot and then went back in to recovery. I flashed GApps and rebooted and it works perfectly. I did not try another version of GApps this time.
Lesson learned.
groggie said:
WelI, I made a very simple mistake. I only read the directions partially, assuming everything would work like flashing my phone or Nexus 7. I wiped data, wiped dalvik, installed the ROM and then installed GApps. I booted my Xoom and of coarse, even with the unified version of GApps, it still did not work.
I repeated the process but did not install GApps. I let the device boot and then went back in to recovery. I flashed GApps and rebooted and it works perfectly. I did not try another version of GApps this time.
Lesson learned.
Click to expand...
Click to collapse
Download Google appstore zip file by itself.. After flashing gapps, flash the appstore by itself as well.. Worked for me
Latest Nightly issue Camera+Gallery
I'm using the 20130609 nightly in my Everest, but re-flashing the Unified Apps from CM 10.1 official thread doesn't work. On the 20130601 nightly it works like a charm!.
Any help would be appreciated.
P.s: As an advice, I tried formatting system partition in CWM, reinstall nightly and gapps. All works fine now!
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
visclo49 said:
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
Click to expand...
Click to collapse
stop using toolkits, learn something for a change
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I'm having a problem when I flash the CM12 ROM.
While having CM11.x I go to Settings and navigate to "CM Updates" where I can see a list of Nightlys and stable CM releases. When I install the new CM update this way everything seems to go okay, however This may be normal, I get a message from CWM "Possible Root loss, fix?",.. I select yes and it boots up, runs through the whole "Android is upgrading" message and all. When the phone is finally ready for use I get spammed with millions of messages saying "Application has stopped" and they will pop up infinity in less then a second. I have to hold power and tell the phone to reboot into recovery so I can resotre from backup.
I also downloaded the ROM from CM website and flashed it using "ROM manager". I get the exact same issues sadly.
What could be the problem?
Is CWM not compatible with lollipop?
Do I need to run a factory reset and wipe my phone before flashing?
I've been fiddling with this all day now. -Sigh-
EDIT:
Should I flash the latest version of "gapps" ?
You're going to need to do some reading. Installing LP over KK thru a nightly isn't going to work. You'll need LP Gapps for starters and you'll need to go into recovery and do some wiping before you flash. There are some good LP roms here: http://forum.xda-developers.com/lg-g2/development with full installation procedures. Also, most are using TWRP for recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 You may also need to flash a different baseband but you'll find everything you need in the general development section. Also, next time you really should post your questions in the Q&A section. Anyway, do some reading and you'll be good to go! :good:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Traceguy said:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Click to expand...
Click to collapse
First let me apologise, I see that you are in Q&A and I'm the one that doesn't know which forum he's in.
Next, well I've used both CWM and TWRP. Personally I prefer TWRP but as long as you're on the latest and greatest you should have no problems from what I've read. And if you do just flash over to the other and see if it fixes the problem. I've been using the 10D radio for quite some time now and it works for me.
As I go from rom to rom I always do a clean flash, wiping data, system, dalvik and cache. I rarely do a dirty flash but that's just me. As long as you can recover from the occasional boot loop you'll be good. :laugh: