Related
Re-released flashable zip version for those people who are stuck at Froyo because of modem issues
Features:
Modified CWM to support Froyo. Credits to tj_style for porting CWM on Galaxy Mini ==> http://forum.xda-developers.com/showthread.php?t=1167750
Uses tj_style's overclock kernel ==> http://forum.xda-developers.com/showpost.php?p=12880870&postcount=39
All partitions @ Ext4
Pre-rooted
Deodex
Bootanimation
init.d support (running custom scripts during boot)
cifs and tun modules
Darktremor Apps2SD 2.7.5.3 Beta 03
Removed startup sound
Changed default language to English
Added some live wallpapers
TouchWiz replaced with zeam
Pre-installed apps: OpenVPNSettings (inlcuding binary), Screenoffandlock, and CifsManager
Others
FLASHING DISCLAIMER APPLIES!
Should anything go wrong, please make sure you have a backup of your firmware from samfirmware.com or use CheckFus http://forum.xda-developers.com/showthread.php?t=1032437
How to install from stock firmware:
This procedure assumes that you are still using Froyo so there is no need to flash any firmware
1. Download attached ClockworkMod (CWM) Recovery for Froyo. Flash as 'One Pacakge' using Odin
2. Download S5570XWKC1_MOD_ROM.zip and save it on the root your SD card ==> http://www.multiupload.com/0INURR5M72
3. Turn off phone. Go into recovery mode by pressing and holding the Home + Power buttons. Release buttons when you see the Samsung logo
4. Once you are in recovery mode you will get lot of options on screen. In recovery mode touchscreen does not work, so use the Volume button to toggle through options, Home button to select option or confirm action, and Power or Back button to go back to the previous menu.
5. Select 'wipe data / reset'. Confirm action
6. Select 'install zip from sd > 'choose zip from sdcard' > file in Step 2. Confirm action
7. Go back to previous menu and select 'reboot system now'
Done!
Stock theme
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quadrant (600MHz)
Quadrant (overclocked)
thanks for this rom really like it) i have just 1 tiny problem :-s when i press home and select task manager it force stops :| this is the only thing that bother me
I can't recreate your issue. Does it happen all the time or in just some cases?
Thank you Parasmi!!! You rock!!! Already downloading and I'll give it a try tomorrow!!!
does the dark font in menu exist in this release too?
if not i'm going to install it
trance89 said:
does the dark font in menu exist in this release too?
if not i'm going to install it
Click to expand...
Click to collapse
No because this is stock theme.
Please note this is a Froyo ROM. If you are coming from Gingerbread, you need to flash a Froyo firmware first using Odin.
parasmi said:
I can't recreate your issue. Does it happen all the time or in just some cases?
Click to expand...
Click to collapse
all the time. you know? when i press menu it pops up recent apps and under the task manager.when i press on task manager phone vibrates and i got the "force close " message.same if i press the task manager from menu :-?
Great work Parasmi.
It's just one thing that I will ask you to consider : some apps that you included in the zip package. For instance, AFAIK Root Explorer is only available as paid version only. How could you manage to include it in your ROM ? I hate to see this great ROM turned into a warez ROM. And secondly, SetCPU, though it's free for xda-dev members, its' developer explicitly asked ROM Developers not to include SetCPU. You can see his post here :
SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011
Or I'll just quote part of his OP here :
coolbho3000 said:
ROM developers: Please do not include SetCPU in your ROM. I appreciate the work you're doing, but link to this thread instead, and I'd really appreciate it if you mention that SetCPU is available on the Android Market.
SetCPU is a CPU speed tweaking application for Android. More specifically, it allows control of certain aspects of the Linux cpufreq driver, allowing for overclocking, underclocking, or tweaking speeds and settings on many Android devices. It will work with most if not all rooted Android 1.5/1.6/2.0/2.1/2.2/2.3/3.0/3.1 builds on most devices.
The program is free here for XDA members. It costs 1.99 on the Android Market and available for purchase on the Amazon Appstore for users in the US.
QR code (please donate by buying it on the market ):
Click to expand...
Click to collapse
Cheers
distan7 said:
Great work Parasmi.
It's just one thing that I will ask you to consider : some apps that you included in the zip package. For instance, AFAIK Root Explorer is only available as paid version only. How could you manage to include it in your ROM ? I hate to see this great ROM turned into a warez ROM. And secondly, SetCPU, though it's free for xda-dev members, its' developer explicitly asked ROM Developers not to include SetCPU. You can see his post here :
SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011
Or I'll just quote part of his OP here :
Cheers
Click to expand...
Click to collapse
Thank you for the reminder. I'm having seconds thought about them actually. I'll remove them and re-upload a new file
adistf said:
all the time. you know? when i press menu it pops up recent apps and under the task manager.when i press on task manager phone vibrates and i got the "force close " message.same if i press the task manager from menu :-?
Click to expand...
Click to collapse
Not happening to me. Try launching task manager via applications, let's see how it goes
I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup
splattx_x said:
I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
Click to expand...
Click to collapse
Does you SD have a 2nd partition?
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup
Click to expand...
Click to collapse
Im not sure abour this one. Can you check if the zip file is not corrupted?
parasmi said:
Does you SD have a 2nd partition?
Click to expand...
Click to collapse
No, I only have one partition in FAT format.
parasmi said:
Im not sure abour this one. Can you check if the zip file is not corrupted?
Click to expand...
Click to collapse
I tried once, failed. Then I deleted the file from SDcard, copied it again but it failed again with same error... I was able to extract the zip correctly so I don't think the file is corrupt. Perhaps Latin and European devices are more different than we thought.
splattx_x said:
No, I only have one partition in FAT format.
I tried once, failed. Then I deleted the file from SDcard, copied it again but it failed again with same error... I was able to extract the zip correctly so I don't think the file is corrupt. Perhaps Latin and European devices are more different than we thought.
Click to expand...
Click to collapse
Hhmmm....Let's take this offline. Sent you PM
Hi,
Does this ROM work with my phone?
PDA: S5570XWKC7
PHONE: S5570XXB1
CSC: S5570XXKC3
System information shows me exactly the same version number, except Build is FROYO.XWKC7 compared to FROYO.XWKC1
the same happen with me plz edit ur scrpit and thanks
splattx_x said:
I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup
Click to expand...
Click to collapse
Hey are u trying to do it with rom manager?
Sent from my GT-S5570 using xda premium
debsattam said:
Hey are u trying to do it with rom manager?
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
was trying with CWM. Anyway I was able to upgrade to Gingerbread and then flashed new EmanoN rom based on gingerbread and everything went ok.
Thanks for the help anyway!
what are the modem issues? because i think i face modem issues but i cannot find a thread where somebody has issues like mine
This is an outdated thread. Please go HERE instead
Liberty 3
Sunday Bloody Sunday!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
* Please Wipe Data regardless of what ROM you come from
Team Liberty
Primary Dev’s and project leads - Kejar31 and Jurmmy16
Primary Dev - Syaoran12
Artist - Koveleski
Thanks:
FABOLOUS for all his help on the DX port!
Thanks to Teamdouche for publicly posting the CM source, which I compiled some of my apps from
Thanks to Superteam and Dustin Jorge as Liberty-Laucher was forked from and based on their work
DroidTh3ry for his camera app
droidjunk for his powerwidgets mod
sbrissen for his smali help, if not for him I (syaoran12) wouldn’t have been able to learn smali
TopazAaron for our new server!
Everyone else who helped make this ROM possible - you know who you are
Features:
- Most all apps were built from source.... rather that decompiled and hacked apps via APKmanager!!!!! To do this I took the CM7 source tree and reworked the framework to allow apps to properly find resources after they were compiled.
- The only apps left from Blur are the Dialer, Contacts and Camera
- AppWidgetPicker - built by boombuler
- Ads blocked via hosts file -thanks to delta_foxtrot2
- 1% battery increments built in (Icons made by thanks to Nitro)
- Themed Dialer, Contacts, Task Manager by me to integrate into the stock GB look and feel
- Reboot options (Reboot,Recovery and Screenshot)
- DSPManager included
- Custom Launcher2 with extra hotseats and speed tweaks (lightest fastest launcher you will ever use)
- Liberty Customizer (choose to add back blur apps)
- Start-up Tweaks (tool to allow you to manager your start-up tweaks)
- Root Browser (full edtion that normally comes with the pro version of the ROM toolbox - no need for Root explorer any-longer)
- Root Toolbox
- 8 Lockscreens (Moto, Rotary, AOSP, 4Tab, Honeycomb, Rotary Revamp, Lense and Rings) with widgets
- Statusbar Tweaks
- Updated gtalk (should fix the 3g/4g issue)
- Updated Camera - credit DroidTho3ry
- Scrolling powerwidgets - credit DroidJunk
Change Log From 1.0 (is also in the ROM)
- Update for new status bar settings
- New lockscreens added
- build.prop tweaks
- Updated Talk, Google Music, Market, etc
- zipaligned apks and jars missing alignment
- Minor theme fixes
- Liberty Settings updated
- Updated Rom Toolbox and Root Browser
- sysrw and sysro scripts added
- Theme Manager added (for donate users, more info on second post)
Liberty Parts
All of these will be found within Liberty Settings > Customization
Lockscreen Settings will give you the option to change your lockscreen within the style menu, and widgets within the widgets menu.
Status Bar will give you control over status bar tweaks.
The battery icon does disappear it just takes time, you can cycle the signal tweaks to get it to go faster.
Battery text will turn green while charging and red when you are at 20% or below.
Hide Alarm goes into effect if the alarm is already set, or will require a reboot..
Known Issues:
Disclaimer:
I nor anyone in Team Liberty take any responsibility for what this ROM or its tools may do to your phone.
Download:
Liberty3 for the DX 2.0
MD5SUM: 29ad0ec267994d1724e30c85ca71f680
Option #2 - download rom toolbox -> go to rom manager -> liberty
Updates:
Superuser Fix for those having issues updating it in the market.
MD5SUM: c1b022744dfc8a48cdf8c70a12e7193f
Install - CWM only
make sure you have root and Clockwork recovery installed
-boot into recovery via Recovery
-select "wipe data/factory reset"
-select "Yes -- delete all data"
-go back
-select "install zip from sdcard"
-select "choose zip from sdcard"
-find and select LibertyXX.zip
-reboot
Installing Themes
-boot into recovery via Recovery
-select "install zip from sdcard"
-select "choose zip from sdcard"
-find and select LibertyXthemeX.zip
-reboot
Donate:
Donate to Kejar31
Donate to Jrummy16
Donate to Syaoran12
Screenshots
Theme Manager is included in the Donate version of Liberty Customizer.
You can find it here on the android market.
The Theme Manager will only be found in the Donate version of the app because we wanted the people who donated to our cause to feel they got something extra for their donation.
Screenshots
Can I install this directly over liberty gingerbread v0.9???
Obviously I know a full data wipe will be necessary, but I am concerned about
the system version not being up to par.
Any info. would be much appreciated.
thanks
Nycorduroy
This Rom is outstanding. Feels like CM7 but has all the advantages of stock. I've been on CM7 GB for months now and I'm really surprised at how much better the display looks with this rom over CM7. Also the flext9 keyboard works with this ROM.
Sent from my DROIDX using xda premium
My sisters dx is running cm7 currently the gb version. But the phone is very unstable and continues to reboot constantly. (she blames me as I modded the phone for her). I really want to flash this liberty rom but I'm very unsure as I have read a couple different places and it's confusing. I'm pretty sure the .608 is the gb update number but what is init #20? and how do I check this? I currently have a atrix 4g and have flashed my phone several different times with different roms and kernels but the dx process is so very new to me. Any help or guidance in the flash from cm7 to liberty would be greatly appreciated. I've already soft bricked her phone twice and am pretty familiar with the sbf process. Thanks.
stevehkim said:
My sisters dx is running cm7 currently the gb version. But the phone is very unstable and continues to reboot constantly. (she blames me as I modded the phone for her). I really want to flash this liberty rom but I'm very unsure as I have read a couple different places and it's confusing. I'm pretty sure the .608 is the gb update number but what is init #20? and how do I check this? I currently have a atrix 4g and have flashed my phone several different times with different roms and kernels but the dx process is so very new to me. Any help or guidance in the flash from cm7 to liberty would be greatly appreciated. I've already soft bricked her phone twice and am pretty familiar with the sbf process. Thanks.
Click to expand...
Click to collapse
Go into settings/about phone. If the Baseband version ends in .13p then you are on the most updated kernel needed to flash this rom. Follow the instructions above and you should be good to go.
Freaking outstanding ROM guys.
Oddly my crt off animation quit working after a day or so. I'm sure i messed it up, not sure with what though.
NEED HELP WITH WIFI TETHER! Please read details below Thnx
Despite my low number of posts, I am not new here. Long time reader/lurker
Just thought I would give a shout out to the devs for all of their hard work on this rom. I am very pleased with it to say the least. Minimal bugs and problems I have found so far. Just came off of Liberty2 v0.9 which had many bugs for me and got worse the longer I ran it.
-WIFI TETHER ISSUE-
Only thing that bugs me about this new rom is that I can't seem to get WiFi tethering to work anymore. I tried the WugPacked All-in-one patch, which I had been using on Liberty2 v0.9, but it doesn't seem to work now. Is there something I am missing? When I first set it up on 0.9 there was a thread that explained how to set it up to work but I can't seem to find it again. Something about after installing the WugPacked patch you needed to change some settings in the WiFi Tether app to get it to work properly. Where I seem to run into a roadblock is when you open WiFi Tether app and click to start tethering, Superuser is asking for permission to allow/deny. It always crashes Superuser and makes it force close. Is there some way around this? Can I manually add the Tether app to the Superuser list of allowed root access? I know once you open an app and Superuser pops up asking to allow/deny, it will save that setting from then on and not ask every time. Is there a way to manually add the WiFi Tether app into the list of allowed apps so I can skip this pop up that seems to keep crashing SU? I desperatley need to get Tether back working again. Or if there is something I am missing or and easier method, please feel free to elaborate. Thanks in advance for the help.
Something else I would like to post here for help to anyone hoping to install this rom. Like I said, I was on Liberty2 v0.9 before. It was complete hell trying to get it to install. Took me nearly 4 days to get there because my phone kept bricking. I think I finally figured out where the problem lies.
One major issues I had was that ClockWorkMod Recovery would come up after every boot. Doesn't sound like a major issue right? Well when you need to restart your phone in a hurry, you have to go through CWM every time. It gets better... How about if you are plugged into power with the phone off? Usually the phone goes to a battery charging screen, no? NOPE. CWM comes up 1st and you have to reboot the phone to get to the charging screen. And since the phone will not charge while in CWM, it produces some very aggravating results when you plugged in your dead phone and come back 4hrs later expecting it to be charged.
So if you are booted in android and need to reboot while plugged in and charging... you get: Booted > Reboot > CWM > Reboot > Charging screen > Reboot > CWM > Reboot > Booted.
Takes like 4mins to reboot from in the OS to get back in the OS. Not fun.
So what makes CWM come up after every boot? I think it has something to do with a conflict between the CWM Recovery and the stock Recovery menus. When CWM is starting on every boot, the stock recovery refused to work. You could get it to boot the stock recovery, but it shows the little triangle error icon.
I think it has something to do with the .602 sbf file. Everytime I sbf to the .602, I get the CWM error and other things not working properly. I had lots of issues on Liberty2, too many to list. So if you plan on installing Liberty3, I suggest these steps for best results.
BACKUP EVERYTHING! If recommend My Backup Root by Reware (android market) and Titanium Backup
If you have CWM installed, boot into CWM and wipe data, cache and dalvik (if no CWM installed, use the stock recovery to do these steps)
SBF to 2.3.340
Let phone boot and activate the phone. No need to set up google accounts or anything else.
From the home screen click menu button/Settings/About Phone/System Updates and let the phone find the recent .605 software.
Download and install the .605 and activate your phone like you normally would (Google account too)
Go to the Android Market and download the Droid2 Bootstrap by Koush.
Before you open it, you need to root your phone using the Droid3 one click root process. (Please google it as I don't have a link)
Follow the instructions for the root exactly so you don't miss anything.
Now you are rooted and need to install the Droid2 Bootstrap.
Open it up and click "Allow" on the Superuser pop up. Now you see 2 buttons. Click the "Bootstrap" button.
Should pop up a notification saying "Success".
(Make sure you have the Liberty3 v2.0 on your sdcard at this time)
Now you can click the "Recovery" button to reboot the phone into ClockWorkMod Recovery.
Now in CWM you need to wipe data, cache and dalvik before installing Liberty3.
Install Liberty3 and wipe data, cache and dalvik again after it finishes before you leave CWM.
Liberty3 v2.0 should boot fine now and not give you any problems I hope
I am not sure why wiping the data, cache, and dalvik before and after the Liberty3 install helps (as it shouldn't matter), but it seemed to clear up installation issues I was having. Like Boot Looping and other odd things.
I highly recommend not using the .602 sbf file as it seems to be missing some files that the .340 sbf has. And yes I downloaded, redownloaded, downloaded the .602 from many places and get the same errors every time. The install method I mentioned above took me like 1hr if you already have all the files on your computer.
Hope this helps anyone experiencing the same problems I was having.
that gives a new meaning to tl;dr
Sent from my DROIDX using XDA App
---------- Post added at 07:31 PM ---------- Previous post was at 07:10 PM ----------
What version of wifi tether are you using? Do you have the routing fix enabled?
I was having some trouble with this on stock rooted .608 and ended up just doing the NVram hack. It went smoothly and took 5 minutes...i haven't sbf'd since then so i suspect that's why i'm not having an issue now.
http://rootzwiki.com/topic/3136-wir...gerbread-tether-fix-instructions-updated-102/
followed them to the letter.
-WIFI TETHER ISSUE UPDATE-
Ok, so i got wifi tethering up and running. Thanks tdrussell for the info but I did not need to NVhack my phone. I believe that was the purpose of the WugPacked All-in-one zip file. It does the NVhack and installs wifi_tether_v3_1-pre99.apk in one step.
Since I was having trouble getting the included wifi_tether_v3_1-pre99.apk to work with the Superuser on Liberty3, I decided to try one of the newer versions of it.
I am currently using Wifi Tether v3.1-beta6, and to my surprise it is working. Yay!
Anyhow, let me clear this up for anyone else that might need to get tether running on their new Liberty3 install.
FOLLOW EVERY STEP CAREFULLY! kthanksbai
-Make sure you have all Wifi Tether apps uninstalled (you cant uninstall the stock app so leave it alone)
-Download the http://goo.gl/hpPoJ and place it on the root of your sdcard.
-Reboot your phone into ClockWorkMod Recovery
-Scroll down to "install zip from sdcard"
-click it and scroll down till you find WugPacked_GB_Tether_Patch_1.1.zip
-click it and let it install
-reboot into android
-uninstall the Wifi Tether v3.1-pre99 that the zip file just installed.
-go here http://code.google.com/p/android-wifi-tether/downloads/list and download v3.1-beta6
-install the app and open it (but do not click the signal icon to start tethering yet)
-click your menu button and go into settings
-In the settings menu, click on Select Device-Profile. Scroll down and check DroidX
-Now back in the settings menu, scroll down and look for "Routing Fix". Check that box.
-Exit out of the app and go back to your home screen
-Click your menu button and go into settings (android)
-Navigate to: Wireless & networks > Tethering & mobile hotspot > Mobile Wi-Fi hotspot settings > Configure Wi-Fi hotspot (you will have to enable hotspot 1st to be able to change the settings)
-Once in the configure screen, set the Security to none (no wpa or psk or wep)
-Exit back to home screen
-Open the Wifi Tether app again
-Click the signal icon to start tethering. Superuser should pop up and ask to Allow/Deny. Wait for about 2 seconds and then click Allow (if you do it too fast, superuser has a tendency to Force Close)
-Now, end all tethering and reboot your phone cause the next set is VERY IMPORTANT!
-After reboot, use Titanium Backup to freeze these four programs.
-Once you are in Titanium, click search and type in "data" and click "apply"
-You shoud see: Data Collection 1.0, Data Collector Service 1.0, DataCollectorProvider 1.0, Setup data encryption 2.3.3
-Freeze all 4 of those (do not uninstall). These are new programs that Verizon has added to the new GingerBread to track data on your handset. It could tell them the difference between your phone data and tethtering data. It is unconfirmed, but better safe than sorry
ENJOY! You should be tethering now
You can set connection security within the app but do not use "Access Control". I have been told that it is still unstable and might cause connection issues.
Hope I was able to help anyone out. Good day *tips hat* /:-{
Sorry to post again, but can I make a request? Would it be possible to get the Swype keyboard in the same colors as the android keyboard? It is really hard on the eyes trying to type on a white keyboard at night. LoL
Thanks in advance
Rom bricked my dad's phone. I'm currently trying to fix it but I need help pleaseeeeeee.
After wiping cache and factory resetting I used dx bootstrap. flashed the rom and when it tries to load up I get a dim Liberty in the backround for about half a second then it goes away. It'll keep doing that as long as the phone is on. Please help.
iSpencerPro said:
Rom bricked my dad's phone. I'm currently trying to fix it but I need help pleaseeeeeee.
After wiping cache and factory resetting I used dx bootstrap. flashed the rom and when it tries to load up I get a dim Liberty in the backround for about half a second then it goes away. It'll keep doing that as long as the phone is on. Please help.
Click to expand...
Click to collapse
Which OS was on it before you flashed it? It needs to be on Gingerbread (.602 or .605). Probably the easiest way to fix it would be to SBF, root, and then reload the ROM.
http://androidforums.com/droid-x-al...ad-602-sbf-root-process-updated-9-9-11-a.html
I am also experiencing issues with flashing this rom. I've had every prior liberty build work without fail on the same device. I'm wondering if i'm missing a step somewhere in the flashing process. My most recent attempt at flashing Liberty3 had me booting into bootloader mode with errors reporting?! No power-up key binding either, just power on and boom - bootloader.
Is a dalvik wipe needed? and do i need to mount system before installing liberty3.zip, or do i just install after wiping?
Also, any chance anyone can direct me to a download for a gingerbread SBF file? would make this a less tedious process as ive had to SBF back to Froyo then wait for the ota about 3 times now with each botched rom install - gets very time consuming
Thanks in advance
Edit- checked the post above and found a .602 SBF (thx ylexot)
Just installed this got an issue. Whenever I open AOSP gallery it shows no pictures, blur gallery just crashes. Pictures aren't "saved" either.
Any idea?
I've been rooting and ROM's my Androids phones, and I think this is the 1st time ever that I've bricked my phone... All I did was perform a backup, wipe data and cache. Tried to install the new Liberty and it kept erroring out, I think becaue the .zip was bad. I went to do a restore of my working backup and now my phone is bricked. How can I restore my phone, not being able to get into bootstrap to perform a manual restore? I'm stuck.
The5ickne55 said:
Just installed this got an issue. Whenever I open AOSP gallery it shows no pictures, blur gallery just crashes. Pictures aren't "saved" either.
Any idea?
Click to expand...
Click to collapse
Try going into settings-> applications-> manage applications, select the gallery, and clear data and cache.
That should force the gallery to rebuild the thumbnails that may have gotten corrupted.
Sent from my DROIDX using XDA App
gomisan said:
I've been rooting and ROM's my Androids phones, and I think this is the 1st time ever that I've bricked my phone... All I did was perform a backup, wipe data and cache. Tried to install the new Liberty and it kept erroring out, I think becaue the .zip was bad. I went to do a restore of my working backup and now my phone is bricked. How can I restore my phone, not being able to get into bootstrap to perform a manual restore? I'm stuck.
Click to expand...
Click to collapse
SBF...see my link a few posts back.
Sent from my DROIDX using XDA App
So i wiped everything (dalvik/data/cache) and still no luck. Maybe a bad .zip?
The install seems too fast and when i boot up after installing it sends me to bootloader and im seeing the following:
-----------------------
Bootloader
30.04
Err:A5,69,35,00,23
Battery OK
OK to Program
Connect USB
Data Cable
-----------------------
At least it's a great opportunity to try this .602 SBF
Must....have....liberty....
The .SBF trick works flawless. I'm on stock Gingberbread, Rooted! It's super simple to do and restore your phone. Am I the only one finding bad Liberty 3.0 ROM's? Everyone that I've downloaded and attempted to Flash, get's a "Bad Zip" error in clockwork..... I'm about to give up on this Liberty 3.0 ROM.
Greetings,
Me and krook1 have been working on a CM9 port for the Lenovo Ideapad K1. This is an Alpha release as there is still a lot of work to be done. I have included instructions to either flash as an update.zip with CWM recovery, or if your still on stock you can use the nvflash package.
I have very limited time to invest to this project so if anyone would like to help please join us at freenode IRC room #ideapad-k1. The source code download link is posted below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Working
-Touchscreen
-Wifi
-Bluetooth
-Accelerometer
-Rotation Lock
-Internal and External Storage
-Audio (thx Koshu and digetx)
-HW Acceleration (thx digetx for green overlay fix)
-CWM Backup/Restore - Fixed by using updated CWM below
Not Working
-GPS? appears to work but doesn't connect?
-HD Video Streaming
-Microphone
-Camera
Haven't tested HDMI out
Changelog
Alpha 1.6
- Fixed storage issue
Alpha 1.5
- Bluetooth fix (Audio doesn't work?)
- Full market compatibility
- Hardware buttons
- Rotation Lock Switch (Functions, but doesn't notify the SW layer)
- External SD mounted at /sdcard/external_sd and linked to /mnt/sdcard2
- goo.im app OTA update compatibility
- Synced with CM9
- New CM9 Bootanimation
- nvflash package includes updated CWM with working backup/restore
Alpha 1.0
- Initial Release
Downloads
As usual flash at your own risk
Gapps
http://goo-inside.me/gapps
CWM Package
update-cm-9.0.0-ALPHA1.6-k1-KANG-signed.zip
md5sum: 239091872daae568d7e9f1680ce49176
1. Place the update.zip on your external sdcard
2. Reboot into recovery.
3. Wipe data/Factory reset
4. Install .zip from sdcard
5. Choose the update.zip and say Yes
6. Flash gapps (optional)
Nvflash Package
K1_CM9_Alpha_1-5_nvflash.zip
md5sum: 7c34ec9242ab6ad4659b3bf310627ff4
Nvflash Windows Drivers
md5sum: 9aa3a4814ca63366329d85a22ed01f64
To boot into APX mode:
1. Power off
2. Hold down the Vol - and the Vol +
3. While holding the Volume keys down, Power on
4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode.
How to flash:
1. Extract the K1_CM9_nvflash.zip contents to a directory
2a. If using Windows, double click the "flash-windows.bat" file
2b. If using Linux, cd into the extracted directory and run either "sudo ./flash-linux.sh" or "./flash-linux.sh" from a root prompt
Source Code
http://github.com/khanning/android_device_ideapad_k1
-or-
git clone git://github.com/khanning/android_device_ideapad_k1.git
Special Thanks
The entire Cyanogenmod team and everyone that has contributed to CM
digetx
Koshu
Jon2555
All the developers that have made the source code for their device tree public. Thank you for helping to move the Android development community forward.
Thank you khanning88 and krook1 for releasing the first ICS rom for the K1!! Of course you had to upload this right before I leave for work, but thats okay! Now I have something to try out over break next week. Woohoo!!
thanks for another great rom ...even being alpha fast and smooth
Been running ice for around an hour now and no issues in performance
Glitches I've noticed
External SD shows being mounted but shows empty in total commander and es file explorer
and will not allow access
But other then the posted issues its running great
Sent from my K1 using xda premium
Just installed this, running great.
Installed Apex Launcher (smooth and fast)
link >>> Apex
Tried Chrome browser, kept crashing
Physical home button doesn't do nothing (no big deal, low priority)
Can't seem to get it connected to pc via usb port.
Storage > USB computer connection > MTP is checked.
After going through the Rom and I've noticed I can get to the external sd card if I go through. /mnt/sdcard2
But not through the regular way
I'm also going to make an update.zip for full screen nexus prime boot anim
Sent from my HTC Sensation 4G with Beats Audio using xda premium
This is excellent news.. ! Great to see progress on K1 custom ROMs!
Even though i have flashed custom roms on other android devices, i am a nOOB when it comes to K1 -- ie, should the tablet be rooted first before one can flash this ROM ? (using Root methods mentioned on other threads here?) or just do what is mentioned here ? -- Sorry.., but inputs here will help a lot of us.
djsat03 said:
Just installed this, running great.
Installed Apex Launcher (smooth and fast)
link >>> Apex
Tried Chrome browser, kept crashing
Physical home button doesn't do nothing (no big deal, low priority)
Can't seem to get it connected to pc via usb port.
Storage > USB computer connection > MTP is checked.
Click to expand...
Click to collapse
DISREGARD THE POST BELOW. BROWSER STILL CRASHES. BUT THIS ONE INSTALLS IF ANYOE WANTS TO PLAY AROUND WITH IT.
Chrome browser works. The problem is the same that all other unofficial ICS builds on other devices have. It has to do with the Device Id Check in the apk from the market. Download chrome from the link below and you are smooth sailing.
http://forum.xda-developers.com/showthread.php?t=1515900
Sent from my K1 using XDA
arjunprabhu said:
This is excellent news.. ! Great to see progress on K1 custom ROMs!
Even though i have flashed custom roms on other android devices, i am a nOOB when it comes to K1 -- ie, should the tablet be rooted first before one can flash this ROM ? (using Root methods mentioned on other threads here?) or just do what is mentioned here ? -- Sorry.., but inputs here will help a lot of us.
Click to expand...
Click to collapse
Like any Android device, flashing custom rom need custom recovery installed (ie CWM revovery).
And root is needed to install custom recovery !
Even the default browser for ICS crashed a lot. So far no problems with dolphin browser HD from market. Its fast and smooth browsing on there.
quyTam said:
Like any Android device, flashing custom rom need custom recovery installed (ie CWM revovery).
And root is needed to install custom recovery !
Click to expand...
Click to collapse
djsat03 said:
Even the default browser for ICS crashed a lot. So far no problems with dolphin browser HD from market. Its fast and smooth browsing on there.
Click to expand...
Click to collapse
I am not a NOOB, as I flash roms to my Droid Incredible all the time, but I have found the detail of instructions on flashing/root in the Idea K1 to be a bit confusing.
So any chance someone could add to the detail above, " if not rooted do install process #2 and follow these step by step"
Reads as if we can use the nvflash method, but no mention of rooting before, if that is the case great. I am looking forward to getting a new rom installed on my K1 as the stock is very buggy!
sorry, didn't see the nvFlash method. Not sur it need root or not (but think it's also needed)
quyTam:
Sorry for not getting back to you sooner. The CWM update.zip is used if you have already used my Honeycomb rom with CWM included. If you are on stock, or unsure, just use the nvflash method. There are no requirements to using the nvflash method because it reformats all the partitions. (root is not required, and it doesn't matter what build you are coming from)
ok, thanks for your reply.
didn't know the nvflahs method; it works on all Android device ?
ps: I don't have K1 but Thinkpad. Is it because Thinkpad doesn't have his bootloader unlocked, so it's not possible to use nvflash ?
khanning88 said:
quyTam:
Sorry for not getting back to you sooner. The CWM update.zip is used if you have already used my Honeycomb rom with CWM included. If you are on stock, or unsure, just use the nvflash method. There are no requirements to using the nvflash method because it reformats all the partitions. (root is not required, and it doesn't matter what build you are coming from)
Click to expand...
Click to collapse
Great to hear, is there any special needs for nvflash or is everything included in the nvflash method. I seem to remember in one of the rooting methods reading about installing drivers or related software necessary to use nvflash.
dc52317 said:
Great to hear, is there any special needs for nvflash or is everything included in the nvflash method. I seem to remember in one of the rooting methods reading about installing drivers or related software necessary to use nvflash.
Click to expand...
Click to collapse
i downloaded the nvflash zip file,.. and it talks about apx drivers.. and asks the user to have the tablet in apx mode --- where can one find that ?
arjunprabhu said:
i downloaded the nvflash zip file,.. and it talks about apx drivers.. and asks the user to have the tablet in apx mode --- where can one find that ?
Click to expand...
Click to collapse
That is exactly what I am trying to find out. I am planning on installing this when I get home in a few hours, but I am hoping that someone can add that detail to the post. I was looking a bit earlier, and found references to making sure you have these apx drivers installed for rooting etc, but no instructions.
Updated the nvflash section with the APX drivers and instructions.
Updated CWM recovery to 5.5.0.4 and fixed Backup/Restore. This will be incorporated into the next nvflash package. For now download the updated CWM recovery .zip in the 'Mods' section of the first post, and flash from recovery.
thank you..! Will try this out soon...
if i have to go back to stock rom from this ROM -- whats the process/steps?
Also, before I do this, is there a way for me to do a nandriod backup of the existing rom from within CWM ?
arjunprabhu said:
thank you..! Will try this out soon...
if i have to go back to stock rom from this ROM -- whats the process/steps?
Also, before I do this, is there a way for me to do a nandriod backup of the existing rom from within CWM ?
Click to expand...
Click to collapse
if you are not rooted and don't cwm on it already. Then just do the nvflash package instructions posted in the op.
This guide is for fellow at&t customers who will be stuck with JB 4.1.2 forever because there won't be an official 4.3 release (and any new Sony phones until at least the next year).
WARNING: You may lose some of your contacts if you don't follow this guide!
DISCLAIMER: I'm not responsible for bricked devices and data loss from power surges, hardware damage, or changes to the linked software. Always check the native manuals for all the tools listed here!
What You Will Lose:
All at&t branding
at&t address book (see below how to save contacts)
at&t emergency numbers dialer
Stable LTE connection (you'll see the H+ icon often in places with weak signal)
NFC icon
What You Will Gain:
Clean ROM with all stock Sony apps
All the new JB 4.3 features
Sony's new camera app with plugins
Significant improvement in battery life if your phone barely survives a day
What You Will Keep:
All of your contacts and data
James Bond themes
Root access
Recovery
Required Downloads:
1. Flashtool (got questions about it? - ask them here) - requires installation
2. @[NUT]'s dual XZDualRecovery. I'm linking to v2.7.94 BETA installer. If you wish to check for a more recent version, go to his download page and do a page search (CTRL+F) for XT-lockeddualrecovery[version-goes-here].installer.zip. (got questions about it? - ask them here) - unzip to a location you'll remember (say, C:\xperia-upgrade\recovery\)
3. @amarullz's AROMA File Manager - current version can be found at the bottom of the 2nd post - don't do anything to the zip
4. @DaRk-L0rD's Ultimate PureXT ROM and all patches and/or add-ons from the 2nd post you'd like (got questions about it? - ask them here) - don't do anything to the zip, save it to a location you'll remember (say, C:\xperia-upgrade\ROM\)
4.1 There might be additional files needed for the ROM, such as SuperSU update. They will be mentioned in the post. Download them to the same location as the ROM (e.g., C:\xperia-upgrade\ROM\).
5. at&t baseband FTF (attached) - unzip it to the default Flashtool firmware directory (C:\flashtool\firmwares\)
The Guide (assuming your phone is running at&t's 4.1.2 (9.1.F.1.120):
1. Backup any contacts saved in at&t address book or make sure there are none.
1.1 Open the stock Contacts app.
1.2 Tap the filter icon on the left.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1.3 Make sure that the two checkboxes are blank.
1.4 Go through every single connected account EXCEPT for AT&T Address Book and uncheck them (there might be a few), then tap OK.
1.5 Tap the menu button, then Back up contacts.
1.6 Select SD card.
1.7 You don't need to remember the location of the vcf file - the system will recognize it on its own.
2. If USB debugging isn't enabled yet, you need to do it.
2.1 Go to (System) Settings -> Developer options and flip the switch in the top-right corner of the screen.
2.2 Look a bit down (toward the middle of the screen) and check USB debugging.
3. Connect your phone to the computer and let the computer recognize it.
4. Copy AROMA Filemanager to the SD card
4.1 Go to the location on your computer where you saved aromafm.zip and copy the file (select, then CTRL+C).
4.2 Navigate to your SD card (not internal storage) and create a folder called clockworkmod.
4.3 Open the new folder and create another folder inside it called aromafm.
4.4 Open that folder and paste the zip (CTRL+V).
5. Copy the ROM and all of the files required for it to the SD card.
5.1 Go to the location on your computer where you saved the ROM zip with all other required files and copy the files (select, then CTRL+C).
5.2 Navigate to your SD card (not internal storage) and create a folder called 00-install (such a name keeps it on the top of the content list in Linux).
5.4 Open that folder and paste the zips (CTRL+V).6. Install the dual recovery.
6.1 Go to the location on your computer where you extracted dual recovery (e.g., C:\xperia-upgrade\recovery\).
6.2 Double-click install.bat.
6.3 Press 3 on your keyboard for the option 3. Installation on unrooted ROM.
6.4 Follow the instructions on your computer's screen.
6.5 When you will try to reboot the phone back into Android, the recovery will prompt you to root the OS. Do that.
7. Backup old system and install the new ROM (YOU MUST DO THIS!!!) - if you skip this and have issues, later, I'm not responsible
7.1 Initiate the reboot sequence by holding POWER + VOLUME UP for a few seconds.
7.2 Once you see SONY logo, start pressing VOLUME UP to enter clockworkmod recovery.
7.3 Connect the phone to a power outlet.
7.4 Tap Backup and Restore
7.5 Tap Backup to /storage/sdcard1 and confirm. The process can take up to 10-15 minutes depending on the amount of data in your internal storage.
7.6 When backup is complete, tap the Back button (2nd from the right) to go to the main menu.
7.7 Tap Wipe Cache Partition (4th from the top) and confirm the operation.
7.8 Tap Back button (2nd from the right) to go to the main menu.
7.9 Tap Advanced (3rd from the bottom), then Wipe Dalvik Cache (1st from the top) and confirm the operation.
7.10 Tap Back button to go to the main menu.
7.11 Tap Install Zip (2nd from the top), then Choose zip from /storage/sdcard1, then select the folder 00-install, then the ROM file, and confirm the operation. If you receive Status 7 error message, leave the phone as is, scroll down to the troubleshooting section to restore the backup and fix it.
7.12 Repeat step 7.11 for all the files that need to be installed.
7.13 When you are done, select Reboot System Now in the main menu. It may take good 20 minutes for the system to perform all operations needed for the first start.
8. If the phone doesn't pick up LTE signal, you need to re-flash the at&t baseband.
8.1 Turn off the phone.
8.2 Start Flashtool from your Start menu.
8.3 Click the flash icon, select Flashmode (default), and click OK.
8.4 In the list of firmware select the one you've downloaded (if this is your first time flashing, it'll be the only one for LT30) and make sure that No final verification is checked. Then click Flash.
8.5 When prompted, hold the VOLUME DOWN button, and connect the phone to the computer. The operation will take about 10-15 seconds. DISREGARD THE INSTRUCTIONS IN THE ANIMATION. Xperia T/TL doesn't have a hardware Back button.
8.6 Boot the phone.
8.7 Sometimes the phone will still lose LTE signal and show H+. You can reconnect to LTE by putting the phone into Airplane mode for a couple of seconds and then turning the Airplane mode off. If that doesn't help, open dialer, type *#*#4636#*#* to get into Testing service menu. There, you need to tap Phone information and scroll all the way to the bottom where you'll see a selector with the label Set preferred network type. Pick the flavor of LTE and downgrade that you'd like and watch the connection be re-established. Unfortunately, through experimentation, I've discovered that every ROM keeps its regional baseband regardless of flashing method (even overwriting with NAM bands will only enable LTE reception but the baseband property stays the same).
9. Battery fix if your battery dies within 9-10 hours of use.
Apparently, in some areas at&t doesn't support a network feature called fast dormancy (it allows for somewhat faster reconnection to the data network after idling). Some apps aren't written properly and keep on pinging Sony's FD service to connect, which results in thousands of wakeup alarms and the phone never entering deep sleep. You can notice this if Android OS is your top battery hog in standard battery usage stats (com.sonyericsson.android.wakeup is the service name). Before applying this fix, check your battery drain using BetterBatteryStats or Wakelock Detector. If you see what I've described, this will help you increase your battery life by at least a couple of hours (for me, it almost doubled).
There's one downside though: the last 10-15% of battery charging take much longer (my battery now charges over 3+ hours).
Huge thanks to @mirhl for writing the original guide.
1. Install some root-capable file browser (I prefer ES File Explorer for being free).
2. Grant it root access (in ESFE, tap the top-left corner to open the navigation sidebar, scroll down to Tools, tap it to expand, scroll down to Root Explorer, and tap the switch).
3. Mount /system as R/W (in ESFE, get to Root Explorer as above, but instead of the switch tap the tile itself, then tap Mount R/W, and move the radio button next to /system into R/W column).
4. Navigate and open /etc/fast-dormancy/fd_custm_conf.txt (ESFE has a built-in text editor but editing needs to be enabled through the top-right menu.
5. In the file, you'll see two lines ending with MCC and MNC and a zero next to each. Change the zeros to 310 (MCC) and 410 (MNC), save the file, and reboot the phone. That should take care of it.
IF SOMETHING WENT WRONG
1. There shouldn't be any issues until you complete 7.6 (phone backup).
2. You better have followed this guide and created a complete backup of the working setup.
Bricked phones (something went wrong and you turned off your phone and now it doesn't boot)
1. Download a 4.1.2 FTF file from this master list to C:\flashtool\firmwares\.
2. Remove the SD card from the phone just in case.
3. Follow the instructions in the master list on how to flash the firmware.
4. Insert the SD card back into the phone.
5. Repeat steps 2, 3, and 6 of the guide above to install recovery.
6. Boot into clockworkmod (7.3 above), navigate to Backup and Restore, then Restore from /storage/sdcard1 and select the appropriate backup. This will get you up to step 7.6 and you can try the guide again.
Status 7 error message when flashing a ROM
After some experimentation, I noticed that some rooting methods are the culprit. You need to unroot your phone (don't worry recovery installer will work either way and will reroot it safely). Just download this Xperia rooting script, connect your phone with Debugging access enabled, run the script, and select the appropriate option (unroot). When it's done and the phone reboots, reinstall recovery (it will prompt you at one point to root the device), and continue to 7.7.
Huge thanks to all the devs who have built the tools!
Changelog
Code:
v2 - Apr 1, 2014 - Added extensive troubleshooting & battery fix; formatting changes
v1 - Mar 26, 2014 - Original publish
I've linked your guide to my list: http://forum.xda-developers.com/showthread.php?p=50323041#post50323041
I think it will make many AT&T users happy
Nice one
I didn't do that at all due using Ubuntu, I download flash tool, I used the bell firmware didn't exclude baseband (they use the same bands plus h+42 for T-Mobile in case this phone has it). Rooted it and added a recovery, flashed a 4.3 ROM by our doomlord and flashed superuser update thus 4.3 no bloat and got LTE working on T-Mobile
Sent from Sauwny the TL
Durteedee said:
I didn't do that at all due using Ubuntu, I download flash tool, I used the bell firmware didn't exclude baseband (they use the same bands plus h+42 for T-Mobile in case this phone has it). Rooted it and added a recovery, flashed a 4.3 ROM by our doomlord and flashed superuser update thus 4.3 no bloat and got LTE working on T-Mobile
Sent from Sauwny the TL
Click to expand...
Click to collapse
Which rooting script did you use? I couldn't find a working one so I had to wait for a good flashable release. How's the battery life on Bell firmware?
bsined said:
Which rooting script did you use? I couldn't find a working one so I had to wait for a good flashable release. How's the battery life on Bell firmware?
Click to expand...
Click to collapse
I used the one that came with the flash tool 4.1.2 only, battery life wouldn't know it was only on the bell firmware for about 30 mins at most before flashing doomlords 4.3 ROM
Sent from Sauwny the TL
Durteedee said:
I used the one that came with the flash tool 4.1.2 only, battery life wouldn't know it was only on the bell firmware for about 30 mins at most before flashing doomlords 4.3 ROM
Sent from Sauwny the TL
Click to expand...
Click to collapse
That's strange. I've tried every single root method in Flashtool and none of them worked on 4.3.
Link to doomlord's ROM (I found only his 9.2.A.0.278 release)?
bsined said:
That's strange. I've tried every single root method in Flashtool and none of them worked on 4.3.
Link to doomlord's ROM (I found only his 9.2.A.0.278 release)?
Click to expand...
Click to collapse
Because I rooted bell 4.1.2, 4.3 can't be rooted yet without an unlocked bootloader
Sent from Sauwny the TL
Thanks for this. Its been a long time since I've upgraded, came from XperimenT 3.5, and I wasn't sure where to start reading first. I'm curious though. Do you know if the cpu control is working for us locked bootloaders?
Also, do you know how to get rid of this "close all x" button at the bottom of the recent apps list? It covers the bottom ago in the list. Plus I like the one in the top corner thats enabled by gravity box. I'm not sure how it even turned on. I don't remember it being there at first. Even disabling all the xposed modules doesn't remove it.
- Xperia TL, Ultimate PureXT v2 ~ via XDA App
redincali said:
Thanks for this. Its been a long time since I've upgraded, came from XperimenT 3.5, and I wasn't sure where to start reading first. I'm curious though. Do you know if the cpu control is working for us locked bootloaders?
Also, do you know how to get rid of this "close all x" button at the bottom of the recent apps list? It covers the bottom ago in the list. Plus I like the one in the top corner thats enabled by gravity box. I'm not sure how it even turned on. I don't remember it being there at first. Even disabling all the xposed modules doesn't remove it.
- Xperia TL, Ultimate PureXT v2 ~ via XDA App
Click to expand...
Click to collapse
- Judging by the CPU states reported in BBS, governor changes are working. Though I'm also using CPU Tuner for automatic downthrottling.
- "Close all X" is a part of the ported Z2 UI. There's a request to remove it in the ROM thread.
How did you root? is it the dual recovery that does that? or another method. Just asking as I understand that rooting the AT&T TL is extremely hard.
Happy-J said:
How did you root? is it the dual recovery that does that? or another method. Just asking as I understand that rooting the AT&T TL is extremely hard.
Click to expand...
Click to collapse
Dual recovery will prompt you to root the phone on reboot during installation and the new ROM retains root access. However, rooting 4.1.2 on its own was very easy, too - the scripts provided on the forums work flawlessly.
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Happy-J said:
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Click to expand...
Click to collapse
Yes its what I used for my att TL
Sent from Sauwny the TL
Thank you for your help, I think I'll be installing this very soon!
Happy-J said:
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Click to expand...
Click to collapse
FYI: the install might fail if the phone is rooted by a method other than the one included with recovery. If that's the case, see the bottom of the guide for troubleshooting - just don't forget to backup your existing setup before trying to flash.
bsined said:
FYI: the install might fail if the phone is rooted by a method other than the one included with recovery. If that's the case, see the bottom of the guide for troubleshooting - just don't forget to backup your existing setup before trying to flash.
Click to expand...
Click to collapse
Ok, I will keep that in mind when I start the installation, and just use the recovery's root. Thanks for the tip.
I can't seem to get into recovery. I have tried pressing volume up at said time, and long pressing, but no dice. Can anyone offer assistance?
Happy-J said:
I can't seem to get into recovery. I have tried pressing volume up at said time, and long pressing, but no dice. Can anyone offer assistance?
Click to expand...
Click to collapse
Did the phone boot into recovery during installation? If not, you need to reinstall it. If yes, there's now a new app called NDR Utilities - use it to boot into PhillZ Recovery. Otherwise, please ask the recovery script author.
No, the phone did not boot recovery any of the times I reinstalled it, which was about 5. I am going to try flashing back to stock and try it again. Thanks for the helping hand again, very much appreciated.
---------- Post added at 01:07 PM ---------- Previous post was at 12:59 PM ----------
OK, a clean flash of the stock firmware did the trick. Thanks again for the help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
[COLOR="Red"]* Your warranty is now void.[/COLOR]
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
The "N" is for Nougat
some words of wisdom:
1- This is an Android 7.1 Nougat-based release - update your third party addons to ensure compatibility
2- The CM backupscript.sh in recovery will ignore and remove incompatible applications from your system partition (these are usually non-CM apps that users have opted to install). You must install a compatible app (or app pack) to regain that functionality
3- You can flash CM14.1 nightlies directly from CM13 snapshot or CM 13 nightlies (no need to wipe, BUT for optimum results, better follow Clean Update procedure explain below.), provided you read and followed items 1 and 2
ALLERT:
4- Once one CM14 nightlies, you cannot downgrade back to CM13 – if you are thinking of just exploring the release, then take a backup of your existing installation if you want to go back to it.
5- You’ll need an N compatible recovery, i.e. TWRP 3.0.2-1
Happy Flashing,
Latest features :
XDA:DevDB Information
Cyanogenmod 14.1 for Falcon, ROM for the Moto G
Contributors
matmutant, luca020400, LuK1337, Google, CyanogenMod Team, Motorola
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Firmware Required: CyanogenMod13
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-09
Last Updated 2016-11-19
Download & Install
LINKs:
All Downloads
Nightly Changelog
OpenGapps choose ARM>7.1>micro/nano/pico (micro might still be too big... unless you use the custom install options that allows you not to install everything from the package)
Either way, you might want to further customize your installation (both gapps and system apps), refer to this tutorial
REMEMBER:
ONLY use TWRP 3.0.2-1 or up
/!\ Before installing, read post #3. /!\
HOW TO INSTALL
Requirements: Unlocked Bootloader, a Nougat compatible Custom Recovery and the Downloaded Zips.
NB: Since 20161118, with a Lollipop compatible recovery like TWRP 3.0.2-0, you will get stuck to recovery, It is MANDATORY to update to 3.0.2-1.; the following error is still present : E:unknown command [log] but will not prevent install.
Place the rom and other like Gapps on the internal Storage or on a USB OTG
Reboot to recovery using the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Do Wipes (Data, Cache, Dalvik and System partitions) if you are in a different ROM.
Select the Zips
Swipe to install (if using TWRP)
Reboot and wait 2-3 min
-Not confirmed for CM14 as of 20161109- Pro-TIP : To avoid GPS locking issue, refer to #Q7 of the CM12 dedicated FAQ
HOW TO DIRTY UPDATE
Download the rom zip using CM Updater or third party apps like CM downloader, CyanDelta...
Press update.
Wait 2-3 min
HOW TO CLEAN UPDATE : this kind of update helps to avoid any update related issues, you can follow this when coming from CM13 and want to keep you personal data.
ProTip : Read the Changelog and disable features that have been updated between your build and the latest build (this is important when Theme features are updated and it could break things)
Download the rom zip on the CM Website or using CM Updater or third party apps like CM downloader, CyanDelta... make sure you have gapps zip on your device
Reboot to recovery using the power menu or the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Format /system, /cache and /dalvik-cache (advance format in wipe menu of TWRP); do NOT Wipe DATA!
Select the Zips
Swipe to install
Reboot and wait 2-3 min
Notes, Bugs, and miscellaneous.
Tips and notes:
When choosing a Gapps package ensure it can fit into /system when flashed.
Nano gapps package is recommended as it fits and provides everything in a base package you will need for gapps support. Then, you can install the other google apps from the store later on if needed.
Remember nightly builds are experimental: they can and will be broken from time to time. Always have a backup at hand.
To transfer files from/to PC when plugged in you will get the charging mode prompt status in the status bar, then click it to change from charging mode to transfer files.
Considering the quite low amount of Falcon users left over here, I'm not sure about making a full-sized FAQ;
For now, the following will take that purpose:
[SIZE=+1]Q1: Where are themes/tiles/whatever gone?[/SIZE]CM14.1 I still at early stage of public development, you should expect to face bugs, missing features, regressions, and other things closely related to WIP. Do not complain about it (even less if someone already discussed it in the thread)
[SIZE=+1]Q2: How to get root?[/SIZE]
Enable Dev settings (multiple tap on "Build Number" in /settings/about phone/)
Go to Dev settings
Root access : Change to Apps and ADB
[SIZE=+1]Q3: Where is the Terminal?[/SIZE]It is now disabled by default, simple enable it in Dev Settings by toggling "Local Terminal"
[SIZE=+1]Q4: What's that # at the to right corner of my screen sometimes?[/SIZE]This icon warns you that an app or service is currently using its granted root access, maybe your file manager or some automated actions like Greenify auto hibernate is running (in the background?)
[SIZE=+1]Q5: Why does swipe to write feature doesn't work although it is enabled? [/SIZE]There is a fix for that "known" issue: see here.
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]
reserved
i will try it and will post the results.
Just downloaded the ROM and Pico GApps.
I'm running CM14.1 unofficial before. I'll do the Clean Install anyway.
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Edit: Pressing on "Skip" when I am being asked for my Google Account sends me back to the "Use Mobile Data" screen.
Edit 2: I can receive calls and messages, but can't send a message or call someone myself.
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
legendavey said:
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
Click to expand...
Click to collapse
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
cooldude5500 said:
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Edit: Pressing on "Skip" when I am being asked for my Google Account sends me back to the "Use Mobile Data" screen.
Edit 2: I can receive calls and messages, but can't send a message or call someone myself.
Click to expand...
Click to collapse
working fine on my xt1033 both sims are working, sms are also working didnt try the call yet
legendavey said:
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
Click to expand...
Click to collapse
as of CM14.1-20161109
I performed the "clean update" I had wrote before, (before it I reverted to stock theme.)
Install script complained about not being able to "log" the install which is expected as TWRP 3.0 wasn't supposed to support 7.1 logging feature on install.
Code:
E:unknown command [log]
Micro gapps was too big, so I used nano instead.
First boot attempt never went to home; a force reboot made it work.
First full boot was awfully laggy and many apps forced close after the mini setup-wizard (as I didn't wiped data, the wizard only asked for language and wifi), I let it set a few minutes and then reboot it.
Now the UI is really fluid and works perfectly
Some tiles in the quick access menu are missing (you can't add them I mean, or I didn't see them)
I will update in next posts if I encounter interesting things in the next few days.
cooldude5500 said:
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Click to expand...
Click to collapse
same,sim card not getting detected
edit:reflashed it and both sims are getting detected
Can we disable second sim if we want in this latest nightly of 14.1.
Because I need sim disable feature.
drwierdo said:
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
Click to expand...
Click to collapse
yes
drwierdo said:
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
Click to expand...
Click to collapse
Yes, this was fixed a while ago and it is working in this build, head to Settings > Buttons > Configure your home button action(s).
This is build is very stable and the multitasking is unbelievable. Totally worth it!
Hiraethic said:
yes
Click to expand...
Click to collapse
You can change that in buttons option
matmutant said:
as of CM14.1-20161109
I performed the "clean update" I had wrote before, (before it I reverted to stock theme.)
Install script complained about not being able to "log" the install which is expected as TWRP 3.0 wasn't supposed to support 7.1 logging feature on install.
Code:
E:unknown command [log]
Micro gapps was too big, so I used nano instead.
First boot attempt never went to home; a force reboot made it work.
First full boot was awfully laggy and many apps forced close after the mini setup-wizard (as I didn't wiped data, the wizard only asked for language and wifi), I let it set a few minutes and then reboot it.
Now the UI is really fluid and works perfectly
Some tiles in the quick access menu are missing (you can't add them I mean, or I didn't see them)
I will update in next posts if I encounter interesting things in the next few days.
Click to expand...
Click to collapse
We really appreciate the work you do (in your free time) for our beloved Moto G. I know you guys worked really hard for this to happen, I've been checking the CyanogenMod Gerrit for a while now.
P.S.: I was in no way trying to dissuade anyone from using the dirty update or clean update methods. In my experience, a clean flash is always the most stable in the long run.
battery icon options circle and landscape mode doesnt work.
Newer builds will hopefully be free of these
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
the reason why my sims were not gettting detected was i flashed supersu 2.78.
Hiraethic said:
battery icon options circle and landscape mode doesnt work.
Newer builds will hopefully be free of these
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
the reason why my sims were not gettting detected was i flashed supersu 2.78.
Click to expand...
Click to collapse
SuperSU over CyanogenMOD should have caused a bootlop, you were lucky.
running 20161109.
* Dual SIM works fine
*Music app is not opening. Showing me that the app is stopped (Is it just me?)
Long press Home button brings Google Assistant after configuring with Buttons settings. (I tweaked build.prop for bringing up Google Assistant)
Battery percentage is showing only on Icon Portrait. None of other icons are working.
It's been 7 hours since I flashed it. The SoT is not that bad.
May be I'll flash abyss kernel later to check if the battery life will be improved and the swipe is definitely working very well on abyss kernel.