Related
Hi Folks,
I just wanted to put my experiences on the forums here in case it might help someone. I trawled through a lot of answers from all over to get the info I wanted and this is a consolidation of that effort.
This post is aimed at:
people who need to root orange razr i after JB OTA update
people who have bricked their phone after attempting the above using other methods
I bought a razr i last year from Orange in the UK. I originally tried to unlock the bootloader using the thread here: http://forum.xda-developers.com/showthread.php?t=1928551
But the official way of unlocking did not work, probably because Orange didn't want people unlocking their phones (or did I just do it wrong – did other orange users have success?).
I next tried the x86 version of motofail2go by Dan Rosenberg: http://forum.xda-developers.com/showthread.php?p=32927646
This worked fine and I was happy. Then Orange/MOTO released the OTA update for JB and my device was no longer rooted. I went back to the start and went to see if my bootloader would unlock after the update – and to my surprise – it did!
Next I went to root using this method: http://www.xda-developers.com/android/multi-platform-root-tool-for-the-motorola-razr-i/
I should mention as well I am using Debian Linux to the unlocking and rooting. This method left my phone unbootable, though I didn't think there was a problem with the method itself, it's just that the files provided are for ICS and don't work after the OTA JB update.
After some research I found the files which worked: I downloaded 91.2.26001.Orange.en.GB.zip from http://batakang.com/ftp/RAZRi/HomemadeFastboots/91.2.26001.Orange.en.GB.zip
This is the same version number as existing on my phone after JB update. After unzipping this I had the files I needed, namely: boot.img, Superuser.apk and su. I also downloaded the latest android sdk from:
http://developer.android.com/sdk/index.html in order to get the latest fastboot and adb programs. I put all these files in the same folder along with the files from the multi-platform-root-tool from above, replacing those original files. I also copied boot.img to overwrite razr_i_boot.img and fastboot to fastboot.linux in order for the Root.sh script to work later.
Next: I connected the phone to my laptop via USB and set it up in fastboot mode. Previously it was in a boot loop, where it would display the unlocked bootloader warning and then reboot over and over again. To break out of this: hold the decrease volume button and then hold the power button for approx 10 seconds until the phone reboots and vibrates, then let go of the power button and wait 1 second for good measure before releasing the volume button. It will then boot into fastboot mode and should say "connected by USB" or something like that in yellow text.
Then, I went to the folder with all those files in my computer and issued:
Code:
$ sudo fastboot flash boot boot.img
And voilà! It booted normally, but was still not rooted. This was simply a matter of following the multi-platform-root instructions again with the replacement JB files.
So that's it. I hope this might help others. I welcome any questions, comments or queries.
Thanks to everyone who provided the files I need, especially to mattlgroff who did most of the ground work for this.
Code:
Description:
Your warranty is now void.
I am not responsible if you brick your phone during the process.
Flash it at your own risk.
Sony’s mid range device Xperia T has been recently updated to Android 4.3 Jelly Bean. In the recent past Sony remained quite fair with the users in terms of Software updates keeping its promise at top, the Android Jelly Bean 4.3 update started reaching out the users taking the device one stop close to KitKat that is under investigation / testing by Sony at the moment. Well, the new firmware definitely needs new methods to run a CWM Recovery inside and a new method to get rooted as well. For those who have updated their devices to this new firmware and are now looking for a compatible CWM recovery, they have spotted the right place at the moment.
Here are some important installation instructions and pre-requisites:
This guide is only for Sony Xperia T. Do not try this on any other model, please check your device’s model in Settings > About Device.
The CWM recovery is only for Sony Xperia T running stock or stock based Android 4.3 [9.2.A.1.199] or [9.2.A.0.295].
Check your firmware version in Settings > About Device and make sure that it matches the one mentioned above.
You must have installed Android ADB & Fastboot drivers. Follow this link http://techbeasts.com/2013/12/18/install-android-adb-fastboot-drivers-quickly-with-minimal-tool-on-windows-pc/.
Your device must have an unlocked bootloader. Follow this link to unlock bootloader http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
Please make sure that your phone’s battery is charged at least over 60%. This is highly recommended in order to prevent any power issues during the recovery flashing process.
Backup all your important data before flashing CWM.
Backup your current system using a custom recovery (CWM or TWRP) if you’ve flashed one. This is recommended in case something goes wrong with CWM installation, you can use the custom recovery and return to the old working state of your system.
Enable USB debugging mode on your device. Get it in Settings > Developer Options > USB Debugging mode.
Use working data cable to establish connection between your PC and Phone.
Alright! Follow this guide to the letter now.
How to Install CWM Recovery on Sony Xperia T:
Download Stock Kernel with CWM Recovery here http://www.mediafire.com/download/xwjdwcmpomn6wth/kernel_sj.elf
You will get a kernel_sj.elf file. Just rename it to Kernel.elf
Place the Kernel.elf file in the Minimal ADB & Fastboot folder that you created using our ADB & Fastboot Quick Setup Guide.
If you are using Android ADB & Fastboot full package, you can place the downloaded Kernel.elf file in the Fastboot folder or in the Platform-tools folder.
Open the folder where you placed the Kernel.elf file.(E.g Minimal ADB & Fastboot or Fastboot or Platform Tools).
Press and hold the shift key and right click on an empty area within the folder, and click on “Open Command Window Here”.
Turn off your Xperia T completely.
Now press the Volume Up Key and while keeping it pressed plug in the USB cable.
You should see a blue light in the notification light of your phone, that means your device is now connected in Fastboot mode.
Now type the following command: fastboot flash boot Kernel.elf
Hit Enter and it will quickly flash CWM recovery in your Sony Xperia T.
Once recovery is flashed, now issue this command Fastboot Reboot
Your device will reboot now(even if your device does not reboot do it manually). As soon as you see the Sony logo, and the pink LED, press Volume Up key to enter recovery.
Congrats! You should now see the custom recovery.
That’s All with the recovery installation. In case you got any queries or face any difficulties regarding this post, please feel free to stop by the comment box below and let me know. I will get back to you as soon as possible. Thanks all.
Attachments
Q&A for Gear Live Stock Firmware Image - 24JUL14 & Bootable Root ADB image
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Returning to stock [fastboot doesn't work, looks like I have odin]
I've bought modded Gear Live with custom ROM. I wan't return to stock Android Wear but it looks like fastboot doesn't work or I don't know how to do this. If I choose fastboot during boot I can enter Odin download mode. It looks like somebody flashed ROM from Android device to this watch.
My watch is visible under adb but when i put it in download mode fastboot doesn't recognize my device. What's the procedure of returning from Odin to stock Android Wear?
tomrozb said:
I've bought modded Gear Live with custom ROM. I wan't return to stock Android Wear but it looks like fastboot doesn't work or I don't know how to do this. If I choose fastboot during boot I can enter Odin download mode. It looks like somebody flashed ROM from Android device to this watch.
My watch is visible under adb but when i put it in download mode fastboot doesn't recognize my device. What's the procedure of returning from Odin to stock Android Wear?
Click to expand...
Click to collapse
Youre talking about three different tools here. Either you have fastboot or odin mode. What OS are you using? What modes do you have available? What do you see on your screen?
When I swipe the screen diagonal when holding the power button I see:
Select REBOOT MODE:
Continue, Download, Upload, Recovery, PowerOff, Fastboot
No matter if I choose download or fastbook it enters in ODIN MODE like on a phone with Android OS. The model is SM-R382.
Any chance to restore to stock Android Wear? As I mentioned 'fastboot devices' shows nothing when the device is in download mode.
lsusb returns:
Bus 001 Device 004: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)
Any chance flashing this to stock Android Wear?
AdamOutler said:
Youre talking about three different tools here. Either you have fastboot or odin mode. What OS are you using? What modes do you have available? What do you see on your screen?
Click to expand...
Click to collapse
Any chance flashing this to stock Android Wear?
Flashed this to fix a number of screwups. Now I'm trying to do delta OTA updates to get to 5.0.1.
This system.img installed KMV78X, so I tried to flash sprat-KGW42N-from-KMV78X first.
The sha1sum for "/system/lib/libstagefright.so" seems to be wrong. The update script expects 85998faea63db14c87c02c128d7e4fe39da0202f, on this image it is 624e6eb8000d6c1c0ff53998fb54d1e008deb41e.
EDIT: sprat-KMV78Y-from-KMV78X seems to expect 85998faea63db14c87c02c128d7e4fe39da0202f as well.
EDIT2: I'm not sure how this is supposed to work. Every time I "fastboot flash system system.img", I get a different hash for libstagefright.so (other files stay the same). I removed the patching for that file from the OTA updates and I was able to get to LWX48P, but now I need the updated libstagefright.so. Ostensibly, this version has SHA1 hash 9279477d8f47f6e042ab1e88a82d79cd7ac5ed20 (according to sprat-LWX48P-from-KNX01Q.fc0bcfbe.zip)
EDIT3: Solved. Installed stock KMV78Y from http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620, then did OTA delta updates to get to 5.0.1.
Bricked Gear Live
Hi All,
I am making a huge education effort to learn the way of developing in my mid 30's. I recently bought a refurbished Gear Live "the Best Buy mess". I was able to reflash the stock onto the watch but it would not update it's firmware; so easy enough I thought I would push the latest version which leads me to the current state of the watch which is "could not do normal boot" I can teach the fastboot screen but cannot authorize the ADB now that I cannot approve the change or even change it through the developer tools. I downloaded Odin but I am not able to connect to the watch to push the flash. Has anyone run into this? I have downloaded the Gear Live reset tool but without ADB authorized it won't allow access. Can anyone help an up and tech savvy learner find his way to bringing it back? I use the watch to monitor my sons Blood Sugar since he's a type 1 diabetic.
Help?
Update, I was able to fastboot the original img files and I'm back to where I started. Now to get it up to 5.0.1
Crooter777 said:
Update, I was able to fastboot the original img files and I'm back to where I started. Now to get it up to 5.0.1
Click to expand...
Click to collapse
kindly help how you did it ?
Disclaimer: This procedure involves a higher risk than normal to brick your device. If you are not really familiar with flashtool please do not attempt to do this! I am not resposible for bricked devices, World War III or your exploding cats!
Also you acknowledge this points:
- This tutorial includes flashing the system partition of a firmware that is for a different device (Z3 Phone D6603)
- At some point your screen will not display anything
- This will not work on non-LTE versions of the Tablet (SGP611 and SGP612). Instructions for SGP611 can be found there.
- You also will loose all of you data, so please make a Backup.
If you are still sure you want to do this then here are the Steps:
1. Get the firmware ftf (SGP621_23.0.1.A.0.167_CE.ftf) for the SGP621 (for example from here or here)
2. Get a vulnerable firmware ftf (D6603_23.0.A.2.93_Generic_20GLOBAL.ftf) for the Xperia Z3 D6603 (for example from here or here)
3. Get the patched giefroot version for our device here
4. Open Flashtool and select flash. Then select flashmode and press OK
5. Select the 23.0.A.2.93 firmware and select to NOT wipe anything (see Picture 1). In the Exclude mark everything BUT system then start the flash process. If you do something wrong here you ran a VERY HIGH risk of bricking your device permanently
6. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
7. Start your device - you'll notice black bars on the left and right of the picture
8. It should boot up and display lots of errors, but still function
9. Go into Settings -> Backup and Reset -> Factory data reset and make a factory reset from there (It seems wiping in flashtool does not work for some people)
10. Do initial configuration and select enable adb debug and allow mock location in developer options
11. Select Security -> Unknown Sources (If you do not do this, giefroot will not work)
12. Open a shell/command prompt and try if adb shell works and brings you to your device <- This step is important because here you authorize the device for adb access that you need later, please select to authorize the connected computer permanently when asked to do so
13. Open Flashtool and select flash. Then select flashmode and press OK
14 Select the 23.0.A.2.93 firmware and select to NOT wipe anything (see Picture 2). In the Exclude mark everything BUT kernel then start the flash process. If you do something wrong here you ran a VERY HIGH risk of bricking your device permanently
15. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
16. Start your device and notice that the Screen stays pitch black, but you can hear the starting Sound
17. Once the tablet has started, go into the folder where you extracted giefroot and launch the install.bat
18. Wait till it is finished and tells you that you achived root (The device will reboot once while rooting, this is normal)
19. Open Flashtool and select flash. Then select flashmode and press OK
20. Select the SGP621_23.0.1.A.0.167_CE.ftf. Select to NOT wipe anything (see Picture 3). In the Exclude mark everything BUT kernel then start the flash process.
21. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
22. Congratulation. After rebooting you should have a rooted SGP621 with the system of a D6603.
23. Now backup your TA with the tool from here
24. Unlock the bootloader via the instructions from Sony here. Do this only if you have your TA partition backed up!
To install CyanogenMod 12 nightly:
25. Download a CM12 nightly build from here.
26. Unpack the boot.img from the downloaded zip file
27. Go into fastboot mode (press volume up and plug device into computer until led flashes blue).
28. Issue 'fastboot flash boot /path/to/boot.img'
29. Issue 'fastboot reboot'
30. Once the led gets purple press volume down to get into recovery
31. Select install -> install via adb
32. Issue 'adb sideload /path/to/downloaded-zip.zip'
33. Wipe data and cache
34. Reboot and enjoy CyanogenMod
To install rooted Stock:
25. Open Flashtool and select flash. Then select flashmode and press OK
26. Select the SGP621_23.0.1.A.0.167_CE.ftf. Leave everything as it is and start the flash process.
27. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
28. Get the advanced stock kernel from here, boot into fastboot mode, execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img'
29. Download RicDefeat from here.
30. Reboot the device and while booting once the led goes purple press the volume down key.
31. In the recovery tap on Advanced and Install with ADB and swipe to activate ADB
32. Issue 'adb sideload /path/to/RICDefeat.zip' (If sideloading does not work, put the zip file on your sd card and install it from there)
33. After that is finished, exit the recovery. It will ask you if you want to root. Answer yes and exit.
34. Open Flashtool again and select flash. Then select flashmode and press OK
35. Select the SGP621_23.0.1.A.0.167_CE.ftf. Select to NOT wipe anything (see Picture 3). In the Exclude mark everything BUT kernel then start the flash process.
36. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
37. Restore your TA Backup and enjoy root on stock.
Congratulations, you now have a rooted device with either stock or CM12
Update Log
Update 1: I verified that Backup of TA works by reflashing it and checking if DRM is still intact in Service Menu.
Update 2: Changed instructions so wiping is done from the booted firmware directly, because for some users it was not possible to flash userdata from flashtool
Update 3: Added step 11 to enable Unknown Sources as otherwise giefroot will not work
Update 4: Added mirrors for the ftf files
Update 5: Added information to step 12 because it is important to authorize the device
Update 6: Added tutorial link
Update 7: Added tutorial for stock and CM12
Update 8: Update cause new giefroot is able to root our kernel
Thanks to zxz0O0 for giefroot and DevShaft for TA Backup
Good Luck and Have Fun
Your awesome man and thank you I'll give it a try
---------- Post added at 04:12 PM ---------- Previous post was at 03:52 PM ----------
hi boss I don't know if you could make a video on how to do it some of us are not that smart. so if you could please thanks
some screenshots for the "worst" steps too
jaime4272 said:
Your awesome man and thank you I'll give it a try
---------- Post added at 04:12 PM ---------- Previous post was at 03:52 PM ----------
hi boss I don't know if you could make a video on how to do it some of us are not that smart. so if you could please thanks
Click to expand...
Click to collapse
The instructions are very detailed, if you aren't that smart, as you put it, you should not do this process.
I don't know if I will have time to make a video, but I will do some screenshots in a few hours once I am back on my PC
rooting
i suggest taking out variables and automate the entire rooting process. i.e creating a .bat file or program.
why?
i dare say there will be noobs who will screw up the process and brick their tablets.then come crying in xda asking for solutions.
we are dealing with a fw frm another device(even though its in the same family) so there are bound to be risks involved.might as well preempt the possibility of dealing with a grief stricken noob and jus write a rooting progam....
need help with errors
lowtraxx can you tell me what's going on here. I've tried 4 times and I get this error. could you tell what am I doing wrong. I have been following you instructions but I cant get pass the first stage.
jaime4272 said:
lowtraxx can you tell me what's going on here. I've tried 4 times and I get this error. could you tell what am I doing wrong. I have been following you instructions but I cant get pass the first stage.
Click to expand...
Click to collapse
It seems system flashes okay, but the wipe of userdata fails. Could you please try to instead of wiping everything to wipe nothing and only flash system. After that reboot the tablet and you should get a normal bootup with lots of errors. Then go into Settings -> Backup and Reset and make a factory data reset. Then after that finished the tablet reboots and you should get no more errors. Then follow the rest of the steps.
Update: I also changed the tutorial to reflect that problem.
frostmore said:
i suggest taking out variables and automate the entire rooting process. i.e creating a .bat file or program.
why?
i dare say there will be noobs who will screw up the process and brick their tablets.then come crying in xda asking for solutions.
we are dealing with a fw frm another device(even though its in the same family) so there are bound to be risks involved.might as well preempt the possibility of dealing with a grief stricken noob and jus write a rooting progam....
Click to expand...
Click to collapse
I will try to do just that once I have the time. I just wanted to share the way as soon as I could so others that are experienced with flashtool (hence the big red disclaimer ) could try it out while I refine the proccess.
great i will try this!
Hope will succeed. by the way you have mirrors?
infinitylook said:
Hope will succeed. by the way you have mirrors?
Click to expand...
Click to collapse
Mirrors:
D6603_23.0.A.2.93_Generic_20GLOBAL.ftf
SGP621_23.0.1.A.0.167_CE.ftf
great lowtraxx! thank you very very very much it' s a really good workaround!
hi I have run into a little problem after rooting and trying to flash the spg621 rom back it looks like it doesn't and still on z3 and wifi and Bluetooth wont work any idea?
---------- Post added at 10:31 AM ---------- Previous post was at 09:55 AM ----------
when running on cmd giefroot when it says press any key to continue do I just let it be or do I press any key
Follow the giefroot instructions and press a key. For the Wifi and Bluetooth issues; If you flash a update zip you will need to do a factory reset, because otherwise your device could act funny, as configuration data from the D6603 is still there and needs to be erased.
hth
Working for me!
I've managed to get my device back onto rooted stock firmware with locked bootloader and the DRM keys intact. Created a guide for this here.
thank you. ill keep trying even thought i'm a hard time but ill get to it thanks
jaime4272 said:
thank you. ill keep trying even thought i'm a hard time but ill get to it thanks
Click to expand...
Click to collapse
Do not despair. It works, as proven by the people in this thread. You will work it out. For flashing to rooted stock use the tutorial from @CubicU07 in this post.
well I did manage to root even thought I took me some time. but thanks to you lowtraxx I was able to root and backup TA next I will follow his instructions for unloched BL then restore. thanks
Hello, did anybody got it work with the 32gb wifi modell? Thanks a lot
CubicU07 said:
Working for me!
I also managed to get back to rooted stock via the following steps after obtaining root:
1. Backup TA partition using Backup TA.
2. Return to stock unrooted by flashing the SGP621 rom using FlashTool without changing any of the options.
3. Unlock the bootloader (There are various ways to do this, including using FlashTool, just Google for it).
4. Flash the Advanced Stock Kernel by krabappel2548 using FlashTool in FastBoot mode.
5. Download the SuperSU.
6. Using PRFCreator on the SGP621 rom and the SuperSU zip, create a flashable stock rom zip.
7. Copy the resulting zip onto your device.
8. Boot into TWRP on your device and flash the zip.
9. Once complete, restore the TA partition using TA Backup
Note: Restoring TA partition without going back to stock kernel will soft brick your device, thus the need for steps 5 to 8 to return to stock kernel, while retaining root at the same time. This however, means that you lose custom recovery. So if you prefer having custom recovery over getting your DRM keys back into the device and restoring functionality like X-Reality, then skip steps 5 to 9 altogether..
Update: Unfortunately, after a bit of testing, I realized that the root I ended up with, following steps I listed, was not properly installed. I wasn't able to mount system in R/W mode in Root Explorer nor install BusyBox and it seemed like the only way I could make changes to files in the system was via ADB. Since I have no experience at all in Android programming, I'm striking out steps 5 - 9 until someone finds a solution to this. Sorry for anyone who tried this.
Click to expand...
Click to collapse
You need to disable Sony's RIC write protection by inserting the proper kernel module. Look here if the precompiled one works for you. With that you should be able to use the stock kernel (TA intact) WITH r/w to system.
************
First, I am not responsible if you damage your phone in any way.
Also you might back up your phone's data completely because after unlocking bootloader you can lose all your installed data.
*************
So, first step is unlock the bootloader. First go into
Setiing> About Phone > Press Build Number A couple of time until it shows you are a developer now > go back > Developer Options > Turn on USB debugging.
After that, go to your bootloader, by powering off your phone and once it is powered off press the Volume down key + Power button until something appears with a vibration.
Now download adb and fastboot from this link:
http://*******/1Zsyme
After downloading it, install it. And you can install it easily with no problem. Just make a folder in your windows drive of :
C:\Android-adb\
And you are good to go.
Now goto that folder (C:\Android-adb\) and press SHIFT+CTRL+RIGHT-CLICK together or just SHIFT+CTRL first and then RIGHT-CLICK and then click "open command window here".
Now connect your nexus 5 and check if your PC makes a sound like when you connect a external device.
If yes, then you are good to go. Else try connecting it several times to automatically make the PC install any drivers.
After this, go to that DOS type window and write:
fastboot devices
(press enter to activate any command)
If you it shows a serial number then you are doing fine.
After this, write this command in that CMD.exe window:
fastboot oem unlock
and wait until something pop-ups in your phone. It might be a warning, read it carefully and using your volume up or down key cycle through the options and using power button select yes. And it might reboot on it's own else restart manually by pressing the power button for 10 or 15 sec until you see your screen with a unlocked lock which means you have successfully unlocked the device.
Now after that, it's finally time to FLASH recovery file.
For this to happen you need to download CWM latest version from here:
http://*******/1Zt1Fs
It's latest for HAMMERHEAD or NEXUS 5!!!!
Now, again go to the bootloader as described in the beginning.
Now you can also copy the recovery zip file by your data cable of your phone by turning in on normally and also from bootloader.
How to do it from bootloader? Here's how too.
Now you have to be on the bootloader screen. Now goto the same CMD.exe and write:
adb push filename.zip /storage/emulated/0/
adb push filename.img /storage/emulated/0/
If you get any error ask me.
Now it might get some time to be moved to that.
(Data Cable should be attached to do so, also the RECOVERY img file should be in C:\Android-adb\ this folder to be moved to PHONE)
Now, you might have successfully moved the zip file to your phone. So now write this command to flash Recovery.img file:
fastboot flash recovery your_recovery_image_name.img
After this, it will FLASH the recovery file. Until it's installed successfully wait till then.
Once it is FLASHED, now cycle to recovery mode using volume buttons from the BOOTLOADER and wait till it gets there:
Now you will see some options, but you need to flash a zip file so cycle again using volume buttons and select anyone using power button. So select:
install zip
Now select choose zip from /sdcard
Now you are in your internal storage's directory where you moved your zip files from CMD.exe. Just select it and you are done. go back and reboot system now. And you are done.
Don't forget to say thanks if you find it helpful in any way.
Also report to me if you get any errors between in it. By the way, I didn't have any errors in my journey to do this in first time.
You should point out and highlight that unlocking the bootloader will wipe all data.
Sent from my Nexus 5 using Tapatalk 2
You do not need USB debugging for fastboot, you do not need to open fastboot or adb within the directory they are install in, you...
There are already guides, which are more accurate and up to date, to direct people through the process. Who uses CWM?
wangdaning said:
You do not need USB debugging for fastboot, you do not need to open fastboot or adb within the directory they are install in, you...
There are already guides, which are more accurate and up to date, to direct people through the process. Who uses CWM?
Click to expand...
Click to collapse
TWRP not worked for me. I use and recommend CWM. TWRP is full of bugs and does not show errors and hangs. But CWM is the best.
ddimple4 said:
You should point out and highlight that unlocking the bootloader will wipe all data.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I did mentioned but didn't highlight.
Except for the fact that CWM is out of date and not maintained for our device.
---------- Post added at 05:53 AM ---------- Previous post was at 05:52 AM ----------
Except CWM is out of date and not maintained for our device. TWRP is not full of bugs.
What is the point of this thread? Isn't this all common knowledge?
Google says you need to hold VOL UP, VOL DOWN, and POWER to boot into fastboot, but I've used just VOL DOWN and POWER on my N5.
fastboot oem unlock has been superseded by fastboot flashing unlock, though it still works for the N5.
You can download the Android ADK CLI tools from https://developer.android.com/sdk/index.html . Always point to the authoritative source.
You'll need to be in the \platform-tools directory UNLESS you add it to the PATH.
So far's I know, ADB will not push a file while you're in fastboot. You can just flash the recovery file from the directory you have it, e.g. fastboot flash recovery .\your_recovery_image.img.
Very nice of you to post, OP, but you've got a few things wrong in your guide. Read some others to find your errors, and keep writing, Android needs informed enthusiasts and writers.
Yeah, it's 2016. Why was this thread even made? It's either common knowledge, or there are a hundred other guides about doing this.
Plus, who the hell uses cwm these days? Twrp or don't waste your time.
This whole post feels like something from 4 years ago.
GldRush98 said:
Yeah, it's 2016. Why was this thread even made? It's either common knowledge, or there are a hundred other guides about doing this.
Plus, who the hell uses cwm these days? Twrp or don't waste your time.
This whole post feels like something from 4 years ago.
Click to expand...
Click to collapse
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
ChromeJob said:
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
Click to expand...
Click to collapse
Outdated for years.
ChromeJob said:
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
Click to expand...
Click to collapse
It's outdated, no updates. Last I heard some of the CWM team are now contributing to TWRP. It's pretty much the official unofficial Android custom recovery at this point. You will also have a lot of issues trying to flash or update on older versions of TWRP or other recoveries that aren't updated due to file structure changes in newer Android versions.
RoyJ said:
It's outdated, no updates. Last I heard some of the CWM team are now contributing to TWRP. It's pretty much the official unofficial Android custom recovery at this point. You will also have a lot of issues trying to flash or update on older versions of TWRP or other recoveries that aren't updated due to file structure changes in newer Android versions.
Click to expand...
Click to collapse
I see the light. CWM team seem to have abandoned Helium, too; no longer works on systemless root. That's second or third app they've simply gotten bored with and not continued development.