I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
neocortex08 said:
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Click to expand...
Click to collapse
He is correct. You have to be on CM. EMUI will NOT allow closed to work. Flash the uninstaller zip.
icyboyice said:
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
Click to expand...
Click to collapse
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
neocortex08 said:
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
Click to expand...
Click to collapse
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Moody66 said:
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Click to expand...
Click to collapse
Thanks! As excited as I am to have Xposed, I really like my EMUI (and don't want to pay for the play store one you suggested to others), I like B321s stability, and I like not changing settings often. So for now I'll wait and deal with not having trivialities like AdAway or playing Youtube in the background.
@neocortex08
You only need root on your phone to be able to install adaway. You don't need xposed.
For background playback of YouTube videos you may want to check this out
http://forum.xda-developers.com/showthread.php?t=2213945
They have a install method for those who are rooted and have xposed and those who don't .
Related
Welcome to wilson3q's CM12 Unoffical Build!
As requested by some users, I started to build cm12 for I605. I don't own a I605, please help to test. If you like my work, you can donate here.
Disclaimer: I take no responsibility for bad things that happen as a result of flashing this.
My kernel source is standard cm12 kernel without any modifications.
SaberMod tool chain source is HERE.
All the rests are pretty standard cm12 stuffs, except a few patches I applied on top of them.
[Download]
ROM (please don't mirror):
build - 20150513
build - 20150602
Gapp:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Recommended launcher:
Nova Launcher (really like its JB zoom app animation, hate L slide up animation)
Recommended theme:
Deep Darkness
If you need enable soft buttons, flash this: View attachment softkeys.zip or soft+hardkeys.zip
[Flashing Guide]
1. Reboot to CWM/TWRP recovery
2. Flash ROM zip file
3. Flash Gapps
4. Reboot
* Wipe data first if you come from another rom *
* Newer boot loader, modem and recovery is highly recommended (don't use twrp 2.8.4, use 2.8.1 instead) *
* No other kernel will be supported, use the stock one, for your best experiences too *
[Patches]
My additional patches over cm12 includes:
Enhancements and bug fixes cherry-picked from other ROMs, including Slim LP, Nameless
SaberMod for ROM and kernel
O3, JustArchi optimization
Pthread enabled & strict aliasing
Latest sqlite db library
Added Boeffla sound engine 1.67
Added CPU governor zzmoove, smartassv2, savagedzen
Added io scheduler row, bfq, zen, vr
Disabled some useless Samsung processes
Fixed GPS
Fixed low in call volume
Video playback forward/backward fix
Removed all kernel debuging stuffs
Fixed keyboard not showing up during setup wizard
Fixed a crash of music app
Changed DPI to 280
Fixed Camera issue
Fixed Day Dream
Fixed Netflix streaming (one more reboot needed after installation of Netflix)
Enabled Multi-user
LMK minfree tweaks
Misc tweaks
more...
For better experience, change Nova animation/scroll speed to Fast...
[Known Bugs]
I am not sure what issues you will get, but one thing is for sure: YOUR PHONE WILL FLY!
chrome glitch: type chrome://flags as URL and disable GPU thank @bigmarv31)
Thank cm team for the amazing ROM.
Thank sabermod for the amazing toolchain.
Special thanks to: @DerTeufel1980, @sbrissen, @rogersb11, @TheBr0ken, @DreamFX, @frankie...
[Screenshots]
Always nice to see a new thread for i605. This doesn't happen often. Thank you!
Thanks again for building this for us we all appreciate it!
will be testing this out and see how it spars. thanks for this! I was going to try and "port" it over from the t0lte with replacing some libs and such, lol.
Thank you! I'm downloading right now. Looking like a slow day at work, so why not?
Downloaded files. Backed everything up. Rebooted to recovery. Wiped / Factory Reset using TWRP. Installed both zips sequentially. Apprehensive when I rebooted. Took a couple of minutes of sweating watching the CM Logo swirl around, and then bam! I'm up and running Lollipop. I'll update soon...
UPDATE
thefinancemaster said:
Downloaded files. Backed everything up. Rebooted to recovery. Wiped / Factory Reset using TWRP. Installed both zips sequentially. Apprehensive when I rebooted. Took a couple of minutes of sweating watching the CM Logo swirl around, and then bam! I'm up and running Lollipop. I'll update soon...
Click to expand...
Click to collapse
So, I've got it up and running. It's fast and smooth, but there's a couple of glaring issues stopping me from testing any farther. The first screen that comes up after you initially select your language, is a new (to me) "Activating Cellular Service" screen. It has a message on the screen saying this "can take up to 5 minutes". I let it go for longer than that, but I got an error that it was unable to activate and I was able to try again, or skip it. I'll skip it for now just to see how the rest of the ROM works. Next screen is Wifi login, works fine., but you still have to hit "skip" even after you sign in to wifi.
Then it checks connections, for updates, etc and I keep getting the error that google play services has stopped. I haven't even logged into it yet...
Next screen is Tap N Go. Option to transfer all of your stuff off your old phone using NFC. Great idea, but I'm not testing because my new phone IS my old phone.
Then, it's google login time. Worked fine, standard stuff we're used to with options to download/backup your apps using google. It takes a minute here, and I kept getting popups about all of the google apps stopping, each individually. Annoying a bit... I hit the "RESTORE" option, this is my second try, and the first time I didn't have Root, so I couldn't download Titanium to restore everything. I also skipped the google restore last time, so I tried it this time. This is a new screen for me, but it takes me to a "Restoring" screen for a bit. It's not as annoying as on previous Android versions, having to individually approve each app that was updating/downloading. I keep getting the popups about one Google app or another stopping.
I get past the restore page, and the phone locks up. Reboot... After reboot, I have to go into the play store to download Titanium. It seems quite a few apps were restored by Google, but not all. I looked at the "My Apps" section of the play store, and there's a ton of apps cued up to download. It's what I was trying to avoid... So I hit "Stop" at the top, and it stops them all.
**I mentioned earlier that this is my 2nd try, the first try was about the same, but I didn't have root access. I downloaded SuperSU, but it wouldn't update the binaries, so it was useless. I tried SuperUser, it didn't work either. So, I rebooted to recovery, wiped, flashed the ROM, GApps, and the SuperSU zip I had saved on my SD card from my previous Omni Rom. Then I rebooted and now you can read what happened.
At this point, I'm having problems downloading Titanium Backup, SuperSU, or anything I really want. The Play Store is hanging and force closing. I can't even open the SuperSU I flashed from TWRP. There must be compatibility issues. I read somewhere that Lollipop has issues with root somehow, but I'm not sure. On my first try, I was able to download Titanium Backup no problem, but it wouldn't work because I didn't have root access. SuperSU and SuperUser didn't help after downloading. CM has always been pre-rooted on all of the other devices I've installed it on.
For now, I'm just going to restore my backup of Omni Rom and be content with 4.4.4 for now.
I'll try again if anyone can help with actually being on the VZW Network and Root. I didn't get a chance to play with the other stuff in Lollipop yet, but I would love to.
thefinancemaster said:
So, I've got it up and running. It's fast and smooth, but there's a couple of glaring issues stopping me from testing any farther. The first screen that comes up after you initially select your language, is a new (to me) "Activating Cellular Service" screen. It has a message on the screen saying this "can take up to 5 minutes". I let it go for longer than that, but I got an error that it was unable to activate and I was able to try again, or skip it. I'll skip it for now just to see how the rest of the ROM works. Next screen is Wifi login, works fine., but you still have to hit "skip" even after you sign in to wifi.
Then it checks connections, for updates, etc and I keep getting the error that google play services has stopped. I haven't even logged into it yet...
Next screen is Tap N Go. Option to transfer all of your stuff off your old phone using NFC. Great idea, but I'm not testing because my new phone IS my old phone.
Then, it's google login time. Worked fine, standard stuff we're used to with options to download/backup your apps using google. It takes a minute here, and I kept getting popups about all of the google apps stopping, each individually. Annoying a bit... I hit the "RESTORE" option, this is my second try, and the first time I didn't have Root, so I couldn't download Titanium to restore everything. I also skipped the google restore last time, so I tried it this time. This is a new screen for me, but it takes me to a "Restoring" screen for a bit. It's not as annoying as on previous Android versions, having to individually approve each app that was updating/downloading. I keep getting the popups about one Google app or another stopping.
I get past the restore page, and the phone locks up. Reboot... After reboot, I have to go into the play store to download Titanium. It seems quite a few apps were restored by Google, but not all. I looked at the "My Apps" section of the play store, and there's a ton of apps cued up to download. It's what I was trying to avoid... So I hit "Stop" at the top, and it stops them all.
**I mentioned earlier that this is my 2nd try, the first try was about the same, but I didn't have root access. I downloaded SuperSU, but it wouldn't update the binaries, so it was useless. I tried SuperUser, it didn't work either. So, I rebooted to recovery, wiped, flashed the ROM, GApps, and the SuperSU zip I had saved on my SD card from my previous Omni Rom. Then I rebooted and now you can read what happened.
At this point, I'm having problems downloading Titanium Backup, SuperSU, or anything I really want. The Play Store is hanging and force closing. I can't even open the SuperSU I flashed from TWRP. There must be compatibility issues. I read somewhere that Lollipop has issues with root somehow, but I'm not sure. On my first try, I was able to download Titanium Backup no problem, but it wouldn't work because I didn't have root access. SuperSU and SuperUser didn't help after downloading. CM has always been pre-rooted on all of the other devices I've installed it on.
For now, I'm just going to restore my backup of Omni Rom and be content with 4.4.4 for now.
I'll try again if anyone can help with actually being on the VZW Network and Root. I didn't get a chance to play with the other stuff in Lollipop yet, but I would love to.
Click to expand...
Click to collapse
Did you flash the andriod 5 gapps? Do a full wipe?
You also need latest twrp recovery or philz touch recovery...
baseband unknown no data
bigmarv31 said:
baseband unknown no data
Click to expand...
Click to collapse
Will fix this today.
Keep a close look.
wilson3q said:
Will fix this today.
Keep a close look.
Click to expand...
Click to collapse
Yes Sir Thanks
New build online...
Giving this a try!! Downloading now
Update- Downloaded and installed without any problems. I did have to skip the network verification set-up as it never went anywhere and wifi set-up worked as with setting up my g-mail account,.
Everything seems good except for no service, baseband version still unknown and no service or apn's for data.
going back to Liquid till this gets updated.
LvnInOC said:
Giving this a try!! Downloading now
Update- Downloaded and installed without any problems. I did have to skip the network verification set-up as it never went anywhere and wifi set-up worked as with setting up my g-mail account,.
Everything seems good except for no service, baseband version still unknown and no service or apn's for data.
going back to Liquid till this gets updated.
Click to expand...
Click to collapse
Can you get a logcat?
I guess my proprietary blobs are not correct...
wilson3q said:
Can you get a logcat?
I guess my proprietary blobs are not correct...
Click to expand...
Click to collapse
I already went back to Liquid but I dont mind doing another try at it especially if it would benefit. let me get ir flashed and try to get you the Logcat
. give me a few
---------- Post added at 05:38 AM ---------- Previous post was at 05:10 AM ----------
ok so I got this flashed again strange this time after booting it said no sim card inserted and to insert my sim, it was not out and i skipped and moved to wifi , setup worked all the way and I got a log cat, hope I did it correct as this is new to me. I have to re-flash to Liquid for now so that I have a working phone as I go to work in an hour,
Again let me know if you need any more details
Same on this build baseband unknown so no data
wilson3q said:
Did you flash the andriod 5 gapps? Do a full wipe?
You also need latest twrp recovery or philz touch recovery...
Click to expand...
Click to collapse
Yes, I flashed the gapps from your post. gapps-lp-20141109 is what the file name was. I use TWRP, not sure if it's the latest but it works fine. I always do the "factory reset" wipe option in twrp, because I believe that's a full wipe with one swipe... Now, just to test it out and see if I was doing something wrong, I tried the Liquid Smooth build (latest nightly) from 1/7, and it loaded and booted just fine. Had to flash the ROM, Gapps, GPS Fix, and Super SU (so I can restore my apps in Titanium). It connected to data, and ran me through the setup in a flash. It's working well enough to be a daily driver. Do you have any other suggestions? I'm willing to help if you want me to try something else.
Going to give this a try. Thank you for giving this phone options. It is greatly appreciated.
"Chance Favors the Prepared"
glockman4519 said:
Going to give this a try. Thank you for giving this phone options. It is greatly appreciated.
"Chance Favors the Prepared"
Click to expand...
Click to collapse
You're like me you change roms by the hour.
DreamFX said:
You're like me you change roms by the hour.
Click to expand...
Click to collapse
I love to flash and then go through a process of testing. I actually got 2 gt-n5110s so I could test a couple builds at same time, kind of a back to back comparison.
I would love to pick up another i650 that still has unlocked bootloader for testing that way on this device as well.
Well back to this rom, I couldn't get past the getting data screen and had to abort. I did a clean flash and wiped everything with both philz and TWRP 2.8.3.0. I tried both stock and shift kernels.
Lets face it, I'm a flashaholic. lol.....
"Chances Favors the Prepared"
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
Hi everyone,
My phone has this restarting loop issue after flashing either Candy7 or CM13 ROM. Not sure if this is bootloop error because It got pass the Huawei booting logo, but as soon as it finish loading the Google App and go to the OS home screen it restart again and again. Worth noting that the phone restart from ROM loading logo (the blue face for CM13 or the Google Dot for Candy7), not all the way back from Huawei booting logo.
First I use TWRP to factory reset wipe, then advance wipe /system, /data, /cache / Dalvik, then install new ROM + Gapp, and got the sucess message, then reboot to system.
I also tried with out Gapp to save loading time, and it restart again when get to OS home screen.
Please advise what may cause this.
No issue when i restore back to B322 EMUI 3.1
I have US version unlocked MT2-L03, B322 version, unlocked bootloader, rooted, TWRP 3.1.1.0 installed.
I made a video clip of the looping: https://www.youtube.com/watch?v=Y7kRpdGN2qA
I'm going through the EXACT same thing. I tried CM13, CM14 and even CandyRom, and the same thing happened more or less. Even if I got the ROMs running for a while, eventually that LOD (Loop of Death) would hit and I'd have to again reflash. I'm now back to B322 (Lollipop) for stability.
Given that the SAME thing is happening on all those ROMs, it's leading me to think that perhaps there is a software issue with my phone. Not sure if this helps, but I do think it could be the way I updated to Lollipop (B322) from the original Jelly Bean (B148). I've done a LOT of digging, and it looks like the way I did it was not quite right, even though my phone has worked fine all this time.
Here is the XDA post that seems to detail the correct upgrade path to B322:
https://forum.xda-developers.com/ascend-mate2/help/how-to-update-unlocked-mt2-l03-to-t3422775
Basically, it looks like the correct path should be B148 (Jelly Bean) --> B309 (Lollipop) --> B322 (Lollipop)
Being rather new, I just flashed to B322 right off of B148. I am now wondering if this could be the source of my problems. Especially since I keep getting the "Error 7" for "unknown bootloader" whenever I use TWRP 3.1.1 to flash LineageOS or CandyRom.
But, if you successfully used TWRP 3.1.1 to flash, that means your bootloader was recognized (I got the Error 7). If that's the case, then we're both having the same issue and something else is indeed the culprit.
I strongly suspect that "something else" could be GAPPS. I've experimented with several GAPPS packages, and noticed that right before crashing and the dreaded infinite loop, something glitched involving Google apps.
Desperately want to leave Lollipop since Oreo is about to drop meaning we Android L users are in for a world of hurt if we can't migrate soon. :-\
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
My phone has been rooted for over a year now, I've had many roms on it doing that time. This loop started with a app I updated from the play store. Not sure it may be substratum will look into it when I have more time..
These problems is because of the room. Try to install lineageOs.
Thanks Kevinoriej,
Same looping issue on LineageOS, after loading to OS homescreen , phone restart.
Also get error 7, and manually remove "assert" lines in the ROM script in order to flash.
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
I believe the Error 7 message is because your bootloader is showing as "unknown". I downloaded an app from the Playstore that gave me my device's technical info, and sure enough, my bootloader is listed as "unknown". I forwarded a question to Huawei's EMUI team asking them if that happened due to unlocking it (using Huawei's official unlocking request). Still waiting for a replay. In order to get any of the ROMs to install, I had to downgrade TWRP to 2.8.7.0. Any version above that would trigger Error 7.
Out of curiosity, I then downgraded and flashed CandySix (with a corresponding GAPPS package) - and sure enough, the same looping happened. And again when I flashed CM13 AND LineageOS. The phone would successfully boot, get to the actual Start screen, and then boot again. I could NEVER predict exactly what triggered this. Also, I tried installing ROMs without GAPPS, and that didn't go well for me (couldn't get any of them to load properly without flashing a GAPPS package for some reason).
Something goofy seems to be happening between Google services and the custom ROMs on this phone. I'm not sure what's triggering it, but given the sheer number of different ROMs I've tried - ALL of which have the EXACT SAME ISSUE - I strongly suspect there is indeed a GAPPS problem lurking somewhere.
As a side note - I reflahsed B322 (restoring from backup) and the phone is again as stable as it has always been.
Is there an EMUI GAPPS package for Marshmallow and/or Nougat (i.e., pulled from Mate 7, 8 or 9) available for download? I'm game for testing.
RE: MT2 boot loop
(*** SEE POST #25 FOR UPDATED FIX!***)
I just noticed this thread, wish I found it earlier. I recently posted my discussion of the boot loop (and fix) here:
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345/page14
Bratzilla was right when he said in his post, "I strongly suspect there is indeed a GAPPS problem lurking somewhere".
Thanks EndlessFall,
please help to check this link: github(dot)com/opengapps/arm/releases/download/20170811/open_gapps-arm-7.1-pico-20170811.zip
no files listed.
RE: dead link for Open GApps previous versions & boot loop fix
Strange, it seems that in the past day Open GApps has purged their GitHub archive. The "Older Releases" button at their website still redirects to the GitHub repo, but it no longer displays any version other than the current one.
As long as it does not violate any policy, I can always post a copy of the Open GApps 08/11/17 ARM 7.1 Pico package.
Although I have not tried other GApps distributions (Delta, Beans, etc), in theory there is no reason why they shouldn't work, as long as Google Play Services is not newer than v11.3.02. I recommend the minimal GApps available. Installing "pico" was an important part of isolating, and simplifying the search for, the culprit.
As I mentioned in my original post, I tested all versions of Google Play Services on apkmirror newer than v11.3.02 (build format 436 for MT2L03), up until 08/26. All newer builds induced an immediate boot loop. A future version may resolve the boot loop issue and work fine on the MT2L03, but it does not seem to be available as of today.
Have been running custom ROMs on my MT2L03 for years. Boot looping problem began for me two weeks ago when I completely wiped/formatted my CandyROMs v7.1.2 06/15 install and flashed MDMower's 08/19 LineageOS. Began digging deep into the cause (knowing MDMower would not release garbage) and discovered the connection to Play Services. Have been running MDMower's LineageOS & CandyROMs v7.1.2 ever since without any issues.
Remember to use MDMower's TWRP v3.1N0-0, it is much more stable on the MT2L03.
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
RE: MT2 boot loop fix (workaround)
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
hondaman82 said:
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
Click to expand...
Click to collapse
EndlessFall said:
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
Click to expand...
Click to collapse
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
RE: new ROM builds, GApps, & boot loop issue
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing (at least for me). Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
MT2-User said:
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Click to expand...
Click to collapse
EndlessFall said:
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing. Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
Click to expand...
Click to collapse
Thanks!
RE: return of boot loop
Sorry to hear that Hondaman82.
I can only speak from my own experience, which is that my MT2L03 has been stable for the past 2 weeks using Open GApps pico dated no later than 08/11. It is possible that your Google Play Services was auto-updated to a version newer than v11.3.02 (inducing the loop), but you won't be able to tell because you can't boot the corrupted OS to read the version number in app settings. If my boot loop returns, I'll do an ADB pull from TWRP to examine the Play Services package version (curious to see if there is an update correlation).
Goes to show what I mentioned yesterday, which is that the root cause is likely some incompatibility between the ROMs customized for MT2L03 and Play Services that can only be fixed by a commit to the ROM source code, a script, patch, or change to Play Services.
Let's see what happens, perhaps MDMower would be willing to offer his expertise? I visited Matt's website, GitHub and XDA profile, but it seems difficult to contact him directly....
hondaman82 said:
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
Click to expand...
Click to collapse
RE: preventing Google Play Services auto-update
(***SEE UPDATED FIX IN POST #25!***)
For those of you willing to experiment further, there is a method that supposedly disables Google Play Services from updating. This might allow you to "lock in" v11.3.02 until there is a proper fix for the boot loop:
https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832
Basically, this involves using a root file manager to create two empty folders entitled "com.google.android.gms-1.apk" and "com.google.android.gms-2.apk" in the "\data\app" directory, causing auto-update to fail.
I haven't used this hack, try at your own risk!
Of course, this works off of the assumption that updating Google Play Services beyond v11.3.02 is the only factor involved in the boot loop. I just haven't dug deep enough...
Mine (Candy 0725 build) went into LOD by itself a moment ago
Does anyone have a B322 TWRP backup ZIP? I as of this morning have 2 MT2 phones dead. One went into LOD about 3am and the other about 4am.
I'm very new to the rooting community, and I'm well aware of all of the problems. I've messed around, and bricked my phone many times but always knew how to fix it by flashing the custom rom. I've did whole of April until I figured out the proper rooting my model's for 6.0.1 software, and the 7.1.1 software. I eventually got tired of repeating this process, so in May (after I properly rooted my device and everything worked perfectly) I backed up everything including my system in TWRP.
Now the problem is, after using the xui tuner from xposed installer a bit, my phone seemed working for a bit, and lockscreen worked, but it randomly kept restarting at the boot animation . I grew impatient and restarted my phone properly a couple times but it kept rebooting after I unlocked my phone or just waited at my lockscreen. I then started got scared that I damaged something in my system or software, so I went to use TWRP to restore my backup (which I also literally backed up on this Tuesday). It apparently was successful, until the bootlogo freezing and saying my kernal wasn't SEANDROID ENFORCING.
Then now, I kept reformatting my data and restarting but it wouldn't work, it kept failing. So I gave up, and flashed my stock rom. This worked, but I obviously lost all my data. So to possibly help someone, I want to list what I think could've been the problem. (Still new, so I may list alot of unlikely things. Also random order)
1. I didn't format my data before the first restore, thus it failing.
2. Improper backup, I either backed up unnecessary partions like radio, or TWRP just didn't backup properly.
3. My sd card, I had many problems with my sd card before doing this type of stuff, but it went away during may. During may however, I backed up my magisk modules to it too, but they didn't appear on TWRP. Meaning it may have stopped working again. It also deleted my root folder, where I held the magisk zip and uninstaller.
Now this could bring another problem, I was using Magisk and Xposed installer, while also having my stock framework, xposed framework, and sony framwork (this was to use remote play), and in result my phone couldn't handle it and the module from both Magisk and Xposed.
4. I backed up my system while using the ashyx encryption zip, meaning when TWRP restored encrypted files?
5? XUI Tuner, I modified too many things with the app and probably did something to to the root directory. (Most likely Unlikely)
6. I modified my build prop by adding more code like the android users function, and TWRP probably couldn't back that up so it restored wrong like in 2
7? I modified TWRP by using a custom theme in the recovery, making certain functions like backup and restore not work?
8. I was using an old version of TWRP, 3.0.2 instead of 3.2 because 3.2. However, this is because 3.2 didn't work with my phone, and neither did 3.1.
I now flashed the stock rom, and everything works again. I just have to re-root. I didn't lose much data really, and I backed up some stuff in samsung cloud anyway. I just wanted to make this thread so I can fix the problem properly in the future, in which someone else may need it too. This model of samsung phone really isn't popular in the community, so it really would be helpful to other people. The solution could also work for other J700 variants, especially J700T1 since it's the most similar.
P.S. This is also just a small thing to help people too. Rooting this model is actually pretty easy, there's just a catch for one version of it.
6.0.1 can easily be rooted, especially with autoroot. It's works well, and you don't have to lose anydata at ALL! However magisk is untested.
7.1.1 on the other hand does require to format it's data to work so you have to back up anything you want to keep.. Superuser for me made wifi and the flashlight inaccessible, so I had to use Magisk. Which worked fine. There are two different versions of this root though. (Tested Once) One is basically like how the stock rom and has the manual, mobile data quick setting, and battery settings. to get it, don't use ashyx encrptyion . The other is like how you got it your device and set it up normally, no manual or extra settings, and requires ashyx encryption for this. The one I used was the ashyx encrpytion, and I was fine using this method because I kinda already lost everything over and over so I didn't care (end of april).
Edit: Turns out the stock version happens when you flash the stock rom, then immediately flash a custom recovery, and formatting the data without launching the the phone. I think this happens because when you get your phone, and activate it with a carrier sim card it downloads the additional files for that carrier which allows and when you format the data it formats the carrier version instead of the default system on the phone.
I hope we can find a solution for the kernal problem, so other people can fix this properly.
I would also like to ask if someone can make a odin and TWRP flashable kernal file of both the 6.0.1 and 7.1.1 versions of the SM-J700 variants, but for now in this thread the J700T is fine, unless all variants have the same stock kernal. This could be a solution and very helpful.
I have a USA T-Mobile Samsung Galaxy J7 J700TUVU3BQK3 phone and Can someone give me links to where I need to download the firmware ROM for this phone & all the different software I would need to root this phone or modify-backup its operating system??? My computer operating system is windows and also does anyone know how to setup a multiple operating systems on a computer where u can choose to either boot to different versions of windows and lynux.?? Computer Lenovo Gaming Laptop & HP Pavilion Laptop.
This is a debloated/slightly modified ROM. There are NO ASUS apps, and only the bare minimum Google apps. I don't use any of the Fit apps, so they have been removed, but I believe they can be easily reinstalled through the PlayStore. Everything on the watch is significantly faster, except the Bluetooth call lag still exists on 4G, like it does on every device lately. I don't notice the bluetooth lag when the phone and watch are connected to WiFi. There is no watch face installed, so install one from the PlayStore after it boots. I pulled the boot animation from the developer preview, and the clock works during boot. It's pretty sexy.
Within the zip are the boot and recovery files as well, which include TWRP and a patched boot.img for Magisk. You'll need to sideload the latest Magisk Manager to have root access.
DIRECTIONS:
Download and extract Sparrow_7.1.1_Debloat
Boot into fastboot mode.
fastboot -w (This wipes the device, which is HIGHLY recommended.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.simg
I highly recommend starting with fastboot -w to wipe the device. If you run into any issues at all and didn't wipe before install, then wipe and try again before posting issues. Also, pay close attention to the SIMG in system.simg. Type it exactly as it's posted, or copy and paste it. The SIMG is important lol.
Anyone running this ROM should look into this mod by @LeeonLee. Everything is noticeably smoother and lightning fast. I haven't gotten any Bluetooth lag since I implemented it. https://forum.xda-developers.com/ze...parrowaw2-0-enabling-cores-gpu-boost-t3800427
Let me know what you guys think and if I should add/remove anything. I plan to add some more tricks if I update the ROM, including some speed tweaks. Happy Flashing!!!
Appears to work fine here.
CVertigo1 said:
This is a debloated/slightly modified ROM. There are NO ASUS apps, and only the bare minimum Google apps. I don't use any of the Fit apps, so they have been removed, but I believe they can be easily reinstalled through the PlayStore. Everything on the watch is significantly faster, except the Bluetooth call lag still exists on 4G, like it does on every device lately. I don't notice the bluetooth lag when the phone and watch are connected to WiFi. There is no watch face installed, so install one from the PlayStore after it boots. I pulled the boot animation from the developer preview, and the clock works during boot. It's pretty sexy.
Within the zip are the boot and recovery files as well, which include TWRP and a patched boot.img for Magisk. You'll need to sideload the latest Magisk Manager to have root access.
DIRECTIONS:
Download and extract Sparrow_7.1.1_Debloat
Boot into fastboot mode.
fastboot -w (This wipes the device, which is HIGHLY recommended.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.simg
I highly recommend starting with fastboot -w to wipe the device. If you run into any issues at all and didn't wipe before install, then wipe and try again before posting issues. Also, pay close attention to the SIMG in system.simg. Type it exactly as it's posted, or copy and paste it. The SIMG is important lol.
Anyone running this ROM should look into this mod by @LeeonLee. Everything is noticeably smoother and lightning fast. I haven't gotten any Bluetooth lag since I implemented it. https://forum.xda-developers.com/ze...parrowaw2-0-enabling-cores-gpu-boost-t3800427
Let me know what you guys think and if I should add/remove anything. I plan to add some more tricks if I update the ROM, including some speed tweaks. Happy Flashing!!!
Click to expand...
Click to collapse
Hi...I install this rom and the mod leeonlee, my watch have high battery drain, I do not know what to do
Did the battery life get significantly worse compared to stock 2.0? There was no noticeable difference in battery life for me. It was always horrible on 2.0 for me.
I have been running this for almost 3 weeks with @LeeonLee mod, and I haven't gotten any significant Bluetooth lag for calls. Before his mod, it wasn't uncommon that my phone would ring for 5 seconds before the watch showed me someone was calling. I mainly use my watch for riding my motorcycle, so any call lag is a big deal when I can't see who is calling.
I also haven't gotten the "not available" message when using voice commands since the mod.
Hello, I'm using still the stock rom, just rooted + performance patch, watch last 2 days, even 3 days when not used so intensively.
LeeonLee said:
Hello, I'm using still the stock rom, just rooted + performance patch, watch last 2 days, even 3 days when not used so intensively.
Click to expand...
Click to collapse
Maybe I should look into the build.prop mods I added from another watch. Perhaps it's causing excessive battery usage. It could also be that my watch battery is degraded.
which version of magisk manager and how sideload it? i'm little bit noob with adb
Here is a much easier way if you don't know adb too well. Download the latest Magisk installer zip from the Magisk thread onto your PC. I personally am using the 16.4 beta at this time. The Magisk Manager is included in the Magisk zip. Assuming you have TWRP installed, boot into recovery using *adb reboot recovery* or swipe from the top right when booting. The watch is recognized as a storage drive when it's in recovery. Then you can copy the Magisk zip from you PC to your watch, and install it with TWRP. This will give you the latest Magisk and Magisk Manager.
CVertigo1 said:
Here is a much easier way if you don't know adb too well. Download the latest Magisk installer zip from the Magisk thread onto your PC. I personally am using the 16.4 beta at this time. The Magisk Manager is included in the Magisk zip. Assuming you have TWRP installed, boot into recovery using *adb reboot recovery* or swipe from the top right when booting. The watch is recognized as a storage drive when it's in recovery. Then you can copy the Magisk zip from you PC to your watch, and install it with TWRP. This will give you the latest Magisk and Magisk Manager.
Click to expand...
Click to collapse
Never thought about using TWRP to transfer the zip, I just simply pushed it via adb and then rebooted to TWRP to install magisk zip.
BTW, after installing recovery.zip, boot.zip, magisk.zip, I rooted and setup the OnDemand script. It now is much smoother and don't see any noticeable lags. I downloaded System Info Wear to check that the script is actually working. It shows all four cores running at 787Mhz. Kudos to @LeeonLee for the script setup!! Many thanks also to @CVertigo1 !! I also decided to do what @LeeonLee mentioned in regards to stock rom staying put. I wasnt too eager to wipe current system just yet
hi guys... the smartwatch finally is usable.. but i have a question, have the wrist gestures been removed?
Just want to say that I've been using this ROM for a few weeks now, along with the core unlock mod. And it is amazing. The watch is so much more fluid. And with my rather light usage (always on, no gestures) I still get a full day out of the battery. I'm also glad all the extra bloat is gone. No apps I'll never use and no watchfaces I never set.
If you are thinking about switching from stock, highly recommended.
Thanks @CVertigo1
mastermoon said:
hi guys... the smartwatch finally is usable.. but i have a question, have the wrist gestures been removed?
Click to expand...
Click to collapse
Wrist gestures are still there, you just have to turn on that setting under Gesture settings.
bleached45 said:
Just want to say that I've been using this ROM for a few weeks now, along with the core unlock mod. And it is amazing. The watch is so much more fluid. And with my rather light usage (always on, no gestures) I still get a full day out of the battery. I'm also glad all the extra bloat is gone. No apps I'll never use and no watchfaces I never set.
If you are thinking about switching from stock, highly recommended.
Thanks @CVertigo1
Click to expand...
Click to collapse
I really appreciate the kind words. That's exactly what I was going for. I'm not big into searching through a hundred apps to find the few I need, so I prefer my devices to be very militaristic. If I need Fit apps, or any other app, I'll install them separately. They don't need to live in the system. I stripped as much as I could without causing bootloops. I may be able to pull a few more out for the next ROM upload, and I'll also include @LeeonLee mods.
despite my limited modding skills I managed to do everything without doing any damage .. a big thank you to @CVertigo1 and @LeeonLee for the great work ..
Hope @CVertigo1 will be able to port a zenwatch3 rom on 2 one day...
Can I use this rom for wren?
I have just recently installed this on my watch, and it is very nice! The only thing that I noticed is that the pedometer (through Google Fit) does not seem to count the steps I am taking, is this related to some of the files be removed or is it just Google?
I'm not working at the moment but I want to send you a donation as soon as I can. I wanted to thank you because your debloated ROM managed to get my watch booting up once again for the first time in nearly a year. You deserve a donation because you saved me from spending money I don't wanna waste on an entirely new watch.
Is there any way to install some watchfaces stock after installing this Rom?
jnelsoninjax said:
I have just recently installed this on my watch, and it is very nice! The only thing that I noticed is that the pedometer (through Google Fit) does not seem to count the steps I am taking, is this related to some of the files be removed or is it just Google?
Click to expand...
Click to collapse
Is the pedometer really not working on this rom?
djleor said:
Is the pedometer really not working on this rom?
Click to expand...
Click to collapse
nope, but everything else works great.