Database Develop

HELP!!! I bricked my N3!!!

Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial I Heimdalled the MI9_Fix.img.ext4 file and then started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimdall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!

533y4 said:
Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial and started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so I Heimalled the MI9_Fix.img.ext4 file and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!
Click to expand...
Click to collapse
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.

posersk8r said:
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.
Click to expand...
Click to collapse
I can do the ODIN part, then when I try the Heimdall part, it comes up with an error. I have tried it 5 times over. To a T... : (
And yes, I know you flash those BEFORE. That's what I meant to say, but I was in a rush...

Im in a similar pickle but my problem is that I need a way to get those files to the SD card because the thing is bricked. I can't copy the files to a bricked phone and every device in my house refuses to read the micro SD card.

533y4 said:
I was in a rush...
Click to expand...
Click to collapse
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.

mazdamiata210 said:
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.
Click to expand...
Click to collapse
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files;
MI9_fix.img.ext4
https://mega.co.nz/#F!icMTnSQY!bMBNFmUnn2_K8olSTYpwIA (mirror provided by drakeymcmb)
sec_csc.zip
rldv.zip
2400258.zip
Put everything except for the system.img on your external SD card
3) Download and install the MJ5 partions. Use Odin to flash these files (match the file names with the different upload slots)
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
THIS IS WHERE I CAN NO LONGER GO ANY FURTHER!!! IT SPITS A I/O ERROR 87 AT THIS POINT! I CANNOT GET AROUND THIS! THIS IS WHAT I NEED HELP WITH!
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
This will give you a stock MJ5 system. You can choose to stop here if you don't want to root.
10) Extract rldv.zip to the root of your internal sdcard (NOTE **my script removes Knox apps). Reboot, then once SuperSu installs, Reboot again.
This leaves you with a rooted MJ5 device.

533y4 said:
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
Click to expand...
Click to collapse
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​

mazdamiata210 said:
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​
Click to expand...
Click to collapse
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
The drivers named "WinUSB 6.1.7600"

533y4 said:
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
Click to expand...
Click to collapse
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?

mazdamiata210 said:
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?
Click to expand...
Click to collapse
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.

533y4 said:
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.
Click to expand...
Click to collapse
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.

I was in the same boat. I had to switch computers and it worked first time. Both of them were windows 8.1 btw.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Did you try changing ports for heimdall? Sounds like its not recognizing your n3, had that problem before too where after odin'ing the mj5 files heimdall wouldnt see my phone. Did a reboot on my laptop and changed ports had 7 different 2.0 cables. Just keep trying did this 5 times already and always had the same result.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

So is there no way to mount the card so that I can copy these files if I am bricked?

mazdamiata210 said:
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.
Click to expand...
Click to collapse
Did this every single time. I also have tried all 4 USB ports. This program (Heimdall) worked the first time no problem. That's the weird part... The second and on time all is a no go.
I have attached pictures. 3.jpg is Heimdall with the error.

Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

posersk8r said:
Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...

533y4 said:
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...
Click to expand...
Click to collapse
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.

mazdamiata210 said:
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.
Click to expand...
Click to collapse
I'm going to try my girls computer tomorrow after work. See if her crappy Toshiba can do any better.

My Phone is DEAD
I was talking on my phone yesterday and it just shut off and hasn't been back on since. It is not responding to anything i try. Power + Vol down + Home. When i plug it up, there is no sounds or vibration no response. The phone is in a permanent off state. Any thought or suggestion on how to repair. I did the OTA update last week SM-N900A.

Lost stock rom using safe strap

Hello I need help I am using safe strap 3.72 on a at&t note 3. In my stock rom location in safe strap I have no os and I am unable flash a new rom or even restore a backup. I tried going to stock recovery to do a factory reset still unable to restore my stock rom. Is there a away to repair this problem. Please help

ryanalivingston said:
Hello I need help I am using safe strap 3.72 on a at&t note 3. In my stock rom location in safe strap I have no os and I am unable flash a new rom or even restore a backup. I tried going to stock recovery to do a factory reset still unable to restore my stock rom. Is there a away to repair this problem. Please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-3-att/general/n900aucucnc2-odin-files-t2838117 for nc2

I am sorry I forgot to mention. I am unable to get Odin to recognize my phone when connected.

Do you have the phone in download mode

Yes I have my phone in download mode

Try different cable and USB slots

ryanalivingston said:
I am sorry I forgot to mention. I am unable to get Odin to recognize my phone when connected.
Click to expand...
Click to collapse
You may need to install the Sammy Drivers. If you install Kies 3 it will do it for you.

I have installed the latest Samsung drivers tried 3 or 4 different cables still no luck.

Well your best bet would be an att service center or Samsung experience booth at best buy

jerrycoffman45 said:
Well your best bet would be an att service center or Samsung experience booth at best buy
Click to expand...
Click to collapse
I have already been to the best buy and there systems couldn't find my phone

Call att you have a year warranty I assume since you factory reset the phone won't go past the Samsung boot screen the will send you a replacement for free
---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------
Of course don't tell them you where rooted and flashing custom roms

jerrycoffman45 said:
Call att you have a year warranty I assume since you factory reset the phone won't go past the Samsung boot screen the will send you a replacement for free
---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------
Of course don't tell them you where rooted and flashing custom roms
Click to expand...
Click to collapse
I am not in contract with at&t to go to them

ryanalivingston said:
I am not in contract with at&t to go to them
Click to expand...
Click to collapse
then if you cant get odin to see the phone your screwed sorry

jerrycoffman45 said:
then if you cant get odin to see the phone your screwed sorry
Click to expand...
Click to collapse
Thank you for trying to help.

ryanalivingston said:
Thank you for trying to help.
Click to expand...
Click to collapse
your welcome but i wasnt much help

ryanalivingston said:
Hello I need help I am using safe strap 3.72 on a at&t note 3. In my stock rom location in safe strap I have no os and I am unable flash a new rom or even restore a backup. I tried going to stock recovery to do a factory reset still unable to restore my stock rom. Is there a away to repair this problem. Please help
Click to expand...
Click to collapse
Back when our phones had jellybean, I did the exact same thing. I deleted my stock rom without installing a replacement. BIG NO NO!
Anyway, to get your phone recognized, I would install kies 3, then tools > reinstall device driver. Do this with the phone connected in download mode.
Next I would use the files found here to reinstall the stock kk rom using Odin: http://forum.xda-developers.com/note-3-att/general/n900aucucnc2-odin-files-t2838117
There is a guide on YouTube entitled "AT&T Note 3 MLG Restore Part 1" that should walk you through the process.
Please let me know if this helped.
Edit: I noticed that my fellow XDA members have recommended the same thing (except for telling kies to reinstall the drivers) As a last ditch effort, I would try a different pc running a different operating system (especially if you're using Windows 8).
---------- Post added at 05:04 AM ---------- Previous post was at 04:56 AM ----------
I took this from thedroidguy dot com.
"First Solution: This is the recommended way to make any Samsung device, in this case the Galaxy Note 3, get detected by the computer without a problem: download and install KIES. Depending on your connection, the download process may take several minutes to complete but the installation won’t take a minute. Installing KIES into your computer mean installing all necessary USB drivers as well. You can download KIES from here.
Second Solution: If you’ve already installed the KIES into your computer and it still refuses to detect the phone, reboot it and try again. If the problem persists, uninstall KIES, reboot the computer and plug the phone in. Let the computer detect the device as a general storage then install KIES again. This time, it would work.
Third Solution: If you don’t want to install KIES to your computer, you can download just the drivers. They are packed into one package and compressed to only have around 25 megabytes. You can find the download link from here.
Fourth Solution: There is also what they call the universal ADB driver that would make any Android device detectable by the computer once it’s installed. The driver was built by clockworkmod team and can be downloaded from their website."

sireniankyle said:
Back when our phones had jellybean, I did the exact same thing. I deleted my stock rom without installing a replacement. BIG NO NO!
Anyway, to get your phone recognized, I would install kies 3, then tools > reinstall device driver. Do this with the phone connected in download mode.
Next I would use the files found here to reinstall the stock kk rom using Odin: http://forum.xda-developers.com/note-3-att/general/n900aucucnc2-odin-files-t2838117
There is a guide on YouTube entitled "AT&T Note 3 MLG Restore Part 1" that should walk you through the process.
Please let me know if this helped.
Edit: I noticed that my fellow XDA members have recommended the same thing (except for telling kies to reinstall the drivers) As a last ditch effort, I would try a different pc running a different operating system (especially if you're using Windows 8).
---------- Post added at 05:04 AM ---------- Previous post was at 04:56 AM ----------
I took this from thedroidguy dot com.
"First Solution: This is the recommended way to make any Samsung device, in this case the Galaxy Note 3, get detected by the computer without a problem: download and install KIES. Depending on your connection, the download process may take several minutes to complete but the installation won’t take a minute. Installing KIES into your computer mean installing all necessary USB drivers as well. You can download KIES from here.
Second Solution: If you’ve already installed the KIES into your computer and it still refuses to detect the phone, reboot it and try again. If the problem persists, uninstall KIES, reboot the computer and plug the phone in. Let the computer detect the device as a general storage then install KIES again. This time, it would work.
Third Solution: If you don’t want to install KIES to your computer, you can download just the drivers. They are packed into one package and compressed to only have around 25 megabytes. You can find the download link from here.
Fourth Solution: There is also what they call the universal ADB driver that would make any Android device detectable by the computer once it’s installed. The driver was built by clockworkmod team and can be downloaded from their website."
Click to expand...
Click to collapse
The computer recognizes the phone just unable to get of in to recognize my phone in download mode

ryanalivingston said:
The computer recognizes the phone just unable to get of in to recognize my phone in download mode
Click to expand...
Click to collapse
Well if the phone is in download mode, and Odin is up to date, then it has to be a driver issue. My pc always acts like it's recognizing my devices, but then it screws with the drivers to where nothing works.

Thanks for all the help I don't know what will work but I will continue to try everyone's advice and hopefully something works for me. At this time I can only use the for rom slots in safe strap. Phone works great other than I am unable to use full storage space of the note 3

It might be too late to help but i had to uninstall all the drivers from the PC then put my phone in download mode, then plug it in to the pc and it would install the drive and work maybe?
Or pull your sd card our and copy over a rom to it then put it back in and boot and flash?

(please help)hardbrick with usb debuging off

please help me anyone.my flex after install rom hardbricked.it boot only in download mode and now its unrooted.no recovery menu.but i cant back to stock with usb debuging off.not conecting with my phone in kdz installation.any solution any idea?my flex is really dead

tomtsigg said:
please help me anyone.my flex after install rom hardbricked.it boot only in download mode and now its unrooted.no recovery menu.but i cant back to stock with usb debuging off.not conecting with my phone in kdz installation.any solution any idea?my flex is really dead
Click to expand...
Click to collapse
Regardless if you have USB debugging on or off if you plug up to your PC in download mode you can use the LG PC SUITE software that comes on your phone, or download it from lg, to revive your phone.
You'll need your PC connected to the internet for this
Just put in download mode
Plug into PC
Open pc suite
At the top click mobile devices tab
In drop down click "restore upgrade error"
If it doesn't recognize your phone you will need your serial number and your device model number I.e D959, D950, D955, D958, etc.
Sit back and relax this takes about 10 mins
This is the only method I use now to restore my device. Works like a charm for me.

when the phone is softbricked and usb debugging is off you cant install all drivers my friend.and phone no connected with anything.thanks for your intresting

mattwheat said:
Regardless if you have USB debugging on or off if you plug up to your PC in download mode you can use the LG PC SUITE software that comes on your phone, or download it from lg, to revive your phone.
You'll need your PC connected to the internet for this
Just put in download mode
Plug into PC
Open pc suite
At the top click mobile devices tab
In drop down click "restore upgrade error"
If it doesn't recognize your phone you will need your serial number and your device model number I.e D959, D950, D955, D958, etc.
Sit back and relax this takes about 10 mins
This is the only method I use now to restore my device. Works like a charm for me.
Click to expand...
Click to collapse
KDZ is over 1.5GB. How it takes 10 minutes?
Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted
using XDA mobile app

Once it downloads the kdz it only takes 10 mins.

mattwheat said:
Once it downloads the kdz it only takes 10 mins.
Click to expand...
Click to collapse
Is there an option in LG suite to manually place already downloaded KDZ in the specific folder.
So it wont downloading it..
Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted
using XDA mobile app

When phone is hard bricked it wont boot. USB debug does work only when system is up and running.
Sent from my LG-D955 using XDA Free mobile app

Murshad007 said:
Is there an option in LG suite to manually place already downloaded KDZ in the specific folder.
So it wont downloading it..
Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted
using XDA mobile app
Click to expand...
Click to collapse
Yes. There is a folder on your c:\program data\lg ....something or other folder. go into it and into mobile phone folder I think its called. I'm not in front of my PC right now. But you'll find the folder you need in there. Just put the stock .kdz file in there. It must be the same version or newer than you're on. Or was on when it bricked.
I've even actually pulled the .kdz files from there after I used PC suite the first couple of times. Used them in the lg flash tool.
---------- Post added at 10:47 PM ---------- Previous post was at 10:39 PM ----------
robdevil said:
When phone is hard bricked it wont boot. USB debug does work only when system is up and running.
Sent from my LG-D955 using XDA Free mobile app
Click to expand...
Click to collapse
I've noticed, by accident, when I did the factory reset method \ steps to get into twrp, but for some reason twrp wasn't installed and it actually reset my phone.... And caused it to boot loop due to what ever i did to FUBAR it. Factory reset defaults USB debugging back to off but when in download mode it didn't stop PC suite from "restoring upgrade errors" and flashing my flex back to stock. I've used it so much I now make sure my PC at work has it and the .kdz on it. My laptop has it and I have a flash drive in my truck with PC suite & .kdz on it. Lmao. Yeah I get a little ballsy sometimes and try just about anything. OK a lot but I always have a way back now.

my friend try this with pc suite and it stop in 0%.not run.and my interner connection is very good.why?

I have no clue. Try different usb cable if you don't have the one the one that came with it. I've noticed my flex and nexus 7 don't like some cheaper no name brand cables when transferring files or using adb. They seem to be fine with just charging. I use mostly my usb cable that came with my moto razr hd maxx. Only cuz it stays connected in the micro end better. And I have no clue what happened to the original.
Also make sure you have the latest LG drivers installed.
Sometimes to get the old "offline method" to work I would have to make sure no Samsung drivers were installed or Motorola drivers, Kies, or moto device manager. If any were I would have to uninstall them and the LG drivers. Restart Windows. And re install the latest LG drivers.
So not sure what exactly did the trick but I did all of it just to make sure and something helped. Try that. Don't plug in your flex till after LG drivers are installed and you have restarted Windows. I don't know but seems like what ever sequence or install or uninstall of drivers I've done now works all the time. Before we got bump I would go from 4.2.2 to 4.4.2 a couple times a week just to fool around a few days till something I modified or themed would bootloop me and I would get passed and go back to 4.2.2 and swear I'm not leaving JB till we have a custom recovery on KK. But my A.D.D. would get the better of me and I ,..... oh yeah I gotta run get some,.... oh never mind I'll .... huh oh yeah my A.D.D. it causing crack flashing syndrome. Lmao

I am on F340K Rooted Stock recovery Kitkat 4.4.2 V20D.
after changing my build.prop I forgot to set permissions.
Now I am unable to fix permissions through adb... although I succesfully Pushed the Original backup file from my PC..
I have two backups of Build.prop in my phone also.. One in system directory with the name of Build.prop.bak and 2nd is external sd card.
please advise me what to do?. I can access phone though Volume+Power = LG service Manaual (which is shown in ADB as Recovery device)
whereas Original Stock recovery Volume down+Power have an Android Logo with Red Triangle...
Is there a way I can install/ Push Some custome recovery Like Freedom Flex Bumped cwm or twrp to my phone? Fixing permissions through ADB Operation not Permitted or Permission denied error

My MI3 seems bricked

Hello guys,
I tried updating it to MM from KitKat by simply flashing it via TWRP . The partition table got corrupted it seems. The phone doesn't boot up. No lights glowing. Initially when connected to pc, few drives were shown. Now when I connect it says the USB is unrecognized. In Mi-flash , its not getting detected. Any solutions?

http://forum.xda-developers.com/showthread.php?t=3353289
Sent from my MI 3W using XDA-Developers mobile app
---------- Post added at 03:36 PM ---------- Previous post was at 03:35 PM ----------
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=3353289
Sent from my MI 3W using XDA-Developers mobile app
Click to expand...
Click to collapse
Please do some searching...
Sent from my MI 3W using XDA-Developers mobile app

[email protected] said:
http://forum.xda-developers.com/showthread.php?t=3353289
Sent from my MI 3W using XDA-Developers mobile app
---------- Post added at 03:36 PM ---------- Previous post was at 03:35 PM ----------
Please do some searching...
Sent from my MI 3W using XDA-Developers mobile app
Click to expand...
Click to collapse
U didn't read the whole post I guess. For me, Those drives are not showing up anymore. The device is not getting detected. It says USB cannot be recognized. On Mi Flash Tool , the device is not showing up.

what u have to do is...
1) (if the screen is blank even after power on) power on the device
2) Download SDI and connect ur phone to pc. if it connects with unknown drivers , use SDI to detect those drivers and it will take care of it
(in my case it shows some qualcomm drivers are installed)
3) if everything works fine, put ur phone in FASTBOOT MODE . (i know there is no display but u can continue pressing vol down+ power button , and there will be a detection sound in pc)
4) at this point there will be another sets of driver will get load.
5) use mi flash to refresh your device. it will show some unique character number or just COM port if SDI is used
6) use any stable fastboot rom and select "flash all' script.
7) flash it, it will normally take more time than normal and u will see weird massage during installation. pay no attention to that and don't disconnect phone if u get pissed.
8) and tadaaa...ur phone will become normal.

sid8840 said:
what u have to do is...
1) (if the screen is blank even after power on) power on the device
2) Download SDI and connect ur phone to pc. if it connects with unknown drivers , use SDI to detect those drivers and it will take care of it
(in my case it shows some qualcomm drivers are installed)
3) if everything works fine, put ur phone in FASTBOOT MODE . (i know there is no display but u can continue pressing vol down+ power button , and there will be a detection sound in pc)
4) at this point there will be another sets of driver will get load.
5) use mi flash to refresh your device. it will show some unique character number or just COM port if SDI is used
6) use any stable fastboot rom and select "flash all' script.
7) flash it, it will normally take more time than normal and u will see weird massage during installation. pay no attention to that and don't disconnect phone if u get pissed.
8) and tadaaa...ur phone will become normal.
Click to expand...
Click to collapse
the drivers got installed via windows update. tried flashing, it all worked and completed successfully. The issue now is , the screen is not powering on.

it worked like hell. Thanks a lot buddy.. Problem solved. Mine was windows 10, when I checked the settings, the connection was metered. Hence no drivers were getting installed. Once I changed it , the drivers got downloaded automatically from internet. Then came the driver signature verification, I disabled it, and everything worked fine after that. The screen wasnt powering on even after completion. Then I noticed that the Flashall.bat has to be modified,
as per the thread
http://forum.xda-developers.com/xiaomi-mi-3/general/guide-instruction-to-restore-mi4-mi3-t3279927
flashed with changes applied first and then again flashed after reverting the change on the script. The process got completed, but the device wasnt powering on.
tried connecting and disconnecting the phone to pc multiple times , and it just booted up with the logo voila. Thanks a lot guys .

dittualex said:
it worked like hell. Thanks a lot buddy.. Problem solved. Mine was windows 10, when I checked the settings, the connection was metered. Hence no drivers were getting installed. Once I changed it , the drivers got downloaded automatically from internet. Then came the driver signature verification, I disabled it, and everything worked fine after that. The screen wasnt powering on even after completion. Then I noticed that the Flashall.bat has to be modified,
as per the thread
http://forum.xda-developers.com/xiaomi-mi-3/general/guide-instruction-to-restore-mi4-mi3-t3279927
flashed with changes applied first and then again flashed after reverting the change on the script. The process got completed, but the device wasnt powering on.
tried connecting and disconnecting the phone to pc multiple times , and it just booted up with the logo voila. Thanks a lot guys .
Click to expand...
Click to collapse
happy to help!!

Hello guys,
Unfortunately I have only ubuntu machine. Can someone help me to solve this issue.
Thanks in Advance!

fix
http://en.miui.com/thread-243483-1-1.html
try this will surely help

phone :moto xt1068............ prob :not booting

i used kingo root in PC to root the phone , then after when i reboot the phone, it was stuck with the logo fore ever..
then i unlocked the boot loader and then flashes it with kitkat stock firmware..
then downloaded the lollipop update in the phone , after installing it the phone didn't booted ..
i cant boot it manually, cant go to fast boot mode ..
it is just dead...
what can i do ..plz help.
not showing qhslk bulk when connected to pc but shows ----unknown usb device(device descriptor request failed)

Oh I think its hardbricked dude,because if bootloader is unlocked then we shouldn't do any official updates...
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
Still u can try to charge it or connect it to pc and goto device manager in pc and see that if it showing qhslk bulk or not,...

Divesh ahuja said:
Oh I think its hardbricked dude,because if bootloader is unlocked then we shouldn't do any official updates...
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
Still u can try to charge it or connect it to pc and goto device manager in pc and see that if it showing qhslk bulk or not,...
Click to expand...
Click to collapse
nope..... not showing ......

Then what is it showing in pc??

Divesh ahuja said:
Then what is it showing in pc??
Click to expand...
Click to collapse
it shows ..
unknown usb device(device descriptor request failed)
i tried the blank flash but during the blank flash error occurs ..
cant install the specified driver for the blank flash..

Then its hardbricked bro,replace motherboard or sell it its body parts who needs or in the market

Just a few general ideas - probably won't help but you never know:
Leave it charging for several hours and then see if you can access fastboot
Try a different PC (including one that you've never plugged your phone into before, one with a different Windows version, etc.) to see if you can get it to recognise the phone as qhslk bulk
Try plugging the device into your PC using a different USB cable to see if you can get it to recognise the phone as qhslk bulk
Have a look around the web on guides for restoring a hard-bricked Moto G 2014 (specific model, type, etc.). This probably won't work but anything is worth a try. You could try following these on different PCs, with different USB cables, etc.
I think this problem was caused by trying to downgrade your phone to KitKat
Hope you get it working