Hey,
I was trying to flash the custom ROM's provided here to my OnePlus X ceramic. But I could install none of these (Resurrection Remix, SudaMod Project, MoKee). I always got some difficulties by flashing them.
I know some of them are explicit offered for the onyx version but are there differences between the onyx and the ceramic version, except the optical differences?
Are some of them nevertheless usable for the ceramic version?
Tell us what difficulties you had. There are no differences between colors.
Exactly... Show us what goes wrongly
When I try to flash a ROM, I alwas get the error message "This package is for oneplus onxy E1003, your phone is a "." or " "
The message varies slightly from ROM to ROM but means alwas the same: my phone should be another device than the ROM is for.
I admit, maybe this trouble is caused by myself, obviously.
When I rooted the OPX, I first have had flashed an wrong version of the TWRP. After that I made nandroid-backup, but then i saw the system was dissapeared miraculous.
There was no more system installed on the phone, surprisingly. So I installed the original OPX firmware but the error when I tried to install a ROM, persisted.
Deerix said:
When I try to flash a ROM, I alwas get the error message "This package is for oneplus onxy E1003, your phone is a "." or " "
The message varies slightly from ROM to ROM but means alwas the same: my phone should be another device than the ROM is for.
I admit, maybe this trouble is caused by myself, obviously.
When I rooted the OPX, I first have had flashed an wrong version of the TWRP. After that I made nandroid-backup, but then i saw the system was dissapeared miraculous.
There was no more system installed on the phone, surprisingly. So I installed the original OPX firmware but the error when I tried to install a ROM, persisted.
Click to expand...
Click to collapse
Try opening the updater-script file within the zip file and remove the "assert" statements at the beginning. Save the zip and try to flash again.
Deerix said:
Hey,
I was trying to flash the custom ROM's provided here to my OnePlus X ceramic. But I could install none of these (Resurrection Remix, SudaMod Project, MoKee). I always got some difficulties by flashing them.
I know some of them are explicit offered for the onyx version but are there differences between the onyx and the ceramic version, except the optical differences?
Are some of them nevertheless usable for the ceramic version?
Click to expand...
Click to collapse
If you could post your device info on the development thread, Dev's can whitelist your device so you won't have to go through troubles flashing roms.
Ex: EXXXX?
MrKhozam said:
Try opening the updater-script file within the zip file and remove the "assert" statements at the beginning. Save the zip and try to flash again.
Click to expand...
Click to collapse
I did it, without success. When I try to flash the zip I just get the message "Error flashing zip"
SpiritBreak3r said:
Ex: EXXXX?
Click to expand...
Click to collapse
Where is this number found?
Deerix said:
I did it, without success. When I try to flash the zip I just get the message "Error flashing zip"
Where is this number found?
Click to expand...
Click to collapse
I use total commander to modify the updated script. Open zip, reach the right path, open the updater script with total commander editor. First it asks to you to choose three options, choose open and modify then delete the first row of file. Go back with keys and it asks to you save and insert the file modified into the previous zip. Tap yes. It will works and when it finishes to work u are ready to flash. Use a twrp provided into opx development forum section
Related
Hello Everyone,
I badly need help on my Huawei Honor U8860 phone. I have recently updated it from 2.3.6 to 4.03 over WIFI and the update went smoothly. So now here is what my phone have:
Kernel Version: 3.0.8-perf-00059-g3a757a2 [email protected] #1
Build Number: U8860IV100R001C00B923SP01
I have not rooted the phone at this time. It was working fine until 2 days ago when I started getting messages on the screen like:
"Unfortunately, 2D Home has stopped"
"Unfortunately, Google Play has stopped"
"Unfortunately, Contacts has stopped"
"Unfortunately, Settings has stopped"
"Unfortunately, Google Play Music has stopped"
"Unfortunately, Browser has stopped"
And so on, and so forth. It seems that all apps and processes have stopped when I try to use them so I literally can't use the phone. I went through several threads here just trying to restore my phone back to a
working state. I tried to do the following in order but without success:
1.) Factory data reset / erase everything - the phone boots to the recovery menu then it formats the /Data, /Cache and /HWUserData then it reboots. After reboot, the phone is back to where it was before the factory data reset with everything in it including downloaded apps.
2.) Manually uninstalled all downloaded apps. Removed screen lock (just to see if phone behavior changes). Then rebooted the phone but after reboot, all the apps are still installed and the screen lock is back as well.
3.) I tried to Force Update with the following official ROMs: B886, B919 and B923 but I always get the message "Update failed" during the update process.
4.) I downloaded the file "recovery-u8860-en.img" so I can replace the "recovery.img" file . Rebooted the phone w/ the pink screen and connected it to my PC but there is no USB mass storage device mounted.
5.) Finally, I tried to root the phone. I enabled USB debugging. I installed the ADB drivers then I downloaded the U8860 root tools and rootexplorer.apk. When I ran the "root-me.cmd", it tried to copy some files to the phone but it failed. The error was "read-only file system".
So it seems that the problem is because of the "read-only filesystem". I does not permit/allow any changes made to the phone. Can you help me restore my phone?
Please.. Can somebody help me on this?
Thanks, clint2rose
clint2rose said:
Please.. Can somebody help me on this?
Thanks, clint2rose
Click to expand...
Click to collapse
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
clint2rose said:
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
Click to expand...
Click to collapse
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
kaefert said:
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
Click to expand...
Click to collapse
thanks for the reply. it did not work. I even formatted the internal SD. Re-run the firmware update but it failed. when i boot the phone, all the contents of the internal SD remains intact. any other suggestion?
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
kaefert said:
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
Click to expand...
Click to collapse
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
clint2rose said:
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
Click to expand...
Click to collapse
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
kaefert said:
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
Click to expand...
Click to collapse
Thank you once more for your time. Most of the thread I read regarding these patches often used the phrase" you have to flash the current version of your ROM using the patch"...
And yes I created dload folder, place the UPDATE.APP and put it on the sdcard. I turned off the phone and removed the battery. Then I pressed vol+ vol- and power on/off button. The firmware update went to about 70% installing before displaying update failed.
I guess I will have to bring my phone to a repair center. My only problem is that there is no Huawei service center at my place (I reside here in Saudi Arabia). I got the phone as a free device on a broadband package and the warranty is already expired. I'm a little worried to take the phone to the small mobile repair shops as they might screw up the phone even more. Huawei is not a popular device here unlike iPhone, HTC and Samsung Galaxy.
As I understood that your device is rooted, you should get some custom ROM and try to install it.
okty2k said:
As I understood that your device is rooted, you should get some custom ROM and try to install it.
Click to expand...
Click to collapse
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
clint2rose said:
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
Click to expand...
Click to collapse
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
kaefert said:
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
Click to expand...
Click to collapse
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
U8860 not responding
clint2rose said:
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
Click to expand...
Click to collapse
Have you find the solution yet? I have the same problem. Somehow my phone system is "locked". I can't install or uninstall app. Some google apps keep showing not responding. Everything changes i made, keep showing up after the phone rebooted.
This was happen a few days after I upgrade to ICS B932SP01 and rooted my phone (to remove original chinese apps).
Luckily i have friend in huawei indonesia. He gave my u8860 to the technical support. But the result was no good.
They try everything, even install my phone with the original GB and always failed.
The last suggestion is change the phone machine, which is as same as buy a new phone.
I really appreciate is someone can help me here...
Thanks
While trying to flash custom roms to my C6833 I continually get error messages that "this rom is for versions" and then it lists C6833 along with the other model numbers. If this were happening to one rom exclusively I would chalk it up to just a bad match, but on every instance I've tried I get the same error.
I can unlock my bootloader and get into TWRM and CWM both just fine, I have no obvious issues using Sony Mobile Flasher (as I have to use it to restore my factory default firmware each time) but I can't figure out what step I'm missing that's throwing this error each time.
Has anyone encountered anything like this, or does anyone have any speculation as to what I'm missing? I assume it's a simple thing, but I can't seem to figure it out.
flawlesscowboy said:
While trying to flash custom roms to my C6833 I continually get error messages that "this rom is for versions" and then it lists C6833 along with the other model numbers. If this were happening to one rom exclusively I would chalk it up to just a bad match, but on every instance I've tried I get the same error.
I can unlock my bootloader and get into TWRM and CWM both just fine, I have no obvious issues using Sony Mobile Flasher (as I have to use it to restore my factory default firmware each time) but I can't figure out what step I'm missing that's throwing this error each time.
Has anyone encountered anything like this, or does anyone have any speculation as to what I'm missing? I assume it's a simple thing, but I can't seem to figure it out.
Click to expand...
Click to collapse
One or two of the older kernels/recoveries were built of a port from the Z1, and this is where the error stems from nearly all of the time.
If you get this error just open the zip for the rom up and extract the boot.img file and flash that with flashtool in fastboot mode (hold vol up when connecting to the PC) that should solve the problem
blueether said:
One or two of the older kernels/recoveries were built of a port from the Z1, and this is where the error stems from nearly all of the time.
If you get this error just open the zip for the rom up and extract the boot.img file and flash that with flashtool in fastboot mode (hold vol up when connecting to the PC) that should solve the problem
Click to expand...
Click to collapse
Just so I'm clear, would I not use the kernel I had before at all? I would just use the .img from the rom I'm trying to flash. This would also mean I'd need to ensure my own custom recovery is present, correct?
Also, for the curious, I was using the kernel found in the first post of this topic:
http://forum.xda-developers.com/showthread.php?t=2687549
Seems like it didn't have too many issues, might just be my phone.
flawlesscowboy said:
Just so I'm clear, would I not use the kernel I had before at all? I would just use the .img from the rom I'm trying to flash. This would also mean I'd need to ensure my own custom recovery is present, correct?
Also, for the curious, I was using the kernel found in the first post of this topic:
http://forum.xda-developers.com/showthread.php?t=2687549
Seems like it didn't have too many issues, might just be my phone.
Click to expand...
Click to collapse
The boot.img int the zip will contain a recovery
I just wanted to let everyone know this was exactly my problem and I have successfully flashed a custom rom. Took all of five minutes. Thanks!
Hi guys,
I flashed Genysis ROM yesterday to try it out then got a few issues.
Upon first boot I got the error attached in the image.
Since then I can not get rid of it. I tried flashing New ROMs, even flashed the firmware again using LGUP and it still pops up after every reboot.
It also broke my fingerprint ability and the option was missing during setup and in setting as posted in the thread. The LGUP flash solved the fingerprint issue but can't shift the other one.
It also installed an app called Orange Jeux and it keeps appearing no matter what ROM I install. Its as if its somehow changed my devices region or something
Step 1
*Flash V10d kdz
*install twrp
*Full wipe
*install Genisys Rom
Step 2
*Full Wipe
*Flash H850 v10d Full Bootloaders Download
*Flash Genisys Rom
try, give me inform
Roshi69 said:
Hi guys,
I flashed Genysis ROM yesterday to try it out then got a few issues.
Upon first boot I got the error attached in the image.
Since then I can not get rid of it. I tried flashing New ROMs, even flashed the firmware again using LGUP and it still pops up after every reboot.
It also broke my fingerprint ability and the option was missing during setup and in setting as posted in the thread. The LGUP flash solved the fingerprint issue but can't shift the other one.
It also installed an app called Orange Jeux and it keeps appearing no matter what ROM I install. Its as if its somehow changed my devices region or something
Click to expand...
Click to collapse
I haven't flashed this ROM due to many people having similar issues and it does sound like it changed the region code and installed carrier bloat. Check this link and try the procedure described to fix device:
http://forum.xda-developers.com/showpost.php?p=67711440&postcount=56
Pphish20 said:
I haven't flashed this ROM due to many people having similar issues and it does sound like it changed the region code and installed carrier bloat. Check this link and try the procedure described to fix device:
http://forum.xda-developers.com/showpost.php?p=67711440&postcount=56
Click to expand...
Click to collapse
Thanks for the help. I will try again once I get this rooted again haha.
Go to root/cust and delete all content there
You can do this with TWRP or root file manager if you are rooted
gwolfu said:
Go to root/cust and delete all content there
You can do this with TWRP or root file manager if you are rooted
Click to expand...
Click to collapse
That worked a treat.
Thanks for the help guys, took the east way out and deleting the contents of the Cust folder and it solved the issue.
Thanks again
Hi developers. ^^ hey just wanna ask if there is anyone who is willing to make a custom rom for my zte blade s7... I prefer resurrection remix or cyanogenmod because of the veriety of customizing.. . Could anyone help? Or maybe some tutorials on how to create my own custom rom.. . I'm just a basic android customizer. I already know how to root, install xposed, reflash, backup, and such... But wanna kick it up a notch and make a custom rom.. . Hehe..
Jo_bell said:
Hi developers. ^^ hey just wanna ask if there is anyone who is willing to make a custom rom for my zte blade s7... I prefer resurrection remix or cyanogenmod because of the veriety of customizing.. . Could anyone help? Or maybe some tutorials on how to create my own custom rom.. . I'm just a basic android customizer. I already know how to root, install xposed, reflash, backup, and such... But wanna kick it up a notch and make a custom rom.. . Hehe..
Click to expand...
Click to collapse
My ports for S7
NFound said:
My ports for S7
Click to expand...
Click to collapse
Hey, you've made ports. Do you know what the difference is between twrp ports? For instance what makes a recovery.img different between phones? Does recovery.img have its own kernel? A rootfilesystem?
peterius said:
Hey, you've made ports. Do you know what the difference is between twrp ports? For instance what makes a recovery.img different between phones? Does recovery.img have its own kernel? A rootfilesystem?
Click to expand...
Click to collapse
Yes. To install TWRP use Google Translator: https://4pda.ru/forum/index.php?s=&showtopic=697227&view=findpost&p=64637653
Preview Oreo: https://4pda.ru/forum/index.php?s=&showtopic=697227&view=findpost&p=64948575
Yes to which? "Translation to secure pages is not supported". I was asking about phones in general, not just the ZTE. I asked in a different thread but there was no response. So I thought you might know, maybe PM would be better, or maybe it's inconvenient for you?
NFound said:
My ports for S7
Click to expand...
Click to collapse
hi i downloaded ur custom roms both cm12.1 and lineage...
but non of them were flashable.. it said tht the rom was for s7.. #something like tht# lucikly i have a backup of my rom to reflash. i researched some threads and found out tht i can flash the rom without the verification by deleting some symbols and words in updater script located inside google folder... but before I do tht.. i just want to make sure.. is the custom rom actually for "ZTE BLADE S7 T920" or is it for the "samsung s7"
http://m.gsmarena.com/zte_blade_s7-7670.php
here are the specs and such about the phone for reference
Jo_bell said:
hi i downloaded ur custom roms both cm12.1 and lineage...
but non of them were flashable.. it said tht the rom was for s7.. #something like tht# lucikly i have a backup of my rom to reflash. i researched some threads and found out tht i can flash the rom without the verification by deleting some symbols and words in updater script located inside google folder... but before I do tht.. i just want to make sure.. is the custom rom actually for "ZTE BLADE S7 T920" or is it for the "samsung s7"
http://m.gsmarena.com/zte_blade_s7-7670.php
here are the specs and such about the phone for reference
Click to expand...
Click to collapse
Yes, ZTE BLADE S7 T920. so you have an old TWRP therefore swearing. establish this TWRP 3.1.1-1 or delete first 2 lines in updater-script
NFound said:
Yes, ZTE BLADE S7 T920. so you have an old TWRP therefore swearing. establish this TWRP 3.1.1-1 or delete first 2 lines in updater-script
Click to expand...
Click to collapse
hi sorry for not replying... i was finding ways to flash the rom with my friend...
i think my phone is outta luck... already flsh the recovery you suggested but still can't install any of the roms... tried editing ro.product.device as s7... still the same with either error 6/7 if i use the edited updater script rom it will show up
Updater Process ended with error : 6
if i use the unedited rom it will show up error : 7
bummer for my phone... is there anymore that i can do?.. hehe.. i really want to experience android nougat and oreo..
but if its a dead end.. bummer...
maybe this could help?
i remember over the days.. i changed the build.prop and edit the model as my name..XD to fool my friends tht i made the device(trick failed.. they saw the logo at the back)XD... but i did'nt change it back.. because.. there was no harm. no error seem to pop up.. so... yeah... busted build.prop
i followed the custom rom... because i saw in some lines in updater script that wrote ro.product.device= s7
still the same with errors... below are the errors..
https://ibb.co/iRpA65
pictures of the log is in this link or in the attachment below... the picture is quite blurry because i used a java phone to snap a photo... hehe
inside the log is
''white colour'' regular process
installing zip file 'filename'
bla bla bla .etc
red colour... first red colour... was when i flash the edited rom(deleted some keywords in updater.script)
red 1
Updater process ended with ERROR : 6
Error installing zip file '/ filename'
the second red colour is flashing with the unedited rom
red 2
Updater process ended with ERROR : 7
Error installing zip file '/ filename'
if nothing can be done.. its okay ill just go with the stock then...
Jo_bell said:
hi sorry for not replying... i was finding ways to flash the rom with my friend...
i think my phone is outta luck... already flsh the recovery you suggested but still can't install any of the roms... tried editing ro.product.device as s7... still the same with either error 6/7 if i use the edited updater script rom it will show up
Updater Process ended with error : 6
if i use the unedited rom it will show up error : 7
bummer for my phone... is there anymore that i can do?.. hehe.. i really want to experience android nougat and oreo..
but if its a dead end.. bummer...
maybe this could help?
i remember over the days.. i changed the build.prop and edit the model as my name..XD to fool my friends tht i made the device(trick failed.. they saw the logo at the back)XD... but i did'nt change it back.. because.. there was no harm. no error seem to pop up.. so... yeah... busted build.prop
i followed the custom rom... because i saw in some lines in updater script that wrote ro.product.device= s7
still the same with errors... below are the errors..
https://ibb.co/iRpA65
pictures of the log is in this link or in the attachment below... the picture is quite blurry because i used a java phone to snap a photo... hehe
inside the log is
''white colour'' regular process
installing zip file 'filename'
bla bla bla .etc
red colour... first red colour... was when i flash the edited rom(deleted some keywords in updater.script)
red 1
Updater process ended with ERROR : 6
Error installing zip file '/ filename'
the second red colour is flashing with the unedited rom
red 2
Updater process ended with ERROR : 7
Error installing zip file '/ filename'
if nothing can be done.. its okay ill just go with the stock then...
Click to expand...
Click to collapse
i just tried the lineageOS 15 rom, and got an error 7, before that there was a line saying "this rom is for "s7" this is a "".
so how can i flash this rom?
Scepterus said:
i just tried the lineageOS 15 rom, and got an error 7, before that there was a line saying "this rom is for "s7" this is a "".
so how can i flash this rom?
Click to expand...
Click to collapse
Hi, I want to share a solution for this as user of ZTE Blade S7 too:
If you want to install any rom via TWRP 3.1.1 you will have to edit updater_script with Notepad ++ because probably these errors are caused by trying to edit with any other Windows text editer.
Please confirm two options in Notepad ++: "Edit/EOL Conversion/Convert to UNIX Format" and "Encoding/Encode in ANSI".
I recommend to erase the first two lines in the script, use "update archive" via WinZip, WinRAR, 7ZIP (not to rezip the files, only update updater_script with the modified one) and you will not encounter the ERROR:7.
This way I manage to install custom roms because the problem is that TWRP 3.1.1 do not recognize our ZTE Blade S7 as "ZTE_T920" so the best solution is to erase this lines of code in all roms that include "ro.product.device" and things like that but in the correct way, just erase correctly and if rom is correct it will install without a problem.
For error:6 if you do this correctly maybe it can be caused by not erasing system. Do not forget to wipe system in advanced settings.
Additionally, I have the latest B20 version from Malaysia in TWRP zip, but I cannot share links so if you want it please message me.
Still unable to flash the lineage 15 Rom and somebody please assist by posting a link for a flashable file. Thanks
Hey Guys,
i got the same Problem here.
I´ve rooted with Kingroot posted by NFound and flashed the TWRP 3.1.1-1.img with Rashr ony my ZTE Blade S7 (T920)
After that i switched into TWRP and wiped everything.
Next i tried to install the lineage os but get error 7, after deleting those 2 lines i still get the error 7 just the "this rom is for "s7" this is a ""." message is missing now.
So i tried the cm-rom, install works like a charm but google play freezes and i cant delete cache of apps because the settings window freezes too when i want to click on apps.... (used open gapps arm 5.1 nano)
So both dont work very well 4 me, maybe u got an idea.
Right now i´m downloading lineage os another time to make sure the rom is not bricked or sth.
Lg Seg
Thanks for updating, i was having problems with the stock rom after installing xposed and magisk and was considering trying the fix for the lineage rom.
I do wonder if anyone here actually managed to get that rom to work. Please update us if you succeed.
4pda
Scepterus said:
Thanks for updating, i was having problems with the stock rom after installing xposed and magisk and was considering trying the fix for the lineage rom.
I do wonder if anyone here actually managed to get that rom to work. Please update us if you succeed.
Click to expand...
Click to collapse
4pda android 8 lineageos 15.0 post 445 theme zte blade s 7
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
nmyshkin said:
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
Click to expand...
Click to collapse
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
Does this work on 16GB only or does this include 8GB version?
It should work on both, they run the same ROMs, only requirement is Lollipop+.
Edit: I'm making the assumption users know which ROMs accommodate the 512mb models. Obviously, the ROM needs to be functional for Magisk to work.
fddm said:
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
Click to expand...
Click to collapse
OK, no joy here. After waiting for a couple of hours to download a ROM (!) I finally put it all together. The system hangs at the "N" screen, never getting to the Cyanoboot screen. I tried this on an 8 GB tablet because I didn't want to mess majorly with my 16 GB one, but as you say, the result should be the same
BTW, there were no error messages I detected as the Magisk zip installed.
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
fddm said:
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
Click to expand...
Click to collapse
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
nmyshkin said:
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
Click to expand...
Click to collapse
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
fddm said:
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
Click to expand...
Click to collapse
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Your right, sorry, after testing again I can reproduce this error. Going to have a closer look, see if I can correct it. Thank you!
Edit: problem found, fix incoming
nmyshkin said:
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Click to expand...
Click to collapse
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
fddm said:
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
Click to expand...
Click to collapse
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
Anyway, I now have questions as I'm no magiskan I read about Magisk before and even tried it on a similar ROM (to no avail, of course), but there are many things I don't fully understand.
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
2. I need to install an SU manager, yes? MM seems to indicate that it can't find any. Seems like I recall it was based on the phh su so can I just install the manager app for that? Is that what I need to effect "root" or do I already have it?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
nmyshkin said:
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
Click to expand...
Click to collapse
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
fddm said:
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
Click to expand...
Click to collapse
Things are looking up I searched the AdAway issue and see there is a newer version that seems to solve the problem for people using Nougat ROMs (including someone running Magisk!). Worked like a charm. ES File Explorer seemed to have root access issues but I went into MM to see what the issue was and managed to manually turn on root access. Seems OK now.
As you say, part of this is getting used to it. I'm not seriously thinking this ROM is going to be good for the 8 GB tablet (for one thing I cannot tolerate the shutdown bug) but it's fun to see what's going on and try out this approach. Who knows? Someday there may be an Unlegacy AOSP 8.1 "mini-me" that will run (and maybe even shut down...) and I'll have the know-how to deal with it.
Thanks for your efforts. Sorry to have been a bit of a pain.
nmyshkin said:
Thanks for your efforts. Sorry to have been a bit of a pain.
Click to expand...
Click to collapse
No, you were perfect. You provided essential information and kept trying when you hit a wall, and we got working Magisk in the end. Couldn't be happier, thank you!