when i flash a new rom and kernel for that matter i got no confirmation like the first time i flashed a rom on the clockwork recovery.
i wipe and then try flashing and it says something really quick, so fast that i cant even read it, and then goes back to the first clockwork recovery menu and only says "clockwork recovery 2.5.1" or whatever number im running (which is the latest)
try again doesnt work, so i reboot and then it still says im running "bakedsnack 1.0" is that normal for it to say im still running that rom after a complete wipe? and it still has the roms background and satus bar, etc
please any help would be nice because im new to android and am looking forward to continuing my rom experience
running epic 4g have clockwork recovery and super user etc
Have you tried wiping both cache's and wiping the data 3 times ? There is the regular cache and then a davlik ( spelling may be off) cache in the advanced menu of clockwork's recovery. If that doesn't work, you could always try reinstalling the stock epic 4g rom and kernal through odin. I need to try that myself but hopefully one of those other options helps.
Related
i had bootloops with my transformer ( revolverrom) so i want to go back to stock.
Meanwhile it seems to me that i had the reason:
every time i want to wipe cache data with clockmos recovery (3.2,0.1) there is a message:
error removing data/system /packages.xml
and the data are all there.
I think thats the reason for freeze + bootloop afterstarting .
Or is it maybe a hardware problem?
What can i do to find it out? If i flash revolver or ics rom i get freeze + bootloop seconds after the Mainscreen.
What can be the reason for no possible wipe data?I think it is the same reason as for the bootloops.
Kind regards- and sorry for my poor englisch
gandalf -
Of course i can trie do delete with rootexplorer- but that will be no solution of the fault-or am i wrong .
just my two cents, but can't you just flash the Super Wipe script from the Revolution ROM thread, and then flash your ICS ROM after doing that?
Also I've had problems with CWM Recovery on my Evo 4g, so I flashed Amon RA recovery and that seemed to do the trick for me. I'm not sure if it's available for the TF101, but like I said, this is just my two cents.
best of luck!
I have been trying the new ICS ROMS and have an interesting observation to share. I have had many weird problems like the shutdown reboot issue, touch key lights staying on, force closes etc. The only time I had a clean install (without even the shutdown issue) was when I first used CWM to wipe everything and then used the stock (gingerbread) 3e recovery to perform another wipe before flashing a ROM. Anyone willing to try and confirm?
when u say another wipe using stock recovery, u mean just a factory reset, before reflashing cwm and then ics? becuz if so, ive tried that, and it was still hit and miss
CWM - wipe data, cache and system, Darkside superwipe, ODIN 3e, wipe cache and factory reset, ODIN CWM and flash. Works every time for me.
rushi.1986 said:
CWM - wipe data, cache and system, Darkside superwipe, ODIN 3e, wipe cache and factory reset, ODIN CWM and flash. Works every time for me.
Click to expand...
Click to collapse
It seems like there isn't an easy fix that works for everyone (for the shutdown freeze bug anyways--this was the one problem I just couldn't get rid of until just a couple days ago). I had a theory that Darkside superwipe was screwing it up for me (the method you use as I've quoted was basically my method for wiping prior to flashing any roms, with the exception of using 3e recovery).
Seanzscreams new Sky ICS rom claims to have fixed the shutdown issue for good. I don't know if this is true for everyone but it seems to have worked for me.
What I do is:
Flash darkside x1
factory reset x5
wipe cache x5
wipe dalvik x5
format system x5
Flash radio
wait 1 minute
flash rom
wait 1 minute
reboot and don't touch phone for at least 10 minutes
I've noticed that some people go to the extreme when it comes to wiping....... Super extreme.
I've always in my YEARS of flashing roms (I got G1 on day one), I've always done just a simple format of data and cache. Normally don't get any unexplained errors or bad flashes.
LOT of the problems rise from users. Either installing something that is buggy or just not following directions.
Restoring backups is probably the BIGGEST CULPRIT OF ALL. Often times, people just restore files that they shouldn't. Adding themes, adding animations, boot animations blah blah blah...then blaming devs because so and so is not working.
I use restore but I'm selective about my restores. I don't just restore everything that I just backed up. Has NEVER caused me any problems.
about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks
and to clarify , it was gapps 4.2.2
Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.
If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app
i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .
You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.
actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.
i figured out twrp. never gave it achance. ill see if that does the trick
tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks
Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?
Hey guys, since my post count is too low to post my problems with this OTA update in the development section of this rom, ill do it here. Sorry for that.
I think im having no problems with flashing the 2.1. ROM yet but i have my concerns if i did that right.
First problem with flashing it, is the question if im having a custom kernel. I flashed ViperOneS a several times but made a fullwipe before.
So am i having a custom kernel or not?
Next issue is that im only able to flash this ROM with CWM. TWRP 2.5 doesnt work and even 2.3.3.0, which should work, but does not for me...
Well with CWM i ll do it that way:
1. Doing Fullwipe in CWM (Factory reset, Wipe Cache, Wipe Dalvik and System).
2. Flashing the ROM and choosing HTC Theme > Custom Kernel? > not sure sometimes "yes" sometimes "no".
3. Flash finished? > asks me if i want to reboot (into system) or save the logs. Since the instruction tells me to flash the boot.img first before rebooting...
4. ... im going into bootloader via adb which works
5. flash the boot.img
6. fastboot erase cache
7. reboot system
8. before doing the first setup i go into recovery and wipe cache.
I think 2.1 works but i want to be sure if i did everything right, especially with the custom kernel question and that i reboot into bootloader right after aroma says that the flash is finished.
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
The problem is that they dont keep their instructions up-to-date (+ how to flash the OTA... right)
It looks to my like there are 100 different ways to flash 2.1.0 and 2.2.0 and only 1 is the right way which lets the ROM being amazing...
Hope you can help me. Thanks in advance!
turnschuh said:
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
Click to expand...
Click to collapse
All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
What EXACTLY doesn't work with TWRP 2.3.3.0?
All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
Click to expand...
Click to collapse
yea i did it like that. i just flashed it in the recovery, but im not sure if i have to wipe caches after or before doing that.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
Click to expand...
Click to collapse
about finding such "tricks": the problem is that those ROM release threads have tons of post (500+ sites of them) and it seems like 90% are from people who didnt even flash the ROM... i think you ll excuse me if i say i got tired of searching for my problems there^^
well can u tell me which skin i have to change? on venom tweaks or the htc skin on personalization? and app settings > venom tweaks > wipe cache and data right?
What EXACTLY doesn't work with TWRP 2.3.3.0?
Click to expand...
Click to collapse
when i flash it with 2.3.3.0 (or 2.5... its the same), the flash process doesnt even take up to 2 seconds and it says its finished and that causes a bootloop but doesnt make me wonder.
dont you have problems with TWRP flashing sense roms either?
ah and another one: did i flash the version 2.1 right and what about the custom kernel question?
well thanks for ur time.
edit: well this time flashing with twrp 2.3.3.0 worked somehow, but i choosed flashing without wipe (made it in recovery) and not to delete apps with aroma installer (which i did before)... just strange.
new problem. dont know whats wrong with my phone but:
wanted to make a backup of my ViperOneS 2.1 with TWRP 2.3.3.0 after lets say 70% of progress it starts turning off my phone and restarts into system. i flashed 2.5.0.0 but its the same issue (edit#1: with CWM too...). strange is that TWRP turned out my phone before when i wiped something there.
i think somethings really messed up atm...
edit#2: had to run a ruu over the system again, flashed twrp and backups seem work again..strange ****
Title kind of tells the story trying to flash to Synergy-yes md5 passed on the download.I wiped everything twice and then cache and davlik seperately and launched TWRP and when I try to install it just hangs and then eventually prompts me to close the app.
Do I need to flash back to stock and then install a custom ROM?I wipe everything but remain on Carbon of course.
For those running Synergy what recovery were you using-any issues with TWRP.What process worked for you?
Luckily my restore back to Carbon worked no problem.
Thanks
I wipe system internal storage data a the caches. You may also want to try cwm as it might work better. Make sure your download for synergy is for the vzw one.
Sent from my SCH-I535