Related
please delete
Tips & Suggestions, Common Fixes & Questions
please delete
Cant get PC to read watch in step 10 of flashing
I have an Omate 1/8 which arrived yesterday. I factory reset it. I got through steps 1-9 of the recent Rom update. When I tried 10, to connect my watch to my PC, it recognized a "removable disc G:" and told me to insert a disk, but it didn't/couldn't read the watch contents.
(The setup file in step 2 did properly set up according to my pc.)
Anyone able to suggest what I do?
Tom19146 said:
I have an Omate 1/8 which arrived yesterday. I factory reset it. I got through steps 1-9 of the recent Rom update. When I tried 10, to connect my watch to my PC, it recognized a "removable disc G:" and told me to insert a disk, but it didn't/couldn't read the watch contents.
(The setup file in step 2 did properly set up according to my pc.)
Anyone able to suggest what I do?
Click to expand...
Click to collapse
Are you trying to flash the ROM or trying to run the patch? They are two different things. This thread is for the Patch.
No root
Thanks for all your work so far on the x201! Having an issue of no root on the watch...
1. x201 Omate Truesmart
2. Omate_Truesmart_20140120.154604_v2.0
3. Not root after flashing 1.0.2 patch
4. Reverted back to stock, reflashed. Attempted the 1.0.1 version. Security Settings and SU say no root ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!")
urmcgwy said:
Thanks for all your work so far on the x201! Having an issue of no root on the watch...
1. x201 Omate Truesmart
2. Omate_Truesmart_20140120.154604_v2.0
3. Not root after flashing 1.0.2 patch
4. Reverted back to stock, reflashed. Attempted the 1.0.1 version. Security Settings and SU say no root ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!")
Click to expand...
Click to collapse
What OS?
EDIT;
What model?
Lokifish Marz said:
What OS?
Click to expand...
Click to collapse
Sorry Win7 x64
---------- Post added at 09:18 PM ---------- Previous post was at 08:46 PM ----------
urmcgwy said:
Sorry Win7 x64
Click to expand...
Click to collapse
And I have no idea why I wrote Win7.... its Win8.1 x64 =P
---------- Post added at 09:25 PM ---------- Previous post was at 09:18 PM ----------
urmcgwy said:
Sorry Win7 x64
---------- Post added at 09:18 PM ---------- Previous post was at 08:46 PM ----------
And I have no idea why I wrote Win7.... its Win8.1 x64 =P
Click to expand...
Click to collapse
Omate "Developer Edition" 1/8
urmcgwy said:
Sorry Win7 x64
And I have no idea why I wrote Win7.... its Win8.1 x64
Omate "Developer Edition" 1/8
Click to expand...
Click to collapse
Is ADB installed?
Did you disable Quickboot?
Did you enable USB Debugging?
Did the Patch give any errors when you ran it?
Just hard wiped my dev unit, flashed stock Jan20 and ran the Patch v1.0.2. The only thing I had happen was SuperSU tell me the su binary needed to be updated. I am curious as you mention trying to install SuperSU, it's preinstalled by the Patch and should not have to be installed by the user.
Lokifish Marz said:
Is ADB installed?
Did you disable Quickboot?
Did you enable USB Debugging?
Did the Patch give any errors when you ran it?
Just hard wiped my dev unit, flashed stock Jan20 and ran the Patch v1.0.2. The only thing I had happen was SuperSU tell me the su binary needed to be updated. I am curious as you mention trying to install SuperSU, it's preinstalled by the Patch and should not have to be installed by the user.
Click to expand...
Click to collapse
I did all of that according to your instructions and didn't get any errors. Decided to wipe and return to stock, but got an error during flashing (status bar went to 100% really quick and an error popped up around 13 seconds). Watch won't respond to anything including plugging it into a wall charger. Will try with another computer to see if that helps, and then try pulling the battery if that doesn't work. Any advice to unbrick?
urmcgwy said:
I did all of that according to your instructions and didn't get any errors. Decided to wipe and return to stock, but got an error during flashing (status bar went to 100% really quick and an error popped up around 13 seconds). Watch won't respond to anything including plugging it into a wall charger. Will try with another computer to see if that helps, and then try pulling the battery if that doesn't work. Any advice to unbrick?
Click to expand...
Click to collapse
Those errors are really important. Knowing what the error and what color the was was tells me a lot of things. As far as the watch being unresponsive, battery pull or wait a few hours for the battery to die. If you don't want ot void the warranty I suggest waiting for the battery to die.
Something is not right then because if SuperSU (or any file file that matter) was not installed, the script would have given an error.
EDIT:
I don't want to seem like I'm not trying to help but I run the script 20-30 times before a release and use it about 10-15 times a day on a regular basis. In fact I use a slightly modified version to cut down on dev time.
Lokifish Marz said:
Those errors are really important. Knowing what the error and what color the was was tells me a lot of things. As far as the watch being unresponsive, battery pull or wait a few hours for the battery to die. If you don't want ot void the warranty I suggest waiting for the battery to die.
Something is not right then because if SuperSU (or any file file that matter) was not installed, the script would have given an error.
EDIT:
I don't want to seem like I'm not trying to help but I run the script 20-30 times before a release and use it about 10-15 times a day on a regular basis. In fact I use a slightly modified version to cut down on dev time.
Click to expand...
Click to collapse
Sounds good! SuperSU was installed, it just said the binaries weren't installed. I took off the screw covers for the waterproofing warranty, but one of the screws was stripped, so I think I'm out of luck...the watch is off so I don't think the battery will even drain. I guess it is time to see what Omate customer service is made of.
urmcgwy said:
Sounds good! SuperSU was installed, it just said the binaries weren't installed. I took off the screw covers for the waterproofing warranty, but one of the screws was stripped, so I think I'm out of luck...the watch is off so I don't think the battery will even drain. I guess it is time to see what Omate customer service is made of.
Click to expand...
Click to collapse
Unless you pull the battery, the watch may appear to be off but stuck on bootloader mode. It's happened to me a couple times as well.
If yours is anything like mine, the placement screws are better than the ones in the TS.
Lokifish Marz said:
Unless you pull the battery, the watch may appear to be off but stuck on bootloader mode. It's happened to me a couple times as well.
If yours is anything like mine, the placement screws are better than the ones in the TS.
Click to expand...
Click to collapse
Thanks for all the help! I'll just wait until tomorrow to see if the watch dies on me and see what Omate has to say. Really appreciate the quick responses!
I just flashed back to stock, what next is needed?
Following Lokifish's very helpful video, I have finally succeeded in flashing back to stock. Do I need now to do a security patch, or was that included in the stock file I'd have used? Also, how might I obtain some of the useful additions that Loki installed in Imperium, working from stock?
Thanks for all your help!
Tom
Tom19146 said:
Following Lokifish's very helpful video, I have finally succeeded in flashing back to stock. Do I need now to do a security patch, or was that included in the stock file I'd have used? Also, how might I obtain some of the useful additions that Loki installed in Imperium, working from stock?
Thanks for all your help!
Tom
Click to expand...
Click to collapse
If you flashed back to stock then none of the improvements listed in the OP will be found on your device. Stock is exactly that, stock with no changes at all.
Except for some build.prop edits, removing preinstalled apps like FB and a different launcher, there is no difference between the patch and the ROM. I in fact use a slightly modified version of the Patch myself to build the test builds of the ROM.
Lokifish Marz said:
If you flashed back to stock then none of the improvements listed in the OP will be found on your device. Stock is exactly that, stock with no changes at all.
Except for some build.prop edits, removing preinstalled apps like FB and a different launcher, there is no difference between the patch and the ROM. I in fact use a slightly modified version of the Patch myself to build the test builds of the ROM.
Click to expand...
Click to collapse
I am not sure if I understood. Weren't there some security issues you helped address,( before Imperium), that were recommended to add to the stock rom?
Are you saying if I do this patch, I will basically have the Rom plus some adjustments? Are these security related or just improvements, tweaks and some helpful programs? Either way, I think I will prefer this to the basic stock. (I took your reply to suggest there might be no need to do the patch, that it is useful to you but not so necessary...)
Tom
Oh, by the way, for us true newbies, it might be helpful to offer some advice how best to negotiate the downloads at host-dev... I found myself in a hellish loop of websites offering that I join for free but then never giving a way to get past the "upgrade to premium" offers. In the end, I downloaded iLivid download manager and got it to work.
Tom19146 said:
I am not sure if I understood. Weren't there some security issues you helped address,( before Imperium), that were recommended to add to the stock rom?
Are you saying if I do this patch, I will basically have the Rom plus some adjustments? Are these security related or just improvements, tweaks and some helpful programs? Either way, I think I will prefer this to the basic stock. (I took your reply to suggest there might be no need to do the patch, that it is useful to you but not so necessary...)
Tom
Oh, by the way, for us true newbies, it might be helpful to offer some advice how best to negotiate the downloads at host-dev... I found myself in a hellish loop of websites offering that I join for free but then never giving a way to get past the "upgrade to premium" offers. In the end, I downloaded iLivid download manager and got it to work.
Click to expand...
Click to collapse
Fixes have not made it to official firmware yet.
Rom = Patch + extras
Use an adblocker and only the actual download button will be seen.
Thanks. All working with the patch now.
---------- Post added at 07:38 PM ---------- Previous post was at 06:40 PM ----------
I successfully downloaded the patch. I was downloading apps and after downloading cal from the Omate store, it froze. I cannot shut the phone off. Neither button. Touch screen unresponsive. Is there any other way to reboot things than to take the battery out? Any reset pin hole or such?
Tom19146 said:
Thanks. All working with the patch now.
---------- Post added at 07:38 PM ---------- Previous post was at 06:40 PM ----------
I successfully downloaded the patch. I was downloading apps and after downloading cal from the Omate store, it froze. I cannot shut the phone off. Neither button. Touch screen unresponsive. Is there any other way to reboot things than to take the battery out? Any reset pin hole or such?
Click to expand...
Click to collapse
Iv'e had that happen to me a couple of times even when on stock w no patch. Short of pulling the battery you have to wait for the battery to die.
Omate TS slow and built-in memory full
Hi all, hopefully this time I am posting in the right place. After flashing the patch my TS seems to be slower and seems to ignore storing things on the sd card. The TS memory now has only 228mb free and the SD card is all free (this is set up as the default storage). Has anybody come across a similar situation (TS slow and memory full) and how could I overcome that? Many thanks in advance (please be patient, I am not an expert)!
I have an MT2-L05, applied the new B606 update, but now I can't restore an older version of the firmware. B606 wiped out TWRP, when I try and reinstall TWRP, I can no longer get into recover. Is there any way to flash one of the older firmwares? I can flash B603 which is the beta version of B606 but it doesn't seem to do me any good.
tomlemange said:
I have an MT2-L05, applied the new B606 update, but now I can't restore an older version of the firmware. B606 wiped out TWRP, when I try and reinstall TWRP, I can no longer get into recover. Is there any way to flash one of the older firmwares? I can flash B603 which is the beta version of B606 but it doesn't seem to do me any good.
Click to expand...
Click to collapse
Use Dload method to install via OTG & SD card
tomlemange said:
I have an MT2-L05, applied the new B606 update, but now I can't restore an older version of the firmware. B606 wiped out TWRP, when I try and reinstall TWRP, I can no longer get into recover. Is there any way to flash one of the older firmwares? I can flash B603 which is the beta version of B606 but it doesn't seem to do me any good.
Click to expand...
Click to collapse
TWRP for MT2-L05 on b606...... Works great for me :
http://forum.xda-developers.com/ascend-mate2/development/recovery-t2979471#post57676235
This thread is almost a month old but regardless I must still put my two cents in it . A TWRP build won't be harmed by an update typically, unless the partition layouts were modified which RARELY happens, a new kernel was installed by the result of accepting a new update or a modification to the boot loader (which usually occurs when there is a new kernel involved). Normally, when it is kernel related, you can literally just unpack the custom recovery and new stock recovery images so you may swap out the kernel binaries then rebuild. Not the best method but it will most certainly do the job until an official build has been updated to reflect the latest changes in whatever update the phone may had received.
---------- Post added at 03:23 AM ---------- Previous post was at 03:16 AM ----------
Should the partition happen to be modified then it is not recommended to use the last TWRP build. A Dev must update the device tree to reflect the new partition layout and their sizes.
MT2-L05_EMUI3.0B60x_toEMUI2.3B600SP2_downgrade
Click to expand...
Click to collapse
This did the trick for me. Can be used to downgrade from 60x to B600SP2, which would allow a downgrade to B408 - Subfirmware B404 could then be used to downgrade from B408 to B404 and then to B109SP1, the old basic version
thomascook said:
This did the trick for me. Can be used to downgrade from 60x to B600SP2, which would allow a downgrade to B408 - Subfirmware B404 could then be used to downgrade from B408 to B404 and then to B109SP1, the old basic version
Click to expand...
Click to collapse
Ever find a link for B600SP2? All the links I found on google point to the Huawei website and those links are broken. I think emui 3.0 gives me less than reliable sms results so I'd like to try emui 2.3
I have a 16gb wifi 7" HDX (Thor).
I was on 13.3.2.4 forever rooted with ota blocked. I saw TWRP was available and the latest SW too. I enjoy it on the HD7 we have, so I figured I"d flash TWRP, then install the latest rom 14.4.5.2.
I had to downgrade in order to flash TWRP, so I used safestrap and flashed the roll back images provided by @ggow and followed the instructions listed here - http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 - with no problems at this point. I then booted up into the 13.3.1.0 with a factory wiped system.
I then installed towelroot, rooted, installed flashify and installed TWRP recovery 2.8.5.0 from here - http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Once that was done, I flashed the 14.4.5.2 TWRP file provided by @Cpasjuste - http://forum.xda-developers.com/showpost.php?p=57988207&postcount=19
Booted up and followed the guide provided here - http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550 - to install gapps and stop OTA. The only thing I think I did different was, when I was prompted to overwrite certain system files when copying gapps folders over, I declined. Unfortunately the tablet is at home and I can't get to it until tonight.
My problem - Amazon Instant Video and my Kindle Library won't load properly. I can install apps, listen to Amazon music, and shop the store, but I cannot get video or books to work.
I will try to re-copy the gapps packages over and let everything overwrite, but I'm not sure if that is the issue.
Has anyone experienced this before?
Thanks.
riggsandroid said:
I have a 16gb wifi 7" HDX (Thor).
I was on 13.3.2.4 forever rooted with ota blocked. I saw TWRP was available and the latest SW too. I enjoy it on the HD7 we have, so I figured I"d flash TWRP, then install the latest rom 14.4.5.2.
I had to downgrade in order to flash TWRP, so I used safestrap and flashed the roll back images provided by @ggow and followed the instructions listed here - http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 - with no problems at this point. I then booted up into the 13.3.1.0 with a factory wiped system.
I then installed towelroot, rooted, installed flashify and installed TWRP recovery 2.8.5.0 from here - http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Once that was done, I flashed the 14.4.5.2 TWRP file provided by @Cpasjuste - http://forum.xda-developers.com/showpost.php?p=57988207&postcount=19
Booted up and followed the guide provided here - http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550 - to install gapps and stop OTA. The only thing I think I did different was, when I was prompted to overwrite certain system files when copying gapps folders over, I declined. Unfortunately the tablet is at home and I can't get to it until tonight.
My problem - Amazon Instant Video and my Kindle Library won't load properly. I can install apps, listen to Amazon music, and shop the store, but I cannot get video or books to work.
I will try to re-copy the gapps packages over and let everything overwrite, but I'm not sure if that is the issue.
Has anyone experienced this before?
Thanks.
Click to expand...
Click to collapse
You have to upgrade to OS 3.2.3.2.3, it doesn't work with 3.1.0
kulturschock said:
You have to upgrade to OS 3.2.3.2.3, it doesn't work with 3.1.0
Click to expand...
Click to collapse
i'm currently on 13.4.5.2 - not 13.3.1.0.
Can you clarify what you mean?
Thanks.
riggsandroid said:
i'm currently on 13.4.5.2 - not 13.3.1.0.
Can you clarify what you mean?
Thanks.
Click to expand...
Click to collapse
You have flashed the 13.4.5.2 over the 13.3.1.0 not over the 13.3.2.3, this is the problem. I had the same problem.
You can find infos in the nexus 2.0.5 thread, I think, the problem has the same reason. I think, you need the bootloaader or the kernel of the 13.3.2.3 OS.
There is a thread with the kernel of the 13.3.2.3 to flash, perhaps this works. Otherwise
You have to flash the whole bin-file, then root, then flash twrp and then flash the higher 13.4.5.2 OS. This worked for me.
---------- Post added at 07:49 PM ---------- Previous post was at 06:54 PM ----------
Here is the link to the thread of the bootloader you need:
http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
kulturschock said:
You have flashed the 13.4.5.2 over the 13.3.1.0 not over the 13.3.2.3, this is the problem. I had the same problem.
You can find infos in the nexus 2.0.5 thread, I think, the problem has the same reason. I think, you need the bootloaader or the kernel of the 13.3.2.3 OS.
There is a thread with the kernel of the 13.3.2.3 to flash, perhaps this works. Otherwise
You have to flash the whole bin-file, then root, then flash twrp and then flash the higher 13.4.5.2 OS. This worked for me.
Click to expand...
Click to collapse
i'm going to try flashing the updated bootloader in TWRP first provided here - http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
Did you have the SAME issues that I've listed or just similar?
Looks like you updated your post as I was making mine. Will let you know how it goes tonight.
I had the same problem, I got messages with license error in prime video, many others things worked normally but not all. For example, l couldn't flash other OS like my backup of the 3.2.6 made by safestrap, this worked well, too.
kulturschock said:
I had the same problem, I got messages with license error in prime video, many others things worked normally but not all. For example, l couldn't flash other OS like my backup of the 3.2.6 made by safestrap, this worked well, too.
Click to expand...
Click to collapse
Yea that didn't fix it. Next I'm going to deregister and reflash the 13.4.5.2 and see if that fixes it.
Can I just flash the 3.2.3.2 bin with twrp?
Edit
So I deregistered, wiped and reflashed 13.4.5.2 and have working video and books again. Haven't touched gapps yet but glad to see its semi sorted.
Errors While Trying To Install CyanogenMod
I am currently trying to install cyanogenmod on my HAM2. I have an unlocked bootloader, latest version of TWRP installed, and cynogenmod in the root of my sd card. I have cleared my cache, delvik cache, and system as well. However I keep getting an error telling me "unable to mount storage during GUI start up" and the other saying that there was an "error executing updater binary in zip external sdcard cyanogemod." Can someone please assist me as to how to resolve this issue ?
Are you using the correct version of TWRP? You can find it at http://android.cmphys.com/twrp-mt2/ . Also did you update to B322 before flashing.?You can also find instructions here. Its from the PAC thread but it applies to Cyanogenmod as well you can find it here http://forum.xda-developers.com/showpost.php?p=62508471&postcount=3 . the TWRP version listed in the instructions is the old one but either one should work. There's also videos that show you how to flash TWRP and install Cyanogenmod step by step. You can find them here https://www.youtube.com/user/superbass311 . There's also a starter pack for new users that might be helpful you can find it here https://drive.google.com/file/d/0B9t_gcL17JqtSnV0eGpiLWpHaWs/view . its mostly text files with links to what you will need. try this and see if this helps any.
robertbarber said:
Are you using the correct version of TWRP? You can find it at http://android.cmphys.com/twrp-mt2/ . Also did you update to B322 before flashing.?You can also find instructions here. Its from the PAC thread but it applies to Cyanogenmod as well you can find it here http://forum.xda-developers.com/showpost.php?p=62508471&postcount=3 . the TWRP version listed in the instructions is the old one but either one should work. There's also videos that show you how to flash TWRP and install Cyanogenmod step by step. You can find them here https://www.youtube.com/user/superbass311 . There's also a starter pack for new users that might be helpful you can find it here https://drive.google.com/file/d/0B9t_gcL17JqtSnV0eGpiLWpHaWs/view . its mostly text files with links to what you will need. try this and see if this helps any.
Click to expand...
Click to collapse
Hi Robert, yes I am currently running TWRP 2.8.7.0 right now and yes I was running b322 at the time of install. I followed that same video actually, step by step. I have actually done it twice now, and I still receive the same error. I will go ahead and try the starter pack you gave to me. Ill update soon.
Did you wipe Data as well when you did your wipe? You didn't include it in your original post so I figured I would ask?
Which version ham/2 do you have? CC or stock or what.
Try an older version of CM. I ran into some strange SD card behavior yesterday. Go back a week or so and try to install.
cookiejuice said:
I am currently trying to install cyanogenmod on my HAM2. I have an unlocked bootloader, latest version of TWRP installed, and cynogenmod in the root of my sd card. I have cleared my cache, delvik cache, and system as well. However I keep getting an error telling me "unable to mount storage during GUI start up" and the other saying that there was an "error executing updater binary in zip external sdcard cyanogemod." Can someone please assist me as to how to resolve this issue ?
Click to expand...
Click to collapse
KimTyson is correct. There was an issue. Download an older version of CM and try again. It has been confirmed by three people. I still use 9/17/2015.
Sorry I did not post earlier but using a the version of twrp that was suggested to me actually worked, I am not sure if it was something i did wrong on my part but everything is working fine now
cookiejuice said:
Sorry I did not post earlier but using a the version of twrp that was suggested to me actually worked, I am not sure if it was something i did wrong on my part but everything is working fine now
Click to expand...
Click to collapse
Good to hear! Welcome to XDA!
Hey everyone!
It's been a while since I've done a ROM and I had a hankering to play around and have some fun again. This build is nothing super special but it is a base for me to work with and I figured I would share it with anyone who is interested.
This build is an almost 100% stock odexed ROM. The only difference from this and flashing a stock TAR is that this can be flashed through recovery and comes pre-rooted.
I'm currently working on a deodexed ROM for devs and themers to use as a base if they are so inclined but I'm having issues with my Java environment.
REQUIREMENTS:You MUST be on a Lollipop bootloader in order for this ROM to work. I recommend flashing the OG1 Stock TAR and then Philz Recovery through Odin prior to flashing the ROM.
ROM FLASHING:- Boot to your custom recovery (recommended recovery is Philz Touch v6.41.6).
- Wipe Cache.
- Wipe Dalvik Cache.
- Wipe System and Data (Under "Wipe Data/Factory Reset" and then "Clean to Install a New ROM" in Philz Touch).
- Flash ROM!
- Enjoy!
As a side-note I would strongly recommend flashing Tdunham's Debloat tool before running the ROM for the first time. It comes with a TON of bloat (thank you Sprint and Samsung!). You can get the Debloat tool in the attachments on this post: http://forum.xda-developers.com/spr...ent/stock-rom-od3-android-l-deodexed-t3128908
CHANGELOG:OG1 Stock Rooted Odexed v1.2 - (Released 11/18/15)
- Changed root method to be consistent with changes in my Mostly Stock OG1 ROM
OG1 Stock Rooted Odexed v1.1 - (Released 10/7/15)
- Fixed issue with root access not sticking
OG1 Stock Rooted Odexed v1.0 - Initial Release (Released 10/6/15)
- Added Root to Stock Odexed ROM
DOWNLOADS: Odexed OG1 ROM
OG1 Stock Restore TAR
Philz Touch Recovery v6.41.6
Enjoy!
It says it comes pre-rooted.. It doesn't seem to be pre-rooted. I followed the instructions precisely even running the Dbloat right after flashing the firmware. What did I do wrong? Super SU won't function. Busybox won't install. What gives?
fbarcenas said:
It says it comes pre-rooted.. It doesn't seem to be pre-rooted. I followed the instructions precisely even running the Dbloat right after flashing the firmware. What did I do wrong? Super SU won't function. Busybox won't install. What gives?
Click to expand...
Click to collapse
Good question... Can you do me a favor and download Root Check from the Play Store and see if it shows you as rooted?
rwilco12 said:
Good question... Can you do me a favor and download Root Check from the Play Store and see if it shows you as rooted?
Click to expand...
Click to collapse
Root Checker responds "Sorry! Root access is not properly installed on this device." Do ya think the Dbloat nerfed it?
---------- Post added at 04:13 AM ---------- Previous post was at 04:10 AM ----------
I don't think the debloat nerfed it the script does not contain a line for deleting busybox nor Super SU.
Code:
delete_recursive("/system/app/Blurb");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/DriveLink");
delete_recursive("/system/app/DriveLinkRemote");
delete_recursive("/system/app/Flipboard");
delete_recursive("/system/app/GeoLookout");
delete_recursive("/system/app/Headlines");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/SamsungAppsWidget_Phone_Carrier");
delete_recursive("/system/app/SecKidsModeInstaller");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/ConnectionManager");
delete_recursive("/system/priv-app/ID");
delete_recursive("/system/priv-app/SamsungApps_K");
delete_recursive("/system/priv-app/SamsungBilling");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/SNS");
delete_recursive("/system/priv-app/Zone");
delete_recursive("/data/app/com.google.android.apps.books-1");
delete_recursive("/data/app/com.google.android.apps.books-2");
delete_recursive("/data/app/com.google.android.apps.magazines-1");
delete_recursive("/data/app/com.google.android.apps.magazines-2");
delete_recursive("/data/app/com.google.android.play.games-1");
delete_recursive("/data/app/com.google.android.play.games-2");
delete_recursive("/data/app/com.lookout-1");
delete_recursive("/data/app/com.lookout-2");
delete_recursive("/data/app/com.nascar.nascarmobile-1");
delete_recursive("/data/app/com.nascar.nascarmobile-2");
delete_recursive("/data/app/com.nbadigital.gametimelite-1");
delete_recursive("/data/app/com.nbadigital.gametimelite-2");
delete_recursive("/data/app/com.pinsight.eureka.offers-1");
delete_recursive("/data/app/com.pinsight.eureka.offers-2");
delete_recursive("/data/app/com.pinsightmedia.vpl.Amazon-1");
delete_recursive("/data/app/com.pinsightmedia.vpl.Amazon-2");
delete_recursive("/data/app/com.sprint.android.musicplus2033-1");
delete_recursive("/data/app/com.sprint.android.musicplus2033-2");
delete_recursive("/data/app/com.wipit.sprintmoneyexpress-1");
delete_recursive("/data/app/com.wipit.sprintmoneyexpress-2");
delete_recursive("/data/app/flipboard.app-1");
delete_recursive("/data/app/flipboard.app-2");
delete_recursive("/data/app/com.mobiroo.xgen-1");
delete_recursive("/data/app/com.mobiroo.xgen-2");
delete_recursive("/data/app/com.google.android.apps.docs-1");
delete_recursive("/data/app/com.google.android.apps.docs-2");
delete_recursive("/data/app/com.telenav.app.android.scout_us-1");
delete_recursive("/data/app/com.telenav.app.android.scout_us-2");
delete_recursive("/data/app/com.sprint.w.v8-1");
delete_recursive("/data/app/com.sprint.w.v8-2");
delete_recursive("/data/app/com.sprint.international.message-1");
delete_recursive("/data/app/com.sprint.international.message-2");
delete_recursive("/data/app/com.google.android.videos-1");
delete_recursive("/data/app/com.google.android.videos-2");
delete_recursive("/data/app/com.google.android.music-1");
delete_recursive("/data/app/com.google.android.music-2");
fbarcenas said:
Root Checker responds "Sorry! Root access is not properly installed on this device." Do ya think the Dbloat nerfed it?
---------- Post added at 04:13 AM ---------- Previous post was at 04:10 AM ----------
I don't think the debloat nerfed it the script does not contain a line for deleting busybox nor Super SU.
Code:
delete_recursive("/system/app/Blurb");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/DriveLink");
delete_recursive("/system/app/DriveLinkRemote");
delete_recursive("/system/app/Flipboard");
delete_recursive("/system/app/GeoLookout");
delete_recursive("/system/app/Headlines");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/SamsungAppsWidget_Phone_Carrier");
delete_recursive("/system/app/SecKidsModeInstaller");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/ConnectionManager");
delete_recursive("/system/priv-app/ID");
delete_recursive("/system/priv-app/SamsungApps_K");
delete_recursive("/system/priv-app/SamsungBilling");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/SNS");
delete_recursive("/system/priv-app/Zone");
delete_recursive("/data/app/com.google.android.apps.books-1");
delete_recursive("/data/app/com.google.android.apps.books-2");
delete_recursive("/data/app/com.google.android.apps.magazines-1");
delete_recursive("/data/app/com.google.android.apps.magazines-2");
delete_recursive("/data/app/com.google.android.play.games-1");
delete_recursive("/data/app/com.google.android.play.games-2");
delete_recursive("/data/app/com.lookout-1");
delete_recursive("/data/app/com.lookout-2");
delete_recursive("/data/app/com.nascar.nascarmobile-1");
delete_recursive("/data/app/com.nascar.nascarmobile-2");
delete_recursive("/data/app/com.nbadigital.gametimelite-1");
delete_recursive("/data/app/com.nbadigital.gametimelite-2");
delete_recursive("/data/app/com.pinsight.eureka.offers-1");
delete_recursive("/data/app/com.pinsight.eureka.offers-2");
delete_recursive("/data/app/com.pinsightmedia.vpl.Amazon-1");
delete_recursive("/data/app/com.pinsightmedia.vpl.Amazon-2");
delete_recursive("/data/app/com.sprint.android.musicplus2033-1");
delete_recursive("/data/app/com.sprint.android.musicplus2033-2");
delete_recursive("/data/app/com.wipit.sprintmoneyexpress-1");
delete_recursive("/data/app/com.wipit.sprintmoneyexpress-2");
delete_recursive("/data/app/flipboard.app-1");
delete_recursive("/data/app/flipboard.app-2");
delete_recursive("/data/app/com.mobiroo.xgen-1");
delete_recursive("/data/app/com.mobiroo.xgen-2");
delete_recursive("/data/app/com.google.android.apps.docs-1");
delete_recursive("/data/app/com.google.android.apps.docs-2");
delete_recursive("/data/app/com.telenav.app.android.scout_us-1");
delete_recursive("/data/app/com.telenav.app.android.scout_us-2");
delete_recursive("/data/app/com.sprint.w.v8-1");
delete_recursive("/data/app/com.sprint.w.v8-2");
delete_recursive("/data/app/com.sprint.international.message-1");
delete_recursive("/data/app/com.sprint.international.message-2");
delete_recursive("/data/app/com.google.android.videos-1");
delete_recursive("/data/app/com.google.android.videos-2");
delete_recursive("/data/app/com.google.android.music-1");
delete_recursive("/data/app/com.google.android.music-2");
Click to expand...
Click to collapse
I'm 99% positive it wasn't the debloat script. My guess is that for some reason root didn't stick when it was flashed. Can you try flashing the ROM again without wiping first? See if maybe flashing over it fixes it for you? If that doesn't let's try a clean slate with a full wipe and flash again. When I flashed it earlier I got root with each flash, I did it three times just to be sure prior to posting.
no root
I'm also having issues with root. Root checker says the device is rooted, but no root dependent apps will function and I never get the prompt to grant rights. Dirty flashing the rom again to see if it helps.
---------- Post added at 09:09 AM ---------- Previous post was at 08:16 AM ----------
Cubit33 said:
I'm also having issues with root. Root checker says the device is rooted, but no root dependent apps will function and I never get the prompt to grant rights. Dirty flashing the rom again to see if it helps.
Click to expand...
Click to collapse
When I first did a wipe and flashed this rom, before rebooting my Philz recovery prompted a warning that the rom might flash stock recovery, do I want to allow this? The first time I said no, following the dirty flash just now I said yes and root appears to be working now. Possibly just a weird recovery bug?
rwilco12 said:
I'm 99% positive it wasn't the debloat script. My guess is that for some reason root didn't stick when it was flashed. Can you try flashing the ROM again without wiping first? See if maybe flashing over it fixes it for you? If that doesn't let's try a clean slate with a full wipe and flash again. When I flashed it earlier I got root with each flash, I did it three times just to be sure prior to posting.
Click to expand...
Click to collapse
I don´t think you're doing a full wipe before you install. the remnant files are giving you root. Try formatting system before doing your install. I'm going to try formatting system before trying it again.
Cubit33 said:
When I first did a wipe and flashed this rom, before rebooting my Philz recovery prompted a warning that the rom might flash stock recovery, do I want to allow this? The first time I said no, following the dirty flash just now I said yes and root appears to be working now. Possibly just a weird recovery bug?
Click to expand...
Click to collapse
fbarcenas said:
I don´t think you're doing a full wipe before you install. the remnant files are giving you root. Try formatting system before doing your install. I'm going to try formatting system before trying it again.
Click to expand...
Click to collapse
I found the source of the issue and have uploaded a fix!
Let's just say its not a good idea to work on two projects at once.
v1.1 is now available via the links in the OP. Thank you for your patience!
OK I've done the dirty flash twice now. Once were I hit DISABLE and the other time I hit NO. Both times I ran Root Checker and both times it said it was not rooted.
Any Ideas?
---------- Post added 8th October 2015 at 12:25 AM ---------- Previous post was 7th October 2015 at 11:36 PM ----------
What root method are you using? maybe we should just run the root script you used. Towelroot, doomlord?
fbarcenas said:
OK I've done the dirty flash twice now. Once were I hit DISABLE and the other time I hit NO. Both times I ran Root Checker and both times it said it was not rooted.
Any Ideas?
Click to expand...
Click to collapse
I uploaded an updated build a few hours ago that should fix the issue. Have you tried that new build?
rwilco12 said:
I uploaded an updated build a few hours ago that should fix the issue. Have you tried that new build?
Click to expand...
Click to collapse
Nope. I will give that a shot.
Thanks flashing it now and putting the phone back in the drawer, its my backup phone now that I got an S6. I do get it out time to time to play with it and see what's new lol
I did the ROM INSTALL WIPE. I ran the installer twice one saying NO after the reboot prompt and one saying yes. In both instances I did not have root and busybox was not installed.
fbarcenas said:
I did the ROM INSTALL WIPE. I ran the installer twice one saying NO after the reboot prompt and one saying yes. In both instances I did not have root and busybox was not installed.
Click to expand...
Click to collapse
Did you try it with the new upload? Version 1.1?
rwilco12 said:
Did you try it with the new upload? Version 1.1?
Click to expand...
Click to collapse
Yeah That is what I was talking about. V1 installs busybox and supersu, but does not give root. V1.1 does not install busybox, nor does it give root.
I'm tempted to revert to pure stock and use the SKIPSOFT UNIFIED ANDROID TOOLKIT to acquire root and make my own ROM distro. Nothing seems to be working right with these ROM. How are you testing your ROMs before deployment? Are you doing a full nandroid backup of your phone and a full wipe before testing these? Or are we the guinea pigs?
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
I would like to suggest that you publish the MD5 hash of your file next to the download link, so the we can verify that we have a good copy and that the downloaded file is not corrupt.
fbarcenas said:
Yeah That is what I was talking about. V1 installs busybox and supersu, but does not give root. V1.1 does not install busybox, nor does it give root.
I'm tempted to revert to pure stock and use the SKIPSOFT UNIFIED ANDROID TOOLKIT to acquire root and make my own ROM distro. Nothing seems to be working right with these ROM. How are you testing your ROMs before deployment? Are you doing a full nandroid backup of your phone and a full wipe before testing these? Or are we the guinea pigs?
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
I would like to suggest that you publish the MD5 hash of your file next to the download link, so the we can verify that we have a good copy and that the downloaded file is not corrupt.
Click to expand...
Click to collapse
You're definitely not the guinea pigs.
When I do my testing I will revert back to a 100% stock ROM by flashing one of my one-click Odin packages and then flash recovery. I then flash the ROM and test it out. While doing the testing I don't actually make a Nandroid, all I do is a TB backup that is then moved to my PC to avoid any cross contamination. I repeat the process a minimum of three times before posting.
To clarify a point - Busybox is installed when you flash the ROM. You don't need the app to install it. The app you normally see is a Busybox Installer. It adds the functionality to the system files the same way the updaterscript can (and in this case does) when flashing a ROM. Busybox is really just a bunch of fancy symlinks that create a "toolbox" in system\bin.
I'm not sure why you are having the issues with root, but myself and several others (I show the ROM has been downloaded 68 times) have had success with it. Where you are continuing to have issues, even with the updated version, I would maybe recommend you hold off on flashing this one and wait either for my Mostly Stock ROM I am working on or for another ROM that you like.
fbarcenas said:
Yeah That is what I was talking about. V1 installs busybox and supersu, but does not give root. V1.1 does not install busybox, nor does it give root.
I'm tempted to revert to pure stock and use the SKIPSOFT UNIFIED ANDROID TOOLKIT to acquire root and make my own ROM distro. [emoji14] Nothing seems to be working right with these ROM. How are you testing your ROMs before deployment? Are you doing a full nandroid backup of your phone and a full wipe before testing these? Or are we the guinea pigs?
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
I would like to suggest that you publish the MD5 hash of your file next to the download link, so the we can verify that we have a good copy and that the downloaded file is not corrupt.
Click to expand...
Click to collapse
The rom works...the idea of an MD5 isn't a bad one, and I'm sure that the OP could add it...the dev provided a pre-rooted, stock rom that works as advertised...it's free for you to avail or no; however, the suggestion that he is deploying the users of this forum as test subjects for his own, untested work is untrue.
You want to not use it? Fine, they don't. You wish to make your own? Please, have at it.
But to come into a man's thread and announce that you'll build your own hewn from a toolkit, then distribute it, because his didn't work for you, when it's working for others, seems unwarranted at best.
#WhiteUIsMustDie, #EndDarkAppOppression
fbarcenas said:
Yeah That is what I was talking about. V1 installs busybox and supersu, but does not give root. V1.1 does not install busybox, nor does it give root.
I'm tempted to revert to pure stock and use the SKIPSOFT UNIFIED ANDROID TOOLKIT to acquire root and make my own ROM distro. Nothing seems to be working right with these ROM. How are you testing your ROMs before deployment? Are you doing a full nandroid backup of your phone and a full wipe before testing these? Or are we the guinea pigs?
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
I would like to suggest that you publish the MD5 hash of your file next to the download link, so the we can verify that we have a good copy and that the downloaded file is not corrupt.
Click to expand...
Click to collapse
micmars said:
The rom works...the idea of an MD5 isn't a bad one, and I'm sure that the OP could add it...the dev provided a pre-rooted, stock rom that works as advertised...it's free for you to avail or no; however, the suggestion that he is using the users of this forum as test subjects for his own, untested work is unwarranted.
You want to not use it? Fine, they don't. You wish to make your own? Please, have at it.
But to come into a man's thread and announce that you'll build your own hewn from a toolkit, then distribute it, because his didn't work for you, when it's working for others, seems unwarranted at best.
#WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
^ I cannot agree more with this. Use it or don't, but do not come into a developers thread and discuss making your own ROM, it's rude, disrespectful and completely unwarranted. Good luck on these forums with an attitude like that...
rwilco12 said:
You're definitely not the guinea pigs.
When I do my testing I will revert back to a 100% stock ROM by flashing one of my one-click Odin packages and then flash recovery. I then flash the ROM and test it out. While doing the testing I don't actually make a Nandroid, all I do is a TB backup that is then moved to my PC to avoid any cross contamination. I repeat the process a minimum of three times before posting.
To clarify a point - Busybox is installed when you flash the ROM. You don't need the app to install it. The app you normally see is a Busybox Installer. It adds the functionality to the system files the same way the updaterscript can (and in this case does) when flashing a ROM. Busybox is really just a bunch of fancy symlinks that create a "toolbox" in system\bin.
I'm not sure why you are having the issues with root, but myself and several others (I show the ROM has been downloaded 68 times) have had success with it. Where you are continuing to have issues, even with the updated version, I would maybe recommend you hold off on flashing this one and wait either for my Mostly Stock ROM I am working on or for another ROM that you like.
Click to expand...
Click to collapse
Thanks I got desperate and reverted to stock and rooted it with the Unified Android Tookit, and ran the D bloat script. I just couldn't wait any longer. Thank you for your hard work and patience anyways.
And to all the haters.
Does this have all the boatware?
Sent from my SM-G900P using XDA Free mobile app