Database Develop

Android 4.2.1 (JOP40D) for Nexus 7

Android 4.2.1 (JOP40D) for Nexus 7 Wifi and 3G+
Manual Update Available [Updated]​
Install:
Those with a custom recovery can just download the zip below, move it to their device, and flash away. If you're running stock recovery, substituting only the zip file name in Step 2.
Just after users began reporting that your Google Nexus N7 device were receiving an update to Android 4.2 Jelly Bean (build JOP40C, to be precise), it looks like the manual update package is available for download. As could be expected, this coincides almost perfectly with the launch of Google's newest additions to the Nexus family – the Nexus 4 and 10.
For those ready to download and install manually, the process is easy. If you have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual. Those with stock recovery should keep the file on their computer, and just follow a few easy instructions:
Disclaimer: I'm not responsible in case of brick of your device - proceed at your own risk.​
Step 1.
- Reboot your Google Nexus 7, holding the Volume Up and Volume Down buttons while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, press Volume Up and the Power button together, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
- Connect your Google N7 to your computer with a USB cable.
- Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
- Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the JOP40C zip file you've downloaded.
Type in the following:
For the Nexus 7 "NAKASI"
Code:
adb sideload 659e6288b87d.signed_nakasi_JOP40D_from_JOP40C.659e6288.zip
For the Nexus7 3G+ "NAKASIG
Code:
adb sideload 65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
- Reboot and enjoy! You are now running Android 4.2.1 on your Nexus

I modified my OP and put online the updates for both versions of Nexus 7

Hello
The link for the wifi N7 is broken I think

My N7 is rooted, stock rom, cwm recovery, voodoo ota rootkeeper, supersu. I d/l the update from Droid Life and copied it from my computer to the N7 internal storage. Booted into cwm recovery, chose to install zip from sdcard, chose the d/l'd file from the /0 folder (filename 659e6288b....zip), chose to reboot system, answered 'Yes' to preventing flashing stock recovery, answered 'Yes' to keeping root. All is good. Still have root and cwm recovery.

Foggy79 said:
Hello
The link for the wifi N7 is broken I think
Click to expand...
Click to collapse
I have the same issue.
Sent from my Nexus 7 using xda app-developers app

Will this wipe my data, let me know so I can make a backup, thanks
Sent from my Nexus 7 using xda premium

OP Why you don't post oficial Google link directly from Google servers? Also here is a thread already http://forum.xda-developers.com/showthread.php?t=1745781 and in instruction its better to explain how to open cmd Window/cmd prompt in a folder "ctrl+right click" in an empty space where your zip is and (select open cmd here).
Sent from my SPH-D710 using Tapatalk 2

philos64 said:
Install:
Those with a custom recovery can just download the zip below, move it to their device, and flash away. If you're running stock recovery, substituting only the zip file name in Step 2.
Click to expand...
Click to collapse
Link is Broken above...... but I worked out it is here
http://www.androidfilehost.com/?fid=9390202682628636802
What do I need to do if I have custom recovery but am still on 4.1.2?
Thanks

Try to flash this with TWRP 2.3.2.1 but got error Status 7, same with CWM 6.0.1.0, tried to google what's going on but I can find none, can someone help me with this ?

mr_gem said:
Try to flash this with TWRP 2.3.2.1 but got error Status 7, same with CWM 6.0.1.0, tried to google what's going on but I can find none, can someone help me with this ?
Click to expand...
Click to collapse
I had this problem with the first 4.2 update and now the same again with 4.2.1.
Last time I had to put the bootloader back to stock (drastic) to get the update,.
sideload doesnt work either.
Motorola Atrix (AOKP JB)
Nexus 7 (Stock)
Past life:
HTC Desire HD reboot loop overheating.
Nokia N900 micro usb port loose.

Omar04 said:
OP Why you don't post oficial Google link directly from Google servers? Also here is a thread already http://forum.xda-developers.com/showthread.php?t=1745781
Click to expand...
Click to collapse
Because it's my choice, and if you don't use it, don't use it :silly:
and if you read this thread, have you got some instructions for install it? NO
Have you find one link from Google servers ? Not yet - at 03.15 PM - 29 Nov 2012
Omar04 said:
and in instruction its better to explain how to open cmd Window/cmd prompt in a folder "ctrl+right click" in an empty space
Click to expand...
Click to collapse
I surprised that you don't know how to use the command lines,
And if you think about the new users , they can read a lot of guide which explain how use the command lines. It's one of the basic of installations under Android
and it's not the usefulness of this post !!!
Omar04 said:
where your zip is and (select open cmd here).
Click to expand...
Click to collapse
And if you click to "DOWNLOAD LINK" you will see that you can download the files
With a lot of pleasure

The download link for the Nexus 7 wifi aka "NAKASI" is repaired

Downloaded update from official Google link, flashed in CWM Recovery, kept bootloader, kept root. All is well.

Help Help PLEASE
OK I did everything and the update worked for JOP40C. I`m running stock so no rooting.
Then I wanted to upgrade to JOP40D.
I got to just after the little green android with the exclamation mark on it. I then held the Power button and the Up button. Instead of getting the next menu it just died on me. :crying:
So what now?

I went through this project step by step and was just about to flash manually when the OTA symbol magically appeared in my bar.
Oh well... I guess I'll take the easy way this time.

St1ck33 said:
Downloaded update from official Google link, flashed in CWM Recovery, kept bootloader, kept root. All is well.
Click to expand...
Click to collapse
Sounds good for you :good:
AfrikaansAndroid said:
OK I did everything and the update worked for JOP40C. I`m running stock so no rooting.
Then I wanted to upgrade to JOP40D.
I got to just after the little green android with the exclamation mark on it. I then held the Power button and the Up button. Instead of getting the next menu it just died on me. :crying:
So what now?
Click to expand...
Click to collapse
- If you're running stock recovery, substituting only the zip file name in Step 2.
Step 2.
- Connect your Google N7 to your computer with a USB cable.
- Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
- Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the JOP40C zip file you've downloaded.
type this line command for N7 3G:
Code:
adb sideload 65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
for N7 wifi only go to OP..
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update
and reboot for finish
PMOttawa said:
I went through this project step by step and was just about to flash manually when the OTA symbol magically appeared in my bar.
Oh well... I guess I'll take the easy way this time.
Click to expand...
Click to collapse
Use the update by OTA...let's go

Running 4.2, rooted, CWM latest recovery (forget version). I had previously done the clear data from one of the Google apps and succesfully got my 4.2 from 4.1.2 OTA - CWM handled it just fine. I didn't want to take any chances doing that again, I downloaded this file, flashed in CWM, rebooted and all seems fine. Still have root, still have swype, still have cerberus.
Thanks OP!
Edit: Due to the new /0/ emulated sdcard for multiple users, I copied the zip file to my sdcard through windows - but CWM couldn't see it. I had to navigate to /0/ and then CWM could see it. Just a heads up.

Thread will be closed
Code:
[B][COLOR="Red"][CENTER][SIZE="4"]This thread will be closed very shortly because it's now useless.
"Developers Google"website has released updates ;)
I will deleted all download links.[/SIZE][/CENTER][/COLOR][/B]

philos64 said:
Code:
[B][COLOR="Red"][CENTER][SIZE="4"]This thread will be closed very shortly because it's now useless.
"Developers Google"website has released updates ;)
I will deleted all download links.[/SIZE][/CENTER][/COLOR][/B]
Click to expand...
Click to collapse
Edit: NM there's a thread linking to all OTA updates. you can delete this post.

Sorry, but your post is useless too
I have contacted Mods for close this thread

[Q] Uninstall Clockworkmod

Guys any suggestion on how to uninstall CWM, want to give a try on roms using 4ext.

Lol. Its funny cuz i was thinking the exact same thing this morning.
However, its really simple. just go here. Go down to Download section and download 4ext Revocery Updater. Put that on your phone. install the application thru a file browser. Then open the application and press Online install | upgrade and it will ask for u to connect to 4ext servers. Click Do not display again and then press yes. Install the latest version. This will come in the form of a zip file and put that back on your computer.
Extract the recovery.img (dont rename it for simplicity sake) from the zip folder into ur sdk/platform-tools. Then open the Command Prompt and navigate to the platform-tools folder or alternatively just click shift right click and "open command window here" from within the platform-tools folder. Now power into bootloader and clock fastboot. It shoulds say fastboot USB. Now type into the cmd from your computer
fastboot flash recovery recovery.img
and hit enter. Then ure recovery should be flashed. Boot into recovery and u should have 4ext touch reovery

072665995 said:
Lol. Its funny cuz i was thinking the exact same thing this morning.
However, its really simple. just go here. Go down to Download section and download 4ext Revocery Updater. Put that on your phone. install the application thru a file browser. Then open the application and press Online install | upgrade and it will ask for u to connect to 4ext servers. Click Do not display again and then press yes. Install the latest version. This will come in the form of a zip file and put that back on your computer.
Extract the recovery.img (dont rename it for simplicity sake) from the zip folder into ur sdk/platform-tools. Then open the Command Prompt and navigate to the platform-tools folder or alternatively just click shift right click and "open command window here" from within the platform-tools folder. Now power into bootloader and clock fastboot. It shoulds say fastboot USB. Now type into the cmd from your computer
fastboot flash recovery recovery.img
and hit enter. Then ure recovery should be flashed. Boot into recovery and u should have 4ext touch reovery
Click to expand...
Click to collapse
I would give it a shot.
Do you already did it??
Enviado desde mi XT910 usando Tapatalk 2

Download 4EXT Updater. Download latest version of 4ext and the phone flashes it for you. Keep in mind that 4ext does not replace cwm, it just copies over it. You backups are still in the cwm folder.
Sent from one of the few remaining Incredible S'

Piccilino said:
Download 4EXT Updater. Download latest version of 4ext and the phone flashes it for you. Keep in mind that 4ext does not replace cwm, it just copies over it. You backups are still in the cwm folder.
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
What I see is that I can continue using both but by sepatate.
Once installed and in a future want to use the CWM just uninstall 4ext or have to do something special
Sent from my Incredible S using Tapatalk 2

Yes i did flash 4ext recovery and works like a charm. However, its just copied over cwm. I also dont think its possible to uninstall something once its flashed to your phone. its like when u flash something in the ROMs or other things like Mods from the recovery. U cannot remove it (at least from my basic understanding lol). Cuz whenever u wanna flash something in cwm it always says
Are you sure you want to flash this
-no
-no
-no
-no
-no
-yes
-no
-no
lol

072665995 said:
Yes i did flash 4ext recovery and works like a charm. However, its just copied over cwm. I also dont think its possible to uninstall something once its flashed to your phone. its like when u flash something in the ROMs or other things like Mods from the recovery. U cannot remove it (at least from my basic understanding lol). Cuz whenever u wanna flash something in cwm it always says
Are you sure you want to flash this
-no
-no
-no
-no
-no
-yes
-no
-no
lol
Click to expand...
Click to collapse
Once its flashed "over the top", CWM is removed and 4EXT takes its place. Basically anything you flash on top of something else removes what was there before in that exact place. For example if you were sitting on a chair and I came and replaced you, you wouldn't be on that chair anymore, would you?
That is just a precaution because you can go wrong with flashing the wrong thing, and you can't un flash

markj338 said:
Once its flashed "over the top", CWM is removed and 4EXT takes its place. Basically anything you flash on top of something else removes what was there before in that exact place. For example if you were sitting on a chair and I came and replaced you, you wouldn't be on that chair anymore, would you?
That is just a precaution because you can go wrong with flashing the wrong thing, and you can't un flash
Click to expand...
Click to collapse
Lol very nice metaphor!
I did this the other day and it worked fine. Just install the 4EXT app and install from there.

I installed the app and installed the recovery from there, everything working fine.
Sent from my Incredible S using Tapatalk 2

hi have done the what you instructed but am stuck at sending recovery for the past 20 minutes. I am on HTC Incredible S rooted with htc dev and having installed cwm with unlocked status with S-on, HBoot - 2.00.0000 & radio - 3822.10.08.28_M. Right now am using NIK's rom but cannot install other Rom's as am not on 4ext.. so please help me...Thanks in advance!!!
072665995 said:
Lol. Its funny cuz i was thinking the exact same thing this morning.
However, its really simple. just go here. Go down to Download section and download 4ext Revocery Updater. Put that on your phone. install the application thru a file browser. Then open the application and press Online install | upgrade and it will ask for u to connect to 4ext servers. Click Do not display again and then press yes. Install the latest version. This will come in the form of a zip file and put that back on your computer.
Extract the recovery.img (dont rename it for simplicity sake) from the zip folder into ur sdk/platform-tools. Then open the Command Prompt and navigate to the platform-tools folder or alternatively just click shift right click and "open command window here" from within the platform-tools folder. Now power into bootloader and clock fastboot. It shoulds say fastboot USB. Now type into the cmd from your computer
fastboot flash recovery recovery.img
and hit enter. Then ure recovery should be flashed. Boot into recovery and u should have 4ext touch reovery
Click to expand...
Click to collapse

Downloaded the 4ext recovery, installed it on phone, did the online install, upgraded and installed 4EXT_Recovery_Touch_v1.0.0.5_RC9, extracted recovery image from this file put it in the android folder with the following files adb (application file), AdbWinApi.dll, boot (image file), Fastboot (application file), Unlock_code file. Connected the phone to the computer in bootloader, went to fastboot and connected it to the computer which than showed fastboot usb, went into cmd and typed fastboot flash recovery recvoery.img in the android folder with the above mentioned files with the recovery image file. Now for the past 20 minutes it is stuck at sending recovery <5466 kd>.....
Please help??? dont know what I am doing wrong???

there is other way to Flash recovery by avoiding overwriting files...I used this many time to switch between 4EXT Touch >> CWM >> TWRP...
Right click on command prompt and select 'RUN AS ADMINISTRATOR'...
Give a path of fastboot drivers... (mine is C:/android/adb) depend on ua adb driver location...
type command...
fastboot erase recovery
it will erase ua recovery (It will erase ua recovery only and only if u run command prompt as administrator)
put ua desired recovery in adb folder where u installed adb and fastboot drivers (rename it to recovery for more connivance )
type this command now...
fastboot flash recovery recovery.img
it will send ua recovery to system and ua done...

Thanks but right now I am stuck at sending recovery, so if I remove cwm and than flash 4ext as you have suggested and I again get stuck on sending than I won't have any recovery...
Sent from my HTC Incredible S using Tapatalk 2

andzy said:
Thanks but right now I am stuck at sending recovery, so if I remove cwm and than flash 4ext as you have suggested and I again get stuck on sending than I won't have any recovery...
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
So you are saying that after flashing 4ext, you cant boot into recovery???
Cuz i find that kinda funny considering the fact that 'flashing' means you overwrite and replace. Since 4ext is built from CWM I dont see how it wudnt be compatible. Plus our device is fully supported.

It's not that I can not boot into recovery...I cannot flash the 4ext recovery, it gets stuck at sending recovery for ages and than I have to unplug the USB and reboot the phone...
Sent from my HTC Incredible S using Tapatalk 2

[RECOVERY] Official ClockworkMod Recovery 6.0.4.7

[UPDATE 8/27/2013:] GS4 GPe (I9505G/jgedlte) is now officially supported by the ClockworkMod team as of version 6.0.3.6. You can use the I9505/jfltexx recovery on both International and Google Play edition variants.
Download at the official page here, scroll down to "Samsung Galaxy S4 (i9505)". Both regular and touch versions are available.
Flash it via Heimdall:
Download the latest version of Heimdall from here and extract the ZIP to a folder on your hard drive (e.g. C:\Heimdall\ )
Download and install Microsoft Visual C++ 2012 redistributables package from here. These are required to have Heimdall work properly.
Download the latest recovery .IMG file for the I9505 from here and save it to the Heimdall folder.
Shut down your phone. This is important! Do not simply "Reboot to Bootloader" from a ROM or via ADB; the phone needs to boot to Download mode from the "off" state. Disconnect the phone from USB, and turn it on by holding Home + Volume Down + Power buttons together. This will start the phone in the Download mode. Connect the phone to your computer via USB.
Run zadig.exe included in the "Drivers" subdirectory of Heimdall installation. From the menu chose Options -> List All Devices. From the USB Device list chose "Samsung USB Composite Device", or "MSM..." - basically the SGS4. Press "Install Driver", click "Yes" to the prompt and if you receive a message about being unable to verify the publisher of the driver click "Install this driver software anyway". Your phone should now be recognized by Heimdall.
Open Windows Command Prompt and navigate to the directory where you extracted Heimdall. Now type in the following command:
Code:
heimdall flash --RECOVERY recovery_file_name_here.img --no-reboot
and press Enter. This will flash the recovery. Disconnect the USB cable, and hold the Power button until the phone vibrates. Now hold Home + Volume Up + Power to boot into ClockworkMod recovery.
Known issue: On CM 10.2 and 11 ROMs sometimes while rebooting, the phone gets stuck on the Google logo for a long time. This seems to be a race condition (likely culprit is recently merged SELinux, but not confirmed.) Sometimes it clears up on its own after waiting for several minutes, but usually a reboot via battery pull (or holding Power for 10 seconds) clears is right up. Alternatively, removing and immediately re-inserting the SD Card will work as well.
[Insert generic CYA here.]
Flash and use at your own risk.
All thanks go to ClockworkMod team and @gweedo767 in particular.

Chahk said:
This is the unofficial beta of the ClockworkMod recovery built specifically for I9505G/jgedlte/S4 GPe, built by @gweedo767.
Flash it via Heimdall:
Download the latest version of Heimdall from here and extract the ZIP to a folder on your hard drive (e.g. C:\Heimdall\ )
Download and install Microsoft Visual C++ 2012 redistributables package from here. These are required to have Heimdall work properly.
Download the attached .IMG file and save it to the Heimdall folder.
Shut down your phone, disconnect it from USB, and turn it on by holding Home + Volume Down + Power buttons together. This will start the phone in the Download mode. Connect the phone to your computer via USB.
Run zadig.exe included in the "Drivers" subdirectory of Heimdall installation. From the menu chose Options -> List All Devices. From the USB Device list chose "Samsung USB Composite Device", or "MSM..." - basically the SGS4. Press "Install Driver", click "Yes" to the prompt and if you receive a message about being unable to verify the publisher of the driver click "Install this driver software anyway". Your phone should now be recognized by Heimdall.
Open Windows Command Prompt and navigate to the directory where you extracted Heimdall. Now type in the following command:
Code:
heimdall flash --RECOVERY beta-recovery-clockwork-6.0.3.5-jgedlte.img --no-reboot
and press Enter. This will flash the recovery. Disconnect the USB cable, and hold the Power button until the phone vibrates. Now hold Home + Volume Up + Power to boot into ClockworkMod recovery.
So far I've tested mounting all partitions, formatting and wiping, backup and restore to both internal storage and external SD Card, flashing ROMs. Everything seems to be working.
[insert generic CYA here.]
Test it at your own risk, and report any issues here or on IRC in #koush at irc.freenode.net
All thanks go to ClockworkMod team and @gweedo767 in particular.
Click to expand...
Click to collapse
Nice! I tried to build a touch recovery one -- it just rebooted constantly when I tried to enter recovery.

tublah said:
Nice! I tried to build a touch recovery one -- it just rebooted constantly when I tried to enter recovery.
Click to expand...
Click to collapse
This one isn't touch enabled. If all goes well, gweedo767 will be releasing this officially some time today.

Thanks Chahk
Sent from my GT-I9505G using Tapatalk 2

Okay fairly new to the Rom scene but what is the difference between TWRP and ClockworkMod? I know that TWRP is touch based is that the only difference? I know in one of the CM10.2 threads they keep telling people to use CWM recovery and not the other ones.
Sorry for the stupid question but I am curious.

ChaoticUnreality said:
Okay fairly new to the Rom scene but what is the difference between TWRP and ClockworkMod? I know that TWRP is touch based is that the only difference? I know in one of the CM10.2 threads they keep telling people to use CWM recovery and not the other ones.
Click to expand...
Click to collapse
Just like custom ROMs, custom recovery images are just different ways to do the same thing. One is not necessarily better than the other, it's just pure personal preference. Other threads are urging people to use official recoveries, as opposed to those modified and built by random forum members. It doesn't necessarily mean CWM only, it just means the official versions will have a better chance of being more stable and having less issues.
FYI, there are touch-enabled versions of CWM also: http://www.clockworkmod.com/rommanager

ODIN-flashable TAR
Here is an ODIN-flashable TAR of this recovery (the beta)
https://www.box.com/s/1026fqbf49sthkd2rfv5

Any idea when this will be released in ROM manager? Iv been using the beta with no issues.
Sent from my GT-I9505G using xda premium

How is clockwork mod compare to TWRP. When I use TWRP it freezes sometime
Google Edition S4

CWM and TWRP both work well. One feature I like that TWRP has that CWM does not is the ability to queue multiple zips for flashing all at once. On the flip side being able to use hardware buttons to navigate in CWM is handy on the rare occasion when the touchscreen is on the fritz.

I booted from this version of CWM via fastboot with the command
fastboot boot beta-recovery-clockwork-6.0.3.5-jgedlte.img
and successfully completed a back-up to internal flash, though I haven't tried restoring from the back-up. I then rebooted the phone, choosing not to have CWM overwrite anything on the phone, in order to keep stock recovery in place.
The only odd thing I've noticed is that the back-up file dates are set to January 6, 1970, with the back-up directory being named
1970-01-06.14.02.54

Latest recovery for I9505 (jfltexx) is now also fully compatible with I9505G/jgedlte. Download it at the official page here.

Chahk said:
Latest recovery for I9505 (jfltexx) is now also fully compatible with I9505G/jgedlte. Download it at the official page here.
Click to expand...
Click to collapse
Sweet! Touch as well?
Sent from my GT-I9505G using xda app-developers app

tublah said:
Sweet! Touch as well?
Click to expand...
Click to collapse
Yep. Both regular and touch-enabled 6.0.3.6 recoveries for I9505 work on I9505G.

Chahk said:
Latest recovery for I9505 (jfltexx) is now also fully compatible with I9505G/jgedlte. Download it at the official page here.
Click to expand...
Click to collapse
Thanks for the heads-up on this. It's working great for me, with one exception. I can't mount or back up to my FAT32-formatted 64GB microSD card. According to what I've found via searching the forums, this is supported, at least for the I9505. Anyone else seeing a similar issue when using 6.0.3.6 with the I9505G?

highvista said:
Thanks for the heads-up on this. It's working great for me, with one exception. I can't mount or back up to my FAT32-formatted 64GB microSD card. According to what I've found via searching the forums, this is supported, at least for the I9505. Anyone else seeing a similar issue when using 6.0.3.6 with the I9505G?
Click to expand...
Click to collapse
For me, it's working fine. I have a Sandisk 64G formatted to FAT32 and did a successful backup. It's not as fast as TWRP but I can live with that.
When dialog fails, it's time for violence.

bleez99 said:
For me, it's working fine. I have a Sandisk 64G formatted to FAT32 and did a successful backup. It's not as fast as TWRP but I can live with that.
Click to expand...
Click to collapse
Thanks for the feedback. I've got it working, as well. I was trying to avoid using Heimdall to flash the recovery to my phone and was doing a fastboot into recovery instead. It looks like you can't backup to external using that process. I used Heimdall to do the flash and now the backup to external works.

I did a fastboot boot recovery-clockwork-touch-6.0.3.6-jfltexx.img and was able to do a backup and a create image zip. I could not do this to the external SD card. Got an error on the bottom No file_contexts. I'm ok with that at least I got backup up.
My question is where are these backups stored? In CWM going to the "advance restore" option I see that it was created /sdcard/clockworkmod/backup "1970 etc etc", however using ES file Explorer and Total Commander there are only 3 files in the /sdcard/clockworkdmod/backup folder. .nomedia 0.00 B, .recovery_version 40.00 B and .settings 285 B.
I've also used root browser can can't seem to find where these backups are stored.
Where are these files store so I can copy them to my computer for safe keeping?
Thanks.
Ok, found 'em.... /data/media/clockworkmod directory contains all the info!

ThugEsquire said:
Here is an ODIN-flashable TAR of this recovery (the beta)
https://www.box.com/s/1026fqbf49sthkd2rfv5
Click to expand...
Click to collapse
By any chance do u have the new cmw Odin flashable tar file
Sent from my GT-I9505G using xda app-developers app

toanau said:
By any chance do u have the new cmw Odin flashable tar file
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
6.0.3.6 is the latest and there is an Odin tar in this thread. Is there a newer one floating around I didn't see anything updated from the website?
Update I think that image was for 6.0.3.5 if so let me know I can make you a .tar file
Sent from my GT-I9505G using Tapatalk 2

[GUIDE] How to update to Android M-Preview-2 from V1 without loosing your data

If you are in M-preview-1 and don't want to lose your dat/apps you can follow this guide, after that, you'll havw M-preview-2 installed and a rooted device.
Firstly, you need to have a pc with adb working. There are several wyas to achive that, but I presume that if you are already in M preview V1, you have it.
Then, you need to have an unlocked bootloader, again I assume that you have it.
======Skip this is you have adb and unlocker bootloader===========
In any case, in linux there is a very trivial way to get both things (probably in windows and mac is more or less the same):
In a terminal:
sudo apt-get install android-tools*
Then plug your N5 to your computer with a usb cable (depuration mode enable), check that everything is working fine:
sudo adb devices
Then;
sudo adb reboot bootloader
sudo fastboot oem unlock
Then reboot
========================================================
Again, if you are not coming from M-preview-1 I do not recommend this method
1. Download M-preview-2 from this page.
2. Download twrp from here.
3. Create a folder, move twrp to that folder and extract M-preview-2 to the same folder (no sudir, all the files in the same folder), extract again image-hammerhead-MPZ79M.zip in the same folder.
4. Download Despair kernel in your device.
5. Download SuperSU beta 2.49 in your device.
Now, we are ready to flash everything:
6. Open a terminal and cd to the folder where you keep everything from previous steps.
7. Plug your device using a usb cable
8. Type the following commands in the terminal (if you are not in Linux, use the same commands but without "sudo"):
sudo device (just to check that adb ·see your device)
sudo adb reboot bootloader
sudo fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
sudo fastboot flash boot boot.img
sudo fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
sudo fastboot flash system system.img (this step takes a while)
sudo fastboot flash cache cache.img
sudo fastboot flash recovery twrp-2.8.7.1-hammerhead.img
9. Reboot in recovery (just using the vol up or down and the on buttom).
10. Flash Despair kernel
11. Flash SuperSU
12 Wipe Dalvik and cahe (just in case)
13. Reboot

Flashing over preview 1 won't bring additional issues?

migueldbr said:
Flashing over preview 1 won't bring additional issues?
Click to expand...
Click to collapse
Of course II'm still testing, but it seems that there is not new bugs (yet).

All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.

does your guys system app crash if you open data usage (set language to something except english) ?

tugler said:
does your guys system app crash if you open data usage (set language to something except english) ?
Click to expand...
Click to collapse
Yes

I just did a clean flash via fastboot manually. Booting now. I ain't got time for issues.

Is there a reason the OP links to TWRP 2.8.6.1 instead of the latest version (2.8.7.1)?

Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?

6spdsc4 said:
Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?
Click to expand...
Click to collapse
I'm still transferring my nandroid backup to my PC and haven't tried yet, but it's possible that the kernel won't flash on preview 2 because it's not yet updated for preview 2. As @TonyHoyle said, it's probably not a great idea to use one until they've specifically been updated for preview 2.

TonyHoyle said:
All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.
Click to expand...
Click to collapse
can u explain more detailed?

Flashable zip for multirom
flashable zip to use with multirom, please ?

As TonyHole suggested, just remove the -w; basically this will do: (you can do below on a command line as long as you are in the extracted TGZ file and in the hammerhead-MPZ79M folder/directory)
fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
fastboot reboot-bootloader
fastboot update image-hammerhead-MPZ79M.zip
This works for me no issues as data is left intact but everything else is updated ; suggesting NOT to do this from an Android L to Android M Preview 2 and do a proper wipe
This will rebuild the ART app optimize on reboot
OP: Next time make a guide for doing STOCK update FIRST ; save the kernel and root for a SEPERATE post or a seperate section in the post

Hellscore kernel works great
Clean flash
I don't understand why any one would do a dirty dirty install with a preview no less
Sent from my Nexus 5 xda-dev app

The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.

NPS_CA said:
The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.
Click to expand...
Click to collapse
Do you have a link?
Sent from my Nexus 5

Is there zip file available
Sent from my Nexus 5 using XDA Premium 4 mobile app

thesebastian said:
Do you have a link?
Sent from my Nexus 5
Click to expand...
Click to collapse
Is this a real question?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Is this a real question?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5

thesebastian said:
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5
Click to expand...
Click to collapse
Surely if you go about phone. System update. Then you'll either have it or not if it's been pushed out to your device?
Sent from my Nexus 5 using Tapatalk

BLU R2 LTE??? unlock/rootable?

I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?

DaGoo_Balls said:
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
Click to expand...
Click to collapse
It apparently is.
https://forum.xda-developers.com/r1-hd/development/unofficial-lineageos-14-1-t3689435/post75020813

Thanks. Looks like I have plans for NYE

I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.

somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
You would be better off to patch my boot image and fastboot boot it.
Then backup your boot image, patch it with magisk, and flash that one back to the device.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/blur2-boot.img"
This keeps things clean, just incase you are using a boot image that is different from your own device. Plus you have a "stock" boot image backup if you ever need it.
Not a bad idea to grab recovery also.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/blur2-recovery.img"
Sent from my ford using XDA Labs
BLU R2 LTE files. Link

somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!

bobsmithy said:
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
Click to expand...
Click to collapse
The size of memory "shouldn't" matter.

Braunish said:
Hi there, am trying to root this phone also. Stumbled upon your thread and had a question. If I take the 3 image files (recovery, boot, system) that are included at mediafire site (that you included in your post) and replace the same 3 image files in stock rom, would that work to root the phone? Thank you for any help, I've tried kingoroot, kingroot, and framaroot to no avail.
Click to expand...
Click to collapse
Read back few post on this thread. They discuss successful root method.
Basically unlock bootloader and use majisk manager to patch boot.img and flash patched image with fastboot.

Root R2 Plus w/ BLU R0190WW V7.0.04.01 GENERIC 11-02-2018
DaGoo_Balls said:
Thanks. Looks like I have plans for NYE
Click to expand...
Click to collapse
Hi there, I recently got a Blu R2 Plus and am aiming to root. I used the boot-sign.img that came with that ROM version in title (9447 KB) when patching with Majisk Manager and came up with a patched file of 9.57 MB size. Is there a way to test this ROM, or can you verify that is the same sizes you dealt with when you went through this process. Thank you for any information. It took me a while and a factory reset before I could get majisk manager installed to patch the correct boot-sign.img file.

Hi There copy img file to where on phone
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse

Braunish said:
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
Click to expand...
Click to collapse
If I understand correctly.
You have adb and fastboot installed.
You have a boot image that works for your device and tested it by using fastboot to boot it. let's call it working_boot.img
You have MagiskManager installed.
The next steps:
adb push working_boot.img /sdcard Doesn't really matter where you put it.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on working_boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
adb pull /sdcard/magiskmanager/patched_boot.img
Reboot to bootloader and fastboot boot patched_boot.img
Open MagiskManager. You should see that Magisk is installed and active.
Now that you have temporary root, you have some options.
The easiest way would be to open MagiskManager and use the Direct install option. This will pull, patch and install a patched boot.img to the device.
Unless the the original working_boot.img used is the correct one for your device.
The safer way, pull the stock_boot.img I normally grab recovery also from the device.
For BLU R2 LTE
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/BLUR2-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/BLUR2-recovery.img"
adb pull /sdcard/BLUR2-boot.img
adb pull /sdcard/BLUR2-recovery.img
Then patch it and fastboot boot it to make sure it works.
After that you can either use MagiskManager Direct install or fastboot to flash the new patched_boot.img.

Bricked my device, used SP Flash Tool to update - Now no OTA?
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx

Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.

8milerd said:
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
Click to expand...
Click to collapse
These links do not work? Link Direct download links are from MediaFire. Click on the name of the file.
I try to use direct download links from MediaFire. There servers can normally handle it. You do not have to navigate ads and redirects with direct download links.
---------- Post added at 04:58 AM ---------- Previous post was at 04:35 AM ----------
HornyOryx said:
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Click to expand...
Click to collapse
A while back , I had to do a factory reset to get an OTA. Then I had to un-root it to get the OTA to flash.