I have a rooted G1 and I am planning to install Cyanogen ROM, but what I definitely want is to have all google apps like GMail, GTalk, Market working.
Since these are no longer included in Cyanogen, I am interested in the way how to install them afterward.
Does it suffice if I just copy them HTC official 1.6 zip into "/system/app" directory, and which of these will work?
I am curious how those stock apps like GMail, GTalk, Calender etc. integrate if installed manually on a custom build such as Cyanogen and what are the eventual problems.
Follow the steps in the Cyanogen MOD wiki
It's just that easy
The method in which you perform you're first Cyanogen MOD install are designed to backup then restore the Google Apps for you
Stuck, but quite far on
Hi there,
I am in a similar boat, and it isn't that easy unfortunately - at least not for me.
I am running a UK O2 Desure with HBOOT 0.80.
I have successfully pushed the new recovery, and used it to install cyanogen 6, which runs great and is very elegant. Unfortunately, the google apps refuse to install. I have tried doing it thru ROM manager and manually.
When I do it manually in CM Recovery, the message I get is:
--Installing: SDCARD:gapps-hdpi-20100817-signed.zip
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
I have had this happen with several downloads from the main site and mirrors, and I have verified the MD5 checksum.
I am not sure what I can do - is there a way to put them on from within cyanogen?
Thanks in advance for any help - I am so close but I feel so far away!!!
Your in the Dream section so I assume you have a dream.
You are using the wrong Gaps. you Need the MDPI not the HDPI.
I recommend the Google Apps (20100816)-tiny
Link is in the wiki above or direct download is
http://mirror.kanged.net/gapps/gapps-mdpi-tiny-20100816-signed.zip
I have installed Last nightly build (46) and I can't install GoogleApps... In the log I see the next steps (something like this):
--Installing: SDCARD:gapps-hdpi-20100817-signed.zip
Finding update package...
Opening update package...
Verifying update package...
Copying files...
Deleting files...
Deleting files...
Deleting files...
Installation complete
After I restart device nothing has changed - NO google apps in phone (((
what's wrong?
PS I used this GoogleApps package before, on Azure ROM.
google is everybodys best friend
Sent from my PC36100 using XDA App
Just get the google apps appropriate to your rom and wipe wipe wipe flash rom then flash gapps reboot system wait about 5-8 minutes before touchin
Oh god... Finally found the source to download the GApps - http://wiki.cyanogenmod.com/index.php?title=Latest_Version
Downloaded last one (http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-20101020-signed.zip), tried to install and ... have another problems!!! (((
After device booted, I receive tooooo many errors! Errors about all google apps. And last one is com.android.setupwizzard! I can't access to phone (((
Help!
fizic said:
Oh god... Finally found the source to download the GApps - http://wiki.cyanogenmod.com/index.php?title=Latest_Version
Downloaded last one (http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-20101020-signed.zip), tried to install and ... have another problems!!! (((
After device booted, I receive tooooo many errors! Errors about all google apps. And last one is com.android.setupwizzard! I can't access to phone (((
Help!
Click to expand...
Click to collapse
thats because you didnt wipe reboot ya phone to recovery wipe everything flash the rom then flash gapps restart and good 2 go
ok this is my first time flashing cyanogen. i have the cyanogen zip file, the danger spl, the new radio, and the mdpi gapps file, and i flashed them all and it still wont boot.
ok the first time i tried
i flashed the spl,
then the radio,
then CM6,
then gapps,
and i was caught in a bootloop so i wiped again
flashed just the CM6 and it booted, so i tried wiping,
flashing CM6
then gapps, now it booted up but my GApps arent there.. so i'm not sure what i'm doing wrong.
fizic said:
I have installed Last nightly build (46) and I can't install GoogleApps... In the log I see the next steps (something like this):
--Installing: SDCARD:gapps-hdpi-20100817-signed.zip
Finding update package...
Opening update package...
Verifying update package...
Copying files...
Deleting files...
Deleting files...
Deleting files...
Installation complete
After I restart device nothing has changed - NO google apps in phone (((
what's wrong?
PS I used this GoogleApps package before, on Azure ROM.
Click to expand...
Click to collapse
use tiny: h t t p://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps (remove spaces)
hey guys...i just rooted my EVO with cm 6.1.2 and i forgot that i needed to flash something else for the market and all google apps....im about 1 hour into rooting and sort of lost.....been asking around and i guess i wasnt asking the right poeple cause no one seems to know what im talking about....some help would be much appreciated,,,,,great to bee rooted though LOL....just need to learn as i go.....thanks fellas
fotochap said:
Hi there,
I am in a similar boat, and it isn't that easy unfortunately - at least not for me.
I am running a UK O2 Desure with HBOOT 0.80.
I have successfully pushed the new recovery, and used it to install cyanogen 6, which runs great and is very elegant. Unfortunately, the google apps refuse to install. I have tried doing it thru ROM manager and manually.
When I do it manually in CM Recovery, the message I get is:
--Installing: SDCARD:gapps-hdpi-20100817-signed.zip
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
I have had this happen with several downloads from the main site and mirrors, and I have verified the MD5 checksum.
I am not sure what I can do - is there a way to put them on from within cyanogen?
Thanks in advance for any help - I am so close but I feel so far away!!!
Click to expand...
Click to collapse
this is the g1 side you need to post in the Desure forum not here
fizic said:
Oh god... Finally found the source to download the GApps - http://wiki.cyanogenmod.com/index.php?title=Latest_Version
Downloaded last one (http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-20101020-signed.zip), tried to install and ... have another problems!!! (((
After device booted, I receive tooooo many errors! Errors about all google apps. And last one is com.android.setupwizzard! I can't access to phone (((
Help!
Click to expand...
Click to collapse
what phone are you on also like they said do a clan wipe then flash rom then gapps
reverepats said:
hey guys...i just rooted my EVO with cm 6.1.2 and i forgot that i needed to flash something else for the market and all google apps....im about 1 hour into rooting and sort of lost.....been asking around and i guess i wasnt asking the right poeple cause no one seems to know what im talking about....some help would be much appreciated,,,,,great to bee rooted though LOL....just need to learn as i go.....thanks fellas
Click to expand...
Click to collapse
please post in the right forum this is the g1 side you need to post in the evo side
CM7 + Google apps
tcash2010 said:
ok this is my first time flashing cyanogen. i have the cyanogen zip file, the danger spl, the new radio, and the mdpi gapps file, and i flashed them all and it still wont boot.
Click to expand...
Click to collapse
Hi, I had the same problem.
Yesterday I flashed 'update-cm-7.0.0-buzz-signed', played with it a bit and tried to flash from sdcard a file called 'gapps-gb-20110307-signed'.
The phone wouldn't boot, it would hang avter the logo arrow made 3 circles.
The same happened for 'gapps-passion-ERE27-2-signed'.
Today I flashed 'update-cm-7.0.0-buzz-signed' again, went to recovery, disables signature, flashed 'gapps-gb-20110307-signed' and it worked.
I had market and google account. Other paas like GMAIL I added manually.
Hope it helps.
I have the correct Gapps zip folder
download this Gapps file to your computer and copy and paste onto the root (paste on the device root not in any folder) on your device. boot into recovery mode and select "Flash from SD card". Then you'll see "gapps-mdpi-tiny-20101020-signed.zip" and Select it. Install and reboot and you should be good and see all your Google apps.
how do you flash all of these things?
newbie...sorry...please help!
thanks!
hectordelarosa501 said:
how do you flash all of these things?
newbie...sorry...please help!
thanks!
Click to expand...
Click to collapse
Look up above u. The instructions are there. If u need further. Instructions then let me know and I'll give u specific instructions.
Took me too long to figure this out, so in case it helps anyone else...
Make sure you do not let your browser unpack the .zip file when you download it, the signature will fail, it's a sig of the zip file package itself, not a checksum on the contents of the zip file.
Do you mean to past alone not in a folder when you say (paste on the device root not in any folder)
Ok, so there seems to be some issues with installing the recent 4.2.1 OTA update with custom recoveries (ie: CWM or TWRP). I ran into this issue myself, and I've seen many other posts with similar problems. I've found the solution and explained it in multiple threads, but due to the nature of the issue, I thought it deserved it's own thread to make sure everyone is aware of the problem and the workaround.
Details:
The 4.2.1 OTA update comes in two flavors - nakasi and nakasig. The former is for WiFi devices (8, 16, 32), and the latter is for 3G devices. In turn, they each have their own device types - grouper and talapia, respectively. While the hardware differences between the WiFi and 3G models is negligible, and most things are interchangeable (ie: kernels, recoveries, etc.), the updates are NOT, and you need to pick the correct one for your platform. For the 3G models, this means the 'nakasig' version.
However, the first thing the OTA update does is validate the integrity of the system. In addition to checking about 200 files in the /system partition, it also looks at the device itself. Specifically:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2/JOP40C/527662:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2.1/JOP40D/533553:user/release-keys");
assert(getprop("ro.product.device") == "talapia" ||
getprop("ro.build.product") == "talapia");
While the first part checks the build.prop file to see what the "ro.build.fingerprint" has defined, the latter (bolded) assert examines what the RECOVERY says the system is. This is where the problem lies. AFAIK, there are no 'talipia' versions of CWM or TWRP. All 3G users running custom recoveries are using the 'grouper' (ie: Wi-Fi only) version. And this is fine 99% of the time. But this is the 1% of the time when they are not compatible. As a result, when the updater script checks recovery, and is told that the system is 'grouper', it aborts the update.
I ran into this issue on both the latest versions of TWRP and CWM. I wasn't sure why, since I thought it just looked at build.prop which was OK. After speaking with oldblue910, he explained that it is getting that information not from build.prop, but from the custom recovery, which is why the update was failing (thanks to oldblue910 for the info!).
SO, I was left with one of two options. I could either restore the stock talipia recovery or modify the update zip to ignore this information. I chose the latter. I'm not sure why Google decided to even but this redundant check in place, since the build.prop fingerprint check should suffice to validate the hardware. Not to mention that the next part of the update is to assert check the majority of files in 'system' anyway, which would fail if it wasn't a 3G device. In any case, by removing the above bolded lines out of the updater-script, my tablet was able to be successfully updated to 4.2.1.
Since many other XDA users run custom recoveries, it is safe to say many other users will run into this issue as well. So I put my custom update online for anyone else to use.
You can download it here:
http://core.routed.com/CUSTOM_RECOVERY-65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
MD5SUM: b0adff6a04ca2ca6234a9678476d329e
A couple notes:
1) This update zip is completely identical to the Google version, outside of the talipia check removed.
2) This update should ONLY BE USED ON 3G NEXUS 7 MODELS. It will NOT work on Wi-Fi only versions.
3) All the other asserts are left in-tact, as they should be. So your 'system' needs to be mostly stock. It checks and patches about 200 files, and if any of them are modified, removed, frozen, etc., the update will fail.
4) The OTA update does NOT check or update the bootloader or kernel, so modifications or non-4.2-stock versions in those areas are fine. However, as stated in #3, mostly everything else should be stock.
5) If the update fails on a specific assert, it will explain what the problem is (ie: the specific apk or odex file). You will need to fix that before proceeding. If you run into an issue and require assistance, you will need to explain the exact error message.
6) As this is almost completely stock OTA update, you WILL lose root/custom recovery unless you take precautions to prevent them from being overwritten. To preserve root, you can use RootKeeper or a similar app to back it up. The latest version of CWM also will warn you if root is lost and apparently restore it for you. For the recovery side of things, the update puts that recovery-recovery file on the system. You can either manually remove it via adb shell (BEFORE REBOOTING AFTER THE UPDATE), or in CWM (and possibly TWRP's case), it should warn you that you might lose custom recovery after the update and ask if you want it to fix it for you (say yes).
Hopefully this helps others who ran into the same error as me. Enjoy!
phonic said:
Ok, so there seems to be some issues with installing the recent 4.2.1 OTA update with custom recoveries (ie: CWM or TWRP). I ran into this issue myself, and I've seen many other posts with similar problems. I've found the solution and explained it in multiple threads, but due to the nature of the issue, I thought it deserved it's own thread to make sure everyone is aware of the problem and the workaround.
Details:
The 4.2.1 OTA update comes in two flavors - nakasi and nakasig. The former is for WiFi devices (8, 16, 32), and the latter is for 3G devices. In turn, they each have their own device types - grouper and talapia, respectively. While the hardware differences between the WiFi and 3G models is negligible, and most things are interchangeable (ie: kernels, recoveries, etc.), the updates are NOT, and you need to pick the correct one for your platform. For the 3G models, this means the 'nakasig' version.
However, the first thing the OTA update does is validate the integrity of the system. In addition to checking about 200 files in the /system partition, it also looks at the device itself. Specifically:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2/JOP40C/527662:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2.1/JOP40D/533553:user/release-keys");
assert(getprop("ro.product.device") == "talapia" ||
getprop("ro.build.product") == "talapia");
While the first part checks the build.prop file to see what the "ro.build.fingerprint" has defined, the latter (bolded) assert examines what the RECOVERY says the system is. This is where the problem lies. AFAIK, there are no 'talipia' versions of CWM or TWRP. All 3G users running custom recoveries are using the 'grouper' (ie: Wi-Fi only) version. And this is fine 99% of the time. But this is the 1% of the time when they are not compatible. As a result, when the updater script checks recovery, and is told that the system is 'grouper', it aborts the update.
I ran into this issue on both the latest versions of TWRP and CWM. I wasn't sure why, since I thought it just looked at build.prop which was OK. After speaking with oldblue910, he explained that it is getting that information not from build.prop, but from the custom recovery, which is why the update was failing (thanks to oldblue910 for the info!).
SO, I was left with one of two options. I could either restore the stock talipia recovery or modify the update zip to ignore this information. I chose the latter. I'm not sure why Google decided to even but this redundant check in place, since the build.prop fingerprint check should suffice to validate the hardware. Not to mention that the next part of the update is to assert check the majority of files in 'system' anyway, which would fail if it wasn't a 3G device. In any case, by removing the above bolded lines out of the updater-script, my tablet was able to be successfully updated to 4.2.1.
Since many other XDA users run custom recoveries, it is safe to say many other users will run into this issue as well. So I put my custom update online for anyone else to use.
You can download it here:
http://core.routed.com/CUSTOM_RECOVERY-65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
MD5SUM: b0adff6a04ca2ca6234a9678476d329e
A couple notes:
1) This update zip is completely identical to the Google version, outside of the talipia check removed.
2) This update should ONLY BE USED ON 3G NEXUS 7 MODELS. It will NOT work on Wi-Fi only versions.
3) All the other asserts are left in-tact, as they should be. So your 'system' needs to be mostly stock. It checks and patches about 200 files, and if any of them are modified, removed, frozen, etc., the update will fail.
4) The OTA update does NOT check or update the bootloader or kernel, so modifications or non-4.2-stock versions in those areas are fine. However, as stated in #3, mostly everything else should be stock.
5) If the update fails on a specific assert, it will explain what the problem is (ie: the specific apk or odex file). You will need to fix that before proceeding. If you run into an issue and require assistance, you will need to explain the exact error message.
6) As this is almost completely stock OTA update, you WILL lose root/custom recovery unless you take precautions to prevent them from being overwritten. To preserve root, you can use RootKeeper or a similar app to back it up. The latest version of CWM also will warn you if root is lost and apparently restore it for you. For the recovery side of things, the update puts that recovery-recovery file on the system. You can either manually remove it via adb shell (BEFORE REBOOTING AFTER THE UPDATE), or in CWM (and possibly TWRP's case), it should warn you that you might lose custom recovery after the update and ask if you want it to fix it for you (say yes).
Hopefully this helps others who ran into the same error as me. Enjoy!
Click to expand...
Click to collapse
I compiled a CWM image for tilapia, so now users can flash updates and roms for their device without trying to by-pass the safety checks. With everyone recommending flashing grouper recovery, people are going to keep flashing grouper roms and wonder why things aren't working correctly.
The two devices differ in more respects than a simple assert check, including having different recovery.fstab files, which are used to make and configure recovery.
Better to have proper recovery for our (unique) device instead of a grouper port. The CWM image is not touch, the touch sources are not open source and koush's online builder is not producing a working image at this time. I ported one by hand, but it is too buggy to release.
I'll add twrp to the post sometime later.
mateorod said:
I compiled a CWM image for tilapia, so now users can flash updates and roms for their device without trying to by-pass the safety checks. With everyone recommending flashing grouper recovery, people are going to keep flashing grouper roms and wonder why things aren't working correctly.
Better to have proper recovery for our (unique) device instead of a grouper port. The CWM image is not touch, the touch sources are not open source and koush's online builder is not producing a working image at this time. I ported one by hand, but it is too buggy to release.
I'll add twrp to the post sometime later.
Click to expand...
Click to collapse
Thanks, that's definitely a better solution versus a work around.
Though the safety check bypassed in the OP wouldn't cause any issues since it was redundant and unnecessary. The OTA update already checks build.prop for the model info and all the apks/odexes it updates, so it would be impossible to flash it on a non-compatible device. But you raise a very valid point about incorrect ROMs and other things. The 3G unit probably needs it's own forum.
Did you have to make any real modifications to CWM outside of changing grouper to talapia?
The 3G unit probably needs it's own forum.
Click to expand...
Click to collapse
Its already done here; http://forum.xda-developers.com/forumdisplay.php?f=2022
Ather said:
Its already done here; http://forum.xda-developers.com/forumdisplay.php?f=2022
Click to expand...
Click to collapse
Woohoo! Thanks.
I had some issues when I did the update. It gave me some errors, and aborted, but then I found a link that had the update and I got it to update. This happened on my n4 and n73g. Well, for some reason, the recoveries got deleted so I had to reinstall them. I was able to use the goo manager to restore TWRP on my N4, but it wasn't working on my N7 so I had to side load it. After this, I noticed that google now wasn't working on my n4, and the volume rocker on my n7 had some issues. I went in and wiped the cache and dalvik cache and rebooted. Google now works on my N4, and while the volume gets adjusted on my N7, it won't make the beep every time I push up or down on the rocker indicating the volume level. I haven't noticed any other issues, but I haven't really delved into my devices. I may try to do a factory wipe and return everything to stock just to see what went wrong in the first place and to see if I can do anything different I still can't figure out how to get ADB running on my computer, so yes I used one of the tool kits to load everything. I know the OP's position on tool kits, but I just can't figure out how to get ADB running manually, AND it takes so long to download and install everything unless I am installing things I don't even need.
Nexus 7 takju firmware update
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Do you have the Galaxy Nexus or Nexus 7? If Galaxy Nexus, you of course would want to check those forums. As for the updates, you should normally see a notification alerting you of the update, but you can also check for it in settings/about phone/system updates. Otherwise the appropriate forum for your device will have links to the update files. Good luck!
lil help please
I updated to 4.2.1 with the OTA zip file using TWRP and voodoo root keeper installed. It flashed just fine. Rebooted with update. My root access is funky though. SuperSU is still there and I can access root file threw root explorer but I can't mount it as writable and when I install a new app that needs root access it never asks for it. Does superSU need to be updated? There is no update available for it.
Vlad7777 said:
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Click to expand...
Click to collapse
Is your device rooted? Is this your first android device? You will get a little notification in the notification bar at the top saying your deivce has an update.. If you have not rooted, you will receive the first OTA in a day or two that will go from JVP15S to JOP40C. Then later, you will receive the update for JOP40D. Some people have had success at forcing the update by going to settings, apps, all, google framework services, and selecting force stop then clearing the data. You then go back into settings, about device, check for updates and check for update.
Vlad7777 said:
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Click to expand...
Click to collapse
The N73G ships with an interim 4.2 build, which is JVP15S. There are some significant differences between this and JOP40C, which is the first update you will get out of the box. I imagine 4.2 wasn't fully finalized prior to hardware production, and they didn't want to hold it up until they were ready (wise choise!). In my case, within an hour after opening my N73G and turning it on, I had the 40C update notification. I applied this prior to rooting/modding/etc. ONLY after you are on 40C can you get the upgrade to 40D (4.2.1). Google pushes out incremental patch updates, so you can't skip a version.
So you have two options:
1) Apply update #1 and wait for #2 and then root/etc.
2) If you don't want to wait, and your device is still basically brand new and not setup (too much), AND assuming you want to root, customize, etc., just download the 4.2.1 system image from Google and fastboot flash it. You'll need to unlock the bootloader anyway, which will wipe your system, so now's a perfectly good time to do everything at once. Unlock bootloader, flash 4.2.1 stock (40D FULL IMAGE), flash custom recovery, install su zip, install any other mods (which is limited really to basic stuff and a custom kernel right now), enjoy.
Andoid 4.2.1 update
adamhlj said:
Is your device rooted? Is this your first android device? You will get a little notification in the notification bar at the top saying your deivce has an update.. If you have not rooted, you will receive the first OTA in a day or two that will go from JVP15S to JOP40C. Then later, you will receive the update for JOP40D. Some people have had success at forcing the update by going to settings, apps, all, google framework services, and selecting force stop then clearing the data. You then go back into settings, about device, check for updates and check for update.
Click to expand...
Click to collapse
Thanks!
It is my first Android device.
I am trying to root it (unsuccessfully).
I was able to get the FASTBOOT unlock - but cannot root because of the drivers interface...
I did update the firmware by forcing via framework system. Had to do in two steps as it only upgrades one generation at a time.
By the way - I had the "takju" - now it is "tilapia" after "official OTA update.
I hope to get the rooting problem resolved - all instructions on the net are for older ROMs and I already screwed up my work laptop installing obsolete PDANET drivers which replaced the original drivers - so my device manager which originally saw my Nexus 7 as "Nexus 7" now sees it as "Android Phone Device". I do not know how to recvert back.
So now I am going to try my other laptop for rooting.
Hopefully I could find just a "professional step by step procedure - unlike many that I found on the net. Many people just happy to get on YouTube to show themselves off but the advice is half ass.
Thanks again for your help though I am half way through.
Best regards
Vlad7777 said:
Thanks!
It is my first Android device.
I am trying to root it (unsuccessfully).
I was able to get the FASTBOOT unlock - but cannot root because of the drivers interface...
I did update the firmware by forcing via framework system. Had to do in two steps as it only upgrades one generation at a time.
By the way - I had the "takju" - now it is "tilapia" after "official OTA update.
I hope to get the rooting problem resolved - all instructions on the net are for older ROMs and I already screwed up my work laptop installing obsolete PDANET drivers which replaced the original drivers - so my device manager which originally saw my Nexus 7 as "Nexus 7" now sees it as "Android Phone Device". I do not know how to recvert back.
So now I am going to try my other laptop for rooting.
Hopefully I could find just a "professional step by step procedure - unlike many that I found on the net. Many people just happy to get on YouTube to show themselves off but the advice is half ass.
Thanks again for your help though I am half way through.
Best regards
Click to expand...
Click to collapse
I think you are either looking at really bad guides or simply making the rooting process much harder on yourself.
While some Android devices have more complicated unlocking/rooting/etc. requirements, that is not the case with Nexus devices - certainly not the Nexus7. The process couldn't be more simple. If you've already unlocked the bootloader, you are 1/3 of the way there. All you need to do is copy over a compatible "su" app zip to the device, install or run a custom recovery, install the su zip and voila - rooted.
If you already have fastboot running, that's the only tool you need. Download a custom recovery (CWM or TWRP) from a thread in this forum that is compatible, reboot into bootloader mode and install it:
fastboot flash recovery <recovery.img>
Then reboot into recovery mode (you can do this from bootloader), and you should be in CWM/TWRP. Then you simply install the SU zip using the menu on the screen.
It's a very simple process and does not require a special toolkit or anything like that.
phonic said:
I think you are either looking at really bad guides or simply making the rooting process much harder on yourself.
While some Android devices have more complicated unlocking/rooting/etc. requirements, that is not the case with Nexus devices - certainly not the Nexus7. The process couldn't be more simple. If you've already unlocked the bootloader, you are 1/3 of the way there. All you need to do is copy over a compatible "su" app zip to the device, install or run a custom recovery, install the su zip and voila - rooted.
If you already have fastboot running, that's the only tool you need. Download a custom recovery (CWM or TWRP) from a thread in this forum that is compatible, reboot into bootloader mode and install it:
fastboot flash recovery <recovery.img>
Then reboot into recovery mode (you can do this from bootloader), and you should be in CWM/TWRP. Then you simply install the SU zip using the menu on the screen.
It's a very simple process and does not require a special toolkit or anything like that.
Click to expand...
Click to collapse
Thank you for your reply and advice.
How do I place the "su zip" in the device and into which directory - I can try download directly to Nexus but needs to know where to place it.
Also what are "CWM" or "TWRP" And where do I place them for custom recovery procedure.
I apologize for my ignorance but Android is a complete new experience for me.
Vlad7777 said:
Thank you for your reply and advice.
How do I place the "su zip" in the device and into which directory - I can try download directly to Nexus but needs to know where to place it.
Also what are "CWM" or "TWRP" And where do I place them for custom recovery procedure.
I apologize for my ignorance but Android is a complete new experience for me.
Click to expand...
Click to collapse
You can place the "su zip" anywhere you like on the internal storage. When you get into custom recovery (CWM or TWRP), you can select "Install ZIP" (or something along those lines) and it will bring up a file system explorer that will let you select the one you want to install.
CWM and TWRP are both custom recoveries. They replace the stock, and very useless, recovery and give you many more advanced features. Things like flashing zip files, making nandroid backups, etc. You need to flash them to your "recovery" partition. It's a very easy process, but will require some specialized software. There are many guides and toolkits (if that's what you want to use) online. Just make sure you use the Talipia recovery (which exists now in the 3G forum).
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
AbhiM7 said:
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
Click to expand...
Click to collapse
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
hellcat50 said:
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
Click to expand...
Click to collapse
Hi, I've already downloaded this very stable file and tried flashing using TWRP
AbhiM7 said:
Hi, I've already downloaded this very stable file and tried flashing using TWRP
Click to expand...
Click to collapse
I read something about wrong batteries causing this problem. Do you use the original battery?
hellcat50 said:
I read something about wrong batteries causing this problem. Do you use the original battery?
Click to expand...
Click to collapse
I though of running a diagnosis check by dialing *#808# and looked up Charger option, it shows the battery as "itech_3000mah"
is that original?
I had given the phone to repair for water damage to a professional service chain (Not OnePlus, some company here called Yaantra). I've heard from talking to an official repair person of OnePlus that fake batteries are not possible for OnePlus.
The battery works absolutely alright, charges up nicely and I get decent SOT. Can't complain at all.