Related
hi guys, i have the X722, i can use ROMs of X727 and X720?
No the x722 has no custom ROMs. You'll soft brick the phone if you try to load any ROMs from other variants onto it, to my knowledge.
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
I also soft bricked my Le Eco Pro 3
vsrocha said:
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
Click to expand...
Click to collapse
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
For anyone else reading this post : don't trust every comment here. Some people will give incorrect or incomplete info, such as advice to wipe the system to get around encryption.
* That's what I did and after successfully unlocking the boot-loader, I find that my system was somehow encrypted.. I did not encrypt my phone so I am not sure how this happened. In my haste, I did not create a recovery, I thought that is what the official Leeco twrp was for?
Options?
I too read about the Qfil tool, at the time I was having trouble downloading the files so I attempted to wing it... and failed.
I see now that I did not spend enough time on this complex option.
Update:
here is the exact instructions for using the Qfil method. ( this link provides step by step, and is tedious, but appears to work.
Sigh! I attempted to post a link and could not, due to being new on this site.
No doubt, I found the best instructions that I have seen yet on the Qfil Process.
Its on the unoffical Leeco Repair site : tora33 #comment-15320 this post is much more extensive than some other posts by Tora33 linked from XDA
Again, I can't post the actual link here! Just search for : unoffical Leeco Repair site : tora33 #comment-15320
Potential other options
J tag brick repair service website : brickedmyphone they charge $45 to repair a bricked phone.[/U
[*] This video seems very promising! Unfortunately, I wasn't able to find this video before now.
Since I am new here I am not allowed to help you by posting links!
search YouTube for How to unbrick any bricked letv phone without loosing data ( easiest way ) in Hindi.
Yes its in Hindi, but you will still understand because he used some English and it seems that he has built a fairly useful tool. Although, its still easy to get the gist of what he is telling us and he apparently built a program to repair a bricked Leeco phones, and he has other videos
[*] Finally Google : LeEco X820 Max 2 Super Unbrick Guide ( gizmochina. website) seems to be another complete solution.
I hope this helps you!
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
https://www.youtube.com/watch?v=m0o4QtNXljg
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
tsongming said:
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
Click to expand...
Click to collapse
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
sk8223 said:
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
Click to expand...
Click to collapse
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
tsongming said:
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
Click to expand...
Click to collapse
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
sk8223 said:
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
Click to expand...
Click to collapse
Thank you for you very good detailed advice. Its truly appreciated.
I was decrying the shop ROM a lot but it's okay. I thought it'd be a lot worse than it is, but at least it lets me play the games I want to play on it without issue (so far...). I'm debloating it soon. Gonna remove all the LeEco apps. I hope kernel sources get released for the x722 but I ain't holding my breath.
Hello, thank you very much for reading, I hope you can help me. I need one or more files to be able to recover my phone: Samsung Galaxy S7 Active.
These are the files that I need:
prog_emmc_firehose_8996.mbn (.elf)
rawprogram0.xml
patch0.xml
I do not know if I would also need these:
MPRG8996.hex
rawprogram_unsparse.xml
I think these files are the same as prog_emmc_firehose_8996.mbn (.elf):
8996_msimage.mbn
MSM8996.mbn
How did I make a brick my phone? Installing the first official version:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
Previously I used this version without any problem:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
I wish someone could help me, I have read more than 50 pages, but I have not been able to solve the problem.
Please.
Can anybody help me?
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
I hope someone helps us.
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
yakine13 said:
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
Click to expand...
Click to collapse
Hello, sorry for my bad English. My phone is a Samsung Galaxy S7 Active (SM-G891A). I will try to explain what happened.
I had this version of Android 6 installed (via Odin) on the phone:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
With that version my phone was fine, but then I tried to install the first version of Android 6 (official) via Odin:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
When the installation was completed (Odin said the installation was successful), the phone never restarted. There is no way to turn it on with any combination of buttons, nor with a microSD with a debrick.img. A USB JIG has not worked for me either.
Windows detects my phone in Qualcomm 9008 mode. Odin does not detect it.
did you find a solution?
actually it look like to be a hard brick but as it's snapdragon 820 you can recover from it
I'm waiting for the day when noobs and half-noobs (no offense, all of us have been there) will start reading before writing and stop assuming that their 1st aid kit will revive a kitten ran over by a train.
It's okay not to know, but before writing a spam reply, just consider for a second that the user already tried your solution and is already a step ahead.
Listen guy, go to Halab Tech. They have certain firmwares for what you need, but they ask money.
Those type of firmwares have a prefix "DEBUG_EMERGENCY_DOWNLOAD_FA....'
In my case it's "DEBUG_EMERGENCY_DOWNLOAD_FA70_G955U1SQU6ASG1_CL12542406_QB24669289_REV00_user_mid_noship_MULTI_CERT.tgz"
As I consider that a bastard move (since they are selling Samsung's intellectual property as their own, stuff that should be public in the first place), I encourage you to share the files if you buy them, so that we can all use them and screw over these monopoly playing-intellectual property stealing bastards.
I'm now working on a recovery of my G955U1 (S8+ Qualcomm USA). I paid $25 for a god damn firmware and I'm gonna post it in next couple of days.
I'm personally having trouble of flashing the firmware (because not many flash tools support flashing .elf flash loaders), but I used one FRP tool (Octoplus FRP tool) to check the loader and it managed to send it, receive the "hello" packet, read partitions and erase the FRP partition (I assume it worked by the log), but I don't have a way to flash other partitions yet.
You people should have in mind one thing: even though certain devices have the same chipset, doesn't mean that you can use the same firehose flash loader, since manufacturers create different loaders for them and write their digital signatures into the chip (don't know is it hardwired or flashed), meaning that you cannot use Xiaomi's prog_ufs_firehose_8998_ddr.elf (just an example) to flash a Samsung device with MSM8992 chipset.
In fact, I think that each phone model and possibly even it's different firmware revisions have unique loaders, since I didn't manage to get a successful response from my G955U1 by sending G955U2 loader, and the loader which I managed to send is actually stated to be for G955U1U6 (U6 is the bootloader revision number, while U1 is the part of the model number).
Best of luck, contact me if you need help.
There's a little story i needed to rant about before i wrote this guide so read if you'd like if not tldr; will be down below
NO ROOT OR BOOTLOADER OR ANY FORM OF CODING NEEDED FOR THIS FIX, THIS METHOD WE WILL BE USING OTG AND THE RENAMED STOCK NA 8.07 ROM FOR THE 5S GOING FROM CN 6.23
Requirements​ - NA 8.07 rom from the official redmagic website
- A Computer/laptop
- USB stick (mine was usb2.0)
- OTG adapter (if you have any old samsung phone boxes look in them there's usually one)
Hey guys! First of all im terrible with technology, i havent touched a computer in over 15 years before 4 days ago.. So i bought this phone 4 days ago as i needed a decent phone with a snapdragon soc (samsung uses trash exynos in Australia). The shop i bought it from didnt tell me it was the cn version and thought he would just have NA version as thats what it says australians will recieve on the official site.
So i did some research and found out we can easily change roms using the local update thingy so i dl'ed the 8.07 NA rom and it would load to 25% then freeze, reset and nothing would happen.
So i tried the OTG method, same thing again, 25% then crash and reset. So at this point im starting to get pissed, i downloaded the latest 5G NA rom and tried to otg method that rom to the phone. It loaded to 80%, crashed and hard bricked my phone to the point of where it was corrupt, couldnt get into recovery and couldnt factory wipe,
I was however, happy to see the boot logo had changed to english though so i didnt give up, 3 days, 3 f##ing days i was trying to research flash guides, recovery guides, root guides, downloaded about 100 usb drivers because i wasnt updating to the right drivers at the right times when plugging in and unplugging my phone, i tried unbrick tools and when trying to fastboot it was saying the password was incorrect (fastboot oem nubia_unlock NUBIA_NX659J is what worked for me to unlock fastboot. all the guides i read said the fastboot cmd was
fastboot oem nubia_unlock NUBIA NX659J) nothing worked. Luckily i had gone into dev options after reading a guide and unlocked oem unlocking and usb debugging before the phone bricked as this is what helped unbrick my phone. I had to individually flash each .img file from the CN rom back to the phone.
I didnt know how to code or do cmd thingys before i bought this phone. Now i could f## join anonymous im that good LOL but yeah i managed to unbrick, wipe, and flash the NA 8.07 rom to my CN 5S using OTG. You wanna know what i did to make it work? I can tell you right now it didnt need a f##ing 4 day crash course on hacking and coding.
TLDR; bought CN rom 5S brand new from shotty phone shop, i couldnt get the NA rom to load past 25% on the local update so i went through hell and back.
I highly highly recommend unlocking developer options in your phone, turn on oem unlocking and usb debugging before doing any updates or experiments with this phone, just incase anything goes wrong with any updates
Solution:
- Always back up your phone before anything you will need to do a factory wipe after doing this
- Change the name of the NA 8.07
NX659J-update.zip folder you downloaded to "update"
- Copy that update.zip folder to a freshly formatted fat32 USB stick, do not unzip and copy. It has to be the zipped folder then safely eject the usb from the PC
- Hold the Volume up button and the power button until the screen turns on, once the screen turns on release the power button and you should reach a blue screen with 2 language selection buttons, use the volume keys to navigate and the power button to interact.
- After choosing language you will see "choose a package" and some other buttons, this is recovery mode.
- select "choose a package" and plug in your OTG adaptor and USB stick
- Select OTG method
- Find your "update.zip" folder it should be right there
- Start update and keep an eye on the phone incase any errors pop up it should take about 5 minutes to update and it will stop at certain points (stopped at 80% for a good 30 seconds for me) for bigger files so dont stress if the numbers aren't moving. I was tapping the screen so fast with anxiety at 80% hahah
- After the update go back to recovery and wipe data/cache partition and reboot
- Enjoy your goog apps
unlocking dev options and using the oem unlock option is not necessary for our device.
Unlocking the bootloader also corrupts the fingerprint sensor data, making fingerprint break.
when you need to flash a rom and the normal method does not work, flashing though recovery normally works.
as you have a CN variant of the phone. note you cannot use the NFC function. as there is no NFC chip on CN variant devices.
Patrick Morgan said:
unlocking dev options and using the oem unlock option is not necessary for our device.
Unlocking the bootloader also corrupts the fingerprint sensor data, making fingerprint break.
when you need to flash a rom and the normal method does not work, flashing though recovery normally works.
as you have a CN variant of the phone. note you cannot use the NFC function. as there is no NFC chip on CN variant devices.
Click to expand...
Click to collapse
Oh i didn't know that! I was unable to flash the na rom through recovery until i renamed the zip folder lol but i wish i knew i had to rename it before i bricked my phone.
Im not sure how to relock my bootloader and fix the fingerprint sensor, i read somewhere theres a number to dial #xxx# for the calibration but i cant find it
Brae2 said:
Oh i didn't know that! I was unable to flash the na rom through recovery until i renamed the zip folder lol but i wish i knew i had to rename it before i bricked my phone.
Im not sure how to relock my bootloader and fix the fingerprint sensor, i read somewhere theres a number to dial #xxx# for the calibration but i cant find it
Click to expand...
Click to collapse
fastboot flashing lock or fastboot oem lock I think are the commands to relock your bootloader. which after a wipe should restore your fingerprint.
you can then follow my TWRP and ROOT guide on XDA here for the 5S and not have flashing problems again.
Patrick Morgan said:
fastboot flashing lock or fastboot oem lock I think are the commands to relock your bootloader. which after a wipe should restore your fingerprint.
you can then follow my TWRP and ROOT guide on XDA here for the 5S and not have flashing problems again.
Click to expand...
Click to collapse
Thanks for the help! Im wondering if i should just return this phone and just buy the na version from the website, i find it a little annoying that the shop didnt mention it was the cn version, i dont know what else im missing apart from NFC aswel so im stressing
Brae2 said:
Thanks for the help! Im wondering if i should just return this phone and just buy the na version from the website, i find it a little annoying that the shop didnt mention it was the cn version, i dont know what else im missing apart from NFC aswel so im stressing
Click to expand...
Click to collapse
all 3 regions had the exact same hardware.
with the exception of the NFC chip on the CN units.
if you can live without NFC the phone should be the same and function correctly with any of the roms once you're able to flash them.
its just that there will be an NFC option in the rom, it just wont activate, since you dont have the actual hardware.
if you were to give the phone back look into buying it from redmagic directly. as Nubia's Warranty only covers direct sales, it does not cover any 3rd party website this includes places like Nubia store on Aliexpress. you won't get official warranty from there.
only the redmagi.gg or nubia homepage which normally directs you to redmagic.gg will support official warranty so this is something to consider.
but also, as you've unlocked the bootloader, flashed things and what not. if the seller knows or finds this out they can refuse a refund as you've modified the system.
good luck either way.
corrupt
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
I can. So last week I managed go back from a rooted situation to stock rom with LOCKED bootloader. This means that you're phone will be as you bought it and you're gonna lose everything of course.
This video on YT helped me.
***REMEMBER TO CHOOSE YOUR FIRMWARE BECAUSE I THINK THIS VIDEO IS FOR ASIA, IF IT IS THE SAME FOR YOU THEN YOU SHOULD FOLLOW THIS VIDEO***
I provide you a link with a thread on xda where I found the version for my oneplus 8 pro (EU)
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS | XDA Developers Forums (xda-developers.com)
Thanks I'll check it out and report back
glhelinski said:
Thanks I'll check it out and report back
Click to expand...
Click to collapse
Let me know
glhelinski said:
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
Click to expand...
Click to collapse
Visit the MSM thread, that's it
Sneakdovi said:
Let me know
Click to expand...
Click to collapse
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
glhelinski said:
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
Click to expand...
Click to collapse
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Sneakdovi said:
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Click to expand...
Click to collapse
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
chr_rocke808 said:
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
Click to expand...
Click to collapse
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Post #2 above has a video and also links to the same place that freshlybaked420 referenced... Should be enough to get you back on track
FreshlyBaked 420 said:
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, it's all true. Sorry for that i have now working for many days on this. Not sleeping enought. One more question that could bring me a step foward...
I was on IN11.0.2.2 before i locked the bootloader and bricked the device.
Now i downladed the Decrypted OxygenOS 11.0.0 IN21BA Version. I have now the error: Param Preload Device not match image. Question: Must i habe the Decrypted OxygenOS 11.0..2.2 IN21BA Version that it goes to work?
I can't the use the link for the right version, it is password protected.!
Thanks
The password is listed in the OP
glhelinski said:
The password is listed in the OP
Click to expand...
Click to collapse
Thank you, but I didn't find it.
One point I have forgotten to tell. Before the hard brick happened, I used Magistik and Patch a new boot.img then I flashed this with fastboot command. My failure was to make this 2. times. with different patches. The horrible thing is now that I must delete these files on my Laptop to get more space. When this the Problem of the MSMTOOL error is I had not really a chance to unbrick my device. Have anyone Downgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try it. I feel really scared. Maybe my device is not unbricked anymore.
The other Tool that I have (last chance) is the original Qualcomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But I found nothing here, that this tool was used. There is no special Rom here to found.
chr_rocke808 said:
Thank, but i didn't find it.
One point i forgotten to tell. Before the hard brick happend, i used Magistik and Patch a new boot.img then i flashed this with fastboot comand. My failure was to make this 2. times. with diffred pachtes. The horrible thing is now that i must delete this files on my Laptop to get more space. When this the Problem of the MSMTOOL error is i had not realy a chance to unbrick my device. Habe anyone Donwgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try. i feel realy scared. Mabye my device is not unbricked anymore.
The other Tool that i have (last chance) is the orginal Qulacomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But i found nothing here, that this tool was used. There is noch spezial Rom here to found.
Click to expand...
Click to collapse
None of that matters.
1st identify your device!
What region is it?
If you have BA then don't flash AA you'll mess things up.
2nd visit the MSM thread!
Download the tool 'for your device!'
3rd boot to EDL (I responded to you in the romaur thread how to do this)
4th as soon as it's connected to your pc in edl, flash the device
5th MSM will relock your bootloader.
6th don't do something if you're not sure, just ask.
Oh and lol chill on the swearing also on posting everywhere, just make 1 thread and stick with it, people will help
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
chr_rocke808 said:
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
Click to expand...
Click to collapse
Lol no worries pal, but trust me, always make a thread unless one exists, it'll work out.
Glad you're sorted.
My son tried to root Oneplus 8 Pro and failed, i tried to fix it and failed even harder.
Somehow the entire phone HD got formated and the phone was stuck in a bootloader loop or something similar when i got it.
Gooled a little and after a while i understood that MsmDownload Tool is what im looking for.
I checked for a suitable version of Oxygen and i think i picked the EU version but im not sure.
Anyway, after trying a few times i managed to install something, maybe oxygen or maybe a new bootloader im not sure to be honest.
I got a popup window telling me that the OEM Unlocking switch will be turned off.
The phone booted up and everything is working again, almost..
Now the phone says no simcards inserted, but there are working simcards in simcardslot and
i cant turn on OEM unlocking so i cannot redo the installation of Oxygen.
Anyone that can help me here?
jebraham said:
My son tried to root Oneplus 8 Pro and failed, i tried to fix it and failed even harder.
Somehow the entire phone HD got formated and the phone was stuck in a bootloader loop or something similar when i got it.
Gooled a little and after a while i understood that MsmDownload Tool is what im looking for.
I checked for a suitable version of Oxygen and i think i picked the EU version but im not sure.
Anyway, after trying a few times i managed to install something, maybe oxygen or maybe a new bootloader im not sure to be honest.
I got a popup window telling me that the OEM Unlocking switch will be turned off.
The phone booted up and everything is working again, almost..
Now the phone says no simcards inserted, but there are working simcards in simcardslot and
i cant turn on OEM unlocking so i cannot redo the installation of Oxygen.
Anyone that can help me here?
Click to expand...
Click to collapse
Hello and good afternoon, @jebraham
Welcome to XDA! I hope you'll always find and get the support you require.
However. prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to
OnePlus 8 Pro Questions & Answers
Ask your questions about the OnePlus 8 Pro and get answers from the community! Please be as specific as possible when posting.
forum.xda-developers.com
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
jebraham said:
My son tried to root Oneplus 8 Pro and failed, i tried to fix it and failed even harder.
Somehow the entire phone HD got formated and the phone was stuck in a bootloader loop or something similar when i got it.
Gooled a little and after a while i understood that MsmDownload Tool is what im looking for.
I checked for a suitable version of Oxygen and i think i picked the EU version but im not sure.
Anyway, after trying a few times i managed to install something, maybe oxygen or maybe a new bootloader im not sure to be honest.
I got a popup window telling me that the OEM Unlocking switch will be turned off.
The phone booted up and everything is working again, almost..
Now the phone says no simcards inserted, but there are working simcards in simcardslot and
i cant turn on OEM unlocking so i cannot redo the installation of Oxygen.
Anyone that can help me here?
Click to expand...
Click to collapse
I guess you used the wrong msm tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Download from here and try again.