Database Develop

Well, I F'ed up... :(

OK, so...I was messing around, and I ended up flashing the wrong boot.img file.
The phone just kind of goes in and out of the LG booting screen, which didn't concern me too much, because...it was still turning on and such.
SO I tried to hook up into the LG Flash tool, and......it didn't work. I put my phone in download mode, and it comes on my computer as a QHSUSB_BULK, and it opens up 15 "portable devices", all of which are not formatted correctly except for one (which comes up as drive E.
In E, there is a folder that says "image" with the following contents:
modem.mdt
cmnlib.mdt
isdbtmm.mdt
playread.b03
playread.b00
playread.b01
mc_v2.b02
modem.b02
mc_v2.b00
mc_v2.b01
modem.b06
modem.b23
modem.b22
widevine.mdt
tqs.mdt
modem.b08
widevine.b01
widevine.b00
widevine.b03
widevine.b02
modem.b18
modem.b13
modem.b09
mc_v2.mdt
modem.b19
playread.b02
adsp.b00
adsp.b08
adsp.b09
adsp.b06
adsp.b07
adsp.b04
adsp.b05
adsp.b02
wcnss.b02
wcnss.b01
wcnss.b00
playread.mdt
mba.b00
wcnss.b08
mc_v2.b03
mba.mdt
wcnss.b07
modem.b14
adsp.mdt
modem.b16
modem.b17
modem.b11
modem.b12
wcnss.b06
wcnss.mdt
cmnlib.b00
cmnlib.b03
cmnlib.b02
tqs.b03
tqs.b02
tqs.b01
tqs.b00
cmnlib.b01
modem.b03
wcnss.b04
modem.b00
modem.b15
modem.b24
modem.b01
adsp.b03
dxhdcp2.b02
dxhdcp2.b03
dxhdcp2.b00
dxhdcp2.b01
isdbtmm.b03
isdbtmm.b02
isdbtmm.b01
isdbtmm.b00
dxhdcp2.mdt
adsp.b01
adsp.b11
adsp.b10
Things I can do:
Get into download mode, with crazy folders.
Get into some crazy Korean Screen with three options (Mode On, Mode Off, Cancel)
Turn the Phone on and off
Things I cannot do:
Boot into the OS
Boot into Fastboot
LG Flash Tools
ADB
If you guys want a screenshot of the korean screen, I can get you that. Maybe you can translate more of it, but I was only able to get the mode on and off, and the cancel part. Since I don't know what it does, I can't make it do anything.
If you want the files, lemme know, and I'll upload them.
Hopefully someone knows how I can fix this. Argh....
---EDIT---
Forgot to mention: Sprint Variant, if it makes a difference. I'm in the US. Thanks!
---EDIT2---
Adding the picture:
{
"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"
}

It should be fixable, but going to take some work. This thread will get you going in the right direction.
http://forum.xda-developers.com/showthread.php?t=2582142
Sent from my LG-D959 using Tapatalk

Going through it now, but virtual machines don't want to play nice for the moment. I'm going to have to fire up the old laptop and hope for the best...

Weeeeeeeeelllllllp.....
...it won't turn on now. I believe it is bricked. Squee.

You didn't use the same files from that link I gave you good you?
Sent from my LG-D959 using Tapatalk

kintwofan said:
You didn't use the same files from that link I gave you good you?
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
Well, I used the .bin files extracted from the TOT files I had before for the sprint gflex. I'm pretty sure that's where I made the mistake.

jkrlvgn said:
Well, I used the .bin files extracted from the TOT files I had before for the sprint gflex. I'm pretty sure that's where I made the mistake.
Click to expand...
Click to collapse
Yep I think they should have been .img files. I did not think I needed to specify to not use the g2 files from that link, glad you didn't.
Sent from my LG-D959 using Tapatalk
---------- Post added at 02:13 AM ---------- Previous post was at 02:12 AM ----------
Not that it changed the outcome though, sorry to hear. So there's no life now? What about plugged into computer
Sent from my LG-D959 using Tapatalk

Yeah, I saw the difference. *lol* No life in the device at all, my linux mint doesn't discover it anymore. I'm going to try it again when I get home -- had to get to work, damn it.
If it reads it on the computer, which I doubt, but...maaaybe....I'll try it again with some img files. it's ok if it doesn't -- I'll just go to see about replacing it tomorrow.

OK. Plugged it back into the computer, and it comes up as:
Qualcomm HS-USB QDLoader 9008
It doesn't show the 15 or so drives, and Linux doesn't read it at all.
LG Flash tool can see it sometimes, but it can't flash anything because it can't read the IMEI or anything on the phone -- fails every time.

Well unfortunately now you f'ed up
HS-USB QDLoader = hard brick
Sorry
Sent from my LG-D959 using Tapatalk

Yeppers. It's ok, it's my own fault -- HAVE TO PAY ATTENTION. *lol* Anyway, I'm going to see about what I can find on the net. Maybe I can get QPST or something to work with...something...or something....

Well I hope you find something. Let us know if you do
Sent from my LG-D959 using Tapatalk

I wonder if there's a way to reassign the IMEI and such with CDMA Workshop or QPST...? The LG Flash tool says it can't find the phone, but it reads the phone on the right port.

I take it this method does not apply to a phone that cannot be seen by a pc?

Well...probably not. I still get it showing up as an "unknown USB" device now, lately, but nothing past that. No worries -- I'm just grabbing at straws while waiting for payday.

Need aNew phone it's bricked. I learned my lesson all this flashing is not worth it. My note 2 died the same way
Sent from my LG-LS980 using XDA Premium 4 mobile app

It wont go into fastboot? That korean screen is just the hardware button selector. Pretty much asks you if you want to use your hardware buttons. If you can adb it and get it to reboot thru fastboot then u have a chance.
Sent from my LG-D959 using XDA Premium 4 mobile app

bonebeatz1234 said:
I learned my lesson all this flashing is not worth it.
Click to expand...
Click to collapse
You simply have to pay attention to what you're doing. If you're into flashing rom's and tinkering, I'd suggest you buy a Nexus device because they're easy to work with and hard to screw up.
I'm enjoying my G Flex just the way it is, there isn't any "must-have" root apps that are worth the trouble of going back to stock, or re-flashing this or that. Just look at all the problems people are having. Plus, I'm paying monthly on this device and have no interest in voiding it's warranty.

Visa Declined said:
You simply have to pay attention to what you're doing. If you're into flashing rom's and tinkering, I'd suggest you buy a Nexus device because they're easy to work with and hard to screw up.
Click to expand...
Click to collapse
That is why I went exclusively to Nexus devices several years ago when I traded in my Vibrant for the Nexus S. Since then I have had 4 Nexus devices and not a one of them have been bricked in any way, after thousands of flashed files have been done to them. On my Nexus 7 I think its impossible to kill it via a bad flash. I think you would need to pull the cable in mid flash of the bootloader for any damage to occur, lol... But for recovery and roms/kernels etc, its near impossible I think.
This is the first non Nexus device in a long time so I think I will stick to stock on it and just root it and do away with the bloat. lol

[NEW][15-08-2014][I9300UBUGNG1_I9300UBUGNG2_I9300UBUGNG1_ultra.

{
"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"
}
,theme pack green,,,lock button,,,buttons holo,,,keyboard note,,,,accuweather (widget transparency) edit ini --etc,,,,,ultra speed wifi.....
thaks:special credit for Aonja xda thanks..justarchi..&xda .
http://www.mediafire.com/download/2x3865ma5qmqjio/ultralite.zip
440-Mg.:good:
semi:http://www.mediafire.com/download/h5qvdh65x11l4p7/semiultra.zip
608Mg.
stock:http://www.mediafire.com/download/kuwc303tar2k5tm/complet-stock.zip
840Mg.

Hi dude,
sorry for complaining but the thread title is a bit confusing. Beside that you should add more informations/details about your work to OP.
Cheers.
- Occasus

Ultra speed wifi?! seriously? WiFi speed depends on your network speed, if you have 10mbps you cannot achieve 20mbps, but, ok.
Please correct your description also?

Okay, here some first impressions:
I've flashed this with the actual version of PhilZ Touch & there were no problems, the ROM booted up normally (it is based on Samsung's 4.3, just for the newbies). Played around with it a bit and thought by myself, okay, time for a reboot. I'm doing this always after a new ROM has come to my phone.
And that is where the trouble begins; the phone got stuck in bootloop and started to get really warm. I don't know what has happend, another try, same result.
Not usable for me. Fortunately, I've decided to put another ROM on my SD-Card too, just for the case that something goes wrong......
Cheers
- Occasus

No.
lsalamun said:
Ultra speed wifi?! seriously? WiFi speed depends on your network speed, if you have 10mbps you cannot achieve 20mbps, but, ok.
Please correct your description also?
Click to expand...
Click to collapse
I have 20mg. and with this rom I have reached the maximum photo look thanks.
magic can not be 10 to 20 mg. logical.
if I change parameters gps can do better or worse ....
if I change moden kernel can influence or not '
if I change the rom can do better or worse or not?
try and comment ... thanks.

thanks
Occasus said:
Okay, here some first impressions:
I've flashed this with the actual version of PhilZ Touch & there were no problems, the ROM booted up normally (it is based on Samsung's 4.3, just for the newbies). Played around with it a bit and thought by myself, okay, time for a reboot. I'm doing this always after a new ROM has come to my phone.
And that is where the trouble begins; the phone got stuck in bootloop and started to get really warm. I don't know what has happend, another try, same result.
Not usable for me. Fortunately, I've decided to put another ROM on my SD-Card too, just for the case that something goes wrong......
Cheers
- Occasus
Click to expand...
Click to collapse
thanks Occasus install this rom and comment ....
This rum is stock justArchi
True, files were deleted but I have it installed since yesterday and all day today with no problems ...
I also think it is very stable ..... thanks again, friend.

olititi said:
thanks Occasus install this rom and comment ....
This rum is stock justArchi
True, files were deleted but I have it installed since yesterday and all day today with no problems ...
I also think it is very stable ..... thanks again, friend.
Click to expand...
Click to collapse
Hehe,
don't worry about that & thanxx for your reply. As I said, I don't know what was wrong. My phone just didn't boot up again & showed me the bootanimation. Anyway, in the end all phones are different, even if from the same type & model, so the users & their experiences vary too

ok
Occasus said:
Hehe,
don't worry about that & thanxx for your reply. As I said, I don't know what was wrong. My phone just didn't boot up again & showed me the bootanimation. Anyway, in the end all phones are different, even if from the same type & model, so the users & their experiences vary too
Click to expand...
Click to collapse
yes it´s true...thanxx mate

occasus said:
okay, here some first impressions:
I've flashed this with the actual version of philz touch & there were no problems, the rom booted up normally (it is based on samsung's 4.3, just for the newbies). Played around with it a bit and thought by myself, okay, time for a reboot. I'm doing this always after a new rom has come to my phone.
And that is where the trouble begins; the phone got stuck in bootloop and started to get really warm. I don't know what has happend, another try, same result.
Not usable for me. Fortunately, i've decided to put another rom on my sd-card too, just for the case that something goes wrong......
Cheers
- occasus
Click to expand...
Click to collapse
hi i also suffered the same issue.
I did a clean install and after booting i saw the home screen just for about two minutes and then it went into boot loop.
As i'm sending this msg. I'm flashing stock rom through odin just so i can get my phone to work. Thanks anyway.

After installing the rom looks promising but 2 issues a rise:
1. some bits of the phone hasn't been translated properly into english.
2. after rebooting the phone it get stuck on samsung logo and there is response from capacitive buttons and is unable to boot the phone

Please,wipe cache-wipe dalvik, thanks

Occasus said:
Hehe,
don't worry about that & thanxx for your reply. As I said, I don't know what was wrong. My phone just didn't boot up again & showed me the bootanimation. Anyway, in the end all phones are different, even if from the same type & model, so the users & their experiences vary too
Click to expand...
Click to collapse
You should try Wipe cache, wipe Dalvik cache and then fix permissions...

[Q] Custom ROMs and Kernels and CM

Hi everybody!
Has there been any kernel and ROM development for the Z3 Compact, because I hope to buy it?
My second choice would be the S5 Mini but again I have not seen any development.
( Reasons for my choices are weight and size, being a girl I have seem to have been given smaller hands so giant sized phones have been dropped. )
Thanks lots and kind regards,
Soph.
P.S I'll post this on the s5 min forum also

Its kinda hard to develop for a phone which hasn't been released yet.

I can buy them here.
----
EDIT
no I cannot! I thought they'd released this. My apologies.
http://www.sonymobile.com/nl/products/phones/xperia-z3-compact/
This should be available in NL in 11 days, because when I try and place the order they say it won't ship for eleven day:
http://www.bol.com/nl/p/sony-xperia-z3-compact-groen/9200000032103951/?Referrer=ADVBETWE0020159200000032103951
and from here,
http://www.belsimpel.nl/Sony/Sony-Xperia-Z3-Compact-Green/abonnement

Fingers crossed that it will be supported by the CM team

forgetmyname said:
I can buy them here.
----
EDIT
no I cannot! I thought they'd released this. My apologies.
http://www.sonymobile.com/nl/products/phones/xperia-z3-compact/
This should be available in NL in 11 days, because when I try and place the order they say it won't ship for eleven day:
http://www.bol.com/nl/p/sony-xperia...3951/?Referrer=ADVBETWE0020159200000032103951
and from here,
http://www.belsimpel.nl/Sony/Sony-Xperia-Z3-Compact-Green/abonnement
Click to expand...
Click to collapse
If you don't live far away from the boarder, here in Germany it's available tomorrow.

forgetmyname said:
I can buy them here.
----
EDIT
no I cannot! I thought they'd released this. My apologies.
http://www.sonymobile.com/nl/products/phones/xperia-z3-compact/
This should be available in NL in 11 days, because when I try and place the order they say it won't ship for eleven day:
http://www.bol.com/nl/p/sony-xperia-z3-compact-groen/9200000032103951/?Referrer=ADVBETWE0020159200000032103951
and from here,
http://www.belsimpel.nl/Sony/Sony-Xperia-Z3-Compact-Green/abonnement
Click to expand...
Click to collapse
You need to be patient, developers need time, most people in north america who preordered from the UK retailers won't even get it until next week. I wouldn't expect boot loader unlocks or root until late next week at the absolute insanely earliest

Nuckin said:
You need to be patient, developers need time, most people in north america who preordered from the UK retailers won't even get it until next week. I wouldn't expect boot loader unlocks or root until late next week at the absolute insanely earliest
Click to expand...
Click to collapse
Actually you can already unlock the bootloader > http://developer.sonymobile.com/unlockbootloader/
I'm going to try it this evening. Afterwards maybe try Framaroot to see if the existing exploits to obtain Root access also work on this device.

I'm also personally waiting for CM; the xperia ROM feels really strange to use. Does anyone know roughly how long CM take to make a ROM for a new phone if they decide to support it?

Altitudes90 said:
Actually you can already unlock the bootloader > http://developer.sonymobile.com/unlockbootloader/
I'm going to try it this evening. Afterwards maybe try Framaroot to see if the existing exploits to obtain Root access also work on this device.
Click to expand...
Click to collapse
I have already unlocked and tried Framaroot, it does not work

kutaxov said:
I have already unlocked and tried Framaroot, it does not work
Click to expand...
Click to collapse
Have you tried Easy Root tool as well?
http://forum.xda-developers.com/showthread.php?t=2784900

Altitudes90 said:
Have you tried Easy Root tool as well?
http://forum.xda-developers.com/showthread.php?t=2784900
Click to expand...
Click to collapse
Does not work, hangs on the moment:
{
"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"
}

And your device is showing up when you use the "adb devices" command?

Altitudes90 said:
And your device is showing up when you use the "adb devices" command?
Click to expand...
Click to collapse
Yes

kutaxov said:
Yes
Click to expand...
Click to collapse
Too bad.

I dont think even the Z1C got an official CM release did it? And the one that was there broke all sensors when encryption was enabled
HosainH said:
I'm also personally waiting for CM; the xperia ROM feels really strange to use. Does anyone know roughly how long CM take to make a ROM for a new phone if they decide to support it?
Click to expand...
Click to collapse

SenK9 said:
I dont think even the Z1C got an official CM release did it? And the one that was there broke all sensors when encryption was enabled
Click to expand...
Click to collapse
A lot of it comes down to how many people (developers in particular) want or get the phone. I'm hoping that there will be a decent community behind the Z3C as many people don't want larger phones anymore and this still has decent specs and a great battery life. We'll have to wait and see, but CM isn't a necessity if you just want the options that CM exposes to the uses - there's plenty of ways to customise the device.
Personally, I'd be happy with root and a more vanilla android version without some of the Sony customisations.

SenK9 said:
I dont think even the Z1C got an official CM release did it? And the one that was there broke all sensors when encryption was enabled
Click to expand...
Click to collapse
Z1c has cm11 support officially.

Altitudes90 said:
Have you tried Easy Root tool as well?
http://forum.xda-developers.com/showthread.php?t=2784900
Click to expand...
Click to collapse
Even modified kernels with recovery from z1c and z2 not fit, and you somehow childish way want to get Root.

Joe_Mama said:
Even modified kernels with recovery from z1c and z2 not fit, and you somehow childish way want to get Root.
Click to expand...
Click to collapse
Jesus, don't get your panties all in a bunch.
Anyway, what makes you think that flashing a custom recovery is "easier" then getting root access?

Altitudes90 said:
Jesus, don't get your panties all in a bunch.
Anyway, what makes you think that flashing a custom recovery is "easier" then getting root access?
Click to expand...
Click to collapse
It is not easier. It is more reliable. And most importantly, even though I was doing something to get root, and do not sit in my panties like you in anticipation of a good magician.

Hardbricked Kindle Fire (5th Gen)

Hello,
I tried to downgrade from 5.6.x to 5.2.x. And its hardbricked.
I thought I could unbrick. But now, dont know what to do with that brick.
The Fire is connected to my pc, its doing something like open/close. Windows plug-in sound comes around each 22 seconds.
I see just black screen (its like off)
I've installed and tried KindleUnbrickV1.1, but it waits for nothing. (It says, waiting for adb device. But doesn't become visible on abd...)
Regards

mahmuttbey said:
Hello,
I tried to downgrade from 5.6.x to 5.2.x. And its hardbricked.
I thought I could unbrick. But now, dont know what to do with that brick.
The Fire is connected to my pc, its doing something like open/close. Windows plug-in sound comes around each 22 seconds.
I see just black screen (its like off)
I've installed and tried KindleUnbrickV1.1, but it waits for nothing. (It says, waiting for adb device. But doesn't become visible on abd...)
Regards
Click to expand...
Click to collapse
There is no unbrick utility for the 5th gen Fire.
Sent from my Gemini 4G using Tapatalk
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
Or any method for unbricking a 5th gen Fire
Sent from my Gemini 4G using Tapatalk

So, its garbage now?

mahmuttbey said:
So, its garbage now?
Click to expand...
Click to collapse
yep
Sent from my Gemini 4G using XDA Labs
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Plenty of warnings about this throughout the forun
Sent from my Gemini 4G using XDA Labs

oh my word. it's openning and closing as I understood from the plug-in sound. does not mean anthing?

mahmuttbey said:
oh my word. it's openning and closing as I understood from the plug-in sound. does not mean anthing?
Click to expand...
Click to collapse
The only recovery method
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Sent from my Gemini 4G using Tapatalk

sd_shadow said:
The only recovery method
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Sent from my Gemini 4G using Tapatalk
Click to expand...
Click to collapse
but the problem is that the Fire is not seen by "adb devices"
(as I get, the Fire restarts itself and it takes around 22 seconds. its like an infinite loop)

mahmuttbey said:
but the problem is that the Fire is not seen by "adb devices"
(as I get, the Fire restarts itself and it takes around 22 seconds. its like an infinite loop)
Click to expand...
Click to collapse
adb devices only works in adb sideload mode
Sent from my Gemini 4G using XDA Labs
---------- Post added at 07:20 PM ---------- Previous post was at 07:17 PM ----------
You tried to downgrade firmware, there is no reason to believe it can be recovered
Sent from my Gemini 4G using XDA Labs

thats what I'm talking about. this happens about every 22-23 second. I didn't get actualy whats this.
I'm looking for a way to open recovery mode.
thanks for your fast replies btw.
https://www.youtube.com/watch?v=TbyyN6rTsoU

If I solve dissappearing problem, I believe I'll do it.
I even tried to dissassembly battery for using just usb cable. It does same thing. @sd_shadow
edit: now it doesn't restart. but now, sp flashtools doesn't recognize my Fire
{
"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"
}

mahmuttbey said:
If I solve dissappearing problem, I believe I'll do it.
I even tried to dissassembly battery for using just usb cable. It does same thing. @sd_shadow
edit: now it doesn't restart. but now, sp flashtools doesn't recognize my Fire
Click to expand...
Click to collapse
Downgrading FireOS from 5.6 to anything below 5.4 borks the bootloader. There is no known method to resurrect the device. Save or sell it for parts.

in a near future, do you think that a new method will be found? @Davey126

mahmuttbey said:
in a near future, do you think that a new method will be found? @Davey126
Click to expand...
Click to collapse
Unlikely; bootloader downgrades are almost always fatal regardless of device.

I contacted to Amazon support. Hope that they'll help me

mahmuttbey said:
I contacted to Amazon support. Hope that they'll help me
Click to expand...
Click to collapse
If device is within warranty they will likely exchange it for a refurbished unit as a one time courtesy. There is no technical fix if unable to access recovery.

btw, I have another amazon Fire which works fine (my friend's). can I do something with two of them to recover my broken one? @sd_shadow @Davey126

mahmuttbey said:
btw, I have another amazon Fire which works fine (my friend's). can I do something with two of them to recover my broken one? @[email protected]
Click to expand...
Click to collapse
Dude - not sure how many different ways it needs to be explained. Device is dead. Learn from the experience and move on.

amazon fire 5th generation dead fix
Amazon fire 5th generation is making by downgrade i
Result this black screan and dead ...
Pc driver manager into mtk port ?
I need sp flashtool or Solution
Please ... my all best friend .... :crying:

Hi, i also had the same problem but sadly nothing to do. My device brick was caused by an ota update through the system (so officially) and i assume i was unlucky. Same symthomps like your. I searched all the web and i found up that's really nothing to do with that. Amazon tries in any way to descourage this pratique so the bootloader is locked for that motivation. In less words:
Nothing to do, i suggest to put that thing in garbage or sell it for parts.

PitAcc27 said:
Hi, i also had the same problem but sadly nothing to do. My device brick was caused by an ota update through the system (so officially) and i assume i was unlucky. Same symthomps like your. I searched all the web and i found up that's really nothing to do with that. Amazon tries in any way to descourage this pratique so the bootloader is locked for that motivation. In less words:
Nothing to do, i suggest to put that thing in garbage or sell it for parts.
Click to expand...
Click to collapse
same

Question Android 13 DP1 locked bootloader !!!

I installed A13 DP1 my OP10Pro(NE2215) software but it is not working with a locked bootloader.cannot get pass the password setup screen or connect any wifi also it keeps saying try another PW option.i cant fastboot any stock rom it says locked bootloaders cannot do this.I cant enable oem unlocking dot in developer settings because i cant pass setup screen.phone is stuck this stitution.any method for EDL tool or for unlock oem unlock ?

Well if you can't get past the screen you'll have to contact support and see if they can remotely flash your device with the stock software. If they can't/won't do this, you will have to send the device in for service. Without an unlocked bootloader, there's nothing you can do.
If they do it, try to snag the MSM files before they can delete them

EtherealRemnant said:
Well if you can't get past the screen you'll have to contact support and see if they can remotely flash your device with the stock software. If they can't/won't do this, you will have to send the device in for service. Without an unlocked bootloader, there's nothing you can do.
If they do it, try to snag the MSM files before they can delete them
Click to expand...
Click to collapse
Hahaha .thx for replying.i wrote and waiting.

Issue video
VID_20220615_015451_01.mp4
drive.google.com
{
"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"
}

If you hit the X in the top left, does it give you the option to skip setting a password?
EDIT: Nevermind, watched the video again and I see it just takes you back and makes you do it again.
I assume you tried factory reset from stock recovery too to make sure nothing got corrupted?
This is why I always unlock my bootloader before I tinker with anything.
Hopefully they agree to remotely flash it for you.

I did
EtherealRemnant said:
If you hit the X in the top left, does it give you the option to skip setting a password?
EDIT: Nevermind, watched the video again and I see it just takes you back and makes you do it again.
I assume you tried factory reset from stock recovery too to make sure nothing got corrupted?
This is why I always unlock my bootloader before I tinker with anything.
Hopefully they agree to remotely flash it for you.
Click to expand...
Click to collapse
You could sure I did factory reset in fastbootd screen but same result like a video .

metrixx02 said:
I did
You could sure I did factory reset in fastbootd screen but same result like a video .
Click to expand...
Click to collapse
That's unfortunate. I hope you can get them to fix it for you.

OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
I solve it and wrote solution.just fallow this .

Could be a chance to get the log in for MSM??
Just saying.

dladz said:
Could be a chance to get the log in for MSM??
Just saying.
Click to expand...
Click to collapse
He said on the OnePlus forum that they didn't even answer. It seems like it's probably true that they aren't going to do remote flashing anymore for devices outside of China.

EtherealRemnant said:
He said on the OnePlus forum that they didn't even answer. It seems like it's probably true that they aren't going to do remote flashing anymore for devices outside of China.
Click to expand...
Click to collapse
Ok so that's the last straw.
This is my final OnePlus device.
I really hope the tensor chip v2 does a job cos that the only avenue I'd consider at this point unless the nothing phone actually is decent.. Which I can't see.
OnePlus is screwed..
Why the hell did I sell my 8 pro.
What is the point of having a development forum for a device that isn't being developed for?
I'm done with the turd, it's a bullet taken nothing more.. I took one on the note 4 and the Evo 3D
Thought I was past all that.
Jesus.
If we were to get ROMs they'd have been out by now, it's not happening mate, period.
OnePlus is the new HTC. All that promise and no desire to stay faithful.
It is what it is, I won't buy another 1+ again.
Pixel only now

dladz said:
Ok so that's the last straw.
This is my final OnePlus device.
I really hope the tensor chip v2 does a job cos that the only avenue I'd consider at this point unless the nothing phone actually is decent.. Which I can't see.
OnePlus is screwed..
Why the hell did I sell my 8 pro.
Click to expand...
Click to collapse
Yeah it's incredibly disappointing that they're going so south with regards to being dev friendly, the same way Samsung did.
I tried extracting the OnePlus 10 Pro ColorOS MSM to see if it can be tweaked to flash units from other regions like regular MSM Tools can and the publicly-available decryption tools don't even work on it. I figured yeah, ColorOS sucks, but being able to unbrick and then use fastboot enhanced to get back to the right firmware would be a much better option but no, the MSM Tool they provide with it requires a technician to log in and the encryption method on the files is different from OnePlus OPS files OR Oppo OFP files.

EtherealRemnant said:
Yeah it's incredibly disappointing that they're going so south with regards to being dev friendly, the same way Samsung did.
I tried extracting the OnePlus 10 Pro ColorOS MSM to see if it can be tweaked to flash units from other regions like regular MSM Tools can and the publicly-available decryption tools don't even work on it. I figured yeah, ColorOS sucks, but being able to unbrick and then use fastboot enhanced to get back to the right firmware would be a much better option but no, the MSM Tool they provide with it requires a technician to log in and the encryption method on the files is different from OnePlus OPS files OR Oppo OFP files.
Click to expand...
Click to collapse
Ping it to me please if you have it.. I'll see if I can get it cracked.
Afaik people have had repairs with the MSM outside of China, or so I've heard anyway.
I may know someone who can remove the validation

dladz said:
Ping it to me please if you have it.. I'll see if I can get it cracked.
Afaik people have had repairs with the MSM outside of China, or so I've heard anyway.
I may know someone who can remove the validation
Click to expand...
Click to collapse
one plus support team offered me remote flash .but i solved already i hope u can contact them and solve ur problem

so i have to unlock bootloader to install A13 ?

I have some inquiries if it’s not too much trouble, guide me about this. These inquiries are displayed underneath here:
https://forum.xda-developers.com/t/...ntly-being-sold-prime-day-discussion.4465075/
Sitting tight for most appropriate response straightaway. I’m excessively confounded here.

For me it worked without unlocking bootloader. There was everything normal expect having no network signal.
Try to factory reset in bootloader