Related
Tutorial includes stock firmware .ftf files for Flashtool!
Changelog:
31/05/2012 - Adding firmwares.
13/06/2012 - ICS update.
14/06/2012 - Adding posts to keep improving. Massive dictionary update!
17/07/2012 - Few firmwares added!
16/08/2012 - Scrolling made easy!
07/06/2013 - Time to do something good!
This tutorial has been created to help XDA members in order to modify their 2011 Xperia phone. This tutorial is originally made for Xperia Ray by hansip87, link to original topic forum.xda-developers.com/showthread.php?t=1426912. Topic has been modified to fit the following phones:
Xperia Active (ST17)
Xperia Mini (ST15)
Xperia Mini Pro (SK17)
Xperia Live with Walkman (WT19)
These tutorials can also work on other 2011 Xperia phones. Instructions will also work with ICS unless written otherwise, so read carefully!
All kinds of ideas/comments/critism are always welcome.
Everything you do is on your own responsibility. I am not responsible for any damage that you have made to your phone.
Tutorial includes:
Android Dictionary
Root the Phone(GB and ICS)
What to do after rooting(apps etc)
Installing stock firmware and downgrading
Install Busybox and CWM Recovery
Unbricking your phone(after OTA update)
Install Supercharger to optimize Memory and KAK to optimize Kernel
Edit build.prop for additional optimizations
Enable Dual Band and Burst Mode for Wifi
Unlocking bootloader
Installing custom kernel
Installing custom ROM
Relocking bootloader
Preparing for ICS
Overclock/Underclock/Undervolting guide
Optimizing battery life
Downloads
Frequently Asked Questions(FAQ)
Yet to be added:
List of system apps and which can be removed
Depending on what tutorial you will follow, you may need:
Stock ROM on your Xperia and USB cable
PC Companion installed on your computer (for base drivers)
Flashtool(Flashtool topic and download)
Enable "USB DEBUGGING" from Menu -> Settings -> Applications -> Development
Enable "UNKNOWN SOURCES" from Menu -> Settings -> Applications
Set Connectivity mode to MSC from Menu -> Settings -> Sony Ericsson -> Connectivity -> USB Connection Mode
Root Explorer or any file manager that provides access to root (I personally use ES File Explorer)
1. Android Dictionary
ADB - Short for Android Debug Bridge. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
Android - Operating System for smartphones and tablets, based on Linux, built by Google, similar to Windows on PC.
AOSP - Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK - An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
Baseband - System of a smartphone, that controls the cellular radio systems(GSM, 3G, HSDPA etc).
Bootloader - Controls the booting process, makes sure that you will access User Interface. These programs tell the Android device how to start up, and are critical to its functionality.
Build.prop - A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations.
BusyBox - Command line bridge, used to give commands to Android system. You will need app to send commands, it will use BusyBox to send the commands.
Brick - A phone, that you paid a lot for and now you can use it as brick, because it doesn't start up.
CWM/ClockworkMod Recovery - A specific program, that is used before booting to Android. Allows the user to make full backup of system and install custom ROMs, updates etc.
CM - Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
Dalvik Cache - The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
Deodexed - Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
Downgrade - A job, that you have to do, when you want to get from newer firmware to older firmware.
Factory Reset - This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card.
Fastboot - Command Line Tool to edit Android filesystem. Unlike flashmode, this allows flashing unsigned partition images.
FC - Short for FORCE CLOSE. See FORCE CLOSE.
Flashing - The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
Flashmode - Phone mode, where you can freely flash any firmware to your phone via WotanServer or Flashtool.
Force Close - When a program on the Android device becomes unstable, the DALVIK program will force it to terminate to prevent further system instability.
GB/Gingerbread - Android 2.3 version, codename Gingerbread, mostly used shortly as GB.
Governor - A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HSUPA/HSDPA - Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS/Ice Cream Sandwich - Android 4.0 version, codename Ice Cream Sandwich, mostly used shortly as ICS.
Kernel - Bridge between hardware and Android, used for hardware information exchange and control hardware parts(CPU etc).
Launcher - A program that launches programs in Android. Examples are Touchwiz (Samsung), Launcher Pro, ADW Launcher, and Go Launcher.
MD5 Checksum - A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
Nandroid Backup - A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
OTA/Over The Air - Updating your phone firmware directly from your phone via 3G or WiFi connection.
Overclocking - Setting the processor's clock speed to run faster than its default setting, i.e. 1200 MHz (1.2 GHz) vs 1000 MHz (1.0 GHz).
RAM - Random Access Memory, data storage area, where are currently in use apps and services. It is used, because it has really high data transfer rate compared to other possibilities(SDcard, hard disks etc).
ROM - Read Only Memory, data storage, where the data can only be read by system itself. It includes all data to start the Android. Many developers edit this ROM to change Android interface.
Root(ing) - Process, during which user gets access to Android system partition and files, giving the possibility to edit Android.
SEUS - Sony Ericsson Update Service, can be used in some cases to get back to newest stock firmware.
Undervolting - Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
WotanServer - A paid application, which can be used to flash any stock firmware version with kernel to your phone.
2a. Root your phone - Gingerbread
Currently ZergRush method by DoomLord is the simplest way to do it.
NOTE: If you have newer firmware(4.0.2.A.0.62 or 4.0.2.A.0.69), check tutorial point 4 first to downgrade your firmware. This rooting method will not work on those firmwares.
Download the attached file from here, extract it to a folder using any .zip manager, for example 7-Zip.
Connect Phone to USB.
Execute "RUNME.bat" from the extracted folder.
Follow the instructions in the window.
The phone will be rebooted, after reboot you will have Superuser app and your phone is rooted!
Don't forget to thank DoomLord on the original link in the credits
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
2b. Root your phone – ICS 4.1.A.0.562 ONLY
NOTE: Make sure you have Android 4.0.3 and 4.1.A.0.562 firmware! This might not work on Android 4.0.4!
Download the file from this post, extract it to a folder using any .zip manager, for example 7-Zip/WinRar.
Make sure all drivers are installed.
Make sure USB debugging(Menu\Settings\Developer Options\Development) and Unknown Sources(Menu\Settings\Security) is allowed in the settings.
Connect Phone to USB.
Execute "RUNME.bat" from the extracted folder.
Follow the instructions in the window.
The phone will be rebooted, after reboot you will have Superuser and Busybox and your phone is rooted!
Don't forget to thank DoomLord on the original link in the credits
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
2c. Root your phone – ICS 4.1.B.0.431 and newer
NOTE: You need to have rooted version of older firmware(GB 2.3.4 for example)!
Download the Xperia-ROOT.revX.zip file from this post, extract it to a folder using any .zip manager, for example 7-Zip/WinRar.
Make sure USB debugging(Menu\Settings\Developer Options\Development) is allowed in the settings.
Connect Phone to USB.
Execute "01-local-prop.cmd" to create /data/local.prop (this enables android emulator the backdoor).
Follow the instructions in the window.
Update to 4.0.4 via PC Companion/Update Service(DO NOT REPAIR) or Flashtool(DO NOT WIPE DATA!). Else the hack will be lost and root cannot be done.
Open the "02-push-root-files.cmd" file from the folder, it will install Superuser and Busybox and push all required files to system.
Done.
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
3. What to do after rooting?
Congratulations! You've rooted your Android phone. But...what now? Here is a list of what you can do:
Install Titanium Backup. It allows you to backup all system and user apps with all data that belongs to the app. Very useful when installing firmwares and wipe is required. Using this program, you can easily backup and restore lots of apps at once. Also includes some other functions, link to Play Store.
Edit your Android. In this tutorial are some modifications that can be done. Read the forum, explore different sections and look for more modifications(there are thousands of them!), that you can do. Watch out, make sure that it will work on your phone, else you might mess up something and need to reinstall the ROM.
Remove unneeded system apps to free up some space on the ROM. This [/B]topic, http://forum.xda-developers.com/showthread.php?t=1089470, includes info about APKs, that can be removed and what must stay.
4. Installing stock firmware and downgrading
In the newer firmware, the ZergRush exploit has been blocked. If you want to return to stock ROM or you want to get your phone rooted, you have to install (older) firmware to your phone, which can be done 2 ways:
Flashtool, you need to find correct files yourself.
WotanServer, you have to register a account. - Costs €1.99
Flashtool method
Download the correct firmware file for your phone at the bottom of the post.
Make sure Flashtool is installed.
Place downloaded firmware file(.ftf format) in Flashtool\firmwares(by default C:\Program Files\Flashtool) folder.
Start Flashtool.
Click the lightning button and choose Flashmode.
Firmware should appear there, if you have it in correct folder. Choose it.
Turn off your phone, connect USB cable to computer, then press Volume Down button and connect USB cable to your phone.
Flashtool should detect your phone and starts flashing. Follow the instructions.
When it says „Flashing completed“, unplug your phone and turn it on.
WotanServer method
Go to WotanServer.com, make an account and download the client.
Start the client.
It wants to find your phone. Turn off your phone, then connect USB cable to computer, press Volume Down button and connect USB cable to your phone.
WotanClient detects your phone automatically.
Click Advanced Settings and choose firmware (4.0.2.A.0.58 or older if you want to root).
For region, it isn’t a big deal, which one you choose, although picking own one is easier.
Next, enter your account details(e-mail address and password) and click Update. Make sure you have enough credit.
Click Next and it will download proper firmware files and automatically install them.
When it’s ready, unplug your phone and turn it on.
After that you can proceed with rooting your phone, which is explained in previous guide. Or just enjoy your recently installed stock ROM
5a. Installing ClockworkMod Recovery
NOTE: You must have stock and rooted phone!
NOTE: Most custom kernels already include Recovery.
What you need to do:
Go to this link: http://forum.xda-developers.com/showthread.php?t=1346190 and download SE Tweak Installer.
Connect your phone via USB cable.
Start SE Tweak Installer.
Pick CWM, which is for your phone.
Click Install and wait. When it is ready, CWM is installed.
There is one more solution to install Recovery.
Go to Android Market/Play Store.
Search for Xperia CWM Auto-Installer.
Download the app to your phone and start it.
Follow the instructions to install the Recovery.
And enjoy having a recovery.
To enter the Recovery, turn off your phone, then turn it again, when Sony Ericsson logo appears, get ready. When screen gets brighter during Sony Ericsson logo, click Volume down button(I usually keep clicking it until I get into the recovery).
To move around in Recovery, use volume buttons to go up/down, Menu button to enter, Power button for back(in some cases, also back button works).
5b. Installing BusyBox
NOTE: Requires root.
NOTE: If you used zergRush method to root, BusyBox is automatically installed already and you can skip this.
Go into Play Store(Android Market) and search for BusyBox Installer.
Download it and start it.
Follow the instructions and install will be successful.
6. Turning the "brick" into a smartphone
If you had unlocked bootloader and did OTA(Over the Air) update, then you probably ended up with a dead phone, aka brick. Don't worry, it is not completely bricked, still can be saved!
Download UnbrickingXperia2011.zip file from this post below.
Unpack the .zip file and place the .ftf file in Flashtool\firmwares folder.
Open Flashtool.
Get your phone to flashmode, make sure it is turned off, press down Volume DOWN button and connect USB cable.
In Flashtool, click the lightning button, pick Flashmode and choose the Xperia_2011_FreeXperia_ALL.ftf file.
Let Flashtool finish.
Install stock firmware and kernel to your phone.
Remove USB cable from your phone and start your phone.
Try not to brick it again, less problems for you.
7a. Installing V6 Supercharger
Both can be used to improve the speed of your phone. Supercharger is meant to improve RAM, KAK is for kernel.
Install Script Manager.
Download Supercharger from this topic, http://forum.xda-developers.com/showthread.php?t=991276, make sure to download the "V6_Supercharger_for_Android-update8.sh.txt" file.
Place the file on root of your SDcard, that is the main folder on SDcard(where everything else is).
Open Script Manager, start the V6 Supercharger as normal. You can choose 0 as scrolling speed.
Pick the choice, that you like. I have used Agressive 1 personally(enter the number infront).
When done setup, just exit from the menu (no.17). The result file named 99Supercharger will be generated at /data/ (or in /system/etc/init.d/99Supercharger if you have init.d mod)
(If you use init.d mod, skip this) Open Script Manager, select the /data/99Supercharger.sh, and when the properties window pops up, tag it as "su" and "boot") The ScriptManager will load it at startup and as root, otherwise it will fail.
To test if the script is loaded or not, launch again the setup script(repeat step 4-5) You will find a text like "Launcher is.. xxxxxxx" if it is written as "weak", the script is not running yet. If it is "hard to kill" it is running correctly.
7b. Installing Kickass Kernelizer
This should improve your kernel, haven't tested myself yet.
Go to http://forum.xda-developers.com/showpost.php?p=22078137&postcount=7649 and download the file.
Open it with Script Manager.
Follow the instructions, I/O tweak is optional, I don't recommend it at this time. Pass when asked.
Press I for Install.
(If you use init.d mod, skip this) Open ScriptManager, select the /data/98KickAssKernel.sh, when the properties window pops up, tag it as "su" and "boot") The Script Manager will load it at startup and as root, otherwise it will not work properly.
Reboot your phone.
To verify, run it again after reboot and when it offers Verify, choose it.
8. Editing build.prop to optimize your phone's system
Build.prop consists of quite a lot lines, which set up, how some phone functions work. To edit the file, you need root rights and a program to explore root(ES File Explorer, Root Explorer etc).
Making a NANDroid backup in Recovery first is a good idea, because if you make a mistake in build.prop file, and phone does not boot into Android, you can still restore it.
Start your Explorer app and go to directory \system
Open build.prop file with a text editor.
Go with your PC to this post: http://forum.xda-developers.com/showpost.php?p=16833651&postcount=1. There are also other tweaks, you can try if you want(you might need init.d script for your ROM for init.d tweaks).
Read the first part of the post, there are some build.prop tweaks, choose which ones you want.
Make modifications in your build.prop file, save it and restart your phone.
Changes should take effect, if you have made a mistake, edit the file again or restore the backup, depending on the situation.
Some more tweaks for build.prop, init.d etc:
http://forum.xda-developers.com/showthread.php?t=1289539
http://forum.xda-developers.com/showthread.php?t=1342241
9. Enabling WiFi Dual Band and Burst Mode
As the title already, this is to increase the internet speed for WiFi on your phone.
Personally, I didn't notice any difference in battery usage.
Open Root Explorer, go to \system\etc and open file named tiwlan.ini with Text Editor.
Edit these lines:
Code:
HT_Enable=0
BurstModeEnable = 0
WiFiAdhoc = 0
to
Code:
HT_Enable=1
BurstModeEnable = 1
WiFiAdhoc = 1
and
Code:
Single_Dual_Band_Solution = 0
to
Code:
Single_Dual_Band_Solution = 1
Reboot your phone.
Tutorials | Firmware | FAQ | First Aid - Updated 13/6/2012
10. Unlocking bootloader
Unlocked bootloader is needed for most custom ROMs and for ALL custom kernels. It allows the booting system to be changed.
This can be done via official way or via test point method. Official way also removes DRM keys, which cannot be restored at all.
WARNING: You will lose warranty with this!
THE OFFICIAL METHOD - You lose DRM!
Go to http://unlockbootloader.sonymobile.com.
Enter service menu, open keypad and enter *#*#7378423#*#*.
Service Info - Configuration, Bootloader Unlock Allowed: Yes/No. If it says Yes, continue. If it says No, do not continue, because it will not work.
On the website, click "Start Unlocking the bootloader".
In the text, there are instructions, what you need to do. Also there are drivers that are needed for this process. Follow the instructions.
Install the drivers, then click Continue.
Enter your IMEI, name and e-mail. Leave out the last number from the IMEI.
You get a code, leave the website open, you will need this code.
Turn off your phone, then connect USB cable to your PC, hold down Volume UP button and connect USB cable to your phone. Blue LED should light up.
You will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
Open command prompt, first enter this
Code:
cd C:\...\android-sdk\platform-tools
Replace C with the correct drive letter and ... with the path to the android-sdk folder. Next, enter this command
Code:
fastboot.exe -i 0x0fce oem unlock 0xKEY
Replace KEY with the key that you got from the website.
Bootloader is now unlocked.
THE TEST POINT METHOD
Go to this topic http://forum.xda-developers.com/showthread.php?t=1285285.
Follow the instructions to patch bootloader.
11. Installing custom kernel
Most custom ROMs will require a custom kernel, some of these include it already(CM, MIUI etc), other you need to find yourself(Hybrom). Installation is done via fastboot. First, you need to find a custom kernel, that will work on your phone. You can find these from Development section.
Make sure your bootloader is unlocked, enter service menu(*#*#7378423#*#*), Service Info, Configuration, if it says Bootloader unlocked: Yes, then it is unlocked.
Make sure fastboot drivers are installed. These should come with Android SDK.
Download the kernel you want. You will need a .img file, which is mostly inside a .zip file.
From the downloads section, download kernel installation package and extract the folder.
Place the .img file inside the folder. If it's name isn't boot.img yet, rename it to boot.img.
Place your phone in fastboot. Turn it off, connect USB cable to your computer, hold Volume UP button and then connect USB cable to your phone. Blue LED should light UP.
Double-click on the flash.cmd file. It will start fastboot automatically and install the kernel.
When finished, disconnect the cable and turn on your phone.
12. Installing custom ROM
Requirements: Unlocked bootloader, ROM .zip file downloaded.
Nothing difficult here.
Place the downloaded .zip file to the root of your SDcard.
Install the custom kernel, explained in previous tutorial.
Enter Recovery(while booting, when screen gets brighter, press Volume Down button until phone enters Recovery).
Make factory reset, wipe cache partition and clear Dalvik Cache(under Advanced).
NB! Do NOT make format /system, because some ROMs require files from system folder and installation will not finish if files are not available. Then you have to install stock ROM again.
Choose install zip from sdcard, pick the downloaded .zip file on your SDcard.
Wait for it to finish and reboot your phone.
13. Relocking bootloader
When you return to stock and/or need warranty back, you will need to relock bootloader. First install stock ROM and kernel and then relock bootloader, else you will have problems. Depending on the unlocking method, there are 2 ways to relock.
TEST POINT METHOD
Start S1 Tool and click Restore button. Should relock the bootloader automatically.
OFFICIAL METHOD
Will not work on test point method, because bootloader was patched there ant not unlocked.
Make sure you have Flashtool installed.
From the downloads section, download Xperia_Relock_Bootloader.zip file.
Extract the package, there is a .ftf file.
Flash the .ftf file with Flashtool.
Bootloader is locked again
14. Preparing for Ice Cream Sandwich update
ICS update is already released. You might want to know, what you need to do to get the update. Make sure, that you have
a working Xperia 2011 device
with stock ROM and stock kernel installed(if you install via PC Companion or SEUS)
and locked bootloader(if you install via PC Companion or SEUS).
Root access doesn't matter(according to current information), whether you have or not. It is lost after update anyway.
PC Companion and/or Update Service installed on your computer.
Drivers working for your phone.
Official update will only be available via PC Companion and Update Service. But you can also use Flashtool to install ICS.
15. Overclock/undervolt/underclock guide
Want to give your phone a small performance boost? Or save battery?
WARNING! The following is done fully under your own responsibility! Overclocking is a dangerous process and doing it without knowledge will end in FULL BRICK! Be careful with what you do and proceed only if you fully understand the process!
You need root, unlocked bootloader and custom kernel, that allows OC/UC/UV, installed.
Install app to edit the CPU, for example SetCPU, SetXperia, NoFrills CPU Control or another one.
Open the application on your phone.
CPU Frequency is the clock, how fast your CPU works. The faster it works, the more power it uses, more heat is generated, info is faster calculated.
CPU voltage is how much power the CPU receives. It can affect, how CPU works. Manufacturers set it to high enough for CPU to work properly. You can set it lower to save battery, however you might occur problems with your phone!
Search on internet for more information about overclocking to know more about it.
Do everything carefully, as a small mistake could result in serious problems(for example, FULL BRICK due to motherboard damage). Repairing can cost more than phone itself.
16. Optimizing your phone's battery life
Tips, how to increase the battery life of your phone.
Turn off GPS, Bluetooth, WiFi, if you do not need them at that moment.
Turn off automatic sync(ronization). This can be done in Settings, but some apps also have those features inside their own settings. For that, open the application, open its settings and look there. These vary, so I can not help any further here.
Look for battery tweaks on the forum. These can be either build.prop or init.d type.
Turn off unnecessary programs, but not which start up automatically again. And do not use taskkillers.
Why? http://lifehacker.com/5650894/android-task-killers-explained-what-they-do-and-why-you-shouldnt-use-them
Turn off your phone, if you do not need it overnight.
Set display brightness to as low as possible, as high as necessary (depending, where you use your phone).
Remove unnecessary widgets. They require also some juice to keep on working and the more there is of them, the more juice is used. If the widgets on the home screen are not necessary, remove them.
If you do not use your phone for a longer period, use Airplane Mode, if it is possible. It saves a lot of battery by turning off all radio functions on your phone.
If you do not use mobile internet provided by your operator (that means you only use WiFi to go on the internet), then you won't need 3G either. Set your phone to GSM only, it saves quite a few % per day.
Underclock/undervolt your phone's CPU, if you have custom kernel that allows it. Do it carefully and only at your own responsibility!
NB! If you underclock/undervolt, do NOT “Set on Boot” until you know that they are going to work. Otherwise if it doesn’t work and your phone randomly reboots, you will get into a boot cycle (not a bootloop) because you put them in “Set on Boot”. You must test before you should do this.
Use apps like BetterBatteryStats or Android's stock Battery Info to find out, what is consuming battery.
And of course, just to mention it - batterystats.bin file has NO influence on battery life!
Tutorials | Firmware | FAQ | First Aid - Updated 13/6/2012
XX. Downloads
Stock firmwares, ftf file is inside the zip/7z archive(except PreRooted firmwares)
4.0.2.A.0.XX type - Android 2.3 Gingerbread
4.1.A.0.562 - Android 4.0.3 Ice Cream Sandwich - You will need 7-zip to extract the ftf file.
4.1.B.0.431 - Android 4.0.4 Ice Cream Sandwich - You will need 7-zip to extract the ftf file.
Xperia Mini (ST15i)
4.0.2.A.0.42 - http://www.mediafire.com/?uboo3lrdxnoeldn
4.0.2.A.0.62 - http://www.mediafire.com/?zad88cn2n78ashv
4.1.B.0.431 - http://www.mediafire.com/?wot47vumhstlc4h
Xperia Mini Pro (SK17i)
4.0.2.A.0.42 - http://www.mediafire.com/?hevz3x5w9pqt24q
PreRooted 4.0.2.A.0.69 - http://www.mediafire.com/?desy0bkka1b44g0 - Flash via Recovery
4.1.B.0.431 - http://www.mediafire.com/?j0bdx06zz5skvzt
Xperia Mini Pro (SK17a) - "a" model
4.0.2.A.0.58 - http://www.mediafire.com/?433tco785pj1y69 - Branded Mexico Telcel firmware
4.0.2.A.0.62 - http://www.mediafire.com/?zykznaar0yjxbp5
4.1.B.0.431 - http://www.mediafire.com/?9d2wcbfqly4lkf3
Xperia Active (ST17i)
4.0.2.A.0.42 - http://www.mediafire.com/?3zm7iss0sid94wr
4.1.B.0.431 - http://www.mediafire.com/?7hsrd2wmuqgmmq1
Xperia Active (ST17a) - "a" model
4.1.B.0.431 - http://www.mediafire.com/?yvjnt0qctun9t6j
Xperia Live with Walkman (WT19i)
4.0.2.A.0.42 - http://www.mediafire.com/?5ahb85ir7ni0i06 - NOT WORKING
4.0.2.A.0.58 - http://www.mediafire.com/?4deeznrbldz886u
4.0.2.A.0.62 - http://www.mediafire.com/?ervpg54922b9c0p
4.1.B.0.431 - http://www.mediafire.com/?xklhl2uk1itk0ey
Xperia Live with Walkman (WT19a) - "a" model
4.0.2.A.0.58 - http://www.mediafire.com/?adigb2qgvpf0o1s - NOT WORKING
4.1.B.0.431 - http://www.mediafire.com/?4t3mm7dvm01v3mh - NOT WORKING
Xperia Ray (ST18i)
4.0.2.A.0.42 - http://www.mediafire.com/?0oi9t2m0z5p8a9y
4.1.A.0.562 - http://www.mediafire.com/?1lh84f1nyzoz883
4.1.B.0.431 - http://www.mediafire.com/?2j7i7rruqxnui3q
Xperia Arc (LT15i)
4.0.2.A.0.42 - http://www.mediafire.com/?8aa5x52vc9dc25l
4.0.2.A.0.62 - http://www.mediafire.com/?0ann64yqnl4ei62
4.1.B.0.431 - http://www.mediafire.com/?pzr6phfd19xgbva
Xperia Arc S (LT18i)
4.0.2.A.0.42 - http://www.mediafire.com/?9mz2rhdouu6ggtk
4.0.2.A.0.62 - http://www.mediafire.com/?gn6y626km6nryi7
4.1.A.0.562 - http://www.mediafire.com/?9at03bbhdf72h3h
4.1.B.0.431 - http://www.mediafire.com/?20z5t5tg3dgbugz
4.1.B.0.587 - http://www.mediafire.com/?rhr59r4o6oarnfx
Xperia Neo (MT15i)
4.0.2.A.0.42 - http://www.mediafire.com/?4qy6vd4ndbfy8wy
4.0.2.A.0.62 - http://www.mediafire.com/?4apn8hchshmqq07
4.1.B.0.431 - http://www.mediafire.com/?6i2ihiint7tfl79
Xperia Neo V (MT11i)
4.0.2.A.0.42 - http://www.mediafire.com/?8bwwe8m6c49vs4t
4.0.2.A.0.62 - http://www.mediafire.com/?elicesjb6aerb7i
4.1.A.0.562 - http://www.mediafire.com/?aao25nnf30rcs50
4.1.B.0.431 - http://www.mediafire.com/?84d4w462qdfk44a
Xperia Play (R800i)
4.0.2.A.0.42 - http://www.mediafire.com/?cne2yvrtcu3ccvn - NOT WORKING
Xperia Pro(MK16i)
4.1.B.0.431 - http://www.mediafire.com/?8jdu5dkhlm4psoc
Kernel Installation Package for Xperia phones - http://www.mediafire.com/download/b8gz98ct96makyx/Kernel-Installation-Package.zip
Unbricking Xperia 2011 Package - http://www.mediafire.com/?s166qsg8qaaxc43
Relocking Xperia Bootloader Package - http://www.mediafire.com/?1an09qoq5yq4b5y
XX. Frequently Asked Questions
Q. I just installed custom ROM, but phone is frozen at the logo!
A. Did you install custom kernel, which is confirmed to be working with that ROM? If you did everything correctly, it might take a while, because at first boot new caches are created.
Q. Flashtool won't install stock firmware, gives this-and-this error.
A. Make sure phone is in flashmode(turn off, hold down Volume DOWN, connect USB cable). If yes, make sure, that correct drivers are installed. If yes, post here with FULL log, and I will take a look.
CREDITS
http://forum.xda-developers.com/showthread.php?t=1093062 - Android dictionary
http://forum.xda-developers.com/showthread.php?p=18805532 – zergRush rooting method by DooMLoRD
http://forum.xda-developers.com/showthread.php?t=1346190 - SE Tweak Installer by quangnhut123
http://forum.xda-developers.com/showthread.php?t=1426912 - Original tutorial by hansip87
FreeXperia Team for the unbricking file
http://forum.xda-developers.com/showthread.php?t=991276 - V6 Supercharger
http://forum.xda-developers.com/showpost.php?p=22078137&postcount=7649 - Kickass Kernelizer by zeppelinrox
http://forum.xda-developers.com/showthread.php?t=1477440 - Stock firmware list for 2011 Xperia phones by benji.berg
http://forum.xda-developers.com/showthread.php?p=24882250 - DooMLoRD ICS Rooting method
http://www.xperiablog.net/2012/04/16/root-for-android-4-0-ics-xperia-update-now-available-guide/ - Original Xperia ICS rooting guide
http://forum.xda-developers.com/showthread.php?p=26914104#post26914104 - Android 4.0.4 rooting guide by puppet13th
All users, who gave me ideas for this topic.
All users, who have shared their stock firmwares.
Everyone else, who I may have forgotten.
Thanks for the nice post. There should be a section for flashing kernel via Fastboot and Flashtool too.
BTW for installing ClockworkMod Recovery into the system partition, I highly recommend downloading the Xperia CWM Auto-Installer. It's right straight on Google Play and also absolutely free, just one click and everything will be done.
can't wait to see it done
acb123 said:
Thanks for the nice post. There should be a section for flashing kernel via Fastboot and Flashtool too.
BTW for installing ClockworkMod Recovery into the system partition, I highly recommend downloading the Xperia CWM Auto-Installer. It's right straight on Google Play and also absolutely free, just one click and everything will be done.
Click to expand...
Click to collapse
Already planned to add kernel and custom ROM flashing.
Will check out that Auto-Installer.
You should also add a 2 more sections on how to Flash stock ROM and Relock the Bootloader just incase anyone messes up. Also if needed, add a Unbrick method . Great thread and can't wait for more!
Plus, when you root through ZergRush method, doesn't that automatically install Busybox?
BudgyN1 said:
You should also add a 2 more sections on how to Flash stock ROM and Relock the Bootloader just incase anyone messes up. Also if needed, add a Unbrick method . Great thread and can't wait for more!
Plus, when you root through ZergRush method, doesn't that automatically install Busybox?
Click to expand...
Click to collapse
Unbricking is already planned, thanks for other ideas
As for the rooting, I am not sure. Could anyone confirm it, I used that method long ago, can't remember.
Sent from my WT19i using xda premium
I just read the ZergRush method thread and using it does install Busybox
Sent from my SK17i using XDA
sk17i
Root / Unroot Sony Ericsson Xperia 2011 v1.5 without unlock bootloader
http://forum.xda-developers.com/showthread.php?t=1346198
sk17i(4.0.A.2.335), root OK, no sw downgrade was needed
akloms said:
Root / Unroot Sony Ericsson Xperia 2011 v1.5 without unlock bootloader
http://forum.xda-developers.com/showthread.php?t=1346198
sk17i(4.0.A.2.335), root OK, no sw downgrade was needed
Click to expand...
Click to collapse
Downgrade is only needed if you have 4.0.2.A.0.62 or 4.0.2.A.0.69.
Also, I am unaware of this firmware, never heard/seen.
Sent from my WT19i using xda premium
Information for return from custom Kernel/ROM to stock one?
Only need to re-flash with WotanServer and re-lock the bootloader (before or after the flash)?
Thanks
m4x23 said:
Information for return from custom Kernel/ROM to stock one?
Only need to re-flash with WotanServer and re-lock the bootloader (before or after the flash)?
Thanks
Click to expand...
Click to collapse
Yes, just reflash with WotanServer and then relock bootloader if you want completely clean stock.
Will add guide about that also, thanks for tip
More stuff will come in the following days, been a bit busy.
Can you please post how to install Supercharger and KAK next? I read those threads and just getting confused how to install them. Really want to optimise my phone but not mess it up.
Thanks
I think you should add some basic concepts like what is fastboot or why do you need it difference between flashmode and fastboot and how to access them. What is the bootloader and what good or bad will it do to unlock it. Most new users don't know all that.
If you like to I can help you adding some concepts just let me know.
Oh and adding the info for the processor governor and i/o scheduler will be good to.
Hi there guys! By the way excelent tutorial, but I have an question!
I did the unlock bootloader by the test point method with s1tool!
I had Bootloader unlocked allowed: No and I still have it!
Here's the S1LOG: http://pastebin.com/XSDQ2iVf
Is my bootloader unlocked?
Please help,
pedrorubster
pedrorubster said:
Hi there guys! By the way excelent tutorial, but I have an question!
I did the unlock bootloader by the test point method with s1tool!
I had Bootloader unlocked allowed: No and I still have it!
Here's the S1LOG: http://pastebin.com/XSDQ2iVf
Is my bootloader unlocked?
Please help,
pedrorubster
Click to expand...
Click to collapse
Mmmm it is hard to tell with this log can you click on identify in s1tool and upload again?? Anyway I suppose you have a branded sim locked phone right?? Then even if you unlock your bootloader you won't be able to flash a custom kernel because the fast boot mode will be locked, if you are lucky you will be able to access it, you can always try, power off your phone hold down volume up key and connect it to your PC still holding down the volume up key it should stay off with the notification led on blue.
If you are lucky and can access it then you are good to go if not you will need to pay to fully unlock your phone sorry about that.
ginryu said:
Mmmm it is hard to tell with this log can you click on identify in s1tool and upload again?? Anyway I suppose you have a branded sim locked phone right?? Then even if you unlock your bootloader you won't be able to flash a custom kernel because the fast boot mode will be locked, if you are lucky you will be able to access it, you can always try, power off your phone hold down volume up key and connect it to your PC still holding down the volume up key it should stay off with the notification led on blue.
If you are lucky and can access it then you are good to go if not you will need to pay to fully unlock your phone sorry about that.
Click to expand...
Click to collapse
Thanks! I think I will have to pay 15€ to WotanServer...
pedrorubster said:
Thanks! I think I will have to pay 15€ to WotanServer...
Click to expand...
Click to collapse
Yes, branded phones can only have unlocked bootloader via paid method.
Sent from my WT19i using xda premium
Hi..sorry if my question is off topic
I did the unlock bootloader by the test point method
I want to relock bootloader back.
Im use Restore option at S1tool and got this error:
RUNNING S1_EROM VER "r9A021"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0098/00B3"
LOADER VERSION: "R4A069"
FAILED TO FIND RESOURCE ""
Anybody can help?
All right, so you wanna Full Unlock your Nokia L710 device but you faced a website on the internet saying it was impossible, which turned you down. There's a little thing you should now: most site are whether wrong or outdated, so it is very possible to full unlock a Nokia L710 (and theoretically a Nokia L800 too). But instead if you just want to developer unlock your device here's a thread that might help you with steps to officially dev unlock your phone free of charge: http://forum.xda-developers.com/showthread.php?t=1569119
It is very easy to full unlock your phone, but you must know that some knowledge and some nerves are required... Here it goes my experience on unlocking my Nokia Lumia 710 device. Note it has not been tested on Nokia Lumia 800 and that the stock rom with Qualcomm's bootloader is for Lumia 710 devices only.
Step 1.
First we must know if your device has its bootloader unlocked. Nokia phones were previously (and prior to tango updates hold that too) shipped with Qualcomm's boot loader, which allows nand access (needed to flash roms) and allows us to unlock our phones. To do so you must turn your device off, then press Power and Volume Up key till it vibrates. Then connect it to your Windows PC, where you shall get a notification whether saying Nokia Dload (nokia's locked boot loader) or a Explorer pop-up asking you to format a flashdrive (do not do that). If you get the Explorer pop-up your good to go to Step 2 but if you got Nokia's Dload, don't panic.
You are able to downgrade the boot loader using an old rom (this one specific is from Russia) that holds the Qualcomm's unlocked one. For this you'll need Nokia Care Suite and the stock rom files. The stock rom files you might find here (http://forum.xda-developers.com/showthread.php?t=1599401), a great thread posted by Suzughia where you can learn more about this issue. Anyway, the file you need is in the FAQ session, second question/answer. The NCS file I used you can download here (http://www.4shared.com/file/0YxlvalR/Nokia_Care_Suite_5_20115126304.html?) from my 4shared account*, but for the latest release you'll might check the official site, just google it.
Once you got NCS installed you'll have to go to C:\Program Files\Nokia\Nokia Care Suite\Drivers\ and install WinUSB Drivers x86.msi (or, if you use Windows 64 bit, the respective file). Then go to C:\ProgramData\Nokia\Packages (note that ProgramData is a hiden folder) and create a new folder named Products. Within this folder you'll copy the folder you downloaded (and unzipped, its name shall be, in this case, RM-803).
Now on the start menu you search for Application Launcher, and the app that appears shall call the Nokia Care Application Launcher. There you choose Product Support Tool For Store, a tool that allows you to install any rom from recovery (even the phone you've already unlocked using this tutorial or bricked phones, by theory). Wait to app to load up and connect your device on the computer. Now select the “Automatic Product Selection” box and waits till it recognizes your device. Notice your device might restart once or twice.
Now, in order to install the rom on your phone you must firt open your device model (even if the program indentifies your phone). Go to File>Open Product and select your phone model (in this case the Nokia 710 RM-803). Now go to the sidebar and select Programming>Recovery, on Properties you'll see the information of the rom you downloaded. Select it and then click Start. Ready, your phone is being flashed with the rom 1600.3015.8107.12070, that holds the Qualcomm's bootloader. Wait for it to reboot and you're ready to go to step 2.
Step 2.
Now we're gonna install the custom fully unlocked rom to your phone over the stock rom we just installed. To do so you must have access to a Terminal prompt (wheter on a Linux distribution or on an emulator running on Windows; I strongly recommend you to use Linux, which is more reliable) which will allow you to write the rom image to the phone's flash memory. You'll also have to download the os image, which you can get from Lucifer3006 here (http://forum.xda-developers.com/showthread.php?t=1654415).
Once you have access to a Terminal prompt and to the os-new.nb file you're ready to go. It is discussed on the thread by Lucifer3006 the use o NSS (a Linux terminal emulator), which I don't have experience to share. For instance, I used Ubuntu 12.04 for the flashing.
First boot your phone into Qualcomm's driver mode (just turn off your device, and then boot up holding power + volume up untill you feel a short vibration and then connect your phone to the computer) . Now you have to know the "address" of your device (that's given by the system). Open up terminal and type:
fdisk -l
With this command you'll see a list of the registered blocks of the storage devices on your computer. Usually your device will be the second on listed (in the case you only have your hardrive and your device plugged to the computer) and it is named sdXY, where X is the name of your device and Y is the number of the partition. On my case my device was f.
Now navigate to the folder you saved the os-new.nb file in terminal (in my case I saved on the User's folder, where the terminal opens by default in Ubuntu, the distro I used, or in most Linux distros). To be sure verify if the file is there by typing "ls", it will show a list of the files on that folder. If everything's fine, now you should enter the command that will copy the os-new.nb file to the phone boot memory, so the rom will be literally installed when the phone is booted.
Type this command in:
dd if=./os-new.nb of=/dev/sdX9
Explanation: "dd" is the command that copies the "if" to the "of" partition with low level privilegies. In this case "if" is the os-new.nb file and "of" is the boot partition address of your device. Make sure to replace the X with your device name. For example, my device was named "f", so my address will be of=/dev/sdf9, where sdf9 stands for storage device f, partition 9**. The boot partition of Windows Phone is addressed as the nineth one of the device (it is not an statement).
Once done copying (it will give you no feedback but the blinking square, so when it's done you'll just see the prompt address again) you shall disconnect your device.
In order to boot your device you have to perform a hard reset (this will literally install the os-new.nb to your device). To do so you have to hold down power + volume up + camera key for 10 seconds, then release the power key but still hold the volume up and the camera key for more 5 seconds (this was said in other post I can't remember which, don't know if is the correct way, but it worked for me). If the device does not boot up you can remove the battery and place it again, now just turn it on normally, and it will boot into the custom fully unlocked rom.
Note that the WP Root Tool installed on the rom is the 0.9 version and as for up to today it has expired, so you won't be able to use it unless you set your device date to past August 2012. In Baazar you can install the newer version but for using it you must mark it as trusted in RootManager app included on the mod rom.
Post anything you have to say and if you have a doubt, just ask me and I might help with anything I'm capable of.
Notes:
Everything I posted here is upon my personal experience only. I do not own any rights over any file posted here through other threads. The responsability for them relies on the threads' holders then.
* I do not own any rights over this program and I just posted a personal link once I wasn't able to recall the original one. Also this is the only file who sucessfully recognized my device upon my experience.
** This is said just to make an example and clearify the idea, it is not its actual meaning for as long as I don't know its actual meaning.
All Links Used Here:
Nokia Care Suite version 2011.51.2.63046 5.0
http://www.4shared.com/file/0YxlvalR/Nokia_Care_Suite_5_20115126304.html?
Get Ubuntu Linux 12.04 for free
www.ubuntu.com
Nokia's 710 RM-803 Country Variant Russia direct download link:
http://narod.ru/disk/45935058001.2aaca38c9acf622332f4a81b5bf0e331/RM-803.rar.html (300mb)
How to Interp Unlock Nokia l710 original thread:
http://forum.xda-developers.com/showthread.php?t=1599401
RainbownMod v1.4 and older, also the original thread of discussion:
http://forum.xda-developers.com/showthread.php?t=1654415
Is it possible to get that ROM from somewhere else, all it does is download YandexBarChrome in russian!... lol
*nevermind... i installed the stupid bar and it let me get the file.
**I cant get this stuff to work.... I get an error when installing the NCS, it installs anyways, but then never detects my phone. Any help would be appreciated!!
XperianceIT said:
Is it possible to get that ROM from somewhere else, all it does is download YandexBarChrome in russian!... lol
*nevermind... i installed the stupid bar and it let me get the file.
**I cant get this stuff to work.... I get an error when installing the NCS, it installs anyways, but then never detects my phone. Any help would be appreciated!!
Click to expand...
Click to collapse
What operating system are you using? I usually get installation error and phone never detected when running it on Windows 7 or Windows 8 64bit.
You might try reinstalling the NCS, and if it holds the same error, check the official site for the updated program and try it.
When you connect your phone to the computer, does the program recognizes an unidentified handset or it doesn't recognize your phone at all?
Unlocked
Sent from my Lumia 610 using XDA Windows Phone 7 App
My problem is this:
File C:\Documents and Settings\All Users\Application Data\Nokia\Packages\Products\RM-803\RM803_059M5W4_Qualcomm_DLOAD.vpl has no signature.
I have a problem. After I copy the ROM to the memory, I can't seem to boot to it. I feel the vibrations but everything is black. Please any help
Hi, i've bricked my phone...someone knows how to unbrick.?
luisfernandoo.nunezfranco said:
Hi, i've bricked my phone...someone knows how to unbrick.?
Click to expand...
Click to collapse
Without any further details, it's going to be difficult to help. It's pretty hard to do so..... What did you do to brick it? Can you get into recovery. Do you have a custom rom? Provide some more details & someone might be able to help you
mightymaki said:
Without any further details, it's going to be difficult to help. It's pretty hard to do so..... What did you do to brick it? Can you get into recovery. Do you have a custom rom? Provide some more details & someone might be able to help you
Click to expand...
Click to collapse
>Hi Friend, i would appreciate yor help, my Nubua Z7 max is bricked after flashing the new(from needrom site) 5.0 stock rom and reflashing the original kitkat stock rom.
I need to repartition the phone storage , when i boot it appears only 4.0 Gbyte storage for programs , but no internal storage.
How can i repartition the internal storage?
Thank you
Simonis said:
>Hi Friend, i would appreciate yor help, my Nubua Z7 max is bricked after flashing the new(from needrom site) 5.0 stock rom and reflashing the original kitkat stock rom.
I need to repartition the phone storage , when i boot it appears only 4.0 Gbyte storage for programs , but no internal storage.
How can i repartition the internal storage?
Thank you
Click to expand...
Click to collapse
There are some instructions on the Z7 mini thread here on XDA. Have a search & follow the instructions
Unbrick Z7 max
mightymaki said:
There are some instructions on the Z7 mini thread here on XDA. Have a search & follow the instructions
Click to expand...
Click to collapse
Thank you but i did not find anything relevant by searching
[email protected] said:
Thank you but i did not find anything relevant by searching
Click to expand...
Click to collapse
You can follow this thread: http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini.html
use google translate.
I am going to post a guide in English in about 2 hours. I have bricked mine and I followed the procedure from androidiani.
Guide to unbrick ZTE Nubia Z7 Mini
I have done this procedure on my device without any problem after a repartition failure, but I am not responsible about anything happens to your device (which is already bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
- Windows XP https://mega.co.nz/#!30I1yLRD!kLblCqP9_LmiOXjpfzGbFL7m2zqAqKqZ8ciPFWMBDB0
- Windows 7 http://www.sabrent.com/support/knowledgebase.php?article=14
- Windows 8 http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Nubia Toolstudio , and Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Hi Stratos,
i was able bevor to google translate the italian text an d using the screenshots avaliable there i was able to flash the Nubia 7 MAX
software. BUT no imeis are in the Phone so now i have to find a method to type the IMEI numbers in the Phone dont know how..
I tried to create a flashable zip (as suggested by nano7mobile.blogspot) but did not work maybe becuase i dont know
the IMEI Folder location inside the Phone..
Simos
previously after bricked zte z7 max, can flash with ToolStudio : http://www.needrom.com/download/z7-max-2-13-android-5-beta_eng_chi/ (file: NX505J_CNCommon_V2.13.tar)
voila, phone revive.. thankyou..
Another Problem is Appear..
Imei,Meid, is gone.
i backup imei (blank) with Qpst, generate name: blank_imei.QCN ( ^^)
edit my own file : blank_imei..QCN (with blank imei,meid,esn)
the file is about 141 KB.
i open with hexa editor, feel confuse, don't know where to start, don't know the location of imei,meid,esn.
i don't know where "offset" position to be edit.
i google around,
i think need file : *.QCN from someone z7 max backup, to determine the position of imei,meid,esn. (cmiiw)
can someone help me, provide backup of Z7 Max *.QCN file?
i will Surely change it with hexa editor, edit it with my own imei,meid,esn.
or there is another way to fix this imei-meid-esn problem?
please help...
best regard's
stratos_21 said:
I have done this procedure on my device without any problem after a repartition failure, but I am not responsible about anything happens to your device (which is already bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
- Windows XP https://mega.co.nz/#!30I1yLRD!kLblCqP9_LmiOXjpfzGbFL7m2zqAqKqZ8ciPFWMBDB0
- Windows 7 http://www.sabrent.com/support/knowledgebase.php?article=14
- Windows 8 http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Nubia Toolstudio , and Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Click to expand...
Click to collapse
I bricked it yesterday trying to downgrade from cm12.1 to Official nubia 3.01. Yesterday it showed up as QHUSB_BULK, but now it shows up as android cd rom drive and I can't do anything with it. Currently it will boot into the nubia recovery and it will charge, I can't enable it as mass storage device . I can see that all my files are there through the recovery but I can't gain access to them. Will it let me flash from External USB micro sd card as I am about to go buy one? If I turn it on it goes straight into nubia recovery and when I have it off it charges.
When you said 1.28 did you mean Official 1.82? The 1.82 did not work for me as I had an official 1.82 already downloaded. The file you linked I could not download due to poor connection. I was able to install Nubia 3.01 but I think I lost my imei because it says no sim detected. Fortunately, I do have an efs backup from HC-kTool - will I be able to restore that? Also all of this began as I went straight to V3.01 instead of V2.03, first . And then I went to cm12.1 which was extremely buggy so I try to downgrade to official v3.01 and then to Kitkat 4.4.4 v1.82 when something happened to the pc and phone lost connection during the downgrade.
What should I do next? I currently am on Lollipop 3.01 with no radios, baseband etc. My blue-tooth and wi-fi are working. Should I try to restore my efs.img I backed up with HC-kTool?
next4nextel said:
I bricked it yesterday trying to downgrade from cm12.1 to Official nubia 3.01. Yesterday it showed up as QHUSB_BULK, but now it shows up as android cd rom drive and I can't do anything with it. Currently it will boot into the nubia recovery and it will charge, I can't enable it as mass storage device . I can see that all my files are there through the recovery but I can't gain access to them. Will it let me flash from External USB micro sd card as I am about to go buy one? If I turn it on it goes straight into nubia recovery and when I have it oharges.
Click to expand...
Click to collapse
I'm in a similar situation with mine, self inflicted of course while I was trying to get the phone rooted with 3.01.
Anyway where it is now I can still boot to a point and I still have the Nubia recovery util fully functional. If you go into that and look under 'other' you will see that you have the ability to enable mass storage from there and yes you have the option of updating via SD,internal and OTG via the recovery util.
For me though unless I want to get nasty and do things from scratch it looks like I can only carry out an update using an official Nubia file and not just a recovery nor an earlier or current version of stock firmware which is kind of weird. And yes you have the option of updating via the SD,internal and OTG via the recovery util.
Thanks Parso, fortunately I followed the above steps and I restored to official 5.0. but then I lost my imei and had to sort that out. I actually like the official 5.0 except for 2 bugs one where I can't see the WiFi icon on the status bar unless I'm connected to Wi-Fi. And the other is sometimes when I get a call the screen never lights up and I can't swipe to answer the calls which is really annoying because I have to call them back.
I have the same situation right now.I upgraded my z7max 1.64 to 3.09.then I tried cm12 but there were so many problems with mobile data.
So I decided to change it.It was a big mistake to go back to 1.64 without reading anything.In the end it stopped working after a few trys.
Anyway I managed to enter toolstudio 4.6 and show it at por as com13 .Then I watched steps and flashed 3.09 to phone.It seemed like succesfull but it wasnt.Now it s not reacting and all black screen.
Also when I connected it to computer again at the beginning it was QHUSB_BULK with yellow sign.Then I tried to install Qualcomm CDMA Technologies MSM to set it up.Now it became worse.When I connect my phone it s written "unidentifed device" on device manager.
I guess we re missing one thing.For example this "Qualcomm CDMA Technologies MSM" or qhsusb驱动 folders are for XP, Vista or 7. I m using windows 8 right now and I think these files are not suitible as drivers.
So my phone is dead now.If I can set drivers up I guess I can fix it.But I cant find any other drivers and that s the biggest problem.
Hi everyone,
My feedback, After try CM12.1 i decided to return at android 4.4 and for that i used nubia updated tools and nubia studio.
After flash, no imei and only USA Band.
After restored my NV backup 1 IMEI of 2 come back ?!, After restore my
NV Value (values from opo guide, because NV Calculator give me a bad number ?) all band done USA, ENRO, JAPAN etc ...
BUT the phone lock/unlock (after enter my lock pin) every 5 secondes ?
Please help me, i have no ideas
buzz-27 said:
Hi everyone,
My feedback, After try CM12.1 i decided to return at android 4.4 and for that i used nubia updated tools and nubia studio.
After flash, no imei and only USA Band.
After restored my NV backup 1 IMEI of 2 come back ?!, After restore my
NV Value (values from opo guide, because NV Calculator give me a bad number ?) all band done USA, ENRO, JAPAN etc ...
BUT the phone lock/unlock (after enter my lock pin) every 5 secondes ?
Please help me, i have no ideas
Click to expand...
Click to collapse
For all those who are facing issues unbricking the phone as given above, use these Qualcomm drivers (5th post from top)
http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/page__st__40
Point to these drivers from Device manager (QHUSB_BULK). Your device should be identified correctly. Also follow the same steps exactly as given earlier. I managed to unbrick with completely working phone & IMEI.
If anyone is intersted in reading why Qualcomm devices cannot be bricked completely, read the links given below in 2 parts
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/
http://www.androidbrick.com/unbrick...oader-9008-if-you-have-the-right-kind-of-rom/
next4nextel said:
Thanks Parso, fortunately I followed the above steps and I restored to official 5.0. but then I lost my imei and had to sort that out. I actually like the official 5.0 except for 2 bugs one where I can't see the WiFi icon on the status bar unless I'm connected to Wi-Fi. And the other is sometimes when I get a call the screen never lights up and I can't swipe to answer the calls which is really annoying because I have to call them back.
Click to expand...
Click to collapse
Hello,
COuld you please tell me how you solved the problem, cause all imei and meid are:null
Please someone help me fix the imei problem, i have my imei nr's on the box, but i did not do a back-up.
Thank you
zte z7 mini
hi bad rom update and can not get back into recovey have looked at the posts but drivers link down and when i get Nubia Toolstudio i downloade 3 times put needs password ??? any help please i am runing on windows 10 64bit and win 7 32 bit if some can help on here or mail me on [email protected] going mad with this
Hi, this is my first post here. XDA-forums are great and I think here is the place where you would help me to solve the problem with my phone Nubia z7max.
The problem is that after a software (ROM) update in recovery TWRP from the stock 3.22 to Mokee (android 6 ) , the phone remained on logo "Nubia powered by Android". I have read probably everything written about that problem in all possible places that I found around the internet including Chinese NUBIA forum, Androidiani, 4PdA and so on. I followed all the steps which incidentally are the same everywhere for fixing the phone:
http://forum.xda-developers.com/zte-z7/general/unbrick-nubia-z7-mini-t3006268/page2
stratos_21 said:
I have done this procedure on my device without any problem after a repartition failure,
but I am not responsible about anything happens to your device (which is already
bricked...)
The source is http://www.androidiani.com/forum/zte-nubia-z7/446548-guida-di-unbrick-z7-max-mini-27.html
1) We disable driver signature verification for windows.
2) We download the drivers, which we extract in our desktop.
3) We connect the device while switched off to PC via a USB 2.0 port, and we launch Windows device manager. We press simultaneously Vol +/Vol -/Power button for ~5 seconds. We should see our device identified as QHUSB_BULK under Ports section in device manager. If we get prompted to format several drives we cancel all of the actions.
4) We right-click at device QHUSB_BULK > Update Driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have disk > Browse, and we open Nuova cartella folder which we have extracted, containing the drivers.
We choose the driver named Qualcomm HS-USB QDloader 9008 and we install it.
We can see our device now identified with that name in the device manager.
5) We download Z7 mini files.
We extract them inside a folder in our desktop, and we run toolstudio as administrators, disabling our anti-virus, or putting the program to its' exceptions because it will be detected as malware.
In the prompt which will pop-up requiring a password, we enter the e-mail address found at the .txt file.
6) We select eMMC Download, we refresh and we should see our device identified like this.
7) We select browse, and we select the folder nx507J_files containing the Z7 mini files.
8) We select start all, and we wait until the procedure finishes.
The whole process has ended, we unplug our device and we can boot it. We will be with stock rom 1.28
Click to expand...
Click to collapse
The difference in my case is that the procedure for flashing have completed with no errors and the phone restarts and it is in the same condition without any change: the logo "NUBIA powered by Android".
I tried to maybe over 10 different drivers. The phone is detected by the computer as it should be. When downloading the ROM in to the phone with ToolStudio_4.6 or NX505J Nubia Tool V2.1.0, procedure runs without any problems but the result is the same. There is no possibility to enter into recovery, I was TWRP and accordingly have a backup made in TWRP ahead of time when my phone is working normally.
With the combination Vol+, Vol- & Power pressed together for about 7-8 seconds the phone is recognized by the computer as HSUSB_Bulk and a cuple of disc drives with a different volume. Drivers are installed correctly although hardware is 19d2 and the phone is recognized as Qualcomm HS-USB QDLoader 9008 (COM XX).
With the combination Vol+ & Power pressed together for about 7-8 seconds the phone is recognized as Android ADB Interface, on screen are Nubia logo. In this kind I can charge (at least visibly) TWRP through "Z7_Max_All_In_One_Tool_Created_By_Tigreos" (NeedRom), but after that I can not go into Recovery. With the same tool I can install stock recovery too but still can not login to recovery.
The biggest success I've achieved after many attempts, two weeks from now, are to initial animation pictures and melody at startup and phone suddenly goes off.
Pleace Help
The definite guide to rooting Samsung Galaxy J3(2016) SM-J320FN & FRP Locked Bootloop
As first I have to say, I had to create a thread in Q&A because of the low rank, but I am sure this can be moved to the J3 section as there are many questions on how to gain root access to this device. This guide can work on the SM-J320F model as well, but it hasn't been tested on other models, so don't try it !
Lets start :
Dont forget to Backup all your data before the process !!!
1. Tick USB Debugging and OEM Unlock in Developer Mode (OEM has to be ticked to unlock the bootloader)
2. Connect to PC with USB Cable and open Odin
3. Power off and reboot into Download Mode (VOL.DOWN+HOME+POWER)
4. Add twrp.zip to AP tab
5. Untick Auto-Reboot and Start
6. Wait to finish
7. When it's finished hold (VOL.DOWN+VOL.UP+HOME+POWER) to Power Off
8. Load into TWRP Mode (VOL.UP+HOME+POWER)
9. In TWRP first go to the Wipe Tab, check Cache and Data and click Wipe
10. Copy SuperSU into internal memory from your PC
11. Go back to TWRP and select Install, select the SuperSU from the internal memory and click install without ticking anything, then reboot
12. Wait for the phone to reboot, it may boot-loop a few times, and it boots slowly but dont interrupt the process !
13. From there on, check the root status by downloading Root Checker from PlayStore
KEEP OEM-UNLOCK ON ALL THE TIME, IF YOU DONT WANNA END UP WITH A BRICKED DEVICE(CUSTOM BINARY WAS BLOCKED BY FRP LOCK)!!!
If that happens, here is an official guide from the Samsung Kies Support Page :
IMPORTANT: You may need your device model name, S/N number, or IMEI number in order to proceed. This information can be found on the label underneath your device battery.
WARNING: This process permanently deletes all personal information from the device. The information will not be recoverable if you proceed with this process.
1. Open Kies 3 and click Tools > Firmware Upgrade and Initialization.
2. Enter your device Model name and click OK.
3. Enter the device S / N number and click OK.
4. Kies 3 will verify that the feature is available for your device. If the feature is available, click OK to continue.
5. The firmware version is displayed along with a note that the information on your device will be permanently deleted during this process. Click OK to continue.
6. Follow the steps to prepare your device for emergency recovery. Mark the checkbox next to I have read all of the above information. Select whether you agree to share this update with Samsung. Connect your device to Kies when you have activated the download mode. When your device is in download mode and connected to Kies 3, the Start upgrade button is available. Click Start upgrade to reinstall the firmware.
7. Touch Create backup to create a copy of selected items before proceeding. Touch Skip backup to proceed without backing up any items.
8. Kies 3 will download and prepare your system to update the firmware. This process can take some time. The time will vary based on your network and computer capabilities.
9. Respond to any security warnings about installing software.
10. The progress screen is shown during the upgrade process. The process will take several minutes to complete. Do not disconnect your device, turn the device off, or turn off your computer during this process.
11. Click OK when the upgrade is finished.
Therefore I provide you all the needed files to do this :
How to root SM-J320FN.rar
Works like a charm on J320FN.
I signed up just to say, after hours of trying different guides, accidentally factory resetting once or twice, and getting my phone stuck in a boot loop, this method worked. BUT it did factory reset my phone, but that's fine I've everything backed up and it wont take long to get it back. Maybe I pressed something I shouldn't have.
Some info on my phone in case it helps anyone in a similar position to how I was:
At one point I installed stock firmware from to get my phone out of the boot loop, I can't link it but if you google "J320FNXXU0APB4_J320FNO2C0APC1_O2C" (WITH quotes) you should find the page.
After doing that:
Android version: 5.1.1
Model number: SM-J320FN
Kernel version: 3.10.65-7225942 (Sun Feb 14 2016)
Build no: LMY47V.J320FNXXU0APB4
Baseband version: J320FNXXU0APB5
I hope I typed all that right. Thank you so much!!
have anyone tried on j320v?
kekambas18 said:
have anyone tried on j320v?
Click to expand...
Click to collapse
Going to attempt that right now wish me luck.
---------- Post added at 08:06 PM ---------- Previous post was at 07:09 PM ----------
And it didn't work. Not suprised, but I at least tried.
GN9166 said:
4. Add twrp.zip to AP tab
10. Copy SuperSU into internal memory from your PC
Click to expand...
Click to collapse
Hey, why this guide doesn't mention that I have to download something. It's definitely NOT definitive! What is twrp.zip? Where do I take it from? What is AP tab? Where exactly do I copy SuperSU? What will happen in the download mode?
Problems in Root J320AZ
My name is Dario Lobos. I am working as a gardener and I am making a little application in my phone. I don't have computer so I did it in Java n-ide. I started with a Samsung core prime but the screen was broken and I did change it and the technicians broke it and gave me an Samsung s320. Android 6 (api23) and after that the java n-ide don't compiles the permits that I am requesting in the manifest so I can't grant permissions to my apk. Parallel of it the phone always show a notice unauthorized actions have been made please restart the phone to undo the unauthorized actions. And the lookout said message root access detected. I wrote Samsung without any positive answer. No technical assistance at all. But the roots checkers says that I have no root in my phone. Now I am trying to do a root. But I don't know if someone have a hidden root access in my phone. A page suggest Framaroot and you suggest kingroot. I don't want to store all my phone in their server to root it. Does any program that don't access to all the data to root the phone?. I am writing you since you have more experience to request you if it is in your possibilities. Also to ask you about prompt root commands. Where I can find info about that. A suggestion to solve my problem. My simple all is here
....github.com/DarioLobos/sistemariego
....github.com/tranleduy2000/javaide/issues/163
....1drv.ms/u/s!Asr3Ewn45KOLtGOqDkoMq20A-hbc?e=24Wwx3
The system don't let me put url since I am new add please http...
Well thank you in advance and any help is wellcome
Regards,
Dario Lobos
Adding more information to what I did to try to find a an answer. I tried to root with Frama root 1.9.3 and the installation only request me access to the camera and after installed the programs showed a banner that said can't root your device.
Today I downloaded from firmware.mobi some zip and img files but I already I couldn't learn how to use them properly.
I am trying to avoid the exploids system because maybe is a hacker in the middle. Always I am trying to root w/o SIM card and with Wi-Fi off. So I think that kingroot and kingoroot are not useful for my.
I am trying to buy an old desktop computer as an alternative.
Well any suggestion is usefull and wellcome.
Before of all of that I did two factory reset in recovery mode.
Then I installed an apk Dev Tools (trinea) and one menu request me developer permit in accesibility setting. The phone started to change the color of the screen and the outside padding start to flashing red. Then was open a setting menu and the language was changed suddenly to Japanese or Korean while the screen was lighting like receiving knoks. I turned of the phone and restarted and hopefully I remembered the position in settings to change the language.
After that I had to use an apk repair system and fix Android and the screen get better but the padding outside still flashing in red ones in a while.
Also where added plenty sha certificates (settings user certificates) like system certificates
Go daddy
VeriSign
Some governments (Turkish, Spain, Japan, Germany, Holland, and more)
The Catholic religion with 6 certificates called
Quo Basis
And much more.
So I did another factory reset recovery mode. And the screen problem disappeared and the certificates that I turned off manually firt too (All) but the root alert in the look out and the security notice didn't disappeared.
Today I wanted to print your forum page and the phone put error. Only put error in your forum page.
Other thing that I had to to just after the unpackage the restored Android is disable the setup and transfer. Because I think that is this apk that were using to access and modify my files and grants permissions.
I installed the TWRP application but said the phone have no root.
Today I opened the developer option in settings and turned to on the OEM option to unlock the boot loader but instead of put a banner saying that all data will be erased put a banner saying that the device protection will be not work and didn't do the reboot or nothing more that put this dialog.
Dario Lobos
great, unlocken/rooten worked here. But after that, the mobile became unusable. All google apps complain no connection is available. I cannot update google play store, cannot update other google apps like youtube, or install any app now.
And perhaps it does not have anything to do with the mentioned process, but before I started the process, I made sure all nessacary file were on the sd card. But now I have finished wiping the data / cache from the recovery and all files on the sd card are gone.
I cannot login to google photos to see if the apps are backupped because every google app complains no internet connection is available.
So yes, rooting/unlocking worked, but that's the only thing that worked here. I now got a useless Samsung J3 2016...
I need assistant trying to root my J320FN, which I mistakenly wipe some backed up recovery file now, I can not get through with the rooting and I can get back to forma phone setting am locked up , samsung phone not coming up again please what can I do ?
GN9166 said:
The definite guide to rooting Samsung Galaxy J3(2016) SM-J320FN & FRP Locked Bootloop
As first I have to say, I had to create a thread in Q&A because of the low rank, but I am sure this can be moved to the J3 section as there are many questions on how to gain root access to this device. This guide can work on the SM-J320F model as well, but it hasn't been tested on other models, so don't try it !
Lets start :
Dont forget to Backup all your data before the process !!!
1. Tick USB Debugging and OEM Unlock in Developer Mode (OEM has to be ticked to unlock the bootloader)
2. Connect to PC with USB Cable and open Odin
3. Power off and reboot into Download Mode (VOL.DOWN+HOME+POWER)
4. Add twrp.zip to AP tab
5. Untick Auto-Reboot and Start
6. Wait to finish
7. When it's finished hold (VOL.DOWN+VOL.UP+HOME+POWER) to Power Off
8. Load into TWRP Mode (VOL.UP+HOME+POWER)
9. In TWRP first go to the Wipe Tab, check Cache and Data and click Wipe
10. Copy SuperSU into internal memory from your PC
11. Go back to TWRP and select Install, select the SuperSU from the internal memory and click install without ticking anything, then reboot
12. Wait for the phone to reboot, it may boot-loop a few times, and it boots slowly but dont interrupt the process !
13. From there on, check the root status by downloading Root Checker from PlayStore
KEEP OEM-UNLOCK ON ALL THE TIME, IF YOU DONT WANNA END UP WITH A BRICKED DEVICE(CUSTOM BINARY WAS BLOCKED BY FRP LOCK)!!!
If that happens, here is an official guide from the Samsung Kies Support Page :
IMPORTANT: You may need your device model name, S/N number, or IMEI number in order to proceed. This information can be found on the label underneath your device battery.
WARNING: This process permanently deletes all personal information from the device. The information will not be recoverable if you proceed with this process.
1. Open Kies 3 and click Tools > Firmware Upgrade and Initialization.
2. Enter your device Model name and click OK.
3. Enter the device S / N number and click OK.
4. Kies 3 will verify that the feature is available for your device. If the feature is available, click OK to continue.
5. The firmware version is displayed along with a note that the information on your device will be permanently deleted during this process. Click OK to continue.
6. Follow the steps to prepare your device for emergency recovery. Mark the checkbox next to I have read all of the above information. Select whether you agree to share this update with Samsung. Connect your device to Kies when you have activated the download mode. When your device is in download mode and connected to Kies 3, the Start upgrade button is available. Click Start upgrade to reinstall the firmware.
7. Touch Create backup to create a copy of selected items before proceeding. Touch Skip backup to proceed without backing up any items.
8. Kies 3 will download and prepare your system to update the firmware. This process can take some time. The time will vary based on your network and computer capabilities.
9. Respond to any security warnings about installing software.
10. The progress screen is shown during the upgrade process. The process will take several minutes to complete. Do not disconnect your device, turn the device off, or turn off your computer during this process.
11. Click OK when the upgrade is finished.
Therefore I provide you all the needed files to do this :
How to root SM-J320FN.rar
Click to expand...
Click to collapse
The link says "the key is invalid"
Hello guys,
I have come many times here to root my phone and I did success, thanks to you.
But now there is a new problem and I did not find any solution, then I will try to explain with my bad english what I did :
At first I tried to flash TWRP (an unofficial one many said it was working) on the phone after unlocking the bootloader, SP flash tool said it was successful.
But it was not, after reboot former recovery was still there, not TWRP (does anyone knows why it did not work ?).
I tried to install Lineage, which bricked my phone. After the debrick, I installed Android 10 GSI, and it worked but impossible to use MTP, Bluetooth or to download with the HTMLViewer (in other words, the system was unusable).
Then I reinstalled the ROM provided by Blackview, and installed Magisk, rooted the phone, also suppressing all the Google stuff it was possible.
And there is the main problem : I think I erased the NVRAM while unbricking the phone and then I have got an overlay of red chinese caracters on the corner of the screen. I tried to replace the original IMEI and MEID successfully with MAUI Meta, but chinese caracters are remaining here.
A screenshot of the ugly writings : https ://ibb.co/bWWp1wr
My phone is a Blackview BV9500 Plus.
Any suggestion about how to remove them ?
Thanks in advance !
I have just tried to replace the BT/Wifi adresses with SN Writer.
The soft said it was a success, but in the system parameters of the phone these adresses were not modified. I wonder why...
I guess these adresses (and/or the serial number, in others words all the parameters of the NVRAM) are the causes of the message. What do you think about that ?
Also, in the official firmware, there are some files for only one choice for the AP and MD databases (what are the correct ones ?).
I think I almost tried everything I am able to do...
Any suggestion or solution ?
Thanks
John Manjiro said:
I have just tried to replace the BT/Wifi adresses with SN Writer.
The soft said it was a success, but in the system parameters of the phone these adresses were not modified. I wonder why...
I guess these adresses (and/or the serial number, in others words all the parameters of the NVRAM) are the causes of the message. What do you think about that ?
Also, in the official firmware, there are some files for only one choice for the AP and MD databases (what are the correct ones ?).
I think I almost tried everything I am able to do...
Any suggestion or solution ?
Thanks
Click to expand...
Click to collapse
Hi John, same issue here, but not same process. Phone won't boot so I've restored which made IMEIs being 111111 and 22222. Used MetaModem (successor of AMUI Meta or whatever you used is called) to restore correct IMEIs. But got those red "TEE" and "Google" followed by Chinese chars. Will keep you updated here if I can find a solution.
@John Manjiro
It seem's Trusted Execution Environment (TEE) for Android is installed on your phone. It's a secure Operating System (OS) what runs in parallel to Android OS. TEE protects phone from malicious apps installed by the user and potential vulnerabilities that may be discovered in Android.
Did you ever find a solution to this?
huafu said:
Hi John, same issue here, but not same process. Phone won't boot so I've restored which made IMEIs being 111111 and 22222. Used MetaModem (successor of AMUI Meta or whatever you used is called) to restore correct IMEIs. But got those red "TEE" and "Google" followed by Chinese chars. Will keep you updated here if I can find a solution.
Click to expand...
Click to collapse
I'm having the same issues with a BV9800 Pro.
cnorman27 said:
I'm having the same issues with a BV9800 Pro.
Click to expand...
Click to collapse
Still same issue, got a long email thread with BlackView team which tried to help even tho they seem to not get well my Enlgish. They keep giving me a version of SNWritter where I had to modify some ini file in some tee subfolder. But the exe couldn't launch and was complaining about MVC100.dll missing. I could fix that by downloading from the web a SNWritter tool with working exe. Now I need to find some special screwdriver so that I can remove the battery from the phone. Doing so will keep the phone appearing as MT65XX Preloader in the devices manager and not for only one second...
Just FYI, I gave up and was using it with this **** red overlay.
Last week I was really bored of this overlay so I've installed AOSP 10 GSI. Tho it doesn't pass safety net, and believe me I've tried many way to make it pass. So I cannot use most of my banking apps + no google pay :-(
I even tried with AOSP 9, 10 and 11, as well as LineageOS 15, 17 and 18... unable to pass safety net even with universal safety net fix, magiskhidepropsconf, ...
Hahaha, looks like I just needed to write the previous post and finally got it wokring on PixelExperience Android 10 rooted and passing SafetyNet!!!!
Quick howto if someone is interested:
with SPFlashTools, restore the original ROM
Activate developer mode + USB debug
on the computer, adb reboot bootloader
Download PixelExperience system image and extract it (on linux with unxz) - I've tried many other ROMs with no success. Also while the device is not an A/B, you must download A/B images else they do not work.
fastboot -w && sleep 1 && fastboot flash system path/to/downloaded/system.img && fastboot reboot
Skip everything you can skip at first boot (you can restore later from an online backup or another android phone)
Download MagiskManager apk
adb push path/to/MagiskManager.apk /sdcard/download/
On the phone go in the file manager in download folder and install MagiskManager
copy the boot-signed.img from stock ROM on the device adb push path/to/boot-signed.img /sdcard/download
Open Magisk Manager, install, uncheck the first checkbox (to disable encryption, I forgot the exact label) but keep "recovery mode" checked, then click on next, then second option (patch boot image) and select the boot-signed.img you uploaded on step 10
download on your computed the patched image using adb pull
adb reboot bootloader
fastboot flash boot path/to/downloaded/patched-boot-magisk.img
You need to reboot in recovery mode, this is important: press power and volume up until you see the Blackview logo (can take up to 40 seconds)
select "reboot" (first option) in the recovery mode
once rebooted, open magisk manager, activate magisk hide and go in plugins.
install MagiskHideProps Config but do not reboot yet
install SafetyNet fix (download from here, it's not in online modules)
click on reboot
It'll reboot in recovery, that is normal and you MUST boot your device into recovery each time you need to boot/reboot it. Once in recovery, as before select reboot
Once it has rebooted, go in magisk and change in the settings so that the default method is not "prompt" but "grant".
from your computer:
adb shell
su
props
Select device fingerprint, then choose from certified, google, pixel 2, android 10
confirm but do not reboot when asked, simply exit
adb reboot recovery
again, select "reboot system"
Once booted, open Magisk Manager, click SafetyNet, it should pass SafetyNet.
Scroll down notification, and choose "continue device setup"
continue as normal the setup of the bv9500 plus!