[Q] rooting and recovery mode - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi,
I followed the instructions on http://forum.xda-developers.com/showthread.php?t=2271909
Now every time I get into the recovery mode and even if I click reboot system is shows the orange kindle sign and then the blue and back to recovery.
I want to copy the zip files and flash a rom. How can I do that?

chenhajaj said:
Hi,
I followed the instructions on http://forum.xda-developers.com/showthread.php?t=2271909
Now every time I get into the recovery mode and evtold f I click reboot system is shows the orange kindle sign and then the blue and back to recovery.
I want to copy the zip files and flash a rom. How can I do that?
Click to expand...
Click to collapse
To "flash a rom" make sure you know where the file is. I always put it at the root if the sdcard. (Or what my kindle calls "sdcard") At the root of sdcard means not in any file or folder. DO NOT UNZIP whatever it you are trying to flash. Now, from recovery, select install zip. Or install or something similar depending on what recovery you are using. (Are you using team win recovery project aka twrp or clockwork mod aka cwm?) Next choose zip from sdcard, select the zip you want to flash, (it sounds like you don't have an operating system so I think you would flash one.) Select yes is should be flashing some logs on screen now. When done go back to your recovery home. At this point I always go to wipe, then wipe cache and dalvik cache. When done just reboot, system. If the problem persists I would think you have a problem with your os.
Good luck!

JeremySwagS said:
To "flash a rom" make sure you know where the file is. I always put it at the root if the sdcard. (Or what my kindle calls "sdcard") At the root of sdcard means not in any file or folder. DO NOT UNZIP whatever it you are trying to flash. Now, from recovery, select install zip. Or install or something similar depending on what recovery you are using. (Are you using team win recovery project aka twrp or clockwork mod aka cwm?) Next choose zip from sdcard, select the zip you want to flash, (it sounds like you don't have an operating system so I think you would flash one.) Select yes is should be flashing some logs on screen now. When done go back to your recovery home. At this point I always go to wipe, then wipe cache and dalvik cache. When done just reboot, system. If the problem persists I would think you have a problem with your os.
Good luck!
Click to expand...
Click to collapse
My problem is that I can't copy the ROM to the kindle right now because when I plug it I don't see it in my computer.
I saw it before I had the trouble of the constant recovery mode.

chenhajaj said:
My problem is that I can't copy the ROM to the kindle right now because when I plug it I don't see it in my computer.
I saw it before I had the trouble of the constant recovery mode.
Click to expand...
Click to collapse
So you have no os installed on your fire now? And no rom downloaded on it either?
Also, do you have a "fastboot" cable?
---------- Post added at 07:06 AM ---------- Previous post was at 06:45 AM ----------
http://forum.xda-developers.com/showthread.php?t=1893838

JeremySwagS said:
So you have no os installed on your fire now? And no rom downloaded on it either?
Also, do you have a "fastboot" cable?
---------- Post added at 07:06 AM ---------- Previous post was at 06:45 AM ----------
http://forum.xda-developers.com/showthread.php?t=1893838
Click to expand...
Click to collapse
I guess that I don't have either.
I only have the regular micro USB to USB

chenhajaj said:
I guess that I don't have either.
I only have the regular micro USB to USB
Click to expand...
Click to collapse
You shouldn't need fastboot cable. In your recovery's main menu, there should be an "Advanced" button or something to that effect. After clicking it, there should be a button called "Sideload" or whatever. It let's you use the "adb sideload" command to push files to your device.
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<

Ph0enix_216 said:
You shouldn't need fastboot cable. In your recovery's main menu, there should be an "Advanced" button or something to that effect. After clicking it, there should be a button called "Sideload" or whatever. It let's you use the "adb sideload" command to push files to your device.
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
Can you please direct me on how I push the files using the adb sideload?
lets say that the rom files are a.zip b.zip and c.zip

Here just follow the tutorial I just put up. http://forum.xda-developers.com/showthread.php?t=2459498
Note: my tutorial doesn't use side loading, it just pushes it, so don't put your kindle into sideload mode if you follow it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Here just follow the tutorial I just put up. http://forum.xda-developers.com/showthread.php?t=2459498
Note: my tutorial doesn't use side loading, it just pushes it, so don't put your kindle into sideload mode if you follow it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
tnx, you're the best

Related

Complete Installation Guide for JB or ICS on a Nexus One (Updated 12/29/12)

I initially looked for a complete update guide on here and eventually found all the information I needed, but it was in multiple places and sometimes hard to find. After getting everything installed on my N1 I thought I would write a guide for other noobs like me that want to try out ICS or JB but would like a step-by-step guide. I hope that it is helpful. SpazeDog ROMs (both ICS and JB) are working wonderfully on my N1 - its a very nice update from CM7 with only minor issues so far.
Note: this was initially written specifically for SpazeDog roms, but as they have not been updated in a while I have provided links to other popular roms as well. If you would like to try a different ICS or JB rom this guide should work, just substitute with the appropriate rom and depending on the one you choose, you may also need to install Google apps.
If you looking at this guide and don't know the basics yet, check out the Newbie Friendly thread first.
Links to popular roms that will work using this guide:
Evervolv JB 4.2
Evervolv JB 4.1
CM 10, JB 4.1.2 by vijendrahs
CM 10, JB 4.2.1 by vijendrahs
Spazedog ICS/JB
Disclaimer: This guide involves making changes to your phone that potentially could brick your phone leaving it unusable. I am not liable for any changes you make or problems you may have with your phone. You should at least be familiar with entering commands using command prompt. This procedure will erase ALL the data on your phone. Make sure you have a backup of everything. A nandroid backup is highly recommended. Proceed at your own risk.
Before we get started make sure you have the following: a rooted Nexus One, a USB cable to attach your phone to a computer, and the Android SDK. If you are just now installing the Android SDK, open the SDK manager and make sure to install the "Tools" and in "Extras" the "Google USB Driver" are checked off and download them. Alternatively, you just download ADB and Fastboot (search this forum or google). If you have a Mac see this thread to get started with ADB and Fastboot.
If you Nexus One is NOT already rooted, then follow this guide from Cyanogenmod to root your phone. If you plan to use the adb commands below (they are optional) make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Step 1 - Download everything you will need:
4EXTRecovery Updater - the first link will download the .apk to your computer or phone.
BlackRose - go down to bottom of the first post to "Attached Files" and download the latest BlackRose zip file. If you don't want to do it yourself, check out this thread to flash a pre-made partition scheme. Often the developers (Evervolv) will also have a partition schemes that you can flash via Fastboot from your PC as well.
Your rom of choice - go to the downloads section and choose which rom you would like to try. Download the zip installation file.
Since you will be decreasing the size of your partition that apps can be stored on consider something like Mounts2SD or AD2SDX to move apps to your SD card.
Step 2 - Install and use 4EXTRecovery Updater on your phone:
The easiest thing to do is go to the 4ext link above, download and install it, directly from your nexus one. You can also install it by copying the APK file to your SD card, then using a file manager to find it and install it or you can use command prompt by opening command prompt, cd to the location of the Android SDK tools, and then type in the following command (replacing "path" with the path to where the APK is located on your computer):
Code:
adb install /path/4EXTRecoveryUpdater.apk
After you have installed 4ext open the 4EXT Recovery Updater. Tap "Settings" → "Allow" superuser request → "Yes" to connect to 4ext to get new data. Now select "Online install/upgrade" → "Yes" assuming it detects your nexus one correctly → select and install the latest 4ext recovery (at the top of the list).
After 4ext has installed, it will have placed a recovery image on your SD card - find it (its called recover.img) and it should be located in SD/Download/4EXT_Recovery_Touch/ folder. Copy this to your computer in case something goes wrong later and you need to re-flash the recovery image!
After installation of the 4ext recovery turn off your phone and boot into recovery by turning off your phone, turning it on again while holding the trackball down. This will boot into the bootloader, then press the power button once, use Volume Down to select "recovery" and press the trackball to select. Alternatively you can use the command prompt:
Code:
adb reboot recovery
Your phone should now boot into the 4ext recovery menu. Before moving on make sure you have any important stuff backed up because you are about to erase your entire SD card! Select "tools" →“partition sd card” → “remove all partitions and start from scratch.” Then for the 1st partition select “1024″ for a 1GB partition (this will be where ICS will be able to put your applications & data). Select "skip" for the 2nd partition and for the swap partition. Finally select the system “ext4″.
Step 3 - Copy the Evervolv, SpazeDog, or whatever zip installation file you have chosen to your phone's SD card
Download the ICS or JB zip file above and copy it to the root of your newly formatted SD card.
Step 4 - Installing and using BlackRose to resize the system partition:
Download the BlackRose application and install it on your computer. (Alternatively people have made flash-able partition schemes that you can just flash from your PC - usually links and instructions are provided in the installation rom's thread, Evervolv's here. If you do have access to a computer you can check out this thread).
Make sure your nexus one is attached via USB to your computer.
Open the BlackRose application - it will install and reboot your phone. Then follow along as shown in this video to resize your partitions for a JB ROM.
If you plan to install the ICS rom then use the video above as a guide but use the numbers (sizes) for the different partitions as indicated below.
After BlackRose has installed you will need to restart the application. After it has started up and recognized your device select "apply stock/custom blackrose" by typing in 1 and enter.
Then select "custom blackrose" by typing in 2.
Then type "resize" when prompted.
Now you will need to change the sizes of the system partition to 220 for ICS or 260 for JB.
Change the cache size to 8.
Finally name the new system partition, either "ICS" or "JB" depending on what you plan to install.
Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip.
Step 5 - Install JB or ICS:
Now turn your phone off and boot into recovery as you did in step 2.
4ext will load. Select "wipe/format" → "format all partitions (except sdcard)" and then also "wipe data/factory reset."
Now go back and select "install from sdcard" → "choose zip from sdcard" → and then select the ICS or JB zip you copied to the SD card in step 3.
Now either the ICS/JB installer will load or it will just install in one step. Just follow the prompts to install and enjoy.
Depending on the ROM you chose you may need to install Google apps (see the specific ROM thread for details) and will also likely want to flash an apps-to-SD script as mentioned above so you do not run out of space.
This method worked perfectly for me, hopefully it will work well for you as well. Enjoy.
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
diegolm said:
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
Click to expand...
Click to collapse
I am sorry to hear that. Can you boot into recovery or is that broken as well? If you can boot into ext recovery try selecting "wipe/restore" → "wipe data/factory reset" and then try to install BCM again. I probably should have added that above, I will do that now.
If your recovery is broken but you can get into the bootloader (holding down trackball while starting up), you should be ok. You will probably need to flash Amon_Ra's Recovery using Hboot as was described in the guide from cyanogenmod link above. If there is a way to directly hboot flash 4ext recovery I don't know how to do it. Then you can try installing BCM again from the Amon_Ra's recovery and re-install 4ext after you get everything working.
I tried the Texasice ROM and it worked, but I didn't like it! Later I tried again BCM and It worked! I dont know, maybe I did something wrong... Anyway thanks again for the guide!!
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
intel415 said:
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I am not sure which part you are referring to, but, yes, a few of the above instructions could be replaced with fastboot commands.
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
intel415 said:
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I used the adb commands above because you can use adb to reboot directly into recovery (fastboot you can only reboot normally or into the bootloader) and you can also use adb to directly install apk files - fastboot cannot do those two things - it is more for flashing images (recovery, roms, etc). In order for adb to work make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Note that adb commands are not required - you can reboot into recovery and install the 4ext manually.
It won't let me post a link right now, but just google "adb commands" to find a list of all the commands you can use.
Hope that helps.
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
intel415 said:
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, its not bad - glad you got it working! ICS has been smoother than cm 7.2 for me as well.
Blackrose didn't ask me about userdata - it just assumed that automatically after putting in 220 system and 16 cache... I'll make note of that in the guide so its clearer. Thanks.
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Look for "recovery.img"
bobbyphoenix said:
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Click to expand...
Click to collapse
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
c2med said:
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
Click to expand...
Click to collapse
OK I'm stuck on what the path name is suppose to be. I tried it every way I can think of. Can you take a look at my screen shot, and tell me where I'm going wrong? The recovery image is on my desktop, so I'm not sure what exactly I should be replacing "path" with. I tried it from the link, and how you have it in your note. You don't have the "/to/" after path as in the CM link.
Well I tried a couple more times, and I can get it to seemingly do it, but it just hangs on this: (see screen shot) I get no error, and if I try to enter recovery on the phone I still get the reboot to the android and triangle with the ! in it.
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
n1newbie said:
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
tommert38 said:
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
Click to expand...
Click to collapse
WOW Thank you both. I spent literally hours yesterday trying to get it to work. Tried your suggestions, and in five minutes it was up and running!
---------- Post added at 12:31 PM ---------- Previous post was at 11:33 AM ----------
I may have spoke too soon. I followed the instructions to the end. Installed the ROM, and rebooted, but now after the X I get the Spazdog splash screen with the big Z in the middle and green dots moving, but it stays there forever. I waited 20 minutes one time. Tried reflashing, but I get the same thing.
---------- Post added at 01:17 PM ---------- Previous post was at 12:31 PM ----------
Just giving an update on progress (in case someone else is in my boat too) Flashed back to stock GB. Reinstalled recovery, and reflashed Spaz. Got past the X, and the splash screen, but now it's stuck on the Android logo that looks like the night rider beam that goes across the word. Been there now for about 10 minutes.
You do have Blackrose, right?
Yep. Installed everything according to OP. I think it may be the partition sizes as I think flashing back to GB messed with them. It says 220 and 10, but after checking some threads, it looks like there is one missing (userdata). I tried flashing a custom GB from here http://forum.xda-developers.com/showthread.php?t=1214543&page=98 and I was able to install everything. Got it up and running, so I'm going to start over for ICS, or do you think I can flash one of these for ICS http://forum.xda-developers.com/showthread.php?t=1637166 , and then just flash the ROM after?
220/10 means that you have 220MB for system and 10MB for cache, everything that's left will be userdata, so it doesn't ask (total is ~436MB, so userdata will be ~206MB in that case).
In HBOOT you can check how large your partitions are, or you could use the FreeSpace app for example. Always make sure your system partition is large enough before flashing a ROM.

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

[RECOVERY]ClockworkMod Touch v6.0.3.4

USB OTG Info:
USB OTG will show up as external_sd. If external_sd is not mounting, reboot recovery. You must enter recovery with usb already inserted.
Installation:
Unlock bootloader at http://www.htcdev.com/bootloader/
Uncheck fastboot in the rom in power options
Turn phone completely off
Boot into HBOOT>Fastboot
Inside of fastboot. Erase cache. Use command "fastboot erase cache"
Use command "fastboot flash recovery recovery.img"
Root:
To gain root on stock rom. Flash recovery in fastboot then flash this inside of recovery. There are two root programs. Superuser and SuperSU. Both are listed.
Superuser - http://download.clockworkmod.com/superuser/superuser.zip
OR
SuperSU - http://download.chainfire.eu/supersu
Downloads:
http://goo.im/devs/Flyhalf205/MYSTUL/Recovery//recovery-clockwork-6.0.3.4-mystul.img
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Touch version is a test. Not sure if it will work properly but the classic version should be fully working. Let me know of any problems.
Flyhalf205 said:
Touch version is a test. Not sure if it will work properly but the classic version should be fully working. Let me know of any problems.
Click to expand...
Click to collapse
At least on my device, the touch recovery does *not* work, but the classic recovery *does*. Cheers!
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
One more thing to note: mounting the internal storage/sdcard does not seem to work either.
nuclear_eclipse said:
At least on my device, the touch recovery does *not* work, but the classic recovery *does*. Cheers!
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
One more thing to note: mounting the internal storage/sdcard does not seem to work either.
Click to expand...
Click to collapse
I'll take down the Touch and get a test build out....Will never work mounting the storage The internal sdcard is actually located in /data/media. It can not be mounted as storage. The only way is to use ADB commands.
Flyhalf205 said:
I'll take down the Touch and get a test build out....Will never work mounting the storage
Click to expand...
Click to collapse
That's quite a shame then. Flashing from /sdcard is by far easier to manage than using adb sideload.... :'(
nuclear_eclipse said:
That's quite a shame then. Flashing from /sdcard is by far easier to manage than using adb sideload.... :'(
Click to expand...
Click to collapse
Adb sideload or adb push to the sdcard.
Sent from my ADR6425LVW using Tapatalk 2
Flyhalf205 said:
Adb sideload or adb push to the sdcard.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I tried adb pushing to /sdcard while running the recovery image, but it still refused to flash from there because it would fail trying to mount /sdcard. adb sideload was the only method that actually worked. Unless I'm missing something...
nuclear_eclipse said:
I tried adb pushing to /sdcard while running the recovery image, but it still refused to flash from there because it would fail trying to mount /sdcard. adb sideload was the only method that actually worked. Unless I'm missing something...
Click to expand...
Click to collapse
Not sure. Newer HTC phones are strange in the recovery. You mind testing TWRP?
Sent from my ADR6425LVW using Tapatalk 2
Sure, I'll test it shortly.
nuclear_eclipse said:
Sure, I'll test it shortly.
Click to expand...
Click to collapse
So, were you able to successfully root the First as well? Or was that back-and-forth about adb loading/side-loading about root? I tried re-reading the posts, but my newb-translator is on the fritz.
lordlittlebrooks said:
So, were you able to successfully root the First as well? Or was that back-and-forth about adb loading/side-loading about root? I tried re-reading the posts, but my newb-translator is on the fritz.
Click to expand...
Click to collapse
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
nuclear_eclipse said:
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
Click to expand...
Click to collapse
Thanks for spelling that out. Beers headed for you and flyhalf. Can't wait to get home and root my First!
lordlittlebrooks said:
Thanks for spelling that out. Beers headed for you and flyhalf. Can't wait to get home and root my First!
Click to expand...
Click to collapse
Thanks Glad everything is working out. Uploading a new TWRP build if anyone likes that better.
I've added a few extra features into the classic version of CWM. Power off option in the menu and reboot to bootloader in advance menu. Regular CWM doesn't have those
nuclear_eclipse said:
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
Click to expand...
Click to collapse
Is it not possible to just put zip on sdcard and choose install zip from sdcard?
Sent from my HTC first
phositadc said:
Is it not possible to just put zip on sdcard and choose install zip from sdcard?
Sent from my HTC first
Click to expand...
Click to collapse
Since the recovery currently can't mount the sdcard partition, any attempt to flash from sdcard fails. The only method that works afaik is the option to flash via sideload, which requires the phone to be attached to a PC running adb. I'm not certain, but it sounds like this would also prevent the CyanogenMod built-in update mechanism to fail as well...
nuclear_eclipse said:
Since the recovery currently can't mount the sdcard partition, any attempt to flash from sdcard fails. The only method that works afaik is the option to flash via sideload, which requires the phone to be attached to a PC running adb. I'm not certain, but it sounds like this would also prevent the CyanogenMod built-in update mechanism to fail as well...
Click to expand...
Click to collapse
Can you see the folders on the sdcard when you go to install zip from sdcard?
Sent from my ADR6425LVW using Tapatalk 2
Flyhalf205 said:
Can you see the folders on the sdcard when you go to install zip from sdcard?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
No.
nuclear_eclipse said:
No.
Click to expand...
Click to collapse
Okay. I'll need to look over my configs again. New build of twrp graphics should be fixed. See if you can see sdcard on that.
EDIT: I think I see what I did wrong in my config file. Building a new build.
Sent from my ADR6425LVW using Tapatalk 2
New build of CWM classic is up. Internal storage should work.
Flyhalf205 said:
New build of CWM classic is up. Internal storage should work.
Click to expand...
Click to collapse
Internal storage worked like a charm! Thanks again FlyHalf!

[Q] I think I bricked my One.

I have a UK Vodafone HTC One. It's running the Trickdrpid Rom with TWRP 2.5.0.0 recovery. Everything was working fine until I flashed tbaldens kernel to enable lock2wake function. Everything went ok with flashing (I think!) but upon reboot, nothing. Just flashing back and home keys when I press the power button. I can get into recovery but have no rom on my internal SD to reflash. The PC gives the USB spund when i boot into recovery, but the phone storage doesnt show up on PC. Is there any way to get another Rom on the storage to reflash, or is it bricked? Please help.
There is an option in TWRP to sideload with adb. Try pushing a new Rom with the ADB Push romname.zip
Then you should be able to locate it and flash it
Sent from my HTC One using xda app-developers app
gazlufc said:
There is an option in TWRP to sideload with adb. Try pushing a new Rom with the ADB Push romname.zip
Then you should be able to locate it and flash it
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply. Is there a tutorial on ADB anywhere? I've not had experience using it before.
http://developer.android.com/tools/help/adb.html
You will need to install Android SDK if you don't already have it installed.
If you are using windows open Command prompt and Change in to the android-sdk/platform-tools folder.
In here you can run the ADB devices command to see if your device is showing up as connected.
If so copy the rom in the the platform-tools folder to make it easier.
so lets say your rom is called rom.zip the command to push would be
adb push rom.zip /sdcard/ (OR WHAT EVER LOCATION YOU WANT)
If all goes well you should be select zip from storage in TWRP and flash it.
Hope this helps
---------- Post added at 02:12 PM ---------- Previous post was at 01:18 PM ----------
liverman666 said:
I have a UK Vodafone HTC One. It's running the Trickdrpid Rom with TWRP 2.5.0.0 recovery. Everything was working fine until I flashed tbaldens kernel to enable lock2wake function. Everything went ok with flashing (I think!) but upon reboot, nothing. Just flashing back and home keys when I press the power button. I can get into recovery but have no rom on my internal SD to reflash. The PC gives the USB spund when i boot into recovery, but the phone storage doesnt show up on PC. Is there any way to get another Rom on the storage to reflash, or is it bricked? Please help.
Click to expand...
Click to collapse
I see that the command to sideload is 'adb sideload rom.zip'
My appologies if this didn't work up to now
gazlufc said:
http://developer.android.com/tools/help/adb.html
You will need to install Android SDK if you don't already have it installed.
If you are using windows open Command prompt and Change in to the android-sdk/platform-tools folder.
In here you can run the ADB devices command to see if your device is showing up as connected.
If so copy the rom in the the platform-tools folder to make it easier.
so lets say your rom is called rom.zip the command to push would be
adb push rom.zip /sdcard/ (OR WHAT EVER LOCATION YOU WANT)
If all goes well you should be select zip from storage in TWRP and flash it.
Hope this helps
---------- Post added at 02:12 PM ---------- Previous post was at 01:18 PM ----------
I see that the command to sideload is 'adb sideload rom.zip'
My appologies if this didn't work up to now
Click to expand...
Click to collapse
Ok. I've managed to upload the Rom via sideload. But now I can't find it anywhere on the SD card?
Coincidentally i'm having the same issue when installing the same exact kernal (lock2wake) last night.
It soft bricked after it was flashed using the AndroidRevolution rom
No USB access despite popups and there are no roms installed on my SD.
I can access the bootloader and recovery (Clockwork) but thats about it.
I'll follow the instructions Gaz posted above and see where it takes me.
There should be an option to install from side load in your recovery.
If you can't find it I would recommend flashing CWM for the flash. You can do it via the fastboot method or the HTC one AIO toolkit. The toolkit option is the easiest.
Then when you are in CWM select install zip. There should be an option in there to install from ADB sideload.
Here you push the the Rom zip via the adb sideload Rom.zip and then it should install. Let me know how you guys get on
If you need anymore help feel free to PM me and I'll try to explain it more if needed
Sent from my HTC One using xda app-developers app
got it working! thanks gaz
Review:
1. I (soft) bricked my phone flashing TeamSeven Sense "Home2Wake" kernel
http://forum.xda-developers.com/showthread.php?t=2255160
2. My phone currently had the android revolution 12.0 rom installed
http://forum.xda-developers.com/showthread.php?t=2183023
3. To unbrick my phone and get access to the bootloader/recovery, i perform the following step
gunnyman said:
put the phone under a bright light.
hold down power, lights will flash and phone will shut down in about 15-20 seconds
then hold volume down and power to get back to bootloader
Click to expand...
Click to collapse
4. Once i had access to the bootloader, i navigated to recovery (CWM-Touch) but couldn't reflash my rom since i no longer had the zip file on my internal SD.
5. So I followed Gaz instructions posted above by installing the Android SDK files from http://developer.android.com/tools/help/adb.html
6. After I installed the SDK on my Bootcamp Windows 7 Home (on a Macbook), I copied my rom to the platform-tools folder and renamed it something shorter.
7. Then I opened command prompt and used it to pushed the rom file to the root of the internal sd (followed gaz instructions above)
8. Once completed, I re-opened recovery and reflashed. Fixed.
I just want my PC to recognize my phone.. Once that happens, i think I'll be in good business... The list of devices attached is none...

bricked, stuck in recovery

Hi there!
I have a TX1085, it is already unlocked and rooted and has the CM Recovery installed. But before the CM Recovery I had the TWRP Recovery installed and tried to use it to flash CM12, which I had put on the SD-Card. It kept on telling me that mounting the system failed. Unfortunately I wiped everything via TWRP Recovery without creating a backup. Then I installed the CM Recovery to try again. Now, if I try to flash via CM Recovery (apply update) it doesn't show anything in my internal storage and I can't connect via adb using Ubuntu (Terminal tells me either "device not found" or "device offline".)
Any suggestions?
Greets
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
psssss said:
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
Click to expand...
Click to collapse
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
pyq said:
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
Click to expand...
Click to collapse
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
josuearisty said:
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
pyq said:
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
Click to expand...
Click to collapse
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
Click to expand...
Click to collapse
I am using Linux without Android SDK, but I have working fastboot and adb installed.
josuearisty said:
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
try to flash stock firmware
kaktusmaier125 said:
try to flash stock firmware
Click to expand...
Click to collapse
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Click to expand...
Click to collapse
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
josuearisty said:
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
pyq said:
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
Click to expand...
Click to collapse
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
josuearisty said:
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
If I use the "fastboot boot CM_recovery.img" command the phone installs it and then starts into TWRP. Except for that nothing changes. How can I continue?
rotorbudd said:
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
Click to expand...
Click to collapse
If I try to make a tick (as to mount) system the phone vibrates but doesn't tick system, so I can't mount it this way.
pyq said:
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
Click to expand...
Click to collapse
Yes you can

Categories

Resources