A Guide to Bringing The “Bricked” P10 Plus Back to Life With All Its Details - Huawei P10 Plus Guides, News, & Discussion

{
"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 all started with preparing the P10 Plus to install HarmonyOS. But by an error we have corrupted the device irreversibly. Similarly, if you have broken your P10 Plus while downgrading or updating software, we have good news for you, you can bring your P10 Plus back to life at no cost. Tested and approved!
Let's get started quickly.
First of all, you need to connect your device to your computer to detect the problem. If your device shows as USB_SER in device manager, the steps are even simpler for you. Because USB_SER mode is a mode that you can think of as an emergency recovery mode, created for the purpose of installing recovery software on your device. If your phone switches to this mode as soon as you plug the cable into this mode, it will be enough to follow a few steps. But if you don't get any response when you connect your phone to the computer, we're sorry, you need to turn on your device.
Before proceeding with all these steps, we would like you to know that you are responsible for any problems that may happen to you on the way to unlocking your device, that the Huawei Family is only the guide provider and will not take any responsibility. All these steps will cause your device to be considered within the scope of "unauthorized intervention" if it has a warranty, and we want you to know that you cannot claim any rights in any problem that may occur.
We will continue to explain the hard way, because many devices cannot enter emergency recovery mode on their own.
The list of needs for those who will perform the transaction the hard way is as follows:
- A conductive cable (paper clip, etc.) that will allow you to put your device in emergency recovery mode.
- Thin Phillips screwdriver
- Screen removal vacuum and pick to quickly remove the screen
- Archive with all the files that will bring your device back to life
We will continue to explain the steps, assuming you have removed the screen, you can learn this type of removal from the internet professionally.
When you remove your device until the motherboard is visible, disconnect the battery for your safety, then remove the intermediary cable that connects the lower board to the motherboard, you will see the emergency rescue (testpoint point). Connecting this point takes some patience and experience because you also have to reattach the lower board cable to the motherboard. We used T-7000, which is a screen adhesive, to provide this process. After gluing one end of the conductive cable to the point indicated in the photo with a T-7000 style easy-release adhesive as a tiny dot, attach the connecting cable to the motherboard. Connect your phone to your computer while touching the other end of the conductive cable to one of the metal plates on the motherboard. Then if you did everything right, your phone will appear as USB_SER on your computer. This is a sign that you are approaching the recovery stage.
When it shows as USB_SER, there is a small step you need to take, you need to disable the driver signature verification, otherwise the driver for the emergency mode will not be installed. There are variable steps you need to take to accomplish this, depending on the version of Windows you have.
Windows 7: Type cmd in search and right click to run as administrator, then execute bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS and bcdedit.exe -set TESTSIGNING ON commands. Then restart your computer.
Windows 8/8.1/10: Settings > Update & security > Recovery > Advanced reboot > Troubleshoot > Advanced > Change startup settings > Press 7 on the keyboard. Driver signature verification will be disabled.
11: Settings > Recovery > Advanced reboot > Troubleshoot > Advanced > Change startup settings > Press 7 on the keyboard. Driver signature verification will be disabled.
You can now continue with all these steps by installing the driver for your device. Find the device manager, select the device named USB_SER, right-click it, then click the update driver software button. Then click the browse drivers button on my computer, select the "usb_serx64" folder in the archive we shared with you, and click next. When prompted to install driver, click Install this driver software anyway button. The operation is successful and USB_SER will now appear as Huawei USB COM PORT.
Again, run the program called PotatoNV, which is in the archive. Select "Kirin 960" in the Bootloader section of the program. Then “Start!” Press the button. Disconnect your phone from the computer when the download line at the bottom is full. Then close the PotatoNV program, your device will be in fastboot mode:
We can interpret this mode as vegetative life, if you restart your device without taking any action, the device will enter the emergency recovery mode again. Since our goal is to recover the device, let's continue!
Reconnect your phone to the computer and run the command line named ”flash_1” in the unbrickfw folder in the archive. Recovery images will begin to install on your device. This whole process can take about 15 minutes. When the installation process is completed, your device will automatically reboot and you will get rid of all this torture. As soon as you see the Huawei logo, all the processes are complete.
That's it!
Main source

Related

Virus on my moms laptop.

Alright. She has some weird program on there called "System Tools 2011" and I don't know how it got there. Right when you boot up, a minute into it, it pops up the app and a wallpapers and blocks you from A LOT of things. You can't back up files to a USB, can't access Control Panel, etc... when I did get into the Control Panel, it won't allow me to uninstall the app because it doesn't show up and there is no way to uninstall it. Is there anything I can do to get rid of it? Any ideas? Let me know please. Thanks.
Original Android <3ers! said:
Alright. She has some weird program on there called "System Tools 2011" and I don't know how it got there. Right when you boot up, a minute into it, it pops up the app and a wallpapers and blocks you from A LOT of things. You can't back up files to a USB, can't access Control Panel, etc... when I did get into the Control Panel, it won't allow me to uninstall the app because it doesn't show up and there is no way to uninstall it. Is there anything I can do to get rid of it? Any ideas? Let me know please. Thanks.
Click to expand...
Click to collapse
Download RKill and run it!!! search Google about RKill. And stop turning it off and on...that will damage your computer to the point of no return
I've removed that virus from two computers already but read above!!!
Nice to see you around little one
Or you can google the name and find the registry keys for said virus and remove them. DOne that at work manny times and saves the time of backup and format
I have had to literally roll back my computer to an earlier date to get rid of the annoying pop ups and remove viruses like that. And yes, I got them from torrents.
As an IT Tech for many years those Viruses are a pain to deal with. I use a paid AV Boot CD called Avast BART or you can try using TRK (Trinity Rescue Kit) Bootable CD AV's work best as they are seperate from the OS. Try TRK just google it and burn it to a disk. Best of luck!
Malwarebytes/Spybot/NOD32 cocktail also does a pretty decent job at getting rid of that crap. Just remember to turn off System Restore or your viruses will be back upon booting your computer.
MalwareBytes anti-malware is great but some viruses are so good that they will block any known anti-virus program from executing.
What are the Symptoms of System Tool 2011 Infection?
It will modify Windows Registry and add the following entries:
HKEY_CURRENT_USER\Software\System Tool 2011
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run “5648541024″
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run “[random]”
The threat will drop the following malicious files:
%AppData%\[random]\
%AppData%\5648541024
%AppData%\5648541024\5648541024.bat
%AppData%\5648541024\5648541024.cfg
%AppData%\5648541024\5648541024.exe
%UserProfile%\Desktop\System Tool 2011.lnk
%UserProfile%\Start Menu\Programs\System Tool 2011.lnk
How to Remove System Tool 2011 Manually
1. Restart your computer in SafeMode
- Press F8 on keyboard as soon as you turn on the computer
- Select SafeMode to start the computer loading only minimal resources
2. Delete Windows registry entries the malware created. It is important to BACKUP YOUR REGISTRY FIRST.
- On Windows Start Menu, Click Start > Run
- Type in the field, regedit
- Find registry entries mentioned above and delete if necessary
3. Files related to System Tool 2011 must be deleted:
- Browse and delete malicious files detected above.
- Some files cannot be deleted instantly. Press Ctrl+Alt+Del to open Windows Task Manager, look for any virus-related files mentioned on this page and highlight it, click End Process. Try to delete the file once more.
4. Run Antivirus Program
- You must be connected to Internet to be able to update your anti-virus program. This is needed to have the latest database available and detect newer threats.
- Thoroughly scan the computer and clean or delete all detected threats.
+1 for rkill > malwarebyte
if rkill doesn't work at the first time, keep running it until is says successful
Dude don't watch porn on your moms laptop! Number 1 rule
#1 way to get rid of viruses on your computer...
{
"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"
}
Backup personal data, format the HDD, reinstall the OS, no viruses.

Unable to backup my IMEI/NV data

Hi, I just got this I-9305 a week ago and I finally wanted to mess around with it a bit, it's been rooted since day one with no problems but after reading around the stickies a bit it seems like backing up my "IMEI/NV" data, whatever that is, is pretty important before flashing anything on my phone. ( http://forum.xda-developers.com/showthread.php?t=1946915 )
I followed all the steps in that thread to a T but when I get to the part where you add a new port it doesn't seem to see my device or display the correct ports
this is what I see
{
"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 after adding that "com1 - serial" port it says "no phone".
Does anyone know a fix for this? I'm willing to provide whatever more info about the phone that would be needed.
Thanks in advance.
naxol said:
Hi, I just got this I-9305 a week ago and I finally wanted to mess around with it a bit, it's been rooted since day one with no problems but after reading around the stickies a bit it seems like backing up my "IMEI/NV" data, whatever that is, is pretty important before flashing anything on my phone. ( http://forum.xda-developers.com/showthread.php?t=1946915 )
I followed all the steps in that thread to a T but when I get to the part where you add a new port it doesn't seem to see my device or display the correct ports
this is what I see
and after adding that "com1 - serial" port it says "no phone".
Does anyone know a fix for this? I'm willing to provide whatever more info about the phone that would be needed.
Thanks in advance.
Click to expand...
Click to collapse
•Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom. Now select 'RNDIS + DM + MODEM' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now in DIAG Mode.
•Download and Install: SAMSUNG_USB_Driver_for_Mobile_Phones_1590.exe - 23.06 MB if you don't already have Kies or a USB Driver installed.
•Download and Install: QPST v2.7.378.zip - 14.68 MB
•Now connect your phone to the PC with a USB cable and wait for Drivers to install.
•Start the 'QPST Configuration' application and select the 'Ports' tab then press the 'Add New Port...' button.
•Select the COM Port that has 'USB/QC Diagnostic' next to it, change the Port Label if you like to 'Samsung GT-I9305' then press 'OK'.
•You should now see your phone listed in the 'Ports' tab and the 'State' should indicate 'Enabled'.
•You can now Close this application.
Raistlin1158 said:
•Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom. Now select 'RNDIS + DM + MODEM' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now in DIAG Mode.
•Download and Install: SAMSUNG_USB_Driver_for_Mobile_Phones_1590.exe - 23.06 MB if you don't already have Kies or a USB Driver installed.
•Download and Install: QPST v2.7.378.zip - 14.68 MB
•Now connect your phone to the PC with a USB cable and wait for Drivers to install.
•Start the 'QPST Configuration' application and select the 'Ports' tab then press the 'Add New Port...' button.
•Select the COM Port that has 'USB/QC Diagnostic' next to it, change the Port Label if you like to 'Samsung GT-I9305' then press 'OK'.
•You should now see your phone listed in the 'Ports' tab and the 'State' should indicate 'Enabled'.
•You can now Close this application.
Click to expand...
Click to collapse
Yeah I've done all that I assure you, I don't see any COM ports that have 'USB/QC Diagnostic' next to them. :/
Just a quick thought, you do have usb debugging enabled.
Raistlin1158 said:
Just a quick thought, you do have usb debugging enabled.
Click to expand...
Click to collapse
Yeah I used it to install some apks.
So your PC can see your phone okay, then try another version of Odin.
Maybe remove your drivers, reboot the PC and then reinstall them
I had this also just unpluged usb from phone and put it back in and it showed up.
So either it's dodgy drivers in which case reinstall or get a better usb lead...

[How-To] Install Windows 8 Drivers to Establish ADB with NookColor

Hello mods, surely haven't done one of these before but there seems to be a big hole in our knowledgebase here and I thought I'd take a stab at filling it. If I somehow overlooked another solution for this, feel free to take this down and also smack me because I turned the web upside down trying to find the answer before putting it together.
All that being said....I've now done this on two Windows 8 machines so I feel confident that it works. All of the following was done on a fresh install of the Android SDK by installing Android Studio with all default options. Get Android Studio here. You'll need to install Java first if you haven't already, you can grab Java SE Development Kit 7u75 here.
1) The first step is to disable driver signature enforcement on Windows 8, which is the cause of all this devilry that makes it seemingly impossible to install the drivers and get ADB working with the NookColor. Follow the instructions on this link: Disabling Signed Driver Enforcement on Windows 8
2) Download and extract the attached adb_usb.zip file. Take the adb_usb.ini file inside and drop it in your.android directory. If my Windows username is cabbieBot, then I find it here: C:\Users\cabbieBot\.android
{
"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"
}
Alternatively, you can just make this file yourself by opening up notepad, typing 0x2080 into it, clicking save, change dropdown from .txt to All Files, and save it as adb_usb.ini
3) Open Device Manager and plug in your NC. You will see NookColor under "Other Devices" with a yellow exclamation mark.
4) Download/extract the attached NookColorADBInstall.zip file.
5) Open Device Manager in Windows 8 You will see "NookColor" under "Other Devices" with the exclamation mark. Right-click on it and click "Update Driver". From here on out its all about just going through the right process of menus and dialogs.
6) Click whats in the red box: "Let me pick from a list of device drivers on my computer".
7) Just leave it on "Show All Devices" and click Next.
8) IMPORTANT STEP! Click "Have Disk"
9) Click "Browse"
10) Navigate to where you extracted the NookColorADBInstall zip and you'll select the "usbdrivers" folder inside.
11) Without restarting Windows with the driver signature check we'd hit a dead-end here but we good. Click "Next".
12) Tell the dialog to eff off and click "Yes"
13) Click "Install this driver software anyway".
14) DING DING DING! If you have your NC hooked in, you should now see it prompting you to accept the computer's RSA certificate which means your computer and nook are gloriously flirting, so lets check it out to be sure.
15) Navigate to where ADB lives, which on a default installation will be at C:\Users\cabbieBot\AppData\Local\Android\sdk\platform-tools. Hold SHIFT and RIGHT-CLICK in the folder to select "Open Command Window Here"
type:
adb kill-server
then....
adb start-server
then...
adb devices
When you see your device's serial number pop up, you are certifiably done. I decided I wanted to learn to build CM from source and the trusty old NookColor is a handy device to play on. If you are worried about the driver signature check being disabled, just reboot your computer because it doesn't survive a reboot. Hope this is useful to someone else even though dear old Encore is downright ancient at this point.

How to UNBRICK HTC desire 626 (When all else fails!!!)

This is made for the AT&T HTC desire 626, But It should work with other similar 'desire' phones,
just download the image for the model you own.
(Note: the buttons for 'download mode' and 'force reboot' should be similar for most models, look it up if needed)
So after spending around 8 hours trying to unbrick this phone, I finally found a working method!
This is a combo of about 6 guides, and some of my own work. so I'll credit who I can remember.
This guide is not meant to be noob friendly, it expects you to have at least some knowledge of android, and flashing.
Anyway, You'll need a few things.
1. Good Quality Micro USB cord
2. HTC sync manager (official link)
3. Stock Rom
(official links) find your model, and carrier.
-----
How to unbrick!
(NOTE, this will DELETE ALL DATA, including the built in storage for music/videos)
Step 1: Enter Download mode
unplug your phone, power off, and boot into Download mode, Hold: [Power]+[Volume Down]
{
"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"
}
Step 2: run the installer for HTC sync manager. (this will install the drivers we need)
Step 3: uninstall HTC sync manager. (only sync manager, we need to keep the drivers)
Step 4: Pause your anti-virus program, or allow the stock image flashing program.
Yes, I know how shady that sounds, double check the link, it's an official HTC program.
And yes, flashing firmware over USB is NOT something most programs often need to too. it makes sense it's treated as a virus.
If you're really worried, use a spare PC. [works on windows only]
Step 5: Connect to your phone via USB.
Make sure any other android devices are disconnected.
And if possible connect directly to the main USB ports, avoid using an (external) USB hub
Step 6: Start Flashing!
Run the Flashing program, the name starts with:
Code:
RUU_
It may take some time to startup, and you'll need to give it admin rights.
To proceed, you'll just need to keep clicking 'Next',
You'll have to agree to some terms, and eventually you'll see the "upgrade" button, click that to start the process.
It will now start flashing your phone, Your phone may reboot a few times,
and the progress bar will fill up to 100% more than once.
(it flashes each part individually, 'Boot image'. 'system', etc)
The whole process should not take very long, it should be done in well under an hour.
The main program will tell you when it's complete.
The phone will automatically reboot, and the phone will be returned to stock!
Notes:
-This will remove root, or any custom, recovery
-If you plan to sell the phone, please note, this dose not unregister the phone from your google account.
IF you want to sell the phone, re-setup the phone as normal. Then, sign in to your google account, and manually remove it
-This dose NOT re-lock your bootloader.
To re-lock, go back to download mode, and run:
Code:
fastboot oem lock
-I am writing this after only 4 hours of sleep, so expect some grammar errors.
And I don't remember all of the buttons prompts from the flashing prompt. but it's very straight forward.
----
Here are some issues I had when following other guides online, this may help some with similar issues.
---
1. phone stuck at HTC logo screen, can't force power down!
Answer: Hold [power] +[volume up] for 10 seconds, that will reboot the phone
2. I Can't get the software to run. (closes after a few seconds)
Answer: If you're running bit defender, it will block the program, unblock it, then turn off bit defender.
3. I can't get the program to run at all!
Answer: Try re-downloading. if you're on the AT&t 626, then the hash should be: MD5: f4d2bdab11290c367136067a96d3dfaf
4. Program fails to flash (stuck at 0%)
Answer: HTC sync manager seems to interfere with the flashing, uninstall ONLY sync manager!
5. Can't enter download mode
Answer: With your Phone OFF, Hold [Power] + [Volume down] it will take you to a weird screen. that is download mode
6. flashing stuck for more than 10 mins! (progress bar never moves.)
Answer: restart using the same method above for stuck at HTC logo screen, then boot to download mode.
-----
Sources:
https://www.reddit.com/r/htcone/comments/3o1l0r/htc_desire_626s_stock_rom/
http://www.htc.com/us/support/htc-desire-626-att/howto/658492.html
http://www.modifyandroid.com/stock-roms/htc/how-to-flash-stock-rom-for-htc-desire-626-att/
http://forum.xda-developers.com/desire-626/development/ruu-att-626-t3272165
Thank you. By simply uninstalling HTC sync manager on your PC allowed me to update and flash ruu thru adb. No more errors! ?

Mi 9T Pro - Hardbricked & Needing Help

Hello XDA Community,
As a preface, I'm an idiot. I figured I could dabble around with different ROM's and through all of my insightful wisdom appear to have hard-bricked my phone in the process. As seen via the attached photos I at one point was able to boot my phone into Fastboot > TWRP > Flash Rom > Off to the races.
Now the phone will not boot period. When plugged into an outlet the blue indicator atop the camera doesn't even blink a blue color. Moreover, when plugged into my PC it is not found via my PC "Devices & Drives" folder. However, when I open the MiFlash tool the phone reflects as "COM3" whereas before it would show what I assume to be the unique ID for the phone.
I came across another thread titled "[EDL Flash] How to fix your hard brick [Mi 9T Pro/K20 Pro]" but even here it mentions the phone booting and displaying some type of error message.
Anyhow, this is a long shot but figured I'd give it a go and see what comes of it.
Thanks for any insight and for simply taking the time to read my post.
Image of MiFlash reflect COM3:
{
"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"
}
Update 1 - I've tried to flash a ROM and get error message: "Object reference not set to an instance of an object". Here:
RealSykes said:
Hello XDA Community,
As a preface, I'm an idiot. I figured I could dabble around with different ROM's and through all of my insightful wisdom appear to have hard-bricked my phone in the process. As seen via the attached photos I at one point was able to boot my phone into Fastboot > TWRP > Flash Rom > Off to the races.
Now the phone will not boot period. When plugged into an outlet the blue indicator atop the camera doesn't even blink a blue color. Moreover, when plugged into my PC it is not found via my PC "Devices & Drives" folder. However, when I open the MiFlash tool the phone reflects as "COM3" whereas before it would show what I assume to be the unique ID for the phone.
I came across another thread titled "[EDL Flash] How to fix your hard brick [Mi 9T Pro/K20 Pro]" but even here it mentions the phone booting and displaying some type of error message.
Anyhow, this is a long shot but figured I'd give it a go and see what comes of it.
Thanks for any insight and for simply taking the time to read my post.
Image of MiFlash reflect COM3:
Update 1 - I've tried to flash a ROM and get error message: "Object reference not set to an instance of an object". Here:
Click to expand...
Click to collapse
That error message is some sort of program error:
https://stackify.com/nullreferenceexception-object-reference-not-set/
I'm no expert on c# programming so cannot say why that error occurred.
You could try to use adb commands, see if adb picks the device up, when you say it does not power on at all, does the phone go into bootloader mode? (, power and volume down)
MOD EDIT: QUOTE REMOVED
try it under windows 7 computer, preferably laptop with usb 2.0 port. It can recognize the device, if not, and standart unbrick method doesnt work even under w7, then you have to use test points on motherboard, edl account is needed for that, idk how to get it as i tried to get it several times but received only mails in chinese so i gave up, not paid too much to bother so much time on fixing one phone.
There is even modified version of flash tool that is believed to authorize any account logged in bypassin the authorize account error i can provide a link for you but not tested if its actually working.
MOD EDIT: QUOTE REMOVED
i actually did research about this while ago and it might help the guy unless he is willing to pay some russian scammer 60 bucks via teamspeak that is doing this stuff from either stolen or modified authorized account which i can provide link to @RealSykes pm me if u wanna try and give it a go, u can pay russian scammers few bucks in the end if all tries fails there is even command for adb if you have unlocked bootloader that will enter edl without test pin points, but u need to enter fastboot mode first which im assuming u cant from what i have understand.
Kind of important question, what did you do to screw up your phone? So others know what not to do.
https://c.mi.com/thread-2173190-1-0.html follow steps on this site if you already didnt find this by yourself, maybe it can give you and permission to flash, as it appears for some people it actually gave it. tried it myself for you now, and it appears my account is somehow ready to flash (authorized) now, but, i applied some time ago for actually get it, so, it can be different for you.
RealSykes said:
"Object reference not set to an instance of an object"
Click to expand...
Click to collapse
An Object is an instance of a Class , it is stored some where in memory. A reference is what is used to describe the pointer to the memory location where the Object resides. The message "object reference not set to an instance of an object" means that you are referring to an object the does not exist or was deleted or cleaned up. It's usually better to avoid a NullReferenceException than to handle it after it occurs. To prevent the error, objects that could be null should be tested for null before being used.
if (mClass != null)
{
// Go ahead and use mClass
mClass.property = ...
}
else
{
// Attempting to use mClass here will result in NullReferenceException
}
hardbrick and button not press
Need Guideline stepbystep pls.....

Categories

Resources