Related
Sorry guys for spamming this **** now, I do need help, I am doing research already but I bricked my tablet trying to downgrade it. I am running 3.2.4, and I was trying to get 3.1.0 from this guide and I edited my build.prop like he said but I got it bricked when I rebooted it... It turns on when I hold down my power button it turns on, and I can boot into Amazon's default recovery. (the only one I have.) Please help me, I think it bricked because I edited my build.prop file, I can't seem to get ADB access, I am trying to get to it but please help me.
*sigh* maybe this tablet is not for you....
What guide? "this" guide is of no help. Did you even see this guide? http://forum.xda-developers.com/showthread.php?t=2991015
I know, but I can't get ADB access. Do I need a fastboot cable?
I also didn't install Safestrap...
MinerBoy004 said:
I also didn't install Safestrap...
Click to expand...
Click to collapse
After so many people reporting about bricking after editing build.prop and not changing permissions , you went ahead and did the same thing! Nice job!
As of for now no solution to unbrick. The only way to unbrick it is to connect it with a fastboot cable, making it to enter a Qualcomm 9008 mode. After this you will need some files (.mbn programmers, WICH ARE NOT AVAIABLE, dont try people have tried and failed) so you can enter Download mode 9006. And then flash every single partition in Linux with dd comand.
I had a Thor in this mode (got it from a friend for free), and couldn't unbrick it, so I went to eBay and bought a Motherboard for $39.
I suggest you do the same...
Good luck
MinerBoy004 said:
Bricked it again...
Click to expand...
Click to collapse
No surprise. You were warned after the last crash-and-burn. If you want to play recklessly get different device that is more recoverable.
Coulden't I just reflash the image again? I am getting a much better tablet soon, can't belive I forgot to change the persimmons though...
Sorry man, right now there's just nothing to be done.
May i ask you a question?
aaronkatrini said:
After so many people reporting about bricking after editing build.prop and not changing permissions , you went ahead and did the same thing! Nice job!
As of for now no solution to unbrick. The only way to unbrick it is to connect it with a fastboot cable, making it to enter a Qualcomm 9008 mode. After this you will need some files (.mbn programmers, WICH ARE NOT AVAIABLE, dont try people have tried and failed) so you can enter Download mode 9006. And then flash every single partition in Linux with dd comand.
I had a Thor in this mode (got it from a friend for free), and couldn't unbrick it, so I went to eBay and bought a Motherboard for $39.
I suggest you do the same...
Good luck
Click to expand...
Click to collapse
First of all i'm sorry for my English. I'm not an American. My device Kindle hdx7" is bricked long time ago. No adb attach and only grey kindle logo. As you say if i bought a Kindle's Motherboard and replace the part could i fix my device? You have solved the problem? could you adb access? I'm eagerly looking foward to your answer. Thankyou have a nice day
Hi, you need to understand that after a brick the only part of the tablet that is not woking is the Motherboard (just the memory chip to be precise, but it is attached to the motherboard), the other parts of the tablet are perfectly working. So you just replace the Motherboard and you have a brand new tablet, which means you get new cpu , new memory chip, new software ect. Remember that you should find the exact motherboard for your tablet. And you need to be handy opening a device, trust me , its not that easy and you can crack things very easily. If you need to make any questions feel free to PM me, im talking from experience.
aaronkatrini said:
Hi, you need to understand that after a brick the only part of the tablet that is not woking is the Motherboard (just the memory chip to be precise, but it is attached to the motherboard), the other parts of the tablet are perfectly working. So you just replace the Motherboard and you have a brand new tablet, which means you get new cpu , new memory chip, new software ect. Remember that you should find the exact motherboard for your tablet. And you need to be handy opening a device, trust me , its not that easy and you can crack things very easily. If you need to make any questions feel free to PM me, im talking from experience.
Click to expand...
Click to collapse
Thankyou for your answer. As a whole 1. Find correct Motherboard ID in my device. 2. open the tablet not easy and easily crack. 3.Not impossible but difficult work. Right? Oh my god. broken my mental..
if i find correct Motherboard ID and replace Motherboard then my device is working? I understood my device is working correctly. Thankyou for your kindness and effort thankyou.
Yes it will work, in fact I'm writing this post from my kindle fire hdx 7
I found the teardown guide from ifixit.com very helpful, check it out, good luck!
May i ask another quistion?
aaronkatrini said:
Yes it will work, in fact I'm writing this post from my kindle fire hdx 7
I found the teardown guide from ifixit.com very helpful, check it out, good luck!
Click to expand...
Click to collapse
I have disassembled my device but I can't find mother board ID. Do you know how find mother board ID? I search e-bay i can find only C9R6QM. Is this mother board ID? um. I can't find this ID in my mother board so how can i find Mother boar ID? thankou for your help
For my kindle fire hdx 7" 16gb WiFi-only the model was C9R6QM. Make sure it is same screen size and with or without LTE.
aaronkatrini said:
For my kindle fire hdx 7" 16gb WiFi-only the model was C9R6QM. Make sure it is same screen size and with or without LTE.
Click to expand...
Click to collapse
Oh, thankou my device is same you have. thankou very much and have a nice day
cjdfyd2 said:
Oh, thankou my device is same you have. thankou very much and have a nice day
Click to expand...
Click to collapse
I'm a little too late to the party, but you could have just requested a replacement. It would cost them next to nothing to repair it. They might have a jig in place that flashes everything via QPST.
---------- Post added at 12:45 AM ---------- Previous post was at 12:34 AM ----------
aaronkatrini said:
Yes it will work, in fact I'm writing this post from my kindle fire hdx 7
I found the teardown guide from ifixit.com very helpful, check it out, good luck!
Click to expand...
Click to collapse
Your dead mainboard would make an excellent guinea pig for developing an unbrick method. I'm sure we can find someone on the forum with the required knowledge and equipment that is willing to help. If you're willing to let it go, of course.
Thankyou for everybody
I will´ing to buy used mother board by ebay but i did not. because just item´s cost $35 but shipping fee $46 by usps. I think total $81 cost not benefit. so after sell my device $45 and buy used one(just one month use) only $140. I´m satisfied with my decision because my break kindle is 7inch wif only 16g storage but new one is lte and 64g wow upgrade my device i´m happy Kindle is not popular in my country so new one is $180~190 lte 64g so i decide this method. um~ add answer above qustion i cant replace my device because i did´nt regi. amazon and i lost my device serial number so amazon says they cant replace my device thankyou every one and one more question? I just use my device? How do i regist used device?
My dead motherboard is not useful to anyone, everybody needs the leak of the programmers for the snapdragon apq8074. Until that happens nothing will help...
Hi all, I was in the process of trying to put Android 5.0 on my Verizon G3. I was following this thread:http://forum.xda-developers.com/verizon-lg-g3/general/howto-update-to-stock-lollipop-23a-t3044398. I downgraded to 10b, upgraded to 12b and then the last step, which is when things went wrong is I was upgrading to 23b (5.0) via the Action Launcher method and when the device when to boot back up to install the update it failed.
Im now stuck to where I can not power up the device, I get the LG screen and it says "Secure Boot Error/Certificate Error".. something along those lines. I lost the ability to get into download mode, it tries and then shows the boot error screen before going black.. the notification lights also flash amber and blue. The only thing I can get into is Recovery mode by Volume down + power but I tried every option.. safe mode, wipe cache, factory reset, usb debug mode all give me the boot error screen before going black.
Any suggestions before I trash the device?
I don't know how to get out of that situation, but if you post in the Verizon G3 Q&A section, someone might have some ideas.
Otherwise, I'd go to a Verizon store, tell them that you received am OTA update and left your phone like that.
roirraW "edor" ehT said:
I don't know how to get out of that situation, but if you post in the Verizon G3 Q&A section, someone might have some ideas.
Otherwise, I'd go to a Verizon store, tell them that you received am OTA update and left your phone like that.
Click to expand...
Click to collapse
This is the VZW G3 Q&A no?
I called tech, said I received an update and wasn't sure what happened but the phone wont start now, its going through insurance with the $100 deductible but my concern now is, the tech said if they find it was modded in any way I would be charged $300. The phones not rooted or anything, just a bad file I tried to apply I guess through Action Launcher. But with the notification lights flashing different colors and a boot error message I feel busted lol.
If I can somehow fix the phone I would like to try. I've been in bad situations with other devices and have always found a way out, but this being my first LG device I'm feeling lost and worried its too late.
Cyber Warrior said:
This is the VZW G3 Q&A no?
I called tech, said I received an update and wasn't sure what happened but the phone wont start now, its going through insurance with the $100 deductible but my concern now is, the tech said if they find it was modded in any way I would be charged $300. The phones not rooted or anything, just a bad file I tried to apply I guess through Action Launcher. But with the notification lights flashing different colors and a boot error message I feel busted lol.
If I can somehow fix the phone I would like to try. I've been in bad situations with other devices and have always found a way out, but this being my first LG device I'm feeling lost and worried its too late.
Click to expand...
Click to collapse
Blame Tapatalk. Sorry about that, LOL.
I understand. Don't blame me if I'm wrong, but I doubt if they'll be able to tell. First thing they'll do is put it back to Stock with some advanced tool of their, and I'm sure it'll wipe internal storage where the file was.
roirraW "edor" ehT said:
Blame Tapatalk. Sorry about that, LOL.
I understand. Don't blame me if I'm wrong, but I doubt if they'll be able to tell. First thing they'll do is put it back to Stock with some advanced tool of their, and I'm sure it'll wipe internal storage where the file was.
Click to expand...
Click to collapse
lol. yeah I hope so, at this point I really would like to just fix it though so I dont get stuck paying insurance.
Cyber Warrior said:
lol. yeah I hope so, at this point I really would like to just fix it though so I dont get stuck paying insurance.
Click to expand...
Click to collapse
Maybe when all this rooted stock LG Lollipop news and ROM-making dies down some, bump this thread if noone more knowledgeable comes along and shares some info in the meantime.
Sorry man. Good luck!
Cyber Warrior said:
lol. yeah I hope so, at this point I really would like to just fix it though so I dont get stuck paying insurance.
Click to expand...
Click to collapse
This is for the g2 but I believe it will work. You'll need to run linux or a linux live cd and find the correct files for vs985. Theyre on autoprimes site. If you cant find them reply to this and ill track down the url.
http://forum.xda-developers.com/showthread.php?t=2582142
That should work , I bricked my g2 and was able to fix it using
Fastboot commands, I'm thinking you can use adb commands
And fix your phone. You basically have to push .img files to
The phone through adb. Good luck
Edit, I could always swap mother boards for under two hundred
And just don't even go through your insurance. Check eBay and
Amazon they sell them.
hawkswind1 said:
This is for the g2 but I believe it will work. You'll need to run linux or a linux live cd and find the correct files for vs985. Theyre on autoprimes site. If you cant find them reply to this and ill track down the url.
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Yeah I was looking at that last night.. I wouldn't have to be rooted though? I'll see if I can find the files I need. I've never run Linux before but its worth a shot. I was kind of discouraged when I read about a similar G3 user who tried the process with no luck.
Alright I found these.. http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Would those do? And what mode would I put the device in? The computer does not recognize the phone..download mode won't work and recovery mode options won't work either. I'm familiar with adb and fastboot but if someone could post the commands I need it would be helpful..in the meantime I'm going to try and see if I can find them myself. Thanks
Cyber Warrior said:
Alright I found these.. http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Would those do? And what mode would I put the device in? The computer does not recognize the phone..download mode won't work and recovery mode options won't work either. I'm familiar with adb and fastboot but if someone could post the commands I need it would be helpful..in the meantime I'm going to try and see if I can find them myself. Thanks
Click to expand...
Click to collapse
Does your phone even show as qhsusb_bulk or similar in device manager while in Linux? Make sure you use the img's from the firmware you were installing when you had the problem. I assume 23B. The commands are in the link I posted above but keep in mind they are for the G2. It's likely to DD commands, ie. partition locations are different on the G3, I don't know the correct ones. Maybe some research can dig them up. Doesn't look too bad assuming you can get linux to recognize the phone in some form, which it should and that you're able to verify the location of the partitions for G3. Wish I could be more help. It was a long time ago when I went through this on the G2
Cyber Warrior said:
This is the VZW G3 Q&A no?
I called tech, said I received an update and wasn't sure what happened but the phone wont start now, its going through insurance with the $100 deductible but my concern now is, the tech said if they find it was modded in any way I would be charged $300. The phones not rooted or anything, just a bad file I tried to apply I guess through Action Launcher. But with the notification lights flashing different colors and a boot error message I feel busted lol.
If I can somehow fix the phone I would like to try. I've been in bad situations with other devices and have always found a way out, but this being my first LG device I'm feeling lost and worried its too late.
Click to expand...
Click to collapse
I've never had to do insurance for a bad update.
I have TEC and in those cases where there is absolutely no damage, I get a replacement for free.
YMMV but I wouldn't pay $100.
hawkswind1 said:
This is for the g2 but I believe it will work. You'll need to run linux or a linux live cd and find the correct files for vs985. Theyre on autoprimes site. If you cant find them reply to this and ill track down the url.
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Hi I have Linux up and running.. can you help me with what files I need please?
Cyber Warrior said:
Hi I have Linux up and running.. can you help me with what files I need please?
Click to expand...
Click to collapse
It's a bit confusing the way it's written in the guide. I believe you use the 23b files in your case. Reread it to be sure.
The files are here- http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
More files here if needed http://downloads.codefi.re/autoprime/LG/LG_G3
I'm not even sure my phone is being recognized..at least nothing pops up. I'm not familiar with terminal commands in linux. At this point I'm lost.. I messaged auto prime to see if he could help out. I'm not even sure where to begin converting that g2 guide for use with the g3.
For the hek of it I'm putting the android SDK on Linux just to see if I can get fastboot to recognize the phone.
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 you can try this from Windows if your phone is showing up as Qualcomm in device manager.
dwheimerl said:
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 you can try this from Windows if your phone is showing up as Qualcomm in device manager.
Click to expand...
Click to collapse
IS there a driver to get my phone to be recognized as Qualcomm?? I think i found a way to fix mine but i need the driver
danetbra63 said:
IS there a driver to get my phone to be recognized as Qualcomm?? I think i found a way to fix mine but i need the driver
Click to expand...
Click to collapse
Qualcomm driver is on this page.. 252-253 http://forum.xda-developers.com/showthread.php?t=2582142&page=252
Good luck, I was able to get the phone recognized as qhsusb_bulk, then as qualcomm 9008 but eventually gave up after spending over 2 days researching and trying different methods before i threw in the towel.. I even had help via remote access to my computer with no luck. Check the thread I linked there were a few guys willing to help out.
My replacement G3 actually arrived today.. still cant believe I hard bricked a device.
Cyber Warrior said:
Qualcomm driver is on this page.. 252-253 http://forum.xda-developers.com/showthread.php?t=2582142&page=252
Good luck, I was able to get the phone recognized as qhsusb_bulk, then as qualcomm 9008 but eventually gave up after spending over 2 days researching and trying different methods before i threw in the towel.. I even had help via remote access to my computer with no luck. Check the thread I linked there were a few guys willing to help out.
My replacement G3 actually arrived today.. still cant believe I hard bricked a device.
Click to expand...
Click to collapse
What's the next step after the 9008? i made it that far but idk what to do next.
danetbra63 said:
What's the next step after the 9008? i made it that far but idk what to do next.
Click to expand...
Click to collapse
I'm assuming using the tool to push the img files but I didn't get that far.
Well, I tried all the "one-click" apps (I don't care if they sell my info) and none work so far...
So it's time to consult XDA. Did it years ago, doin' it now. I'm new here, but you will be happy to know I read all the rules.
Time to fix this chinese piece of crap! This is the only device I own, and I can post all the processor and system info if needed. IDK if the bootload is unlocked or not, but a guy in another post for another RCA tablet mentioned he owned this same one and they said he might not need to unlock it. So IDK. NOTE I HAVE RCT6513W87 WITH NO "M" ON THE END. DIFFERENT MODEL.
So first, what am I gonna need? USB M-2-M?
I don't have any experience using ADB, however.
Don't really know what I'm doing so far.
BUMP
BUMP
BUMP BUMP
BUUUUUUMP
@Lootron
Did you try Dr Fone?
I suggest you consult this thread for more information on rooting with or without one click tools:
https://forum.xda-developers.com/canvas-juice/how-to/guide-unlocking-bootloader-rooting-t3705781
HIT THANKS IF FOUND USEFUL
I just spent the last few hours attempting to connect it to my Windows 10 PC. Nothing. 100% Impossible. Modified registry, edited drivers, tried modified google drivers but it kept saying "Windows has determined that you already have the best drivers for this device" trieda few workarounds for that. Damn, really want this rooted but it seems impossible.:crying:
Lootron said:
I just spent the last few hours attempting to connect it to my Windows 10 PC. Nothing. 100% Impossible. Modified registry, edited drivers, bla, bla, bla. END QOUTE]
Yeah, been there. However there should be a way. There's a five second window of opportunity when you have the USB connected, have the PC in the device manager. I'm willing to bet most of the process is the same when it comes to accessing the device according to Smartman Vartans tutorial for the RCA Viking Pro. I have that, the version before it and I have the Galileo, Build Number (RCT6513W87-ANDROID6.0-V21-V1.23.30-W02). It's about time I do something with it. His method is incredibly complex from the looks of it. But I'm willing to get root at least. Sounds like it's time for experimenting. Okay, I'm in. I'll see if I can pull some resources. Enable Developer settings (tap build 7 times). In The Developer settings turn it on. Turn on OEM Unlocking (to unlock the Bootloader). Turn on USB Debugging. Go down to Select USB configuration and make sure it's at MTP.
---------- Post added at 12:23 AM ---------- Previous post was at 12:07 AM ----------
[/COLOR]The Viking Pro used a SP splash tool to see the device , I've heard it works on this. Also listed was a driver. I'll go look for the frimware hopefully we both have the same. Then there's one thing that's been making me wonder. The Viking Pro uses the exact same motherboard and components as the Acer Icona, which has current 8.0 firmware. I don't see why for the life of me why I can't float that firmware in the RCA. It's an idea. But here's the Viking Pro link,
https://forum.xda-developers.com/android/general/firmware-rca-viking-pro-rct6303w87dk-t3325158
Click to expand...
Click to collapse
I feel forced to leave a note here. Stuck on some double reply mode. Where's the delete button?
Wow!
Hey thanks, I saw you on another forum (unless Casper Young is a common name?) and you said something about usb serials being locked, but I will defintely look into this! THX!
EDIT: BTW, my build number is V08- 1.15.20
I'll bet that's me, and my actual name. Howdy Thar. Yes USB Serials appear locked by manufactuer. When I dig into the data section of my rooted Viking Pro I happened to notice they were somehow locked and I was unable to follow the pathway. I can still try. But what I think you're trying to do is gain access via USB, correct? I talked to Smartman Vartan long ago and we have one interesting delima. Okay so we can gain access, but then what? It's not like we can just throw anything in it. I have 3 different devices The Maven Pro, the Viking Pro (both are rooted) and I got this Galileo Pro. Long story short, I was looking for compatible firmware. Went old school, look at the specs. Not the ordinary ones you find anywhere, the real specs. Go here, https://www.productchart.com/tablets/11121 sign up, yeah, WOW! Okay so I compare a few things, (I'm off exploring the Viking Pro), didn't have the galileo yet. Now, come to find out, the Viking has the same exact motherboard and components as the Acer Icona 10.1 (I forget which specific one). Hmmmm, now that's intresting. Can I, just toss it in there? I don't see why not. Others here suggest otherwise. I don't flash anything without back-up That's item #1 we need if you're gonna follow along. #2? The SP Flash Tool. I have those. Now I gotta open this puppy up and check out the motherboard. Gimmie a couple days I'll get back.
I wish we could use Odin3 but here's what I got For starters. I'll write out the tutorial if I get anywhere. How to run the SP Flash Tool:
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Current SP Flashtool: https://drive.google.com/open?id=1JzB5tzTvQYOGpVfhZNKY22_N-nD-jtDA
Firmware: https://drive.google.com/open?id=1zB1waSYM0iwdobu0jdxP1WJD6r1F8-XI
MTK Drivers: https://drive.google.com/open?id=1wRdulyOKLgeT_VWbhM9tm1-hqtgSL_BD
How to install the drivers:https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Rooting
If your intention is only to root the device you must first enable Developer Settings and then enable OEM unlock which gives you access to the Bootloader. Now you can flash in a custom recovery and then you will be able to root the device. You cannot do so by any other means. It will reject any attempt to root unless the Bootloader is unlocked!
Casper Young said:
If your intention is only to root the device you must first enable Developer Settings and then enable OEM unlock which gives you access to the Bootloader. Now you can flash in a custom recovery and then you will be able to root the device. You cannot do so by any other means. It will reject any attempt to root unless the Bootloader is unlocked!
Click to expand...
Click to collapse
Ok, I have everything, I THINK I installed the drivers, but I am waiting for it to charge to be sure. Can you be a little more clear on your instructions here? Do I flash the firmware? What order do I do everything? Custom Recovery first? Firmware first? How do I unlock the bootloader when it STILL doesn't regonize the device in ADB?
BTW, I installed the drivers by the SmartmanVartan method.
Lootron said:
Ok, I have everything, I THINK I installed the drivers, but I am waiting for it to charge to be sure. Can you be a little more clear on your instructions here? Do I flash the firmware? What order do I do everything? Custom Recovery first? Firmware first? How do I unlock the bootloader when it STILL doesn't regonize the device in ADB?
BTW, I installed the drivers by the SmartmanVartan method.
Click to expand...
Click to collapse
How do I flash the firmware? SmartmanVartan's method?
MTK drivers
Lootron said:
How do I flash the firmware? SmartmanVartan's method?
Click to expand...
Click to collapse
You have Windows 10 right?
Read this:
https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/
Casper Young said:
You have Windows 10 right?
Read this:
https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/
Click to expand...
Click to collapse
Yesterday, I tried flashing the firmware you linked to, and well, RIP. Bricked. Yours had build number .22, while I needed .15. So now I don't know if I can fix it. BTW Drivers worked and everything else. Did "fastboot oem unlock" and got to the "Do you want to unlock bootloader?" page, BUT the volume keys weren't programmed into it so you can't confirm nor deny. The bootloader needs to patched.
But before I get there, I need you to find a firmware that has .15 in the middle like this: x.15.x
Please, you are my only hope.
PS: I contacted Bogram, who patched the bootloader on the viking pro. If I can get the right firmware, then I can send it to him so he can patch it and I'm there. IF HE DOES IT.
TIA!
Brick
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)
EDIT: When flashing, it never said completed. I waited for a really long time and then clicked stop. I really don't know too much of what I'm doing
Woouch!
Lootron said:
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)[END QOUTE]
Wow try slowing down a bit. Sorry to hear your having difficulties with your tablet. I didn't expect you to flash it yet. No-one has provided anything to flash into it yet, I thought we were going to go looking. I'm hoping there can be a way to get past a brick. I've been reluctant to flash any of my devices for exactly the reason that you're dealing with. I didn't think to post what my firmware build number was, I'll edit that in.
I'll look for your firmware or ask RCA for it. This might take a bit. What color light is showing. And somehow try getting it to boot to recovery. Where you can reset it. Thats where the back-up is supposed to go also. There can be a variety of combinations to get there. Isn't there a reset hole to the left and a little below the micro sd slot. You may have to have it docked to get to recovery (the Viking Pro is like that). I'll do some research and see what I can find.
Click to expand...
Click to collapse
Casper Young said:
Lootron said:
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)[END QOUTE]
Wow try slowing down a bit. Sorry to hear your having difficulties with your tablet. I didn't expect you to flash it yet. No-one has provided anything to flash into it yet, I thought we were going to go looking. I'm hoping there can be a way to get past a brick. I've been reluctant to flash any of my devices for exactly the reason that you're dealing with. I didn't think to post what my firmware build number was, I'll edit that in.
I'll look for your firmware or ask RCA for it. This might take a bit. What color light is showing. And somehow try getting it to boot to recovery. Where you can reset it. Thats where the back-up is supposed to go also. There can be a variety of combinations to get there. Isn't there a reset hole to the left and a little below the micro sd slot. You may have to have it docked to get to recovery (the Viking Pro is like that). I'll do some research and see what I can find.
Click to expand...
Click to collapse
Whoops. Yeah I'm sorry, I've always been a bit hasty. I have looked for my firmware, but would RCA give it to you? I forgot to say my processor is MT6513. Not MT6127.
Well, thanks for spending so much of your time for me though. You have been very helpful. For me, bricking it was a learning experience. I learned a LOT about how android works messing with this tablet, and come on, it was a crap-let I only decided to
"hack" it once we ordered a new one (The keyboard doesn't work anymore)
The day I did it, I got frustrated I couldn't unlock the bootloader, so I wanted to do something else, without thinking about it. LOL. Well, more learning for me!
The only light it ever does it bright blue, and it no longer does it without being plugged into the outlet. Oddly enough, I didn't think to use the reset button, and in device manager it still shows up as preloader device, even though I suspected to be the preloader to be corrupted. There really shouldn't be a reason it won't start now. Also for some reason, ADB never has regonized this device, unless in fastboot mode.
Click to expand...
Click to collapse
Lootron said:
Casper Young said:
Whoops. Yeah I'm sorry, I've always been a bit hasty. I have looked for my firmware, but would RCA give it to you? I forgot to say my processor is MT6513. Not MT6127.
Well, thanks for spending so much of your time for me though. You have been very helpful. For me, bricking it was a learning experience. I learned a LOT about how android works messing with this tablet, and come on, it was a crap-let I only decided to
"hack" it once we ordered a new one (The keyboard doesn't work anymore)
The day I did it, I got frustrated I couldn't unlock the bootloader, so I wanted to do something else, without thinking about it. LOL. Well, more learning for me. [End Qoute]
Welcome to the place where you gotta play it safe. Yes RCA does provide the firmware, here;s your like for that.
https://stockromfiles.com/download-rca-stock-rom/
Now what I don't understand is why RCA implies there's no different versions of the software and you have a possible bricked device. I have a few articles that say even if your bricked you can flash in the software. Here's the tutorial for using the SP flash tool and another software location. The Tutorial makes me wonder though because if you look at steps 1, 2 and 3 they're questionable, especially #3. I'll get back to you in a bit, gotta chore to do.
https://stockromfiles.com/rca-rct65...323c6df5dcc913b1e77a5c8f2bbfe10#comment-53815
Oh, and you have yet to learn about playing with Androids These RCAs don't count. They're completely different from flashing a Samsung Galaxy or any other Androids.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[Update]
Solved the issue
1. Go to this link 4pda . ru/forum/index.php?showtopic=399304&st=600#Spoil-55136455-3
(Of course without spaces)
Or just search on google for "4pda forum" then in the forum search for mdz 22 ab
2. You will find a tread with someone holding a mi box in hand. Enter and read the instructions, translate it because it is in russian.
3. Download usb tool and rom
4. Open box back plastic cover, inside you will see a metal cover. Remove it carefully with a tweezer. Careful not to scratch the board.
5. Install usb tool with drivers, unzip rom. Open usb tool, load rom, insert usb male in box and the other male in pc.
6. This is the tricky part. Click start, shortcircut with the tweezers the test point and the metal frame and PLUG IT
7.If done correctly it should recognize and start download.
8. If it gives an error, repeat, uninstall usb drivers, reinstall, retry. Mine worked after 20 attempts. You need patience.
THANK YOU VLADIMIR UHLIR FOR THE INSTRUCTIONS!
Hello, sometime ago I did a pretty stupid thing with an usb stick and wrote on my mdz-22-ab firmware for mdz-19... something..
Long story short is bricked.. only a red light in the back of the box, no signal to hdmi.. nothing else
Can you, please, be so kind and tell me if it is any way to unbrick it?
Thank you so much for your patience!
It seems not a lot of people made stupid mistakes like me!
mikescorei said:
Hello, sometime ago I did a pretty stupid thing with an usb stick and wrote on my mdz-22-ab firmware for mdz-19... something..
Long story short is bricked.. only a red light in the back of the box, no signal to hdmi.. nothing else
Can you, please, be so kind and tell me if it is any way to unbrick it?
Thank you so much for your patience!
Click to expand...
Click to collapse
Sorry, your box is scrooged. Hope you learned your lesson.....
Ask for a new box for Christmas
Me too. Just 2 days after purchase...
zsolarewicz said:
Me too. Just 2 days after purchase...
Click to expand...
Click to collapse
So, no fix?
mikescorei said:
So, no fix?
Click to expand...
Click to collapse
Tried all that 'magic', unfortunately nothing so far ((
successful unbricking
Hi, I had same problem like you. I fixed it using USB Burning Tool and flash image file from: 4pda forum (I'm not allowed to post link to external site)
You can find here mdz-22-ab image as well as instructions how to get your Mibox to "worldcup mode" (you have to disassemble device first), than you will be able to flash that image and bring your bricked Mibox back to the life. URL link for USB burning tool 2.1.7.3 is not valid, so I used version 2.1.7.0 which I found somewhere.
Hope it will help...
Thank you! You saved my device!
DexV said:
Hi, I had same problem like you. I fixed it using USB Burning Tool and flash image file from: 4pda forum (I'm not allowed to post link to external site)
You can find here mdz-22-ab image as well as instructions how to get your Mibox to "worldcup mode" (you have to disassemble device first), than you will be able to flash that image and bring your bricked Mibox back to the life. URL link for USB burning tool 2.1.7.3 is not valid, so I used version 2.1.7.0 which I found somewhere.
Hope it will help...
Click to expand...
Click to collapse
Can you contact me by email, please? [email protected] . com
It seems I cannot get the device to worldcup mode.. dunno which pins to short.
bricked mdz 22-AB
mikescorei said:
Can you contact me by email, please? [email protected] . com
It seems I cannot get the device to worldcup mode.. dunno which pins to short.
Click to expand...
Click to collapse
hi all
please i have this probleme too. bricked mibox s mdz 22-AB . i try and try to revive it but i dont know whos pins to short to connecte the device to burning tools. can you please share with me if you have any solution.
thniks
my mail [email protected]
crocodile61 said:
hi all
please i have this probleme too. bricked mibox s mdz 22-AB . i try and try to revive it but i dont know whos pins to short to connecte the device to burning tools. can you please share with me if you have any solution.
thniks
my mail [email protected]
Click to expand...
Click to collapse
Email sent
bricked mdz 22-AB
mikescorei said:
Email sent
Click to expand...
Click to collapse
hi
i receive your mail but no picture .jpg
can you please resend it
thanks
mikescorei said:
Email sent
Click to expand...
Click to collapse
hi
thak you very much bro. my mibox s 22-AB unbriked and revive succesful with this methode in the first time
best regard
Does your netflix, amazon and hbo go work? Mine are not working at all
mikescorei said:
Does your netflix, amazon and hbo go work? Mine are not working at all
Click to expand...
Click to collapse
Hello
not the versions in the rom. I had to install other versions from aptoid.tv
thanks
you saved my life !
crocodile61 said:
Hello
not the versions in the rom. I had to install other versions from aptoid.tv
Click to expand...
Click to collapse
Can you share what versions do you use? Pls
Amlogic_USB_Burning_Tool's Config should be Erase flash - Erase normal.
If set to Erase flash - Flash all , DRM key will be deleted and amazon video/Netflix will not work,
I did it ... how do I restore the DRM key?
Vitamin_B2 said:
Amlogic_USB_Burning_Tool's Config should be Erase flash - Erase normal.
If set to Erase flash - Flash all , DRM key will be deleted and amazon video/Netflix will not work,
I did it ... how do I restore the DRM key?
Click to expand...
Click to collapse
You can't. They're gone.
send me a pic of pins to short?
crocodile61 said:
hi
thak you very much bro. my mibox s 22-AB unbriked and revive succesful with this methode in the first time
best regard
Click to expand...
Click to collapse
i have the firmware flashed ok to an external USB stick, but where are the pins to short together on the MDZ 22 AB? or, where is this "test point" im supposed to short to a "metal case? i see 3 metal covers on the board, probably with chips beneath them...do i have to remove one of these? can you send me a pic of the pins to short? [email protected]
Hi guys,
appreciate the hard effort. can you please tell me why has this happened just today morning & send me links or how to repair.
[email protected]
Well the device is stuck in a fastboot bootloop. I'm about to have an online session to unbrick it. What does the XDA community need from me to assist with future issues?
Jaybone073 said:
Well the device is stuck in a fastboot bootloop. I'm about to have an online session to unbrick it. What does the XDA community need from me to assist with future issues?
Click to expand...
Click to collapse
please save the msmdownload tool and upload it either google drive or one of the services that do so and provide a link .. i had my phone for months and only worked for few hours before it bricked .. if you want i can give my email or send me a message .. i need to fix this thing .. thank you
p.s. after they played with me for 1 1/2 months i decided not to send my phone for repair and chose to wait for msmdownload here .. now i know i made a mistake because it took so long ..
Dimitrimem said:
please save the msmdownload tool and upload it either google drive or one of the services that do so and provide a link .. i had my phone for months and only worked for few hours before it bricked .. if you want i can give my email or send me a message .. i need to fix this thing .. thank you
p.s. after they played with me for 1 1/2 months i decided not to send my phone for repair and chose to wait for msmdownload here .. now i know i made a mistake because it took so long ..
Click to expand...
Click to collapse
I hope they use such a tool. I know one exists for T-Mobile so I'm hoping they use something similar. Fingers crossed. The appointment is in an hour or so from now.
Jaybone073 said:
I hope they use such a tool. I know one exists for T-Mobile so I'm hoping they use something similar. Fingers crossed. The appointment is in an hour or so from now.
Click to expand...
Click to collapse
from what i heard they should've already send you some sort of link to download all the stuff via email before the actual appointment .. i am crossing my fingers here .. hopefully you will get the tool... oh they will ask you if the computer sees the phone .. please say YES even if it doesn't and ask for a remote session because you need the phone for work .. ( i know i sound awful) but that might be the only way to get the tool
I replied to the email yesterday early. The tech should be sending the information over soon. They said it would be between 24 and 48 hours. Hopefully we find out very soon.
Jaybone073 said:
I replied to the email yesterday early. The tech should be sending the information over soon. They said it would be between 24 and 48 hours. Hopefully we find out very soon.
Click to expand...
Click to collapse
that sounds like good news my friend .. thank you for sharing your story and for trying to help ..
Please insist on the remote session .. btw i filled up a form and waited for the link myself but never sent it .. when i called them back they said they don't have the tool for my phone ( basically not releasing for the unlock variant) .. but that was maybe 4-5 months ago .. hopefully they changed their policy
Dimitrimem said:
that sounds like good news my friend .. thank you for sharing your story and for trying to help ..
Please insist on the remote session .. btw i filled up a form and waited for the link myself but never sent it .. when i called them back they said they don't have the tool for my phone ( basically not releasing for the unlock variant) .. but that was maybe 4-5 months ago .. hopefully they changed their policy
Click to expand...
Click to collapse
I sure hope so! Right now, I do have fastboot so all is not totally lost and if they don't respond I could probably reinstall TWRP even though it's not fully functional and try to install the stock ROM, but that seems to be quite the task given the limited capabilities of our version of TWRP right now.
UPDATE: I called support and the reason they have not escalated the case is because they needed my receipt for proof of purchase. Scanned and emailed the receipt. On the phone with them now and they will be sending the repair request "tools" to download within the next 24 hours! So another wait period is in store. I'm hitting the refresh button on my mail inbox every 3 minutes!!! THE SECOND I GET THESE FILES I WILL PUT THEM ON ANDROIDFILEHOST!!
Jaybone073 said:
I sure hope so! Right now, I do have fastboot so all is not totally lost and if they don't respond I could probably reinstall TWRP even though it's not fully functional and try to install the stock ROM, but that seems to be quite the task given the limited capabilities of our version of TWRP right now.
UPDATE: I called support and the reason they have not escalated the case is because they needed my receipt for proof of purchase. Scanned and emailed the receipt. On the phone with them now and they will be sending the repair request "tools" to download within the next 24 hours! So another wait period is in store. I'm hitting the refresh button on my mail inbox every 3 minutes!!! THE SECOND I GET THESE FILES I WILL PUT THEM ON ANDROIDFILEHOST!!
Click to expand...
Click to collapse
I love you bro .. ..
Jaybone073 said:
I hope they use such a tool. I know one exists for T-Mobile so I'm hoping they use something similar. Fingers crossed. The appointment is in an hour or so from now.
Click to expand...
Click to collapse
There's a big chance that they won't give you it. They'll likeky tell you that they don't have the files and will tell you to ship the phone in. (Many have tried to get the unbrick tool but failed because they "don't have the files".)
UPDATE: My frustration had gone from high level to now astronomical! I have called yet, once again, to get this device unbricked. I am now being told the device will be handled via a remote session. They will basically connect to my device via my PC and reflash it.
So this now begs the question:
"What do I need to do on my end to secure the tool? "
Maybe I should sweet talk the technician to let me get my hands on the reflash tool. Or perhaps disconnect the session "prematurely" once I see the device is back to full operation and some remnants of the tools will be left stuck in my PC.
My bet is that the files I will be downloading are nothing more than updated platform tools and the full OTA file.
However, they did CONFIRM that it will be done via a remote session which is significantly more progress made than others have had at this point so that leaves me hopeful that the tool is going to be utilized. Maybe I will be the guinea pig...
Jaybone073 said:
UPDATE: My frustration had gone from high level to now astronomical! I have called yet, once again, to get this device unbricked. I am now being told the device will be handled via a remote session. They will basically connect to my device via my PC and reflash it.
So this now begs the question:
"What do I need to do on my end to secure the tool? "
Maybe I should sweet talk the technician to let me get my hands on the reflash tool. Or perhaps disconnect the session "prematurely" once I see the device is back to full operation and some remnants of the tools will be left stuck in my PC.
My bet is that the files I will be downloading are nothing more than updated platform tools and the full OTA file.
Click to expand...
Click to collapse
nah. You'll be likely to be getting something called msm download tool. (If they even give you it.) Basically it uses qualcomm's edl mode to repair your phone. And you can't really do much to secure the tool, just if they don't give the tool just prob ask them again. (that's how the tmobile msm tool for the n200 was given to someone lol.)
FINALLY got the email with the link to the files I am to download. The email also states that I need WinRAR installed to extract these files. The ROM is also password protected and I'm not about to give that out in the event they change it. I would imagine it is not your standard stock rom. The "driver" is not password protected though.
I took a screenshot of the link to the driver and ROM files. But of course....I'm not going to post these just yet in the event that they are single use files.
Also, I am at work right now and should be done 1230 ish EST and the remote session is scheduled for 3PM. This should give me time to download these files, unzip them, place them on my desktop for the remote session and then copy them directly to a flash drive for later use and download to AFH.
Also, I plan on sweet talking the tech as much as I can to see if I can ask what tools she is using for the session.
BTW:. THIS TOOK CALLS EVERY SINGLE DAY FOR ESCALATIONS FOR 5 DAYS! They realized I wasn't going to give up until I got exactly what I wanted.
EDIT:. The representative also told me the device will be downgraded to Android 10??? I thought the device came with Android 11 out of the box. If this is the case it may be a tool that works from a predecessor. All of this is speculation at this point until the actual session. But noteworthy nonetheless.
Here is the image of the ROM file site. Ran late today at work. And the technician literally emailed me back saying she leaves at 2PM. Ain't that a kick in the head!
Jaybone073 said:
FINALLY got the email with the link to the files I am to download. The email also states that I need WinRAR installed to extract these files. The ROM is also password protected and I'm not about to give that out in the event they change it. I would imagine it is not your standard stock rom. The "driver" is not password protected though.
I took a screenshot of the link to the driver and ROM files. But of course....I'm not going to post these just yet in the event that they are single use files.
Also, I am at work right now and should be done 1230 ish EST and the remote session is scheduled for 3PM. This should give me time to download these files, unzip them, place them on my desktop for the remote session and then copy them directly to a flash drive for later use and download to AFH.
Also, I plan on sweet talking the tech as much as I can to see if I can ask what tools she is using for the session.
BTW:. THIS TOOK CALLS EVERY SINGLE DAY FOR ESCALATIONS FOR 5 DAYS! They realized I wasn't going to give up until I got exactly what I wanted.
EDIT:. The representative also told me the device will be downgraded to Android 10??? I thought the device came with Android 11 out of the box. If this is the case it may be a tool that works from a predecessor. All of this is speculation at this point until the actual session. But noteworthy nonetheless.
Here is the image of the ROM file site. Ran late today at work. And the technician literally emailed me back saying she leaves at 2PM. Ain't that a kick in the head!
Click to expand...
Click to collapse
Ok the fact that the device will be downgraded to android 10 makes zero sense. It didn't come with Android 10 in the box, (like you said) which kinda means that the tool might flash a possibly faulty version of oxygen os 10. (Unless if the representative lied about the Android 10 thing.)
Edit: the n100 and the n10 came with Android 10 in the box, so slight chance that the tool is for the two phones mentioned
biff_train said:
Ok the fact that the device will be downgraded to android 10 makes zero sense. It didn't come with Android 10 in the box, (like you said) which kinda means that the tool might flash a possibly faulty version of oxygen os 10. (Unless if the representative lied about the Android 10 thing.)
Edit: the n100 and the n10 came with Android 10 in the box, so slight chance that the tool is for the two phones mentioned
Click to expand...
Click to collapse
UPDATED INFORMATION as of 8:45PM EST 12/6/2021:
The files are being downloaded now as we speak. I will post them to AFH but I am not sure how much good they will do.
File 1: L2+drivers.rar
File 1 is small. 1.88 MB and can easily be downloaded. IT CANNOT be easily extracted though. To extract it requires a password and I have been told this password will be input by the technician during the remote session.
File 2: dre8t_10_O.07_211014.tar.bz2
File 2 is MASSIVE (3.24GB zip) compared to file 1 and also takes FOREVER to download. It is directly from a site called obox. It appears to be an Android 10 base file. It also appears to have a build date of October 14, 2021. The site created the download file October 28, 2021. The remaining time for this file being active is currently 329 Days and 13 hours. You can't even log into the site without a password and that was given to me via email. Since the download is coming from China it is slower than a turtle covered in molasses walking in February! It's been hours now and I have just over half the file.
I have been in direct contact via email with my technician and her name is Agnes. but as you can see the header of the zip for the ROM does indeed appear to be for the N200 but Oxygen 10, wherefore Android 10.
So this begs the questions of:
1.) When the driver is extracted do I quick copy and paste it or move it to a secure location? Or do I just assume that they want to make sure I have the correct OnePlus Drivers to make sure the phone can be recognized by the PC? If that's the case, the file and installing BreeZip (because 7Zip isn't properly working with Windows 11 yet) are both an epic waste of time.
2.) If that links me to their computers, how in the name of all things good and holy am I going to be able to get my hands on this tool?
NEED HELP!!! Tell me my next steps folks because I desperately want to assist our community!
Jaybone073 said:
dre8t_10_O.07_211014.tar.bz2
Click to expand...
Click to collapse
Unfortunately, judging from the filename, this is the MSMDT for the TMo variant. It won't even flash by default. There is a small possibility that the representative modded the package, but I wouldn't count on it.
AndyYan said:
Unfortunately, judging from the filename, this is the MSMDT for the TMo variant. It won't even flash by default. There is a small possibility that the representative modded the package, but I wouldn't count on it.
Click to expand...
Click to collapse
Well, it definitely appears to be somewhat recent! Holy radioactive Christmas Trees, Batman!!!
I sure hope this works! Downloading to AFH now so if it works, great. If it doesn't, I guess I will be mailing in a phone or taking it back for a replacement to Best Buy. Either way, I'm not going to be sweating it too much. But if this works for the community, I will be very happy to have helped you all out.
The tool for T-Mobile was out in August. This appears to have been modified in October. Pretty confident that it "might" work. However, until I successfully complete the remote session, I will NOT share the link to my AFH for the file in the event it is faulty or I have been misinformed. If they make it worse then so be it, I'll just exchange it as broken at Best Buy and call it a day.
Jaybone073 said:
Well, it definitely appears to be somewhat recent! Holy radioactive Christmas Trees, Batman!!!
Click to expand...
Click to collapse
Not sure why you're so excited. The filename indicates it's just an updated version (contains OxygenOS version O.07) of the TMo tool, and the modified date show that it was untouched, i.e. strictly TMo and unflashable on unlocked variant.
You need to persuade the representative to pass you something that starts with "Dre9".
AndyYan said:
Not sure why you're so excited. The filename indicates it's just an updated version (contains OxygenOS version O.07) of the TMo tool, and the modified date show that it was untouched, i.e. strictly TMo and unflashable on unlocked variant.
You need to persuade the representative to pass you something that starts with "Dre9".
Click to expand...
Click to collapse
I'm not a developer, more like a well informed or advanced user. If they have indeed screwed the pooch here it's going to be on multiple fronts. On every occasion when I've called and emailed OP they have asked for the case number and verified the build I was on, the model, asked for the receipt on multiple occasions and verified the IMEI and model every single time. It's like this dance with them. If the tool hasn't been modded to add unlocked variant support, I would be shocked that they've verified it that many times only to get it wrong and have this be unsuccessful.
As stated earlier... I may very well be a guinea pig for this and one of the first to do this since that.
The plain and simple truth is that we may not know for sure that the update doesn't simply remain the same tool with a line of code added to it to simply add unlocked support.
We simply will not know until the process starts and that will be at 1:25PM EST today.
Please don't take the above statements as me bashing you. I can plainly see by your years here and multiple devices and posts that you're much more informed than I am about this. And I most certainly will ask if there have been modifications to support my specific model before we start. The download count of that updated file was only 13 times when I downloaded the file so it hasn't been widely issued out.
UPDATE: THE TECH CONFIRMED THAT THEY WERE AWARE THAT I HAVE THE UNLOCKED VERSION AND THAT THEY ALSO HAVE SUCCESSFULLY FLASHED UNLOCKED DEVICES BEFORE WITH THIS TOOL. When it was extracted, the tool became MSMV5.19 if that helps. They also logged in via the others in the dropdown box and I can too. I was allowed to keep the tool!!!!
dre8t_10_O.07_211014.tar | by jaybone073 for Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
WARNING!!! The technician confirmed that this does work. However, my remote session was UNSUCCESSFUL because the ocdt was a mismatch. Their project number is 20818 and my ocdt number is 2083c. If there was a way to edit that in fastboot or fastbootd or by dumping the file in the update as an image I would seriously flash that and try. I DO NOT RECOMMEND DOING THAT!
The tool could NOT complete the update and it will have to be sent in!
7zip and BreeZip DID NOT WORK - USE WinRar to extract all files and open all files!
Jaybone073 said:
I'm not a developer, more like a well informed or advanced user. If they have indeed screwed the pooch here it's going to be on multiple fronts. On every occasion when I've called and emailed OP they have asked for the case number and verified the build I was on, the model, asked for the receipt on multiple occasions and verified the IMEI and model every single time. It's like this dance with them. If the tool hasn't been modded to add unlocked variant support, I would be shocked that they've verified it that many times only to get it wrong and have this be unsuccessful.
As stated earlier... I may very well be a guinea pig for this and one of the first to do this since that.
The plain and simple truth is that we may not know for sure that the update doesn't simply remain the same tool with a line of code added to it to simply add unlocked support.
We simply will not know until the process starts and that will be at 1:25PM EST today.
Please don't take the above statements as me bashing you. I can plainly see by your years here and multiple devices and posts that you're much more informed than I am about this. And I most certainly will ask if there have been modifications to support my specific model before we start. The download count of that updated file was only 13 times when I downloaded the file so it hasn't been widely issued out.
UPDATE: THE TECH CONFIRMED THAT THEY WERE AWARE THAT I HAVE THE UNLOCKED VERSION AND THAT THEY ALSO HAVE SUCCESSFULLY FLASHED UNLOCKED DEVICES BEFORE WITH THIS TOOL. When it was extracted, the tool became MSMV5.19 if that helps. They also logged in via the others in the dropdown box and I can too. I was allowed to keep the tool!!!!
dre8t_10_O.07_211014.tar | by jaybone073 for Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
WARNING!!! The technician confirmed that this does work. However, my remote session was UNSUCCESSFUL because the ocdt was a mismatch. Their project number is 20818 and my ocdt number is 2083c. If there was a way to edit that in fastboot or fastbootd or by dumping the file in the update as an image I would seriously flash that and try. I DO NOT RECOMMEND DOING THAT!
The tool could NOT complete the update and it will have to be sent in!
7zip and BreeZip DID NOT WORK - USE WinRar to extract all files and open all files!
Click to expand...
Click to collapse
I guess I'll keep my expectations low since it didn't work for you .. but after download I'll give it a shot
So it is exactly as I thought - they just sent you the TMo package.
Jaybone073 said:
the ocdt was a mismatch. Their project number is 20818 and my ocdt number is 2083c.
Click to expand...
Click to collapse
Yes theoretically you can unpack/repack the ops, but you need A TON of partitions from the unlocked variant, and I'm not sure that all of them can be extracted out of a device, and also without a full MSMDT conversion I'm not even sure if you still qualify for OTAs.
This topic will remain fruitless until someone persuades a "dre9" package out of them.