Hi. I'm in a bit of a rut. My tf101(b60) is rooted, running the latest recovery, TWRP 2.3.2.3 and no rom installed. I'm trying to flash EOS 4 but all I get is the infinite. I tried wiping the cache & dalvik cache and that didn't help. I also tried to flash a previous rom that worked before and that no longer works either. Anyone have a solution? Thanks!
EDIT: aaaaannnnd after the 3rd time I flashed it, the rom worked(seriously wtf?). Please delete this embarasing post as I can't. xD
Sent from my EVO using xda app-developers app
Related
I just flashed MIUI (latest version) and my DS is restarting repeatedly.I was at stock ROM before and i had factory reset it before I flash MIUI.
Anyone knows what happened?
EDIT: sorry for spamming...i got to CWM and i format again and it worked
ps. greate job with the ROM
are you using clockwork recovery?
barkermichaelj said:
are you using clockwork recovery?
Click to expand...
Click to collapse
would recommend that you install EXT4 recovery rather than CWM
simply download file onto SD
boot into CWM
and flash ZIP file
CWM works just fine, you just need to make sure you wipe everything before flashing new ROM, ie data, cache, dalvik cache, etc, then all is good
Just wanted to add that I to ended up in a bootloop, and I've had miui 1.8.5 installed since it came. It stopped after about 10 reboots. Dunno know what's up, had a lot of FC's as well these last few days.
Looking forward to tomorrow for am update! Cheers!
Sent from my HTC Desire S using XDA App
I also had some problems with 1.8.5 version (random reboots). I am still using the 1.7.29 version that is working great. Only theme chooser FC's.
I don't have enough posts here to be allowed to post this in the development forum, so I figured this might be a place to ask about my issue.
I have a MZ602 (4G) and was coming from rooted ICS 4.0.4. I used TWRP and wiped cache, dalvik and system. I flashed the latest nightly (120) and GAPPs (O8120802-eos-signed.zip). When I rebooted, all looked okay except, I could not unlock. Camera works, Google works (it loads. I am obviously not online ). I double checked the MD5s and they were correct. Same problem when I flashed with the 119 nightly.
Any ideas?
Wipe data.
Sent from my SGH-I747 using xda premium
Tried that with no change. Also tried earlier nightly and Gapps, also no change.
From recovery, wipe all, format system , flash ROM again...
Sent from my MZ601 using Tapatalk 2
Thanks,:good: I have tried that, but that doesn't mean I don't appreciate your help. This stuff will definitely make us nuts.
Wipe everything via fastboot then try to reinstall.
Sent from my Galaxy Nexus using xda premium
d3athsd00r said:
Wipe everything via fastboot then try to reinstall.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My entire experience with fastboot was unlocking the bootloader on my Xoom. So I don't speak much fastboot. What are the commands I would need to do a wipe using fastboot and would it hamper my ability to restore my nandroids?
Thanks
I have the same problem and have tried the same things you have with no success.
iosmacman said:
I have the same problem and have tried the same things you have with no success.
Click to expand...
Click to collapse
Out of curiosity which recovery did you use to flash? I was using TWRP.
Another poster in the Developer Forum, happysteve11c , has this result too. So, perhaps we all did something similar. I was wearing my lucky shirt and waited until mercury was in retrograde before trying to flash, so it should have worked.
Hi guys! I've been trying to install CM and JellyBam but I couldn't. I could only install stock roms
I have a rooted phone with CWM recovery
I followed every step to install a ROM: wipe data, wipe cache, even wipe dalvik, then installed ROM from SD card.
Some help, please?
santipuig said:
Hi guys! I've been trying to install CM and JellyBam but I couldn't. I could only install stock roms
I have a rooted phone with CWM recovery
I followed every step to install a ROM: wipe data, wipe cache, even wipe dalvik, then installed ROM from SD card.
Some help, please?
Click to expand...
Click to collapse
I always get a bootloop
Have you tried doing the wipes after you installed the roms
Sent from my LG-P920 using xda app-developers app
Yes I did. Also I tried installing again the same ROM and wiped the data.
You need to flash bernie's files before installing any CM based rom.
dcoelho said:
You need to flash bernie's files before installing any CM based rom.
Click to expand...
Click to collapse
Actually I want to install JellyBam ROM. Do I also need to flash bernie's files in order to install this rom?
Where can I find them?
http://forum.xda-developers.com/showthread.php?p=35199371
try that link.
Can you explain me why I have to downgrade in order to install a custom Rom?
Sent from my LG-P920h using xda app-developers app
You're not actually downgrading...you're just flashing a baseband to get cm compatible. Ignore the posy name. Its the method you follow
Sent from my LG-P920 using xda app-developers app
Ok I'll try
I have flashed many 4.3 Roms and can not get any of them to boot. I have followed all install instructions but can't get past gs3 screen. Any ideas?
Sent from my SCH-I535 using xda app-developers app
im having a similar problem to yours..i mean after i do a fresh install+gapps it works..but after i go back to recovery and install my other files it wont go past the gs3 logo no idea why.
Yep frustrating any other ROM is OK just 4.3 not working, sucks.
Sent from my SCH-I535 using xda app-developers app
I've flashed every 4.3 and all booted. Try just flashing ROM first. Let sit a few minutes then flash gapps. I also use the eclipse ROM gapps for all. No issues.
Sent from my SCH-I535 using xda app-developers app
I also have the same problem when I try to reboot on 4.3 Roms. First boot up is fine. But when I go into to recovery it won't boot back up unless I reflash the ROM from the start. If someone tries flashing ROM and gapps separately let us know if it fixes it.
Sent from my SCH-I535 using Tapatalk
Tried eclipse ROM and apps. No different. Initial boot works and ROM runs fine but reboot freezes up on gs3 screen. What is getting scrambled and is there a way to fix this.
Sent from my SCH-I535 using xda app-developers app
I've never had this issue. What I've done/used to flash all 4.3 roms was use the super wipe tool found in the general section(the one that wipes data, system and caches only) and then run it once and flash Rom+ gapps as instructed. I use twrp as well. Also, perhaps it's a stock 4.3 kernel and maybe flash a kernel straight after you flash the rom and gapps. Rom> gapps>kernel . Hope it helps
Sent from my SCH-I535 using Tapatalk
---------- Post added at 08:47 PM ---------- Previous post was at 08:41 PM ----------
http://forum.xda-developers.com/showthread.php?t=2097365
[Mod][Utility] Wiping Tools - Simple and Fast
Sent from my SCH-I535 using Tapatalk
I used ez recovery from the play store and used cwm touch recovery and I no longer have the reboot issues. Even if you're using cwm, I would just download ez recovery and try it.
Sent from my SCH-I535 using Tapatalk
Use ez recovery to flash the ROM or install cwm and then flash through that?
Sent from my SCH-I535 using xda app-developers app
I had a similar problem when I first tried 4.2 but I've found two ways that have always worked for me
Full wipe (I wipe everything 3 times, but I'm sure that's overkill)
Flash rom
Flash gapps
Reboot
If it gets stuck on any screen wipe the cache and dalvik cache
Reboot
The other method I've only used with Dirty Unicorns
Full wipe
Flash rom
Reboot
Once the rom reboots, reboot back into recovery
Flash gapps
Reboot
Wait 10 minutes
You can either reboot again or just use as is
But if nothing is working you can odin back to stock
Then use this tool to root, unlock the bootloader, and flash the custom recovery of your choice http://forum.xda-developers.com/showthread.php?t=2332825 (it even works on a mac)
(This is what I always use to root, unlock the bootloader, and flash recovery whenever I have to flash back to stock)
After I do that I always reboot and use Rom Manager to flash the latest recovery before flashing anything else.
These 2 roms have been 100% stable for me
http://forum.xda-developers.com/showthread.php?t=2484256 (4.3.1)
http://forum.xda-developers.com/showthread.php?t=2469789 (4.3 I've never tried the weeklies just the lastest stable build)
Hope it helps
It seems that most ROMs will boot up fine with the latest TWRP recovery. But there are a few that will only boot up with CWM. So download both recoveries and flash them using ez recovery when one of them isn't working.
So, I usually stick with TWRP 2.6 as my default. The great thing about ez is that it includes cwm in it. First off I'd make sure you're running the latest recovery available. Then if that doesn't work restore your backup, hopefully you made one, and flash cwm and try reflashing the ROM. Assuming you're wiping everything at least 3 times and flashing the correct ROM with the correct gapps, there's no reason why it shouldn't work. And another thing. It's never a good idea to restore data from any app, ever. Trust me, I know.
Sent from my SCH-I535 using Tapatalk
Juice3250 said:
It seems that most ROMs will boot up fine with the latest TWRP recovery. But there are a few that will only boot up with CWM. So download both recoveries and flash them using ez recovery when one of them isn't working.
So, I usually stick with TWRP 2.6 as my default. The great thing about ez is that it includes cwm in it. First off I'd make sure you're running the latest recovery available. Then if that doesn't work restore your backup, hopefully you made one, and flash cwm and try reflashing the ROM. Assuming you're wiping everything at least 3 times and flashing the correct ROM with the correct gapps, there's no reason why it shouldn't work. And another thing. It's never a good idea to restore data from any app, ever. Trust me, I know.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
You do realize that the recoveries built into ez recovery are over a year old. I wouldn't flash those under any circumstances. Only use ez recovery to flash from the custom slot.
Sent from my SCH-I535 using Tapatalk 2
Thanks for correcting me on that one. My bad.
Sent from my SCH-I535 using Tapatalk
My brother just got himself a skyrocket he's on the newest radio w/custom recovery installed but can't seem to flash anything but cm 10.1 with an old 4.2 GApps package.
Kinda frustrating because I haven't seen anyone else having this issue in any other thread. I did to his all I did to mine and I'm running Wantowan2's DU. Just says installation failed and we can't even flash other recovery from within recovery. Where should we go from here
Sent from my SGH-I727 using xda app-developers app
Odin back to stock and start over. Something got messed up in your recovery
Make sure you've got the proper recovery for 4.3 as well.
Sent from my SGH-I727
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
K
Boot_Derran said:
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
The gapps isn't right for 4.3, cm 10.1. Flash the 8-13-2013 gapps
Edit, you can find it on the OP of this http://forum.xda-developers.com/showthread.php?p=46685423
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Boot_Derran said:
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
What is the exact error message that TWRP is giving?
Gotta wait for my bro to get off work but will post as soon as I can get his phone and give it another go
Sent from my SAMSUNG-SGH-I727 using xda app-developers app