I just bricked yesterday in spite of know downgraded ROM contain firmware update folder which may brick . During changing ROM accidentally flash that ROM, after Black screen I realised. I didn't get Authorization to unbrick. So just handed over my phone to mi service centre today and waiting. How many of you bricked and restored by how?
It's hard to brick if you do the flashing carefully. Many people bricked their devices just because they didn't know about the ARB. To my knowledge flashing bootloader partition to older version of the bootloader will certainly brick the device.
You can flash modem, bluetooth, dsp, splash, system, vendor, data, cache, recovery partitions and it wont brick
A good question would be how many have successfully unbricked their devices by their own.
It's hard to brick if you do the flashing carefully. Many people bricked their devices just because they didn't know about the ARB.
Click to expand...
Click to collapse
No, it isn't hard, several active rom tutorials here have instructions that include flashing a lower version and do not mention that downgrading will cause bricking. So, if you follow a ROM guide, you can easily brick your device.
But the real problem isn't the guides and the users, the real problem is that it is very stupid to allow flashing the device with something that will certainly brick it. And for this, we can only thank the phone manufacturer.
drmuruga said:
I just bricked yesterday in spite of know downgraded ROM contain firmware update folder which may brick . During changing ROM accidentally flash that ROM, after Black screen I realised. I didn't get Authorization to unbrick. So just handed over my phone to mi service centre today and waiting. How many of you bricked and restored by how?
Click to expand...
Click to collapse
flashed using twrp or mi recovery ????
I really hope that Xiaomi is not going to get away with this
SunilSuni said:
flashed using twrp or mi recovery ????
Click to expand...
Click to collapse
Twrp.
kellerman40 said:
It's hard to brick if you do the flashing carefully. Many people bricked their devices just because they didn't know about the ARB. To my knowledge flashing bootloader partition to older version of the bootloader will certainly brick the device.
You can flash modem, bluetooth, dsp, splash, system, vendor, data, cache, recovery partitions and it wont brick
Click to expand...
Click to collapse
To be fair, in the LineageOS15.1 thread, the official instructions to flash are leading to brick. I reported but nobody cares.
And a few users got bricked (I did not).
htchd2sucks said:
To be fair, in the LineageOS15.1 thread, the official instructions to flash are leading to brick. I reported but nobody cares.
Click to expand...
Click to collapse
I guess You don't read a section called "Things to do before flashing"
Sent from my whyred using XDA Labs
MikiGry said:
I guess You don't read a section called "Things to do before flashing"
Sent from my whyred using XDA Labs
Click to expand...
Click to collapse
I understood nothing of what you said.
The instructions are indicating to flash an older firmware which leads to bricking. Worse, they give a link to version 8.7.5 and indicate falsely it's 9.7.5 which is a killer for those with ARB V4.
How do i exactly flash vendor?
Before flashing xiaomi.eu i accidentely wiped my vendor, which resulted in an error 7
cassinni said:
How do i exactly flash vendor?
Before flashing xiaomi.eu i accidentely wiped my vendor, which resulted in an error 7
Click to expand...
Click to collapse
Just Flash a new firmware and install the rom
Authorization Has been patched
Related
Well, some days ago I accidentally encrypted my gnex, and many attempts to undo the encryption failed.
But this time, the **** was bigger than the hole.
I wiped ALL the data(YES I WENT FULL RETARD) and now I cant boot the android neither flash the stock ROM by common ways.
So guys, how can i flash again to the stock rom?
lotusgg said:
Well, some days ago I accidentally encrypted my gnex, and many attempts to undo the encryption failed.
But this time, the **** was bigger than the hole.
I wiped ALL the data(YES I WENT FULL RETARD) and now I cant boot the android neither flash the stock ROM by common ways.
So guys, how can i flash again to the stock rom?
Click to expand...
Click to collapse
more info please how are you flashing what version do you have what have you tryed ill help if i can but i need info please
lotusgg said:
Well, some days ago I accidentally encrypted my gnex, and many attempts to undo the encryption failed.
But this time, the **** was bigger than the hole.
I wiped ALL the data(YES I WENT FULL RETARD) and now I cant boot the android neither flash the stock ROM by common ways.
So guys, how can i flash again to the stock rom?
Click to expand...
Click to collapse
You can follow efrants guide in general.
Sent from my Nexus
Alpha_wolf said:
more info please how are you flashing what version do you have what have you tryed ill help if i can but i need info please
Click to expand...
Click to collapse
There is no version since I wiped everything, i got no boot, only the fastboot and the cwm recovery. Trying to flash stock rom.
bk201doesntexist said:
You can follow efrants guide in general.
Sent from my Nexus
Click to expand...
Click to collapse
I cant follow any guide, since in gnex toolkit any version I select wont recognize my device. At least i did not tryied every version.
lotusgg said:
I cant follow any guide, since in gnex toolkit any version I select wont recognize my device. At least i did not tryied every version.
Click to expand...
Click to collapse
You don't need a toolkit, that guide doesn't use one or recommend one.
cupfulloflol said:
You don't need a toolkit, that guide doesn't use one or recommend one.
Click to expand...
Click to collapse
Exactly, who said anything about toolkits?
Sent from my Nexus
Hi everyone,
I've got a quick bootloader unlocking query - if I were to unlock my bootloader and then immediately flash a custom kernel (i.e. no reboot in between), would this cause a hard-brick?
I ask because I'm on my 2nd phone now, having bricked the first one due to impatience! I'd like to unlock the bootloader but I'm too scared of bricking it again :silly:
Cheers
im quite sure you may need to let it settle for a bit
there has been no one who i know of who has done that so id suggest of unlocking and waiting a day or two
Sent from my LT26i using XDA Premium 4 mobile app
I think you'd better read carefully in the furom,unless you are full understanding,you can flash the custom rom
Sent from my Xperia S using XDA Premium 4 mobile app
Yeah I've done a lot of reading & following guides for rooting etc. I've been searching through the bricked devices threads and it has now put me off unlocking the BL :laugh:
I found this post (http://forum.xda-developers.com/showthread.php?p=48773344#post48773344) where someone has successfully unlocked their bootloader and flashed an advanced stock kernel, and then flashed the DooMKernel (same one I tried the first time) and then bricked their phone!! Their symptoms are exactly the same as mine. The annoying thing is that everyone else seems to be able to flash the DooMKernel without issue - the DooMKernel thread is full of satisfied customers! The randomness of bricking isn't worth the risk
Cheers guys
supermeerkat said:
Yeah I've done a lot of reading & following guides for rooting etc. I've been searching through the bricked devices threads and it has now put me off unlocking the BL :laugh:
I found this post (http://forum.xda-developers.com/showthread.php?p=48773344#post48773344) where someone has successfully unlocked their bootloader and flashed an advanced stock kernel, and then flashed the DooMKernel (same one I tried the first time) and then bricked their phone!! Their symptoms are exactly the same as mine. The annoying thing is that everyone else seems to be able to flash the DooMKernel without issue - the DooMKernel thread is full of satisfied customers! The randomness of bricking isn't worth the risk
Cheers guys
Click to expand...
Click to collapse
well, this is my person experience, i unlocked and loaded a custom ROM immediately without flashing the kernal and it works fine. I am not sure if flashing a kernel after that will create any issues.
lowks said:
well, this is my person experience, i unlocked and loaded a custom ROM immediately without flashing the kernal and it works fine. I am not sure if flashing a kernel after that will create any issues.
Click to expand...
Click to collapse
If you flashed a custom rom that required an unlocked bootloader, then I assume it's because it comes with a custom (i.e. non-stock) kernel? After unlocking the bootloader, did you let the phone boot normally before flashing the custom rom?
supermeerkat said:
If you flashed a custom rom that required an unlocked bootloader, then I assume it's because it comes with a custom (i.e. non-stock) kernel? After unlocking the bootloader, did you let the phone boot normally before flashing the custom rom?
Click to expand...
Click to collapse
Yes I did... I asked the custom rom had a custom kernel inside
supermeerkat said:
Hi everyone,
I've got a quick bootloader unlocking query - if I were to unlock my bootloader and then immediately flash a custom kernel (i.e. no reboot in between), would this cause a hard-brick?
I ask because I'm on my 2nd phone now, having bricked the first one due to impatience! I'd like to unlock the bootloader but I'm too scared of bricking it again :silly:
Cheers
Click to expand...
Click to collapse
I did it and immediately flash carbon rom (4.4.2)....no problem so far make sure you u wipe everything cache,dalvik cache, data and system then flash doomlord's kernel....
eddie13 said:
I did it and immediately flash carbon rom (4.4.2)....no problem so far make sure you u wipe everything cache,dalvik cache, data and system then flash doomlord's kernel....
Click to expand...
Click to collapse
Ah, so you managed to flash a custom rom/kernel without rebooting after unlocking the bootloader? At least that confirms that something else is responsible for bricking my phone. When I bricked my phone, I didn't wipe cache or dalvik - I started from a fresh stock rom...didn't even root or have a recovery installed.
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?
flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !
porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does
flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well
I understand that with thins new update it becomes impossible to downgrade to previous versions of MIUI but how about custom roms like lineage? Or installing twrp and magisk? There is a lot of info scattered but i would like to get some answers and update OP with something like a FAQ of do and Do not to make it easier for everybody
*Work in Progress*
-Miui 10
- From 8.7.10 onward flashing TWRP is impossible but booting into TWRP is possible from Fastboot using "fastboot boot recovery.img"
- There is one report of a successful Treble Lineage Flash ( take it with a grain of salt )
Tyrany said:
I understand that with thins new update it becomes impossible to downgrade to previous versions of MIUI but how about custom roms like lineage? Or installing twrp and magisk? There is a lot of info scattered but i would like to get some answers and update OP with something like a FAQ of do and Do not to make it easier for everybody
Click to expand...
Click to collapse
Yes we need to know if possible flash custom roms or not. If yes the anti rollback isnt a big deal.
I updated to latest global beta.......now i cant flash twrp recovery now because of this anti rollback.
in my expiriance with LG G4 with antirollback. i could flash any custom rom aosp laos. just stock rom from LG i could not . qfuse will blow and brick phone.. this was only on LG firmware stock roms. not sure if its the same in xiaomi.
TWRP can be installed
Im currently on Miui 10 8.7.12 global beta
I have TWRP 3.2.1 installed along with magisk 16.0 :good:
Everything works fine
Have no intention of going back to previous builds
00r3 said:
Im currently on Miui 10 8.7.12 global beta
I have TWRP 3.2.1 installed along with magisk 16.0 :good:
Everything works fine
Have no intention of going back to previous builds
Click to expand...
Click to collapse
did you install before or after updating?
Installed it after as twrp was replaced by stock.
After rooting it works fine
Anti roll back is already in moto phones. Only problem is rollback to stock only you can flash 8.1 to 7.1 custom ROMs. Even in stock you can skip bootloader files and flash to rollback with upgraded bootloader. Its new to xiaomi.
So Anti-rollback is no big deal because we can install TWRP + custom roms then? Some people say no (they can't, with little to no evidence) and others say yes (with decent evidence). Do we know what's up, I read comments telling it's basically 50:50. Is it device dependant, or do we need some exploits in terms of drivers/software usage etc? Thanks for your reply!
I'm also searching whether we can install custom rom or not ?
My RN5 AI came with stable MIUI 9.5.22.0. When I tried to install TWRP, to begin the process of flashing RR, I got the anti-rollback message and TWRP install failed.
You can install custom recovery and roms. Method here: Everything About Anti Roll-back .
ToXiTe said:
You can install custom recovery and roms. Method here: Everything About Anti Roll-back .
Click to expand...
Click to collapse
Link is down!
MarvinMe said:
So Anti-rollback is no big deal because we can install TWRP + custom roms then? Some people say no (they can't, with little to no evidence) and others say yes (with decent evidence). Do we know what's up, I read comments telling it's basically 50:50. Is it device dependant, or do we need some exploits in terms of drivers/software usage etc? Thanks for your reply!
Click to expand...
Click to collapse
we can install it, i did on 8.7.12. using redwolf.
also will be falshing custom roms tomorrow. so its just few extra precaustions. otherwise it business as usual
Kapiljhajhria said:
we can install it, i did on 8.7.12. using redwolf.
also will be falshing custom roms tomorrow. so its just few extra precaustions. otherwise it business as usual
Click to expand...
Click to collapse
Did you check the version of anti-rollback via fastboot (fastboot getvar anti)?
What was your method of flashing? Minimal adb and fastboot flash recovery redwolf.img and then boot into it, or just booting into it and flashing redwolf.img from the recovery itself? Did you use lazyflasher afterwards, or is it even necessay with redwolf? Which version of Redwolf did you use?
Thanks for your effort and sorry for all of these questions, I really hope we can help the community out. Plz tell then if you succeed in flashing a custom rom
MarvinMe said:
Link is down!
Click to expand...
Click to collapse
Sorry, wrong link. Updated
ToXiTe said:
Sorry, wrong link. Updated
Click to expand...
Click to collapse
So nothing has changed regarding flashing recovery and custom roms? I mean, people managed to flash twrp/redwolf the normal way --> doing the same with custom roms. I don't think we have a problem here but still this new implementation makes me nervous...
Edit: huh, no just flashing the antibypass image before doing the twrp in case you are on anti rollback > 3. Just with "fastboot getvar anti" the version, if you are on 3 you are good, if you are on 4 use the method the link I guess...
MarvinMe said:
Did you check the version of anti-rollback via fastboot (fastboot getvar anti)?
What was your method of flashing? Minimal adb and fastboot flash recovery redwolf.img and then boot into it, or just booting into it and flashing redwolf.img from the recovery itself? Did you use lazyflasher afterwards, or is it even necessay with redwolf? Which version of Redwolf did you use?
Thanks for your effort and sorry for all of these questions, I really hope we can help the community out. Plz tell then if you succeed in flashing a custom rom
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...warning-update-to-recent-miui-builds-t3814895