Hey guyz! I m new here and I hope someone will really help me here...
I was using Xiaomi Redmi 6A and recently i unlocked bootloader using official mi tool.
Now I flashed official twrp using adb and it flashed successfully but it was showing "internal storage 0mb" and whenever i perform any task in it, it shows 'failed to mount "/data" (invalid argument)'. So I searched for new Twrp and I found one somewhere and downloaded it and flashed it in my redmi 6a using prev. twrp and when i clicked reboot into recovery, my phone just turned off and after a second started vibrating and nither turn into recovery nor in Fastboot....
Please help me how to recover it... :crying:
Did you created a backup?, If yes then you can search on google on how to restore backups
If not, check if your phone os soft bricked or hard bricked. Both of them are DIFFERENT.
Soft brick is when your phone is bootlooping or stuck at fastboot mode, bootlooping is where you booted to the OS but it keeps looping at the boot animation. Stuck at fastboot on the other hand is where you can't boot to the OS and you're stuck at the Redmi logo and after a while it will boot to fastboot mode.
Hard brick is when your phone literally can't turn on, like you can't see the the boot animation or even the Redmi logo and you just can see the screen is on with just a black empty screen with nothing on it.
You can recover from soft brick by wiping the cache and Dalvik. Wiping and formatting the data also can help you to recover from a soft brick. Doing a dirty flash can sometime solve a soft brick (if you use a custom ROM)
If you diagnosed your phone with a hard brick then your only choice is to flash the stock firmware with XiaomiFlashTool or take your phone to the nearest service center (i hope not this option because with the virus and stuff). If you flashed your stock firmware and your phone managed to turn on but it's showing a white and gray error, that means that you flashed the wrong firmware.
---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------
Also what's perv TWRP?, i never heard of that before. I recommend you flash TWRP the normal way with ADB or flash the zip file with a custom recovery you currently have
I think you flashed a wrong TWRP. I did the same. If you cannot enter fastboot any more there is no chance. Only a specialist can help you.
kharuba said:
I think you flashed a wrong TWRP. I did the same. If you cannot enter fastboot any more there is no chance. Only a specialist can help you.
Click to expand...
Click to collapse
Actually you can flash the stock firmware all by yourself
Dude if it's vibro brick then you can't do anything, just visit service center or find a guy with Mi Authorized Account.
PS: SP Flash Tool doesn't work without Mi Authorized account
Don'tNoticeMe said:
Did you created a backup?, If yes then you can search on google on how to restore backups
If not, check if your phone os soft bricked or hard bricked. Both of them are DIFFERENT.
Soft brick is when your phone is bootlooping or stuck at fastboot mode, bootlooping is where you booted to the OS but it keeps looping at the boot animation. Stuck at fastboot on the other hand is where you can't boot to the OS and you're stuck at the Redmi logo and after a while it will boot to fastboot mode.
Hard brick is when your phone literally can't turn on, like you can't see the the boot animation or even the Redmi logo and you just can see the screen is on with just a black empty screen with nothing on it.
You can recover from soft brick by wiping the cache and Dalvik. Wiping and formatting the data also can help you to recover from a soft brick. Doing a dirty flash can sometime solve a soft brick (if you use a custom ROM)
If you diagnosed your phone with a hard brick then your only choice is to flash the stock firmware with XiaomiFlashTool or take your phone to the nearest service center (i hope not this option because with the virus and stuff). If you flashed your stock firmware and your phone managed to turn on but it's showing a white and gray error, that means that you flashed the wrong firmware.
---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------
Also what's perv TWRP?, i never heard of that before. I recommend you flash TWRP the normal way with ADB or flash the zip file with a custom recovery you currently have
Click to expand...
Click to collapse
Not perv, it's prev (previous). The first twrp..
ovilone said:
Not perv, it's prev (previous). The first twrp..
Click to expand...
Click to collapse
Oh.., prev(previous) twrp. Then there's probably a mistake in that script. Did you use an official twrp zip or an unofficial one?
Don'tNoticeMe said:
Did you created a backup?, If yes then you can search on google on how to restore backups
If not, check if your phone os soft bricked or hard bricked. Both of them are DIFFERENT.
Soft brick is when your phone is bootlooping or stuck at fastboot mode, bootlooping is where you booted to the OS but it keeps looping at the boot animation. Stuck at fastboot on the other hand is where you can't boot to the OS and you're stuck at the Redmi logo and after a while it will boot to fastboot mode.
Hard brick is when your phone literally can't turn on, like you can't see the the boot animation or even the Redmi logo and you just can see the screen is on with just a black empty screen with nothing on it.
You can recover from soft brick by wiping the cache and Dalvik. Wiping and formatting the data also can help you to recover from a soft brick. Doing a dirty flash can sometime solve a soft brick (if you use a custom ROM)
If you diagnosed your phone with a hard brick then your only choice is to flash the stock firmware with XiaomiFlashTool or take your phone to the nearest service center (i hope not this option because with the virus and stuff). If you flashed your stock firmware and your phone managed to turn on but it's showing a white and gray error, that means that you flashed the wrong firmware.
---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------
Also what's perv TWRP?, i never heard of that before. I recommend you flash TWRP the normal way with ADB or flash the zip file with a custom recovery you currently have
Click to expand...
Click to collapse
Don'tNoticeMe said:
Oh.., prev(previous) twrp. Then there's probably a mistake in that script. Did you use an official twrp zip or an unofficial one?
Click to expand...
Click to collapse
The first (prev) was official. But the second one was unofficial.
Related
Sorry if this is in the wrong thread, not sure where to put it,
I own a NATPC M009s x2.
I rooted it today and was hoping to install the cwm.
I had to install the driver manually so i tried to install it through the recovery mode
However after I did this the device wouldnt boot up past the boot logo and im not too sure what to do.
Unfortunately this is a soft bricked device now. You can either try to use ADB to attempt rebooting into recovery.
EDIT: If you do not have cwm successfully flashed, (this is based off of previous experience) there is no way to fix this. Please correct me if I am wrong, I rooted my first phone and factory reset it through the stock rom without a recovery. Sent the phone into a boot loop. I did write a program (Mango Tools) to help fix this however, it can be found on mellowdev.net It is being updated atm but wouldnt mind emailing it to you if you PM me.
Sent from my Nexus 4 using xda premium
I've just unlocked the bootload and flashed TWRP on to my moto G4 plus and went to flash magisk after to get root. After i flashed it I rebooted my phone but it wouldn't boot into the system and wouldn't even show the boot animation. I tried to use the Stock recovery I made after putting TWRP on my phone but it kept on saying error 255. This lead me to sideload lineage OS onto the phone which work. However when I tried to boot into android it did the same thing again. I have a feeling that something is wrong with the /boot partition as when i go to recover using my stock img there is only a system box.
Any help is appreciated
Welcome to XDA,
and did you try reflashing stock firmware?
That will always work.
Hello there. I'm having a major issue with flashing magisk right now. So all was fine. Then today, I flashed OxygenOS open beta 19 on my OnePlus 5T. I then tried flashing Magisk. What's really weird is it boots, but as soon as it does, I get a split second of enter pin, before my phone just says shutting down before it does just that. I've tried the uninstaller then reinstalling it with no luck. I'd really like to stay rooted without wiping data, but I can live without root. Does anyone know how I could fix this problem? Thanks so much in advance.
---------- Post added at 09:12 PM ---------- Previous post was at 09:10 PM ----------
Oh very sorry, I mean open beta 29.
i was restoring an twrp and rom that i backed up while attempting to root my phone and installing another stock rom, i was unable to install the this rom and so i tried to restore the previous files using twrp, now my phone is stuck in a bootloop (stuck with the space having just the android logo)with me unable to access the recovery or the phone in any other way. i am also unable to initialize a soft or hard reset.
i am pretty new to this and do not know what to do further.
i did what was referred to me on the link given below
https://forum.xda-developers.com/nokia-1/development/unlocking-rooting-nokia-1-stock-rom-t3832230
and things went wrong trying to install this rom
https://forum.xda-developers.com/nokia-1/development/rom-ta-1060-stock-oreo-8-1-t3809578
Please kindly let me know how i can fix this problem
Thank you
My nexus is having issues i tried rooting it it worked but i dowloaded this app called flashfire i wanted to flash something but when i tapped on flash it wiped my device and now it wont boot up it will turn on but gets stuck on the google logo which is when you first turn it on i can acces the bootloader but thats it i tried recovery by wipping everything again i think its called boot loop not sure please help.
Jean Santiago said:
My nexus is having issues i tried rooting it it worked but i dowloaded this app called flashfire i wanted to flash something but when i tapped on flash it wiped my device and now it wont boot up it will turn on but gets stuck on the google logo which is when you first turn it on i can acces the bootloader but thats it i tried recovery by wipping everything again i think its called boot loop not sure please help.
Click to expand...
Click to collapse
Re flash the stock firmware with fastboot.
Flashfire doesn't wipe anything unless you tell it to. Besides chainfire ended support and use of flashfire so don't use it.
Use fastboot to flash.
Go into fastboot and just run the flash-all.sh script and for the desired stock firmware.
So I recently tried to unroot my device with flashing official ROM on it. Apparently I used the wrong file because my phone got bricked. I tried using XiaoMiTool by Francesco but it didn't help. I spent a lot of time trying to fix it so ill post what worked for me. I downloaded a lot of ROMS but none of them worked for me there was either flash error or device mismatching and I couldn't find right flash official software anywhere. I downloaded another ADB fixing program which worked, I downloaded Szaki/XiaomiADB fastboot tools which worked perfectly. I simply connected my phone searched for my phone code name (tucana) downloaded ROM from there, wiped all data off and finally flashed OS on my device. I also have a question, are there any android software fixing programs for phone repair companies or something similar?
Have good day and stay healthy,
MX8MC8
id suggest to unbrick with mi flash tool.
I did that always when i was stuck on something, it ofcourse removes your data but saves the device so its still the profit probably... After succesfull rom installation you can flash again.
Also you do this in fastboot mode
When I was stuck in the same way the solution I found was to flash whatever rom then when the phone bootloops, go into recovery, and format data. Afterwards it will boot to startup screen and take forever to load up. Anyway that is my solution, before that I would have to flash stock recovery to boot for the first time then flash a custom recovery back.