[ROM][N6P] Stock ROM 6.0.1 [MMB29M] - Nexus 6P General

STOCK ROM 6.0.1 (MMB29M)
Hello guys, here is the untoched flashable zip for our beloved Angler. This will help peeps who use custom recovery to get their new update.
once again i remind you that this is pure flashable factory image
Instruction :
1. Download ROM and bootloader. Move it in internal storage
2. Boot into TWRP recovery
3. Make Backup
4. Wipe (Dalvik cache, system, data, cache) and Factory reset
5. Flash bootloader
6. Flash zip
7. Reboot​
​

shmshd12 said:
STOCK ROM 6.0.1 (MMB29M)
Hello guys, here is the untoched flashable zip for our beloved Angler. This will help peeps who use custom recovery to get their new update.
once again i remind you that this is pure flashable factory image
Instruction :
1. Download ROM, and move it in internal storage
2. Boot into TWRP recovery
3. Make backup (optional)
4. Wipe (Dalvik Cache , System , data,cache ) and Factory reset
5. Flash zip
6. Reboot​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Does this include new vendor/radio/bootloader partitions?
Thanks

gprovale said:
Does this include new vendor/radio/bootloader partitions?
Thanks
Click to expand...
Click to collapse
radio and bootloader are same as 6.0. i did not include vendor.img

shmshd12 said:
radio and bootloader are same as 6.0. i did not include vendor.img
Click to expand...
Click to collapse
No they're not.
MDB08M bootloader: 2.01
MDB08M radio: 2.15
MMB29M bootloader: 2.45
MMB29M radio: 2.50
Without these and the vendor image this isn't a proper update, nor if it a flashable factory image as you state in the OP. You need to add a disclaimer in the OP that these need to be flashed separately via fastboot, which kinda defeats the purpose doesn't it? They might as well just flash everything via fastboot.

Heisenberg said:
No they're not.
MDB08M bootloader: 2.01
MDB08M radio: 2.15
MMB29M bootloader: 2.45
MMB29M radio: 2.50
Without these and the vendor image this isn't a proper update, nor if it a flashable factory image as you state in the OP. You need to add a disclaimer in the OP that these need to be flashed separately via fastboot, which kinda defeats the purpose doesn't it? They might as well just flash everything via fastboot.
Click to expand...
Click to collapse
@Heisenberg ohk thanks for that info. Ok then i will add radio and bootloader as attachments.

shmshd12 said:
@Heisenberg ohk thanks for that info. Ok then i will add radio and bootloader as attachments.
Click to expand...
Click to collapse
Users will need to flash the vendor image as well, but that's probably too big to add as an attachment here. Beanstown has a flashable version in his Pure Nexus thread, I'd suggest you ask him if it's OK to link to that from here, and give him credit of course.

Heisenberg said:
Users will need to flash the vendor image as well, but that's probably too big to add as an attachment here. Beanstown has a flashable version in his Pure Nexus thread, I'd suggest you ask him if it's OK to link to that from here, and give him credit of course.
Click to expand...
Click to collapse
vendor if Beanstown is from AOSP, so will it make trouble?

shmshd12 said:
vendor if Beanstown is from AOSP, so will it make trouble?
Click to expand...
Click to collapse
His vendor is taken directly from the factory images, the only difference is he made it flashable in recovery. You're both AOSP anyway.

Why is this in General?

Is this rom now ok to flash from twrp now that you've added the new bootloader img?

5. Flash bootloader with twrp ?

Can someone explain to me the purpose of a rom that still requires you to flash something via adb and a computer? Can't we just get a rom with everything needed built in? Love flashing new roms but I usually download and flash via my phone and don't always have a compatible USB type c cable laying around. Is there anyway to update my phone to 6.0.1 without the need of a computer? I'm rooted with twrp recovery on 6.0 the M build if that helps.

I would like to do that too. Wipe dalvik cache, regular cache, and get on my way. Stock everything. Just unlocked bootloader, rooted with supersu 2.5.2

OP should also state whether this will force encryption or not.
Im assuming it will as its "untouched" but this should be clarified.
Sent from my Note 5, Nexus 6P, Note 4 or Nexus 6

I'm still kind of scratching my head with this too. I was under the impression once I unlocked the bootloader and installed TWRP, rooted and have SU permission I could just flash updates without having to wipe my phone every time. I'm really not trying to wipe my phone and then copy over all my pictures and music again.

hustletron said:
I'm still kind of scratching my head with this too. I was under the impression once I unlocked the bootloader and installed TWRP, rooted and have SU permission I could just flash updates without having to wipe my phone every time. I'm really not trying to wipe my phone and then copy over all my pictures and music again.
Click to expand...
Click to collapse
Why would you need to copy over all your pictures etc after wiping and flashing a rom?
Sent from my Note 5, Nexus 6P, Note 4 or Nexus 6

force70 said:
Why would you need to copy over all your pictures etc after wiping and flashing a rom?
Sent from my Note 5, Nexus 6P, Note 4 or Nexus 6
Click to expand...
Click to collapse
Factory reset wipes all your info and data correct? Pictures, music, downloads, etc. Have to copy them back to the phone since there's no removable storage.

hustletron said:
Factory reset wipes all your info and data correct? Pictures, music, downloads, etc. Have to copy them back to the phone since there's no removable storage.
Click to expand...
Click to collapse
Lol, no sir.
A proper twrp wipe is factory reset, then in advanced wipe only cache,dalvik cache,system and data..thats all. This will not remove pics etc
If you format data/wipe internalthat wipes your internal storage clean which is usually not needed for flashing roms.
You have some reading to do, its good to fully grasp how all this works before flashing anything. Props to you for asking in advance, :thumbup:
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4

force70 said:
Lol, no sir.
A proper twrp wipe is factory reset, then in advanced wipe only cache,dalvik cache,system and data..thats all. This will not remove pics etc
If you format data/wipe internalthat wipes your internal storage clean which is usually not needed for flashing roms.
You have some reading to do, its good to fully grasp how all this works before flashing anything. Props to you for asking in advance, :thumbup:
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
Click to expand...
Click to collapse
Well I've been rooting my devices since my Samsung Moment so throwing around the term "wiping" and "factory reset" have a few different meanings to me since the process is obviously different for different phones and has evolved over the years. I just "factory reset" my Galaxy S5 before I sold it and it removed all my personal data to include pictures and music hence why I asked.
If you can' recommend any threads for me to read to help me understand the process with regards to the 6P then by all means.....

hustletron said:
Well I've been rooting my devices since my Samsung Moment so throwing around the term "wiping" and "factory reset" have a few different meanings to me since the process is obviously different for different phones and has evolved over the years. I just "factory reset" my Galaxy S5 before I sold it and it removed all my personal data to include pictures and music hence why I asked.
If you can' recommend any threads for me to read to help me understand the process with regards to the 6P then by all means.....
Click to expand...
Click to collapse
Ah ya one thing, a factory reset with the stock recovery will absolutely wipe the device. Twrp will not...my bad i should have clarified that.
Everything you need should be here.
http://forum.xda-developers.com/showthread.php?p=63049038
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4

Related

[MOD][SCRIPT] Kernel Cleaning Script & Super Wipe Script

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have decided to post the wipe scripts here for those KernelHolics & Flashaholics that are flashing kernels and ROMs constantly. I've made small modifications to these scripts FULL credit to the originator of them Credits below.
These are compatible with TWRP, CWM.
Since there have been numerous kernels recently being posted and people wondering what to wipe or what not to wiped here is the Kernel Cleaner.
1. Place the file in the root of your /sdcard
2. Flash Kernel Cleaner
3. Flash/Fastboot Kernel
4. Reboot.
Download: http://d-h.st/ke1
This second script I'm sure everyone is familiar with SUPERWIPE script.
Tired of wiping after every ROM or not knowing what to wipe to flash a ROM and have a clean install? Just flash this script & flash ROM easy right?
1. Place Wipe-Script in root of /sdcard
2. Flash Wipe-Script
3. Flash ROM
4. Reboot.
5. Wipes System, Cache, Data.
Download: http://d-h.st/qIo
Debug​
If it doesn't flash please tell me what recovery your using.
ONLY works for the DROID DNA flashing this on another device will brick your phone.
Credit goes to the following people.​
Mike1986
AmazingLarry31
Jivy26
I-777
Myself
IF YOU USE/DOWNLOAD THIS SCRIPT PLEASE PRESS THE THANKS BUTTON​
Reserved for more Awesome Scripts
Awesome. Thanks. Will test later today when I get home.
Sent from my ViperDNA
cool,works great Thanks!
Very cool...what does the Kernel Cleaner wipe? I will either Flash GUI or fastboot flash the boot.img file, then boot into recovery, wipe cache, wipe dalvik, mount system then flash the corresponding zip files.
Anything else I should be doing/this script does?
when using the system wipe it will wipe your SD card FYI. Just lost my backups luckly I know about the adb sideload trick to get a rom back on my device to get back up and running. May want to adjust the script to not wipe the location on data that is the SD card (not sure of the xact location )
crackeyes said:
when using the system wipe it will wipe your SD card FYI. Just lost my backups luckly I know about the adb sideload trick to get a rom back on my device to get back up and running. May want to adjust the script to not wipe the location on data that is the SD card (not sure of the xact location )
Click to expand...
Click to collapse
Will update the zip today.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Will update the zip today.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
It is the data/media folder that holds the SD card
crackeyes said:
It is the data/media folder that holds the SD card
Click to expand...
Click to collapse
Yes its cache, system, data. I will make one with just cache, system.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Yes its cache, system, data. I will make one with just cache, system.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
has it been updated
bakemcbride21 said:
Very cool...what does the Kernel Cleaner wipe? I will either Flash GUI or fastboot flash the boot.img file, then boot into recovery, wipe cache, wipe dalvik, mount system then flash the corresponding zip files.
Anything else I should be doing/this script does?
Click to expand...
Click to collapse
i second this.. what does the kernel cleaner wipe actually do?
No most of those programs already wipe. This is only if you fastboot/flash the kernel just like the OP states.
Sent from my HTC One S using Tapatalk 2
So i used the superwipe script in TWRP recovery and immediately after I went into mounts and attempted to mount system. I was going to install CyanogenMOD newest nightly from a clean flash.
Although when I chose mount system my phone rebooted, since there is no OS it obviously stays at the HTC white splash screen. So i hold the power and vol down button get back into bootloader so i can go back into recovery but now my entire SDcard is wiped, gone, no where to be found. At first I am like alright whatever screw it sh*t happens so i move onto to restore a backup of a ROM i have via USB-OTG and now nothing works, I cant boot into OS or recovery, i tried fastboot flash recovery again, and it succeeds both with TWRP and CWM but it never boots into recovery.
I see like the splash screens of the recovery (the teamwin icon and CWM icon but never fully boots) and then it goes into a constant bootloop that never comes out of it.
Help please!
El Ha$on said:
So i used the superwipe script in TWRP recovery and immediately after I went into mounts and attempted to mount system. I was going to install CyanogenMOD newest nightly from a clean flash.
Although when I chose mount system my phone rebooted, since there is no OS it obviously stays at the HTC white splash screen. So i hold the power and vol down button get back into bootloader so i can go back into recovery but now my entire SDcard is wiped, gone, no where to be found. At first I am like alright whatever screw it sh*t happens so i move onto to restore a backup of a ROM i have via USB-OTG and now nothing works, I cant boot into OS or recovery, i tried fastboot flash recovery again, and it succeeds both with TWRP and CWM but it never boots into recovery.
I see like the splash screens of the recovery (the teamwin icon and CWM icon but never fully boots) and then it goes into a constant bootloop that never comes out of it.
Help please!
Click to expand...
Click to collapse
Follow the unbricking thread. Specifically my posts to get you back up and running.
Skip right to the part where you flash "ROM.zip", check md5, in fastboot. This will restore your to stock and you can start over.
If you have the eng hboot or a custom splash screen you may have to flash the original parts if the flash doesn't take.
Pay any attention to errors while flashing. I don't follow the DNA much so hit me up in pm if you need help.
thanks a lot
Doesn't work on TWRP 2.5 !
Hi there ,
I have Htc DNA . installed custome recovery TWRP ... flashing Kernel cleaner works! BUT flashing superwipe.zip Doesn't work ! (gives [email protected]).
Can you please help ?!
One another question : how to format phone with twrp ? i have one option "wipe" ... as written there it will wipe everything needed by sliding ?! I do that but seems something still not wiped !? cause phone has crashes ... I would prefer CWM! (better and simple).
BY the way in TWRP i have in wiping partions ... something like "OTG USB " ?? WTF ? what's this that i can't wipe ?!
Thanks for help .

Problem, help needed!!!

i was doing swap in my, phone.
i restart phone, and i cant boot a system.
i went to the recovery and wiped sdcard, cache, data , just everything.
i installed new rom, but i still cant boot system.
Can someone help me?
TheHardew said:
i was doing swap in my, phone.
i restart phone, and i cant boot a system.
i went to the recovery and wiped sdcard, cache, data , just everything.
i installed new rom, but i still cant boot system.
Can someone help me?
Click to expand...
Click to collapse
Total lack of details firmware etc please post what and where and why .
Dont use such stupid sized fonts .
[READ THlS FlRST] POST QUESTIONS IN THE Q&A SECTION AND NOT HERE!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
siayh kernel
ultima rom XXEMC3
philz recovery 4 cwm based 6.3.0.1
i was making swap to expand my ram
yeasterday about eight oclock PM
did you tried to go back to previous ROM or stock ROM ?
Yea, i installed new rom from recovery and i boot animation cant start. i have still screen samsung galaxy s3.
when i installed rom from odin boot animation starts, im waiting, restart and again.
Im also was tring to restore my backub but i didnt change anything
marbedMB pozdrawiam
Now i restored system from backup and bootanimation cant end. it is still flashing and flashing.
But i think im on the right way
Can you link us to the page you got the instructions and script for swap off please, also try flashing a stock rom then wipe data from stock recovery.
Sent from my GT-I9300 using Tapatalk 2
i was using app Root Swapper Extend Memory
i was tring that.
i installed rom from recovey, from odin, restored system from backup
actualy boot animation starts and cant end
You should look into how you write an informative title. "Problem, help needed" doesn't really describe what you need help with.
But i dont now hot to do this
Did you use the swap file or choose a swap partition?
Sent from my GT-I9300 using Tapatalk 2
i used swap file 256 mb but on sdcard i saw that that file has only 32 mb
i deleted that file from recovery menu
any ideas?
im flashing XXEMC3 stock rom thru odin and bootanimation is starting, ending and restarting after thet im restoring system from backup and i bootanimation cant end
when i restored boot from backup boot animation couldnt start
If you used a swap file there is no reason for the phone to bootloop after flashing stock rom, a data wipe and formatting the SD card (data wipe in stock recovery automatically formats the SD card)
Sent from my GT-I9300 using Tapatalk 2
but im using philz cwm based 6.0.3.2
TheHardew said:
but im using philz cwm based 6.0.3.2
Click to expand...
Click to collapse
If you had tried a stock rom you would have flashed stock recovery it's why I said flash it THEN wipe data. You can wipe SD card by going to mounts and storage and format /sdcard.
Sent from my GT-I9300 using Tapatalk 2
ok i do that i do factory reset and wipe cashe but still the same problem
TheHardew said:
ok i do that i do factory reset and wipe cashe but still the same problem
Click to expand...
Click to collapse
Format /sdcard?
If that doesn't solve it, I don't think you are telling us everything reflashed a rom should be enough to fix problems, worst case a data wipe will be needed.
Sent from my GT-I9300 using Tapatalk 2
i wiped anything.
I dont now how i do that. Maybe i have to try to install another rom thru odin
TheHardew said:
i wiped anything.
I dont now how i do that. Maybe i have to try to install another rom thru odin
Click to expand...
Click to collapse
Here is what I would do in this order exact order:
Wipe data through recovery
format /sdcard in recovery (in CWM touch, mounts and storage format /sdcard)
restore a nandroid backup or flash a custom rom
flash a stock rom through Odin
wipe data again through stock recovery (flashed when you flash any stock rom)
Be sure to check it's fixed after each step, and it should solve 99% of all software based problems.
Also if you recieve any errors tell us exactly what they say, otherwise we are shooting in the dark.

Honor 5x restarting repeatedly after installing Cyanogenmod 13(Snapshot)

Hey there,
I'm having repeated restarts after installing Cyanogenmod 13 (Snapshot) on my honor 5x, let me put you through the steps I followed.
First I unlocked my bootloader using adb/fastboot.
then flashed custome recovery(TWRP)
rooted my phone using SuperSU from TWRP
placed CM 13 and open gApps zip files on SD card
rebooted in recovery mode(TWRP)
selected wipe and swipe
then click on install
selected CM 13 zip file from SD card
swipe to flash
after process completed
wipe Dalvik/cache
then click on install
selected gApps zip file
swipe to flash
and then reboot
then when the phone reboots my phone shows the default honor boot screen and then Cyanogenmod boot screen
and then the phone restarts with a vibration
and keeps on repeating the process untill I restore my TWRP backup
Also I tried only installing CM 13(No gApps-thought it might be interrupting the system) and reboot
and installing gApps and clearing cache/dalvik and then reboot
I tried it many times but still the same issue
Please help me
swapnilVtiwari said:
Hey there,
I'm having repeated restarts after installing Cyanogenmod 13 (Snapshot) on my honor 5x, let me put you through the steps I followed.
First I unlocked my bootloader using adb/fastboot.
then flashed custome recovery(TWRP)
rooted my phone using SuperSU from TWRP
placed CM 13 and open gApps zip files on SD card
rebooted in recovery mode(TWRP)
selected wipe and swipe
then click on install
selected CM 13 zip file from SD card
swipe to flash
after process completed
wipe Dalvik/cache
then click on install
selected gApps zip file
swipe to flash
and then reboot
then when the phone reboots my phone shows the default honor boot screen and then Cyanogenmod boot screen
and then the phone restarts with a vibration
and keeps on repeating the process untill I restore my TWRP backup
Also I tried only installing CM 13(No gApps-thought it might be interrupting the system) and reboot
and installing gApps and clearing cache/dalvik and then reboot
I tried it many times but still the same issue
Please help me
Click to expand...
Click to collapse
I Think you should only Wipe Dalvik/Cache after you install both The Rom and the Gapps... Just install at the same time (The Rom and Gapps)
And Factory reset your System before you install the cynogen and gapps
Milupi said:
I Think you should only Wipe Dalvik/Cache after you install both The Rom and the Gapps... Just install at the same time (The Rom and Gapps)
And Factory reset your System before you install the cynogen and gapps
Click to expand...
Click to collapse
Milupi said:
I Think you should only Wipe Dalvik/Cache after you install both The Rom and the Gapps... Just install at the same time (The Rom and Gapps)
And Factory reset your System before you install the cynogen and gapps
Click to expand...
Click to collapse
What do you mean by installing both at the same time, do you mean selecting both zip files at once?
Also I factory reset my phone before I install cyanogen mod from within twrp and had my phone factory reset before rooting.
Also I've tried to install cm and gapps one by one and wiping dalvik/cache after both of them.
Please help
swapnilVtiwari said:
What do you mean by installing both at the same time, do you mean selecting both zip files at once?
Also I factory reset my phone before I install cyanogen mod from within twrp and had my phone factory reset before rooting.
Also I've tried to install cm and gapps one by one and wiping dalvik/cache after both of them.
Please help
Click to expand...
Click to collapse
Yes selecting both zips at the same time
Milupi said:
Yes selecting both zips at the same time
Click to expand...
Click to collapse
Do I need to factory reset again and Will this revoke my root access.
I'm asking this because of a reason...let me tell you what I've done.
I factory reset my phone, and then made a nandroid backup using twrp, then I flashed superSU using twrp, installed root checker biscuit said root access is installed properly. Then installed cm 13 and gapps, when that didn't worked, I restored my nandroid backup that I made before rooting, and when I checked from root checker, it was saying the phone is not rooted.
swapnilVtiwari said:
I factory reset my phone, and then made a nandroid backup using twrp, then I flashed superSU
Click to expand...
Click to collapse
You made a nandroid backup before root so when you restore it is not rooted ( normal ).
What version of stock do you have before flashing cm13 ? If b360, you have bootloop, under b360 shall be no issue.
What i do to flash:
1/ wipe factory reset
2/ advance wipe cache,dalvik,system,data
3/ install ROM
4/ install gapps (arm64)
5/ wipe dalvik/cache
6/ reboot system
To have root, you need to flash supersu ( after gapps ) or alone after first setup of ROM and gapps.
But most of ROM have root built inside, just need to go to options for dev under settings and select app for root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my KIW-L21 using XDA-Developers mobile app
rodolphe06 said:
1/ wipe factory reset
2/ advance wipe cache,dalvik,system,data
3/ install ROM
4/ install gapps (arm64)
5/ wipe dalvik/cache
6/ reboot system
Click to expand...
Click to collapse
I did as you say, but still the same...it's restarting repeatedly.
swapnilVtiwari said:
I did as you say, but still the same...it's restarting repeatedly.
Click to expand...
Click to collapse
Have you thought of trying another rom ?
Zakaria.R said:
Have you thought of trying another rom ?
Click to expand...
Click to collapse
No, because I think there are no other final builds, and I just wanted to try cyanogen mod and waited for the snapshot build because I don't want to have trouble with my phone as this is my main phone.
swapnilVtiwari said:
No, because there are no other final builds, and I just wanted to try cyanogen mod and waited for the snapshot build because I don't want to have trouble with my phone as this is my main phone.
Click to expand...
Click to collapse
You do know that the other roms share the same sources as cm13 right ? And that a snapshot isn't that more stable than the other roms, it's pretty much a placebo effect,anyway your phone, your call.
R
Zakaria.R said:
You do know that the other roms share the same sources as cm13 right ? And that a snapshot isn't that more stable than the other roms, it's pretty much a placebo effect,anyway your phone, your call.
Click to expand...
Click to collapse
Can you name any other custom Rom that is as good as cyanogen mod and has final stable builds.
And why do you say placebo effect, aren't snapshots the stable builds?
swapnilVtiwari said:
Can you name any other custom Rom that is as good as cyanogen mod and has final stable builds.
And why do you say placebo effect, aren't snapshots the stable builds?
Click to expand...
Click to collapse
There's the final build of RR or crdroid or any other you really should try yourself and see because like I said they all share the same sources
as for what I said about the snapshot, yeah it is stable and is supposed to be bug-free but what I mean is at this point every other rom is as much stable as that snapshot, try by yourself and see.
​
Zakaria.R said:
There's the final build of RR or crdroid or any other you really should try yourself and see because like I said they all share the same sources
as for what I said about the snapshot, yeah it is stable and is supposed to be bug-free but what I mean is at this point every other rom is as much stable as that snapshot, try by yourself and see.
Click to expand...
Click to collapse
I checked both RR and cRdroid download page, they don't seem to have builds for honor 5x.
swapnilVtiwari said:
I checked both RR and cRdroid download page, they don't seem to have builds for honor 5x.
Click to expand...
Click to collapse
They are in the development section of honor 5x, what are you using to check xda ?
Zakaria.R said:
They are in the development section of honor 5x, what are you using to check xda ?
Click to expand...
Click to collapse
My phone, I restored the nandroid backup I made using twrp.
Could you please share links for cRdroid and resurrection remix download page.
swapnilVtiwari said:
My phone, I restored the nandroid backup I made using twrp.
Could you please share links for cRdroid and resurrection remix download page.
Click to expand...
Click to collapse
I meant which app, but here you go http://forum.xda-developers.com/honor-5x/development you can find any rom you like, it's the "roms and Kernels" section for honor 5x
Zakaria.R said:
I meant which app, but here you go http://forum.xda-developers.com/honor-5x/development you can find any rom you like, it's the "roms and Kernels" section for honor 5x
Click to expand...
Click to collapse
Not using any app, just my phone's browser.
And thank you so much for the links, but most of them links say they're unofficial, and as I said earlier I just can't afford to have trouble as this is the only phone I have.
I really appreciate your help, but I can't take risk as I'm not very much into android development.
Sorry if I bothered you.
I really appreciate your help...but I hope you could help me with my cm13 issue.
swapnilVtiwari said:
Not using any app, just my phone's browser.
And thank you so much for the links, but most of them links say they're unofficial, and as I said earlier I just can't afford to have trouble as this is the only phone I have.
I really appreciate your help, but I can't take risk as I'm not very much into android development.
Sorry if I bothered you.
I really appreciate your help...but I hope you could help me with my cm13 issue.
Click to expand...
Click to collapse
Brother don't be afraid, what matters is the absence of bugs not the tags "official" or "unofficial" your are not gonna break your device (unless you are doing something stupid) and if you want an example to be assured just look at all the users in XDA, they are all rocking nightly builds on their phone, some of them use "betas" and some others use even "alphas" so don't let that Stop you, and if you have a nandroid backup what would you lose ? If you don't like it you get back to your stock rom, don't let your fear prevent you from the sweetness of custom roms.
Hey buddies,
I m currently using kiw-l22,
I installed twrp, but when I flash any custom rom,
I have the same problem as discussed above,
it would be great if I get some help
Appy punia said:
Hey buddies,
I m currently using kiw-l22,
I installed twrp, but when I flash any custom rom,
I have the same problem as discussed above,
it would be great if I get some help
Click to expand...
Click to collapse
Were you on volte firmware before coming to custom rom??

[RECOVERY][c70n][OFFICIAL] TWRP for LG Spirit H440N

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download & Installation (assuming, you've unlocked the bootloader following Korelev's instructions)
1) Download and open the Official TWRP App from the Play Store
2) Select TWRP flash
3) "Select device" > "LG Spirit LTE (H440N) -- c70n" > select the latest image available
4) When the image is downloaded, return to the app and "select a file to flash". Select the downloaded image and tap "Flash to recovery"
5) Reboot to recovery
You're in TWRP!
NOTE: To boot into recovery with hardware buttons use this method. Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally. This is because LG phones are a bit different and they instruct the recovery (TWRP in this case) to automatically perform a factory reset of the phone by triggering the /misc wipe flag. I mapped /misc partition to a different partition (/pad) so TWRP doesn't perform a factory reset.
BUGS:
battery indicator (sometimes)
Some features were untested, but the most important ones seem to work just fine. As I'm pretty unexperienced with this, help from other devs would be greatly appreciated. If you come up with an improved version of my build, let me know and I'll edit the OP ASAP.
XDA: DevDB Information
[RECOVERY]Official TWRP for LG Spirit H440N, Device Specific App for the LG Spirit H440N
Contributors
Fobos531
Device tree: https://github.com/TeamWin/android_device_lge_c70n
Version Information
Status: Stable
Thanks to:
@midzan21
@Korelev
@pvineeth97
@cerg2010cerg2010
If I've left anyone out, please let me know. I'm new to this too
Created 2017-02-27
Last Updated 2017-03-24
CHANGELOG
#1 2017-02-27 - first build
#2 2017-02-27 - screen timeout bug fixed
#3 2017-03-02 - fixed booting into recovery with hardware buttons, you can now do that normally
#4 2017-03-11 - TWRP 3.1.0 released, check the changelog here
It's already starting!!! Actual development for our old but still good Spirit! :,-)
Is this the desire twrp? I think you should post it at kernerls recoveries and development subforum instead of the guides one. Good work!
Korelev said:
Is this the desire twrp? I think you should post it at kernerls recoveries and development subforum instead of the guides one. Good work!
Click to expand...
Click to collapse
the base is from Moto G 3rd gen.
Yeah, my bad. I'll leave it here for now.
fixed screen timeout bug, redownload the recovery from OP
I'll give it a try tonight
Make sure you flashed the c70n_recovery3.img(I forgot to update the link till today) recovery image since that's latest one with all fixes so far.
New build up, download: https://drive.google.com/open?id=0B4VJbV8vBFHadllaM2EyY3hVMk0
Check post #2 for changelog
Another build up, download from the OP.
The difference between this build and the one in post #9 is that in post #9 I used a dirty hack that told TWRP to ignore the /misc wipe flag when booting into TWRP with hardware buttons on LG phones. In the newest build I removed that hack and instead the mapped the /misc partition to a different partition (/pad) so the factory reset doesn't occur. The reason this was needed is because, with the previous build, if we had LineageOS and tried to do a factory reset in the system, it wouldn't work because of the hack I used. Now the factory reset will work when performing a factory reset on (future) custom ROMs.
@Fobos531: Hi, just wanted to tell you that the latest TWRP didn't seem do what the OP says. If I understood correctly, the intended behaviour on stock roms should have been to ignore the factory reset commands and just boot up TWRP for normal use.
When I selected yes for the second time, to confirm a factory reset, TWRP booted executing some kind of a script (forgot the exact name), and never gave me a chance to stop it. After that it rebooted. It technically performed a factory reset, only using TWRP to do it.
Did I misunderstand something in your explanation? I'm running stock MM, installed using Korelev's zip.
Alanon said:
@Fobos531: Hi, just wanted to tell you that the latest TWRP didn't seem do what the OP says. If I understood correctly, the intended behaviour on stock roms should have been to ignore the factory reset commands and just boot up TWRP for normal use.
When I selected yes for the second time, to confirm a factory reset, TWRP booted executing some kind of a script (forgot the exact name), and never gave me a chance to stop it. After that it rebooted. It technically performed a factory reset, only using TWRP to do it.
Did I misunderstand something in your explanation? I'm running stock MM, installed using Korelev's zip.
Click to expand...
Click to collapse
Can you specify the exact name of the "latest" TWRP you're referring to? I flashed the exact TWRP that is currently in the OP and booting into TWRP with hardware keys works completely fine for me. I encountered this script you're referring to as well, but that was when I was using an older version of the build. The newest image that I built shouldn't do that.
If there are more issues, feel free to send me a PM in your native language. I speak it so we should be fine.
I pretty much flashed them in order of appearance, closely following your posts. If I remember correctly, the first was called recovery.img, then there was c70n_recovery.img, and finally twrp.img, which was the last one I flashed. The only memory I have is of these names, and I have a twrp.img in a folder on my PC. The file attributes, like the time of creation, match.
If I didn't flash the latest twrp, I still must have flashed the build with the previous factory reset hack, which still doesn't explain what happened. The only explanation I can think of is that that somehow Flashify didn't really overwrite the existing twrp?
Anyways, It's not all that big a deal, since I boot to recovery from the OS in 90% of the cases, and ADB is always there as a backup solution. This was really about testing to see if it worked, for if and when this was the only option. I've already reflashed the twrp from the first post, but I'd really hate to have to go through another factory reset in search of confirmation. I just got the apps sorted again. xD
Alanon said:
I pretty much flashed them in order of appearance, closely following your posts. If I remember correctly, the first was called recovery.img, then there was c70n_recovery.img, and finally twrp.img, which was the last one I flashed. The only memory I have is of these names, and I have a twrp.img in a folder on my PC. The file attributes, like the time of creation, match.
If I didn't flash the latest twrp, I still must have flashed the build with the previous factory reset hack, which still doesn't explain what happened. The only explanation I can think of is that that somehow Flashify didn't really overwrite the existing twrp?
Anyways, It's not all that big a deal, since I boot to recovery from the OS in 90% of the cases, and ADB is always there as a backup solution. This was really about testing to see if it worked, for if and when this was the only option.
Click to expand...
Click to collapse
If you've indeed flashed the build with the previous factory reset hack, you may have left out the "cd /cache/recovery, echo '--show_text' etc." steps. I suppose they have to be done every time a build is flashed.
I've already reflashed the twrp from the first post, but I'd really hate to have to go through another factory reset in search of confirmation. I just got the apps sorted again. xD
Click to expand...
Click to collapse
Fine, no problem, the only unfortunate thing that could happen is if you were to flash a custom ROM and it would bootloop, you wouldn't have much chance of properly getting into recovery (since it would execute that wipe script AFAIK) and you wouldn't be able to flash the recovery through fastboot either so it's worth getting the recovery right, at least before flashing custom ROMs.
Remember, you can always make a Nandroid backup of your ROM in TWRP and then test if you can boot into TWRP with hardware buttons, and if factory resets the phone, you can have it set up like before by restoring the backup in TWRP.
how to boot into twrp recovey with key.?
when i go to twrp recovery my phone going to auto reset.
i install marshmellow rom with twrp.
plz help
inoxentrajaa said:
how to boot into twrp recovey with key.?
when i go to twrp recovery my phone going to auto reset.
i install marshmellow rom with twrp.
plz help
Click to expand...
Click to collapse
Make sure you flashed the latest TWRP (link is in the original post) using the procedure described in the original post.
To boot into TWRP recovery with hardware keys:
Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally
Click to expand...
Click to collapse
TWRP 3.1.0 is released, download from the OP, changelog in second post
inoxentrajaa said:
how to boot into twrp recovey with key.?
when i go to twrp recovery my phone going to auto reset.
i install marshmellow rom with twrp.
plz help
Click to expand...
Click to collapse
use adb its better way
adb reboot recovery
fobos531 said:
twrp 3.1.0 is released, download from the op, changelog in second post
Click to expand...
Click to collapse
thanks bro
inoxentrajaa said:
thanks bro
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B4VJbV8vBFHaUmREejFjeUpUZ1k

Redmi Note 4X bootloop

Welcome, I have Xiaomi Redmi Note 4X Global. I've had my new phone for a week. Right after the first boot I updated it to MIUI 9, unlocked bootloader, installed root, exposed etc.
Everything was working fine without any problems. Today I wanted to try something new and I installed Resurrection Remix OS. Before it I took a backup with TWRP (through PC, I got backup.ab)
I was using the new rom for a few hours but then I realised that I preferred MIUI and I restored previously made backup (backup.ab). And here came the problems.
The device after restore came into a bootloop. Xiaomi logo appeared for a few seconds, then a single vibration, restart and the same again. After this I flashed (with MiFlash) a stock
firmware for my device from [url]http://en.miui.com/a-234.html[/URL] (the right one for sure) "Redmi Note 4X Latest Global Stable Version Fastboot"
Flashing through PC has always helped to unbrick devices but I don't know why in this case it didn't.
I can still enter fastboot mode and recovery so I flashed TWRP, made a full wipe with it, and installed:
-Resurrection Remix OS
-LineageOS
-recovery zip versions of MIUI (many versions)
After installing each of those I get the same result, a bootloop. I spent rhe last hours of trying everything in different combinations and looking for any information.
Can anyone help me with this problem, has anyone even faced something like that?
Pr3z3s said:
Welcome, first of all I have Xiaomi Redmi Note 4X Global. I've had my new phone for a week. Right after the first boot I updated it to MIUI 9, unlocked bootloader, installed root, exposed etc.
Everything was working fine without any problems. Today I wanted to try something new and I installed Resurrection Remix OS. Before it I took a backup with TWRP (through PC, I got backup.ab)
I was using the new rom for a few hours but then I realised that I preferred MIUI and I restored previously made backup (backup.ab). And here came the problems.
The device after restore came into a bootloop. Xiaomi logo appeared for a few seconds, then a single vibration, restart and the same again. After this I flashed (with MiFlash) a stock
firmware for my device from http://en.miui.com/a-234.html (the right one for sure) "Redmi Note 4X Latest Global Stable Version Fastboot"
Flashing through PC has always helped to unbrick devices but I don't know why in this case it didn't.
I can still enter fastboot mode and recovery so I flashed TWRP, made a full wipe with it, and installed:
-Resurrection Remix OS
-LineageOS
-recovery zip versions of MIUI (many versions)
After installing each of those I get the same result, a bootloop. I spent rhe last hours of trying everything in different combinations and looking for any information.
Can anyone help me with this problem, has anyone even faced something like that?
Click to expand...
Click to collapse
Well, try this method :
Download firmware.zip, Amy custom Rom, and Gapps.
Next, boot to TWRP and wipe (advanced wipe ~) wipe everything except internal storage or SD card.
Flash firmware.zip, followed by Rom and Gapps, Reboot.
Link to firmware : https://androidfilehost.com/?fid=673791459329068624 (credits to zile995)
Sent from my Redmi Note 4 using Tapatalk
sachin n said:
Well, try this method :
Download firmware.zip, Amy custom Rom, and Gapps.
Next, boot to TWRP and wipe (advanced wipe ~) wipe everything except internal storage or SD card.
Flash firmware.zip, followed by Rom and Gapps, Reboot.
Link to firmware : https://androidfilehost.com/?fid=673791459329068624 (credits to zile995)
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice but after following your instructions and the result stays the same.
Pr3z3s said:
Thank you for your advice but after following your instructions and the result stays the same.
Click to expand...
Click to collapse
Did you flash any mods after installing Rom?
Sent from my Redmi Note 4 using Tapatalk
sachin n said:
Did you flash any mods after installing Rom?
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I didn't.
Pr3z3s said:
I didn't.
Click to expand...
Click to collapse
If I recall right, I've had this same issue. So, do one thing download Recovery flashable Xiaomi stock miui Rom or download Xiaomi EU Rom, then as I said earlier boot to TWRP once again, wipe, advanced wipe > wipe everything > install stock miui > lazyflasher.zip >reboot. Lemme know how it goes.
LazyFlasher : https://www.androidfilehost.com/?fid=529152257862700328
Flash lazyflasher.zip if you flash any miui Roms other than Xiaomi eu Rom before reboot.
sachin n said:
If I recall right, I've had this same issue. So, do one thing download Recovery flashable Xiaomi stock miui Rom or download Xiaomi EU Rom, then as I said earlier boot to TWRP once again, wipe, advanced wipe > wipe everything > install stock miui > lazyflasher.zip >reboot. Lemme know how it goes.
LazyFlasher : https://www.androidfilehost.com/?fid=529152257862700328
Flash lazyflasher.zip if you flash any miui Roms other than Xiaomi eu Rom before reboot.
Click to expand...
Click to collapse
I did exactly as you said, wiped everything, installed stock MIUI recovery version and lazyflasher.
No errors appeared but when I wanted to reboot my phone after installation I got an information that
no OS was installed.
I swiped right anyway to reboot and here comes the bootloop again. :/
EDIT: Tried with both stable and developer versions
-miui_HMNote4XGlobal_V9.0.5.0.NCFMIEI_d6176de291_7.0.zip
-miui_HMNote4XGlobal_7.12.21_9a89725dfc_7.0.zip
EDIT:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also get those errors (?) while mounting during installation.
It's red themed because I was currently using Red Wolf Recovery but I get the same results when I use cofface TWRP or original TWRP
Pr3z3s said:
I did exactly as you said, wiped everything, installed stock MIUI recovery version and lazyflasher.
No errors appeared but when I wanted to reboot my phone after installation I got an information that
no OS was installed. I swiped right anyway to reboot and here comes the bootloop again. :/
Click to expand...
Click to collapse
Holy crAp. Alright, I'm no expert with fastboot Rom or so, did you try flashing fastboot Rom? Give it a go... :c
BTW, there's a device team guide on mi forum about flashing Redmi Note 4/4x : http://en.miui.com/thread-482304-1-1.html
Sent from my Redmi Note 4 using Tapatalk
sachin n said:
Holy crAp. Alright, I'm no expert with fastboot Rom or so, did you try flashing fastboot Rom? Give it a go... :c
BTW, there's a device team guide on mi forum about flashing Redmi Note 4/4x : http://en.miui.com/thread-482304-1-1.html
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I already tried installing fastboot ROMs with Miflash and it always says "succes" in the end but the phone is in bootloop anyway after I turn it on :/
Pr3z3s said:
I already tried installing fastboot ROMs with Miflash and it always says "succes" in the end but the phone is in bootloop anyway after I turn it on :/
Click to expand...
Click to collapse
Ohk. I'm outta answers now.
Hang on, did you try installing with TWRP? I see redwolf. What about Twrp? Try it once
sachin n said:
Ohk. I'm outta answers now. I hope someone like @Zile995 can help you regarding this.
Click to expand...
Click to collapse
Thanks for trying anyway.
Pr3z3s said:
Thanks for trying anyway.
Click to expand...
Click to collapse
See my edit.
*Did you try flashing Rom with TWRP? I See redwolf. Give it a go with TWRP once.
Pr3z3s said:
I did exactly as you said, wiped everything, installed stock MIUI recovery version and lazyflasher.
No errors appeared but when I wanted to reboot my phone after installation I got an information that
no OS was installed.
I swiped right anyway to reboot and here comes the bootloop again. :/
Click to expand...
Click to collapse
Did you just "wipe" everything, or did you "format data" also? I suggest that you format the data partition (there is a button for this under the "Wipe" menu in TWRP), and then install your ROM again.
You need to install lazyflasher only once - after installing a custom Recovery. - but -you must do this each time you change your custom Recovery (but only do it once) - otherwise, MIUI will not boot correctly. Note that you do not need lazyflasher if you are using a custom ROM (eg, AOSP, etc).
I had a similar issue after installing Resurrection Remix then trying to go back to MIUI.
I used MiFlash to install a stable rom but got a boot loop after reboot.
In the end I flashed a stable rom using Miflash using the 'clean all' option. Then without rebooting I installed TWRP via adb. Booted straight into TWRP and installed the no_verify .zip. Then used TWRP to restore a nandroid backup I had on an OTG USB drive. It then booted without bootlooping. So I used Miflash to reinstall the stable rom with 'clean all' option again. Rebooted ok like a brand new phone.
Sent from my Redmi Note 4 using Tapatalk
I join the cause
Hi, I join the cause @ Pr3z3s. I have tried everything. And I still have the same problem. the only thing that occurs to me is that someone gives us a backup, please do upload it, and we try to restore it in our mobile.
can you tell me what kind of unable to mount or unmount errors you encounter when flashing? my guess is that some of your partition is corrupted
sachin n said:
See my edit.
*Did you try flashing Rom with TWRP? I See redwolf. Give it a go with TWRP once.
Click to expand...
Click to collapse
Yes, I tried maybe 4 different recoveries for my device.
DarthJabba9 said:
Did you just "wipe" everything, or did you "format data" also? I suggest that you format the data partition (there is a button for this under the "Wipe" menu in TWRP), and then install your ROM again.
You need to install lazyflasher only once - after installing a custom Recovery. - but -you must do this each time you change your custom Recovery (but only do it once) - otherwise, MIUI will not boot correctly. Note that you do not need lazyflasher if you are using a custom ROM (eg, AOSP, etc).
Click to expand...
Click to collapse
I did both many times. When it comes to lazyflasher I did flash it but didn't help.
Spukey said:
I had a similar issue after installing Resurrection Remix then trying to go back to MIUI.
I used MiFlash to install a stable rom but got a boot loop after reboot.
In the end I flashed a stable rom using Miflash using the 'clean all' option. Then without rebooting I installed TWRP via adb. Booted straight into TWRP and installed the no_verify .zip. Then used TWRP to restore a nandroid backup I had on an OTG USB drive. It then booted without bootlooping. So I used Miflash to reinstall the stable rom with 'clean all' option again. Rebooted ok like a brand new phone.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Tried that, same result :/
chun_9876 said:
can you tell me what kind of unable to mount or unmount errors you encounter when flashing? my guess is that some of your partition is corrupted
Click to expand...
Click to collapse
Those on the second screen I put in the previous page of this thread, like unmount of /firmware failed; no such volume
EDIT: I just tried restoring .ab backup through adb and an error while restoring EFS partition occurred so I flashed a stable ROM with MiFlash and took a backup of EFS partition.
Then I restored my backup again and after an error with EFS I restored it from a backup I had just taken - no errors appeared. Then I flashed lazyflasher and rebooted and still I'm in a bootloop.
Pr3z3s said:
Yes, I tried maybe 4 different recoveries for my device.
I did both many times. When it comes to lazyflasher I did flash it but didn't help.
Tried that, same result :/
Those on the second screen I put in the previous page of this thread, like unmount of /firmware failed; no such volume
EDIT: I just tried restoring .ab backup through adb and an error while restoring EFS partition occurred so I flashed a stable ROM with MiFlash and took a backup of EFS partition.
Then I restored my backup again and after an error with EFS I restored it from a backup I had just taken - no errors appeared. Then I flashed lazyflasher and rebooted and still I'm in a bootloop.
Click to expand...
Click to collapse
here you go, my /firmware and /efs nandroid backup, seems like you have some trouble with efs as well so i included it , and to clarify things, my device is redmi note 4x MIDO 3gb/32gb edition running on cardinal aosp 5.1.1 12/10 with global miui v9.0.3.0 firmware, dont restore backup if you have a different edition because i don't know what will happen to your device . https://drive.google.com/open?id=1a8-tjbrkV8vNKaWcBsClbVlvBADinXSB
EDIT : I'm not confident that this will fix your device because it seems that either your /firmware is corrupted, or somehow disappeared .. do tell your results though , dont blame me if it becomes a hard brick ><
chun_9876 said:
here you go, my /firmware and /efs nandroid backup, seems like you have some trouble with efs as well so i included it , and to clarify things, my device is redmi note 4x MIDO 3gb/32gb edition running on cardinal aosp 5.1.1 12/10 with global miui v9.0.3.0 firmware, dont restore backup if you have a different edition because i don't know what will happen to your device . https://drive.google.com/open?id=1a8-tjbrkV8vNKaWcBsClbVlvBADinXSB
EDIT : I'm not confident that this will fix your device because it seems that either your /firmware is corrupted, or somehow disappeared .. do tell your results though , dont blame me if it becomes a hard brick ><
Click to expand...
Click to collapse
Thank you for sharing your backup but I get errors while restoring it.
EDIT: All partitions seem to be present when I go to "Backup" section. What is more, I got the same error with EFS when I was trying to restore my orignal backup.
Pr3z3s said:
Thank you for sharing your backup but I get errors while restoring it.
Click to expand...
Click to collapse
i removed my link because it seems that efs might contain device sensitive info like my IMEI and mac addresses, so dont restore my efs backup,it seemed to ended up spitting an error though. anyways, it seems that you are on TWRP , i backup-ed using redwolf, so that might result in the error, and yeah, dont restore my efs partition next try

Categories

Resources