Related
Me and my son rooted our S3's a while ago. We have Cm 10 nightly "Oct 28/12" and want to update to Cm 11 nightly but I think we have to do something different as to a normal rom update? I think I read we have to update the kernal or something first but didn't understand it. We have the newest Clockworkmod 6.0.4.3. If someone could point us in the right direction it would be greatly appreciated. Thanks
Frostman5555 said:
Me and my son rooted our S3's a while ago. We have Cm 10 nightly "Oct 28/12" and want to update to Cm 11 nightly but I think we have to do something different as to a normal rom update? I think I read we have to update the kernal or something first but didn't understand it. We have the newest Clockworkmod 6.0.4.3. If someone could point us in the right direction it would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Alright first of all, which was the last official AT&T software update you did? If your at least updated to 4.1.2, you'll be good. As for the update, since it is a different update, a clean flash is necessary. First, you have two options, can get the latest CM 11 nightlife from
http://download.cyanogenmod.org/?device=d2att
OR, there's an excellent ROM by a developer named PwnCakes193, called Quantum which is based on CM 11, but based on community feedback and comparing it to the official CM 11 bug thread, Quantum is a lot more stable. It doesn't get updated daily but at least every 2-4 days (no promises). If you decide to check it out, make sure to read the thread twice and read a few of the latest comments here:
http://forum.xda-developers.com/showthread.php?t=2390147
For both these, you'll need the latest GApps. I recommend Paranoid Android GApps from here:
http://forum.xda-developers.com/showthread.php?t=2397942
Don't let the name trick you, you can use these GApps for any 4.4.x ROM (I recommend the Modular package).
Once you have a ROM and GApps downloaded and on your phone, the flashing process will be like this for CWM:
Wipe data/factory reset>wipe cache
>format /system>format /cache> wipe dalvik cache. Flash ROM, flash GApps, wipe cache, wipe dalvik cache. After this, you should be good as gold, so just setup and download your apps and that's it!
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Thanks a lot for your help. I have 4.1.2 on my phone .Do I not have to update the kernel ? As I think awhile ago I tried updating to 4.2 and it wouldn't go and someone said I needed to update the kernel,,but that was awhile ago maybe things have changed.I 'll try your method and let you know how it goes. thanks
ok I wiped everything they said to then tried to install Quantum 4.3 and says installation aborted "status 7" I remember this from last time and I never went any further because someone said I had to update the kernel?
its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm
Frostman5555 said:
its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm
I have I747MVLLH1,,its not in the list on the rom,,I remember this from last time and i stopped,,More reading
Click to expand...
Click to collapse
Frostman5555 said:
its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm
Click to expand...
Click to collapse
Are you trying to install 4.3 or Quantum v3?, Because Quantum v3 is 4.4.2 KitKat. Do you have a Canadian Galaxy S3? There might be something related to this in the ROM thread. Double check to make sure your recovery is the latest. If I had to guess, its probably be the boot loader, just be careful and read twice before you do anything.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
It was the bootloader. Updated it with Clockworkmod to the newest Canadian one"DLK4" then the Quantum v3 went on smooth . thanks for the help
Frostman5555 said:
It was the bootloader. Updated it with Clockworkmod to the newest Canadian one"DLK4" then the Quantum v3 went on smooth . thanks for the help
Click to expand...
Click to collapse
Sure thing, glad I could help. If you feel brave, PwnCakes just posted v3.15 about 5 minutes ago, which is the latest 4.4.2. If you decide to, you'll need a clean flash and latest GApps.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Drx,does the 3.12 have the google now working?I can't seem to get it to work.Also what would be the procedure to put 3.15 on now that I have 3.12 on,,thanks
Frostman5555 said:
Drx,does the 3.12 have the google now working?I can't seem to get it to work.Also what would be the procedure to put 3.15 on now that I have 3.12 on,,thanks
Click to expand...
Click to collapse
Yup, all versions have Google Now working. Have you made sure that there's no updates pending for it in the Play Store? Make sure that after every update, even a dirty flash, that you install GApps. If you forget to, the search bar will bring up a Gingerbread looking search app, and a lot of the Google apps and services will not work. For a "dirty" flash (no apps or data is lost), my process goes like this: wipe cache>wipe dalvik cache> format /system (no data will be lost)> Install ROM> Install GApps> wipe cache and dalvik. You should only use this if you are on the ROM already, not if it is a completly new ROM. Hope this helps!
Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks
Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.
Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.
is a ZIP file available for flashing via TWRP?
Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?
seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.
Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
ejaf said:
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
Click to expand...
Click to collapse
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Here is the link to the latest, grab the first tar flash it via odin & you should be good to boot into recovery to flash roms.
https://dl.twrp.me/d2spr/
Lonelyskatter12 said:
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Click to expand...
Click to collapse
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
ejaf said:
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
Click to expand...
Click to collapse
Yes, the official thread is CM13, you don't need Cwm, pretty much twrp supports marshmallow now.
And i believe you would need root.
If there's any way for you to be able to download the files, id be happy to give you step by step instructions :good:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
ejaf said:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
Click to expand...
Click to collapse
Yeah the Unofficial thread was being maintained by a Developer, who stopped as soon as the officials came out.
And yes
1.) Wipe Data, Cache, System, & Internal Storage (So backup anything on there)
2.) Flash Rom, Gapps, SuperSu 2.71 (If you want root)
& should be good to go
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
ejaf said:
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
Click to expand...
Click to collapse
That's the order, now about the apn im not sure, i just use mine for wifi and stuff.
That Cyanogenmod build "04282016" wasn't running so well for me, so I'm on AICP for now.
But i would suggest, OctOs , AICP, or Exodus Roms. Those are the most stable roms for this device.
Same steps just different ROMs.
But i did hear Exodus gives you data right off the bat, so that'd be good to try
Interesting...thanks for the tips. Hopefully I won't have to bother any of you all again, since I really don't have much in the way of knowledge to return
E
FYI...was able to boot up into CM 12.1 over the weekend. Jury's still out on whether to go to a 6.0.1 based ROM, but appreciate all the help.
Eric
I found the APN fix didn't work with the CM13 rom (I've used it previously with 12.1 fine). I also found that the build-in cm update failed on 20160505 nightly. Not sure if this was just that day or a known bug.
Here is my stock based B207 rom, Simply Google. This is great for those of you who have a hard time getting the Google Apps to work and want some extra mods and features. You must have an unlocked bootloader and TWRP installed. This rom is tested on the M2-803L. Flashing it on other versions (801L, 802L) should work but you're flashing it at your own risk. All Google Apps you can download from the Play Store have been removed from the rom. I also heavily debloated it and removed a lot of Huawei apps. Please don't ask me to add anything in as I want to keep this rom slim. Open up Tablet Manager, hit the settings icon and uncheck Smart Tune-up if Permissions Manager force closes when you open it. Please hit the Thanks button if you like the ROM.
Features & Mods:
-AdAway
-Cust Mods
-Dark M2 Theme
-Deodexed
-GBoard
-Google Play Store, Google Contacts Sync
-Heavily Debloated
-Insecure boot.img
-Marshmallow Boot Animation
-Nova Launcher
-Region Mods
-SuperSU Preinstalled
Instructions:
1. OTA or Dload to B2xx first before flashing. The ROM will not boot if you're still on anything lower than B2xx
2. Download ROM and put it on the phone's internal storage or SDCard
3. Boot into TWRP recovery.
4. Performing a factory reset using TWRP is recommended.
5. Flash the ROM
6. Reboot System
7. Profit!
Bugs:
-You tell me
Simply Google B207:
https://www.androidfilehost.com/?fid=817550096634797575
Many thanks! What a nice surprise. This seems to be the first custom rom for the m8.
Appears that it is for the 802l. Would it also work for the 801l?
At the moment I have 5.1 reverted to stock. BL unlocked.
Demianis said:
Many thanks! What a nice surprise. This seems to be the first custom rom for the m8.
Appears that it is for the 802l. Would it also work for the 801l?
At the moment I have 5.1 reverted to stock. BL unlocked.
Click to expand...
Click to collapse
It should work on both versions provided you update to stock B2xx first. After someone updates to B2xx on their 802L I need them to send me two things.
1) Their cust folder so I can integrate it into the rom.
2) Their system/emui folder. There should be a folder called oversea in there which I need to integrate into the rom.
Sorry, I don't have the b215 yet. There was no update to 6.0 till now and i can't find even a newer version for the 801l then the one attached.
Demianis said:
Sorry, I don't have the b215 yet. There was no update to 6.0 till now and i can't find even a newer version for the 801l then the one attached.
Click to expand...
Click to collapse
The B215 update posted in one of these threads is for the 801L because when I flashed it I had no cellular data option at all.
Just tried to install the b019. But again it's a incompatible version. I guess it's because it's for the m2 803l.
Anyway, thanks for your help. I'll have to wait until until the official update hits my tab.
I tried with hisuite, but i have already the latest version available.
Hi. Thanks for the rom. I have 802l - b006 with unlock bootloader. Can I use your rom without updating to b219? I dont have any ota update that I can installl
Thanks
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
budif said:
Hi. Thanks for the rom. I have 802l - b006 with unlock bootloader. Can I use your rom without updating to b219? I dont have any ota update that I can installl
Thanks
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
Click to expand...
Click to collapse
No, things like wifi won't work unless you upgrade to B211 first. Hold off on flashing until I sort out the root issue. Systemless root causes freezes. I'm working on porting the kernel from the X2 so I can use regular root which will fix the freezing issues.
New build up. Fixed root causes freezing in apps.
Do you know where to get the b011? The b006 is the latest rom that I can find for my m2.
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
budif said:
Do you know where to get the b011? The b006 is the latest rom that I can find for my m2.
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
Click to expand...
Click to collapse
You're gonna have to wait until you get the OTA to B215. Then you can flash this rom.
Installed this last night after updating to B207 from the other thread. Works perfectly, thanks!!
how can i remove 3g above my signal? my data is turned off and it still shows
New update. Fixed Multi-Screen not working. Rebased the rom to the International B207 version. Deodexed and added more mods.
ajsmsg78 said:
New update. Fixed Multi-Screen not working. Rebased the rom to the International B207 version. Deodexed and added more mods.
Click to expand...
Click to collapse
Currently I'm using your rom with xposed included.
Is the update also for this version available?
Lots of thanks for your work!
Demianis said:
Currently I'm using your rom with xposed included.
Is the update also for this version available?
Lots of thanks for your work!
Click to expand...
Click to collapse
I didn't integrate xposed this time because I figured if someone wanted it they can install it separately. You can grab it here:
https://drive.google.com/folderview?id=0B5I_q70mNuR4OWRaejdUdE1fcjA
ajsmsg78 said:
I didn't integrate xposed this time because I figured if someone wanted it they can install it separately. You can grab it here:
https://drive.google.com/folderview?id=0B5I_q70mNuR4OWRaejdUdE1fcjA
Click to expand...
Click to collapse
Ok, many thanks for the links. I will uninstall xposed, then dirty flash and after the first boot install xposed again.
my 801w was detected during installation as 802l. Don't know if this is what's causing the trouble, but after installing via TWRP, coming from some b2xx official ROM, i'm stuck at the Huawei Bootscreen for about 10 minutes now. I know that the first start could take a lot of time, but this seems a bit unusual to me. I'll keep it watching for another 15-20 minutes and see if it boots up fine or is frozen in any way.
[Update] so it was stuck in a loop for sure. I tried flashing a clean b2xx from another thread, which booted fine, and dirty flashing your ROM over, but same behaviour. What actually DID work is flashing the boot.img from stock over your ROM, so keeping the other partitions from Simply Google Installation. At least it's booting up now, showing the proper Android Nougat loading screen. Let's see how it works out...
toxic_garden said:
my 801w was detected during installation as 802l. Don't know if this is what's causing the trouble, but after installing via TWRP, coming from some b2xx official ROM, i'm stuck at the Huawei Bootscreen for about 10 minutes now. I know that the first start could take a lot of time, but this seems a bit unusual to me. I'll keep it watching for another 15-20 minutes and see if it boots up fine or is frozen in any way.
[Update] so it was stuck in a loop for sure. I tried flashing a clean b2xx from another thread, which booted fine, and dirty flashing your ROM over, but same behaviour. What actually DID work is flashing the boot.img from stock over your ROM, so keeping the other partitions from Simply Google Installation. At least it's booting up now, showing the proper Android Nougat loading screen. Let's see how it works out...
Click to expand...
Click to collapse
I need the /cust folder from the 801w so I can add it to the rom so it shows up correctly.
ajsmsg78 said:
I need the /cust folder from the 801w so I can add it to the rom so it shows up correctly.
Click to expand...
Click to collapse
Hello
same for me, i have a W, and i'm stuck on logo menu.
I have backup my tablet in trwp before, can you send me your email ???
Thank you.
(PS: is it complicated to deoxed the huawei rom ?) Ty
I installed TWRP and Lineage OS last weekend. I've been actively tweaking everything under the sun. I'm now wondering how the update process works. I installed Lineage Downloader app, and just received a downloaded zip file.
Would installing that zip completely redo my OS again (after just being installed a week ago)? Wiping out all the tweaks I've been making?
If so, is there a way to get just regular incremental changes (i.e. OS updates/patches) rather than having to reinstall the entire OS every week or so?
Sorry for the newbie questions, but I don't see them asked elsewhere, and all this rooting business is new to me.
TIA
prickett said:
I installed TWRP and Lineage OS last weekend. I've been actively tweaking everything under the sun. I'm now wondering how the update process works. I installed Lineage Downloader app, and just received a downloaded zip file.
Would installing that zip completely redo my OS again (after just being installed a week ago)? Wiping out all the tweaks I've been making?
If so, is there a way to get just regular incremental changes (i.e. OS updates/patches) rather than having to reinstall the entire OS every week or so?
Sorry for the newbie questions, but I don't see them asked elsewhere, and all this rooting business is new to me.
TIA
Click to expand...
Click to collapse
You don't need an extra app, if you have official lineageOS. Simply go settings > about phone > updates. The updater downloads and installs a full OS. Incremental updates only available from MoKee AFAIK.
Everything "under the sun" will stay the same. But changes in the dark corners of /system will be overwritten if they don't have addon.d survival equipment.
kurtn said:
You don't need an extra app, if you have official lineageOS. Simply go settings > about phone > updates. The updater downloads and installs a full OS. Incremental updates only available from MoKee AFAIK.
Everything "under the sun" will stay the same. But changes in the dark corners of /system will be overwritten if they don't have addon.d survival equipment.
Click to expand...
Click to collapse
Thanks for the information!
Do the gapps update themselves or do I also need to download them from time to time?
prickett said:
Thanks for the information!
Do the gapps update themselves or do I also need to download them from time to time?
Click to expand...
Click to collapse
Gapps are shelf-updating. Modern twrp can flash recovery.img for own updates. I recommend manual update. Not twrp app.
kurtn said:
Gapps are shelf-updating. Modern twrp can flash recovery.img for own updates. I recommend manual update. Not twrp app.
Click to expand...
Click to collapse
Again I think you! Some day, I'll understand all this.