Database Develop

Do I need to ALSO revert from Amon-Ra's recovery to stock recovery to get the OTA

I have been searching around on this forum and reading stickies and can't seem to find a definitive answer.
I've reverted my N1 to the stock ROM, but it's still running Amon-Ra's recovery.
The System Updates option in "About Phone" *IS* there, but says no updates are available.
My question is: Do I also need to restore the stock recovery.img in order to get the OTA 2.2 update? Does anyone KNOW whether Amon-Ra's stuff disables OTA Updates? I just am getting a lot of conflicting posts on this.
Thanks

yes you do. amons recovery will only flast test/developer signed roms. the stock recovery will only flash google signed roms.

Yes you need stock recovery for OTA

Thanks for the reply. Now if only I could find an original stock ZIP that isn't reporting as CORRUPTED!!!! Argh..
Randy

****.. if thats true i need a stock recovery too, i'll try to find one

Yeah okay, I've downloaded a bunch of the images both in update format and in 'original' HTC format from the sticky. The originals don't seem to be unzippable. Says the files are corrupt with winzip and windows unzip. so I can't seem to find a recovery.img file to put in my tools folder. I can't believe all these files are corrupt so I'm assuming user error. Anyone?

Just flashed my recovery back to stock.
Used this recovery.img to do it.
Since I'm a new user, I can't post links, but it's on rapidshare DOT com /files/390350606/recovery.zip.html

stock
How to flash back to stock?

Thanks, I think I'm all set. Now just time to wait.....

kevinniven said:
How to flash back to stock?
Click to expand...
Click to collapse
Same way as you flashed to the Amon_Ra recovery image. Fastboot command
"fastboot flash recovery Recovery.img" Just use the stock .img file instead.

In order to unzip the original stock zip files from the HTC mothership, you need to use '7Zip' (Google it) as it's a different kind of zip file. Then you will have all of the imaged you need. Check the post in this forum about going back to stock for the rest of the steps... Now if they would just release thr darn OTA..! (c:
Sent from my Nexus One using Tapatalk

that recovery image is no good.

I followed the instructions in the following thread:
http://forum.xda-developers.com/showthread.php?t=614850
And after the installation I got Build ERD79 (original shipping ROM), almost immediately I got the OTA update to 2.1-update 1 and now my device has the build ERE27 (official update).
That means if you go back to Stock ROM and Recovery, the OTA process should work fine.

Help please
Ok, for the first time, I have a problem that I don't know how to solve.
I followed Seraph1024's instructions to restore to stock. I flashed the userdata.img, boot.img and system.img just fine...it said okay on all counts and booted back into stock ROM. I DID NOT flash the stock recovery.img though
Everything booted fine and it found the 2.1 Update 1 and downloaded it, installed it and then it said verification failed-installation aborted. I then tried to fastboot flash recovery recovery.img to the stock recovery instead of Amon-Ra's and reboot.
When I tried to re-download 2.1 update 1, it says my phone is up-to-date although the About Phone=>Version still says 2.1 only
Now it's stuck on the android with a triangle/exclamation mark in it I need some direction quick as I don't want to screw it up anymore without guidance. THANKS!

mtw4991 said:
Ok, for the first time, I have a problem that I don't know how to solve.
I followed Seraph1024's instructions to restore to stock. I flashed the userdata.img, boot.img and system.img just fine...it said okay on all counts and booted back into stock ROM. I DID NOT flash the stock recovery.img though
Everything booted fine and it found the 2.1 Update 1 and downloaded it, installed it and then it said verification failed-installation aborted. I then tried to fastboot flash recovery recovery.img to the stock recovery instead of Amon-Ra's and reboot.
When I tried to re-download 2.1 update 1, it says my phone is up-to-date although the About Phone=>Version still says 2.1 only
Now it's stuck on the android with a triangle/exclamation mark in it I need some direction quick as I don't want to screw it up anymore without guidance. THANKS!
Click to expand...
Click to collapse
after flashing the stock recovery img i get the same pics when attempting to load the into the recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

punkcell said:
after flashing the stock recovery img i get the same pics when attempting to load the into the recovery.
Click to expand...
Click to collapse
Fixed it with this link, worked like a charm!
http://www.androidcentral.com/how-manually-update-your-nexus-one

HTC one M8_WHL H/K sprint version no OS showing in bootlooder.

Hello all,
I bought this new HTC one m8 few days back, it was in kitkat so i tried the Software update thing, but it keeps searching it for hours then I tried to flash ROMs and then i messed up in TWRP. I accidentally deleted everything without any backup. I tried to flash CM12.1 (not nightly)+ gapps, the logo of cm appears and after that my phone auto reboot and same thing is happening again and again. What i did so far is, i changed my CID, I unlocked my device, tried flashing many ROMs like SkyDragon, and also tried many RUU.zip/RUU.exe files but non of them work. When i tried to open zip files it says cannot open the file/ file maybe damaged or corrupted. I can get into recovery(TWRP 2.8...) I tried to flash through SD but after showing successfully done I get back to this white HTC screen again.
I am seriously in trouble.. please somebody help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SaifAhmed said:
Hello all,
I bought this new HTC one m8 few days back, it was in kitkat so i tried the Software update thing, but it keeps searching it for hours then I tried to flash ROMs and then i messed up in TWRP. I accidentally deleted everything without any backup. I tried to flash CM12.1 (not nightly)+ gapps, the logo of cm appears and after that my phone auto reboot and same thing is happening again and again. What i did so far is, i changed my CID, I unlocked my device, tried flashing many ROMs like SkyDragon, and also tried many RUU.zip/RUU.exe files but non of them work. When i tried to open zip files it says cannot open the file/ file maybe damaged or corrupted. I can get into recovery(TWRP 2.8...) I tried to flash through SD but after showing successfully done I get back to this white HTC screen again.
I am seriously in trouble.. please somebody help.
Click to expand...
Click to collapse
You need to make sure you follow the instructions while flashing a ROM. If you already did check the following:
1. Check if you have custom recovery (TWRP) and custom bootloader (check the thread in development for your device).
2.. Did you flash the right ROM? International (GSM) ROMs are not compatible with Sprint M8. Make sure you are using one from this thread.
3. Most of the time, the ROM zip you have is not completely downloaded. sometime it's error with the download. Whenever you download a ROM/any file make sure the downloaded item matches the MD5 sum.
4. Before flashing a ROM make sure you did a clean wipe. This includes system, data, cache and dalvik cache (but not the data in the sd card - last option shouldn't be checked in twrp). Also for some ROMs you need to be S-OFF. Try installing boot.img using the CMD window.
Let me know if anything mentioned above works for you

Cashreedhar said:
You need to make sure you follow the instructions while flashing a ROM. If you already did check the following:
1. Check if you have custom recovery (TWRP) and custom bootloader (check the thread in development for your device).
2.. Did you flash the right ROM? International (GSM) ROMs are not compatible with Sprint M8. Make sure you are using one from this thread.
3. Most of the time, the ROM zip you have is not completely downloaded. sometime it's error with the download. Whenever you download a ROM/any file make sure the downloaded item matches the MD5 sum.
4. Before flashing a ROM make sure you did a clean wipe. This includes system, data, cache and dalvik cache (but not the data in the sd card - last option shouldn't be checked in twrp). Also for some ROMs you need to be S-OFF. Try installing boot.img using the CMD window.
Let me know if anything mentioned above works for you
Click to expand...
Click to collapse
Thanks bro.. I waited for 1 day then I didnt came back though i fixed it later that day by flashing sprint bad boyz rom and their firmware.. It worked for me

just wanted to point out that the OS showing in the bootloader changes while flashing a zip file in the fastboot. Whatever zip you flashed last, check android-info.txt file. (ofcourse you can flash custom zip files with firmware if you have SOFF only)

Huawei P9 deleted system

Hi everyone, I just bought a P9, nice and shiny I love it. I easily unlock bootloader and I wanted to root but I had some issues with TWRP and ... I deleted System by mistake.
Now I'm tying to repair it without success. I tried with HiSuite, but it says that the phone is not supported. Any ideas ?
thanks

Restore the stock recovery and then you can do a factory reset.

tnhh said:
Restore the stock recovery and then you can do a factory reset.
Click to expand...
Click to collapse
That I tried. I just end up with the big red "!" in the circle. It seems that there's is nothing to reset. Like no system
Any other ideas ? Is there a way to flash a full firmware ? I couldn't find The P9 firmware

for the same mistake i supported another user in a german android forum yesterday.
what model do you have? EVA-09 (single sim) or EVA-19 (dual sim) or any other chinese variant?
if you have EVA-09 you could try my TWRP backup and restore the partitions you deleted.
https://drive.google.com/open?id=0B9gJ44ME0ZkcWFlNdXZKdjdfZmc

paratox said:
for the same mistake i supported another user in a german android forum yesterday.
what model do you have? EVA-09 (single sim) or EVA-19 (dual sim) or any other chinese variant?
if you have EVA-09 you could try my TWRP backup and restore the partitions you deleted.
Click to expand...
Click to collapse
Thank I try that and I get back to you :good:

It seemed to work at first, but i'm in the BootLoop. I wiped dalvik and cache on TWRP and even did a factory reset on stock. I need help getting out of the loop. System seems to be restored anyway. Thank you again for your solutions

tricknaah said:
It seemed to work at first, but i'm in the BootLoop. I wiped dalvik and cache on TWRP and even did a factory reset on stock. I need help getting out of the loop. System seems to be restored anyway. Thank you again for your solutions
Click to expand...
Click to collapse
what model variant do you have? maybe also try to restore the cust partition, but only if you have the EVA-L09.
if i remember correctly the boot.img from my backup is already superSU patched. try to flash superSU 2.65 after restoring the backup. maybe the bootloop is because half installed superSU.

I get a message in log "unable to locate partition by backup name 'cust'
What I did:
1) Restored the backup in TWRP (system + boot)
2) flashed superSU 2.65
3) Wiped Dalvik + cache
4) Wiped Data
5) Reboot
But I'm still stuck in bootlop.
@paratox, I found the german forum, it was a pretty fast success. I'm maybe doing something wrong here.
And Yes I'm on EVA-L09 too

tricknaah said:
I get a message in log "unable to locate partition by backup name 'cust'
What I did:
1) Restored the backup in TWRP (system + boot)
2) flashed superSU 2.65
3) Wiped Dalvik + cache
4) Wiped Data
5) Reboot
But I'm still stuck in bootlop.
@paratox, I found the german forum, it was a pretty fast success. I'm maybe doing something wrong here.
And Yes I'm on EVA-L09 too
Click to expand...
Click to collapse
do you use paulobriens (modaco) TWRP? the other one i think does not support cust partition.
i would try:
1. paulobriens twrp -> restore boot and system
2. flash superSU
3. reboot
4. if bootloop boot into bootloader
5. flash stock recovery
6. boot into stock recovery and do a factory reset

Can You share the twrp recovery img you used ?? paulobriens (modaco) TWRP I found on his website is a test and does not start on my phone after successful flash

this is strange, it should boot. on my EVA-L09 C900 it is working.
maybe do a "fastboot erase cache" before and after twrp fastboot flash. then switch the phone off, remove usb cable and boot into recovery.

paratox said:
this is strange, it should boot. on my EVA-L09 C900 it is working.
maybe do a "fastboot erase cache" before and after twrp fastboot flash. then switch the phone off, remove usb cable and boot into recovery.
Click to expand...
Click to collapse
can you share your recovery img ? "fastboot erase cache" produce a command not allowed. :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i used both recoveries from this site and both are working on mine.
redownload the modaco one, unzip it and flash it again.
or use the other one and try what i wrote.

paratox said:
i used both recoveries from this site and both are working on mine.
redownload the modaco one, unzip it and flash it again.
or use the other one and try what i wrote.
Click to expand...
Click to collapse
Alright, I try that again

@paratox I tried again. The second TWRP is not working and put me in loop, even though it installs.
I was able to perform the factory reset, but bootloop again. I'm a bit desperate. I've owned multiple devices until this P9, I've never been in that situation. aweful !!
I hope someone bring me a solution. I really like the phone :s

you get a bootloop when trying to boot into recovery?
you have to boot into recovery without usb attached. hold power and vol- until the bootloader warning (yellow font, not as many options like normal booting) appears then release the both buttons. then wait until twrp appears.

Thank you @paratox I finally got it !! You help a lot on this one, and another great help as well I thank him too. :highfive:I won't forget to back up next time. I'll take some time to write about what I did in case someone else find itself in trouble with all this. I guess it might be useful .
Thank you guys !! Long day, I need to sleep:laugh::laugh::laugh::laugh::laugh:

@tricknaah: how to fix it?
I have the same problem with modaco recovery bootloop

freak3000 said:
@tricknaah: how to fix it?
I have the same problem with modaco recovery bootloop
Click to expand...
Click to collapse
Hi,
1) flashed TWRP 3.0.0, the other one wasn't working
2) Wiped everything, cache, data, Dalvik, and even System
3) I was provided a link for EVA-L19_C185B130_Middle_East_Region_Android_6.0_EMUI_4.1
3) extracted system.img, boot.img, cust.img and even userdata that I flashed everything (fastboot) with Huawei Extractor
4) After reboot, I got the update circle I guess , and It just fired up Like WOW, better than the first time
I'm not sure all that was neccessary, but yeah It actually worked
I hope it helps! :highfive:

paratox said:
for the same mistake i supported another user in a german android forum yesterday.
what model do you have? EVA-09 (single sim) or EVA-19 (dual sim) or any other chinese variant?
if you have EVA-09 you could try my TWRP backup and restore the partitions you deleted.
https://drive.google.com/open?id=0B9gJ44ME0ZkcWFlNdXZKdjdfZmc
Click to expand...
Click to collapse
Hi, I have the same problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program hauuk user https://forum.xda-developers.com/p9-plus/development/huawei-p9-p9-plus-firmware-updater-t3435878 I used several options inside the L09 option in the middle Of the installation gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.

TWRP / Encryption / Mount issue when trying to root [OP3T]

Hi All. Complete newbie to the forum here......in search of advice!
I've just got my new OnePlus 3T, so wanted to get it all set up and rooted before switching over from my Galaxy S5.
After reading several guides I followed the below steps:
Completed the OTA update to OOS 4.0.2
Unlocked the boot loader
Flashed TWRP 3.0.3
Booted into Recovery and TWRP asked for the encryption password (which was the same pattern I used in normal mode)
Internal memory was accessible so I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip. (I couldn't tell if they flashed successfully).
Rebooted
When the phone tries to reboot, I eventually get a screen saying 'Encryption Unsuccessful' and suggests I need to factory Reset.
When I select to reset, it boots back in to TWRP, but there is no request for the encryption pattern this time, and internal memory doesn't seem to mount. (showing as 0mb).
I'm wondering what my next step should be?
Should I try to flash the latest TWRP (3.0.4) via ADB?
Or would I be better off trying to flash back on stock recovery and the stock OOS 4.02 rom, and then wait for a newer TWRP before trying to get root access again?
.......Or will none of the above work?!
All I was really looking to do was root the phone. I'm not planning on changing from the stock OOS rom. I also don't mind if its encrypted or not encrypted.
I have had a look through some of the threads, but cant find examples of this scenario. Any help appreciated!

Which SuperSU file did you flashed?

The-Wexican said:
I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip.
Click to expand...
Click to collapse
I hope you didn't flash in that exact order. That could possibly be the reason for your issue. Also, you don't need the verity zip if you're flashing SuperSU.

Thanks for the feedback. Below is a link to the guide I followed on the Oneplus forums:
[GUIDE] OnePlus 3T: How to Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup and More !! (It wont let me link the thread as I'm a new user, but Google will show it!
That suggested to flash them in that order, I think.
SuperSU-v2.79-201612051815.zip was the SuperSU I used.

All, just to add, I don't need to recover any data or anything like that. I'm just looking for the best way to get out of this bot loop (of sorts).
I'm kinda thinking that because TWRP Recoveryseems to load OK, I could maybe flash back on the stock recovery and then side load the stock rom?
Any thoughts?
Or is it worth a shot at updating to the latest TWRP first (3.0.4)?

Below is the message I see when I try to boot the phone normally now (not in recovery)........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The-Wexican said:
Below is the message I see when I try to boot the phone normally now (not in recovery)........
Click to expand...
Click to collapse
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success

stephlal said:
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success
Click to expand...
Click to collapse
Awesome!
That worked. Thanks for your help!
Now running OP3T with OOS 4.0.2, TWRP recovery, rooted with SuperSU, and I even cleared the DM-Verity nag screen by booting into bootloader and running:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Very happy now!

Xperia Z booting problem

I unlocked the bootloader of my phone and flashed custom rom. But I decided to return to stock rom. I flashed a stock rom with flashtool, but my phone didn't boot. It stucks at black screen after Sony logo. I can flash custom roms but I can't flash stock roms. Please help, I missed my original phone. :crying::crying::crying::crying:

You have to flash stock kitkat(4.4.4) firmware first, and after that flash lollipop(5.1.1) firmware. It will boot then. When you try to just flash lollipop(5.1.1) it just won't boot.

Tebex said:
You have to flash stock kitkat(4.4.4) firmware first, and after that flash lollipop(5.1.1) firmware. It will boot then. When you try to just flash lollipop(5.1.1) it just won't boot.
Click to expand...
Click to collapse
The first stock rom that I flashed was 4.4.4, but it didn't work. Should I flash the second rom without restarting the phone?

Install 4.4.4 via flashtool - and i mean stock ftf file. make sure you wipe data and cache while flashing. After this you should boot normally. If you want, After you make sure 4.4.4 works, you could Flash 5.1.1

Tebex said:
Install 4.4.4 via flashtool - and i mean stock ftf file. make sure you wipe data and cache while flashing. After this you should boot normally. If you want, After you make sure 4.4.4 works, you could Flash 5.1.1
Click to expand...
Click to collapse
But it's not working, I flashed kitkat rom before but it stucks at black screen, I think I should relock the bootloader but when I want to do that device selector in flashtool is empty so I cant relock.

OXUSINTHEHOUSE said:
But it's not working, I flashed kitkat rom before but it stucks at black screen, I think I should relock the bootloader but when I want to do that device selector in flashtool is empty so I cant relock.
Click to expand...
Click to collapse
Well, now the phone stucks at a screen that "carrément vous" shows up. What does it mean I couldn't have found anythng.

OXUSINTHEHOUSE said:
Well, now the phone stucks at a screen that "carrément vous" shows up. What does it mean I couldn't have found anythng.
Click to expand...
Click to collapse
Thank you very much bro, I fixed my phone thanks to you.

same situation's here!
OXUSINTHEHOUSE said:
Thank you very much bro, I fixed my phone thanks to you.
Click to expand...
Click to collapse
how did you fix your situation?
in my case, i can't anything but black screen just after passing SONY logo.
i can still flash and boot up with custom roms such as xosp or resurrection, but not a single chance with roms based on original xperia one.
how did you fix your mobile ?

Sinwoo Yoo said:
how did you fix your situation?
in my case, i can't anything but black screen just after passing SONY logo.
i can still flash and boot up with custom roms such as xosp or resurrection, but not a single chance with roms based on original xperia one.
how did you fix your mobile ?
Click to expand...
Click to collapse
We had the same situation, I was able to flash the custom rom but not stock. I flashed the 4.4.4 stock rom and I tried to boot but a screen occured than I flashed the 5.0 rom and my phone booted up.

OXUSINTHEHOUSE said:
We had the same situation, I was able to flash the custom rom but not stock. I flashed the 4.4.4 stock rom and I tried to boot but a screen occured than I flashed the 5.0 rom and my phone booted up.
Click to expand...
Click to collapse
I assume that this issue is caused by wiped TA partition after bootloader unlocking.
With my best knowledge, some of customized official ftf has blank TA partition or no partitioning in its ftf.
I found this last night, and I could get my Xperia Z recognized on the Emma, and flashed with geniune service port. (it shows the right one automatically)
But the issue has remained yet. My device is being recognized only as some weird name of device under Emma (I guess it's following the information based on the IMEI number)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
anyway, I guess I may give up at this moment... I can still flash and use with AOSP based ones...