Hey, I'm on liberty 2.0.1and since the recent toolbox update, the file to update to rooted gb has been added to nightlies. I downloaded the file, but when I tried to install it, it says the phone will reboot into recovery and install, but my phone just reboots back to normal. I tried redownloading the file, but it just reboots normally. I've been having issues with my phone freezing lately, so I wanted to update to liberty gb. I tried to email jrummy and message him on twitter, but he never responds, which is **** customer service if you ask me. I just want to get my phone working again. Does anyone know about this issue? Any advice?
Thanks,
Garrette
Sent from my DROIDX using XDA Premium App
I'm not sure about that. You could always update to rooted/blured GB then load up liberty from there.
Sent from my Xoom using XDA Premium App
I did that last night. I had to SBF back to stock group though, reboot, then installed prerooted gb. Dl the Liberty toolbox, dl nightly version gb. O9, and it STILL DOESN'T FREAKING WORK!!!!!!!!
It still doesn't reboot into recovery and just restarts the phone normally. Can I just use bootstrap and install the file from there?
yes, u can use bootstrap
Related
Daily, my phone downloads an update and attemps to install it. Everytime it say the update has failed after a restart. I am rooted and running bootstrap. Do I need to update some non normal way
Sent from my DROID2 using XDA App
What is your system version?
Sent from my Motorola Droid 2 with Fission 2.1
Currently says 2.2.20.a955
It downloads and starts the install of 2.3.20 but it never finishes successfully
Sent from my DROID2 using XDA App
If the OTA update fails I would flash the 2.3.2 sbf that will update it. There are tutorials in the droid 2 android development section.
Sent from my DROID2 using XDA App
Did you remove any of the apps after rooting? The update fails if the preinstalled apps are not present. I put mine back and the update worked fine, then I re-rooted.
I've found that having the Bootstrap installed causes the update to fail (probably messes with the update process). I was running Fission, and restored a backup I had made when my system was stock. Upgrade failed, so I tried unrooting. Still failed, so I restored from the 2.3.20 SBF, which brought me up to date.
pool_shark said:
Did you remove any of the apps after rooting? The update fails if the preinstalled apps are not present. I put mine back and the update worked fine, then I re-rooted.
Click to expand...
Click to collapse
I was just going to ask that. You are correct...
After updating to the.340 ota update I have been experiencing frequent random reboots. I am rooted with z4 root. I have tried 2 factory resets with clearing the cache and it doesn't help. Any suggestions?
Sent from my DROIDX using XDA App
If ur comfortable with an sbf u can try that. Or a good rom like GummyJar.
Just a thought. Or could be bad hardware
I was thinking I was going to have to sbf. Is the file you download called update.zip? If so I have the file and rsd lite, I just can't find good instructions on how to do it. I have done it once before but it has been a while.
Sent from my DROIDX using XDA App
This should help you out:
http://forum.xda-developers.com/showthread.php?t=895261
Yes thanks that is what I was looking for. I think that was the instructions I used last time. I didn't have much time to mess with it tonight but when my phone was plugged in and turned off and went into whatever mode when you hold down the volume down and camera button, windows couldn't find the drivers for the device.
Sent from my DROIDX using XDA App
Just wipe data. I had the same problem. Completely wiped and phone is fine now.
Sent from my DROIDX using XDA App
I had the same problem. I had downloaded app killer & found out that Droid X doesn't need it. Once I removed app killer that fixed my issue.
Well I finally sbf'd my phone but it was a .320 instead of the.340. I still am having random reboots and can't figure it out. I have tried to do a manual update to.340 but the phone says I'm up to date. I found the system only .340 update and will update it that way. I thought that launcher pro might be a problem and noticed it was slowing down the system, but I am still rebooting with adw launcher also
Sent from my DROIDX using XDA App
If I'm not having reboots should I update my baseband, kernel and so on to the leak versions?
I got this phone 3 weeks ago, got a update to 2.2.1 then I flashed fission on it after wanting more..
someone help me out here
I can't seem to figure out why the themes won't flash from the Liberty toolbox. I'm running v1.5. The themes will download, they just won't flash. I have tried literally everything - I've re-flashed the ROM, didn't work. I wiped data/cache then re-flashed the ROM, didn't work. I uninstalled the toolbox and then downloaded the new version of it (1.1.2), didn't work. I tried downloading the themes from the internet instead of the toolbox, still didn't work. Anyone have any idea on what to do?
Make sure your bootstrap is working. After it downloads it usually reboots into recover to load it.
Sent from my DROIDX using XDA App
It reboots into recovery every time. I then try and manually flash it and it doesn't work.
ive had this same exact problem
I have had the same problem. I notice when I click on a theme to install it, it doesn't download, it just reboots without realizing it wasn't downloaded. Hence no download, no install. I do not have a connection problem and I have plenty of signal. I'm guessing perhaps there is a problem with download location.
Sent from my DROIDX using XDA Premium App
I have had a similar issue. I found that once my ROM manager was updated, I had to reflash clockwork mod from within the ROM manager. Once I did that, I was able to install a theme with liberty toolbox.
Sent from my DROIDX
djnikkofb said:
I have had a similar issue. I found that once my ROM manager was updated, I had to reflash clockwork mod from within the ROM manager. Once I did that, I was able to install a theme with liberty toolbox.
Sent from my DROIDX
Click to expand...
Click to collapse
I had this exact issue and I did this but now it just downloads an empty zip file with the themes name
I'm having the same issues this morning, my guess is that they have removed the files in preparation for a new Liberty release.
I updated to EI22, stock w/OTA update. I then rooted and things were working great. Then about 1 week ago, I did a CWM backup and when I restarted the phone just kept automatically rebooting approx. every 3 -4 minutes. I could not stop it no matter what I did. Then I restored the backup and it worked fine. A few days later, I turned the power off to put in a my extra battery, and when I turned it on, the same thing happened. I had to restore twice fir it to stop this time. Then this morning, I did a reboot to see what would happen, and again it happened. Mind you it was working flawless before I restarted it. I have tried everything from removing programs, turning off the wifi, leaving the battery out for a half hour, but nothing. Sometimes after it reboots, I leave it alone for 15 minutes and then when I hit the power button, it just restarts.
Any ideas before I put back froyo??
Sounds like a bad flash. I would Odin all the way to Stock EC05 then root then flash a Gingerbread ROM. Your error is either in the kernel or recovery to happen immediately after boot. It could even be a flaky partition table.
Sent from my SPH-D700 using XDA App
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
mszach said:
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
Click to expand...
Click to collapse
I figured that but the problem may lie in the rooting which required you to flash a kernel or in your recovery module.
Sent from my SPH-D700 using XDA App
mszach said:
Any ideas before I put back froyo??
Click to expand...
Click to collapse
Your not alone on this issue. I am also considering going back to froyo
ADW was nice enough to bring up a crash report that I emailed myself. In the stack trace I see that android Package manager has died as a cause of the exception. I am not a java programmer so am at a loss here to what's happening.
See also this related post
So I flashed to the ACS ICS rom and so far no problems. What a great ROM!! Many thanks to Marcusant and ACS.
Sent from my SPH-D700 using XDA App
don't use the OTA.
just root ec05, flash CWM 5, flash modem update ec05 to EI22, flash a rom of your choosing. it's that simple. i don't see why people go the OTA route. it just causes problems with the recovery.
EDIT: also if you want Rom manager, check the kernel(or rom) for compatibility.
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I'm lazy sometimes and like to use a GUI...
Sent from my SPH-D700 using XDA App
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
It was not supported for the Epic before but with the new CWM5 it is. It is much faster to boot into recovery from ROM Manager rather than powering down and 3 fingering into it. Plus ROM Manager supports renaming your backups when you are doing them. Also ROM Manager will continuously update your CWM if new versions come out. There is also OTA updates available if the developer supports it on their ROM.
I had encounter ICS, which was great, but isn't ready to be a daily rom, so I use koush's app to reboot into recovery.
then I got stuck at the boot animation, so I decided to open up the stock recovery, and wiped data/factory reset like an idiot. So now all i have is stuck at the M logo, or stock recovery.
Am I going to have to use an official update.zip to flash, then root my phone again?
You are going to have to sbf.
Sent from my DROID2 using xda premium
okay, so I sbf'd back to stock froyo (only GB sbf I can find around the net is a megaupload link, which is obviously not very helpful nowadays) and let it do an OTA update to GB.
I then root, just like i have before, using the motorola one click root program on my computer.
I get root, install koush's bootstrap, and reboot into recovery. I then try to install libertyv3 2.0, which seems to go well...
until i reboot. once i reboot my phone, I'm stuck back at the bootloader, and can't do anything except SBF all over again.
seriously, what's going on? maybe this liberty .zip is broken or something? (i had to find a mirror, because A team gummy's site seems to be down, and B the only other official mirror is megaupload)
I'm going to try another rom, probably encounter ICS because i already have it on my SD card.
this time, I actually read the instructions and tried to install Liberty with clockwork recovery instead of koush.
still. effing. happening.
I reboot after flashing the zip and I can't get past the bootloader screen.
Code:
Bootloader
D2.37
Err:A5,69,35,00,23
Battery OK
OK to Program
Connect USB
Data Cable
I'm seriously at wit's end here. I just got this phone but a couple days ago after I lost my original. it's an insurance replacement. I rooted with the moto one click root, and used koush to install encounter ICS. after not knowing about encounter's wonky way of activation the custom bootloader, I mistakenly wiped the phone with the stock bootloader. I SBf'd back to stock froyo, then OTA updated to gingerbread.
That is my entire history with this phone. what the hell could possibly be wrong with it?
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Albinoman said:
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Click to expand...
Click to collapse
I did certainly wipe before flashing, but have never not once heard of wiping twice after flashing. wouldn't that undo the flash? what's the point of that? And like I said, I would use encounter ICS, but it's nowhere near stable enough for daily use.
When you wipe after its just to make sure everything is stock. As long as you don't wipe /system the rom will still be there. Actually if you can live without a camera EncounterICS is an amazing daily driver. Also never use bootstrap unless you're on stock gb.
Sent from my DROID2 ICS using xda premium
I can live without a camera, but google music barely works, which is something I can't live without. I'm thinking about going back to Apex until encounter gets really good (had apex for months up until i lost my original phone)
Google music is working fine for me. Good idea apex is great.
Sent from my DROID2 using xda premium