Tutorial on how to update firmware and install newer custom ROM - Xiaomi Redmi Note 5 Pro Questions & Answers

After losing several days now knowing the exact steps and files needed to upgrade from my 6 month old AOSP Extended custom ROM to the latest version, I present you this tutorial
Latest ROM you can install without updating your firmware is
Code:
AospExtended-v6.5-whyred-20190527-0118-OFFICIAL.zip
If you read the changelog of
Code:
AospExtended-v6.6-whyred-20190609-1902-OFFICIAL.zip
it says that new TWRP and firmware is required. Download both firmware and TWRP and place them on microSD card and insert it into the phone. First boot with the old firmware and "v6.4" version took 1 minute. First boot with the newest mentioned firmware and "v6.7" also took 1 minute. If it takes more then that or if you don't see AEX logo spinning 10 seconds after Mi logo, something is wrong.
How to enter into TWRP: hold Volume up + Power while phone is turned off. Once you feel the vibrations and Mi logo appears release the Power button and hold the Volume up for 10 seconds. Release after TWRP logo appears.
I had problems with both Windows 10 and Linux on my computer so I used USB 2.0 port on old Windows 7 laptop. This is how I did it. Maybe some steps are redundant.
1. Don't touch anything and wait around 8 seconds. Unplug USB cable from the phone after completion. Notice new look of TWRP.
Code:
C:\adb>fastboot boot recommended-twrp-3.3.1-1-whyred
downloading 'boot.img'...
OKAY [ 0.827s]
booting...
OKAY [ 0.140s]
finished. total time: 0.998s
(2a.) While inside the new TWRRP, install recommended-twrp-3.3.1-1-whyred.img Return. Return. Return. Reboot. Shutdown. Turn on phone. Don't touch any button. It will reboot a few times and go into fastboot. Step 2a is useless because this way doesn't install TWRP permanently (it actually deletes TWRP).
2b. Once temporarely booted into 3.3.1-1 after step 1, Install required new MIUI firmware without ZIP signature check.
3. (Install new ROM.) Reboot again into bootloader/recovery.
4.
Code:
fastboot flash recovery recommended-twrp-3.3.1-1-whyred
5.
Code:
fastboot reboot
& unplug USB cable from the phone. twrp-3.3.1-1 should be permanently installed.
6. Go to Wipe and do: 1. Swipe to Factory reset 2. Format Data 3. Advanced Wipe (select Dalvik / ART Cache) and cache). You can then install new ROM :good:

Related

[Help] Broken Defy

Last chance i see to save my phone is by posting here...
So, what i did:
1. Downloaded and installed ClockworkMod 2.5.1.8 (com.kb7sqi.defy.boostrap.old.apk)
2. Made a full BackUp (stored on PC and SD-Card)
3. Wipe data/factory reset + Wipe cache
4. Selected "CyanogenMod 7"-ROM for install
5. Install succeded -> chose "Reboot"
6. Defy stuck at Boot-Loop for like 30 Mins.
7. Removed battery -> held volume down + power button
8. NO ClockworkMod showed up ... instead "Android system recovery <2e>" shows up
9. Wipe data/factory reset + wipe cache doesn't do anything at all
10. only other options are "reboot system now" (, which got me stuck at Boot-Loop again) and "apply sdcard:update.zip" (where do i have to get the update.zip?)
So, i tried to connect my Defy via USB (installed Motorola Defy USB-Drivers and RSD Lite (tried 4.7+, 4.9 and 5.0). None of the RSD Lite Versions could recognize my phone while it's in "Android system recovery <2e>". So i can't "flash" a stock-rom (sbf-Files)...
I tried downloading an update.zip (CookieCutter ROM i found in another forum) and placed the file in the root-directory of my SD-Card. When i chose "apply sdcard:update.zip" i get the Errors:
"E: failed to verify whole-file signature
E: signature verification failed
Installation aborted."
So please, i need your help... how can i save my phone and put it back into the old state? ... thanks in advance
Quick Edit:
I managed to get into "BootLoader" by holding volume up-button, but as soon as it starts it says "Battery Low - Cannot Program" and exits... i charged my defy for hours... "should" be no problem... if it even charges correctly, i don't know... if i connect it via USB to charge it, i got a white light and black screen... nothing seems to charge at all...
I think there is only one thing you can do: http://forum.xda-developers.com/showthread.php?t=892026
You defy is not bricked.
But in the state your device is, it cannot charge the battery.
You need to charge the battery with another phone or charger in order to flash an sbf with RSD lite.
Or you can try this hack: http://forum.xda-developers.com/showthread.php?t=892026
It was worked form me some time ago...
Thanks for the hope, i'll try this workaround tomorrow, hope it goes well.
So when i actually get the BootLoader working my PC and therefore RSD Lite should recognize my phone and then i just can flash my device with any official .sbf and it works? And when it's flashed i can reinstall ClockworkMod and install my old backup? :X
Do not be afraid. Your Defy is not briked. What should you do after you manage to charge your phone, if your battery is to low:
1) boot it in stock recovery (Vol Down + Power); the Android with a exclamation mark will appear on the screen; you'll have to press both volume buttons (if you had froyo)/press the right lower corner on the screen(if you previously had eclair)
2) wipe data/factory reset, wipe cache and dalvik cache
3) restart your phone in bootloader (Vol Up+ Power)
4) connect it to your pc and start RSD Lite 4.9
5) Flash the SBF with RSD Lite (choose one from this topic, maybe you can find there the version that was on your Defy before you tried to put CM7, you might find there also other useful tips)
To install CM7 you need to upgrade your software to Froyo, if you are on Eclair, then install 2nd Init v1.4.2 from this topic and then install CM7. It won't work without 2nd Init and kb7sqi recovery mod doesn't have also the 2nd Init modules. However before upgrading to CM7 you can read this topic as there you'll find all the steps required to install CM7.
You should borrow another battery or charge using desktop charger first.
Try wipe data & cache first from stock recovery. If it doesn't make any change, you can try flash with full sbf. Once had this problems too. Solved with full sbf flash + wipe data & cache.
Good News, i got it charged with the trick and successfully installed the stock ROM via RSD Lite. But now i always get "MD5 mismatch!"-Error when i want to restore my backup created with Clockworkmod :S...
Check if your folder, where the nandroid is stored, contains any spaces in the name. If so remove the spaces.
Yeah, i already did that and tried to fix it with:
# cd /sdcard/clockworkmod/backup/2011-05-23.16.30.06
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse
but without success... :S
Solved Battery Low Cannot program
pull ur battery out and put in and connect it with wall cherger motorola original.!
that's done.
works for me//
hit thnx. for me
Hi,
I have exactly the same problem but my phone USB-port really doesnt work.
I managed to put the orig. Froyo and changeged the bootlogo but did a mistake with erasing CWM. Now the Defy is stuck in Bootloop.
I can only reach the Bootloader and the Android Recovery System.
I need a working update.zip to flash the phone via SD-card.
Start over again follow forum rds lite sfb flash then root again
Sent from my MB525 using xda premium
o_Honk said:
Hi,
I have exactly the same problem but my phone USB-port really doesnt work.
I managed to put the orig. Froyo and changeged the bootlogo but did a mistake with erasing CWM. Now the Defy is stuck in Bootloop.
I can only reach the Bootloader and the Android Recovery System.
I need a working update.zip to flash the phone via SD-card.
Click to expand...
Click to collapse
On stock recovery do a full wipe it should get you out the boot loop
mckarty said:
On stock recovery do a full wipe it should get you out the boot loop
Click to expand...
Click to collapse
I have similar problem. I stuck in boot loop. I am able to go into stock recovery and did a data wipe & cache wipe. Still I am in boot loop. RSDlite also does not shows my phone. Tried in several PCs with different USB cable. But no luck. If there is a possibility to flash stock rom with update.zip, please help me with update.zip. Any help is appreciated. Thanks!

Issue with reinstall CyanogenMod 12 Latest Release Galaxy Note 2 - Reboot loop TWRP

Good Day,
Thanks for taking the time to read my posting.
I am running a Galaxy Note 2 with TWRP v2.8.7.0. Previously, had been running CyanogenMod 12 Latest Release from 2015-11-17.
Had an issue with the phone rebooting, went into TWRP to clear Cache/Davlik Cache, seen an error after this with /Data partition not being mounted(phone was encrypted). Proceeded to go into TWRP and Format Data then reinstall the ZIP listed above from an external SD card, successfully completed installation of ZIP file for CyanogenMod 12. When I reboot the device from TWRP, through Reboot->System, keeps rebooting back into TWRP and not into CyanogenMod.
I have connected the device to a Windows computer, confirmed that I can see it connected through USB. When I issue abd devices, I see the ##### recovery listed for the device, but if I issue fastboot devices, no device is listed.
Any recommendations for what could be done to reinstall the CyanogenMod build on my device so that it can boot properly would be greatly appreciated.
Thanks to everyone on the community for the support, education and feedback over the years and for all the hard work that you do, cheers to you.
Maybe flash back to a completely stock rom, confirm that everything works, flash twrp, and cm again?
I was thinking about recovery to stock recovery when I read your post .
Tried the stock recovery using Odin3-v3.07 pointing to CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.tar.md5(1/20/2015), this appeared to complete from Odin, but the phone still went into a reboot loop into CyanogenMod, but never fully started up, thereafter.
Went to the autoroot.chainfire.eu site, downloaded the latest stock recovery for device.
Pulled the battery, back into TWRP, select Wipe/Factory reset from TWRP. Installed Samsung Kies onto desktop, ran Odin3-v3.10.6 pointing AP to CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.tar.md5 dated from 3/31/2016. Then went to phone and go to download mode (turn off first, press and hold following buttons: vol down + home + power). Then Press Up Volume key to get into Download mode, then connect it to PC via USB. Device shown in Odin under ID:COM. On Option uncheck “Repartition”. After reboot, phone boot into IMG for CyanogenMod. Confirmed access to phone thereafter.
Thanks for the feedback, hope this helps someone down the line, if they run into the same issue.

No OS installed : Not able to shutdown & enter twrp.

I was trying to install Iron rom https://forum.xda-developers.com/galaxy-tab-s/development/stock-tw-rom-galaxy-tab-s-8-4-t2995235
and followed the below steps as mentioned in the installation document of roms thread..
1. Download the rom and put it to your SD card or internal storage
2. Download latest bootloader and modem for SM-T705 and bootloader only for SM-T700
3. Boot into download mode, download latest Odin available and flash BL in BL tab and CP in CP tab
4. Make sure you use most recent TWRP which can be found T705 or T700
5. Flash TWRP with odin in AP tab
6. Boot into recovery using: home+power on + volume up
7. Select wipe, advanced wipe: data, cache, dalvik-cache and system
8. Install the rom (in aroma select "dirty flash", otherwise you may have problems!)
9. After rom installation reboot and wait around 20 minutes till the tab boots up
10. Enjoy MM on your Tab S!
I followed steps 1 to 7 successfully. When I tried step 8 it said "Failed to map file IronRom_SM-T70X_V3.2.zip" in external sd card.
Now when pressed rebooted it warned that "No OS is installed."
After rebooting its stuck in the boot screen with "powered by android logo. I pressed power button for 1 min and still tab is not shutting down.
Questions
1) How to do shutdown the tab & reboot to twrp?
2) How do i fix the "Failed to map file IronRom_SM-T70X_V3.2.zip" issue and install IronRom_SM-T70X_V3.2.zip?
3) Atleast how to enter into download mode so that I ca at least install stock rom?
Please help!
Thanks
mrcet007 said:
I was trying to install Iron rom https://forum.xda-developers.com/galaxy-tab-s/development/stock-tw-rom-galaxy-tab-s-8-4-t2995235
and followed the below steps as mentioned in the installation document of roms thread..
1. Download the rom and put it to your SD card or internal storage
2. Download latest bootloader and modem for SM-T705 and bootloader only for SM-T700
3. Boot into download mode, download latest Odin available and flash BL in BL tab and CP in CP tab
4. Make sure you use most recent TWRP which can be found T705 or T700
5. Flash TWRP with odin in AP tab
6. Boot into recovery using: home+power on + volume up
7. Select wipe, advanced wipe: data, cache, dalvik-cache and system
8. Install the rom (in aroma select "dirty flash", otherwise you may have problems!)
9. After rom installation reboot and wait around 20 minutes till the tab boots up
10. Enjoy MM on your Tab S!
I followed steps 1 to 7 successfully. When I tried step 8 it said "Failed to map file IronRom_SM-T70X_V3.2.zip" in external sd card.
Now when pressed rebooted it warned that "No OS is installed."
After rebooting its stuck in the boot screen with "powered by android logo. I pressed power button for 1 min and still tab is not shutting down.
Questions
1) How to do shutdown the tab & reboot to twrp?
2) How do i fix the "Failed to map file IronRom_SM-T70X_V3.2.zip" issue and install IronRom_SM-T70X_V3.2.zip?
3) Atleast how to enter into download mode so that I ca at least install stock rom?
Please help!
Thanks
Click to expand...
Click to collapse
When press all the buttons ie. power +volume up +volume down+home its showing the battery charging screen even though the tab is not plugged in.
So since tab is still not shutdown i am not able to try to boot to recovery.
Please guide.
Power volume - and home button should get you in to download mode so you can flash a stock rom......

zs570kl deluxe - android not starting - help!

hello,
i hade no root and an original asus firmware on the phone.
when i start the phone I get the message to enter the security pattern.
after entering the safety pattern android should start.
the screen reads ASUS IN SEARCH OF INCREDIBLE and underneath the dots rotate in a circle.
This remains so until the battery is empty.
What can I do?
When pressing Power and Volume Up comes:
Fastboot Mode!!!
Batterien Capacity: 89%
ASUS
but can not do anything else just switch off again.
When pressing Power and Volume Up comes:
Fastboot fashion !!!
Batteries Capacity: 89%
ASUS
but can not do anything else just switch off again.
When pressing Power and Volume Down comes:
The android male lying on his back with a red triangle and a call sign
and underneath is No command.
after some time (minutes) the screen returns with the input of the security pattern ......
Are there any other keyboard shortcuts that might help me?
I'm a beginner - so I do not know me so well - so I need a step by step guide
Hopefully someone can help me
sorry for my bad english
In recovery mode (Power+Volume down) press power+volume up to see the menu and do a factory reset.
Hi,
when pressing Power and Volume Down comes:
The android male lying on his back with a red triangle and a call sign
and underneath is No command.
but i can not do anything else - there comes no menu - for the factory reset!
I need help - please.
When you see the lying android do as i told and press power+volume up button. When you release the volume button you will see the recovery menu.
Hi Dabiolos,
Thanks alot. After a few attempts, I managed to get into the recovery menu.
Here is an entry Wipe data/factory reset.
My question - what is after the factory reset - are all my data ( phptos ) gone?
If so - is there any other way to save the photos?
Is it possible with Apply update from ADB - install the firmware new - so that the system boots again - but the phptos are still there?
Thank you
After factory reset everything on the phone will be wiped.
There is a way/solution to apply an rom install over adb. But i guess you never used ADB and making a mistake like using the wrong files could result in a brick i dont recommend it.
If you got an sd card you could just download the rom from asus and apply update from zip. Triple check for the right file....
If you absolutely need your photos and no sd: It is easier using fastboot and booting twrp-recovery and backup your pictures over MTP/USB.
For this just boot into fastboot connect your device to usb (on a pc with fastboot installed).
Just follow this tutorial (the test part).
https://forum.xda-developers.com/ze...covery-twrp-recovey-zenfone-3-deluxe-t3681354
After backup factory reset.
Hi,
first i tried to apply update the original asus firmware from sd card
the same as i have/had on the phone UL-Z016_1-WW-5.17.44.87-user.zip
This worked fine - but the problem was the same.
Then i tried an older version UL-Z016_1-WW-5.17.44.68-user.zip
Finding update package...
Opening update package...
Verifying update package ...
Update package verification took 94.7 s (result 0 ).
header.flash_count: 34
header.current_entry_index: 33
Installing update...
Device image Version:
7.0
OTA image ersion: 7.0
Only Android 6.0.1(newer than 20161227 version) or Android 7.0 (older version) can upgrade to this version
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
then i tested this:
fastboot devices
it shows me my device ( number and fastboot )
after i tried the twrp-image file:
fastboot boot twrp-3.2.1-0-Z016-20180304.img
here i got the following messages:
downloading 'boot.img'...
OKAY [ 0.594s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.616s
so i cant'n install the twrp-image file!
Is it possible in my situation to unlock the device?
I found a recovery imge ( Z016_1-WW-5.17.44.87_recovery.img ) for my phone.
What cani do with this image? - Can this help me?
Or is the only way to do a factoty reset - and lose my photos on the phone?
Thank you
Unlocking für bootloader will wipe your data. So this is not an option.
The new recovery wont help either.
Better try this:
https://forum.xda-developers.com/showthread.php?t=2339530

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.
Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps
mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.

Categories

Resources