Related
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Spumpkin said:
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
Click to expand...
Click to collapse
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
renzo090513 said:
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
cm11 => jb bootloader
cm12, cm12.1 and cm13 => kk bootloader
klemenSLO said:
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Click to expand...
Click to collapse
The current version is 2.8.7.3. Should I try other versions?
Did you solve the issue? Or is it still not allowing you to get into your F/W?
staylecrate said:
Did you solve the issue? Or is it still not allowing you to get into your F/W?
Click to expand...
Click to collapse
Hi!
I tried to install TWRP version 2.6.6.3, but it fails to flash it so I'm stuck with the version 2.8.7.3. All I'm able to enter is just the recovery mode. I can't enter the download mode so I can't flash the stock firmware.
Currently I'm out of ideas. I can't flash any OS, the TWRP fails everytime and creates errors.
Try flash bumped kernel like lp dorimanx then flash bumped bootstak then lp rom like cloudy or stock. Or google this: lg g2 unbrickable now xda ...that work for me
Hi to all,
had root this device on 6.0.1 with TWRP. Now I needed a full reset due to a Bluetooth problem to check if its root/software related. BUT on my mistake I erased EVERYTHING through TWRP (Dalvik/ART Cahe,System,Data,Internal Storage,Cache, Micro SD, Android Secure, USB-OTG)
Tried to install custom rom Aospextended but I don't know the how to and I am lost in forums.. the phone doesn't boot... after zip file installation the screen fades to somewhat yellowish like LCD problem... I can still access TWRP..
p.s. I am an iPhone guy and just tried to fix this for my son... hope for your understanding for probably asking something very common..!
ANY HELP WOULD BE greatly appreciated even to get back to stock rom
Many thanks in advance!
gsp1 said:
Hi to all,
had root this device on 6.0.1 with TWRP. Now I needed a full reset due to a Bluetooth problem to check if its root/software related. BUT on my mistake I erased EVERYTHING through TWRP (Dalvik/ART Cahe,System,Data,Internal Storage,Cache, Micro SD, Android Secure, USB-OTG)
Tried to install custom rom Aospextended but I don't know the how to and I am lost in forums.. the phone doesn't boot... after zip file installation the screen fades to somewhat yellowish like LCD problem... I can still access TWRP..
p.s. I am an iPhone guy and just tried to fix this for my son... hope for your understanding for probably asking something very common..!
ANY HELP WOULD BE greatly appreciated even to get back to stock rom
Many thanks in advance!
Click to expand...
Click to collapse
Install a ROM with marshmellow firmware please don't post in this thread of j5 forum
hi, already posted by mistake at firmware section admins can delete that please...
having TOTALLY erased my SM-J500F/DS with TWRP I cannot put back anything...
ANY help on stock recovery, custom rom or anything would be greatly appreciated... I tried already one custom rom but I am not sure... just install the zip file? This procedure doesn't boot, restarts gets the logo and after this the screed gets yellowish like damaged!!!... again I have TWRP access thankfully...
please any help?
gsp1 said:
hi, already posted by mistake at firmware section admins can delete that please...
having TOTALLY erased my SM-J500F/DS with TWRP I cannot put back anything...
ANY help on stock recovery, custom rom or anything would be greatly appreciated... I tried already one custom rom but I am not sure... just install the zip file? This procedure doesn't boot, restarts gets the logo and after this the screed gets yellowish like damaged!!!... again I have TWRP access thankfully...
please any help?
Click to expand...
Click to collapse
You must go to section Samsung j5 2015 you will find all you need, since restoring to stock, rooting, installing the correct TWRP for your device....and more.
You NEED to READ because too much information for one post, but this is the correct place for you.
Pay attention the correct files TWRP for 601 because there are TWRP for lollipop devices, and when choosing ROMs you MUST downgrade your firmware to Lollipop, that's the reason for artifacts and greenish screen because of incompatibility of TWRP and there are ROMs that you can install with twrp601, others need booltloader and twrp lollipop. Hope you are nota blind anymore
Taivotat2 said:
You must go to section Samsung j5 2015 you will find all you need, since restoring to stock, rooting, installing the correct TWRP for your device....and more.
You NEED to READ because too much information for one post, but this is the correct place for you.
Click to expand...
Click to collapse
Many thanks! I will do it!
gsp1 said:
Hi to all,
had root this device on 6.0.1 with TWRP. Now I needed a full reset due to a Bluetooth problem to check if its root/software related. BUT on my mistake I erased EVERYTHING through TWRP (Dalvik/ART Cahe,System,Data,Internal Storage,Cache, Micro SD, Android Secure, USB-OTG)
Tried to install custom rom Aospextended but I don't know the how to and I am lost in forums.. the phone doesn't boot... after zip file installation the screen fades to somewhat yellowish like LCD problem... I can still access TWRP..
p.s. I am an iPhone guy and just tried to fix this for my son... hope for your understanding for probably asking something very common..!
ANY HELP WOULD BE greatly appreciated even to get back to stock rom
Many thanks in advance!
Click to expand...
Click to collapse
I had the same problem when flashing Lineage 14.1 on my phone (J500M), screen fadding with a green-yellowish color and no boot. That happened because I was trying to flash the custon Rom with the wrong base. I was using 6.0 before flashing and Lineage requires you start from 5.1.
All I need to do was search for my device on sammobile.com , get the right stock firmware and use Odin to flash the rom on my device. From there I was able to flash TWRP again and install Lineage correctly.
gsp1 said:
Hi to all,
had root this device on 6.0.1 with TWRP. Now I needed a full reset due to a Bluetooth problem to check if its root/software related. BUT on my mistake I erased EVERYTHING through TWRP (Dalvik/ART Cahe,System,Data,Internal Storage,Cache, Micro SD, Android Secure, USB-OTG)
Tried to install custom rom Aospextended but I don't know the how to and I am lost in forums.. the phone doesn't boot... after zip file installation the screen fades to somewhat yellowish like LCD problem... I can still access TWRP..
p.s. I am an iPhone guy and just tried to fix this for my son... hope for your understanding for probably asking something very common..!
ANY HELP WOULD BE greatly appreciated even to get back to stock rom
Many thanks in advance!
Click to expand...
Click to collapse
You have two solutions, you can restore your phone STOCK ROM with Samsung Smart Switch or downgrade to Lollypop firmware and install any custom rom trough TWRP.
Restore to STOCK:
Use Samsung Smart Switch, see howto here
Downgrade to Lollipop:
Install only Bootloader/Modem [6.0.1/5.1.1]BOOTLOADER AND MODEM FOR J500xx [Downgrade more easy] (Collection)
Downgrade to Lollypop (full ROM) (Tutorial) Upgrade J5 (2015) to 6.0 and Downgrade to 5.1.1 + Rooting
Also take a look at [GALAXY J5] Basic informations | Guides | Tips and Tricks | ROMS & KERNELS
DDkin said:
I had the same problem when flashing Lineage 14.1 on my phone (J500M), screen fadding with a green-yellowish color and no boot. That happened because I was trying to flash the custon Rom with the wrong base. I was using 6.0 before flashing and Lineage requires you start from 5.1.
All I need to do was search for my device on sammobile.com , get the right stock firmware and use Odin to flash the rom on my device. From there I was able to flash TWRP again and install Lineage correctly.
Click to expand...
Click to collapse
American_Jesus said:
You have two solutions, you can restore your phone STOCK ROM with Samsung Smart Switch or downgrade to Lollypop firmware and install any custom rom trough TWRP.
Restore to STOCK:
Use Samsung Smart Switch, see howto here
Downgrade to Lollipop:
Install only Bootloader/Modem [6.0.1/5.1.1]BOOTLOADER AND MODEM FOR J500xx [Downgrade more easy] (Collection)
Downgrade to Lollypop (full ROM) (Tutorial) Upgrade J5 (2015) to 6.0 and Downgrade to 5.1.1 + Rooting
Also take a look at [GALAXY J5] Basic informations | Guides | Tips and Tricks | ROMS & KERNELS
Click to expand...
Click to collapse
MANY THANKS to both of you guys!
Bro just install the official rom ,u can download it from the official site and flash with odin ..
I was trying to flash Arrow Rom. Previously i had installed another rom which was oreo too. Can't remember its name. Steps that I followed:-
1. Wiped everything. Since i don't use this device i didn't take any backup. So i don't have any rom installed now:'(
2. Tried to flash the file. But it keeps showing error
Help plox
golu12c said:
I was trying to flash Arrow Rom. Previously i had installed another rom which was oreo too. Can't remember its name. Steps that I followed:-
1. Wiped everything. Since i don't use this device i didn't take any backup. So i don't have any rom installed now:'(
2. Tried to flash the file. But it keeps showing error
Help plox
Click to expand...
Click to collapse
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
strongst said:
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
Click to expand...
Click to collapse
Oh okay. Sorry;_;
Thank you. I will try to flash another rom.
strongst said:
You simply downloaded the wrong file, it's for Zuk Z2, not for moto g4 plus aka athene.
Please be aware what rom files for which devices you download.
Click to expand...
Click to collapse
Hi. Downloaded the Athene file this time. It started downloading normaly. But then a new error popped up. Update Process ended with signal 7.
Attaching photo again
golu12c said:
Hi. Downloaded the Athene file this time. It started downloading normaly. But then a new error popped up. Update Process ended with signal 7.
Attaching photo again
Click to expand...
Click to collapse
Error 7 leads to corrupted file. Please make sure you download it without interrupting or it will be broken.
strongst said:
Error 7 leads to corrupted file. Please make sure you download it without interrupting or it will be broken.
Click to expand...
Click to collapse
So i downloaded the rom again. Transfered it properly. Same error.(error 7)
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
golu12c said:
So i downloaded the rom again. Transfered it properly. Same error.
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
Click to expand...
Click to collapse
And your absolut sure these 5 rom files are OK and not broken? You download the correct device versions?
Which roms you have(file names)?
What twrp version(link /file name)?
You can flash twrp with twrp itself(install - > image) or with fastboot like the first time.
golu12c said:
So i downloaded the rom again. Transfered it properly. Same error.(error 7)
So just to be sure. Downloaded 5 different Roms.
Same error. My friend suggested me to flash through Adb sideload. I think it flashes but not properly since my device got stucked on bootloop for around 40 minutes before i switched it off for 2 different ROMs. Ene of the day I am back to stage 1. My friend told me to instal TWRP again. But without any OS how can i do it. Please help;_;
Click to expand...
Click to collapse
I hope you did not pause the download in between or it did not failed and you started from the failed point (It can be done in Firefox)
Check the md5 of the zip file.
Also try a different TWRP. What TWRP are you using right now??.......just tell what source you downloaded it from
Heeth21 said:
I hope you did not pause the download in between or it did not failed and you started from the failed point (It can be done in Firefox)
Check the md5 of the zip file.
Also try a different TWRP. What TWRP are you using right now??.......just tell what source you downloaded it from
Click to expand...
Click to collapse
I downloaded the TWRP from the official website version 3.2.1
Link : https://dl.twrp.me/athene/
I have a moto g4 plus 3gb/32 gb version.
golu12c said:
I downloaded the TWRP from the official website version 3.2.1
Link : https://dl.twrp.me/athene/
I have a moto g4 plus 3gb/32 gb version.
Click to expand...
Click to collapse
Wrong TWRP my friend (its a 32 bit TWRP and you need 64 bit TWRP)........strange I thought it was error 255 when we tried to install using wrong TWRP.
Download TWRP by Lyuu and backup EFS first and then flash the ROM.
Heeth21 said:
Wrong TWRP my friend (its a 32 bit TWRP and you need 64 bit TWRP)........strange I thought it was error 255 when we tried to install using wrong TWRP.
Download TWRP by Lyuu and backup EFS first and then flash the ROM.
Click to expand...
Click to collapse
Installed this twrp too. Still no good. Still same error;_;.
But when i tried installing stock rom a new error pooped up. Attaching image of that.
I thought it was successful but it got stuck on boot loop for around 30 mins so i switched off my phone :/
golu12c said:
Installed this twrp too. Still no good. Still same error;_;.
But when i tried installing stock rom a new error pooped up. Attaching image of that.
I thought it was successful but it got stuck on boot loop for around 30 mins so i switched off my phone :/
Click to expand...
Click to collapse
Try installing Stock ROM from fastboot then.
Heeth21 said:
Try installing Stock ROM from fastboot then.
Click to expand...
Click to collapse
Thank you. This worked. Finally i have a ROM ;_;. I will now try to flash custom rom. Thank you for your help
strongst said:
And your absolut sure these 5 rom files are OK and not broken? You download the correct device versions?
Which roms you have(file names)?
What twrp version(link /file name)?
You can flash twrp with twrp itself(install - > image) or with fastboot like the first time.
Click to expand...
Click to collapse
I think there was some problem with the TWRP. Not sure entirely. Yes i downloaded the correct versions of the ROMS. Downloaded 3 versions of one ROM just to be sure;_;
I am currently back to stock rom thanks to Heeth21.
I will try to flash now from the beginning.
Thank you for your help
golu12c said:
I think there was some problem with the TWRP. Not sure entirely. Yes i downloaded the correct versions of the ROMS. Downloaded 3 versions of one ROM just to be sure;_;
I am currently back to stock rom thanks to Heeth21.
I will try to flash now from the beginning.
Thank you for your help
Click to expand...
Click to collapse
I asked you about your twrp already https://forum.xda-developers.com/mo...sh-custom-rom-noob-help-t3883210/post78527551
Please make sure to read and answer the questions properly
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
mikekote666 said:
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
Click to expand...
Click to collapse
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
mikekote666 said:
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
Click to expand...
Click to collapse
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
you need to format data first time
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
Format data
gandyprakoso said:
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Format data
Click to expand...
Click to collapse
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
noddledizzy said:
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
Click to expand...
Click to collapse
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L.. and since your TWRP has been nuked, youll have to reflash TWRP again yes? ?
Or, if youbdont want to downgrade TWRP, you can use AOSP based rom such as LOS15.1.. i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
gandyprakoso said:
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L..
Or, you can use AOSP based rom such as LOS15.1.
i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
Click to expand...
Click to collapse
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
noddledizzy said:
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
Click to expand...
Click to collapse
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
gandyprakoso said:
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
Click to expand...
Click to collapse
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
noddledizzy said:
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
Click to expand...
Click to collapse
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
gandyprakoso said:
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
Click to expand...
Click to collapse
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
noddledizzy said:
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
Click to expand...
Click to collapse
Ok then and happy flashing m8 ?
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
Where? Right in the portion where it says Known Issues of the first link.
Downgrading TWRP to 3.2.3-4 will fix it. I had the same issue.
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
From TWRP thread:
Changed one last thing to try to fix stock Oreo decryption.
There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
Click to expand...
Click to collapse
If you still have your non-Encryption-supporting TWRP as download mode, wipe data from there. For some reason which was documented in the TWRP thread, most versions of V20 TWRP doesn't remove the encryption flag even on a full wipe. I've gone through the pain several times, but here's roughly what I went through about a month ago. It's possible that using the latest TWRP may allow you to skip straight to step 8. As of this latest wipe, I'm finally at a point again where my phone works properly and TWRP can still see my data.
Basic process to hopefully have a working ongoing phone and TWRP:
1. Reboot to download-mode TWRP
2. Wipe dalvik/cache/data from the older download-mode TWRP
3. Factory reset with YES, still in older download-mode TWRP
4. Reboot to system; it should give you the new-system-setup past the Decryption unsuccessful screen on your wiped device
5. Setup without a Google account or fingerprint
6. Reboot back to recovery, not download TWRP; use download mode to get there if you need to
7. Flash the latest TWRP version from the thread (no older than October 25, 2019)
8. Reboot back to recovery
9. Wipe dalvik/cache/data
10. Reboot back to system
11. Setup as you like
12. Reboot back to recovery and make sure you can see your storage
If it gets a decryption error on latest TWRP at step 12 and you can't see data while in Recovery, try skipping adding a fingerprint during setup (run through steps 8-12, no fingerprint on 11) and see if that fixes it.
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
My solution turned out to be formatting /data. Wiping it was apparently not really wiping it clean. Formatting it got me back to a working phone, though I had to re-install everything.
Thanks everyone for the help!
Rob
anyone knows how to fix fingerprints not working? h990 oreo rom mk2000 kernel is there any fix?
do i need to return to nougat but than what? please help
edit: was able to fix that by flashing nougat modem
now wifi wont turn on tho anyone know how to fix?
Hello everyone i am in desparate need of some guidance where i unfortunately Hard bricked my Mi9t while trying to flash the new Mokee Rom.
Where i think i went wrong was wiping the system option in twrp. After reboot i was stuck on flashboot and unable to get back into twrp recovery.
I then proceeded to flashboot twrp, also used multiple versions of twrp, again to hopefully be able to get into twrp recovery with no prevail.
Also tried to fastboot via Miflash tool with all latest fastboot roms available currently but kept getting a anti-rollback error.
So then i searched a way to install recovery or stock rom manually via flashboot commands. This caused me to end up where im at, no fastboot, no recovery, no logo at all. I connect the usb and the phone wont turn on at all, just a dead phone. Power button completely unresponsive now, Vol-Up/Vol-Down + Power and nothing.
I worked on it for countless hours trying to simply get into fastboot now with huge anxiety thinking i killed my phone.
I left my phone to charge all night and woke up this morning trying to get into fastboot again and nothing again.
Can someone please lead me in the right direction???
Everywhere i look the info seems to be outdated. At this point i am willing to send it in for repairs but i live in Indiana, US and there isnt a Xiaomi Service location anywhere in site.
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
When i 1st attempted to recover twrp i used TWRP 3.1.1-2 fixed from 4PDA. Ran the .exe file and the prompt said both fires installed successfully, but when i did a reboot it wouldnt go into twrp anymore, just stuck in logo so i would end up back in bootloader.
ttp://en.miui.com/thread-942449-1-1.html
This is exactly the instructions i tried to use before i lost fastboot.
At one point while entering the commands, it froze then my phone completely died and could never make it do anything else.
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
fabsen said:
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
Click to expand...
Click to collapse
I kno bro i felt like shyt believe me. Literally all day in panic and anxiety that i just wasnt thinking straight and using any kind of guide i can find and ended up here.
Made some progress today tho.
Since my device manager or MiFlash tool wasnt recognizing my device even when i installed Qualcom drivers and pushing all sorts of buttons lol,
I have now opened her up for some surgery and using the Test-Point EDL method.
https://i.postimg.cc/HWJGWHRw/test-point-redmi-k20-mi-9t.png
While USB connected and shorted these 2 pins my computer finally recognized my device in MiFlash Tool and Device Manager again as Qualcomm HS-USB QDLoader 9008 (COM3)!!!
Now the next problem is the MiFlash tool. I tried to flash rom and status states cannot receive hello packet. From what i understand, i need an authorized account.
Only thing i could find to bypass this was this but currently not yet working. - https://forum.xda-developers.com/mi-8/how-to/unbrick-mi8-edl-authorized-account-t3896677
Any ideas where to go from here?
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
fabsen said:
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
Click to expand...
Click to collapse
Already ran into those sites and actually am currently trying out S-Unlock service to bypass Authorized Account with there XiaomiTool v0.01, and unfortunately again with no prevail.
https://imgur.com/gallery/WMt968b
As you can see i got passed Hello packet, but now it doesn't go passed this message or looks like it didnt do anything.
https://imgur.com/gallery/hHApyJL
Already contacted S-Unlock Admin and now waiting for response. Im assuming im using the right Flashboot Roms. Tried latest flashboot roms from here available. https://xiaomifirmwareupdater.com/miui/davinci/
I also emailed unbrick.ru if they support K20/Mi9T variant and waiting for there reply.
Firmware on your page is not up to date. Use https://mifirm.net/
What device do you have? EEA/Global/CN? And what flashfiles did you use? I'm asking this because the only way I know to brick your device is to flash global/eea-rom on chinese device and lock the bootloader.
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Waidowai said:
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Click to expand...
Click to collapse
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
fabsen said:
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
Click to expand...
Click to collapse
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Waidowai said:
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Click to expand...
Click to collapse
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
fabsen said:
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
Click to expand...
Click to collapse
If i download the xiamitool v2 and choose my device is bricked it says feature is not available yet.
/edit
If I choose mod the phone it says my phone serial and all the 3 other things are unknown.
if I select my phone my phone reboots and says waiting for debugging mode....
Then if I delete the ARB lines and try to flash via MiFlash it says error error no such file found
Can someone pls give me some clearer instructions.
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
/edit
alright who gives a dang I just flashed the eu rom to be safe with updates..
anyhow is it normal that my devices says Redmi by Xiaomi now?
Prior on my stock rom it said MI by mi.com or something
Waidowai said:
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
Click to expand...
Click to collapse
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
fabsen said:
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Click to expand...
Click to collapse
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
mauriciocardoso said:
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
Click to expand...
Click to collapse
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
just like me , for the anti roll issue u need to flash newers rom like from latest u flash on ur device before (recommend V10.3.11.0.PFJMIXM) u can get on mifirm.net . after download rom extract the file into fastboot tools then copy all .img file into fastboot tools . after that open the fastboot mode on ur phone and tools on pc
then flash this file
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
then try reboot phone into recovery
if work let me know . im trying make this method because before this i got this problem to after flashing paranoid rom without format data .
Waidowai said:
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
Click to expand...
Click to collapse
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
fabsen said:
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
Click to expand...
Click to collapse
I mean yeah that's what i thought just flash a official rom like any stock rom. Or rather if you change roms cuz if you update existing roms you don't really need to wipe anything anymore.
But apperently it busted my whole phone. It was a weird brick. My phone wasn't recognized as a phone anymore in fastboot. But it was recognized normal in adb. So I needed to change windows drivers to make my phone recognize.
And after that nothing booted but stock recovery and even then it said I don't have debugging enabled. Eventho I was connected to adb??
Anyhow I think the flash messed up the whole system partition. So what I did is in short formate the whole drive and start with a clean slate.. anyhow don't need to repeat all that.
But yeah I'm with you with the take on costume roms. I don't see the need anymore since most stock roms are decent nowadays and costume roms especially are most likely buggy somehow. Good thing is that most stuff I need in my phone is working on the eu rom. Like I said only thing that I could find not working are themes. But thats ok.
I don't know what that widevine L1 thing is. So I prolly don't need it. But maybe u can explain it to me Always up to learn new things.
Well for now I stick with the costume rom since it's basically no different to me. And the chance of bricking again like that with a costume rom are slim to none. If the phone brick it's most likely just a simple brick that can be fixed with twrp. and if that doesn't work by booting into twrp from adb.
Btw that didn't work on my weird brick either. I couldn't boot anything from adb. It gave me a black screen when trying to boot something.
Anyhow I'm glad I've got it running again. But somehow I'm not that surprised. Most times when I brick phones I can fix it when I'm at the point where I wanna throw the phone away. Cuz then I'm just flashing everything I can to make it work xD.