Database Info

ChevronLab Tokens

For over a week now I keep reading this on ChevronWP7 Labs:
The sale of tokens has been put on hold until more arrive, thanks for your patience.
Is it just me or is there a recurring problem with the Tokens?
It's alright if InteropUnlock gets fixed, thanks to some very hard work by Heathcliff and others....
But if I can't get ChevronUnlocked because they aren't giving out 'tokens' , well that's just annoying really isn't it?
Any one else having these issues?

Not good communicator
Not only that, but they don't reply to postings in their forum. If anyone posts a question, they might, on rare occasions, get an answer from another poster. I have to say that I am unlocked via token and appreciate that, but as far as being transparent and keeping people up to date, these developers are doing a very poor job. There are requirements to use this service that appear no where on the site other than pointing to the forums or twitter, they do a horrible job of setting expectations and, in general, are not setup to provide customer support.

Looked again today and still no tokens..
Did they close down and not tell me or something?

well better flash a DFT unlocked ROM than to trying to Unlock, its far better, u can install xap files using IE9 within WP7.

maybe they lack of manpower.

I'm also waiting for a week or more, checking several times every day.
So anoying that they are not selling tokens

December 12th?
They tweeted on their web site that more would be available December 12th.

A thought occured to me that MS might be clamping down on the release of these (they have to allow it with Chevron). The intent of these tokens was to allow people to play with app development and NOT allow a method for getting Interop-Unlock.
If MS is following any of the MULTIPLE web postings on how you can IU your phone but need to be Dev or Chevron unlocked first they probably don't care much for that (MS does not want people accessing native code and registry; that is apparent from the lock downs 2nd gen devices have plus the continued clamping down they have done with each new generation).
I wouldn't be surprised if
a) They stop issuing tokens
b) They revoke tokens (and give refunds)
There has been too much publicity on using the Chevron tokens to open up your phone to allow the various Interop-Unlock methods to be used.

LiFePo4 said:
A thought occured to me that MS might be clamping down on the release of these (they have to allow it with Chevron). The intent of these tokens was to allow people to play with app development and NOT allow a method for getting Interop-Unlock.
If MS is following any of the MULTIPLE web postings on how you can IU your phone but need to be Dev or Chevron unlocked first they probably don't care much for that (MS does not want people accessing native code and registry; that is apparent from the lock downs 2nd gen devices have plus the continued clamping down they have done with each new generation).
I wouldn't be surprised if
a) They stop issuing tokens
b) They revoke tokens (and give refunds)
There has been too much publicity on using the Chevron tokens to open up your phone to allow the various Interop-Unlock methods to be used.
Click to expand...
Click to collapse
I wouldn't be surprised if that's why 7740 update come out of no where all of a sudden.

I don't think that MS is putting the kaibash on token sales. You didn't see the tweets?
For all other issues, please email us at [email protected]. The PayPal dispute process is not for tech. support. ^RR
29 Nov
We're working on switching payment gateways prior to re-opening token sales. Possible ETA: December 12. ^RR
29 Nov
Good news, we're switching payment gateways soon. This means those having trouble with PayPal won't have trouble anymore. ^RR
21 Nov
Click to expand...
Click to collapse
They're like, a three man-team overwhelmed with a tsunami of unlockers who've been waiting for this, and lo-and-behold, there are: a) technical issues they didn't anticipate with different phone models/versions and worse b) clearly real problems with managing payments/purchases and customer service/payment support.
So they were probably naive about how much work it would be to deal with people who have trouble with their unlock. People doing things like: issuing a chargeback to Paypal (who not only reverses $9, by the way, but then hits then with another $10 'dispute fee' no matter the outcome... and eventually does massive fund freezes without explanation or recourse. Anyone who's used PayPal for any but smallest, least-refund-prone business has been there.) If they'd never undertaken something like this before, it wouldn't surprise me that they hadn't anticipated those types of problems beyond the technical.
Assume they're trying to get a merchant account opened.
{
"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"
}
whyJoe @ChevronWP7 I'm guessing what's going on is you guys have also discovered how much #PayPalSucks. / @ChrisWalshie @longzheng @paypal 7 minutes ago
in reply to ↑
@WithinRafael @whyJoe @ChevronWP7 @ChrisWalshie @longzheng Yep, and how slow banks are.
Click to expand...
Click to collapse

Chevron token is frozen, tried to contact them no reply, haven't seen any info on what to do, and links?

[ASK/OPINION] What to do about Xiaomi's decision on disabling UBL service?

Sorry if I posted this thread in the wrong place, but after searching here and there, the only place appropriate for my thread seems like in here. If I posted in the wrong place feel free to delete my thread or to move my thread to the right sub-forum. Sorry if this feels like I'm ranting or complaining, but this issue of mine just seems so cruel, evil, and unfair, especially done by such a big brand like Xiaomi.
So here's the deal, I bought a Xiaomi Redmi 5A (2GB RAM and 16GB's of storage) in mid of January. I bought the 5A because it had great specs even with it's low price and it's because my current daily driver can't handle the latest of what Android offers (I was using an ASUS Zenfone 5 with an Intel Chipset, very fast battery drainage, low compatibility with latest apps, and very poor signal reception plus dying support on XDA).
I bought my 5A online from a Official Store, but it was manufactured in my country (Indonesia) that was under a certain brand of smartphone warranties (TAM). I checked the device via Mi-Verify and the results showed up seeing my 5A is an official device supported by Xiaomi.
When the device was in my hands I proceeded to try to unlock it's bootloader, so I can gain root access and start restoring right away every Titanium Backup backup I had so I can use the 5A as my daily driver. I logged in to my Mi-Account and because my account had already been approved of Mi bootloader unlocking since 2016. I thought everything would turn out smooth, I expected that I had to wait for 72 hours or something (which I didn't mind about and was willing to patiently wait for). I proceeded to enable Developer Settings (in which is required to be able to bind my account to the device and unlock it using Mi-Unlock Status). I turned on USB debug & OEM unlock then I proceeded to get permission (bind Mi-Account) from Mi-Unlock status. This is were things went downhill.
First, it showed me an error code 10008 (in which could be fixed by using a Chinese based VPN server), then after using a VPN, it showed me another error code which is now my current nightmare: code 86023 hardwareId abnormal (<- originally Chinese fonts which I translated via google translate). I started searching for guides here and there to fix this issue with no luck at all. I tried every guide out there and even destroyed my warranty in process (I had to open the back case and use the test point methods) because I was followed a guide that said I had to flash via QFIL/Mi-Flash a China Developers ROM to be able to unlock my bootloader (which didn't change a thing, it still failed to unlock and still showed those 2 error codes: 10008 & 86023).
I even posted a thread in MIUI forums about error code 86023 in the complaints/advice sub-forum (in which now has the highest views and replies), and was surprised to see that I wasn't the only one with this UBL issue. It affected lots of Xiaomi devices that were manufactured or distributed in the near end of 2017 and early 2018 (especially Asia-Pacific devices). I faced a dead end and was hoping that it'll get fixed in a month.
After waiting for a month or more, it didn't get fixed at all. The only thing that was fixed was error code 10008 (Now it doesn't require a bypass via VPN) but the error code 86023 persisted. I got totally frustrated and tried contacting customer service via online chat and via email. First I tried online chat, and they suggested me to go to a local authorized service center to ask for bootloader unlocking. When I arrived to one of those shops, I was surprised that they said that they don't accept UBL pleas, they say that the user has to do it by their own consent (which pissed me off because I told them my situation and they still refused to help me). Then I emailed my country's customer service ([email protected]). I had 2 sessions of replies in which first they told me that UBL has been disabled by Xiaomi because they fear my device would be vulnerable to virus attacks (SERIOUSLY!?). I told them that I understand the risks of UBL and asked for a better and decent explanation on why UBL has been disabled. Then I received this reply:
{
"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"
}
"Kami mohon maaf atas kendala dan ketidaknyamanan yang Bapak Ezra alami. Terkait kendala yang terjadi, perihal kebijakan bahwa Unlock Bootloader sudah ditiadakan merupakan wewenang dari pihak Xiaomi Pusat yang berada di Cina."
This translates to:
"We are sorry for these issues and inconveniences that Mr. Ezra has experienced. Regarding to the problems that have occurred, the Unlock Bootloader policy has been removed and it is under the authority of Xiaomi's central headquarters that is in China."
After reading this, I was dumbfounded, totally dumbfounded. I nearly went ballistic. I was super pissed off and disappointed.
So from what I read, it seems like devices for my country, or maybe all of Asia Pacific has been totally locked out of UBL. So now I have no idea on how to unlock my Redmi 5A.
I did read UA of Xiaomi and found that they have total rights on removing a feature of some sort (read Xiaomi's User Agreement):
"The user accepts that in relation to business development, we may change, suspend, restrict, terminate or revoke the rights of our services at any time without notice;"
I understand this very much, but why did they have to terminate UBL? I thought Xiaomi supported developement and modding. But how did it come to this?
Please give me your opinions about this absurdness that Xiaomi has thrown to me and many other users out there.
Thanks.

[TUT] How to bypass FRP (verify your account) on LG V10 running Nougat

{
"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"
}
​
Factory Reset Protection (FRP) is a security method that was designed to make sure someone can't just wipe and factory reset your phone if you've lost it or it was stolen. Starting with Android Lollipop, FRP is "standard" in vanilla Android, and most companies making our phones have implemented it in their own models. It's a good thing — it makes a stolen phone harder to use, which makes it less appealing to thieves, and anything that can protect our data on a phone we've lost is welcome.
The problem is that people are selling or trading or even giving away phones with FRP enabled and this makes things difficult for the next user.
I found myself in this predicament recently having purchased a used LG V10 and, being in a rush, I flashed a factory KDZ on the device. Needless to say, I could do nothing with the phone once I rebooted - I was stuck on the proverbial "Verify your account" prompt.
If you reset a phone with FRP enabled, you have to provide the user name and password for the last Google account that was registered with the device. There are tons of random work-arounds on the Internet, but they tend to get patched almost as soon as they are discovered. You'll pretty much need to know the login details for the last account to use the phone before you can do anything with it if FRP was enabled before you reset it.
A quick XDA search turns up some 13000+ hits pertaining to "frp v10 verify account" and it takes time to try them all. The truth is that most were exploits geared for Android versions prior to Nougat and, even those which claimed to fix the problem for Android 7 no longer worked due to changes LG likely made between the 30B and 30C updates.
To make a long story short I finally found one method that worked. I got the device back and fully functional. Although I have only tried this on the 901H (T-Mobile variant) it may well work on any V10 running LG's version of Nougat (30C). If you try it and it fails or works you should let people know which variant and how you made out.
The solution for the V10 devices is documented in this video.
The ADB command line used is in the comments of the video but for ease of use this is it:
Code:
adb shell content insert --uri co-ntent://settings/secure --bind name:s:user_setup_complete --bind value:s:1
If you have another method that you have tried and know works on this specific device, by all means, do tell.
It is nice to have the device I legitimately bought working again!

Help
My LG V10 is missing the USB port. Is there an alternative way?

Lrrrrr said:
My LG V10 is missing the USB port. Is there an alternative way?
Click to expand...
Click to collapse
If your V10 is running the 30C version of Nougat I have not found another working method. With other versions of Android there may be more choices.
Sent from my LG-H901 using XDA Labs

Mine is actually running version 30B

NYLimited said:
Factory Reset Protection (FRP) is a security method that was designed to make sure someone can't just wipe and factory reset your phone if you've lost it or it was stolen. Starting with Android Lollipop, FRP is "standard" in vanilla Android, and most companies making our phones have implemented it in their own models. It's a good thing — it makes a stolen phone harder to use, which makes it less appealing to thieves, and anything that can protect our data on a phone we've lost is welcome.
The problem is that people are selling or trading or even giving away phones with FRP enabled and this makes things difficult for the next user.
I found myself in this predicament recently having purchased a used LG V10 and, being in a rush, I flashed a factory KDZ on the device. Needless to say, I could do nothing with the phone once I rebooted - I was stuck on the proverbial "Verify your account" prompt.
If you reset a phone with FRP enabled, you have to provide the user name and password for the last Google account that was registered with the device. There are tons of random work-arounds on the Internet, but they tend to get patched almost as soon as they are discovered. You'll pretty much need to know the login details for the last account to use the phone before you can do anything with it if FRP was enabled before you reset it.
A quick XDA search turns up some 13000+ hits pertaining to "frp v10 verify account" and it takes time to try them all. The truth is that most were exploits geared for Android versions prior to Nougat and, even those which claimed to fix the problem for Android 7 no longer worked due to changes LG likely made between the 30B and 30C updates.
To make a long story short I finally found one method that worked. I got the device back and fully functional. Although I have only tried this on the 901H (T-Mobile variant) it may well work on any V10 running LG's version of Nougat (30C). If you try it and it fails or works you should let people know which variant and how you made out.
The solution for the V10 devices is documented in this video.
The ADB command line used is in the comments of the video but for ease of use this is it:
If you have another method that you have tried and know works on this specific device, by all means, do tell.
It is nice to have the device I legitimately bought working again!
Click to expand...
Click to collapse
I grp bypassed my verizon lg g7 thinq through an exploit using wifi with a dead sim card. I basically found a way through youtube and google settings and i never once used any kind of downloaded app. Im on 9.0 pie. This was acheived about 15 minutes ago. It took 5 days to get it. But if you get at me tomorrow I will share what I did through step bu step instructions.

GkHammer said:
I grp bypassed my verizon lg g7 thinq through an exploit using wifi with a dead sim card. I basically found a way through youtube and google settings and i never once used any kind of downloaded app. Im on 9.0 pie. This was acheived about 15 minutes ago. It took 5 days to get it. But if you get at me tomorrow I will share what I did through step bu step instructions.
Click to expand...
Click to collapse
tooo bad you wil likely never see this - as im VERY curious as to whats up with a dead sim somehow allowing a frp bypass!!

Pixel 2 9.0 FRP bypass

I recently bought a pixel 2 XL for cheap on ebay, turns out it is FRP locked. I was looking for a bypass and they all seem to be patched. E.g. Talkback, maps, magnification. While digging I was able to get to the internet in a limited capacity. The google keyboard allows you to search for gifs and I was able open a tenor gif which had the a link to see more gifs which led me to a website. Ill link pictures. I was able to navigate from there to facebook and then to youtube and the rest of the internet by logging into facebook and messaging myself or posting links privately on my wall. What I could not do was launch other apps or download anything. Anyways this is what I've manage so far, hopefully someone can finish what I have started.
{
"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"
}

Pics link
https://imgur.com/a/hoLNPwN

code9523 said:
FRP is not a solution to protect stolen phone from use as it is bypassable. There should be an option in google account to full dissable phone to prevent it even turn on.
Click to expand...
Click to collapse
open an issue for this on google's issue tracker and lets see what response you get.

Moderator Information: Some posts are removed. Please remember our rules while posting. Thanks.

Any Luck
I am on the same boat. Talkback 7.0

i have successfully bypass frp on pixel 2 xl android 9.

adna said:
i have successfully bypass frp on pixel 2 xl android 9.
Click to expand...
Click to collapse
That's kinda not helpful at all. The way it works is you post your method and anyone who accidentally locked their own device can unlock it. Naturally, this is not useful for blacklisted IMEIs in the US.

so sad to see no updates on this thread, I've had this stupid pixel for months now while my gfs phone continues to detoriate, and I'm really hoping someone discovers a new method soon. I don't trust the guy who posted that and then disappeared when he was essentially asked to prove it lol

Search YouTube: Android 9 FRP bypass.

kelarys said:
so sad to see no updates on this thread, I've had this stupid pixel for months now while my gfs phone continues to detoriate, and I'm really hoping someone discovers a new method soon. I don't trust the guy who posted that and then disappeared when he was essentially asked to prove it lol
Click to expand...
Click to collapse
The problem with any discussion about bypassing Google's Factory Reset Protection - even if it were possible - is that it is impossible to determine if we're helping people legitimately access their phone or if we're helping them take over an ill-gotten phone. That's why conversations around this topic always stall out. We don't want to go around accusing people and we also don't want to even inadvertently be party to theft.

computerslayer said:
The problem with any discussion about bypassing Google's Factory Reset Protection - even if it were possible - is that it is impossible to determine if we're helping people legitimately access their phone or if we're helping them take over an ill-gotten phone. That's why conversations around this topic always stall out. We don't want to go around accusing people and we also don't want to even inadvertently be party to theft.
Click to expand...
Click to collapse
We have to give benefit of the doubt. But I agree with you entirely.
Sent from my [device_name] using XDA-Developers Legacy app

I’m not able to find a true working frp bypass. I don’t get a search icons to bypass like all the videos show for android P. And the helo&feedback button doesn’t take you anywhere. So I’m guessing Verizon blocked it in the last patch

The only way to fix this is to send it back to the seller. Ask for a refund.

No news?

try this new video youtu.be/WS1RFEiFMM8

hakkuba said:
try this new video youtu.be/WS1RFEiFMM8
Click to expand...
Click to collapse
Thanks a bunch! This worked.

computerslayer said:
The problem with any discussion about bypassing Google's Factory Reset Protection - even if it were possible - is that it is impossible to determine if we're helping people legitimately access their phone or if we're helping them take over an ill-gotten phone. That's why conversations around this topic always stall out. We don't want to go around accusing people and we also don't want to even inadvertently be party to theft.
Click to expand...
Click to collapse
I just discovered a new way.I dont know if itll work but.....
https://forum.xda-developers.com/pixel-c/help/pixel-c-8-1-1-frp-bypass-t3879498

Factory Reset Protection is Annoying, Get Rid of it!!!
I purchased a Google Pixel 2 Certified Refurbished on Amazon and I have this issue as well. If anyone has a solution I suggest they post it...party to theft or not, **** happens and I hate when device vendors install crap like this claiming it's to prevent theft....it's to boost sales, period. Fortunately I can get a refund or replacement but its a bleeping waist of time having to mail in my phone and wait for another phone be sent to me.
IMO this factory reset protection hurts more legitimate users than it protects. It create brick/useless devices that is a waist of resources just so companies can make more $ . . . If you lose your phone, track it down, get insurance and/or consider it a loss. If I irreversibly lost my phone I would not harbor some BS attachment to it...Ideally I would like it returned but alternatively I'd prefer someone else make use of it than create more waist.
Please search Change dot org for my petition for Google to remove FRP

I got a Pixel 2 XL with Android 10. How can i bypass the FRP ?

"Suro T0004502" Cool security phone with a serious bug.. and cant find any info at ALL HELP!!

Well I have an interesting one for yall today, someone gifted me this phone..
It's a 'high security' type phone with a hard switch on the side to toggle security modes.. I was intrigued..
After looking over it's almost pure black shell, I found a name / model..
SURO CARBON
T0004502
And thats it..
The problem with the phone is it's stuck on a proprietary activation screen... I sign into wi-fi ,
then as any android does, immediately searches for software updates.. Gathering that I cant
find any info.. I assume it's due to the company tanking and servers being taken offline,
thus it cannot complete the update process, gives me a generic "Encountered a problem"
screen with no error codes or anything.. then is pretty much locked until I reboot it...
oh it also DEMANDS I have a sim installed to even continue trying to activate
the regular Vol- / Vol+ /+/ PWR don't seem to do anything at all either..
{
"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 anyone has any ideas, or by some off chance has actually delt with this same problem
PLEASE let me know!!
Looks like an interesting product I would love to take a look at in working shape!
- Nick

Contact Suro: https://suro.dev/#contact

Hint: Add Suro T0004502 to this thread's title thus mainly owners of such a phone get addressed.

NURabbit said:
Well I have an interesting one for yall today, someone gifted me this phone..
It's a 'high security' type phone with a hard switch on the side to toggle security modes.. I was intrigued..
After looking over it's almost pure black shell, I found a name / model..
SURO CARBON
T0004502
And thats it..
The problem with the phone is it's stuck on a proprietary activation screen... I sign into wi-fi ,
then as any android does, immediately searches for software updates.. Gathering that I cant
find any info.. I assume it's due to the company tanking and servers being taken offline,
thus it cannot complete the update process, gives me a generic "Encountered a problem"
screen with no error codes or anything.. then is pretty much locked until I reboot it...
oh it also DEMANDS I have a sim installed to even continue trying to activate
the regular Vol- / Vol+ /+/ PWR don't seem to do anything at all either..
View attachment 5254753
If anyone has any ideas, or by some off chance has actually delt with this same problem
PLEASE let me know!!
Looks like an interesting product I would love to take a look at in working shape!
- Nick
Click to expand...
Click to collapse
i have the same problem with mine, and its not T0 butt TO004502 mine is TO026281 i think its the phone's ID number.
its an encrypted phone who uses the ENCRO network servers wich were taken down i bought it new € 1300,- after a week it was out off the air like yours, i would like to install android on it but dont know how.
did you get a respond from www.suro.dev ? i email them to but no respond
greetings Danny

NURabbit said:
Well I have an interesting one for yall today, someone gifted me this phone..
It's a 'high security' type phone with a hard switch on the side to toggle security modes.. I was intrigued..
After looking over it's almost pure black shell, I found a name / model..
SURO CARBON
T0004502
And thats it..
The problem with the phone is it's stuck on a proprietary activation screen... I sign into wi-fi ,
then as any android does, immediately searches for software updates.. Gathering that I cant
find any info.. I assume it's due to the company tanking and servers being taken offline,
thus it cannot complete the update process, gives me a generic "Encountered a problem"
screen with no error codes or anything.. then is pretty much locked until I reboot it...
oh it also DEMANDS I have a sim installed to even continue trying to activate
the regular Vol- / Vol+ /+/ PWR don't seem to do anything at all either..
View attachment 5254753
If anyone has any ideas, or by some off chance has actually delt with this same problem
PLEASE let me know!!
Looks like an interesting product I would love to take a look at in working shape!
- Nick
Click to expand...
Click to collapse
mine is TO012200, with same probleme ..............

HI someone who know what do i have a same problem or get some answer from suro ? thanks

I have the same problem, anyone managed to get it somehow fixed or flashed with normal firmware?

I have the same problem, anyone managed to get it somehow fixed or flashed