Related
Hi All, I have unlocked the bootloader the unnofical way and i am on global 7.1.7.0(LHOMICL) with twrp and root.
I now have recieved the official sms to unlock from xiaomi.
Already i had to open the phone 3 times to get into edl mode. I really dont wont to open the phone agian.
When i try to unlock the tool answers no need to unlock. I think this is because i flashed the adapted emmc_appsboot.mbn and boot.img thru fastboot.
Do i have to change te rom to another version before i try thru edl or fastboot? What is the best procedure to official unlock now because i read a lot of bricks if they try to revert back to original state.
Can some one give me a detailed guide? Thanx in advance.
You need to flash a fully stock edl ROM on top of your current setup.
This will wipe out your hacked bootloader and throw the original (still locked) one back onto your device.
Then just unlock as usual. I did the procedure myself today already as I got my unlock notification today as well.
Ok thnx for the info. I have changed this global rom 7.1.7.0 in great extend and dont wont to lose this setup.
So can I backup my current setup with twrp with the hacked bootloader.
Flash the complete global 7.1.7.0 in edl mode. Unlock with the unlock tool.
Root the rom and install twrp.
After this can i restore the backup with the hacked bootloader with twrp?
I dont know how the unlock tool of xiaomi works, so i could leave the official bootloader in place when i do the restore with twrp and only replace system and data partition or can i flash all the parts back with twrp to keep the unlock?
Wich procedure will keep the official unlock in place or will this unlock stick always?
davegrond said:
Hi All, I have unlocked the bootloader the unnofical way and i am on global 7.1.7.0(LHOMICL) with twrp and root.
I now have recieved the official sms to unlock from xiaomi.
Already i had to open the phone 3 times to get into edl mode. I really dont wont to open the phone agian.
When i try to unlock the tool answers no need to unlock. I think this is because i flashed the adapted emmc_appsboot.mbn and boot.img thru fastboot.
Do i have to change te rom to another version before i try thru edl or fastboot? What is the best procedure to official unlock now because i read a lot of bricks if they try to revert back to original state.
Can some one give me a detailed guide? Thanx in advance.
Click to expand...
Click to collapse
Plz could you help me and tell me where you got the hacked unlocked bootloader cause I bricked my redmi note 3 pro snap dragon and only only fastboot is available and when I try to flash it I get the message device locked boot locked can not flash and plz hobe me a detaild link and downloads and how to flash also I did not get the unlock code and how to get the locked one back z original plz help best regards
Plz indeed to know how to hack the bootloader cause I bricked my phone and I need to make it life
MrColdbird said:
You need to flash a fully stock edl ROM on top of your current setup.
This will wipe out your hacked bootloader and throw the original (still locked) one back onto your device.
Then just unlock as usual. I did the procedure myself today already as I got my unlock notification today as well.
Click to expand...
Click to collapse
please give a detailed tutorial how to do it. I am now in AOSP with unofficially unlocked bootloader. How to relock it again to unlock officially?
Relock Bootloader
I see many asking how to Relock Bootloader, especially those who had unlocked unofficially.
The steps to be followed are following:
(1) Turn on USB debugging for your phone;
Go to Settings -- About Phone --> Touch 7 times on "MIUI version" to Enable Developer Options.
Now go to Settings - Additional Settings - Developer Options --> USB debugging.
Enable USB Debugging and Connect to PC.
(2) Download Fastboot ROM (file extension .tgz or .tar) from
Code:
http://en.miui.com/a-234.html
(3) Boot into EDL
adb devices (to check it's connected)
adb reboot edl
(4) Use MI Flash Tool to Flash the Fastboot ROM
PS: It is assumed that person knows how to get drivers installed for phone if not already, use ADB command as well as know MI Flash Tool basics.
@BRoy_98 @ioosis @davegrond : hope this helps.
@MrColdbird Thanks for the tip
BRoy_98 said:
please give a detailed tutorial how to do it. I am now in AOSP with unofficially unlocked bootloader. How to relock it again to unlock officially?
Click to expand...
Click to collapse
Thx
Sent from my Redmi Note 3 using XDA-Developers mobile app
Unable to relock
Someone please let me know how to relock the bootloader.
I tried flashing the global rom using flash tool but still it says unlocked when i check it from fastboot mode.
anwar08 said:
Someone please let me know how to relock the bootloader.
I tried flashing the global rom using flash tool but still it says unlocked when i check it from fastboot mode.
Click to expand...
Click to collapse
On MiFlash, select folder of Fastboot ROM, then click on Advanced, and in fastboot script select flash_all_lock.bat. After it, close MiFlash then open it again and check in advanced if flash_all_lock.bat comes selected. If yes, close advanced box and flash ROM. Don't forget to close and open MiFlash after choose flash_all_lock.bat script, it's important step. And you can do it in Fastboot mode, don't need to go to EDL mode to flash the ROM.
andersonaragao said:
On MiFlash, select folder of Fastboot ROM, then click on Advanced, and in fastboot script select flash_all_lock.bat. After it, close MiFlash then open it again and check in advanced if flash_all_lock.bat comes selected. If yes, close advanced box and flash ROM. Don't forget to close and open MiFlash after choose flash_all_lock.bat script, it's important step. And you can do it in Fastboot mode, don't need to go to EDL mode to flash the ROM.
View attachment 3854529 View attachment 3854530 View attachment 3854531 View attachment 3854532
Click to expand...
Click to collapse
Am using the 32 bit beta version and there is no Advanced option
anwar08 said:
Am using the 32 bit beta version and there is no Advanced option
Click to expand...
Click to collapse
see if it's in Configuration.
warranty
does rooting redmi note 3 void warranty bcuz it has a locked bootloader and cannot root without unlocking it ????
and can we lock bootloader again for warranty claims ????
plzz help ???
ty.
Why can't we directly update the device..
Like after flashing miui ROM (7.1)then installing (8.1)....will the bootloader get locked....
?....somebody have any idea place help out
Q. Can the device be rooted without voiding warranty?
A. Yes, by unlocking the BL unofficially.
Q. Once rooted and on MiUI, can I update using Updater?
A. No! You'll lock your BL and end up in a bootloop. Instead, use the updater to download the zip file, reboot into recovery (TWRP or ZCX) flash the zip first and then the universal boot.img patched/lazy flasher and reboot to system.
I followed the method mentioned in the replies to relock the bootloader, i.e, flashed the fastboot rom in edl mode
But for some strange reason, when I entered the fastboot mode and checked whether the bootloader is locked or not by "fastboot oem device-info", it said "Device Unlocked: True"
The main problem came when I booted into the ROM; It broke all kinds of wireless connections. The wifi malfunctioned, the phone wouldn't read the SIM cards etc.
Is there a solution? Please help
Thanks
Hi all!
I was on cm13 nightlies with cm recovery. when I was trying to flash oxygen recovery and oxygen os 3.0.1 I have locked bootloader by mistake with command fastboot oem lock and when I trying to unlock it again with command fastboot oem unlock I get the OKAY message but phone reboot to cm recovery and lock bootloader again!
Now I have no access to cm13 or any ROM just cm recovery and when I flash cm13 again through recovery nothing is done phone just booting to recovery
Please HELP.
Use Qualcomm restore method to get back to official ROM and recovery and then unlock again, it should work.
pitrus- said:
Use Qualcomm restore method to get back to official ROM and recovery and then unlock again, it should work.
Click to expand...
Click to collapse
please explain the method or mention it here.
thanks for reply
It has been answered to many times already, just search and you'll find it in a second.
pitrus- said:
It has been answered to many times already, just search and you'll find it in a second.
Click to expand...
Click to collapse
Thank you so much it's worked well
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
RoyJ said:
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
Click to expand...
Click to collapse
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
anokmik said:
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
Click to expand...
Click to collapse
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
fapste said:
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
Click to expand...
Click to collapse
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Alsen Lea said:
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Click to expand...
Click to collapse
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
Click to expand...
Click to collapse
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Steps that I have done from stock recovery:
1. Wipe cache
2. Wipe data/ factory reset
3. Sideload 7.0 (angler-ota-nbd91k-32c2eac8) and the result is successful "script succeded: result was [1.000000]"
4. Wipe cache
5. Wipe data/ factory reset
6. Power off
7. Power on
Unfortunately boot loop persists and if I go back to recovery there is the same build version MTC20F (6.0.1).
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
Click to expand...
Click to collapse
For "fastboot oem unlock" command prompt returns "failed: remote: unknown command". I think this is because Google has changed such command to "fastboot flashing unlock", which gives me "failed: remote: oem unlock is not allowed". This because OEM unlocking hasn't been allowed from Developer Options by previous owner and now I cannot get there because of boot loop. Also have tried "flash-all.bat" from 7.0 latest factory image and on each step it returns error "failed: remote: device is locked. cannot flash images" and this is because of locked bootloader.
Possible solution?
In Stock recovery I have "Mount /system" option. Maybe someone can clarify what does it mean and could it potentially fix boot loop in some way? I have tried google for it, but unfortunately have no luck in finding information about this option.
Thanks in advance for any information!
anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
---------- Post added at 11:39 AM ---------- Previous post was at 11:29 AM ----------
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
fapste said:
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
Click to expand...
Click to collapse
Issue has star from me now. Thanks for the link!
jhs39 said:
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
anokmik said:
Issue has star from me now. Thanks for the link!
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
Click to expand...
Click to collapse
Are you running the latest versions of ADB and Fastboot?
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
jhs39 said:
Are you running the latest versions of ADB and Fastboot?
Click to expand...
Click to collapse
These are the outputs from command prompt:
adb:
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
fastboot:
fastboot version 0e9850346394-android
I think that they are the latest, because I'm an Android dev and I'm updating SDK with tools as soon as new version come in.
jhs39 said:
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
Click to expand...
Click to collapse
Yep, I have known that device has boot loop issue and it was selling as-is for repair. Also I have known that this issue could be fixed, so it was hit or miss. Now I think that this was a miss.
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
jhs39 said:
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
Click to expand...
Click to collapse
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
anokmik said:
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
Click to expand...
Click to collapse
I don't think the warranty is transferable but it won't cost you anything to contact Huawei and see if they will help you out.
http://consumer.huawei.com/in/support/warranty-query/index.htm
You can go to this site to check if the device is still under warranty. I have read about them allowing RMA on 6Ps that were out of warranty so it's worth a try at least.
http://consumer.huawei.com/us/support/warranty-query/index.htm
Sorry this is the site to check if phone is in warranty within the US. Other site was for India.
I`ve decided to return to stock and I wish I didn`t!
After flashing the files for the latest stock image , I was unable to pass the boot animation.
That was six hours ago.
I tried to reinstall another full image from google website.
I did and then my computer doesn`t recognize my device on adb mode.
Tried to update the drivers via Android Studio and through the usb drivers folder , it gives an error of not being able to download the update because of disabling the automatic windows update even though I did.
Help, people what can I do?
Should I just get a new phone?
It`s a very tough option for me right now due to some financial issues.
:crying::crying::crying:
I have also unlocked the bootloader afterwards.
That was such a stupid move!
Sulieman 91 said:
I have also unlocked the bootloader afterwards.
That was such a stupid move!
Click to expand...
Click to collapse
Hi... Explain how exactly you flashed your phone. Fastboot? Adb sideload?
What was your android version prior to your problem.
What version did you try to flash? Did you use the flash all.bat/sh? Or flashed each image manually?
Are you stuck in bootloader? Can you still access recovery? Or does it bootloop when trying to reboot into recovery?
Sulieman 91 said:
I have also unlocked the bootloader afterwards. That was such a stupid move!
Click to expand...
Click to collapse
No, unlocking the bootloader may make the difference in being able to recover your phone. Did you also enable USB debugging in Developer Options when you unlocked your bootloader? Was ADB working before and now has stopped working? I would first focus on getting ADB/fastboot binaries (and USB drivers) set up and working properly on your PC.
5.1 said:
Hi... Explain how exactly you flashed your phone. Fastboot? Adb sideload?
What was your android version prior to your problem.
What version did you try to flash? Did you use the flash all.bat/sh? Or flashed each image manually?
Are you stuck in bootloader? Can you still access recovery? Or does it bootloop when trying to reboot into recovery?
Click to expand...
Click to collapse
I flashed the latest version of Android 7.1.1 with March update
I flashed each image manaually
Not stuck on boot loader but stuck on the animation of booting without accessing anything on the phone so it`s a bootloop.
I flashed stock all and unlocked the bootloader afterwards....... Trying to unlock it now with no hope of how to unlock it and flash anything and save myself from this problem!
v12xke said:
No, unlocking the bootloader may make the difference in being able to recover your phone. Did you also enable USB debugging in Developer Options when you unlocked your bootloader? Was ADB working before and now has stopped working? I would first focus on getting ADB/fastboot binaries (and USB drivers) set up and working properly on your PC.
Click to expand...
Click to collapse
Please tell me that there is a way to unlock the bootloader without enabling usb debugging :\
This is gonna save my butt from a lot of trouble!
Sulieman 91 said:
I have also unlocked the bootloader afterwards. That was such a stupid move!
Click to expand...
Click to collapse
You said you UNLOCKED your bootloader, and that is what I responded to. Did you mean you LOCKED it?
Sulieman 91 said:
Please tell me that there is a way to unlock the bootloader without enabling usb debugging :\
This is gonna save my butt from a lot of trouble!
Click to expand...
Click to collapse
No you just need fastboot working to unlock (this is assuming you already had it unlocked before)... but again this depends on you having your PC set up correctly.
fastboot flashing unlock - try that and see if it finishes successfully or not.
Edit: That and try to answer @5.1 's questions
v12xke said:
You said you UNLOCKED your bootloader, and that is what I responded to. Did you mean you LOCKED it?
No you just need fastboot working to unlock (this is assuming you already had it unlocked before)... but again this depends on you having your PC set up correctly.
fastboot flashing unlock - try that and see if it finishes successfully or not.
Edit: That and try to answer @5.1 's questions
Click to expand...
Click to collapse
I unlocked it before but now did a full recovery to Stock and locked the bootloader.
I need to access the usb debugging option before I can type in that command in the CMD
My PC is set up correctly .
My only problem is that I don`t have access to my phone in order to enable that option and don`t know how to unlock the bootloader with any other way.
That is all
Sulieman 91 said:
I flashed the latest version of Android 7.1.1 with March update
I flashed each image manaually
Not stuck on boot loader but stuck on the animation of booting without accessing anything on the phone so it`s a bootloop.
I flashed stock all and unlocked the bootloader afterwards....... Trying to unlock it now with no hope of how to unlock it and flash anything and save myself from this problem!
Click to expand...
Click to collapse
Not answering what I asked, doesn't help me to help you...
5.1 said:
Not answering what I asked, doesn't help me to help you...
Click to expand...
Click to collapse
I flashed my phone using fastboot
after that unlocked the boot loader
and then I tried to boot the phone normally.
I couldn`t and it stuck on the boot animation for over 6 hours now.
Hi... Explain how exactly you flashed your phone. Fastboot? Adb sideload?
Fastboot
What was your android version prior to your problem.
7.1.1
What version did you try to flash? Did you use the flash all.bat/sh? Or flashed each image manually?
The same version again after flashing a pure nexus rom , flashed each image manually
Are you stuck in bootloader? Can you still access recovery? Or does it bootloop when trying to reboot into recovery?
not stuck on bootloader , still have access to the recovery mode (stock one not TWRP) it bootloops only when I try to turn on the phone.
5.1 said:
Hi... Explain how exactly you flashed your phone. Fastboot? Adb sideload?
Fastboot
What was your android version prior to your problem.
7.1.1 Pure Nexus Rom
What version did you try to flash? Did you use the flash all.bat/sh? Or flashed each image manually?
7.1.1 with March Update , each image manually
Are you stuck in bootloader? Can you still access recovery? Or does it bootloop when trying to reboot into recovery?
Click to expand...
Click to collapse
stuck in boot animation , have access to bootloader & recovery both in stock with no TWRP or Unlocked bootloader
Sulieman 91 said:
I flashed my phone using fastboot
after that unlocked the boot loader
and then I tried to boot the phone normally.
I couldn`t and it stuck on the boot animation for over 6 hours now.
Click to expand...
Click to collapse
Yet you didn't answer the last question...
Do you still have access to recovery?
Try this just in case:
fastboot erase cache
fastboot format userdata
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
Sulieman 91 said:
stuck in boot animation , have access to bootloader & recovery both in stock with no TWRP or Unlocked bootloader
Click to expand...
Click to collapse
Well... Enter recovery and try a factory reset...
Though I find it really strange that your bootloader was unlocked and now... Locked?
5.1 said:
Yet you didn't answer the last question...
Do you still have access to recovery?
Try this just in case:
fastboot erase cache
fastboot format userdata
Click to expand...
Click to collapse
Stock recovery only without any ability to edit or fix anything because of flashing stock android
....... I can`t fix anything from the boot loader as it is locked and need a way to unlock it without the usb debugging that I have no access to.
5.1 said:
Yet you didn't answer the last question...
Do you still have access to recovery?
Try this just in case:
fastboot erase cache
fastboot format userdata
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
Well... Enter recovery and try a factory reset...
Though I find it really strange that your bootloader was unlocked and now... Locked?
Click to expand...
Click to collapse
I locked the bootloader after flashing the system image to return fully to stock but now I realize I`ve blocked myself from even accessing the phone in case such a situation takes place
Sulieman 91 said:
Stock recovery only without any ability to edit or fix anything because of flashing stock android
....... I can`t fix anything from the boot loader as it is locked and need a way to unlock it without the usb debugging that I have no access to.
Click to expand...
Click to collapse
Recovery > wipe data/factory reset
Doesn't work?
5.1 said:
Recovery > wipe data/factory reset
Doesn't work?
Click to expand...
Click to collapse
I just did that and will wait for 4 to 5 minutes to check whether it worked or not.
Stand by
Sulieman 91 said:
I just did that and will wait for 4 to 5 minutes to check whether it worked or not.
Stand by
Click to expand...
Click to collapse
Sure... Good luck...
5.1 said:
Sure... Good luck...
Click to expand...
Click to collapse
Still with the same problem ........ I don`t know what to do , brother !
Sulieman 91 said:
Still with the same problem ........ I don`t know what to do , brother !
Click to expand...
Click to collapse
Neither do I...
What version are you on? 7.1.1?
Try sideloading the beta 7.1.2 ota. You can find it on the N6P general section I think.
I'm not saying it will solve your problem. If factory reset didn't fix your bootloop, I don't know what else to do... Good luck!
Hello y'all.
Today I received the update notification and I tried to install it. That's what I got in the attachment. Can anybody give me a light?
sergioricardojsj said:
Hello y'all.
Today I received the update notification and I tried to install it. That's what I got in the attachment. Can anybody give me a light?
Click to expand...
Click to collapse
You need to provide a bit of information about what you have done to your phone. Unlocked bootloader won't matter but any system changes.
kudos1uk said:
You need to provide a bit of information about what you have done to your phone. Unlocked bootloader won't matter but any system changes.
Click to expand...
Click to collapse
I've done nothing. My bootloader is locked. Nothing is changed.
sergioricardojsj said:
I've done nothing. My bootloader is locked. Nothing is changed.
Click to expand...
Click to collapse
Looking at your previous posts that is clearly not the case, good luck.
SOLVED! I flashed the same Stock ROM in the Fastboot Mode and tried to update again, it worked.
sergioricardojsj said:
SOLVED! I flashed the same Stock ROM in the Fastboot Mode and tried to update again, it worked.
Click to expand...
Click to collapse
can you share the rom you flashed please
ccalixtro said:
can you share the rom you flashed please
Click to expand...
Click to collapse
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
sergioricardojsj said:
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
Click to expand...
Click to collapse
thanks but i cant get into fastboot mode only blinking led.
sergioricardojsj said:
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
Click to expand...
Click to collapse
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
barrack1 said:
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
Click to expand...
Click to collapse
Hi, any alternative to solve this issue? I dont think the boot img or partition have been tempered because safetynet check and all my banking apps working fine
i have same problem, i was enable camera2 api for Gcam in my phone, by following tutorial in this forum, Using temporary twrp, unlock bootloader and lock back. And now i cant update with same problem in first post picture. Please someone give us solution for fix this. Thx
Sorry- ignore this message, wrong thread.
ltf_195 said:
Hi, any alternative to solve this issue? I dont think the boot img or partition have been tempered because safetynet check and all my banking apps working fine
Click to expand...
Click to collapse
You don't need to make any modifications, just mounting /system with rw in twrp will break ota.
barrack1 said:
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
Click to expand...
Click to collapse
Dude, I'm just trying to help who wants help (I was in need before).
The ROM is not from the Official Website, I took it from a post here I don't remember which post. I'll search and drop it here.
The VOL - trick worked for me.
I never said I booted the TWRP, the phone was in fastboot all the time with .bat command executing the commands.
I'm here for future questions
Hola Sergio Ricardo, no entendí si es oem unlock o local y después los últimos pasos me perdí, podrías explicarlo en español?
sergioricardojsj said:
Dude, I'm just trying to help who wants help (I was in need before).
The ROM is not from the Official Website, I took it from a post here I don't remember which post. I'll search and drop it here.
The VOL - trick worked for me.
I never said I booted the TWRP, the phone was in fastboot all the time with .bat command executing the commands.
I'm here for future questions
Click to expand...
Click to collapse
I was just warning you that the trick as you put it will be nasty one when you or someone else who tries to follow get their phone wiped if they ever boot into twrp.
barrack1 said:
I was just warning you that the trick as you put it will be nasty one when you or someone else who tries to follow get their phone wiped if they ever boot into twrp.
Click to expand...
Click to collapse
He already said he has no TWRP installed and obviously if you're using OTA, you wouldn't have TWRP whilst updating
So does this mean you can't update to january if you have an unlocked bootloader? I had magisk installed in my device, restored image and downloaded the update but it shows installation error. Then after that, I flashed stock pie 9.0 via fastboot from someone who decompiled the payload from OTA and kept bootloader unlocked and tried to update but still it shows as installation error. I have no TWRP installed.
hola,si quieres restaurar la imagen stock para actualizar,as recovery PERO NO EN TWRP y monta la imagen desde ahí, reinicia y listo yo estoy con parche de noviembre que acabo de actualizar y antes de eso tenía magisk con Gcam y mods de audio espero les sirva
Mod edit google translate added:
hello, if you want to restore the stock image to update, as recovery BUT NOT IN TWRP and mount the image from there, restart and ready I am with November patch that I just updated and before that I had magisk with Gcam and audio mods I hope serve them
try n flash original pie fastboot rom from here
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
rexendz said:
He already said he has no TWRP installed and obviously if you're using OTA, you wouldn't have TWRP whilst updating
So does this mean you can't update to january if you have an unlocked bootloader? I had magisk installed in my device, restored image and downloaded the update but it shows installation error. Then after that, I flashed stock pie 9.0 via fastboot from someone who decompiled the payload from OTA and kept bootloader unlocked and tried to update but still it shows as installation error. I have no TWRP installed.
Click to expand...
Click to collapse
Having TWRP installed as the recovery and just booting into TWRP are 2 different things.