Related
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
EDIT: Sorry, I post on the wrong section. If someone can move this post on the right section ...
gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
try to use QPST (Qfil) method. This is final method can bring back your phone. If fail, congratulation ! :silly:
I success with QFIL Zui works but it's awful
Unfortunately, I try to install stock cos but I have the same issue.... Bootloop after "App update message".
I don't know why
Try flashing Cyanogen Os using fastboot
I did that...
I flash with the tool via fastboot. But bootloop result...
I also tried to flash CM13 via TWRP but I have an error message...
Do you have any other solutions?
I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice
Here u go, QFIL CM 12 ROM: https://mega.nz/#!RFUw2CbZ!GXS6KeOy_8n2y_rOBJUS5WJSP5kchODcGUF0U1TxYO8
So with the ham version is the same as the QFIL version?
gaara19 said:
I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice
Click to expand...
Click to collapse
READ THIS( use google translate)
BTW, what are the fastboot commands that you are using?
Hi, i have tried to remove my root and unlocked bootloader as I didnt think they were correctly installed in the first place. Also I wanted to install a new oem update that it keep reminding me of in the background. So now after doing alot of things found in forums and youtube I have come to an end point were the phone just comes to the bootscreen, "your devise has been unlocked and cant be trusted." from here it is just stuck with the "your devise is now booting..." then nothing happens so I realy need help now, otherwise I will have to buy a new phone within the next days.. I cant still get into the twrp and format/wipe data etc, so is it something in here I need to fix then?
Anyone that can please help me out a bit?
Regards Kristoffer
I'm having the same issue. I am unable to flash a custom rom or an official rom. One issue I am having is that I can not relock the bootloader as I get an command not allowed. Please can someone help with this issue.
Thanks
Sent from my SM-G928F using Tapatalk
I have the same issue try to flash stock ROM 182 and latter or directly 132, is important to flash 132 BCS is the only really complete rom
Luigi Ra said:
I have the same issue try to flash stock ROM 182 and latter or directly 132, is important to flash 132 BCS is the only really complete rom
Click to expand...
Click to collapse
But I cant get into the twrp anymore, only the fastboot and recue mode and the huawei erecovery mode, and in this the wifi just gives me failed to download the package or something like that.... ://
I managed to get in recovery by running the oem unlock. The problem I have is that I am unable to lock the bootloader again.
I really want to get the phone working again. I don't want to have to send the device to a Huawei Service Centre since the bootloader has been unlocked.
I really hope someone can help us all get the device back to stock firmware.
Thanks
How did you get to the recovery mode? I cant get to the twrp anymore, i think i did something wrong and wiped data or formated it so now i can only se bootup screen, or huawei logo or get to fastboot and rescue mode. There it says phone unlocked and frp (or something) in green letters lock....? And also the huawei erecovery which i cant do anything in...
I run fastboot oem unlock and flashed twrp using fastboot.
I have managed to flash update.app, Default_hw.app, Default_normal.app and Default_eu.app using an app called DC Phoenix, but now when the phone boots it goes in to eRecovery and the touchscreen doesn't work. Even when I flash twrp again the touchscreen still doesn't work.
Please can someone advise what to do to get the touchscreen and the other phone back to normal.
Thanks
Were i find a link for step by step rooting my huawei p9 lite. I have company from amateurs pretty good ones. So i cant make mistakes. Thnx for the help...rock the world wild and free whopppaaa
Hi ,
I have an ASUS ROG2 and I'm experiencing quite a problem here , I would like to know if this can still be rescue or not? or maybe I'm missing some steps here. here's what I've done so far.
Before it got to this dilemma my phone is suffering from autoshutdown so i rooted my phone using magisk and applied the thermal mode by one of the OP here. everything is working fine , the phone is not shutting down until today. it suddenly restart before me and it is stuck in ROG Logo.
what I've done.
1) i flash the stock boot img for my firmware version 2009.49 using fastboot flash boot 2009.49stock.img both slot A & B then followed by fastboot reboot so it can boot to system but it is still stock at the ROG Logo
2) i downloaded a RAW Firmware of 2009.49 , put my phone into fastboot mode. i made sure it was detected by the PC using the command fastboot devices and surely it was. i execute the flashall_AFT.cmd and waited , after it finishes my phone reboots but still stuck at the ROG Logo and here's the problem.
I reboot my phone into bootloader , scroll to Recovery after pressing Power button to select it , it boots and stuck at the ROG Logo at this point i'm confused since i need to factory reset it. so i downloaded TWRP for ROG2 Android 10 the one i usually use then i tried to boot from it using fastboot boot twrp10.img , it only boots and stuck at the ROG Logo again
3) I tried to flash a firmware using EDL mode , everything went well without any errors and there's the success message in Xiaomiflashtool , i reboot the phone to recovery and it is still stuck in ROG Logo.
any guesses? I'm kinda lost here since both RAW and EDL are not working.
KnowThyPro said:
Hi ,
I have an ASUS ROG2 and I'm experiencing quite a problem here , I would like to know if this can still be rescue or not? or maybe I'm missing some steps here. here's what I've done so far.
Before it got to this dilemma my phone is suffering from autoshutdown so i rooted my phone using magisk and applied the thermal mode by one of the OP here. everything is working fine , the phone is not shutting down until today. it suddenly restart before me and it is stuck in ROG Logo.
what I've done.
1) i flash the stock boot img for my firmware version 2009.49 using fastboot flash boot 2009.49stock.img both slot A & B then followed by fastboot reboot so it can boot to system but it is still stock at the ROG Logo
2) i downloaded a RAW Firmware of 2009.49 , put my phone into fastboot mode. i made sure it was detected by the PC using the command fastboot devices and surely it was. i execute the flashall_AFT.cmd and waited , after it finishes my phone reboots but still stuck at the ROG Logo and here's the problem.
I reboot my phone into bootloader , scroll to Recovery after pressing Power button to select it , it boots and stuck at the ROG Logo at this point i'm confused since i need to factory reset it. so i downloaded TWRP for ROG2 Android 10 the one i usually use then i tried to boot from it using fastboot boot twrp10.img , it only boots and stuck at the ROG Logo again
3) I tried to flash a firmware using EDL mode , everything went well without any errors and there's the success message in Xiaomiflashtool , i reboot the phone to recovery and it is still stuck in ROG Logo.
any guesses? I'm kinda lost here since both RAW and EDL are not working.
Click to expand...
Click to collapse
You could try booting into TWRP 3.4.0-0 Q Unofficial by mauronofrio without flashing ( fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img ) , then copy the zip over to root of internal storage, either 2009.49 or lastest 2012.65, from here. Be sure to check during flash which slot gets flashed first. Then repeat the process, booting twrp so that you can flash the other inactive slot. If you want to be sure you have changed slots, click on reboot in twrp and see which is active before flashing. Good luck
Hopefully flashing both slots successfully will do it. Let us know how you get on.
reg66 said:
You could try booting into TWRP 3.4.0-0 Q Unofficial by mauronofrio without flashing ( fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img ) , then copy the zip over to root of internal storage, either 2009.49 or lastest 2012.65, from here. Be sure to check during flash which slot gets flashed first. Then repeat the process, booting twrp so that you can flash the other inactive slot. If you want to be sure you have changed slots, click on reboot in twrp and see which is active before flashing. Good luck
Hopefully flashing both slots successfully will do it. Let us know how you get on.
Click to expand...
Click to collapse
Hi Reg !
Thanks for replying , i think I'm using the official version of TWRP so I'll give this a try , i should overcome the obstacle of booting into TWRP..
I'll let you know the outcome.
KnowThyPro said:
Hi Reg !
Thanks for replying , i think I'm using the official version of TWRP so I'll give this a try , i should overcome the obstacle of booting into TWRP..
I'll let you know the outcome.
Click to expand...
Click to collapse
Any news?
reg66 said:
Any news?
Click to expand...
Click to collapse
I used the TWRP you've linked. and i'm afraid that it is stuck on the rog logo again..
what i've done. ' fastboot boot twrpQ3400.img ' after i sent that command , the phone reboots and instead of going to twrp , it goes to rog logo and stuck there.
is there anyway i could check if there's partition? it feels like the phone has no partition that's why it is always going back to the rog logo.
KnowThyPro said:
I used the TWRP you've linked. and i'm afraid that it is stuck on the rog logo again..
what i've done. ' fastboot boot twrpQ3400.img ' after i sent that command , the phone reboots and instead of going to twrp , it goes to rog logo and stuck there.
is there anyway i could check if there's partition? it feels like the phone has no partition that's why it is always going back to the rog logo.
Click to expand...
Click to collapse
Did you change the name of the twrp file? the fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img cmd must have an identical name to the file, which as the original should be twrp-3.4.0-0-I001D-Q-mauronofrio.img
and just to be sure, you have the twrp img in fastboot folder, correct?
reg66 said:
Did you change the name of the twrp file? the fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img cmd must have an identical name to the file, which as the original should be twrp-3.4.0-0-I001D-Q-mauronofrio.img
and just to be sure, you have the twrp img in fastboot folder, correct?
Click to expand...
Click to collapse
Yes i did rename it as twrpQ3400.img and yes also , it is in the same folder as my adb & fastboot folder enviroment.
i'll try a different approach maybe using QFIL? although i don't know where to start like finding the XML / Programmer or firehose..
any ideas?
KnowThyPro said:
Yes i did rename it as twrpQ3400.img and yes also , it is in the same folder as my adb & fastboot folder enviroment.
i'll try a different approach maybe using QFIL? although i don't know where to start like finding the XML / Programmer or firehose..
any ideas?
Click to expand...
Click to collapse
Well i'm running out of ideas, never used QFIL so wouldn't know. since you cannot boot into twrp (i'm assuming you didn't relock bootloader? twrp won't work with locked bootloader), you could try this thread. be sure to use the supplied 1910.35 images as it tried and tested. read posts 1 and 2 at the very least, post 2 has useful steps
if successful, you'll then need to update 1910.64 before android 10 2004.60 to start with, then up to latest
reg66 said:
Well i'm running out of ideas, never used QFIL so wouldn't know. since you cannot boot into twrp (i'm assuming you didn't relock bootloader? twrp won't work with locked bootloader), you could try this thread. be sure to use the supplied 1910.35 images as it tried and tested. read posts 1 and 2 at the very least, post 2 has useful steps
if successful, you'll then need to update 1910.64 before android 10 2004.60 to start with, then up to latest
Click to expand...
Click to collapse
yes , i didn't lock my bootloader since i can still see the bootloader unlock message.. i'm also running low in ideas , for worst it is a bricked phone at best. i'll check the link.
thanks for helping. i'll still update this thread to maybe update u as well.
edit: i checked the link , i already did the xiaomi flash tool approach on the link.. everything was a success with no errors... maybe i shud give qpst tool a try? although i'm not familiar using it.
KnowThyPro said:
yes , i didn't lock my bootloader since i can still see the bootloader unlock message.. i'm also running low in ideas , for worst it is a bricked phone at best. i'll check the link.
thanks for helping. i'll still update this thread to maybe update u as well.
edit: i checked the link , i already did the xiaomi flash tool approach on the link.. everything was a success with no errors... maybe i shud give qpst tool a try? although i'm not familiar using it.
Click to expand...
Click to collapse
did you remember to shut the phone down after successfully flashing, boot into recovery and wipe data, then reboot? as per the instructions...?
reg66 said:
did you remember to shut the phone down after successfully flashing, boot into recovery and wipe data, then reboot? as per the instructions...?
Click to expand...
Click to collapse
yes , ofcourse since the phone is in EDL mode the only way to shut it down is by using Power + volume up + volume down like around 15 seconds then phone will shutdown since the 9008 COM in device manager will be gone this means that it's no longer in EDL mode. i wait like 1minute before i power it up to recovery by power + volume down then scroll to recovery in bootloader. then with no luck still stuck to Rog logo..
it's like the recovery partition is gone...
KnowThyPro said:
yes , ofcourse since the phone is in EDL mode the only way to shut it down is by using Power + volume up + volume down like around 15 seconds then phone will shutdown since the 9008 COM in device manager will be gone this means that it's no longer in EDL mode. i wait like 1minute before i power it up to recovery by power + volume down then scroll to recovery in bootloader. then with no luck still stuck to Rog logo..
it's like the recovery partition is gone...
Click to expand...
Click to collapse
I've been googling for you dude but no joy yet.... will have another look tomorrow
reg66 said:
I've been googling for you dude but no joy yet.... will have another look tomorrow
Click to expand...
Click to collapse
Thanks man , i'm searching for the qfil approach but i'm getting a sahara error. currently searching for fixes
edit : i manage to boot the phone using the link you've provided by using QFIL approach and not thru XiaomiFlashTool
the phone boots successfully and i can use the recovery again ! although there's a problem , it can't read my sim card and everything is like stock android without any skins or what.. i used the RAW firmware to update it but the problem with stuck logo is back :/
gonna re-flash using QFIL and i'll check some more ~ maybe use TWRP and flash the firmware there no?
edit: the one from the link is not working , stuck at rog logo.. but the one from the internet i was able to boot to system but can't detect simcard , also when plugging to PC it will go to crashdump mode.
also can't flash TWRP will result in stuck at ROG logo :/
was able to boot the phone but can't connect to wifi and is locked by google frp :/ any guides i can follow to remove that FRP without wifi connection ?
Sorry bud, really not sure what's going on with your phone or know much more. Good luck with it tho
KnowThyPro said:
was able to boot the phone but can't connect to wifi and is locked by google frp :/ any guides i can follow to remove that FRP without wifi connection ?
Click to expand...
Click to collapse
Actually, if you now have recovery, what about booting into twrp and flashing lastest 2012.65 zip from asus website, twice - both slots. see if that fixes your wifi issue
As you said using the QFIL approach worked to boot into system and recovery is back - boot to twrp from that state
KnowThyPro said:
Thanks man , i'm searching for the qfil approach but i'm getting a sahara error. currently searching for fixes
edit : i manage to boot the phone using the link you've provided by using QFIL approach and not thru XiaomiFlashTool
the phone boots successfully and i can use the recovery again ! although there's a problem , it can't read my sim card and everything is like stock android without any skins or what.. i used the RAW firmware to update it but the problem with stuck logo is back :/
gonna re-flash using QFIL and i'll check some more ~ maybe use TWRP and flash the firmware there no?
edit: the one from the link is not working , stuck at rog logo.. but the one from the internet i was able to boot to system but can't detect simcard , also when plugging to PC it will go to crashdump mode.
also can't flash TWRP will result in stuck at ROG logo :/
Click to expand...
Click to collapse
I think my i messed my phone like yours. Can you provide me step by step? I have tried those step one by one but still stuck at rog logo
Hey i spend today a lot of time to tried to fix my bricked Redmi Note 10 5G.
I just wanted to unroot my phone but i did something wrong.
First problem i have is the dm-verity corrupt.
So i read and tried this
https://forum.xda-developers.com/t/...g-bricked-but-has-access-to-fastboot.4366655/
Without succes i flashed the right firmware for my device many times but the dm-verity corrupt is still there and then i keeps hanging in the redmi boot logo.
But i dont know how but now i also got my bootloader locked so now i cant flash any thing.
And the dm-verity corrupt and keeps hanging on the redmi bootlogo.
So i hope some one have an solution for me and can help me and fix my phone.
u have made a common mistake. u have flashed firmware with miglash, without change default option to flash all. you have select flash all and lock. so yout phone is hard bricked. i think theres a guide to solve this. search on this forum
wetito said:
u have made a common mistake. u have flashed firmware with miglash, without change default option to flash all. you have select flash all and lock. so yout phone is hard bricked. i think theres a guide to solve this. search on this forum
Click to expand...
Click to collapse
Hey thanks for the reply
i know i made a mistake and i search and tried anything what i thougt it is maybe a solution on this forum.
Bun without any succes and because my bootloader is locked now i cant do anything in the fastboot.
i dont know how to unlocked now.
Because the bootloader is locked now i think i have the Guarantee now but if the i boot the phone the dm-verity corrupt message is still there and then it keeps hangin on the redmi logo.
So if there is no way to fix it i think go trie it to bring it to the store where i bought it 2 months ago.
i think you can solve using mtk spflash tool
look here, u can find the solution
Soft Bricked Phone
Hello, I need help. I tried to flash back to stock firmware using mi flash tool but it said error and it failed. I tried to flash again and then it didn't detect the device. It rebooted on its own and now it's stuck on bootloop with black...
forum.xda-developers.com
Hey thanks for the
wetito said:
i think you can solve using mtk spflash tool
look here, u can find the solution
Soft Bricked Phone
Hello, I need help. I tried to flash back to stock firmware using mi flash tool but it said error and it failed. I tried to flash again and then it didn't detect the device. It rebooted on its own and now it's stuck on bootloop with black...
forum.xda-developers.com
Click to expand...
Click to collapse
Hey thnks gor this guide but i cant get it found it in the sp flash tool.
I dont get my phone in the BRom mode to find it so im stuck there tried servel of times when it power of to get my phone BRom mode how dos the screen look if its in BRom mode ?
By pressing the vol + vol - and pwr button when its off id ont get it in the BRom Mode.
Also i googled the sp flash tool to download it so maybe i dont have tight one do you have mabe some links for me?
Or is there maybe a other way to fix my phone?
try this tool. seems very good. but i didn't never used. so you had to try by yourself. it have many interesting and usefull function
Home - Tool All In One
TOOL ALL IN ONE This tool support 67 different devices of some different OEMs. DOWNLOAD CHANGELOG XDA THREAD OTHERS PROJECTS
toolaio.tk
wetito said:
try this tool. seems very good. but i didn't never used. so you had to try by yourself. it have many interesting and usefull function
Home - Tool All In One
TOOL ALL IN ONE This tool support 67 different devices of some different OEMs. DOWNLOAD CHANGELOG XDA THREAD OTHERS PROJECTS
toolaio.tk
Click to expand...
Click to collapse
That also didn't work do i go to reseller today and hope i hot a new one of the gonna fix it.
Becuase the bootloader is locked again warrenty only the dm-verification message is there.
Do gonna say i updated my phone and now its not booting anymore.
Or do you or maybe some one do have an tutorial program or tool to fix it.
Download ROM for your phone and extract to desktop. Reboot to fastboot and open flashall.bat. it should run firmware through and reflash phone completely. Boot phone and on boot screen keep pressing power so phone can boot and bypass DM Verity error. Once booted reboot into fastboot again and enter fastboot oem cdms. Reboot phone and DM Verity should be gone.
passion8059 said:
Download ROM for your phone and extract to desktop. Reboot to fastboot and open flashall.bat. it should run firmware through and reflash phone completely. Boot phone and on boot screen keep pressing power so phone can boot and bypass DM Verity error. Once booted reboot into fastboot again and enter fastboot oem cdms. Reboot phone and DM Verity should be gone.
Click to expand...
Click to collapse
we repeats same anawers continuosly.i dont understand why some users decide to mod their devices, if they dont know how to use Google, and don't understand how to follow the flashing guides step by step. and finally after flashing custom rom, they ask how back to stock
wetito said:
we repeats same anawers continuosly.i dont understand why some users decide to mod their devices, if they dont know how to use Google, and don't understand how to follow the flashing guides step by step. and finally after flashing custom rom, they ask how back to stock
Click to expand...
Click to collapse
Get what you are saying, think there is at least 8 threads on same topic.
Hey thanks for the answers and the things i could tried to fix my phone.
im not a noob with rooting and flashing android phones before i do flasshong or rooting and the other stuff i always read and check the xda forum before i do.
With other android phones that i had before i made some misstakes before but like a bootloop or something else that the phone not was booting but always i can fix the phone.
So the problem what i had with my Redmi note 10 5G and not one solution that i found on xda or something that maube could fix the problem nothing could fix it.
So i a couple of week ago i went to the reseller and they send it to a repair center.
I think the coudnt also fix it because the did a boardswap.
I think if they cam fix it with a tool or software and reflashing the phone they did.
Now i wait some time before i go rooting or flashing stuff on my phone i hope there will be good twrp so thning go musch easier in the future to fix stuuf like (DM-VERITY Corruption.
twrp is not necessary. fix dm-verity is easy. the are MANY MANY MANY post where is explained how to do. root new phones is dofferent but not complicated. magisk works fine if installed following the latest guides. it's impossible damage mainbord after a root procedure. sure you didnt follow the guides with attention. i have rooted my global phone many times without problems. simply you have made a bad flash of vbmeta or product partition. you made a big mistake, cause this devices can be rooted without brick
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Andris85 said:
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Click to expand...
Click to collapse
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
gurtnyi said:
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Click to expand...
Click to collapse
Just the boot.ini. but I think this would make fastboot mode work. But it's not working
tutibreaker said:
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
Click to expand...
Click to collapse
What should I use to reflash? Mi flash? This is the NS
Yes... I probably mixed up the boot file in the downloads folder and not the correct received flash
Click to expand...
Click to collapse
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
gurtnyi said:
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
Click to expand...
Click to collapse
yepp, enable oem unlock. But fastbootmode is required for all operations. But fastboot mode doesn't work.
What do you mean it doesn't work?
Can't enter into fastboot mode?
gurtnyi said:
What do you mean it doesn't work?
Can't enter into fastboot mode?
Click to expand...
Click to collapse
Can't enter fastboot mode. The device only shows "Redmi" lettering. If fatboot worked, I could have done it already. power+volume down, the device just restarts and shows "redmi".
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
gurtnyi said:
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
Click to expand...
Click to collapse
it just restarts, as long as I press and hold volume down+power, if I don't press it, it just shows the redmi text
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
gurtnyi said:
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
Click to expand...
Click to collapse
TXH
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Pegelaar_NL said:
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Click to expand...
Click to collapse
Yep, this guy here 's got the point. If you can't flash with sp flash tool because auth fail, there's a method to bypass it.
You can find the tutorial here: https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
I also got some help from this guy's post, many thanks to him too.
https://forum.xda-developers.com/t/...ad_da_fail-0x7d4-2004-for-mtk-phones.3692259/
Let us know how it's going with it! ;D
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buytoday there is a lot of devices for gaming like rog phone and red magic
Click to expand...
Click to collapse
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Click to expand...
Click to collapse
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
tutibreaker said:
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Click to expand...
Click to collapse
If you can root it easily, then the expensive one is good for me! Normal root was not available for typical gamer phones for years. If I buy something for which root may not be available, then I'm wasting my money...
gurtnyi said:
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
Click to expand...
Click to collapse
I will look today