Related
Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?
flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !
porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does
flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well
Hello Guys
I have a big problem
I installed twrp and unlock bootloader with no problem
But i try to install a Lineage Os , but after all wipe and flashing it , my internal storage is erased , and when enter in TWRP There are only a Micro Sd not not Internal Storage
The value of Internal Storage is 0
I can Rescue my phone??
I'm not very happy
I need a big HELP
or i lose my money and wonderful Phone
Please help me
Repair that with twrp options
I try , i flash with minimal adb the firmware huawei with extractor, rom stock run , but the display is black , i can't enter in bootloader , how i can repair? i'm very busy
i don't understand
dadi90 said:
I try , i flash with minimal adb the firmware huawei with extractor, rom stock run , but the display is black , i can't enter in bootloader , how i can repair? i'm very busy
i don't understand
Click to expand...
Click to collapse
Oh man which firmware you flashed ?
---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------
Another phones firmware relsults to device dead.
Help
venugopalu007 said:
Oh man which firmware you flashed ?
---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------
Another phones firmware relsults to device dead.
Click to expand...
Click to collapse
I'll explain my situation
I unblocked the bootloader and installed the Twrp without any problems
But first flashing the AOP and then the Lineage, I had first lost the internal memory, then recovered it.
Now when flash roms mod, the smartphone is in bootloop
O BRICK
I'm trying to flash the original firmware, but when I put DLOAD in the SD i am mistaken
And also with Huawei's Erecovery
My Honor 8 pro is currently installed with TWRP, but I can not install an official ROM or not to run it.
I am desperate
info
dadi90 said:
I'll explain my situation
I unblocked the bootloader and installed the Twrp without any problems
But first flashing the AOP and then the Lineage, I had first lost the internal memory, then recovered it.
Now when flash roms mod, the smartphone is in bootloop
O BRICK
I'm trying to flash the original firmware, but when I put DLOAD in the SD i am mistaken
And also with Huawei's Erecovery
My Honor 8 pro is currently installed with TWRP, but I can not install an official ROM or not to run it.
I am desperate
Click to expand...
Click to collapse
P.S Before Unlock Bootloader , i have the b172 Europe , i'm italian but Honor 8 pro is from Netherderlands
You need to have B172 fullOTA, then follow these steps.
Boot into TWRP, then flash the update.zip, after that without rebooting flash update_full_DUK-L09_hw_xx.zip and update_data_full_public.zip files. Wait untill they finish.
Factory reset and you should be good
dadi90 said:
I'll explain my situation
I unblocked the bootloader and installed the Twrp without any problems
But first flashing the AOP and then the Lineage, I had first lost the internal memory, then recovered it.
Now when flash roms mod, the smartphone is in bootloop
O BRICK
I'm trying to flash the original firmware, but when I put DLOAD in the SD i am mistaken
And also with Huawei's Erecovery
My Honor 8 pro is currently installed with TWRP, but I can not install an official ROM or not to run it.
I am desperate
Click to expand...
Click to collapse
Italian honor 8 pro , can i know the firmware version to search for firmware.
info
PalakMi said:
You need to have B172 fullOTA, then follow these steps.
Boot into TWRP, then flash the update.zip, after that without rebooting flash update_full_DUK-L09_hw_xx.zip and update_data_full_public.zip files. Wait untill they finish.
Factory reset and you should be good
Click to expand...
Click to collapse
I try but when use files in TWRP , give me a error in recovery and i can't flash files
info
venugopalu007 said:
Italian honor 8 pro , can i know the firmware version to search for firmware.
Click to expand...
Click to collapse
i have first b122 and successfully updating with ota in 133
dadi90 said:
i have first b122 and successfully updating with ota in 133
Click to expand...
Click to collapse
So you got running good now??
dadi90 said:
i have first b122 and successfully updating with ota in 133
Click to expand...
Click to collapse
How good?
no , i can use my phone with OS , only with rom of Morph in guide stock, i extract the firmware with huawei extractor, and i flashed cust, system, boot,recovery with adb
Now Phone Run Os , but is a NRDM90 keys ,, don't working a camera and another function
I try with Twrp and recovery stock but give a error always
I feel like crying
I do not know how to do
To get it back stock
Or at least with a rom in twrp
Nothing works
I spent 500 euro of burned phone so
I am desperate
dadi90 said:
no , i can use my phone with OS , only with rom of Morph in guide stock, i extract the firmware with huawei extractor, and i flashed cust, system, boot,recovery with adb
Now Phone Run Os , but is a NRDM90 keys ,, don't working a camera and another function
I try with Twrp and recovery stock but give a error always
I feel like crying
I do not know how to do
To get it back stock
Or at least with a rom in twrp
Nothing works
I spent 500 euro of burned phone so
I am desperate
Click to expand...
Click to collapse
Bro now can you flash the firmware in twrp
Step one format data and reboot again and to twrp wipe all and flash the firmware.
---------- Post added at 12:09 PM ---------- Previous post was at 12:06 PM ----------
dadi90 said:
no , i can use my phone with OS , only with rom of Morph in guide stock, i extract the firmware with huawei extractor, and i flashed cust, system, boot,recovery with adb
Now Phone Run Os , but is a NRDM90 keys ,, don't working a camera and another function
I try with Twrp and recovery stock but give a error always
I feel like crying
I do not know how to do
To get it back stock
Or at least with a rom in twrp
Nothing works
I spent 500 euro of burned phone so
I am desperate
Click to expand...
Click to collapse
Also bro the nrd keys also appears when the firmware is different region.
flash with twrp or stock recovery? i downloaded all firmware from ru website
when i try in twrp , this method failed
i have bought a honor 8 pro in UNIEURO in ITALY , the product have name DUK-L09 from netherlands
how i can search the right firmware????
info
i formact data , reboot in recovery twrp
i do all wipe
i flashing and i have this error
error have name
i upload the image
Repair internal storage with repair option in TWRP
With type of partition? ext3??
dadi90 said:
With type of partition? ext3??
Click to expand...
Click to collapse
Try Ext 4 but i think this wont work , try the rebranding guide to unbrick
I am looking for twrp for this handset, then i will install su.
I did not find any results, because the new phone launched.
I need somebody to share (TWRP + SuperSU + Xposed) for SM-J250F
Thank you very much
I have some information: Galaxy J2 Pro SM-J250F specifications
(I do not speak English. I'm using Google Translator. Sorry . . .)
I have the same devices ..
I need twrp for it
I'm using the same device. Looking for a custom recovery
i need twrp for j2 pro (2018)
+1
I have tried CF Auto root, but it didn't work. Did anyone try it?
Croveritiel said:
I have tried CF Auto root, but it didn't work. Did anyone try it?
Click to expand...
Click to collapse
If you want root then download magisk and use the create patched boot image option.
Croveritiel said:
I have tried CF Auto root, but it didn't work. Did anyone try it?
Click to expand...
Click to collapse
I tried using odin to flash unofficial twrp g250 f on my dual sim version. (G250f/ds) It did'nt work and I get some kind of error when going into recovery. Phone still works.
Thank you @ashyx i successfully rooted my device using patched boot img with Magisk. the instructions are explained in the official thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445.
I wonder if i can flash supersu with flashfire?
---------- Post added at 02:04 PM ---------- Previous post was at 01:50 PM ----------
SnarfSnarf said:
I tried using odin to flash unofficial twrp g250 f on my dual sim version. (G250f/ds) It did'nt work and I get some kind of error when going into recovery. Phone still works.
Click to expand...
Click to collapse
Yes i got the same, now I tripped knox and therefor I can't use secure folder x)
Croveritiel said:
Thank you @ashyx i successfully rooted my device using patched boot img with Magisk. the instructions are explained in the official thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445.
I wonder if i can flash supersu with flashfire?
Click to expand...
Click to collapse
I wouldn't they are not compatible. Also supersu is no longer up to date. Better sticking with Magisk which is under active development.
Tried using magisk method today. I downloaded the rom from sammobile, extracted the boot.img, put it on to the phone, magisk apk than patched it. I put the patched_boot.img back onto my computer and got stuck at fasttboot. I can get "adb devices" to list and connect but nothing for fastboot. I used command- "adb reboot bootloader" -to put phone into fastboot/download mode. I use linux, but also tried it under windows xp and windows 7, I fastboot can not find my phone. Odin can see me phone (Galaxy J2 2018)
So maybe others might have the same problem, maybe I am not putting phone into fastboot mode correctly?
SnarfSnarf said:
Tried using magisk method today. I downloaded the rom from sammobile, extracted the boot.img, put it on to the phone, magisk apk than patched it. I put the patched_boot.img back onto my computer and got stuck at fasttboot. I can get "adb devices" to list and connect but nothing for fastboot. I used command- "adb reboot bootloader" -to put phone into fastboot/download mode. I use linux, but also tried it under windows xp and windows 7, I fastboot can not find my phone. Odin can see me phone (Galaxy J2 2018)
So maybe others might have the same problem, maybe I am not putting phone into fastboot mode correctly?
Click to expand...
Click to collapse
Samsung doesn't use fastboot. You should have used the option to create a tar file then flash with odin.
Hey thanx Ashyx, I got root for J250F/DS! Thanks for the tip.
The phone rebooted and wiped after a message about integrity check fail at boot, but thats fine!
SnarfSnarf said:
Hey thanx Ashyx, I got root for J250F/DS! Thanks for the tip.
The phone rebooted and wiped after a message about integrity check fail at boot, but thats fine!
Click to expand...
Click to collapse
have you recognized that downloading in Samsung applications (Cloud or Galaxy apps) is so slow?
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
By the way, people can use directly the boot.img given in the cf auto root website.
https://desktop.firmware.mobi/device:1868/firmware:15154
Croveritiel said:
have you recognized that downloading in Samsung applications (Cloud or Galaxy apps) is so slow?
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
By the way, people can use directly the boot.img given in the cf auto root website.
https://desktop.firmware.mobi/device:1868/firmware:15154
Click to expand...
Click to collapse
Sorry, I deleted most samsung sys apps along with getting rid of most google stuff as well. I deleted one to many last night and I have to completely start over; used odin. The boot.img I used was in the 2GB zip file I found on sammobile, opened the AP*meta.tar.md5 and extracted the boot.img. I am not a rockstar in rooting, I did check the md5sum and both where different (desktop.firmware.mobi and the one I downloaded). I will say the rom I found on sammobile was the same listed in my phone under baseband version. I was a little skeptical because I didn't see any mention of DS (dual sim), but after flashing both sims work fine.
I'm retiring my old daily driver a Samsung S2, I noticed on my J2 phone I have option to encrypt sdcard but nothing mentioned about the phones storage. I guess I have some searching to do. cheers
3 cheers for removable battery, headphone jack and root.
SnarfSnarf said:
Hey thanx Ashyx, I got root for J250F/DS! Thanks for the tip.
The phone rebooted and wiped after a message about integrity check fail at boot, but thats fine!
Click to expand...
Click to collapse
can you tell me ..how did you root this device ? Plz and thanks..
If you have twrp can you send it ?
Ahmedzero800 said:
can you tell me ..how did you root this device ? Plz and thanks..
If you have twrp can you send it ?
Click to expand...
Click to collapse
Hello, I used magisk as recomended. I dont have twrp and I didnt see a rooted rom anywhere. Follow the magisk link Croveritiel posted. You will need: windows with odin, samsung drivers, boot.img and magisk manager.apk installed on your phone. For finding the boot.img I looked at my phones baseband version and downloaded the same stock rom from sammobile.com, extracted the zip, and extracted boot.img from the larger ap*.md5sum file. Transfer boot.img to phone. Open magisk manager on your phone and change the settings pached boot output format to img.tar . Next is to let magisk do its thing and it will make a new file named patched_boot.img.tar (or somthing similar). Move that file onto your pc, start odin, select ap and put phone into download/odin mode. Your phone will wipe when it reboots. After it reboots put magisk manager.apk back onto your phone. Your now rooted.
Ahmedzero800 said:
can you tell me ..how did you root this device ? Plz and thanks..
If you have twrp can you send it ?
Click to expand...
Click to collapse
@SnarfSnarf explained it all. the little difference in my case was downloading the boot.img directly from https://desktop.firmware.mobi/, I don't know if it is the right way but it worked for me.
Okey I have secssfully rooted my sm-j250f
But I am looking for twrp for it
I need to make backup and install roms
Can someone halp us ??.
Thanks .
Ahmedzero800 said:
Okey I have secssfully rooted my sm-j250f
But I am looking for twrp for it
I need to make backup and install roms
Can someone halp us ??.
Thanks .
Click to expand...
Click to collapse
You can do all that with Flashfire.
Hi I was on Pixel Experience ROM then I flashed MIUI 9.5.17 via Recovery TWRP 3.2.2.0 with clean flash (i.e. dalvik cache, data, system and internal storage wiped)
but Now mobile is dead its not even turning on. What should I do please help
Flash lazyflasher.
I think this thread provide a compatible version.
https://forum.xda-developers.com/an...zip-lazyflasher-tool-flashing-custom-t3549210
Or from here: -
https://forum.xda-developers.com/showpost.php?p=76904750&postcount=146
Device Manager is showing this
1
corkiejp said:
Flash lazyflasher.
I think this thread provide a compatible version.
https://forum.xda-developers.com/an...zip-lazyflasher-tool-flashing-custom-t3549210
Or from here: -
https://forum.xda-developers.com/showpost.php?p=76904750&postcount=146
Click to expand...
Click to collapse
Qualcomm HS-USB QDLoader 9008 (COM3)
follow this guide:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/guide-redmi-note-5-pro-unbrick-t3816178
huttui said:
Hi I was on Pixel Experience ROM then I flashed MIUI 9.5.17 via Recovery TWRP 3.2.2.0 with clean flash (i.e. dalvik cache, data, system and internal storage wiped)
but Now mobile is dead its not even turning on. What should I do please help
Click to expand...
Click to collapse
huttui said:
1
Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
mmhuseyni said:
follow this guide:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/guide-redmi-note-5-pro-unbrick-t3816178
Click to expand...
Click to collapse
He flashed a safe MIUI version, so should have not triggered ARP!
Solution needed
corkiejp said:
He flashed a safe MIUI version, so should have not triggered ARP!
Click to expand...
Click to collapse
Please provide solution asap
huttui said:
1
Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
I think you are in edl mode right now. You can try to flash the 9.5.17 ROM (use the fastboot ROM, not recovery ROM) with MiFlash tool.
edit: If you are not in edl mode, try to enter fastboot and put this code "fastboot oem edl" to enter edl mode.
Tried it
finsx said:
I think you are in edl mode right now. You can try to flash the 9.5.17 ROM (use the fastboot ROM, not recovery ROM) with MiFlash tool.
edit: If you are not in edl mode, try to enter fastboot and put this code "fastboot oem edl" to enter edl mode.
Click to expand...
Click to collapse
Everytime I flash With MIFLASH Tool i end up with this
I have tried this methods on fastboot rom version 9.5.17, 9.5.14 and global beta 8.7.12
but nothing works results are same
huttui said:
Everytime I flash With MIFLASH Tool i end up with this
I have tried this methods on fastboot rom version 9.5.17, 9.5.14 and global beta 8.7.12
but nothing works results are same
Click to expand...
Click to collapse
Never faced something like that so i looked at google and found some solutions.
1. Try to use test point, flash the ROM.
2. Unplug the battery and charge it with wall charger to get some juices, then plug it again, enter edl, then flash the ROM.
3. Just unplug the battery, enter edl mode, flash the ROM.
4. The worst solution and also the last, take it to the service center, hope they could help you fix your device.
I still have to wait 10 days to unlock bootloader, so i have not tried to enter edl mode with this Whyred yet. Don't know if the edl mode even works in Whyred.
edit:
5. Try to use beta version of MiFlash, because i have tried to unlock bootloader before, the newest version cannot detect my phone, so i used the old one.
6. Use the 64 bit version of windows.
huttui said:
Hi I was on Pixel Experience ROM then I flashed MIUI 9.5.17 via Recovery TWRP 3.2.2.0 with clean flash (i.e. dalvik cache, data, system and internal storage wiped)
but Now mobile is dead its not even turning on. What should I do please help
Click to expand...
Click to collapse
Hii...bro am in exact same situation right now. Did u solve it? Did u find any method to do?
What version of miui you had installed before pixel?
have you flashed any beta versions after 8.7.5 like 8.7.12, 8.7.26, 8.8.2 etc? If yes, then your device has triggered anti rollback and can only be resurrected using authorized mi account or change of motherboard.
EDL mode is disabled in whyred through fastboot command. You'll have to proceed with test point method to enable edl (I've seen in many threads which points to only test point method for edl) and then flash the rom which was there before you flashed PE.
Or, you should take help from service center.
If you can remember ARB3 before PE, then 9.5.17 will work but if you are not sure (like miui used to download the 9.5.19 rom automatically in wifi and a single reboot will upgrade you to ARB4 without your consent and then you wouldn't know it before it's too late and to avoid that, revoking updater authorization in the settings would be the only way to disable downloading ota in wifi ) , then you should flash 9.5.19 otherwise downgrade arb will brick your phone. Also, it s not clear whether you have bricked it while flashing 9.5.17 after PE which was a common reason when people downgraded from 9.5.19 to 9.5.17.
animeshsahood6 said:
Hii...bro am in exact same situation right now. Did u solve it? Did u find any method to do?
Click to expand...
Click to collapse
You have bricked your device by downgrading from arb4 to arb3. go to mi service center to get your mother board replaced as soon as possible..
epicwarlock said:
You have bricked your device by downgrading from arb4 to arb3. go to mi service center to get your mother board replaced as soon as possible..
Click to expand...
Click to collapse
Its covered under warranty r8?
animeshsahood6 said:
Its covered under warranty r8?
Click to expand...
Click to collapse
If you go to xiaomi authorised service centre then it is covered under warranty..
Lucky
animeshsahood6 said:
Hii...bro am in exact same situation right now. Did u solve it? Did u find any method to do?
Click to expand...
Click to collapse
Luckily for me mi service centre replaced the board for free as it was in warranty. try your luck. i told them it stuck during miui10 update.
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
NickDeveloper said:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
Click to expand...
Click to collapse
So, we don't know when will be fixed
NickDeveloper said:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
Click to expand...
Click to collapse
But you can use the OTG touch twrp
Arobase40 said:
I experimented this no touch TWRP but it is mostly buggy excluding the non touch issue there is a bigger issue which is that once installed you can't get out from it as it bootloops into this recovery mode. Flashing a stock recovery won't change anything.
You will have to totally restock your phone from scratch and then re root it and restore all your apps and data !!! ^^
I found out the twrp tree for A52 4G and was able to build a TWRP but obviously I can't test it.
I'm not able to build a twrp for A52S 5G for now as there are missing many kernel modules and other stuffs so I have to build them from kernel source code. So for now I'm working on the device and vendor config files...
Click to expand...
Click to collapse
But how can I fix my phone if I get a bootloop?
Arobase40 said:
You can't that is why I don't recommend you to use this no touch TWRP !
I was told to use a multidisabler but doesn't seem to work...
Click to expand...
Click to collapse
But it is only a soft brick, there is no need to change the motherboard. Would there be a way to reinstall stock firmware with Odin?
Arobase40 said:
I didn't say it will break your motherboard but if you want to waste your time in restocking your phone it's up to you.
Click to expand...
Click to collapse
Can I reinstall stock firmware with Odin? Will it work?
NickDeveloper said:
Can I reinstall stock firmware with Odin? Will it work?
Click to expand...
Click to collapse
Yes.
Arobase40 said:
As I said if you want to waste your time, YES you can reinstall stock firmware but of course you will lose your no touch twrp...
You will have to choose one or the other but not both...
Click to expand...
Click to collapse
Unfortunately, I have tried to reinstall stock firmware, but it failed. Looks like my bootloader became locked. Odin software showed "FAIL". There was a message that I could barely read, so that was the reason it failed to reinstall the firmware.
What should I do now?
Arobase40 said:
You can't that is why I don't recommend you to use this no touch TWRP !
I was told to use a multidisabler but doesn't seem to work...
Click to expand...
Click to collapse
So you got stuck in a bootloop after installing twrp. Have you tried just extracting the stock boot.img from firmware AP file and flashing it with odin? I really don't get it why you had to reinstall everything to stock. It's not necessary to reflash every partition if you only messed up one
Arm1nas said:
So you got stuck in a bootloop after installing twrp. Have you tried just extracting the stock boot.img from firmware AP file and flashing it with odin? I really don't get it why you had to reinstall everything to stock. It's not necessary to reflash every partition if you only messed up one
Click to expand...
Click to collapse
Nope, I did not make the backup of anything. Unfortunately, my bootloader is now locked and I cannot reinstall stock firmware. What now??
NickDeveloper said:
Nope, I did not make the backup of anything. Unfortunately, my bootloader is now locked and I cannot reinstall stock firmware. What now??
Click to expand...
Click to collapse
While the phone is completely off, press vol up and vol down buttons at the same time and then plug in the usb cable to the computer. I had that happen too, when the device fails to boot it automatically puts you into download mode and it says that the OEM LOCK is on. You just have to reboot to download mode manually.
Arm1nas said:
While the phone is completely off, press vol up and vol down buttons at the same time and then plug in the usb cable to the computer. I had that happen too, when the device fails to boot it automatically puts you into download mode and it says that the OEM LOCK is on. You just have to reboot to download mode manually.
Click to expand...
Click to collapse
But how can I reinstall stock firmware when the OEM is locked? I tried to reinstall with all required binaries, including HOME_CSC and it showed "FAIL".
NickDeveloper said:
But how can I reinstall stock firmware when the OEM is locked? I tried to reinstall with all required binaries, including HOME_CSC and it showed "FAIL".
Click to expand...
Click to collapse
You don't need to unlock bootloader to flash stock fw with Odin.
Your problem is most likely related to something else.
Where did you download your fw?
Have you tried different cables?
What Odin version are you trying?
ShaDisNX255 said:
You don't need to unlock bootloader to flash stock fw with Odin.
Your problem is most likely related to something else.
Where did you download your fw?
Have you tried different cables?
What Odin version are you trying?
Click to expand...
Click to collapse
I don't understand why would it be possible to flash stock firmware with locked bootloader, I thought that locked bootloader won't allow the OS to be reinstalled.
NickDeveloper said:
I don't understand why would it be possible to flash stock firmware with locked bootloader, I thought that locked bootloader won't allow the OS to be reinstalled.
Click to expand...
Click to collapse
A Locked bootloader will prevent you from installing any custom things, like recovery or custom roms. It will allow you to install stock firmware via odin. Use Odin 3.14 to install firmware downloaded from here. Use the AP, Bl, Cp, and CSC_OXM files. That will get you started from scratch, all previous data and stuff will be deleted.