Related
Being the noob I am, I can't post this question in the dev forum. Does anyone know if Liberty is compatible with safestrap or not? I know the official instructions says CWM only, but I have read that many install using safetstrap without any problems.
That said, I for the life of me can't get it to boot after install. Are there any special tricks to get it to work with safestrap? Being a noob to Android (this D3 is my first foray into Android), I would like to stick with safestrap until I am very comfortable since it is rather idiot-proof. Thanks!
uconnjack said:
Being the noob I am, I can't post this question in the dev forum. Does anyone know if Liberty is compatible with safestrap or not? I know the official instructions says CWM only, but I have read that many install using safetstrap without any problems.
That said, I for the life of me can't get it to boot after install. Are there any special tricks to get it to work with safestrap? Being a noob to Android (this D3 is my first foray into Android), I would like to stick with safestrap until I am very comfortable since it is rather idiot-proof. Thanks!
Click to expand...
Click to collapse
The thread at RootzWiki in the dev section for Droid3 is very helpful.
Some of the things to double check:
- Make sure you're swapping to "safe mode" before flashing the .zip
- Wipe data/cache
It works fine with safestrap
Sent from my DROID3 using xda premium
I have been switching to safe mode, clearing data/cache, rebooting, installing the ROM zip (with no apparent errors), clearing data/cache again, and then trying to boot the ROM, but it just hangs on a blank screen for >20 minutes before I pull the battery. Tried this a few times, even redownloading the zip, but its always the same.
Steel Droid and Maverick have worked fine, but just can't seem to get Liberty to work. I have reviewed and seacrhed the forums, inluding rootwiki, hoping there was some special trick that needed to be done with this specific ROM, but have found nothing.
Maybe I will try installing an older Liberty ROM to see if that works' and also maybe reinstalling safestrap, maybe even rerooting.
Any ideas?
Sent from my DROID3 using Tapatalk
uconnjack said:
I have been switching to safe mode, clearing data/cache, rebooting, installing the ROM zip (with no apparent errors), clearing data/cache again, and then trying to boot the ROM, but it just hangs on a blank screen for >20 minutes before I pull the battery. Tried this a few times, even redownloading the zip, but its always the same.
Steel Droid and Maverick have worked fine, but just can't seem to get Liberty to work. I have reviewed and seacrhed the forums, inluding rootwiki, hoping there was some special trick that needed to be done with this specific ROM, but have found nothing.
Maybe I will try installing an older Liberty ROM to see if that works' and also maybe reinstalling safestrap, maybe even rerooting.
Any ideas?
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Check the MD5, mine kept doing that until I downloaded over 3g. Downloading over 3g finally gave me an MD5 match
Sent from my DROID3 using xda premium
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Lyxdeslic said:
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Click to expand...
Click to collapse
It has a different way of reporting battery usage, it doesn't affect it though (based on 5.6.890) I've had my phone on for 9 hours now, medium usage, and I'm at 86%.
Lyxdeslic said:
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Click to expand...
Click to collapse
If flashing from the last version of Liberty there shouldn't be a need to wipe, I didn't anyway. It took quite a while, more than 5min, to finally boot just after flashing. As far as the 10-15 second delay, that is how safestrap works. 10 seconds at the safestrap splash screen and about 10 seconds of black before the bootanimation. Though I'm not sure of why the later takes so long. For me the previous version of Liberty took just as long to boot.
Yup, that was it, the MD5s would not match up until I downloaded over 3g. Wireless or PC->phone would always have mismatched numbers. I didn't check the Steel Droid or Maverick ROMS I downloaded wirelessly, but those installed fine regardless. Wonder why the consistent download errors for the Liberty ROM?
Thanks for your help!
uconnjack said:
Yup, that was it, the MD5s would not match up until I downloaded over 3g. Wireless or PC->phone would always have mismatched numbers. I didn't check the Steel Droid or Maverick ROMS I downloaded wirelessly, but those installed fine regardless. Wonder why the consistent download errors for the Liberty ROM?
Thanks for your help!
Click to expand...
Click to collapse
I don't know why either I figured it was my router having a moment, but you're the second other person I've helped with that.
eww245 said:
If flashing from the last version of Liberty there shouldn't be a need to wipe, I didn't anyway. It took quite a while, more than 5min, to finally boot just after flashing. As far as the 10-15 second delay, that is how safestrap works. 10 seconds at the safestrap splash screen and about 10 seconds of black before the bootanimation. Though I'm not sure of why the later takes so long. For me the previous version of Liberty took just as long to boot.
Click to expand...
Click to collapse
If you want to use the new lockscreens or themes you'll need to preform a data wipe, Kejar said so himself.
Androidsims said:
I don't know why either I figured it was my router having a moment, but you're the second other person I've helped with that.
If you want to use the new lockscreens or themes you'll need to preform a data wipe, Kejar said so himself.
Click to expand...
Click to collapse
Using ring lockscreen, haven't tried any of the themes though. I'm suprised it did work actually.
I'm running it with safe strap right now not the best battery life but it'll do til hash gets ics running (which I know he will cm7 is my favorite but need tethering and camera)
Sent from my DROID3 using Tapatalk
My md5 sum is correct and I've cleared the data/cache but I only get a black backlit screen for 20 min + til I remove the battery. Anyone got a tip of what to do?
Sent from my DROID3 using XDA App
kAmaOn said:
My md5 sum is correct and I've cleared the data/cache but I only get a black backlit screen for 20 min + til I remove the battery. Anyone got a tip of what to do?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
SBF back to stock 5.6.890, reroot, reinstall safestrap, re-do EVERYTHING pretty much. Thats my solution to everything.
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..
Phone was running fine. Decided to try a new Rom. Tried 3 different ones and none of them will boot! I see the HTC letters on screen and that is it. I've let it sit for more than 30 minutes. Still using CWM 2 something.
SiNJiN76 said:
Phone was running fine. Decided to try a new Rom. Tried 3 different ones and none of them will boot! I see the HTC letters on screen and that is it. I've let it sit for more than 30 minutes. Still using CWM 2 something.
Click to expand...
Click to collapse
Try updating cwm. Look for dastins recovery thread
Sent from my SCH-I535 using xda app-developers app
SiNJiN76 said:
Phone was running fine. Decided to try a new Rom. Tried 3 different ones and none of them will boot! I see the HTC letters on screen and that is it. I've let it sit for more than 30 minutes. Still using CWM 2 something.
Click to expand...
Click to collapse
Are wiping everything first?
Cache, system,data,delvic cache?
First time I tried to install cm7 it got stuck on HTC screen. I ended up installing cm6 which went fine then loaded cm7 on top of it.
This worked for me maybe for you?
Good luck hope this helps.
Hello All,
I'm not that new to the XDA scene as I've been rooting for a couple of years now (HTC Aria, HTC One XL), however I am completely stumped as to why my HP Touchpad keeps randomly rebooting while in android. Here's the TL;DR
1. Installed moboot 0.3.5, CWM 1012, and CM9 20121212 Nightly using ACMEInstaller2.
2. Everything installed fine, except device randomly reboots within 5 min of starting up, sometimes immediately (before I can even unlock the display), sometimes even while loading the cyanogenmod splash screen.
3. I have read everything on the XDA's about this problem and scoured Google for hours to no avail. Tried clearing cache, Dalvik cache, then fix permissions. Still randomly reboots. Tried turning off beats audio in webOS. Still randomly reboots. Used ACMEUninstaller, erased webOS completely, re-rooted using ACMEInstaller3, moboot 0.3.5, CWM 1012, and CM9 20121212 Nightly. Still Randomly Reboots.
I am at the end of my ropes here, about to give up and just accept that my device is not compatible with android, even though countless others are running android with little problem. I'm just not understanding what I am doing wrong, if anything. Any comments / advice would be very much appreciated.
Peace and Love
That's odd. Maybe try a different ROM?
bananagranola said:
That's odd. Maybe try a different ROM?
Click to expand...
Click to collapse
I've tried CM7 Alpha 3.5, CM9 Nightlys, and CM9 Fat and Creamy by SGA. CM7 was the most stable, but still I had many FC's and random reboots, though not as many as CM9.
leetpcguy said:
I've tried CM7 Alpha 3.5, CM9 Nightlys, and CM9 Fat and Creamy by SGA. CM7 was the most stable, but still I had many FC's and random reboots, though not as many as CM9.
Click to expand...
Click to collapse
I would try wiping cache and dalvik-cache. Aside from that, I'm out of ideas.
bananagranola said:
I would try wiping cache and dalvik-cache. Aside from that, I'm out of ideas.
Click to expand...
Click to collapse
Just tried that and it rebooted before I could even navigate to No-Frills CPU Control :/ I appreciate the input though.
It seems that once it boots, if i don't touch anything, it will not reboot while at the lock screen. I've had it charging for the past 4 hours or so while booted in CM9 and haven't ventured past the lock screen and it hasn't rebooted yet.
When you unlock it, see if you can find out what the min cpu speed. If it's @ 192, try 384 or even 432 and see if that makes a difference
Sent from my ThunderBolt using xda premium
rrrrrrredbelly said:
When you unlock it, see if you can find out what the min cpu speed. If it's @ 192, try 384 or even 432 and see if that makes a difference
Sent from my ThunderBolt using xda premium
Click to expand...
Click to collapse
I have tried both of those as well as setting both the min and max frequency to 1.2 GHz. It still reboots; seems to be independent of CPU clock speed.
I've also tried disabling all haptic feedback as well as turning the sound all the way down and turning off the keypress sounds. Still reboots.
i had the same issue. i used acmeuninstaller and removed android completely. downloaded the latest CM9 nightly and CWM and such. used acmeinstaller to install CWM, then I installed CM9 and gapps manually via CWM. check out jscullins latest CWM build. it may help.
Are you using the right Gapps zip? If you flash CM9 and are using Jelly Bean Gapps, it may have problems trying to run the Google setup at start since its meant for Jelly Bean. Just a thought.
It may be a block of bad Nand memory. Similar problems have been seen / noted in some of the other tablet forums (I hang out a lot in the Advent Vega forum) and this is not totally unknown, although not that common. It may just be an area that hasn't been used or is avoided by Webos, but comes into play with Android and the extra partitions.
Only suggestion from me would be to try AcmeInstaller3 if you haven't already as that sets different partitions to AcmeInstaller2 to allow for the space needed for CM10, but will work fine with CM9.
slicetwo said:
i had the same issue. i used acmeuninstaller and removed android completely. downloaded the latest CM9 nightly and CWM and such. used acmeinstaller to install CWM, then I installed CM9 and gapps manually via CWM. check out jscullins latest CWM build. it may help.
Click to expand...
Click to collapse
The only thing I did different than what you suggested here is let the ACMEInstaller3 install CM9 for me. I have not tried jscullins build of CWM though, I will give that a shot and also try installing the ROM manually after ACME has installed CWM.
jsgraphicart said:
Are you using the right Gapps zip? If you flash CM9 and are using Jelly Bean Gapps, it may have problems trying to run the Google setup at start since its meant for Jelly Bean. Just a thought.
Click to expand...
Click to collapse
I'm 99% sure I was using the right apps, and usually I can make it through the setup portion of the initial boot without a restart. Doesn't last too much longer than that though...
dmarchant said:
It may be a block of bad Nand memory. Similar problems have been seen / noted in some of the other tablet forums (I hang out a lot in the Advent Vega forum) and this is not totally unknown, although not that common. It may just be an area that hasn't been used or is avoided by Webos, but comes into play with Android and the extra partitions.
Only suggestion from me would be to try AcmeInstaller3 if you haven't already as that sets different partitions to AcmeInstaller2 to allow for the space needed for CM10, but will work fine with CM9.
Click to expand...
Click to collapse
I've used ACMEInstaller3 the last two times I reverted everything to stock, erased and reset webOS, and started over. Still had the same problems as when I used ACMEInstaller2.
youre doing something wrong,, probly something simple..
have you looked @ youtube?
roland has some good vids.
so does reverendkjr