Develop Bugs

Manually update 4.2.1(JOP40D) on your Galaxy Nexus running official 4.2(JOP40C)

I am on windows 8 and was not successful in sideloading until i restarted my machine ... Not sure why , but it was getting detected in adb but just didnt want to push the update file after " adb sideload "
Happy updating to 4.2.1
I always found issues with bluetooth headset on 4.2 , hope this update has fixed it .
Step 1: Download the Android 4.2.1 OTA Update for your Galaxy Nexus Takju from here.
Step 2: Download the Fastboot Package to your PC.
Step 3: Unzip the downloaded fastboot.zip file into C:\ (C drive in my computer) to generate the fastboot folder that contains four files. Then copy the downloaded update zip file to the fastboot folder.
Step 4: Turn off your Galaxy Nexus and reboot your phone into recovery mode, Reboot your phone into recovery mode, to do so reboot phone by holding down volume up, volume down and power buttons, you’ll enter in fastboot mode, there use volume keys to navigate and power button to select. You need to select recovery option to enter in recovery mode.
Step 5: Here hold down the power button first, then press volume up button, it will open up the recovery menu, then select “apply update from adb”.
Step 6: Connect the phone to PC using a USB cable.
Step 7: Open up the command prompt that you can find at start menu>programs>accessories. Then using command prompt, navigate to the fastboot folder, if you’re using Windows 7 or above, you can open the command prompt directly from the folder, to do so open the folder, there press right click on mouse while holding down shift button on keyboard, then select “open command prompt here”. Or enter the below command on command prompt to navigate to fastboot folder.
cd c:\ fastboot
Step 8: Enter following command, it will deliver your Galaxy Nexus ID number, if it delivers, your phone is connected to PC properly. Otherwise make sure device drivers are installed properly.
adb devices
Step 9: Enter the following command to install the downloaded Android 4.2.1 OTA update .zip file, it will show progress bar on your phone, after that it will start the installation:
adb sideload 1d62212ba0a9.signed-takju-JOP40D-from-JOP40C.1d62212b.zip
Step 10: Once the installation is done, on your phone select “reboot system now”.
That’s it, if you faced any issue in above guide, do comment below.

Will this work for Fido GNex? Or do I need a different ota update.zip?

[Q] Ouya will not boot anymore (blackscreen)

While i was trying to do adb in cmd in windows and had more than one device and emulator error and i tryed closing the process and turning off system to fix error.Then when i booted up system it gives black screen i tryed several things.

This might unbrick if you can do it
blessy said:
While i was trying to do adb in cmd in windows and had more than one device and emulator error and i tryed closing the process and turning off system to fix error.Then when i booted up system it gives black screen i tryed several things.
Click to expand...
Click to collapse
Are you able to get the device into fastboot if you have adb showing working in the windows device manager if your on windows when you switch it on and it's at the black screen?
If so go to android sdk hang over the platform-tools folder within and right click it and select open a command window here,now get hold of ouyatoolbox 1.0.0.0 or another version of this tool,now go back to command and then type adb reboot bootloader and hit enter,check to see if you have fastboot pop up in windows device manager now, and if it shows yellow the best i can say is get it working asap. Then go to ouyatoolbox and click install CWM Recovery it should bring you to the recovery,you then go to install from zip then to install zip via adb option and download an ota firmware file from the net on your pc one that matches the firmware you had before on your ouya, then drop he download into android sdk/ platform-tools folder as a zip file as it came downloaded,go to the open command window you opened from platform-tools and type in adb sideload (name of the ota firmware zip file ) hit enter,this should unbrick it by installing the ouya system firmware from the file,if not then go back to the ouya recovery by turning off the ouya and press power then hold in alt+printscreen & every 2 seconds press i until clockworkmod recovery appears or an ! press home button then,if your in adroid system recovery 3e try to adb sideload the firmware,if not working it means clockworkmod didn't install and you must try again because built in recovery is not functioning with sideload firmware option,so if your in the clockworkmod menu just click these factory data reset then erase cache then go to advanced and click erase then click erase dalvik cache then click install from zip then go to install zip via adb option click that and try type adb sideload (name of the ota zip file)in command window you opened from platform-tools and hit enter,this should apply the update and unbrick the console.
If not then there is something more wrong than just the firmware at a guess,sorry if the guide is a bit poor but it's the best i can do.

Installing Clockwork Recovery

Hello
I am following the following tutorial below to install the clockworkmod recovery but when I enter the cmd fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img. The cmd prompt displays the message "waiting for device" but does not do anything. Am I doing anything wrong?
1. Download and place the package file onto your Desktop.
2. Extract files from the package to your Desktop.
3. Connect your smartphone to the PC using the USB cable.
4. Double-click the Start Here.bat file to open the Command Prompt Window.
5. Enter the following command into the Command Prompt Window:
adb reboot bootloader
6. Your smartphone should reboot into the Fastboot mode.
7. Now, enter the following command into the same Command Prompt Window:
fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img
8. After the recovery has been installed on your smartphone, issue the following command:
fastboot reboot
9. Your smartphone should reboot.
Thank You

mfredy said:
Hello
I am following the following tutorial below to install the clockworkmod recovery but when I enter the cmd fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img. The cmd prompt displays the message "waiting for device" but does not do anything. Am I doing anything wrong?
1. Download and place the package file onto your Desktop.
2. Extract files from the package to your Desktop.
3. Connect your smartphone to the PC using the USB cable.
4. Double-click the Start Here.bat file to open the Command Prompt Window.
5. Enter the following command into the Command Prompt Window:
adb reboot bootloader
6. Your smartphone should reboot into the Fastboot mode.
7. Now, enter the following command into the same Command Prompt Window:
fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img
8. After the recovery has been installed on your smartphone, issue the following command:
fastboot reboot
9. Your smartphone should reboot.
Thank You
Click to expand...
Click to collapse
Are your drivers installed already?

bananagranola said:
Are your drivers installed already?
Click to expand...
Click to collapse
Yh, I have installed all the latest driversss

mfredy said:
Yh, I have installed all the latest driversss
Click to expand...
Click to collapse
Is your phone in debug mode?

bananagranola said:
Is your phone in debug mode?
Click to expand...
Click to collapse
yupppppppppppp

mfredy said:
yupppppppppppp
Click to expand...
Click to collapse
No idea then. Post the entire log.

mfredy said:
yupppppppppppp
Click to expand...
Click to collapse
Were your drivers installed with the phone unplugged?

-Check your data-sync cable,It should not only allow your device to charge but also data-sync.( Try with another data-sync cable)
-As you stated drivers are installed.Then when you're on bootloader,It should show HBOOT-USB. If that shows than try doing same thing again.
Or else follow simple steps below:
-Copy CWM recovery.img into fastboot files.
-Unplug your device if connected to computer.
-Manually power off your device.
-Press Volume down + Power button,It will redirect into hboot.
-Select Bootloader by clicking on power button,It will change color of HBOOT from Blue to Red.
-Next thing you'll notice that it stated as HBOOT USB.
-Put your phone on side and do same commands fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img
-Fastboot reboot.
Once process been done. Unplug it and boot device normally. And to check whether there's a recovery.img installed or not,Just power off your device and put on charge. In CWM it will redirect your into recovery mode while device is switched off.

4EXT Recovery Touch
Try 4EXT Recovery Update , install app , download 4EXT Recovery . Done

go back to AW 1.5

Hi,
as now - officialy - I'll never get a newer version of AW which maybe increases the usability of the system, I want to try to go back to 1.5
I found this thread: https://forum.xda-developers.com/hu...aw-1-5-build-m9e42c-to-downgrade-2-0-t3607859
But I'm not sure about all the steps and I want to make sure, I don't brick my watch.
So here's what I tried to read out of the post:
1. Download the file from this thread (sturgeon_M9E42C_TWRP_Flashable.zip) and negalite-HW-TWRP-3.0.3-v1.5.img
2. install adb (I have minimal adb and fastboot installed)
3. copy files from 1 to directory of adb
4. open adb
5. adb connect *IP-adress*
6. adb push sturgeon_M9E42C_TWRP_Flashable.zip /sdcard/
7. adb reboot bootloader
8. fastboot boot negalite-HW-TWRP-3.0.3-v1.5.img (where do I execute this step?)
9. on watch select "install zip" (where do I find this?)
10. select /sdcard/sturgeon_M9E42C_TWRP_Flashable.zip
Is this correct?

[root] redmi 4x root

Firstly this is my first helpful post so be gentle.
How to root the Redmi 4x
First off I am not accountable if your fry your device or shut down the power grid etc.
Alright. It took me some research and trial and error but I found the CORRECT way to root the Redmi 4x.
Needed files:
Lasted version of the magisk zip. DO NOT USE ANY VERSION OF SUPER SU. IT CAUSES BOOTLOOP.
TWRP for Redmi 4x
Lazy patcher.
Adb and fastboot files.
Step one:
Ensure your bootloader is unlocked. If not search XDA for a thread there are multiple threads showing you how to do it. Once that's done let's move on.
Step 2:
Alright let's get going with flashing TWRP first.
You need to enable developer options and enable USB debugging on your Redmi. To do that go to settings>about devices>scroll down>continually tap on MIUI version and a toast notification will tell you that you are now a developer>go to developer option under the more options tab and enable USB debugging.
Step 3:
Now that we've got USB debugging we can connect to Adb. Firstly download all aforementioned files and place them in the same folder as your Adb installation for ease of access. Now open up a command prompt in that folder by either typing "cmd" into the address bar or shift+right click and select open command window here. Now you need to connect your phone via USB to your computer and ensure it is connected by entering "adb devices" into the command window.
Step 4: commands
Here are the commands you will need to enter. I recommend making a backup of everything first.
Enter these commands
adb reboot bootloader
Fastboot flash recovery (put TWRPS full file name here including the .zip)
Wait for it to finish.
Now DO NOT BOOT TO SYSTEM.
Enter in fastboot reboot and hold volume up to enter recovery. If you boot to system it will remove twrp and you will have to reflash it.
Once in Twrp check the box to allow modifications and slide right.
Go to advanced and the ADB sideboard.
Now flashing magisk and lazy patcher.
Reconnect your phone to the computer and leave Twrp on sideload mode.
Enter this command
adb sideload (lazy patchers full file name here)
Now I made sure my phone still booted to system after this because every time I flashed SuperSU it would boot loop.
Once your back in sideload mode let's flash magisk.
adb sideload (magisks full file name here).
Once it's done select reboot to system from Twrp and enjoy your root!!
Again I say do not use any flashable root other than magisk. I don't know if I had a specific problem but every single one I tried resulted in bootloop.