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.....
Related
I wrote this basic little application to help out those who are either afraid of the command prompt or simply just don't want to deal with it. Drop it in the same folder as adb and run it.
Feel free to leave feedback or contact me with any questions/comments.
http://incredible.groove2.net/IncredibleRooter.zip
If people decide they like this, I will continue development and add some new features to it.
Check out the Readme.txt for more information and detailed explanations.
Thank you, I had rooted mine before using the command prompt, your application save me time on taking off the battery and waiting for reboot. Thanks again.
vVv mDaWg said:
I wrote this basic little application to help out those who are either afraid of the command prompt or simply just don't want to deal with it. Drop it in the same folder as adb and run it.
Feel free to leave feedback or contact me with any questions/comments.
http://incredible.groove2.net/IncredibleRooter.zip
If people decide they like this, I will continue development and add some new features to it.
Check out the Readme.txt for more information and detailed explanations.
Click to expand...
Click to collapse
Thanks for your work, it doesn't go unappreciated =).
Glad to see people are finding it useful. Expect a CityID removal button in the near future.
where exactly do we drop this? what's the path?
As the OP stated, place this program in the same folder as adb, so depending on where your sdk is located it might go in C:\sdk\tools\
what's the adb?
Please bare with me...
Robes1 said:
what's the adb?
Please bare with me...
Click to expand...
Click to collapse
Found it...thanks anyway.
Appreciate it, wish I would have seen before I rooted. I will try this as I need to get back there to remove cityid anyways.
-------------------------------------
Sent via the XDA Tapatalk App
lol.. you know whats sad... is i almost guarantee besides trying 2.2 on this beast.. CityID is #1 on peoples list of crap to remove that is absolutely useless
Nice App.
Thanks!
What does the app do? Will it help get people into the adb shell? That seems to be the real problem.
When will option be avail to remove cityid? that is big reason for me to root.
also please explain more on where to find adb folder?
thanks for this app cant wait to try it.
metalmenance said:
When will option be avail to remove cityid? that is big reason for me to root.
also please explain more on where to find adb folder?
thanks for this app cant wait to try it.
Click to expand...
Click to collapse
Extract it or place it inside the tools folder.
{
"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"
}
hmmmm
well I'm stuck. tried several cards tried all the methods and still no go. It goes to the screen with the red triangle and dead ends. and after that it just says cant open cache recovery command guess im screwed oh well thanx for posting all the steps you guys went through effen pisses me off though
Has anyone used this and has it worked. I've tried every method on every site and nothing, I'm going to try this when I get home from work.
Hey guys, sorry if there's been any confusion.
This app will not make ADB start up in recovery. That's still something that we still have to achieve to get any of this to work.
Peronally I used the Kingston 4GB Class 4 card and it works pretty much almost every single time I just do a simple adb reboot.
This application was designed to make the rooting process a quick and painless command prompt-less process after you achieve adb running in recovery mode. I used this on my friend's Incredible and the rooting process took me literally 30 seconds to complete.
vVv mDaWg said:
Hey guys, sorry if there's been any confusion.
This app will not make ADB start up in recovery. That's still something that we still have to achieve to get any of this to work.
Peronally I used the Kingston 4GB Class 4 card and it works pretty much almost every single time I just do a simple adb reboot.
This application was designed to make the rooting process a quick and painless command prompt-less process after you achieve adb running in recovery mode. I used this on my friend's Incredible and the rooting process took me literally 30 seconds to complete.
Click to expand...
Click to collapse
Does the red triangle with the exclaimation point mean it has failed, or do you wait further?
Thanks,
Jim
I used a SanDisk 2GB works everytime.
After your in recovery mode and have clicked the Step 3: button "Check for ADB In Recovery".
If you get the "sorry adb not running" message try this:
Unplug your usb cord from the device and remove your battery.
Replace your battery and hold down the volume- key and press the power button.
Highlight Recovery as soon as possible.
Plug the usb cord back in and press the power button at the same time.
Note: If you hear a noise when you plugged in the usb cord before you see the black Recovery screen you did it wrong.
Click the Step 3: button one to five times.
If it doesn't work try it again or try a different SD card.
Touch thanks for all the help Bro. My incredible is just a stubborn ***** LOL Great job on the windows app
I'm having problems with my Galaxy S GT-I9000. First, the history, in case that offers any clues. [I should say, "The history as far as I know it." The phone was given to me from someone's proverbial 'sock drawer'; it could have been there for a reason...]
It was running crap with stock firmware (couldn't delete files or pictures [well, they would delete, but they'd always come back], had a hard time writing files [they would write (sometimes) but then disappear (though not immediately)], tons of 'Force close' messages for apps, couldn't change G-Mail account, etc., etc., etc.). I used Kies to update the firmware to 2.3.6. When this was completed I seem to remember some message about not being able to go back to the firmware I updated from. Unfortunately, I didn't write that message down. I figured the new Samsung firmware would fix things.
However, the problems persisted with the new Samsung / Kies-provided firmware. At that point I decided to try third party firmware, specifically Cyanogen 7.2.0. I followed the instructions at the wiki[dot]cyanogenmod[dot]org/w/Install_CM_for_galaxysmtd site (sorry, apparently I'm not able to post external links as a new user). Heimdall put Semaphore's CWM on just fine, and I can still boot into it no problem. I then tried to flash the ROM from the internal SD card (though it took a few tries to copy it there successfully [see write problems referred to above]). It didn't work... It got to Andy on the blue skateboard, but then just looped. And looped and looped and looped... I then tried install the ROM from an external SD card. This seemed to get farther (Andy hung around longer on the first boot after flashing than previously), but it still ended up looping.
I tried the Troubleshooting instructions in the cyanogenmod site referred to above (basically, a different Recovery version). The new Recovery installed fine, but Cyanogen did not... Same boot loop.
I'd like to try to use ADB to push the ROM back to the internal SD card, but now my computer doesn't install the drivers for Galaxy S when I plug it into USB. I have tried to re-install "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" (v. 1.5.27.0), but it still doesn't get the right driver (Win 7-64). "Galaxy S" shows up in Device Manager, under "Other Devices", when I plug it in, but with a yellow triangle and no valid driver.
I've read a bit about internal memory issues with the Galaxy S. Am I banging my head against the wall with this phone? Does it sound like the internal memory is hooped? Is there any fix if it is? It seems to me that, following the instructions, a flash should work. Since it isn't, I'm beginning to think that it's not able to write/read what it needs to to/from internal memory...
If any of that twigs your memory for a suggestion as to how to proceed, please let me know. I've tried a lot, but probably not everything... Thanks for listening.
knottedknickers said:
but with a yellow triangle and no valid driver.
I'v Is there any fix if it is? .
Click to expand...
Click to collapse
For first issue download win 7 drivers from My Android Collections, also for fixing USB problems follow this as for your basic problem, what you seem to indicate is a corrupted Internal SD card, to solve that you need to use only the External SD card by this method
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
{
"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 are using XDA App or Tapatalk, long press on the post and select :good: Thanks
Its easier to give "Feedback" in this manner than make an additional post.
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! ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am following a YouTube video letter-for-letter and this is the part I’m stuck at. It doesn’t restart the phone like it’s supposed to. It just says “Sending” and never does anything. I renamed my TWRP img file to: “twrp-payton” since that’s what his YouTube video does and works for him. Tried removing the hyphen as well and re-downloading the img. Kept the original file name and still doesn’t work.
Some others had this issue in the YouTube comments and I tried all of the “possible solutions” but none work.
Any help is GREATLY appreciated.
43t34 said:
I am following a YouTube video letter-for-letter and this is the part I’m stuck at. It doesn’t restart the phone like it’s supposed to. It just says “Sending” and never does anything. I renamed my TWRP img file to: “twrp-payton” since that’s what his YouTube video does and works for him. Tried removing the hyphen as well and re-downloading the img. Kept the original file name and still doesn’t work.
Some others had this issue in the YouTube comments and I tried all of the “possible solutions” but none work.
Any help is GREATLY appreciated.
Click to expand...
Click to collapse
The img file is inside the same folder as fastboot files?
The file need to be in the same folder.
And which version are you using?
abrfilho said:
The img file is inside the same folder as fastboot files?
The file need to be in the same folder.
And which version are you using?
Click to expand...
Click to collapse
If that doesn't work, try using the Moto specific version of fastboot, called mfastboot.
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
cango123 said:
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
Click to expand...
Click to collapse
Just saw these replies, but this was the option I used to fix it. Tried an older PC downstairs and it worked.
My only issue now is: I have no 4G/LTE at all. Verizon SIM through StraightTalk. I went into APN settings, but everything is greyed out and can’t be edited, or added. When I go into my network settings and set my Preferred Network Type to “LTE only,” I lose all bars and signal. Is this just a Verizon thing or would it work with ATT SIM? Before I got the phone, I did extensive research to make sure it’d fully work on Verizon/StraightTalk, so I’m clueless right now.
A guy named Frank, with StraightTalk live chat, told me that my device isn’t 4G compatible....like, at all. Wth...? They didn’t seem like they knew what I was talking about, though.
ensure motorola drivers are installed and try different USB 2.0 ports.
cango123 said:
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
Click to expand...
Click to collapse
Worked for me! Thanks for the great help!
Hi everyone,
I installed infected flashtool app wa strying to flash my xz3, usb debugging was activated when windows detected a malware from the computer during flashtool setup while my phone was plugged, is there any possibillity to be hacked? and if so, is wipping data and factory reset would solve the problem? thank you all.
Rvn.
I believe so. If not we can solve anything here lol
Of course it's possible
ID the issue. Isolate your backup data drives from both machines until proven clean.
A factory reset won't get rid of flashed malware... a hacker's wet dream.
If so you need reflash with a clean rom copy.
Pachacouti said:
I believe so. If not we can solve anything here lol
Click to expand...
Click to collapse
Lol, after some pain and suffering...
Lol, but In android even if usb debugging activated you need to approve the access to it whenever a computer going to use it, a window pop up on your phone to either approve or deny which it didn't appear at all. So I'm safe I think?
ravncool said:
Lol, but In android even if usb debugging activated you need to approve the access to it whenever a computer going to use it, a window pop up on your phone to either approve or deny which it didn't appear at all. So I'm safe I think?
Click to expand...
Click to collapse
Well it isn't going to kill you, so you are safe.
As for the affected device(s)... they are scared.
Trust Windows security?
I mean, deny/allow window appears on phone not windows, I didn't allow because it didn't appear at all lol, sorry for my English
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I didn't get this at all, so computer got no access through USB debugging then phone is safe right loool
Dont feel safe JUST yet...
If the adb window for granting keys does not show, that could be a warning sign, that adb MAY still be hacked (if hacked at all)
disconnect fone, go into developer options. look for revoke permissions, then plug fone back in, tell me if you see the window again?
Sometimes it goes into the background and you cant see it in time so it shuts you out...
If all goes well, on pc,
adb shell (should give grant window in fone)
settings put secure install_non_market_apps 1
settings put global adb_enabled 1
settings put global setup_wizard_has_run 1
settings put secure user_setup_complete 1
settings put global device_provisioned 1
settings put global development_settings_enabled 1
then even after a flash, if you never flashed your bootloader, you wont need to continually grant keys
Thanks for your time and answers brother..
But to make it more clear, I wasn't at a point where it had to show up (ADB window on phone), I just opened the app flashtool, I have seen it getting online stuff from GitHub and getting ready, after that it started detecting the phone after Malware Warning appeared on windows, at this time I just removed the phone and it wasn't into any mode. Only usb debugging was active.
I hope I make it more clear, and waiting your answers. Thanks a lot.
You've a virus in your pc, so fone wont allow you to connect until you remove virus ?
Deal with the virus first, then we'll probably find out your fone is fine...
Flashtool MAY be seen as a virus in windows so you may need to disable some security settings, it may not be a virus at all :O
Edit, best doing flashtool offline btw
I love you man, really I appreciate your time and help, now it's fine. I understand. Thanks a lot guys.