[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
Related
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.
UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ROM Choices:
Original Cloned ROM (First version with direct partition image copy, requires >1GB space on SD card which has caused issues for some)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Update 10/12:
NEW ROM with full ext4 optimizations. System, Cache and Data (only in wipe version) will be cleared, formatted and "fsck -Dfy" checked!
DO NOT WIPE ANYTHING IN CWM!!! Just choose the ROM file appropriately.
Non-Wipe Version (This one leaves existing data partition alone, only checks it for errors)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_nowipe.zip
Wipe Version (THIS ONE WILL FORMAT DATA PARTITION, ALL USER DATA WILL BE LOST!)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_wipe.zip
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
WARNING: DO NOT wipe or factory reset in CWM! You can simply install ICS over an existing Honeycomb setup! Choose the correct ROM version: One erases everything and the other one preserves user data. Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there! We had too many reports of problems when wiping/factory resetting with CWM. So for now the best advice for anyone looking into installing the ROM is DO NOT WIPE!
UPDATED PROCEDURE as of 10/16 - NO NEED to flash the old 3e recovery any more! Much easier and quicker baseband update below...
Step 5: Download and flash the baseband modem.bin with ODIN
Download the baseband update: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Bring the tab back into ODIN mode the same as before. Extract the modem.bin file from the modem.zip and drop it in the PHONE section (not PDA!) in ODIN this time. Click start and let it flash and reboot. Done. Under settings/about device you should now have Baseband Version i815.04 V.LP10 / I815LP10
B]Step 6: Optional: Keep CWM or go all stock[/B]
If you would rather like to be full stock than keeping CWM as the recovery program, then bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash LP10_recovery.
The ROM is pre-rooted. SuperSU is pre-installed as part of the ROM.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
Yes the 6.0.1.1 (as far as I know!) is safe. No need to wipe anyway. The v2 included more files that turned out to be not necessary. The files posted here along with the updated, safer method of flashing, should be the best and quickest way to get to full stock ICS.
The v2 was mainly an attempt to bring user ice's tab back to life after his data partition got killed.
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Thank you so much, and I do plan on doing a wipe to clear out my Tab to bring it to a clean slate. Just didn't want it to be a broken state lol.
rhester72 said:
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Click to expand...
Click to collapse
IMEI and such is stored in the mmcblk0p1 partition which (along with 2 and 3 which are the bootloader) we don't touch. So no, we only flash the factory fs, lte modem and kernel. CDMA modem.bin via the new method.
electron73 said:
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ICS ROM: http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Modem Upgrade: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Make sure you have MORE than 1GB of free space left on the SD card when done.
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
BTW there is NO NEED to wipe! You can simply install ICS over an existing Honeycomb setup! Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there!
Step 5: Flash the old Honeycomb recovery in order to do the modem upgrade
Since CWM does not understand the proprietary command used to flash the "firmware" which is the base modem file, we need to use STOCK recovery for this. The downside is that, of course, the new recovery is now locked down and won't accept unsigned files. So we need to flash the OLD Honeycomb FD01 recovery and feed it the modem update!
When the CWM flash above is finished and tells you to reboot, simple press and hold power and vol down again to get back into ODIN mode. Connect the USB again and this time use Odin the same way as above, but to flash the FD10_recovery.tar. This time uncheck the "reboot" tick mark.
Step 6: Flash the modem upgrade with the old stock 3e recovery
When Odin is done above, hold down pwr and vol up until you see the old school recovery pop up saying *manual mode*. Select flash update zip from sdcard and select the electron_ICS-LP10_i815_modem.zip this time. It will go on for a while in total bling flight. No output apart from rotating gears! This one is tricky. Just wait until it either ends saying that it is done or a yellow exclamation point shows up in the middle of the screen. The flash is done.
Step 7: Choose between Stock and CWM
Now bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash either CWM or LP10_recovery if you rather like to be full stock. If you chose CWM then be aware that the ROM will try to overwrite that immediately on first boot!! In order to avoid that, flash it with "reboot" box unticked and manually reset into CWM mode (pwr + vol up) and inside CWM select reboot system. It will then give you a big warning that the ROM has a CWM killer and offers you to disable that, so CWM will stay in place (good for Nandroids etd).
Step 8: Boot the ICS ROM and enjoy!
Once you see ICS, go to the play store and install SuperSU. The rom is pre-rooted and just needs the SuperSU app for full root access control.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Click to expand...
Click to collapse
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
bathanr said:
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here, what steps do I take to flash the updated modem
Awesome!
ice0901 said:
Same here, what steps do I take to flash the updated modem
Click to expand...
Click to collapse
from step 5 on forward. no need to reflash the whole rom if you already have ICS running.
Just odin the old recovery on, flash the modem update zip, then odin the new recovery or CWM back.
boot loop
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
rspong said:
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
Click to expand...
Click to collapse
Weird. OK did the v2 flash go all the way through? Did it finish at some point and say "please reboot" ? Or did it get stuck half way though?
Can you in CWM mount your internal storage? Did you get any errors when you did the full wipe/factory reset? anything saying "error mounting /data" maybe ?
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
almus said:
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
Click to expand...
Click to collapse
No I didn't create it but it is guaranteed the right one for i815. I know because I messed up my partition table last night and had to use that pit to repartition Lucky I found that. What you would do in order to re-do your pit is open odin, put the CWM in the PDA section as usual and then click PIT and select that pit. That should activate a checkbox "repartition device". Leave that on for this one run and click start.
As a result it should partition, then flash the CWM and you should immediately be able to enter CWM. With CWM running connect USB
and use adb shell to get onto your tab.
IN the root prompt enter parted /dev/block/mmcblk0
and in the parted prompt enter print. If you see the result as in the attached pic (note: no file system in the DATAFS line) then you need to fix that the same way ice got it fixed last night. I think the link to the thread is in the OP
bathanr said:
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
Click to expand...
Click to collapse
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Yes. V2 went through with no problems.in CWM I can mount efs,cache,system but not data. Then in cwm... OK..wiping data then I get a error mounting data. Skipping format
Sent from my DROID RAZR using xda premium
chefdave12118 said:
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
The flash controller in our tablets is buggy. See here http://forum.xda-developers.com/showthread.php?t=1862294
electron73 said:
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Click to expand...
Click to collapse
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
bathanr said:
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
Click to expand...
Click to collapse
I ran into the splash screen just hanging and followed the data retore steps. I keep getting this error when trying to print the print command from the parted prompt.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Flatlinz>f:
F:\>cd 7.7
F:\7.7>cd adb
F:\7.7\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ls
ls
boot init sys
cache init.rc system
charger lpm.rc tmp
data preload ueventd.goldfish.rc
default.prop proc ueventd.rc
dev recovery ueventd.smdk4210.rc
efs res vendor
etc sbin
external_sd sdcard
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have the end before the start!
(parted)
Any ideas?
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
A few questions:
spazlon said:
I tried installing a custom ROM on my 7310 and it had issues.
Click to expand...
Click to collapse
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop.
Click to expand...
Click to collapse
How far into the boot sequence does it get?
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Have you tried seeing what is causing the boot-loop using adb?
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Click to expand...
Click to collapse
This is an action of last resort. Exhaust all other avenues first.
boscorama said:
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
Click to expand...
Click to collapse
I used CWM to flash AOSP 4.1.2. It seemed to work fine for a day or two, but then it needed charging (as normal). I let it charge over night and in the morning it had less battery. I figured the charger or cable were flaky so I tried another set on another outlet and same thing. Then it finally ran out of battery. I let it charge again over night and when I tried to turn it on it was really slow. The boot animation was only 1 frame every couple seconds. It would eventually boot all the way up, but it was still REALLY slow. So I went into CWM and reflashed the same ROM. Then I got a boot loop of the boot animation. I couldn't get into CWM any more, so then I went into download mode and flashed the official firmware and flashed it with ODIN.
boscorama said:
How far into the boot sequence does it get?
Click to expand...
Click to collapse
Now when I turn it on it just says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can flash again with ODIN and it will get to the Samsung boot animation and just pulse SAMSUNG.
boscorama said:
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Click to expand...
Click to collapse
If I hold power and volume down I can get into download mode or Samsung recovery, not CWM, and power with volume up doesn't do anything.
boscorama said:
Have you tried seeing what is causing the boot-loop using adb?
Click to expand...
Click to collapse
I don't know anything about adb and I'm not sure what I would be looking for. Is there a tutorial I can follow somewhere?
Thanks for any help!
This worked for me with similar problem
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Thanks! I'll give this a try when I get home. I'll let you know how it works out.
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Agreed - my procedure avoids manual repartitioning - I tried lots of other procedures but none worked. I think my data partition had become corrupt because I kept getting error messages. My first try was to recover with my cwm recovery file I made originally but I kept getting back to the boot loop .
spazlon said:
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
Click to expand...
Click to collapse
I always got something like that ...
After bootloop just go to recrovery mode then factory riset ... its 100% WORK
Sent from my GT-P7300 using xda premium
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
Sorry - being a newbie myself I'm at a loss. It worked a charm for me.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
did a format /system before installing the custom roms? This is an important step.
prince93 said:
did a format /system before installing the custom roms? This is an important step.
Click to expand...
Click to collapse
This fixed it. Never had to do it with any of my other devices. CM10 loaded quickly after that. Loving how fast JB is!
Thanks!
Sent from my GT-P7310 using Tapatalk HD
It worked
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
WOw! This fixed my Tablet! thank you ever so much!!
mjramos15 said:
WOw! This fixed my Tablet! thank you ever so much!!
Click to expand...
Click to collapse
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
Gee thanks. This saved my tab. I'd almost given up on it and then voila.
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
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
_______________________________________________________________________________
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Thank you for posting this. I tried three other methods to get root back before this, and none of them worked. This one did the trick without any problems at all. Thanks again!
Wug's Nexus Root Toolkit 1.9.4
kyoshiro22 said:
Wug's Nexus Root Toolkit 1.9.4
Click to expand...
Click to collapse
I know there's Toolkit's out there, but this is for those who choose to take the "Fastboot" approach.
gestevez1213 said:
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP[ - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Click to expand...
Click to collapse
This is NOT working.... I tried it 3 times on 2 devices
papayayoghurt said:
This is NOT working.... I tried it 3 times on 2 devices
Click to expand...
Click to collapse
What part are you stuck at?
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
I used chainfires auto root for the N5 (stock lollipop Boot loader). Worked great. Just download to a PC put phone into boot loader and run the bat file. I can't link but a quick google will find it for you.
Sent from my Nexus 5 using Tapatalk
andrelessa said:
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
Click to expand...
Click to collapse
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Personally, I'm using the autoroot from chainfire. Works like a charm, no custom recovery is needed (I have the stock recovery).
gestevez1213 said:
What part are you stuck at?
Click to expand...
Click to collapse
Everything is working, but then SuperSU can´t find a Binary.
gestevez1213 said:
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Click to expand...
Click to collapse
Yes, I read somewhere that TWRP need this...
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Are you running the official lollipop release? It should work with that. Delete the app, and try again.
Just put your phone in bootloader and run cf-autoroot from windows if you dont want twrp.
I have twrp but its not working like that
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Had the same issue and needed to flash the updated kernel from chainfire : https://www.androidfilehost.com/?fid=95747613655047375
Why are you trying to do this the hard way? Just use chainfire's autoroot.
It works perfect and it's literally one command
fastboot boot CHautoroot.img (or whatever the file name is)
cf-auto-root is the way
I agree, just use cf-auto-root. You should be good to go in no time.
Just for FYI, if you already have unlocked bootloader, it won't wipe your data, if you are concerned.
CF-auto-root roots N5 without modifying your kernel. I believe, if you flash the SuperSU in TWRP, it would modify the kernel. It's nothing bad, but if you want to remain "stock" and don't want to reflash stock ROM later to get the OTA, just use "Full unroot" from SuperSU app and you are stock and ready for next OTA.
I have encrypted the storage on my Nexus 5. Will CF-Auto-Root wipe my storage?
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
I have the same error.