I came upon this device on Christmas (a gift from my girlfriend to her father) and wanted to root it and also install clockworkmod recovery, so I could mess with it a bit without bricking it. Since I found a lack of tailored guides for it, I decided to write this one, although I really did no actual development whatsoever. Normally I would be posting this on general, but given the spirit of this forum, I guess I'll just leave it here. Also, keep in mind I don't have the device anymore and am writing this from memory. If I missed anything or you have any doubts, please let me know (for example, I can't recall specifically the drivers I installed to make it work properly).
Please, please read the whole guide before trying anything, and if you are a novice user, just leave this be, I don't want you to turn your tablet into a paperweight because of my shoddy instructions written from memory and you probably don't need any of this anyway as there are no custom roms yet.
!!!DISCLAIMER!!!: As stated above, anything you do is at your own risk. I provided the procedures that worked for me on a Qilive 97r tablet, which is an Auchan branded ARCHOS 97b Platinum HD, so my step by step should work for all of you. There are probably easier ways to do this, and I hint at them in the guide, but beware I have not tried them and cannot vouch for them. In fact, I cannot and will not take any responsability if you brick your device following these instructions, correctly or otherwise. You do this at YOUR OWN RISK. You have been warned!
Rooting:
I followed this guide on Windows 7 x64 and it worked perfectly.
So thanks to dhigby for that. I would just like to make a couple of remarks:
When you get to step 7 (Installing Superuser by ChainDD), don't. Install SuperSU by Chainfire instead, Use it to update the superuser binary (I think a prompt shows up) and when asked, let it delete the "other" superuser applications, that is, the chinese one. Clean and easy, you don't need to follow any more steps.
Congratulations, you now have (english language) root!
Clockworkmod Recovery:
There is no specific recovery for this device. Fortunately, thanks to AndroTab.info, there's a generic version for 3188 devices that you'll see should work quite nicely, albeight with some caveats.
What works:
Nandroid backup to/from external SDCard (won't recognize internal)
Installing zip files should also work, although I didn't try it at the time, as the device wasn't mine and I can't since I don't have it anymore, but since it mounts system partitions perfectly well I wouldn't think there would be a problem. Try it at your own risk though.
Other things probably work, give it a try.
What doesn't work:
Internal SDCard access
Probably other things
Installation:
Now that you have a rooted tablet, installing clockworkmod recovery is easy-peasy. Go to developer options and enable USB Debugging, then make sure you have a working adb daemon (look it up) that recognizes your tablet.
NOTE: I'm not sure if I had to install any specific drivers for this to work, I think if so they were installed while rooting by the chinese app. Anyhow, here's the Rockchip drivers, you might want to try to install them if you can't get a connection: http://www.rockchip.nl/downloads/
Download the file RK30GENERIC_CWM.zip from here - that's the recovery.
Now extract flash_image and recovery.img from the downloaded file above to the folder where you have your adb and follow the following commands.
Push the files to /dev partition on the device:
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Then enter root shell, like so:
Code:
adb shell
su
Now flash recovery.img into recovery partition with flash_image:
Code:
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Now power off your device. To enter recovery press volume down then the power button and keep them pressed until CWM boots. Voilá!
NOTE: The instructions above were adapted from here and all credit goes to AndroTab.info ; I posted these particular instructions because they are the ones I used and worked for me; there are other methods listed on that page which might or might not work, TRY THEM AT YOUR OWN RISK.
Backing up your original recovery (for warranty, if anything goes wrong, etc.)
To obtain a backup image of your recovery \ restore it back afterwards, follow this guide here. All credit goes to Originalas.
Don't follow it to the letter though: first and foremost, you need a working linux installation. If you don't have one, I recommend Wubi.
Then:
Follow step 1;
Ignore step 2 (it's outdated);
Follow 3;
Follow 4 - but don't expect the screen to turn on, it won't, just hold the volume down button for 10 seconds or so after plugging it in, don't press the power button!
Ignore 5, 6 and 7
Follow 8, but don't use the last command to flash the CWM recovery onto the device. This is because since it is a generic version, it relies on the original recovery kernel. Flashing the image like stated in step 8 would probably overwrite the kernel and result in no recovery at all (I might be wrong about this).
Do follow the last command to restore your own backup if you ever need to.
I am unsure if recovery dumps obtained in this way are device specific; I don't see a reason why they should be, so I'll provide you with my own backup:
ORIGINAL RECOVERY
Flash through any method of your choice, but keep in mind I haven't tried this on other devices, so, as you know by now DO IT AT YOUR OWN RISK.
Closing remarks:
There you have it. Sorry for not holding your hand through every step, but this is meant for people who know a bit of what they're doing, making it faster than having to look up and figure out all these things and quirks on their own. If you have any doubts don't hesitate to ask, but keep in mind I don't have the device anymore and don't know much more than what I have written here. I do appreciate feedback and corrections, and will gladly change the guide giving you full credit - if it's really urgent just PM me, I might not check this thread often.
Cheers!
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Newbleeto said:
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Click to expand...
Click to collapse
hi and thanx for the answer
yes i saw that it's almost stock but crappy optimized...in the very first start of the tablet i had 1.8gb occupied by nothing and clean master always notifies me that 90% of the ram is busy...meh
maybe just a kernel will fix like you say but you know, android 4.4 will be a must (rockchip already released sdk for 3188). I am not a coder (totally zero) but i will try your suggestion...just a question about the performance governor, does it drain more battery?
i am trying to backup my rom but cwm is so buggy...first was impossible, now i'm stuck on backing up boot image
there is a twrp available for this tablet?
solved
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Dump stock ROM QiLive 97R
Jammed_Death said:
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Click to expand...
Click to collapse
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Redinpais said:
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Click to expand...
Click to collapse
you can upload it on mega or gdrive or something like that
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
about the cwm, there is a way to mount sdcard?
Dump stock ROM QiLive 97R
Jammed_Death said:
you can upload it on mega or gdrive or something like that
Click to expand...
Click to collapse
Here he are...
https://www.wetransfer.com/download...556a9cf8fdbc6ddd7ab35ab820141126224717/09298e
Is only available until Decenber, 3 ,so Download it now.
Jammed_Death said:
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
Click to expand...
Click to collapse
I've been watching but I can not understand. Is confused. There are many files and do not know what to do to "fix".
If you are Portuguese, I would like to talk to you on Skype.
Can be?
Jammed_Death said:
about the cwm, there is a way to mount sdcard?
Click to expand...
Click to collapse
I don´t know how I can answer that. I'm new in android, so I sorry.
Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
Try this. Sooooooooo beautiful.:good:
(Because this - "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!" i can not put link now. So ask me by Skype) SORRY
:victory:
Follow the instrutions ther and enjoy KK 4.4.2 Oma ROM Iron KK v1.2 - 24-05-2013 (My QiLive say now - Nexus 7 :angel:
Regards
Qilive 97r
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Denysorlyk said:
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Click to expand...
Click to collapse
I'm interested
please ROM stock
Hello, i need help , if somebody know where I can download original rom , and original installer, I will be thankful for that's.
Related
Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Probably drivers. Just manually boot into bootloader.. And then flash the factory image.
Sent from my Galaxy Nexus using xda app-developers app
Fastboot reboot-bootloader command will only work if you are already in the bootloader mode anyways...
As @mrgnex said, just do it manually, or use adb commands to boot into bootloader where THEN you use fastboot command.
To manually get into bootloader/fastboot mode; power down, then hold power button and volume up AND down all at same time for few seconds, it'll vibrate and you'll be in the bootloader mode where u can issue the fastboot commands.
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
You don't actually move the factory images onto your phone.
One of the sticky threads here is called "return to stock". That should guide you in the right direction.
Sent from my Galaxy Nexus using xda app-developers app
huzzug said:
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
Click to expand...
Click to collapse
it's great that you're learning to do this Droid life has a good howto, just google "droidlife how to root galaxy nexus"
if worse comes to worse you can use this toolkit that does it for you, it's called wugfresh google "wugfresh nexus toolkit"
If you want to install ROMs you download the zip right on your device (make sure you get a ROM zip file AND a gapps zip file. They are linked in pretty much every OP for ROMs)
Downloading a ROM zip directly from/on device is easiest because then you do not have to transfer the file(s) over to your device in order to "flash"(aka install). Then all you do is go into recovery mode. Then go to install, then choose your ROM zip file. After that installs, then install gapps file the same way, always install gapps zip AFTER the rom zip.
If you use TWRP as your custom recovery you can "queue" your zip installs(choose rom zip and then you can choose to add another zip file and it will flash them both for ya)
And usually it is recommend to do a factory reset from recovery before you reboot into system. (Make sure to not wipe ALL /data...choose factory reset...wiping ALL /data will wipe /sdcard contents as well)
This all might seem foreign and difficult at first, but once you've done it once or twice(or more... you might become what we call a "crack flasher"-one who is constant changing ROM and kernel and setups lol, that's when it gets REALLY fun) so do not get discouraged. Especially if you don't understand the terminology we all use, you will become familiar with it quickly. And remember, Google is your best friend, almost any questions you might have will yield MANY helpful results when you put in a Google search, highly recommend that if using Google for trying to get useful info to put things like "how to install custom recovery "Galaxy Nexus" xda" to get the best info possible )
And do not be afraid to ask us either if you feel lost. It's easier to prevent an issue than to fix it(though fixing a borled Gnex is fairly easy with all the tools available here and elsewhere)
As for going back completely to stock, as mentioned above, to do that you aren't putting any files onto your device itself. You download them to PC(I use my laptop) and install from there using fastboot. When you download the factory img that is for your specific device and unzip it (I believe they still come compressed... If not ignore that part sorry!) You will see inside there is a script called "flash-all.sh" OR if using windows use the "flash-all.exe" that will automate the fastboot commands needed for a full factory stock restore of the device.
I could link you to posts containing useful how-tos and info and such, but right now I'm viewing forum via Tapatalk app on my device and really gonna be lazy and just say look at the "Sticky posts" in General, Q&A, and Development sections, those are most likely what I would link to you here.
After reading through some of those, if you need clarification of steps taken or something, come on back and let us know.
huzzug said:
Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Click to expand...
Click to collapse
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
SolGoodGuy said:
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
Click to expand...
Click to collapse
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
ashclepdia said:
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
Click to expand...
Click to collapse
I see an optimus G on swappa for $115. Much better phone.
Actually, I ain't in US guys. And whatever I found was a personal preference as I wanted this model and not any other.
Bumpity bump
huzzug said:
Bumpity bump
Click to expand...
Click to collapse
Bump?
Did you ever try what I said?
You need to download the factory img needed and run the flash all script...
Edit::
HERE go to this thread.
http://forum.xda-developers.com/showthread.php?t=2726518
Follow my advice there, except make sure to grab maguro img for your device. Be sure to grab the correct package for your device (takju yakju, etc...it will tell u in bootloader mode which one u have)
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Outblaze713 said:
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Click to expand...
Click to collapse
Do you have an OTG Usb drive. If so, you can use it with Nameless TWRP. Copy the Installation files into the USB drive and plug the usb drive into the phone. Now boot into Nameless recovery. It will show USBOTG. You can install the CM11 from USBOTG.
Flash Nameless recovery using Fastboot.
Download Nameless Recovery from HERE.
soft brick
This link explains how to restore our find 7 to factory settings:
oppoforums.com/threads/guida-riportare-il-find-7-7a-nello-stato-dacquisto-con-il-firmware-sahara.24561
if phone doesn't start try it i've use it several times and it works fine
I might just be reposting what dracula6mt was talking about, but there's an English post with full brick recovery here: http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/. I've used it before and it works perfectly. Just make sure you follow it exactly as written!
Bug
same bug report
for retrive your data just open the gummy twrp recovery, go on mount --> sd card and internal memory... in this way when you connect the phone to pc you will be able to see what's inside and try to rescue your data. in the same way you can send files to it.
I suggest you to get back your files, reboot the phone in fastboot mode (hold power and volume +) and just flash a recovery, it depends about what you want to install:
twrp for custom roms https://dl.twrp.me/find7/
colorOS stock recovery http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397&extra=
you have to install fastboot on your pc and do from a command prompt:
fastboot devices
this will check if your phone is connected
fastboot flash recovery nameoftherecoveryfile.img
that will flash the recovery, only check the name of the .img file you want to install
be carreful, twrp has only a version for both find7s (QHD) and find7a while colorOS recovery 1.0 is different, unified for both models in 1.2 if i remember right...
after that you just have to put on your external storage the rom you want to use, wipe all except the external sd card, and flash...
Outblaze713 said:
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Click to expand...
Click to collapse
There is a much easier way :
http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
mail me to : [email protected], greetings.
os_man said:
There is a much easier way :
http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
mail me to : [email protected], greetings.
Click to expand...
Click to collapse
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
spoonymoon said:
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
Click to expand...
Click to collapse
Every human beeing who can communicate gets the password for free, especialy OPPO and OPO owners, every e-mail i get starting with "Pasword pleaseee pleaseee pleaseee" gets different behaviour of course. OH, and every CLEVER people already knows the tool in my article, i mentioned it a couple of times, for stupids like you its impossible to see of course. I helped hundreds of people for free and sometimes i request for donation, ITS MY VERY COMMON RIGHT + to help those i want and not to help to those that i dont want.
Greetings from TURKEY you silly Viking.
spoonymoon said:
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
Click to expand...
Click to collapse
Taken from my article ( for those who can read ) :
Please Stop asking for password without reading the article completely till the end, THIS TOOL WONT WORK UNLESS YOU HAVE THE NECESSARY SERVICE ROM ! Try sharing your phone model first and also try to share the service ( QPST ) Rom if you have it so more people can use it, THANK YOU.
os_man said:
Every human beeing who can communicate gets the password for free, especialy OPPO and OPO owners, every e-mail i get starting with "Pasword pleaseee pleaseee pleaseee" gets different behaviour of course. OH, and every CLEVER people already knows the tool in my article, i mentioned it a couple of times, for stupids like you its impossible to see of course. I helped hundreds of people for free and sometimes i request for donation, ITS MY VERY COMMON RIGHT + to help those i want and not to help to those that i dont want.
Greetings from TURKEY you silly Viking.
Click to expand...
Click to collapse
Hahaha,if so why, don't you post a link here, on mega or something, instead of all this " mail me" crap??? That would be a honest thing too do, instead....
And no, it's not common too sort in who and which, you want to help out, at least not here on XDA, we help every body, with no exceptions.
I say again, give us this file freely or I report you too forum admins.
My x9076 is bricked because of me making a lvm error, but I'd rather have it semi Working, with messed up partitions, like now, than pay our beg some guy like you for something that not working any way.
Last chance give this freely or get locked out from xda
EDIT: believe me, this turk psyko, has NOTHING not known already, regarding unbricking devices, there´s hundreds of posts here and on oppo forum about people having storage issues etc, not one ever mentioned anything about any other tools than those oppo them selves gave us, there is NO other working ways not known as this cracy dude claims, he´s just running a scam and wants 20$ for nothing - OS_MAN is a fraud dude all over.
EDIT 2: Silence from sir os_man tells the truth....
spoonymoon said:
Hahaha,if so why, don't you post a link here, on mega or something, instead of all this " mail me" crap??? That would be a honest thing too do, instead....
And no, it's not common too sort in who and which, you want to help out, at least not here on XDA, we help every body, with no exceptions.
I say again, give us this file freely or I report you too forum admins.
My x9076 is bricked because of me making a lvm error, but I'd rather have it semi Working, with messed up partitions, like now, than pay our beg some guy like you for something that not working any way.
Last chance give this freely or get locked out from xda
Click to expand...
Click to collapse
Never threaten a Turk Do whatever you can !
If XDA will lock me becouse of you, let it be
And i dont think that you can help anybody with that brain of yours, you even cant rescue your unbrickable Oppo..
spoonymoon said:
I say again, give us this file freely or I report you too forum admins.
Click to expand...
Click to collapse
When asking for help in a free space and for free, sometimes some manners can really make a huge difference. I think you fail to understand that even though you have a problem and someone might have a solution, that someone has no obligation whatsoever to share their time and the fruit of their research with you, especially so when threatened.
Hmm, considering the files and how-to's for unbricking a Find7 are freely available from Oppo forums (and here, I believe), I'm pretty suspicious of anyone doing ANYTHING other than giving them away freely. The files I downloaded and have used, a few times now, were free and had no passwords on zip/rar archives.
As for 'fruits of research', this guy wasn't the guy who put up the how-to's or did the initial research on it so, in my books, he doesn't get the credit, be it kudos OR cash money.
Some folks seem to literally want something for nothing. No harm in asking for donations, sure, but don't be at all surprised if I tell you to go f*** yourself. That's not how this game works, we all stand on each other's shoulders.
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?
Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method
well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.
Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.
Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..
Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.
links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy
If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?
famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
So, building asteroids and syncing with latest sources and also trying to fix bluetooth is my main goal here.
First test build is complete! Link: [urlhttp://www.mediafire.com/?0c0xusva0z5e0[/url]
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/asteroid-image-tetra.ext4 /sdcard/linux/rootfs.ext4 (pushes the file to the virtual sdcard)
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/zImage-dtb-tetra.fastboot
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
amunarjoh said:
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
Click to expand...
Click to collapse
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
I am willing to be a beta tester
Alright, stay tuned. Building rom right now, also getting instructions for how to flash it (I don't think it is a simple twrp flash, not sure, we need some tester to confirm that).
RAZERZDAHACKER said:
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
Click to expand...
Click to collapse
That sounds interesting. Looking forward to further development
Build finished after a couple of hours. Since I am new to this whole android wear thing, I am a bit confused as to which files to flash, but I assume it is the one that is the largest and has the correct file format, right? So here is where the beta tester thingy comes into place. I am still experimenting on flashing the rom (the flashing method can be a bit confusing for new people) so I am planning on coding a toolkit that does all of that for ya, but the main thing is that I use linux and I don't really have a windows machine available to test this and quickly be able to change some things in the code (or either the rom files and then pack em up) so if someone is willing to perhaps skype or something similar where they can test such things that would be amazing, since I don't believe that a lot of people are running linux and want to flash this particular rom for this particular device etc.
Enough ranting! Here comes the rom link! http://www.mediafire.com/?0c0xusva0z5e0
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext4
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/file.fastboot.
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
niai_mack said:
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
Click to expand...
Click to collapse
Thanks for trying, and you followed the instructions here I assume. I'll try to compile a new one today (I got some interesting warnings when compiling)
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
niai_mack said:
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
Click to expand...
Click to collapse
Can you perhaps try "adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext2" ? Thanks.
I can test as well
d_crossfader said:
I can test as well
Click to expand...
Click to collapse
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
drakonizer said:
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
Click to expand...
Click to collapse
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
RAZERZDAHACKER said:
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
Click to expand...
Click to collapse
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
drakonizer said:
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
Click to expand...
Click to collapse
I can always try :/
RAZERZDAHACKER said:
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
Click to expand...
Click to collapse
I can do the steps on the first page, not sure about replacing the virtual sd though
d_crossfader said:
I can do the steps on the first page, not sure about replacing the virtual sd though
Click to expand...
Click to collapse
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
RAZERZDAHACKER said:
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
Click to expand...
Click to collapse
cool, will try in a few