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??
Related
Is Samsung Galaxy S5 G900T a KLTE handset? cannot seem to find anything related to T-mobile S5
nht48823 said:
Is Samsung Galaxy S5 G900T a KLTE handset? cannot seem to find anything related to T-mobile S5
Click to expand...
Click to collapse
Yes it is
from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.1.1 DOB1 with Resurrection Remix ROM v5.5.6
jt1998 said:
Yes it is
from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.1.1 DOB1 with Resurrection Remix ROM v5.5.6
Click to expand...
Click to collapse
I'm trying to flash cyanogenmod from twrp but getting error 7 , can't flash over incompatible system data. I'm on t mobile sm-g900t and downloaded the latest klte snapshot...
Help please.
Dorsant said:
I'm trying to flash cyanogenmod from twrp but getting error 7 , can't flash over incompatible system data. I'm on t mobile sm-g900t and downloaded the latest klte snapshot...
Help please.
Click to expand...
Click to collapse
Trying to flash cm 12 rom right? It's a zip? Checked md5 to ensure good download?
I'd update to latest twrp 3.0 first. Make a backup of current rom/setup.
Are you trying clean or dirty flash?
Sent from my SM-G900T using Tapatalk
jt1998 said:
Trying to flash cm 12 rom right? It's a zip? Checked md5 to ensure good download?
I'd update to latest twrp 3.0 first. Make a backup of current rom/setup.
Are you trying clean or dirty flash?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Not sure how to check if md5 download was good, but there were no interruptions so I believe it was.
And what is clean vs dirty flash? I downloaded the only "snapshot" version that was on the klte downloads page directly to my phone. Rebooted into twrp recovery, selected zip file, swipe to flash. Then I get the error. Looks like file name says CM 12.1-20115007....
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Thanks
Dorsant said:
And what is clean vs dirty flash?
Click to expand...
Click to collapse
Make a backup, then wipe system, data, cache, and dalvik before flashing the ROM. It helps prevent bugs
Dorsant said:
Thanks for the reply. Not sure how to check if md5 download was good, but there were no interruptions so I believe it was.
And what is clean vs dirty flash? I downloaded the only "snapshot" version that was on the klte downloads page directly to my phone. Rebooted into twrp recovery, selected zip file, swipe to flash. Then I get the error. Looks like file name says CM 12.1-20115007....
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Thanks
Click to expand...
Click to collapse
This is the Cm 12.1 ROM I'd use for your device https://download.cyanogenmod.org/get/jenkins/129251/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
You'll need an android 5.0 lollipop gapps also which allows you to use your ROM with google apps, play store functionality, etc. This is the one I'd use for your device. https://basketbuild.com/filedl/devs...gapps-modular-micro-5.1.1-20150927-signed.zip
Once both are downloaded onto your phone storage, make sure you backup 1st in TWRP so if anything goes wrong you're ok.
Clean flash means you're wiping system, data, dalvik, and cache before installing new ROM/Gapps - always reccommended if you're coming from stock touchwiz a different non CM rom.
Dirty flash means you only wipe dalvik and cache typically b/c you're just updating your current ROM with a newer version of same ROM so no need to wipe data/system but it is the first thing to evaluate if your device has errors like force closures, bugginess, etc.
Also, after you've wiped your device and now are ready to install your ROM and gapps, do both zip installs in one step. so add the ROM, then add another zip which will be your gapps, then swipe to flash having 2 zips in your queue. Then when all is done, reboot and let your device install. Sign in setup your accounts and profit.
Let me know how it goes ok! Hit thanks for me please!!
jt1998 said:
This is the Cm 12.1 ROM I'd use for your device https://download.cyanogenmod.org/get/jenkins/129251/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
You'll need an android 5.0 lollipop gapps also which allows you to use your ROM with google apps, play store functionality, etc. This is the one I'd use for your device. https://basketbuild.com/filedl/devs...gapps-modular-micro-5.1.1-20150927-signed.zip
Once both are downloaded onto your phone storage, make sure you backup 1st in TWRP so if anything goes wrong you're ok.
Clean flash means you're wiping system, data, dalvik, and cache before installing new ROM/Gapps - always reccommended if you're coming from stock touchwiz a different non CM rom.
Dirty flash means you only wipe dalvik and cache typically b/c you're just updating your current ROM with a newer version of same ROM so no need to wipe data/system but it is the first thing to evaluate if your device has errors like force closures, bugginess, etc.
Also, after you've wiped your device and now are ready to install your ROM and gapps, do both zip installs in one step. so add the ROM, then add another zip which will be your gapps, then swipe to flash having 2 zips in your queue. Then when all is done, reboot and let your device install. Sign in setup your accounts and profit.
Let me know how it goes ok! Hit thanks for me please!!
Click to expand...
Click to collapse
Perfect! Great explanation, worked perfectly!
Dorsant said:
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Click to expand...
Click to collapse
there's little reason to use an old & insecure version at this point, i've ONLY used a few nightlies, the bugs were usually minor & you can get the fixes pretty much as soon as they come out rather than waiting months
deep sleep battery use & the camera app are greatly improved in CM13
http://www.cmxlog.com/13/klte/ changelogs
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
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Dileter said:
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Click to expand...
Click to collapse
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
Yes I am rooted and I tried flashing this ROM http://forum.xda-developers.com/lg-g5/development/unofficial-cyanogenmod-14-1-lg-g5-h850-t3494001
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
I also dont really care if I lose photos or anything I already got all of them saved on my pc before I even started rooting the damn thing. I do need to ask tho how do you dirty flash and Do i just flash twrp normally since im already in it or ??? As I said im rlly new to this
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
DidierMoulin said:
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
Click to expand...
Click to collapse
Okay thanks a lot I will see if Any of it helps.
Please report.
DidierMoulin said:
Please report.
Click to expand...
Click to collapse
UPDATE I fixed it I just downgraded to the 2nd to lates version of twrp and it booted normally. Now I regret flashing the pixel one XDD If you have any idea for a good custom rom tell me Thanks for the help it actually helped a lot gave me the idea to downgrade the twrp recovery.
What you mean by pixel one xxd?
DidierMoulin said:
What you mean by pixel one xxd?
Click to expand...
Click to collapse
Its a 7.1.1 android rom from the google pixel
Dileter said:
Its a 7.1.1 android rom from the google pixel
Click to expand...
Click to collapse
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Pphish20 said:
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Click to expand...
Click to collapse
What he asked [emoji32]
It's happened to me too! Like three times lol. Just use UpperCut / LG UP to flash the latest nougat rom. That will fix the issue. You will need to re-root after that. There are instructions in this forum that tell how to do all of that. Good luck
Well and don't flash a ROM which is not for your device...
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
So, I have updated lineageOs through TWRP.
I wipe dalvik, system and cache.
I flash latest rom and reflash Gapps then magisk but then it's bootloop.
I'm using lineageOs before, but I want to update it to latest rom and this is happening.
I tried many ways like flash lazyflasher etc. but no use, the problem is still happen.
So I have my phone unrooted now.
Please, help me to solve this problem, how can I root my phone? I'm still noob at this things.
PS:
lineageOs version : 15.1-20180611-NIGHTLY-mido
pandip said:
So, I have updated lineageOs through TWRP.
I wipe dalvik, system and cache.
I flash latest rom and reflash Gapps then magisk but then it's bootloop.
I'm using lineageOs before, but I want to update it to latest rom and this is happening.
I tried many ways like flash lazyflasher etc. but no use, the problem is still happen.
So I have my phone unrooted now.
Please, help me to solve this problem, how can I root my phone? I'm still noob at this things.
Click to expand...
Click to collapse
You would be really helpful if you were more specific about which version of lineage you flashed!
David_#27 said:
You would be really helpful if you were more specific about which version of lineage you flashed!
Click to expand...
Click to collapse
lineageOs version : 15.1-20180611-NIGHTLY-mido.
I download it from it's official site.
pandip said:
lineageOs version : 15.1-20180611-NIGHTLY-mido.
I download it from it's official site.
Click to expand...
Click to collapse
From here: https://download.lineageos.org/mido, right?
pandip said:
So, I have updated lineageOs through TWRP.
I wipe dalvik, system and cache.
I flash latest rom and reflash Gapps then magisk but then it's bootloop.
I'm using lineageOs before, but I want to update it to latest rom and this is happening.
I tried many ways like flash lazyflasher etc. but no use, the problem is still happen.
So I have my phone unrooted now.
Please, help me to solve this problem, how can I root my phone? I'm still noob at this things.
PS:
lineageOs version : 15.1-20180611-NIGHTLY-mido
Click to expand...
Click to collapse
You need a special TWRP for Treble if you want to flash Magisk. It's all linked and discussed in the LineageOS thread.
Also, when coming from an old or unofficial LineageOS build, you need to do a full wipe (System, Data, Cache, Dalvik and Vendor).
David_#27 said:
From here: https://download.lineageos.org/mido, right?
Click to expand...
Click to collapse
yea it's from there, it's an official site, isn't it ?
Noter2017 said:
You need a special TWRP for Treble if you want to flash Magisk. It's all linked and discussed in the LineageOS thread.
Also, when coming from an old or unofficial LineageOS build, you need to do a full wipe (System, Data, Cache, Dalvik and Vendor).
Click to expand...
Click to collapse
I did a full wipe even it's an official lineageOs but the problem is still exist.
I reflash all stuff like gsi vendor mido treble, gapps, kernel and boom, the problem is stand still.
pandip said:
yea it's from there, it's an official site, isn't it ?
Click to expand...
Click to collapse
Yes exactly! After downloading the ROM and flashing it from recovery you will notice that it is treble rom(apart from the message: "patching system image unconditionally..." You will also see a message: "Patching vendor image...")! So you need two things to download:
1) Custom TWRP for treble ROMs.
2) Custom Magisk for treble ROMs.
David_#27 said:
Yes exactly! After downloading the ROM and flashing it from recovery you will notice that it is treble rom(apart from the message: "patching system image unconditionally..." You will also see a message: "Patching vendor image...")! So you need two things to download:
1) Custom TWRP for treble ROMs.
2) Custom Magisk for treble ROMs.
Click to expand...
Click to collapse
I just download magisk custom from the lineageOs's thread and flash it then it's succesfully installed a.k.a. no bootlooping anymore.
Maybe I should reads the threads carefully before execute next time.
Wow thanks a lot man, you helped me.
Same problem
Hi there, I'm having the same bootloop problem. Could you show me the thread you got the magisk from?
So first of all I would really recommend you to grab this TWRP: https://sourceforge.net/projects/orangefox/files/mido/ (all credits go to orangefox developers and you can find them here: https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933)
Download the latest R7 zip because it supports now all kinds of roms (treble, non-treble and Android P!)
Now go and download the magisk from here: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
First rom then gapps custom kernel(optional) last flash magisk. If you encounter any issues with magisk then wipe everything flash rom gapps and kernel if u want boot your phone to system reboot to recovery and flash magisk.