UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.
Related
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
AW: [Q] razr i problems - fastboot menu
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
xX_Alex_Xx said:
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
I am not able to do anything. if i scroll to any of the options on the menu as soon as i hit the volume up key it just returns a message advising the fastboot menu is disabled.
**edit
ah commands not menu options. not sure how i go about doing that. i am 100% new to droid...
ged flanders said:
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
Click to expand...
Click to collapse
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
AW: [Q] razr i problems - fastboot menu
If the solution from mervluk does not work (It didn't work for me either) , you should try if you are able to use the fast boot commands .
To do that simply connect your phone to the PC. Then download fast boot , if you do not already have that. It is in the .zip from the RAZR I root thread.
The go to the downloaded folder. There hold shift and perform a right mouse click. Then choose" start a command prompt here "or something similar (don't know how the option is called in English).
Then type in
fastboot reboot
When the phone reboots you might be able to unlock your phone and flash the software.
BUT BE AWARE! YOU WILL LOSE YOUR WARRANTY!!
So you better try the other solution first. This should be your last option.
If you don't know how to unlock the bootloader look in the RAZR I forum or pn me .
Alex
Sent from my XT890 using xda premium
mervluk said:
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
Click to expand...
Click to collapse
thanks buddy. i will give this a whirl and let you know how i get on. fingers crossed!
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
ged flanders said:
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
Click to expand...
Click to collapse
Glad about that. This phone can be a bit of a so-and-so. ics is being updated ota to Jelly Bean 4.1.2, which I've avoided so far to keep fm (although not activated on the supplied software). I did succeed with unlocking the bootloader (loose warranty - important) following the whole complicated procedure on Moto's website - but couldn't myself use the shortcuts on here. (Then had to set up again and re-download everything from the PlayStore). It required the Moto-supplied key. I then rooted, though I think the JB ota download unroots again? You can't use RSD lite with JB.
With JB the procedures are different, and a modified JB European (not for use with GB) firmware is now available on another thread which is impressing some posters. But I think just be a bit cautious as there does not appear to be any fix for the "service code corrupt" bootloader error yet. Looks like the options are very restricted whilst no-one understand the interaction between Google Android and the intel atom chipset.
I have a network unlock key from one of the commercial suppliers (cellunlocker.net), but haven't needed to try and use it yet!
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.
i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..
7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working
Or as bricked as these Qualcomm devices CAN be?
Hey all,
The TL;DR is basically where the list starts
I was running Blu's TWRP v45, the latest PureFusion, Blu's latest Custom kernel, had OB15 firmware underneath. I had been SO USED to simply downloading the newest firmware from kamilmirza's AFH page and just flashing it + it being totally fine that I did it without thinking for OB16. I wasn't too worried because about a week ago I had flashed the unofficial Oreo Lineage and it worked just fine! Plus, I just assumed if it died I could just restore a backup or re-flash the older OB. But as soon as I flashed the new firmware/modem by itself this time on an otherwise perfectly running device, I only saw the OnePlus splash screen. No booting, no access to recovery, no NOTHIN.
I tried flashing the beta TWRP version afterward via fastboot but no dice. Also tried temporary booting via fastboot to it, flashing Blu's again, booting to that. Everything the same result. Splash screen & nothing more. I then went to the extent of trying to format all the partitions and flash a boot.img or do a "-w update" or "flashall" command via fastboot. Because everything out in the universe is a recovery-flashable-zip, it seems like there's no way I can flash the necessary OTA stuff to bring it back to life!
My only remaining idea is getting this damn unbrick tool to work (duhh). I can see the Qualcomm HS-USB QDLoader 9008 in device manager after doing the Vol Up (only) and plugging the cable in. BUT the MSMDownloadTool just cannot see the device. Not in bootloader, not in the weird Vol-Up/cable state. [This is with Qualcomm drivers QUD.WIN.1.1 Installer-10037.3 Setup.exe, the official OnePlus drivers, ADB & Fastboot installed.]
Sorry for long explanation. In the end, what I'm left with is:
Blank formatted partitions (I hope... I'm not even positive they wound up formatted from the fastboot commands)
Fastboot is detected, but no ADB devices are found
Can get to bootloader, but nothing else
No recovery access - Flashing beta akhilnarang Oreo recovery does nothing. Flashing stock recovery does nothing. Flashing Blu_Spark recovery does nothing. (The fastboot commands succeed though each time somehow)
So far the only suggestion I've received is trying the MSMDownloadTool/unbrick process on another computer.
Does anyone have ANY ideas? From my experience, it seems like what might help me would be if a folder with the specific partition images existed for the OTAs, like how Google offers. (boot.img, recovery.img, user-data.img, system and so on). Am I wrong in thinking that? OnePlus has told me this simply does not exist and cannot give me anything like that (don't know why, when they already offer all the OTA flashables...)
PS - OnePlus support just absolutely refuses to even let me communicate to a "level 2" representative to ask a couple of the more technical questions about it. I can't understand why. They are insisting I start an RMA and send it for repair. They even initially scheduled a time for me to talk to higher level rep and then thought up a reason to cancel it via email an hour or so later...
Edit: Just in case the thread gets large and people don't read further posts, this is using:
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. Have the watermark bottom right of desktop
It's with the stock DASH cable
Tried multiple ports
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times
Tried starting the tool BEFORE the device is plugged in, as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
HOW IT GOT SOLVED:
At the end of the day, I had to fight and convince OnePlus support to grant me a remote session with Level 2 Support.
(Attached final image) These two password protected RAR files had almost identical tools as the Unbrick tutorial on XDA.
The major difference was that MSMDownloadTool was version 3.0.8 ***does anyone have this version??*** I can't get into these RARs. The 3.0 tool circulating did not work for me. We might need the newer version as time goes on?? Otherwise, the process was identical.
Unfortunately, the image they used was for 7.1.1. I had to unlock the bootloader and after doing that and getting OB15 & the RR build I wanted, etc, I then realized my phone was force-encrypted as well.
The only toolkit that worked for force decrypting once everything else worked was:
OnePlus_3_3T_5_64bit_TOOLKIT_by_Neisor
Finally, something like 3 clean flashes later, we Gucci.
Thanks for the attempted help to those that did! Hopefully this can help someone else.
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
As long as you can turn your phone off and on, it's doable. But you need to do that USB plugging + volume up thing while phone is totally off (you can hear Windows making bling when you connect it while pressing volume up, but phone itself stays screen off). And there shouldn't be anything on the screen before/while MSMtool do its job.
You can try different USB ports too.
Eremitus said:
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
Click to expand...
Click to collapse
Hahaha yes...... That's why I made this post though! It SEEMS like it should be possible to recover from this since fastboot commands + bootloader work! It SEEMED like it would be easy to recover from if anything went wrong... But, here I am.
Oh yeah forgot to mention ~
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. That part of the process went totally fine with BIOS and installing stuff, etc.
Also, shot in the dark but might @Funk Wizard have any ideas? Sorry to call out for this
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
btw, I messed up my phone in nearly similar case, flashing wrong firmware when using leaked H2OS ROM.
Eremitus said:
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
Click to expand...
Click to collapse
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
Hmm, ok.
Stock dash cable works, so that part is ok. Also usb3.0 ports should work too, atleast for me. So everything else seems to be ok except the MSMtool itself
Try different cable, bin there done that!!
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
I hope you find a solution, since my experience sounds similar to yours Ill share it and maybe you can find something to help out.
I was exactly where you are for about 3 hours last night.
Boot would always get stuck at the splash screen. Could boot into Fastboot, tried using the Skipsoft tool to fastboot flash a stock image but it kept failing.
As far as the Unbrick Tutorial goes, I know the first thing I kept messing up was thinking I needed to press the power button while holding the volume up and connecting to the PC
Also when I tried to manually update the driver on "Qualcomm 9088" it said it was already up to date.
Then I just ran the MSMTool it flashed 6.0.1 back on my phone and I was back in business.
Im sure this is the guide you followed: Here
I found another on the oneplus forums that is essentially the same but goes into a little more detail in the steps: Here
Since I was back completely Stock including Recovery I went ahead and sideloaded OB16 to get the firmware and modem then went about rooting, unencrypting etc...
Lost a few days worth of files but I'm back running LunuxOS Oreo right now.
Good luck I know how you feel. :good:
I've got it revived! I'll update OP. Sadly, it required OnePlus's intervention.
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
guilhermeferrari said:
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
Click to expand...
Click to collapse
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
purplepenguin said:
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
Click to expand...
Click to collapse
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
namefaisal said:
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
Click to expand...
Click to collapse
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Yeah, I got it open
purplepenguin said:
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Click to expand...
Click to collapse
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
New Files without Password
namefaisal said:
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
Click to expand...
Click to collapse
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
@Sam Nakamura
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
cdorrell12000 said:
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
Click to expand...
Click to collapse
You are most welcome.
Sadly everyone gets unbricked with these files but My device didn't. I have to send the device to the service center now. It seems my case is a hardware issue. Tough luck
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
thanks a lot saved my day !!
purplepenguin said:
@Sam Nakamura
Click to expand...
Click to collapse
Sorry, I just saw your mentioning somehow I missed it, happy you got your phone back already, unfortunately not independent for big OP, did you guys already share this new 3.08 MSM-download-tool to the well established threads or did you I missed this too? This information and according files should be shared with the community and easy to find for those poor souls who unintentionally killed their beloved device...
---------
Edit: further sharing isn't necessarily needed, you did already a pretty good job by naming the thread and describing the situation thoroughly, only suggestion could be to link the updated MSM-download-tool download to the first post with some hint, just an idea though...
Cheers
Sent from my OnePlus 3T using XDA Labs
Hello guys,
Is it possible to flash anything to the Redmi 4X Global if the bootloader is locked? Perhaps using fastboot, Mi Flash Tool or some unofficial tool I don't know about? Maybe using the device's IMEI numbers and SN? Just shooting in the dark here.
My situation:
Locked Mi account, credentials unknown. Want to reset.
Details:
A relative of mine works at a store that sells smartphones. Boss rarely bothers sending defective devices for repairs and often gives them to employees instead. A customer brought this device back because some of the pixels on the screen are dead. He said he had performed a factory reset on the phone. They gave him a new one and handed the "defective" one to my relative who noticed the Mi Account Locked thing upon booting. When I got the device yesterday, the battery was dead. I charged it a little bit and when it turned on, it went through the setup normally, I was able to use the device without issues for 30 seconds or so (!), THEN it locked me out! That makes me think that if I let the battery go down to 0 and wait before charging and turning it back on, that will give me enough time to go to developed options and turn on OEM unlock and USB debugging (which needs a SIM card I think for some reason but OK). Then I may be able to unlock it; but that requires a lot of waiting and is unlikely to work anyway.
If you have an FRP locked Samsung phone, you just flash the stock ROM through Odin and it's as good as new. But Xiaomi locks everything down so tightly, there isn't even a download mode (just reboots to system if I choose "download" on the recovery menu)!
Wondering if there's any way to bypass all this? I don't mind the risk of bricking it cause it's useless as it is. Opening the device's back and tinkering is not an obstacle either :good: In all honestly, I understand Xiaomi does this for security (although if Samsung doesn't do it, I'm not sure why Xiaomi even bothers) and it would make me feel better knowing if someone stole my locked Xiaomi phone, they wouldn't be able to use this, but at the moment it's simply frustrating. I also know that officially unlocking the bootloader often doesn't even work, gets stuck or you never get an unlock code (personal experience with broken Xiaomi unlocking system)...
Any info appreciated. Thanks in advance.
i have a bootloader locked redmi x4 and wanted to take its original firmware backup (requires edl-mode) before unlocking/rooting/tinkering the device (i always do this with all my devices), tried every possible solution (except test point) but couldn't succeed.
You can try with deep flash cable or patched fastboot if your x4 has an old firmware...
And as per my knowledge, shorting test points is the only solution for new/updated xiaomi devices to open edl-mode now, only then you can reflash it... Good luck...
if you find any other solution, please share. As currently i have to wait for 3 days before i can unlock my x4...
Sent from my ONE 3G HD using Tapatalk
So, I Googled the Test Point method and it worked like a charm! :laugh: Thanks for the info!! :good:
Basically you open the phone's back, you unscrew a small metal plate and then you have access to 2 tiny dots, the "test points", which apparently are built exactly for such purposes.
Instructions:
You unplug the battery (and the display I think although once it worked with the display plugged so don't take my word for it), temporarily connect the test points with a pair of tweezers or a paperclip ?, while the test points are connected you plug the phone to the PC and it miraculously shows up in device manager under "ports" as "Qualcomm 9008"! (Qualcomm drivers need to be installed. If it shows up as "diagnostics..." anything, you did something wrong).
The device is flashable in that state, you use XiaoMiFlash to flash a stock ROM (it's a folder that contains a folder named "images". The flash tool doesn't have you selecting specific files to flash, you need to select the whole images folder).
Pictures attached.
Left: the screws you gotta unscrew
Right: the test points and what you need to unplug
PS on opening the back: insert a flat narrow tool (best to have a smartphone repair kit) where the back plate connects with the front part of the phone (NOT where the glass meets the rest of the device). At first it won't go in but be persistent and patient, eventually it it. Wobble it back and forth and go slowly around the whole device the same way, paying attention not to wound the parts under the side buttons. Once you do that, it'll be possible to remove the back with your hands. Don't yank it because you need to carefully unplug the tape connecting the fingerprint sensor to the motherboard first
Or just wait a couple of days when you ask for a unlocked bootloader
Whatever floats your boat
Mister Advance said:
Or just wait a couple of days when you ask for a unlocked bootloader
Whatever floats your boat
Click to expand...
Click to collapse
Hi, I don't think you actually read the post. The device I got was completely locked, not just the bootloader. There was no way to remove the Mi account. Since the device does not normally have a download mode, there was no way to flash the stock firmware in order to factory reset it. The only way that I know of now, is what I did and described above
bi11ie said:
Hi, I don't think you actually read the post. The device I got was completely locked, not just the bootloader. There was no way to remove the Mi account. Since the device does not normally have a download mode, there was no way to flash the stock firmware in order to factory reset it. The only way that I know of now, is what I did and described above
Click to expand...
Click to collapse
Whoops, sorry read it to fast i gues then yeah xD
I already found it a weird solution to unlock a bootloader
Don't mind me pls
bi11ie said:
So, I Googled the Test Point method and it worked like a charm! :laugh: Thanks for the info!! :good:
Basically you open the phone's back, you unscrew a small metal plate and then you have access to 2 tiny dots, the "test points", which apparently are built exactly for such purposes.
Instructions:
You unplug the battery (and the display I think although once it worked with the display plugged so don't take my word for it), temporarily connect the test points with a pair of tweezers or a paperclip , while the test points are connected you plug the phone to the PC and it miraculously shows up in device manager under "ports" as "Qualcomm 9008"! (Qualcomm drivers need to be installed. If it shows up as "diagnostics..." anything, you did something wrong).
The device is flashable in that state, you use XiaoMiFlash to flash a stock ROM (it's a folder that contains a folder named "images". The flash tool doesn't have you selecting specific files to flash, you need to select the whole images folder).
Pictures attached.
Left: the screws you gotta unscrew
Right: the test points and what you need to unplug
PS on opening the back: insert a flat narrow tool (best to have a smartphone repair kit) where the back plate connects with the front part of the phone (NOT where the glass meets the rest of the device). At first it won't go in but be persistent and patient, eventually it it. Wobble it back and forth and go slowly around the whole device the same way, paying attention not to wound the parts under the side buttons. Once you do that, it'll be possible to remove the back with your hands. Don't yank it because you need to carefully unplug the tape connecting the fingerprint sensor to the motherboard first
Click to expand...
Click to collapse
Hi, you were using miui 8 or 9 when you used the test point method?
uts58 said:
Hi, you were using miui 8 or 9 when you used the test point method?
Click to expand...
Click to collapse
Oops, forgot to mention..
MIUI 8
I don't think it makes a difference though. The test points are a hardware thing.
Locked bootloader and phone bricked
Hi,
I have a locked redmi 4x device which cannot boot to system. I can only boot to fastboot or to stock recovery. Since the bootloader is locked, I cannot flash TWRP or any rom. I have tried to apply for unlock permissions from xiaomi at http://en.miui.com/unlock/
but the link is greyed out for me. (screenshot attached)
Please let me know if there is a way to unlock my bootloader without the test points method. Thanks.
Your doing correct
Go ahead
Try using the Test Point, i use that to flash my new Redmi 4X from chinese version to global version.
Did it work?
bi11ie said:
Oops, forgot to mention..
MIUI 8
I don't think it makes a difference though. The test points are a hardware thing.
Click to expand...
Click to collapse
Thank you man!
fluster84 said:
Hi,
I have a locked redmi 4x device which cannot boot to system. I can only boot to fastboot or to stock recovery. Since the bootloader is locked, I cannot flash TWRP or any rom. I have tried to apply for unlock permissions from xiaomi at http://en.miui.com/unlock/
but the link is greyed out for me. (screenshot attached)
Please let me know if there is a way to unlock my bootloader without the test points method. Thanks.
Click to expand...
Click to collapse
Hi, as far as I know, there is no other way. The test points are there exactly for cases like yours and mine, where you need to restore a device to factory defaults. There's no reason not to try it. If you are careful, you won't damage the phone and it won't even show that you opened it.
Hi,
I restored santoni 8.2.8 in EDL mode but bootloader is still locked, did I miss an important step?
best regards
Sorry for pulling an old thread but I was wondering if this solution would work in Redmi Note 3SD as I am facing the same problem i.e. locked bootloader and no option to enter developer options for turning on debugging options
I have the same issue
bi11ie said:
So, I Googled the Test Point method and it worked like a charm! :laugh: Thanks for the info!! :good:
Basically you open the phone's back, you unscrew a small metal plate and then you have access to 2 tiny dots, the "test points", which apparently are built exactly for such purposes.
Instructions:
You unplug the battery (and the display I think although once it worked with the display plugged so don't take my word for it), temporarily connect the test points with a pair of tweezers or a paperclip , while the test points are connected you plug the phone to the PC and it miraculously shows up in device manager under "ports" as "Qualcomm 9008"! (Qualcomm drivers need to be installed. If it shows up as "diagnostics..." anything, you did something wrong).
The device is flashable in that state, you use XiaoMiFlash to flash a stock ROM (it's a folder that contains a folder named "images". The flash tool doesn't have you selecting specific files to flash, you need to select the whole images folder).
Pictures attached.
Left: the screws you gotta unscrew
Right: the test points and what you need to unplug
PS on opening the back: insert a flat narrow tool (best to have a smartphone repair kit) where the back plate connects with the front part of the phone (NOT where the glass meets the rest of the device). At first it won't go in but be persistent and patient, eventually it it. Wobble it back and forth and go slowly around the whole device the same way, paying attention not to wound the parts under the side buttons. Once you do that, it'll be possible to remove the back with your hands. Don't yank it because you need to carefully unplug the tape connecting the fingerprint sensor to the motherboard first
Click to expand...
Click to collapse
Hey, so I have the same issue.. Redmi 4x boots into the boot screen all the time.. Bootloader is locked so I can't flash a ROM from Fastboot. I found a solution wherin I require to use a Deep Flash Cable so as to flash a stock ROM. I just ordered one and am planning to try that. Do you think that method would work as well? .... After reading your post I tried opeing up the phone... but one of the screws is so messep up it just isn't unscrewing!
So my question, is the Deep Flash Cable method legit ?
---------- Post added at 01:57 PM ---------- Previous post was at 01:47 PM ----------
sambau5 said:
Hey, so I have the same issue.. Redmi 4x boots into the boot screen all the time.. Bootloader is locked so I can't flash a ROM from Fastboot. I found a solution wherin I require to use a Deep Flash Cable so as to flash a stock ROM. I just ordered one and am planning to try that. Do you think that method would work as well? .... After reading your post I tried opeing up the phone... but one of the screws is so messep up it just isn't unscrewing!
So my question, is the Deep Flash Cable method legit ?
Click to expand...
Click to collapse
Alrternate method found:
#1 To enter EDL mode (also known as Download mode) :
Make a 'Deep Flash Cable' by short-circuiting the 'Green' and the 'Black' wire inside the USB cable. I would better recommend you to buy a quality thick USB cable from a local store and tell the guy to cut open the cable and solder the green and the black wire to a small switch.
Now, power off your device and yes, make sure it's powered off. (In case the device is not getting powered off, see the images below for disconnecting and reconnecting the battery connector.)
If Windows 10 or 8/8.1, press 'Shift' key while restarting your computer. Now, go to Advanced settings - Startup Settings - Reboot, and if on Windows 7, reboot your PC and press F8 key before the Windows startup icon appears.
Now, select 'Disable Driver Signature Enforcement' from the list.
Connect the cable to your phone and pressing the switch, connect the cable to your PC. Your phone should not show as charging. Being sure that it's not charging, release the switch. You should now see your device recognized as 'Qualcomm QLoader 9008' under Device Manager. Voila ! You are on EDL mode.
Link for making your own Deep Flash cable : https://www.youtube.com/watch?v=hmdrj4uX7gY
#2 To flash official MIUI ROM :
Download the fastboot ROM for your device, and download the latest Mi Flash tool from http://api.bbs.miui.com/url/MiFlash
I would recommend downloading the fastboot ROM with a separate download manager. Internet Download Manger - Recommended (https://www.internetdownloadmanager.com/download.html)
Also install 7Zip and WinRAR from https://ninite.com/
Now, first extract the fastboot ROM file with WinRAR and then re-extract it from the extract folder with 7Zip, and shorten the file names.
Having installed Mi Flash tool along with all its drivers ( I mean the popups asking for installing driver while installing Mi Flash), run it and select 'Clean all' from the bottom-right side.
Click 'Refresh' and it should show as 'COM10' or something similar. Now, click 'Flash'. And yes, that's it.
After successful flash, disconnect it from the cable and boot it up by pressing the Power key until it vibrates and turns on.
Yeah, you DID IT
*Why a download manager ? I had downloaded the file with Chrome and Firefox (without even pausing it), but even after successful flash, the phone does not boots into MIUI. It gets stuck on the MI logo. However, on using a download manager, the boot successfully completes without any hassle. I have used several download manager, but only IDM downloads the file with .tar extension which always and YES, ALWAYS results in successful flash. You can try out a different method but I would recommend you to play safe as my method is FOOLPROOF.
I have try this method before, but unfortunately it doesnt work. When i connecting those 2 pins, there are nothing changed in my device manager. No new hardware founds at all. I Have install these drivers too, no luck
---------- Post added at 03:45 AM ---------- Previous post was at 03:42 AM ----------
meltbanana said:
Hi,
I restored santoni 8.2.8 in EDL mode but bootloader is still locked, did I miss an important step?
best regards
Click to expand...
Click to collapse
Flahing ROM didn't unlock your bootloader bro. Its just a way to migrate from somehow global rom into dev rom. UBL is kind of different things
Hello
i've bought a used phone, and the device is locked (MIUI10) with the MI account of the first owner. The bootloader is locked.
If i try to flash ROM in EDL mode, is the MI account of the first owner will be delete ??
Thanks
conduisant said:
Hello
i've bought a used phone, and the device is locked (MIUI10) with the MI account of the first owner. The bootloader is locked.
If i try to flash ROM in EDL mode, is the MI account of the first owner will be delete ??
Thanks
Click to expand...
Click to collapse
Yes, it should be.
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?