Database Users

Free Unlock For I9000 - I897 - T959 To All Users

I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone

I9000 drivers
I9000 drivers

This solution is is not working for me. The problem is that the Update.zip says:
E: Signature verfication failed
Installation aborted
Any advice? How to install that update.zip package?

cellularhut said:
I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
Click to expand...
Click to collapse
Fantastic find if it works, my phone is unlocked so I can't test it but thanks a lot for sharing!!! Priceless
N.B. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.

tyxerakias said:
fantastic find if it works, my phone is unlocked so i can't test it but thanks a lot for sharing!!! Priceless
n.b. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
Click to expand...
Click to collapse
1000000000000000% working tested before post here !!!!!

I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks

erreterr said:
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
Click to expand...
Click to collapse
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.

The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Tyxerakias said:
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
Click to expand...
Click to collapse

No idea. Have you rooted your phone already? Have you installed any mods or firmwares?

No need to root
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.

So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks

knkartha said:
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
Click to expand...
Click to collapse
Huh. Interesting. I would have thought /efs is a protected folder.

I have a Bell one, i asked their staff when i bought my phone if i still on WARRANTY when i unlock the phone by Bell, they said yes.
Anybody know if i will lose my phone WARRANTY after i unlock the phone? Or can i lock it back if my phone have any problem in the future?
Thanks

could somebody point out which value in the address 00181460 says the unlock code?

erreterr said:
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Click to expand...
Click to collapse
you should put the update.zip file on your internal sd card directory.
i encountered the same error when i put the update.zip file in the external sd card

erreterr said:
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
Click to expand...
Click to collapse
which of the values in the said address gives the unlock code?

Hi,
I have a NSPRO box and read the unlock code, but as I insert it, it doesn't unlock the phone.
As this didn't work, I tried your method, and the code that showes up is the same as read by NSPRO box, and... it still doesn't work.
Attached is the printscreen of the HEX area where the code is. I've noticed it says "18146D" and not "181460" as your indicated. Could this be the reason why the code doesn't work?
Please help...

Samsung Vibrant SGH-T959 Recovery Mode
I've tried all sorts of button combinations to get the Samsung Vibrant T959 into recovery mode. I think since this device is a T-Mobile phone, the firmware has been modified for VolUp+VolDn+Pwr recovery mode.
As of now, the only way I know how to get the phone into recovery mode is by using the Android SDK and sending off a command: adb reboot recovery
I've been putting together an Android SDK & Rooting tutorial as well as other Samsung Vibrant T959 findings here: jordanpeterson.me/content/t-mobile-samsung-vibrant-sgh-t959
Sorry.. the external references aren't working.. Good spam rules on new users.
Thanks
Jordan

It worked great, althoug the address on my I9000 was 00181462. My suggestion is try to find closest address to the given by the tuturial....
Thanks for everything

Don't need to root the device. Download terminal emulater from Market. Went straight to step 10. Works like a charm. Thanks for the instructions.
Sent from my GT-I9000M using XDA App

[Q] is there a custom recovery that will work for me

My phone settings
firmware version 2.1-update 1
baseband 63.18.55.06PU_6.35.15.14
KERNEL VERSION 2.6.29-36D5CB8D
[email protected] #1
build number 3.35.61.2 cl196735 release-keys
software number 3.35.61.2 browser version webkit 3.1
I have been wanting to install a custom rom on my phone for several months now however no matter what method i try i am unsuccesful closest i have come is using rom manager which allows me to reboot into recovery but once the handset has rebooted home screen and power button just gets me to the triangle on screen and i have to remove battery. all flash recorder methods fail at either back up recovery
or writing flash.
I believe my phone is rooted as i can grant su to rom manager ect and androot tells me i am rooted it is like something resets recovery every time the handset boots into os.
i really have tried every method i have found but dare not try and install anything for fear of recovery not being available to me and i am now wondering if the 2.1 update has blocked something.
please help willing to make donation to any devs that can help me through this as well as the countless others having the same problem

there was one thread here .. try to search it i forget link it can explain you how to root official 2.1 otherwise run RUU & Do downgrade

according to all the programmes i run to check status of root (latest one is under the hood) it lists
Device: htc_hero hero
Root Status: Device routed
ro. build fingerprint: orange_uk/htc_hero/hero/hero:2.1-update1/ERE27/196735:user/release-keys
every programme that requires root access works for me tho i do have to grant it every time for programmes , the clockwork recovery has to be reflashed if phone has been restarted to enable me to access the recovery, and when i do this su pops up telling me it has been granted.

1 method i tried but never got past step backup recovery was this but i get message backup failed could not run command
"HTC Hero Custom Recovery
Step 1:
It's advisable to format the SD Card before do this process. You're going to lose all the information in the SD Card, do a manual backup to your computer of whatever you want, to do it:
Settings -> SD Card & phone storage -> Unmount SD card -> Format SD card
Step 2:
Download the flashrec from http://code.google.com/p/flashrec/
Download the recovery image provided by Paul from http://www.romraid.com/paul/hero/1.2-hero-recovery.zip
Extract the 1.2-hero-recovery.zip to your PC.
Step 3:
Now copy flashrec and recovery-RA-hero-v1.5.2.img (wich is inside the .zip file) directly to your SD card
Step 4:
Use an app installer from Google Market to install flashrec, i used ASTRO, but can be any other.
Step 5:
Once installed, open the program, click the button "Backup Recovery Image" and wait to finish, shouldn't take much time, this will do a backup of your actual recovery and put it in your SDCard with the name recovery-backup.img.

brisuth said:
My phone settings
firmware version 2.1-update 1
baseband 63.18.55.06PU_6.35.15.14
KERNEL VERSION 2.6.29-36D5CB8D
[email protected] #1
build number 3.35.61.2 cl196735 release-keys
software number 3.35.61.2 browser version webkit 3.1
I have been wanting to install a custom rom on my phone for several months now however no matter what method i try i am unsuccesful closest i have come is using rom manager which allows me to reboot into recovery but once the handset has rebooted home screen and power button just gets me to the triangle on screen and i have to remove battery. all flash recorder methods fail at either back up recovery
or writing flash.
I believe my phone is rooted as i can grant su to rom manager ect and androot tells me i am rooted it is like something resets recovery every time the handset boots into os.
i really have tried every method i have found but dare not try and install anything for fear of recovery not being available to me and i am now wondering if the 2.1 update has blocked something.
please help willing to make donation to any devs that can help me through this as well as the countless others having the same problem
Click to expand...
Click to collapse
You're absolutely right, the 2.1 update for the Hero installs a recovery rom reset, so whenever you boot up your phone normally, it reflashes it (or possibly checks that it's not the original and then flashes).
I don't quite remember where this was done anymore, it might have been a script in /system/bin that gets called from init(rc), called something like flash_recovery.sh. Perhaps someone who isn't running a custom rom could help out and pinpoint it for future reference (I am so not going back from cyanogen 6.0
Edit: I grabbed unyaffs and checked out my old nandroids, it's /system/etc/install-recovery.sh, comment out the line in it (add a # at the beginning of the line) and it will not clobber your custom recovery

i have located file but now i feel really stupid as have not got a clue what to edit it with i am assuming it would be some type of txt editor and if u could specify the line i need to edit out or is it the name of the file i am changing,
really am gratefull for you pointing this out i had guessed what was happening just could find nothing to confirm it.

brisuth said:
i have located file but now i feel really stupid as have not got a clue what to edit it with i am assuming it would be some type of txt editor and if u could specify the line i need to edit out or is it the name of the file i am changing,
really am gratefull for you pointing this out i had guessed what was happening just could find nothing to confirm it.
Click to expand...
Click to collapse
It might need to be a text editor that knows not to break unix line endings, but you can copy the file (cat file > /path/to/destination/file) to your sdcard or use adb to pull the file... fairly straightforward I thought.

A big thankyou to duck0 for identifying the problem and botoo for getting me to a happy conclusion with the correct commands
SOLUTION IS HERE USING Console mode from windows using ADB USB DEBUGGING HAS TO BE ENABLED WITH HERO CONNECTED TO PC THEN TYPE THE FOLLOWING
THEN ENTER AFTER EACH COMMAND
anyone needing help setting up adb see this link http://forum.xda-developers.com/showthread.php?t=757233
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
Thats it all done next step
INSTALL ROM MANAGER FROM MARKET IT IS FREE
open it and sellect flash alternate recovery image from the bottom, you can use the clockwork recovery but it is not compattable with all roms.
once done turn phone off, boot into recovery home + power choose to exit recovery with reboot shut down once again and if you can enter recovery then everything is sweet.

*UPDATED**UNLOCK TOOL (4-2019) for ALL Versions of BLU R1-HD

BLU R1-HD bootloader unlock script tool, and TWRP install tool.
Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat
The included files and folders are set to hidden, in effort to keep them safe from accidental delete.
Must have adb+fastboot + drivers installed and setup prior to using tool
Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"
LINK==>ADB+FASTBOOT
It is for windows
In linux :
"sudo apt-get install android-tools-adb"
"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"
"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)
Using Tool
On Windows?
Unzip the downloaded file to a new folder, open new
folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"
Do the steps in order (1-2-3-4) to be unlocked, then
Step (5) to get to second page where step (1) is root
The rest is optional
On Linux?
Unzip downloaded file to new folder folder .
Open folder. Then open R1-Linux-tool-v2 folder
Open terminal from that folder and type
" . R1-HD-TOOL.sh "
Same order of steps (1,2,3,4) step (5) for extra
Steps (1 on second menu) for superSU root.
Second menu steps (2,3,4,5,6,7,8) are optional.
**Linux Note**
The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.
The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize
this command. But "apt-get install fastboot" updated some version and then the command was recognized.
******OTHER NOTES****
--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----
--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"
--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.
CHANGE LOG
V1:. Initial release : removed
V2:. : fixed typos preventing proper function
V3:.: switch file verification to md5 check instead of "ls-l" comparison.
V4: current version: add extras page, add SU flash, de-bloat script, Added Fm Radio, Added pre-loader roll back
V5: Fixed wrong loop "goto" line that made preloader rollback do "MTK_BLU Debloat v2" instead
V6: Added manual pause to script for mods that need recovery (Extra's 5) . Added redundent recovery flash command .
Few reports of recovery "not Sticking" and needed to run the flash commands manually one by one. Maybe the redundent
flash will make it survive. If still having problem with recovery "staying install" try manually flashing
here is link to the steps needed. FLASH RECOVERY
V7 Improved logs Added line to make batch run as sub-process so if error occurs , will not close
V7.1 : Updated the fm radio install zip and include the needed selinux mode changer app
V8: fixed dependency of needing to be unzipped to location w/o spaces in name. (when used from location with spaces, tool used to fail to push needed files).
.. added more time to allow dirtycow to "spawn" its root shell. Recent testing has shown sometimes it takes longer than the 60 seconds allowed in the script. Now it is looped 3 times.
V9 Added full path to abd push lines for recovery flash files. included fastboot.exe file to address some version issue where user s version would not output text file I coded into script for a verification ( included file is called by script, no need to do anything different with it)
V10: Moved zip file to included folder to help preserve locations when unpacked, added device check before running tool; So tool not used on wrong device, Rearranged order of operations on extra's page. (recovery installed options) Push files while in android before rebooting to recovery( should improve reliability for multiple reports of not automatically installing options for some)
******I have received some reports that some devices are reporting "ro.build.product =R1_HD and not "BLU_R1_HD" like mine, so the added device check is blocking tool from starting If this happens to you , you can make edit to the .bat file like below.
Change this line
Code:
:next_check
find "BLU_R1_HD" "%~dp0workingproduct.txt"
To this
Code:
:next_check
find "R1_HD" "%~dp0workingproduct.txt"
it is line #23
V11: Updated device model verification lines
MTK-SU: Replaced all dirty-cow part with New MTK-SU binary(elf) from @diplomatic
source
Click to expand...
Click to collapse
Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.
DOWNLOAD LINK
Preferred to use the Downloads tab of this thread.
Archived downloads on android file host also == link
XDA:DevDB Information
R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD
Contributors
mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,
Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD
Version Information
Status: Testing
Current Stable Version: V11
Stable Release Date: 2017-04-11
Current Beta Version: MTK-SU
Beta Release Date: 2019-04-14
Created 2017-02-22
Last Updated 2019-04-18

Reserved
Items planed to be addressed in next release:
--Add few more file integrity checks to the extra's page
--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file
--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)
--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above
--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )
--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.

Reserved

Works great on OEM 6.6, thanks for the tool!

So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function

theredbaron1834 said:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
Click to expand...
Click to collapse
thank you for your input.
As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.
The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.
The lines with only 2 "::" are standard windows comment / remark line entries
The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for

Does Works to unlock 7.4.2?

khyr said:
Does Works to unlock 7.4.2?
Click to expand...
Click to collapse
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.
The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.

edit:
I have the linux version ready.
-the first step, (ADB Push) is ready. including md5 file checks
-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device
-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check
I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison
-step 4 is ready .--flash twrp
Finished 90% of tool.
still need to tweek the log feature.
I ran tests on the lop back to menu and test ran
1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass
2. run dirty cow commands and md5 verification on resulting file. ==pass
3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass
4 . flash twrp --installed both version i have, both install fine ===pass
5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass
(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)
6. instruction ====not written yet
7. exit yes it closes == pass
8. logs --- needs completeing

I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.

torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system

mrmazak said:
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
Click to expand...
Click to collapse
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.

OOPS
found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"
fixed and still reading and re-reading to search for errors.
This looks bad.
The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.
re-posted V5 combined with linux V2--

torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you

gabriel986 said:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
Click to expand...
Click to collapse
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.

mrmazak said:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
Click to expand...
Click to collapse
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
In case it's needed, my R1 HD is running on
BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38

gabriel986 said:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
Click to expand...
Click to collapse
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.

mrmazak said:
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
Click to expand...
Click to collapse
trying again....
for how long should I press the volume up key?

gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on

mrmazak said:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
Click to expand...
Click to collapse
ok.. trying again
---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
it beat me!
I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.

Huawei Nova Youth Problems

Hi Guys,
a german Forum advised me to ask here because, here are the experts. So sorry for my Basic englisch, but have a big problem.
My problem:
I got a Huawei Nova Youth as a gift. This is explicitly offered in the Chinese market. After some fumbling I have been able to change the language to German. However, the keyboard still partially takes false inputs. In addition, the Play and App store does not work. Of course, many other apps will be blocked, not to mention the Bloodware.
It is the model WAS-AL00. I now know that it is sold here as P10 lite. I did not find out how to install a European OS or a custom OS (Lineage). The support say only blah blah does not work, blah blah license problems ... Can someone please give useful information about my problem?
If more information is needed, I'll give it to you. I have always been Windows Phone users so far. So please apologizes if I do not understand all Android technical Terms.
thx

Hi, you need
backup alldata
unlock bootloader
install twrp
service rom: b182(ds) or b183(ss),
oeminfo: c432ds or ss
adb drivers
sdcard 8gb or more
links:
adb: https://forum.xda-developers.com/showthread.php?t=2588979
oeminfo: https://www.youtube.com/watch?v=I2DeM1pCcwo
service rom: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
twrp: https://forum.xda-developers.com/p10-lite/development/beta-t3619496
info:
imei: open settings, go to about phone and look if there one or two imei
oem unlock: press several times till enable in build number(developer settings), back to settings and open developer options scroll to see oem unlock and enable
twrp1: fastboot flash recovery recovery.img(open cmd c: )
sdcard1: create dload folder
insert sdcard:
servicerom: extract the download file, open folders untill you see update.app and folders, then copy all to dload folder in your sdcard
oeminfo: extract
twrp2: open twrp with vol+ + power, backup only oeminfo in sdcard(copy to safe place), then copy the downloaded oeminfo to the backup folder and replace oeminfo then press restore(dont reboot, poweroff only)
install: press vol+/- and power buttons untill update starts.

foliaje said:
Hi, you need
backup alldata
unlock bootloader
install twrp
service rom: b182(ds) or b183(ss),
oeminfo: c432ds or ss
adb drivers
sdcard 8gb or more
links:
adb: https://forum.xda-developers.com/showthread.php?t=2588979
oeminfo: https://www.youtube.com/watch?v=I2DeM1pCcwo
service rom: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
twrp: https://forum.xda-developers.com/p10-lite/development/beta-t3619496
info:
imei: open settings, go to about phone and look if there one or two imei
oem unlock: press several times till enable in build number(developer settings), back to settings and open developer options scroll to see oem unlock and enable
twrp1: fastboot flash recovery recovery.img(open cmd c: )
sdcard1: create dload folder
insert sdcard:
servicerom: extract the download file, open folders untill you see update.app and folders, then copy all to dload folder in your sdcard
oeminfo: extract
twrp2: open twrp with vol+ + power, backup only oeminfo in sdcard(copy to safe place), then copy the downloaded oeminfo to the backup folder and replace oeminfo then press restore(dont reboot, poweroff only)
install: press vol+/- and power buttons untill update starts.
Click to expand...
Click to collapse
I tryed to do this.
I entered the developer steeings. 2 points are not present oem unlock and root access are both not seen. I tryed to install app store for twrp but it is blocked. If I try to enter the fastboot option with restart from smartphone, it is blocked. So I think the main problem is to get twrp to load new image. I tryed to install the with apk file directly and via huawei store. Both was not possible. Any Idea? Backup is not necessary. I never worked with the smartphone.
Update:
It was possible to download me.twrp.twrpapp-26.apk and copy on phone. Now he ask for device. Is the P9 plus the best choise?

ok you need first unlock bootloader:
register here with your phone(faster with it) or with email: https://emui.huawei.com/en/plugin/unlock/detail
then:
1º Download serviceRom(b182 or b183) on your pc and extract it, Same thing for oeminfo c432(ds or ss) and twrp.
2º Once you get unlock code open cmd(type cd c: /users/yourname/adb(more or less)), type fastboot oem unlock code , press on the screen and reboot wait to finish.
3º Move twrp image(extract) to c:/adb, type fastboot flash recovery recovery.img, type fastboot reboot and press vol+ till erecovery screen, poweroff and unplug then vol+ and power button(briefly stop pressing power button)
4º insert your sdcard on laptop and create dload folder in it, then copy update.app and folders from dload folder of downloaded service rom.
5º in twrp press backup button select sdcard storage and backup only oeminfo(copy to safe place), with downloaded oeminfo copy and replace oeminfo then restore.
6ºpoweroff and unplug, then press vol+- and power button untill update starts, if all goes ok should reboot.

at first big thanks foliaje. I am very happy for your fast answers. I tryed today the unblock page from hauwei. There was foolowing Problem.
1. I registered an account via Smartphone. Most of informations was chinese.
2. Change lange was not possible - same in PC browser. Seems like fix Region.
3. delete account and create new on PC. Change language to german was possible.
4. Try to login to unblock Website was not possible - Change Password Shows failure Email or account not present ....
Is it necessary to great account on Smartphone with fixed Region again and use this account for unblock?
Further *adb devices* shows an ID and unautorised device. Is that right?

Kerberos79 said:
at first big thanks foliaje. I am very happy for your fast answers. I tryed today the unblock page from hauwei. There was foolowing Problem.
1. I registered an account via Smartphone. Most of informations was chinese.
2. Change lange was not possible - same in PC browser. Seems like fix Region.
3. delete account and create new on PC. Change language to german was possible.
4. Try to login to unblock Website was not possible - Change Password Shows failure Email or account not present ....
Is it necessary to great account on Smartphone with fixed Region again and use this account for unblock?
Further *adb devices* shows an ID and unautorised device. Is that right?
Click to expand...
Click to collapse
try now on your pc, i change hwid5 to hwid7(link below), logged without problems :good:
for adb/fastboot devices Works correctly enable usb debugging and press authorize
https://hwid7.vmall.com/CAS/portal/userRegister/regbyemail.html?reqClientType=2023&loginChannel=22000000&countryCode=es&loginUrl=https%3A%2F%2Fhwid7.vmall.com%2FCAS%2Fportal%2Flogin.html&service=https%3A%2F%2Femui.huawei.com%2Fen%2Fplugin%2Fhwlogin%2Fvalidate%3Fru%3D%252F%252Femui.huawei.com%252Fen%252Fplugin%252Funlock%252Findex&lang=en-us&themeName=red

I think I have to wait 2 weeks
*The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.*

Kerberos79 said:
I think I have to wait 2 weeks
*The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.*
Click to expand...
Click to collapse
have you tried deleting account since huawei id and creating one on your pc with the link from above?

yes I greated a new account with your link with other email adress.

Any progress with your p10lite?

I tryed it now and still same issue. this time I tryed with meid other time with emei.
https://www.pic-upload.de/view-34293605/unlockfehler.jpg.html
same message with both emei

Hi, I have this problem months ago, (I have a Nova Youth as gift too) and I solve it installing this app: gmsinstaller.apk or can use Googleinstaller.apk (just google it) and you dont need the root, it install the play services from Google and then you can install any app from the play store, sorry cause I dont have the apps to share but there is easy to find.
greetings from México!

[GUIDE] Enable VoLTE for your non operator handset

I have finally been able to get VoLTE working on my X Performance despite my carrier never having 'supported' my handset (they never sold it here).
What you will need?
Windows Computer with Flashtool and minimal ADB and fastboot (if you have already downloaded fimrware as below you can use flashtool on whatever platform your prefer)
Bootloader Unlocked
TWRP
ROOT (Magisk Preferred)
VoLTE enabled firmware (not sure about this one I think you can edit build.prop appropriately)
To unlock Bootloader, TWRP, and ROOT follow this guide
I will first describe how I did it and then how anyone else should be able to achieve the same outcome. Now includes a less convoluted way to do this allowing you to keep all data thanks to those who tested
1) First using a root file browser - I recommend this one browse to /system/etc/customisations/modem/
2) Check to see if there is any reference to your operator's modem in your model firmware. They are all in the format of amss_fsg_dora_xxx_tar.mbn
3) Once you have a spotted your operator you need to take note of what's in between 'dora_' and '_tar' so for example if I use china mobile - I would find amss_fsg_dora_china_mobile_hk_ims_tar.mbn I would need to take note of china_mobile_hk_ims
4) Once you have this you need to connect your phone via ADB to your PC (I found this much easier on a computer).
5) Enter the following commands adb root then adb shell
6) mount -o rw,remount /oem
7) vi /oem/modem-config/modem.conf
8) press 'i' on your keyboard to enter edit mode and delete whatever is in the file and replace it with your operator modem from step 3 - (china_mobile_hk_ims in this example) then press 'ESC' and then ':wq'
9) make a backup of your important data
10) Turn off your phone, connect it into Flashmode to your PC (hold vol- while plugging in to the PC)
11) Flash your firmware with these options - do a wipe of all partitions. Tick the OEM box in the 'Exclude SIN' section. Alternatively follow this and avoid factory reset as per @pbarrette and @SGH-i200
12) Once you have completed reboot your phone and you should pickup VoLTE settings at setup.
IF you don't have root follow the guide earlier on how to backup TA, unlock bootoader
Flash a VoLTE enabled firmware. Install TWRP. Enter recovery (hold Vol- and power to start phone) install your preferred root option. Then connect your phone via ADB (step 5) to find your operator modem per step 3. Continue with Step 6&7. Start your phone.
I have tested this using existenZ 5.5. Theoretically should work for any Xperia phones with an OEM partition, however each phone might have a different modem name for the same operator ( I know this to be the case between the XZP and the XXP), however if you get the bit in between 'modelname_' and '_tar' and follow the same process for editing the modem.conf file you should get the same results.
Credit to
@sdugoten for Unlock, TWRP and ROOT guide
@akshay2shah for informing me of the modem selector tool for other Xperias
@VeixES for informing me of the oem.sin partition and modem.conf files
@niaboc79 for existenZ ROM (highly recommended)
@SGH-i200 and @pbarrette for testing and coming up with an easier way to use this (step 11)

Wipe all partition. It's too difficult.

Is it possible to enable VoWiFi for this device.? My phone carrier supports both VoWiFi and VoLTE on newer Sony Model. But only supports VoLTE on X Performance......

would not be a more detailed guide?
do not know how to copy ...
I did not find my operator ,,amss_fsg_dora_xxx_tar.mbn"
there is a link "default"

kodein said:
would not be a more detailed guide?
do not know how to copy ...
I did not find my operator ,,amss_fsg_dora_xxx_tar.mbn"
there is a link "default"
Click to expand...
Click to collapse
Is your operator an MVNO? You could try and see if using the underlying carrier modem is present? Otherwise see if another operator in your country's modem settings work ( unlikely but your only other option is to try till you have a modem setting that works). You could try looking at the apns-conf.xml file and see if there is an operator with similar settings if you know them.

bluesky1126 said:
Is it possible to enable VoWiFi for this device.? My phone carrier supports both VoWiFi and VoLTE on newer Sony Model. But only supports VoLTE on X Performance......
Click to expand...
Click to collapse
I have the same problem. Unfortunately I don't think there is any way unless you know the VoWiFi settings. I'll look into it. For me at least I'm no longer having dropped calls or missing out on important calls

chris_j26 said:
I have the same problem. Unfortunately I don't think there is any way unless you know the VoWiFi settings. I'll look into it. For me at least I'm no longer having dropped calls or missing out on important calls
Click to expand...
Click to collapse
I see......
Well, still congrats to you~

Please flashable zip sir

chris_j26 said:
1) First using a root file browser - I recommend this one browse to /system/etc/customisations/modem/
2) Check to see if there is any reference to your operator's modem in your model firmware. They are all in the format of amss_fsg_poplar_xxx_tar.mbn
Click to expand...
Click to collapse
If the mbn file is not there, can I copy it to this folder? What has to be changed after copying the file threre?

SGH-i200 said:
If the mbn file is not there, can I copy it to this folder? What has to be changed after copying the file threre?
Click to expand...
Click to collapse
If you got an mbn file it might work. However I suspect that it contains modem specific files if you copied it across from one device family (Xperia X , Xperia xz for example) it theoretically could work. I would imagine you would need to set permissions on the mbn file once copied I would think 1744 would do it but I'm not an expert on Android filesystem permissions. You could always do ls -la in terminal on the folder and replicate those permissions.

chris_j26 said:
10) Turn off your phone, connect it into Flashmode to your PC (hold vol- while plugging in to the PC)
11) Flash your firmware with these options - do a wipe of all partitions. Tick the OEM box in the 'Exclude SIN' section.
12) Once you have completed reboot your phone and you should pickup VoLTE settings at setup.
Click to expand...
Click to collapse
A Factory Reset is not needed to switch the active MBN! Please update point 11 to 'Flash cust-reset.ta' (and keep all your data and settings!):
pbarrette said:
I usually just flash the cust-reset.ta file. That clears the unit in the TA partition which holds the current carrier customization information.
Click to expand...
Click to collapse