[test][rom]Anyone willing to do some ROM testing for this device? - Sony Smartwatch 3

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

Related

[SCRIPTS][Win] A100 Flashing Toolkit v1.1 7-16-12 Discontinued

As I wrote the guide I realized the files, scripts, and images are scattered through multiple threads, which makes finding what you need difficult, even from a main thread (the guide for example). This was compounded even more when I was writing the CM9 Install Guide for the CyanogenMod Wiki and listed the commands themselves, it became huge, intimidating, and looks extremely daunting, I can only imagine what a new flasher must think seeing it! And and so I decided perhaps I can fix this, and with that I present to you...
The A100 Flashing Toolkit!
What is it?
A single zip file that, when unzipped, contains EVERYTHING you need, ADB, fastboot, scripts, CWM recovery image, everything you need to take your stock ICS A100 through rooting, unlocking the bootloader, and flashing CWM recovery (twrp coming soon)!
How is it used?
Its a set of 6 PC scripts, 3 for windows users (.bat) and 3 for linux users (.sh). Run in order from the same folder, and you can just click and run, reboot, click and run, reboot, click and run, install custom rom, done!
You MUST already be on ICS! This is not for HC, if you are on HC update to ICS FIRST!
Instructions
Make sure you are on ICS! Read the bold red letters above! You have been warned! You should already have installed the Acer USB drivers for ADB to work.
Ok, now you're on ICS....right?
Download and unzip the file to whatever folder you can remember, for example c:\acer or ~/acer.
Open your file manager of choice and browse on over to where you unzipped the files, and get ready.
Windows
Right click on A100-root-win.bat and select Run as Adminitrator.
Once that is finished, let your tablet reboot.
Once it's rebooted, right click on A100-unlock-win.bat and select Run as Administrator.
Once this finishes, let the tablet reboot again (the script will tell you what's happening)
Once it's rebooted, right click on A100-recovery-win.bat and select Run as Administrator.
Allow it to finish, it'll reboot a couple times.
Half the time it reboots into recovery, other reboots into system, not sure why it happens.
If it boots into recovery, go ahead and make a full backup, might as well.
If it boots into system, reboot into recovery and make a full backup, might as well.
At this point, you can now wipe and install a custom ROM, see the A100 Guide in General for ROMs and instructions on this.
Linux
Execute A100-root-linux.sh and allow it to run.
Once that is finished, allow tablet to reboot.
Exectute A100-unlock-linux.sh and allow it to run.
Let the tablet reboot
Execute A100-recovery-linux.sh and allow it to run.
It'll either reboot into recovery, or system, it does one or the other for some reason.
If rebooted into recovery, make a full backup.
If rebooted into system, reboot into recovery and make a full backup.
Wipe and install a new custom ROM, see the A100 Guide in General for ROMs and instructions on this.
How to boot into recovery
There's a few ways, 1 way is an app like quick boot, you can use adb by typing adb reboot recovery or you can do it manually.
Power off the tablet.
Press and hold the volume - button, closest to power and lock switch.
Holding volume - press and hold Power.
Hold until the screen says Booting recovery kernel then let go.
You should be in recovery, either CWM, TWRP, or stock, whatever you have installed.
As always I am open to suggestions, advice, or reports! Feel free to post up or PM me with any issues, questions, bugs, or ideas!
Download
A100 Flash Toolkit 1.1 7-16-12
Now featuring the correct bootloader!
Thanks to smokku for pointing this out.
Who do we thank for this package?
ZeroNull: Alot of the scripting is based on his work, and borrows his ADB and fastboot executables.
ptesmoke: Uses his CWM recovery.img file
CyanogenMod Iconia Team: For allowing me the chance to write for the Wiki, and realizing this NEEDED to be done.
Anyone else I'm forgetting, I'm sorry I will add you as soon as I remember (feel free to drop me a note!)
Sounds great, many thanks.
Thanks for all you hard work and patience.
a100 flash program
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Birbey said:
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Click to expand...
Click to collapse
Oh wow OK I'll take a look I must have mixed everything up. My desktop is littered with files from all these projects. I'm sorry about that I should have double checked everything before I uploaded it. If the called files are different then the scripts it must be the old version mixed with new scripts or something. I should have it squared away sometime tonight/tomorrow morning.
Edit: I'm assuming by saying command prompt you use windows, the a100-root-win.bat file looks fine, was this one giving any issues?
I'm checking the second and third now for whatever is going on.
Tapatalked from my Galaxy S II.
Fixed.
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
diegof18 said:
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
Click to expand...
Click to collapse
You have to be FAST when it gets there, it times out in like half a second it seems.
When you run it, have the tab in your hand, fingers on volume - and volume + (volume - is next to the lock switch). As soon as you see the screen change, hit volume - then volume +. It takes a few tries usually. It'll just sit there until you reboot afterwards.
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
elander said:
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
Click to expand...
Click to collapse
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
thanks for the info.
pio_masaki said:
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
elander said:
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
Click to expand...
Click to collapse
I'm not sure, but I don't think resetting these puts them back to 100% if rooted, the root stays since it sits in /system. You'll have to manually remove SU then reset to get rid of the root, I think. Other option is restore through the update.zip method which should wipe /system. You could try a hard reset and see if it removes SU or not, it might.
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
NeO_CooL said:
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
Click to expand...
Click to collapse
Not quite clear on what you're asking, but as far as I know it should work on any version bootloader unless they changed it on some update, which wouldn't surprise me.
What is the whole message, and when is it occuring?
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
NeO_CooL said:
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
Click to expand...
Click to collapse
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Forgot to say i´m using the windows version.
Thanks
pio_masaki said:
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Click to expand...
Click to collapse
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 (not unlockable) bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
smokku said:
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 not unlockable bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
Click to expand...
Click to collapse
It's just labeled a100, it isn't the actual a100 blob. But go ahead and use that link until I get the chance to go back through it, I'm obviously messing it all up somewhere, I may have used the a100 blob and gotten it mixed up with the a200 blob when I was renaming and shifting things around. I'll pull the download for now until I get the chance to get it all sorted out, sorry guys.
Edit OK its back up with the proper boot loader for unlocking. I can't believe I did that. Huge thanks to smokku for pointing that out!
No worries.
And yeah, you have to be quick when it asks to toggle unlock, like half a second quick.

[Q] Toro plus binaries for SPH-L710 AOSP build?

I have built and slightly tweeked CM 10.1 but to be honest, it does drain that battery quite a bit and sometimes it freezes in landscape mode.
So I sync'ed up the source for the AOSP and then I realized that I needed binaries and I don't have the stock ROM to extract them from.
Are these "Galaxy Nexus (Sprint) binaries for Android master (20130603)" the right binaries for SPH-l710 ?
Under the Toroplus section at the very bottom of this page https://developers.google.com/android/nexus/drivers
Basically I just want try moding from stock because of the battery thing, I need to add Arduino support and maybe tweek USB or write an app, so that my phone can hook up over usb to an Arduino board and chit chat. I want the Arduino to control motors while Android gathers sensor data and decides where to go, Arduido will just follow orders. Anyways, battery consumption is huge in this project.
EDIT-1: Also, what version of Android are the 20130603 binaries for?
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
CNexus said:
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
Click to expand...
Click to collapse
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Edge-Case said:
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Click to expand...
Click to collapse
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
CNexus said:
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
Click to expand...
Click to collapse
Makes Sense.
So if I am learning anything... I would need binaries ("blobs"), I am sure Sprint, Google, and Samsung proprietary apps, and the nessiccary make (Android.mk) files, maybe some kernel patches and/or kernel object files, and hopeful to all hell I don't have to do too much XML modification I need to go find a trust-worth factory zip for the sph-l710 and rip everything I need out of that, and the bootloader I need to get it all back to stock eventually in case kit-kat does get updated by the Samsung (I am guessing thats whose hands it is in, I think they have a counter), who knows maybe the open source community will get there first.
Thanks for your help, saved me a ton of hassle.

[GUIDE][ROOT][CWM] ARCHOS 97b Platinum HD

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.

[ROM] RemixOS 3.0 [Marshmallow] Easy Install Package

Hi folks. I'll start off with some disclaimers.
I'm not part of the Jide team or in any way affiliated with RemixOS other than that I was given permission to post an "easy install" package here.
I cannot fix bugs. If you want to tell me about bugs you are welcome to, but there's nothing I can do about them. This thread *may* be monitored by Jide team members, but I cannot guarantee timeliness nor thoroughness.
I am only here to support this thread in regard to "How To Install It". That said, I will try to assist anyone with any issues that I can. I can't fix bugs, but I can answer question and may be able to resolve some issues.
This process WILL WIPE your device, so be sure to back up any important files beforehand.
Now that all that's out of the way, let's get to it.
If you haven't heard about RemixOS, here's a little intro: http://www.jide.com/remixos
Remix is a different kind of Android experience.
The only way to install RemixOS at this moment is through fastboot. I took their firmware files and simplified "flash-all" batch script and packaged it alongside ADB and fastboot. If you already have ADB and fastboot, you can download the firmware directly from Jide and install just like always: http://www.jide.com/remixos/devices/nexus9
If you don't have ADB or fastboot, or just want to speed up your install process, keep reading.
You will need an UNLOCKED BOOTLOADER to do this. Unlocking your bootloader will wipe your device, but so will installing this ROM normally, so again be sure to back up important files. Click the spoiler button in the instructions below to see the additional steps for unlocking your bootloader.
Pre-install: Enable "OEM Unlocking" in Developer Settings. To do this: go to "About Tablet" in Settings. Tap "Build Number" seven times. You'll see a notification that you are now a developer, and now you'll have a "Developer Options section in Settings. Go into Developer Options and enable "OEM Unlocking" by flipping the toggle.
1. DOWNLOAD EASY INSTALL PACKAGE:
https://www.androidfilehost.com/?w=files&flid=92087
2. Unzip the package. Just the .zip file you downloaded, no need to unzip anything within the original .zip file.
3. Boot your Nexus 9 into bootloader mode. (power off tablet, hold "Volume Down" and "Power" buttons simultaneously for 4-5 seconds. You'll see a white screen with multicolor text if successful)
4. Connect tablet to PC via microUSB cable.
To unlock bootloader, if necessary:
A. Hold Shift and right-click within the unzipped folder containing ADB and fastboot tools, then click "Open a command window here". A command prompt will pop up.
B. Type
Code:
fastboot oem unlock
C. This will wipe your device and takes a few minutes. If it reboots afterwards, get back into bootloader mode to continue.
5. Double-click "flash-all.bat", the batch file within the folder you unzipped from the package.
6. Wait for a while. It takes a few minutes. Do not unplug the tablet or turn off your computer during this process. It will reboot automatically when complete.
Congratulations, you are now running RemixOS 3.0!
A few notes for modders:
I was able to root using CF Auto Root.
TWRP works fine for flashing some .zips, but remember this is a heavily modified AOSP so not all mods will work.
I have not tested Xposed.
Layers do NOT work.
If you install a custom recovery or modify /system you will not be able to install OTA updates, you will have to flash the entire package manually.
Awesome! Can't wait to try it. I just left remix because I couldn't stand to run a 5.1 base. But it was always fast and smooth!
Sent from my HTC 10 using XDA-Developers mobile app
Rather than this, a TWRP flashable version would be awesome.
dictionary said:
Rather than this, a TWRP flashable version would be awesome.
Click to expand...
Click to collapse
Make me one and I'll post it up.
Or use the method provided.
Your choice.
Sent from my XT1575 using Tapatalk
Runs beautifully and was a breeze to install! Thanks
Sent from my SM-N930T using XDA-Developers mobile app
how to get lte working?i really need this
mangomonkey00 said:
how to get lte working?i really need this
Click to expand...
Click to collapse
I am not sure it supports LTE. I only have a WiFi Nexus 9, and have no way to test it.
I'll ask @RemixOS_Jason to check on it for you.
I have been using it from when I got N9 from swappa. Tried other custom and stock ROMs. I keep coming back. Been the best so far. The last stock was dp5 haven't tried 7.0
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
borxnx said:
I am not sure it supports LTE. I only have a WiFi Nexus 9, and have no way to test it.
I'll ask @RemixOS_Jason to check on it for you.
Click to expand...
Click to collapse
RemixOS_Jason said:
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
Click to expand...
Click to collapse
its nice but i was able to get lte working on this after the whole installation had to manually flash vendor.img from latest google image
mangomonkey00 said:
its nice but i was able to get lte working on this after the whole installation had to manually flash vendor.img from latest google image
Click to expand...
Click to collapse
From latest Google image, as in from Nougat? Wouldn't any 6.0.1 vendor image work, so long as it was more recent than the ROM build?
RemixOS_Jason said:
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
Click to expand...
Click to collapse
Would love another update for WiFi version as well, but I have two questions.
1. Is there any way we can be given the choice of using our own launcher? It's really frustrating.
2. If we can't, can the option be added back to not have all apps on the home screen? It was present I believe in the previous build, but it's gone again. I could have two apps on the screen, and everything else in the app drawer. Prefer that.
Hey dictionary,
I talked to migration team and, as of my writing, there is no schedule for another update for the the Wi-Fi version.
1) Currently, Remix OS doesn't support other launchers.
2) Putting this feature back into Remix OS for N9's can be done if we gather enough feedback from the community for it. Personally, I totally get the reason you'd rather have clean desktop option, but we have limited resources here and I need for the feature to be asked by many users first.
Thanks and I do hope you understand. Btw, have you tried any of our other products (ie. Remix OS for PC or Remix OS Player?) They both have the clean desktop feature.
Thanks!
dictionary said:
Would love another update for WiFi version as well, but I have two questions.
1. Is there any way we can be given the choice of using our own launcher? It's really frustrating.
2. If we can't, can the option be added back to not have all apps on the home screen? It was present I believe in the previous build, but it's gone again. I could have two apps on the screen, and everything else in the app drawer. Prefer that.
Click to expand...
Click to collapse
RemixOS_Jason said:
Hey dictionary,
I talked to migration team and, as of my writing, there is no schedule for another update for the the Wi-Fi version.
1) Currently, Remix OS doesn't support other launchers.
2) Putting this feature back into Remix OS for N9's can be done if we gather enough feedback from the community for it. Personally, I totally get the reason you'd rather have clean desktop option, but we have limited resources here and I need for the feature to be asked by many users first.
Thanks and I do hope you understand. Btw, have you tried any of our other products (ie. Remix OS for PC or Remix OS Player?) They both have the clean desktop feature.
Thanks!
Click to expand...
Click to collapse
1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great
You may want to try Remix OS Player again if you're still interested as we made some optimizations and now allow you to use all your CPU cores rather than leave at least one core for your host OS and PC.
http://www.jide.com/remixos-player#download
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
QUOTE=dictionary;68895033]1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great[/QUOTE]
RemixOS_Jason said:
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
Click to expand...
Click to collapse
I would also like to have the option of using a clean desktop on my N9
Thank you for the great work, btw!
I used latest 6.0.1 vendor IMG as nougat factory image is not available for lte
RemixOS_Jason said:
You may want to try Remix OS Player again if you're still interested as we made some optimizations and now allow you to use all your CPU cores rather than leave at least one core for your host OS and PC.
http://www.jide.com/remixos-player#download
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
QUOTE=dictionary;68895033]1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great
Click to expand...
Click to collapse
[/QUOTE]
I'll give player another shot later today.
No disrespect to the PM's, but I vehemently disagree. There is no easy way to sort them, and putting all things in folders isn't very aesthetically pleasing. I have well over 60 apps installed, and it's just a jumbled mess. I always run a clean desktop on my devices. I find it much more intuitive having all apps right by my thumb.
If they refuse to, that's fine. I'll try to find a way to just move the launcher and file manager from my Remix OS for PC over to the n9
@dictionary Your opinion is duly noted. I've definitely passed on your opinion to them as well as @KSS2016 's comment.
Let me know how Remix OS Player works out for you. Thanks.
Any word on the LTE easy install package?
Sent from my Nexus 9 using Tapatalk

Root + twrp + bootloader unlock + twrp flashable stock rom - marhsmallow

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.

Categories

Resources