Related
The purpose of this guide is to walk you through the process of rooting your phone running 2.3.3 ONLY! I will do the best I can to make this as painless as possible and help you achieve your goals of S-Off.
***THIS THREAD IS ONLY FOR OBTAINING S-OFF, OBTAINING ROOT, AND INSTALLING CLOCKWORK MOD RECOVERY! ANY QUESTION REGARDING INSTALLING ROMS DO NOT BELONG HERE AND WILL NOT BE ANSWERED! ONLY ISSUES REGARDING ROOT WILL BE ANSWERED BY MYSELF OR OTHER MEMBERS.***
What you will need: (** = File is attached to OP)
Windows XP or higher (Thats all I have, someone else with MAC and/or Linux will need to assist and I can add it to the OP)
http://revolutionary.io/ .:UPDATE:. PRE4 now available
This site is where you will download the rooting tools and obtain a beta key. When you click on the download button for your OS, make sure you view the box that pops up requesting your OS version, phone model, HBoot version, and phone serial number. Without doing this you cannot root your phone so do it or you are screwed. There are two ways to get your phone serial number: 1) Remove the battery and look at the white sticker or 2) On your phone, go to Settings -> About Phone -> Phone Identity and under Device Serial Number you will see it. After you receive your code COPY AND PASTE it onto a word document or notepad because there are times when you will get confused with the font type from the Revolutionary site. Example, in my beta key, the lower case L looks exactly like the capital I and it threw me off. Also, the key IS case sensitive so keep that in mind.
If running windows, you will need these drivers:
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
If running Linux, reports show that you do not need any drivers.
If running Mac OS, I currently do not know so someone please let me know and I will update.
http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip **
This file is required to obtain ROOT AFTER you have S-Off.
http://forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076 (WINDOWS) **
http://forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076 (LINUX) **
http://dl.dropbox.com/u/33327355/cwm-4.0.1.4-vivow.img **
These two items are in case Revolutionary tool fails to install CWM on your phone OR if you want to do this offline at another location. Fastboot and abd tool is the software that will take the img file of CWM and flash it onto your phone after S-OFF is obtained.
Prepping your Phone:
Turn off FAST BOOT in the settings located: SETTINGS -> POWER
Turn on Unknown Sources: SETTINGS -> APPLICATIONS
Turn on USB Debugging: SETTINGS -> APPLICATIONTS -> DEVELOPMENT
Installing Root:
1 - First, install the HTC drivers on your computer. It is a very simple step and you should have no issues doing this at all. Also look at your installed programs list and confirm HTC Sync is not installed. This will stop your device from being detected by Revolutionary to other problems when rooting.
2 - Extract the Fastboot and ABD zip file onto the root of your local disk drive (ex. C:\android-win-tools )
3 - Copy/Cut and Paste the CWM img file into the Fastboot and ABD folder (ex. C:\android-win-tools\cwm-4.0.1.4-vivow.img) Doing this will prep your PC to flash CWM in the event the Revolutionary tool does not download and install it.
4 - Place phone in "Disk Drive" mode then Copy/Cut and Paste the root su zip file (do not extract it) onto the root of your SDCard on your phone (ex. x:\su-2.3.6.3-efgh-signed.zip )
5 - Place phone in "Charge Only" mode. A lot ot people run into issues and not realize this was not selected.
6 - Run the Revolutionary file now that everything is set to go.
7 - You will get a prompt to enter your beta code. This is the code you received when you downloaded the revolutionary file and entered the information to obtain the beta key.
8 - Sit back and WAIT while the application does what is needed. This process will take anywhere from 3 to 5minutes so be PATIENT.
9 - Upon completion, you will get a prompt to install CWM. Say yes here! Once done skip to step 10.
9a - If the revolutionary app crashes or fails to download/install, leave your phone in the state it is (HBoot mode and should say "Fastboot USB". Open a command prompt in windows (Start - Run - type CMD).
9b - If you did exactly as told, type "CD.." until you see "C:\"
9c - Type the following:
CD android-win-tools
fastboot flash recovery cwm-4.0.1.4-vivow.img
9d - This process takes about 30sec max. Almost done!!!
10 - On your phone, back track to the main menu of HBoot using the volume keys and Power button and select recovery (2nd Option). In a few seconds your will be in CWM.
11 - As long as you copied the signed zip file to the root of your sdcard, perform the following:
"Install Zip From SDCard" (5th Option)
"Choose Zip From SDCard" (2nd Option)
Select the root/su zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait.
Back track to main menu and reboot
12 - Give yourself a pat on the back for paying attention and have a cookie!
I am typing this on my tablet/phone/pc so if an error exists, please let me know right away and I will update the OP. Again, questions here are ONLY for rooting. Anything else...kick yourself in the head, do a real search, and post if needed.
Support:
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Common Q&A for their recovery tool
irc.freenode.net channel #revolutionary
IRC Support Channel
Special thanks to:
XDA-Developers - You guys rock!!!
AlphaRev and unrevoked (Revolutionary) - You have made many dreams come true!!! DONATE to them if you can peeps.
http://forum.xda-developers.com/showthread.php?t=1122694 - attn1 - his How to guide on manually installing CWM.
Nice guide bro.
Sent from my Incredible Sensation using XDA App
The Incredible 2 or VIVO is not an option in the Beta key?
kyrumo71 said:
The Incredible 2 or VIVO is not an option in the Beta key?
Click to expand...
Click to collapse
The incredible 2 is definitely an option when obtaining a beta key. Unless you are refering to something else?
rivera82falcon said:
The incredible 2 is definitely an option when obtaining a beta key. Unless you are refering to something else?
Click to expand...
Click to collapse
My bad, my work computer is crappy, the 2 does not show up on my browser lol
NICE, this thread should be sticky.
On a side note, make sure you have your phone connected to wifi or 3G if you want the revolutionary tool to download and install the CWM automatically. If not then you would have to flash the CWM manually per the instruction from OP.
kyrumo71 said:
My bad, my work computer is crappy, the 2 does not show up on my browser lol
Click to expand...
Click to collapse
I went to the site just now and HTC DROID Incredible 2 is the 6th option down in the device list. If it still doesn't show up, test another pc or try it on your phone. All you need is the key anyways.
Sent from my A500 using XDA Premium App
Thanks for this guide...
Sent from my DROID using XDA App
Awesome thanks but question. my computer keeps saying usb device not recognized every like 5 seconds when my phone is connected and in bootloader. Is that suppose to be like that?
Darkpsych0 said:
Awesome thanks but question. my computer keeps saying usb device not recognized every like 5 seconds when my phone is connected and in bootloader. Is that suppose to be like that?
Click to expand...
Click to collapse
I will say it is okay as this happens to my PC as well. The files still transfer and CWM flashes through fastboot as well.
Sent from my A500 using XDA Premium App
Mmk. I downloaded ROM Manager but everytime i start it up it says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su/" or "system/xbin/su"
I have the file on the root of the sdcard and im pretty sure i rooted it with revolutionary and installed CWM as well.
Ok... Dumb question... where do we find the fastboot and adb zips to install on the C drive??
I have gotten thru step 8 and failed whentrying to install CWM. I manually installed it with step 9 and it said finished. Step 10 says to select recovery but it is not listed. I rebooted to see if that would work but it didnt. Where did I go wrong?
EDIT: Actually it did work just was trying to hard. Thanks for the great instructions.
@ Darkpsycho0
try installing busybox from the market and give it a try again.
@PacerguyDon
The links are in the OP.
It's next to the one that has the img file as well. There is only one zip file and it contains both items in it.
@Flightmed
Power down, and get back into HBoot. You will see the following options:
Fastboot
Recovery
Factory Reset
Simlock
Hboot Usb
Image CRC
The second option (Recovery) is what you want.
EDIT: Glad you got it working!!!
Sent from my A500 using XDA Premium App
Got it... thanks, Found it a few minutes after posting
PacerguyDon said:
Got it... thanks, Found it a few minutes after posting
Click to expand...
Click to collapse
It happens...we get so excited that we tend to overlook the obvious. Kind of like my wife...I love her to death and I love to make love to her but I overlooked the obvious that she is also crazy. Oh well...
Sent from my A500 using XDA Premium App
Busybox said "Root not found! The su binary was not found on your phone." -_____-
Thinking about it and looking back...I didn't complete the instructions on applying root. I apologize to you and everyone else.
When you have CWM installed, open it up through recovery. Next, as long as you copied the signed zip file to the root of your sdcard, select "Install Zip From SDCard" (5th Option).
Select "Choose Zip from SDCard" (2nd Option)
Select the zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait. Once done, reboot and you should be good!
Again, I apologize. I will update main post asap!
Sent from my A500 using XDA Premium App
That worked.. no more error thanks. I was about to throw my phone across the room especially since while i was waiting for replies I was trying to just install new themes but can't get Astros to work with the apk files correctly. -_- (still can't)
I'm already rooted via 2.2 but this is a great guide for the truly n00b.
Should be seeing lots of new members posting in the development section soon ;!)
[FONT=Albany, Arial]Flashing latest firmware (upgrading & updating) and rooting[/FONT]
For Sony Xperia ION LT28 Series – Locked and Unlocked Boot loaders.
THIS TUTORIAL IS IS NOT APPLICABLE FOR ROOTING ICS 6.1.E.3.7 LT28i and LT28h FIRMWARES.
To root these firmwares:
1. Follow Spectre's thread for Pre-rooted firmwares
OR
2. My thread for flashing stock kernel with root. (unlocked boot loaders only)
Click to expand...
Click to collapse
This guide is for everyone who wishes to flash the latest ION firmware and then proceed on to root it.
Though this guide is for Xperia ION, but I suppose, this is quite universal and applicable to all Xperia Phones.
Read carefully and understand clearly the process before starting the actual process of flashing. When in doubt, ask your queries in this forum and wait for it to get answered.
The Xperia ION Lt28 exists in 4 variants.
AT&T version with LTE. ( Lt28at )
Rogers Version with LTE. ( Lt28rogers )
International Version with LTE. ( Lt28i )
Version without LTE. ( Lt28h )
Getting Ready
There a a few very essential things that need to be sorted out before you could flash a firmware. I am listing them below.
Connecting the phone to the PC and making it recognize the phone.
(Windows only):
When you connect the phone to the PC for the first time, the phone will prompt you to install the PC Companion S/w on your pc. Go ahead and Install it. In addition to this, essential drivers required for connectivity will also be installed. In windows , both MTP and MSC modes of connectivity work. MTP mode allows access to both Internal and External SD card. MSC mode will allow access of only the External SD card.
Click to expand...
Click to collapse
(Linux Only):
It is a little tricky in the case of linux to achieve connectivity. The following are the steps you need to follow:
1. Open Command Window, “ terminal” in case of Gnome base Linux and “konsole” in the case of KDE based Linux. It should be easily accessable through menu.
2. Inside the Command Window type “ sudo gedit /etc/udev/rules.d/51-android.rules” if you are using Gnome or “sudo kwrite /etc/udev/rules.d/51-android.rules” for KDE.
3. Add the below lines into the file and save it.
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
4. Execute the following command from command window:
chmod a+r /etc/udev/rules.d/51-android.rules
5. Restart Linux now.
6. Connect the phone to the PC, open Command Window and type “ lsusb” without the quotes and press Enter. You should see an output, and you should see a line with the following:
ID 0fce:6177 Sony Ericsson Mobile Communications AB
7. If you don't see it, then you have made a mistake in the previous steps. Retrace the steps again to see that they are correct.
8. Open the phone, go to settings and select Xperia Settings and then select connectivity. Select USB Connection mode as “ Mass Storage Mode (MSC)”. The MTP mode does not work in linux. The support is not yet available.
9. Now when you connect the phone to the Pc it will mount the external_sd card automatically.
The above steps just ensures that the Phone is recognized by the PC and
Click to expand...
Click to collapse
Download and Install flashtool and Drivers:
Download flashtool:
Link1 ( http://androxyde.github.com/)
Link 2 Linux ( http://www.sendspace.com/file/0pz8ru)
Link3 Windows ( http://www.mediafire.com/?9d64a4twrqd3w7y)
Click to expand...
Click to collapse
Install Drivers:
( Windows Only) After installing Flashtool, navigate into the flashtool folder and go into drivers folder. Double click on the Flashtool-drivers.exe to install the drivers. Restart the computer. This step is not required for Linux Users.
Click to expand...
Click to collapse
Download and Install Android Sdk. (Not Mandatory)
Downloading Android Sdk:
Android Sdk can be downloaded from here. ( http://developer.android.com/sdk/index.html)
Click on the “SYSTEM REQUIREMENTS” to check that you sysytem meets the minimum requirement.
The downloads are under “SDK Tools Only” section.
Click to expand...
Click to collapse
Setting up Android Sdk:
( Windows Only) Installing in Windows is as simple as clicking in the downloaded exe. After installing, start the Sdk Manager. In windows it can be accessed from the start menu. Select Tools Checkbox and then Install Button. Wait for the installation to complete.
Click to expand...
Click to collapse
Set up the PATH environment variable to access adb:
( Windows 7)
Select Computer from the Start menu
Choose System Properties from the context menu
Click Advanced system settings > Advanced tab
Click on Environment Variables, under System Variables, find PATH, and click on it.
At the end add the path to android-sdk tools and platform-tools folder.
(Windows XP)
Start -> Control Panel -> System -> Advanced
Click on Environment Variables, under System Variables, find PATH, and click on it.
At the end add the path to android-sdk tools and platform-tools folder.
Click to expand...
Click to collapse
Setting up Android Sdk:
(Linux Only)
Right click on the downloaded .tgz file and extract it. Probably, it will create a folder “android-sdk-linux”. Copy the folder to root of your home. Open the file manager and navigate to the android-sdk-linux/tools folder and click on android script to execute it.
It will start the Android Sdk Manager. Select Tools Checkbox and then Install Button. Wait for the installation to complete.
Click to expand...
Click to collapse
Set up the PATH environment variable to access adb:
(Linux Only)
Now to set up the PATH environment variable to access adb. For this you need to edit the .bashrc file to setup the path so that adb can be accessed by just typing the command.
Open the command window and type “gedit ~/.bashrc” or “kwrite ~/.bashrc” and add the following lines and save it.
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
Restart the PC.
Click to expand...
Click to collapse
Proceed to POST#2 for FLASHING Steps.
Flashing and Rooting ICS on any Xperia ION
Flashing Firmware:
Now comes the easiest part.
So if you have completed the steps from post#1, then you are ready to flash the firmwares. It does not matter if your ION is on Gingerbread or Ice Cream Sandwich, the process of flashing remains the same. Flashing firmwares does not require Bootloader's to be Unlocked.
First and foremost you need to downlod the latest firmware for your Phone. So you head over to this site.
Firmware Links ( http://forum.xda-developers.com/showthread.php?t=1752345 )
After downloading the firmware, follow the Screen shot attachments with the steps below:
1. Start flashtool and click the lightening icon.
2 .Select Flash Mode.
3 .Select firmware to flash.
4. Click OK to start flash.
5. When the screen 5 pop's up, power down the phone. Press power + volume down button simultaneously. If the green led lights up, then the phone is in flash mode.
Flashtool will start flashing automatically. Once it is done flashing, it will show a message that the phone is disconnected.
Now detach the usb cable from the phone and press the power button to start the phone.
Click to expand...
Click to collapse
Proceed to POST#3 for ROOTING Steps
Rooting:
FOR LOCKED BOOT LOADERS
As per the developer of this method, it works only on ICS and JB.
To root the phone, first you need to download the rooting kit from here.
( http://forum.xda-developers.com/showthread.php?p=31545627#post31545627 )
At the time of writing, the latest version available is Version 15. ( http://ul.to/h44f6vni )
This is known to work well with Ion.
Also there is Version 13 which works well for me. ( http://www.mediafire.com/?1q4nt6b63ooaf1s )
Click to expand...
Click to collapse
This method of rooting requires the Backup & Restore utility to be installed on the phone. If it is not available by default, on your phone, download it from here. ( https://docs.google.com/file/d/0ByrrmqPijqISWElSQjV1aWVkMVk/edit?pli=1 ) and install it as a normal app.
Click to expand...
Click to collapse
Now on the phone, got to settings/developer options for ICS and enable USB debugging. Without this your phone will not be recognized by adb and you won't be able to root your phone.
Click to expand...
Click to collapse
Unzip the downloaded rooting kit to the place of your choice.
(Windows only) Connect the phone to the pc. Now navigate to the folder which contains the unzipped contents of the rooting kit. Click on the RunMe.bat. Now follow the instructions.
Click to expand...
Click to collapse
(Linux Only) I don't know if the Linux script in the latest version works or not. But it works in the the Version 13, which i have attached to this post. Open the terminal window and navigate to the folder where you have unzipped the rooting kit. Now type the following command and follow the instructions.
chmod +x runme.sh
sudo ./runme.sh
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FOR UNLOCKED BOOT LOADERDS
Flash the stock kernel with Root + Cwm + Init.d support.
Download this kernel.elf and flash it using flashtool.
The Download links and Instructions are on the OP of THIS post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
LINKS
Here is Captainkrtek's ADB GUIDE
Click to expand...
Click to collapse
very well put together guide. thx
now need root instructions for ICS
vladvertigo said:
now need root instructions for ICS
Click to expand...
Click to collapse
Rooting method of Xperia S works on our phone.
http://forum.xda-developers.com/showthread.php?t=1742992
This should go in a sticky as installing ice with LTE too many threads and right now.
Sent from my LT28at using xda premium
Updated Post 2 with rooting method for ICS.
I used this to root before you posted it but it slowed ICS down to point out was almost unusable. Any thoughts on why? Did I screw something up maybe?
Sent from my LT28h using xda premium
Recon Freak said:
I used this to root before you posted it but it slowed ICS down to point out was almost unusable. Any thoughts on why? Did I screw something up maybe?
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
I followed the above instructions as it is. I had pre-rooted gingerbread.
ICS is pretty fast, not as fast as Gb, but no lags either.
May be some problem with the ICS Rom zip. Try downloading it again. None have reported this problem.
I'm running it now and it flies. But as soon as I root it happens. I tried it twice from stock ATT and generic .111.
Sent from my LT28h using xda premium
Am I reading wrong? But I currently have ICS. So do I need to like re flash gingerbread then go back to ICS?
Sent from my Sony Xperia Ion
wolf0491 said:
Am I reading wrong? But I currently have ICS. So do I need to like re flash gingerbread then go back to ICS?
Sent from my Sony Xperia Ion
Click to expand...
Click to collapse
I think You will need to. Both the batch files need to be executed, to be able to get root.
ganeshbiyer said:
I think You will need to. Both the batch files need to be executed, to be able to get root.
Click to expand...
Click to collapse
That's just annoying haha. I'll wait
Sent from my Sony Xperia Ion
So I want to make sure I have this straight!
I have a stock ATT Ion 2.3.7
3. Application Settings: [Unknown sources] checked {Allowed}
4. Application Settings: Development [USB debugging] checked {Allowed}
5. Run Step 1.bat
6. Install Ice Cream Sandwich without wiping anything.
(wipe data, wipe cache and wipe apps log are not selected).
Once flashing is done, start the phone manually. It does not reboot automatically.
7. Application Settings: [Unknown sources] checked {Allowed}
8. Application Settings: Development [USB debugging] checked {Allowed}
9. Run step 2.bat
And this will give me ROOTED ICS 4.0.4 with locked bootloader?
Then what do I flash to get my LTE radio back? Just the Stock ATT baseband?
Sorry for the noobish question, my Ion is less than a week old and I havent picked insurance through best buy yet so I don't want to brick before I insure it
vpllover said:
So I want to make sure I have this straight!
I have a stock ATT Ion 2.3.7
3. Application Settings: [Unknown sources] checked {Allowed}
4. Application Settings: Development [USB debugging] checked {Allowed}
5. Run Step 1.bat
6. Install Ice Cream Sandwich without wiping anything.
(wipe data, wipe cache and wipe apps log are not selected).
Once flashing is done, start the phone manually. It does not reboot automatically.
7. Application Settings: [Unknown sources] checked {Allowed}
8. Application Settings: Development [USB debugging] checked {Allowed}
9. Run step 2.bat
And this will give me ROOTED ICS 4.0.4 with locked bootloader?
Then what do I flash to get my LTE radio back? Just the Stock ATT baseband?
Sorry for the noobish question, my Ion is less than a week old and I havent picked insurance through best buy yet so I don't want to brick before I insure it
Click to expand...
Click to collapse
Download the stock GB AT&T, when flash de-select all wipes. Checked everything esle below that Except baseband.
Sent from my LT28h using Tapatalk 2
Thanks for the guide. I had to do it solo, You might want to add in to guide for the noobs how to get into flash mode.
Where is the att ftf files located? Just in case something goes wrong
Sent from my LT28at using XDA Premium App
erichall82 said:
Where is the att ftf files located? Just in case something goes wrong
Sent from my LT28at using XDA Premium App
Click to expand...
Click to collapse
Firmwares are stickied at the top of the ion General forum.
ganeshbiyer said:
Rooting method of Xperia S works on our phone.
http://forum.xda-developers.com/showthread.php?t=1742992
Click to expand...
Click to collapse
FYI - this does have CWM in it, but because it was designed for the Xperia S it doesn't work completely. If someone would be so kind to redesign the CWM in that file for us that would be awesome!
My goal for this thread is to gather as much info for the BLU Life One X 2016.
Specs
Screen: 5.2", 1080 x 1920 pixels, ~424 ppi, Gorilla Glass 3
Memory: 2 GB RAM, 16 GB storage, microSD slot (up to 64GB)
Camera: 13 MP rear, 5 MP front, LED flash front & rear, [email protected] video
Battery: Li-Ion 2900 mAh
Chipset: Mediatek MT6753
CPU: Octa-core 1.3 GHz Cortex-A53
GPU: Mali-T720
Model: L0070UU
Links & Other General Resources
BLU Products
Amazon: Black - White
GSMArena
BLU Products Development Team (Google+)
L0070UU User Manual
ClanGSM claim to have firmware files for our phone but it would cost $$$ to download: / mnt / data / ftp / Flashes / BLU / Life One X / L0070UU /
Similar Phones
Wiko Fever (GSMArena)
Micromax Canvas 5 (GSMArena)
XOLO Black 1X (GSMArena)
Elephone P8000 (CM12.1) and P6000 Pro
Quantum Go 4G (PhoneMore)
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Note: While I use a variety of operating systems on a regular basis everything here will be Windows 10 focused.
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
Drivers
I recently setup a 5th gen Kindle Fire 7" tablet on my Windows 10 desktop. Because the BLU Life One X 2016 and the Kindle Fire are similar enough it just worked. To use the Amazon drivers you can find them on this page: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing. The direct link is https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip. Extract the zip file and then run KindleDrivers.exe.
Unlock Bootloader, Install Custom Recovery, and Install Root
Note #1: All credit for this guide goes to manos78's post for rooting the Wiko Fever!!! You can check it out here.
Note #2: I use Windows 10 on every PC I own. I assume Windows 7 and 8 should work just fine but cannot test that.
Note #3: The following assumes you have setup ADB and the proper drivers before beginning. I will try to detail that at a future time.
Note #4: Your phone will be completely erased. If there is anything you want to save do so beforehand.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
2) Install Custom Recovery
Note #1: We will flash a version of CWM or TWRP that was built for a Wiko Fever as they appear to be fully compatible with the BLU Life One X 2016. Go to this thread and download the latest CWM (http://www.sendspace.com/file/4g87bj) or TWRP (http://www.sendspace.com/file/y4jel8). Extract the img file. Again, many thanks to manos78 for CWM and hanuma for TWRP!!!
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
For CWM type fastboot flash recovery recovery-custom-wiko-fever.img or for TWRP type fastboot flash recovery TWRP_WikoFever_2.8.7.0.img
Type fastboot reboot
Note: If your phone does not reboot then just hold the power button until it turns off. Hold the power button again until it turns back on.
3) Install Root
Note: While there are newer beta versions of the SuperSU app I am not sure if they will work properly on our stock rom. You can test one of those out and report back but I would recommend you do a full backup beforehand.
Download BETA-SuperSU-v2.52.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in CWM. Go to Install zip, find BETA-SuperSU-v2.52.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Xposed
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Mine rebooted like five times during the "Android is starting" step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
ViPER4Android
ViPER4Android adds audio effects to your Android device and is beloved by many. First we will install SELinuxModeChanger and then ViPER4Android. Special thanks to Tha Watcher for his original write-up here.
1) SELinuxModeChanger
Go to the SELinuxModeChanger page on F-Droid, download the latest version (3.2 as of this writing) or use this direct link, and save it to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\com.mrbimc.selinux_42.apk
On the phone you may see a prompt saying Installation Blocked. If so, click the little triangle and tap Install anyway (unsafe). If you see a failure just do it again and it should work.
Launch the SELinuxModeChanger app on your phone, grant it root permissions, and click Permissive
Note: If you have any issues with SELinuxModeChanger then head over to the XDA thread.
2) ViPER4Android
Download the latest version in zip format from here and extract ViPER4Android_FX_A4.x.apk to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\ViPER4Android_FX_A4.x.apk
Launch the ViPER4Android app on your phone, click Yes when prompted, click Super Audio Quality, and then click OK
Grant root access when prompted
Click OK
Reboot your phone
Note: Once your phone reboots you can start configuring ViPER4Android. I cannot really help much with that but feel free to look over the official XDA thread or their Settings Explained page on the official website.
Engineering Mode
Note: If I were you I would not change anything unless you absolutely know what you are doing!
I cannot seem to get the phone codes to work. You can install the MTK Engineering Mode app from the Google Play Store.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Frequently Asked Questions
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
MTK Droid Tool
MTK SP Flash Tool
Latest Version: 5.1548.00.000
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Q: How can I tell if my model is the BLU Life One X 2016?
A: Go here and see if it is the same model.
Q: When I try to use adb root I get the following error: adbd cannot run as root in production builds
A: You can purchase and install [root] adbd Insecure by Chainfire. Once installed, launch the app, grant it root access, and then check Enable insecure adbd and Enable at boot
Q: How do I (re)mount /system as read-write?
A: Install [root] adbd Insecure as mentioned above, open a Command Prompt, type adb root, and then adb remount rw
Q: How can I disable the audio that plays when starting up or shutting down my phone?
A: Using a file explorer with root access, or an adb shell, delete or rename (with .bak at the end) /system/media/bootaudio.mp3 and /system/media/shutaudio.mp3 and then reboot your phone.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Reserved #4
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Has anyone been brave enough to try this yet?
---------- Post added at 02:16 AM ---------- Previous post was at 02:12 AM ----------
I'm receiving my phone tomorrow so i might be the guinea pig...lol
Did this last night on my phone. Most difficult part for myself was finding the correct drivers as this is my first mediatek device. Ended up being my fifth attempt that had the correct set.
After I had the drivers it was extremely similar to a nexus process.
Do you have a link to the drivers
Sent from my 6045X using Tapatalk
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
OK thanks
Sent from my 6045X using Tapatalk
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Click to expand...
Click to collapse
Unfortunately the guy that was bringing up the elephone p8000 has sold it and subsequently not be supporting it any longer. I'm happy enough there is custom recovery options and root. An AOSP ROM would be nice, but naturally the custom gestures would be lost.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
hottcakes said:
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
Click to expand...
Click to collapse
I was trying to using the link to download the driver, but the mega site asked for "decryption key" before I can download. Is there a key available to share? Thanks,
Tha Watcher said:
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
Click to expand...
Click to collapse
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
clu1688 said:
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
Click to expand...
Click to collapse
I appreciate that but the only way I'd post it in this thread is if the OP says it's fine. I do not like hijacking or taking over other people's threads.
It sounds like ADB is actually not loaded or working on your computer or otherwise you wouldn't get that message. I could be wrong, though. To test to see if it is indeed working and drivers are properly loaded, what does it respond when you type: adb devices
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu?...
Click to expand...
Click to collapse
Not yet, but I do plan to try to start with that. It's nice that Elephone released the source code for the P8000 so that could help as well. If I ever get to this I will need lots of help.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
Everything that *I* post in the OP will be something that I tested on my own device first unless I specifically mention otherwise.
hottcakes said:
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
Click to expand...
Click to collapse
I will add a note about that but some of us had issues so I chose the alternate method that has worked for me the first time every time.
I read an article on cnx-software that said that it is possible to install an unofficial version of Android OS on Nvidia Shield. It said: "It’s also running Android TV by default, which limits the number of apps in the play store. It’s however possibly to install a full (unofficial) version of Android."
I'm not much into gaming but if i can get Android TV, Netflix 4K and others plus Android OS to me that is a deal!
How do i learn more about this? Does it work? Is it hard to do? Does it void the warranty?
Thanks!
jacobpressures said:
I read an article on cnx-software that said that it is possible to install an unofficial version of Android OS on Nvidia Shield. It said: "It’s also running Android TV by default, which limits the number of apps in the play store. It’s however possibly to install a full (unofficial) version of Android."
I'm not much into gaming but if i can get Android TV, Netflix 4K and others plus Android OS to me that is a deal!
How do i learn more about this? Does it work? Is it hard to do? Does it void the warranty?
Thanks!
Click to expand...
Click to collapse
Yes, but your bootloader must be unlocked.
Andrid 6:
http://www.videomap.it/forum/viewtopic.php?t=1580
Android 7:
http://www.videomap.it/forum/viewtopic.php?t=1646
Thanks for the reply. I'm going to check this out!
Is it difficult to put on the shield? I've been searching on the internet and YouTube but haven't found a how to video or at least a reliable one, just videos of people showcasing that they had it. Please help? Thanks in advance.
Yes a good tutorial YouTube video would be greatly appreciated
Sent from my SM-G935F using Tapatalk
jeffery225 said:
Is it difficult to put on the shield? I've been searching on the internet and YouTube but haven't found a how to video or at least a reliable one, just videos of people showcasing that they had it. Please help? Thanks in advance.
Click to expand...
Click to collapse
First you have to know which android version you currently have (android 6 or 7?) And which nvidia shield tv you used (2015 or 2017? 16GB? 500GB?)
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
pn56137 said:
Yes a good tutorial YouTube video would be greatly appreciated
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=LQaYb4oVHVc&feature=youtu.be
I have the 2017 16GB version, I'll have to check to answer the other question though
---------- Post added at 10:37 AM ---------- Previous post was at 10:26 AM ----------
I have the 2017 16GB version, I'll have to check to answer the other question though
jeffery225 said:
I have the 2017 16GB version, I'll have to check to answer the other question though
---------- Post added at 10:37 AM ---------- Previous post was at 10:26 AM ----------
I have the 2017 16GB version, I'll have to check to answer the other question though
Click to expand...
Click to collapse
OK, then you have Android 7? Nvidia Update 5.1?
A Tutorial is here: http://www.videomap.it/forum/viewtopic.php?t=1646
I believe that I updated to the latest OS on there, and thanks. I think I've seen this before but I'll try to follow all the same. Thank you.
---------- Post added at 02:39 PM ---------- Previous post was at 02:18 PM ----------
Is there a simpler tutorial or can you give a simple step by step process cause the link you gave, while I am grateful, it's kinda intimidating and confusing a bit.
I I'll write you a new tutorial
Thanks so much I will try this today when I get off from work.
jeffery225 said:
Thanks so much I will try this today when I get off from work.
Click to expand...
Click to collapse
I hope this tutorial helps you, since my English is not so good. : D
I assume no liability for damage to the device
I tested it myself and it worked.
I have written this guide only for the Shield 2017 16GB with the Shield Update 5.1 (at your own risk, to test it with other versions!)
If the console is not recognized correctly on the PC, please apply this: https://forum.xda-developers.com/sh...status-faq-t3542005/post70773842#post70773842
All games and apps are deleted so make a backup!
1. On the Shield, go to Settings-Info and then scroll down to the point Build and press 7 times up. There should be a message where you are now a developer. Go back to the settings and go to developer options. Enable developer options and enable USB debugging
1.1 Go to the page: http://www.videomap.it/forum/viewtopic.php?t=1646
2. Download the ROM: https://goo.gl/l4y33q
***Driver: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
***Minimum ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
***TWRP: https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544
***SuperSU: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
You need a USB 3.0 A Male to A Male Cable to connect the Shield with the PC
3. Install the driver and minimum ADB and Fastboot
4. Next, put your SHIELD into fastboot mode using following method:
Controller method:
Connect SHIELD Controller using USB cable
Use USB port near HDMI port for PC connection ( You need a USB 3.0 A Male to A Male Cable to connect the Shield with the PC)
Hold Button-A and Button-on SHIELD Controller and then insert power adapter to SHIELD
5. Wait until you see Fastboot menu on HDMI display
Use X / Y to navigate
Use A to select
6. Go to C / Program Files and find the folder Minimal ADB and Fastboot and open it.
7. Extract the ROM, extract TWRP and copy the SuperSu.zip file into it. (System.img, vendor.img, recovery.img and SuperSU.zip)
8. Next you have to unlock the bootloader. Open Minimal ADB and Fastboot and press Shift and right-click and then open Command Prompt here.
8.1 Write in the command prompt this: fastboot oem unlock.
- When the bootloader is unlocked, In the command prompt type:
1) fastboot flash system system.img
2) fastboot flash vendor vendor.img
3) fastboot flash recovery recovery.img
4) fastboot boot recovery.img -> to boot TWRP recovery and flash SuperSu package. You need a regular mouse.
4.1) Go to Wipe and make a Factory Reset.
5) In TWRP go to: Advanced >> ADB sideload and swipe to enable sideload mode
6) adb sideload supersu_package_name.zip (You must flash the zip via TWRP, go to Install and select the zip)
7) Reboot system
Yeah I'm going to take my time and go step by step, how long did it take you to do it?
jeffery225 said:
Yeah I'm going to take my time and go step by step, how long did it take you to do it?
Click to expand...
Click to collapse
30 - 45 minutes
Ok thanks it's a bit confusing but I think I got it
jeffery225 said:
Ok thanks it's a bit confusing but I think I got it
Click to expand...
Click to collapse
I'm sorry, I've tried to explain this step by step, but my English is not so good!
LM209 said:
I I'll write you a new tutorial
Click to expand...
Click to collapse
LM209 said:
I'm sorry, I've tried to explain this step by step, but my English is not so good!
Click to expand...
Click to collapse
Nah, it's cool, I'm just going to read over everything a couple more times before I'm confident in trying it. I did try to start downloading some of the stuff, I tried to get the Nougat but it was taking too long and then it stopped. I got the second and third pieces but haven't tried the fourth and fifth things yet. I'm also about to get a USB male to male cable in a bit and try again.
LM209 said:
I hope this tutorial helps you, since my English is not so good. : D
I assume no liability for damage to the device
I tested it myself and it worked.
I have written this guide only for the Shield 2017 16GB with the Shield Update 5.1 (at your own risk, to test it with other versions!)
If the console is not recognized correctly on the PC, please apply this: https://forum.xda-developers.com/sh...status-faq-t3542005/post70773842#post70773842
All games and apps are deleted so make a backup!
1. On the Shield, go to Settings-Info and then scroll down to the point Build and press 7 times up. There should be a message where you are now a developer. Go back to the settings and go to developer options. Enable developer options and enable USB debugging
1.1 Go to the page: http://www.videomap.it/forum/viewtopic.php?t=1646
2. Download the ROM: https://goo.gl/l4y33q
***Driver: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
***Minimum ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
***TWRP: https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544
***SuperSU: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
You need a USB 3.0 A Male to A Male Cable to connect the Shield with the PC
3. Install the driver and minimum ADB and Fastboot
4. Next, put your SHIELD into fastboot mode using following method:
Controller method:
Connect SHIELD Controller using USB cable
Use USB port near HDMI port for PC connection ( You need a USB 3.0 A Male to A Male Cable to connect the Shield with the PC)
Hold Button-A and Button-on SHIELD Controller and then insert power adapter to SHIELD
5. Wait until you see Fastboot menu on HDMI display
Use X / Y to navigate
Use A to select
6. Go to C / Program Files and find the folder Minimal ADB and Fastboot and open it.
7. Extract the ROM, extract TWRP and copy the SuperSu.zip file into it. (System.img, vendor.img, recovery.img and SuperSU.zip)
8. Next you have to unlock the bootloader. Open Minimal ADB and Fastboot and press Shift and right-click and then open Command Prompt here.
8.1 Write in the command prompt this: fastboot oem unlock.
- When the bootloader is unlocked, In the command prompt type:
1) fastboot flash system system.img
2) fastboot flash vendor vendor.img
3) fastboot flash recovery recovery.img
4) fastboot boot recovery.img -> to boot TWRP recovery and flash SuperSu package. You need a regular mouse.
4.1) Go to Wipe and make a Factory Reset.
5) In TWRP go to: Advanced >> ADB sideload and swipe to enable sideload mode
6) adb sideload supersu_package_name.zip (You must flash the zip via TWRP, go to Install and select the zip)
7) Reboot system
Click to expand...
Click to collapse
Is this for the 2017 shield or the 2015? I have the 2015 one.
Sent from my SM-G935F using Tapatalk
pn56137 said:
Is this for the 2017 shield or the 2015? I have the 2015 one.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
For the 2017 Version, but i can create a tutorial for you.
Sorry I'll answer my own stupid question
2017
Sent from my SM-G935F using Tapatalk
Updated with more compatible adb link!
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then follow the guide to install adb https://www.xda-developers.com/install-adb-windows-macos-linux/
7. Follow the XDA adb install guide and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
shadi90 said:
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
Click to expand...
Click to collapse
This is for US Fold 3 models f926U/1. Sorry brotha. Basically you need to change the beta file you downloaded to this http://fota-secure-dn.ospserver.net...48:16&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA== as well as flash AUJ7 firmware first. I hear UK with CSC BTE works fine. Get it at https://samfw.com/firmware/SM-F926B/BTE/F926BXXU1AUJ7 . After you replaced those files, just follow the instructions again
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Haven't logged in to XDA in years. Just wanted to say THANK YOU.
mha1021 said:
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Click to expand...
Click to collapse
Don't rename the file.
What I always do with adb related stuff is put it in the root of my C drive. So it would be
Code:
C:\adb\platform-tools\
Then put the .bin file in here as well.
After that open cmd and do
Code:
cd C:\adb\platform-tools\
and hit enter.
After that do adb sideload 94 and hit tab so it should autofill the name of the update file.
Let me know if you have any questions.
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
AlexMartin00 said:
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
Click to expand...
Click to collapse
The baseband is just something that gets updated, so ZUJH is the Android 12 beta firmware. Every time you update your firmware the baseband gets updated as well.
More technical: Baseband is firmware that controls all radio devices on the phone, including GPS, Wi-Fi, Bluetooth, NFC, cellular data, and more.
Will this work on att Galaxy fold 3 since I can't get update cause att blocks it.
Hero_is_Over said:
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then download the "15 Second ADB Installer" HERE
7. Install the 15 second adb installer and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Click to expand...
Click to collapse
hi I'm getting a status 1 error with my sideload
erneyone said:
hi I'm getting a status 1 error with my sideload
Click to expand...
Click to collapse
What does the error say?
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
zimgir124 said:
What does the error say?
Click to expand...
Click to collapse
Status 1
Is there a mirror for the beta download anywhere? It looks like the link isn't working for me.
ElGuyarc said:
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
Click to expand...
Click to collapse
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Dick_Stickitinski said:
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
thank you so much...
I updated my SM-F926U1 with the Beta 4 its really buggy for me
Just want to get my facts straight. Can I just flash back to non-beta ?
What will happen to my Beta status will I still be able to OTA update when the next beta comes out ?
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
Is it a good idea to wipe my data when doing an downgrade like this ?
Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
I thought you can't flash a previous version of Android once you're on the higher version?