First off i want to make known that I have been on may different custom roms & just comming from RCmix 234 2.7.
The other day I tried using cwm to restore a previously saved rom that I had backed up & switched to many times before but I would not work. Then today I tried to go back to a previous version through recovery, which I have done in the past. (I Believe I was having superuser issues)
I have tried multiple different roms & the device keeps getting stuck on the white HTC screen before going to the bootloader screen for the particular rom I am trying to install.
I have even started over again by going back to basics.... PD98img, root, s-off, eng-off, install root checker, & rom manager...... up to this point everything is working but If I try to install either via cwm, or through recovery I keep getting nothing but the White HTC Screen
Any ideas before I attempt to put all back to stock again.... & send in for repair?
Many thanks in advance.
Ok Now.... i have been able to restore the old backup I have using recovery, I attempted through rom manager but it would only just opened recovery so I attempted to flash any zip from a new rom...... but why wont it work as it would before? It only freezes on the white htc screen
HTC White Screen
Anyone know why when trying to flash a new rom that it hangs @ the HTC White Screen?
System Partitions?
Since I all of a sudden cannot reboot after flashing a rom.... does my system partition free space of only 14.8MiB be the cause of why it wont boot fully when asked to re-boot from recovery?
Am I forever stuck with the backup I created weeks ago, its the only rom that goes to the boot img of the rom which is just past the white htc screen.
Thanks for helping.
Well I hope I solved it.... somehow Recovery seems changed to mabey a new version, & it seems that the roms I was using were ext3 roms & I was led to believe I needed the ext4 full wipes which modded my configuration to ext4.
Switched configuration back to ext3 & now roms boot up past the white screen.
i have the same problem with this rom RCMmid3d Bliss i stuck in splash screen..i tried the recoveries 4ext and clockworkmod but at all i stuck there..
shadowman110 said:
i have the same problem with this rom RCMmid3d Bliss i stuck in splash screen..i tried the recoveries 4ext and clockworkmod but at all i stuck there..
Click to expand...
Click to collapse
I found a fix.... restore your saved rom, assuming you have one.
1) Update cwm to the newest version
2) reboot into recovery & find the format ext3 option & format to ext3
3) Choose whichever rom you like (I went back to RCMIX 3D 234 V2.7) Install
4) Reboot & be rid of that pesky issue
Please hit the thanks if this helped!
gixer131 said:
I found a fix.... restore your saved rom, assuming you have one.
1) Update cwm to the newest version
2) reboot into recovery & find the format ext3 option & format to ext3
3) Choose whichever rom you like (I went back to RCMIX 3D 234 V2.7) Install
4) Reboot & be rid of that pesky issue
Please hit the thanks if this helped!
Click to expand...
Click to collapse
Nice find!
the 3.5 sense roms are temperamental at best to some users right now, though capy of rcmix with his new update seems to be working well just keep in mind its truly a beta still. as for issues with flashing and getting the roms to fully boot is mostly a recovery issue and that only. as long as u r not only wiping all before the flash, but also formatting everything there should be very little to nothing left that could cause any issues at all. i recommend first using ext4 for recovery especially if that is the type of roms u r using. if the rom doesn't format the system to ext4 and u have wiped with cwm recovery u could of reverted back to ext 3 and now your rom is going to loop or lock up for sure. u can always flash new version of ext4 if ur back ups don't restore also, this happenes if a rom manager update is an issue with ext4 and on a few of the old non-final versions. good luck, though u seem to be back up and running already
Related
hi there, i really need some help..not a tech genius..i installed the gingervillian 1.5 rom..everything went fine, but i forget to make a nandroid back up..when i install it was too late and my nandroid back up now is the gingervillian rom itself!..i dont really like the gingervillian because it wont work with htc sync. i have googled and tried so many ways i cant use other roms except gingervillian 1.5. all other roms just get stuck at the htc boot screen(for like 5 hours!)..factory reset dont work, full wipe dont work..i just need help on how to get back the original rom of the desirez 2.2 froyo..thx a lot..my life is counting on u genius out there!
I am assumng that you flashed CWM Recovery 3.0.0.x (orange) to install Gingervillian in the first place, right? Well in order to flash a Froyo version rom you need to flash the CWM Recovery 2.5.1.3 (green) back onto your phone prior to trying to flash a Froyo (2.2) based rom.
Update: The new CWM 3.0.0.5 recovery from ROM Manager now support both 2.2 and 2.3 roms.
joemm said:
I am assumng that you flashed CWM Recovery 3.0.0.x (orange) to install Gingervillian in the first place, right? Well in order to flash a Froyo version rom you need to flash the CWM Recovery 2.5.1.3 (green) back onto your phone prior to trying to flash a Froyo (2.2) based rom.
Click to expand...
Click to collapse
yes i did flash cwm(orange)..i also revert back to green (2.5.1.3), but where do i get the froyo rom?..i did get 1 from modaco but it wont work..i am now in the CWM Recovery 2.5.1.3 (green), but every rom i install stuck on the htc boot screen..
rottenapples said:
yes i did flash cwm(orange)..i also revert back to green (2.5.1.3), but where do i get the froyo rom?..i did get 1 from modaco but it wont work..i am now in the CWM Recovery 2.5.1.3 (green), but every rom i install stuck on the htc boot screen..
Click to expand...
Click to collapse
What particular ROM's have you tried? Are any of them still on your sd card?
i tried 'Z ROM v2.0' and 'modaco r2 rom' and yes still in my sd
Have you been clearing the data and cache partitions after flashing new roms?
Sent from my T-Mobile G2 running Cyanogenmod.
rottenapples said:
i tried 'Z ROM v2.0' and 'modaco r2 rom' and yes still in my sd
Click to expand...
Click to collapse
I'm unfamiliar with those ROMs but if they aren't built for the Desire Z and/or TMobile G2, then that is your problem. The best place to get your ROMs is in the Development thread here:
http://forum.xda-developers.com/forumdisplay.php?f=758
If the ROM you have is specifically built for your phone and is on the sd card then:
1 boot into recovery
2 wipe data/factory reset
3 (still in recovery) advanced>wipe davlik cache
4 (still in recovery) mounts and storage>format boot & format system
5 flash the zip from the sd card
6 reboot system (you may need to reboot a second time on some ROMs for everything to work correctly)
thanks man
Thanks man
edkeys said:
i'm unfamiliar with those roms but if they aren't built for the desire z and/or tmobile g2, then that is your problem. The best place to get your roms is in the development thread here:
http://forum.xda-developers.com/forumdisplay.php?f=758
if the rom you have is specifically built for your phone and is on the sd card then:
1 boot into recovery
2 wipe data/factory reset
3 (still in recovery) advanced>wipe davlik cache
4 (still in recovery) mounts and storage>format boot & format system
5 flash the zip from the sd card
6 reboot system (you may need to reboot a second time on some roms for everything to work correctly)
Click to expand...
Click to collapse
is this a known issue? i myself am stuck with GV, nice rom but i want my swype back! lol, anyways will try the green cwm and see what happens
Try finding a stock g2 rom. After that download the zip. Go into recovery mode by pressing power and vol down. Make sure you have clockwork mod recovery. Not sure which version. Mine is orange. Wipe data and cache partition or something. Then install the zip. Should work. Hope I helped.
Sent from my HTC Vision using XDA App
So my phone now will only reboot up to the HTC Incredible white screen. I'm not even sure what the issue is, all i did last before it got stuck was erase data on an old sd card i had in the phone. Then I just did a reboot and it froze on the white screen.
I'm running GB evervolv 2.3.2 with 2.6.37.4 incredikernel.
I can get into HBOOT but when i click on recovery it takes me into fastboot everytime.
What can i do to fix this????
Sorry please move this thread to the Q&A section, i thought that's where I was posting it, my bad.
Go to the Clockwork Recovery thread and download the update for a different version and try getting that to flash via bootloader. That way you can at least get into recovery if you need to flash new. Just to clear it up, did you use your phone to delete stuff off the old card, by using Astro or ES file explorer? I know ES file explorer has root access so is there a chance you could've deleted a system file on accident? All it takes is a click of the SD card icon and you're in root instead of SDcard. Also this is probably a thread more for the Q&A subforum, just an fyi
i deleted an old sd card that i don't even use for my phone, i was just putting it in there to clear out whatever was left on it. so i could use it new.
And it still bootloops even when you put your normal SD card back in?
yup, i dunno what it's deal is.
I remember an older version of cm7 on the nook color warned against formating sd cards because it accidentaly formats the boot partition, this may be a bug that exists in the rom your using.
at least you can get into hboot, you should be able to download ruu image and flash it in hboot. this would get you back to stock, then root and install clockwork, and then restore your latest nandroid.
Flash this recovery in hboot
http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
It should at least give you a working recovery.
i have to rename things as update.zip in order for hboot to flash them right??
facedown41 said:
i have to rename things as update.zip in order for hboot to flash them right??
Click to expand...
Click to collapse
NO leave it PB31IMG.ZIP.
hboot can only see that name. if you rename it hboot will not see it at all.
also make sure your card is formatted as FAT32
got it into recovery so i'm just wiping and restoring, thanks for the help!
ok now i'm getting a bootloop on the cm7 boot screen...i just went to flash that new instead of my nandroid because the nandroid was from an older rom.
Did you wipe everything? Davik, Cache, Data, etc?
wiped data and cache...didn't do davik because i've never had to in the past. but i'll give it a try.
would i need to update CMW from version 2.0+ to 3 in order for cm7 to work? because it's still bootlooping
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
JWorth said:
THIS IS EXACTLY WHAT JUST HAPPENED TO ME!
i was on MIUI 1.3.25 (the newest GB release) and i was formatting an sd card and when i restarted my phone i got stuck at the splash screen! i have been able to boot back into cwm recovery but even when i wipe and flash, nothing works.
i booted into recovery and tried to restart from there - failed
i reflashed 3.18 (wiped cache/dalvik) - failed
i wiped all data and reflashed 3.18 - failed
wiped all, flashed 3.25, fixed permissions - stuck at splash screen again
restored an old MIUI (v1.1.15) - stuck at splash screen
pleaseee let me know if you figure this out
edit:
i ran the RUU and got stock to start working. i'm about to root and try flashing something
Click to expand...
Click to collapse
Are you getting errors when you wipe?like when you wipe data does it say error can't mount or anything like that.... I have a feeling you may have to flash an Ruu and then reroot
Sent from my Incredible using XDA App
no, no errors. but i flashed the RUU and rerooted and everything works just fine. I flashed MIUI again and it worked perfect
thanks!
I figured that's what you would have to do glad you are back running
Sent from my Incredible using XDA App
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
rynosaur said:
I always mount my sdcard in a linux and format/fix/repartion, or at least let Clockwork Recovery do it. I have never found a Sense, Vanilla, or AOSP ROM that handled SD partition operations very well, without at least a little tragedy.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
This tends to be things go as far as ROMs partitioning my sd, always back it up externally and format/partition before transferring stuck back over to it while in phone.
I rooted my Desire yesterday and it worked fine (with the Superuser app showing up and all)
I have downloaded ClockworkMod recovery and that too works fine. I backed up my current factory ROM on it.
I downloaded the devnull.zip yesterday from
Code:
http ://download.oxygen.im/devnull.zip
and installed it on the phone and it is stuck in an infinite android logo loop.
What should I do ? The recovery *.zip file in ClockworkMod does not do anything ..
I am currently downloading a new ROM by Cyanogen CM 7.0.2
Let me see if it works .. =/
Okay .. So I erased the all user data and the old ROM works fine. It doesn't have the Sense UI so I am still going to install the Cyanogen ROM
I think this has to do with one of 2 things.
1. Your version of recovery. If you have ClockworkMod 2.5.0.7 then you will be able to flash most things fine. Later versions of some ROMS require different scripting in later versions of Clockworkmod like 3.0.0.5 but they will normally tell you in the instructions.
If that isn't the problem
2. Your EXT partition on your SD card is not correct or corrupt. Many of the newer sense ROMS built on the new HTC Desire test keys sense don't support EXT4 and you need to format your SD-ext as EXT3
If you are still having an issue and you are S-OFF. You most likely have will have flashed an alternate HBOOT. If that is the case, flash the stock HBOOT, then choose the option reboot bootloader in the fastboot screen.
Should get you back on track.
What is the problem with cm? The download speeds i am getting for the rom are inane. 83 MB is going to take forever @8kbps ..
Sent from my HTC Desire using XDA App
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
DroidUser_Wind said:
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
Click to expand...
Click to collapse
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
DUDE.THANK YOU so MUCH FOR REPLYING.Ill try what you told me tonight,and ill let you know how it goes down.thanks again chills.:good:
chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
What OP wrote applies to me as well. I am looking for something better than aerovan's CM9 (which has been my DD), and thought I would give Viper a try. Without fail, bootlooping (which I could have guessed since I did tacoroot and this seems to be an issue with sense based roms).
That said, I tried steps 1 through 4 and the bootlooping stopped in Viper - it goes through startup and just shuts down before leaving the boot screen. One strange thing that I noticed is that the ICS Firmware/radio with Viper (which I loaded in CWM), wouldn't load in 4ext. Maybe I'll give paranoid a go if I can't resolve this bootlooping issue in Viper! I hope OP has better luck.
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Jasonp0 said:
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Click to expand...
Click to collapse
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
gtdtm said:
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
Click to expand...
Click to collapse
Good call. When chilly said you don't flash kernels in recovery I hit my head. I flashed the radio, but now my challenge is getting back into recovery since I renamed the file and bootloader always finds it and wants to reboot or I load CM9 which stays on flash screen. I'll figure something out, maybe with adb. Thanks.
Power down, pop the sd out, boot to recovery, rename file, profit.
gtdtm said:
Power down, pop the sd out, boot to recovery, rename file, profit.
Click to expand...
Click to collapse
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
digitalshepard said:
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
Click to expand...
Click to collapse
good lucking going back to aosp lol
almost thesame problem
chillybean said:
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
i made a stupid mistake of flashing radio in recovery, in fact the radio is for Samsung at&t and now my phone vibrates it doesnt show htc quietly brilliant, only vibrates and orange light with black screen untill i pull out the battery... i was able to return to stuck and it can only boot if its connected to power, it doesn't read sd card while android is booted and in recovery to, only in bootloader it reads sd... error in mounting if i try to... i flashed RUU.exe 2.3.3 and 2 other RUUs for my droid inc 2 but it keeps vibrating... please help me!!! thanks
I made the same mistake when i first gained s-off for my dinc2. the thing with the venom rom tho is if you ever want to go back to aosp ull need to gets chill's anti-venom zip and flash it through recovery because doing a normal wipe wont do the trick. also a helpful trick that worked for me with roms if i ever start getting boot loops i go into recovery from the bootloader menu and i wipe the dalvik cache under advanced and then wipe the chache under mounts and storage and it always works like a charm for me. but ive also learned that you have to be careful which kernel you flash with the rom of your choice because not only will it cause lags if you happen to get past the boot animation to the main screen but in some cases it can cause breaks in your framework like your wifi data etc. im not an expert tho those are just suggestions that im familiar with because theyve already happened to me before. hope this helps in any way.
Hey there EVO owners,
So I got S-OFF, but now my phone is a little stuck.
I have an EVO 4G that had the stock Froyo 2.2 running.
( We managed to keep it away from the 2.3.5 OTA )
I was able to get S-OFF using Revolutionary for the 2.16 hBoot.
Afterwards, I attempted to use the default CWM to flash the [Triple S] ROM.
- Partitioned ( 0 swap, 1024 ext2 )
- Wiped Cache + Dalvik
- Flashed Triple S
- Rebooted
Result: Boot Loop at the Triple S Android Splash Screen
I thought, "maybe CWM messed up", so I flashed Smelkusmod Amon Ra based recovery and tried flashing Triple S again with the same result.
Now I'm trying to get [JellyBread] and App2SD to flash.
The initial flash did make it to JellyBread's Nexus Android Splash.
After several attempts at wiping and flashing, however, the phone will no longer reach the Android Splash Screen. It gets stuck on the White HTC Evo Splash Screen on boot after flashes.
I have S-OFF
I can boot into Recovery
I've tried a full wipe and proper partition before flashes. (as in wiping everything)
I have tried Smelkusmod's [ext2 > ext3] and [ext3 > ext4] features
What's causing these boot loops?
My girlfriend just needs a stable phone, but it would be nice if it wasn't running all of the Sprint junk that comes stock.
The stock battery life is atrocious.
Any help is appreciated; thanks.
Save your SD to PC
Format using smelks again 1024 swap 0 ext 3
Move everything back to SD card from your PC
Wipe everything except SD card
Flash sense ROM
Be it one of mine or captian throwbacks or who evers
Read the op make sure the rom
Supports ext3
If it has a2sd it will reboot 3 times and take a while to boot
Sent from my PC36100 using Tapatalk 2
I feel like that is exactly what I've been trying to do over and over again.
Do you perhaps have a ROM that you could recommend me flashing?
She just needs something fast and stable.
Is there any reason why I might be having such terrible luck getting this phone to flash and boot properly?