So I've been reading everything I can while trying to follow the steps within all the guides I've found. I know everything I do is everything described in the guides but I can't get anywhere when I reach draw9patch. Just doesn't work. Can't figure it out for the life of me.
I'm using Windows 7 Ultimate x64 and pretty sure I know how to get things to work most of the time, but this is quite the venture for me.
I should state now that I am new to the android platform but have a lot of experience with everything I've learned. I read every guide I find before making those changes to the actual device.
My Dream/G1 is rooted with Cyanogen... 4.2.1.11 and the Hard SPL.
ADB is established but fastboot is still a problem(for now).
I know how to push the framework-res.apk back to the device so my question after all this nonsense above would be
Can someone post a framework-res.apk with a black notification bar along with white text in all fields pertaining to such and have that be the only change within the stated framework-res.apk above?
This was my last resort. If this is a double post, I apologize.
I have searched the forums, google and etc...
I would suggest going to the market and downloading Metamorph. (either free version or donate version. Either will work)
Then go to this thread http://forum.xda-developers.com/showthread.php?t=589315 and scroll down a little bit (first post) and download the blackbar mod (under the "Morphs by AndroidFiend:" section)
You can have blackbars in less than 5 minutes following this route and there is nothing to edit. Metamorph seems to be the way of the future in themeing.
Metamorph Download complete!
Sorry!
The application Market (process com.android.vending) has stopped unexpectedly. Please try again.
FORCE CLOSE
I must install busybox and I will give update.
I am very stunned right now. I spent days trying to figure it out and you just ... Wow.
That's all I can really say...
Woot!
That worked.
I am actually a little mad. Not at you but at the fact that I spent about 2 days trying to figure it out.
wow
So basically looking for a tutorial or something to rip a ROM from my phone and make it easy to pass along to someone else.
Reason being is because it took me a while to get the rom setup the way I was wanting with the least amount of hassles of messing with the framework etc via Metamorph and Ninjamorph. I want to be able to port my creation over to another device without all my user data(messages and contacts etc) included...
Just want to know if there is a easy way to do this...but in the meantime I am downloading Linux and prepping to go the hard route to doing this...
magneticzero said:
So basically looking for a tutorial or something to rip a ROM from my phone and make it easy to pass along to someone else.
Reason being is because it took me a while to get the rom setup the way I was wanting with the least amount of hassles of messing with the framework etc via Metamorph and Ninjamorph. I want to be able to port my creation over to another device without all my user data(messages and contacts etc) included...
Just want to know if there is a easy way to do this...but in the meantime I am downloading Linux and prepping to go the hard route to doing this...
Click to expand...
Click to collapse
The easiest way to build ROMs is using Android Kitchen, its under under Chef Central. Just follow the directions in the thread to a tee. With Windows you basically have to set up a Linux virtual machine on your pc to use it. I've done it both ways, through Linux Ubuntu 10 and Windows. I curently have it set up on a Windows Vista laptop, took a few hours to get everything setup right then built some ROMs for my Eris with it. The ROM building part takes only a couple minutes. I haven't used it with my Incredible.
http://forum.xda-developers.com/showthread.php?t=633246
Thanks, going to try it the old fashioned way first...apktool and resigning everything, so I get a general idea...then mess with the kitchen after I get a headache from my first ROM attempt haha!
I prob would of spent 1/2 day doing it the old way, I think I finished it in 15 mins. +1 Kitchen
I really need to get the right drivers for the Iconia A100 and i need um soon. I searched alot and there all dead links or ads now.
I just attempted to port a 4.1.2 rom from another tab, I get past the install and sit at the boot animation, no damn adb cause i did a reinstall on the computer and they got lost in the hundreds of zip files in my downloads.. And I cant get a logcat, I know I can get this booting and its freaking sweet. Its based on pio_masaki's Jellytime Final, and a mixture of ParanoidAndroid Roms. If i get it going its getting posted. Anyone wanna help on the testing just ask here or pm me.
Thanks in Advance.
I do need an xml person, I hate them ....:silly:
Try the Acer support site?
Sent from my Galaxy Nexus using Tapatalk 2
Sure did...
The ones I got from them didn't work for some reason. I found a thread on here that's got a naked usb driver that worked just fine. I am waiting for cygwin to install to unpack and compare boot.img from your SoseiB3 Final to the rom I ported from, Then its off to recovery and some logcating to see if I can get it to boot. did this once today and I failed. I went about this build from another angle and I think this should boot. I'm not to good at logcat reading but I hope I dont need to read to much. I'm about 30 minutes from a signed update to test. Then hopefully I can post my rom. If i can find a mirror to use that is lol. I'm new can you tell?
I have successfully ported roms before without building from source. If you post some logcats I might be able to help with what might be causing to boot to fail.
Most of the things I had to do to make it work were transferring lib files and doing some modifications to framework.jar
hardslog said:
I have successfully ported roms before without building from source. If you post some logcats I might be able to help with what might be causing to boot to fail.
Most of the things I had to do to make it work were transferring lib files and doing some modifications to framework.jar
Click to expand...
Click to collapse
Its uploaded to dev host, the links below. if you would like to download it and see what you think then feel free. Just be aware I have not even tried this build out yet. Nothing to worry about really but it may be way far from booting. Its fresh out the winrar folders lol.
link d-h.st/i5U
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.
Hello all, I haven't been here for about 2 years, got busy with some things. I'm currently running a home compiled JSS15Q that has a touchscreen hack to load in the firmware that works best with my tablet. I'd like to build 5.1.1 LMY48I from source and give it a try. Do I need to upgrade any bootloaders or other stuff before attempting to push the new OS on there?
It's been 2 years since I did any of this stuff so I'm a bit foggy about it all. I had a good handle on it back then, but I've slept a lot since then. I might go with sfhub's locked in firmware this time since I was accomplishing pretty much the same thing just a different way. That's, of course, assuming that the old firmware is compatible with the newer releases of Android OS.
I built the older release in a VirtualBox VM running Ubuntu 12.04. I think I need to upgrade some things to be sure that the compile of 5.1.1 works as it should. I was about out of space on the 12.04 VM and I was going to grow the partition, but I'm thinking it might be smarter to just follow the build-from-source instructions from scratch in a new VM install. It takes a huge amount of space to do a build. AOSP took 20GB and JSS15Q took about 40GB of drive space. I "only" set up a 100GB VM which means I likely don't have enough room to download the newer release source.
If anyone that's done this has any advice, I'd sure appreciate hearing it. Thanks for reading.
Sounds like you already have it figured out.
There is a new bootloader so don't forget that. Sfhubs firmwares work fine.
I forget how big it was when I synced 5.1.1 but if you delete the jellybean code you should be fine.
LOL You're giving me wayyyy too much credit. I'm pretty much stumbling around in the dark here. I went with the new VM using Ubuntu 14.04. I struggled through all the apt-get commands especially the one with libgl1-mesa-glx:i386. It just didn't want to install because of some dependency quirk of some sort with something called cheese. I finally found a solution by doing this:
sudo apt-get install libglew-dev libcheese7 libcheese-gtk23 libclutter-gst-2.0-0 libcogl15 libclutter-gtk-1.0-0 libclutter-1.0-0 xserver-xorg-input-all
God only knows why I had to do all that to get the libgl-mesa-glx installed, but it finally let me do the get for libgl-mesa-glx:i386. Then I could finally create the symlink for the mesa library. After that, I successfully repo synced the source tree; it took up 35GB of disk space. I did the lunch command, picked flo user (11) and started my make command to build. That's running right now.
I was concerned about the proprietary binaries for the broadcomm stuff, but I found a directory under ./device/asus/flo called self-extractors. I'm guessing that stuff takes care of itself now and you don't have to do the steps of finding, downloading and extracting it into the tree. That's my guess anyway. I'm following this "howto":
http://source.android.com/source/requirements.html
I had been looking at an older one on blogspot, but it was for a different device and I figured it would be better to follow the one I'm using instead since it seems more current. I hope this build works okay and doesn't drag badly from bloat. I like my tablet's responsiveness on jellybean. I'm wondering now if I shouldn't have just gone to kitkat instead of all the way to lollipop. Oh well, live and learn. Thanks again for you input and for reading this. Let me know if I'm messing up.
I got it compiled. It took about 2.5 hours. I tried to find the program that I modified before, but I can't find it anywhere in the source tree. They've apparently moved everything around real good. If anyone knows where the touchscreen firmware update takes place, I'd appreciate knowing. It used to be in a program named ektf3k.c That program no longer exists in the build. I can use sfhub's utility to lock in the firmware I need, but I'd still like to know how where they moved the firmware update stuff.
afremont said:
I got it compiled. It took about 2.5 hours. I tried to find the program that I modified before, but I can't find it anywhere in the source tree. They've apparently moved everything around real good. If anyone knows where the touchscreen firmware update takes place, I'd appreciate knowing. It used to be in a program named ektf3k.c That program no longer exists in the build. I can use sfhub's utility to lock in the firmware I need, but I'd still like to know how where they moved the firmware update stuff.
Click to expand...
Click to collapse
I built the whole thing without the proprietary binaries installed. I'm guessing that my build is basically useless. I'm kinda disappointed that they don't bring up the binaries until after they walk you through the lengthy compile process. I guess I have to do a make clobber, unpack the binaries and then do the whole build over again. The build went fine as far as I can tell.
Can anyone verify if I have to do it all over with the binaries unpacked? I'm afraid to try flashing the stuff I built just to see what happens. Would there be any harm in that?