I decided recently, with the release of towelroot, to root my Transformer. I was having performance problems since the Jellybean update, but the optimizations I installed improved it. There was still some lag though, so I tried to flash a Cyanogenmod 11 nightly. There were no errors from CWM, but the tablet stalked at the bout animation. I tried an OmniROM homemade, same story. I flashed the newest OmniROM nightly, the GApps package listed on the OmniROM thread on here, and the US_epad-user-10.6.1.27.5 kernel, no soap. I can get Windows to detect the tablet when CWM is in sideload mode, but fastboot never connects, so I can't flash another recovery.
Sent from my Droid Ultra
What version of CWM you are using ?
Maybe you should update it via a flashable zip (no need to pc)
And a good advise, always wipe cache & dalvik cache after flashing rom and before reboot.
I'm using 6.0.4.7. I've been using a jump drive plugged into the dock to load ROMs, so I haven't connected directly to the computer for a while. I've wiped cache and dalvik before flashing nearly every time, and after several times.
Sent from my XT1080 using XDA Premium 4 mobile app
Ok if you still have the OmniROM image, try to flash it exactly as follow :
1- Wipe system, data, cache and dalvik cache
2- install OmniRom
3- install gapps
4- install kernel
5- wipe again cache and dalvik cache before reboot
6- reboot
Download links for latest gapps and kernel are in my signature (Geass is the best kernel IMO)
OK, I'll give it a shot. Probably ten minutes.
Sent from my Droid Ultra
Whenever I try to format /data, it says Error mounting /data! Would this be part of the trouble, perhaps?
It's all flashed, but it looks like it hung up during the boot sequence again. I'll let it sit a while longer, and see what happens.
OK, it did absolutely nothing. I haven't worked on it for a while, because between work and the rest of life, I haven't really needed it. It is the same state, though.
travisw495 said:
OK, it did absolutely nothing. I haven't worked on it for a while, because between work and the rest of life, I haven't really needed it. It is the same state, though.
Click to expand...
Click to collapse
Look up buster99's fix. I think that is what you need to do next.
Related
My Wifi-Only US Xoom is rooted with the universal xoom root, and has the EOS-Wingray-60 Rom successfully installed, but everytime I try to download Gapps, this comes up:
How do I fix that?
EDIT: That is no longer the problem. Everytime I flash Gapps now, my xoom ALWAYS gets stuck on the dual core screen after reboot.
Double EDIT: I was too lazy to stock flash it, so I simply wiped everything again, downloaded EOS wingray 60, Then I wiped my cache and my dalvik (Not data), then reinstalled Gapps, and fixed permissions and it finally loads now. Thank ****ing god.
Can anyone help me with this please??
Slayergramp said:
Can anyone help me with this please??
Click to expand...
Click to collapse
Okay
1. Dont use v9 gapps you should always use latest v10.5 is the latest...
2. Check the md5 of the file
3. Wipe cache and dalvik cache
4. Install said gapps
5. Fix permissions
6. Win
Sent from my mind control device
Where's v10.5?
I still need help with this D:
I can get the EOS-Wingray-60 ROM to work, and then I fixed permissions, and then tried installing GApps and it's still (bad)!!!
Slayergramp said:
I still need help with this D:
I can get the EOS-Wingray-60 ROM to work, and then I fixed permissions, and then tried installing GApps and it's still (bad)!!!
Click to expand...
Click to collapse
Go to the eos rom.. There is a gapps link.. Click it and it will take you to all the gapps packages ... Download 10.5 check the md5
Sent from my mind control device
Goo-inside.me/roms/teameos/gapps
Download the most recent EOS gapps from there. The (bad) in your attempted install means the zip is corrupt.
Sent from my MB860 using xda premium
Alright, so my problem continues. I was running stock unrooted ICS, then flashes recovery. Then I wiped data, cache and dalvik. Then I rooted with the Xoom universal root. Rebooted, works fine. Then I went to recovery, wiped data, cache, and dalvik, and flashes eos Rom 60. Rebooted, works fine. Then I went to recovery, wiped data, cache, and dalvik, successfully installed gapps 10.5 for the first time, it wasn't (bad). Rebooted, andddd stuck. After I rebooted in permanately stuck on the dual core Motorola logo thing. What did I do wrong?
You need to flash the GApps file immediately after the EOS rom...no reboot first. This is a must.
okantomi said:
You need to flash the GApps file immediately after the EOS rom...no reboot first. This is a must.
Click to expand...
Click to collapse
When I flash them, is there anything I need to wipe or clear? Or do I leave everything alone?
God Dammit! This is pissing me off!!!!!!!!!!!!!!!!!!!!! It ****ing takes for ever to upgrade back to ICS when I have to flash the ****ing stock of 3.0!!!
I upgraded to ICS, after flashing 3.0, I flashed the R4c Recovery, I did a factory reset, and wiped Dalvik and Cache, then I installed the Universal root (Is there a different root I should use?), then I went back (Still in recovery mode) and did a factory reset, and wipe cache and dalvik. Then I install Wingray-60, then *immediately after* I installed Gapps v10.5!!!! I rebooted and my ****ING xoom is stuck on the dual core screen AGAIN!!!
WHAT THE ****.
Not quite sure what those first few steps were, but boot to recovery, go to mounts and storage and wipe system and cache, then go to the wipe menu and do a data wipe and dalvik wipe.
Then flash ICS and gapps.
Shouldn't have any problems after that unless your Xoom doesn't like ICS for some strange get reason.
Sent from my Xoom using xda premium
I'd post a reply to the official thread, but I still can't as of now due to low number of posts.
So I downloaded S'perience ROM from here:
http://forum.xda-developers.com/showthread.php?t=1888350
Then I tried flashing it as needed. The phone restarts and voila, S'perience. However, I found out that I had lost my root.
Busy Box is installed, but when I checked via Root Checker, it told me that some SU binaries are not present, therefore my phone has lost root.
I tried rerooting my phone and flashing S'perience three times, but the same thing happen. Yeah, I did the usual factory rest, cache and data wipe, etc, and I have no idea why my phone loses root when I flash this ROM.
Can anyone help me?
I just contacted the author of that ROM.
Hopefully they'll be able to help you out
''Evil corrupts the mind of the weak but fails to feed off the mind of the strong''
Hi dude why didnt you pm me anyways Download this: http://forum.xda-developers.com/attachment.php?attachmentid=1266013&d=1345206743 and Flash it will fix your root Problem
Sent from my SK17i using xda app-developers app
So I just flash this right after I flash S'perience, right?
Thank you so much for your replies!
Okay, so I finally installed S'perience on my LWW. And for the sake of comparison and exploration, I'm trying out Hyperbeam.
So I did the following:
1. flashed .58 firmware,
2. unlocked bootloader
3. installed Rage Kernel
4. CWM
5. wipded data (factory reset)
6. wiped cache
7. wiped dalvik cache
8. flashed base ROM (Hyperbeam)
9. flashed patch
10. flashed lockscreen
Then reboot.
Now, my phone's undergoing bootloop for a good fifteen minutes. And it's still continuing as I type this. Anything I did wrong?
Thank you so much in advance.
holocoz said:
Okay, so I finally installed S'perience on my LWW. And for the sake of comparison and exploration, I'm trying out Hyperbeam.
So I did the following:
1. flashed .58 firmware,
2. unlocked bootloader
3. installed Rage Kernel
4. CWM
5. wipded data (factory reset)
6. wiped cache
7. wiped dalvik cache
8. flashed base ROM (Hyperbeam)
9. flashed patch
10. flashed lockscreen
Then reboot.
Now, my phone's undergoing bootloop for a good fifteen minutes. And it's still continuing as I type this. Anything I did wrong?
Thank you so much in advance.
Click to expand...
Click to collapse
You forget to wipe system
Do this
Wipe data
Wipe Cache
Wipe dalvik Cache
Under mounts and storage,Format system
Then Flash the Base,your patch and the lockscreen
Today i will Update my Roms to all in One ZIP
Sent from my SK17i using xda app-developers app
So now that we're getting nightlies for CM10 and the CM Updater has gone live (system settings>About Phone>>CyanogenMod updates) what are your thoughts? I've used it now twice and it seems everything is going smoothly but I was just wondering if people still feel safer installing nightlies through sk8er's CWR? Today after I used CMU I had it "upgrading" about half of my apps after it booted as if it wiped some of the dalvik and I found that kind of weird because it didn't do that a few days ago. Does anyone know what else the CMU is doing besides installing the newer version? Is it auto-wiping cache as well? Is it ready for prime time? Because if so, man is it an awesome feature!
I just don't want to be the guy that bricks...
It's safe, I'm using it with sk8's CWM 5.5.0.4. The updater is just writing a command to the cache partition and rebooting into recovery. Recoveries know to check for this command file on startup and execute it (this is exactly how the ROM Manager interface works.)
So using CM Updater to flash and update is no different then manually booting into recovery and flashing the update, same process just automated.
Neither CM Updater nor the update script are clearing the dalvik cache. The 'Upgrading applications' occurs because on first boot the OS recognizes that some of the dalvik cache files are now out of date with what's in /system/app, so it's updating the cache files.
^^ so quiet, yet so smart.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Thanks for the clarification. Now all we need is the speedy downloads like before and we're golden!
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
sheltont said:
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
Click to expand...
Click to collapse
Use Odin to restore to the stock ROM. Download the stock rom from samfirmware.com and flash it in Odin as PDA. Then, use the latest recovery (either TWRP, CWM, OR PhilZ) from @Android-Andi's recovery thread in the Dev section. You should now be able to flash any ROM you want to. Make sure you do a backup and a wipe system, cache, Dalvik, data, and android secure (if it's an option.)
Sent from my SGH-T989
thanks and....
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
sheltont said:
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
Click to expand...
Click to collapse
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
yep
jrc2 said:
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did twice and it's still hung after apparent success installation according to Odin. I've tried it twice.
No success
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
sheltont said:
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
Click to expand...
Click to collapse
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
good idea but still no success....
jrc2 said:
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, I've retried all that this morning-i must admit that I didn't know about wiping cache after install, however it's not made any difference, and still hangs on first boot...
Any other ideas? Thanks for all your help.
Happy success
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
sheltont said:
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
Click to expand...
Click to collapse
Which version of PhilZ? And I have found that TWRP 2.7.1.0 works better than other versions for KK.
Sent from my SGH-T989
Use latest Philz touch recovery. And use the rom and gapps compatible to your tab. Don't forget to reset to factory setting, clear cache and wipe dalvic cache before flashing the rom and gapps ☺
Sent from my GT-P3100 using XDA Free mobile app
I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus
Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom
Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk
Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).
Very exited, good job
so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)
coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk
unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.
Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!