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!
Related
Okay I recently rooted my TB and flashed bamf 3.0 RV4.9 ran perfect with no issues.... I later tried to change and font and after rebooting it would not load past the splash screen so I went unto hboot and reflashed bamf ROM. It than rebooted and loaded up as normal. However now it will not connect to Skype or WiFi. When trying to connect to WiFi it'll say "obtianing up address" and sit there for a minute that disconnect is this a radio issue or US it bc i didn't wipe all the data when I reflashed bamf? Tundra for the help in advanced
Your word correction is not serving you well LOL.
Anyway I would say do a full wipe of data, cache, and dalvik cache in Clockworkmod Recovery and then try to reflash the ROM. For future reference even if you are doing something small like changing fonts ALWAYS make a nandroid backup in Clockworkmod recovery FIRST. Then if you have a similar issue to this one you can do a full wipe and restore your backup without losing anything.
Sent from my HTC Thunderbolt
You talking about where it says "all user data/factory reset" ??
Sent from my Rooted Gingerbread using XDA App
NavyKwonMA said:
You talking about where it says "all user data/factory reset" ??
Sent from my Rooted Gingerbread using XDA App
Click to expand...
Click to collapse
In Clockworkmod recovery, using the volume rocker to move up and down and tapping the power button to select, choose wipe data/factory reset and then select yes. Let it do it's thing and it will come back to the main recovery screen. Now choose wipe cache partition then select yes. Now go down to advanced and select that. In the advanced menu choose wipe dalvik cache and then select yes. After it is done you will still be in the advanced menu so scroll down to go back and select it. Now flash your ROM.
This is how you should always wipe before flashing a new ROM or update unless the ROMs thread specifically says not to. (which probably won't happen.) This only applies to ROMs, and NOT to themes, kernels, or mods.
Sent from my HTC Thunderbolt
Thanks !
Sent from my ADR6400L using XDA App
i whipped up a rom in the android kitchen, and im having this problem as well. ive tried wiping and formatting each and every thing 3x+, and have tried every radio except mr1, and i still cannot get wifi to connect. and the 704 radio causes my phone to freeze. while im sure it has something to do with the actual rom im puttingout, i just thought id throw my experience in here. i cant figure out whats causing it not to connect
If you figure it out shoot me a pm! I'm fixing to deploy overseas so I need my WiFi!
Sent from my ADR6400L using XDA App
Wiped all data and caches and reflashed ROM.... Everything works now thanks for the help!
Sent from my ADR6400L using XDA App
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:
Now my head i about to explode
Anyhow, I have an annoying problem.
Before the upgrade to XXALF6 I noticed no problem other than the known drainage of the battery in idle mode.
I rooted and flashed a ROM and it was ok.
But I got sick of the ROM and I hard reset the phone.
No problems.
Then I upgraded to XXALF6 - still unrooted and all.
First thing I notice is that the phone is lagging a bit now and then. Then when I sent and recieved an SMS or two the phone hung and rebooted.
I seems that happend because when vibration was active.
Also there was a new message saying "com.google.process.gapps" stopped working. And that came up again and again.
As far as I could find online that had to do with syncing the calendar and it should help to clear calendar cache in the phone. It did not.
Then I rooted the phone, just "CF-Root-SGS3-v6.4", no other ROM.
Now the problem was even worse and also the sound stops working on and off all the time.
I tried to find the "com.google.process.gapps" with a file explorer with no luck.
I do find it in ROM Toolbox but its not possible to see the where on the phone the file is even there. Also its not possible to uninstall or even kill the process.
I did notice there seem to be doubles of some apps that I didnt notice previously to flashing CF-Root this time.
And I recall the new guide never mentions to wipe any phone data whatsoever during rooting the phone, and now I am thinking that maybe that should have been in the guide?
Anyhow.. appreciate ANY tips at all, Im so sick of this for the moment ^^
Go to cwm recovery, wipe cash, wipe dalvik cash, wipe data/factory reset, then go to mounts&storage, format system. Then put your phone into the download mode and flash ROM again with odin. This should give you a nice and clean install,without any force closes..
Sent from my GT-I9300 using xda app-developers app
pedja381 said:
Go to cwm recovery, wipe cash, wipe dalvik cash, wipe data/factory reset, then go to mounts&storage, format system. Then put your phone into the download mode and flash ROM again with odin. This should give you a nice and clean install,without any force closes..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I did wipe all things, cache, Dalvik, battery and user data with CWM.
At the moment it seems the phone is quite okay actually! The only thing left is SU.
U think I have to format system as well? What else would really be "cleaned" out that wasn't allready with the wipes?
Trust me,some of the devs insisted on formating system before flashing their custom roms,and I did have a bunch of force closes,until I decided to go their way and fully format the phone. It then installs everything from the scratch,so there's no way anything to go wrong.. give it a try,and report back... btw. make sure that you DO NOT restore any of the system data,if you use TB
Sent from my GT-I9300 using xda app-developers app
Yeah I pretty much learnt same way as predja it is always better to do full system wipe, it is not always necessary with some roms but if you do it you won't come across the problems you have as often.
sent from my SGS3 Using XDA app
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
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