Related
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
First flash this file and then Rom. That's right?? Or its other way around
karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..
Wouldn't this procedure downgrade some performance on the device?
Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs
Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk
puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..
snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk
it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)
Hey everyone! I have a weird problem. I have rooted my Honor 5C NEM-L21 but everytime i try to flash a custom rom it gets bootlooped. I have tried multiple different roms and formatting /data as f2fs , yet have the same problem everytime that i flash a custom ROM. I have as well everytime downgraded the OS back to EMUI 4 and updated the OS to EMUI 5 but it does not help with the problem. Does anyone have any idea what might cause this problem? Thanks
onnz423 said:
Hey everyone! I have a weird problem. I have rooted my Honor 5C NEM-L21 but everytime i try to flash a custom rom it gets bootlooped. I have tried multiple different roms and formatting /data as f2fs , yet have the same problem everytime that i flash a custom ROM. I have as well everytime downgraded the OS back to EMUI 4 and updated the OS to EMUI 5 but it does not help with the problem. Does anyone have any idea what might cause this problem? Thanks
Click to expand...
Click to collapse
Don't use the original TWRP
AlexMihai26 said:
Don't use the original TWRP
Click to expand...
Click to collapse
I have used HassanMirza01's TWRP everytime when flashing, that should be the correct one right?
onnz423 said:
I have used HassanMirza01's TWRP everytime when flashing, that should be the correct one right?
Click to expand...
Click to collapse
It should be,it depends if you want to flash one of his roms.I'm using Lineage with the latest TWRP and it's working .
AlexMihai26 said:
It should be,it depends if you want to flash one of his roms.I'm using Lineage with the latest TWRP and it's working .
Click to expand...
Click to collapse
Yeah, not sure what im doing wrong then. Maybe i should try to reflash the kernel after flashing the ROM. This phone is pretty painful to mod if you ask me
onnz423 said:
Yeah, not sure what im doing wrong then. Maybe i should try to reflash the kernel after flashing the ROM. This phone is pretty painful to mod if you ask me
Click to expand...
Click to collapse
I have the same problem, i tried it several times but never worked. I gave up and instaled OctRom form felix-development after all...
onnz423 said:
Yeah, not sure what im doing wrong then. Maybe i should try to reflash the kernel after flashing the ROM. This phone is pretty painful to mod if you ask me
Click to expand...
Click to collapse
Try the stock kernel.I did that to make Lineage work,or you could try first to install elite rom then the rom that you want.
Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
About
This is Unofficial mod rom for adding tweaks , I will work on a making this full user friendly for mido , plus adding another latest features which are not officially supported to LOS
How To Flash
1.Make a BACKUP of current boot,data and system partition first partition using TWRP.
2. Wipe system,data,dalvik and cache.
3.Flash the ROM.
4.Flash the Gapps.
5.Reboot
Download:
ROM
GAPPS
Credits & Thanks:
LineageOS team
ResurrectionRemix team
crDroid team
And all other open source Devs/Teams I may have missed!
Pipaolo
SamarV
Dhiraj
Sandeep Sethi
Adam Belamri
Good job sir, work fine for me
First of all, many thanks for developing a ROM for this device.
As far as feedback can go though : I've tried installing this rom over and over again but without luck.
I tried flashing the rom (with and without gapps) on TWRP 3.1.1 as well as TWRP 3.2.2.0. Every time I get the boot screen (Moto powered by android) with the usual warning about the phone being unlocked, then the warning goes away and the boot screen just hangs there without any indication of anything happening on the screen.
Device : XT1663
Stock ROM : Moto-M_XT1663_S378_180503_ROW Android 7
facing same problem
me too facing exactly same issue
As far as feedback can go though : I've tried installing this rom over and over again but without luck.
I tried flashing the rom (with and without gapps) on TWRP 3.1.1 as well as TWRP 3.2.2.0. Every time I get the boot screen (Moto powered by android) with the usual warning about the phone being unlocked, then the warning goes away and the boot screen just hangs there without any indication of anything happening on the screen.
Device : XT1663
Stock ROM : Moto-M_XT1663_S378_180503_ROW Android 7 [/QUOTE]
Phone is stuck at moto logo after flashing the rom
CJ2311 said:
First of all, many thanks for developing a ROM for this device.
As far as feedback can go though : I've tried installing this rom over and over again but without luck.
I tried flashing the rom (with and without gapps) on TWRP 3.1.1 as well as TWRP 3.2.2.0. Every time I get the boot screen (Moto powered by android) with the usual warning about the phone being unlocked, then the warning goes away and the boot screen just hangs there without any indication of anything happening on the screen.
Device : XT1663
Stock ROM : Moto-M_XT1663_S378_180503_ROW Android 7
Click to expand...
Click to collapse
Pls try this version and tell me if u face same issue or not
http://adambelamri.eu/MOTO_M/Rom/Releases/Los/lineage-14.1-20180811-UNOFFICIAL-XT1663.zip
Thanks
ahmadmemon said:
me too facing exactly same issue
As far as feedback can go though : I've tried installing this rom over and over again but without luck.
I tried flashing the rom (with and without gapps) on TWRP 3.1.1 as well as TWRP 3.2.2.0. Every time I get the boot screen (Moto powered by android) with the usual warning about the phone being unlocked, then the warning goes away and the boot screen just hangs there without any indication of anything happening on the screen.
Device : XT1663
Stock ROM : Moto-M_XT1663_S378_180503_ROW Android 7
Click to expand...
Click to collapse
[/QUOTE]
Pls try this version and tell me if u face same issue or not
http://adambelamri.eu/MOTO_M/Rom/Releases/Los/lineage-14.1-20180811-UNOFFICIAL-XT1663.zip
Thanks
Swaraj Kumar said:
Phone is stuck at moto logo after flashing the rom
Click to expand...
Click to collapse
Pls try this version and tell me if u face same issue or not
http://adambelamri.eu/MOTO_M/Rom/Releases/Los/lineage-14.1-20180811-UNOFFICIAL-XT1663.zip
Thanks
blitzfire3 said:
Pls try this version and tell me if u face same issue or not
http://adambelamri.eu/MOTO_M/Rom/Releases/Los/lineage-14.1-20180811-UNOFFICIAL-XT1663.zip
Thanks
Click to expand...
Click to collapse
Tried this version and I have the same problem.
Is there any way we could maybe help? By providing certain files or something?
CJ2311 said:
Tried this version and I have the same problem.
Is there any way we could maybe help? By providing certain files or something?
Click to expand...
Click to collapse
well Look like something happen with the source btw did u try the old version of los?
if not here is the link Los 14.1 Test 1
blitzfire3 said:
well Look like something happen with the source btw did u try the old version of los?
if not here is the link Los 14.1 Test 1
Click to expand...
Click to collapse
I have tried lineage-14.1-20180702-UNOFFICIAL-XT1663.zip, if that's what you're referring to.
CJ2311 said:
I have tried lineage-14.1-20180702-UNOFFICIAL-XT1663.zip, if that's what you're referring to.
Click to expand...
Click to collapse
Try the new one i uploaded yesterday and tell me the result
blitzfire3 said:
Try the new one i uploaded yesterday and tell me the result
Click to expand...
Click to collapse
Currently just flashed that file, and I got past the motorola logo screen, but now I seem to be having a bootloop. I'll leave it be for an hour or so then I'll try to reinstall again if it doesn't work still.
CJ2311 said:
Currently just flashed that file, and I got past the motorola logo screen, but now I seem to be having a bootloop. I'll leave it be for an hour or so then I'll try to reinstall again if it doesn't work still.
Click to expand...
Click to collapse
Did u get any further? Waiting for your feedback.
Yes plz post a review on this ROM
blitzfire3 said:
Try the new one i uploaded yesterday and tell me the result
Click to expand...
Click to collapse
Thapagaurav said:
Did u get any further? Waiting for your feedback.
Click to expand...
Click to collapse
[email protected] said:
Yes plz post a review on this ROM
Click to expand...
Click to collapse
Sadly, I've kept getting a bootloop on the new build no matter what. Tried reinstalling several times, with and without gapps/superSU but no luck.
CJ2311 said:
Sadly, I've kept getting a bootloop on the new build no matter what. Tried reinstalling several times, with and without gapps/superSU but no luck.
Click to expand...
Click to collapse
there is some problem with the rom i will look at it
@CJ2311 thanks for testing and really appreciate the feedbacks. I have a question about your Moto M, are you experiencing the battery drain as well? like once it reaches to 50% or below it'll immediately drain to 2% in just 1-2 minutes or so?
@blitzfire3 thank you so much for your time developing LOS 14.1 as I'm really looking forward to getting it if this battery drain issue won't be addressed as it seems Lenovo/Motorola doesn't plan to anyway...
blitzfire3 said:
there is some problem with the rom i will look at it
Click to expand...
Click to collapse
Any bugs is there in this rom lineage-14.1-20180825-UNOFFICIAL-XT1663.zip ?
SeishiNui18 said:
@CJ2311 thanks for testing and really appreciate the feedbacks. I have a question about your Moto M, are you experiencing the battery drain as well? like once it reaches to 50% or below it'll immediately drain to 2% in just 1-2 minutes or so?
Click to expand...
Click to collapse
Sounds like you might have a defective unit.
Personally for me it's quite the opposite, the phone holds the entire day easily, and I can often make it last 2 days. Whenever I get the battery low warning it'll keep running for quite a while in standby or light use, and even when I get the "battery level critical, phone shutting down in 30 seconds" warning, it only shuts down after 5 minutes or more... D:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
florian-m19 said:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
Click to expand...
Click to collapse
I think yes, but I'm not sure
Was wondering the same thing, does anyone know if the red magic 3 is A only or an A/B device. I'm pretty sure it's A only, but I couldn't find any documentation online.
Its A only i think.
Hum... So Project Treble should work ?
That is interesting !
If I could install Resurrection Remix to this device and provided everything works it would become really almost perfect.
If anyone wants to try... If not I'll do it myself when I have time (in 2 or 3 days)...
Regards.
If the device has treble support, meaning a vendor partition it should work no problem, a/b partitioning is really not required for treble.
I tested treble using fastboot, since twrp had some issues, but it resulted in a bootloop and a corrupted recovery partition. I managed to fix it by following: https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
Twrp gave me a mounting error for
/system_root, which is fixable by setting system to be read-only and then rebooting the recovery and re enableing read/write. Have not had the time to test using twrp and treble yet.
*I posted earlier in the day but managed to fix all the issues I had, so this a better summary :silly:
trepKep said:
I tested treble using fastboot, since twrp had some issues, but it resulted in a bootloop and a corrupted recovery partition. I managed to fix it by following: https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
Twrp gave me a mounting error for
/system_root, which is fixable by setting system to be read-only and then rebooting the recovery and re enableing read/write. Have not had the time to test using twrp and treble yet.
*I posted earlier in the day but managed to fix all the issues I had, so this a better summary :silly:
Click to expand...
Click to collapse
So, this means its not working.. Sad Story.
florian-m19 said:
So, this means its not working.. Sad Story.
Click to expand...
Click to collapse
Well not necessarily, since I flashed the lineageos gsi through fastboot. (That may be the issue) I was having issues with twrp. I will try again today, although the chances are slim.
trepKep said:
Well not necessarily, since I flashed the lineageos gsi through fastboot. (That may be the issue) I was having issues with twrp. I will try again today, although the chances are slim.
Click to expand...
Click to collapse
U should clear user data and cache after installing new system if you have bootloop problem
Make sure its A only GSI
em902566 said:
U should clear user data and cache after installing new system if you have bootloop problem
Make sure its A only GSI
Click to expand...
Click to collapse
I'll keep that in mind
trepKep said:
I'll keep that in mind
Click to expand...
Click to collapse
Hey, did you try it again?
florian-m19 said:
Hey, did you try it again?
Click to expand...
Click to collapse
No, I was busy. But I'm trying right now
Treble Attempt #2
No luck, everything flashed with no errors, but all I get is more than 10 minutes of black screen. I also tried flashing magisk right after the gsi finished, same result.
trepKep said:
Treble Attempt #2
No luck, everything flashed with no errors, but all I get is more than 10 minutes of black screen. I also tried flashing magisk right after the gsi finished, same result.
Click to expand...
Click to collapse
Hmm then we must wait for a custom Rom..
florian-m19 said:
Hmm then we must wait for a custom Rom..
Click to expand...
Click to collapse
Yeah, a one plus 7 pro port would be nice
florian-m19 said:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
Click to expand...
Click to collapse
Word of advice. Do not attempt to flash anything on this cell. You will regret it. I tried to flash TWRP over 6 weeks ago an it's been dead ever since. Even a cellphone repair center guy could not repair it.
You need to leave good enough alone.
People all around the world have been stuck in permanent recovery screens or fastboot screens like me.
It really is a very good cell the way it is ?
Bryceicle1971 said:
Word of advice. Do not attempt to flash anything on this cell. You will regret it. I tried to flash TWRP over 6 weeks ago an it's been dead ever since. Even a cellphone repair center guy could not repair it.
You need to leave good enough alone.
People all around the world have been stuck in permanent recovery screens or fastboot screens like me.
It really is a very good cell the way it is ?
Click to expand...
Click to collapse
Many people have faced the issue and they have recovered their device. Look for all solutions available.
danishajaz said:
Many people have faced the issue and they have recovered their device. Look for all solutions available.
Click to expand...
Click to collapse
I have. 7 weeks an counting an no working cell yet. I bought an Mi9 an no issues with it. Easy to reinstall firmware. The red magic 3 is the most difficult to repair cell I have ever encountered. I wish they had something like miflashpro for it
Treble is working from chinese ROM with twrp make sure image is A/B because this device is A/B
Good time of the day, I need help with resolving the issue mentioned in title. No matter which kernels I flash, bootloop consistently occurs. I flashed them using TWRP and cleared all caches as required, but to no avail. Neither on a clean system nor on a rooted one do they work
Did you recently upgrade to May1 Security Patched Firmware upgrade?
OldNoobOne said:
Did you recently upgrade to May1 Security Patched Firmware upgrade?
Click to expand...
Click to collapse
Yes, I did
VerySorryFor said:
Yes, I did
Click to expand...
Click to collapse
ok I thought so, atleast flashing disable-dmverity makes the GSI boot to rom logo but nothing beyond that, it just refuses to boot anything but the latest Stock ROM, I think its time to throw away this device (SM-M215G) into the garbage bin. Man Shamshung ruined my device, now stuck on 1UI5.1!
#Edit: You can try to contact a dev called Fredin, he might be able to help if there is any hope at all, you can find him on TGram & M21 Threads btw, all the best
VerySorryFor said:
Yes, I did
Click to expand...
Click to collapse
Have you tried flashing Kernel through Terminal or ADB sideload? Try finding out if A13 Stock ROM is R/O-System?