Related
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 2.2.0
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen OS 2.2.0 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.11 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.11_151211" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@paultje162 for adaptation of Instructions. Refer his thread here if you are looking for an older version of stock reset (2.1.1).
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Edit:- file confirmed legit ! Totally official, way to go, @fareed_xtreme !
[email protected] said:
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Click to expand...
Click to collapse
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
fareed_xtreme said:
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
Click to expand...
Click to collapse
Whenever you get drivers like this, dig into their folders and you'll find important documents and instructions to use
That is how I found out about this certificate
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
xbit said:
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
Click to expand...
Click to collapse
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
beaverhead said:
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
Click to expand...
Click to collapse
This didn't work for me:
fastboot oem unlock didn't work because I had a corrupt bootloader.
Spannaa said:
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
But this was great! My OPO is alive now. Thanks
Thank you!!!! this worked.
I was eventually able to get the restore program to recognize it and restore it so it could boot normally. Thank you!
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Thanks for spotting the errors. I have updated them. It is indeed a miss on my part in regards to the QC. Hence I have uploaded it separately and updated the instructions.
Spannaa said:
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Click to expand...
Click to collapse
Yup, A copy paste is not the right way to copy a link. Haven't been around these threads for quite some time and guess i did not remember that the links are trimmed down. Thanks for the correct link.
Updated Information with UnTamper Guide
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
albertocastillo2001 said:
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
Click to expand...
Click to collapse
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
fareed_xtreme said:
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
Click to expand...
Click to collapse
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
albertocastillo2001 said:
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
Click to expand...
Click to collapse
Please note that the Tamper part of the guide is NOT done by OnePlus. Please note that OnePlus is in no way affiliated to the Tamper part of the guide. The Tamper guide is a result of comprehensive research conducted by thedropdead (information provided in the First Post). The guide is an easier interpretation of all the research that went in there.
OnePlus will only reflash this package which will re-lock the Bootloader only. Tamper Flag is not modified. So sit tight and let them reflash it for you.
You are right to assume I had a session with them earlier and that's how i have the files.
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
albertocastillo2001 said:
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
Click to expand...
Click to collapse
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
fareed_xtreme said:
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
Click to expand...
Click to collapse
Oh, then what happened? I thought the remote support tried to fix your phone. Since you said they didn't untamper the device after I expected they remoted to your phone. What happened then?
Thanks
Hi,
I followed your instructions, but my God damned Windows 8.1 doesn't see my God damned Android 4.4.2, so I "adb devices" command -- pc doesn't see my Android. "file transfer (MTP) files" command is useless.
Is there any of you in the whole wide world could help me?
My phone is in recovery mode can't boot stuck in boot loop.
Nobody answeres. This is said to be the best geeks' forum.
Sorry, I am disappointed, fed up, etc. as none of you give a damn about my f***ing problem.
Thx if any...
You could try using the latest adb and some universal driver ***,
but not much use from ADB really, if it has a stock recovery Then also
making update zip s could be problematic... signing...
Best to try contacting the manufacturer or seller, what ever, and try to get the firmware + tools.
http://smartnavon.eu/
http://hungaroflotta.hu/page-7.html
http://hungaroflotta.hu/contact.html
If no luck, try to find out its soc. You could even try to open the damn thing...
Or just assume it's a MTK. If so -> MTK drivers, DroidTool, Wwr, SP_FlashTool, etc..
and make a backup. Worked ok? Good! Now find someone having the same piece of...
and ask her to do the same and share his system...
Good luck! :fingers-crossed::good:
*** For example this installer of mine. Contains universal adb driver and adb/fastboot downloader
https://forum.xda-developers.com/an...taller-universal-adb-driver-package-t3595277/
Thx 4 UR reply!
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Don't open it yet! :laugh: I did a bit more searching. It's a MT6572. This "dazexy" fellow
most likely can help if you cannot get that factory firmware.
http://forum.gsmhosting.com/vbb/f29...nfinity-box-725574-post10962286/#post10962286
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...rum.gsmhosting.com/vbb/10962286-post1173.html )
At least he helped "kaller1" at the same forum.... see the second post here.
(if needed you can find kaller1's email by clicking his paypal donate button)
http://forum.gsmhosting.com/vbb/f82...nck-dongle-1314877/index147.html#post11354667
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...d-phones-via-nck-dongle-1314877/index147.html )
Some more helpful people having d402??
https://mobilarena.hu/tema/navon_mizu_d402/hsz_1-50.html
So no worry, I think your problem will be solved. :highfive: (Hopefully...)
(if it is that Navon Mizu D402, as I assumed because of this post
https://forum.xda-developers.com/showthread.php?t=3501143 )
edit: gsmhosting works again. The second link (kaller1) updated to be more accurate.
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Here is another fellow who gives a damn. "donrico" is sharing the full rom here
http://forum.gsmkabelek.com/showthread.php?28404-navon-d402-rom&p=250246&viewfull=1#post250246
Because that 4shared site is a bit nasty, i copied it to mega, here
https://mega.nz/#!v4MgVIbJ!htsUcjHSrwwGIDuTeNRMAXKhxZOvVxJ8mnY3vMZoVks
Taking a full backup first might be a good idea.
SP_Flashtool should do the trick. You probably
can use the scatter file from that rom dump.
Or make your own: https://forum.hovatek.com/thread-21970.html
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Sub forum changed... Okay, let us continue here if needed.
Though you should be able to fix that damn thing now...
:victory:
Thank you so much for making such a hard effort to help me! ?
I'll do my best and will keep you informed.
Partitions "nvram" and in in my case also "pro_info" are important backups.
Nvram contains IMEI values etc... anyway it can be important to save it/them.
And pro_info might have some extra values defined in it. At least if the device
has some faked firmware showing wrong hardware values like in my case.
Then there might be some real values needed, defined there along with the faked ones...
I'm no MTK expert but managed to fix my tablet by restoring those partitions...
Ehh!
I've read all the info you linked. ????
OMG!
Well, I guess that I should download the rom.
After that do I have to do all the instructions?
How will my pc be able to see my phone?
I need no data backup.
I swear I got in touch with the store in which I bought the data cable and asked if it is really a data cable and not just a charging one.
I can do anything I just need to know the steps to be taken one by one.
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Nikkka said:
Ehh!
1. After that do I have to do all the instructions?
2. How will my pc be able to see my phone?
<snip>
3. There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Click to expand...
Click to collapse
1. I can relate your "shock". That Wwr route isn't the easiest one, I can imagine.
Haven't done it myself. Maybe that SP_FlashTool + scatter file is enough for
the backup. If you have those IMEI numbers saved you probably can skip
the backup, but as I said I'm no expert, so you might want to do some
Googling before deciding anything...
2. Install the MTK drivers (search). any tool will need them too.
3. IDK. Maybe someone else has an answer to this?
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Nikkka said:
Ehh!
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Click to expand...
Click to collapse
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
CXZa said:
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Click to expand...
Click to collapse
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
CXZa said:
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
Click to expand...
Click to collapse
Yep. Thanks.
Well, actually the antivirus Zemana asked if I wanted to make SELinuxModeChanger a part of the system/a system file. I agreed. I made the wrong decision. I used ES File Manager to delete SELinuxModeChanger. Well, I succeeded in half... but failed to delete it from all system maps and couldn't reinstall it again. Rebooted... The rest is history...
I guess phone thinks that it has a corrupted system and that's why it doesn't boot.
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Nikkka said:
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Click to expand...
Click to collapse
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
h t t p s://w w w . getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
(Bad site, sorry. While the info in this article might be ok, all at this site is not.
So better to search if the info can be found elsewhere.)
+ lots of more similar articles + videos. Almost too much really...
CXZa said:
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
+ lots of more similar articles + videos. Almost too much really...
Click to expand...
Click to collapse
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
I guess it will be a hard effort to make my phone work again. I seem to give it up. Unfortunately, sending the phone to Navon for refurbishing... would cost too much and phone must be sent by post (!!!). It is a great phone, but customer service at Navon is...
Nikkka said:
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
Click to expand...
Click to collapse
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Nikkka said:
I guess it will be a hard effort to make my phone work again.
Click to expand...
Click to collapse
Maybe not that hard if you're able to connect to PC... but..
(it looks like that at the moment I cannot make a connection either, LOL
re-installing the drivers probably fixes it, IDK, have to check it some day... )
---
That OTA update needed (at least) one program more (to be run as a service).
Did that too. And I also disabled the firewall that was blocking the connection. :laugh:
It just says that my system is up to date. (Changing version numbers etc. doesn't help).
The server response hints to http://europedownhw.mayitek.com/ site
that seems to be dead...
Navon...
https://forum.hovatek.com/thread-25956-post-155741.html#pid155741
Oh yeah? http://smartnavon.eu/smartphones/navon-t503 (not even an old model)
https://logout.hu/bejegyzes/cappa72/sp_flashtool_readback_kiolvaso_opcio_hasznalata_gy.html
https://itcafe.hu/tema/android_dual_sim_ket_sim_okostelefonok_topikja/hsz_16132-16132.html
[QUOTE
CXZa said:
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Factory Reset doesn't work. I mean that in Recovery Mode it doesn't matter how many times I do Factory Reset nothing happens.
I have no twrp. Only KingRoot was able to root my phone. TWRP said my phone not compatible with it.
Click to expand...
Click to collapse
Nikkka said:
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
Click to expand...
Click to collapse
While you're are letting go, you could read some stuff linked below. Good
instructions. What to do and what not to do. (Unlike at that "getdroidtips"
site I linked earlier. Some of the tips and articles there are total rubbish.
Mixed stuff copied somewhere else, I guess. Some might work, but not all.
Also they use wrong words in article names to get better Google rankings.)
SP Flash Tool + MediaTek MT65xx drivers download and installation guide including bricked devices
Download MTK Drivers (32 & 64 bit) XP Vista Win7 Win8
Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Drivers installation tutorial (Might be useful with win8 too.)
Download SP Flash Tool v3 & v5 – Latest versions ( Tip: read to the end)
Remove, Disable & Uninstall MTK USB Drivers and inactive COM Ports – USBDeview (if having driver problems)
(And I also sent you some info in Hungarian already in the previous post. Backup etc.)
Again. just for fun sake, I tried again if my MTK tablet/phone would be recognized by SP flash tool.
No luck. Previously it wasn't a problem. Still, the adb/fastboot works okay.
So, some problem with MTK drivers. I have used SP_Flashtool, BeTools,, even older ones
like WiseLinkTool. And maybe some that were between those two.
Well, I don't have any good reason to fix those driver problems at the moment,
everything works ok, but still it kind of sucks.
Anyway adb/fastboot works okay. And that is the problem mentioned originally in the title.
So, does the fastboot work?
With fastboot, if it works, you might be able to boot some modified recovery without flashing and then maybe do some backups etc.
My adb driver package, mentioned in my signature has some options to remove the
old adb installations and the old (maybe problematic) values from the registry...
USBDeview is better choice in some situations though...
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
First post has a section specifically about the drivers you'll need to have your phone recognized in fastboot mode:
The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile...
forum.xda-developers.com
That said, I'm pretty sure you're stuck until the MSM tool comes out (the MSM tool is different for each phone, DO NOT use one for a different OnePlus phone) to fix it yourself.
edale1 said:
First post has a section specifically about the drivers you'll need to have your phone recognized in fastboot mode:
The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile...
forum.xda-developers.com
That said, I'm pretty sure you're stuck until the MSM tool comes out (the MSM tool is different for each phone, DO NOT use one for a different OnePlus phone) to fix it yourself.
Click to expand...
Click to collapse
Yeah I run linux, I don't need the drivers
It b what it b
Gip-Gip said:
Yeah I run linux, I don't need the drivers
It b what it b
Click to expand...
Click to collapse
Ah. Sadly, I have next to no experience with Linux outside of the tinkering I've done on my Raspberry Pis, so can't help you there.
Gip-Gip said:
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
Click to expand...
Click to collapse
My experience with USB passthrough on different hypervisors is that they all suck. I have to use Windows at work, so I use it for most of the tools including MSM tools.
That being said, I've never seen a real difference in adb / fastboot on Linux or Windows.
Have you tried calling OnePlus by chance?
SMcC2 said:
My experience with USB passthrough on different hypervisors is that they all suck. I have to use Windows at work, so I use it for most of the tools including MSM tools.
That being said, I've never seen a real difference in adb / fastboot on Linux or Windows.
Have you tried calling OnePlus by chance?
Click to expand...
Click to collapse
No, but there is a 100% chance that they'll just tell me to use their repair program. Which I'll be surprised if it's under $100 for me to mail it in, have some dude spend 5 minutes flashing it, and then mail it back
Gip-Gip said:
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
Click to expand...
Click to collapse
what exactly is messed up on your phone. i have metro ver rooted and can backup any partition img you need to flash from my stock rooted n200. do you need stock boot or recovery? if not then what do you need?
an is fastboot able to detect your phone?
PopCaps1996 said:
what exactly is messed up on your phone. i have metro ver rooted and can backup any partition img you need to flash from my stock rooted n200. do you need stock boot or recovery? if not then what do you need?
an is fastboot able to detect your phone?
Click to expand...
Click to collapse
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Dimitrimem said:
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Click to expand...
Click to collapse
do you have a unlock code from oneplus for you n200?
PopCaps1996 said:
do you have a unlock code from oneplus for you n200?
Click to expand...
Click to collapse
my phone was paid in full from oneplus store in US .. so i dont think i need a code
Dimitrimem said:
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Click to expand...
Click to collapse
my bootloader is unlocked I just can't enter fastbootd, which is a problem
Hey there, so I managed to get a hold of the MSM tools this morning. Since I have to go out soon, I'll upload them later. Once I upload them, you should be able to unbrick your phone.
lzgmc said:
Hey there, so I managed to get a hold of the MSM tools this morning. Since I have to go out soon, I'll upload them later. Once I upload them, you should be able to unbrick your phone.
Click to expand...
Click to collapse
Excellent! This will be of so much help to many folks out here who have bricked their phones. Look forward to your sharing the tool.
Is the MSMDownload tool, that you got, for the Tmobile version or the unlocked version/retail or both?
jilebi said:
Excellent! This will be of so much help to many folks out here who have bricked their phones. Look forward to your sharing the tool.
Is the MSMDownload tool, that you got, for the Tmobile version or the unlocked version/retail or both?
Click to expand...
Click to collapse
It's for the T-Mobile version. Someone with a retail N200 will have to request a "remote session" with OP support in order to get the MSM tools for the retail version.
lzgmc said:
It's for the T-Mobile version. Someone with a retail N200 will have to request a "remote session" with OP support in order to get the MSM tools for the retail version.
Click to expand...
Click to collapse
@lzgmc, thanks.
How does this "remote session" with OP work? Does one report that the phone is bricked, and then they send you the tool which you execute? Or do they run the tool in real time using a remote desktop tool, but then one has to somehow capture their MSMDownlod tool using some other tool? Do they not try to delete the downloaded tool?
If you could share your detailed experience of this "remote session", and how to capture the MSMDownload tool, it would be of tremendous help. I don't own a retail/unlocked N200, but your experience can perhaps help those who have one, in getting the MSMDownload tool for the retail version. It would benefit the Tmobile users too, in finding a way to potentially convert Tmobile version to retail version. Thanks!
Can you upload the tool please mine is bricked after crash dump
nache2001 said:
Can you upload the tool please mine is bricked after crash dump
Click to expand...
Click to collapse
this might help..... https://forum.xda-developers.com/t/...ot-magisk-patched-boot-imgs-included.4323439/
PopCaps1996 said:
this might help..... https://forum.xda-developers.com/t/...ot-magisk-patched-boot-imgs-included.4323439/
Click to expand...
Click to collapse
Bootloader is locked i can't flash a patched rom, thanks anyway.
nache2001 said:
Bootloader is locked i can't flash a patched rom, thanks anyway.
Click to expand...
Click to collapse
That is a pity. The MSMDownload Tool seems to be the only way to fix this.
The good news is that the MSMDownload Tool is now available with Oneplus support, as of today e.g. until last week, folks out here posted that Oneplus support did not have the tool released to them. Perhaps you can contact Oneplus support and request a "remote session" to unbrick it similar to what @lzgmc did, and get your phone un-bricked sooner? If you do so, try to grab a copy of the MSMDownload Tool that they use in the session and share it with others out here. I am sure @lzgmc will post it soon, but no harm in having multiple copies available.
lzgmc said:
It's for the T-Mobile version.
Click to expand...
Click to collapse
@lzgmc Do you happen to recall which version of Oxygen OS the MSMDownlod tool is for? 11.0.1.4 or 11.0.1.5?
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
I got it to fastboot mode, but there's no boot image for 11.0.0 available, right? Please help
Is it T-Mobile version or unlocked?
There's MSM tool for T-Mobile version and you can download full ROM for unlocked
If yours is unlocked and you can access recovery, use sideload
Code:
adb sideload
Press spacebar once and drag and drop the ROM onto command window and press enter
This can fix boot as well as making version update
bouyakasha said:
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
Click to expand...
Click to collapse
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
amboyscout said:
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
Click to expand...
Click to collapse
wow .. please upload it to google drive or mega (dot) nz and post the link here .... honestly this gets me very excited ...
mingkee said:
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
Click to expand...
Click to collapse
my bootloader is locked .. thats why MSMDownload tool is a must
edale1 said:
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
Click to expand...
Click to collapse
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a maual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Dimitrimem said:
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
Click to expand...
Click to collapse
If you use the "+ Quote" button, rather than the reply button, it'll create a multiquote, letting you quote and reply to multiple posts all at once (it'll add a "insert quotes" button to the reply box). This eliminates double-posts, which most forums frown upon.
@Dimitrimem here ya go https://drive.google.com/drive/folders/1DzR0uEdyFeBeID4sVaT96z0Y88sMaomL?usp=sharing
Dimitrimem said:
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
Click to expand...
Click to collapse
Tried this today. Now waiting on OnePlus to respond.
bouyakasha said:
Tried this today. Now waiting on OnePlus to respond.
Click to expand...
Click to collapse
Don't wait to long for their reply .. if they don't answer call them on the phone.. it takes less than a minute to have them speak with you ... I dragged it for too long with them waiting 7 days to send me a shipping label than another 5 for another try at it .. another 4 to get the link for download ..after all that they said they don't have it... but this was a while back ... I'd be on that phone fast.. tell them you need your phone as it's the only one ... honestly if you can get the msm tool it would be amazing
mingkee said:
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a manual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Click to expand...
Click to collapse
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
darkghost568 said:
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
Click to expand...
Click to collapse
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
mingkee said:
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
Click to expand...
Click to collapse
Ok so now I'm stuck here as well (saw your comment in the other thread):
mingkee said:
I attempted to flash unlocked ROM on bootloader unlocked T-Mobile version phone
It stuck on products.img. The error stated "not enough space for the partition"
What happened?
Click to expand...
Click to collapse
Any luck getting past this?
darkghost568 said:
Ok so now I'm stuck here as well (saw your comment in the other thread):
Any luck getting past this?
Click to expand...
Click to collapse
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Towards the bottom of that post it talks about getting past that error.