Related
i was trying to test all the 2.3.4 roms nd now my phone wont go past the white htc screen even when i restore 2.3.3 help?
If it turns on it's not bricked
Re-download a rom zip, boot to recovery, wipe everything, then flash the rom
(assuming you can still get to recovery [HOME+POWER] since it wasn't mentioned)
Sent from my Android using Tapatalk
i can get to recovery but when it says that i sucessfully flashed the rom then i go to reboot system it just stays at the white HTC screen idk wat to do my nandroid wont even work now its doing the same thing i have no clue what i did wrong?
are you using firerat's?
wiping before restoring nandroids/flashing a new Rom?
what recovery are you using?
what rom is your nandroid?
have you tried to re-download the rom you are flashing? (the one that stays on the HTC screen)
How long is it staying on the HTC screen?
do you have adb installed?
Sent from my Android using Tapatalk
just FYI, next time you ask for help you should post some of the answers to kyouko's questions without anyone having to ask. we can't help you as well if we don't know these things.
I put 5$ on the ROM he was flashing uses an uncapped kernel...
3 letter word; RUU.
Start from scratch and be careful what you flash before you flash it
Happy flashing buddy. Be careful!
Sent from my HERO200 using XDA Premium App
Maybe you just need to let it sit on the HTC screen for a while longer to see if it finally starts booting up. Sometimes it can take a couple of minutes. Try not to watch it, if you can.
scataldo721 said:
i was trying to test all the 2.3.4 roms nd now my phone wont go past the white htc screen even when i restore 2.3.3 help?
Click to expand...
Click to collapse
If your still having problems send me a pm I might be able to help. Good luck.
#Root/Hack-Mod_Always*
Drunkpilot said:
Maybe you just need to let it sit on the HTC screen for a while longer to see if it finally starts booting up. Sometimes it can take a couple of minutes. Try not to watch it, if you can.
Click to expand...
Click to collapse
I've had them go as long 5 mins. or so
WOW! HOLY CRAP THIS PLACE IS DEAD! Its been a while since I read around these Zio places. Yup, my ol Zio still bootlooped (its around here somewhere). I tried all the "guides" n zip's and skd's and all that other.....stuff, its koo gathering and installing stuff and gettin that lil rush of hope, but then one lil thing goes wrong or ain't in the step-by-step guied, BOOM- all bad, and nobody's around all of a sudden. Alot of HERE, TRY THIS POST FROM SO N SO (not for the Zio), GO TO BLAHBLAH.COM install that n profit (evil setup to rom someone's phone AND wipe it clean), BUT ITS ALL MY BAD, NEWBIE like me shouldn't mess with roots n roms. Don't get me wrong, if I can find somebody that would fix it for cash, id go back to my zio and chuck this HALLWIE A2 (whatever its called) to a dev. Well, I'm probly gona get smashed for posting this. DEEEEP BREATH........K, I FEEL BETTER NOW.
Now I'm soo broke I cant even pay attention!
What you need help on? Bootloop fix? I can help you. Pm me on the details. Could you still get into faatboot or recovery? What service sprint or cricket!?
Sent from my Zio using XDA App
My zio is messed up too. I have no home/launcher or whatever you wanna call it. I can't get to settings to enable usb debugging either so none of the adb stuff works for me (so far). New to this and I don't want to buy another phone just yet. More details can be provided as to how this happened if needed. ty.
Not sure where it is but there was a fast boot zip of launcher apk. If you boot your phone into fast boot and cwm copy the zip to the phone and then flash the zip to your Zio it should resolve the issue
Sent from my Zio
Krsmqn said:
My zio is messed up too. I have no home/launcher or whatever you wanna call it. I can't get to settings to enable usb debugging either so none of the adb stuff works for me (so far). New to this and I don't want to buy another phone just yet. More details can be provided as to how this happened if needed. ty.
Click to expand...
Click to collapse
I can make a launcher apk. flashable zip for ya,just let Me know.
Sent from my LG-P509 using xda premium
openZIO Rom issue
Hi, I just installed the openZIO 2.1.2 ROM. Everything worked fine, but after rebooting and going through the initial set up (i.e. the google user setup blahblah) the VTL Launcher continually force closes and I can't do anything but go back and recover my original boot.img has anyone else had this kind of issue? Any possible fixes? Any help would be appreciated, I know not to many people are in using the Zio forums anymore... but yeah.. Thanks in advance
Try Reflashing again
Sent from my LG-P509 using xda premium
I've actually already done that, and it's still doing the same thing. I've deleted and re-downloaded the ROM, and re-flashed it to my phone, and still having the same issue. VTL Launcher just continually force closes, and it sucks cause I've been waiting months to get to install the ROM cause I couldn't afford a new USB cord. I've read so much on this ROM and everything for the Zio and was excited to actually be able to overclock my phone, and get some pretty good performance boosts out of it. Now I got one, and can't get it to work.. what a sad day
Could you explain your steps when flashing?
Sent from my LG-P509 using xda premium
well I first move the .zip to the sd, then power down and boot up CWM, and "install from SD card" and once it's finished flashing, I reboot the phone. when it comes back up my kyocera logo comes back up and it takes me through the first-boot programming (google sign-in) and once I input my un/pw and sign in, it tells me that VTL had an error and must hit force close. and once I hit force close it continues to come up saying the same thing over and over again. so I rebooted my phone, still the same thing. SO I go back through and flash it back to my original boot.img. I have gone through and completely deleted the openZIO 2.1.2.zip file and re-downloaded it, and gone through the same steps to see if maybe it was just a bad file somehow. But to no avail, still having the same issues.
After you boot into cwm : wipe cache partition, then go into mounts and storage, format: system, data, cache :then go into advanced and wipe dalvick cache.
Now flash rom
Sent from my LG-P509 using xda premium
Ok just went through with what you had mentioned, and still getting the same results. "Sorry! The application VTL.Launcher (process android.process.acore) has stopped unexpectedly. Please try again. with the only option to force close. As soon as I force close, the same message pops up
Have you tryed flashing my rom?
I would try that, and see what happens.
You can always push a launcher with adb or Droid commander.
Sent from my LG-P509 using xda premium
doing this now actually.. been reading for the last hour or so and seems like you did some good work on the ROM. it's flashing now, hopefully all works well I'm excited to see how it goes.
Well it flashed and well... seems to be having a strange issue.
When switching screens, it seems to glitch out? Like you see the icons, and when you switch screens, it's like the icons move but it freezes different frames. imma re-flash it in the morning to see if that helps any.
XCmaster said:
doing this now actually.. been reading for the last hour or so and seems like you did some good work on the ROM. it's flashing now, hopefully all works well I'm excited to see how it goes.
Well it flashed and well... seems to be having a strange issue.
When switching screens, it seems to glitch out? Like you see the icons, and when you switch screens, it's like the icons move but it freezes different frames. imma re-flash it in the morning to see if that helps any.
Click to expand...
Click to collapse
Im outta suggestions, I think you might have a hardware problem, but can't be for sure on that.
I've never heard of anybody having that problem, let me know if you get the issue resolved
Sent from my LG-P509 using xda premium
could defiantly be, this phone is well over a year old and has been dropped quite a number of times lol.
XCmaster said:
could defiantly be, this phone is well over a year old and has been dropped quite a number of times lol.
Click to expand...
Click to collapse
Was your phone acting like that before you flashed openzio?
Sent from my LG-P509 using Tapatalk 2
Nope, I've never had these issues before. And I can still flash it back to my original boot.img and it works like before. I've never had any problems with it, so that's why I'm surprised this is happening lol
XCmaster said:
Nope, I've never had these issues before. And I can still flash it back to my original boot.img and it works like before. I've never had any problems with it, so that's why I'm surprised this is happening lol
Click to expand...
Click to collapse
I guess then its probably not a hardware issue.. hmm.. its almost Like the roms your flashing are getting corrupted some how.
Sent from my LG-P509 using Tapatalk 2
hmm.. .well maybe I'll format my sd and do a factory reset on the phone first, then try to flash the rom?
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Maybe he dont follow the instructions correctly
Sent from my GT-N7000 using xda premium
meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
What method is he using to flash? If using pc Odin does the flash get stuck at factoryfs. Img?
Was he on ics stock and did he perform any factory resets on it?
If answers are yes, it's likely he's got traces of damage on his emmc chip, but we need to know where the flash is failing to understand further.
Sent from my GT-N7000 using xda premium
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
meminiau said:
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
Click to expand...
Click to collapse
Try flashing rom with pc odin instead of cwm.
Check out Dr ketan sticky thread in rom development for directions on how to use pc odin. It's simple.
Let us know how you progress.
Sent from my GT-N7000 using xda premium
meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
No problem at all.
Sent from my GT-N7000 using xda premium
What?????
Swiped on my Gnex
Sounds very odd - only though is he's not following instructions correctly..
Now before we all jump to conclusions, let me explain what I HAVE tried and what caused it.
1) I HAVE tried various roms, including stock.
2) I HAVE tried various kernels.. including stock kernel at 600 mhz..
3) There are no reboots when in I'm in recovery.. but in the OS, it reboots within 3 minutes. ANY OS..
4) I tried wiping EVERYTHING.
5) Once I tried fixing this when I went from CWM to TWRP, for some reason, that fixed everything, but 5 days later, now on Nit-picked sense rom, the problem returned.
6) I tried returning to stock 600mhz kernel but it still reboots.
7) yes, I've factory reset it several times now
Here are my conclusions..
1) it is NOT because of frequency
2) it is NOT individual rom at fault
help would be appreciated
Update
The problem solved itself after I reflashed recovery and installed a rom.. but I see a familiar circle here.. a few days later, it'll start behaving like that again
just as predicted.. happened again.. can someone atleast tell me what the cause is?
Check if the battery is okay.... It could be because of a lose connection or something... Otherwise there shouldn't really be any reason for your phone to reboot like that.
Sent from my HTC Desire C using XDA Premium 4 mobile app
thanks for your reply.. but no, I dont think thats the case, I've kept the phone on in recovery for many hours when that happened, nothing.. no problem while flashing either..
once I'm in my new custom OS, sometime while choosing if I'd have data synced manually, it restarts... any rom..
but, when I reflash recovery, it seems ok... last time I did that was when I posted my previous reply, it betrayed me again today.. was fine for nearly a week...
Another thing could be that your RAM is used up and your phone freezes... It's happened to me. So try using zRAM or RAM manager pro or something and see if it helps.
Sent from my HTC Desire C using XDA Premium 4 mobile app
Do you have mobile data turned on? I had the same problem on my desire c it rebooted when data was on. Try to disable data as soon as it turns on! It's unexplainable it randomly went away.
Sent from my C5303 using xda app-developers app
Alright im not new to flashing roms, I am unlocked, s-off and have a custom recovery, the other day I wanted to try a CM11 rom, everytime i tried to install the rom on my phone through TWRP it would fail, after reading up on a few threads, I decided to upgrade my firmware and change to clockwork mod recovery. after doing that i was able to install the cm11 rom, i used the rom for a few days and decided i like sense roms more so I wanted to install viper rom like i have a million times before without issue. clockwork mod would not allow me to install viper rom, so I switched back to TWRP through i believe it was rom installer from the play store, it asked to install busybox after, and i believe it said something about switching mounting points, I said yes like an idiot not knowing what I was doing, anyway now i am at the point where TWRP is on my phone, i cannot ruu back to stock because it is failing at 4% giving me an error, and when i fastboot install it i get (bootloader) read zipped android info fail
FAILED (remote: 24 parsing android-info fail) CHECK THE PICTURES
I have tried relocking bootloader then running the ruu zip though fastboot, didnt work, I have tried a nandroid backup, that didnt work either. When ever i install any roms now, they act like they install just fine but when the phone boots up, it runs me through the startup wizard, and from there the phone just keeps getting phone dialer force close about half way through, and from there it will boot loop after and acts like it is setting up the phone everytime, Any body have any ideas of what I did to mess this up, or how to fix it??
Try flashing your radio.
Sent from my HTCONE using XDA Free mobile app
n0mad73 said:
Try flashing your radio.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Hmm alright I'll try that and report back my findings, did you also notice in the bootloader menu pic where is says OS, there is nothing after that, I was reading through other peoples Help forms for an answer, and they have version numbers and all that, where I just recently noticed mine is just blank after it says OS.
My OS field is also blank; no issues with that.
Sent from my HTCONE using XDA Free mobile app
Wow!!! YOU ARE THE MAN!! the radio was the problem, after installing it, no more bootloops on any roms. Thank you.
No problem!
Sent from my HTCONE using XDA Free mobile app