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.
Related
What is happening? Pulled battery 5 times already today...what should I do and would pulling battery as often as this affect my phone or battery?
-------------------------------------
Sent via the XDA Tapatalk App
Anyone?
-------------------------------------
Sent via the XDA Tapatalk App
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
Click to expand...
Click to collapse
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
Click to expand...
Click to collapse
I did wipe prior flashing to Paul's zip with radio.
-------------------------------------
Sent via the XDA Tapatalk App
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
SurfHost said:
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Click to expand...
Click to collapse
does it work?
Im having similar issues with my 2.2 installation. I have it installed on my wife's non-rooted N1.
Not just that but the market is not even usable. Even if I clear cache.
Again, her phone is not rooted, I wipped everything from her phone then applied Froyo and its been a nightmare. Her phone isn't even stable enough to use and I cant seem to figure it out.
I need to find a way back to 2.1 without having to root her phone. She is adamant about me not doing that to her phone even though Ive rooted all the phones I've ever used with no issues.
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Ive tried all that on her phone. I just wiped it again completely and re flashed just in case that was the issue. Phone still had all the issues described in this thread.
I wiped the sd card, wiped all previous system files via the stock recovery and re flashed the update zip. You cant get anymore clean than that and its still so unstable the phone its unusable. I have to either hope soft booting works or pull the battery as a last ditch.
Is there any way I could downgrade her phone to 2.1 without rooting? I tried the shipping rom in the sticky above but it seems that isn't totally legit for stock use because the phone doesn't like how its signed.
I guess I could call google/htc tomorrow but who knows where that'll get me. The only bonus iud that her phone is not rooted so she didn't really have her warranty voided.
-------------------------------------
Sent via the XDA Tapatalk App
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Click to expand...
Click to collapse
I was worried if I was the only one with this problem. Phone improved today (3rd day of using) but I didn't do anything to it. Only hanged once when someone called. Hanged on calling in screen and had to pull battery.
Only once compared to 7 times yesterday!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
does it work?
Click to expand...
Click to collapse
Yes until now it does. Sometimes the power button is reacting a little late but i havent had to pull the battery yet with the older radio.
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
krabman said:
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
Click to expand...
Click to collapse
I'll give this a shot when I get home from work. I'll report back on if it works or not. Thanks for the idea.
Interesting, not that I'm complaining, but after a few days of using 2.2 it seems more stable now....? haven't had any freezes today...yet.
Power button response also getting better.
-------------------------------------
Sent via the XDA Tapatalk App
I haven't had any issues for a few days as well. Still wondering if it had to do with the battery level.
-------------------------------------
Sent via the XDA Tapatalk App
SurfHost said:
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Older radios are not 100% compatible.
Just wiped everything and flashed with Amon RA's recovery straight to FRF83. My phone has rebooted about 7 times over the few hours I've had it. Anyone else experiencing this?
Radio is 4.06.00.12_07.
I went from [email protected]'s FRF50 ROM to his FRF83 using the latest AmonRA. I wiped cache and Dalvik before flashing the zip just to be safe. Aside from it freezing on first boot at the lock screen (battery pull fixed it), I've been good.
Can you link me to his ROM? I had a reboot during first long boot. Freaking annoying!
I went with #2, which is rooted with superuser already installed.
http://android.modaco.com/content/g...-frf83-stock-rooted-deodex-superboot-repacks/
Wiped and flashed that one and I'm still getting reboots. Anyone else have any ideas?
Sent from my Nexus One using XDA App
rickytenzer said:
Wiped and flashed that one and I'm still getting reboots. Anyone else have any ideas?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yes, stop using leaked software and wait for final release.
I'm worried that we're close enough to the OTA that I'll still have these issues when it hits...
Could this be a precautionary thing the phone is doing because of battery temp? Right now it's at 36°C. Is that normal?
Try to boot the phone without the SD card. Good luck!
I had this issue as well but I was also running an overclocked kernel. After I flushed everything (post backup w/ titanium backup) I flushed, reflashed rom, kernel and other mods and I was good to go.....
Alright I did a little digging now that I'm home and have access to ADB.
I pulled the last_kmsg:
http://pastebin.org/362745
I'm no genius but I'm pretty sure that "ARM9 has CRASHED" is NOT a good thing. Also, logcats show noting unusual prior to the reboots.
Anyone know what the frig is going on?
Thanks!
EDIT: I'm using the [email protected] #1 kernel which I assume is the stock kernel for FRF83.
I've had a few "reboots" but they weren't reboots in the traditional sense. Or the reboot seemed to happen VERY fast, maybe in less than 10 seconds, rather than 30 or 40 that it normally would. So i'm not quite sure what to call it but it is annoying..
Please kernel gurus! Hellllllp!
SEE MY NEXT POST! I Got it, but it boot-loops.
My Friend said his Droid forgets contacts, is loosing texts & was acting up after the 2.2 software update so Verizon replaced it. But only took the battery so he still has it. I could wipe, root, n install CM6 and most likely get it running good right. I'm thinking after a radio and OS reinstall it might be ok.
Is $50 worth it. Where can I get an originally battery? And will the phone still work if I call and register it on another Verizon account?
Thanks for any help.
So worth it....ebay
OK, so I got the Droid and I have it home. I got a battery cover and battery from my friend at verizon.
So, what Recovery options are there for the Droid. I don't know anything about the droid. I've always done things on my Nexus One only. I tried holding X while booting and this is the screen I get
http://twitpic.com/2lpio0
and this Droid has an endless boot-loop. I'm not sure whats wrong atm. or what verizon may have tried to do to fix it for the customer. What should be my first move. How can I boot into the stock recovery and do a factory wipe?
Update. I've loaded SPRecovery ESE81 while following the Cyan Wiki for the Droid. I've tried a Full Wipe, and Cache wipe. It still does an endless boot-loop.. I'm not sure what my next move is from here.
I was going to keep following the Cyan Wiki for the Droid and install the rooted ESE81.update file from the Wiki. But that is 2.1 and I'm pretty sure the phone has 2.2 So the radio's wouldn't match. Or would flashing the ESE81 file from the wiki also do the radio? (if so from there I'd be rooted and can flash some CM6 like I have on my Nexus One). I'm not sure what to do next. I don't know how messed up it is, or what all Verizon did. but for now it boot-loops, and it has SPRecovery ESE81 on it.. What should I do next. What steps should I take?
Thanks for any help!
*Update - I've learned Droid doesn't have Radio mis-match problems. thats only GSM phones, so from here I should just flash the rooted ESE81 and from there flash CM6 right?
double post
Well, something messed up here. I was able to load 2.1 on the phone it booted once, seemed fine and on reboot I'm back to boot loops all over again, tried wipe and reflash. Same thing. I then flashed CM6.0-Droid and now I get the CM boot animation, but it still is having a boot loop. I'm not able to get it to boot into the system other than that one time. WTH.
idea's? oh and how do I charge the Droid without it turning on, when I plug it in, it boots. (N1 doesn't do this)
Try using RSDlite to flash ese81 while in the bootloader screen. (Bootloader - power and up on d-pad)
Sent from my Droid using XDA App
xguntherc said:
idea's? oh and how do I charge the Droid without it turning on, when I plug it in, it boots. (N1 doesn't do this)
Click to expand...
Click to collapse
that is a crazy issue with Motorola. I don't know why they do like that.
my solution is ... charge the battery using external charger
Been A long time Lurker here at XDA, so much great info and support!!
Ok so here is my problem I have a 32GB touchpad. I have WebOS running, no problems at all. I have tried many many times installing CM7 and CM7 XRON-ified. Every version and i get into this boot loop....
I have done an ACME Uninstall....reinstalled webos with the Doctor.... fresh installs of everything... full formats of "SD Card"... I am at a loss
After i have done a fresh install i will reboot into CM and it will be working... then just reboot, and start the boot loop...ill stop it on the MBOOT menu and just let it sit then boot back into CM and it will load... then randomly just reboot and go back to the boot loop...
I am at a loss... could it be hardware related... WebOS runs find and diagnostics that i have run in webos come back clean... Any one have any thoughts?.....
If you need any other info please let me know...
Thanks
Cdrshm
Sounds to me like the caches need wiping and another fresh install. But I'm sure you've tried this so I am at a loss.
"A little nonsense, now and then, is relished by the wisest men."
strikerage said:
Sounds to me like the caches need wiping and another fresh install. But I'm sure you've tried this so I am at a loss.
"A little nonsense, now and then, is relished by the wisest men."
Click to expand...
Click to collapse
I have done it more then a dozen times.. hardware issue maybe?
Sent from my Galaxy Nexus using Tapatalk
Bump. Anyone have any thoughts?
Sent from my Galaxy Nexus using Tapatalk
according to the thread, it does that a few times (exact numbers havent been given) because of initial settings.
the 4 TPs ive done all had at least 2 or 3 random reboots that settled out and disappeared .
endlesszeal said:
according to the thread, it does that a few times (exact numbers havent been given) because of initial settings.
the 4 TPs ive done all had at least 2 or 3 random reboots that settled out and disappeared .
Click to expand...
Click to collapse
Yea, but this is actually a boot loop, not just a reboot....many times won't even boot back into cm...
Sent from my Galaxy Nexus using Tapatalk
FLASHING ROMS WILL VOID YOUR WARRANTY AND COULD POTENTIALLY DAMAGE YOUR PHONE -- WHILE I MAKE EVERY ATTEMPT NOT TO LET THIS HAPPEN, IT'S STILL A RISK THAT YOU'RE TAKING. IF SOMETHING BAD SHOULD HAPPEN TO YOUR PHONE, PLEASE DON'T BLAME ME -- HENCE THIS WARNING.
This isn't so much a ROM announcement as it is a direction to find the unofficial nightly builds of CM9 for the Droid 4 (based on Motorola ICS leaks)
Download Here from ROMbot
Download GApps Here (04/29 Goo-Inside GApps Link).
FLASH THE GAPPS.ZIP FILE AFTER YOU FLASH THE ICS.ZIP
WHAT do I need to run this ROM?
- Rooted
- Running a Motorola ICS leak (.206, .208, .211, etc)
- I recommend that you run Safestrap v2.00 to install this. Here's how to use Safestrap
And you can download Safestrap for the Droid 4 (v2.x for ICS-leak users) here:
Safestrap « Hash-of-Codes
WHAT can I expect to work right now?
- 4G and basic phone function
- All sensors
- Camera, Panorama and Face-unlock
- Video Recording
- HD YouTube
- Netflix
Current Known Issues?
- Data connection is a work in progress. It's MUCH better than it used to be in the old ICS builds, however there is always room for improvement. Due to the "global" data connection style of stock Motorola ICS, this problem will probably continue to be worked on. Feedback is always appreciated, but if you see it posted already then there's a good chance I know about specific issues.
- Currently, there is a bug in the rotation display of the phone. What I mean is, that when you take the phone and rotate it, the display will squeeze in on itself and then pop back out. This is a *known* issue and I'm working very hard to fix it.
- The CM9 built-in Wifi Tether won't work. You need to use the "Wifi Tether" app that's bundled into the ROM. Once you open it, hit [menu] and "Settings". Select "Change Device-Profile" to "Generic ICS".
- I'm sure there's more, I'll update this list here in a bit.
WHO works on this?
Myself and @DHacker29 work as a team to build AOSP-based ROMs (and device setups) for several Motorola phones. Typically, I do the coding work in C, C++ or Java while DHacker maintains the blobs, runs merges with CM/AOKP sources, and solves device issues which require less coding.
WHAT is a "nightly"?
It's an automated build ran from a script. It basically: deletes the current set of output files, sync's with github, and then attempts to do a brand new build. It can break at times, in which case we'll fix it (usually this happens when there are framework changes which didn't get merged).
WHY would I want this?
- Since we work on several devices, this is how we decided to start keeping builds up-to-date. Rather than spend several hours a week on builds and uploading. This happens automatically every night around 2am PST.
- It's up to you the community to identify good "stable" builds.
Feel free to follow me on Twitter as I do sometimes make announcements there before I do forum postings:
Hashcode (@Hashcode0f) on Twitter
We maintain all of our code at github:
https://github.com/o...ns/STS-Dev-Team
Screenshots:
[ COMING SOON ]
Reserved for future use
Looking great Hash! Thanks for your work.
my excitement is robust
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
kwyrt said:
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I was able to get it installed and working just fine under safestrap. Did you wipe data, cache, and dalvick?
jgardner said:
I was able to get it installed and working just fine under safestrap. Did you wipe data, cache, and dalvick?
Click to expand...
Click to collapse
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
I did the exact same thing (not wiping on a fresh safestrap). I believe that message about the sd-ext is normal when wiping dalvik.
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
I believe the reason behind that message is that the Dalvik cache is not stored on the sd-ext, but rather the sd, which is internal. Since theres technically 2 SD cards on our device, it looks for the dalvik on the first one. A dev would probably have better advice on it though,....I may be wrong.
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
Safestrap checks for a dalvik cache under a theoretical /sd-ext partition on the external SD. It's almost never there tho. So you can safely ignore that message.
So one thing I have noticed switching between stock and the ICS ROM is the battery level is not consistent. Reads 60% on stock. Reads 26% on ICS. Anybody know what's up with that?
Sent from my DROID4 using XDA
kwyrt said:
So one thing I have noticed switching between stock and the ICS ROM is the battery level is not consistent. Reads 60% on stock. Reads 26% on ICS. Anybody know what's up with that?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I havent flashed this one just yet but i know on my droid 3 i let the battery charge all the way up and then wiped battery stats and all was fine after that.
Sent from my DROID4 using XDA
thanks hashcode! you're the man!
Appreciate the Rom.. Runs very nicely on Droid 4. Easy install.
I know HW video is being worked on. Will that fix or update allow Movie Studio to work?
Very interested and excited about Ice Cream Sandwich and future updates to this Rom
Installed and loving it so far.
The one thing I've noticed, the phone gets really hot, and the battery usage is pretty poor. I actually watched my battery percentage drop while doing my installs of all the apps that I had to download.
I lost about 3% during that process, even when plugged into the wall charger.
I'll keep an eye on it, as I'm close to a charger at all times, so bad battery life doesn't affect me too much.
Can't wait for BT to work, as that would be the last piece in a daily driver for me.
EDIT - just discovered I'm having issues with Chrome Beta. I've never used it before, but it won't load any websites. I'll DL Dolphin for the time being, but would love to try out Chrome. Just wondering if anyone else is running into this.
Im fully installed and Chrome Browser works great along with all other functions on my end.
As for battery percentage Im not sure if im having your problem with excess heat....
doubleokneegro said:
Im fully installed and Chrome Browser works great along with all other functions on my end.
As for battery percentage Im not sure if im having your problem with excess heat....
Click to expand...
Click to collapse
Ok found out it was my charger. For some reason it wasn't actually charging and was just causing heat. Plugged it into a different charger and all is well now.
still no love with Chrome though.
kwyrt said:
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Im in this same predicament.. Uh.. How do i hard reset? Hold power? That doesnt seem to be working for me....
---------- Post added at 10:16 PM ---------- Previous post was at 10:07 PM ----------
gangrif said:
Im in this same predicament.. Uh.. How do i hard reset? Hold power? That doesnt seem to be working for me....
Click to expand...
Click to collapse
Nevermind, google has solved my despair.
http://www.technipages.com/how-to-reset-frozen-droid-4.html
Thanks.
Absolutely love this ROM!!!!! One request though, what do I need to install to get webtop working? Just got the lapdock 500 a couple hours ago and love this ROM to much to give it up
Sent from my DROID4 on ICS
Everything seems to be working perfectly for me, even the camera is working properly. I haven't tried bluetooth yet, but I'm not too worried about it, I barely use it. Wifi connects and works, no problem there. I noticed a slight lag after installing setCPU but now it seems fine. I'll check tomorrow to see how the battery life is but for now every things pretty smooth. Thanks!