Hi,
I'm a real neewbie so please be gentle.
I've rooted my phone and put defrost 5.4 on it.
Works good and i'm figuring out how things work.
I found out now that when i reboot the phone it gets stuck in starting up.
The colors exploding from the left and the right side to become a "X", but then after a while the x is not made any longer and after half an hour it is still trying to make an X.
Take out the battery, put it back and start the phone and it starts normal.
When i install something from the "defrost setup" its downloaded and when i press install the phone restarts, it is unpacking the file, reboots and then gets stuck again.
Have to take out the battery to start the phone again.
What can be the couse of this??
Just found out that also a "normal start" ends up in a endless bootscreen.
The only way to start the phone is take the battery out, put it back and press "start".
Do a full wipe and try another ROM is my first suggestion.
So idid a wipe, after that a recovery (had to start all over again) but the endless bootscreen still remains.
???
1) Find a new ROM and put it on the root of your SDCARD
2) Boot into Recovery by pressing BACK and the POWER button
3) Perform a full wipe (data/factory reset) and cache
4) Flash the new ROM
5) Boot the phone
If you still have problems post logcat.
i've cleaned and whiped (i think) almost everything.
Installed a fresh defrost 5.6.
Installed the defrost apps addon, the phone reboots and a screen apears with a android an a box with an arrow out.
Text is passing by, the phone reboots and starts up.
So far so good, but when i restart or reboot the phone its hangs in this endless lashing coulorfull screen.
I've tried to make a "logcat".
Hopefully it tells you more than it tells me.
i am having the same problem.
first off all: you can press power + volume down + optical joystick to restart phone.
no need to remove battery
my last logcat (with Error filter): www wog-fds.de/log_bootloop.txt
i started to have this problem when i redid the unrevoked process (dont really remember why, thou).
thx for help
edit: not sure but the first logcat looks like somethings missing
heres anotherone without filter www wog-fds.de/log_bootloop2.txt
thx
OK, maybe this is getting somewhere.
I also did a re-revoke, but i do know why.
the first attempt to root my phone ended up in a small disaster.
At the end of the proces i found out that i have a SLCD screen and not an AMOLED, so my phone was as good as dead.
Thanks to someone on a Dutch forum i was able to get my phone back to life.
After that i rooted my phone with the latest version of unrevoked, and this time i was succesfull.
But now i am encountering this problem and it is no fun.
I have at the moment nothing running on the phone because after a re-re-reinstallation i can start all over again with al the apps and so on.
It hangs at the final stages of the boot it looks like.
I had a similar problem when I was messing around with my old framework.
So why you're getting it, I have no idea.
First thing is first Bud
Download DeFrost 5.7 And use the latest version (Illuminate some issues to start with)
What your saying is the Boot Animation (The Multi Colour X animation "Nexus Boot Animation"
You get a boot loop on there....
How long have you left it trying to boot? the first boot after a Reflash does take alot longer than normal as it has to write to a number of files first.
(This only occurs on a New ROM or a Reflash of the frameworks)
So first off Lets Get that latest ROM on the SD Card:
Use w/e method you need to to get it on there
Turn the Phone Off "Where going to load recovery"
Press the Down Volume Key and press the power button Once.
You will see a white screen with Android images at the bottom:
Press the Volume down once (Recovery) when this is highlighted press the power button
Where now in a black screen Press Volume Up and Power
(We should now have a Blue Menu (Am taking it by the issues you talk about your using Clockwork Recover.......)
Go down to Apply sdcard:update.zip
And press the power button. So where now Clock Work Recovery
(If you dont have Clockwork i.e. Fake Flash Update.zip maybe someone can post it for me, Limited for time in work, But search for Fake FLash Clockwork if you dont have it.
Then go down to Wipe Date/Factory Reset
Select the only line that is Populated.
Go back to main menu and go to install Zip from SDCard and press the OJ
Select Choose Zip from SDCard.
Find you ROM and press the OJ
Wait some time and press the back button a few times, and select the reset option?
DO NOT INSTALL NO MODS OR THEMES, THIS CAN ONLY BE DONE AFTER A FULL BOOT OF A CLEAN ROM.
Leave it some time, as the first boot is always the longest.
Fingers crossed you should be OK.
What your talking about is a problem with the ROM (as the bootanimation is called by the ROM)
dave7802 said:
DO NOT INSTALL NO MODS OR THEMES, THIS CAN ONLY BE DONE AFTER A FULL BOOT OF A CLEAN ROM.
Click to expand...
Click to collapse
That'd be my guess too. If you try to apply a mod before you've let the ROM unpack itself it does exactly as you describe.
What your saying is the Boot Animation (The Multi Colour X animation "Nexus Boot Animation"
You get a boot loop on there....
How long have you left it trying to boot? the first boot after a Reflash does take alot longer than normal as it has to write to a number of files first.
(This only occurs on a New ROM or a Reflash of the frameworks)
I've installed the defrost.
After it came in full working conditions i've added the defrost add-on.
Phone shuts down, starts again in the screen with the one doid and a box with an arrow out.
Some writing apears and the phone starts again.
The colours apears and making a cross and this goes faster and faster and then a screen where i have to enter my sim-unlockcode and the phone is up and running.
So far so good.
When i now switch the phone off or give it a reboot ( in the screen after a long press on the powerbutton) the phone starts in the white screen with HTC logo, then the colours apear making a cross, but after time this goes slower and slower until the cross is not ever made again.
The colours appear trying to make a cross and diappear and comming back again, and this goes on for ( i left it once for 1/2 an hour)
I will give it a go with the 5.7
thanks for the help.
Really, i heave my phone for one month now and it is my first android thing.
Never worked with linux etc etc.
What does "press the OJ" means ??
oj = optical joystick
@dave7802
thanks for the answer but i have the bootloop also when i do a manual restart without flashing anything.
i use defrost 5.7
i did a restart after flashing
bye
strange thing to happen. it must be in the ROM because it wasn't happening on the stock ROM.
so try another ROM some like cyanogen or opendesire. is it happening also?
Wel, i've come to the point that i think "WTF", it works and the only thing is the start/reboot.
I'm not going to re-re-re-re sign in to my google account, and not want to re-re-re-re-enter my mail account again.
Thanks to "olaxe" i know how to start the phone wthout taking out the battery.
anyway, everybodie, thanks for reading etc.
OK so you guys are still having the same issue.
Can we provide as much info as possible,
As i use DeFrost 5.7 and i just done a normal reboot and its working fine,
if its a problem with the ROM everyone would have the issue,
All i can think is a MOD you have installed is conflicting,
So some info you can provide:
What MODS are you running / installing, like Super Circle Battery, or Custom HAVS and SVS?
What version where they developed for?
i.e. are you installing MODS that where developed for an older version of defrost? as the frameworks change on each version and so do the HAVS and SVS
If your not flashing anything how about installing it?
It could be an app you used worked for an older version, and since the update its no longer working?
olaxe
thanks for the answer but i have the bootloop also when i do a manual restart without flashing anything.
i use defrost 5.7
i did a restart after flashing
Click to expand...
Click to collapse
You say you have not flashed anything? and then you said you restarted after flashing? i dont follow?
What settings are you using and apps do you have installed?
What are you doing in clockwork recovery, are you wiping then installing JUST DEFROST then letting your system start up?
or
Are you flashing a couple of things like defrost and super circle battery?
Dave,
A nephew, who ownes a desire and is "into android" from the moment of the first googlephone, was going to root my desire.
The great misstake (we found out after we've dit it) was that he used a version of unrevoke witch was mend for use with amoled and i own a slcd.
So my phone would'nt show anything anymore. Only the bootscreen when pressed vol down and power.
I've followed several advises of diehards, have put "this.zip" on the sdcard, "that.zip" and even "ifthisdon'twork.zip" shoot me.
All i got in the bootscreen was "no image" "no image or wrong image" and "version is older".
After a week a guy on a dutch forum told me to download some files to my computer, take the sdcard out of the phone, connect the phone to the computer and then type the following:
3. Typ in je commandprompt:
code:
1
2
3
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom210.zip
After that the phone came back to live and i was happy as a child.
After that i did the unrevoked thing with the latest version and the phone was rooted.
Put the sdcard back, formatted it whitin the phone and after that i placed the defrost 5.4 on the root of the sdcard.
Did the full wipe, dalvikwipe and flashed the defost 5.4
After a while i had the defrost up and running.
In the defrost setup i found the defrost addon.
downloaded it (all IN the phone) and after that pressed "install".
The phone shuts down a screen appears with the one droid and a box, the phone restarts and is up and running.
Then i found in the defrost setup a file "no adds"
Installed that to and then the troubles start.
Hangs in the bootscreen.
I can only start the phone when the power is completely turned of ( battery out) or with vol down, power and trackball pressed at the same time.
Related
I have a rooted (Supersonic EVT2-2 SHIP S-OFF; HBOOT-0.93.0000) EVO that I'm running Warm 2.2 RLS 4 on. I have it set up the way that I wanted and it is running perfect (enough for me).
Yesterday, I caught a glimpse of the MIUI ROM that has an iPhone theme so I wanted to try it out. So, I used Titanium to back up my apps and data to my SD card (8GB with 3GB open). Then, I went to ROM Manager to back up my ROM. I saw that there was an update for the ClockworkMod Recovery so flashed it up to 3.0.0.5. Then I went to Backup Current ROM, kept the suggested name, and hit OK. After a few seconds, the Splash Screen (white HTC EVO 4G) briefly shows, the phone buzzes and then I'm on the initial Bootloader menu screen (with the three Androids at the bottom).
I highlight Bootloader, then I hit the Power button to go to the next set of menus, and the phone does it's checks. After the checks, I push the Volume Down button to go to Recovery, then hit the Power button. The splash screen shows again, the phone buzzes, and I'm back at the initial Bootloader screen.
Whether I use the Quick Boot app, the ROM Manager app, or the Power and Volume Down method, I cannot get past the Bootloader screen to get into Recovery. All I get is Splash, buzz, then the initial Bootloader. Warm 2.2 RLS4 is a nice stable ROM, but I am starting to feel limited, which is why I rooted the phone a few months ago.
Could someone PLEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEZZZZSSSSSSEEEEE help me with this? I have been reading forums and Googling this issue for hours and I can't find an answer. I am far from a comp engineer, but I can follow instructions pretty well.
Thanks a million!
Try using ROM Manager to reflash your recovery, that should fix it for you.
Fourth times the charm! WHEEWWW!!!
It's seems to be working now and I'm backing up my ROM as I type. I went into ROM Manager and flashed it again and this time I went into Recovery straight from ROM Manager (I had did it indirectly via the ROM backup before) and I saw a orange and black menu, instead of the green and black. COOOLLLL!!!!
I tried to go into recovery from the Quick Boot app and that works too, NIICCEE!!!
I guess after you flash the ClockworkMod Recovery, you have to "initialize" it by going to it directly from ROM Manager, or else any other method you try won't work? I'm not sure but it seems like it.
A good lesson, glad I can fully enjoy the EVO again.
Cheers!
Glad you got it figured out
I decided to try out the new RcmixHD 6.0 today...I backed up my Rom , wiped data n Cache n Dalvik Cache..The phone rebooted n now I am stuck on the bootscreen with white background n htc...plz someone help!!...I dont know what to do!!!....neone?..plz reply soon..
OK, i'm only new to this, so it might be better to wait and see if someone more experienced can answer you question.
but if its still stuck on the white screen then remove the battery & then put it back in again then hold down the Vol down button and power button until the bootloader loads up. then select 'recovery', it hopefully should take you back into the clockworkmod recovery & you can then flash your rom.
again, i'm only new & thats just my best guess.
first off, when you flash a new rom, it tends to stay on the white htc screen a bit longer. make sure you give it a few minutes (i'd say a good 3-4 minute wait should suffice but lets say 5 just to be safe). if nothing happens by then, you can always follow the method listed above by henipah to restore your backed-up rom.
once you have restored your rom and your heart rate has returned to normal levels, you can try flashing the new rom again. remember to wait it out a bit at the white htc screen.
First boot can take an age, if you issue the command
Code:
adb logcat
it will at least confirm the phone is doing something and hasn't hung, if it has hung issue
Code:
adb reboot recovery
and reflash your chosen rom.
Thank you for the replies...flashed it again n its fixed...it was stuck on Boot screen for about 15 minutes!!!..I thought I bricked by device or something...lolz..neways, all is well now..
Help plzzzz!!!!
I am a newbie here and am facing a problem with the data connection on the phone. I have flashed the new RCMix Rom v6.0.0.1 with partial Sense 3.0.
The problem is that if I leave the phone unattended or even otherwise, the data connection turns off. Is this a bug with the ROM, cause I see that the option for the Mobile Data Connection is still ticked in the Notifications Menu, but for me to be able to connect, I have to untick and then tick it again for the connection to happen again. Would also want to specify that I am not on 3G. Any help would be really appreciated.
Hello,
well I read a lot about rooting and flashing custom Roms the last few days and I figured I would give it a try.
I really hope I didn't break my phone, hopefully one of you Android / Defy Gurus can help me out
I rooted my phone with Super-One-Click and that worked fine, then I installed Recovery Bootstrap for Defy from a thread in this forum (can't find it at the moment) but it is this one: "bootstrap-recovery-clockwork-mod"
Anyway, that worked fine too... I make a backup (backup/restore->backup). Then did multiple factory resets and deleted the Cache as well as the dalvik cache multiple times. And then installed CM7 off the SD card.... the first time it didn't work, and it booted back to the setup of blur... I tried it again this time activating "Fix Permissions" before install... it then worked and it booted up CM7 fine.
I then wanted to go ahead and install The Google apps from here: goo-inside.me for CM7 ... did the same thing wiping the caches and then installing off of SD card... rebooted and I get stuck with the motorola logo... which just stays there and does not go away.
I rebooted multiple times (by taking out the battery) entered recovery mode with the volume button (this is the standard android recovery) tried clearing cache and rebooting, same problem... tried "wipe data / factory reset" same problem. No matter what I do it doesn't boot past the motorola logo.
Any ideas? I read about RSDLite and downloaded a stock sbf but my phone isn't recognized by RSDLite while not booted... even in the recovery utlitiy no connection is made (USB Debugging is off I think).
Any help would be very much appreciated. I am kind of freaking out, I just got the phone a few days ago
Thanks so much,
MrPink52
before u turn your phone on hold vol+ key until it loads the bootloader for rsd lite
Didn't want to make the first post overly long or complicated so here a quick update.
I read somewhere else that I could get a connection in RSDLite by holding volume up while booting and entering the bootloader... that seemed to work, so chose this SBF File "JRDNEM_U3_2.21.0" from and developers and told RSDLite to flash it... it said complete...the display then turned black... and now I don't have any image at all. It is still found in RSDLite but nothing happens when I boot... and I don't even see the logo anymore.
Now I will definetly stop trying until someone here can hopefully help me.... it seems like me trying by myself is only making things worse
Please tell me there is still hope for my Def.
Thanks,
MrPink52
When the red M logo is on the screen the led should turn blue for a few seconds, at this point press the Down Volume key & you should then go into ClockworkMod Recovery. I would try clearing the cache from there or maybe even doing a factory reset.
you will probably have to flash stock and start over
gramps50 said:
When the red M logo is on the screen the led should turn blue for a few seconds, at this point press the Down Volume key & you should then go into ClockworkMod Recovery. I would try clearing the cache from there or maybe even doing a factory reset.
Click to expand...
Click to collapse
I already tried that, like I said it didn't start the ClockWorkMod but instead the standard Android recovery Utlity which only has limited options... but now as I have described, the problem has gotten worse... I can't even get in there anymore after flashing with RSDLite.
Help!
MrPink52
im in us and my stock file is this one p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
pmp326 said:
you will probably have to flash stock and start over
im in us and my stock file is this one p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
Click to expand...
Click to collapse
I took the one listed for Germany. My phone isn't branded so I tried to flash it with the sbf that seemed to fit.
Can you tell me exactly how I can do this correctly?
I may be doing something wrong with RSD Lite... but slowly I am really affraid I have bricked my Defy for good
MrPink52
after you flash go into stock recovery vol- key and factory reset then reboot should work fine then
pmp326 said:
after you flash go into stock recovery vol- key and factory reset then reboot should work fine then
Click to expand...
Click to collapse
That gives me hope... the problem is I can't press vol- after flashing... the screen just stays black... I can reflash it and I get white writing on the screen "Updating SW" but when its finished the screen just turns black again... and neither Vol+ nor Vol- during boot does anything.
Any further advice?
try another sbf the one ur flashing isnt the right one
it should show a gray motorola logo when u go to boot
i think this is the one u neeFull SBF name ::JRDNEM_U3_3.4.2_179-6.1_TMNAB_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PD S03C_USAJRDNFRYOTMDE_P016_A013_M005_HWp3_Service1F F.sbfd
Do you have a direct link? I couldn't find it on the and-developers site... so a direct link would be great!
Until then I guess it can't hurt to try various sbf files to see if one works.
The only thing I am afraid of, is that my battery will dy during the flashing... is there a way to charge the battery in my current state? Or will it only charge when Android is booted?
Thanks for your support so far,
MrPink52
go here and follow directions in this thread http://forum.xda-developers.com/showthread.php?t=1175801
after reading that is the only one i could find for ya hope it works for ya
if u can get into a recovery it will charge when plugged in
I have tried some of the sbf files... and tried this one: JOREM_U3_3.4.2_177-003
that seemed to work, at least I got the logo back and could enter the Android utilities... and it seems like it is booting up blur right now... wow... what a scare.
Don't know if I will try to move to CM7 again anytime soon... I don't know what went wrong since I tried to follow tutorials.
But again thank you for your help.. I will update here again when I know for sure that everything is working
your fine dont let that scare you just wrong file its not the end of the world anyways enjoy!!!
I just did mine last night and at times it was a little scary, being the 1st time I had tried to flash a phone. I followed these directions to a point.
http://forum.xda-developers.com/showthread.php?t=897445 I also used these directions pretty much combined the 2 to get the job done. http://forum.xda-developers.com/showthread.php?t=1065798
When I got to the point where CM7 RC1v2 was installed along with Google Apps I then rebooted and let it all start and create all the necessary caches. I then flashed the nightly from the sd card.
I did NOT do the 3g stuff mentioned in the instructions, There is an app that will let you set your baseband for your country in the app drawer called Defy Baseband
Hi guys
I've searched the forum for something like this but I'm coming up empty handed. But then again, I'm freaking out a bit.
I just tried flashing ARHD 9.7.0 and I've hit a big snag... For a bit of background, I was previously running ARHD 9.4.2 with the Endeavoru-Faux123-010b3 kernal. The battery was at 35% when I started the process...
I downloaded the zip, put it onto my SD card and rebooted into CWM. No worries there.
Did a wipe/factory reset and wiped the cache aswell. No worries there.
I did NOT flash the boot.img in the zip as I believed it would work okay with the current kernel (possibly the issue)
Went to install zip from SD card and chose the zip to install. AROMA starts up and I go through the familiar install process. No problem there.
I checked the reboot now option in AROMA and let it reboot. This is where the fun begins...
I get the beepy boopy start up sound and let it sit there because, as we all know, first boot can take a while. 10 minutes later, it's stuck at the HTC One splash screen. So I thought I'd reboot into CWM and start over like I've done with other ROM/kernal incompatibilities.
So I hold down the power button, let the three lights blink and the screen go blank and hold down the volume down button. And it goes back to attempting to boot up. I've tried different combinations of holding the buttons down and letting them go and hell, I've even sat there hammering the volume down button while it starts up! Still, I can't get into the bootloader.
Obviously, no bootloader, no ADB connection so I can't go through CMD and can't re-flash the kernel.
I'm currently sitting here looking at it. The USB cable is plugged in and the orange light is lit up so I hope it's charging. I'm at a loss here guys. Please, if anyone can give me some help, I will be most appreciative.
I'm really sorry to have wasted your time. It worked eventually after about 50 tries! :laugh:
Looks like it ws a kernel incompatibility.
But out of curiosity and for anybody else who gets this problem and really can't boot into the bootloader, what would be the steps involved in recovering a device in that state? I'd rather look like a knob in public as long as something constructive comes from it. :silly:
It's a bit tricky to get into hboot after a forced reboot, I think we've all been there
Just avoid the problem altogether by flashing the boot.img inside the zip first to make sure that it boots. Once up and running, flash your custom kernel and modules.
Try this http://forum.xda-developers.com/showthread.php?t=1734365
And don't let go when reboots keep hold of buttons and it should go to bootloader
Sent from my HTC One X using xda premium
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
rfgamaral said:
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
Click to expand...
Click to collapse
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Tarima said:
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Click to expand...
Click to collapse
Tried to reflash Maximus, didn't work, still didn't boot. Backed up everything I could and wiped everything, I'm now on Lineage OS 16.0. Thanks for your reply.