Related
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
UPDATE: found a stock system image dump, thank you to @lopestom for directing me to this. This guy's been the MediaTek king for as long as I can remember.
It appears to be a dtbo and system partition dump. It also has the vendor partition and a (partial?) boot image dump. Not sure if things like the full boot and recovery images are stored somewhere in here, I didn't look too deeply into it yet. I have no idea how whoever this is managed to pull these partitions... they either got root access somehow, or they found a proper Download Agent and Auth file to pull it all. Either one of these would be awesome. I reached out to the user to ask them how they did it, we will see what they say if they want to share how they did it.
https://git.rip/dumps/att/u304aa
jasonmerc said:
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
Click to expand...
Click to collapse
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
sjjtnj said:
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
Click to expand...
Click to collapse
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
jasonmerc said:
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
Click to expand...
Click to collapse
Right, I'm considering giving him my current phone when I get a new one. It doesn't seem like I'm going to be able to unlock and root it so I want a phone I can. Mainly for space personally. He's young so he doesn't need it rooted, but I'm thinking if I can root it then I might be able to use it to root my phone. Speaking of rooting I think I found a way to root this phone. It took me a couple days to get the phone since he said he couldn't find it, but I have it now. It just needs to charge, but the battery sucks so it takes forever. I did find out that it does have a decent recovery. I had booted it into recovery and then I was messing around with the keys after the little passed out green guy popped up and suddenly it loaded stock recovery. It had an option to mount the system and flash with adb and everything. The only problem is I kept booting it by messing with keys. So I honestly don't know which ones worked. I kept booting into it last night by messing with them, but now I can't seem to get it to boot into the right recovery now that I'm trying to figure out the right key combination. I will figure it out though (eventually) and let you know what you have to click, but if you get the chance just mess with it and hopefully you'll find it like I did.
Also I was looking up the phones variants and downloaded a couple stock roms that I felt had all the right specs I'm going to try to flash one if I can get it plugged in. I downloaded custom twrp image's for them as well, and even found one twrp that I was able to download in the app. If you used it then you know that it takes you to a download page if you are downloading the wrong twrp.img. So the fact it let me download it in the app meant it tricked twrp into thinking it was that phone. So I'm going to try that stock rom first. Maybe we'll be able to change it to another model. It really needs something flashed, because it's a mess. I thought he messed it up, but after reading what you said maybe it's just the phone. He's young so it doesn't matter as much to him, but I feel bad for my niece. I really need to look into at least getting her another phone. I'm going to work on it later today and see what I can do. First I got to get it to work on the computer, but I may be able to root it without the computer. I'll keep you updated with my progress.
any luck with this?
Yeh, is there a status update?
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
sjjtnj said:
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
Click to expand...
Click to collapse
I need to unlock my phone U304AA
Ok boys and girls, in case anyone is still wondering here is how to root this sucker.
https://drive.google.com/file/d/1--Ul1ae73zcejNuJ1a7ftq5sTo2VP8Ya/view?usp=drivesdk
Comes with two files. Mtksu amd magisk be sure to use the magisk version included in the zip. Install mtksu then wmagisk, open mtksu and install the top magisk option. Reboot then open magisk hit install when it asks. Now open mtksu scroll to the bottom and hit activate and reboot again. Should be good too go at this point. Oh yeah be sure to click apply at boot in mtksu. Not sure if this had been posted before or not. Now, to find a way to unlock bootloader and install twrp.
Thank you, I tried Mtksu on mine and it didn't work, but it might've been the phone. I don't have one of these anymore, but I hope you all the best of luck. For the bootloader and Twrp try Flashfire or flashify.
MTK bypass method released by some smart dudes out there. I will test if we can use SPFT on this phone now. Stay tuned. This could mean root & recovery in a matter of minutes.
EDIT: It ALMOST works. Technically it bypassed the auth file as advertised. The only thing left now is finding a compatible preloader/scatter file to use.
Used a modified Moto E6 Play scatter file to pull images from the device. Tried flashing over stuff and got an error. Long story short my U304AA is now permanently bricked, so I'm tapping out of this project here
I do have recovery and boot images that (supposedly) work if anyone else wants to try and take over Keep in mind these were pulled with a scatter file from a DIFFERENT phone that's of the same chipset, so not everything is guaranteed to work. For example, the preloader was pulled with the specified parameters but I do NOT know if it's functional
Because I'm tapping out, and because nobody else seems to have anything on this, I'm uploading everything I can. Some pulls are too big to upload and some just won't work for some reason, but use whatever you'd like for anything you can. Hope I did something helpful
I have searched in Google Search and the tutorials forum but not found a tutorial
_____________
Sent from my website: https://topsanphamhay.com/kem-chong-nang-danh-cho-da-dau-mun.html - https://topsanphamhay.com/kem-chong-nang-innisfree-perfect-uv-protection-cream-co-tot-khong.html - https://topsanphamhay.com/kem-chong...ifying-face-fluid-dry-touch-co-tot-khong.html using Iphone X
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
My wife and I just got one, so now I have two of these but I'm not sure I trust AT&T enough to use the "free" phone that they sent.
It would be great if someone can pickup this project, especially since so many phones are now flooding the market.
I just got 3 of these "free" from AT&T. In fact I don't really need them, I just happen to have phones with an IMEI number that AT&T cannot decipher, so they sent me new phones just in case I can't use 4G.
Anyway, I'm trying to use mine as spare Google assistants scattered around the house, but because they run that crappy Android Go, the Go version of Assistant won't listen to me until I long-press the home button. I would also like to use them when I travel as a spare.
These things are essentially throw-away, so I'm OK to risk bricking one of them.
What I really want to do is install a real version of Android on here, has anyone managed to crack this yet?
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
kayshinonome said:
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
Click to expand...
Click to collapse
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
luridphantom said:
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
Click to expand...
Click to collapse
Not possible to do, already tried before when I didn't brick it
KJ7LNW said:
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
Click to expand...
Click to collapse
Just got mine from this. I'd like to install something like NixOS mobile, but I've never used an android phone before. Will that be possible on this phone? If so, is there a good guide for newbs like myself?
I've been getting help in the Newbie thread, but it's time I start a new topic, since it's getting harder and harder to find replies.
All I'm trying to do is upgrade an old LG from Android 5.0 to 6.0. That's it.
I've got the drivers installed. I've downloaded three different versions of Flash Tool. The only one I got to do anything was "Flash Tool 2014".
The first time I ran it (following the directions on the web page where I found it), I picked "CDMA", "DIAG", and "CSE Flash". I was able to pick "Other Country" and "English" and got the phone to start installing. However, it only got as far as 4% and gave me an error. Now, when I run it, I pick "Other Country" and can't even pick a language. They're all blank. If I continue, all the messages consist of Question Marks, however, it still gets as far as 4% before stopping.
The phone is bricked in Download Mode. I have tried two different USB cables, two different computers, one of which has Windows 7 & 8.1 installed. I've tried all different USB ports to make sure I'm on USB 2.0 and not 3.0. I've tried running in Administrator Mode.
I see many posts about the 4% Error. The solution involves downloading a "wx.dll" file and putting it in the C:\system32\LGMOBILEAX\PHONE folder, but that didn't work. I also so one that said when you get the error, take the battery out of the phone, unplug it, put it all back together, and then Continue. That didn't work either.
What else can I possibly do? Thanks.
Hey, I have been trying to find a rom for 6.0 and I can't find anything. The only way to get to 6.0 is through ota. If you have 5.0 then your lucky. Ota can only be used if you still have a sim card that's active in the phone. There isn't roms for stock android 6. I would try and help but I can't.
If anyone finds away to get stock 6.0 please let me know.
Talking about your issue of your phone being bricked, there is many unbrick methods. I personally used https://forum.xda-developers.com/t/...n-qualcomm-hs-usb-qdloader-9008-mode.2933853/ it helped and fixed my issue. I still had my device info wiped off my phone somehow but at least it works. Your at a issue with a flash tool, fresh reflash with that method I sent if you can use it and start over. I can guide you through it if needed.
You might be stuck at a stand still, tell me what your phone says in device manager. You probably flashed a bad firmware. In that case I used the method above.
Ive uploaded signed Qualcomm driver's I found that install on windows and don't turn on test mode. These work. Then afterwards toggle USB options with device plugged in PC ,change from charging to PTP and let it automatically install drivers. Rebooted and opened msm tool and Is connecting and now showing 2 ports. Hope this works for anyone having trouble ; as earlier I had no Qualcomm driver's installed and no ports showing on msm tool after many attempts to install drivers. I'm now ready when something comes along to flash. After rebooting PC use cmd window adb reboot edl. Will then show up on msm tool as connected. When installing Qualcomm driver's choose first option Wwan is not used to get Ip address. If this works for you hit the like button "it's free". I've seen many people complaining they can't connect to msm tool. This fixed my issues. Tested on windows 10 pro
Driver's. https://drive.google.com/file/d/1AOeuMj6D5f6H4yhAC1QKGN437qV9YmJs/view?usp=drivesdk
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
XNine said:
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
Click to expand...
Click to collapse
No additional driver's need to make Qualcomm devices/one plus phones to connect to msm tool.
illusiveairforce said:
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Click to expand...
Click to collapse
You don't use the factory one use the one above or below. It's a tool that relocks bootloader and flashes device to original firmware that it was shipped with. It's an anti-brick tool so to speak.
I still cant get it to work. the driver looks to be working and MSM identifying it
but no matter what i do it wont progress. i cant adb reboot because adnb nor fastboot are responsive. the phone just disconnectes and reconnects USB over and over and thats it. no button combo of volume keys and power being held for along time seems to work either.
I finally got it functional and now at "Image does not match" tried on 3 other machines with 3 seperate MSm installs.
9 5G LE2115 is my phone I bought directly form OnePlus. Idk what to do from here.
Usually kicks up that warning if your trying to use the wrong msm tool.?
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
applyscience said:
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
Click to expand...
Click to collapse
What about that global fastboot rom I linked you to?
mattie_49 said:
What about that global fastboot rom I linked you to?
Click to expand...
Click to collapse
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
applyscience said:
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
Click to expand...
Click to collapse
You were able to get back from aospa though right? Via msm
mattie_49 said:
You were able to get back from aospa though right? Via msm
Click to expand...
Click to collapse
i always had fastboot access during that, i just was too stupid to extract my own img files form the paylod dumps (theres so many guides online, i just suck with it) anyhow, after you hooked me up with download i just ran the the imgs in a flash-all bat file to clean up both slots of the phone and it was wonderful. as soon as i went to the unofficial lineage my phone just gave up. 2 reboots later.
im not sure what im going to do. its been a long day and not too pleased with myself so im trying to just procrastinate it till tmw or sunday.
[17784][07-04 07:23:08.893]<4> [3] [CSerialCommHelper] No data in buffer to be sent 0
[17784][07-04 07:23:11.061]<4> [3] [SP][195] Check cmd done status failed. 1
this is the 2 lines in the log that have ruined my weekend.
I'm investigating possible solutions to common MSM errors that prevent flashing.
See the following thread and feel free to try the steps outlined if you're brave enough.
Please report back your findings.
[ADVANCED] [UNTESTED] Possible Fix - MSM Errors (Sahara, Param info, etc)
WARNING: THE FOLLOWING IS FOR INFORMATIONAL PURPOSES ONLY AND MAY FURTHER DAMAGE YOUR DEVICE. EXERCISE EXTREME CAUTION. USE ONLY AS A LAST RESORT. This was tested with a Global OnePlus 9 LE2115 Overview So I was encountering an error with MSM...
forum.xda-developers.com
Can you re-up these? I'm getting a 404 on the google drive link.
Ethanadams642 said:
Can you re-up these? I'm getting a 404 on the google drive link.
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
Hi all, sorry for the total noobness of this post but I'm really struggling to get my Oneplus 8t back to stock.
I have the KB2000 version. It came to me from ebay with the global software. Everything worked fine and I could update straight from the phone.
I'm new to all this but decided to try pixel experience. I followed the guide from the pixel experience thread here on XDA, unlocked the bootloader and installed and everything was fine. I'm having an audio issue with the pixel experience though and decided I want to go back to stock software and lock the bootloader. Plus I might end up selling the phone on ebay soon so need to get it back to a normal state!
I tried to use MSM but ran into a problem. It wouldn't recognise my phone in MSM. ADB and Fastboot see the phone but not MSM. I have a qualcomm driver exclamation mark in device manager. At first it said something about qualcomm bulk but I installed drivers. That changed to say something else. Think it was qualcomm 9008 but I still have the driver exclamation mark like the drivers aren't installed.
Can anyone help let me know where I might be going wrong??
Any help would be appreciated!
Disable driver signature verification and reinstall the drivers.
After successfull driver installation MSM should do it job.
flyingfrome said:
Hi all, sorry for the total noobness of this post but I'm really struggling to get my Oneplus 8t back to stock.
I have the KB2000 version. It came to me from ebay with the global software. Everything worked fine and I could update straight from the phone.
I'm new to all this but decided to try pixel experience. I followed the guide from the pixel experience thread here on XDA, unlocked the bootloader and installed and everything was fine. I'm having an audio issue with the pixel experience though and decided I want to go back to stock software and lock the bootloader. Plus I might end up selling the phone on ebay soon so need to get it back to a normal state!
I tried to use MSM but ran into a problem. It wouldn't recognise my phone in MSM. ADB and Fastboot see the phone but not MSM. I have a qualcomm driver exclamation mark in device manager. At first it said something about qualcomm bulk but I installed drivers. That changed to say something else. Think it was qualcomm 9008 but I still have the driver exclamation mark like the drivers aren't installed.
Can anyone help let me know where I might be going wrong??
Any help would be appreciated!
Click to expand...
Click to collapse
You could use TWRP to install stock OOS. Just follow the OP's instructions in the TWRP thread: https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2022-03-09.4302449/
I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9
Flash by edl if you can't do it then pm I'll fix it by tv
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.
I had this problem because I flashed a custom kernel on a custom rom today
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.