Hello,
I been running Bionix V 1.2.1 on my vibrant. Just flashed a segmented battery mod for Bionix V 1.2 from here
As per the instructions, i first wiped cached and then wiped the dalvik cache in recovery before flashing the zip for the mod. Rebooted and the phone has been on boot animation since the past 20 minutes. I took the battery out and started the phone after putting the battery in. The phone is still doing the same thing.
Any one know whats going on with the phone?
Thanks.
Update: Fixed. I was able to get into recovery and restore my nandroid backup.
ok im stuck on my boot logo for my motorola droid 2. its a liberty logo, no the original M logo, ive held in x when it starts up and then it takes me to the triangle and then i hold the search button down and then it takes me to a menu saying this:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
ive already tried just rebooting it and then it does the same thing again and just gets stuck at the boot logo, so please help. thanks!
Have you tried pulling the battery out for about 15 seconds?
See if that clears it up.
with it unplugged and turned off?
Yes Sir. Unlug it and turn it off.
yes i just did that and it didnt work, its still at the boot logo, the only thing i can do is go to that recovery menu that i said about in my 1st post, but idk what to do when i get there?
Try wipe data/factory reset.
Obviously you're gonna have to tweak your settings again.
okay, is there anyway i can get my settings back like a recovery? or something
Well, you might want to head in to the Droid 2 forums to get better responses related to your phone.
Here is a link to start with.
As far as recovery goes, I don't think you have a custom recovery installed. Sounds like you have a stock phone. So, there's no way of backing your stuff up.
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Zimm814 said:
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Click to expand...
Click to collapse
If you have it rooted, did you ever perform a Nandroid backup ?
Do you have a non standard recovery installed?
EDIT: Sorry re-read last few post and come to conclusion that you probably don't.
sorry but doesnt rds lite 4.8 and the correct sbf file let u flash back to stock?
If your phone is rooted then you have changed your kernal.It might be a fault with the kernal.I had a similar thing happen in an SGS.It was rooted and when i flashed the kernal againh via CWM it also got stuck on the same as you.The only way to solve it was boot to download mode and flash via odin again.
I tried booting various sense and aosp roms, but my phone won't boot past the flying 3d or any other boot animations. Can someone please help? I tried wiping everything. It worked at first but it doesn't now.
Edit - i think it has to do something with flashing a bad kernel
Take the battery out for 15 minutes. Then boot to recovery or whatever. Are you on old version of twrp?
sent from my EVO 3D via XDA app
this will fix it...
power off phone, charge for 20 minutes.
remove battery
load a sense 3.0 rom like eternity 1.4 to your sd card (most stable of the eternity builds in my experience)
load synergy super wipe.zip
insert sd card
boot to recovery
wipe cache partition 3 times
wipe data/factory reset 3 times
flash synergy super wipe
flash rom
boot up
should be good to go. follow those steps
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
New radios might help. Are you wiping EVERYTHING before flashing?
We're comin from a pure power source.
How can I flash this new radio? Just install .zip of the file from recovery, correct?
I do "factory reset" on the twrp 2.0 recovery before I install any rom
ninten5 said:
I do "factory reset" on the twrp 2.0 recovery before I install any rom
Click to expand...
Click to collapse
I'm using twrp2 and I do
Factory reset
Wipe cache
Wipe dalvic cache
Wipe system
Factory reset (again)
Flash Rom
Reboot system.
And i never have any bootloops or stuck in HTC white screen or any issues.
Sent From My Optimized R3Dimensions
Yea. Factory reset isn't enough. I encountered that issue when doin restores on me og evo. I had to wipe cache and dalvik to get it to work.
We're comin from a pure power source.
Use cwm older 4 version as recovery.
Fastboot boot recovery.img. make sure you have a copy of it in your adb folder.
Wipe everything and flash rom
OK ill try that.
What about backup and restores, my nAndroid backups don't work
ninten5 said:
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
Click to expand...
Click to collapse
Either one of two things:
your phone is defective
stop using so many apps for stuff like checking on system statuses. Just install a ROM fresh and leave it for a week with just your base essential apps like email and stuff. If the problem doesnt arise you know all your crap is causing it.
A radio update isnt going to do anything for a system issue as it is just your signal and stuff that the radio firmware would affect.
Sounds like the flash went bad due to not a full wipe or boot.img.
Twrp 2.0 is known to have its own issues.
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
ninten5 said:
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
Click to expand...
Click to collapse
Do this man
Get cwm 4.0 version ok now flash that then leave a copy of it in your adb folder where adb is...
Now make sure debug is on
adb reboot bootloader
fastboot boot recovery.img
Then wipe everything but not your SD card
and flash rom works this way just like the S off users use. You don't have to use flash gui or pull boot img..
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
ninten5 said:
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
Click to expand...
Click to collapse
cwm 4 is better for this phone dude. he said 4 not 5.
I'm pretty new to the whole flashing business, so if whatever I asked does not make sense, please be patient. Thanks!
I am stuck in CWM recovery. No matter how many times i flash a ROM after wipe data/cache partition and dalvik i still boot only into recovery when the ROM asks to reboot the device.
Here's what happened
1. Had a nandroid backup of older version of CWM mostly 5.0.2.x
2. Based on Nottachtrix thread installed the romracer recovery(updated flashable zip)
3. Updated to Nottachtrix 1.3.1 and successfully booted
4. Figured out that contacts everything weren't synced. So wanted to go back to older CM7 rom using restore ROM
5. Something went wrong during restoration. Data and other wern't restored and i guess only boot had been restored
6. Only boots into recovery thereafter. . Installing nottachtrix again give error at end when it asks to reboot the device: error in sdcard xxxzip status 0 installation aborted
Trying out different things like flashing boot.img, recovery etc battery drained and couldn't flash.
Fasbtoot and other options triggered by using volume buttons and power button works fine. RDS also detects the device but bootloader unknown and other info all were unknown.
Since battery drained i was searching on methods to charge the battery. Had figured out that custom method for charging the phone needs to be implemented.
While playing around again with phone i powered it through directly through charger and opted for linux cold-booting which gave me the battery icon with the question mark on screen. Popped in the battery and it started to charge. So now i know i can charge the battery using this method.
I am yet to make progress on flashing ROM successfully again. Is my backup lost ? Did the error happen because i backed up using an older version of CWM or flashing to Nottachtrix changed something
Help appreciated.
EDIT: Even after applying the backup successfully it still gets stuck in recovery.
Anyone?
Managed to.resolve by deleting partition from recovery which gave me the no os detected starting RSD in 5 seconds scenario. Performed clean wipe etc using fastboot n flashed ROM using Tom racers recovery.
Sent from my MB860 using xda app-developers app