It seems most are able to get the rom going without issue. Just curious if there is anything outside of the standard process before loading a fresh rom. I've wiped cache/data/dalvik multiple times as well as reinstalled multiple times to no avail. Will not get past the white HTC screen.
ulmerj79 said:
It seems most are able to get the rom going without issue. Just curious if there is anything outside of the standard process before loading a fresh rom. I've wiped cache/data/dalvik multiple times as well as reinstalled multiple times to no avail. Will not get past the white HTC screen.
Click to expand...
Click to collapse
I've had problems flashing to I tried various combinations. The one that worked for me was flash superwipe twice clear dalvik cache cache and data/factory reset on 4-ext recovery
Sent from my XxX Sense 4 HTC Thunderbolt
How long are you waiting? It could take a while....maybe 4-5 minutes???
jonah1234 said:
I've had problems flashing to I tried various combinations. The one that worked for me was flash superwipe twice clear dalvik cache cache and data/factory reset on 4-ext recovery
Sent from my XxX Sense 4 HTC Thunderbolt
Click to expand...
Click to collapse
Thanks, I had to go back to skyraider for the time being, but ill give that a shot later.
ulmerj79 said:
Thanks, I had to go back to skyraider for the time being, but ill give that a shot later.
Click to expand...
Click to collapse
U should do it the ROM is definitely worth it and also try redownloading u might have gotten a bad Download
Sent from my XxX Sense 4 HTC Thunderbolt
Lineside said:
How long are you waiting? It could take a while....maybe 4-5 minutes???
Click to expand...
Click to collapse
It sat for at least 10 minutes. I always let a fresh rom sit for awhile. It just never got to the splash screen.
format system, that is one thing that most people miss.
I always backup my stuff then format /cache, /system, /data, & /sdcard so the phone is completely fresh. Then I re-install my backup app and restore my backups to the sdcard. I realize that formatting the sdcard is not necessary, but I just prefer having my the phone completely fresh. Most of my data is in the "cloud" anyways, so very little needs to be restored.
Personally I never really wipe the /system, as it is done automatically before the ROM installs. I do wipe /cache, /data, and /dalvick 3 times, just to make sure it works. The ROMS install without a hiccup, now if I could just get the Wi-Fi to stop causing my phone to lock up.
My recommendation would be format system manually just in case cause I have always done that and never had issues with a rom install. Liquid Ics jmod is running o so smooth for me.
liquid thunderbolt ics
Related
I am running Das BAMF 2.1 Remix and had a strange issue today that I can't seem to get around. My battery died while I was using the phone, so I plugged it in and promptly rebooted. The lock screen was completely missing. The notification bar is still there, but I can't use the phone. Here is what I have tried:
Wipe Cache and Dalvik and reboot
Put it in a Car dock to Unlock
Reflash ROM after wiping cache and dalvik
Wipe system, cache, dalvik and reflash ROM
Wipe system, cache, dalvik each 3 times and reflash ROM.
I am trying to avoid wiping data because I have only had the ROM on a week and had just got it the way I wanted it so I don't have a nandroid or a Ti Backup (I know, dumb). I think I have most of it backed up, but I really don't want to lose anything else. The only other thing I can think of is flashing the kernel again (I don't think this will help, but as you can tell, I am out of options). Anyone have any ideas or am I just going to have to wipe everything and start over?
Edit: I also can't get ADB to recognize the phone, but I think it because the driver never loaded properly.
Even though it's currently down, go to teambamf.net for assistance. That is where the devs are now that they left XDA
Sent from my ADR6400L using XDA App
Thanks man, I will contact them. I ended up wiping data and flashing. Fixed it but man it is a pain to set everything up. My market links must have been broken because none of my apps downloaded.
does 2.1 have the tool kit. im not sure if they are all the same but in the sense system settings, you can enable it but i really dont know about 2.1
Tool kit is the same, but what are u talking about enabling?
Sent from my HTC ThunderBolt using XDA App
wow, never had that issue. I'd check with DasBamf. They know best!
Alright, we will start with a story - I am a fairly experienced root user. I had a fascinate, droid x, and now I have a thunderbolt. I had all three rooted and never had problems until now.
I have root access as well as a custom ROM on my thunderbolt. (I am currently using liquid 3.2).
The problem is that when I try to flash any other rom (I tried two: CM7.2 by ThunderShed and Infected by Virus) they do not work at all. I flash data, davik, and all that stuff. Infected gets stuck on HTC logo and CM7 gets further but freezes on startup after initial setup shows up.
My friend recomended flashing all different radios and I did that, but still having an issue. (I have 1.48.... and 0.0178... on now).
A few things.....check the md5 when you download. Wiping........wipe data/factory reset, then wipe cache, then go advanced and wipe dalvik cache, then go format/mount and format /system. Then install the .zip. If that doesn't do it, I have no idea, never had a problem flashing ROMs, only have problems once I start messing with them on my own.
I had to change to different recovery
Sent from my ADR6400L using xda premium
First, the roms do flash - just not boot up after. Both go through the process fairly well. Like I said - the only that actually works is Liquid 3.2, both Infected and CM 7.2 flash just get stuck at a different stage when booting up.
I'm going to download yet another rom and see whether that does it.
The recovery that I have is 5.0.2.1. I was going to install touch recovery and see if that was more reliable. I'll post later and see whether it was just the two roms possibly being bad (both downloaded from RootzWiki and not XDA).
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Try flashing a stock kernel first.
I also had the droid, droidX, droidx2, incredible2, thunderbolt, and now the galaxy tab. Also fairly familiar with rooting and flashing, and I had the same problem and couldn't figure it out. My clockwork was out of date. Updated, and everything was right in the world again. Check your Recovery. I didn't think if the update during flash took that it was my recovery but I was wrong.
flashing problem...
did you make sure usb debugging is on, and allow mock locations and non market downloads, and try deleting the current infected rom and re-download it just to make sure it was a clean download...i love the infected roms, especially eternity with darkhorsetheme. if that doesn't do it idk man. best of luck and try to get a hold of a developer maybe
Thank you guys!
Alright, so first off - I made sure my recovery was up to date.
I did wipe format /system and that caused infected to load, but after about an hour of using it - it froze and then when I pulled the battery, it wouldn't go past HTC logo.
I did load CM 7.1 and that works well.
I'll keep digging at it and see if I can figure it out. Thank you everyone!
Did you ever find a solution? I am having the same problem. I have tried 3 roms. It starts the boot screen and then after a minute it reboots into recovery.
It's the recovery folks.
Cwm = fail
4ext = win
donnyp1 said:
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
Using super wipe fixed this issue for me. Even after triple wiping dalvik didn't work, super wipe did. :good:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Hmm, I'd say this is Not normal. One of the big "selling points" of the gs3 and ICS is the quick boot time. For me it is very quick. Maybe u should try doing a factory reset and see if it stops this behavior??
Sent str8 from my half eaten Banilla Ice Cream Samich
ratledge said:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Click to expand...
Click to collapse
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
That is not normal if it is happening on every boot, only if you wipe your dalvik cache then yes it will update.
id_twin said:
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
Click to expand...
Click to collapse
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Are you using a custom rom or rooted? Or are you completely stock?
Sent from my SCH-I535 using Tapatalk 2
ratledge said:
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Click to expand...
Click to collapse
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
krackerjac said:
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
Click to expand...
Click to collapse
Sure sounds like it. I'm using the "Route66" rooted ROM with the Invisiblek overclocking kernel in place of the recovery.
Most likely the overclock. i ran the stock rooted 66 with no issue. I also have titanium backup installed without that issue.
id_twin said:
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
Click to expand...
Click to collapse
Worth a shot. I'll give it a rip and report back... Thanks!
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
ratledge said:
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
Click to expand...
Click to collapse
Oh, well - factory reset, re-route66, invisiblek's v2 overclocked kernel. I'm good, no "Android is updating..." every time, and no mo unlocked icon on the main screen.
I dunno what I did, but the Sammy din't like it!
Thanks, guys!
I've had my NT for quite a while now. Once I got it, I'm pretty sure I used the nook & zergy tool to root, and that's been it.
I've been on 1.4 forever, with CWM 5.5.04 as my recovery (on the emmc maybe? I don't need an sd to boot into it).
I've noticed that my stability has been declining, with random reboots here and there and rapid battery drain, so I decided it was time to get back to some flashing. I started with this http://forum.xda-developers.com/showthread.php?t=1494367, using the first 1.42 version as the others are dead. Everything loaded and booted fine, but it reboots with little provocation...you know, like, touching it, and may or may not go into a reboot cycle 3-4 times before chilling out. I still can't do much without triggering a reboot though. Search in the market? Reboot.
I attempted to restore using this http://forum.xda-developers.com/showthread.php?t=1402190, but it just boots right up normally. If I manually flash it it fails.
So, here I am with a non-bricked NT that doesn't do me much good, and I'm wondering how to get it back in order.
Are you wiping cache and dalvik cache from recovery?
Also, are the reboots occurring on battery power, or on charging as well?
Sent from my ST27i
I've done a data wipe and wiped the dalvik from cwm. I've not wiped the cache partition if that's what you're asking. Reboots are when it's unplugged or plugged.
n8w said:
I've done a data wipe and wiped the dalvik from cwm. I've not wiped the cache partition if that's what you're asking. Reboots are when it's unplugged or plugged.
Click to expand...
Click to collapse
Ok. Data wipe does wipe cache as well.
You could try a cm Rom to see if the problem persists, but if you are looking for warranty, better to stay on stock.
Also, if you pull last kernel message ( from /proc/kmsg) , some dev may be able to determine cause for reboot.
I think it's possible this is a hardware issue.
Sent from my ST27i
Thanks for jumping on this. I went ahead and wiped the cache partition, because "why not?" and I'll be damned, but I haven't had a reboot yet. Hitting search in the market was a sure trigger, and it's behaving well so far.
satan89 said:
Ok. Data wipe does wipe cache as well.
...
Click to expand...
Click to collapse
/Cache and /Data are two separate partitions on emmc, and unless something change in recent CWM/TWRP Recovery, there are separate menu options to wipe each of them.
/Data is typically used to hold user downloaded/installed apps, and should not need to be wiped except when upgrading to a different ROM or a different ROM version.
I really don't know much about how all that works, but for whatever reason, wiping the cache fixed my issue.
Sent from my DROID RAZR using Tapatalk 2
Several users swear by wiping or flashing multiple times. However, the explanations often seem like superstitions.
I would think if a single wipe didn't completely clear a partition, that would be a bug of the recovery software.
I would think if a ROM didn't install right with a single flash, that would be a bug of the ROM.
Thoughts?
I agree with your thoughts. I've never had a problem with just wiping once and/or flashing once. Not sure what wiping and/or flashing more than once would do if it didn't work the first time lol.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
I wipe atleast twice and flash once. Just check the md5 of the zip before flashing and there shouldn't be errors
Idk why someone would need to flash more than one time, and there's scripts to wipe 5 to 10 times automatically
But I wipe twice just to feel I got everything but I know one time is enough lol
Sent from my ADR6425LVW using xda app-developers app
I figured as such. Just wanted to make sure.
sdz2 said:
Several users swear by wiping or flashing multiple times. However, the explanations often seem like superstitions.
I would think if a single wipe didn't completely clear a partition, that would be a bug of the recovery software.
I would think if a ROM didn't install right with a single flash, that would be a bug of the ROM.
Thoughts?
Click to expand...
Click to collapse
There was a problem a long time ago involving clockwork recovery where wiping wasn't working all the time. At that time it was suggested to perform multiple wipes on that recovery. I think this all started and sort of stuck since then.
A developer friend of mine once said about wiping and changing ROMs...
"I treat wiping for a ROM change like taking a crap, you wipe and wipe until it's clean, then wipe one more time just to make sure I got everything."
Doesn't really answer the OPs question, just comes to mind every time someone says wipe more than once.
I wipe once because I like to live dangerously ... ohh we are talking about phones
but in honesty I never had a problem wiping once.