Database Develop

Exercise in bricking the Fire. Any advice?

So let's say theoretically that someone in their first week of using an Android device (ever) were to boot up the TWRP recovery and wipe their Fire because YOLO. Would anyone have advice for any possible way to revive it? Here's a description of the device's state:
It boots the Amazon logo only, and adb lists the device as unauthorized. If I boot it in recovery it says it's in fastboot mode and adb doesn't recognize the device at all. (Edit: ) Fastboot does recognize it though, but I'm not sure of the best path to take since I can't use adb to push files to the device for reinstallation of the firmware.
So from my view it's a paperweight, and that's cool because what I did was all kinds of dumb (thinking I could still revive it after what I was doing). But before I use it as a door stop, I figured I might ask you guys what you'd do. I'm guessing maybe I boot from an image that allows me to push the firmware to the sdcard, then I can boot from TWRP recovery and install it, but the first image to use there is something I'm not yet sure of.

Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639

stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Thanks for the reply
I think that's along the lines of what I need to do, but I can't use adb sideload as adb no longer sees the devices in recovery. Fastboot does though.

stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Ah you know what, you just encouraged me to read over again and try one different thing. The CM recovery enables adb sideload, and I'm pushing the stock firmware to it now.
Thanks for the help

I need some help unbricking my fire...

Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!

Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.

Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740

hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36

blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.

blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.

I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..

blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!

Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.

drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.

I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.

I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!

So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!

drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?

thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip

drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.

thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.

What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.

blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery

watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4

Stuck in recovery mode

I just received my new oneplus 3t
After setting up the basics I updated to Android nougat
It gave an error,
the phone reboots, asks for my code, entered my code started decrypting, got stuck, after 10 mins the phone reboots and the cycle repeated.
Called the help desk, got into recovery mode, wiped everything and now it keeps rebooting into recovery mode.
Is there a way to get out of this?

guusguus said:
I just received my new oneplus 3t
After setting up the basics I updated to Android nougat
It gave an error,
the phone reboots, asks for my code, entered my code started decrypting, got stuck, after 10 mins the phone reboots and the cycle repeated.
Called the help desk, got into recovery mode, wiped everything and now it keeps rebooting into recovery mode.
Is there a way to get out of this?
Click to expand...
Click to collapse
What do you mean by "everything"? If I guess correctly, just get the full 4.0.2 and sideload it from stock recovery.

nvertigo67 said:
What do you mean by "everything"? If I guess correctly, just get the full 4.0.2 and sideload it from stock recovery.
Click to expand...
Click to collapse
I mean the hard reset, kind of a noob here.
I have the option to install from internal storage but the customer service said that might break my phone or something.

guusguus said:
I mean the hard reset, kind of a noob here.
I have the option to install from internal storage but the customer service said that might break my phone or something.
Click to expand...
Click to collapse
I'm pretty sure atock recovery has the option to install via adb sideload - but I had to admit, I've never seen the stock-recovery...

nvertigo67 said:
I'm pretty sure atock recovery has the option to install via adb sideload - but I had to admit, I've never seen the stock-recovery...
Click to expand...
Click to collapse
Well I don't wanna mess around before I **** up my warranty. In that case I would have no phone and no money.

guusguus said:
Well I don't wanna mess around before I **** up my warranty. In that case I would have no phone and no money.
Click to expand...
Click to collapse
Boy, you own a OnePlus device:
https://oneplus.net/nl/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
One of my main reasons to go for oneplus!
BTW: these devices are really hard to brick - and if you have bricked it, there is an unbrick-tool...
BTW2: adb sideload does not unlock boot loader or make 3t explode. sideloading a rom is just an other method to update stock roms.

nvertigo67 said:
Boy, you own a OnePlus device:
https://oneplus.net/nl/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
One of my main reasons to go for oneplus!
BTW: these devices are really hard to brick - and if you have bricked it, there is an unbrick-tool...
BTW2: adb sideload does not unlock boot loader or make 3t explode. sideloading a rom is just an other method to update stock roms.
Click to expand...
Click to collapse
I have exactly the same problem. Do we have any stock ROM we can try to use to install it via recovery? Cos I can't access to internal storage, and there's an option in recovery to that (but i have nothing on it...)

Same issue just today, download adb for your computer, download the file from one plus and sideload it. I had to place the file in the adb folder on my computer to get it to work correctly.
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app

One plus 3T stuck in recovery no acces to internal storage PC
Helle everybody,
A couple of weeks ago i unlocked my boot-loader of my one plus 3T.
I was also planning on rooting my phone and flash a custom recovery but i could not acces the internal storage of my phone through my laptop (win 10). So after a couple of hours trying i decided this was to complicated for me and just went on using my phone without a custom recovery/rooting... but with my bootloader still unlocked.
Today i received an OTA update and installed it. Now i have a big problem i am stuck in TWRP recovery mode and still cant acces my internal memory through my pc.... so i cant flash the factory ROM and reboot my device. Does anybody know how i can get acces to my internal memory or how to get my device out of TWRP recovery mode? I am really a beginner so please explain clearly.
Greetings Bas

baswillems123 said:
Helle everybody,
A couple of weeks ago i unlocked my boot-loader of my one plus 3T.
I was also planning on rooting my phone and flash a custom recovery but i could not acces the internal storage of my phone through my laptop (win 10). So after a couple of hours trying i decided this was to complicated for me and just went on using my phone without a custom recovery/rooting... but with my bootloader still unlocked.
Today i received an OTA update and installed it. Now i have a big problem i am stuck in TWRP recovery mode and still cant acces my internal memory through my pc.... so i cant flash the factory ROM and reboot my device. Does anybody know how i can get acces to my internal memory or how to get my device out of TWRP recovery mode? I am really a beginner so please explain clearly.
Greetings Bas
Click to expand...
Click to collapse
Use this...
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Ty
Thanks

I really ****ed up

So, I ****ed up.
Earlier this night i hard bricked my device while trying to uninstall Magisk. Used a guide that worked and was back on stock OOS 3.5.0.
In the old Oxygen OS I installed TWRP. But the thing with the recovery was that you needed to boot recovery from the command line with the command
Code:
fastboot boot twrp.img
. If I booted into recovery in any other way the screen is just black and never boots.
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
I relocked it, and when it was done I got the prompt to fill in the password to start Android. But the thing was I did not use any security options, no fingerprint or pin code. So zero luck there. And now I can't boot into recovery because I didn't flash the stock recovery because I'm a retard, so when I'm trying to boot recovery it's just black. So I have no chance to come back. Please help...

So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!

thes3usa said:
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply, I tried to do the method with the MSMDownload thing yesterday, but the computer did not recognize the device. It was late in the night (5am) so I went to bed. This morning I took my other computer and plugged my phone in, it recognized it and I was able to fully recover the phone!

avveawesome said:
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
Click to expand...
Click to collapse
This isn't good idea. As already noted, never relock the bootloader on this device with TWRP, root, etc. It should only be relocked after returning to full stock condition.
Also, never install an incremental OTA when you have TWRP (root, etc.), only the full update zips should be used in that case.
Try to stick to these forums for advice. Maybe the guidance your found above is not specific to this device?

Phone stuck in bootloop

Hey everybody
My friend gave me his Mi 9t Pro to repair it as he bricked it accidentally and he knew I had experience with changing ROMs and recoveries.
From what I know, what he did is tried to change dpi and then phone jumped into bootloop.
Let me just state that:
- bootloader is locked
- there is no custom recovery
- I have no authorization for ADB
I am stuck and would be really thankful for any ideas. Wiping data is not an option at the moment as we want to recover data from the phone.
Dropping battery to 0% and then charging didn't work.
Adb is only possible at the very short moment phone gets into boot animation, but as I have no authorization I can't pull files from it.
For whatever I tried ADB sideload when connected with Mi Assistant in recovery didn't help me neither.
If you have any ideas please share them with me, I'll appreciate that a lot

Hilus said:
Hey everybody
My friend gave me his Mi 9t Pro to repair it as he bricked it accidentally and he knew I had experience with changing ROMs and recoveries.
From what I know, what he did is tried to change dpi and then phone jumped into bootloop.
Let me just state that:
- bootloader is locked
- there is no custom recovery
- I have no authorization for ADB
I am stuck and would be really thankful for any ideas. Wiping data is not an option at the moment as we want to recover data from the phone.
Dropping battery to 0% and then charging didn't work.
Adb is only possible at the very short moment phone gets into boot animation, but as I have no authorization I can't pull files from it.
For whatever I tried ADB sideload when connected with Mi Assistant in recovery didn't help me neither.
If you have any ideas please share them with me, I'll appreciate that a lot
Click to expand...
Click to collapse
I can't see any way you're going to keep the data. Recovering the phone is going to wipe everything. Without an unlocked bootloader I can't see any way your going to be able to access the data first before restoring the phone.
As far as restoring the phone, if you can access the official recovery, then you should, hopefully, be able to flash an official recovery ROM from there, or so I believe, I've never actually tried it.
If that fails, then you will need to EDL flash the phone.
This involves taking off the back to put the phone in EDL mode, then paying someone, who has an authorised account, to remotely flash the phone for you.

Robbo.5000 said:
I can't see any way you're going to keep the data. Recovering the phone is going to wipe everything. Without an unlocked bootloader I can't see any way your going to be able to access the data first before restoring the phone.
As far as restoring the phone, if you can access the official recovery, then you should, hopefully, be able to flash an official recovery ROM from there, or so I believe, I've never actually tried it.
If that fails, then you will need to EDL flash the phone.
This involves taking off the back to put the phone in EDL mode, then paying someone, who has an authorised account, to remotely flash the phone for you.
Click to expand...
Click to collapse
Yeah, that's kinda hard situation :/
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Thanks for answering either way

Hilus said:
Yeah, that's kinda hard situation :/
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Thanks for answering either way
Click to expand...
Click to collapse
Have you tried updating ROM through Mi PC Suite (latest version)?

0xFast said:
Have you tried updating ROM through Mi PC Suite (latest version)?
Click to expand...
Click to collapse
I tried through MiFlash, but it only allows fastboot ROMs, and because bootloader is not unlocked I couldn't flash it. But that's a good idea, I'll try Mi PC Suite, I'll let you know how it ends.

0xFast said:
Have you tried updating ROM through Mi PC Suite (latest version)?
Click to expand...
Click to collapse
I tried, but seeing that mipcsutie is same program as mi assistant, I cannot do anything because it doesn't recognize my phone.

Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
---------- Post added at 12:13 AM ---------- Previous post was at 12:10 AM ----------
Because not possible if your bootloader was locked to enter EDL mode, then AFAIK you need Mi Account with authorization to flashing with EDL mode.

Hilus said:
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Click to expand...
Click to collapse
Are you talking phones in general, or this phone specifically. For this phone the only way is to take the back off and do the 'Test point' method. I've never heard of anyone successfully entering EDL mode using any other method.
Hilus said:
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
Click to expand...
Click to collapse
ADB sideload needs the phone to be put into ADB sideload mode first, so to speak. This is why you have the ADB sideload option in TWRP. You don't have this option in the standard recovery.
Hilus said:
I tried, but seeing that mipcsutie is same program as mi assistant, I cannot do anything because it doesn't recognize my phone.
Click to expand...
Click to collapse
0xFast said:
Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
Click to expand...
Click to collapse
Also make sure you're using a good USB cable and also try a different USB port.
Also try using your friends PC. I assume they have previously connected the phone to the PC successfully before, so they should have the correct drivers already installed.

Robbo.5000 said:
Are you talking phones in general, or this phone specifically. For this phone the only way is to take the back off and do the 'Test point' method. I've never heard of anyone successfully entering EDL mode using any other method.
ADB sideload needs the phone to be put into ADB sideload mode first, so to speak. This is why you have the ADB sideload option in TWRP. You don't have this option in the standard recovery.
Also make sure you're using a good USB cable and also try a different USB port.
Also try using your friends PC. I assume they have previously connected the phone to the PC successfully before, so they should have the correct drivers already installed.
Click to expand...
Click to collapse
If you connect via 'Mi Assistan' option in recovery the phone connects to pc using adb sideload.
I tried different cables and ports, and I have correct drivers.

0xFast said:
Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
---------- Post added at 12:13 AM ---------- Previous post was at 12:10 AM ----------
Because not possible if your bootloader was locked to enter EDL mode, then AFAIK you need Mi Account with authorization to flashing with EDL mode.
Click to expand...
Click to collapse
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.

Hilus said:
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.
Click to expand...
Click to collapse
In this case your only option now is to EDL flash. Sorry. Search for guides on how to do this, within these forums. XDA admins have been removing contact details of anyone with an authorised account, who will remotely flash for you. These people charge for doing this, so it's against XDA policy to give details of people who perform paid for services. You will find recent posts from people who've got details of these people who can EDL flash, that will kindly allow you too PM them for details of such persons.

Hilus said:
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.
Click to expand...
Click to collapse
AFAIK, USB debugging not required just adb sideload to work.

Have you tried looking at the .bat files miflash executes from the fastboot images. You can flash system etc.. without dating perhaps this will reset the dpi