Related
So coming from this :
http://forum.xda-developers.com/showthread.php?t=1658568&page=38
Thread i decided to create a new one to collect and focus all necessary informations for the procedure of flashing and rooting the Motorola Defy Mini XT 320.
Credits for Rooting Guide and files goe's to leos0 and i thank him very much for giving us (me) the freedom to root this Phone.
Also many thanks to coder011 he extracted the recovery.img from defy mini which is necessary for rooting :highfive:
Table of Contents:
Do i have Fastboot or not?
How to flash Firmware?
How to gain Root access?
Which Firmwareverisions have Fastboot Mode?
How to flash only older Bootloader to get Fastboot without changing Firmware?
At first, you have to know if your Phone have Fastboot or not.
The easyest Way to find out, is to boot the Phone in Recovery or (if it can) in Fastboot Mode.
Power off the Phone
Power on by pressing both Volume Buttons and the Power Button at once and hold them for 5-10 seconds
if then a screen comes up, you can see if you have Fastboot
look at the pictures below to compare
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you see this, then you are a happy one, because your phone has fastboot. You can directly go to the rooting procedure below. :good:
If you get this screen, you have to decide if you want to risk an flash of different SBF Firmware file as described in the next Part of Guide.
Your Phone has no Fastboot. :crying:
Due to some questions in this Thread i want to make clear, what is necessary to do all this strange stuff.
rocker55555 said:
I read the guide. The only mention of installing drivers is in the flashing guide and that guide is for users who didn't have fastboot on their phone.
Click to expand...
Click to collapse
OK
For anyone who needs it more clear.
For everything that is more than using the Phone as USB Mass Storage, you need to install the Drivers.
What the PC doesn't know, he cannot deal with it.
Drivers are (nearly in everything you do) absolutely mandatory.
And if anything doesn't work on a computer, the first thing you be asked is "Have you installed the drivers?".
Defy Drivers:
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=2cff07f8ef573210VgnVCM1000008806b00aRCRD
Install the Drivers and connect your Phone with USB Debugging enabled or bootet in Fastboot Mode (Power up with holding Volume + and - Buttons for 5-10 seconds).
If the Drivers are installed correct your Phone was shown in device Manager like this:
For flashing other Firmware your Phone must connected as Flashing device.
Power it up with Volume - and Camera Button pressed. You see then an Black screen with some white Text.
Connect Phone and let Drivers install.
If your Phone is connected correct it will be schown in Device Manager like this:
Only after you have installed all drivers and your Phone is recognized by your PC as shown above, you will be able to work with ADB or RSD-Lite.
At first, my Guide to flash your Phone with different ROM if your ROM didn't have Fastboot.
Flashing Guide:
And you have to download RSD Lite:
http://www.chip.de/downloads/RSD-Lite_49139659.html
Defy Drivers:
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=2cff07f8ef573210VgnVCM1000008806b00aRCRD
Install Drivers and RSD-Lite.
Start RSD Lite and load SBF File.
Then shut down the Phone and Boot up by holding Camera + Volume- (down) and Power Buttons.
If you done right, you see an black screen with white Text, telling you the Device is in flashing mode.
Connect Phone to PC and let Drivers install (after that RSD Lite shows an "Connected" Message in App.
Click on "Start" in RSD-Lite
Flash begins and you see a lot of Message Lines for everey Flash Step.
At the End of the Process Phone reboots.
Now you cann deconnect and close RSD Lite, ignoring the Message that it is still in Progress.
BUT NOT BEFORE THE PHONE REBOOTS!!
Sometime there is an Error and the Flash fails at first try.
You have then to pull the Accu and to repeat flash Procedure.
Warning!!!
You can brick your Phone!!
In some cases the Phone loses IMEI and Connection to SIM and is broken!!
If you do this, you do it at your own risk!
To prevent this and/or to recover your IMEI and unlocked SIM follow this Guide:
[Important] Backup and Restore Defy Mini IMEI and NV Data
Additional Hint.......
If you can't find an ROM of your native carrier which is rootable, search for a ROM of an Carrier from your Continent which supports eventually your Language and Carrier.
E.g. i found Brazil ROM which is rootable but have no German Input and Language. So i testet some European ROM's and found one from Spain which is rootable and have native German Support and APN in it.
So now i don't need to test further because all works great and have German Phone UI.
The ROM i use at the Moment:
http://hotfile.com/dl/184330128/2d4ce8b/TNBST_4_0A.1F.0ERPS_flex_WE_Orange_Spain.zip.html
(you have to register before you can download, ZIP Password is "mod2xtreme.com" but be aware, that the Site is sometimes down)
And feel free to donate to the Board for their excellent Service to offer us this ROM's. :good:
If you have an ROM with Fastboot, follow this Guide to Root (Original Post from leos0 here):
Important!!
Some prerequisits:
Download and extract the View attachment root_xt320.zip to the Root of your Harddisc. Best place is C: so it has to be in
Code:
C:\root_xt320
.
If you place it in any other place, adjust the Path variables from next advices to your needs.
Open Command prompt on PC.
Type in
Code:
cd C:\root_xt320
and hit Enter
Now you are in correct folder to do the next steps
Okey, so, rooting You have to download this : ( it contains fastboot adb recovery.img and update.zip [ I think it is the right one, becourse
i was applying a few of them at one time to save my time xd ] )
0. Copy update.zip to /sdcard/
1. You need to boot into fastboot (NOT RECOVERY, F A S T B O O T ). You can use:
a)
Code:
adb reboot-bootloader
or
b)turn off the phone, then hold POWER+VOL UP+VOL DOWN for 5-10 sec.
2. Now you need to use fastboot. use:
Code:
fastboot boot recovery.img
3.Now CWM TOUCH will boot. There is small problem, it doesn't look as it should, some options are somewhere else etc.
But it works! In normal CWM Recovery i was unable to choose any option, but there everything "works" And you should use
keys on your phone ( POWER to execute, vol. keys to move ), not screen to choose things ( it crashed once when i was using screen )
4. Install zip from sd..(second option)-->choose zip from sdc..)--> ...choose...--> Yes - Install --> Reboot --> back
For commands in [.code] marker you need to use cmd. I hope it will work for you guys You are doing everything on your own so if something dont work its not my fault.
If you want to repost it somewhere, please, just write who invented it You should also thanks coder011 becourse he extracted the recovery.img from defy mini which was very helpful
Enjoy
Click to expand...
Click to collapse
Download of Files for Root
So now i have one Wish.
Please can anyone who have found an ROM which is rootable/ed and have no SIM-Lock post the FW Version and SBF Name here so we get an complete List of useful ROM Versions.
I will try to update it several times.
View attachment root_xt320.zip
Rootable Firmware List
TNBST_4_0A.1F.0ERPS_flex_WE_Orange_Spain (the one i use at the Moment)
TNBST_4_07.1D.08RPS_flex_LATAM_Claro_Latam
TNBST_4_0A.1D.22RPS_flex_WE_RTIT
TNBST_4_07.26.11RPD_flex_LATAM_RTL_Brazil
TNBST_4_0A.1F.10RPS_flex_WE_Retail_CEE
Some additional "special" Procedures to have mor Options
Option to flash only older Bootloader with Fastboot enabled without changing your current Firmware and have the Option to root after that.
Some "special" Method posted by Alin Razvan, member of droiddevelopers forum.
Let me explain how i got this working a good sbf flash with a lower bootloader version.
First step you are about to do, is downloading a compatible sbf version that you like !
2nd step flash it with RSD Lite 5.7
3rd step after flashing it go into recovery menu by pressing both volume keys + - and power up .
4th step -> Clean Cache -> Clean User Data , after cleaning select reboot
5th step Let it reboot normally , set it up , connection etc , google account and so on .
6th step Download TNBST_4_0A.1F.0ERPS_flex_WE_Orange_Spain.sbf
Power off the phone , remove battery , pres camera button + volume down+power insert usb (if doesn't power up attach battery but only for a second than remove it) , now you should be in boot mode .
Open RSD Lite 5.7 select the TNBST_4_0A.1F.0ERPS_flex_WE_Orange_Spain sbf file and (read bellow).
Here comes the tricky part !!!
Be carefull and fast otherwise you got to flash again your favorite sbf ,and follow the upper steps again !
Before pressing start button take your phone on your right hand , grab with your left hand the usb cable because you are about to pull it back quickly after you see
Flashing Modem (mdm) or something like i reallly don't remember how the text really was but what you need to do is let it flash some reboot files it takes up 3 seconds after pressing start button to flash those files so you got to be fast boot ) i know it sounds awkward but this **** really works !
After removing usb cable your phone will instantly shut down because it doesn't have the battery on , i did it without battery because i wanted the phone to shut down instant !
So the next step is to power up the phone by pressing both volume buttons + - and power up button , now you should see fastboot menu YaY!
After that, you can switch to the rooting Procedure as described above.
afadel wrote in Post #14:
afadel said:
Alin's method consists of loading an older bootloader version. In theory you don't even have to flash an SBF if the one you're using (original or already flashed) is working for you (meaning no simlock). You just go from step 6 onwards.
You put the phone in flash mode by holding camera+vol down and powering the phone. You should see a screen with the following:
MBM Flash-mode.
TinBoost
version: 06.0a --> (versions may vary)
Bootloader USB Init SECURE BOOT ENABLED
Now you have to use an SBF with an old version of bootloader. I don't know up to which version the bootloader has fastboot, but I used the SBF TNBST_4_07.1D.20RPS_flex_LATAM_VIVO. This one has fastboot.
So, you open RSD Lite and use this SBF. When you click start first it will update (in this case downgrade) the bootloader version. It will run some stuff and then you will see the same screen from above again (but now with different version - 01.0a if you use the SBF I mentioned) and it will start the flashing process. That's when you have to unplug the battery or USB cable to stop the flashing. All you wanted was to install the bootloader.
After that you just have to follow the procedures as if your phone had fastboot since the beginnig! That was a very smart move by Alin.
Click to expand...
Click to collapse
I have tested Alin's Method today.
My biggest Problem was, that my Phone is not able to Power on only with USB Cable connected. I also have to insert Accu (very loose) and to pull Cable and shake out the Accu the same time immediately as the Message of "Modem flashing" (or something like this) comes up on Screen.
I now have newest German ROM ( TNBST_4_0A.21.0CRPS_flex_WE_RTDACH ) with Bootloader (Fastboot enabled) from Spanish ( TNBST_4_0A.1F.0ERPS_flex_WE_Orange_Spain ) ROM and rooted.
Great thing.
Big thanks to Alin and afadel for this!!
Moved to General
TNBST_4_0A.1D.22RPS_flex_WE_RTIT
This is the ROM my phone came with (Italian retail), it has fastboot and it's not sim locked.
http://www.droidevelopers.com/f412/14395-defy-mini-root-success-yes-works-2.html#post59544
Bro add this to first post, it's how i did it.
Sh0m1 said:
http://www.droidevelopers.com/f412/14395-defy-mini-root-success-yes-works-2.html#post59544
Bro add this to first post, it's how i did it.
Click to expand...
Click to collapse
Sorry Guy, have you read the above Guide?
This is exactely what i wrote.
But without all the Pull of Accu and USB and, and, and...
Because it is simply not necessary.
Flashing is much mor simple. Just two steps.
And why should anyone flash two times?
First with an SBF of his Wish. And then (by completely overwriting this Firmware in the Phone) with the one you posted?
And exactely this is also the one i used and wroted in my Guide.
But a lot of Asian and Latam Users cannot use this because it is not containig their Languages.
So this is why i asked anyone who have rooted his Phone to write here with which SBF he does it.
No bro, you do not flash 2 times.
First time you flash some sim unlocked firmware that works for you, than you flash the one with bootloader, but not the whole firmware, just modem stuff, and then you cancel the flashing by disconnecting the phone so you still have YOUR old firmware, but now it has new firmware's bootloader.
I hope i made it more clear now.
Sh0m1 said:
No bro, you do not flash 2 times.
First time you flash some sim unlocked firmware that works for you, than you flash the one with bootloader, but not the whole firmware, just modem stuff, and then you cancel the flashing by disconnecting the phone so you still have YOUR old firmware, but now it has new firmware's bootloader.
I hope i made it more clear now.
Click to expand...
Click to collapse
OK.
My fault.
I'm to tired to read conscious. Last 8 days in job was to busy.
Will give it a try.
But i am not sure if i will do it really, because i am very satisfied with my current state. I have installed the TNBST_4_0A.1F.0ERPS_flex_WE_Orange_Spain.sbf by flashing it completely and have set up Link2SD and all works like a charm with constantly mor than 120mb free internal Memory also after installing a lot of Apps. :highfive:
But.
If you agree, i will include your advice in "my" (not really mine, have only made a summary) Guide.
Sure, just write that the original creator of that method is Alin Razvan, member of droiddevelopers forum.
Sh0m1 said:
Sure, just write that the original creator of that method is Alin Razvan, member of droiddevelopers forum.
Click to expand...
Click to collapse
Done :good:
Thank's
Great guide i must say, thank you for the effort and i hope this will attract some devs to start making roms for mini
Can't download the firmware with that link, i think the link is wrong...
Just to be sure, the firmware you gave the link is that Brazil no simlock you said?
Alin's method consists of loading an older bootloader version. In theory you don't even have to flash an SBF if the one you're using (original or already flashed) is working for you (meaning no simlock). You just go from step 6 onwards.
You put the phone in flash mode by holding camera+vol down and powering the phone. You should see a screen with the following:
MBM Flash-mode.
TinBoost
version: 06.0a --> (versions may vary)
Bootloader USB Init SECURE BOOT ENABLED
Now you have to use an SBF with an old version of bootloader. I don't know up to which version the bootloader has fastboot, but I used the SBF TNBST_4_07.1D.20RPS_flex_LATAM_VIVO. This one has fastboot.
So, you open RSD Lite and use this SBF. When you click start first it will update (in this case downgrade) the bootloader version. It will run some stuff and then you will see the same screen from above again (but now with different version - 01.0a if you use the SBF I mentioned) and it will start the flashing process. That's when you have to unplug the battery or USB cable to stop the flashing. All you wanted was to install the bootloader.
After that you just have to follow the procedures as if your phone had fastboot since the beginnig! That was a very smart move by Alin.
BlueSpyBR said:
Can't download the firmware with that link, i think the link is wrong...
Just to be sure, the firmware you gave the link is that Brazil no simlock you said?
Click to expand...
Click to collapse
Corrected the Link.
ROM is:
TNBST_4_0A.1F.0ERPS_flex_WE_Orange_Spain
afadel said:
Alin's method consists of loading an older bootloader version. In theory you don't even have to flash an SBF if the one you're using (original or already flashed) is working for you (meaning no simlock). You just go from step 6 onwards.
You put the phone in flash mode by holding camera+vol down and powering the phone. You should see a screen with the following:
MBM Flash-mode.
TinBoost
version: 06.0a --> (versions may vary)
Bootloader USB Init SECURE BOOT ENABLED
Now you have to use an SBF with an old version of bootloader. I don't know up to which version the bootloader has fastboot, but I used the SBF TNBST_4_07.1D.20RPS_flex_LATAM_VIVO. This one has fastboot.
So, you open RSD Lite and use this SBF. When you click start first it will update (in this case downgrade) the bootloader version. It will run some stuff and then you will see the same screen from above again (but now with different version - 01.0a if you use the SBF I mentioned) and it will start the flashing process. That's when you have to unplug the battery or USB cable to stop the flashing. All you wanted was to install the bootloader.
After that you just have to follow the procedures as if your phone had fastboot since the beginnig! That was a very smart move by Alin.
Click to expand...
Click to collapse
Thank's for this variant.
Included in guide at Starting Page.
Why you didn't include my name? I'm the one who extracted recovery.img that was very helpfull.
coder011 said:
Why you didn't include my name? I'm the one who extracted recovery.img that was very helpfull.
Click to expand...
Click to collapse
Sorry.
My fault.
Didn't recognized it.
Please forgive me.
Don't want to do any harm. And never done liek it was my work.
Which Text do you want to put (where) in the Gude to show which work you have done?
pbruck said:
Sorry.
My fault.
Didn't recognized it.
Please forgive me.
Don't want to do any harm. And never done liek it was my work.
Which Text do you want to put (where) in the Gude to show which work you have done?
Click to expand...
Click to collapse
At this part
Credits for Rooting Guide and files goe's to leos0 and i thank him very much for giving us (me) the freedom to root this Phone
Click to expand...
Click to collapse
@pbruck and @coder011
Thank you to work on this and make it possible.
I have a Defy mini dual chip XT321 and tried to root by flashing Claro Latam firmware on it but I didn't have success. Can you help me on this?
When I flashed Claro firmware phone worked normally and it has got fastboot =D
I've made all steps you described but after power up phone was no rooted.
I'll really apreciate if you help me!
Congrats for the initiative!
How to fully fix au Japanese HTC Butterfly 3 with Taiwan’s ROM
[ROM verified working in US on all gsm networks and Europe (other networks may place sim lock ie. Middle East, South America)]
**Read over entire guide before starting**
**I am not responsible for any damage done to your phone. (Guide is basically without flaw, but still)**
**It is recommended you leave sim card out until point you stop, turn off phone, insert, then reboot.**
Shout out to mars3712 for uploading the file images check him out and donate:
https://www.androidfilehost.com/?w=profile&uid=24052804347819348
and another shout out to moizjazz for helping me diagnose my problem that many have been experiencing (banner error due to CID and MID[this prevents HTC updates from installing and/or installing zips])
Pre-req.s htc drivers and adb 1.3 drivers
1. Enable adb debugging on phone
2. Download this file and unzip: https://drive.google.com/file/d/0BwjkdhnznIw6THQxdHFIcWUxRms/view?usp=sharing
3. add this zip with it and unzip contents into same directory https://www.androidfilehost.com/?fid=24352994023706379
4. hold shift and then right click blank space in folder and select open command window here
5. Type: adb reboot download
6. Type: fastboot oem get_identifier_token
7. Right click terminal and left click and hold from First "<" to last ">"
8. Press enter, paste into wordpad or text editor
9. Delete all <bootloader> s and space afterwards
10. Log into www.htcdev.com
11. Copy the token to http://www.htcdev.com/bootloader/unlock-instructions/page-2
12. Proceed with instructions until you get the email.
13. Download Unlock_code.bin and put it with all other files (in b3twrp)
14. Type into terminal Fastboot flash unlocktoken Unlockcode.bin
15. You will be prompted to allow unlock, with volume rocker move to yes and press power button
16. During reboot hold all three buttons and when phone shuts off let go of vol+
17. You will be in download mode again
18. Type these commands
a. Fastboot flash boot boot.img
b. Fastboot flash recovery recovery.img
c. Fastboot flash system system.img
d. Fastboot oem writecid HTC__621
e. fastboot oem writemid 0PL220000
[Good time to make twrp backup on SD card]
[You can stop here if you are content with lollipop; skip to bottom for gps fix]
f. fastboot oem lock
19. Reboot and upgrade to marshmallow without dealing with banner errors and RUU
At this point the Tiawan rom has two software malfunctions, no gps and no nfc, however, there is a patch you can flash for gps
Marshmallow update has gps fixed and nfc detected, but unusable.
-video- https://www.youtube.com/watch?v=LEAH...SD4YsS3P4WqrPA
-Straight up link- http://1drv.ms/1nKdi4e
This dude is awesome for having the gps fix, like his video.
P.S. There is now a way to root or add xposed installer to Marshmallow because twrp 3.0 for recovery has been made for this device running marshmallow
[Edit]: Now there is twrp!!!!! (see bottom!!!!)
**I have tested this method twice and confirmed that even with some updated download mode firmware, updates will always be possible**
*This method rocks!*
Also (to end this goose chase), if any of you want the zips for some reason, here are the links to the best servers:
Japan: https://www.androidfilehost.com/?fid=24052804347822774 Credit goes to - Krocko
Taiwan: https://www.androidfilehost.com/?fid=24352994023706373 Credit goes to- mars3712
Big ANNOUNCEMENT! An actual twrp recovery image has been compiled and uploaded!(In china)
Here's my reuploaded copy! (Won't take 10 minutes to download) Thanks to mrquyen1993 for sharing this update and a HUGE thanks to... I actually dont know...
https://drive.google.com/file/d/0B6qqU5WVQ2khMVRMSUhOUWY3WU0/view?usp=sharing
Phone, SMS, and data work perfectly! I had issues with sms due to damaged SIM card(weirdest thing ever).
Hello, I believe a simlock solution has been found. add attached misc.img to your b3 adb directory and open terminal and enter command fastboot flash misc misc.img in bootloader mode. If that doesn't work try it in download mode. I can't test if this is a successful fix or not because I didn't have this problem.
So when I flash this rom, I will get a completely clean rom with no bloatware, root and TWRP?
And if I have root I can use your method to be able to text again?
Twrp is still only flashable to recovery and and all gsm cell service works, but other than that you're correct. These are the stock flashable images. (You need to decompress the file)
Sent from my HTC_B830x using XDA-Developers mobile app
Works like a charm, thanks a lot!
So if I follow your steps, I can convert my Japan version to Taiwan version? Does NFC and GPS work?
Can you post a copy of your updated boot.img somehow?
NP. Srry I Just saw this now.
[deleted]
Half correct
frosticfire said:
So if I follow your steps, I can convert my Japan version to Taiwan version? Does NFC and GPS work?
Click to expand...
Click to collapse
Only gps will work and you have to follow the bottom link. Follow the instructions.txt in the zip.
Sim card problem
My phone keeps showing "SIM network subset unlock PIN" , it reboots after i entered the pin, it goes back to the same page after it reboots. Any solutions?
This only happens when there's a SIM card being inserted.
Troubleshooting
bernard090 said:
My phone keeps showing "SIM network subset unlock PIN" , it reboots after i entered the pin, it goes back to the same page after it reboots. Any solutions?
This only happens when there's a SIM card being inserted.
Click to expand...
Click to collapse
Have you tried:
-soft factory reset(in settings)
-factory reset and/or wiping cache in download mode
-factory reset and/or wiping cache in recovery
-wiping system, data, and cache in twrp prior to flashing boot, recovery, and system
-reverting to backup
-trying simlock toggle in recovery/weird mode with vol+ and power on boot
-Checking sim support/trying different sim
These are steps I would take (in the order least to most in depth[not this order])
Sounds like a problem with your sim card from your specific provider. The phone with Tiawan has an international apn-configs.xml
TWRP for B3 By BOA ai-dev
Tutorial Chinese
TWRP-Recovery Rom taiwan
TWRP-Recovery Rom Japan
Rom stock B3 HTV31 Au ver 1.11.970.0 - new
Boa rom cook pay
After updating Marshmallow , you do not need to fix gps.
Sorry, my english very bad
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bug:
1. NFC.
2. Power.
This is some awesome stuff!
mrquyen1993 said:
TWRP for B3 By BOA ai-dev
Tutorial Chinese
TWRP-Recovery Rom taiwan
TWRP-Recovery Rom Japan
Rom stock B3 HTV31 Au ver 1.11.970.0 - new
Boa rom cook pay
After updating Marshmallow , you do not need to fix gps.
Sorry, my english very bad
Bug:
1. NFC.
2. Power.
Click to expand...
Click to collapse
I'm going to test these files!
[Edit] I have now confirmed twrp works. If you can, please have the creator make a thread in android development!
@ boa19861105
http://forum.xda-developers.com/member.php?u=1580110
Sent from my HTC_B830x using XDA-Developers mobile app
Birkyjon said:
Have you tried:
-soft factory reset(in settings)
-factory reset and/or wiping cache in download mode
-factory reset and/or wiping cache in recovery
-wiping system, data, and cache in twrp prior to flashing boot, recovery, and system
-reverting to backup
-trying simlock toggle in recovery/weird mode with vol+ and power on boot
-Checking sim support/trying different sim
These are steps I would take (in the order least to most in depth[not this order])
Sounds like a problem with your sim card from your specific provider. The phone with Tiawan has an international apn-configs.xml
Click to expand...
Click to collapse
I've tried every single method you have listed but to no avail, any other suggestions?
Butterfly 3 android 6 sense 8
https://m.facebook.com/story.php?story_fbid=1083701208319409&id=241474159208789
Sent from my HTC_B830x using XDA-Developers mobile app
So... will SMS Work?
Hi, the whole reason to do this for me is to get SMS working in the UK on this phone. Will this fix it? Also will this root the phone, as the KLGadget guy on Youtube seems to think that you can flash the Taiwan Rom without Root, but I have had no luck (keeps saying SC CARD NOT MOUNTED when I try his method) thanks.
nickbarr said:
Hi, the whole reason to do this for me is to get SMS working in the UK on this phone. Will this fix it? Also will this root the phone, as the KLGadget guy on Youtube seems to think that you can flash the Taiwan Rom without Root, but I have had no luck (keeps saying SC CARD NOT MOUNTED when I try his method) thanks.
Click to expand...
Click to collapse
you should have a PC, Laptop and follow my instructions.
however I write in Vietnamese, you can use gg translate
Link
Sorry my english very bad
mrquyen1993 said:
you should have a PC, Laptop and follow my instructions.
however I write in Vietnamese, you can use gg translate
Link
Sorry my english very bad
Click to expand...
Click to collapse
Thanks, but I am not sure you have answered my questions.
Rom stock taiwan can fix sms,
I use adb to flash rom, it should not need sd
mrquyen1993 said:
Rom stock taiwan can fix sms,
I use adb to flash rom, it should not need sd
Click to expand...
Click to collapse
thanks. I will follow the original instructions.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
[/CENTER]
Credits:
- TWRP Team
Device: Lenovo Tab3 7 Tablet - TB3-730X
Do not flash this on TB3-730F. The F model has different chipset and this recovery will softbrick it.
@sun_dream reported that 730F is working. So you can probably flash it, but be prepared with OFW, in case something goes wrong.
Instructions:
IMPORTANT: read all instructions at least once, before starting.
Note: If you're are a newbie, you can read more detailed instructions by honzazkrumlova here
- Download from link below.
- Enable "USB debugging" from developer options.
- Enable "OEM Unlocking" from developer options.
- Reboot device in Fastboot Mode (Bootloader mode), either with "adb reboot bootloader" or with VolDown+Power, to enter Recovery mode and then select "Reboot into bootloader"
- Unlock the bootloader with "fastboot flashing unlock" or "fastboot oem unlock" and follow the instructions on the tablet. (WARNING: This will erase all your data - Factory Reset)
- Once unlocked, you can use "fastboot boot TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img" to start TWRP.
- When TWRP ask to modify system partition, answer "NO". Otherwise you will soft-brick your device and you will have to flash the original firmware and start from the beginning.
- If you want root - flash SuperSU, or as the user @Kellicros reported, you can flash Magisk 11.1.
- If you want XPosed, get it here.
- If you want to permanently flash the recovery, use "fastboot flash recovery TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img".
- If you use it on any other Lenovo Tab3 7 device, please post the model.
- Thanks is always welcome.
Downloads:
TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.zip (well tested, consider it stable)
TWRP_3.1.1_Lenovo_TB3-730X_Android-6.0_recovery.zip
Unbrick your device:
Follow this thread
Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)
beldy said:
Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)
Click to expand...
Click to collapse
Hi.
When TWRP is started for the first time, it asks to modify the system partition.
I answered NO, NEVER. I saw some posts about other MTK devices and other people seems to have problems like yours when TWRP modify the system partition.
Is this your case?
If yes, then you need to download the original firmware and flash it on the device. After that you need to flash the recovery again.
I've downloaded the original firmware from Russian forum (this post: http://4pda.ru/forum/index.php?showtopic=731493&st=20#entry52434543). Here is direct link: https://cloud.mail.ru/public/Fjd9/u7e8mUbhq )
This is the last TB3-730X firmware. Do not try 710 firmwares, they should not work and it is probably dangerous to flash it. I dont know for 730F, this one could work, but anyway, download the the 730X firmware from the link above.
I guess you will need the SPFlash Tool to flash the firmware.
Hope this helps.
Thank you for the link ...
so probably it is my case that TWRP modify the system partition ... try this firmware and send the result ..
Thanks again for your help, I appreciate it.
I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?
DonKapselo said:
I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?
Click to expand...
Click to collapse
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".
"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....
beldy said:
"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....
Click to expand...
Click to collapse
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.
0xAF said:
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".
Click to expand...
Click to collapse
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.
DonKapselo said:
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.
Click to expand...
Click to collapse
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
Error 0×7D4
Message: BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL
Meaning: SP Flash tool encountered an error writing to the phone
Solution
* Try using a different USB cord, PC port and PC
* Use the latest version of SP flash tool
* Ensure the battery is well charged and the phone's USB port isn't faulty
Click to expand...
Click to collapse
But I guess it's not very helpful.
0xAF said:
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
But I guess it's not very helpful.
Click to expand...
Click to collapse
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
DonKapselo said:
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
Click to expand...
Click to collapse
The easiest way to port TWRP is to get it from another device with the same chipset and cpu. I did not wanted to prepare a toolchain/crosscompiler and start from the beginning to compile TWRP. So I took a TWRP from another tablet (DOOGEE_X6pro_Android6.0_20160707). Since it has a recent version of TWRP and is compiled for android 6.
Then all you need is to replace the kernel in this recovery, so we are booting with the kernel for our device. I needed the kernel from our original recovery for that. Then I've touched some files inside the recovery, fixed the fstab and default.prop and repackaged the recovery image.
This is the easiest way to port the recovery IMO. Took me 15-20 mins with all the testing.
This procedure work for any recovery, not only TWRP.
I guess, I could have dumped the original recovery from the device, but since I was looking for custom recovery for some time, I found the dump in the russian forum and downloaded it. So when I decided to port TWRP, I already had the recovery from the dump.
Thanks for info Any link to step by step how to replace kernet, what data change?
DonKapselo said:
Thanks for info Any link to step by step how to replace kernet, what data change?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=hwMFBuCY-5k
I saw this video and decided to follow the steps.
You will need some intuition about the files you need to change inside the new recovery, as the video shows that only the fstab is needed, but you need more files, like default.prop and some other device dependent files from the original recovery (mostly in root folder).
In this recovery, I've used the default.prop from the original recovery.
As for the fstab, you will need to convert it by hand to a format understandable by TWRP. I've used the TWRP fstab file from the other device (from which I took the recovery in first place) and adopted it to our device. IIRC, almost nothing had to be changed.
I've copied some other device dependent files from the original recovery too.
Since I'm on linux, I've used these tools:
https://github.com/osm0sis/Android-Image-Kitchen.git
https://github.com/osm0sis/mkbootfs/
https://github.com/osm0sis/mkbootimg/
The tools are also available for windows (as the video shows) and for android itself (I believe the CF-SuperSU uses them on android to repack the boot.img).
These tools can repack recovery.img and boot.img.
Many thanks!
0xAF said:
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.
Click to expand...
Click to collapse
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx
beldy said:
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx
Click to expand...
Click to collapse
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).
0xAF said:
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).
Click to expand...
Click to collapse
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
beldy said:
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
Click to expand...
Click to collapse
You should try to flash the dump with "fastboot flash system <file>"
Hello,
Got the Lenovo TAB3-730M.
What SuperSU.zip do I have to take to get "root"?
The "SR3-SuperSU-v2.78-SR3-20161103171345.zip" does not work.
Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
Prerequisites:
Service firmware. Can be downloaded here. It's an older build, but it will do the trick and it's the only one I could find freely available at the time of writing. Only for WW SKU
Zip for your desired build. Can be found here.
- Note: For this guide, my desired build will be WW-17.1810.1910.63, which is a special case, as you will need to flash in the following order: Service Firmware -> WW-16.1220.1909.194 -> WW-17.1810.1910.63. In other cases, unless noted otherwise in a description of the build on the ASUS website, Service Firmware -> Desired build will suffice.
Platform tools of Android SDK. Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
This is not required but for the sake of simplicity and keeping everything in one place, create a folder and name it whatever you like, for example ASUS or Unbrick
Create a sub-folder inside the folder you've created in the previous step, call it service_firmware, download and unzip service firmware into this folder
Download files for the desired builds from the above link. For this specific case, WW-16.1220.1909.194 and WW-17.1810.1910.63.
3.a If you have microSD card, transfer zip file for the desired build into its root and insert the card into the phone.
3.b. If you do not have a microSD card, download and unzip platform tools mentioned in the prerequisites as you will need adb to flash firmware/s via sideload
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode via one of the methods:
1.1. Turn off your device, then turn it on while holding down the power and volume up buttons at the same time. Release the power button when it powers up (keep holding the volume up button)
1.2. If you have platform tools, you can do adb reboot fastboot
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices
Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
It is possible to avoid userdata wipe (although not encouraged) but keep in mind, unless you flash your current build after flashing service firmware, your phone will not boot up.
If you absolutely would like to preserve your userdata, even if for the sake of backing it up before doing a factory reset, you have to edit the flashall script in the following way:
Windows: Open flashall.cmd in your favorite text editor, go to line #298 and change it from fastboot -w to REM fastboot -wand save the changes.
Unix: Open flashall.sh in your favorite text editor, go to line #275 and change it from $fastbootcmd -w to #$fastbootcmd -w and save the changes.
Once again, this is not encouraged as it can potentially cause issues later on. You've been warned.
Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Step 3 - Upgrade to your desired build
Enter Recovery mode via one of the following methods:
1.1. If your phone is turned on and USB debugging is enabled, use command adb reboot recovery
1.2. While in fastboot mode, navigate to Recovery Mode using Volume Up/Down buttons and select with a single press of a Power button
1.3. While in fastboot mode, issue one of the following commands : fastboot reboot recovery or fastboot oem reboot-recovery
Once in Recovery Mode, you have 2 ways to proceed:
A: Update from SD card
A.1. Select Apply update from SD card option
A.2. Navigate your SD card and select UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip
A.3. Confirm your choice with a single press of the Power button
A.4. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
A.5. Select Apply update from SD card option again
A.6. Navigate your SD card and select UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip
A.7. Confirm your choice with a single press of the Power button
A.8. Once you're back to the menu of Recovery Mode, select Reboot system now
B: Update through ADB Sideload
B.1. Select Apply update from ADB option
B.2. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip"
B.3. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
B.4. Select Apply update from ADB again
B.5. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip"
B.6. Once you're back to the menu of Recovery Mode, select Reboot system now
Note: Like I've mentioned earlier, these steps are specifically for build WW-17.1810.1910.63. If your target build does not require another build for an update, you can skip steps A.4 to A.7 or B3 to B5
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone with your desired build of firmware.
If you have any questions, do not hesitate to ask.
Cheers.
Hello i've a question (sorry for my bad English). This morning my phone was bricked (red message logo), and with this tuto i remove this logo and i found my original recovery.
But when i want to install firmware from recovery with SDcard option, i've a message no SDcard found and impossible to install firmware. (even after several tries)...
If i reboot my phone i have android logo bootloop...
Can you help me???
https://drive.google.com/file/d/1GStfEgZFpb66JRaAmjeYOKmyn9d8WcPz/view?usp=sharing
https://drive.google.com/file/d/1FSRZfI1vNAyDQDZaLDGrHyiC-lImsYhr/view?usp=sharing
Thank you and Happy New Year...
Thanks for the link to that service firmware!
_Kuroi_ said:
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Cheers.
Click to expand...
Click to collapse
Thanks a lot mate, you made my day!
Please, one question: can you tell me, if both slots (A & B) are flashed by this method?
Thanks!
Thank you so much!
I've wanted to go back to stock for so long, but I haven't been able to find a stock ROM. I've even contacted ASUS support and they couldn't even get it! Thank you so much for the download and for the guide, you've made my week. I'll be smiling every time I use my phone thanks to you!
Great guide. I have a soft bricked device after flashing Lineage 16.0 recovery. Have a boot loop and can't get to recovery. I realise the mistake was flashing the recovery as should have just booted it.
Has anyone else had success with this on a Zenfone 6?
For those who need it; managed to resolve by downloading the stock firmware from Asus, extracting the boot.img and flashing it. Back working.
Didn't try the guide but this is quicker in this scenario if you have flashed a custom recovery to the boot partition. There is no separate recovery partition so this soft bricked the device, overwriting boot with recovery (I followed the guide here for LineageOS which is ill advised) . Should be booting the recovery rather than flashing, or booting into stock recovery and using the installer zip for your custom recovery.
Steps to recover:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
This worked for me, but I'm still in CSC FastBoot Mode and when Android boots, I'm asked to insert a previous pin, which nothing works. Any advice?
kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
hey, did you manage to fix this? i'm having the exact same problem
sapientsaxonsaboo said:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Click to expand...
Click to collapse
I tried to install latest firmware from
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
everything goes fine but it shows till this moment:
fastboot flash boot_b boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.295s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed for non-official image')
any suggestions ?
kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
Taylor Moon said:
hey, did you manage to fix this? i'm having the exact same problem
Click to expand...
Click to collapse
Try flashing latest image of Android 9 and then flash Android 10
Can somebody please help me with my problem?
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Click to expand...
Click to collapse
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
CVonV said:
Can somebody please help me with my problem?
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
When you connect it to your laptop, go to device manager and check what it is detected as.
_Kuroi_ said:
When you connect it to your laptop, go to device manager and check what it is detected as.
Click to expand...
Click to collapse
I can't seem to find any listing that would correspond to the phone under the Ports section :/
CVonV said:
I can't seem to find any listing that would correspond to the phone under the Ports section :/
Click to expand...
Click to collapse
Maybe upload a screenshot of the devices listing?
_Kuroi_ said:
Maybe upload a screenshot of the devices listing?
Click to expand...
Click to collapse
I thought it would've been listed in the Ports section but it's right at the top under "Android Device" as "Android ADB Interface". I believe I have the correct Qualcomm drivers installed.
Attached screenie also shows device not found when I try an "adb reboot" in command prompt.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hmm, I half expected it to be listed as QDLoader 9008, but then it would be under serial ports.
Try fastboot commands instead of adb and also try holding power + vol down for 10-15 seconds
Great guide @_Kuroi_ , I will be trying it out soon. The service rom you are using is pretty old. So I grabbed the last P update service firmware (WW-16.1220.1909.194) and the latest Q build I could get currently (WW-17.1810.2002.133). I have a subscription to one of the paid firmware sites for reasons like this. This way people have more options and it will simplify most people's updating because they can go from the new P service rom to any Q ota. Q firmware doesn't really make sense until it's not being updated anymore but it's here just in case someone finds it useful. If there is some incompatibility in the future or something that requires a newer update I will grab it then. If there isn't I will grab the last firmware once Q is stopped being updated.
WW-16.1220.1909.194
Here
WW-17.1810.2002.133
Here
WW-17.1810.2009.176
Here
Feel free to update your guide to incorporate these all I ask is a credit in the OP for providing it.
After running ./flashall.sh I get the following output:
Done.
target reported max download size of 805306368 bytes
File system type is raw !!!
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'userdata'...
OKAY ( 0.266s)
Sending 'userdata' (1888 KB)...
OKAY ( 0.067s)
Writing 'userdata'...
OKAY ( 0.003s)
Erasing 'metadata'...
OKAY ( 0.027s)
Finished. Total time: 0.799s
Rebooting...
(I changed square brackets to round brackets in the output because otherwise it wouldnt let me post this comment because of bbcode)
I don't seem to have a recovery partition by the end of it and "adb devices" doesn't show me anything.
Does anyone know what might have gone wrong?
*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people).
*** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. If you just ran a bunch of unknown commands, I would tell you to MSM.
*** Know how to use the MSMTool, Don't start before figuring it out. https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-glo-in.4272549/
*** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH ANY STEP DESCRIBED IN THIS GUIDE
General notes:
NR and LTE bands are read only and not modifiable, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
If you wish to unlock the bootloader without unlock_code.bin, you MUST do it from OOS11. If you upgrade to OOS12/OOS13, you will need the unlock_code.
The T-Mobile NON-HLOS is no longer necessary as of OOS13 release. If you must stay on OOS11 or OOS12, make a backup of the T-Mobile modem partition for the OOS version you want to stay on.
Dual-SIM does not work.
Prerequisites:
This conversion will not SIM unlock you. You can only SIM unlock on a T-Mobile ROM, meaning if you want to do that in the future, you must go back to a TMO ROM (and wipe)
Familiarity with MSMDownload tools. If the regular MSM tool doesn't work for you, turn back now.
Back up all data, it will be wiped.
Download:
Conversion: AndroidFileHost (MD5: 8cc3e5e81d15e28bb10dc5f1e7bd4133)
Steps:
Run the MSM file normally.
Unlock your bootloader if necessary. Now is the time if you don't have unlock.bin
Patch up to Android 13 while on Wifi if your mobile data doesn't work. Use this time to go to another variant (GLO, IN, etc) as needed.
Fastboot method:
* The steps in this guide will convert your TMO LE2127 to EU 11.2.3.3. This is intentionally not the latest version to force you to take a FULL OTA.
* You must already have the bootloader unlocked with an unlock_code.bin
* You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. No support will be given if you choose to manually do it.
* Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools. DO NOT USE MINIMAL ADB, it has not been updated for years.
* Fastboot can't see your device? https://forum.xda-developers.com/t/...stboot-mode-windows-10.4194491/#post-84943553
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.
Steps to convert your device to EU
You need your device bootloader and SIM unlocked. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
Download and unzip the conversion package:
EU 11.2.3.3
MD5: cb949816fa80d5f0d984359b819426c3
Boot to bootloader.
From adb:
Code:
adb reboot bootloader
From fastboot/bootloader:
Code:
fastboot reboot bootloader
Execute "flash_all.bat" from the unzipped directory from step 2.
Reboot into recovery, and wipe everything.
Once fully booted, connect to WiFi and download Oxygen Updater and take the FULL OTA (11.2.4.4 as of this writing)
Do a regular reboot, don't reboot to fastbootd, bootloader, recovery, etc. Reboot to system.
Reboot into bootloader or fastbootd, and flash the T-Mobile modem.
Code:
fastboot flash modem NON-HLOS.bin
After each Full OTA you take in the future, you will need to repeat step 7 & 8
FAQ
Q: The most recent version is 11.2.4.4, why is this guide converting to 11.2.3.3?
A: You didn't read the full post.
Q: Why is there no conversion to Global?
A: Global variant uses the Google incremental OTA server, and full OTAs are not always provided. There's no functional difference, and EU has better privacy requirements anyways. You can do it manually by extracting payload.bin and running the same flash script. No support will be provided if you choose to flash to Global.
Q: Can I re-lock the bootloader after conversion?
A: While you can go ahead lock your bootloader after conversion, I don't recommend it as you will not be able to take incremental OTA due to modem changes, and lose connectivity if you take a full OTA. To fix it, you need to unlock the bootloader and end up wiping.
Q: Where is the Linux guide?
A: Too lazy, if you're using Linux, you can make your own bash script from the Windows batch script.
Q: Help, I see is 'fastboot' is not recognized as an internal or external command.
A: Your fastboot.exe is not in your $PATH. You can either drop fastboot into the same folder as flash-all.bat, or you can fix your $PATH
Q: Help, I cannot boot to fastbootd because previous flashes messed things up.
A: MSM
Q: Help, "not enough space to resize [system, product, system_ext]"
A: MSM. If the error is on Vendor, it might still work and boot with a generic Android boot logo. If so, take the full OTA as described in the guide.
Q: Help, something went wrong!
A: Post in here the starting state of your device (Device model, ROM version, etc), all steps you've taken since unlocking bootloader, and the output of whatever is causing you trouble. Chances are, the answer is MSM, but read my MSM warning.
Q: Help, I see "Invalid sparse file format at header magic"
A: Ignore this message, not an error
Fixing the About Phone page
These steps are optional, and is only applicable for OOS11. It will fix the "About Phone" page. There are no performance differences. All that's done is change build.prop to reflect the correct model.
You need to rooted with Magisk
Download and install the magisk module: here
Reboot, the About Phone page is filled out.
Instructions to Bootloader Unlock a SIM locked device:
In ADB:
Code:
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
Reboot
Go to dev settings and enable OEM Unlock
Reboot to bootloader
Code:
fastboot oem unlock
No unlock.bin needed
Issues so far (please post if you run into more):
If your mobile data doesn't work on OOS13, PM me details including HW Revision in About Phone.
What appears to work:
Everything else.
Much appreciation for everyone that help develop and test
@razercortex
@retryfail
@amaroney55
I went straight to the 11.2.4.4 as well, instead of the 11.2.3.3. Probably why I had such an issue also. Dummy me, wanted the latest and greatest right away and paid the price for it.
Goodness man. Presently I see where I wrecked. I did the EU 11.2.4.4 and not the 11.2.3.3. much obliged for this and clearing that up. Likewise, thank you again for assisting me with saving my mobile. JBBattery
Woohoo! Thank you!!
for some reason my Wildvine downgrades to L3, not sure how to fix it, also as other post indicates, voice mail on dialer doesn't work
avid_droid said:
It says to have magisk hiding from Google play services. Have you done that?
Click to expand...
Click to collapse
Yes, I toggled all options under google play services, no luck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ok going to give this a go later fingers crossed and just to clarify i only need to backup ModemST1 and ModemST2 img correct?
avid_droid said:
Nope. TRied again and its a no go since every damn thing is failing. fastboot mode and fastbootd is constantly failing on every file thats being flashed. What you need from me.?
Click to expand...
Click to collapse
you mind pasting some errors here? maybe the 1st error you got from cmd
Ultraman666 said:
ok going to give this a go later fingers crossed and just to clarify i only need to backup ModemST1 and ModemST2 img correct?
Click to expand...
Click to collapse
Persist
avid_droid said:
Nope. TRied again and its a no go since every damn thing is failing. fastboot mode and fastbootd is constantly failing on every file thats being flashed. What you need from me.?
Click to expand...
Click to collapse
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.
Sounds like you tested that fastboot can't get you to fastbootd, but you continued anyways.
If you want troubleshooting, post the information I said to post
craznazn said:
Persist
Click to expand...
Click to collapse
Thanks for the hint, I backed up the persist.img but that's after root/unlock bl, so you are saying flash persist.img will get me back to L1?
avid_droid said:
everything fails in flashing. it just says FAILED on every .img that is being pushed. Im so confused. It says be in bootloader,but isnt it supposed to be in fastbootd???
Im still getting no response from fastboot reboot fastboot. Only way i can get into fastbootd is by adb reboot fastboot.
Which is it? in bootloader or fastbootd??
Click to expand...
Click to collapse
avid_droid said:
fastboot --version says unkown option
Click to expand...
Click to collapse
sounds to me like you don't get the proper version of fastboot, one thing to notice, if you install the one plus driver you may get the fastboot from C:\Android, DONT use this one. either put the correct platform-tool path to your $PATH or manually modify every fastboot.exe to be full path in script
sunxutian said:
Thanks for the hint, I backed up the persist.img but that's after root/unlock bl, so you are saying flash persist.img will get me back to L1?
Click to expand...
Click to collapse
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
craznazn said:
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
Click to expand...
Click to collapse
Yes, my safetynet passes and I do have magisk canary
avid_droid said:
I have it in C: and am opening powershell from that folder
Click to expand...
Click to collapse
Download a fresh copy of platform tools and unzip it into the folder that has flash_all.bat and .img files
craznazn said:
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
Click to expand...
Click to collapse
what I suspect might be wrong is when I did the BL unlock I use fastboot oem unlock while some people use fastboot flashing unlock (not sure this makes any difference or not)
I did oem unlock, shouldn't make a difference
From that folder, run fastboot --version and share the screenshot
craznazn said:
I did oem unlock, shouldn't make a difference
Click to expand...
Click to collapse
Then anything I can try?
sunxutian said:
Then anything I can try?
Click to expand...
Click to collapse
Hmm, also try the fix about page magisk module, shouldn't affect anything but you never know.
If that doesn't fix it, take the 11.2.4.4 OTA again via local update, and then lock the bootloader and check. You won't have a working modem but I want to make sure your wildvine keys are still there.