Related
Hello I'm here to show how to Unlock and root your FIGO M405B Dual sim any carrier cheapo 40$ or lower phone mine was free in this case!:good:
If you have not already please get ADB and Fastboot install I shall refer you to this page
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
~~~BOOTLOADER UNLOCKING~~~
WARNING THIS CAN AND WILL DELETE YOUR CURRENT SETTING FILES AND OTHER CANDIES YOU PREVIOUSLY INTSTALLED MAKE SURE TO BACKUP
Now you will need to enable dev options you should already know how to do this and also enable bootloader unlocking and debug mode
Second you will need to power off your device once it's off hold the Vol+ and plug your USB cable in it should take you to an boot selection screen use your Vol+ to select Fastboot and open up CMD and type "fastboot oem unlock" select Yes on your phone
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~Rooting~~~~~
To root your device get King root android version Here https://kingroot.net/ follow the instructions
Now to remove the KingRoot SuperUser I'd recommend using Super-Sume Pro It's only 4 bucks and you can even refund it right after this will give you good old SuperSU without the crap KingRoot has
Super-Sume Pro Link :: https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
~~~~~~~Custom Recovery~~~~~~~
Me My self am working on porting a copy to this phone if you find a copy that works let me know and and I'll add the Instructions here
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Radio : Coming Soon
MI Flash : http://bigota.d.miui.com/tools/MiFlash2018-5-28-0.zip
Firstly we download this rom : https://drive.google.com/drive/folders/16lQ-A175D_5DJU-YT4lbul5htgaNNw21
Then we take the device into EDL Mode and install Rom.
After installing the ROM, install the device again in EDL Mode.
We are putting rawprogram0.xml into the AntiTest folder.
rawprogram0.xml "https://drive.google.com/open?id=1TNlPjMTkyh7urJiRV9egzLnzDr27dlOL"
We are installing from MiFlash "clean all in a selected" way again.
Good luck when the device is opened Fake UBL will be removed wait 720 hours and the bootloader will be unlocked
Wow how did you come up with this? Seems persist.img contains the bootloaders unlock/lock status. Great.
Maybe you could just replace the rawprogram0.xml on the anti_test_note5 images folder with this
http://www.mediafire.com/file/btd8ddid8dbn3tc/rawprogram0.xml/file
I enabled persist.img on the default rawprogram0.xml so that you could just flash it once on miflash and not doing it twice.
devcon69 said:
Wow how did you come up with this? Seems persist.img contains the bootloaders unlock/lock status. Great.
Maybe you could just replace the rawprogram0.xml on the anti_test_note5 images folder with this
http://www.mediafire.com/file/btd8ddid8dbn3tc/rawprogram0.xml/file
I enabled persist.img on the default rawprogram0.xml so that you could just flash it once on miflash and not doing it twice.
Click to expand...
Click to collapse
persist.img has been known currently to contribute to several "curse" (s) those occured when you buy RN5 whyred China version which has been flashed to Global. Probably the seller broke this partition when trying to unlock the phone (carrier bundling unlock).
The curses come in different flavors :
1. OIIMIFA (correct one is OEIMIFA), no matter what you flash, using recovery/fastboot, it will stay as OIIMIFA. This is the earliest curse, at that time, still no ARP yet.
2. Fake ROM, overlay on top say it is unofficial ROM
3. Sensor not functioning, all accelero, compass, gyro and other sensors seems to be totally broken
4. Many other variant, such as OEIMIFA 9.5.17.0.0 (5 digit version); 9.5.6.0 but ROM show MIUI 10 interface (possibly already anti 4, but show anti 3 version ROM); 9.5.19.0 but still anti 3 (probably seller flash using firmwareless, my guess); JIAMIFA and many more. They keep evolving by natural selection :LOL
5. The worst of all the curses is the Fake UBL. Since all above can be cured easily by flashing persist.img, if it is UBL ready. But fake UBL get locked out, status show unlocked, no way to bind account, but it is still locked out in fastboot.
That's why the solution is to flash persist.img. AFAIK, it is not flashed by default. That's why during OIIMIFA curse, when users try so many fastboot ROM, nothing changed (because persist.img is not flashed)
Desmanto said:
persist.img has been known currently to contribute to several "curse" (s) those occured when you buy RN5 whyred China version which has been flashed to Global. Probably the seller broke this partition when trying to unlock the phone (carrier bundling unlock).
The curses come in different flavors :
1. OIIMIFA (correct one is OEIMIFA), no matter what you flash, using recovery/fastboot, it will stay as OIIMIFA. This is the earliest curse, at that time, still no ARP yet.
2. Fake ROM, overlay on top say it is unofficial ROM
3. Sensor not functioning, all accelero, compass, gyro and other sensors seems to be totally broken
4. Many other variant, such as OEIMIFA 9.5.17.0.0 (5 digit version); 9.5.6.0 but ROM show MIUI 10 interface (possibly already anti 4, but show anti 3 version ROM); 9.5.19.0 but still anti 3 (probably seller flash using firmwareless, my guess); JIAMIFA and many more. They keep evolving by natural selection :LOL
5. The worst of all the curses is the Fake UBL. Since all above can be cured easily by flashing persist.img, if it is UBL ready. But fake UBL get locked out, status show unlocked, no way to bind account, but it is still locked out in fastboot.
That's why the solution is to flash persist.img. AFAIK, it is not flashed by default. That's why during OIIMIFA curse, when users try so many fastboot ROM, nothing changed (because persist.img is not flashed)
Click to expand...
Click to collapse
Good. Nice to know man. Thanks for the detailed info.
[ask] Verified me account.
Hi,
I'm stuck with this fake UBL thing for quite a while now, and haven't found any solution.
Does it need verified / bind Mi account when doing the flashing part ? (the first and second time)
StracerX said:
Hi,
I'm stuck with this fake UBL thing for quite a while now, and haven't found any solution.
Does it need verified / bind Mi account when doing the flashing part ? (the first and second time)
Click to expand...
Click to collapse
have you disconnected your battery with pull up battery socket and entering edl mode?
anugrahlando said:
have you disconnected your battery with pull up battery socket and entering edl mode?
Click to expand...
Click to collapse
I haven't done it with the files provided within this thread. I would like to know if the flashing process needs a mi account because i haven't got one that bound to a ReN 5.
If the flashing process doesn't need one, I think I would like to give it a shot.
StracerX said:
I haven't done it with the files provided within this thread. I would like to know if the flashing process needs a mi account because i haven't got one that bound to a ReN 5.
If the flashing process doesn't need one, I think I would like to give it a shot.
Click to expand...
Click to collapse
if you flash in edl mode with battery disconnected it wouldnt ask you to authorized mi acc
Is it a must to remove battery? I'm not familiar with dismantling the hardware so juz trying to avoid.
anugrahlando said:
if you flash in edl mode with battery disconnected it wouldnt ask you to authorized mi acc
Click to expand...
Click to collapse
Thanks for the info, I think I will give it a shot.
Pinage said:
Is it a must to remove battery? I'm not familiar with dismantling the hardware so juz trying to avoid.
Click to expand...
Click to collapse
Yes, because to access the test point to enter the edl mode as discussed, you would have to open the back case and unscrew some panels covering it.
I found it quite a hassle the last time i tried to do it, especially when opening the hard back case.
UtkuAblak said:
MI Flash : http://bigota.d.miui.com/tools/MiFlash2018-5-28-0.zip
Firstly we download this rom : https://drive.google.com/drive/folders/16lQ-A175D_5DJU-YT4lbul5htgaNNw21
Then we take the device into EDL Mode and install Rom.
After installing the ROM, install the device again in EDL Mode.
We are putting rawprogram0.xml into the AntiTest folder.
rawprogram0.xml "https://drive.google.com/open?id=1TNlPjMTkyh7urJiRV9egzLnzDr27dlOL"
We are installing from MiFlash "clean all in a selected" way again.
Good luck when the device is opened Fake UBL will be removed wait 720 hours and the bootloader will be unlocked
Click to expand...
Click to collapse
Confirmed working with a bit of tinkering for:
redmi note 5, internal 64gb, ram 4 giga, red box, rear camera 12mp+5mp
my experience:
1. Enter EDL mode - Battery plugged in
2. Flash Anti ROM with original rawprogram0.xml (I accidentally chose clean and Lock)
3. unplug the phone, and replace rawprogram0.xml with the patched version (persist only )
4. Enter EDL Mode again, flash ROM clean mode. This time, the flasher app only flashed persist.img. Finish a lot quicker
5. unplugged the phone - disconnect the battery (lazy me)
6. Turn on phone - Automatically Enter Mi Recovery 3 - Said MIUI Rom not compatible, FAILED
Then...
7. Download Fastboot ROM from : https://en.miui.com/thread-2340434-1-1.html
8. I chose latest fastboot ROM: http://bigota.d.miui.com/V10.0.2.0....EICNFH_20180918.0000.00_8.1_cn_7af050826b.tgz
9. Extract the ROM, then replaced Firehose file from this: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
Repeat step 1 to 6, this time , for the China Stable ROM
Again Stuck in Recovery...BUT... I waited..and the phone restart by it self, and after a very long boot, The phone finished boot
SUCCESS!
Then...
Binding device to Mi account, SUCCESSS
Power off phone, enter fastboot
Trying to unlock using mi unlock, FAILED
NO PHONE NUMBER ASSOSIATED
Login to : https://account.xiaomi.com/ and complete the data
Then RE Unlock
FAILED AGAIN, I have to wait 360 hours since the last unlock attempt
No problem, I can wait ,
I'm Relieved.... FAKE UBL IS GONE
This Miui Version can't be installed
I follow your step, but when i turned on the phone, it boot into recovery mode "this MIUI version can't be installed on this device"
Please help.
Thank you
dedieko said:
Confirmed working with a bit of tinkering for:
redmi note 5, internal 64gb, ram 4 giga, red box, rear camera 12mp+5mp
my experience:
1. Enter EDL mode - Battery plugged in
2. Flash Anti ROM with original rawprogram0.xml (I accidentally chose clean and Lock)
3. unplug the phone, and replace rawprogram0.xml with the patched version (persist only )
4. Enter EDL Mode again, flash ROM clean mode. This time, the flasher app only flashed persist.img. Finish a lot quicker
5. unplugged the phone - disconnect the battery (lazy me)
6. Turn on phone - Automatically Enter Mi Recovery 3 - Said MIUI Rom not compatible, FAILED
Then...
7. Download Fastboot ROM from : https://en.miui.com/thread-2340434-1-1.html
8. I chose latest fastboot ROM: http://bigota.d.miui.com/V10.0.2.0....EICNFH_20180918.0000.00_8.1_cn_7af050826b.tgz
9. Extract the ROM, then replaced Firehose file from this: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
Repeat step 1 to 6, this time , for the China Stable ROM
Again Stuck in Recovery...BUT... I waited..and the phone restart by it self, and after a very long boot, The phone finished boot
SUCCESS!
Then...
Binding device to Mi account, SUCCESSS
Power off phone, enter fastboot
Trying to unlock using mi unlock, FAILED
NO PHONE NUMBER ASSOSIATED
Login to : https://account.xiaomi.com/ and complete the data
Then RE Unlock
FAILED AGAIN, I have to wait 360 hours since the last unlock attempt
No problem, I can wait ,
I'm Relieved.... FAKE UBL IS GONE
Click to expand...
Click to collapse
I follow your steps, but it always end up in ACK could not match.
My bootloader is blocked and for my luck with no account linked, so i can't unlock BL.
Anyone know how fix this problem?
I've just got Realme GT2 PRO (RMX3300) (China ROM) and I need to flash the global ROM on it. but with all of my knowledge and hours and days wasted trying to flash the global ROM I am still unable to.
my main problem is that the phone doesn't have fastboot or bootloader !!!, I honestly never seen a phone that doesn't have a bootloader, and accessing it is necessary to flash a ROM or Unlocking the bootloader
here are some of the things i tried:
1- turning off the phone then holding the VOLUME DOWN and POWER BUTTON (AS SHOWN IN THE PICTURE) only puts me in recovery mode
2- using commands such adb reboot bootloader just restart the phone and shows a weird Chinese text for a split second (AS SHOWN IN THE VIDEO)
3- tried installing DEEP TESTING app but it gives me this error (AS SHOWN IN THE PICTURE)
I am honestly very desperate at this point and I am willing to pay anyone who manages to fix this issue
Tl;dr : can't go into bootloader/fastboot
Mr.pizza said:
my main problem is that the phone doesn't have fastboot or bootloader !!!, I honestly never seen a phone that doesn't have a bootloader, and accessing it is necessary to flash a ROM or Unlocking the bootloader
Click to expand...
Click to collapse
Each computer so also every Android phone ( regardless of brand / model ) has a bootloader. Whether Google's Fastboot tool is supported or not on Android phone depends on brand / model: e.g. Samsung does NOT support it whereas Realme does.
See also here:
How to Unlock Bootloader of Realme GT2 Pro? – (Easy Method)
Do you want to Unlock the Bootloader of Realme GT2 Pro? We have shared the Easiest Method.
androidcatch.com
My Xiaomi Redmi Note 8 Pro isn't booting anymore.
I'm stuck in the fastboot screen, I don't even reach the redmi logo in the boot, I need to recover the data on the phone but I have no idea about how to do that.
Any suggestions?
(Already tried going to recovery with power down + volume up, isn't working)
I'm stuck in the fastboot screen
Click to expand...
Click to collapse
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.
OldNoobOne said:
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.
Click to expand...
Click to collapse
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.
BrickedXiaomi said:
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.
Click to expand...
Click to collapse
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok
OldNoobOne said:
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok
Click to expand...
Click to collapse
I'll try tomorrow, thanks for all the precious details btw!
Just a question, shouldn't I unlock the phone with mi unlocker before that?
BrickedXiaomi said:
Just a question, shouldn't I unlock the phone with mi unlocker before that?
Click to expand...
Click to collapse
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.
OldNoobOne said:
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.
Click to expand...
Click to collapse
As said, I never modified this phone, is basically as if it was brand new, OS side.
Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?
BrickedXiaomi said:
Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?
Click to expand...
Click to collapse
Wow thats great link, I hope it works so you don't lose data.
The link is fresh so you can also ask there. All the Best
Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?
BrickedXiaomi said:
Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?
Click to expand...
Click to collapse
Is your phone In-Warranty? If yes or no i would suggest go your own way, once purchased an used any device, don't connect with OEM servers ever again for any OTA update coz lots of recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates and after that the phone doesnt boot, no recovery no fastboot too, so careful with contacting/updating through OEMs if out -of-warranty specially. Once out-of-warranty always use ROM channels to upgrade to new handroid versions instead of direct OTA upgrade/update, that way you may still be able to roll back the OS to previous version in case you don't like the new handroid version, lots of people don't like handroid 12 but they cant roll back to handroid 11 .
> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.
BrickedXiaomi said:
> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.
Click to expand...
Click to collapse
Yes they might not try doing that with uropean customers but they might try in other countries where there no proper legal system for things like these, also they wont do it with everyone in a particular country to avoid suspicion, theyre smart enough to know what theyre doing, but unofficially speaking many retailers have told me about such a thing (OTA Kill Device) happening in Weaker-Law-N-Order countries, so just saying precaution is always good.
BTW i've put my Retmi Noat 10 up for sale, its still in warranty & I havent used it in the last 10 months, no sim card, unused totally, just once I loaded Gcam to check how the camera is, shamshung is always better than chyneez phones mainly coz better build and component-life, chyneez devices only look shiny from outside but it doesnt last beyond 3-5 yrs, not built to last, just use-n-throw devices u knw. Such devices are only made for mass-surveillance in mind not with customers-focus. This A/B partition thing and super partition thing is adding more bad than good.
I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded* to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup off your device in preloader mode (SLA/DAA bypass and VCOM drivers needed)
After that important step you can unlock bootloader with mtkclient, install TWRP and *proof me wrong (xiaomi devices are hackable/have weak security implementations). In any case do not perform factory reset, your backup is always only backup of android OS and therefore incomplete (there are several OS on every device)
btw fastboot doesn't require usb-debugging (that's adb, not fastboot)
Do you have a tutorial about it?
aIecxs said:
I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup of your device in EDL mode (patched firehose programmer and deep flash cable needed)
Click to expand...
Click to collapse
yes:
my desktop (cause im in bootloader mode i'll need to use it) is artix linux with kde. sadly i cant install on it adb/fastboot and other drivers due to lack of systemd and empty repos so will do it probably from a random linux-based bootable usb...
my mobile is (as was in title) - xiaomi redmi go - european version.
what means ? my mobile have encryption after removing system what makes me unable to boot things... for the now i can still boot stock ROM. although i wanted to remove all associations with google in system (all google apps, bugs caused by removal etc...)
any ideas what i should do with it? wanna have it to tomorrow cause we use our mobiles at work and my current mobile got "marked as over outdated" by boss so i cant use
why noone ?
This same things happen with me also but You need a USB cable to connect your phone to PC. You need to download ADB and Fastboot Tools to your PC and Extract it First of all, you need to enable the developer option and activate the USB debugging on Xiaomi Redmi Go. Now activate the OEM unlock status on your Xiaomi Redmi Go DinarGuru.com
Christinakim said:
This same things happen with me also but You need a USB cable to connect your phone to PC. You need to download ADB and Fastboot Tools to your PC and Extract it First of all, you need to enable the developer option and activate the USB debugging on Xiaomi Redmi Go. Now activate the OEM unlock status on your Xiaomi Redmi Go
Click to expand...
Click to collapse
this i actually know. i have one heavily modded lg so im not a newbie. its more about "encryption unsuccesful" broked roms leading to non-booting state (bootloop) etc... nothing from xda surely doesnt work, yep
surely nothing from : https://forum.xda-developers.com/m/techyminati.8245761/ works. was trying loads of times always bootloop. recovery posible to load but then tends to not make factory reset and lock in "encryption unusccesful", and thats worst... im in europe but have global version btw...
dead chat ?