Related
Vanilla FroYo FRF91
For your Droid2 & DroidX
Developed for You by Team DeFuse
Splitting Blur from your Moto Droid.
{
"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"
}
HotFix:
D2 1.2.1 - Download HERE - This will update your build to 1.2.1
DX 1.2.1 - Download full ROM, if coming from Fission 1.1+ you can install right over.
If you are coming from the 1.2.1 test file from IRC then still install this update file since it will remove items that did not make it to final build (Nexus One Livewallpapers that were not working)
Full 1.2.1 ROMs are listed bleow.
Changelog is listed below.
No need to wipe for update file. No need to wipe if AND ONLY IF you are coming from 1.1, 1.2 and upgrading to 1.2.1. You MUST wipe if coming from any other ROM.
D2/DX - HotFix for data still functioning when custom battery manager is used to turn off data during certain times. Download HERE. Install from recovery as any other update. Just mount system, do not wipe and select the zip file for update.
Twitter:
@AngDroid
@Drod2169
Web:
http://www.teamdefuse.com
IRC:
http://www.freenode.net
#teamdefuse
Changelog:
1.2 -> 1.2.1
Cleaned up Add_On folder. Removed items that would not work with this ROM, added Live Wallpaper packages.
Added Network location (AGPS) pop ups. Will pop up when permission is needed. It is working in ROM but the option is not in settings.
Data Manager fix now included. Fixed issue when setting custom battery manager profile but data was still on during off hours.
Few changes to build.prop.
Added transparent status bar pull down curtain.
1.1 -> 1.2
Addressed Superuser issue - Not sure if it is fixed for some users.
DX Build now has FroYo Android Keyboard stock - Install DX Multi-Touch in add_on folder if you prefer.
Addressed USB issue - Not sure if it is fixed for some users.
Added ability to overclock from shell. Open terminal (download from market) and type in proper commands.
Improved boot animation. Now with hi-res graphics.
Updated install script for ROM.
DX Build - Fixed displayed version info in about phone.
Add Ons have been fixed so all zip files should install fine.
More cleaning of code...
Not part of the release but I updated darkonion's one click root method. It is now an EXE file. Will fix all broken root issues, update you to latest version of Superuser and install the APK properly in data/app so any future update from market should not cause problems.
About ROM:
First Vanilla ROM for Droid2, DroidX & Droid2 WE!
First ROM for Droid2, DroidX & Droid2 WE that can be overlocked!
This is not an AOSP ROM but all stock packages are built from source. It is a complete set of vanilla Android applications. All Blur has been removed so it is the closest you will get to a true AOSP clean ROM for the Droid2/X/WE/Pro right now. This is not a themed ROM to make it look like AOSP ROM.
The purpose of this ROM was to remove all Blur and have a real Android experience. Please do not ask to add anything to ROM. Everything that is missing can be found in the Add On folder that was created when you installed ROM or can be downloaded from market.
The installed applications are all of your basic Android apps. Gmail, Voice Search, Car Home, YouTube and some other apps are missing since there are more updated versions on the market.
ROM has root, deodexed, busybox and zip alligned.
How To Report Bugs:
Before you report a bug please search through thread and see if someone has your problem and if a fix was found. If you do not find a fix please report bugs using this format.
In subject of post place "[Bug Report]" Bug here so it will read [Bug Report]Force Close with X APP.
In Body:
Device Name:
Explain in detail about bug and list anything that will cause it so we have more info when we correct it.
Install Insctructions:
Installing ROM:
This Method works for al supported devices.
It is suggested you follow all the steps even if you are coming from previous Fission ROM. If you do not want to perform all wipe steps then at least wipe system.
Pre-Installation Tasks:
You must have root. You can use our One Click Root in this THREAD.
You must have Koush's Bootstrap program for your device. Download from Market or check HERE.
Select the ROM for your device (Droid2, Droid2 WE, DroidX or Droid Pro)
Download and place ROM on SD Card
Open Bootstrap
Tap "Bootstrap Recovery"
Tap "Allow" if asked to grant SU Persmission
Tap "OK' on "Success" screen
Tap "Reboot Recovery"
You will be booted into Recovery
Use Volume up/down keys to navigate through menu. Press Camera button to Confirm selection. Power button to back up to last menu.
Create Backup - "backup and restore" then select what you want to do
Back out to main menu
Wipe Cache
Wipe Data
Mount System - Screen will read "UNMOUNT /SYSTEM" when mounted
Mount Data - Screen will read "UNMOUNT /DATA" when mounted
Back out to Manin Menu
Install Zip From SD Card
Choose Zip From SD Card
Select your ROM
Yes - Install
Wipe Cache
Wipe Data
Reboot
Back into Android
Perform a Factory Reset
Open App Draw
Tap Settings
Tap Privacy
Tap Factory Reset
Tap Reset Phone
Tap Erase Everything
Your phone will now be rebooted, perform factory reset and then reboot itself when completed.
Activate phone when prompted.
Enjoy!
You may install ROM by not wiping anything and not peform a Factory Reset. You will run into a few problems though. One will be battery manager may force close and Market Facebook App will not sync correctly with contacts.
Please do not ask if doing it another way is good. These are the instructions for a proper clean install and we will only accept bug reports if you followed the above instructions.
Installing Updates and Add Ons:
Open Bootstrap
Tap "Bootstrap Recovery" - if you have not installed yet on new ROM
Tap "Allow" if asked to grant SU Persmission - If you have not granted it SU permission
Tap "OK' on "Success" screen - if you have not installed yet on new ROM
Tap "Reboot Recovery"
You will be booted into Recovery
Use Volume up/down keys to navigate through menu. Press Camera button to Confirm selection. Power button to back up to last menu.
Mount System - Screen will read "UNMOUNT /SYSTEM" when mounted
Back out to Manin Menu
Install Zip From SD Card
Choose Zip From SD Card
Select your Zip File
Yes - Install
Reboot
If you are installing more than one update zip then please remember to mount system before installing new file.
Donations:
We do not have a DX to fully test ourselves yet so donating to project will help us obtain one. We would also like to obtain future devices such as the Droid Pro, Droid2 World Edition and whatever else may come down the pipe that we can port this ROM too. Your help will allow us to do that. If you would like to contribute to our project you may do so by clicking HERE
Downloads:
Fission 1.2.1 for Droid2 HERE
Fission 1.2.1 for DroidX HERE
Place Holder
Holding spot in line...
Hopefully lost stalker...
Please lets keep focus on thread topic if you have issues please PM me directly.
-McMex
Eagerly awaiting the release!
Sent from my DROIDX using Tapatalk
Breezer23 said:
Eagerly awaiting the release!
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Your wait is over...ROMs are now up
is it 1.2 or 2.0?
jrherras said:
is it 1.2 or 2.0?
Click to expand...
Click to collapse
Haha...news spread quick...1.2. First 2.0 based on Android 2.2.1 will be for D2 some time next week. Would love to develop both side by side but do not have a DX to work with.
haha coz you said in other thread it's going to be on 2.0. Is there a HDMI settings on 1.2?
I want to install this but can someone confirm whether or not apps can be added to the car home app? I'm running ApeX right now and it has the Google Car Home, but apps can't be added to the blank slots. I know there is a version that lets you customize it, so is that what's included in this ROM?
I would just install it and see for myself, but uninstalling requires flashing the SBF and while I have the SBF, I don't have instructions on how exactly to do it and have never done it - so I'd like to avoid it if possible.
ok this is weird everything is as if i have Vanilla FroYo FRF91 installed, but I still have a few apps that were from blur like NFS Shift, Files, and a few others...can anyone confirm if they do or dont have these apps...also cardock is not opening, I'm gonna reflash ROM and report back!
DX 1.2 Users...Please apply this update http://tinyurl.com/2fejpew it removes the easter egg...aka...my D2 ROM...accidenta file placement
Hahah Sorry
When I was moving the new boot animation I must have dropped the wrong file
that link is broken for me
paul89 said:
that link is broken for me
Click to expand...
Click to collapse
http://tinyurl.com/25rjngt
paul89 said:
ok this is weird everything is as if i have Vanilla FroYo FRF91 installed, but I still have a few apps that were from blur like NFS Shift, Files, and a few others...can anyone confirm if they do or dont have these apps...also cardock is not opening, I'm gonna reflash ROM and report back!
Click to expand...
Click to collapse
NFS and Flash are there because you need to delete the apk files in the preinstall folder which can be found in the root folder of phone. This is after every SBF or fresh phone, not ROMs fault. Use Root Explorer or something like it.
indypacer said:
I want to install this but can someone confirm whether or not apps can be added to the car home app? I'm running ApeX right now and it has the Google Car Home, but apps can't be added to the blank slots. I know there is a version that lets you customize it, so is that what's included in this ROM?
I would just install it and see for myself, but uninstalling requires flashing the SBF and while I have the SBF, I don't have instructions on how exactly to do it and have never done it - so I'd like to avoid it if possible.
Click to expand...
Click to collapse
If you are talking about the market version then you can install on this ROM. I left the car launcher in but left car home out so there was no issue with market downloads. The launcher needs to be there so you can download it and launch it.
MotoBoy said:
Haha...news spread quick...1.2. First 2.0 based on Android 2.2.1 will be for D2 some time next week. Would love to develop both side by side but do not have a DX to work with.
Click to expand...
Click to collapse
Wow... I am really looking forward to getting a 2.2.1 based rom If you need someone to test on the DX I am available
kejar31 said:
Wow... I am really looking forward to getting a 2.2.1 based rom If you need someone to test on the DX I am available
Click to expand...
Click to collapse
+1 also...
I sent you a PM via DroidLife regarding another issue...
Thank You
Thank you for another awesome release . Now!! you keep asking for donation, but you just refunded mine. I guess my money is not good enough..... (just kidding. I got the email). Donation resent with a little more.
I said this before. I'm in South Fl. and you are more then welcome to use my DX.
Thanks again for your guys hard work.
Anybody care to put up a video of this on YouTube ?
New hot fix is now posted. Cures data still being active when a custom profile is used in battery mananger.
The link is in the first post under the hot fix section.
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.
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
PLEASE PLEASE BE VERY CAREFUL WITH SAFESTRAP!!
MAKE A BACKUP OF STOCK RIGHT AFTER YOU GET SAFESTRAP INSTALLED SO THAT YOU HAVE SOME KIND OF DISASTER RECOVERY.
THEN YOU CAN RESTORE IT TO A ROM-SLOT (AFTER YOU MAKE ONE).
ONLY MODIFY ROM-SLOT FILES. LEAVE YOUR STOCK ROM ALONE!!
WARNING: THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
UNKNOWN ISSUE: If you try and start Wifi and the device crashes/reboots, try turning on bluetooth prior to enabling wifi and see if that works.
CURRENT PROJECT STATUS:
BETA-STABLE
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.7.x.x (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. These ROM-slots allow for different sizes of /system, /data and /cache partitions. The defaults *SHOULD* be good enough for flashing the stock-based ROMs.
NOTE: The bigger you make these partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Rooted w/ SuperSU installed
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Go into your old Safestrap app and use the "Uninstall Recovery" button
Open an "explorer" of some sort (ESFileExplorer, etc)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
DOWNLOADS:
CONFIRM YOUR STOCK OS VERSION BELOW AND THAT YOU ARE USING THE KINDLE FIRE HDX 7" (THOR)
[13.3.2.1 and earlier] LATEST FILE: Safestrap-Thor-3.72.apk
[13.3.2.3.2 and later] LATEST FILE: Safestrap-Thor-3.75-os3.2.4-B02.apk
Mirror 1: Crackflasher Download
Mirror 2: Goo.im Download
Here's an amazon-os .zip that can be used on rom-slots for re-flashing the OS -- MUST MATCH STOCK ROM:
THOR ONLY (HDX 7") 13.3.1.0: Download from goo.im
md5sum: 24fee10d8c6b0dbf583465baa938e842
It's the straight Amazon OS:
not DeOdexed
will not stop OTAs
is not rooted
the only changes I made, were to strip out the boot.img or modem.img flashing stuff.
To root, I recommend flashing SuperSU.zip from here and flash in Safestrap to the active rom-slot after flashing the ROM:
http://download.chainfire.eu/supersu
As of version 3.x, Safestrap Recovery is now based on TWRP. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
For the purposes of direct user testing I've established a channel on freenode.net IRC: #safestrap
I'm in the channel mostly all the time, but may not be active for discussion.
Special Thanks To
DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery
For those that missed it in the 1st post:
PLEASE PLEASE BE VERY CAREFUL WITH SAFESTRAP!!
MAKE A BACKUP OF STOCK RIGHT AFTER YOU GET SAFESTRAP INSTALLED SO THAT YOU HAVE SOME KIND OF DISASTER RECOVERY.
THEN YOU CAN RESTORE IT TO A ROM-SLOT (AFTER YOU MAKE ONE).
ONLY MODIFY ROM-SLOT FILES. LEAVE YOUR STOCK ROM ALONE!!
KNOWN ISSUES WHEN USING ROM-SLOTS (The ROMs are kept on loop device mounted partitions)
1. In theory you will lose an extra 3-4 percent battery compared to normal usage from 100% to 0% due to the extra read/write work involved when using ROM-slots.
2. The /data partition is kept separate from the "/sdcard" contents on SS ROMs. This causes the Storage settings to only show the size of the loopback data partition and then it shows "used" which includes the "sdcard" + /data so this can look odd at times (larger usage than partition size). It doesn't have any adverse affects that I know of.
3. No custom kernel flashing support at this time. Don't try it. It won't work. All kernels need to be signed by Amazon at the moment.
CHANGELOG:
[v3.75-B02]Bugfix rom-slot booting
[v3.75-B01]TWRP 2.7.1.0 update + display fix for 13.3.2.3.2/13.3.2.4
[v3.72]TWRP 2.7.0.0 update. *** This includes a bugfix for backup time showing correctly ***
[v3.72]Raised /data partition size to 16gb
[v3.72]Swapped "Reboot" -> "Download" mode to "Reboot" -> "Bootloader" (places you in fastboot mode)
[v3.70-B01]Seems like I have a solid fix for the "snow" effect when getting into Safestrap sometimes
[v3.70-B01]System partition now matches stock EXACTLY. You can't even change it in the settings due to the way I'm creating it during rom-slot creation. It's not a bug, that's on purpose. That being said, there should be plenty of room in that space to do what we want.
[v3.70-B01]Battery % now being displayed correctly in recovery
[v3.70-B01]Updated to latest Safestrap sources
[v3.65-B01]Initial release for Thor (Kindle HDX 7")
Congrats, Hash!
Sent from my iPod touch using Tapatalk
Nice, just got my my hdx last night. Will let you know my results once I'm not at work .
Thanks!
Sent from my Nexus 4 using Tapatalk
things are moving well, many thanks for your efforts!
I'm new to safestrap world. Can you tell me if there are downside of any sort using safestrap?
I mean, are roms installed via safestrap slower or limited under any aspect? I know it's the only way atm, but just asking...
zooster said:
I'm new to safestrap world. Can you tell me if there are downside of any sort using safestrap?
I mean, are roms installed via safestrap slower or limited under any aspect? I know it's the only way atm, but just asking...
Click to expand...
Click to collapse
GOOD QUESTION!
The ROMs are kept on loop device mounted partitions. This causes a few known issues:
1. In theory you will lose an extra 3-4 percent battery compared to normal usage from 100% to 0% due to the extra read/write work involved when using ROM-slots.
2. The /data partition is kept separate from the "/sdcard" contents on SS ROMs. This causes the Storage settings to only show the size of the loopback data partition and then it shows "used" which includes the "sdcard" + /data so this can look odd at times (larger usage than partition size). It doesn't have any adverse affects that I know of.
3. No custom kernel flashing support at this time. Don't try it. It won't work. All kernels need to be signed by Amazon at the moment.
Hashcode said:
GOOD QUESTION!
The ROMs are kept on loop device mounted partitions. This causes a few known issues:
1. In theory you will lose an extra 3-4 percent battery compared to normal usage from 100% to 0% due to the extra read/write work involved when using ROM-slots.
2. The /data partition is kept separate from the "/sdcard" contents on SS ROMs. This causes the Storage settings to only show the size of the loopback data partition and then it shows "used" which includes the "sdcard" + /data so this can look odd at times (larger usage than partition size). It doesn't have any adverse affects that I know of.
3. No custom kernel flashing support at this time. Don't try it. It won't work. All kernels need to be signed by Amazon at the moment.
Click to expand...
Click to collapse
Thank you for the answer.
I'm not yet an owner of this tab. I'd really want to buy this beast (8.9), but the fireOS is stopping me. So I'm eagerly awaiting for a custom rom. Locked bootloader "turned me off"
So, 1) do you think safestrap can be a solution for a real daily driving custom rom (I guess CM)? Or just something to try/play with?
2) is there any chance/hope to unlock that armored bootloader?
Awesome work Hashcode. You've made two of my devices bearable to live with.
Thanks so much Hashcode!!
zooster said:
Thank you for the answer.
I'm not yet an owner of this tab. I'd really want to buy this beast (8.9), but the fireOS is stopping me. So I'm eagerly awaiting for a custom rom. Locked bootloader "turned me off"
So, 1) do you think safestrap can be a solution for a real daily driving custom rom (I guess CM)? Or just something to try/play with?
2) is there any chance/hope to unlock that armored bootloader?
Click to expand...
Click to collapse
Sorry, but not yet. I talked to Hashcode and he was saying that since we can't use custom kernels yet, we can't use AOSP (Paranoid Android, Cyanogenmod, AOKP, CarbonROM, etc.) roms. It's okay, though. I plan on making a rom that will give you as close to CM experience as possible while still staying on an Amazon ROM.
As for the question regarding bootloader unlock, I'm not sure. I'm still in the process of experimenting with different things. I haven't had time recently though.
Sent from my iPod touch using Tapatalk
Reporting back - Safestrap worked fine for me. Haven't done anything but make a backup of stock yet, but everything seems to be in order. Looking forward to have something to flash .
Thanks again.
Sent from my Nexus 4 using Tapatalk
Gotta love this guy
Sent from my XT926 using Tapatalk
---------- Post added at 11:55 PM ---------- Previous post was at 11:29 PM ----------
HASHCODE I mean. Of course. I'm so giddy...oops I fell off my chair.
Sent from my KFTHWI using XDA Premium 4 mobile app
i dont own one and prob never will but awesome work as always bro!!
Installed and currently running a backup. Would it be a good idea once we get a flashable rom to uninstall all apps from stock to make as much free space as possible? Thanks again Hash for your hard work on this next best thing to an unlocked bootloader.
Noticed that there is some graphics driver issues leaving static / snow on occasion. Other than that, great tool, it saved me once already. Thanks Hashcode!
_Alex_ said:
Noticed that there is some graphics driver issues leaving static / snow on occasion. Other than that, great tool, it saved me once already. Thanks Hashcode!
Click to expand...
Click to collapse
Static / Snow in recovery?
Sent from my XT1060 using Tapatalk
Hashcode said:
Static / Snow in recovery?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
This happens to me as well. But only if i start recovery by pressing the button on boot. If i start it from the "reboot to recovery" button in the app, it looks fine.
Sent from my KFTHWI using XDA Premium 4 mobile app
Hashcode said:
Static / Snow in recovery?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
If I go into the safestrap app then reboot into recover everything works fine and looks fine. If I shutdown the hdx then enter the recovery on power up it looks snowy BUT is still usable. Check it out.
OFFICIAL OOS4.0.1 NOUGAT is out for OnePlus 3!!!
Incremental roll-out of OxygenOS 4.0.1 (N) for the OnePlus 3 is on !
Here are some highlights::
WHAT'S NEW
Upgraded to Android 7.0 Nougat
New Notifications Design
New Settings Menu Design
- Multi-Window View
Notification Direct Reply
Custom DPI Support
Added Status Bar lcon Options
Improved Shelf Customization
Updated APN Settings for select Carriers
Fixed Proximity Sensor bug during calls
Increased System Stability
***Known Issues and Fixes
Apps might not download from Play Store.
If you are trying to download via Data Roaming, it will not work. This is a known Google issue.
Please follow Google’s troubleshooting steps and see if the problem is resolved.
Try turning on Battery Saving Mode and reset Play Store app preferences.
If you have these 3 apps installed: Truecaller, AVG Antivirus and PayTm, please try to force stop or uninstall them before performing download from Play Store.
If you still experience mobile data issues caused by APN, please go to APN settings page and manually choose try all the options. In the case that mobile data is still unusable, please send me a pm along with affected career and device model.
WiFi connectivity might still fluctuate, if you experience this issue, please send me a pm
www.oneplus.net
Use server germany on oos 4.0 to get update directly
If you do not get update try clearing data of app (system update)
-Flashing (method 1) (Unlocked bootloader with custom recovery)
*Flash mod twrp via adb
*Command "fastboot flash recovery recoveryname.img"
*Reboot into recovery
*Clear system (data if u were on any other cm/aosp rom)
*Flash full zip
*Flash super su latest beta(optional)
*Reflash mod twrp
*Reboot
-Sideload (method 2)(Unlocked bootloader with stock recovery)
*Reboot into recovery sideload mode
*Type this command via adb on pc
*" adb sideload zipname.zip"
Download links
Zip ota 37mb (drive)https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
Full zip 1434mb (direct server)
http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
Twrp mod https://forum.xda-developers.com/devdb/project/dl/?id=21835
Hit the thanks button if u like
Join the WhatsApp group for discussion news and fun (no room for spammers)
https://chat.whatsapp.com/0vwWQykbwRoG1I51OhYVdB
Nishidh said:
Only some developers got this update here are some pics
36 mb
Zip files will be uploaded soon
Click to expand...
Click to collapse
No existing link though
Anything yet?
Again! Just updated to 4.0...
Nothing here yet going through Canada.
Nothing and here vpn Canada
Nishidh said:
Only some developers got this update here are
some pics
36 mb
U can update directly using VPN Canada server from oos 4.0 (Not Tested)
Zip files will be uploaded soon
Click to expand...
Click to collapse
Soon? Have you got those zip files?
This is it: https://goo.gl/MpKe7e
Do you need to be on the beta or stable branch to receive the update OTA?
Seems like stable.
Anyone got their hands on flashable zip file?
Why don't you guys just chill for a couple of days. Wouldn't that be nice
Do not need flashable zip, all you need is OTA download and do Local Upgrade
23Six said:
This is it: https://goo.gl/MpKe7e
Click to expand...
Click to collapse
did you save/capture the OTA zip before installing?
It's developer preview, and it's for the developer team I guess. Not for mass distribution.
And then why create a thread at XDA?
23Six said:
This is it: https://goo.gl/MpKe7e
Click to expand...
Click to collapse
How did u get it?
oriveradel said:
And then why create a thread at XDA?
Click to expand...
Click to collapse
Because XDA is for developers... :laugh:
Everyone knows that, but since is not for the public should be OnePlus forums only
No zip available guys, just developer preview so do not expect a zip.
{
"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"
}
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 7 devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
Placeholder
Placeholder
Placeholder
Hi, thank you for doing this. My rooted pixel 7 pro is prompting me to install a security update. I tried to update via pixel flasher.
Flashed with the latest platform tools from offical android site and downloaded the latest factory image. Pixelflasher showed no error
And then my phone still prompts me to download updates,
phone android version = 13
build = TD1A.220804.009.A2
android security update = sept 5 2022
Did I flash the old factory image? or am I doing something wrong? or the pixel update prompt is an error?
dangercl0se said:
Hi, thank you for doing this. My rooted pixel 7 pro is prompting me to install a security update. I tried to update via pixel flasher.
Flashed with the latest platform tools from offical android site and downloaded the latest factory image.
And then my phone still prompts me to download updates, phone android version = 13 and build = TD1A.220804.009.A2
Am I flashing the old factory image? or am I doing something wrong? or the pixel update prompt is an error?
Click to expand...
Click to collapse
You need to download the factory image at the bottom. It's sorted from oldest to newest. So currently TD1A.220804.031 is the latest.
@dangercl0se , like what @Tiebe says.
Tiebe said:
You need to download the factory image at the bottom. It's sorted from oldest to newest. So currently TD1A.220804.031 is the latest.
Click to expand...
Click to collapse
thank you, i am noob.
badabing2003 said:
@dangercl0se , like what @Tiebe says.
Click to expand...
Click to collapse
all good, operator error!
thank you so much for making this, saved me so much time!!!
New Release:
Oct 27, 2022 v4.3.1.0 release
Bug Fix: Magisk modules not listed on MacOS / Linux
Ok so im currently Bootloader unlocked, rooted and custom kernel on Slot B. I would like to update Slot A with verity and verification disabled using the same firmware currently in Slot B. Do I select processed firmware zip first or can I jump right to the patched magisk.img. I tried switching slots and flashing the firmware(no patched init_boot.img) with verity and verification disabled first. It goes through the steps and ends on the Fastbootd screen. When I reboot, it reboots 3 times and ends up on slot b. Not sure what Im doing wrong. I even tried checking "flash to inactive slot" and still boots to slot B.
schmeggy929 said:
Do I select processed firmware zip first or can I jump right to the patched magisk.img.
Click to expand...
Click to collapse
If you intend to flash the firmware on that slot, then yes, you have to select it.
schmeggy929 said:
I tried switching slots and flashing the firmware(no patched init_boot.img) with verity and verification disabled first. It goes through the steps and ends on the Fastbootd screen. When I reboot, it reboots 3 times and ends up on slot b. Not sure what Im doing wrong. I even tried checking "flash to inactive slot" and still boots to slot B.
Click to expand...
Click to collapse
This sounds like the flashing is not going past fastbootd stage.
I have read reports that it takes long in that stage (even doing things manually) with no feedback, so make sure you are waiting long enough.
You should also make sure your cable / USB drivers are good, and preferably use USB 2.0 port.
Few reboots and then back to B indicates that A is not bootable.
badabing2003 said:
If you intend to flash the firmware on that slot, then yes, you have to select it.
This sounds like the flashing is not going past fastbootd stage.
I have read reports that it takes long in that stage (even doing things manually) with no feedback, so make sure you are waiting long enough.
You should also make sure your cable / USB drivers are good, and preferably use USB 2.0 port.
Few reboots and then back to B indicates that A is not bootable.
Click to expand...
Click to collapse
Looks like third time's a charm, I also swapped my usb type-c to type-c cable with a USB-A cable.
When the next update comes around, is it recommended to check the box for "Flash to both slots" along with checking disable Verity and verification?
schmeggy929 said:
When the next update comes around, is it recommended to check the box for "Flash to both slots" along with checking disable Verity and verification?
Click to expand...
Click to collapse
I don't disable verity and verification, Magisk patches properly.
However if you are using custom ROM, then you want to check with the ROM maker if either or both are necessary.
As for monthly update, I recommend you flash to inactive slot, not both slots, this way it is similar to OTA A/B, ie if anything goes wrong, your current setup in the current slot is not effected.
badabing2003 said:
I don't disable verity and verification, Magisk patches properly.
However if you are using custom ROM, then you want to check with the ROM maker if either or both are necessary.
As for monthly update, I recommend you flash to inactive slot, not both slots, this way it is similar to OTA A/B, ie if anything goes wrong, your current setup in the current slot is not effected.
Click to expand...
Click to collapse
thank you, I will "Flash to inactive slot" route. And yes for now, the available Kernels require Verity and verification disabled. I only want to have both slots verity and verification disabled just in case something goes wrong and I have to boot the other slot. I do not want to have to full wipe because I booted a verity and verification enabled slot.
New Release:
Nov 09, 2022 v4.4.0 release
New feature: Font and Font size should be configurable by the user #33
New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
Handy to access a device remotely.
Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
I personally use this to test patching on remote devices, and also use it to access / install apps to my watch.
Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
Minor UI Improvements
If Magisk does not create a backup attempt to trigger Magisk to create one.
Update readme to include Pixel 7 / 7P specific info.
Typically I do everything manually but I decided to try this tool out on OSX and so far everything has worked flawlessly. Thank you for your work.
This is my first time using PixelFlasher; I usually do updates the manual way. I'm trying to install the November update and after flashing I'm getting the message about the device being corrupted.
If I hit the power button to continue it boots fine and everything seems to be good, but when doing this manually with the browser based Android flash tool, I don't end up with this message that I have to manually continue through.
Anyone have a guess as to what I'm doing wrong? FWIW, I'm trying to do this update while keeping data. TIA.
Edit: Attached Support.zip
dpotter38 said:
This is my first time using PixelFlasher; I usually do updates the manual way. I'm trying to install the November update and after flashing I'm getting the message about the device being corrupted.
If I hit the power button to continue it boots fine and everything seems to be good, but when doing this manually with the browser based Android flash tool, I don't end up with this message that I have to manually continue through.
Anyone have a guess as to what I'm doing wrong? FWIW, I'm trying to do this update while keeping data. TIA.
Edit: Attached Support.zip
Click to expand...
Click to collapse
FYI, I was able to get this fixed by flashing the Oct init_boot, then manually patching the November init_boot and flashing it.
I must have missed it the first time, but when trying to patch the November init_boot there was an error in the PixelFlasher console, "Foreign Key constraint failed", but it still showed the patched boot file as available in the list. Just wanted to put this out here in case anyone else runs up against a similar issue.
dpotter38 said:
This is my first time using PixelFlasher; I usually do updates the manual way. I'm trying to install the November update and after flashing I'm getting the message about the device being corrupted.
If I hit the power button to continue it boots fine and everything seems to be good, but when doing this manually with the browser based Android flash tool, I don't end up with this message that I have to manually continue through.
Anyone have a guess as to what I'm doing wrong? FWIW, I'm trying to do this update while keeping data. TIA.
Edit: Attached Support.zip
Click to expand...
Click to collapse
Looking at your logs I have the following observation.
You started with an old SDK, which is not a good idea, and PF warned you about it, and you chose to proceed regardless. Don't do this again, specially on the latest phones / firmware.
Code:
2022-11-17 20:08:35 ERROR: Detected older Android Platform Tools version 29.0.6-6198805
2022-11-17 20:08:51 User accepted older version 29.0.6-6198805 of Android platform tools.
SDK Version: 29.0.6-6198805
At this point Magisk was not installed, and your phone was on slot b
You first processed the 220804 firmware file, and when you tried to patch, PF told you that there was no Magisk on your device.
You then manually (outside of PF) installed Magisk Manager 25.2:25200, or if it was hidden, you restored it. (just for my curiosity, which was it?)
You created a patch from 220804 firmware's init_boot
Then followed by creating a patch from 221105 factory image
The above two patches was created by PF using binaries from Magisk Manager.
Tried to flash the patched file and the phone got stuck at fastbootd.
Most likely due to using an older Platform tools.
Code:
extracting super_empty.img (0 MB) to disk... took 0.002s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for REDACTED >
You then upgraded the SDK to
Code:
Android SDK Version: 33.0.3-8952118
But at this point your phone was already on slot a in bootloader mode, probably due to the previous botched flashing.
You tried to flash slot a and ran into this issue.
Code:
< waiting for REDACTED >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Still on slot a, next attempt was to flash both slots
This worked without errors and the system booted to slot b
You hid the Magisk Manager
you then processed 221105 factory image, (FYI this is unnecessary, if you do it once, nothing changes if you repeat it)
You patched this time PF using rooted Magisk
Interestingly the generated patch had a different SHA1: f44feb1bc2b8643333af5e14f0a12755b537f076
Whereas the previous patch SHA1 was 8753990ce4374d5a4509e0bae48f54e2553be216
This is a curious case, the only differences are.
875399 was patched using non-hidden Manager binaries
f44feb was patched using rooted Magisk
both same versions of Magisk.
I'd be very interested if you could share these files for me to inspect.
if you could zip the following (replace redacted with your username)
Code:
C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4
You then proceeded to flash to both slots again
Which went well.
End of logs
At this point your system is probably on slot a and working well.
dpotter38 said:
FYI, I was able to get this fixed by flashing the Oct init_boot, then manually patching the November init_boot and flashing it.
I must have missed it the first time, but when trying to patch the November init_boot there was an error in the PixelFlasher console, "Foreign Key constraint failed", but it still showed the patched boot file as available in the list. Just wanted to put this out here in case anyone else runs up against a similar issue.
Click to expand...
Click to collapse
No you didn't, or at least I didn't see that you did, If you don't mind I'd be interested in getting another support.zip from you which would include this along with the Foreign key error you encountered.
That error is benign, as PF knows how to handle it, but it is included so that I can troubleshoot and find the root cause (it happens very rarely and I'm trying to see what conditions are causing that)
Thanks and sorry for the delayed response, it takes time to process these logs.