Database Develop

Rooting Problem

Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
EDIT: What I did from beginning was followed this video "How to Root the HTC One-FlamingArio"to the point where you try and flash the recovery fastboot. That didnt work so after trying to fix that I tried How To Root HTC One & Unlock Bootloader - Easiest & User Friendly- The smoking Android ( super boot a 1 click install) that made my bootloader screen turn to tampered. after that I tried One_M7_All-In-One_Kit_v1.
Note in all in one kit I did erase cache and standard recovery works fine, I've re-installed it may times.
Cant post links yet but I gave video names.
EDIT: when I do the cmd fastboot devices my device shows up when I do adb devices nothing shows up could this be part of the problem?
Thank you all for your help, I re-installed all the programs on my laptop and redid all the steps and it worked. Bye!

Try this in ABD fastboot erase cache then flash the recovery again i hope this helps:fingers-crossed:

What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps

Tonberry23 said:
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
Click to expand...
Click to collapse
Keep an eye on this thread http://forum.xda-developers.com/showthread.php?t=2302870
Many people are looking for the Telus RUU.
Can you still access standard recovery? If so try reverting to factory settings (all data will be lost) and try to boot.
If you can get it to boot you should have more luck in trying to root your device.
I know that I had some issue's trying to get root on my device. But once I got S-off with revone, I was able to install root no problem.
ArmedandDangerous said:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Click to expand...
Click to collapse
But I would agree, if you can post the steps you have taken so we know where the bottleneck is.
Hope this helps you out bud

Still need help

Tonberry23 said:
Still need help
Click to expand...
Click to collapse
Nice to see you sorted it

Assuming you have actually flashed a recovery image to your device, you will then need to push a ROM to your sd card so that you can flash it in recovery.
Just do the following:
1. I am guessing you have the HTC drivers installed on your PC.
2. Download the attached adb.zip and unzip it to a folder on your C drive and call the folder whatever you like.
3. Boot your device into recovery and plug it in to a powered USB port on your PC.
4. Navigate to the folder that you just created on your PC and copy your ROM zip into it. rename the ROM zip to 'rom.zip' to make life easy.
5. Inside the folder, press and hold the shift key and right click in a blank part of the window and select 'Open command window here' (screenshot attached).
6. Type 'adb push rom.zip /sdcard' (don't use the quote marks)
7. Press 'enter'
8. Once the zip has finished being pushed to your sdcard, you can reboot into recovery and then flash it as normal.
EDIT: That will teach me not to read to the very end of a post. I'll leave this here for someone else.

[Q] HTC One (M7) Bricked???

Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )

As long as it boots into Recovery its not bricked. Do you have the HTC Driver installed on your computer?
Android Revolution HD 53 requires min. TWRP 2.6.3.3. Your version is too old.

foxgre said:
Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )
Click to expand...
Click to collapse
From recovery go to fastboot connect phone to pc.
It must be recognized.
Then flash boot.img which is in the Revolution.zip.
Then install the rom via recovery.
Remember for unlock and not s-off users the boot.img must be flashed befor flashing a rom.zip.
Sent by myself, without help )

i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly

SAME problem (or pretty similar) here
foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks

foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
Duwie_80 said:
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks
Click to expand...
Click to collapse
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have

nkk71 said:
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have
Click to expand...
Click to collapse
Let me try and I'll tell you later. I also think it's a matter of drivers, so I was downloading and re-installing it... Thank you for your help
-------------------------------------------------- UPDATE --------------------------------------------------------------------------------
Well, I followed your steps (LET ME THANK YOU FOR MAKING THAT GUIDE) and now the device is "My HTC" as you show.
Something has changed:
If I type "adb devices" (in PC) when phone is in fastboot, the listing is void (before I got "FA34HW903605 fastboot"), and if I do the same while phone is in recovery, I get the mentioned "FA34HW903605 recovery".
In Windows7 I don't see "My HTC" as a conventional USB storage or Memory of a Camera (should it be?)
I've managed to ADB PUSH a ROM (ARHD) in recovery, but now I get an error message: "Unable to mount '/data' " and "Unable to mount internal storage " then FAILED. Now I'll try flashing a new recovery...

WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.

Duwie_80 said:
WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.
Click to expand...
Click to collapse
no problem, glad to be of help
remember for most 4.4 ROMs, (for m7_u/ul) TWRP 2.6.3.3 (or higher) is recommended at the moment.
though you should be good by downloading it, then checking MD5 to make sure the download isnt corrupt (that site doesnt work with download managers), then:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery and push the rom

Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:

foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
you're really not giving any details... so you hear a sound... what does Windows Device Manager show??

foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.

Duwie_80 said:
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.
Click to expand...
Click to collapse
Thanks again i am already looking for it.

AT LAST!!!
I've managed to push the rom.
Thank you very much for your help

foxgre said:
AT LAST!!!
I've managed to push the rom.
Thank you very much for your help
Click to expand...
Click to collapse
Hey, congratulations!! :good::good::good:

Can someone PLEASE help me boot my phone into FASTBOOT mode? ( T mobile h811) on CM13

When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?

did you ever unlock the phone....?

Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.

Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)

Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.

aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed

You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.

I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit

Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know

TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.

I reasked the question in Q and A. Please help some one.

You start over. LG bridge.

Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?

The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?

Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing

thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks

* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h

the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.

Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.

travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.

Installed Magisk APP and flashed Magisk v14.0 (BRICKED)

It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!

Stone. Cold said:
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Click to expand...
Click to collapse
Yes, you are going to need a fastboot cable. You can pick one up on Amazon for cheap or you can make your own by using some tutorial online. After you get the fastboot cable, use the Kindle Fire restore tool that I will link down below. Download it (it will take a while) and run it. Please read the directions because I didn't at first and I boot looped my Kindle by installing older recovery and boot image. After this is complete your Kindle will work again. I wouldn't recommend installing Magisk again because it modifies the boot loader. Sorry.
KFHD Restore tool (that tool that I mentioned): https://forum.xda-developers.com/showthread.php?t=1951254

Thank you for this, will. I will follow your instructions once I have received my fastboot cable
Again, thank you. I have left my tablet on my shelf for quite some time now and didn't really have time to fix it due to college work, and so. But I will definitely let you know the results :fingers-crossed:

I made pretty mutch the same error like you and flashed Magisk 12. I used the fastboot cable, entered fastboot and used the recovery tool to restore recovery and stock Rom with supersu and apex launcher. After following exectly the steps in 2. Bootloader and twrp. The problem I am facing is the same I faced before. After flashing linearOS 14 with twrp. I reboot from recovery. At first it showes the orange logo and the the blue. And it stays at blue logo for hours.
I don't know what to do. The strange thing is. I can boot in the recovered Amazonfire OS. But I can't flash any costum Rom.
I have no idea what I made wrong during the process. I followed all steps and repeated the procedure 3 times.
Always ending in blue logo.
Even without flashing any rom. Only following the steps to flash twrp with all the other stuff I am stuck on blue screen.
Please I need advice. Help me

Hardbrick - flashing rom in edl-mode

Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png

PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authenticated mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
As redmi 9 is mtk based device so their is not any edl point...if you have authorized account then you can easily flash it without the device open

Just use older preloader.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

That I have an authorized account was a wrong information.
When I try to flash it with sp_tool the following error is displayed: STATUS_CRC_BROM_FAIL 0xC0060005

PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
Disable authorization and unbrick your Redmi 9
Now you can unbrick your device even if the redmi logo not coming..just go to below link and follow their steps.... https://megafon929.github.io/mtk For more information and how to do follow the below post...
forum.xda-developers.com