Develop Bugs

Lollipop root problem

LG 10.1 wireless only. I upgraded to Lollipop and I am trying to root with the one click script I get a screen that says download mode I start the script my tablet switches to a screen that says updating firmware and that is where it sits. What am I doing wrong? I installed the drivers and Windows can see the tablet when it is on.

I tried many methods to root Lollipop stock on my G Pad 7, but this one is the only that worked for me. It requires to do steps manually, but it works! I was in your same situation, hope it helps..
http://forum.xda-developers.com/showpost.php?p=59309508&postcount=1
[ zer0lab.dev ~ Lollipop stock on LG G2 ~ xda free ]

Thanks I'll try that in the next day or two.
Sent from my SPH-L900 using XDA Free mobile app

jpisini said:
LG 10.1 wireless only. I upgraded to Lollipop and I am trying to root with the one click script I get a screen that says download mode I start the script my tablet switches to a screen that says updating firmware and that is where it sits. What am I doing wrong? I installed the drivers and Windows can see the tablet when it is on.
Click to expand...
Click to collapse
Try with the version 1.3 LG one click root

I have always had to do steps manually. The auto-rooter app only worked once for me across all my devices. It seems to not always work reliably, typically requiring 3 or more attempts before the script actually takes off and roots the device.

player911 said:
I have always had to do steps manually. The auto-rooter app only worked once for me across all my devices. It seems to not always work reliably, typically requiring 3 or more attempts before the script actually takes off and roots the device.
Click to expand...
Click to collapse
Mine rooted first try with kingroot on lollipop , but use at least version 4.1 and 4.5 update from kingroot allowed me to use supersume to switch for upersu with successful binary update... For some reason I am NOT seeing anyone else anywhere mentioning have done this method like me so I'm curious why more people haven't figured that one out lol or I'm just missing a bunch of post somewhere
Sent from my VS986 using Tapatalk

dadrumgod said:
Mine rooted first try with kingroot on lollipop , but use at least version 4.1 and 4.5 update from kingroot allowed me to use supersume to switch for upersu with successful binary update... For some reason I am NOT seeing anyone else anywhere mentioning have done this method like me so I'm curious why more people haven't figured that one out lol or I'm just missing a bunch of post somewhere
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
There are a few different posts around regarding using Kingroot for the G Pad. I had a significant delay in root appearing/working initially then getting king off of the pad. But recently updated everything, tried again and didn't have as many problems.

Yeah it was not a lot of issues to kingroot and switch to supersu, the problem now is I rebooted one day all the sudden and it is stuck in a boot loop I cannot get out of or find clear instructions on how to get out of. I can get to the Verizon logo, or recovery where any option send me to the fast boot screen and it will send me to a blank screen. I don't have a computer and don't really know what to do with it. The crazy thing is I didn't do anything at all that would have cost that it just did it, unfortunately it's just one of the risk of rooting
Sent from my VS986 using Tapatalk

how to fix The dead android bot with error when enter recovery?

hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?

Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.

hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem

koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop

hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?

koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.

rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.

NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!

ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?

koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.

5.1.1 OTA update not working

My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.

traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.

Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.

traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.

traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!

I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937

traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....

Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.

traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous

Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....

traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.

SW3 may need partition repair

My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Edit: I found this post http://forum.xda-developers.com/smar...rsion-t2988087 and I was able to get the watch working again. I still cannot use XC to repair or update, but at least it is working with LP.

golfnut22 said:
My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Edit: Edit: I found this post http://forum.xda-developers.com/smar...rsion-t2988087 and I was able to get the watch working again. I still cannot use XC to repair or update, but at least it is working with LP.
Click to expand...
Click to collapse

Same issue here
Hi,
I have the exact same issue with my sw3, stuck on the four symbols. Like you I managed to flash TWRP and mount the SWR50-LWX48P-repacked ROM. This doesn't do the trick unfortunately because firstly I cannot update the ROM and worst of all the watch will not connect to my smartphone. Like you I suspect there to be an issue with the partitions but I haven't got a clue really. Hope for some help on this.

baronimus said:
Hi,
I have the exact same issue with my sw3, stuck on the four symbols. Like you I managed to flash TWRP and mount the SWR50-LWX48P-repacked ROM. This doesn't do the trick unfortunately because firstly I cannot update the ROM and worst of all the watch will not connect to my smartphone. Like you I suspect there to be an issue with the partitions but I haven't got a clue really. Hope for some help on this.
Click to expand...
Click to collapse
Yes, I still have not been able to update to MM. Mine does connect to my smartphone with no issues. Although, the last time I did have an issue where it kept cycling and trying to connect to the internet via the phone. So, I went thru the steps again to basically get it back to the ROM you noted above and it is working. One thing I have noticed once I get it going with the steps I used, I cannot boot to twrp via fastboot. I have to go to XC and let it try and repair, which it says it does, but doesn't. I get the 4 dots again, and from there when I fastboot, I can fastboot twrp.img and adb push stuff to install. However, I have noticed that I need to use the flash commands and flash the .simg file noted in my thread in order for the above ROM to actually work. I also noticed when that ROM is installing, it does mention working on partitions...so, it must be doing something to some of them.
I would love to be able to get MM working on this, but I think I have run out of ROMs to try. I'm probably not sequencing something right, but have not clue as to what is wrong. I am an newbie at this.
If you get MM to finally update on your watch, it would be much appreciated if you would share your detailed process in achieving that success.

BND-L24 System update failed

I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.

johncro13 said:
I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
Click to expand...
Click to collapse
I'm not certain why that happens, But I have a guess.
On each update that I have looked at, the recovery gets and update too. So different signatures and such.
Maybe the "stock" recovery you have re-flashed, is not correct version for your installed and update rom.
I cannot confirm this as I am missing the update app.
If you could help me with my missing files , I could help you with your update problem.
You could help me by pulling a list of packages installed so I can see what apps I have missing, and hopefully get them back (stock only, preferably done after a fresh factory reset.)
Directions for this on this thread.

See attached.

johncro13 said:
See attached.
Click to expand...
Click to collapse
thank you that helps.
I see I am missing an entire folder.
/data/hw_init
Could you see if it is accessible .
Code:
mkdir %userprofile%\Desktop\hw_init
adb pull /data/hw_init %userprofile%\Desktop\hw_init
I think it is not permitted though.

Uploaded. See referenced thread. I hope it helps!

johncro13 said:
Uploaded. See referenced thread. I hope it helps!
Click to expand...
Click to collapse
I will see what I can do with that. And hopefully can get past any file verification. And if I figure that out it should help you too.
Or , with my luck, the moment I figure it out , the stock firmware will come out.
I pushed the hw_init folder to /data while in twrp, then put stock recovery back(the version I expect should be correct) and I got same update failed error, as the OP.
That tells me maybe is probably some other reason , besides the version of stock recovery is causing this trouble.

Not sure if there is confirmation of successful update while bootloader is unlocked or not. Too late for me to try tonight, but next I will re-lock bootloader and try again.
My last (really current) phone needed to be re-locked in order to take updates.
**UPDATE**
re-locking bootloader did not help any at all. I still have error failed to check file, please download again.

On the manual update to oreo thread, they are using a "stock-ish" recovery named "no-check"
I am thinking I might flash that recovery to try and force this update to install.

BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?

johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
tried it earlier today. Same error. will not finish update

johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
I have ordered a second 7x. I plan to pull the hw_init folder , and the remainder of /data that might be missing from this device , because of a result of formating it in twrp. I plan to restore that as an image, in hopes of getting updater to complete properly. And if that works, you will be able to use my backup and update your phone too.
If not , well , doesn't hurt to try.
I'm comparing the images pulled from my device and the images available for the Indian "return to stock thread. And I see the problem with the USA L24 version.
The cust.img for usa has no app folder.
It did not make sense to me before why there was apps only installed in /data. Because /data should be able to be fully wiped and your system will recreate the file structure. But The apps should have been on one of the images.

My second phone arrived today. I pulled the hw_init folder from it.
did a diff comparison on the updater app from the new phone and and the one that I had to apply patches to , to bring it up from b101 to b140. The result was 100% same.
and three more apps where in the hw_init folder as well. (bloat apps really)
now the bad news.
My original phone (the one that I had formatted /data on). Now has the same /data/hw_init folder as the brand new device. But always shows no update available.--It showed update once, the first time checked, install failed , now shows nothing available.
And the new phone does show an update available (B150) , but fails to install. Then after the failed install, now it shows no update available.

That's insane.
So... in summary, neither will update? Neither the original nor the unaltered brand-new device?

If anyone else has had this issue but has since resolved it, would you mind letting us know how? @mrmazak is working on it and I've also been told by the FUT team that I should expect some kind of communication from "Oscar Felix."
(If you've searched the forums for other Honor or Huawei devices, you probably already know that there is some speculation about whether or not Oscar Felix is a real person.)

I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root

Sonny1732 said:
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Click to expand...
Click to collapse
Did you get the Oreo update today?

No I didn't, did you find out what can we do about this?

Is it a way I can update my phone manually

I'm watching this thread , myself. That might be the key.

Hopefully something comes up soon or is there a rom I can get if I reroot my phone?