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 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
So I brought myself in a bad situation.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
I was trying to root my sony xperia z1 compact using this guide: http ://techglen. com/2014/02/05/root-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/
Following the steps it asked me to CWM 6 using this guide: http ://techglen. com/2014/02/05/install-cwm-6-on-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/2
I checked firmware and version of my phone and everything was correct.
I must admit I have no clue as to what I'm doing but I'm normally ok with tech stuff and the guide seemed detailed and trust worthy so I thought I could do it following the guide.
I got the bootloading unlocked just fine and started to install CWM. I made it this far:
- After downloading CWM kernel zip (Its not the actual name of file, just a reference name), place it in internal or external SD Card of your smartphone
- Now extract CWM kernel zip on your PC’s desktop and copy boot.img
- Paste this file inside the folder where you have installed Minimal ADB and Fastboot
- Now turn off your smartphones completely
- Plug in mobile’s USB in cable in PC port only
- Hold Volume up button and plug in USB cable in mobile’s port
- LED will turn blue (If it does not remain blue for long, then read Optional part in bootloader unlocking method explained above
- Once you are successfully in fastboot mode, then you can continue
- Now type Fastboot flash boot boot.img and press Enter
- It will flash boot.img file on your device
- Now unplug the device and boot it up
- As soon as you see purple colored LED, start pressing volume up and down buttons repeatedly, until you are in CWM mode
- In CWM Mode, select “Install Zip”
Click to expand...
Click to collapse
I downloaded CWM .img file, placed it in my ADB folder and placed a copy on my phone. Using ADB I flashed the CWM .img (bolded step), unplugged the phone and the CWM screen came up and I was able to navigate using the volume buttons. So far so good.
At this point I realized that the CWM .img file I had downloaded and placed on my phone was not a zip file and I couldn't find it. So I hit reboot to boot up my phone normally so I could place the .img packed as a .zip file on the phone. Some error message came up, but I didn't manage to read it but caught something saying root I think.
As it rebooted the sony logo came up but then the purple led turned on and it seemed to boot into CWM again. A brief screen explaining how to navigate came up as you see in the video below (but with no menu options to actually navigate) before it rebooted and repeated.
I can still use ADB and fastboot, but I can't get into CWM and I can't boot normally.
Edit: Just tried "adb devices" and it says "list of devices attached" and then it's just blank. I can't push files onto the phone (error: device not found) but I can still reboot the device fusing fastboot and there's no error when I try and reflash cwm. Reading up on this it would seem that usb debugging has somehow been turned back on so adb can't acces the phone but fastboot can. Any way to turn on usb debugging through fastboot?
I tried a forced shutdown using the off button next to the sim card but it didn't help.
The phone is not recognized by my computer so I can't place or delete files from it.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
If I don't press the volume button it will just keep looping in the sony logo and purple led light.
What I want to do is get back to a normal boot, remove the CWM .img file and put the .img file packed as .zip file onto the phone and retry the process.
I have googled a lot of options, but most results are a year old and I hardly understand half of what is being suggested. If anyone could please walk me through the process in a language that a total idiot can understand I would be so grateful and hopefully get my sleep back.
ravneravn said:
So I brought myself in a bad situation.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
I was trying to root my sony xperia z1 compact using this guide: http ://techglen. com/2014/02/05/root-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/
Following the steps it asked me to CWM 6 using this guide: http ://techglen. com/2014/02/05/install-cwm-6-on-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/2
I checked firmware and version of my phone and everything was correct.
I must admit I have no clue as to what I'm doing but I'm normally ok with tech stuff and the guide seemed detailed and trust worthy so I thought I could do it following the guide.
I got the bootloading unlocked just fine and started to install CWM. I made it this far:
I downloaded CWM .img file, placed it in my ADB folder and placed a copy on my phone. Using ADB I flashed the CWM .img (bolded step), unplugged the phone and the CWM screen came up and I was able to navigate using the volume buttons. So far so good.
At this point I realized that the CWM .img file I had downloaded and placed on my phone was not a zip file and I couldn't find it. So I hit reboot to boot up my phone normally so I could place the .img packed as a .zip file on the phone. Some error message came up, but I didn't manage to read it but caught something saying root I think.
As it rebooted the sony logo came up but then the purple led turned on and it seemed to boot into CWM again. A brief screen explaining how to navigate came up as you see in the video below (but with no menu options to actually navigate) before it rebooted and repeated.
I can still use ADB and fastboot, but I can't get into CWM and I can't boot normally.
Edit: Just tried "adb devices" and it says "list of devices attached" and then it's just blank. I can't push files onto the phone (error: device not found) but I can still reboot the device fusing fastboot and there's no error when I try and reflash cwm. Reading up on this it would seem that usb debugging has somehow been turned back on so adb can't acces the phone but fastboot can. Any way to turn on usb debugging through fastboot?
I tried a forced shutdown using the off button next to the sim card but it didn't help.
The phone is not recognized by my computer so I can't place or delete files from it.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
If I don't press the volume button it will just keep looping in the sony logo and purple led light.
What I want to do is get back to a normal boot, remove the CWM .img file and put the .img file packed as .zip file onto the phone and retry the process.
I have googled a lot of options, but most results are a year old and I hardly understand half of what is being suggested. If anyone could please walk me through the process in a language that a total idiot can understand I would be so grateful and hopefully get my sleep back.
Click to expand...
Click to collapse
I hope you made a backup of your phone.
It may be worth wiping everything and flashing the Z1 stock firmware on to your phone. Stock firmwares can be found relatively easily by using Google. There are also lots of different video tutorials on YouTube on how to how to revert back to stock firmware and on how you can escape bootloops. Try this: www. youtube. com/watch?v=j4gm9VeQCHA
You're on the wrong forum, this one is for Xperia Z, for Xperia Z1 Compact go here:
http://forum.xda-developers.com/sony-xperia-z1-compact
So I'm trying to root my Sprint M7. I've succeeded in doing the following.
1. Unlocked the boot loader
2. Installed CW Touch recovery
Now I think the next step is to go into Fastboot/Recovery and install the SuperSU zip from /sd_card/
That's the step I'm having problems with. How do I get the SuperSU zip onto the /sd_card/ folder? When I plug in my phone I just get HTC Sync manager popping up and I can't browse the phone's directory because Sync Manager says the phone is not connected.
Running Win 7 64.
Thanks
SeriesOfTubes said:
So I'm trying to root my Sprint M7. I've succeeded in doing the following.
1. Unlocked the boot loader
2. Installed CW Touch recovery
Now I think the next step is to go into Fastboot/Recovery and install the SuperSU zip from /sd_card/
That's the step I'm having problems with. How do I get the SuperSU zip onto the /sd_card/ folder? When I plug in my phone I just get HTC Sync manager popping up and I can't browse the phone's directory because Sync Manager says the phone is not connected.
Running Win 7 64.
Thanks
Click to expand...
Click to collapse
uninstall htc sync (but don't touch the drivers)
boot your phone in CWM
Code:
adb push supersu.zip /sdcard
then flash supersu.zip using CWM
or easy way
flash latest twrp recovery for sprint version instead of CWM
boot in recovery and exit, you'll be prompted to root the phone before leaving twrp, select yes.
alray said:
uninstall htc sync (but don't touch the drivers)
boot your phone in CWM
Code:
adb push supersu.zip /sdcard
then flash supersu.zip using CWM
or easy way
flash latest twrp recovery for sprint version instead of CWM
boot in recovery and exit, you'll be prompted to root the phone before leaving twrp, select yes.
Click to expand...
Click to collapse
Thanks! [emoji4]
Sent from my HTCONE using Tapatalk
Background: I have the XT1064 (unlocked, single sim), and I actually just bought this phone. I ordered it because I have a droid Turbo that I don't want to risk custom ROMs on, so I figured this $100 device would be good to play with. I first unlocked the bootloader, courtesy of motorola, and then I flashed custom recovery (TWRP). A bit of tinkering later and I discover I can't get the recovery to stick. "oh well, I can plug in my phone and type a command on boot no problem." Next, I tried flashing the latest release of CM12.1 for my phone (titan) and I get an error. I search around trying to fix the error, and everyone says "use the latest nightly (CM13)" and "factory reset your phone via twrp" so that's what I do. Next, after waiting for my phone to start up, I get everything rolling so I can copy my new image over.
Problem: I find that access is denied to "sdcard/download" so I try other folders in sdcard. None are allowed for adb.
Attempted solutions: On my phone, I install ES file explorer, which reveals that everything in sdcard/ is gone except the Android folder, and an extensionless file called TWRP. Still not suspecting anything, I attempt to create a "download" folder. No luck, access still restricted. I tried downloading a file via the internet browser, "failed to find downloads directory". Everything in sdcard is barred from me. Besides the SuperSU that's half-installed (part of twrp apparently) this is a factory new device, I purchased it from best buy via ebay. Is my phone toast already? Or is there something I can do?
MCFX2 said:
Background: I have the XT1064 (unlocked, single sim), and I actually just bought this phone. I ordered it because I have a droid Turbo that I don't want to risk custom ROMs on, so I figured this $100 device would be good to play with. I first unlocked the bootloader, courtesy of motorola, and then I flashed custom recovery (TWRP). A bit of tinkering later and I discover I can't get the recovery to stick. "oh well, I can plug in my phone and type a command on boot no problem." Next, I tried flashing the latest release of CM12.1 for my phone (titan) and I get an error. I search around trying to fix the error, and everyone says "use the latest nightly (CM13)" and "factory reset your phone via twrp" so that's what I do. Next, after waiting for my phone to start up, I get everything rolling so I can copy my new image over.
Problem: I find that access is denied to "sdcard/download" so I try other folders in sdcard. None are allowed for adb.
Attempted solutions: On my phone, I install ES file explorer, which reveals that everything in sdcard/ is gone except the Android folder, and an extensionless file called TWRP. Still not suspecting anything, I attempt to create a "download" folder. No luck, access still restricted. I tried downloading a file via the internet browser, "failed to find downloads directory". Everything in sdcard is barred from me. Besides the SuperSU that's half-installed (part of twrp apparently) this is a factory new device, I purchased it from best buy via ebay. Is my phone toast already? Or is there something I can do?
Click to expand...
Click to collapse
Since you can boot it, it's not bricked, if ur on cm 13 , ur external memory card is formatted as internal storage (the reason why you cant access it via twrp) , go to settings >storage and USB > select ur memory card >click on options (top right corner) >format as portable storage. Now you can access ur sd card via twrp. And check ur twrp version, 8.6.0 , and command Used to flash it via Pc "fastboot flash recovery filename.img (remove img from original file) . Hope this helps, and about Cm12, what was the error you were getting?