Hello, I have put in a little time to try and port Cm12 to our device . I will allow you to know this ROM is for the Blu Life One X(2016)(L0070UU) only!!
Disclaimer: I am NOT responsible for any damaged,bricked,etc. devices.
Link: https://drive.google.com/open?id=0B9agmneWDUg3QWluaUlJa05QNHM
Link to Gapps:http://opengapps.org/?api=5.1&variant=nano
Note: TWRP MUST BE USED!!!
The status of this rom : Bootlooping,sadly
Whats working: unknown yet:
Whats not working: Unknown yet
Credits: @BlueFlame4
@xpirt @retsen444(For fixing the rom not flashing issue)
If I missed any credits please let me know, thanks
elix9000 said:
Hello, I have put in a little time to try and port this ROM. I will allow you to know this ROM is for the Blu Life One X(2016)(L0070UU) only!!
Disclaimer: I am NOT responsible for any damaged,bricked,etc. devices.
Link: https://drive.google.com/open?id=0B9agmneWDUg3QWluaUlJa05QNHM
The status of this rom : Experimental and/or wont flash
Whats working: unknown yet:
Whats not working: Unknown yet
Credits: @BlueFlame4
@xpirt
If I missed any credits please let me know, thanks
Click to expand...
Click to collapse
Very cool. I'll play with it this afternoon. I assume that we will need to flash gapps as well?
Here is a link...
http://opengapps.org/?api=5.1&variant=nano
Update:
I'm getting the following error when flashing in TWRP 3.0.
'Could not find "META-INF/com/google/android/update-binary' in the zip file" error.
Does not look like rolling back to 2.8.7 will accomplish anything either after reading post below.
I keep getting this error when i try to flash it. I have the old version of the twrp. The error is "This package is for device: BLU_LIFE_ONE_X, BLU_LIFE_ONE_X; this device is 15460."
retsen444 said:
I keep getting this error when i try to flash it. I have the old version of the twrp. The error is "This package is for device: BLU_LIFE_ONE_X, BLU_LIFE_ONE_X; this device is 15460."
Click to expand...
Click to collapse
Are you sure you have the 2016 model of the blu life one x, if so then I will add 15460 to the updater-script in the assert line
elix9000 said:
Are you sure you have the 2016 model of the blu life one x, if so then I will add 15460 to the updater-script in the assert line
Click to expand...
Click to collapse
Looking at the build.prop file it looks like the ro.product properties are pointing to p8000
ro.build.product=p8000
ro.product.model=p8000
ro.product.device=p8000
ro.cm.device=p8000
You should also be able to delete the assert statement (first line) in the updater-script file. Without knowing what the rom porter did and why he did it, it probably make more sense to sit on it until a good zip can get produced.
Yes. I am sure that i have the model of 2016.
And by the way, i was getting that same error of no meta info. but it stoped that error when i putted the files inside of the folder, outside of the folder that is inside of the zip file. And then i deleted that folder. After i did that is that the error that i said started appearing.
Aparently, with the version of twrp 3.0.0.0 it changes the name to blu life one x but i still have the same error.
retsen444 said:
I keep getting this error when i try to flash it. I have the old version of the twrp. The error is "This package is for device: BLU_LIFE_ONE_X, BLU_LIFE_ONE_X; this device is 15460."
Click to expand...
Click to collapse
when i had the old version of twrp my device was always seen as fever. with the newest version on the BLOX thread my device was seen as a bunch of random numbers, kinda like when you type adb devices and it shows 123456789. the only version that shows my devices as the name in the build prop, which is BLU_LIFE_ONE_X, is twrp 3.0. i had to make separate folders for all the backups i have made using the different versions of twrp. If not then the ones made with the first version wont show up when you hit restore in the newest two versions and same thing with the other two . im downloading the port right now so ill see what i can figure out :good:
I appreciate the help of everyone and today i will try to change some things, Sorry for the no flashing thing though
Sent from my BLU LIFE ONE X using XDA-Developers mobile app
elix9000 said:
I appreciate the help of everyone and today i will
Click to expand...
Click to collapse
zaksimmermon said:
I went into the updater script and I changed the Blu Life One X back to p8000. When I did that I didn't get any error when I flashed it just said failed to install zip??
Click to expand...
Click to collapse
hmm, tonight I will work on it, thank you for testing and helping me get this rom officially working
Sent from my BLU LIFE ONE X using XDA-Developers mobile app
elix9000 said:
I appreciate the help of everyone and today i will try to change some things, Sorry for the no flashing thing though
Sent from my BLU LIFE ONE X using XDA-Developers mobile app
Click to expand...
Click to collapse
I went into the updater script and I changed the Blu Life One X back to p8000. When I did that I didn't get any error when I flashed it just said failed to install zip??
I was succesful flashing the rom but, it will not start booting up. It does not pass the blu logo and it restart by it self.
retsen444 said:
I was succesful flashing the rom but, it will not start booting up. It does not pass the blu logo and it restart by it self.
Click to expand...
Click to collapse
We have made some progress! How did you get it to flash though?
Changing the name. And i made it go farther by changing the boot.img but now its on a bootloop. It stays in the cyanogenmod logo. If someone wants i can upload it so someone can fix it.
retsen444 said:
Changing the name. And i made it go farther by changing the boot.img but now its on a bootloop. It stays in the cyanogenmod logo. If someone wants i can upload it so someone can fix it.
Click to expand...
Click to collapse
Can you pm me the zip with the changes, I actually know how to fix the bootloop but i couldn't get past the the flashing, By the way thank you and in the next revision of this rom I will make sure I put your name in the credits
Sent from my BLU LIFE ONE X using XDA-Developers mobile app
Ok. I will send you the zip with the changes. Make sure to format the data and maby system too. And you need the version 3.0.0.0 of twrp to install it.
retsen444 said:
Ok. I will send you the zip with the changes. Make sure to format the data and maby system too. And you need the version 3.0.0.0 of twrp to install it.
Click to expand...
Click to collapse
would you mind sending it to me or posting it whichever is easier for you.
---------- Post added at 03:30 AM ---------- Previous post was at 03:26 AM ----------
retsen444 said:
Ok. I will send you the zip with the changes. Make sure to format the data and maby system too. And you need the version 3.0.0.0 of twrp to install it.
Click to expand...
Click to collapse
did you have to unpack the boot.img and alter it, or did you just use a different img?
First, i changed the img that was there for the boot.img of the blu.
Second, here is the link for those who want the zip file.
https://drive.google.com/file/d/0B_zL7Bx3LSDdczFTS2xGRmdyaWc/view?usp=drivesdk
I hope we can soon finaly have the rom running.
retsen444 said:
First, i changed the img that was there for the boot.img of the blu.
Second, here is the link for those who want the zip file.
https://drive.google.com/file/d/0B_zL7Bx3LSDdczFTS2xGRmdyaWc/view?usp=drivesdk
I hope we can soon finaly have the rom running.
Click to expand...
Click to collapse
Alright, I'm gonna flash this using CWM and update in a bit.
Related
okay so i have a old android phone (1.6 donut) (rooted) Htc tattoo/click i want to install clockworkmod recovery and then flash cm7 with 2.3 gingerbread so i can overclock it and maybe i dont know i need a custom kernel?
so can anyone help me to get clockworkmod recovery to work?
Here you go. I'm not going to kill you over not searching, sometimes it can seem like a vast ocean of info and be overwhelming, but you can run a search for the tatoo/click forum and usually in ANY forum the rooting/flashing stuff is stickied to the development forum.
Just wanted to give you a heads up for easier searching next time, here's the link you need.
http://forum.xda-developers.com/showthread.php?t=716282
orangekid said:
Here you go. I'm not going to kill you over not searching, sometimes it can seem like a vast ocean of info and be overwhelming, but you can run a search for the tatoo/click forum and usually in ANY forum the rooting/flashing stuff is stickied to the development forum.
Just wanted to give you a heads up for easier searching next time, here's the link you need.
http://forum.xda-developers.com/showthread.php?t=716282
Click to expand...
Click to collapse
well i've been seaching yesterday and today alot but i didnt come over that thread thanks mate
hanni7345 said:
well i've been seaching yesterday and today alot but i didnt come over that thread thanks mate
Click to expand...
Click to collapse
No worries, happy flashing
orangekid said:
No worries, happy flashing
Click to expand...
Click to collapse
hey, so im in the menu to flash a zip.... i dont know if i have a goldcard but i think i have - i transformed my sd also the cm 7.1 wont flash 2 my device it just aborts :C please help
hanni7345 said:
hey, so im in the menu to flash a zip.... i dont know if i have a goldcard but i think i have - i transformed my sd also the cm 7.1 wont flash 2 my device it just aborts :C please help
Click to expand...
Click to collapse
What specific error do you get?
Are you on the latest version of CWM?
orangekid said:
What specific error do you get?
Are you on the latest version of CWM?
Click to expand...
Click to collapse
when verifying it stops and says flash aborted - i dont know where can i get latest for click/tattoo also whats CWM `? same as CM?
hanni7345 said:
when verifying it stops and says flash aborted - i dont know where can i get latest for click/tattoo also whats CWM `? same as CM?
Click to expand...
Click to collapse
CWM is "ClockWorkMod recovery" it is a custom recovery. Download the ROM again and try again, it might be failing the MD5 check.
Check out that thread for the latest recovery version etc...
orangekid said:
CWM is "ClockWorkMod recovery" it is a custom recovery. Download the ROM again and try again, it might be failing the MD5 check.
Check out that thread for the latest recovery version etc...
Click to expand...
Click to collapse
well im a kinda using antoher recovery i used a automated one becouse clockworkmod didnt wanna install - does that mean i cant get CM7?
hanni7345 said:
well im a kinda using antoher recovery i used a automated one becouse clockworkmod didnt wanna install - does that mean i cant get CM7?
Click to expand...
Click to collapse
No, it means you are going to have to trial and error some things.
Flash this recovery, then try the ROM again.
http://forum.xda-developers.com/showthread.php?t=649276
orangekid said:
No, it means you are going to have to trial and error some things.
Flash this recovery, then try the ROM again.
http://forum.xda-developers.com/showthread.php?t=649276
Click to expand...
Click to collapse
well i cant download it :C the link and mirror is down :C
hanni7345 said:
well i cant download it :C the link and mirror is down :C
Click to expand...
Click to collapse
http://www.bergfiles.com/i/bf4e51656ch32i0#
Here you go, make sure you check the MD5 after download before flashing as compared to the original thread I linked you to.
orangekid said:
http://www.bergfiles.com/i/bf4e51656ch32i0#
Here you go, make sure you check the MD5 after download before flashing as compared to the original thread I linked you to.
Click to expand...
Click to collapse
okay so im going to replace the original image 2 flash with this one ?
hanni7345 said:
okay so im going to replace the original image 2 flash with this one ?
Click to expand...
Click to collapse
i mean the recovery ? what about boot.img?
oh yeah, here's a boot image
http://forum.xda-developers.com/showpost.php?p=5792750&postcount=38
and here's the hack.ko file.
http://forum.xda-developers.com/attachment.php?attachmentid=286072&d=1266670581
well it still doesnt work ill try with another zip
hanni7345 said:
well it still doesnt work ill try with another zip
Click to expand...
Click to collapse
You flashed the recovery, boot image, and ko file, and THEN CM7 from amon ra?
orangekid said:
You flashed the recovery, boot image, and ko file, and THEN CM7 from amon ra?
Click to expand...
Click to collapse
well lets see i think i flashed all that you said with the easy1click root for tattoo but i replaced the img files with the ones you gave me or should i do from scratch
hanni7345 said:
well lets see i think i flashed all that you said with the easy1click root for tattoo but i replaced the img files with the ones you gave me or should i do from scratch
Click to expand...
Click to collapse
also i found the error - its error 7 in the zip file?
hanni7345 said:
also i found the error - its error 7 in the zip file?
Click to expand...
Click to collapse
Actually, forget all that amon ra stuff, flash ClockworkMod from here
http://forum.xda-developers.com/showthread.php?t=854152
THEN flash CM7 ROM, then full wipe + cache + Dalvik, then flash gapps, then restart. (just my personal preferred order)
edit: i would just flash it via adb
adb push recovery.img /sdcard/recovery.img
adb shell
su
flash_image recovery /sdcard/recovery.img
exit
exit
then just type adb reboot recovery and flash ROM
Hi guys, I'm actually trying to get the pacman rom 4.2.2 But there's no way to get it, I've tryed with CyanogenMod and it doest work... I just get this image and i dont know what thell do because im noobie at this android thing! Just got 3 days with the phone,Its an htc one s, If someone can help me ill appreciate it and sorry for the english,Years without practice it
Its an odd one dude, try getting a fresh copy of the ROM, then shutting down your phone and repeat the wiping process and reflash ?
Sent from my One S using xda premium
I have had similar issues when a rom zip is corrupted. Like blackcell said you should try redownloading the rom or trying another rom just to check if that zip is the issue.
inXavier said:
Hi guys, I'm actually trying to get the pacman rom 4.2.2 But there's no way to get it, I've tryed with CyanogenMod and it doest work... I just get this image and i dont know what thell do because im noobie at this android thing! Just got 3 days with the phone,Its an htc one s, If someone can help me ill appreciate it and sorry for the english,Years without practice it
Click to expand...
Click to collapse
Use twrp 2.4.0.0 recovery. Rest of them have many bugs.
2.3.3.0 is best
Sent from my HTC One S using xda premium
vatsaman said:
Use twrp 2.4.0.0 recovery. Rest of them have many bugs.
Click to expand...
Click to collapse
It says the same thing, Failed with twrp 2.4.0.0 with that file that u says came a .MD5 file do i need to do something with that file? I think thats the problem but i was looking at google and i couldnt find anything about it..
inXavier said:
It says the same thing, Failed with twrp 2.4.0.0 with that file that u says came a .MD5 file do i need to do something with that file? I think thats the problem but i was looking at google and i couldnt find anything about it..
Click to expand...
Click to collapse
No need of MD5 files, what version of recovery are you on ?
I've been experimenting with some ideas to help get cm working but I don't have the One Mini.
If anyone with the AT&T HTC One Mini would like to test out a few builds of cm and recovery images just send me a message and I'll reply back with a link to my mediafire.
If you've got any questions, feel free to ask them here
And thanks in advance to all.
VoluntaryMan said:
I've been experimenting with some ideas to help get cm working but I don't have the One Mini.
If anyone with the AT&T HTC One Mini would like to test out a few builds of cm and recovery images just send me a message and I'll reply back with a link to my mediafire.
If you've got any questions, feel free to ask them here
And thanks in advance to all.
Click to expand...
Click to collapse
i've got an international one, not at&t.. useful ?
BENETNATH said:
i've got an international one, not at&t.. useful ?
Click to expand...
Click to collapse
According to this post, it should work.
It shouldn't matter. My at&t Mini is running an international ROM
I haven an At&t version. I would like to help
ok, so what have you to share with beta testers
i didn't take time to compile the actual gits, as it seems that some major functions are not still ok (eg . audio), plus i'm quite ok with 4.3 + sense.
if you've got more than that, i'm interested
BENETNATH said:
ok, so what have you to share with beta testers
i didn't take time to compile the actual gits, as it seems that some major functions are not still ok (eg . audio), plus i'm quite ok with 4.3 + sense.
if you've got more than that, i'm interested
Click to expand...
Click to collapse
I've been working on the installation glitches related to SELinux.
VoluntaryMan said:
I've been working on the installation glitches related to SELinux.
Click to expand...
Click to collapse
did you make a new recovery ?
i didn"t take time to compile and work on this, as i lack some spare time.
BENETNATH said:
did you make a new recovery ?
i didn"t take time to compile and work on this, as i lack some spare time.
Click to expand...
Click to collapse
yeah, kernel tweaks mostly.
VoluntaryMan said:
yeah, kernel tweaks mostly.
Click to expand...
Click to collapse
ok, currently, need it and no time to do trials, hope abzboi will be helpful ^^
i'm still following here
I just got home and I'm going to download the test 1(first one in the cm-11.0-sm-linaro) do i need to download the md5sum also? what i'm going to do is flash the cwm-m4-6.0.4.6-test1.img and then flash the rom. correct me if i'm wrong.
---------- Post added at 01:25 AM ---------- Previous post was at 01:02 AM ----------
I got installation aborted for test 1 with the cwm recovery.
It says:Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /data/media/0/cm-11-20140113-UNOFFICIAL-TEST1-m4.zip
(status 7)
Installation aborted.
I'm going to try that recovery.img
Edit: same result with recovery.img one.
I'm going to try test2. btw what is that md5sum? what do i do with it? what i did was install the recovery in that folder both of em and i wipe data/factory reset. then install zip, choose zip from /sdcard,0/ then the cm11 test 1 and i got that result installation aborted.
Md5sum download is optional, use the recovery that matches the test number on the rom
VoluntaryMan said:
Md5sum download is optional, use the recovery that matches the test number on the rom
Click to expand...
Click to collapse
Same result. Tried test2 also.
abzboi said:
Same result. Tried test2 also.
Click to expand...
Click to collapse
Same error for TEST2? I was so sure this was it.. Well thanks.
VoluntaryMan said:
Same error for TEST2? I was so sure this was it.. Well thanks.
Click to expand...
Click to collapse
Np. Sorry for the waiting time. I wish it worked.
abzboi said:
Np. Sorry for the waiting time. I wish it worked.
Click to expand...
Click to collapse
no need to fastboot flash boot.img ?
qhat are your requirements ? s-off, bootloader unlocked ..?
BENETNATH said:
no need to fastboot flash boot.img ?
qhat are your requirements ? s-off, bootloader unlocked ..?
Click to expand...
Click to collapse
Rom couldn't be flash. It said installation aborted. (status 7). I'm s-off and unlocked. I really like cm roms. I hope there will be a working cm11 soon.
abzboi said:
Rom couldn't be flash. It said installation aborted. (status 7). I'm s-off and unlocked. I really like cm roms. I hope there will be a working cm11 soon.
Click to expand...
Click to collapse
status 7 is often due to the first line of the update-script, linked to assert
BENETNATH said:
status 7 is often due to the first line of the update-script, linked to assert
Click to expand...
Click to collapse
do u think there are any way to fix that?
BENETNATH said:
no need to fastboot flash boot.img ?
qhat are your requirements ? s-off, bootloader unlocked ..?
Click to expand...
Click to collapse
s-off just means you don't have to flash /boot manually.
abzboi said:
do u think there are any way to fix that?
Click to expand...
Click to collapse
yes, but I don't know what it is. Gotta do more reading online...
BENETNATH said:
status 7 is often due to the first line of the update-script, linked to assert
Click to expand...
Click to collapse
Status 7 here is because the command it's using requires selinux and something is improperly configured for that. I'm considering replacing the command...
I manged to install superSU on my moto g 3rd gen (XT1550).It gave the error "superSU binaries not found"
So I installed superSU 2.65.Now my phone is stuck on bootloader warning.However I can still go to TWRP. Trouble is,installing the previous superSU is not helping either.
Please tell me what went wrong and how can I fix it.Its my first time so I apologise for any newbie mistake here.Thanks for help.
kanav11090 said:
I manged to install superSU on my moto g 3rd gen (XT1550).It gave the error "superSU binaries not found"
So I installed superSU 2.65.Now my phone is stuck on bootloader warning.However I can still go to TWRP. Trouble is,installing the previous superSU is not helping either.
Please tell me what went wrong and how can I fix it.Its my first time so I apologise for any newbie mistake here.Thanks for help.
Click to expand...
Click to collapse
Not sure what you're saying, but once you unlock the bootloader you will get a long bootloader warning unless you flash a boot logo.
See step 4 in:
https://forum.xda-developers.com/20...gin-how-to-t3599251/post72111431#post72111431
KrisM22 said:
Not sure what you're saying, but once you unlock the bootloader you will get a long bootloader warning unless you flash a boot logo.
See step 4 in:
https://forum.xda-developers.com/20...gin-how-to-t3599251/post72111431#post72111431
Click to expand...
Click to collapse
My phone is bootlooping as I tried to reinstall magisk 14.0 over the 14.5 in magisk manager app itself !! It is stuck on warning message !
Twrp is working hopefully ,
I tried to clear system, data , dalvik , cache but it still results in bootloop.
Pls help !
KrisM22 said:
Not sure what you're saying, but once you unlock the bootloader you will get a long bootloader warning unless you flash a boot logo.
See step 4 in:
https://forum.xda-developers.com/20...gin-how-to-t3599251/post72111431#post72111431
Click to expand...
Click to collapse
The phone is stuck on bootloader warning.The step you mentioned points out how to remove the warning screen. My phone was stuck on it until its battery ran out. I have today installed superSU 2.62 beta and did what Tassusian did.While the phone now boots after the warning,it is stuck on the motorola logo screen.I'm waiting to see what it does next.Thanks for the reply though.It is good to see a helping hand.
kanav11090 said:
The phone is stuck on bootloader warning.The step you mentioned points out how to remove the warning screen. My phone was stuck on it until its battery ran out. I have today installed superSU 2.62 beta and did what Tassusian did.While the phone now boots after the warning,it is stuck on the motorola logo screen.I'm waiting to see what it does next.Thanks for the reply though.It is good to see a helping hand.
Click to expand...
Click to collapse
Try to install a different rom ! Clean flash that ROM hopefully that will solve the bootloop issue !
(Clear the system while clean flashing ) and after booting the whole rom then instal root (superSU/magisk)zip file in twrp.
kanav11090 said:
The phone is stuck on bootloader warning.The step you mentioned points out how to remove the warning screen. My phone was stuck on it until its battery ran out. I have today installed superSU 2.62 beta and did what Tassusian did.While the phone now boots after the warning,it is stuck on the motorola logo screen.I'm waiting to see what it does next.Thanks for the reply though.It is good to see a helping hand.
Click to expand...
Click to collapse
What are you installing SuperSU TO? Have you flashed a ROM? Flash a different ROM. Some repeat of above post @Mohammed Siamwala . Avoid majisk until you fix this.- I find it buggy sometimes.
I suspect I have corrupted my ROM somehow.
Installing superSU 2.62 Beta seems to boot it but it still gets stuck at the motorola logo screen.Which ROM should I use and how do I install it?Thanks for diagnosing the problem.:good:
Mohammed Siamwala said:
Try to install a different rom ! Clean flash that ROM hopefully that will solve the bootloop issue !
(Clear the system while clean flashing ) and after booting the whole rom then instal root (superSU/magisk)zip file in twrp.
Click to expand...
Click to collapse
Will certainly try it tomorrow.Thanks for the tip.Any suggestions about which ROM I should use?
kanav11090 said:
Will certainly try it tomorrow.Thanks for the tip.Any suggestions about which ROM I should use?
Click to expand...
Click to collapse
Try any stable nougat ROM like LOS 14.1 ! Avoid installing Oreo ROM as they're still in beta
Mohammed Siamwala said:
Try any stable nougat ROM like LOS 14.1 ! Avoid installing Oreo ROM as they're still in beta
Click to expand...
Click to collapse
hi,
Sorry for getting back so late as I away with my family.I did as you said but the system is stuck at
'patching system image unconditionally....'
I browsed and found this link:
https://forum.xda-developers.com/oneplus-3t/help/twrp-stuck-patching-image-t3623593/page2
It says that sideloading the ROM worked.Will it work here? Thanks for being with me for this long time.
kanav11090 said:
hi,
Sorry for getting back so late as I away with my family.I did as you said but the system is stuck at
'patching system image unconditionally....'
I browsed and found this link:
https://forum.xda-developers.com/oneplus-3t/help/twrp-stuck-patching-image-t3623593/page2
It says that sideloading the ROM worked.Will it work here? Thanks for being with me for this long time.
Click to expand...
Click to collapse
Which version of TWRP you're using ???
Make sure you're having latest !
And try flashing again
kanav11090 said:
hi,
Sorry for getting back so late as I away with my family.I did as you said but the system is stuck at
'patching system image unconditionally....'
I browsed and found this link:
https://forum.xda-developers.com/oneplus-3t/help/twrp-stuck-patching-image-t3623593/page2
It says that sideloading the ROM worked.Will it work here? Thanks for being with me for this long time.
Click to expand...
Click to collapse
Sorry, I have no idea.
Mohammed Siamwala said:
Which version of TWRP you're using ???
Make sure you're having latest !
And try flashing again
Click to expand...
Click to collapse
I'm using twrp 3.2.0. Which one should I use?
KrisM22 said:
Sorry, I have no idea.
Click to expand...
Click to collapse
Will my phone get hard-bricked if i do it unsuccesfully? I'm new so I don't have much knowldege about this.Thanks.
kanav11090 said:
I'm using twrp 3.2.0. Which one should I use?
Click to expand...
Click to collapse
3.2.1
Make sure:
wipe/advanced/check: dalvik/art, system, data, cache - all 4, but NOT internal storage or SDcard
click the thing that says not to install the TWRP app when rebooting
take a screenshot of error (same way as in ROM) and post it.
---------- Post added at 12:18 AM ---------- Previous post was at 12:18 AM ----------
kanav11090 said:
Will my phone get hard-bricked if i do it unsuccesfully? I'm new so I don't have much knowldege about this.Thanks.
Click to expand...
Click to collapse
It's possible. I do not know.
no success.Is there a chance that the zip file is corrupted?Thanks for help.
kanav11090 said:
no success.Is there a chance that the zip file is corrupted?Thanks for help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/2015-moto-g/help/problems-flashing-oreo-8-x-check-t3726839
KrisM22 said:
https://forum.xda-developers.com/2015-moto-g/help/problems-flashing-oreo-8-x-check-t3726839
Click to expand...
Click to collapse
Did as you said,still stuck at 'patching system unconditionally'. Any other OS ROMs that I can try using with TWRP 3.2.1? Thanks for the article though.It threw light on many other new things.
kanav11090 said:
Did as you said,still stuck at 'patching system unconditionally'. Any other OS ROMs that I can try using with TWRP 3.2.1? Thanks for the article though.It threw light on many other new things.
Click to expand...
Click to collapse
Thanks for the help mate.I finally managed to get the stock ROM and shifted to it.Now my phone is faster than ever because of minimal gapps and other useless stuff being thrown out.Thanks for your help once more.
error applying update 7 (error code kinstalldeviceopenerror) -this error is coming for installing rom zip file pixel experience 11+ on oneplus8t
WHAT SHOULD I DO?
Look at the phone is it asking you to install anyway? If so say yes. If it's not asking then you need to ask the question in the rom thread so the dev can have a look
It's not asking anything just the error mentioned only
Honestsheepherder said:
It's not asking anything just the error mentioned only
Click to expand...
Click to collapse
Then take a look in /tmp/recovery.log file after flashing and see what error message is mentioned there.
Honestsheepherder said:
error applying update 7 (error code kinstalldeviceopenerror) -this error is coming for installing rom zip file pixel experience 11+ on oneplus8t
WHAT SHOULD I DO?
Click to expand...
Click to collapse
you should redownload the rom file and pls make sure the file will be downloaded completely
nujackk said:
Look at the phone is it asking you to install anyway? If so say yes. If it's not asking then you need to ask the question in the rom thread so the dev can have a look
Click to expand...
Click to collapse
Anyway thanks
Wishmasterflo said:
Then take a look in /tmp/recovery.log file after flashing and see what error message is mentioned there.
Click to expand...
Click to collapse
Didn't get your point
mydarhieu97 said:
you should redownload the rom file and pls make sure the file will be downloaded completely
Click to expand...
Click to collapse
Checked and tried also no change
Should post in rom thread, see if common issue.
Also msm the device, as it may be partition issue caused by previous installs, And clean start is best way to troubleshoot.
Also provide more relavent nfo, exact device, rom, and recovery you're using.