My mobile phone system is the o12c10 version, and then I downloaded the o12c11 version, but I found that the OTA channel is not displayed on the mobile phone, so I directly used fastbootd to brush into the playload. Bin file in FastBoot mode (not FastBoot mode, but FastBoot mode)
After that, I can't start the machine directly, can't enter any mode, and 9008 can't get in
Long press to enter 9008 or any other mode will not respond, and there will be no vibration feedback
When charging, the screen is also black and does not display
The computer interface didn't respond. I've tried line breaks, too
I tried the original cable, lightning cable and USB port
The driver also attempts to uninstall and reinstall the new driver
The computer device manager window still does not show any new devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I got the remote consultation service. The second-line remote service learned about the situation and didn't solve it remotely. It suggested that I send it for repair, but the epidemic situation was blocked and I couldn't send it for repair
How to solve this situation
emergency----------------
English is not my native language; please excuse typing errors.
2023/03/02to update：XDA post-88110375 comments
Solution：How to prevent and remedy the crash caused by wrong XBL
It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.
ppajdek said:
It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.
Click to expand...
Click to collapse
yeah, it's gone with the wind, motherboard replace is the only solution
nkhater said:
yeah, it's gone with the wind, motherboard replace is the only solution
Click to expand...
Click to collapse
Ok, I have to pay more attention to the next time I swipe the system, so as not to make such a mistake again, thank you
ppajdek said:
It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.
Click to expand...
Click to collapse
Thank you for letting me know what's wrong with me. It seems that I should pay more attention to this next time I swipe the system
小忧忧 said:
Ok, I have to pay more attention to the next time I swipe the system, so as not to make such a mistake again, thank you
Click to expand...
Click to collapse
What do you mean will pay more attention, this is catastrophic, there is no room for error, you make a mistake and your investment is gone. This is new to OnePlus, I have been using their phones from day one, never thought this will ever happen.
nkhater said:
What do you mean will pay more attention, this is catastrophic, there is no room for error, you make a mistake and your investment is gone. This is new to OnePlus, I have been using their phones from day one, never thought this will ever happen.
Click to expand...
Click to collapse
Maybe the translation quality of the translator I use is not so perfect.
I prefer to experience other third-party systems without adaptation, so I will brush GSI
Therefore, I will pay more attention to these problems in the process of system brushing in the future
I solved this problem, and the specific solutions for details have been updated to my blog (need to translate, my English level is not good)
link:How to prevent and remedy the crash caused by the wrong XBL
小忧忧 said:
I solved this problem, and the specific solutions for details have been updated to my blog (need to translate, my English level is not good)
link:How to prevent and remedy the crash caused by the wrong XBL
Click to expand...
Click to collapse
My browser wont load the pictures and if im rifht they would show me the "line" to enter.
According to the description above, we can buy an engineering cable to connect to your phone
Then use this line to perform the normal 9008 flashing operation to save your phone
Just to be sure, we can use an Engineering cable to unbrick our devices?
little follow up here, would that work ? i did the same thing years ago with a Lenovo ZUK Z2 Pro, taped aluminium inside the usb connections which i saw from youtube on how to do that, and it reviewed my dead phone into edl from where i could flash stock roms
would this also work on our oneplus 8 pro ?
i hope we can figure stuff out here, threw away my dev-usb cable years ago, would try making a new one
Please tell me if any of you have been able to revive our 8 pro with this cable? or similar
Winstarshl said:
Please tell me if any of you have been able to revive our 8 pro with this cable? or similar
Click to expand...
Click to collapse
Yes it works, read here.
xtcislove said:
My browser wont load the pictures and if im rifht they would show me the "line" to enter.
According to the description above, we can buy an engineering cable to connect to your phone
Then use this line to perform the normal 9008 flashing operation to save your phone
Just to be sure, we can use an Engineering cable to unbrick our devices?
Click to expand...
Click to collapse
ikram.senguen said:
little follow up here, would that work ? i did the same thing years ago with a Lenovo ZUK Z2 Pro, taped aluminium inside the usb connections which i saw from youtube on how to do that, and it reviewed my dead phone into edl from where i could flash stock roms
would this also work on our oneplus 8 pro ?
i hope we can figure stuff out here, threw away my dev-usb cable years ago, would try making a new one
Click to expand...
Click to collapse
Winstarshl said:
Please tell me if any of you have been able to revive our 8 pro with this cable? or similar
ppajdek said:
Yes it works, read here.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Sorry, due to some work and network problems, I can't follow up XDA's posts in time. Besides, my English is not good. I use Google Translate, so some abnormal sentences may appear in the text. Please forgive me
Many people have encountered the same problems as me, which are solved by using the project line mentioned in How to prevent and remediate the crash by wrong XBL
One of my friends couldn't buy a data line because of some factors. He tried to understand the method of data line short circuit, but the test failed to enter 9008. Other group friends also bought the short data line test mentioned in How to recover your device after flashing incorrect DDR xbl images, but failed to enter the final test. (It is also possible that the line used in this article is qualified? But I can't buy it in my region, so I can't test it)
It is worth noting that the 22K resistor is used in the product description of the engineering data line introduced in my article. I think that's the key
I tried to search the platforms you can buy in your country, but I didn't find the data line
However, I found pcb2.0. It has a lot of internal resistance. Its appearance is roughly as shown in the figure below. This may help you
Related
So I bougjt an LG G2 (international - D802) and I f***ed it up a bit.... Sadly it can not be fixed for some reason. It is stuck in fast boot mode, and I can not boot into recovery or download mode.... So I bought another LG G2 but this time an verizon. (32gb) And I'm planning on combining the 2 together because the verizon has an cracked screen and an not reacting touchscreen.So I want to replace the verizon's screen with an international one. So is there something I need to know? I just really want my g2 to work again..... It has been broken for about 3 months now....
Please help, because I don't want to break another g2
That isn't so nice that you couldnt use it for 3 months. I dont know what you should watch on since so far as i know only that there are 2 display variants lgd/jdi but there isnt an different digitizer on the phone so far as i know. The only thing that would be maybe is that the verizon logo is missing on the front if the original had one. To be sure that there aren't differences google about it and google the displays and see if you can see a difference on the display's. With that i mean differences with the cables, the parts on the digitizer/display and the pcb(greenish thing most time where the parts are on. I can't really find it out for you since i need to sleep now because its 3:02 AM, I hope that i helped you and that you can fix your problem. If i will remember it then i will make an research on it and i will post it here if you couldnt find if its possible or not. ?
wulsic said:
That isn't so nice that you couldnt use it for 3 months. I dont know what you should watch on since so far as i know only that there are 2 display variants lgd/jdi but there isnt an different digitizer on the phone so far as i know. The only thing that would be maybe is that the verizon logo is missing on the front if the original had one. To be sure that there aren't differences google about it and google the displays and see if you can see a difference on the display's. With that i mean differences with the cables, the parts on the digitizer/display and the pcb(greenish thing most time where the parts are on. I can't really find it out for you since i need to sleep now because its 3:02 AM, I hope that i helped you and that you can fix your problem. If i will remember it then i will make an research on it and i will post it here if you couldnt find if its possible or not. ?
Click to expand...
Click to collapse
Yeah, I had already googled it and I didn't found any weird corners or parts at the display that could be a problem. And I actually don't like the verizon logo at the front haha.
I will keep you posted if it works or not! Hope you had a good night rest =p
FritsPikee said:
Yeah, I had already googled it and I didn't found any weird corners or parts at the display that could be a problem. And I actually don't like the verizon logo at the front haha.
I will keep you posted if it works or not! Hope you had a good night rest =p
Click to expand...
Click to collapse
Ahh alright but i don't think its compatible those two models with the display sorry for late reaction since I can't really see where i replied before easy on desktop and thanks yes i had a good night rest till i woke up...
Compare the 2 Pictures you can also magnify it, the only difference i saw was in the small cable up in the pictures so far as i know that part is for the touchscreen to control the above half i believe. So the only difference between these 2 are the touchscreen i think, you can open and try it but i don't think it will work. Maybe you can describe more about your fastboot problem and we could fix your device?
http://www.etradesupply.com/lg-g2-vs980-lcd-screen-and-digitizer-assembly.html
http://www.etradesupply.com/lg-g2-d802-lcd-screen-and-digitizer-assembly-black-22089.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@FritsPikee try these things to get out of fastboot mode:
The first one which is also suggested by me post #132:http://forum.xda-developers.com/showthread.php?t=2680150&page=14
Btw, Download the stock img files from here if you have d802: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
Just execute all those things but i think that you can use TWRP instead of the original recovery or some other kind of recovery But i am not sure
so do that recovery thing at your own risk :/
or if that doesn't work try this one but its not really well explained.: see fix 4: http://forum.xda-developers.com/showthread.php?t=2694530
If you have some other fastboot mode problem then reply again to this thread or add me on Facebook:Wulsic then i can also help you maybe with it.
wulsic said:
Ahh alright but i don't think its compatible those two models with the display sorry for late reaction since I can't really see where i replied before easy on desktop and thanks yes i had a good night rest till i woke up...
Compare the 2 Pictures you can also magnify it, the only difference i saw was in the small cable up in the pictures so far as i know that part is for the touchscreen to control the above half i believe. So the only difference between these 2 are the touchscreen i think, you can open and try it but i don't think it will work. Maybe you can describe more about your fastboot problem and we could fix your device?
http://www.etradesupply.com/lg-g2-vs980-lcd-screen-and-digitizer-assembly.html
http://www.etradesupply.com/lg-g2-d802-lcd-screen-and-digitizer-assembly-black-22089.html
@FritsPikee try these things to get out of fastboot mode:
The first one which is also suggested by me post #132:http://forum.xda-developers.com/showthread.php?t=2680150&page=14
Btw, Download the stock img files from here if you have d802: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
Just execute all those things but i think that you can use TWRP instead of the original recovery or some other kind of recovery But i am not sure
so do that recovery thing at your own risk :/
or if that doesn't work try this one but its not really well explained.: see fix 4: http://forum.xda-developers.com/showthread.php?t=2694530
If you have some other fastboot mode problem then reply again to this thread or add me on Facebook:Wulsic then i can also help you maybe with it.
Click to expand...
Click to collapse
Sorry for the late reaction, but this is what happend;
I wanted to backup my whole system just in case something would go wrong. So I installed cwm and when I booted my phone in recovery mode it was giving me a 'secure boot error'. But I accidently made a backup with the cwm error (I thought it was still the original recovery but it wasn't) then iI installed twrp 2.7 for lg g2 and that worked just great =). I made my backup. But then there was an software update from android (not google play) so I clicked on the 'install update notification' and my phone turned of and back on. but it booted in twrp instead of the original recovery (duh!) I looked it up on internet and found a command line I had to fill in in the twrp menu (something with 'dd if=/' etc). that fixed the problem but still the update wasn't installed. So I installed my old recovery back (the backup I made but what wasn't the original recovery. I installed the cwm 'secure boot error" recovery back). After I click again on the 'install update notification' my phone went in a bootloop with the 'secure boot error'
then I followed the Instructions in this tread: http://forum.xda-developers.com/showthread.php?t=2582142 And I got it out of the secure boot error thingy, but than it got in the fastboot boot loop =( And that's the whole story ...
i hope you can go something with it! Again, sorry for the late reaction!
You mean lg logo then fastboot? If so then the kernel isnt good. And you gotta replace it :/
wulsic said:
You mean lg logo then fastboot? If so then the kernel isnt good. And you gotta replace it :/
Click to expand...
Click to collapse
Yeah, first the logo and then fastboot, and i tried this tread: http://forum.xda-developers.com/showthread.php?t=2477595
But it didn't worked =( (btw I live in the netherlands to!!)
@FritsPikee ahh okay, maybe its easier if we talk with facebook or something like that my facebook is facebook.com/wulsic1, skype hangouts etc is just wulsic because facebook got bugged when i changed my username.
Because if i will talk dutch to you then it is easier and english is the language you must speak here at xda so yeah. Do you still have custom recovery or is that also gone?
wulsic said:
@FritsPikee ahh okay, maybe its easier if we talk with facebook or something like that my facebook is facebook.com/wulsic1, skype hangouts etc is just wulsic because facebook got bugged when i changed my username.
Because if i will talk dutch to you then it is easier and english is the language you must speak here at xda so yeah. Do you still have custom recovery or is that also gone?
Click to expand...
Click to collapse
I've send you an skype request! But I need to go now, so I'll be back in about 2 hours
@FritsPikee alright i will try to help you then if i dont have to eat then.
I've been digging around online and can't find anything that helps me in my case.
Here's my stupidity: I flashed a kernel that was not intended for my phone (meant for Note 2). Reboot and dead screen. Can't get into download mode, recovery, nothing. Removed battery. Didn't help. Plugged into computer. Doesn't pick up anything connected. Odin doesn't see it. Tried RIFF. Can't get it to install the drivers it's supposed to. I saw something about jig dongles that can force it into download mode but I don't know about that.
What really stinks is I had just compiled SheepShaver for android and it took a few hours of work and I really don't want to do that all over again. Also pictures of my father who's just passed away are on there.
Am I screwed? Is there any way at all to get the proper kernel flashed back on this thing without a wipe? If not is there any way I can fix this phone? I have a semi-recent backup (about a month old) on my SD card. I have both Titanium Backup and a full nandroid backup on the SD.
Someone please come to my rescue. I've logged countless hours on this phone and I love it. All this because I couldn't get SELinux to go permissive...
You already know the answer. If you flashed a kernel not for your device and with the symptoms you have, your hard bricked. Jtag is the answer.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You already know the answer. If you flashed a kernel not for your device and with the symptoms you have, your hard bricked. Jtag is the answer.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Do you know if these guys are the real deal? http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair
I don't have the equipment to jtag it myself. Also just to be perfectly clear; An incorrect kernel cannot be fixed with a download mode jig correct?
mascondante said:
Do you know if these guys are the real deal? http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair
I don't have the equipment to jtag it myself. Also just to be perfectly clear; An incorrect kernel cannot be fixed with a download mode jig correct?
Click to expand...
Click to collapse
mobiletechvideos.com have gotten high reviews on xda. They're the only ones I'd use.
Edit, I'm not sure they're the same as your link
Edit, edit it looks like they're the same guys
Edit, edit edit I don't know about the jig. It could get you into download mode.
Sent from my Nexus 5 using XDA Free mobile app
mascondante said:
I've been digging around online and can't find anything that helps me in my case.
Here's my stupidity: I flashed a kernel that was not intended for my phone (meant for Note 2). Reboot and dead screen. Can't get into download mode, recovery, nothing. Removed battery. Didn't help. Plugged into computer. Doesn't pick up anything connected. Odin doesn't see it. Tried RIFF. Can't get it to install the drivers it's supposed to. I saw something about jig dongles that can force it into download mode but I don't know about that.
What really stinks is I had just compiled SheepShaver for android and it took a few hours of work and I really don't want to do that all over again. Also pictures of my father who's just passed away are on there.
Am I screwed? Is there any way at all to get the proper kernel flashed back on this thing without a wipe? If not is there any way I can fix this phone? I have a semi-recent backup (about a month old) on my SD card. I have both Titanium Backup and a full nandroid backup on the SD.
Someone please come to my rescue. I've logged countless hours on this phone and I love it. All this because I couldn't get SELinux to go permissive...
Click to expand...
Click to collapse
Install drivers riffbox and use this program, revive your galaxy
https://mega.co.nz/#!LVZSHbSb!jX5wqKImIiT3C_rKXcQvZDlCzH0jJbLe0V8h5JpZmcE
djdedonrg said:
Install drivers riffbox and use this program, revive your galaxy
https://mega.co.nz/#!LVZSHbSb!jX5wqKImIiT3C_rKXcQvZDlCzH0jJbLe0V8h5JpZmcE
Click to expand...
Click to collapse
Thank you. I'm trying. I installed those drivers. Trying to find the forum that explains how to use that tool. I saw that thread but it didn't have the download link anymore for the tool.
Update:
Huston I believe we have a problem:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried installing manually and I get an error about the file's hash doesn't match the cert.
dead s4
mascondante said:
Thank you. I'm trying. I installed those drivers. Trying to find the forum that explains how to use that tool. I saw that thread but it didn't have the download link anymore for the tool.
Update:
Huston I believe we have a problem:
View attachment 2917703View attachment 2917704
I tried installing manually and I get an error about the file's hash doesn't match the cert.
Click to expand...
Click to collapse
which program is that? link is dead.does someone has it?
emplokeas said:
which program is that? link is dead.does someone has it?
Click to expand...
Click to collapse
I think you will need the actual riffbox device. I've long since given up on trying to interface over USB. Riffbox talks directly to the memory chip. Need to be comfortable with soldering. But I do happen to have a link to the latest release of their software. http://www.unlockforum.com/showthread.php/riff-jtag-manager-v1-72-more-new-models-32724.html?
Thats the forum they use. The official site is riffbox.org
Sorry I don't know much else to tell you. If it won't boot it won't listen for a connection on USB. Some devices have a failsafe that activates a sort of programming mode over USB but the Galaxy S4 isn't one of those devices afaik.
Hey. I've bricked my Huawei P10 lite, literally just for the sole reason alone that I'm an idiot. I was in the process of relocking/unrooting when I did a massive choke - I've relocked the bootloader and IMMEDIATELY closed the goddamn tab. I haven't written the code down anywhere. When I've rebooted my phone, I discovered I have exactly 0 ways of doing a wipe, since the TWRP was obviously gone.
Hitools returns that the phone cannot be recovered due to not being supported.
Recovery? There isn't one. eRecovery always returns "failed to get.." yatta yatta yatta, It's not working.
The only thing currently reacting to my commands is fastboot. And, being the mr. obvious, I cannot push files onto the phone through fastboot to restore it by the full package, which was pretty much my only option at this point.
There aren't any replacement motherboards available for the P10 lite on eBay or pretty much anywhere else I could think of.
If there exists any good soul that can tell me if this is in any imaginable way reversible without getting a cracked screen phone and swapping the motherboards, PLEASE, PLEASE, do tell me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you.
INB4 anyone asks - No, I don't have the numbers to generate the code again either. At least not the serial id, i think.
EvESpirit said:
INB4 anyone asks - No, I don't have the numbers to generate the code again either. At least not the serial id, i think.
Click to expand...
Click to collapse
Did u tryed to flash original firmware by the dload method?
You don need unlocked boatloader for that. I already save my p10 few times.
hdemary said:
Did u tryed to flash original firmware by the dload method?
You don need unlocked boatloader for that. I already save my p10 few times.
Click to expand...
Click to collapse
How can I flash the original firmware? I can't even flash a recovery. The bootloader is l o c k e d, and the only thing I can access is fastboot. How am I supposed to push the files into the phones in fastboot???
EvESpirit said:
How can I flash the original firmware? I can't even flash a recovery. The bootloader is l o c k e d, and the only thing I can access is fastboot. How am I supposed to push the files into the phones in fastboot???
Click to expand...
Click to collapse
Man if you can't even google dload method to find out how to return to stock you r screwed.
But anyways i will help you with that: http://lmgtfy.com/?q=huawei+p10+lite+dload+method
I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
MOD EDIT: Mind your language
EvESpirit said:
I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
Click to expand...
Click to collapse
Man as your post title says, you really are a massive dumbass, if you at least try to help your self with the link i send you u will see that dload method dont need to boot into system, no need for recovery and no need for unlocked boatloader, only an sd card with a folder that have original firmware for your variant.
But as you rude keep your phone as a brick.
Regards!
EvESpirit said:
I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
MOD EDIT: Mind your language
Click to expand...
Click to collapse
Mind your language my friend.
This is an official caution for you.
If you have any doubts, check the FORUM rules
EvESpirit said:
>mfw mods ignore somebody attacking someone first and call me out for using bad language+edit the comment, yet still leave the actual swear happen without deleting
OMEGALUL so relevant
@hdemary If you would kindly learn to read. For the third time I'm telling you that ThErE Is No Way For Me to PUSH the FILES to the PHONE. I do not have an unlocked bootloader nor a functioning recovery AND NO DEVICE to put them on. Also nice OP dodge, but I guess that's just them being unbiasedly biased.
Click to expand...
Click to collapse
My last post in this thread.
Why u ask for help in the first place if you won´t accept?
Have fun with your bricked device!
Best of the best Regards! :angel:
Well, seems this thread has run its course
Thread closed
EDIT 2022-06-30: FOUND A RELIABLE SOLUTION FOR MY NEW T307U TABLET! May work for other models! https://forum.xda-developers.com/t/...e-it-as-a-normal-tablet.4316969/post-87091297
Original post from 2021-08-09 below:
Following this thread to no avail: https://forum.xda-developers.com/t/doordash-knox-customized-tablet-unable-to-remove.3890522/
Setup requires an internet connection, at which point it sets up MobiControl:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My friend's an IT so he set up Meraki for me which I can enroll in instead of MobiControl, but a minute later this pops up:
I still have access to the settings but cannot enable USB Debugging.
I flashed a combination file which got me to the "factory binary" where I can unlock OEM and enable USB Debugging, but I don't know where to go from here:
I flashed a stock ROM, but that doesn't get rid of doordash and MobiControl during setup.
Please help!
Which Android version did you flash? Did you finally get rid of MobiControl?
XDA.Samsung said:
Which Android version didn't you flash? Did you finally get rid of MobiControl?
Click to expand...
Click to collapse
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
genesisboy4 said:
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
Click to expand...
Click to collapse
Good to know. Congratulation. Does it still show secured by knox on boot screen?
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
XDA.Samsung said:
Good to know. Congratulation. Does it still show secured by knox on boot screen?
Click to expand...
Click to collapse
Yes, it does.
XDA.Samsung said:
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
Click to expand...
Click to collapse
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
genesisboy4 said:
Yes, it does.
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
Click to expand...
Click to collapse
Which version of Odin did you use?
XDA.Samsung said:
Which version of Odin did you use?
Click to expand...
Click to collapse
Odin3_v3.13.3
genesisboy4 said:
Odin3_v3.13.3
Click to expand...
Click to collapse
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
XDA.Samsung said:
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
Click to expand...
Click to collapse
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
genesisboy4 said:
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
Click to expand...
Click to collapse
Thank you. It looks like it's Android 9. Did you update it to Android 10?
XDA.Samsung said:
Thank you. It looks like it's Android 9. Did you update it to Android 10?
Click to expand...
Click to collapse
It's Android 8.1. If that file I mentioned is 9, then it's not the one I flashed, but was instead on my to-do list of troubleshooting steps. I was going to try flashing Android 9 and 10 but I got it working with 8.1 so I'm keeping it on that. Plus, the newer the android, the more secure Samsung Knox will be, so it will be harder breaking it.
Any idea where you downloaded it from? I cant seem to find a link.
quiqsilverr said:
Any idea where you downloaded it from? I cant seem to find a link.
Click to expand...
Click to collapse
Android 10: https://samfrew.com/download/Galaxy__Tab__A__/1hjk/VZW/T387VVRU3CUI2/T387VVZW3CUI2/
"The fact that it has MobiControl installed suggests it's a company device, and is therefore administered by that company's IT department. It's probably going to be difficult to remove MobiControl unless you talk to that IT department about it."
The above is a quote I found regarding Knox and the MobiControl app. Which tells me that this thread, although likely unintentional, is violating XDA Forum Rule #9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
XDA does not wish to be held liable for circumventing device security regardless of intent of the user, which is why I'm closing this thread.
-Regards: Badger50
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.
I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?
miris83 said:
I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?
Click to expand...
Click to collapse
sadly doesnt work since oem unlocking is off, and i cant access the os. it seems its in slot b right now, but i cant switch slots due to a locked bootloader.
any ideas would help
why use DSU?if you are stupid in this matter? say goodbye to the phone
Curiosity got the best of me. I used DSU cause I thought I would be able to keep it locked
Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.
Someone had to say it
miris83 said:
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.
Click to expand...
Click to collapse
Trash? I told the truth, if you're crying I'm sorry
You really forgot rule 1 in android modding.
Unlock.
The.
****ing Bootloader.
Seaman228 said:
Trash? I told the truth, if you're crying I'm sorry
Click to expand...
Click to collapse
And even more trash ... You are a waste of time, man.
gordonsosig said:
View attachment 5711879Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.
Click to expand...
Click to collapse
As I see it now, this might be your best bet at this point: https://forum.xda-developers.com/t/...t-centre-and-staff-14-september-2022.4492645/
The staff is pretty friendly. I already reported some bugs and it was just fine.
Use "fastboot getvar current-slot" to get your current slot then switch to the other slot with "fastboot --set-active=a" or "fastboot --set-active=b" I believe those commands work even with a locked bootloader.
Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
nguyenlucky said:
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
sadly i live in switzerland so there isnt any service center i can get to. so either we find a solution or the phone collects dust on my shelf
nguyenlucky said:
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
On the other hand the MSM tool may exist only as an internal tool which they might provide on request in such situations. As you pointed out in the article, they messed up the implementation. To be honest, I wonder how this may have happened in the first place - to boot into mode which should not be available with the booloader unlocked. And given the company has a past link with OnePlus and OnePlus does have an MSM tool ...
Unless @gordonsosig asks the support, he will not know.
Have a look here : https://forum.xda-developers.com/t/nothing-phone-1-flashing-utilities.4478457/
And there : https://forum.xda-developers.com/t/help-to-developers.4484061/
I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
And I think moderator should pin this thread to be always on top, because people should see the varning, this can save users from bricking their phones.
kuba3351 said:
I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
Click to expand...
Click to collapse
where do i send it? is it in person or mail in? any help is appreciated
I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.
kuba3351 said:
I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.
Click to expand...
Click to collapse
guess im ****ed. already contacted them but i bought the phone from ebay so they said just contact ebay